diff --git a/.github/actions-scripts/create-enterprise-issue.js b/.github/actions-scripts/create-enterprise-issue.js index 21a69bd2ab..72e36a0dd3 100755 --- a/.github/actions-scripts/create-enterprise-issue.js +++ b/.github/actions-scripts/create-enterprise-issue.js @@ -86,7 +86,7 @@ async function run() { 'utf8' ) const issueLabels = - milestone === 'release' ? ['enterprise release'] : ['enterprise deprecation', 'priority-3'] + milestone === 'release' ? ['enterprise release'] : ['enterprise deprecation', 'priority-4', 'batch', 'time sensitive'] const issueTitle = `[${nextMilestoneDate}] Enterprise Server ${versionNumber} ${milestone} (technical steps)` const issueBody = `GHES ${versionNumber} ${milestone} occurs on ${nextMilestoneDate}. diff --git a/.github/allowed-actions.js b/.github/allowed-actions.js index c84dca1d41..caf8186623 100644 --- a/.github/allowed-actions.js +++ b/.github/allowed-actions.js @@ -10,8 +10,8 @@ export default [ 'actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f', // v2.2.0 '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 @@ -31,7 +31,6 @@ export default [ '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@65194d8015be7624d231796ddee1cd52a5023cb3', // v2.6 'someimportantcompany/github-actions-slack-message@0b470c14b39da4260ed9e3f9a4f1298a74ccdefd', diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 8818df1437..d1bf204f10 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -9,4 +9,4 @@ updates: - package-ecosystem: 'github-actions' directory: '/' schedule: - interval: weekly + interval: monthly diff --git a/.github/workflows/crowdin.yml b/.github/workflows/crowdin.yml index 395005ddfb..f95686cb34 100644 --- a/.github/workflows/crowdin.yml +++ b/.github/workflows/crowdin.yml @@ -27,6 +27,8 @@ jobs: - name: Sync uses: crowdin/github-action@d7f217268068f1244883a993379d62d816f84f25 with: + # This option enables the transfer of existing translations in this project to Crowdin. + # We explicitly set this to `false` since we only want to use the downloaded translations managed by Crowdin. upload_translations: false download_translations: true create_pull_request: true 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/move-reopened-issues-to-triage.yaml b/.github/workflows/move-reopened-issues-to-triage.yaml index 617dc95182..925ab443ce 100644 --- a/.github/workflows/move-reopened-issues-to-triage.yaml +++ b/.github/workflows/move-reopened-issues-to-triage.yaml @@ -37,5 +37,5 @@ jobs: } } } catch(e) { - console.log(error); + console.log(e); } diff --git a/.github/workflows/notify-when-maintainers-cannot-edit.yaml b/.github/workflows/notify-when-maintainers-cannot-edit.yaml new file mode 100644 index 0000000000..85edabb89b --- /dev/null +++ b/.github/workflows/notify-when-maintainers-cannot-edit.yaml @@ -0,0 +1,64 @@ +name: Notify When Maintainers Cannot Edit + +# **What it does**: Notifies the author of a PR when their PR does not allow maintainers to edit it. +# **Why we have it**: To prevent having to do this manually. +# **Who does it impact**: Open-source. + +on: + pull_request_target: + types: + - opened + +permissions: + pull-requests: write + +jobs: + notify-when-maintainers-cannot-edit: + if: github.repository == 'github/docs' + runs-on: ubuntu-latest + steps: + - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d + with: + script: | + const query = ` + query($number: Int!) { + repository(owner: "github", name: "docs") { + pullRequest(number: $number) { + headRepositoryOwner { + login + } + maintainerCanModify + } + } + } + `; + + const pullNumber = context.issue.number; + const variables = { number: pullNumber }; + + try { + console.log(`Check github/docs#${pullNumber} for maintainer edit access ...`); + const result = await github.graphql(query, variables); + + console.log(JSON.stringify(result, null, 2)); + + const pullRequest = result.repository.pullRequest; + + if (pullRequest.headRepositoryOwner.login === 'github') { + console.log('PR owned by github'); + return; + } + + if (!pullRequest.maintainerCanModify) { + console.log('PR not owned by github and does not have maintainer edits enabled'); + + await github.issues.createComment({ + issue_number: pullNumber, + owner: 'github', + repo: 'docs', + body: "Thanks for submitting a PR to the GitHub Docs project!\n\nIn order to review and merge PRs most efficiently, we require that all PRs grant maintainer edit access before we review them. For information on how to do this, [see the documentation](https://docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)." + }); + } + } catch(e) { + console.log(e); + } 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/staging-deploy-pr.yml b/.github/workflows/staging-deploy-pr.yml index a7e3086157..7b7b5f5da1 100644 --- a/.github/workflows/staging-deploy-pr.yml +++ b/.github/workflows/staging-deploy-pr.yml @@ -79,9 +79,18 @@ jobs: name: prRepoName } } = run - const headLabel = `${prRepoOwner}:${headBranch}` const prIsInternal = owner === prRepoOwner && repo === prRepoName + let headLabel = `${prRepoOwner}:${headBranch}` + + // If the PR is external, prefix its head branch name with the + // forked repo owner's login and their fork repo name e.g. + // "octocat/my-fork:docs". We need to include the fork repo + // name as well to account for an API issue (this will work fine + // if they don't have a different fork repo name). + if (!prIsInternal) { + headLabel = `${prRepoOwner}/${prRepoName}:${headBranch}` + } // If the PR is external, prefix its head branch name with the // forked repo owner's login, e.g. "octocat:docs" 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/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/CONTRIBUTING.md b/CONTRIBUTING.md index 43f7a9e4be..486d910be2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,7 +6,7 @@ Read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approacha In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR. -Use the table of contents icon on the top left corner of the this document to get to a specific section of this guide quickly. +Use the table of contents icon on the top left corner of this document to get to a specific section of this guide quickly. ## New contributor guide diff --git a/README.md b/README.md index dd38f493f9..95b1fbe243 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ This repository contains the documentation website code and Markdown source file GitHub's Docs team works on pre-production content in a private repo that regularly syncs with this public repo. -Use the table of contents icon on the top left corner of the this document to get to a specific section of this guide quickly. +Use the table of contents icon on the top left corner of this document to get to a specific section of this guide quickly. ## Contributing @@ -60,4 +60,4 @@ When using the GitHub logos, be sure to follow the [GitHub logo guidelines](http ## Thanks :purple_heart: -Thanks for all your contributions and efforts towards improving the GitHub documentation. We thank you being part of our ✨ community ✨ ! +Thanks for all your contributions and efforts towards improving the GitHub documentation. We thank you being part of our :sparkles: community :sparkles: ! diff --git a/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png b/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png index 8dde5d07ff..c35ad52b2a 100644 Binary files a/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png and b/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png differ diff --git a/assets/images/help/pull_requests/compare-branch-example.png b/assets/images/help/pull_requests/compare-branch-example.png index 5bce7d268b..7fe08b3c2e 100644 Binary files a/assets/images/help/pull_requests/compare-branch-example.png and b/assets/images/help/pull_requests/compare-branch-example.png differ diff --git a/assets/images/help/repository/code-scanning-library-alert-index.png b/assets/images/help/repository/code-scanning-library-alert-index.png new file mode 100644 index 0000000000..0e668b80ab Binary files /dev/null and b/assets/images/help/repository/code-scanning-library-alert-index.png differ diff --git a/assets/images/help/repository/code-scanning-library-alert-show.png b/assets/images/help/repository/code-scanning-library-alert-show.png new file mode 100644 index 0000000000..ea3891af8d Binary files /dev/null and b/assets/images/help/repository/code-scanning-library-alert-show.png differ diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 5eb3dfcd6f..39495e3ac2 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -134,8 +134,8 @@ Email notifications from {% data variables.product.product_name %} contain the f | --- | --- | | `From` address | This address will always be {% ifversion fpt %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | | `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: | -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes %} +| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: | +| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 %} | `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} ## Choosing your notification settings @@ -144,7 +144,7 @@ Email notifications from {% data variables.product.product_name %} contain the f {% data reusables.notifications-v2.manage-notifications %} 3. On the notifications settings page, choose how you receive notifications when: - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes %} + - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 %} - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt %} - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %} @@ -161,14 +161,14 @@ If "Automatically watch repositories" is disabled, then you will not automatical 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 fpt or ghes > 3.0 or ghae-next %} +2. In the upper-right corner, select the "Watch" drop-down menu to click a watch option. +{% ifversion fpt or ghes > 3.0 or ghae-issue-4910 %} ![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. {% else %} ![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 %} +{% ifversion fpt or ghes > 3.0 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) 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 %} @@ -198,12 +198,8 @@ If you are a member of more than one organization, you can configure each one to 5. Select one of your verified email addresses, then click **Save**. ![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) -{% ifversion not ghae %} -{% ifversion fpt or ghes %} +{% ifversion fpt or ghes or ghae-issue-4864 %} ## {% data variables.product.prodname_dependabot_alerts %} notification options -{% else %} -## Security alert notification options -{% endif %} {% data reusables.notifications.vulnerable-dependency-notification-enable %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index cddd96305f..4df6d439ed 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -114,14 +114,14 @@ To filter notifications for specific activity on {% data variables.product.produ - `is:gist` - `is:issue-or-pull-request` - `is:release` -- `is:repository-invitation`{% ifversion not ghae %} -- `is:repository-vulnerability-alert` +- `is:repository-invitation`{% ifversion fpt or ghes or ghae-issue-4864 %} +- `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt %} - `is:repository-advisory`{% endif %} - `is:team-discussion`{% ifversion fpt %} - `is:discussion`{% endif %} -{% ifversion not ghae %} -For information about reducing noise from notifications for {% ifversion fpt or ghes %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." +{% ifversion fpt or ghes or ghae-issue-4864 %} +For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." {% endif %} You can also use the `is:` query to describe how the notification was triaged. @@ -144,7 +144,7 @@ To filter notifications by why you've received an update, you can use the `reaso | `reason:invitation` | When you're invited to a team, organization, or repository. | `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. | `reason:mention` | You were directly @mentioned. -| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion not ghae %} +| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion fpt or ghes or ghae-issue-4864 %} | `reason:security-alert` | When a security alert is issued for a repository.{% endif %} | `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. | `reason:team-mention` | When a team you're a member of is @mentioned. @@ -163,7 +163,7 @@ For example, to see notifications from the octo-org organization, use `org:octo- {% endif %} -{% ifversion fpt or ghes %} +{% ifversion fpt or ghes or ghae-issue-4864 %} ## {% data variables.product.prodname_dependabot %} custom filters {% ifversion fpt %} @@ -175,8 +175,11 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende For more information about {% data variables.product.prodname_dependabot %}, see "[About managing vulnerable dependencies](/github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies)." {% endif %} -{% ifversion ghes %} -If you use {% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save the `is:repository_vulnerability_alert` custom filter to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +{% ifversion ghes or ghae-issue-4864 %} + +If you use {% data variables.product.prodname_dependabot %} to keep your dependencies-up-to-date, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: +- `is:repository_vulnerability_alert` +- `reason:security_alert` For more information about {% data variables.product.prodname_dependabot %}, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% endif %} diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md index 85dd3fd5d8..ba768003a5 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md @@ -14,7 +14,7 @@ topics: - Profiles shortTitle: Organization's profile --- -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)." +You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories.{% ifversion not ghes and not ghae %} 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)."{% endif %} {% ifversion fpt %}To confirm your organization's identity and display a "Verified" badge on your organization profile page, you must verify your organization's domains with {% 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 %} diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/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 1e711bead9..3bf7997779 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -43,8 +43,8 @@ The repository owner has full control of the repository. In addition to the acti | Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %}{% ifversion ghes = 2.22 or ghes = 3.0 or ghae %} | Delete packages | "[Deleting packages](/packages/learn-github-packages/deleting-a-package)" |{% endif %} | Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes %} -| Receive {% ifversion fpt or ghes %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies | "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" |{% endif %}{% ifversion fpt %} +| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 %} +| Control access to {% data variables.product.prodname_dependabot_alerts %} alerts for vulnerable dependencies | "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt %} | Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | | Manage data use for a private repository | "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)"|{% endif %} | Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | 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/deployment/deploying-to-amazon-elastic-container-service.md b/content/actions/deployment/deploying-to-amazon-elastic-container-service.md index decc02cb95..90f8d5dd6e 100644 --- a/content/actions/deployment/deploying-to-amazon-elastic-container-service.md +++ b/content/actions/deployment/deploying-to-amazon-elastic-container-service.md @@ -21,9 +21,9 @@ shortTitle: Deploy to Amazon ECS ## 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/) when a release is created. +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 there is a push to the `main` branch. -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. +On every new push to `main` 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. ## Prerequisites @@ -67,7 +67,9 @@ 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. +{% ifversion fpt or ghes > 3.0 or ghae %} 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} +{% endif %} ## Creating the workflow @@ -85,8 +87,9 @@ Ensure that you provide your own values for all the variables in the `env` key o name: Deploy to Amazon ECS on: - release: - types: [ created ] + push: + branches: + - main env: AWS_REGION: MY_AWS_REGION # set this to your preferred AWS region, e.g. us-west-1 diff --git a/content/actions/deployment/deploying-to-azure-app-service.md b/content/actions/deployment/deploying-to-azure-app-service.md index 0ea72b7c23..e1fdc88f7e 100644 --- a/content/actions/deployment/deploying-to-azure-app-service.md +++ b/content/actions/deployment/deploying-to-azure-app-service.md @@ -69,13 +69,15 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you 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. +{% ifversion fpt or ghes > 3.0 or ghae %} 5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} +{% endif %} ## 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 when a release is created. +The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when there is a push to the `main` branch. 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`. @@ -85,8 +87,9 @@ Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of {% data reusables.actions.actions-not-certified-by-github-comment %} on: - release: - types: [created] + push: + branches: + - main env: AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name diff --git a/content/actions/deployment/deploying-to-google-kubernetes-engine.md b/content/actions/deployment/deploying-to-google-kubernetes-engine.md index 3affd5041c..044576808a 100644 --- a/content/actions/deployment/deploying-to-google-kubernetes-engine.md +++ b/content/actions/deployment/deploying-to-google-kubernetes-engine.md @@ -21,7 +21,7 @@ shortTitle: Deploy to Google Kubernetes Engine ## 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) when a release is created. +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 there is a push to the `main` branch. 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). @@ -105,9 +105,11 @@ Store the name of your project as a secret named `GKE_PROJECT`. For more informa ### (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). +{% ifversion fpt or ghes > 3.0 or ghae %} ### (Optional) Configure a deployment environment {% data reusables.actions.about-environments %} +{% endif %} ## Creating the workflow @@ -125,8 +127,9 @@ Under the `env` key, change the value of `GKE_CLUSTER` to the name of your clust name: Build and Deploy to GKE on: - release: - types: [created] + push: + branches: + - main env: PROJECT_ID: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %} diff --git a/content/actions/deployment/deploying-with-github-actions.md b/content/actions/deployment/deploying-with-github-actions.md index 3816cb2cbf..46a008279c 100644 --- a/content/actions/deployment/deploying-with-github-actions.md +++ b/content/actions/deployment/deploying-with-github-actions.md @@ -31,13 +31,12 @@ You should be familiar with the syntax for {% data variables.product.prodname_ac ## 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`. +You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, 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 @@ -48,9 +47,6 @@ on: pull_request: branches: - main - release: - types: - - created workflow_dispatch: ``` 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/adding-self-hosted-runners.md b/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 3eae0166a9..8f950feafe 100644 --- a/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -34,7 +34,7 @@ For more information, see "[About self-hosted runners](/github/automating-your-w ## Adding a self-hosted runner to a repository -You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. +You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." {% ifversion fpt %} {% data reusables.repositories.navigate-to-repo %} @@ -55,7 +55,7 @@ You can add self-hosted runners to a single repository. To add a self-hosted run ## Adding a self-hosted runner to an organization -You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. +You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." {% ifversion fpt %} {% data reusables.organizations.navigate-to-org %} @@ -84,7 +84,7 @@ You can add self-hosted runners to an enterprise, where they can be assigned to New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)." {% ifversion fpt %} -To add a self-hosted runner to an enterprise account, you must be an enterprise owner. +To add a self-hosted runner to an enterprise account, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} 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 6e8c8cedca..4b008c7d9e 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 @@ -15,6 +15,24 @@ type: 'overview' 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. +## 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 | + ## Using ephemeral runners for autoscaling {% 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. @@ -44,7 +62,7 @@ You can create your own autoscaling environment by using payloads received from ## Authentication requirements -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. +You can register and delete repository and organization 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: @@ -53,22 +71,8 @@ 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. +- For organizations, assign the `organization_self_hosted_runners` permission. -## Recommended autoscaling solutions +You can register and delete enterprise self-hosted runners using [the API](/rest/reference/enterprise-admin#github-actions). To authenticate to the API, your autoscaling implementation can use an access token. -{% 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 | +Your access token will requite the `manage_runners:enterprise` scope. diff --git a/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index f452d220b5..fab3383f9f 100644 --- a/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -33,7 +33,7 @@ When new runners are created, they are automatically assigned to the default gro ## Creating a self-hosted runner group for an organization -All organizations have a single default self-hosted runner group. Organizations within an enterprise account can create additional self-hosted groups. Organization admins can allow individual repositories access to a runner group. +All organizations have a single default self-hosted runner group. Organizations within an enterprise account can create additional self-hosted groups. Organization admins can allow individual repositories access to a runner group. For information about how to create a self-hosted runner group with the REST API, see "[Self-hosted runner groups](/rest/reference/actions#self-hosted-runner-groups)." Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can move a runner from the default group to any group you create. @@ -83,7 +83,7 @@ When creating a group, you must choose a policy that defines which repositories ## Creating a self-hosted runner group for an enterprise -Enterprises can add their self-hosted runners to groups for access management. Enterprises can create groups of self-hosted runners that are accessible to specific organizations in the enterprise account. Organization admins can then assign additional granular repository access policies to the enterprise runner groups. +Enterprises can add their self-hosted runners to groups for access management. Enterprises can create groups of self-hosted runners that are accessible to specific organizations in the enterprise account. Organization admins can then assign additional granular repository access policies to the enterprise runner groups. For information about how to create a self-hosted runner group with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). Self-hosted runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can assign the runner to a specific group during the registration process, or you can later move the runner from the default group to a custom group. diff --git a/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 3449230a0c..c6c1fd3d32 100644 --- a/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -26,7 +26,7 @@ shortTitle: Remove self-hosted runners {% endnote %} -To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. +To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." {% data reusables.github-actions.self-hosted-runner-reusing %} {% ifversion fpt %} @@ -53,7 +53,7 @@ To remove a self-hosted runner from a user repository you must be the repository {% endnote %} -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. +To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)." {% data reusables.github-actions.self-hosted-runner-reusing %} {% ifversion fpt or ghes > 3.1 or ghae-next %} @@ -81,7 +81,7 @@ To remove a self-hosted runner from an organization, you must be an organization {% data reusables.github-actions.self-hosted-runner-reusing %} {% ifversion fpt %} -To remove a self-hosted runner from an enterprise account, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. +To remove a self-hosted runner from an enterprise account, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. For information about how to add a self-hosted runner with the REST API, see the [Enterprise Administration GitHub Actions APIs](/rest/reference/enterprise-admin#github-actions). {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} 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/essential-features-of-github-actions.md b/content/actions/learn-github-actions/essential-features-of-github-actions.md index c7e0e98f47..783af1c28e 100644 --- a/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -92,6 +92,8 @@ jobs: name: output-log-file ``` +To download an artifact from the same workflow run, your download job should specify `needs: upload-job-name` so it doesn't start until the upload job finishes. + For more information about artifacts, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)." ## Next steps diff --git a/content/actions/learn-github-actions/reusing-workflows.md b/content/actions/learn-github-actions/reusing-workflows.md index 5b12f1de73..69335e1298 100644 --- a/content/actions/learn-github-actions/reusing-workflows.md +++ b/content/actions/learn-github-actions/reusing-workflows.md @@ -45,10 +45,9 @@ 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. * 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. diff --git a/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index f598b1f9a1..3d0e049a3b 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -358,7 +358,7 @@ jobs: -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "Caching dependencies to speed up workflows." +{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "Caching dependencies to speed up workflows." ## Artifacts diff --git a/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index ed7d96f0fd..bf3fba1a92 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -334,7 +334,7 @@ cache: npm -{% data variables.product.prodname_actions %} caching is only applicable to {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "Caching dependencies to speed up workflows." +{% data variables.product.prodname_actions %} caching is only applicable for repositories hosted on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "Caching dependencies to speed up workflows." ## Examples of common tasks diff --git a/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index 30c760de4a..0307e8dc5e 100644 --- a/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -33,7 +33,7 @@ When you enable {% data variables.product.prodname_GH_advanced_security %} for y - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)." - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/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 %}, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." ## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %} diff --git a/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md deleted file mode 100644 index 1532379e8d..0000000000 --- a/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -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/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md new file mode 100644 index 0000000000..ac0441f81a --- /dev/null +++ b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md @@ -0,0 +1,114 @@ +--- +title: Enabling the dependency graph and Dependabot alerts on your enterprise account +intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and {% data variables.product.prodname_dependabot %} alerts in repositories in your instance.' +shortTitle: Enable dependency analysis +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 + - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Enterprise owners 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.product_location %}.' +versions: + ghes: '*' + ghae: "issue-4864" +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- +## About alerts for vulnerable dependencies on {% data variables.product.product_location %} + +{% data reusables.dependabot.dependabot-alerts-beta %} + +{% data variables.product.prodname_dotcom %} identifies vulnerable dependencies in repositories and creates {% data variables.product.prodname_dependabot_alerts %} on {% data variables.product.product_location %}, using: + +- Data from the {% data variables.product.prodname_advisory_database %} +- The dependency graph service + +For more information about these features, 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)." + +### About synchronization of data from the {% data variables.product.prodname_advisory_database %} + +{% data reusables.repositories.tracks-vulnerabilities %} + +You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} 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 %}. + +### About generation of {% data variables.product.prodname_dependabot_alerts %} + +If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}. + +## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.product_location %} + +### Prerequisites + +For {% data variables.product.product_location %} to detect vulnerable dependencies and generate {% data variables.product.prodname_dependabot_alerts %}: +- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghae %}This also enables the dependency graph service. {% endif %}{% ifversion ghes or ghae-next %}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)."{% endif %} +{% ifversion ghes %}- You must enable the dependency graph service.{% endif %} +- You must enable vulnerability scanning. + +{% ifversion ghes %} +{% 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 %} +{% 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 +{% endif %}{% ifversion ghes < 3.2 %} +### 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 %}. +{% endif %} + +### Enabling {% data variables.product.prodname_dependabot_alerts %} + +{% ifversion ghes %} +Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above. +{% endif %} + +{% 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", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**. + ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + + {% tip %} + + **Tip**: 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. + + {% endtip %} + +## Viewing vulnerable dependencies on {% data variables.product.product_location %} + +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/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md index 936179700c..0c74dbfd23 100644 --- a/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md +++ b/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -18,7 +18,7 @@ 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-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud shortTitle: Connect enterprise accounts --- 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/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 41b3f86bc2..ff7127a926 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -8,6 +8,7 @@ versions: fpt: '*' ghes: '>=3.0' ghae: '*' +miniTocMaxHeadingLevel: 3 redirect_from: - /github/managing-security-vulnerabilities/managing-alerts-from-automated-code-scanning - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning @@ -58,6 +59,25 @@ To calculate the security severity of an alert, we use Common Vulnerability Scor By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +### About labels for alerts that are not found in application code + +{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert. + +- **Generated**: Code generated by the build process +- **Test**: Test code +- **Library**: Library or third-party code +- **Documentation**: Documentation + +{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files. + +Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occuring in library code. + +![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png) + +On the alert page, you can see that the filepath is marked as library code (`Library` label). + +![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png) + ## Viewing the alerts for a repository Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." @@ -112,14 +132,7 @@ If you enter multiple filters, the view will show alerts matching _all_ these fi ### 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 -- Documentation - -{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. At this time, you cannot manually categorize source files. +You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. See "[About labels for alerts not in application code](#about-labels-for-alerts-that-are-not-found-in-application-code)" above for more information about the types of code that are not application code. {% ifversion fpt or ghes > 3.1 %} diff --git a/content/code-security/getting-started/github-security-features.md b/content/code-security/getting-started/github-security-features.md index d996978f5a..21524f7ca5 100644 --- a/content/code-security/getting-started/github-security-features.md +++ b/content/code-security/getting-started/github-security-features.md @@ -19,9 +19,9 @@ topics: The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-issue-4864 %} ## Available for all repositories - +{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} ### Security policy @@ -39,9 +39,11 @@ View alerts about dependencies that are known to contain security vulnerabilitie and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} -{% ifversion ghes > 2.22 %} +{% ifversion ghes > 2.22 or ghae-issue-4864 %} ### {% data variables.product.prodname_dependabot_alerts %} +{% data reusables.dependabot.dependabot-alerts-beta %} + View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% endif %} @@ -51,6 +53,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." {% endif %} +{% ifversion fpt or ghes > 2.22 or ghae-issue-4864 %} ### Dependency graph The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository. @@ -75,7 +78,7 @@ Automatically detect security vulnerabilities and coding errors in new or modifi {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 %} ### Dependency review Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." diff --git a/content/code-security/getting-started/securing-your-organization.md b/content/code-security/getting-started/securing-your-organization.md index 18a5dd3333..06e5dc9aeb 100644 --- a/content/code-security/getting-started/securing-your-organization.md +++ b/content/code-security/getting-started/securing-your-organization.md @@ -32,26 +32,32 @@ You can create a default security policy that will display in any of your organi {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-issue-4864 %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph -By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all repositories owned by your organization. +{% ifversion fpt %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %} and a dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. 1. Click your profile photo, then click **Organizations**. 2. Click **Settings** next to your organization. 3. Click **Security & analysis**. 4. Click **Enable all** or **Disable all** next to the feature that you want to manage. -5. Optionally, select **Automatically enable for new repositories**. - -For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." - +5. Optionally, select **Automatically enable for new repositories**. {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% data reusables.dependabot.dependabot-alerts-beta %} +{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} + +For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +{% endif %} + +{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 %} ## Managing dependency review -Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. Dependency review is available in all public repositories and in repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." +Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. +{% ifversion fpt %}Dependency review is available in all public repositories. For private and internal repositories you require a license for {% data variables.product.prodname_advanced_security %}. To enable dependency review for an organization, enable the dependency graph and enable {% data variables.product.prodname_advanced_security %}. +{% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %} +For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." {% endif %} @@ -79,7 +85,11 @@ To enable {% data variables.product.prodname_dependabot_version_updates %}, you {% ifversion fpt or ghes > 2.22 or ghae %} ## Managing {% data variables.product.prodname_GH_advanced_security %} +{% ifversion fpt or ghes > 2.22 %} If your organization has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features. +{% elsif ghae %} +You can enable or disable {% data variables.product.prodname_advanced_security %} features. +{% endif %} 1. Click your profile photo, then click **Organizations**. 2. Click **Settings** next to your organization. diff --git a/content/code-security/getting-started/securing-your-repository.md b/content/code-security/getting-started/securing-your-repository.md index 6c5db69453..0cd76f6db9 100644 --- a/content/code-security/getting-started/securing-your-repository.md +++ b/content/code-security/getting-started/securing-your-repository.md @@ -46,36 +46,47 @@ For more information, see "[Adding a security policy to your repository](/code-s {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-issue-4864 %} ## Managing the dependency graph -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 %} +{% ifversion fpt %} +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 all public repositories, and you can choose to enable it for private repositories. 1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**. 2. Click **Security & analysis**. 3. Next to Dependency graph, click **Enable** or **Disable**. +{% endif %} + +{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-issue-4864 %} ## Managing {% data variables.product.prodname_dependabot_alerts %} -By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.prodname_dependabot_alerts %} can also be enabled for private repositories. +{% ifversion fpt %}By default, {% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and generates {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.prodname_dependabot_alerts %} can also be enabled for private repositories. 1. Click your profile photo, then click **Settings**. 2. Click **Security & analysis**. 3. Click **Enable all** next to {% data variables.product.prodname_dependabot_alerts %}. +{% endif %} + +{% data reusables.dependabot.dependabot-alerts-beta %} +{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt %}" and "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}." {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 %} ## Managing dependency review -Dependency review lets you visualize dependency changes in pull requests before they are merged into your repository. Dependency review is available in all public repositories and in repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." +Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. +{%- ifversion fpt %}Dependency review is available in all public repositories. For private and internal repositories you require a license for {% data variables.product.prodname_advanced_security %}. To enable dependency review for a repository, enable the dependency graph and enable {% data variables.product.prodname_advanced_security %}. +{%- elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the repository (see below).{% endif %} +For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." {% endif %} diff --git a/content/code-security/supply-chain-security/index.md b/content/code-security/supply-chain-security/index.md index 35d491cbc0..7c5b9896dc 100644 --- a/content/code-security/supply-chain-security/index.md +++ b/content/code-security/supply-chain-security/index.md @@ -8,6 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" topics: - Dependabot - Dependencies diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md index 95b97fcd16..f0ae2031bd 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md @@ -9,6 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" type: overview topics: - Dependabot @@ -29,11 +30,13 @@ When your code depends on a package that has a security vulnerability, this vuln ## Detection of vulnerable dependencies +{% data reusables.dependabot.dependabot-alerts-beta %} + {% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when: {% ifversion fpt %} - A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %} -- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} +- New advisory data is synchronized to {% data variables.product.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} - The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)." {% data reusables.repositories.dependency-review %} @@ -59,7 +62,7 @@ For information about permission requirements for actions related to {% data var {% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." {% endif %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)." +When {% data variables.product.product_name %} identifies a vulnerable dependency, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies)." {% ifversion fpt %} For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md index bf8cfaf46b..617cbaf274 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies.md @@ -1,12 +1,13 @@ --- title: About managing vulnerable dependencies -intro: '{% data variables.product.prodname_dotcom %} helps you to avoid using third-party software that contains known vulnerabilities.' +intro: '{% data variables.product.product_name %} helps you to avoid using third-party software that contains known vulnerabilities.' redirect_from: - /github/managing-security-vulnerabilities/about-managing-vulnerable-dependencies - /code-security/supply-chain-security/about-managing-vulnerable-dependencies versions: fpt: '*' ghes: '>=3.2' + ghae: "issue-4864" type: overview topics: - Dependabot @@ -20,7 +21,7 @@ shortTitle: Vulnerable dependencies --- -{% data variables.product.prodname_dotcom %} provides the following tools for removing and avoiding vulnerable dependencies. +{% data variables.product.product_name %} provides the following tools for removing and avoiding vulnerable dependencies. ## Dependency graph The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and {% data variables.product.prodname_dependabot %}. @@ -33,13 +34,12 @@ For more information, see "[About the dependency graph](/github/visualizing-repo By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." ## {% data variables.product.prodname_dependabot_alerts %} -{% data variables.product.prodname_dotcom %} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.prodname_dotcom %} also notifies the maintainers of the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +{% data variables.product.product_name %}} can create {% data variables.product.prodname_dependabot_alerts %} when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. {% data variables.product.product_name %} also notifies the maintainers of the repository, according to their notification preferences. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% ifversion fpt %} ## {% data variables.product.prodname_dependabot_security_updates %} -When {% data variables.product.prodname_dotcom %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +When {% data variables.product.product_name %} generates a {% data variables.product.prodname_dependabot %} alert for a vulnerable dependency in your repository, {% data variables.product.prodname_dependabot %} can automatically try to fix it for you. {% data variables.product.prodname_dependabot_security_updates %} are automatically generated pull requests that update a vulnerable dependency to a fixed version. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." ## {% data variables.product.prodname_dependabot_version_updates %} Enabling {% data variables.product.prodname_dependabot_version_updates %} takes the effort out of maintaining your dependencies. With {% data variables.product.prodname_dependabot_version_updates %}, whenever {% data variables.product.prodname_dotcom %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. By contrast, {% data variables.product.prodname_dependabot_security_updates %} only raises pull requests to fix vulnerable dependencies. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates)." - {% endif %} diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md index af52aab171..c77f640f10 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md @@ -8,6 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" type: how_to topics: - Dependabot @@ -27,10 +28,11 @@ When {% data variables.product.prodname_dependabot %} detects vulnerable depende {% ifversion fpt %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." {% endif %} -{% ifversion ghes %} -By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.{% endif %} +{% ifversion ghes or ghae-issue-4864 %} +By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email. -{% ifversion ghes %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-dependabot-alerts)."{% endif %} +Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." +{% endif %} ## Configuring notifications for {% data variables.product.prodname_dependabot_alerts %} diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md index 7b11941310..5ccafe24ed 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md @@ -10,6 +10,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" topics: - Repositories - Dependabot diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index 3a2b5d8728..eedd2c9707 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -8,6 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" type: how_to topics: - Dependabot @@ -33,7 +34,7 @@ The results of dependency detection reported by {% data variables.product.produc * {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." * {% ifversion fpt %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." - {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes > 2.22 %} and synchronized to {% data variables.product.prodname_ghe_server %}{% endif %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." + {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes > 2.22 or ghae-issue-4864 %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." ## Why don't I get vulnerability alerts for some ecosystems? diff --git a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md index 269b999909..834f3f8200 100644 --- a/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ b/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md @@ -6,10 +6,11 @@ redirect_from: - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository - /code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository permissions: Repository administrators and organization owners can view and update dependencies. -shortTitle: Fix vulnerable dependencies +shortTitle: View vulnerable dependencies versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" type: how_to topics: - Dependabot @@ -19,7 +20,7 @@ topics: - Pull requests - Repositories --- -Your repository's {% data variables.product.prodname_dependabot %} alerts tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts using the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +Your repository's {% data variables.product.prodname_dependabot %} alerts tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can sort the list of alerts by selecting the drop-down menu, and you can click into specific alerts for more details. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% ifversion fpt %} You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." @@ -43,17 +44,17 @@ You can enable automatic security updates for any repository that uses {% data v 1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**. ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button.png) 1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/github/administering-a-repository/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)." -1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, use the "Dismiss" drop-down, and click a reason for dismissing the alert. +1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert. ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) -{% elsif ghes > 3.0 %} +{% elsif ghes > 3.0 or ghae-issue-4864 %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-dependabot-alerts %} 1. Click the alert you'd like to view. ![Alert selected in list of alerts](/assets/images/enterprise/graphs/click-alert-in-alerts-list.png) 1. Review the details of the vulnerability and determine whether or not you need to update the dependency. -1. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert. Alternatively, if you decide not to update the dependency, click the **Dismiss** drop-down, and select a reason for dismissing the alert. +1. When you merge a pull request that updates the manifest or lock file to a secure version of the dependency, this will resolve the alert. Alternatively, if you decide not to update the dependency, select the **Dismiss** drop-down, and click a reason for dismissing the alert. ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/enterprise/repository/dependabot-alert-dismiss-drop-down.png) {% else %} diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 5ee2dcae9c..bc28ed03cc 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -6,6 +6,7 @@ shortTitle: Dependency review versions: fpt: '*' ghes: '>= 3.2' + ghae: "issue-4864" type: overview topics: - Advanced Security @@ -25,10 +26,14 @@ redirect_from: If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities. +{% ifversion fpt %} Dependency review is available in: * All public repositories. * Private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license that have the dependency graph enabled. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." +{% elsif ghes or ghae %} +Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. +{% endif %} Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities. @@ -40,4 +45,4 @@ Dependency review supports the same languages and package management ecosystems ## Enabling dependency review -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 %} +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 or ghae %}For more information, see "[Enabling the dependency graph and Dependabot alerts on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index dbefc9a770..89cbde2016 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -7,6 +7,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" type: overview topics: - Dependency graph @@ -19,18 +20,20 @@ shortTitle: Dependency graph ## Dependency graph availability -The dependency graph is available for every{% ifversion fpt %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% ifversion fpt %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} +{% ifversion fpt %}The dependency graph is available for every public repository that defines dependencies in a supported package ecosystem using a supported file format. Repository administrators can also set up the dependency graph for private repositories.{% endif %} + +{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} ## About the dependency graph The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% ifversion fpt %}: - Dependencies, the ecosystems and packages it depends on -- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} +- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.product_name %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% ifversion fpt %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae %} When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." {% endif %} @@ -61,7 +64,7 @@ You can use the dependency graph to: {% ifversion fpt %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} -{% ifversion ghes %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% ifversion ghes or ghae %}If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% ifversion fpt %} and every push to other repositories in the graph{% endif %}. @@ -73,7 +76,7 @@ The recommended formats explicitly define which versions are used for all direct | --- | --- | --- | ---| | Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | | `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -{%- ifversion fpt or ghes > 3.2 %} +{%- ifversion fpt or ghes > 3.2 or ghae %} | Go modules | Go | `go.sum` | `go.mod`, `go.sum` | {%- elsif ghes = 3.2 %} | Go modules | Go | `go.mod` | `go.mod` | diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index 32328b16b9..ff7c1313e9 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -12,6 +12,7 @@ redirect_from: versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" type: how_to topics: - Dependency graph @@ -23,8 +24,6 @@ shortTitle: Explore dependencies ## Viewing the dependency graph -{% data reusables.repositories.enable-security-alerts %} - The dependency graph shows the dependencies{% ifversion fpt %} and dependents{% endif %} of your repository. For information about the detection of dependencies and which ecosystems are supported, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% data reusables.repositories.navigate-to-repo %} @@ -33,6 +32,10 @@ The dependency graph shows the dependencies{% ifversion fpt %} and dependents{% 4. Optionally, under "Dependency graph", click **Dependents**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %} +{% ifversion ghes or ghae-issue-4864 %} +Enterprise owners can configure the dependency graph at an enterprise level. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." +{% endif %} + ### Dependencies view {% ifversion fpt %} @@ -44,14 +47,14 @@ If vulnerabilities have been detected in the repository, these are shown at the {% endif %} -{% ifversion ghes %} +{% ifversion ghes or ghae %} Any direct and indirect dependencies that are specified in the repository's manifest or lock files are listed, grouped by ecosystem. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_alerts %}. ![Dependencies graph](/assets/images/help/graphs/dependencies_graph_server.png) {% note %} -**Note:** {% data variables.product.prodname_ghe_server %} does not populate the **Dependents** view. +**Note:** {% data variables.product.product_name %} does not populate the **Dependents** view. {% endnote %} diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index 248a09ef3a..1abe7ab3e4 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -3,6 +3,7 @@ title: Understanding your software supply chain versions: fpt: '*' ghes: '>=3.0' + ghae: "issue-4864" topics: - Dependency graph - Dependencies diff --git a/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index ce94a9c86b..4c45a1c172 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -17,7 +17,7 @@ redirect_from: - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces --- -By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. +By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read and write permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust. To manage which users in your organization can use {% data variables.product.prodname_codespaces %}, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." diff --git a/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md index aed13b8a56..b4359aaaa2 100644 --- a/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ b/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md @@ -97,7 +97,7 @@ Permission | Description [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/repos#statuses). Can be one of: `none`, `read`, or `write`. -[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes %} +[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghae-issue-4864 %} `vulnerability_alerts`| Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Can be one of: `none` or `read`.{% endif %} `watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. diff --git a/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/content/get-started/using-git/pushing-commits-to-a-remote-repository.md index f0673fcf58..2ab5e3afee 100644 --- a/content/get-started/using-git/pushing-commits-to-a-remote-repository.md +++ b/content/get-started/using-git/pushing-commits-to-a-remote-repository.md @@ -112,7 +112,7 @@ For more information on working with forks, see "[Syncing a fork](/articles/sync ## Further reading - [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/ch5-2.html) -- [`git remote` man page](https://git-scm.com/docs/git-remote.html) +- [`git remote` main page](https://git-scm.com/docs/git-remote.html) - "[Git cheatsheet](/articles/git-cheatsheet)" - "[Git workflows](/github/getting-started-with-github/git-workflows)" - "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" diff --git a/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 847033abb2..10993eed58 100644 --- a/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -5,6 +5,7 @@ product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' + ghae: "issue-4864" type: how_to topics: - Pull requests diff --git a/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md index bdb9455df7..a008c6e4b2 100644 --- a/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md +++ b/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md @@ -18,7 +18,7 @@ redirect_from: {% ifversion ghes %} By default, if your site administrator has configured email for notifications on your enterprise, you will receive {% ifversion ghes %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} by email.{% endif %} -{% ifversion ghes %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% ifversion ghes %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} ## Configuring notifications for {% ifversion ghes %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} diff --git a/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index c4b076b715..904e0de854 100644 --- a/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -3,8 +3,6 @@ title: Customizing your organization's profile intro: You can share information about your organization by customizing your organization's profile versions: fpt: '*' - ghes: '*' - ghae: '*' topics: - Organizations shortTitle: Customize organization profile diff --git a/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md index 19c9f7eae0..b0b78ebcc7 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -34,7 +34,7 @@ The page that's displayed allows you to enable or disable all security and analy {% ifversion ghes > 3.0 %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} -{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features.{% endif %} +{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %} ## Enabling or disabling a feature for all existing repositories @@ -91,10 +91,10 @@ You can enable or disable features for all repositories. {% ifversion fpt %}The 1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)." 2. Under "Configure security and analysis features", to the right of the feature, enable or disable the feature by default for new repositories{% ifversion fpt %}, or all new private repositories,{% endif %} in your organization. - {% ifversion fpt or ghes > 3.1 %} + {% ifversion fpt %} ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png) {% endif %} - {% ifversion ghes = 3.1 %} + {% ifversion ghes > 3.0 %} ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) {% endif %} {% ifversion ghes = 3.0 %} diff --git a/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md index 8733b1d3cb..54f669e6e2 100644 --- a/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -66,9 +66,9 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. | [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% ifversion fpt %} | [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." -| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion not ghae %} +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt %} | [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} -| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% ifversion not ghae %} +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt %} | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot %} alerts. {% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} | [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." @@ -636,7 +636,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). | `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). -{% endif %}{% ifversion not ghae %} +{% endif %}{% ifversion fpt %} ### `repository_dependency_graph` category actions @@ -653,7 +653,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion fpt %}private {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion fpt %}private {% endif %}repository. -{% endif %}{% ifversion not ghae %} +{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 %} ### `repository_vulnerability_alert` category actions | Action | Description diff --git a/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md index 6d00bad4cc..37b046cbc7 100644 --- a/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ b/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -141,20 +141,20 @@ Some of the features listed below are limited to organizations using {% data var In this section, you can find the repository permission levels required for security features, such as {% data variables.product.prodname_advanced_security %} features. | Repository action | Read | Triage | Write | Maintain | Admin | -|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes > 2.22 %} +|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 %} | Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | | [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designate additional people or teams to receive {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) for vulnerable dependencies | | | | | **X** |{% endif %}{% ifversion fpt %} +| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt %} | Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% ifversion fpt %} -| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 3.1 %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% ifversion fpt %} +| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 %} | [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %} | [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next %} -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** | -| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**[1] | **X**[1] | **X** |{% endif %}{% ifversion ghes = 3.0 %} +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |{% ifversion fpt or ghes > 3.0 or ghae %} +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** | +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes = 3.0 %} | [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** | -| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 2.22 %} +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | | | **X** |{% endif %}{% ifversion fpt or ghes > 2.22 or ghae-issue-4864 %} | [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} 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/viewing-activity-and-data-for-your-repository/about-the-dependency-graph.md b/content/repositories/viewing-activity-and-data-for-your-repository/about-the-dependency-graph.md index 27ede81180..ebb70d132b 100644 --- a/content/repositories/viewing-activity-and-data-for-your-repository/about-the-dependency-graph.md +++ b/content/repositories/viewing-activity-and-data-for-your-repository/about-the-dependency-graph.md @@ -42,7 +42,7 @@ You can use the dependency graph to: ## Enabling the dependency graph -{% ifversion ghes %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% ifversion ghes %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %} When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository. diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md index 018935cbc7..881c4fd1af 100644 --- a/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md +++ b/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md @@ -1,6 +1,7 @@ --- title: Understanding connections between repositories 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." +product: '{% data reusables.gated-features.repository-insights %}' redirect_from: - /articles/viewing-a-repository-s-network - /articles/viewing-a-repositorys-network @@ -24,8 +25,7 @@ shortTitle: Connections between repositories ## Viewing a repository's network -'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 %}' +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. ![Repository network graph](/assets/images/help/graphs/repo_network_graph.png) @@ -65,7 +65,7 @@ Forks are listed alphabetically by the username of the person who forked the rep 3. In the left sidebar, click **Forks**. ![Forks tab](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-issue-4864 %} ## Viewing the dependencies of a repository You can use the dependency graph to explore the code your repository depends on. diff --git a/content/rest/reference/permissions-required-for-github-apps.md b/content/rest/reference/permissions-required-for-github-apps.md index 63bd6772fd..88bb18d6a3 100644 --- a/content/rest/reference/permissions-required-for-github-apps.md +++ b/content/rest/reference/permissions-required-for-github-apps.md @@ -142,11 +142,11 @@ _Search_ - [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (:write) - [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (:write) - [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (:write) -{% ifversion fpt -%} - [`GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (:read) - [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (:read) - [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (:read) - [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (:write) +{% ifversion fpt or ghes -%} - [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write) - [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write) {% endif -%} @@ -894,7 +894,7 @@ _Teams_ - [`GET /repos/:owner/:repo/code-scanning/sarifs/:sarif_id`](/rest/reference/code-scanning#get-information-about-a-sarif-upload) (:read) {% endif -%} -{% ifversion fpt %} +{% ifversion fpt or ghes %} ### Permission on "self-hosted runners" - [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (:read) - [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (:write) diff --git a/contributing/content-style-guide.md b/contributing/content-style-guide.md index 2c720343be..64c6ef3b31 100644 --- a/contributing/content-style-guide.md +++ b/contributing/content-style-guide.md @@ -4,7 +4,7 @@ Welcome to the content style guide for [GitHub Docs](https://docs.github.com/). These guidelines are specific to GitHub’s documentation. For general style questions or guidance on topics not covered here, see the [GitHub Brand Guide](https://brand.github.com/content/) first, then the [Microsoft Style Guide](https://docs.microsoft.com/style-guide/welcome/). For markup specific to source content on docs.github.com, see our [markup reference guide](content-markup-reference.md). -Use table of contents icon on the top left corner of the this document to get to a specific section of this guide quickly. +Use table of contents icon on the top left corner of this document to get to a specific section of this guide quickly. ## The GitHub Docs approach to style 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/release-notes/enterprise-server/3-0/17.yml b/data/release-notes/enterprise-server/3-0/17.yml new file mode 100644 index 0000000000..ab0a13b159 --- /dev/null +++ b/data/release-notes/enterprise-server/3-0/17.yml @@ -0,0 +1,25 @@ +date: '2021-10-12' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/27034, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' + bugs: + - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26971, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' + - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26986, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' + - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26992, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' + - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27081, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' + - 'Pre-receive hook environments were forbidden from calling the cat command via BusyBox on Alpine. {% comment %} https://github.com/github/enterprise2/pull/27114, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' + - 'The external database password was logged in plaintext. {% comment %} https://github.com/github/enterprise2/pull/27172, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' + - 'An erroneous `jq` error message may have been displayed when running `ghe-config-apply`. {% comment %} https://github.com/github/enterprise2/pull/27203, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' + - 'Failing over from a primary Cluster datacenter to a secondary Cluster datacenter succeeds, but then failing back over to the original primary Cluster datacenter failed to promote Elasticsearch indicies. {% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}' + - 'The Site Admin page for repository self-hosted runners returned an HTTP 500. {% comment %} https://github.com/github/github/pull/194205 {% endcomment %}' + - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}' + changes: + - 'More effectively delete Webhook logs that fall out of the Webhook log retention window. {% comment %} https://github.com/github/enterprise2/pull/27157 {% 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/data/release-notes/enterprise-server/3-1/9.yml b/data/release-notes/enterprise-server/3-1/9.yml new file mode 100644 index 0000000000..be28140c54 --- /dev/null +++ b/data/release-notes/enterprise-server/3-1/9.yml @@ -0,0 +1,28 @@ +date: '2021-10-12' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/27035, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' + bugs: + - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26972, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' + - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26987, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' + - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26993, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' + - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27082, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' + - 'With Actions configured, MSSQL replication would fail after restoring from a GitHub Enterprise Backup Utilities snapshot. {% comment %} https://github.com/github/enterprise2/pull/27097, https://github.com/github/enterprise2/pull/26254 {% endcomment %}' + - 'An erroneous `jq` error message may have been displayed when running `ghe-config-apply`. {% comment %} https://github.com/github/enterprise2/pull/27194, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' + - 'Pre-receive hook environments were forbidden from calling the cat command via BusyBox on Alpine. {% comment %} https://github.com/github/enterprise2/pull/27115, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' + - 'The external database password was logged in plaintext. {% comment %} https://github.com/github/enterprise2/pull/27173, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' + - 'Failing over from a primary Cluster datacenter to a secondary Cluster datacenter succeeds, but then failing back over to the original primary Cluster datacenter failed to promote Elasticsearch indicies. {% comment %} https://github.com/github/github/pull/193181, https://github.com/github/github/pull/192447 {% endcomment %}' + - 'The "Import teams" button on the Teams page for an Organization returned an HTTP 404. {% comment %} https://github.com/github/github/pull/193302 {% endcomment %}' + - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194260, https://github.com/github/github/pull/193609 {% endcomment %}' + - 'Performance was negatively impacted in certain high load situations as a result of the increased number of `SynchronizePullRequestJob` jobs. {% comment %} https://github.com/github/github/pull/195253, https://github.com/github/github/pull/194591 {% endcomment %}' + changes: + - 'More effectively delete Webhook logs that fall out of the Webhook log retention window. {% comment %} https://github.com/github/enterprise2/pull/27158 {% 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/data/release-notes/enterprise-server/3-2/1.yml b/data/release-notes/enterprise-server/3-2/1.yml new file mode 100644 index 0000000000..9b770774ce --- /dev/null +++ b/data/release-notes/enterprise-server/3-2/1.yml @@ -0,0 +1,27 @@ +date: '2021-10-12' +sections: + security_fixes: + - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/27118, https://github.com/github/enterprise2/pull/27110 {% endcomment %}' + bugs: + - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26973, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' + - 'In a GitHub Enterprise Server clustering configuration, Dependency Graph settings could have been incorrectly applied. {% comment %} https://github.com/github/enterprise2/pull/26981, https://github.com/github/enterprise2/pull/26861 {% endcomment %}' + - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26988, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' + - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26994, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' + - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27083, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' + - 'Pre-receive hook environments were forbidden from calling the cat command via BusyBox on Alpine. {% comment %} https://github.com/github/enterprise2/pull/27116, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' + - 'Failing over from a primary Cluster datacenter to a secondary Cluster datacenter succeeds, but then failing back over to the original primary Cluster datacenter failed to promote Elasticsearch indicies. {% comment %} https://github.com/github/github/pull/193182, https://github.com/github/github/pull/192447 {% endcomment %}' + - 'The "Import teams" button on the Teams page for an Organization returned an HTTP 404. {% comment %} https://github.com/github/github/pull/193303 {% endcomment %}' + - 'Using the API to disable Secret Scanning correctly disabled the property but incorrectly returned an HTTP 422 and an error message. {% comment %} https://github.com/github/github/pull/193455, https://github.com/github/github/pull/192907 {% endcomment %}' + - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194262, https://github.com/github/github/pull/193609 {% endcomment %}' + - 'Performance was negatively impacted in certain high load situations as a result of the increased number of `SynchronizePullRequestJob` jobs. {% comment %} https://github.com/github/github/pull/195256, https://github.com/github/github/pull/194591 {% endcomment %}' + - 'A user defined pattern created for Secret Scanning would continue getting scanned even after it was deleted. {% comment %} https://github.com/github/token-scanning-service/pull/1039, https://github.com/github/token-scanning-service/pull/822 {% endcomment %}' + changes: + - 'GitHub Apps now set the Secret Scanning feature on a repository consistently with the API. {% comment %} https://github.com/github/github/pull/193456, https://github.com/github/github/pull/193125 {% 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. + - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/reusables/dependabot/dependabot-alerts-beta.md b/data/reusables/dependabot/dependabot-alerts-beta.md new file mode 100644 index 0000000000..f353647fdd --- /dev/null +++ b/data/reusables/dependabot/dependabot-alerts-beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae-issue-4864 %} +{% note %} + +**Note:** {% data variables.product.prodname_dependabot_alerts %} is currently in beta and is subject to change. + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md new file mode 100644 index 0000000000..893925af22 --- /dev/null +++ b/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md @@ -0,0 +1,3 @@ +{% ifversion ghes or ghae-issue-4864 %} +The dependency graph and {% data variables.product.prodname_dependabot_alerts %} are configured at an enterprise level by the enterprise owner. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." +{% endif %} \ No newline at end of file diff --git a/data/reusables/notifications-v2/custom-notification-types.md b/data/reusables/notifications-v2/custom-notification-types.md index 2299c52284..764de9a21f 100644 --- a/data/reusables/notifications-v2/custom-notification-types.md +++ b/data/reusables/notifications-v2/custom-notification-types.md @@ -1,2 +1,5 @@ -{%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}issues, pulls requests, releases, security alerts, or discussions{% endif %} -{%- ifversion ghes = 3.1 %}issues, pull requests, releases, or discussions{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} +issues, pulls requests, releases, security alerts, or discussions +{%- else %}issues, pull requests, releases, or discussions +{% endif %} + \ No newline at end of file diff --git a/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md index 5dcf1f62d3..6a3d822bf9 100644 --- a/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md +++ b/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -1,5 +1,3 @@ -{% ifversion fpt %} +{% ifversion fpt or ghes or ghae-issue-4864 %} You can choose the delivery method and frequency of notifications about {% data variables.product.prodname_dependabot_alerts %} on repositories that you are watching or where you have subscribed to notifications for security alerts. -{% else %} -You can choose the delivery method for notifications about {% ifversion ghes %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} on repositories that you are watching, as well as the frequency at which the notifications are sent to you. {% endif %} diff --git a/data/reusables/notifications/vulnerable-dependency-notification-options.md b/data/reusables/notifications/vulnerable-dependency-notification-options.md index 8755ccfbd1..cda795559e 100644 --- a/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,15 +1,15 @@ -{% ifversion fpt or ghes > 3.1 %} -{% ifversion fpt %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 %}By default, if your site administrator has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 %} +{% ifversion fpt %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} - by email, an email is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option). - in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option). - on the command line, warnings are displayed as callbacks when you push to repositories with any vulnerable dependencies (**Command Line** option). -- in your inbox, as web notifications. A web notification is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Web** option). -- on {% data variables.product.prodname_mobile %}, as web notifications. For more information, see "[Enabling push notifications with GitHub for mobile](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)." +- in your inbox, as web notifications. A web notification is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Web** option).{% ifversion not ghae %} +- on {% data variables.product.prodname_mobile %}, as web notifications. For more information, see "[Enabling push notifications with GitHub for mobile](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)."{% endif %} {% note %} -**Note:** The email and web/{% data variables.product.prodname_mobile %} notifications are: +**Note:** The email and web{% ifversion not ghae %}/{% data variables.product.prodname_mobile %}{% endif %} notifications are: - _per repository_ when {% data variables.product.prodname_dependabot %} is enabled on the repository, or when a new manifest file is committed to the repository. diff --git a/data/reusables/repositories/dependency-review.md b/data/reusables/repositories/dependency-review.md index 26db7a1360..4c29e05ad2 100644 --- a/data/reusables/repositories/dependency-review.md +++ b/data/reusables/repositories/dependency-review.md @@ -1,3 +1,3 @@ -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 %} Additionally, {% data variables.product.prodname_dotcom %} can review any dependencies added, updated, or removed in a pull request made against the default branch of a repository, and flag any changes that would introduce a vulnerability into your project. This allows you to spot and deal with vulnerable dependencies before, rather than after, they reach your codebase. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." {% endif %} diff --git a/data/reusables/repositories/enable-security-alerts.md b/data/reusables/repositories/enable-security-alerts.md index a0128f368c..66d4792347 100644 --- a/data/reusables/repositories/enable-security-alerts.md +++ b/data/reusables/repositories/enable-security-alerts.md @@ -1,3 +1,3 @@ -{% ifversion ghes %} -Your site administrator must enable {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." +{% ifversion ghes or ghae-issue-4864 %} +Enterprise owners must enable {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)." {% endif %} 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 6d861afeb4..5dcc5da963 100644 --- a/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -250,6 +250,8 @@ Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif 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{% endif %} +{%- ifversion fpt or ghes > 3.3 %} +Twilio | Twilio Access Token | twilio_access_token{% 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 %} 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/lib/languages.js b/lib/languages.js index 145df84cd0..dc0e9bfc63 100644 --- a/lib/languages.js +++ b/lib/languages.js @@ -31,7 +31,7 @@ const languages = { nativeName: 'Español', code: 'es', hreflang: 'es', - dir: 'translations/es-XL', + dir: 'translations/es-ES', wip: false, }, pt: { diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index c82322056b..9333f5f0ec 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -34625,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", @@ -74936,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 7cf45346bf..8faaeba7a1 100644 --- a/lib/rest/static/decorated/ghes-2.22.json +++ b/lib/rest/static/decorated/ghes-2.22.json @@ -65978,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 2327ce7805..4916798ce3 100644 --- a/lib/rest/static/decorated/ghes-3.0.json +++ b/lib/rest/static/decorated/ghes-3.0.json @@ -70781,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 319958f8fc..95e6dc7c68 100644 --- a/lib/rest/static/decorated/ghes-3.1.json +++ b/lib/rest/static/decorated/ghes-3.1.json @@ -71471,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 d08018ba60..02d4780872 100644 --- a/lib/rest/static/decorated/ghes-3.2.json +++ b/lib/rest/static/decorated/ghes-3.2.json @@ -73661,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 744c44a2ea..faeaf0d0bc 100644 --- a/lib/rest/static/decorated/github.ae.json +++ b/lib/rest/static/decorated/github.ae.json @@ -26928,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", @@ -64212,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 c61c04816b..be0d439d5a 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -141562,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", @@ -331431,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 786a2d8233..680135e364 100644 --- a/lib/rest/static/dereferenced/ghes-2.22.deref.json +++ b/lib/rest/static/dereferenced/ghes-2.22.deref.json @@ -294768,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 45d76732d0..c4864e54ac 100644 --- a/lib/rest/static/dereferenced/ghes-3.0.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.0.deref.json @@ -301609,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 ca3e109c3e..c7b6ee435d 100644 --- a/lib/rest/static/dereferenced/ghes-3.1.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json @@ -305497,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 1b101f6a22..5c2d170a1c 100644 --- a/lib/rest/static/dereferenced/ghes-3.2.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json @@ -312377,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 ad833af10d..341e70907c 100644 --- a/lib/rest/static/dereferenced/github.ae.deref.json +++ b/lib/rest/static/dereferenced/github.ae.deref.json @@ -96891,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", @@ -278856,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/search/indexes/github-docs-2.22-cn-records.json.br b/lib/search/indexes/github-docs-2.22-cn-records.json.br index 18b4c97a17..4aadb7fe57 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:4786eac6d91a286e44907bc2d77730aadfed4107e45be39eefbbd18dc9063867 -size 525249 +oid sha256:a8356def70ed33b01a0daa1e0e02bf01a422d60fb01fa97dae5f2869c7d70de7 +size 527440 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 dad6124c13..251c88f22a 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:5e78cba601b62dd9925d706d77de43b84f85ea548ec6c9a5862cced2dbf8d86e -size 868608 +oid sha256:93f772a1e644eff798d9ca2b2a2abd95a62c93200e7a8904ccb863043f2668f1 +size 883095 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 18b26450bd..7a6edd0ac3 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:c21f8de4e35f987bf316b15712222743a94a5671d88f32857d918c0bb8a8c0ea -size 479315 +oid sha256:5085cba9d37e0b402383f8f3e326cffde01417c930fd2df78359980e434872cb +size 481235 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 0e3103cc15..677e87c4aa 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:74f97029e12af7a55a04ba2f7c72827cced9f2c8a2643d4b83e89edd1a7f6789 -size 2126348 +oid sha256:f279e08ddaadecb62e2228e9e2873c9d2d8031cb36268e0c1f7b999f96fef699 +size 2140522 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 b5693c28f6..970d26e81e 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:4695d77158ba8b8879d86d60209b89fa09d5ec3b61dbd2a0c1e27351faf6a265 -size 433907 +oid sha256:659741a9102ee5c69473027ed3440379adc6e1d123ce0866705ababc16aae75d +size 433789 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 db205b23b0..0f03a0f236 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:065beb0dab03b00adfca5d3b1c0e14983884036ee00a423da66726e79cd53315 -size 1695238 +oid sha256:488b28b5a01c9af757105a919f5f74da25ec754f14da60bc252dcca60e93fab5 +size 1694743 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 3ffb71cdda..5525775f3f 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:0a7e4aad5d5315eba97767d2876fb4396612ceac3800368e20d483c302377487 -size 195215 +oid sha256:95922d64a40aa341c29ec45489454d49b084197ff46c35dad59ab1128d7d3d41 +size 187115 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 730a861754..c6d347e459 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:ae1b7f168c8cb82cfb0b996d49753e6dd36e3e4e2b74377c7366ae18aa4b9b1c -size 702352 +oid sha256:e1aef3d19b30ee99b600f4861d5c3b18deb84d74cc6c6f08d9eb9e5d4c121d40 +size 658160 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 e4e4cf6444..4ba9024e35 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:9af02343813ca642cea70c38fb51b5b2ce66ee90f2c3695d80278013d69d04c1 -size 545302 +oid sha256:89610819421985327459a57e961cd4052ba8947c4e35c8ca477d9173b288f815 +size 547796 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 3563fc46a5..f0ac95b9e1 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:8132659e84dd00449f4195c908a939f886c1da71b48cfb46afbec8dbde49b022 -size 2880437 +oid sha256:c9f1f5e87e73e2eb085acc1f4db948fa92fd772c3400723160de500d52a4688e +size 2898975 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 17789ddf57..671172d7b6 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:544350152b0948f19243e8eb5865c15a5b208bbd68e67f78023cc7e5c77f007c -size 456740 +oid sha256:52cffd2ce7d913a8fd4005b18f85c06dcb17fe1e6949ba1ea67fd64502102490 +size 457070 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 e75494a0f9..cef6c426b5 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:074b6dfc8a1ad7332151c25be849ab4e825c9474220b71764007f122326bf5ef -size 1905240 +oid sha256:782faef7162121b7d2429a0829220bf8f637ca1adf6e03db2afa5258d6bc0251 +size 1886436 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 2821e2065f..6980ef84a5 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:64838182757ba5ba7587d8dda2135a0139e0fce41cf5c47c09b002d48eb35b1c -size 544927 +oid sha256:1851b648979fc28bc0dff607367b8fdbb59a18362eca09ceac36c7d303e986ac +size 547028 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 a0a99e0377..2316c4a04b 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:e4d66fff24c25b293e47d7a79e27fc41e51e23da14fc0d64bc76e3caf8571b32 -size 906610 +oid sha256:78f9d90262ce021878bf75b61f1e83b240eada12f9c22631aebc4a0eeaff7272 +size 922809 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 48319917c3..b4594ebe44 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:6df1e2b959f980bdac8968b644b6ce9f2b4d0d7c79c352204517eeff32bbd1de -size 499705 +oid sha256:ff24b07832cff76b970f90bba3f4b5e8ef5f09b079707bb2bf03b5ab28f21f07 +size 501928 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 1349c50d73..c1b34e5710 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:b577b17eedc8922274b87450de36e78b39f07730844838cdc08938fa10fba04f -size 2233168 +oid sha256:138efbce24d4c856ac287376df530d2c8bdf22d273735345368e2a1a4bad2833 +size 2247106 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 dfdd828b8c..8de5842150 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:bd6f1ffb6dc02b5c63c300f34f6f5fb4a6bfaac208b713b43ab0e745334adc4f -size 454039 +oid sha256:7ec35c64523e6868280d0f9bf1cb96d7518bdc5ab2a540434eeb9c86ea724ec6 +size 454197 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 0fa16d95aa..60307e0d7f 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:468ab24a5a3f93b0e503a02377891ca687f3de92ccecf3cd62c0598f3c8c4d7d -size 1770272 +oid sha256:41d2bfcb5d0af671a90150c8bfd0d87d2b69024ae6c941f1fdd84eff0d2688a2 +size 1769470 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 9acaa1caab..f416506274 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:f4b3165f99658751b42ddd6195b0401e0261114287de5c23890166fc23e3602b -size 193628 +oid sha256:476505198f26985c07d48df67b65193eb9cf5188f7c87f916a4685776d7b19eb +size 185721 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 f07ea4353d..7837be3dce 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:7577690f8c9ce729e9fee72b9fd1fe21820178b1625ad97f7f696c56b01aca34 -size 694548 +oid sha256:015e8fd6c77ed9fd01835fd9b670cab9f4159de8026cf6cf9d50ef0a9be3303d +size 650327 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 50279e6676..9d8710718f 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:267f8ddc97996b73e00761e84eea6c84bad95cf238d76ada16be360acc4c916e -size 567780 +oid sha256:31199b067cdd460fb6f88fec0083b2cb5f09bce372d448f410ad5e9a25d33f02 +size 570158 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 ad73a6e6df..16dd40c483 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:aab73428acea608f97813f7adfbcf338df7d2e6e67061e24a7a90848f6a91c5b -size 3007131 +oid sha256:b49b217eb8b42e78ec9afec4ca03f4c09fb1677e5410106bc84bb4b2ff4a2ef5 +size 3023912 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 ca53650f77..1ac559f8ad 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:43dda86cf90c32b6d022e2bc853581e03ec0d35f34d54805ffa278330f18dc2c -size 477700 +oid sha256:f03c346dea1e0fef8384321603cc49cbc086346dccc9af879e11a0dd54eada65 +size 477211 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 3b46228129..aaeabdc4c1 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:c28c5b93e1d20b0c9a4a045dbaefcb1a86ab4d145465159f381c6747fcd57e67 -size 1993277 +oid sha256:559de8f0aec0252819ec3fb6c7c10573d042a18fb904df21b9d3a0396fda765a +size 1972002 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 d1cfabaa7c..820b49c7fa 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:cde9f9bc5b5ef87c2383a460cc632ada9397e7c70007d754e26ce31ffe14630c -size 557584 +oid sha256:9f472189dbe08ddda1370bdf2f2e1ce5f02ac809d8b88005139244d4bde49d1a +size 560785 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 6a91a8ea21..1a9f9fb513 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:b12e74ae38d4174f9791c838c8b630a4e1fd55aecfa02b6c63a6d7b0ec0b05ec -size 929609 +oid sha256:0d8ad367352418c3b1c4c9afda2115351dfdd1fb61d93b3fc04999689d2fecae +size 950719 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 ef0ac9b935..276f836a40 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:d92314c347e062ec7a52a4f2550e30d2804a369d722d279deeba2e3aa216e591 -size 508699 +oid sha256:85f209a72786a0d0f6cc7422f55470229c1fd28fba8e10cc527c2467ad6fcc62 +size 511585 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 b2eaf5eeaf..5bd0124b8a 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:c778e3cfd1afbfef7e74f29c74aa5a8860be4369712f4b848d9ee002df68f082 -size 2284796 +oid sha256:38f33d1e2213eb26179909c21bceda28d498d06e32a3c8457604bb185daacdb8 +size 2304581 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 7944c89ceb..cf68d01e42 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:3a9d9381ca12047a3625b5bde9e9b7d2a6517c38f72d371f00c21d43c4e049f8 -size 464144 +oid sha256:94938a6551020b21e326a5450c00d28d27dad39b99315c82523b16a839691fe9 +size 464365 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 acb48ab58d..cf06cd48d0 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:e53c63ea0b5041bc8ce5f980e18594455428b9725ca32510e999f56f2451f4e1 -size 1813533 +oid sha256:0ffd54699179f1f6dcd31a30791d77e7a5bc7d103338cca325f537ae6f9e8600 +size 1813221 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 3d0f5c97d0..c880069edb 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:5fdd4627561520d2e9a04f908df5b0e53e13ca48ffa8d8d38b9bf5a55d834040 -size 193648 +oid sha256:0bfc0fc8753452bf1b985e2fc23a8d9987e9b3f4fd8b926a0a61c5dac6da5314 +size 185700 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 23389969c6..59fb1c56a2 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:77198f0851b1cc1261a3cc2971af6d0fc8c9a270664c3a885317c7c23b50e10f -size 694199 +oid sha256:d7132a6b6b3c30edfebdb606876b33995d183f993766fda83cb2208383307b14 +size 650089 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 20bc1a6a61..472c4a03ed 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:7f86bcbe9ed743aed2f30f8c73ee9a734daef2b3abfa805d2eb2780ccc84cd87 -size 580035 +oid sha256:0e80e28034e08902d76964500473b1a81ce0a68a2a24d20fe2f7d14723c890fe +size 583237 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 5ecf393cba..317fd3824f 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:8e924568813c5158f3c4122d1e436637648e8503cfdfa22a12544b6cd8d84fec -size 3073509 +oid sha256:3a32f35223949a6d1096472e259e5fbc9b4a407168fee1c79db7da0b0d4a826a +size 3102326 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 aaf6cbdad8..bf0ca8bd9d 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:eeb3538b82c8fbdefe78e0aec99ae1bfb08ae5cc60e24beabf02d61cd5c3f0b9 -size 487118 +oid sha256:ed1871848ab7f62cae678b686f1acd1b784a4e8f7ef0b7e665bbf573d2158451 +size 487591 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 c9ebb2a074..c44be9120c 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:636a9044b704af85f600189de1249627ca9a8dbeb5908ca2d87a90d8e2043f57 -size 2036685 +oid sha256:d110f00509feed0d30e67e12ff5142b6f6a2a5be72bd3e19ffceae243db36548 +size 2018840 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 73a8f98344..f1e7673b59 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:6c8a0d06c907ae0a2f1f2a5470cc10a53b7fcacb8d4c6721904bcb2c96c32056 -size 567937 +oid sha256:8d97bcffebeb11650ee0a7f0514a70c3eb89bbf76f882afc34f664a0be4efb11 +size 571661 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 cda4091448..8cac2dade8 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:52d75eee9c962d2557fe7bebd3c214ad2f1a9fe17373ff7e825d9c8a32c01411 -size 949359 +oid sha256:d4e58260a9ff9346dfb2eaafb4dab6341fe6071f3471f65e1ac8c5ec9ca89f52 +size 970450 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 e51d8bcf63..ce1a48be95 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:bceae6b35d4a505b8a77c14774fe8b680641679604e64d636190de529fa8188f -size 517641 +oid sha256:4939e08b81bdec2cca978a42fcf6ace07c155410056279f7e321a4f17143b2a9 +size 520536 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 6747df4208..fe14eb8dc6 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:3c1fa6440aaa0ffb4a29753c7e0ab9da402811f5c174699f0307b43536c71a6c -size 2333276 +oid sha256:2a8f09da6eb4c1061f481300ff9e24fd4ecba8acc813fcf41d4889ef6cb70d52 +size 2351645 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 b8a7d2f390..18732c3c5f 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:bb59275fbe4a8863cf767ca8e79fd79dd25ba7363db285c176cba72a9d2afe05 -size 472643 +oid sha256:dff569c4f11428a54ba025071541057c50ff7026fbee6ece4f7207b0f1693894 +size 472021 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 9b9dc5ef82..eb4edd34dd 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:e4d0f2784b83810fcad0f76812e727df38a160cd3e4ad7e985280574f4a091a9 -size 1844893 +oid sha256:d2b1ea6c50957a3bae39950744e3a34ec809c66cae6f86b2035df9b15e866a27 +size 1845507 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 35130cf7dd..ff8f7e25f6 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:6c1a327461095f007d05dc2062e1b61ddd095e53d7cc04243cd7b988060a4bca -size 193702 +oid sha256:db41328e2020adffd8f1fc2a882ae227856ede6369aa70db4c38c502e588050c +size 185720 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 a076356207..29af2d6518 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:4454113a231a3214d387eba0153102719e676bfce7ce6ce382f36987f1580376 -size 694160 +oid sha256:ef51c341919a540d149c59a985c66cdc9f6b5857bde36dbeacdff9c36b50e099 +size 650082 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 20028c3798..847fd27d85 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:17b32ec1a96a08da0daf36c6e24f9a8c20e79f7b794cebbcfa1ea4c1547745d8 -size 590408 +oid sha256:cad8b8df9d6176cc869780f5715b5d6243a62b2a30e36d2480c43187f425a212 +size 593796 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 b41b8122ab..7b4cf08a3e 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:618858821456bc98f3ea8ec275a840af31d398373eece9fb81d7ff824d620ddc -size 3140224 +oid sha256:61810283ffa964be6274076c622c425ae6e717f3c14f3e6139934df9e6a376bf +size 3167064 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 c041bfe0e7..44283b3680 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:82097965f2013c4feb628aa78226a7df19a2928d212706f4a2ecf657716fa703 -size 496899 +oid sha256:031c8f9c72e2e5fb4a0b3c05931faafd0a32ec8986bfe5354d85e63c7f4f7ebe +size 497001 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 688d194f93..17c6dcbabc 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:8a901edfc7a27a1d23839a76b04ccab0e5eea9e4980095908260356d1b56e407 -size 2079110 +oid sha256:648c9468b2c456ae9f68167264cfc44ffb16d5f2a3cbb75e8b9ca840c8f4acd1 +size 2055768 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 66820b06f4..7b3b1e838d 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:a6d70bed7bf2da642689bbd977a69516ed6e0b5d8b18102d0a46ab49840563bd -size 770387 +oid sha256:0a9f0d99f1a4d8776d41c8171a802d090df524a8065f8a8c00d3053e876bae2a +size 781753 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 7482d656bf..9b995fe071 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:5f44f6bea73e1b8b541d6c50d08119f6b7700607e1b91a0b4ce3ca66f0c84a38 -size 1171387 +oid sha256:3e0359619a593cf99fb6c2bf66e4e8a87ec797dad8eb85fd4d7d4c36dfd4201d +size 1233297 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 cceee259df..2c14c28d49 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:cada21a62e21789ae7e6af3f4d5895aa812ad50e2b1feeff66c010962c906828 -size 690576 +oid sha256:0d8b384f2042dd85b0646ad3b02b4e398d9bdf4831daf468bc19ecf1147f886c +size 701607 diff --git a/lib/search/indexes/github-docs-dotcom-de.json.br b/lib/search/indexes/github-docs-dotcom-de.json.br index 7c839d2eab..41fc659f7a 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:40c92ca695273e1bb0de9ccc5d223651d2ba0edea403816137c918d31b0d10aa -size 3124808 +oid sha256:f66bc908316a6b33d71c5cdad9bc75cfa913dfdada91062fce6fe340a68fcea0 +size 3191576 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 e816fed2f4..02691b0db1 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:57bf9e8e1ee54c70425c255fc64ad41e52f3ddfa950d31294eff285f5d054602 -size 639166 +oid sha256:e1af7f559b8a54181215d141f781218f99818c3f21db333e7cee5382980214bf +size 639731 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 3515f25184..d75680abac 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:951d067b784a87ca618148b2e370548ff009a0816c41445dfeac7b75b1d30524 -size 2428888 +oid sha256:f570efe43fb66c80b45a1e3384d25ecd98999d568e9b84c8e70a1f84abe8d74e +size 2431702 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 b172e38b98..3703599aa8 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:a8ae578d42c9758d362d54c4ac728dd754719a2d326f9a01ba803010d6919ea3 -size 205226 +oid sha256:fb00ef168b702edcd7653ce198e1f1c77b725580e09ee6ad35419513f9e4750e +size 195223 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 86d7dca44c..8c2c515b3d 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:936921fef9219f5b7646381b127020df9b94ab2445c892bfcb0972eb21e1fd88 -size 650902 +oid sha256:85fb55536ee90e38dd68245c0b79af69eb85a4423cb8b4e67c0d6aeeb498a90c +size 615937 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 dcf61460db..5fbaa52113 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:0d5e81d5413dfc952d70c30df1af4c6958a50d6c6449165bf7e7c2e2f073415a -size 795122 +oid sha256:2d79e6b62924216b1d928331cd86e3cc62bbea7111bf81b4898666391ee1b57f +size 805631 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 924fcf9546..17132fa15a 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:5f649fe3416979b42c196665b7d8bf2102e1880a993d533d2d1b429f1c2eb29f -size 4151520 +oid sha256:8a7021dea44e48c8af33f8fbcec622015948dc368a6d244ff167308f15ef6dcd +size 4232342 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 fdf06dd992..82f86dc762 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:6c43d354d8c5b57134f6e0b58776dd7b41f1588ceef9c966c7181ea26f873acf -size 669455 +oid sha256:bb0d2bf864fe1811640bee0c610cf63b288ad3955c61f26fd637573e4d939113 +size 676806 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 5c7a725877..cf2c103d12 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:724e39433cef2f97502cf154f264cf1f25d37b12914343dac69f2fcf7031602f -size 2750153 +oid sha256:841bae19d721ad5f0baaa13026b0e4e46ebb820060525124abc47df27ae96a5e +size 2742893 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 64ad8eb6be..0320a5b096 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:a71b4237a5088d121ec92b3afaf5b88502c7a19b2e6d337c128720e74713b315 -size 433589 +oid sha256:8f3152f0ab29b2699408079b9a6100e3b7959f52b67b11bf0433f76aaa3558f5 +size 437794 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 6f4c3c7342..d6157b21dd 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:2c122e07f270df80c8bb8bdb1fbfc8e00a2a03601176a035ecdf9c7263bbcc6d -size 691580 +oid sha256:3843c70807ade81b220c256121eb1da82ef855b3db1edef007db30d476f31f26 +size 712130 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 a46ca8f265..27c2828fc6 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:71592596f4b71e18683c19853977546db42ac4faf50a94874a02223252de2da4 -size 400534 +oid sha256:24da70d24e87e5afcccc1d31c78b396af7fc3c224120b83807d66454e487ee27 +size 403774 diff --git a/lib/search/indexes/github-docs-ghae-de.json.br b/lib/search/indexes/github-docs-ghae-de.json.br index 647be9c43b..54cba7c0a6 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:7136dbd85ca3c2838f1fe0001953284d68ae8d72cb856cf02c3b9b65465a9345 -size 1741762 +oid sha256:571d75239963a4273ab3fa498dad1401b2dfe645fffd51766f737841c38fc683 +size 1759166 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 4834c5df63..ffa57447be 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:0cf3737c615d34ee4f9679f010f0fe4122a463b24772da894e083873f9199f3b -size 365611 +oid sha256:f2db91f9e70d4b3d265ddb22518f1a1b7957f9aea1bbe5f7fa7c6a2b8cec668d +size 365814 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index f96b92ff2a..47ade6ce86 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:d00bfd3a278f1feb8436970976386dfe28fa73abde814d9a98f37f1351901440 -size 1358729 +oid sha256:fb206003ea252d7e1cca4cf879e5b51ffb51bb8418e7bbb4481e9bee203328a0 +size 1359759 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 6ddc5f425f..8f546fcdb6 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:a17db2d27cfc0dda56102444a35626415074686ea06bab37a9212ee5dc2382a6 -size 130810 +oid sha256:6b647b9ea848cd0dc3814554da58d17f112a6a80fa2cd7b4a965e405a6cc7392 +size 121318 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index ebdace580e..1a3ccc5f6f 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:2af973d2d165d31b5e1a4bee25ef8750d7fdbf7b649bbdd19d1a63d1041c9c8c -size 420075 +oid sha256:779bc3817f03f9381e170651159892a0abeb58270f7b8d977357a06b8267421d +size 386570 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 ec2648feb1..b5a582bb08 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:7ea485e34b695129bcaaaf7e636b5e49c5c32c59f427614c041bcab3f7c8b854 -size 453042 +oid sha256:17aeb7b505f9aab3ecfd1c7543e4e95a11e42c603255c0627509116a154a1f69 +size 457157 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index 4757defb6b..4157d6726f 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:04d8df49a99dee76c6f0e29df051d1e22b1cdbfab23afda4ab01e0f0a4054ecd -size 2296689 +oid sha256:686bc906b2497df001afce475eb855ae142c931785337906860735c8ec114b54 +size 2322296 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 ac2e7595b1..44ac7e89de 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:9bd443425df118380cea6fa76a84a358dc46200ad6b1b5120c2935beece77f38 -size 385008 +oid sha256:efc10247081330fcde0c18a83a7853d4e175fb277765cd16804a1c5fff1586a6 +size 385384 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index e34e8306bd..672fc036a0 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:c8f944435d164d63c0bcd87ad6da2cb054c7cdb617284a025a487a2d54b42a93 -size 1536838 +oid sha256:7b67461657b03e44eee1a66c8a928506ad5b2ea9c8084793bb46ed1c8386e4a5 +size 1524879 diff --git a/package-lock.json b/package-lock.json index c0e750e3db..94990c7b34 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,31 +90,31 @@ "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", - "@typescript-eslint/eslint-plugin": "^4.31.1", + "@typescript-eslint/eslint-plugin": "^4.33.0", "@typescript-eslint/parser": "^4.31.1", "async": "^3.2.1", "await-sleep": "0.0.1", @@ -137,8 +137,8 @@ "eslint-plugin-node": "^11.1.0", "eslint-plugin-promise": "^5.1.0", "event-to-promise": "^0.8.0", - "glob": "^7.1.7", - "graphql": "^15.5.3", + "glob": "^7.2.0", + "graphql": "^15.6.1", "heroku-client": "^3.1.0", "http-status-code": "^2.1.0", "husky": "^7.0.2", @@ -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.3", "make-promises-safe": "^5.1.0", "minimatch": "^3.0.4", "mkdirp": "^1.0.4", @@ -161,7 +161,7 @@ "npm-merge-driver-install": "^2.0.1", "object-hash": "^2.2.0", "postcss": "^8.3.6", - "prettier": "^2.4.0", + "prettier": "^2.4.1", "replace": "^1.2.1", "rimraf": "^3.0.2", "robots-parser": "^2.3.0", @@ -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": "*", @@ -4228,15 +4228,16 @@ } }, "node_modules/@typescript-eslint/eslint-plugin": { - "version": "4.31.1", - "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-4.31.1.tgz", - "integrity": "sha512-UDqhWmd5i0TvPLmbK5xY3UZB0zEGseF+DHPghZ37Sb83Qd3p8ujhvAtkU4OF46Ka5Pm5kWvFIx0cCTBFKo0alA==", + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-4.33.0.tgz", + "integrity": "sha512-aINiAxGVdOl1eJyVjaWn/YcVAq4Gi/Yo35qHGCnqbWVz61g39D0h23veY/MA0rFFGfxK7TySg2uwDeNv+JgVpg==", "dev": true, "dependencies": { - "@typescript-eslint/experimental-utils": "4.31.1", - "@typescript-eslint/scope-manager": "4.31.1", + "@typescript-eslint/experimental-utils": "4.33.0", + "@typescript-eslint/scope-manager": "4.33.0", "debug": "^4.3.1", "functional-red-black-tree": "^1.0.1", + "ignore": "^5.1.8", "regexpp": "^3.1.0", "semver": "^7.3.5", "tsutils": "^3.21.0" @@ -4258,6 +4259,53 @@ } } }, + "node_modules/@typescript-eslint/eslint-plugin/node_modules/@typescript-eslint/scope-manager": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-4.33.0.tgz", + "integrity": "sha512-5IfJHpgTsTZuONKbODctL4kKuQje/bzBRkwHE8UOZ4f89Zeddg+EGZs8PD8NcN4LdM3ygHWYB3ukPAYjvl/qbQ==", + "dev": true, + "dependencies": { + "@typescript-eslint/types": "4.33.0", + "@typescript-eslint/visitor-keys": "4.33.0" + }, + "engines": { + "node": "^8.10.0 || ^10.13.0 || >=11.10.1" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/typescript-eslint" + } + }, + "node_modules/@typescript-eslint/eslint-plugin/node_modules/@typescript-eslint/types": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-4.33.0.tgz", + "integrity": "sha512-zKp7CjQzLQImXEpLt2BUw1tvOMPfNoTAfb8l51evhYbOEEzdWyQNmHWWGPR6hwKJDAi+1VXSBmnhL9kyVTTOuQ==", + "dev": true, + "engines": { + "node": "^8.10.0 || ^10.13.0 || >=11.10.1" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/typescript-eslint" + } + }, + "node_modules/@typescript-eslint/eslint-plugin/node_modules/@typescript-eslint/visitor-keys": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-4.33.0.tgz", + "integrity": "sha512-uqi/2aSz9g2ftcHWf8uLPJA70rUv6yuMW5Bohw+bwcuzaxQIHaKFZCKGoGXIrc9vkTJ3+0txM73K0Hq3d5wgIg==", + "dev": true, + "dependencies": { + "@typescript-eslint/types": "4.33.0", + "eslint-visitor-keys": "^2.0.0" + }, + "engines": { + "node": "^8.10.0 || ^10.13.0 || >=11.10.1" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/typescript-eslint" + } + }, "node_modules/@typescript-eslint/eslint-plugin/node_modules/debug": { "version": "4.3.1", "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.1.tgz", @@ -4275,6 +4323,24 @@ } } }, + "node_modules/@typescript-eslint/eslint-plugin/node_modules/eslint-visitor-keys": { + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz", + "integrity": "sha512-0rSmRBzXgDzIsD6mGdJgevzgezI534Cer5L/vyMX0kHzT/jiB43jRhd9YUlMGYLQy2zprNmoT8qasCGtY+QaKw==", + "dev": true, + "engines": { + "node": ">=10" + } + }, + "node_modules/@typescript-eslint/eslint-plugin/node_modules/ignore": { + "version": "5.1.8", + "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.1.8.tgz", + "integrity": "sha512-BMpfD7PpiETpBl/A6S498BaIJ6Y/ABT93ETbby2fP00v4EbvPBXWEoaR1UBPKs3iR53pJY7EtZk5KACI57i1Uw==", + "dev": true, + "engines": { + "node": ">= 4" + } + }, "node_modules/@typescript-eslint/eslint-plugin/node_modules/ms": { "version": "2.1.2", "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz", @@ -4282,15 +4348,15 @@ "dev": true }, "node_modules/@typescript-eslint/experimental-utils": { - "version": "4.31.1", - "resolved": "https://registry.npmjs.org/@typescript-eslint/experimental-utils/-/experimental-utils-4.31.1.tgz", - "integrity": "sha512-NtoPsqmcSsWty0mcL5nTZXMf7Ei0Xr2MT8jWjXMVgRK0/1qeQ2jZzLFUh4QtyJ4+/lPUyMw5cSfeeME+Zrtp9Q==", + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/experimental-utils/-/experimental-utils-4.33.0.tgz", + "integrity": "sha512-zeQjOoES5JFjTnAhI5QY7ZviczMzDptls15GFsI6jyUOq0kOf9+WonkhtlIhh0RgHRnqj5gdNxW5j1EvAyYg6Q==", "dev": true, "dependencies": { "@types/json-schema": "^7.0.7", - "@typescript-eslint/scope-manager": "4.31.1", - "@typescript-eslint/types": "4.31.1", - "@typescript-eslint/typescript-estree": "4.31.1", + "@typescript-eslint/scope-manager": "4.33.0", + "@typescript-eslint/types": "4.33.0", + "@typescript-eslint/typescript-estree": "4.33.0", "eslint-scope": "^5.1.1", "eslint-utils": "^3.0.0" }, @@ -4305,6 +4371,106 @@ "eslint": "*" } }, + "node_modules/@typescript-eslint/experimental-utils/node_modules/@typescript-eslint/scope-manager": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-4.33.0.tgz", + "integrity": "sha512-5IfJHpgTsTZuONKbODctL4kKuQje/bzBRkwHE8UOZ4f89Zeddg+EGZs8PD8NcN4LdM3ygHWYB3ukPAYjvl/qbQ==", + "dev": true, + "dependencies": { + "@typescript-eslint/types": "4.33.0", + "@typescript-eslint/visitor-keys": "4.33.0" + }, + "engines": { + "node": "^8.10.0 || ^10.13.0 || >=11.10.1" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/typescript-eslint" + } + }, + "node_modules/@typescript-eslint/experimental-utils/node_modules/@typescript-eslint/types": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-4.33.0.tgz", + "integrity": "sha512-zKp7CjQzLQImXEpLt2BUw1tvOMPfNoTAfb8l51evhYbOEEzdWyQNmHWWGPR6hwKJDAi+1VXSBmnhL9kyVTTOuQ==", + "dev": true, + "engines": { + "node": "^8.10.0 || ^10.13.0 || >=11.10.1" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/typescript-eslint" + } + }, + "node_modules/@typescript-eslint/experimental-utils/node_modules/@typescript-eslint/typescript-estree": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-4.33.0.tgz", + "integrity": "sha512-rkWRY1MPFzjwnEVHsxGemDzqqddw2QbTJlICPD9p9I9LfsO8fdmfQPOX3uKfUaGRDFJbfrtm/sXhVXN4E+bzCA==", + "dev": true, + "dependencies": { + "@typescript-eslint/types": "4.33.0", + "@typescript-eslint/visitor-keys": "4.33.0", + "debug": "^4.3.1", + "globby": "^11.0.3", + "is-glob": "^4.0.1", + "semver": "^7.3.5", + "tsutils": "^3.21.0" + }, + "engines": { + "node": "^10.12.0 || >=12.0.0" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/typescript-eslint" + }, + "peerDependenciesMeta": { + "typescript": { + "optional": true + } + } + }, + "node_modules/@typescript-eslint/experimental-utils/node_modules/@typescript-eslint/visitor-keys": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-4.33.0.tgz", + "integrity": "sha512-uqi/2aSz9g2ftcHWf8uLPJA70rUv6yuMW5Bohw+bwcuzaxQIHaKFZCKGoGXIrc9vkTJ3+0txM73K0Hq3d5wgIg==", + "dev": true, + "dependencies": { + "@typescript-eslint/types": "4.33.0", + "eslint-visitor-keys": "^2.0.0" + }, + "engines": { + "node": "^8.10.0 || ^10.13.0 || >=11.10.1" + }, + "funding": { + "type": "opencollective", + "url": "https://opencollective.com/typescript-eslint" + } + }, + "node_modules/@typescript-eslint/experimental-utils/node_modules/array-union": { + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/array-union/-/array-union-2.1.0.tgz", + "integrity": "sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==", + "dev": true, + "engines": { + "node": ">=8" + } + }, + "node_modules/@typescript-eslint/experimental-utils/node_modules/debug": { + "version": "4.3.2", + "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz", + "integrity": "sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==", + "dev": true, + "dependencies": { + "ms": "2.1.2" + }, + "engines": { + "node": ">=6.0" + }, + "peerDependenciesMeta": { + "supports-color": { + "optional": true + } + } + }, "node_modules/@typescript-eslint/experimental-utils/node_modules/eslint-utils": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/eslint-utils/-/eslint-utils-3.0.0.tgz", @@ -4332,6 +4498,50 @@ "node": ">=10" } }, + "node_modules/@typescript-eslint/experimental-utils/node_modules/globby": { + "version": "11.0.4", + "resolved": "https://registry.npmjs.org/globby/-/globby-11.0.4.tgz", + "integrity": "sha512-9O4MVG9ioZJ08ffbcyVYyLOJLk5JQ688pJ4eMGLpdWLHq/Wr1D9BlriLQyL0E+jbkuePVZXYFj47QM/v093wHg==", + "dev": true, + "dependencies": { + "array-union": "^2.1.0", + "dir-glob": "^3.0.1", + "fast-glob": "^3.1.1", + "ignore": "^5.1.4", + "merge2": "^1.3.0", + "slash": "^3.0.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/sponsors/sindresorhus" + } + }, + "node_modules/@typescript-eslint/experimental-utils/node_modules/ignore": { + "version": "5.1.8", + "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.1.8.tgz", + "integrity": "sha512-BMpfD7PpiETpBl/A6S498BaIJ6Y/ABT93ETbby2fP00v4EbvPBXWEoaR1UBPKs3iR53pJY7EtZk5KACI57i1Uw==", + "dev": true, + "engines": { + "node": ">= 4" + } + }, + "node_modules/@typescript-eslint/experimental-utils/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/@typescript-eslint/experimental-utils/node_modules/slash": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz", + "integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==", + "dev": true, + "engines": { + "node": ">=8" + } + }, "node_modules/@typescript-eslint/parser": { "version": "4.31.1", "resolved": "https://registry.npmjs.org/@typescript-eslint/parser/-/parser-4.31.1.tgz", @@ -4794,6 +5004,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 +5113,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", @@ -5725,13 +5940,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 +7139,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", @@ -7795,9 +8018,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 +8296,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 +8373,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 +8998,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 +9316,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 +9375,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 +10293,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 +10686,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 +11546,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", @@ -11446,9 +11704,9 @@ "integrity": "sha512-nTnJ528pbqxYanhpDYsi4Rd8MAeaBA67+RZ10CM1m3bTAVFEDcd5AuA4a6W5YkGZ1iNXHzZz8T6TBKLeBuNriQ==" }, "node_modules/graphql": { - "version": "15.5.3", - "resolved": "https://registry.npmjs.org/graphql/-/graphql-15.5.3.tgz", - "integrity": "sha512-sM+jXaO5KinTui6lbK/7b7H/Knj9BpjGxZ+Ki35v7YbUJxxdBCUqNM0h3CRVU1ZF9t5lNiBzvBCSYPvIwxPOQA==", + "version": "15.6.1", + "resolved": "https://registry.npmjs.org/graphql/-/graphql-15.6.1.tgz", + "integrity": "sha512-3i5lu0z6dRvJ48QP9kFxBkJ7h4Kso7PS8eahyTFz5Jm6CvQfLtNIE8LX9N6JLnXTuwR+sIYnXzaWp6anOg0QQw==", "dev": true, "engines": { "node": ">= 10.x" @@ -12184,9 +12442,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 +12825,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 +13361,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", @@ -14735,16 +14986,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 +15098,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 +15189,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 +15318,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.3", + "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-11.2.3.tgz", + "integrity": "sha512-Tfmhk8O2XFMD25EswHPv+OYhUjsijy5D7liTdxeXvhG2rsadmOLFtyj8lmlfoFFXY8oXWAIOKpoI+lJe1DB1mw==", "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 +15345,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 +15362,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 +15409,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 +15430,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 +15472,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 +15725,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 +15996,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 +16717,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", @@ -19288,6 +19656,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", @@ -19306,9 +19783,9 @@ } }, "node_modules/prettier": { - "version": "2.4.0", - "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.4.0.tgz", - "integrity": "sha512-DsEPLY1dE5HF3BxCRBmD4uYZ+5DCbvatnolqTqcxEgKVZnL2kUfyu7b8pPQ5+hTBkdhU9SLUmK0/pHb07RE4WQ==", + "version": "2.4.1", + "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.4.1.tgz", + "integrity": "sha512-9fbDAXSBcc6Bs1mZrDYb3XKzDLm4EXXL9sC1LqKP5rZkT6KRr/rf9amVUcODVXgguK/isJz0d0hP72WeaKWsvA==", "dev": true, "bin": { "prettier": "bin-prettier.js" @@ -22376,6 +22853,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 +23609,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 +23815,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 +24120,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 +24177,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 +25846,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 +25868,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 +25921,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 +26081,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 +26156,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 +26226,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 +26242,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 +26839,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 +26895,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 +26905,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 +26960,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 +26969,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 +27214,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 +27281,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 +28282,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 +28304,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 +28353,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 +28774,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 +28837,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": "*", @@ -28443,20 +28950,47 @@ } }, "@typescript-eslint/eslint-plugin": { - "version": "4.31.1", - "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-4.31.1.tgz", - "integrity": "sha512-UDqhWmd5i0TvPLmbK5xY3UZB0zEGseF+DHPghZ37Sb83Qd3p8ujhvAtkU4OF46Ka5Pm5kWvFIx0cCTBFKo0alA==", + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-4.33.0.tgz", + "integrity": "sha512-aINiAxGVdOl1eJyVjaWn/YcVAq4Gi/Yo35qHGCnqbWVz61g39D0h23veY/MA0rFFGfxK7TySg2uwDeNv+JgVpg==", "dev": true, "requires": { - "@typescript-eslint/experimental-utils": "4.31.1", - "@typescript-eslint/scope-manager": "4.31.1", + "@typescript-eslint/experimental-utils": "4.33.0", + "@typescript-eslint/scope-manager": "4.33.0", "debug": "^4.3.1", "functional-red-black-tree": "^1.0.1", + "ignore": "^5.1.8", "regexpp": "^3.1.0", "semver": "^7.3.5", "tsutils": "^3.21.0" }, "dependencies": { + "@typescript-eslint/scope-manager": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-4.33.0.tgz", + "integrity": "sha512-5IfJHpgTsTZuONKbODctL4kKuQje/bzBRkwHE8UOZ4f89Zeddg+EGZs8PD8NcN4LdM3ygHWYB3ukPAYjvl/qbQ==", + "dev": true, + "requires": { + "@typescript-eslint/types": "4.33.0", + "@typescript-eslint/visitor-keys": "4.33.0" + } + }, + "@typescript-eslint/types": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-4.33.0.tgz", + "integrity": "sha512-zKp7CjQzLQImXEpLt2BUw1tvOMPfNoTAfb8l51evhYbOEEzdWyQNmHWWGPR6hwKJDAi+1VXSBmnhL9kyVTTOuQ==", + "dev": true + }, + "@typescript-eslint/visitor-keys": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-4.33.0.tgz", + "integrity": "sha512-uqi/2aSz9g2ftcHWf8uLPJA70rUv6yuMW5Bohw+bwcuzaxQIHaKFZCKGoGXIrc9vkTJ3+0txM73K0Hq3d5wgIg==", + "dev": true, + "requires": { + "@typescript-eslint/types": "4.33.0", + "eslint-visitor-keys": "^2.0.0" + } + }, "debug": { "version": "4.3.1", "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.1.tgz", @@ -28466,6 +29000,18 @@ "ms": "2.1.2" } }, + "eslint-visitor-keys": { + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz", + "integrity": "sha512-0rSmRBzXgDzIsD6mGdJgevzgezI534Cer5L/vyMX0kHzT/jiB43jRhd9YUlMGYLQy2zprNmoT8qasCGtY+QaKw==", + "dev": true + }, + "ignore": { + "version": "5.1.8", + "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.1.8.tgz", + "integrity": "sha512-BMpfD7PpiETpBl/A6S498BaIJ6Y/ABT93ETbby2fP00v4EbvPBXWEoaR1UBPKs3iR53pJY7EtZk5KACI57i1Uw==", + "dev": true + }, "ms": { "version": "2.1.2", "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz", @@ -28475,19 +29021,75 @@ } }, "@typescript-eslint/experimental-utils": { - "version": "4.31.1", - "resolved": "https://registry.npmjs.org/@typescript-eslint/experimental-utils/-/experimental-utils-4.31.1.tgz", - "integrity": "sha512-NtoPsqmcSsWty0mcL5nTZXMf7Ei0Xr2MT8jWjXMVgRK0/1qeQ2jZzLFUh4QtyJ4+/lPUyMw5cSfeeME+Zrtp9Q==", + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/experimental-utils/-/experimental-utils-4.33.0.tgz", + "integrity": "sha512-zeQjOoES5JFjTnAhI5QY7ZviczMzDptls15GFsI6jyUOq0kOf9+WonkhtlIhh0RgHRnqj5gdNxW5j1EvAyYg6Q==", "dev": true, "requires": { "@types/json-schema": "^7.0.7", - "@typescript-eslint/scope-manager": "4.31.1", - "@typescript-eslint/types": "4.31.1", - "@typescript-eslint/typescript-estree": "4.31.1", + "@typescript-eslint/scope-manager": "4.33.0", + "@typescript-eslint/types": "4.33.0", + "@typescript-eslint/typescript-estree": "4.33.0", "eslint-scope": "^5.1.1", "eslint-utils": "^3.0.0" }, "dependencies": { + "@typescript-eslint/scope-manager": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-4.33.0.tgz", + "integrity": "sha512-5IfJHpgTsTZuONKbODctL4kKuQje/bzBRkwHE8UOZ4f89Zeddg+EGZs8PD8NcN4LdM3ygHWYB3ukPAYjvl/qbQ==", + "dev": true, + "requires": { + "@typescript-eslint/types": "4.33.0", + "@typescript-eslint/visitor-keys": "4.33.0" + } + }, + "@typescript-eslint/types": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-4.33.0.tgz", + "integrity": "sha512-zKp7CjQzLQImXEpLt2BUw1tvOMPfNoTAfb8l51evhYbOEEzdWyQNmHWWGPR6hwKJDAi+1VXSBmnhL9kyVTTOuQ==", + "dev": true + }, + "@typescript-eslint/typescript-estree": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-4.33.0.tgz", + "integrity": "sha512-rkWRY1MPFzjwnEVHsxGemDzqqddw2QbTJlICPD9p9I9LfsO8fdmfQPOX3uKfUaGRDFJbfrtm/sXhVXN4E+bzCA==", + "dev": true, + "requires": { + "@typescript-eslint/types": "4.33.0", + "@typescript-eslint/visitor-keys": "4.33.0", + "debug": "^4.3.1", + "globby": "^11.0.3", + "is-glob": "^4.0.1", + "semver": "^7.3.5", + "tsutils": "^3.21.0" + } + }, + "@typescript-eslint/visitor-keys": { + "version": "4.33.0", + "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-4.33.0.tgz", + "integrity": "sha512-uqi/2aSz9g2ftcHWf8uLPJA70rUv6yuMW5Bohw+bwcuzaxQIHaKFZCKGoGXIrc9vkTJ3+0txM73K0Hq3d5wgIg==", + "dev": true, + "requires": { + "@typescript-eslint/types": "4.33.0", + "eslint-visitor-keys": "^2.0.0" + } + }, + "array-union": { + "version": "2.1.0", + "resolved": "https://registry.npmjs.org/array-union/-/array-union-2.1.0.tgz", + "integrity": "sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==", + "dev": true + }, + "debug": { + "version": "4.3.2", + "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz", + "integrity": "sha512-mOp8wKcvj7XxC78zLgw/ZA+6TSgkoE2C/ienthhRD298T7UNwAg9diBpLRxC0mOezLl4B0xV7M0cCO6P/O0Xhw==", + "dev": true, + "requires": { + "ms": "2.1.2" + } + }, "eslint-utils": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/eslint-utils/-/eslint-utils-3.0.0.tgz", @@ -28502,6 +29104,38 @@ "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz", "integrity": "sha512-0rSmRBzXgDzIsD6mGdJgevzgezI534Cer5L/vyMX0kHzT/jiB43jRhd9YUlMGYLQy2zprNmoT8qasCGtY+QaKw==", "dev": true + }, + "globby": { + "version": "11.0.4", + "resolved": "https://registry.npmjs.org/globby/-/globby-11.0.4.tgz", + "integrity": "sha512-9O4MVG9ioZJ08ffbcyVYyLOJLk5JQ688pJ4eMGLpdWLHq/Wr1D9BlriLQyL0E+jbkuePVZXYFj47QM/v093wHg==", + "dev": true, + "requires": { + "array-union": "^2.1.0", + "dir-glob": "^3.0.1", + "fast-glob": "^3.1.1", + "ignore": "^5.1.4", + "merge2": "^1.3.0", + "slash": "^3.0.0" + } + }, + "ignore": { + "version": "5.1.8", + "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.1.8.tgz", + "integrity": "sha512-BMpfD7PpiETpBl/A6S498BaIJ6Y/ABT93ETbby2fP00v4EbvPBXWEoaR1UBPKs3iR53pJY7EtZk5KACI57i1Uw==", + "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 + }, + "slash": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz", + "integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==", + "dev": true } } }, @@ -28879,6 +29513,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 +29595,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", @@ -29641,13 +30280,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 +31336,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", @@ -31370,9 +32014,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 +32244,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 +32298,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 +32802,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 +33061,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 +33113,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 +33798,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 +34141,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 +34785,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", @@ -34237,9 +34916,9 @@ "integrity": "sha512-nTnJ528pbqxYanhpDYsi4Rd8MAeaBA67+RZ10CM1m3bTAVFEDcd5AuA4a6W5YkGZ1iNXHzZz8T6TBKLeBuNriQ==" }, "graphql": { - "version": "15.5.3", - "resolved": "https://registry.npmjs.org/graphql/-/graphql-15.5.3.tgz", - "integrity": "sha512-sM+jXaO5KinTui6lbK/7b7H/Knj9BpjGxZ+Ki35v7YbUJxxdBCUqNM0h3CRVU1ZF9t5lNiBzvBCSYPvIwxPOQA==", + "version": "15.6.1", + "resolved": "https://registry.npmjs.org/graphql/-/graphql-15.6.1.tgz", + "integrity": "sha512-3i5lu0z6dRvJ48QP9kFxBkJ7h4Kso7PS8eahyTFz5Jm6CvQfLtNIE8LX9N6JLnXTuwR+sIYnXzaWp6anOg0QQw==", "dev": true }, "gray-matter": { @@ -34788,9 +35467,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 +35756,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 +36120,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", @@ -36732,16 +37410,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 +37486,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 +37546,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 +37634,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.3", + "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-11.2.3.tgz", + "integrity": "sha512-Tfmhk8O2XFMD25EswHPv+OYhUjsijy5D7liTdxeXvhG2rsadmOLFtyj8lmlfoFFXY8oXWAIOKpoI+lJe1DB1mw==", "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 +37664,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 +37693,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 +37708,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 +37738,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 +37962,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 +38166,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 +38667,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", @@ -40206,6 +40959,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", @@ -40218,9 +41080,9 @@ "dev": true }, "prettier": { - "version": "2.4.0", - "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.4.0.tgz", - "integrity": "sha512-DsEPLY1dE5HF3BxCRBmD4uYZ+5DCbvatnolqTqcxEgKVZnL2kUfyu7b8pPQ5+hTBkdhU9SLUmK0/pHb07RE4WQ==", + "version": "2.4.1", + "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.4.1.tgz", + "integrity": "sha512-9fbDAXSBcc6Bs1mZrDYb3XKzDLm4EXXL9sC1LqKP5rZkT6KRr/rf9amVUcODVXgguK/isJz0d0hP72WeaKWsvA==", "dev": true }, "pretty-format": { @@ -42655,6 +43517,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 +44105,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 +44255,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 +44482,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 +44523,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..ed9ba37ad4 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,31 +92,31 @@ "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", - "@typescript-eslint/eslint-plugin": "^4.31.1", + "@typescript-eslint/eslint-plugin": "^4.33.0", "@typescript-eslint/parser": "^4.31.1", "async": "^3.2.1", "await-sleep": "0.0.1", @@ -139,8 +139,8 @@ "eslint-plugin-node": "^11.1.0", "eslint-plugin-promise": "^5.1.0", "event-to-promise": "^0.8.0", - "glob": "^7.1.7", - "graphql": "^15.5.3", + "glob": "^7.2.0", + "graphql": "^15.6.1", "heroku-client": "^3.1.0", "http-status-code": "^2.1.0", "husky": "^7.0.2", @@ -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.3", "make-promises-safe": "^5.1.0", "minimatch": "^3.0.4", "mkdirp": "^1.0.4", @@ -163,7 +163,7 @@ "npm-merge-driver-install": "^2.0.1", "object-hash": "^2.2.0", "postcss": "^8.3.6", - "prettier": "^2.4.0", + "prettier": "^2.4.1", "replace": "^1.2.1", "rimraf": "^3.0.2", "robots-parser": "^2.3.0", diff --git a/server.mjs b/server.mjs index e050d7a593..fac03c795a 100644 --- a/server.mjs +++ b/server.mjs @@ -41,7 +41,9 @@ async function checkPortAvailability() { const portInUse = await portUsed.check(port) if (portInUse) { console.log(`\n\n\nPort ${port} is not available. You may already have a server running.`) - console.log('Try running `killall node` to shut down all your running node processes.\n\n\n') + console.log( + `Try running \`npx kill-port ${port}\` to shut down all your running node processes.\n\n\n` + ) console.log('\x07') // system 'beep' sound process.exit(1) } 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/2-20/0.yml b/translations/es-ES/data/release-notes/2-20/0.yml deleted file mode 100644 index 671ff634d3..0000000000 --- a/translations/es-ES/data/release-notes/2-20/0.yml +++ /dev/null @@ -1,44 +0,0 @@ ---- -date: '2020-02-11' -sections: - features: - - 'En una rama de repositorio, los administradores de éste pueden rechazar cualquier subida que contenga una confirmación de fusión si habilitan el `Requerir un historial lineal` utilizando [reglas de protección de rama](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' - - 'Los administradores de repositorio pueden otorgar a todos los usuarios con acceso de subida la capacidad de subir información forzadamente a una rama protegida si habilitan `Permitir las subidas forzadas` utilizando [reglas de protección de rama](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}' - - 'Los administradores de repositorio pueden otorgar a todos los usuarios con permiso de subida la capacidad de borrar una rama protegida si habilitan `Permitir los borrados` utilizando [reglas de protección de rama](https://help.github.com/en/github/administering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}' - - 'Los administradores pueden configurar un límite de `maxobjectsize` en los repositorios, [limitando el tamaño de las confirmaciones de subida](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) para un repositorio que no esté en el [LFS de Git](https://help.github.com/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server).{% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}' - - 'Los propietarios de las organizaciones pueden crear un conjunto de etiquetas predeterminadas cuando crean un repositorio nuevo. {% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}' - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - 'Cuando los miembros de una organización intentan ver un repositorio público de éstas, un mensaje de SSO podría dañar la visualización de la página. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}' - - "Cuando se visualiza el perfil de un usuario, los enlaces para los equipos de dicho usuario podrían estar rotos. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}" - - 'Los usuarios con el rol de `maintain` no pudieron editar los temas del repositorio. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}' - - "Los usuarios que no son administradores de una organización recibieron un error 500 cuando intentaron acceder a la página de inicio de sesión. {% comment %} https://github.com/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}" - - 'El mensaje emergente de edición de historial no se mostró en los comentarios de los gist. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}' - - 'Una cuenta nueva pudo registrarse con un correo electrónico que ya estaba registrado. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}' - - 'Un servicio de almacenamiento estaba alcanzando un límite de descripción de archivo y causando el bloqueo del kernel y que otros servicios registraran errores. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}' - - 'Cuando una referencia de autoenlace fue parte de una url, el hipervículo podría haberse eliminado. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}' - - 'Cuando se agrega un comentario a una solicitud de cambios, la sección de `Propuestas vinculadas` de la barra lateral podría haber desaparecido. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}' - - 'Al editar una invitación existente a una organización para un usuario, un encabezado duplicado pudo haber aparecido en la tabla de `Equipos`. {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}' - - 'El servicio `resqued` pudo haber dejado de registrar eventos cuando las colas eran muy largas. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}' - - 'Los certificados auto-firmados no se generan automáticamente al ejecutar el comando `ghe-config-apply` para las configuraciones de agrupamientos y de disponibilidad alta. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}' - changes: - - 'No se mostrará ningún logo para un tema si no se ha cargado alguno. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}' - - 'Cuando se visualiza una propuesta en un buscador móvil, sus metadatos se listan en la parte superior de la página. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}' - - 'El dominio de nivel superior de Consul cambió de ".consul" a ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}' - - 'El servicio de hooshot ya no depende de ElasticSearch y solo utiliza MySQL como almacenamiento de base de datos. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}' - - 'La distinción visual entre propuestas, proyectos y debates se implementó en tarjetas de notas de proyecto. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}' - - 'En una revisión de solicitud de cambios, se muestra una notificación si un comentario de línea múltiple se trunca. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}' - - 'Los usuarios pueden visualizar su bitácora de auditoría en la pestaña de `Bitácora de seguridad` de su página de configuración personal. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - Las entradas duplicadas de webhooks en la base de datos pueden causar que las mejoras de las versiones anteriores fallen. (actualizado 2020-02-26) - - 'Las mejoras y actualizaciones de configuración fallarán si se personalizaron las configuraciones en segundo plano de los trabajadores. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/1.yml b/translations/es-ES/data/release-notes/2-20/1.yml deleted file mode 100644 index 90859cf64b..0000000000 --- a/translations/es-ES/data/release-notes/2-20/1.yml +++ /dev/null @@ -1,21 +0,0 @@ ---- -date: '2020-02-27' -sections: - security_fixes: - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}' - bugs: - - 'El hacer restauraciones desde los respaldos fallará con un error de tipo `Invalid RDB version number`. {% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}' - - 'El mejorar una replica de HA estancó indefinidamente la espera para que iniciara MySQL. {% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}' - - 'Los comentarios de revisión de las PR con valores inesperados para "position" o "original_position" ocasionó que fallaran las importaciones. {% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}' - - 'Las entradas de webhook duplicadas en la base de datos podría causar que las mejoras de las versiones previas fallaran. {% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Las mejoras y actualizaciones de configuración fallarán si se personalizaron las configuraciones en segundo plano de los trabajadores. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/10.yml b/translations/es-ES/data/release-notes/2-20/10.yml deleted file mode 100644 index 738f4e8c3b..0000000000 --- a/translations/es-ES/data/release-notes/2-20/10.yml +++ /dev/null @@ -1,21 +0,0 @@ ---- -date: '2020-06-23' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' - bugs: - - 'Las bitácoras de eventos excesivamente grandes podrían ocasionar inestabilidad en el reenvío de bitácoras cuando se utiliza UDP como el mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - "El dejar de suspender a un usuario automáticamente mediante SSO no se completa si el atributo de las llaves SSH ya está asociado con la cuenta de usuario. {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}" - - 'El hash de permiso del repositorio desde la API de REST no indicó acceso de los miembros de negocios que tienen acceso de lectura en los repositorios internos. {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'No se interpretó adecuadamente la vista previa de la descripción de una GitHub App escrita en lenguaje de marcado. {% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}' - - 'La bitácora de auditoría no incluyó los eventos de cambio de protección de rama. {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}' - - "El intentar asignar una revisión de código a un miembro de un equipo vacío resultó en un '500 Internal Server Error'. {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}" - - 'La asignación de revisión de código utilizando el algoritmo de balanceo de carga pudo asignarse repetidamente al mismo miembro del equipo. {% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/11.yml b/translations/es-ES/data/release-notes/2-20/11.yml deleted file mode 100644 index f76f87c961..0000000000 --- a/translations/es-ES/data/release-notes/2-20/11.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2020-07-09' -sections: - security_fixes: - - '**MEDIA:** Se actualizó nginx a la versión 1.16.1 y se dirigió el CVE-2019-20372. (actualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' - bugs: - - 'La gráfica de dependencias no estaba detectando dependencias cuando se desplegó en una configuración de agrupamiento con nodos múltiples de Redis. {% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}' - - 'Algunos archivos de bitácora no rotaron cada 7 días. {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'La reutilización rápida de puertos origen de webhooks dio como resultado conexiones rechazadas. {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}' - - 'Los jobs incorrectos en segundo plano pudieron intentar ejecutarse en instancias que se configuraron como réplicas pasivas. {% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'Los repositorios internos no se incluyeron correctamente en los resultados de búsqueda para las organizaciones habilitadas con SAML. {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/12.yml b/translations/es-ES/data/release-notes/2-20/12.yml deleted file mode 100644 index 548dc7d854..0000000000 --- a/translations/es-ES/data/release-notes/2-20/12.yml +++ /dev/null @@ -1,16 +0,0 @@ -date: '2020-07-21' -sections: - security_fixes: - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' - bugs: - - 'Las gráficas de monitoreo de la consola de adminsitración a veces no se muestra correctamente en pantallas grandes. {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'El flujo de creación de un manifiesto de una GitHub App no se pudo utilizar en algunos escenarios en donde la política de SameSite Cookie se aplicó. {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}' - changes: - - 'Mejoras al escalamiento de HAProxy. {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/13.yml b/translations/es-ES/data/release-notes/2-20/13.yml deleted file mode 100644 index 51706af202..0000000000 --- a/translations/es-ES/data/release-notes/2-20/13.yml +++ /dev/null @@ -1,22 +0,0 @@ ---- -date: '2020-08-11' -sections: - security_fixes: - - '**CRÍTICA:** Se identificó una vulnerabilidad de ejecución en GitHub Pages que podría permitir que un atacante ejecute comandos como parte de la construcción de un sitio de GitHub Pages. Este problema se da debido a una dependencia vulnerable desactualizada que se utiliza en el proceso de creación de Pages. para explotar esta vulnerabilidad, el atacante necesita permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afecta a todas las versiones de GitHub Enterprise Server. Para mitigarla, Kramdown se actualizó para dirigirse a CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**ALTA:** Un atacante pudo inyectar un argumento malicioso en un sub-comando de Git cuando se ejecutó en GitHub Enterprise Server. Esto pudo permitir que el atacante sobreescribiera archivos arbitrarios con un contenido parcialmente controlado por el usuario y que ejecutara potencialmente comandos arbitrarios en la instancia de GitHub Enterprise Server. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para acceder a los repositorios dentro de la instancia de GitHub Enterprise Server. Sin embargo, debido a que existen otros tipos de protección, no pudimos identificar una forma de explotar activamente esta vulnerabilidad. Dicha vulnerabilidad se reportó a través del programa GitHub Security Bug Bounty. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' - bugs: - - 'Un error de configuración de Consul previnió que algunos jobs en segundo plano se procesaran en instancias independientes. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' - - 'Los cálculos de asignación de memoria de servicio pudieron asignar una cantidad incorrecta o ilimitada de memoria a un servicio, lo cual dio como resultado un rendimiento pobre del sistema. {% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}' - - 'La plataforma de virtualización para los sistemas de oVirt KVM no se detectó adecuadamente, lo cual ocasionó problemas durante las mejoras. {% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "El mensaje de error para la autenticación inválida con una contraseña a través de la línea de comandos de Git no llenó la URL que vinculaba a agregar el token o llave SSH adecuados. {% comment %} https://github.com/github/github/pull/149714 {% endcomment %}" - - 'GitHub Connect estaba utilizando una terminal obsoleta de la API de GitHub.com. {% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'Las propuestas no se pudieron clasificar por *Actualizadas recientemente* en los repositorios que se migraron a una instancia nueva. {% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'La página con error 404 contenía los enlaces de estado y contacto de GitHub.com en el pié de página. {% comment %} https://github.com/github/github/pull/151316 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/14.yml b/translations/es-ES/data/release-notes/2-20/14.yml deleted file mode 100644 index f64d20c620..0000000000 --- a/translations/es-ES/data/release-notes/2-20/14.yml +++ /dev/null @@ -1,13 +0,0 @@ ---- -date: '2020-08-12' -sections: - bugs: - - 'Se resolvió un problema que pudo haber llevado a un uso alto de CPU mientras se generaban las plantillas de configuración del sistema. {% comment %} https://github.com/github/enterprise2/pull/21784, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Los cambios recientes a las asignaciones de memoria pudieron haber llevado a una degradación en el rendimiento del sistema {% comment %} https://github.com/github/enterprise2/pull/22067 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/15.yml b/translations/es-ES/data/release-notes/2-20/15.yml deleted file mode 100644 index ea9c2f763c..0000000000 Binary files a/translations/es-ES/data/release-notes/2-20/15.yml and /dev/null differ diff --git a/translations/es-ES/data/release-notes/2-20/16.yml b/translations/es-ES/data/release-notes/2-20/16.yml deleted file mode 100644 index c660f62685..0000000000 --- a/translations/es-ES/data/release-notes/2-20/16.yml +++ /dev/null @@ -1,12 +0,0 @@ -date: '2020-09-08' -sections: - bugs: - - 'Una revisión de salud del servicio causó un crecimiento de sesión que resultó en el agotamiento del sistema de archivos en el nodo. {% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - 'Hacer mejoras utilizando hotpatches podría fallar con un error de `''libdbi1'' was not found`{% comment %} https://github.com/github/enterprise2/pull/22558, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/17.yml b/translations/es-ES/data/release-notes/2-20/17.yml deleted file mode 100644 index fa9a189fff..0000000000 --- a/translations/es-ES/data/release-notes/2-20/17.yml +++ /dev/null @@ -1,12 +0,0 @@ -date: '2020-09-23' -sections: - security_fixes: - - '**MEDIO**: ImageMagick se actualizó a la dirección [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22625, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Se actualizaron los paquetes a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22601, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22605, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22718, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/18.yml b/translations/es-ES/data/release-notes/2-20/18.yml deleted file mode 100644 index 373eabb7a4..0000000000 --- a/translations/es-ES/data/release-notes/2-20/18.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - 'El usuario cuyo nombre de usuario del directorio de LDAP se estandarice a una información de inicio de cuenta de GHES podría autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156518, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22910, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - 'El menú desplegable de Formato de Id de nombre en la consola de administración se restablecerá a "no especificado" después de configurarlo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22403, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'La configuración de guardado a través de la [consola de administración](/admin/configuration/accessing-the-management-console) añadirá una línea nueva a los archivos de [certificado y llave TLS/SSL](/admin/configuration/configuring-tls) que activaron la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22607, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'Las bitácoras de sistema para la Gráfica de dependencias no estaban rotando, lo cual permitió un crecimiento desmedido del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22765, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'Los enlaces a las Asesorías de Seguridad de GitHub utilizaron una URL con el nombre de host de la instancia de GitHub Enterprise Server en vez de la de GitHub.com, lo cual dirigió al usuario a una URL inexistente. {% comment %} https://github.com/github/github/pull/153444, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'Cuando importas un repositorio con un `ghe-migrator`, puede ocurrir una excepción inesperada cuando se presentan los datos inconsistentes. {% comment %} https://github.com/github/github/pull/153848, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'Cuando se utiliza `ghe-migrator` para importar las solicitudes de revisión de PR, los registros asociados con los usuarios borrados resultaron en registros de una base de datos extraña. {% comment %} https://github.com/github/github/pull/154958, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'Cuando se importan los usuarios con `ghe-migrator`, ocurrió un error de "El correo electrónico es inválido" si la dirección de correo electrónico que generó el sistema era mayor a 100 caracteres. {% comment %} https://github.com/github/github/pull/155112, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'El registrar la actividad de los webhooks puede utilizar cantidades grandes de espacio en disco y causar que el disco raíz se llene. {% comment %} https://github.com/github/github/pull/155655, https://github.com/github/github/pull/154100 {% endcomment %}' - changes: - - 'Se agrega compatibilidad con el tipo de instancia `m5.16xlarge` de AWS EC2. {% comment %} https://github.com/github/enterprise2/pull/22500, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Elimina el requisito de las huellas dactilares de SSH en los archivos de `ghe-migrator`, ya que siempre se le puede calcular. {% comment %} https://github.com/github/github/pull/156944, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'Los manifiestos de las GitHub Apps ahora incluyen el campo `request_oauth_on_install`. {% comment %} https://github.com/github/github/pull/156996, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/19.yml b/translations/es-ES/data/release-notes/2-20/19.yml deleted file mode 100644 index 0cb4255b59..0000000000 --- a/translations/es-ES/data/release-notes/2-20/19.yml +++ /dev/null @@ -1,14 +0,0 @@ ---- -date: '2020-10-20' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' - bugs: - - 'El mensaje de la "Política de confirmación para el requisito bifactorial" en una cuenta empresarial fue incorrecto. {% comment %} https://github.com/github/github/pull/158737 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/2.yml b/translations/es-ES/data/release-notes/2-20/2.yml deleted file mode 100644 index c2254d14e1..0000000000 --- a/translations/es-ES/data/release-notes/2-20/2.yml +++ /dev/null @@ -1,28 +0,0 @@ ---- -date: '2020-03-10' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}' - bugs: - - 'En algunos casos, las entradas de bitácora reenviadas, principalmente para audit.log, se estaban truncando. {% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}' - - 'La utilidad de línea de comandos `ghe-license-check` devolvió un error de "Invalid license file" para algunas licencias válidas, lo cual causó que fallaran los cambios de configuración. {% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}' - - 'El syslog no reenvió las bitácoras de excepciones de Alambic. {% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}' - - 'El [evento `org_block`](https://developer.github.com/v3/activity/events/types/#orgblockevent) no se encuentra como "no disponible" pero aparecía en las GitHub Apps en GitHub Enterprise Server. {% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}' - - 'Las respuestas de consulta de GraphQL a veces devolvían identificadores de nodo incoincidentes para los objetos de `ProtectedBranch` {% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}' - - 'La credencial de GtHub App que utilizó GitHub Connect falló en actualizarse inmediatamente después de su vencimiento. {% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}' - - 'El dejar comentarios de repsuesta en un comentario de una solicitud de cambios creó intermitentemente una revisión de solciitud de cambios pendiente. {% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}' - - 'Al utilizar a ghe-migrator o exportar desde GitHub.com, una exportación falla silenciosamente en exportar adjuntos que no sean imágenes. {% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}' - - 'Los ganchos de pre-recepción devolvieron un error 500 en la IU web cuando se encontraron caracteres UTF-8. {% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}' - changes: - - 'La utilidad de línea de comandos ` ghe-license-usage ` incluye una opción `--unencrypted` nueva para proporcionar visibilidad en el archivo de uso de licencia exportado. {% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Las mejoras y actualizaciones de configuración fallarán si se personalizaron las configuraciones en segundo plano de los trabajadores. {% comment %} https://github.com/github/enterprise2/issues/19119, {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/20.yml b/translations/es-ES/data/release-notes/2-20/20.yml deleted file mode 100644 index 3a9b2bb999..0000000000 --- a/translations/es-ES/data/release-notes/2-20/20.yml +++ /dev/null @@ -1,16 +0,0 @@ ---- -date: '2020-11-03' -sections: - security_fixes: - - '**MEDIA:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**BAJO:** La validación de un token incorrecto resultó en una entropía reducida para los tokens coincidentes durante la autenticación. El análisis muestra que, en la práctica, aquí no hay riesgos de seguridad significativos. {% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' - bugs: - - 'Los usuarios suspendidos se incluyeron en la lista de usuarios sugeridos, ocultando potencialmente a los usuarios que no se habían suspendido. {% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/21.yml b/translations/es-ES/data/release-notes/2-20/21.yml deleted file mode 100644 index 09bc73f8cf..0000000000 --- a/translations/es-ES/data/release-notes/2-20/21.yml +++ /dev/null @@ -1,15 +0,0 @@ ---- -date: '2020-11-17' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23843, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'Las bitácoras de babeld no tenían un separador entre los segundos y microsegundos. {% comment %} https://github.com/github/babeld/pull/1004, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'Cuando la política "Cambio de visibilidad del repositorio" en las cuentas empresariales se configura como "Habilitada", los propietarios de las organizaciones no pudieron cambiar la visibilidad de los repositorios dentro de las organizaciones. {% comment %} https://github.com/github/github/pull/160922, https://github.com/github/github/pull/160773 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/22.yml b/translations/es-ES/data/release-notes/2-20/22.yml deleted file mode 100644 index fe2e7e480e..0000000000 --- a/translations/es-ES/data/release-notes/2-20/22.yml +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: '2020-12-03' -sections: - bugs: - - 'El servicio de autorización se detectó como no saludable debido a la condición de raza en bootstrap, lo cual ocasionó que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1279 {% endcomment %}' - - 'Un comportamiento subyacente estaba causando que un servicio estuviera no disponible durante el proceso de mejora del hotpatch.{% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'Un subconjunto de certificados SSL que reenviaban bitácoras no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'La forma en la que se aplicaron los certificados SSH entre las organizaciones y los negocios fue inconsistente. {% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'Cuando una cuenta se limitó en su tasa debido al uso incorrecto de contraseñas, se pudo haber bloqueado por hasta 24 horas. {% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias pudo haber causado que se retrasaran las filas de trabajadores. {% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'Cuando se inicia sesión después de intentar visitar una página específica, se enviaba a las personas a la página de inicio en vez de a su destino previsto. {% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/23.yml b/translations/es-ES/data/release-notes/2-20/23.yml deleted file mode 100644 index c573890a1f..0000000000 --- a/translations/es-ES/data/release-notes/2-20/23.yml +++ /dev/null @@ -1,13 +0,0 @@ ---- -date: '2020-12-17' -sections: - security_fixes: - - '**BAJO:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1020, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/24351, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/24.yml b/translations/es-ES/data/release-notes/2-20/24.yml deleted file mode 100644 index 0a2faa96d4..0000000000 --- a/translations/es-ES/data/release-notes/2-20/24.yml +++ /dev/null @@ -1,28 +0,0 @@ ---- -date: '2021-03-02' -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de control de acceso incorrecto en GitHub Enterprise Server, la cual permitió a un usuario no autenticado de la instancia obtener acceso a los repositorios no autorizados a través de solicitudes de cambios y solicitudes a través de la API de REST configuradas específicamente. El atacante necesitaría poder bifurcar el repositorio de destino, dicha configuración está inhabilitada predeterminadamente para los repositorios privados y para los que pertenecen a una organización. Las protecciones de rama tales como las solicitudes de cambio o verificaciones de estado requeridas prevendrían que las confirmaciones no autorizadas se fusionen sin haber obtenido una revisión o validación adicionales. Se ha asignado un CVE-2021-22861 a esta vulnerabilidad. El problema se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - '**ALTA:** Se identificó una vulnerabilidad de control de acceso incorrecto en la API de GraphQL de GitHub Enterprise Server, la cual permitió a los usuarios autenticados de la instancia modificar el permiso de colaboración del mantenedor para una solicitud de cambios sin una autorización adecuada. Al aprovechar esta vulnerabilidad, el atacante pudo obtener acceso a las ramas de encabezado de las solicitudes de cambios que se abrieron en los repositorios donde ellos eran los mantenedores. La bifurcación se inhabilitó predeterminadamente para los repositorios privados que pertenecían a alguna organización, lo cual previno esta vulnerabilidad. Adicionalmente, las protecciones de rama tales como las revisiones requeridas para la solicitud de cambios o las verificaciones de estado prevendrían que las confirmaciones no autorizadas se fusionen sin contar con una validación o revisión subsecuente. Se asignó un CVE-2021-22863 a esta vulnerabilidad. Este problema se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server que pudo haberse aprovechado al compilar un sitio de GitHub pages. La configuración controlada por el usuario de los intérpretes subyacentes que utiliza GitHub Pages no se restringió lo suficiente y dio cabida a la ejecución de comandos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permiso para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Se asignó a esta vulnerabilidad un CVE-2020-10519 y se reportó a través del [Programa de Recompensa por Errores de GitHub](https://bounty.github.com).' - - '**BAJA:** Una solicitud que se elaboró especialmente para el puente SVN pudo haber activado una espera larga antes de que hubiera una falla, lo cual dio como resultado un ataque de Negación del Servici (DoS).' - - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' - bugs: - - 'Un mensaje informativo se registro involuntariamente como un error durante las capturas de pantalla de las Utilidades de Respaldo de GitHub Enterprise, lo cual dio como resultado que se enviaran correos electrónicos innecesarios cuando los jobs de cron programaron los respaldos que escuchaban a la salida a stderr.' - - 'Al restablecer un respaldo grande, el registro de excepciones relacionado con el agotamiento de memoria de Redis pudo haber causado que la restauración fallara debido a un disco lleno.' - - 'El editar una página de wiki, un usuario pudo haber experimentado un error 500 al hacer clic en el botón de guardar.' - - 'Una confirmación firmada con S/MIME utilizando un certificado con nombres múltiples en el nombre alternativo de asunto se mostró incorrectamente como "No verificado" en la insignia de confirmación.' - - 'Se enviaron correos electrónicos a un usuario suspendido cuando se le agregó a un equipo.' - - 'Al cargar un archivo de licencia nuevo con una cantidad de plazas diferente del archivo de licencia anterior, la diferencia de plazas no se representó correctamente en la página de Configuración -> Licencia de la cuenta empresarial.' - - 'La casilla de verificación de "Prevent repository admins from changing anonymous Git read access" disponible en la configuración de cuenta empresarial no se pudo habilitar o inhabilitar con éxito.' - - 'Durante un año bisiesto, el usuario estuvo obtuvo una respuesta 404 cuando intentó ver la actividad de contribución en un lunes.' - changes: - - 'Se agregó soporte para los [tipos de instanciaAWS EC2 r5b](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Se ajustó la priorización de la cola en segundo plano para distribuir los jobs más equitativamente.' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - 'Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.' - - '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.' - - 'Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos.' diff --git a/translations/es-ES/data/release-notes/2-20/3.yml b/translations/es-ES/data/release-notes/2-20/3.yml deleted file mode 100644 index 12f3f1bfdf..0000000000 --- a/translations/es-ES/data/release-notes/2-20/3.yml +++ /dev/null @@ -1,15 +0,0 @@ ---- -date: '2020-03-12' -sections: - bugs: - - 'Las mejoras y actualizaciones de configuración podrían fallar si las configuraciones en segundo plano de los trabajadores se personalizaron. {% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/4.yml b/translations/es-ES/data/release-notes/2-20/4.yml deleted file mode 100644 index 829039d36d..0000000000 --- a/translations/es-ES/data/release-notes/2-20/4.yml +++ /dev/null @@ -1,18 +0,0 @@ ---- -date: '2020-03-25' -sections: - bugs: - - 'Las solicitudes de autenticación de SAML y los metadatos no se cifraron estrictamente, lo cual causó que algunos proveedores de identidad no procesaran adecuadamente las solicitudes de autenticación que inició el proveedor de servicios. {% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}' - - 'Las exportaciones de `ghe-migrator no contenían usuarios de hito, lo cual pudo haber interrumpido las operaciones de importación. {% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}' - - 'Cuando se sube información a un Gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}' - - 'El `ghe-repl-status` podría fallar cuando se trata de mostrar los repositorios que no se replicaron integralmente. {% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. (actualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/5.yml b/translations/es-ES/data/release-notes/2-20/5.yml deleted file mode 100644 index 69aede8d38..0000000000 --- a/translations/es-ES/data/release-notes/2-20/5.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2020-04-07' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}' - bugs: - - 'El tamaño máximo de 100MB en un objeto de Git no se pudo seleccionar para un repositorio cuando la cuenta empresarial global configuró una opción de tamaño de objeto de Git diferente a 100MB. {% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}' - - 'Los resultados de la API de propuestas y de solicitudes de cambio pudieron tener un comportamiento inconsistente cuando se ordenaron por el campo `updated_at`. {% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}' - - 'El campo `package` de las vulnerabilidades de seguridad no pudo consultarse a través de la API de GraphQL. {% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}' - - 'Cambiar un repositorio de *público* a *interno* mostró un mensaje de facturación irrelevante. {% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Cuando se actualiza desde versiones anteriores, los trabajadores de jobs en segundo plano no pueden generar, lo cual impide las características esenciales tales como fusionar las solicitudes de cambios. {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/6.yml b/translations/es-ES/data/release-notes/2-20/6.yml deleted file mode 100644 index c37a9e4595..0000000000 --- a/translations/es-ES/data/release-notes/2-20/6.yml +++ /dev/null @@ -1,27 +0,0 @@ ---- -date: '2020-04-23' -sections: - security_fixes: - - '**ALTA**: OpenSSL se actualizó a la dirección [CVE-2020-1967](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1967). {% comment %} https://github.com/github/enterprise2/pull/19889, https://github.com/github/enterprise2/pull/19885 {% endcomment %}' - - '**ALTA**: Se actualizó Git para tratar el [CVE-2020-5260](https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q) y [CVE-2020-11008](https://github.com/git/git/security/advisories/GHSA-hjc9-x69f-jqj7). Las restricciones nuevas previenen que los repositorios maliciosos se suban a la instancia del servidor, lo cual protege a los clientes que no se hayan parchado aún. {% comment %} https://github.com/github/git/pull/990 {% endcomment %}' - - '**BAJO**: ImageMagick se actualizó a la dirección [CVE-2019-10131](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10131). {% comment %} https://github.com/github/enterprise2/pull/19655, https://github.com/github/enterprise2/pull/19617 {% endcomment %}' - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/19809, https://github.com/github/enterprise2/pull/19792, https://github.com/github/enterprise2/pull/19899, https://github.com/github/enterprise2/pull/19882 {% endcomment %}' - bugs: - - 'El usuario de git no tenía permisos para invocar a los procesos que se requerían para convertir los repositorios existentes que utilizaban Subversion, desde el formato de la v4 al LRS de la v3. {% comment %} https://github.com/github/enterprise2/pull/19465, https://github.com/github/enterprise2/pull/19150 {% endcomment %}' - - 'Una disparidad en las configuraciones de MySQL pudo haber causado que los respaldos fallaran en las instalaciones grandes. {% comment %} https://github.com/github/enterprise2/pull/19688, https://github.com/github/enterprise2/pull/19409, https://github.com/github/enterprise2/issues/19055 {% endcomment %}' - - 'Cuando se hacen mejoras desde versiones previas, los trabajadores de jobs en segundo plano algunas veces no se generaron, lo cual previnió las características esenciales tales como fusionar solicitudes de cambios. {% comment %} https://github.com/github/enterprise2/pull/19771, https://github.com/github/enterprise2/pull/19712 {% endcomment %}' - - "Cuando una licencia de GitHub Enterprise Server contenía caracteres diferentes a los de ASCII, las solicitudes de tipo `GET` a la terminal `/setup/api/settings` de la API de la consola de administración resultó en un Error Interno del Servidor. {% comment %} https://github.com/github/enterprise2/pull/19790 {% endcomment %}" - - 'La consola de recuperación solicitó una contraseña de raíz, aún si la cuenta raíz estaba bloqueada. {% comment %} https://github.com/github/enterprise2/pull/19810, https://github.com/github/enterprise2/pull/19788, https://github.com/github/enterprise2/issues/18425 {% endcomment %}' - - 'Un archivo de CODEOWNRS con una marca de orden inicial en UTF-8 causó que todas las reglas de codeowners se ignoraran. {% comment %} https://github.com/github/github/pull/140974, https://github.com/github/github/pull/140729 {% endcomment %}' - changes: - - 'Cuando el job de cron de orquestador-cliente falló, varios correos electrónicos se enviaron a la cuenta raíz. {% comment %} https://github.com/github/enterprise2/pull/19761, https://github.com/github/enterprise2/pull/19748 {% endcomment %}' - - "Cuando un proveedor de identidad externo controló el estado de administrador del sitio de un usuario, los usuarios no se podían bajar de categoría a través de la utilidad de la línea de comandos. {% comment %} https://github.com/github/github/pull/140522, https://github.com/github/github/pull/137807, https://github.com/github/github/issues/42727 {% endcomment %}" - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/7.yml b/translations/es-ES/data/release-notes/2-20/7.yml deleted file mode 100644 index 9ed217f7af..0000000000 --- a/translations/es-ES/data/release-notes/2-20/7.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2020-05-05' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}' - bugs: - - 'Tanto `ghe-repl-start` como `ghe-repl-status` presentaron errores de sintaxis. {% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}' - - 'Si un repositorio tenía habilitada la configuración de "borrar ramas de encabezado automáticamente", la rama de encabezado no se borró automáticamente cuando una solicitud de cambios se fusionó con una instalacción de GitHub App. {% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}' - - 'Cuando se reinstauró a un miembro de una organización, la carga útil del webhook reportó al usuario `fantasma` como el remitente y no al usuario que realmente realizó la reinstauración. {% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}' - - 'Si un repositorio tiene habilitada la configuración de "borrar automáticamente las ramas de encabezado", la rama de encabezado no se borró cuando el repositorio de encabezado era diferente al repositorio base. {% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}' - - 'La recolección de basura de archivos temporales pudo haber ocacionado un error de validación de licencia. {% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}' - - 'En algunas situaciones, incluyendo cuando un repositorio se crea por primera vez, el gancho de pre-recepción se ejecutó sin un valor que se llenara para la variable de ambiente GITHUB_REPO_PUBLIC. {% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/8.yml b/translations/es-ES/data/release-notes/2-20/8.yml deleted file mode 100644 index 057807a2a3..0000000000 --- a/translations/es-ES/data/release-notes/2-20/8.yml +++ /dev/null @@ -1,20 +0,0 @@ ---- -date: '2020-05-19' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}' - bugs: - - 'Después de que se actualizó el archivo de licencia, los servicios no se recargaron adecuadamente, lo cual ocasionó una pérdida de funcionalidad. {% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}' - - 'Las solicitudes internas a la API que actualizaban la información de la gráfica de dependencias podrían fallar si el cuerpo de la respuesta era muy largo. {% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}' - - 'No se respetó el argumento de `afiliaciones` en algunas de las conexiones de repositorio de GraphQL. {% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}' - - 'El dejar de suspender un usuario mediante SSO no se completó si el atributo de correo electrónico de SAML tenía una cubierta diferente que el del correo electrónico de usuario de GitHub. {% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}' - - 'Restablecer la membrecía de un usuario en una organización no instrumentó al actor en las cargas útiles del webhook y de la bitácora de auditoría. {% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-20/9.yml b/translations/es-ES/data/release-notes/2-20/9.yml deleted file mode 100644 index 8b961d3414..0000000000 --- a/translations/es-ES/data/release-notes/2-20/9.yml +++ /dev/null @@ -1,17 +0,0 @@ ---- -date: '2020-06-02' -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de control de accesos impropia en la API de GitHub Enterprise Server que permitió a un miembro de una organización escalar los permisos y obtener acceso a repositorios no autorizados dentro de la organización. Dicha vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server antes de la 2.21. Hemos emitido el [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) como respuesta a este problema. La vulnerabilidad se reportó a través del [programa de recompensas por errores de GitHub](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}' - bugs: - - 'Los motors de búsqueda pueden indizar las instancias de GitHub Enterprise Server de cara al internet. {% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'La gráficade dependencias no detecta las dependencias cuando se despliega en una configuración de un agrupamiento con nodos múltiples de Redis. (updated 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/0.yml b/translations/es-ES/data/release-notes/2-21/0.yml deleted file mode 100644 index 93816fbe08..0000000000 --- a/translations/es-ES/data/release-notes/2-21/0.yml +++ /dev/null @@ -1,72 +0,0 @@ -date: '2020-06-09' -sections: - features: - - 'Los usuarios pueden [administrar las notificaciones](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/about-notifications) en las propuestas, solicitudes decambios y otros temas cuando navegan desde una notificación web. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'Los usuarios pueden [convertir las solicitudes de cambio nuevamente en un "Borrador"](https://github.blog/changelog/2020-04-08-convert-pull-request-to-draft/). {% comment %} https://github.com/github/releases/issues/800 {% endcomment %}' - - 'Las [Sugerencias de línea múltiple](https://github.blog/changelog/2020-04-15-multi-line-code-suggestions-general-availability/) permiten que un usuario sugiera un cambio específico para las líneas de código múltiple cuando se está revisando una solicitud de cambios. {% comment %} https://github.com/github/releases/issues/810 {% endcomment %}' - - 'Los usuarios con acceso de escritura en un repositorio pueden [ocultar un comentario en una propuesta o solicitud de cambios como "Duplicado"](https://help.github.com/en/enterprise/2.21/user/github/building-a-strong-community/managing-disruptive-comments#hiding-a-comment). {% comment %}https://github.com/github/github/pull/131746 {% endcomment %}' - - 'Cuando se [crea un repositorio desde una plantilla](https://help.github.com/en/enterprise/2.21/user/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) los usuarios pueden seleccionar opcionalmente el incluir todas las ramas en vez de solo la predeterminada. {% comment %} https://github.com/github/releases/issues/580 {% endcomment %}' - - '[Las tarjetas de proyecto de las propuestas incluyen una sección de solicitudes de cambios vinculadas](https://github.blog/changelog/2020-02-04-project-issue-cards-include-linked-pull-requests/) para que los usuarios puedan ver qué tipo de trabajo de desarrollo se relaciona con la propuesta directamente desde el tablero de proyecto. {% comment %} https://github.com/github/releases/issues/743 {% endcomment %}' - - 'Existe un conjunto nuevo de [terminales de "borrar reacciones"](https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/) en la API de reacciones. Las terminales de "Borrar reacciones" existentes se obsoletizarán en la primera mitad de 2021. {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - - 'Existe un conjunto nuevo de [Terminales de la API de equipos](https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/) que permitirá a GitHub escalar y tener compatibilidad con la API de equipos a la larga. Las terminales existentes de la API se obsoletizarán en la primera mitad del 2021. {% comment %} https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ {% endcomment %}' - - 'Los usuarios pueden [crear enlaces entre las propeustas y las solicitudes de cambios](https://help.github.com/en/enterprise/2.21/user/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-to-an-issue) sin necesitar utilizar las palabras claves de cierre en la descripción de la solicitud de cambios. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - security_fixes: - - 'Se identificó una vulnerabilidad de control de accesos impropia en la API de GitHub Enterprise Server que permitió a un miembro de una organización escalar los permisos y obtener acceso a repositorios no autorizados dentro de la organización. Dicha vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server antes de la 2.21. Hemos emitido el [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516) como respuesta a este problema. La vulnerabilidad se reportó a través del [programa de recompensas por errores de GitHub](https://bounty.github.com/). {% comment %} https://developer.github.com/changes/2020-02-26-new-delete-reactions-endpoints/ {% endcomment %}' - bugs: - - 'Si un usuario con acceso de subida minimiza el comentario de otro usuairio, el autor del comentario podría dejar de minimizarlo aún si tuviese privilegios insuficientes. {% comment %} https://github.com/github/github/pull/141237 {% endcomment %}' - - 'Los usuarios podrían fusionar accidentalmente hacia la rama principal desde el editor de plantillas de propuesta y de blobs. {% comment %} https://github.com/github/github/pull/134483, https://github.com/github/github/pull/134323 {% endcomment %}' - - 'Cuando un usuario borró una cuenta de GitHub, los registros de la bitácora de auditoría no mostraron correctamente los registros de eliminación de la organización. {% comment %} https://github.com/github/github/pull/140940 {% endcomment %}' - - 'El avatar de gist para el usuario actual enlazó a una URL inexistente. {% comment %} https://github.com/github/github/pull/140925 {% endcomment %}' - - 'La pestaña de repositorios de la organización no incluyó los repositorios internos. {% comment %} https://github.com/github/github/pull/136323 {% endcomment %}' - - 'Dar clic en el botón de "Mostrar todos los equipos" cuando se transfiere un repositorio causó un error 500. {% comment %} https://github.com/github/github/pull/134455 {% endcomment %}' - - 'Los nombres de archivo grandes causan problemas de desbordamiento cuando se muestra la etiqueta ''Cambió desde la última vista'' o la alternación de diff de ''Mostrar enriquecido'' en la vista de archivos diff. {% comment %} https://github.com/github/github/pull/134453 {% endcomment %}' - - 'Las tarjetas de visita virtual para los equipos de la organización reportó mal su capacidad de miembros. {% comment %} https://github.com/github/github/pull/133879 {% endcomment %}' - - 'La ventana emergente del comentario de la revisión de solicitudes de cambios tenía un problema desplazamiento. {% comment %} https://github.com/github/github/pull/141157 {% endcomment %}' - - 'Haproxy podría saturarse y causar una ralentización en las opreaciones de git. {% comment %} https://github.com/github/enterprise2/issues/19322 {% endcomment %}' - - 'La característica de la gráfica de dependencias no se habilitó automáticamente después de una promoción de réplica de HA. {% comment %} https://github.com/github/enterprise2/issues/18698 {% endcomment %}' - - 'Puede que se activara un límite de tiempo en la página de índice de lanzamientos para los repositorios con miles de solicitudes de cambios. {% comment %} https://github.com/github/github/pull/131802 {% endcomment %}' - - 'No fue posible filtrar las solicitudes de cambios tanto por estado como por borrador al mismo tiempo. {% comment %} https://github.com/github/github/pull/132567 {% endcomment %}' - - 'Si una solicitud de cambios cambió un indicador de submódulo, entonces el dar clic en "Editar archivo" en dicho archivo de submódulo desde la pestaña de "Archivos que cambiaron" de la solicitud de cambios causó un error 404. {% comment %} https://github.com/github/github/pull/132448 {% endcomment %}' - - 'No fue posible agregar usuarios a una organización o borrar la organización siguiendo la eliminación por lotes de todos los usuarios y administradores de ella. {% comment %} https://github.com/github/github/pull/132238 {% endcomment %}' - - 'Los comentarios de revisión contra los archivos que contenían caracteres diacríticos y diferentes a los latinos en el nombre de archivo dentro de la página de "Archivos con cambios" desapareció cuando se volvió a cargar la página. {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'El estado de la casilla de verificación "Visto" no se retuvo para los archivos que contenían caracteres diacríticos o diferentes a los latinos en el nombre de archivo en la páina de "Archivos que cambiaron". {% comment %} https://github.com/github/github/pull/131836 {% endcomment %}' - - 'Las solicitudes de cambios mostraron la insignia "Aprobada" cuando aún no se llevaban a cabo todas las revisiones requeridas. {% comment %} https://github.com/github/github/pull/131823 {% endcomment %}' - - 'El menú desplegable de la etiqueta estaba vacío cuando se buscaba una etiqueta en los repositorios con más de 100 de ellas. {% comment %} https://github.com/github/github/pull/131914 {% endcomment %}' - - 'Las páginas de solicitudes de extracción que mostraban anotaciones con títulos con un cifrado diferente al de UTF-8 pudieron encontrarse con errores de cifrado en la representación de la vista. {% comment %} https://github.com/github/github/pull/138534 {% endcomment %}' - - 'Una condición de carrera para la actualización de la página de OAuth pudo haber causado que un redireccionamiento se ejecutara dos veces. {% comment %} https://github.com/github/github/pull/131964 {% endcomment %}' - - 'La página de "Tokens de acceso personal" agotaba el tiempo si había más de 10 tokens. {% comment %} https://github.com/github/github/pull/132064 {% endcomment %}' - - 'Los jobs de sincronización programados para usuarios y equipos de LDAP pudieron haberse iniciado mientras que los jobs de sincronización programados previamente aún estaban en proceso. Un mecanismo de bloqueo se implementó para prevenir que los jobs de sincronización nuevos comenzaran si alguno de ellos aún se estaba ejecutando. {% comment %} https://github.com/github/github/pull/139205, https://github.com/github/support/issues/429, https://github.com/github/github/issues/54386, https://github.com/github/iam/issues/40 {% endcomment %}' - changes: - - 'Se actualizó la interface de notificaciones web, incluyendo los [states](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options) , [filters](https://help.github.com/en/enterprise/2.21/user/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-queries-for-custom-filters) y [shortcuts](https://help.github.com/en/enterprise/2.21/user/github/getting-started-with-github/keyboard-shortcuts#notifications) nuevos. {% comment %} https://github.com/github/enterprise-releases/issues/2135#issuecomment-633905096 {% endcomment %}' - - 'Ahora es posible inhabilitar la reactivación de los usuarios de LDAP en la sincronización de LDAP. {% comment %} https://github.com/github/github/pull/139023 {% endcomment %}' - - 'La redacción de la rama protegida de subida se actualizó para aclarar que los administradores siempre pueden subir información y que los usuarios con el rol de mantenedor pueden subir información cuando pasen las verificaciones de estado. {% comment %} https://github.com/github/github/pull/141555 {% endcomment %}' - - 'Prevenir las confirmaciones en blanco cuando la sugerencia es idéntica al original. {% comment %} https://github.com/github/github/pull/138587 {% endcomment %}' - - 'La paginación es compatible como una forma de obtener más archivos en el diff asociado con una confirmación a través de la API de REST. {% comment %} https://github.com/github/github/pull/134341 {% endcomment %}' - - 'Los administradores pueden habilitar, inhabilitar, borrar y buscar webhooks utilizando la ID de webhook desde la línea de comandos y utilizando `ghe-webhook-manage`. {% comment %} https://github.com/github/enterprise2/pull/19027 {% endcomment %}' - - 'La reorientación base automática sucederá despues de una limpieza manual de referencia de encabezado para una solicitud de cambios fusionada. {% comment %} https://github.com/github/github/pull/142133 {% endcomment %}' - - 'Los archivos SVG se manejan como texto y como imágenes en el visualizador de diffs. {% comment %} https://github.com/github/render/pull/1129 {% endcomment %}' - - 'La configuración de "borrar automáticamente las ramas en fusión" puede configurarse cuando se crea y actualiza un repositorio utilizando la API de REST. {% comment %} https://github.com/github/github/pull/131728 {% endcomment %}' - - 'Se agregó una terminal nueva para borrar despliegues a través de la API de REST. {% comment %} https://github.com/github/github/pull/128733 {% endcomment %}' - - 'Los administradores pueden [habilitar las alertas de seguridad](https://help.github.com/en/enterprise/2.21/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server) pero inhabilitan todas las notificaciones de estas alertas. {% comment %} https://github.com/github/releases/issues/841 {% endcomment %}' - - 'La bitácora de Pages muestra la información de inicio de sesión de un usuario que accede al sitio de GitHub Pages. {% comment %} https://github.com/github/enterprise2/pull/19905 {% endcomment %}' - - 'Los miembros empresariales pueden ver todas las organizaciones a las que pertenecen como parte de su cuenta empresarial desde una vista si navegan a `https://[ghes-hostname]/enterprises/[account-name]`. {% comment %} https://github.com/github/releases/issues/832 {% endcomment %}' - - '[La compatibilidad de la API de REST para los roles de mantenimiento y clasificación]](https://developer.github.com/changes/2020-04-07-expanding-rest-api-support-for-the-triage-and-maintain-roles/) se expandió. {% comment %} https://github.com/github/releases/issues/748 {% endcomment %}' - - 'Un usuario puede crear y compartir las consultas de búsqueda que resuelven al usuario actual si utiliza la sintaxis de búsqueda `@me` {% comment %} https://github.com/github/github/pull/129624 {% endcomment %}' - - 'Se [added](https://github.blog/changelog/2019-10-28-new-issue-template-configuration-options/) opciones de configuración nuevas para las plantillas de propuestas. {% comment %} https://github.com/github/releases/issues/660 {% endcomment %}' - - 'Se mejoró la confiabilidad y tiempo de compleción para la restauración y respaldo de MySQL. {% comment %} https://github.com/github/ghes-infrastructure/issues/162 {% endcomment %}' - - '[Visibilidad mejorada](https://github.blog/2020-02-06-get-more-information-at-a-glance-with-issue-and-pull-request-linking/) de las referencias de las solicitudes de cambios y propuestas en la barra lateral, tarjetas y listas de las propuestas. {% comment %} https://github.com/github/releases/issues/704 {% endcomment %}' - - 'Los usuarios pueden filtrar y buscar por `linked:pr` or `linked:issue`. {% comment %} https://github.com/github/releases/issues/744 {% endcomment %}' - - 'Ahora es posible la recuperación automática de fallas de MySQL dentro de una sola región para los despliegues de agrupamientos. {% comment %} https://github.com/github/ghes-infrastructure/issues/136 {% endcomment %}' - - 'Un usuario puede comparar etiquetas entre dos lanzamientos para determinar qué cambios se hicieron en la página de lanzamientos. {% comment %} https://github.com/github/github/issues/107054 {% endcomment %}' - - 'Los comentarios desactualizados ya no se colapsan predeterminadamente en la línea de tiempo de una solicitud de cambios. Pueden colapsarse si se resuelve el hilo. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-634201583 {% endcomment %}' - - 'Los administradores pueden ver una lista de inicios de sesión reservados para uso interno si navegan a la pestaña de "inicios de sesión reservados" de stafftools. {% comment %} https://github.com/github/enterprise-web/pull/6389#issuecomment-637846206 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se sube información a un gist, una excepción pudo haberse activado durante el gancho de post-recepción. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. (actualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error. diff --git a/translations/es-ES/data/release-notes/2-21/1.yml b/translations/es-ES/data/release-notes/2-21/1.yml deleted file mode 100644 index 89af70bbe0..0000000000 --- a/translations/es-ES/data/release-notes/2-21/1.yml +++ /dev/null @@ -1,21 +0,0 @@ ---- -date: '2020-06-23' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}' - bugs: - - 'Las bitácoras de eventos excesivamente grandes podrían ocasionar inestabilidad en el reenvío de bitácoras cuando se utiliza UDP como el mecanismo de transporte. {% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}' - - 'El servicio de comunicación interna que se utiliza para acceder a MySQL podría reiniciarse más frecuentemente de lo requerido, incluyendo a mitad del proceso de actualización, lo cual podría ocasionar que dicha actualización falle parcialmente. Redujimos la tasa de reinicios e hicimos el código más robusto. {% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}' - - "El dejar de suspender a un usuario automáticamente mediante SSO no se completa si el atributo de las llaves SSH ya está asociado con la cuenta de usuario. {% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}" - - 'El hash de permiso del repositorio desde la API de REST no indicó acceso de los miembros de negocios que tienen acceso de lectura en los repositorios internos. {% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}' - - 'La política empresarial de "borrado de propuestas del repositorio" no reflejó la configuración que se guardó actualmente. {% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}' - - 'La bitácora de auditoría no incluyó los eventos de cambio de protección de rama. {% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error." diff --git a/translations/es-ES/data/release-notes/2-21/10.yml b/translations/es-ES/data/release-notes/2-21/10.yml deleted file mode 100644 index e6bbeb8e7d..0000000000 --- a/translations/es-ES/data/release-notes/2-21/10.yml +++ /dev/null @@ -1,15 +0,0 @@ ---- -date: '2020-10-20' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}' - bugs: - - 'El mensaje de la "Política de confirmación para el requisito bifactorial" en una cuenta empresarial fue incorrecto. {% comment %} https://github.com/github/github/pull/158736 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/11.yml b/translations/es-ES/data/release-notes/2-21/11.yml deleted file mode 100644 index 2303c6d1bc..0000000000 --- a/translations/es-ES/data/release-notes/2-21/11.yml +++ /dev/null @@ -1,18 +0,0 @@ ---- -date: '2020-11-03' -sections: - security_fixes: - - '**MEDIA:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}' - - "**BAJO:** La validación de un token incorrecto resultó en una entropía reducida para los tokens coincidentes durante la autenticación. El análisis muestra que, en la práctica, aquí no hay riesgos de seguridad significativos. {% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}" - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23539, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23692, https://github.com/github/enterprise2/pull/23677 {% endcomment %}' - bugs: - - 'El editar las plantillas de las propuestas con los nombres de archivo que contienen caracteres que no son de ASCII fallará con un mensaje de "500 Internal Server Error".{% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}' - - 'Un método de recolección métrica para los jobs en segundo plano incrementó el uso del CPU. (actualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP de origen real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/12.yml b/translations/es-ES/data/release-notes/2-21/12.yml deleted file mode 100644 index 54c30d34e3..0000000000 --- a/translations/es-ES/data/release-notes/2-21/12.yml +++ /dev/null @@ -1,16 +0,0 @@ ---- -date: '2020-11-17' -sections: - security_fixes: - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}' - bugs: - - 'Las bitácoras de babeld no tenían un separador entre los segundos y microsegundos. {% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}' - - 'Cuando la política "Cambio de visibilidad del repositorio" en las cuentas empresariales se configura como "Habilitada", los propietarios de las organizaciones no pudieron cambiar la visibilidad de los repositorios dentro de las organizaciones. {% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}' - - 'Las bitácoras de auditoría podrían atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. {% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/13.yml b/translations/es-ES/data/release-notes/2-21/13.yml deleted file mode 100644 index a18363a796..0000000000 --- a/translations/es-ES/data/release-notes/2-21/13.yml +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: '2020-12-03' -sections: - bugs: - - 'El servicio de autorización se detectó como no saludable debido a la condición de raza en bootstrap, lo cual ocasionó que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}' - - 'Un comportamiento subyacente estaba causando que un servicio estuviera no disponible durante el proceso de mejora del hotpatch.{% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}' - - 'Un subconjunto de certificados SSL que reenviaban bitácoras no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'La forma en la que se aplicaron los certificados SSH entre las organizaciones y los negocios fue inconsistente. {% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'Cuando una cuenta se limitó en su tasa debido al uso incorrecto de contraseñas, se pudo haber bloqueado por hasta 24 horas. {% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias pudo haber causado que se retrasaran las filas de trabajadores. {% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'Cuando se inicia sesión después de intentar visitar una página específica, se enviaba a las personas a la página de inicio en vez de a su destino previsto. {% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/14.yml b/translations/es-ES/data/release-notes/2-21/14.yml deleted file mode 100644 index cf5b9ebca4..0000000000 --- a/translations/es-ES/data/release-notes/2-21/14.yml +++ /dev/null @@ -1,13 +0,0 @@ ---- -date: '2020-12-17' -sections: - security_fixes: - - '**BAJO:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (Dos).{% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/15.yml b/translations/es-ES/data/release-notes/2-21/15.yml deleted file mode 100644 index 138d9103b1..0000000000 --- a/translations/es-ES/data/release-notes/2-21/15.yml +++ /dev/null @@ -1,33 +0,0 @@ ---- -date: '2021-03-02' -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de control de acceso incorrecto en GitHub Enterprise Server, la cual permitió a un usuario no autenticado de la instancia obtener acceso a los repositorios no autorizados a través de solicitudes de cambios y solicitudes a través de la API de REST configuradas específicamente. El atacante necesitaría poder bifurcar el repositorio de destino, dicha configuración está inhabilitada predeterminadamente para los repositorios privados y para los que pertenecen a una organización. Las protecciones de rama tales como las solicitudes de cambio o verificaciones de estado requeridas prevendrían que las confirmaciones no autorizadas se fusionen sin haber obtenido una revisión o validación adicionales. Se ha asignado un CVE-2021-22861 a esta vulnerabilidad. El problema se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - '**ALTA:** Se identificó una vulnerabilidad de control de acceso incorrecto en la API de GraphQL de GitHub Enterprise Server, la cual permitió a los usuarios autenticados de la instancia modificar el permiso de colaboración del mantenedor para una solicitud de cambios sin una autorización adecuada. Al aprovechar esta vulnerabilidad, el atacante pudo obtener acceso a las ramas de encabezado de las solicitudes de cambios que se abrieron en los repositorios donde ellos eran los mantenedores. La bifurcación se inhabilitó predeterminadamente para los repositorios privados que pertenecían a alguna organización, lo cual previno esta vulnerabilidad. Adicionalmente, las protecciones de rama tales como las revisiones requeridas para la solicitud de cambios o las verificaciones de estado prevendrían que las confirmaciones no autorizadas se fusionen sin contar con una validación o revisión subsecuente. Se asignó un CVE-2021-22863 a esta vulnerabilidad. Este problema se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server que pudo haberse aprovechado al compilar un sitio de GitHub pages. La configuración controlada por el usuario de los intérpretes subyacentes que utiliza GitHub Pages no se restringió lo suficiente y dio cabida a la ejecución de comandos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permiso para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Se asignó a esta vulnerabilidad un CVE-2020-10519 y se reportó a través del [Programa de Recompensa por Errores de GitHub](https://bounty.github.com).' - - '**MEDIA:** Los GitHub tokens de las compilaciones de GitHub Pages pudieron haber terminado en las bitácoras.' - - '**BAJA:** Una solicitud que se elaboró especialmente para el puente SVN pudo haber activado una espera larga antes de que hubiera una falla, lo cual dio como resultado un ataque de Negación del Servici (DoS).' - - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' - bugs: - - 'Las verificaciones de salud del balanceador de carga pudieron haber causado en algunos casos que los logs de babel se llenaran con errores sobre el protocolo del PROXY.' - - 'Un mensaje informativo se registro involuntariamente como un error durante las capturas de pantalla de las Utilidades de Respaldo de GitHub Enterprise, lo cual dio como resultado que se enviaran correos electrónicos innecesarios cuando los jobs de cron programaron los respaldos que escuchaban a la salida a stderr.' - - 'Al restablecer un respaldo grande, el registro de excepciones relacionado con el agotamiento de memoria de Redis pudo haber causado que la restauración fallara debido a un disco lleno.' - - 'El editar una página de wiki, un usuario pudo haber experimentado un error 500 al hacer clic en el botón de guardar.' - - 'Una confirmación firmada con S/MIME utilizando un certificado con nombres múltiples en el nombre alternativo de asunto se mostró incorrectamente como "No verificado" en la insignia de confirmación.' - - 'Se enviaron correos electrónicos a un usuario suspendido cuando se le agregó a un equipo.' - - 'Cuando un repositorio tuvo una gran cantidad de manifiestos se mostró un error de `You have reached the maximum number of allowed manifest files (20) for this repository.` en la pestaña ubicada en Perspectivas -> Gráfica de dependencias. Para obtener más información, consulta la sección [Límites de visualización] (https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'Al cargar un archivo de licencia nuevo con una cantidad de plazas diferente del archivo de licencia anterior, la diferencia de plazas no se representó correctamente en la página de Configuración -> Licencia de la cuenta empresarial.' - - 'La casilla de verificación de "Prevent repository admins from changing anonymous Git read access" disponible en la configuración de cuenta empresarial no se pudo habilitar o inhabilitar con éxito.' - - 'Cuando una compilación de GitHub Pages falló, la notificación de correo electrónico contenía un enlace incorrecto para la ubicación de soporte.' - - 'Durante un año bisiesto, el usuario estuvo obtuvo una respuesta 404 cuando intentó ver la actividad de contribución en un lunes.' - - 'Visitar la sección de *Explore* falló con un error interno del servidor 500.' - changes: - - 'Se agregó soporte para los [tipos de instanciaAWS EC2 r5b](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Se ajustó la priorización de la cola en segundo plano para distribuir los jobs más equitativamente.' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - 'Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.' - - '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.' - - 'Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos.' diff --git a/translations/es-ES/data/release-notes/2-21/16.yml b/translations/es-ES/data/release-notes/2-21/16.yml deleted file mode 100644 index 8e11c6f472..0000000000 --- a/translations/es-ES/data/release-notes/2-21/16.yml +++ /dev/null @@ -1,14 +0,0 @@ ---- -date: '2021-03-16' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - El importar repositorios archivados desde GitHub Enterprise Server a los cuales les faltan archivos de repositorio, fallará con un error. - known_issues: - - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - 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. - - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos. diff --git a/translations/es-ES/data/release-notes/2-21/17.yml b/translations/es-ES/data/release-notes/2-21/17.yml deleted file mode 100644 index a7e7bfa3cb..0000000000 --- a/translations/es-ES/data/release-notes/2-21/17.yml +++ /dev/null @@ -1,29 +0,0 @@ ---- -date: '2021-03-23' -intro: Se han desactivado las descargas debido a un error importante que afectó a varios clientes. Pronto tendremos una solución en el siguiente parche. -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server, la cual pudo haberse aprovechado al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario que utilizan las GitHub Pages no se restringieron lo suficiente e hicieron posible que se ignoraran las variables de ambiente que llevaron a la ejecución de código en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permisos 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 antes de la 3.0.3 y se arregló en la 3.0.3, 2.22.9, y 2.21.17. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub y se le asignó un CVE-2021-22864.' - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - La ejecución de `ghe-cluster-config-init` no reconocía completamente el código de salida de los jobs en segundo plano que condujeron a un manejo inadecuado de las verificaciones previas al vuelo. - changes: - - Las bitácoras rotarán con base en su tamaño adicionalmente al tiempo. - - Utiliza una cantidad relativa para el `bootstrap_expect` cónsul y nómada, lo cual permitió que un clúster hiciera un arranque primario, incluso si un conjunto de nodos estaba fuera de servicio. - known_issues: - - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - 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. - - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos. - - |2 - La rotación de bitácoras podrían fallar en señalizar los servicios para transicionar a archivos de bitácora nuevos, lo cual lleva a que los archivos de bitácora antiguos se sigan utilizando y a un agotamiento de espacio en el disco raíz eventuales. - Para remediar o prevenir este problema, ejecuta los siguientes comandos en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), o contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) para recibir asistencia: - - ``` - 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 - ``` - - sections -> known_issues -> 6 diff --git a/translations/es-ES/data/release-notes/2-21/18.yml b/translations/es-ES/data/release-notes/2-21/18.yml deleted file mode 100644 index 38e7bb7602..0000000000 --- a/translations/es-ES/data/release-notes/2-21/18.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-04-01' -sections: - security_fixes: - - '**ALTO:** Se identificó una vulnerabilidad de control de acceso inadecuada en GitHub Enterprise Server, la cual permitió que los tokens de acceso generados desde un [flujo de autenticación web](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) de una GitHub App leyera los metadatos de un repositorio privado a través de la API de REST sin que se le hubieran otorgado los permisos adecuados. Para explotar esta vulnerabilidad, el atacante necesitaría crear una GitHub App en la instancia y hacer que un usuario autorice la aplicación mediante el flujo de autenticación web. Los metadatos del repositorio privado que se devolvió estarían limitados a los repositorios que pertenecen al usuario al cual identifica el token. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anterior a la 3.0.4 y se arregló en las versiones 3.0.4, 2.22.10 y 2.21.18. A esta vulnerabilidad se le asignó un CVE-2021-22865 y se reportó mediante el [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - 'Los servicios no estaban haciendo la transición a los archivos de bitácora nuevos como parte de la rotación de bitácoras, lo cual dio como resultado un uso de disco incrementado.' - - La etiqueta de los resultados de la búsqueda para los repositorios internos se mostró como "Privada" en vez de como "Interna". - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' - - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos. diff --git a/translations/es-ES/data/release-notes/2-21/19.yml b/translations/es-ES/data/release-notes/2-21/19.yml deleted file mode 100644 index afb266118f..0000000000 --- a/translations/es-ES/data/release-notes/2-21/19.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2021-04-14' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - 'Un mensaje de advertencia de tipo `jq: error (at :0): Cannot index number with string "settings"` podría ocurrir durante la promoción de la réplica.' - - Visitar la página `/settings/emails` almacenó el estado que pudo haber causado redirecciones inadecuadas al finalizar sesión y volverla a iniciar. - - Las alertas de la gráfica de dependencias no se mostraron para algunos componentes cuyas asesorías tienen nombres de paquetes con mayúsculas en `vulnerable_version_ranges`. - - Un usuario vio un error 500 al ejecutar operaciones de git en una instancia configurada con autenticación LDAP. - - 'Cuando el ghe-migrator encontró errores de importación, algunas veces abortó todo el proceso y las bitácoras no incluyeron suficiente contexto.' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' - - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos. diff --git a/translations/es-ES/data/release-notes/2-21/2.yml b/translations/es-ES/data/release-notes/2-21/2.yml deleted file mode 100644 index c7bb2098c5..0000000000 --- a/translations/es-ES/data/release-notes/2-21/2.yml +++ /dev/null @@ -1,20 +0,0 @@ -date: '2020-07-09' -sections: - security_fixes: - - '**MEDIA:** Se actualizó nginx a la versión 1.16.1 y se dirigió el CVE-2019-20372. (actualizado 2020-07-22) {% comment %} https://github.com/github/enterprise2/pull/21252 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21089, https://github.com/github/enterprise2/pull/21036 {% endcomment %}' - bugs: - - 'Algunos archivos de bitácora no rotaron cada 7 días. {% comment %} https://github.com/github/enterprise2/pull/21279, https://github.com/github/enterprise2/pull/21264 {% endcomment %}' - - 'La reutilización rápida de los puertos origen de los webhooks dieron como resultado conexiones rechazadas. {% comment %} https://github.com/github/enterprise2/pull/21286, https://github.com/github/enterprise2/pull/21280 {% endcomment %}' - - 'Los jobs incorrectos en segundo plano pudieron intentar ejecutarse en instancias que se configuraron como réplicas pasivas. {% comment %} https://github.com/github/enterprise2/pull/21317, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}' - - 'La VPN entre nodos pudo hacerse inestable causando que los errores se registraran y que el espacio libre en el volúmen raíz se agotara. {% comment %} https://github.com/github/enterprise2/pull/21360, https://github.com/github/enterprise2/pull/21357 {% endcomment %}' - - 'Los repositorios internos no se incluyeron correctamente en los resultados de búsqueda para las organizaciones habilitadas con SAML. {% comment %} https://github.com/github/github/pull/147505, https://github.com/github/github/pull/145692 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error. diff --git a/translations/es-ES/data/release-notes/2-21/20.yml b/translations/es-ES/data/release-notes/2-21/20.yml deleted file mode 100644 index 8f1651b1de..0000000000 --- a/translations/es-ES/data/release-notes/2-21/20.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover. - - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.' - - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected. - - Organizations or projects with errors blocked migration and could not be excluded. - changes: - - Preflight checks allow all AWS instance types by default. - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' - - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos. diff --git a/translations/es-ES/data/release-notes/2-21/21.yml b/translations/es-ES/data/release-notes/2-21/21.yml deleted file mode 100644 index 9d57a5f401..0000000000 --- a/translations/es-ES/data/release-notes/2-21/21.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - Orchestrator auto failover could be enabled during the phase of config apply. - - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page. - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' - - Las alertas de seguridad no se reportan cuando se sube a un repositorio en la línea de comandos. diff --git a/translations/es-ES/data/release-notes/2-21/3.yml b/translations/es-ES/data/release-notes/2-21/3.yml deleted file mode 100644 index 1261970097..0000000000 --- a/translations/es-ES/data/release-notes/2-21/3.yml +++ /dev/null @@ -1,17 +0,0 @@ -date: '2020-07-21' -sections: - security_fixes: - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21438, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21496, https://github.com/github/enterprise2/pull/21479 {% endcomment %}' - bugs: - - 'Las gráficas de monitoreo de la consola de adminsitración a veces no se muestra correctamente en pantallas grandes. {% comment %} https://github.com/github/enterprise2/pull/21398, https://github.com/github/enterprise2/pull/21381 {% endcomment %}' - - 'El flujo de creación de un manifiesto de una GitHub App no se pudo utilizar en algunos escenarios en donde la política de SameSite Cookie se aplicó. {% comment %} https://github.com/github/github/pull/147829, https://github.com/github/github/pull/144121 {% endcomment %}' - - 'En algunas circunstancias, acceder a la página de ''Explorar'' arrojó un error de aplicación. {% comment %} https://github.com/github/github/pull/149605, https://github.com/github/github/pull/148949 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error. diff --git a/translations/es-ES/data/release-notes/2-21/4.yml b/translations/es-ES/data/release-notes/2-21/4.yml deleted file mode 100644 index 6f7cd7f931..0000000000 --- a/translations/es-ES/data/release-notes/2-21/4.yml +++ /dev/null @@ -1,28 +0,0 @@ ---- -date: '2020-08-11' -sections: - security_fixes: - - '**CRÍTICA:** Se identificó una vulnerabilidad de ejecución en GitHub Pages que podría permitir que un atacante ejecute comandos como parte de la construcción de un sitio de GitHub Pages. Este problema se da debido a una dependencia vulnerable desactualizada que se utiliza en el proceso de creación de Pages. para explotar esta vulnerabilidad, el atacante necesita permisos para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afecta a todas las versiones de GitHub Enterprise Server. Para mitigarla, Kramdown se actualizó para dirigirse a CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**ALTA:** Un atacante pudo inyectar un argumento malicioso en un sub-comando de Git cuando se ejecutó en GitHub Enterprise Server. Esto pudo permitir que el atacante sobreescribiera archivos arbitrarios con un contenido parcialmente controlado por el usuario y que ejecutara potencialmente comandos arbitrarios en la instancia de GitHub Enterprise Server. Para explotar esta vulnerabilidad, el atacante necesitaría permiso para acceder a los repositorios dentro de la instancia de GHES. Sin embargo, debido a que existen otros tipos de protección, no pudimos identificar una forma de explotar activamente esta vulnerabilidad. Dicha vulnerabilidad se reportó a través del programa GitHub Security Bug Bounty. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' - - 'Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' - bugs: - - 'Un error de configuración de Consul previnió que algunos jobs en segundo plano se procesaran en instancias independientes. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' - - 'Los cálculos de asignación de memoria de servicio pudieron asignar una cantidad incorrecta o ilimitada de memoria a un servicio, lo cual dio como resultado un rendimiento pobre del sistema. {% comment %} https://github.com/github/enterprise2/pull/21689 {% endcomment %}' - - 'La plataforma de virtualización para los sistemas de oVirt KVM no se detectó adecuadamente, lo cual ocasionó problemas durante las mejoras. {% comment %} https://github.com/github/enterprise2/pull/21731, https://github.com/github/enterprise2/pull/21669 {% endcomment %}' - - "El mensaje de error para la autenticación inválida con una contraseña a través de la línea de comandos de Git no llenó la URL que vinculaba a agregar el token o llave SSH adecuados. {% comment %} https://github.com/github/github/pull/149607, https://github.com/github/github/pull/149351 {% endcomment %}" - - 'El crear una propuesta en un repositorio de usuario utilizando la característica de plantillas de propuestas podría fallar con un Error Interno del Servidor. {% comment %} https://github.com/github/github/pull/150173, https://github.com/github/github/pull/149445 {% endcomment %}' - - 'El visitar la sección de *Explorar* falló con un error interno del servidor 500. {% comment %} https://github.com/github/github/pull/150512, https://github.com/github/github/pull/150504 {% endcomment %}' - - 'Las propuestas no se pudieron clasificar por *Actualizadas recientemente* en los repositorios que se migraron a una instancia nueva. {% comment %} https://github.com/github/github/pull/150688, https://github.com/github/github/pull/149330 {% endcomment %}' - - 'GitHub Connect estaba utilizando una terminal obsoleta de la API de GitHub.com. {% comment %} https://github.com/github/github/pull/150827, https://github.com/github/github/pull/150545 {% endcomment %}' - - 'La recolección de métricas internas para los jobs en segundo plano contribuyó al uso innecesario de memoria y CPU. {% comment %} https://github.com/github/github/pull/151182, https://github.com/github/github/pull/147695 {% endcomment %}' - - 'La página con error 404 contenía los enlaces de estado y contacto de GitHub.com en el pié de página. {% comment %} https://github.com/github/github/pull/151315 {% endcomment %}' - - 'Los jobs en segundo plano para una característica que no se había lanzado se pusieron en cola y se dejaron sin procesar. {% comment %} https://github.com/github/github/pull/151395, https://github.com/github/github/pull/146248 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error." diff --git a/translations/es-ES/data/release-notes/2-21/5.yml b/translations/es-ES/data/release-notes/2-21/5.yml deleted file mode 100644 index bce888ee92..0000000000 --- a/translations/es-ES/data/release-notes/2-21/5.yml +++ /dev/null @@ -1,16 +0,0 @@ ---- -date: '2020-08-12' -sections: - bugs: - - 'Se resolvió un problema que pudo haber llevado a un uso alto de CPU mientras se generaban las plantillas de configuración del sistema. {% comment %} https://github.com/github/enterprise2/pull/21786, https://github.com/github/enterprise2/pull/21741 {% endcomment %}' - - 'Los cambios recientes a las asignaciones de memoria pudieron haber llevado a una degradación en el rendimiento del sistema {% comment %} https://github.com/github/enterprise2/pull/22066 {% endcomment %}' - - 'Los problemas temporales de conectividad mientras se ejecutaban las migraciones de base de datos pudieron causar una pérdida de datos. {% comment %} https://github.com/github/enterprise2/pull/22128, https://github.com/github/enterprise2/pull/22100 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "El configurar el permiso de un repositorio en `Triage` or `Maintain` falla con un mensaje de error." diff --git a/translations/es-ES/data/release-notes/2-21/6.yml b/translations/es-ES/data/release-notes/2-21/6.yml deleted file mode 100644 index 8638d1d9cd..0000000000 --- a/translations/es-ES/data/release-notes/2-21/6.yml +++ /dev/null @@ -1,26 +0,0 @@ -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 %}' - 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 %}' - 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 %}' - 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 %}' diff --git a/translations/es-ES/data/release-notes/2-21/7.yml b/translations/es-ES/data/release-notes/2-21/7.yml deleted file mode 100644 index 6ec30ff084..0000000000 --- a/translations/es-ES/data/release-notes/2-21/7.yml +++ /dev/null @@ -1,14 +0,0 @@ -date: '2020-09-08' -sections: - bugs: - - 'Una revisión de salud del servicio causó un crecimiento de sesión que resultó en el agotamiento del sistema de archivos en el nodo. {% comment %} https://github.com/github/enterprise2/pull/22481, https://github.com/github/enterprise2/pull/22475 {% endcomment %}' - - 'Hacer mejoras utilizando hotpatches podría fallar con un error de `''libdbi1'' was not found`{% comment %} https://github.com/github/enterprise2/pull/22556, https://github.com/github/enterprise2/pull/22552 {% endcomment %}' - - El configurar el permiso de un repositorio en `Triage` or `Maintain` ya no falla. - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/8.yml b/translations/es-ES/data/release-notes/2-21/8.yml deleted file mode 100644 index c65ab25fcb..0000000000 --- a/translations/es-ES/data/release-notes/2-21/8.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2020-09-23' -sections: - security_fixes: - - '**MEDIO**: ImageMagick se actualizó a la dirección [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22621, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Se actualizaron los paquetes a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22571, https://github.com/github/enterprise2/pull/22426, https://github.com/github/enterprise2/pull/22602, https://github.com/github/enterprise2/pull/22592, https://github.com/github/enterprise2/pull/22719, https://github.com/github/enterprise2/pull/22699 {% endcomment %}' - bugs: - - 'Los administradores no pudieron ver los webhooks de repositorio que se entregaron y vieron la leyenda "Sorry, something went wrong and we weren''t able to fetch the deliveries for this hook" en vez de esto. {% comment %} https://github.com/github/authzd/pull/1181, https://github.com/github/authzd/pull/980 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-21/9.yml b/translations/es-ES/data/release-notes/2-21/9.yml deleted file mode 100644 index 29713346d8..0000000000 --- a/translations/es-ES/data/release-notes/2-21/9.yml +++ /dev/null @@ -1,28 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - 'El usuario cuyo nombre de usuario del directorio de **LDAP** se estandariza a una información de inicio de cuenta de GHES podría autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156517, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22911, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - 'El menú desplegable de Formato de Id de nombre en la consola de administración se restablecerá a "no especificado" después de configurarlo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22402, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'La configuración de guardado a través de la [consola de administración](/admin/configuration/accessing-the-management-console) añadirá una línea nueva a los archivos de [certificado y llave TLS/SSL](/admin/configuration/configuring-tls) que activaron la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22608, https://github.com/github/enterprise2/pull/22540 {% endcomment %}' - - 'Las bitácoras de sistema para la Gráfica de dependencias no estaban rotando, lo cual permitió un crecimiento desmedido del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22766, https://github.com/github/enterprise2/pull/22733 {% endcomment %}' - - 'La mejora podría fallar si los trabajadores que se volvieron a poner en cola (resqued) invalidan la configuración que se está utilizando. {% comment %} https://github.com/github/enterprise2/pull/22838, https://github.com/github/enterprise2/pull/22814 {% endcomment %}' - - 'Cuando importas un repositorio con un `ghe-migrator`, puede ocurrir una excepción inesperada cuando se presentan los datos inconsistentes. {% comment %} https://github.com/github/github/pull/153849, https://github.com/github/github/pull/151552 {% endcomment %}' - - 'Los enlaces a las Asesorías de Seguridad de GitHub utilizaron una URL con el nombre de host de la instancia de GitHub Enterprise Server en vez de la de GitHub.com, lo cual dirigió al usuario a una URL inexistente. {% comment %} https://github.com/github/github/pull/153853, https://github.com/github/github/pull/151301 {% endcomment %}' - - 'La página de configuración de seguridad para la cuenta empresarial mostró un enlace para "Visualizar las configuraciones actuales de tus organizaciones" para la configuración de "autenticación bifactorial" cuando el modo de autenticación no es compatible con la autenticación bifactorial incluida. {% comment %} https://github.com/github/github/pull/153861 {% endcomment %}' - - 'Cuando se utiliza `ghe-migrator` para importar las solicitudes de revisión de PR, los registros asociados con los usuarios borrados resultaron en registros de una base de datos extraña. {% comment %} https://github.com/github/github/pull/154959, https://github.com/github/github/pull/153169 {% endcomment %}' - - 'Cuando se importan los usuarios con `ghe-migrator`, ocurrió un error de "El correo electrónico es inválido" si la dirección de correo electrónico que generó el sistema era mayor a 100 caracteres. {% comment %} https://github.com/github/github/pull/155110, https://github.com/github/github/pull/152418 {% endcomment %}' - - 'El registrar la actividad de los webhooks puede utilizar cantidades grandes de espacio en disco y causar que el disco raíz se llene. {% comment %} https://github.com/github/github/pull/155656, https://github.com/github/github/pull/154100 {% endcomment %}' - changes: - - 'Se agrega compatibilidad con el tipo de instancia `m5.16xlarge` de AWS EC2. {% comment %} https://github.com/github/enterprise2/pull/22501, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Elimina el requisito de las huellas dactilares de SSH en los archivos de `ghe-migrator`, ya que siempre se le puede calcular. {% comment %} https://github.com/github/github/pull/156945, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'Los manifiestos de las GitHub Apps ahora incluyen el campo `request_oauth_on_install`. {% comment %} https://github.com/github/github/pull/156994, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las alertas de seguridad no se reportan cuando se sube información a un repositorio en la líneade comandos. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-22/0.yml b/translations/es-ES/data/release-notes/2-22/0.yml deleted file mode 100644 index 9e52b64b34..0000000000 --- a/translations/es-ES/data/release-notes/2-22/0.yml +++ /dev/null @@ -1,125 +0,0 @@ -intro: GitHub se emociona en presentar GitHub Enterprise Server 2.22.0. -date: '2020-09-23' -sections: - features: - - heading: GitHub Actions Beta - notes: - - | - [GitHub Actions](https://github.com/features/actions) es una solución flexible y poderosa para IC/DC y para la automatización de flujos de trabajo. GitHub Actions en Enterprise Server incluye herramientas que te ayudan a administrar el servicio, incluyendo las métricas clave para la Consola de Administración, bitácoras de auditoría y controles de acceso para ayudarte a controlar los lanzamientos. - - Necesitarás proporcionar tu propio [storage](https://docs.github.com/en/enterprise/2.22/admin/github-actions/enabling-github-actions-and-configuring-storage) y ejecturores para las GitHub Actions. AWS S3, Azure Blob Storage y MinIO son compatibles. Por favor, revisa los [requisitos mínimos actualizados para tu plataforma](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de que actives las GitHub Actions. Para aprender más, contacta al equipo de ventas de GitHub o [regístrate para el beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/775 {% endcomment %} - - heading: GitHub Packages Beta - notes: - - | - [GitHub Packages](https://github.com/features/packages) es un servicio de hospedaje de paquetes, integrado nativamente con las API, Acciones y webhooks de GitHub. Crea un [Flujo de trabajo de DevOps de extremo a extremo](https://docs.github.com/en/enterprise/2.22/admin/packages/configuring-packages-support-for-your-enterprise) que incluye tu código, integración contínua y soluciones de despliegue. - - El almacenamiento compatible de lado del servidor incluye a AWS S3 y a MinIO con compatibilidad para Azure blob en un lanzamiento futuro. Por favor, nota que la compatibilidad actual con Docker se reemplazará por un beta del nuevo Registro de Contenedores de Github en el próximo lanzamiento. Por favor, revisa los [requisitos mínimos actualizados para tu plataforma](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de que actives GitHub Packages. Para aprender más, contacta al equipo de ventas de GitHub o [regístrate para el beta](https://resources.github.com/beta-signup/). {% comment %} https://github.com/github/releases/issues/773 {% endcomment %} - - heading: Escaneo Avanzado de Seguridad de Código Beta - notes: - - | - [El escaneo avanzado de seguridad de código de GitHub](https://github.com/features/security) es un ambiente de pruebas de seguridad para aplicaciones estáticas (SAST) nativo de GitHub. Encuentra vulnerabilidades de seguridad fácilmente antes de que lleguen al ambiente productivo, todo impulsado con el motor de análisis de código más poderoso del mundo: CodeQL. - - Los administradores que utilicen la Seguridad Avanzada de Github pueden [registrarse para](https://resources.github.com/beta-signup/) y [enable](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-code-scanning-for-your-appliance) el beta del escaneo avanzado de seguridad de código de GitHub. Por favor, revisa los [requisitos mínimos actualizados para tu plataforma](https://docs.github.com/en/enterprise/2.22/admin/installation/setting-up-a-github-enterprise-server-instance) antes de que actives el escaneo avanzado de seguridad de código. {% comment %} https://github.com/github/releases/issues/768 {% endcomment %} - - heading: Redireccionamiento de solicitudes de cambios - notes: - - | - Cuando una [rama de encabezado de una solicitud de cambios](https://docs.github.com/en/enterprise/2.22/user/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches) se fusiona y borra, el resto de las solicitudes de cambios abiertas en el mismo repositorio que se dirigen a esta rama - ahora se redireccionan a la rama base fusionada de la solicitud de cambios. Anteriormente, estas solicitudes de cambios se cerraron. {% comment %} https://github.com/github/releases/issues/801 {% endcomment %} - - heading: Suspender y dejar de suspender la instalación de una app - notes: - - | - Los administradores y usuarios pueden [suspender cualquier tipo de acceso a las GitHub Apps](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#suspend-an-app-installation) por tanto tiempo como sea necesario, y [dejar de suspender la app](https://docs.github.com/enterprise/2.22/user/rest/reference/apps#unsuspend-an-app-installation) a voluntad mediante la configuración y la API. Las apps suspendidas no pueden acceder a la API o a los eventos de webhook de GitHub. Puedes utilizar esto en vez de desinstalar una aplicación, lo cual revoca la autorización a todos los usuarios. {% comment %} https://github.com/github/github/pull/138316 https://github.com/github/github/pull/150869 {% endcomment %}'' - - heading: Rendimiento mejorado a gran escala - notes: - - | - Hemos revisado el acercamiento que tomamos para programar el mantenimiento de red para los repositorios, asegurándonos que los mono-repositorios grandes puedan evitar estados de fallo. {% comment %} https://github.com/github/github/pull/146789, https://github.com/github/github/pull/147931, https://github.com/github/github/pull/146724, https://github.com/github/git-protocols/issues/94 {% endcomment %}'' - - Las réplicas pasivas ahora [son compatibles y configurables en los despliegues de agrupamiento de GitHub Enterprise Server](https://docs.github.com/en/enterprise/2.22/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster). Estos cambios habilitarán una recuperación de fallos más rápida, reduciendo tanto el RTO como el RPO. {% comment %} https://github.com/github/releases/issues/905 {% endcomment %} - - heading: Ver todos tus usuarios - notes: - - | - Para los equipos exepcionalmente grandes, los administradores pueden [ajustar el máximo predeterminado de 1,500 elementos para las listas de usuario](https://docs.github.com/en/enterprise/2.22/admin/configuration/command-line-utilities#ghe-config). {% comment %} https://github.com/github/github/pull/146508 {% endcomment %}'' - changes: - - heading: Cambios en la administración - notes: - - 'Los trabajadores compartidos se habilitaron para proporcionar más resiliencia a las actualizaciones en vivo al compartir las conexiones entre las pestañas. {% comment %} https://github.com/github/releases/issues/914 {% endcomment %}' - - 'El enlace de "Contacta a soporte" en las páginas de error de `50x` ahora te enlaza con el correo electrónico de soporte o con el enlace configurado en la consola de administración. {% comment %} https://github.com/github/github/pull/142123 {% endcomment %}' - - 'Ahora es posible [administrar los anuncios globales y las fechas de vencimiento a través de la configuración de cuenta empresarial](https://docs.github.com/en/enterprise/2.22/admin/installation/command-line-utilities#ghe-announce). {% comment %} https://github.com/github/releases/issues/945, https://github.com/github/github/pull/148475, https://github.com/github/github/pull/148494 {% endcomment %}' - - 'Ahora puedes [exentar a algunos usuarios de los límites de tasa predeterminados de la API que se configuran en la consola de administración](https://docs.github.com/en/enterprise/2.22/admin/configuration/configuring-rate-limits), en caso de que sea necesario. {% comment %} https://github.com/github/github/pull/148673 {% endcomment %}' - - 'Los administradores de repositorio ahora pueden [configurar su repositorio con cualquier opción de visibilidad disponible](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility) desde un diálogo único en la configuración del repositorio. Anteriormente, tenías que navegar entre secciones, botones y cajas de diálogo separadas para cambiar entre las visibilidades pública y privada y entre las internas y privadas. {% comment %} https://github.com/github/releases/issues/882 {% endcomment %}' - - 'Un enlace nuevo de configuración empresarial en el menú desplegable del usuario facilita la navegación a los ajustes de la cuenta empresarial. {% comment %} https://github.com/github/releases/issues/946, https://github.com/github/github/pull/150595, https://github.com/github/github/pull/150520, https://github.com/github/github/pull/151121, https://github.com/github/hydro-schemas/pull/1244 {% endcomment %}' - - 'Se eliminó el enlace tradicional de "Centro de administración" en la página de /stafftools. El enlace de "Empresa" ahora es la mejor forma de navegar a la cuenta empresarial desde la página de /stafftools. {% comment %} https://github.com/github/github/pull/147633 {% endcomment %}' - - 'El elemento de sub-menú de opciones en la configuración de la cuenta empresarial se migró desde la sección de Configuración hasta la de Políticas. {% comment %} https://github.com/github/releases/issues/944, https://github.com/github/github/pull/148477 {% endcomment %}' - - '[El acceder a los recursos de acceso utilizando un token de acceso personal o una llave SSH ahora cuenta como una actividad de usuario](https://docs.github.com/en/enterprise/2.22/admin/user-management/managing-dormant-users). Esto evita a los administradores la carga de filtrar algunos usuarios de los reportes de usuarios durmientes y hace más seguro el uso del botón "Suspender todos" sin suspender accidentalmente a los usuarios que solo acceden a GitHub en forma de solo lectura a través de las API con un token de acceso personal (PAT) o llave SSH. {% comment %} https://github.com/github/github/pull/140433, https://github.com/github/help-docs/pull/14853, https://github.com/github/customer-feedback/issues/174, https://github.com/github/supportability/issues/14 {% endcomment %}' - - heading: Cambios de seguridad - notes: - - 'Los códigos de recuperación bifactoriales ya no pueden utilizarse durante el proceso de inicio de sesión con dos factores. Las contraseñas de una sola ocasión son los únicos valores aceptables. {% comment %} https://github.com/github/github/pull/145016, https://github.com/github/github/pull/140208 {% endcomment %}' - - 'Cuando un usuario inicia sesión en GitHub Enterprise Server mediante un inicio de sesión único, la [selección de visibilidad predeterminada del repositorio es privada](https://docs.github.com/en/enterprise/2.22/user/github/administering-a-repository/setting-repository-visibility). {% comment %} https://github.com/github/releases/issues/872 {% endcomment %}' - - 'Los propietarios de las GitHub Apps ahora pueden escoger que sus [tokens de acceso de usuario a servidor venzan después de 8 horas](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps/), para ayudar a reforzar la rotación habitual de tokens y reducir el impacto de que existan tokens en riesgo. {% comment %} https://github.com/github/releases/issues/966 {% endcomment %}' - - heading: Cambios de desarrollador - notes: - - '[La IU de GitHub actualizó su diseño](https://github.blog/changelog/2020-06-23-design-updates-to-repositories-and-github-ui/), y la página principal de los repositorios se rediseñó e incluyó un diseño receptivo yuna experiencia web móvil mejorada. {% comment %} https://github.com/github/releases/issues/886 {% endcomment %}' - - 'En el menú desplegable "Clonar con SSH" de los repositorios, se notificará ahora a los usuarios si no han configurado ninguna llave. {% comment %} https://github.com/github/github/pull/149098 {% endcomment %}' - - 'Las confirmaciones ahora se ordenan cronológicamente en la línea de tiempo de las solicitudes de cambios y en la pestaña de confirmaciones. Este orden nuevo también se refleja en la API de REST de ["Listar comnfirmaciones en una solicitud de cambios"](https://docs.github.com/en/enterprise/2.22/user/rest/reference/pulls#list-commits-on-a-pull-request) y en el ["Objeto PullRequest"] de GraphQL (https://docs.github.com/en/enterprise/2.22/user/graphql/reference/objects#pullrequest) timeline connection. {% comment %} https://github.com/github/releases/issues/867 {% endcomment %}' - - 'Los usuarios ahora pueden [configurar un tono de tema predeterminado para los resultados de autocompletado de emojis](https://github.blog/changelog/2020-07-17-customizable-skin-tones-in-emoji-autocomplete/) en las áreas de texto de los comentarios. {% comment %} https://github.com/github/releases/issues/916 {% endcomment %}' - - '[Tree-sitter](https://github.com/tree-sitter/tree-sitter) mejora el resaltado de sintaxis y ahora es la biblioteca predeterminada que se utiliza para en análisis de los lenguajes de programación. {% comment %} https://github.com/github/releases/issues/918, https://github.com/github/windrose/issues/44 {% endcomment %}' - - heading: Los usuarios y las organizaciones pueden agregar nombres de usuario de Twitter a sus perfiles de GitHub - notes: - - '[Los desarrolladores y las organizaciones ahora pueden agregar sus nombres de usuario de Twitter a sus perfiles](https://github.blog/changelog/2020-07-22-users-and-organizations-can-now-add-twitter-usernames-to-their-github-profiles/) {% comment %} https://github.com/github/github/pull/145127 {% endcomment %}' - - heading: Cambios a la API - notes: - - | - #### Vistas previas graduadas - - Las siguientes vistas previas ahora son parte oficial de la API: - * La API y terminales de las GitHub Apps que devolvían la propiedad `performed_via_github_app` ya no requieren el encabezado de vista previa [`machine-man`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/). {% comment %} https://github.com/github/releases/issues/965 {% endcomment %} - * Para agregar y ver una razón de bloqueo de una propuesta, ya no necesitas utilizar el encabezado de vista previa [`sailor-v`](https://developer.github.com/changes/2020-08-20-graduate-machine-man-and-sailor-v-previews/). {% comment %} https://github.com/github/github/pull/143676 {% endcomment %} - - | - #### Cambios al modelo de GraphQL - - * [Los cambios al modelo de GraphQL](https://docs.github.com/enterprise/2.22/user/graphql/overview/changelog) incluyen aquellos retro-compatibles, vistas previas del modelo, y cambios significativos próximos. - - heading: Cambios en el Controlador de VMware Network - notes: - - | - El adaptador de red predeterminado de GitHub Enterprise Server para los clientes de VMware se cambió de E1000 a VMXNET3, comenzando con el lanzamiento 2.22.0. Cuando se actualiza desde una versión anterior a la 2.22.0 o superior, si se detecta un adaptador de red E1000 durante la verificación de pre-mejora, se mostrará el siguiente mensaje en la línea de comandos: - - ``` - WARNING: Your virtual appliance is currently using an emulated Intel E1000 network adapter. - For optimal performance, please update the virtual machine configuration on your VMware host to use the VMXNET3 driver. - Proceed with installation? [y/N] - ``` - El administrador puede elegir actualizar el tipo de adaptador de red a VMXNET3 ya sea antes o después de que se mejore el GitHub Enterprise Server. El aplicativo virtual necesitará apagarse para este cambio. Los clientes deben seguir los pasos recomendados de VMware para [cambiar la configuración del adaptador de red de la máquina virtual](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-3719A0BE-4B4A-44FF-8A21-290950918FBD.html) a VMXNET3. Por favor, nota que `VMXNET3`no será una opción si la versión del SO para el aplicativo virtual se configura en `Other Linux (64-bit)`. En este caso, primero se tendrá que cambiar la versión del SO de `Other Linux (64-bit)` a `Other 2.6.x Linux (64-bit)` o, en caso de que esté disponible, a `Debian GNU/Linux 9` . Te recomendamos probar estos cambios en una [instancia de montaje](https://docs.github.com/en/enterprise-server@2.22/admin/installation/setting-up-a-staging-instance) antes de que se mueva a un ambiente productivo de GitHub Enterprise Server.{% comment %} https://github.com/github/ghes-infrastructure/issues/781 {% endcomment %} - bugs: - - 'La página de stafftools para visualizar colaboradores pendientes mostró un `500 Internal Server Error` cuando había una invitación de correo electrónico pendiente. {% comment %} https://github.com/github/github/pull/150836 {% endcomment %}' - - 'La verificación desalud del repositorio en stafftools puede mostrar resultados incorrectos en los repositorios ocupados. {% comment %} https://github.com/github/github/pull/151160 {% endcomment %}' - - 'Un usuario que inició sesión e intentó aceptar una invitación por correo electrónico pudo encontrarse con un error `404 Not Found`. {% comment %} https://github.com/github/github/pull/150848 {% endcomment %}' - - 'Si los usuarios navegan a un repositorio cuyo nombre iniciaba con "repositories.", se les redirigió a la pestaña de "Repositorios" del propietario en vez de llegar a la página de resumen de éste. {% comment %} https://github.com/github/github/pull/149704 {% endcomment %}' - - 'Las etiquetas en la línea de tiempo del tablero no tienen suficiente contraste. {% comment %} https://github.com/github/github/pull/146749 {% endcomment %}' - deprecations: - - heading: Futura obsoletización de GitHub Enterprise Server 2.19 - notes: - - '**GitHub Enterprise Server 2.19 se obsoletizará desde el 12 de noviembre de 2020** Esto significa que no se harán lanzamientos de parches, aún para los problemas de seguirdad críticos, después de esta fecha. [actualiza a la versión más nueva de GitHub Enterprise Server](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) tan pronto como te sea posible.' - - heading: Obsoletización de los Eventos de Webhook tradicionales de las GitHub Apps - notes: - - 'A partir de la versión 2.21.0 de GitHub Enterprise Server, dos webhooks relacionados con GitHub Apps tradicionales se obsoletizaron y se eliminarán en la versión 2.25.0 de dicho producto. Los eventos obsoletizados de `integration_installation` y `integration_installation_repositories` tienen eventos equivalentes que serán compatibles. Hay más información disponible en la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' - - heading: Obsoletización de la terminal tradicional para las GitHub Apps - notes: - - 'A partir de la versión 2.21.0 de GitHub Enterprise Server, se obsoletizará la terminal tradicional de las GitHub Apps para crear tokens de acceso ainstalaciones y se eliminará en la versión 2.25.0 de dicho producto. Hay más información en la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). {% comment %} https://github.com/github/enterprise-web/pull/6419#issuecomment-668303461 {% endcomment %}' - - heading: Obsoletización de la API de aplicaciones OAuth - notes: - - 'GitHub ya no es compatible con las terminales de las aplicaciones OAuth que contengan `access_token` como parámetro de ruta. Incluimos terminales nuevas que te permiten administrar los tokens de forma segura para las Apps de OAuth al migrar `access_token` hacia el cuerpo de la solicitud. Aunque se obsoletizaron, aún se puede acceder a las terminales en esta versión. Pretendemos eliminar estas terminales para la versión 3.4 de GitHub Enterprise Server. Para obtener más información, consulta la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).' - backups: - - 'GitHub Enterprise Server 2.22 requiere por lo menos las [Utilidades de Respaldo de GitHub Enterprise](https://github.com/github/backup-utils) 2.22.0 para hacer [Respaldos y Recuperación de Desastres](https://help.github.com/enterprise/2.22/admin/guides/installation/backups-and-disaster-recovery/).' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'El menú desplegable de formato de ID de nombre en la consola de administración se restablece a "no especificado" después de configurar la instancia en "persistente". {% comment %} https://github.com/github/enterprise2/issues/13446 {% endcomment %}' - - 'La página de configuración del repositorio para los sitios de GitHub Pages de un usuario u organización falla con un "500 Internal Server Error". {% comment %} https://github.com/github/github/issues/156183, {% endcomment %}' - - 'Los usuarios podrían experimentar un rendimiento más lento de recuperación y de Git clone en una instancia con replicas de disponibilidad alta debido a que las lecturas se reenviaron a un nodo diferente. {% comment %} https://github.com/github/spokesd/issues/746, {% endcomment %}' - - 'El [crear una GitHub App desde un manifiesto](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) falla. Para dar una solución alterna a este problema, los usuarios pueden seguir las instrucciones del manual para [crear una GitHub App](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app). {% comment %} https://github.com/github/enterprise2/issues/22849 {% endcomment %}' - - 'Los nombres de usuario de GitHub podrían cambiar sin querer cuando se utiliza una autenticación con SAML si el nombre de usuario de GitHub no empata con el valor del atributo mapeado en el campo `username en la consola de administración. (actualizado 2020-10-08) {% comment %} https://github.com/github/external-identities/issues/335 {% endcomment %}' - - 'En una instancia 2.22.0 recién configurada o después de actualizar 2.22.0, ya no se actualizará la fuente de actividad en el tablero de una organización. (actualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-22/1.yml b/translations/es-ES/data/release-notes/2-22/1.yml deleted file mode 100644 index 392f2e211a..0000000000 --- a/translations/es-ES/data/release-notes/2-22/1.yml +++ /dev/null @@ -1,70 +0,0 @@ -date: '2020-10-09' -sections: - security_fixes: - - '**MEDIO**: ImageMagick se actualizó a la dirección [DSA-4715-1](https://www.debian.org/security/2020/dsa-4715). {% comment %} https://github.com/github/enterprise2/pull/22623, https://github.com/github/enterprise2/pull/22610 {% endcomment %}' - - 'Las solicitudes de una integración de una GitHub App para actualizar un token de acceso de OAuth se aceptarán si se envían con la ID de cliente y secreto de cliente de OAuth válidos que se utilizaron para crear el token de actualización. {% comment %} https://github.com/github/github/pull/154921, https://github.com/github/github/pull/154423, https://github.com/github/ecosystem-apps/issues/1066 {% endcomment %}' - - 'El usuario cuyo nombre de usuario del directorio de LDAP se estandarice a una información de inicio de cuenta de GHES podría autenticarse en la cuenta existente. {% comment %} https://github.com/github/github/pull/156513, https://github.com/github/github/pull/155512 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/22912, https://github.com/github/enterprise2/pull/22878 {% endcomment %}' - bugs: - - | - El menú desplegable de Formato de Id de nombre en la consola de administración se restablecerá a "no especificado" después de configurarlo como "persistente". {% comment %} https://github.com/github/enterprise2/pull/22376, https://github.com/github/enterprise2/pull/22331, https://github.com/github/enterprise2/issues/13446 {% endcomment %} - - | - Hacer una actualización utilizando un hotpatch podría ocasionar un fallo con un error de tipo: `'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22557, https://github.com/github/enterprise2/pull/22552 {% endcomment %} - - | - La configuración de guardado a través de la [consola de administración](/admin/configuration/accessing-the-management-console) añadirá una línea nueva a los archivos de [certificado y llave TLS/SSL](/admin/configuration/configuring-tls) que activaron la recarga innecesaria de algunos servicios. {% comment %} https://github.com/github/enterprise2/pull/22570, https://github.com/github/enterprise2/pull/22540 {% endcomment %} - - | - Las bitácoras de sistema para la Gráfica de dependencias no estaban rotando, lo cual permitió un crecimiento desmedido del almacenamiento. {% comment %} https://github.com/github/enterprise2/pull/22767, https://github.com/github/enterprise2/pull/22733 {% endcomment %} - - | - La gráfica de rendimiento del servidor de MS SQL mostró las estadísticas de la instancia primaria aún cuando se seleccionó la réplica. {% comment %} https://github.com/github/enterprise2/pull/22778, https://github.com/github/enterprise2/pull/22750 {% endcomment %} - - | - `ghe-actions-precheck` saldrá silenciosamente sin ejecutar las verificaciones de almacenamiento si no se habilitaron las acciones. {% comment %} https://github.com/github/enterprise2/pull/22787, https://github.com/github/enterprise2/pull/22742 {% endcomment %} - - | - La mejora podría fallar si los trabajadores que se volvieron a poner en cola (resqued) invalidan la configuración que se está utilizando. {% comment %} https://github.com/github/enterprise2/pull/22836, https://github.com/github/enterprise2/pull/22814 {% endcomment %} - - | - Algunos servicios que se ejecutan en los contenedores no estaban enviando bitácoras al diario. {% comment %} https://github.com/github/enterprise2/pull/22994, https://github.com/github/enterprise2/pull/22518 {% endcomment %} - - | - Los enlaces a las Asesorías de Seguridad de GitHub utilizaron una URL con el nombre de host de la instancia de GitHub Enterprise Server en vez de la de GitHub.com, lo cual dirigió al usuario a una URL inexistente. {% comment %} https://github.com/github/github/pull/153316, https://github.com/github/github/pull/151301 {% endcomment %} - - | - Cuando importas un repositorio con un `ghe-migrator`, puede ocurrir una excepción inesperada cuando se presentan los datos inconsistentes. {% comment %} https://github.com/github/github/pull/153850, https://github.com/github/github/pull/151552 {% endcomment %} - - | - La página de configuración de seguridad para la cuenta empresarial mostró un enlace para "Visualizar las configuraciones actuales de tus organizaciones" para la configuración de "autenticación bifactorial" cuando el modo de autenticación no es compatible con la autenticación bifactorial incluida. {% comment %} https://github.com/github/github/pull/153860 {% endcomment %} - - | - Los tokens de actualización de OAuth se eliminaron prematuramente. {% comment %} https://github.com/github/github/pull/154271, https://github.com/github/github/pull/153694 {% endcomment %} - - | - Las tareas de búsuqeda y reparación generaron excepciones durante la fase de migración de la configuración. {% comment %} https://github.com/github/github/pull/154573, https://github.com/github/github/pull/153392 {% endcomment %} - - | - En la página de configuración para las GitHub Apps, las "Características Beta" no se podían visualizar en algunas circunstancias. {% comment %} https://github.com/github/github/pull/154612, https://github.com/github/github/pull/154417 {% endcomment %} - - | - Cuando se utiliza `ghe-migrator` para importar las solicitudes de revisión de PR, los registros asociados con los usuarios borrados resultaron en registros de una base de datos extraña. {% comment %} https://github.com/github/github/pull/154960, https://github.com/github/github/pull/153169 {% endcomment %} - - | - Cuando se importan los usuarios con `ghe-migrator`, ocurrió un error de "El correo electrónico es inválido" si la dirección de correo electrónico que generó el sistema era mayor a 100 caracteres. {% comment %} https://github.com/github/github/pull/155109, https://github.com/github/github/pull/152418 {% endcomment %} - - | - El registrar la actividad de los webhooks puede utilizar cantidades grandes de espacio en disco y causar que el disco raíz se llene. {% comment %} https://github.com/github/github/pull/155657, https://github.com/github/github/pull/154100 {% endcomment %} - - | - Los usuarios experimentaron un rendimiento más lento de recuperación y de Git clone en una instancia con replicas de disponibilidad alta debido a que las lecturas se reenviaron a un nodo diferente. {% comment %} https://github.com/github/github/pull/156195, https://github.com/github/github/pull/156016, https://github.com/github/spokesd/issues/746 {% endcomment %} - - | - La página de configuración del repositorio para los sitios de GitHub Pages de un usuario u organización fallaron con un "500 Internal Server Error". {% comment %} https://github.com/github/github/pull/156439, https://github.com/github/github/issues/156183 {% endcomment %} - - | - Las operaciones de mantenimiento de red del repositorio podrían haberse estancado en un estado de `running`. {% comment %} https://github.com/github/github/pull/156669, https://github.com/github/github/pull/156036 {% endcomment %} - - | - El hecho de que un repositorio se borrara inmediatamente después de cargar un resultado de escaneo de código pudo haber causado un estancamiento en el procesamiento de los resultados de dicho escaneo de código en todos los repositorios. {% comment %} https://github.com/github/github/pull/157063, https://github.com/github/github/pull/156437 {% endcomment %} - - | - Cuando se emitió una cantidad grande de resultados del escaneo de código al mismo tiempo, el procesamiento de lotes pudo haber agotado el tiempo, lo cual resultó en el estancamiento del procesamiento de los resultados del escaneo de código. {% comment %} https://github.com/github/github/pull/157065, https://github.com/github/github/pull/156462 {% endcomment %} - - | - El [Crear una GitHub App desde un manifiesto](https://docs.github.com/en/enterprise/2.22/user/developers/apps/creating-a-github-app-from-a-manifest) falló. {% comment %} https://github.com/github/github/pull/157133, https://github.com/github/github/pull/156904, https://github.com/github/enterprise2/issues/22849 {% endcomment %} - - | - Los nombres de usuario de GitHub se cambiaron sin querer cuando se utilizó la autentificación con SAML, cuando el nombre de usuario de GitHub no empató con el valor del atributo mapeado en el campo de `username` en la Consola de Administración. {% comment %} https://github.com/github/github/pull/158131, https://github.com/github/github/pull/157936, https://github.com/github/external-identities/issues/335 {% endcomment %} - changes: - - 'Se agrega compatibilidad con el tipo de instancia `m5.16xlarge` de AWS EC2. {% comment %} https://github.com/github/enterprise2/pull/22502, https://github.com/github/enterprise2/pull/22473 {% endcomment %}' - - 'Elimina el requisito de las huellas dactilares de SSH en los archivos de `ghe-migrator`, ya que siempre se le puede calcular. {% comment %} https://github.com/github/github/pull/156946, https://github.com/github/github/pull/155387 {% endcomment %}' - - 'Los manifiestos de las GitHub Apps ahora incluyen el campo `request_oauth_on_install`. {% comment %} https://github.com/github/github/pull/156991, https://github.com/github/github/pull/155010, https://github.com/github/ecosystem-apps/issues/1055 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Las actualizaciones de configuración fallan cuando se restablecen los datos en una instancia que tiene habilitadas las GitHub Actions si la fuente de respaldo original no cuenta con la característica habilitada. {% comment %} https://github.com/github/c2c-actions-runtime/issues/915 {% endcomment %}' - - 'Las GitHub Actions pueden fallar en su inicio exitoso si se habilitaron previamente en una instancia que ejecutara la versión 2.22.0 y se actualiza a la 2.22.1. (actualizado en 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %}' - - 'En una instancia 2.22.1 recién configurada o después de actualizar 2.22.1, ya no se actualizará la fuente de actividad en el tablero de una organización. (actualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %}' - - 'Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-22/10.yml b/translations/es-ES/data/release-notes/2-22/10.yml deleted file mode 100644 index 1a8d755236..0000000000 --- a/translations/es-ES/data/release-notes/2-22/10.yml +++ /dev/null @@ -1,15 +0,0 @@ -date: '2021-04-01' -sections: - security_fixes: - - '**ALTO:** Se identificó una vulnerabilidad de control de acceso inadecuada en GitHub Enterprise Server, la cual permitió que los tokens de acceso generados desde un [flujo de autenticación web](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) de una GitHub App leyera los metadatos de un repositorio privado a través de la API de REST sin que se le hubieran otorgado los permisos adecuados. Para explotar esta vulnerabilidad, el atacante necesitaría crear una GitHub App en la instancia y hacer que un usuario autorice la aplicación mediante el flujo de autenticación web. Los metadatos del repositorio privado que se devolvió estarían limitados a los repositorios que pertenecen al usuario al cual identifica el token. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anterior a la 3.0.4 y se arregló en las versiones 3.0.4, 2.22.10 y 2.21.18. A esta vulnerabilidad se le asignó un CVE-2021-22865 y se reportó mediante el [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - Algunos servicios que estaban dando un tiempo UTC predetemrinado no estaban tulizando una zona horaria configurada en GitHub Enterprise 11.10.x o anterior. - - 'Los servicios no estaban haciendo la transición a los archivos de bitácora nuevos como parte de la rotación de bitácoras, lo cual dio como resultado un uso de disco incrementado.' - - La etiqueta de los resultados de la búsqueda para los repositorios internos se mostró como "Privada" en vez de como "Interna". - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' diff --git a/translations/es-ES/data/release-notes/2-22/11.yml b/translations/es-ES/data/release-notes/2-22/11.yml deleted file mode 100644 index 39041dc5e6..0000000000 --- a/translations/es-ES/data/release-notes/2-22/11.yml +++ /dev/null @@ -1,18 +0,0 @@ -date: '2021-04-14' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - 'Un mensaje de advertencia de tipo `jq: error (at :0): Cannot index number with string "settings"` podría ocurrir durante la promoción de la réplica.' - - El restablecer respaldos continuamente a un clúster pudo haber fallado debido a que las réplicas de MySQL fallaron en conectarse al primario. - - El resaltado de sintaxis pudo haber fallado debido a que el contenedor de Treelights se quedó sin memoria. - - Visitar la página `/settings/emails` almacenó el estado que pudo haber causado redirecciones inadecuadas al finalizar sesión y volverla a iniciar. - - Las alertas de la gráfica de dependencias no se mostraron para algunos componentes cuyas asesorías tienen nombres de paquetes con mayúsculas en `vulnerable_version_ranges`. - - Las apps de integración a GitHub no pudieron notificar a los equipos cuando se les mencionó directamente a través de una @mención en un comentario de una propuesta. - - 'Cuando el ghe-migrator encontró errores de importación, algunas veces abortó todo el proceso y las bitácoras no incluyeron suficiente contexto.' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' diff --git a/translations/es-ES/data/release-notes/2-22/12.yml b/translations/es-ES/data/release-notes/2-22/12.yml deleted file mode 100644 index d591710374..0000000000 --- a/translations/es-ES/data/release-notes/2-22/12.yml +++ /dev/null @@ -1,21 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - 'During upgrades, the process would pause indefinitely after `cleanup nomad job`.' - - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.' - - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.' - - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover. - - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.' - - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected. - - Organizations or projects with errors blocked migration and could not be excluded. - - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes. - changes: - - Preflight checks allow all AWS instance types by default. - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' diff --git a/translations/es-ES/data/release-notes/2-22/13.yml b/translations/es-ES/data/release-notes/2-22/13.yml deleted file mode 100644 index 0fb5369017..0000000000 --- a/translations/es-ES/data/release-notes/2-22/13.yml +++ /dev/null @@ -1,19 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - '**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App''s user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/).' - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - Orchestrator auto failover could be enabled during the phase of config apply. - - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page. - - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path. - - OpenAPI documentation referred to an invalid header. - changes: - - Added logging for config change on HAProxy reload. - - Added logging for repository creation. - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' diff --git a/translations/es-ES/data/release-notes/2-22/2.yml b/translations/es-ES/data/release-notes/2-22/2.yml deleted file mode 100644 index 70b44e7697..0000000000 --- a/translations/es-ES/data/release-notes/2-22/2.yml +++ /dev/null @@ -1,29 +0,0 @@ ---- -date: '2020-10-20' -sections: - security_fixes: - - Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23097, https://github.com/github/enterprise2/pull/23081 {% endcomment %} - bugs: - - | - Si la configuración de la cuenta de almacenamiento falló su validación cuando se configuró GitHub Actions, se requirió ejecutar `ghe-actions-teardown` antes de hacer un intento nuevo. {% comment %} https://github.com/github/enterprise2/pull/23057, https://github.com/github/enterprise2/pull/22981 {% endcomment %} - - | - Una configuración de proxy personalizado pudo haber afectado de forma adversa al ambiente de GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23121, https://github.com/github/enterprise2/pull/23092, https://github.com/github/c2c-actions-platform/issues/2254 {% endcomment %} - - | - En un cambio de dirección de eth0, Nomad y Consul podrían dejar de responder. {% comment %} https://github.com/github/enterprise2/pull/23227, https://github.com/github/enterprise2/pull/23153 {% endcomment %} - - | - Cuando se utilizan certificados auto-firmados, GHES podría tener excepciones de validación de SSL al configurar las GitHub Actions. {% comment %} https://github.com/github/enterprise2/pull/23381 {% endcomment %} - - | - El utilizar una GitHub Action desde un nombre de rama con un caracter `+` o `/` resultó en un error: `Unable to resolve action`. {% comment %} https://github.com/github/github/pull/157942, https://github.com/github/github/pull/157819, https://github.com/github/launch/pull/3463 {% endcomment %} - - | - El mensaje de la "Política de confirmación para el requisito bifactorial" en una cuenta empresarial fue incorrecto. {% comment %} https://github.com/github/github/pull/158735 {% endcomment %} - - | - En ciertas solicitudes mayores a 100MB, el buffer de Kafka pudo estar sobreasignado. {% comment %} https://github.com/github/kafka-lite/pull/286, https://github.com/github/kafka-lite/pull/285 {% endcomment %} - known_issues: - - En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Las GitHub Actions pueden fallar en su inicio exitoso si se habilitaron previamente en una instancia que ejecutara la versión 2.22.0 y se actualiza a la 2.22.2. (actualizado en 2020-10-23) {% comment %} https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - En una instancia 2.22.2 recién configurada o después de actualizar 2.22.2, ya no se actualizará la fuente de actividad en el tablero de una organización. (actualizado 2020-10-27) {% comment %}https://github.com/github/enterprise2/issues/23050{% endcomment %} - - Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. (actualizado 2020-11-02) {% comment %}https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/es-ES/data/release-notes/2-22/3.yml b/translations/es-ES/data/release-notes/2-22/3.yml deleted file mode 100644 index 7bdd267c28..0000000000 --- a/translations/es-ES/data/release-notes/2-22/3.yml +++ /dev/null @@ -1,23 +0,0 @@ ---- -date: '2020-11-03' -sections: - security_fixes: - - | - **BAJO:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (Dos) en el servicio del puente SVN. (actualizado 2020-11-16) {% comment %} https://github.com/github/slumlord/pull/1005, https://github.com/github/slumlord/pull/1000 {% endcomment %} - - | - **BAJO:** La validación de un token incorrecto resultó en una entropía reducida para los tokens coincidentes durante la autenticación. El análisis muestra que, en la práctica, aquí no hay riesgos de seguridad significativos. {% comment %} https://github.com/github/github/pull/159457, https://github.com/github/github/pull/159193 {% endcomment %} - - | - Los paquetes se actualizaron a las últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23540, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23693, https://github.com/github/enterprise2/pull/23677 {% endcomment %} - bugs: - - Las GitHub Actions pueden fallar para iniciar exitosamente si se habilitaron previamente en una instancia que ejecutara la versión 2.22.0 y se actualizó a la 2.22.1 o 2.22.2. {% comment %} https://github.com/github/enterprise2/pull/23622, https://github.com/github/enterprise2/pull/23490, https://github.com/github/c2c-actions/issues/1680 {% endcomment %} - - Los archivos de configuración para las GitHub Actions no se copiaron a la replica cuando se configuraron las réplicas de disponibilidad alta, lo cual produjo errores durante `ghe-repl-promote`. {% comment %} https://github.com/github/enterprise2/pull/23703, https://github.com/github/enterprise2/pull/23683 {% endcomment %} - - En una instancia 2.22.1 recién configurada o después de actualizar 2.22.1, no se pudo actualizar la fuente de actividad en el tablero de una organización. {% comment %} https://github.com/github/github/pull/159376, https://github.com/github/github/pull/159235, https://github.com/github/enterprise2/issues/23050 {% endcomment %} - - El editar las plantillas de las propuestas con los nombres de archivo que contienen caracteres que no son de ASCII fallará con un mensaje de "500 Internal Server Error".{% comment %} https://github.com/github/github/pull/160588, https://github.com/github/github/pull/159747 {% endcomment %} - - Un método de recolección métrica para los jobs en segundo plano incrementó el uso del CPU. (actualizado 2020-11-03) {% comment %} https://github.com/github/github/pull/160109 {% endcomment %} - known_issues: - - En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} - - Las bitácoras de auditoría pueden atribuirse a la 127.0.0.1 en vez de a la dirección IP de origen real. {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %} diff --git a/translations/es-ES/data/release-notes/2-22/4.yml b/translations/es-ES/data/release-notes/2-22/4.yml deleted file mode 100644 index f49be20cc4..0000000000 --- a/translations/es-ES/data/release-notes/2-22/4.yml +++ /dev/null @@ -1,16 +0,0 @@ ---- -date: '2020-11-17' -sections: - security_fixes: - - Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/23845, https://github.com/github/enterprise2/pull/23712 {% endcomment %} - bugs: - - Las bitácoras de babeld no tenían un separador entre los segundos y microsegundos. {% comment %} https://github.com/github/babeld/pull/1006, https://github.com/github/babeld/pull/1002 {% endcomment %} - - Después de actualizar a GHES con un hotpatch, los comandos `ghe-actions-precheck` y `ghe-packages-precheck` fallaron con el error `"docker load" accepts no arguments`. {% comment %} https://github.com/github/enterprise2/pull/23760, https://github.com/github/enterprise2/pull/23745 {% endcomment %} - - Cuando la política "Cambio de visibilidad del repositorio" en las cuentas empresariales se configura como "Habilitada", los propietarios de las organizaciones no pudieron cambiar la visibilidad de los repositorios dentro de las organizaciones. {% comment %} https://github.com/github/github/pull/160920, https://github.com/github/github/pull/160773 {% endcomment %} - - Las bitácoras de auditoría podrían atribuirse a la 127.0.0.1 en vez de a la dirección IP origen real. {% comment %} https://github.com/github/github/pull/162438, https://github.com/github/github/pull/161215 {% endcomment %} - known_issues: - - En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %} - - Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %} - - 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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %} - - Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %} - - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %} diff --git a/translations/es-ES/data/release-notes/2-22/5.yml b/translations/es-ES/data/release-notes/2-22/5.yml deleted file mode 100644 index 54ae65138f..0000000000 --- a/translations/es-ES/data/release-notes/2-22/5.yml +++ /dev/null @@ -1,22 +0,0 @@ ---- -date: '2020-12-03' -sections: - bugs: - - 'El servicio de autorización se detectó como no saludable debido a la condición de raza en bootstrap, lo cual ocasionó que se reiniciara el servicio. {% comment %} https://github.com/github/authzd/pull/1275, https://github.com/github/authzd/pull/1274 {% endcomment %}' - - 'ghe-diagnostics no estaba capturando el proceso de mejora de Elasticsearch. {% comment %} https://github.com/github/enterprise2/pull/23905, https://github.com/github/enterprise2/pull/23874 {% endcomment %}' - - 'El habilitar las GitHub Actions en una configuración de disponibilidad alta mejorada causó errores en la replicación. {% comment %} https://github.com/github/enterprise2/pull/23979, https://github.com/github/c2c-actions-platform/issues/2479 {% endcomment %}' - - 'Un comportamiento subyacente estaba causando que un servicio estuviera no disponible durante el proceso de mejora del hotpatch.{% comment %} https://github.com/github/enterprise2/pull/24055 {% endcomment %}' - - 'Los usuarios que se conectaron a una réplica activa obtuvieron un error al conectarse al websocket de las actualizaciones en vivo. {% comment %} https://github.com/github/enterprise2/pull/24079, https://github.com/github/enterprise2/pull/24058 {% endcomment %}' - - 'Un subconjunto de certificados SSL que reenviaban bitácoras no se estaba aplicando correctamente. {% comment %} https://github.com/github/enterprise2/pull/24114, https://github.com/github/enterprise2/pull/23981 {% endcomment %}' - - 'Se enviaron notificaciones de correo electrónico para suspender usuarios cuando se eliminaban de un equipo o de una organización. {% comment %} https://github.com/github/github/pull/162973, https://github.com/github/github/pull/162742 {% endcomment %}' - - 'La forma en la que se aplicaron los certificados SSH entre las organizaciones y los negocios fue inconsistente. {% comment %} https://github.com/github/github/pull/163423, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}' - - 'Cuando una cuenta se limitó en su tasa debido al uso incorrecto de contraseñas, se pudo haber bloqueado por hasta 24 horas. {% comment %} https://github.com/github/github/pull/163433, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}' - - 'La sincronización de solicitudes de cambios en los repositorios con muchas referencias pudo haber causado que se retrasaran las filas de trabajadores. {% comment %} https://github.com/github/github/pull/163573, https://github.com/github/github/pull/163142 {% endcomment %}' - - 'Al iniciar sesión con un nombre de usuario y contraseña locales (autenticación integrada) después de intentar visitar una página específica, se dirigió al usuario a la página principal en vez de al destino deseado. {% comment %} https://github.com/github/github/pull/163782, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}' - - 'Para las instancias de GHES que utilizan una autenticación integrada con un proveedor de identidad de SAML interno, los usuarios sin una dirección de correo electrónico asociada no pudieron crear una confirmación desde la interfase web. {% comment %} https://github.com/github/github/pull/164009, https://github.com/github/github/pull/163530, https://github.com/github/github/issues/163524 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-22/6.yml b/translations/es-ES/data/release-notes/2-22/6.yml deleted file mode 100644 index bef5321efe..0000000000 --- a/translations/es-ES/data/release-notes/2-22/6.yml +++ /dev/null @@ -1,18 +0,0 @@ ---- -date: '2020-12-17' -sections: - security_fixes: - - '**BAJO:** El uso alto de CPU puede desencadenarse debido a una solicitud hecha específicamente al puente de SVN, lo cual resulta en una negación del servicio (DoS). {% comment %} https://github.com/github/slumlord/pull/1022, https://github.com/github/slumlord/pull/1017 {% endcomment %}' - - 'Los paquetes se han actualizado a sus últimas versiones de seguridad. {% comment %} https://github.com/github/enterprise2/pull/24353, https://github.com/github/enterprise2/pull/23866 {% endcomment %}' - bugs: - - 'Las solicitudes para algunos recursos de archivos como un archivo zip o un archivo raw podrían ingresar en un bucle de redirección. {% comment %} https://github.com/github/enterprise2/pull/24193, https://github.com/github/enterprise2/pull/24075 {% endcomment %}' - - 'Un límite de tiempo podría prevenir que algunas búsquedas de propuestas y solicitudes de cambios proporcionen resultados de búsqueda completos. {% comment %} https://github.com/github/github/pull/164155, https://github.com/github/github/pull/163845 {% endcomment %}' - - 'Las pestañas personalizadas con caracteres no alfabéticos en pantallas pequeñas no se interpretaron correctamente. {% comment %} https://github.com/github/github/pull/164310, https://github.com/github/github/pull/164159 {% endcomment %}' - - 'Un comportamiento subyacente estaba causando fallas cuando se subía contenido a un repositorio de Git habilitado con LFS. {% comment %} https://github.com/github/github/pull/164663, https://github.com/github/github/pull/150179 {% endcomment %}' - - 'En algunos casos poco frecuentes las propuestas podrían causar un error 500 cuando se accede a ellas a través de la interface web. {% comment %} https://github.com/github/github/pull/165298, https://github.com/github/github/pull/159674 {% endcomment %}' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin ningún usuario, un atacante podría crear el primer usuario administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Las reglas de cortafuegos personalizadas no se mantienen durante una mejora. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Las propuestas no pueden cerrarse si contienen un enlace permanente a un blob en el mismo repositorio en donde la ruta es mayor a 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluyen en los resultados de la búsqueda de GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' diff --git a/translations/es-ES/data/release-notes/2-22/7.yml b/translations/es-ES/data/release-notes/2-22/7.yml deleted file mode 100644 index afbb9d98e7..0000000000 --- a/translations/es-ES/data/release-notes/2-22/7.yml +++ /dev/null @@ -1,57 +0,0 @@ ---- -date: '2021-03-02' -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de control de acceso incorrecto en GitHub Enterprise Server, la cual permitió a un usuario no autenticado de la instancia obtener acceso a los repositorios no autorizados a través de solicitudes de cambios y solicitudes a través de la API de REST configuradas específicamente. El atacante necesitaría poder bifurcar el repositorio de destino, dicha configuración está inhabilitada predeterminadamente para los repositorios privados y para los que pertenecen a una organización. Las protecciones de rama tales como las solicitudes de cambio o verificaciones de estado requeridas prevendrían que las confirmaciones no autorizadas se fusionen sin haber obtenido una revisión o validación adicionales. Se ha asignado un CVE-2021-22861 a esta vulnerabilidad. El problema se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - '**ALTA:** Se identificó una vulnerabilidad de control de acceso incorrecto en la API de GraphQL de GitHub Enterprise Server, la cual permitió a los usuarios autenticados de la instancia modificar el permiso de colaboración del mantenedor para una solicitud de cambios sin una autorización adecuada. Al aprovechar esta vulnerabilidad, el atacante pudo obtener acceso a las ramas de encabezado de las solicitudes de cambios que se abrieron en los repositorios donde ellos eran los mantenedores. La bifurcación se inhabilitó predeterminadamente para los repositorios privados que pertenecían a alguna organización, lo cual previno esta vulnerabilidad. Adicionalmente, las protecciones de rama tales como las revisiones requeridas para la solicitud de cambios o las verificaciones de estado prevendrían que las confirmaciones no autorizadas se fusionen sin contar con una validación o revisión subsecuente. Se asignó un CVE-2021-22863 a esta vulnerabilidad. Este problema se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server que pudo haberse aprovechado al compilar un sitio de GitHub pages. La configuración controlada por el usuario de los intérpretes subyacentes que utiliza GitHub Pages no se restringió lo suficiente y dio cabida a la ejecución de comandos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permiso para crear y compilar un sitio de GitHub pages en la instancia de GitHub Enterprise Server. Se asignó a esta vulnerabilidad un CVE-2020-10519 y se reportó a través del [Programa de Recompensa por Errores de GitHub](https://bounty.github.com).' - - '**MEDIA:** Los GitHub tokens de las compilaciones de GitHub Pages pudieron haber terminado en las bitácoras.' - - '**BAJA:** Una solicitud que se elaboró especialmente para el puente SVN pudo haber activado una espera larga antes de que hubiera una falla, lo cual dio como resultado un ataque de Negación del Servici (DoS).' - - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' - bugs: - - 'Las verificaciones de salud del balanceador de carga pudieron haber causado en algunos casos que los logs de babel se llenaran con errores sobre el protocolo del PROXY.' - - 'Un mensaje informativo se registro involuntariamente como un error durante las capturas de pantalla de las Utilidades de Respaldo de GitHub Enterprise, lo cual dio como resultado que se enviaran correos electrónicos innecesarios cuando los jobs de cron programaron los respaldos que escuchaban a la salida a stderr.' - - 'Al restablecer un respaldo grande, el registro de excepciones relacionado con el agotamiento de memoria de Redis pudo haber causado que la restauración fallara debido a un disco lleno.' - - 'Cuando configuras una instancia nueva por primera vez, si se seleccionó "Configurar como réplica", no se podía iniciar la replicación.' - - 'Cuando se habilitó GitHub Actions, el inhabilitar el modo de mantenimiento en la consola de administración, falló.' - - 'El editar una página de wiki, un usuario pudo haber experimentado un error 500 al hacer clic en el botón de guardar.' - - 'Una confirmación firmada con S/MIME utilizando un certificado con nombres múltiples en el nombre alternativo de asunto se mostró incorrectamente como "No verificado" en la insignia de confirmación.' - - 'Se enviaron correos electrónicos a un usuario suspendido cuando se le agregó a un equipo.' - - 'Un usuario vio un error 500 al ejecutar operaciones de git en una instancia configurada con autenticación LDAP.' - - 'El job en segundo plano `remove_org_member_package_access` pudo visualizarse en la consola de administración e incrementaba contínuamente.' - - 'Cuando un repositorio tuvo una gran cantidad de manifiestos se mostró un error de `You have reached the maximum number of allowed manifest files (20) for this repository.` en la pestaña ubicada en Perspectivas -> Gráfica de dependencias. Para obtener más información, consulta la sección [Límites de visualización] (https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'Al cargar un archivo de licencia nuevo con una cantidad de plazas diferente del archivo de licencia anterior, la diferencia de plazas no se representó correctamente en la página de Configuración -> Licencia de la cuenta empresarial.' - - 'La casilla de verificación de "Prevent repository admins from changing anonymous Git read access" disponible en la configuración de cuenta empresarial no se pudo habilitar o inhabilitar con éxito.' - - 'Cuando una compilación de GitHub Pages falló, la notificación de correo electrónico contenía un enlace incorrecto para la ubicación de soporte.' - - 'Durante un año bisiesto, el usuario estuvo obtuvo una respuesta 404 cuando intentó ver la actividad de contribución en un lunes.' - changes: - - 'Se agregó soporte para los [tipos de instanciaAWS EC2 r5b](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-featuring-60-gbps-of-ebs-bandwidth-and-260K-iops/).' - - 'Se ajustó la priorización de la cola en segundo plano para distribuir los jobs más equitativamente.' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - 'Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.' - - '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.' - - | - Los usuarios podrían experimentar que los activos tales como los avatares no carguen, o que hayan fallos en el código de subida/extracción. Esto podría darse por un desajuste de PID en el servicio `haproxy-cluster-proxy`. Para determinar si tienes una instancia afectada: - - **Instancia única** - - 1. Ejecuta lo siguiente en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. Si muestra que hay un desajuste, reinicia la instancia. - - **Configuración en Clúster o en Disponibilidad Alta** - - 1. Ejecuta lo siguiente en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. Si muestra que uno o más nodos están afectados, reinícialos. diff --git a/translations/es-ES/data/release-notes/2-22/8.yml b/translations/es-ES/data/release-notes/2-22/8.yml deleted file mode 100644 index 820a77d10a..0000000000 --- a/translations/es-ES/data/release-notes/2-22/8.yml +++ /dev/null @@ -1,37 +0,0 @@ ---- -date: '2021-03-16' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - Las bitácoras de los diarios de Systemd se duplicaron en varios lugares. - - Un adminsitrador de sitio podría obtener un error de página 500 al intentar ver las propuestas que se referenciaban de repositorios privados. - - El importar repositorios archivados desde GitHub Enterprise Server a los cuales les faltan archivos de repositorio, fallará con un error. - known_issues: - - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - 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. - - | - Los usuarios podrían experimentar que los activos tales como los avatares no carguen, o que hayan fallos en el código de subida/extracción. Esto podría darse por un desajuste de PID en el servicio `haproxy-cluster-proxy`. Para determinar si tienes una instancia afectada: - - **Instancia única** - - 1. Ejecuta lo siguiente en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. Si muestra que hay un desajuste, reinicia la instancia. - - **Configuración en Clúster o en Disponibilidad Alta** - - 1. Ejecuta lo siguiente en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. Si muestra que uno o más nodos están afectados, reinícialos. diff --git a/translations/es-ES/data/release-notes/2-22/9.yml b/translations/es-ES/data/release-notes/2-22/9.yml deleted file mode 100644 index 491668200c..0000000000 --- a/translations/es-ES/data/release-notes/2-22/9.yml +++ /dev/null @@ -1,35 +0,0 @@ ---- -date: '2021-03-23' -intro: Se han desactivado las descargas debido a un error importante que afectó a varios clientes. Pronto tendremos una solución en el siguiente parche. -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server, la cual pudo haberse aprovechado al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario que utilizan las GitHub Pages no se restringieron lo suficiente e hicieron posible que se ignoraran las variables de ambiente que llevaron a la ejecución de código en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permisos 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 antes de la 3.0.3 y se arregló en la 3.0.3, 2.22.9, y 2.21.17. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub y se le asignó un CVE-2021-22864.' - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - El ejecutar `ghe-cluster-config-init` pudo haber causado que un clúster fuera inoperable. - - El sistema pudo haber perdido el rastreo del PID de HAProxy. - - La advertencia de la recuperación de fallos de mysql se mostró indefinidamente después de una recuperación de fallos exitosa. - - La ejecución de `ghe-cluster-config-init` no reconocía completamente el código de salida de los jobs en segundo plano que condujeron a un manejo inadecuado de las verificaciones previas al vuelo. - - Un enlace de Seguridad y Análisis no aparecía en la barra de navegación izquierda en la página de configuración de los repositorios. - - Después de inhabilitar GitHub packages, algunas páginas de la organización regresaban una respuesta de error HTTP 500. - changes: - - Mejora la confiabilidad de los servicios nómadas al implementar la misma política de reinicio que se introdujo en GitHub Enterprise Server 3.0. - - Utiliza una cantidad relativa para el `bootstrap_expect` cónsul y nómada, lo cual permitió que un clúster hiciera un arranque primario, incluso si un conjunto de nodos estaba fuera de servicio. - - Las bitácoras rotarán con base en su tamaño adicionalmente al tiempo. - - Se agregó a kafka-lite al comando `ghe-cluster-status`. - known_issues: - - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - 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. - - |2 - La rotación de bitácoras podrían fallar en señalizar los servicios para transicionar a archivos de bitácora nuevos, lo cual lleva a que los archivos de bitácora antiguos se sigan utilizando y a un agotamiento de espacio en el disco raíz eventuales. - Para remediar o prevenir este problema, ejecuta los siguientes comandos en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), o contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) para recibir asistencia: - - ``` - 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 - ``` - - sections -> known_issues -> 6 diff --git a/translations/es-ES/data/release-notes/3-0/0-rc.yml b/translations/es-ES/data/release-notes/3-0/0-rc.yml deleted file mode 100644 index 9c3f95d137..0000000000 --- a/translations/es-ES/data/release-notes/3-0/0-rc.yml +++ /dev/null @@ -1,144 +0,0 @@ ---- -date: '2021-01-12' -release_candidate: true -intro: Release notes are now published on the documentation site. The new location makes it easier to learn about new releases and features at the same time. Historical release notes are available on [GitHub Enterprise Releases](https://enterprise.github.com/releases). -sections: - features: - - - heading: GitHub Actions - notes: - - | - [{% data variables.product.prodname_actions %}](https://github.com/features/actions) is now generally available on {% data variables.product.prodname_ghe_server %} 3.0+. Build, test, and deploy your code from {% data variables.product.prodname_dotcom %}. Submit code reviews, branch management, and issue triaging work the way you want. - - This release includes several improvements from the beta of {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}: - - - Enterprise, organization, and repository admins can create security policies for access to {% data variables.product.prodname_actions %} on {% data variables.product.prodname_dotcom_the_website %}. - - Enterprise, organization, and repository admins can allow public repositories to use self-hosted runners. - - Enterprise, organization, and repository admins can now allow workflows to [run on pull requests raised from forks of private repositories](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). - - The `workflow_run` event is [now supported](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) - - Users now have the ability to [disable workflows and enable them at a later date](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). - - Workflow logs have been enhanced for a [better user experience](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). - - Users can now use private images in container jobs and services. - - The max retention days for [artifacts and logs can now be customized](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). - - The runner group API now includes [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). - - You can now create reusable actions using shell scripts with compose run steps. - - [Encrypted secrets for an organization](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) allows you to consolidate secrets across repositories. - - [Workflow templates for an organization](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) streamlines and promotes best practices and consistency across your organization. - - {% data variables.product.prodname_actions %} is not currently supported for enterprises using cluster configurations. - - - heading: Registro del paquete de GitHub - notes: - - | - [{% data variables.product.prodname_registry %}](https://github.com/features/packages) is a package hosting service, natively integrated with GitHub APIs, Actions, and webhooks. Create an [end-to-end DevOps workflow](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) that includes your code, continuous integration, and deployment solutions. - - Supported storage back ends include AWS S3 and MinIO with support for Azure blob coming in a future release. Please note that the current Docker support will be replaced by a beta of the new GitHub Container Registry in the next release. Please review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_registry %}. - - When publishing packages to NuGet, users can now use the `--api-key` option to pass their authentication token instead of writing it into a file. For more information, see [Configuring dotnet CLI for use with GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) - - {% data variables.product.prodname_registry %} is not currently supported for enterprises using cluster configurations. - - - heading: GitHub Mobile beta - notes: - - | - [{% data variables.product.prodname_mobile %}](https://github.com/features/) beta allows you to triage notifications and manage issues and pull requests from your device. You can be simultaneously signed into mobile with one user account on {% data variables.product.prodname_dotcom_the_website %} and one user account on {% data variables.product.prodname_ghe_server %}. - - {% data variables.product.prodname_mobile %} beta is now available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. - - - heading: Advanced Security Secret Scanning beta - notes: - - | - [Secret Scanning beta](https://github.com/features/security) scans public and private repositories for committed credentials, finds secrets, and notifies the secret provider or admin the moment they are committed into a repository. - - Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. - - - heading: Advanced Security Code Scanning - notes: - - | - [GitHub Advanced Security code scanning](https://github.com/features/security) is now generally available on GitHub Enterprise Server. Organizations who have purchased Advanced Security can use this capability to do static analysis security testing against their code, and prevent vulnerabilities from making it to their production code using CodeQL, our semantic analysis engine. For more information, see "[Configuring code scanning on your appliance](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" - changes: - - - heading: Cambios en la administración - notes: - - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. It also uses less CPU and memory in {% data variables.product.prodname_ghe_server %} 3.0+. - - Organization and Enterprise owners can now see when a team member has been promoted to or demoted from being a team maintainer in the audit log through the new `team.promote_maintainer` and `team.demote_maintainer` audit log events. For more information, see "[Audited actions](/enterprise-server@3.0/admin/user-management/audited-actions)." - - 'Repository maintainers with existing {% data variables.product.prodname_pages %} sites can [easily update their prior default branch name](/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 infomation 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)." - - Administrators can now [publish a message](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), which all users must accept. This can help to onboard new users and surface other organization-specific information and policies. - - - heading: Cambios de seguridad - notes: - - Organization owners can now disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization. Disabling {% data variables.product.prodname_pages %} for the organization will prevent members from creating new Pages sites but will not unpublish existing sites. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." - - A datacenter must be explicitly defined on all nodes before enabling an active replica. - - All usage of SSH fingerprints has been switched to use SHA256 fingerprints as they are used with OpenSSH since version 6.8 as well. This applies to the web interface and also the API where fingerprints are returned such as in GraphQL. The fingerprints follow the OpenSSH format. - - SHA-1 and SHA-256 signature headers (two headers) are sent on webhooks. - - - heading: Cambios de desarrollador - notes: - - Majority of the services running in {% data variables.product.prodname_ghe_server %} 3.0+ are now on containers which internally enables GitHub to iterate fast and ship high quality releases - - The webhook events delivery system has been rearchitected for higher throughput, faster deliveries, and fewer delayed messages. - - - heading: Cambios a la API - notes: - - 'Administrators can now configure and manage the site-wide announcement banner via the REST API. For more information, see the endpoints for "[GitHub Enterprise administration](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)."' - - - heading: Default branch renaming - notes: - - | - Enterprise and organization administrators can now set the default branch name for new repositories. Enterprise administrators can also enforce their choice of default branch name across all organizations or allow individual organizations to choose their own. - - Existing repositories are unaffected by these settings, and their default branch name will not be changed. - - {% note %} - - The default branch for newly-created repositories will be set to `main` in GHES 3.1, unless you opt out by setting the default branch setting at the enterprise level. - - {% endnote %} - - This change is one of many changes GitHub is making to support projects and maintainers that want to rename their default branch. To learn more about the changes we're making, see [github/renaming](https://github.com/github/renaming). - bugs: - - The format of several log files have changed, including the addition of a PID for different log types. This does not affect how GitHub Enterprise Support uses support bundles to troubleshoot issues. - - A PATCH request to the webhook configuration API no longer erases the webhook secret. - deprecations: - - - heading: Deprecation of GitHub Enterprise Server 2.19 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.19 is deprecated as of November 12, 2020**. 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 %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) as soon as possible.' - - - heading: Obsoletización de los Eventos de Webhook tradicionales de las GitHub Apps - notes: - - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 two legacy GitHub Apps-related webhook events have been deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. The deprecated events `integration_installation` and `integration_installation_repositories` have equivalent events which will be supported. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/). - - - heading: Obsoletización de la terminal tradicional para las GitHub Apps - notes: - - Starting with {% data variables.product.prodname_ghe_server %} 2.21.0 the legacy GitHub Apps endpoint for creating installation access tokens was deprecated and will be removed in {% data variables.product.prodname_ghe_server %} 3.2.0. More information is available in the [deprecation announcement blog post](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). - - - heading: Obsoletización de la API de aplicaciones OAuth - notes: - - GitHub no longer supports the OAuth application endpoints that contain `access_token` as a path parameter. We have introduced new endpoints that allow you to securely manage tokens for OAuth Apps by moving `access_token` to the request body. While deprecated, the endpoints are still accessible in this version. We intend to remove these endpoints on {% data variables.product.prodname_ghe_server %} 3.4. For more information, see the [deprecation announcement blog post](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/). - - - heading: Deprecation of support for Semiotic - notes: - - The service supported a "Find by Symbol" experience in the pull request view that was not widely used. - - - heading: Deprecation of workflow commands - notes: - - '{% data variables.product.prodname_actions %} `set-env` and `add-path` workflow commands have been deprecated. For more information, see the [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' - known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. - - Release Candidate 1 does not support Cluster mode. - - Custom firewall rules are not maintained during an upgrade. - - Git LFS tracked files [uploaded through the web interface](https://github.blog/2016-02-18-upload-files-to-your-repositories/) are incorrectly added directly to the repository. - - 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. - - Following an unsuccessful attempt to set up Actions, if you then disable Actions you will not be able to create the first user and use the appliance - - The "Mandatory message viewed" audit log event is not being saved - - '`ghe-config-apply` must be run on a replica during first setup before `ghe-repl-setup` can be run to start replication.' - - Backup-utils can trigger unnecessary emails to administrators - - Incorrect Packages settings are being displayed in the Organization member view page - - After removing oneself as an Enterprise Owner, you are redirected to a 404 page. The operation is successful. - - '`ghe-config-apply` occassionally 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`.' - - When configuring a multiple replica node, the status of the replica can be incorrectly synchronized. - - Customers attempting to restore a 3.0 backup to a new instance should not pre-configure the instance, as it may lead to a bad state for user logins. We recommend restoring to a fresh, unconfigured instance. - - GitHub Enterprise Server 3.0 release candidates are not yet available in the Azure marketplace. To test RC1 in staging environments, start a 2.21 or 2.22 instance, and then upgrade it with the Azure upgrade package on the download page. - backups: - - '{% data variables.product.prodname_ghe_server %} 3.0 requires at least [GitHub Enterprise Backup Utilities 3.0.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/release-notes/3-0/0-rc1.yml b/translations/es-ES/data/release-notes/3-0/0-rc1.yml deleted file mode 100644 index 195723393e..0000000000 --- a/translations/es-ES/data/release-notes/3-0/0-rc1.yml +++ /dev/null @@ -1,26 +0,0 @@ ---- -date: '2021-01-12' -release_candidate: true -deprecated: true -intro: Las versiones candidatas a lanzamiento deben probarse en ambientes no productivos. Para obtener más información acerca del Programa de Candidatos a Lanzamiento, consulta el [Blog de GitHub](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) o la sección "[Acerca de las mejoras a lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)". -sections: - bugs: - - El formato de varios archivos de bitácora ha cambiado, incluyendo la adición de un PID para los tipos de bitácora diferentes. Esto no afecta cómo GitHub Enterprise Support utiliza paquetes de soporte para la solución de problemas. - - El hacer una solicitud de PATCH a la API de configuración de webhooks ya no borra el secreto del webhook. - 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. - - El candidato de lanzamiento 1 no es compatible con el modo de agrupamiento. - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.blog/2016-02-18-upload-files-to-your-repositories/) se agregaron incorrecta y directamente al repositorio. - - 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. - - Tras un intento no exitoso de configurar las acciones, si las inhabilitas después, no podrás crear el primer usuario ni utilizar el aplicativo - - El evento de bitácora de auditoría de "Mensaje obligatorio visto" no se está guardando - - 'Se debe ejecutar a `ghe-config-apply` en una réplica durante la primera configuración antes de que se pueda ejecutar `ghe-repl-setup` para iniciar la replicación.' - - 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` falla ocasionalmente con un mensaje de `ERROR: Failure waiting for nomad jobs to apply` hasta que la cola de jobs nómadas se vacíe. Actualmente, esto requiere que una administrador borre el `/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. - - El tamaño de descarga de la imagen y del paquete de mejoras aumentó. Los clientes con conexiones de internet lentas podrían encontrar que los paquetes tardan más en descargarse. diff --git a/translations/es-ES/data/release-notes/3-0/0-rc2.yml b/translations/es-ES/data/release-notes/3-0/0-rc2.yml deleted file mode 100644 index 65aaa0cb61..0000000000 --- a/translations/es-ES/data/release-notes/3-0/0-rc2.yml +++ /dev/null @@ -1,26 +0,0 @@ ---- -date: '2021-01-29' -release_candidate: true -deprecated: true -intro: Las versiones candidatas a lanzamiento deben probarse en ambientes no productivos. Para obtener más información acerca del Programa de Candidatos a Lanzamiento, consulta el [Blog de GitHub](https://github.blog/2020-12-03-improving-the-ghes-release-process-release-candidates/) o la sección "[Acerca de las mejoras a lanzamientos nuevos](/admin/overview/about-upgrades-to-new-releases)." -sections: - bugs: - - - heading: Correcciones para las propuestas conocidas del Candidato a Lanzamiento 1 - notes: - - Si inhabilitas las GitHub Actions seguido de un intento fallido de configurarlas, entonces no podrás crear el primer usuario y utilizar el aplicativo. - - El evento de bitácora de auditoría de "Mensaje obligatorio visto" no se estaba guardando. - - '`ghe-config-apply` necesitaba ejecutarse en una réplica durante una configuración inicial antes de que `ghe-repl-setup` pudiera ejecutarse para iniciar la replicación.' - - El haberte eliminado como propietario empresarial devolvió un 404. - - - heading: Correcciones para otros problemas - notes: - - Los problemas con las migraciones y mejoras a la versión 3.0.0 se arreglaron. - - El versionamiento de utilidades de respaldo ahora funciona para las versiones de candidatos de lanzamiento. - - El generar un paquete de soporte dio como resultado un error en las bitácoras del orquestador. - - Un restablecimiento grande pudo haber dado como resultado que Redis se quedara sin memoria. - - La casilla de verificación para habilitar las GitHub Actions en la consola de administración ahora se puede ver con cualquier método de autenticación. - - Las gitHub Actions solo pueden habilitarse si también se configuró el almacenamiento requerido. - - '`ghe-repl-status` podría fallar silenciosamente si no está configurada la replicación de MSSQL.' - known_issues: - - Los problemas conocidos del Candidato a Lanzamiento 1 aún aplican, excluyendo las correcciones de errores listadas. diff --git a/translations/es-ES/data/release-notes/3-0/0.yml b/translations/es-ES/data/release-notes/3-0/0.yml deleted file mode 100644 index 6bf78ea67d..0000000000 --- a/translations/es-ES/data/release-notes/3-0/0.yml +++ /dev/null @@ -1,145 +0,0 @@ -date: '2021-02-16' -intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".' -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en {% data variables.product.prodname_ghe_server %} que podría aprovecharse al compilar un sitio de {% data variables.product.prodname_pages %}. La configuración controlada por el usuario de los analizadores subyacentes que utiliza {% data variables.product.prodname_pages %} no se restringió lo suficiente y permitió que se ejecutaran comandos en la instancia de {% data variables.product.prodname_ghe_server %}. Para aprovechar 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 %}. A esta vulnerabilidad se le asignó un CVE-2020-10519 y se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - features: - - heading: GitHub Actions - notes: - - | - [{% data variables.product.prodname_actions %}](https://github.com/features/actions) ahora se encuentra comunmente disponible en {% data variables.product.prodname_ghe_server %} 3.0+. Crea, prueba y despliega tu código desde {% data variables.product.prodname_dotcom %}. Emite revisiones de código, administración de ramas y el trabajo de clasificación de propuestas como quieras. - - Este lanzamiento incluye varias mejoras del beta para {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}: - - - Los administradores de las empresas, organizaciones y repositorios pueden crear políticas de seguridad para acceder a {% data variables.product.prodname_actions %} en {% data variables.product.prodname_dotcom_the_website %}. - - Los administradores de las empresas, organizaciones y repositorios pueden permitir que los repositorios públicos utilicen ejecutores auto-hospedados. - - Los administradores de las empresas, organizaciones y repositorios ahora pueden permitir que los flujos de trabajo [se ejecuten en las solicitudes de cambio que se levantan desde las bifurcaciones o desde los repositorios privados](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks). - - El evento de `workflow_run` [ahora es compatible](/enterprise-server@3.0/actions/reference/events-that-trigger-workflows#workflow_run) - - Los usuarios ahora tienen la capacidad de [inhabilitar los flujos de trabajo y habilitarlos en una fecha posterior](/enterprise-server@3.0/actions/managing-workflow-runs/disabling-and-enabling-a-workflow). - - Las bitácoras de flujo de trabajo se mejoraron para que tengas una [experiencia de usuario mejor](/enterprise-server@3.0/actions/managing-workflow-runs/using-workflow-run-logs). - - Los usuarios ahora pueden utilizar imágenes privadas en los servicios y contenedores de los jobs. - - El máximo de días de retención para [los artefactos y las bitácoras ahora puede personalizarse](/enterprise-server@3.0/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account). - - La API del grupo de ejecutores ahora incluye [labels](/enterprise-server@3.0/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners). - - Ahora puedes crear acciones reutilizables que utilicen scripts de shell con pasos de ejecución compuestos. - - Los [Secretos cifrados para las organizaciones](/enterprise-server@3.0/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization) te permiten consolidar los secretos a través de los repositorios. - - Las [Plantillas de flujo de trabajo para las organizaciones](/enterprise-server@3.0/actions/learn-github-actions/sharing-workflows-with-your-organization) simplifican y promueven las mejores prácticas y la consistencia a lo largo de tu organización. - - Las {% data variables.product.prodname_actions %} no son actualmente compatibles para las empresas que utilizan configuraciones de agrupamiento. - - heading: Registro del paquete de GitHub - notes: - - | - El [{% data variables.product.prodname_registry %}](https://github.com/features/packages) es un servicio de hospedaje de paquetes que se integra nativamente con las API, acciones y webhooks de GitHub. Crea un [flujo de trabajo de DevOps de extremo a extremo](/enterprise/3.0/admin/packages/configuring-packages-support-for-your-enterprise) que incluye soluciones para tu código, la integración contínua y el despliegue. - - Las soluciones administrativas para almacenamiento que son compatibles incluyen a AWS S3 y a MinIO con compatibilidad para Azure blob en un lanzamiento subsecuente. Por favor, toma en cuenta que la compatibilidad actual con Docker se reemplazará con un beta del nuevo Registro de Contenedores de GitHub en el siguiente lanzamiento. Por favor, revisa los [requisitos mínimos actualizados para tu plataforma](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) antes de que habilites el {% data variables.product.prodname_registry %}. - - Cuando publicas paquetes en NuGet, los usuarios ahora pueden utilizar la opción `--api-key` para pasar su token de autenticación en vez de escribirlo en un archivo. Para obtener más información, consulta la sección [Configurar el CLI de dotnet para utilizarlo con GitHub Packages](/enterprise-server@3.0/packages/guides/configuring-dotnet-cli-for-use-with-github-packages#publishing-a-package) - - Actualmente, el {% data variables.product.prodname_registry %} no es compatible para las empresas que utilizan configuraciones de agrupamiento. - - heading: GitHub Mobile beta - notes: - - | - El beta de [{% data variables.product.prodname_mobile %}](https://github.com/features/) te permite clasificar las notificaciones y administrar las propuestas y solicitudes de cambio desde tu dispositivo. Puedes firmarte simultáneamente en la aplicación móvil con una cuenta de usuario de {% data variables.product.prodname_dotcom_the_website %} y con una de {% data variables.product.prodname_ghe_server %}. - - El beta de {% data variables.product.prodname_mobile %} ahora se encuentra disponible para {% data variables.product.prodname_ghe_server %}. Ingresa con nuestras apps de [Android](https://play.google.com/store/apps/details?id=com.github.android) y de [iOS](https://apps.apple.com/app/github/id1477376905) para clasificar las notificaciones y adminsitrar las propuestas y solicitudes de cambio al vuelo. Los administradores pueden inhabilitar la compatibilidad con la versión móvil para su empresa si utilizan la consola de administración o si ejecutan `ghe-config app.mobile.enabled false`. - - heading: Escaneo de Secretos de Advanced Security beta - notes: - - | - El [Escaneo de Secretos beta](https://github.com/features/security) escanea los repositorios públicos y privados para las credenciales confirmadas, encuentra secretos, y notifica al proveedor de secretos o al administrador en el momento en el que éstos se confirman en un repositorio. - - Los administradores que utilizan la {% data variables.product.prodname_GH_advanced_security %} pueden [habilitar y configurar](/enterprise-server@3.0/admin/configuration/configuring-secret-scanning-for-your-appliance) el escaneo de secretos de {% data variables.product.prodname_GH_advanced_security %}. Puedes revisar los [requisitos mínimos actualizados para tu plataforma](/enterprise/3.0/admin/installation/setting-up-a-github-enterprise-server-instance) antes de habilitar el escaneo de secretos de {% data variables.product.prodname_GH_advanced_security %}. - - heading: Escaneo de Código de Advanced Security - notes: - - | - [El escaneo de código de GitHub Advanced Security](https://github.com/features/security) ahora está comunmente disponible en GitHub Enterprise Server. Las organizaciones que hayan comprado Advanced Security pueden utilizar esta característica para realizar pruebas de seguridad de análisis estático contra su código y pueden prevenir que las vulnerabilidades lleguen a su código productivo utilizando CodeQL, nuestro motor de análisis semántico. Para obtener más información, consulta la sección "[Configurar el escaneo de código en tu aplicativo](/en/enterprise-server@3.0/admin/configuration/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)" - changes: - - heading: Cambios en la administración - notes: - - '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).' - - 'Se requiere de recursos adicionales de hardware para ejecutar {% data variables.product.prodname_ghe_server %} que tenga habilitadas acciones, paquetes o seguridad avanzada. Para obtener más información sobre los recursos mínimos requeridos para cada plataforma de soporte, 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: - - 'Los propietarios de las organizaciones ahora pueden inhabilitar la publicación de sitios de {% data variables.product.prodname_pages %} de los repositorios de la organización. El inhabilitar a {% data variables.product.prodname_pages %} para la organización impedirá que los miembros creen páginas nuevas pero no dejará de publicar los sitios existentes. Para obtener más información, consulta la sección "[Inhabilitar la publicación de los sitios de {% data variables.product.prodname_pages %} para tu organización](/enterprise-server@3.0/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)".' - - Se debe definir explícitamente un centro de datos en todos los nodos antes de habilitar una réplica activa. - - 'Todo uso de huellas dactilares de SSH se ha cambiado para utilizar huellas dactilares SHA256 como también se utilizan con OpenSSH desde la versión 6.8. Esto aplica a la interface web y también a la API en donde las huellas dactilares se devuelven, tal como en GraphQL. Las huellas dactilares siguen el formato de OpenSSH.' - - Los encabezados de firma SHA-1 y SHA-256 (dos encabezados) se envían en webhooks. - - heading: Cambios de desarrollador - notes: - - 'La mayoría de los servicios que se ejecutan en {% data variables.product.prodname_ghe_server %} 3.0+ ahora se encuentran en contenedores que habilitan internamente a GitHub para iterar rapido y para enviar lanzamientos de alta calidad' - - 'El sistema de entrega de eventos de webhook renovó su arquitectura para tener un rendimiento mayor, entregas más rápidas y menos retrasos en los mensajes.' - - heading: Cambios a la API - notes: - - 'Los administradores ahora pueden configurar y administrar el letrero de anuncio de todo el sitio a través de la API de REST. Para obtener más información, consulta las terminales de "[administración de GitHub Enterprise](/enterprise-server@3.0/rest/reference/enterprise-admin#annoucements)".' - - 'Una nueva terminal de la API permite el intercambio de un token de usuario a servidor para aquellos que tengan alcance de los repositorios específicos. Para obtener más información, consulta las "[Apps](/enterprise-server@3.0/rest/reference/apps#create-a-scoped-access-token)" en la documentación de la API de REST de {% data variables.product.prodname_dotcom %}.' - - heading: Renombrar la rama predeterminada - notes: - - | - Los administradores de organizaciones y empresas ahora pueden configurar el nombre de la rama predeterminada para los repositorios nuevos. Los administradores de empresas también pueden hacer cumplir su elección de nombre de rama predeterminada a través de todas las organizaciones para permitir que cada una de ellas elija su propio nombre. - - Los repositorios existentes no se verán afectados por esta configuración y el nombre de sus ramas predeterminadas no cambiará. - - {% note %} - - La rama predeterminada para los repositorios recién creados se configurará como `main` en GHES 3.1, a menos de que decidas configurar los ajustes de rama predeterminada a nivel empresarial. - - {% endnote %} - - Este cambio es uno de los muchos que GitHub está realizando para apoyar a los proyectos y mantenedores que quieren renombrar su rama predeterminada. Para aprender más sobre los cambios que estamos haciendo, consulta la sección [github/renaming](https://github.com/github/renaming). - bugs: - - heading: Correcciones para los problemas conocidos de los Candidatos a Lanzamiento - notes: - - 'Todos los problemas que se conocen del Candidato a Lanzamiento 1 y 2 se han corregido, con excepción de las que se listan en la siguiente sección de problemas conocidos.' - - heading: Correcciones para otros problemas - notes: - - Los problemas con las migraciones y mejoras a la versión 3.0.0 se arreglaron. - - El versionamiento de utilidades de respaldo ahora funciona para las versiones de candidatos de lanzamiento. - - El generar un paquete de soporte dio como resultado un error en las bitácoras del orquestador. - - Un restablecimiento grande pudo haber dado como resultado que Redis se quedara sin memoria. - - La casilla de verificación para habilitar las GitHub Actions en la consola de administración ahora se puede ver con cualquier método de autenticación. - - Las GitHub Actions podrían estar habilitadas si también se configuró el almacenamiento necesario. - - '`ghe-repl-status` podría fallar silenciosamente si no se configuró la replicación de MSSQL.' - - 'El formato de varios archivos de bitácora ha cambiado, incluyendo la adición de un PID para los tipos de bitácora diferentes. Esto no afecta cómo GitHub Enterprise Support utiliza paquetes de soporte para la solución de problemas.' - - El hacer una solicitud de PATCH a la API de configuración de webhooks ya no borra el secreto del webhook. - - Algunos tipos de ganchos de pre-recepción estaban fallando. - - 'El servicio de Paquetes NuGet ahora normaliza las versiones semánticas al publicar. Los clientes de NuGet no pueden descargar una versión semántica inválida (por ejemplo: v1.0.0.0.0.0) y, por lo tanto, se espera que un servicio de NuGet normalice esas versiones (por ejemplo: v1.0.0.0.0.0 --> v1.0.0). Cualquier versión original sin normalizar estará disponible en el campo `verbatimVersion`. No se requiere de ningún cambio a las configuraciones del cliente.' - 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 personalizadas del cortafuegos no se mantienen durante una mejora. - - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.blog/2016-02-18-upload-files-to-your-repositories/) se agregaron incorrecta y directamente al repositorio.' - - '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 se habilita el modo de mantenimiento, algunos servicios siguen listándose como "procesos activos". Se espera que los servicios que se identificaron se ejecuten durante el modo de mantenimiento. Si estás experimentando este problema y no sabes cómo proceder, contacta a {% data variables.contact.contact_ent_support %}.' - - 'Cuando habilitas las GitHub Actions, utiliza ''`ghe-maintenance -u`'' para dejar de configurar el modo de mantenimiento.' - - '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.' - - 'Las [llaves de despliegue] de repositorio(/developers/overview/managing-deploy-keys) no pueden utilizarse con repositorios que contengan objetos LFS.' - - 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. - - 'La gráfica de dependencias falla en interpretar los archivos de manifiesto de Python `setup.py`, lo cual resultó en errores HTTP 500 en las bitácoras. Esto, en combinación con el problema de bitácoras duplicadas, dio como resultado un incremento en la utilización del volúmen raíz.' - - Una condición de carrera puede causar que las migraciones de la base de datos de la dependencia parezcan fallar. - - Las instancias con la zona horaria personalizada que se mejoraron desde un lanzamiento anterior de GitHub Enterprise Server podrían tener marcas de tiempo incorrectas en la IU web. - - '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.' - deprecations: - - heading: Obsoletización de GitHub Enterprise Server 2.19 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.19 se encontrará obsoletizado desde el 12 de noviembre de 2020**. Eso significa que no se harán lanzamientos de parches, ni siquiera para los problemas críticos de seguridad, después de esta fecha. Para obtener un rendimiento mejor, mejorar la seguridad y tener nuevas características, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](https://help.github.com/enterprise/admin/guides/installation/upgrading-github-enterprise/) tan pronto como te sea posible.' - - heading: Obsoletización de los Eventos de Webhook tradicionales de las GitHub Apps - notes: - - 'Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, dos eventos de webhook relacionados con GitHub Apps se obsoletizaron y eliminaron en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Los eventos obsoletizados de `integration_installation` and `integration_installation_repositories` tienen eventos equivalentes que serán compatibles. Puedes encontrar más información en la [publicación del blog acerca de los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).' - - heading: Obsoletización de la terminal tradicional para las GitHub Apps - notes: - - 'Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, la terminal tradicional de GitHub Apps para crear tokens de acceso a las instalaciones se obsoletizó y se eliminará en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Puedes encontrar más información disponible en la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/).' - - heading: Obsoletización de la API de aplicaciones OAuth - notes: - - 'GitHub ya no es compatible con las terminales de la aplicación de OAuth que contengan `access_token` como parámetro de ruta. Hemos incluído terminales nuevas que te permiten administrar los tokens para las apps de OAuth de forma segura al mover a `access_token` al cuerpo de solicitud. Aunque se hayan obsoletizado, aún se puede acceder a las terminales en esta versión. Intentamos eliminar estas terminales en la versión 3.4 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).' - - heading: Obsoletización de compatibilidad con Semiotic - notes: - - El servicio era compatible con una experiencia de "Encontrar por símbolo" en la vista de solicitud de cambios que no se utilizaba ampliamente. - - heading: Obsoletización de los comandos de flujo de trabajo - notes: - - 'Los comandos de flujo de trabajo de `set-env` y `add-path` de {% data variables.product.prodname_actions %} se obsoletizaron. Para obtener más información, consulta el [changelog](https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/).' - backups: - - '{% data variables.product.prodname_ghe_server %} 3.0 requiere por lo menos de una versión [3.0.0 de las Utilidades de Respaldo de GitHub Enterprise](https://github.com/github/backup-utils) para los [Respaldos y la Recuperación de Desastres](/enterprise-server@3.0/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/release-notes/3-0/1.yml b/translations/es-ES/data/release-notes/3-0/1.yml deleted file mode 100644 index 9857ee8d70..0000000000 --- a/translations/es-ES/data/release-notes/3-0/1.yml +++ /dev/null @@ -1,70 +0,0 @@ ---- -date: '2021-03-02' -intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".' -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de control de acceso incorrecto en GitHub Enterprise Server, la cual permitió a un usuario no autenticado de la instancia obtener acceso a los repositorios no autorizados a través de solicitudes de cambios y solicitudes a través de la API de REST configuradas específicamente. El atacante necesitaría poder bifurcar el repositorio de destino, dicha configuración está inhabilitada predeterminadamente para los repositorios privados y para los que pertenecen a una organización. Las protecciones de rama tales como las solicitudes de cambio o verificaciones de estado requeridas prevendrían que las confirmaciones no autorizadas se fusionen sin haber obtenido una revisión o validación adicionales. Se ha asignado un CVE-2021-22861 a esta vulnerabilidad. El problema se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - '**ALTA:** Se identificó una vulnerabilidad de control de acceso incorrecto en la API de GraphQL de GitHub Enterprise Server, la cual permitió a los usuarios autenticados de la instancia modificar el permiso de colaboración del mantenedor para una solicitud de cambios sin una autorización adecuada. Al aprovechar esta vulnerabilidad, el atacante pudo obtener acceso a las ramas de encabezado de las solicitudes de cambios que se abrieron en los repositorios donde ellos eran los mantenedores. La bifurcación se inhabilitó predeterminadamente para los repositorios privados que pertenecían a alguna organización, lo cual previno esta vulnerabilidad. Adicionalmente, las protecciones de rama tales como las revisiones requeridas para la solicitud de cambios o las verificaciones de estado prevendrían que las confirmaciones no autorizadas se fusionen sin contar con una validación o revisión subsecuente. Se asignó un CVE-2021-22863 a esta vulnerabilidad. Este problema se reportó a través del [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - '**ALTA:** Se identificó una vulnerabilidad de control de accesos inadecuado en GitHub Enterprise Server, la cual permitió que un usuario autenticado con la capacidad de bifurcar un repositorio divulgara los secretos de las acciones para el repositorio padre de la bifurcación. Esta vulnerabilidad existió debido a una falla que permitió que la referencia base de una solicitud de cambios se actualizara al punto de un SHA arbitrario o de otra solicitud de cambios fuera del repositorio de la bifurcación. Al establecer esta referencia incorrecta en una PR, las restricciones que limitan los secretos de las acciones y que envían un flujo de trabajo desde las bifurcaciones pudieron haberse omitido. Esta vulnerabilidad afectó las versiones de GitHub Enterprise Server 3.0.0, 3.0.0.rc2, y 3.0.0.rc1 y se le asignó un CVE-2021-22862. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub.' - - '**MEDIA:** Los GitHub tokens de las compilaciones de GitHub Pages pudieron haber terminado en las bitácoras.' - - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' - bugs: - - 'Las verificaciones de salud del balanceador de carga pudieron haber causado en algunos casos que los logs de babel se llenaran con errores sobre el protocolo del PROXY.' - - 'Los encabezados HTTP no cumplían con los estándares de HTTP RFC en respuestas específicas como el estado 304 para los archivos.' - - 'En las instancias que hospedan repositorios de Python y que cuentan con la Gráfica de Dependencias habilitada, la instancia pudo haberse quedado sin repsuesta debido a que el disco raíz se llenó con bitácoras de error.' - - 'Un mensaje informativo se registro involuntariamente como un error durante las capturas de pantalla de las Utilidades de Respaldo de GitHub Enterprise, lo cual dio como resultado que se enviaran correos electrónicos innecesarios cuando los jobs de cron programaron los respaldos que escuchaban a la salida a stderr.' - - 'En VMWare ESX 6.7, la configuración inicial pudo haberse colgado mientras se creaban las claves del host, lo cual dejó a la instancia inaccesible a través de SSH.' - - 'Cuando se habilitó GitHub Actions, el inhabilitar el modo de mantenimiento en la consola de administración, falló.' - - 'El ajuste de creación de paquetes se mostró en la página de ajustes del miembro de la organización, aunque esta característica aún no está disponible.' - - 'Al habilitar el escaneo de secretos en la página de Seguridad y Análisis, el diálogo mencionó los repositorios privados incorrectamente.' - - 'El editar una página de wiki, un usuario pudo haber experimentado un error 500 al hacer clic en el botón de guardar.' - - 'Una confirmación firmada con S/MIME utilizando un certificado con nombres múltiples en el nombre alternativo de asunto se mostró incorrectamente como "No verificado" en la insignia de confirmación.' - - 'Un usuario vio un error 500 al ejecutar operaciones de git en una instancia configurada con autenticación LDAP.' - - 'Se enviaron correos electrónicos a un usuario suspendido cuando se le agregó a un equipo.' - - 'Cuando un repositorio tuvo una gran cantidad de manifiestos se mostró un error de `You have reached the maximum number of allowed manifest files (20) for this repository.` en la pestaña ubicada en Perspectivas -> Gráfica de dependencias. Para obtener más información, consulta la sección [Límites de visualización] (https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data).' - - 'Corrige que se muestren los usuarios en la opción para configurar la acción de CodeQL del Escaneo de Código, incluso si no se habilitaron las acciones para el repositorio.' - - 'La casilla de verificación de "Prevent repository admins from changing anonymous Git read access" disponible en la configuración de cuenta empresarial no se pudo habilitar o inhabilitar con éxito.' - - 'El modal que se utilizó para mostrar un mensaje obligatorio no contenía una barra de desplazamiento vertical, lo cual significa que los mensajes más largos no se pudieron ver por completo.' - - 'Redis a veces fallaba en iniciar después de un reinicio físico o fallo de aplicación.' - - 'La gráfica de dependencias falla en interpretar los archivos de manifiesto de Python `setup.py`, lo cual resultó en errores HTTP 500 en las bitácoras. Esto, en combinación con el problema de bitácoras duplicadas, dio como resultado un incremento en la utilización del volúmen raíz.' - changes: - - 'Se satisficieron solicitudes de forma concurrente cuando usuarios múltiples estaban descargando el mismo archvio, lo cual dio como resultado un rendimiento mejorado.' - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - 'Las reglas personalizadas del cortafuegos no se mantienen durante una mejora.' - - '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.' - - 'Cuando se habilita el modo de mantenimiento, algunos servicios siguen listándose 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 proceder, contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/).' - - '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.' - - 'Las [llaves de despliegue] de repositorio(/developers/overview/managing-deploy-keys) no pueden utilizarse con repositorios que contengan objetos LFS.' - - 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.' - - 'La gráfica de dependencias falla en analizar los archivos del manifiesto de Javascript `yarn.lock`, lo cual da como resultado errores 500 de HTTP en las bitácoras.' - - 'Las instancias con la zona horaria personalizada que se mejoraron desde un lanzamiento anterior de GitHub Enterprise Server podrían tener marcas de tiempo incorrectas en la IU web.' - - '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.' - - | - Los usuarios podrían experimentar que los activos tales como los avatares no carguen, o que hayan fallos en el código de subida/extracción. Esto podría darse por un desajuste de PID en el servicio `haproxy-cluster-proxy`. Para determinar si tienes una instancia afectada: - - **Instancia única** - - 1. Ejecuta lo siguiente en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. Si muestra que hay un desajuste, reinicia la instancia. - - **Configuración en Clúster o en Disponibilidad Alta** - - 1. Ejecuta lo siguiente en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. Si muestra que uno o más nodos están afectados, reinícialos. diff --git a/translations/es-ES/data/release-notes/3-0/2.yml b/translations/es-ES/data/release-notes/3-0/2.yml deleted file mode 100644 index ec47977ed8..0000000000 --- a/translations/es-ES/data/release-notes/3-0/2.yml +++ /dev/null @@ -1,56 +0,0 @@ ---- -date: '2021-03-16' -intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - 'Al intentar hacer un respaldo, ocurrió un error que indica "Warning: One or more storage objects were not found on the source appliance." al intentar limpiar los objetos de almacenamiento purgables.' - - La gráfica de dependencias falló en interpretar los archivos de manifiesto de JavaScript `yarn.lock, lo cual dio como resultado errores 500 de HTTP en las bitácoras. - - El inhabilitar las GitHub Actions fallará algunas veces. - - Los ganchos de pre-recepción personalizados no tenían permiso de escribir en `/tmp`, previniendo que algunos scripts se ejecutaran correctamente. - - Las bitácoras de los diarios de Systemd se duplicaron en varios lugares. - - Una zona horaria que se configuró en GitHub Enterprise 11.10.x o anterior se restableció a una hora UTC después de actualizarse a la versión 3.0, lo cual causió que las marcas de tiempo se movieran en algunas instancias. - - El hacer clic en "Publicar tu primer paquete" en la barra lateral de los paquetes en un repositorio dirigió a una página en blanco. - - Un adminsitrador de sitio podría obtener un error de página 500 al intentar ver las propuestas que se referenciaban de repositorios privados. - - Después de inhabilitar GitHub packages, algunas páginas de la organización regresaban una respuesta de error HTTP 500. - - El importar repositorios archivados desde GitHub Enterprise Server a los cuales les faltan archivos de repositorio, fallará con un error. - - No se pudieron utilizar las [llaves de despliegue](/developers/overview/managing-deploy-keys) del repositorio con aquellos repositorios que contenían objetos LFS. - - En la barra lateral de paquetes de un repositorio, el icono de Docker se mostraba en gris y un mensaje emergente mostraba la leyenda "Este servicio está obsoletizado". - - Los webhooks configurados con un tipo de contenido `application/x-www-form-urlencoded` no recibieron parámetros de consulta en el cuerpo de la solicitud POST. - - Los usuarios pudieron descartar un mensaje obligatorio sin verificar todas las casillas. - - En algunos casos, después de actualizar a una instancia 2.22.X, los activo de la interface web se perdieron y la página no se interpretó correctamente. - - Pudo haberse agotado el tiempo al ejecutar `ghe-config-apply` con un error de tipo `Failure waiting for nomad jobs to apply` due to `'job' stanza not found`. - known_issues: - - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - 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. - - Cuando se habilita el modo de mantenimiento, algunos servicios siguen listándose 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 proceder, contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/). - - 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/`). - - 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. - - | - Los usuarios podrían experimentar que los activos tales como los avatares no carguen, o que hayan fallos en el código de subida/extracción. Esto podría darse por un desajuste de PID en el servicio `haproxy-cluster-proxy`. Para determinar si tienes una instancia afectada: - - **Instancia única** - - 1. Ejecuta lo siguiente en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi - ``` - - 2. Si muestra que hay un desajuste, reinicia la instancia. - - **Configuración en Clúster o en Disponibilidad Alta** - - 1. Ejecuta lo siguiente en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH): - - ``` - ghe-cluster-each -- 'if [ $(cat /var/run/haproxy-cluster-proxy.pid) -ne $(systemctl show --property MainPID --value haproxy-cluster-proxy) ]; then echo 'Main PID of haproxy-cluster-proxy does not match /var/run/haproxy-cluster-proxy.pid'; fi' - ``` - - 2. Si muestra que uno o más nodos están afectados, reinícialos. diff --git a/translations/es-ES/data/release-notes/3-0/3.yml b/translations/es-ES/data/release-notes/3-0/3.yml deleted file mode 100644 index d7b0fb4ea2..0000000000 --- a/translations/es-ES/data/release-notes/3-0/3.yml +++ /dev/null @@ -1,43 +0,0 @@ ---- -date: '2021-03-23' -intro: Se han desactivado las descargas debido a un error importante que afectó a varios clientes. Pronto tendremos una solución en el siguiente parche. -sections: - security_fixes: - - '**ALTA:** Se identificó una vulnerabilidad de ejecución de código remoto en GitHub Enterprise Server, la cual pudo haberse aprovechado al crear un sitio de GitHub Pages. Las opciones de configuración controladas por el usuario que utilizan las GitHub Pages no se restringieron lo suficiente e hicieron posible que se ignoraran las variables de ambiente que llevaron a la ejecución de código en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, un atacante necesitaría permisos 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 antes de la 3.0.3 y se arregló en la 3.0.3, 2.22.9, y 2.21.17. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub y se le asignó un CVE-2021-22864.' - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - El ejecutar `ghe-cluster-config-init` pudo haber causado que un clúster fuera inoperable. - - El resolver conflictos de fusión en la GUI fallaba cuando los ganchos de pre-recepción personalizados se configuraban en el repositorio. - - '`launch-deployer` y `launch-receiver` se estaban registrando al nivel de DEBUG y llenaban las bitácoras con información innecesaria.' - - El sistema pudo haber perdido el rastreo del PID de HAProxy. - - Cuando se configuraron las acciones para utilizar un almacenamiento de S3, las bitácoras para una acción fallaban en cargarse algunas veces. - - La advertencia de la recuperación de fallos de mysql se mostró indefinidamente después de una recuperación de fallos exitosa. - - La ejecución de `ghe-cluster-config-init` no reconocía completamente el código de salida de los jobs en segundo plano que condujeron a un manejo inadecuado de las verificaciones previas al vuelo. - - Al habilitar las GitHub Actions, la inicialización podía fallar silenciosamente. - - Cuando se habilitaron las alertas de vulnerabilidades, las actualizaciones a la serie 3.0 fallaron. - - Los jobs relacionados con los Codespaces se estaban poniendo en fila, lo cual ocasionó a una acumulación de jobs sin procesar. - changes: - - Utiliza una cantidad relativa para el `bootstrap_expect` cónsul y nómada, lo cual permitió que un clúster hiciera un arranque primario, incluso si un conjunto de nodos estaba fuera de servicio. - - Las bitácoras rotarán con base en su tamaño adicionalmente al tiempo. - - Se agregó a kafka-lite al comando `ghe-cluster-status`. - known_issues: - - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - 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. - - Cuando se habilita el modo de mantenimiento, algunos servicios siguen listándose 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 proceder, contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/). - - 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/`). - - 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. - - |2 - La rotación de bitácoras podrían fallar en señalizar los servicios para transicionar a archivos de bitácora nuevos, lo cual lleva a que los archivos de bitácora antiguos se sigan utilizando y a un agotamiento de espacio en el disco raíz eventuales. - Para remediar o prevenir este problema, ejecuta los siguientes comandos en el [shell administrativo](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), o contacta al [Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us) or [GitHub Premium Support](https://premium.githubsupport.com/) para recibir asistencia: - - ``` - 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 - ``` - - sections -> known_issues -> 6 diff --git a/translations/es-ES/data/release-notes/3-0/4.yml b/translations/es-ES/data/release-notes/3-0/4.yml deleted file mode 100644 index e3e14992b9..0000000000 --- a/translations/es-ES/data/release-notes/3-0/4.yml +++ /dev/null @@ -1,25 +0,0 @@ -date: '2021-04-01' -intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".' -sections: - security_fixes: - - '**ALTO:** Se identificó una vulnerabilidad de control de acceso inadecuada en GitHub Enterprise Server, la cual permitió que los tokens de acceso generados desde un [flujo de autenticación web](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) de una GitHub App leyera los metadatos de un repositorio privado a través de la API de REST sin que se le hubieran otorgado los permisos adecuados. Para explotar esta vulnerabilidad, el atacante necesitaría crear una GitHub App en la instancia y hacer que un usuario autorice la aplicación mediante el flujo de autenticación web. Los metadatos del repositorio privado que se devolvió estarían limitados a los repositorios que pertenecen al usuario al cual identifica el token. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anterior a la 3.0.4 y se arregló en las versiones 3.0.4, 2.22.10 y 2.21.18. A esta vulnerabilidad se le asignó un CVE-2021-22865 y se reportó mediante el [Programa de Recompensas por Errores de GitHub](https://bounty.github.com).' - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - 'Cuando se habilitó el modo de mantenimiento, algunos servicios se siguieron listando como "procesos activos", aún cuando se esperaba que estuvieran ejecutándose y no debieron haberse listado.' - - 'Después de mejorar de una versión 2.22.x a una 3.0.x con GitHub Actions habilitado, la versión del ejecutor auto-hospedado no se actualizó y no se hicieron actualizaciones auto-hospedadas.' - - Las compilaciones de las páginas antiguas de GitHub no se limpiaron y esto llevó a un incremento en el uso de disco. - - '`memcached` no se estaba ejecutando en las réplicas activas.' - - La actualización falló al actualizar los permisos de archivo cuando se habilitó GitHub Actions. - - Algunos servicios que estaban dando un tiempo UTC predetemrinado no estaban tulizando una zona horaria configurada en GitHub Enterprise 11.10.x o anterior. - - 'Los servicios no estaban haciendo la transición a los archivos de bitácora nuevos como parte de la rotación de bitácoras, lo cual dio como resultado un uso de disco incrementado.' - - La utilidad de línea de comando `ghe-saml-mapping-csv` produjo un mensaje de advertencia. - - La etiqueta de los resultados de la búsqueda para los repositorios internos se mostró como "Privada" en vez de como "Interna". - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' - - 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. - - '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.' diff --git a/translations/es-ES/data/release-notes/3-0/5.yml b/translations/es-ES/data/release-notes/3-0/5.yml deleted file mode 100644 index da9b18b415..0000000000 --- a/translations/es-ES/data/release-notes/3-0/5.yml +++ /dev/null @@ -1,26 +0,0 @@ -date: '2021-04-14' -intro: 'Los requisitos mínimos de infraestructura incrementaron para {% data variables.product.prodname_ghe_server %}3.0+. Para obtener más información, consulta la sección "[Acerca de los requisitos mínimos para GitHub Enterprise Server 3.0 y posterior](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)".' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - Algunas bitácoras no se incluyeron en la configuración de reenvío de bitácoras. - - 'Un mensaje de advertencia de tipo `jq: error (at :0): Cannot index number with string "settings"` podría ocurrir durante la promoción de la réplica.' - - El restablecer respaldos continuamente a un clúster pudo haber fallado debido a que las réplicas de MySQL fallaron en conectarse al primario. - - Las páginas mp se estaban publicando cuando se utilizó un certificado CA personalizado. - - Los subdominios relacionados con los paquetes no se estaban mostrando en el mensaje de "Configuración de dominio de prueba" para el aislamiento de subdominio. - - El encabezado de `X-GitHub-Enterprise-Host` enviado con webhooks incluía una secuencia aleatoria en vez del nombre de host de la instancia de GitHub Enterprise Server que envió la carga útil de HTTP POST. - - Actualizar de una versión 2.22.x a una 3.0.x podría fallar si las Acciones de GitHub se habilitaron previamente pero se inhabilitaron antes de la mejora. - - Visitar la página `/settings/emails` almacenó el estado que pudo haber causado redirecciones inadecuadas al finalizar sesión y volverla a iniciar. - - Las apps de integración a GitHub no pudieron notificar a los equipos cuando se les mencionó directamente a través de una @mención en un comentario de una propuesta. - - la interpretación de reStructuredText (RST) en la IU web falló y en vez de esto se mostró un texto de marcado RST sin procesar. - - No se enviaron las notificaciones por correo electrónico de las alertas del Escaneo deSecretos a los usuarios autorizados cuando la gráfica de dependencias no se habilitó completamente. - - 'Cuando el ghe-migrator encontró errores de importación, algunas veces abortó todo el proceso y las bitácoras no incluyeron suficiente contexto.' - - Puede que los blocs de notas de Jupyter con caracteres no ASCII fallaran en interpretarse. - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' - - '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.' diff --git a/translations/es-ES/data/release-notes/3-0/6.yml b/translations/es-ES/data/release-notes/3-0/6.yml deleted file mode 100644 index 0d5ea1f0f0..0000000000 --- a/translations/es-ES/data/release-notes/3-0/6.yml +++ /dev/null @@ -1,29 +0,0 @@ -date: '2021-04-28' -sections: - security_fixes: - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - 'During upgrades, the process would pause indefinitely after `cleanup nomad job`.' - - 'Failing `ghe-cluster-failover` with the error message `Trilogy::Error: trilogy_connect`.' - - '`ghe-cluster-status-mysql` showed warnings about failovers as errors.' - - Setup script running on MySQL replication may have caused unnecessary database reseeding during database failover. - - Upgrades did not include the latest version of Actions runner properly installed. - - '`github-env` configuration could result in zombie processes.' - - '`config-apply` could take longer than necessary due to `rake db:migrate` being called unnecessarily.' - - Orchestrator could have failed over to a MySQL replica which was not replicating from primary during seeding phase when primary could not be connected. - - Organizations or projects with errors blocked migration and could not be excluded. - - The Create Repository button was disabled for users who belonged to more than 50 organizations. - - Deleting a branch would temporarily flash an error message indicating something went wrong when the deletion was successful. - - The `rms-packages` index was shown in the site admin dashboard. - - Organization owner was unable to create internal repository due to the correct visibility options not being displayed on the form. - - The repository actions tab rendered a 500 in cases where the actions starter workflows were misconfigured. - - Customers with more than three storage hosts were unable to restore to their disaster-recovery cluster due to the fullest disks being selected instead of empty nodes. - - Code Scanning backend services did not start up reliably after applying hotpatches. - changes: - - Preflight checks allow all AWS instance types by default. - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' diff --git a/translations/es-ES/data/release-notes/3-0/7.yml b/translations/es-ES/data/release-notes/3-0/7.yml deleted file mode 100644 index e9404ce1e1..0000000000 --- a/translations/es-ES/data/release-notes/3-0/7.yml +++ /dev/null @@ -1,22 +0,0 @@ -date: '2021-05-13' -sections: - security_fixes: - - '**HIGH:** A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App''s user-authorization web flow than was displayed to the user during approval. To exploit this vulnerability, an attacker would need to create a GitHub App on the instance and have a user authorize the application through the web authentication flow. All permissions being granted would properly be shown during the first authorization, but in certain circumstances, if the user revisits the authorization flow after the GitHub App has configured additional user-level permissions, those additional permissions may not be shown, leading to more permissions being granted than the user potentially intended. This vulnerability affected GitHub Enterprise Server 3.0.x prior to 3.0.7 and 2.22.x prior to 2.22.13. It was fixed in versions 3.0.7 and 2.22.13. This vulnerability has been assigned CVE-2021-22866 and was reported via the [GitHub Bug Bounty Program](https://bounty.github.com/).' - - Los paquetes se actualizaron a las últimas versiones de seguridad. - bugs: - - Quotes included in Actions or Packages storage configuration could cause errors. - - Custom pre-receive hooks could fail due to too restrictive file size or number of open file limits. - - Orchestrator auto failover could be enabled during the phase of config apply. - - Users with maintainer permissions to a repository were shown an e-mail verification warning instead of a successful page build on the repository Pages settings page. - - The code owner of a wildcard rule would be incorrectly added to the list of owners for the code owners badge even if a later rule took precedence for that path. - - OpenAPI documentation referred to an invalid header. - - 'When creating or editing a pre-receive hook, a race condition in the user interface meant that after selecting a repository, files within the repository were sometimes not populated in files dropdown.' - changes: - - Added logging for config change on HAProxy reload. - - Added logging for repository creation. - known_issues: - - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - '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.' diff --git a/translations/es-ES/data/release-notes/3-1/0-rc1.yml b/translations/es-ES/data/release-notes/3-1/0-rc1.yml deleted file mode 100644 index 31b0795b0e..0000000000 --- a/translations/es-ES/data/release-notes/3-1/0-rc1.yml +++ /dev/null @@ -1,130 +0,0 @@ ---- -date: '2021-05-06' -release_candidate: 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: - - - heading: GitHub Advanced Security Secret Scanning - notes: - - | - [Secret Scanning](https://github.com/features/security) is now generally available on {% data variables.product.prodname_ghe_server %} 3.1+. Scan public and private repositories for committed credentials, find secrets, and notify the secret provider or admin the moment they are committed into a repository. - - This release includes several improvements from the beta of Secret Scanning on {% data variables.product.prodname_ghe_server %}: - - - Expanded our [pattern coverage](/enterprise-server@3.1/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-private-repositories) from 24 partners to 37 - - Added an [API](/rest/reference/secret-scanning) and [webhooks](/developers/webhooks-and-events/webhook-events-and-payloads#secret_scanning_alert) - - Added [notifications for commit authors](https://github.blog/changelog/2021-03-05-secret-scanning-notifications-for-commit-authors-on-private-repositories/) when they commit secrets - - Updated the index view to made it easy to triage secrets in bulk - - Reduced the false positive rate on many patterns - - Administrators using {% data variables.product.prodname_GH_advanced_security %} can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) {% data variables.product.prodname_GH_advanced_security %} secret scanning. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you turn on {% data variables.product.prodname_GH_advanced_security %} secret scanning. - - - heading: GitHub Advanced Security billing improvements - notes: - - | - This release includes several improvements to {% data variables.product.prodname_GH_advanced_security %} billing in {% data variables.product.prodname_ghe_server %}: - - - {% data variables.product.prodname_GH_advanced_security %} customers can now view their active committer count and the remaining number of unused committer seats on their organization or enterprise account’s Billing page. If Advanced Security is purchased for an enterprise, administrators can also view the active committer seats which are being used by other organizations within their enterprise. For more information, see "[About GitHub Advanced Security licensing](/enterprise-server@3.1/admin/advanced-security/about-licensing-for-github-advanced-security)" and "[Viewing your GitHub Advanced Security usage](/enterprise-server@3.1/admin/advanced-security/viewing-your-github-advanced-security-usage)." - - GitHub Advanced Security customers can now view their active committer count for any Advanced Security enabled repositories on their organization or enterprise account's Billing page. These changes help billing administrators track their usage against how many committer licenses they purchased. For more information see "[Managing security and analysis settings for your organization](/enterprise-server@3.1/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." - - - heading: Dependabot improvements - notes: - - | - This release includes improvements to Dependabot alerts in {% data variables.product.prodname_ghe_server %}: - - - Users with Dependabot alerts enabled can see which of their repositories are impacted by a given vulnerability by navigating to its entry in the [GitHub Advisory Database](https://github.com/advisories). This feature is available in public beta. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository)." - - When a vulnerability is added to GitHub Advisory Database, you will no longer receive [email and web notifications](https://github.com/notifications) for Dependabot alerts on low and moderate severity vulnerabilities. These alerts are still accessible from the repository's Security tab. For more information, see [Viewing and updating vulnerable dependencies in your repository](/enterprise-server@3.1/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository). - - 'You can now give people instructions on how to responsibly report security vulnerabilities in your project by adding a `SECURITY.md` file to your repository's `root`, `docs`, or `.github` folder. When someone creates an issue in your repository, they will see a link to your project's security policy. For more information, see "[Adding a security policy to your repository](/enterprise-server@3.1/code-security/getting-started/adding-a-security-policy-to-your-repository)."' - - - heading: GitHub Actions Workflow Visualization beta - notes: - - | - - GitHub Actions can now generate a visual graph of your workflow on every run. With workflow visualization, you can: - - View and understand complex workflows - - Track progress of workflows in real-time - - Troubleshoot runs quickly by easily accessing logs and jobs metadata - - Monitor progress of deployment jobs and easily access deployment targets - - For more information, see "[Using the visualization graph](/actions/managing-workflow-runs/using-the-visualization-graph)." - - - heading: OAuth 2.0 Device Authorization Grant - notes: - - | - [OAuth 2.0 Device Authorization Grant](https://github.com/login/device) allows any CLI client or developer tool to authenticate using a secondary system with a browser. - - Administrators using [OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow) and [GitHub Apps](/developers/apps/authorizing-oauth-apps#device-flow) can [enable and configure](/enterprise-server@3.1/admin/configuration/configuring-secret-scanning-for-your-appliance) OAuth 2.0 Device Authorization Flow, in addition to the existing Web Application Flow. You can review the [updated minimum requirements for your platform](/enterprise-server@3.1/admin/installation/setting-up-a-github-enterprise-server-instance) before you enable OAuth 2.0 Device Authorization Flow. - - - heading: Fusión automática de solicitudes de cambio - notes: - - | - With auto-merge, pull requests can be set to merge automatically when all merge requirements have been satisfied. This saves users from needing to constantly check the state of their pull requests just to merge them. Auto-merge can be enabled by a user with permission to merge and on pull requests that have unsatisfied merge requirements. For more information, see "[Automatically merging a pull request](/enterprise-server@3.1/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)." - - - heading: Custom notifications - notes: - - | - You can customize the types of notifications you want to receive from individual repositories. For more information, see "[Configuring notifications](/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)." - changes: - - - heading: Cambios en la administración - notes: - - By precomputing checksums, the amount of time a repository is under the lock has reduced dramatically, allowing more write operations to succeed immediately and improving monorepo performance. - - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than GitHub Actions. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." - - GitHub Actions now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message. - - Check annotations older than four months will be archived. - - - heading: Cambios de seguridad - notes: - - 'Display of Code Scanning results on a pull request without submitting with a pull request ID is no longer supported. For more information, see "[Configuring code scanning](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" and "[Configuring CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests).' - - SARIF upload support increased to a maximum of 5000 results per upload. - - - heading: Cambios de desarrollador - notes: - - You can specify multiple callback URLs while configuring a GitHub App. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list. - - The GitHub App file permission has been updated to allow an app developer to specify up to 10 files for read-only or read-write access that their app can request access to. - - CodeQL now supports more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) for a variety of 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),[Java](https://github.com/github/codeql/tree/main/java), [Go](https://github.com/github/codeql-go/tree/main)). The CodeQL engine can now detect more sources of untrusted user data, which improves the quality and depth of the code scanning alerts. For more information, see "[About CodeQL](https://codeql.github.com/docs/codeql-overview/about-codeql/)." - - When configuring a GitHub App, the authorization callback URL is a required field. Now, we allow the developer to specify multiple callback URLs. This can be used in services with multiple domains or subdomains. GitHub will always deny authorization if the callback URL from the request is not in the authorization callback URL list. - - 'Delete an entire directory of files, including subdirectories, from your web browser. For more information, see "[Deleting a file or directory](/enterprise-server@3.1/github/managing-files-in-a-repository/deleting-files-in-a-repository#deleting-a-directory)."' - - 'Include multiple words after the `#` in an issue, discussion, or pull request comment to further narrow your search.' - - 'When you’re writing an issue, pull request, or discussion comment the list syntax for bullets, numbers, and tasks autocompletes after you press `return` or `enter`.' - - - heading: Cambios a la API - notes: - - The code scanning API allows users to upload data about static analysis security testing results, or export data about alerts. For more information, see the [code scanning API reference](https://docs.github.com/en/rest/reference/code-scanning). - - The [GitHub Apps API](https://docs.github.com/rest/reference/apps) for managing installations has now graduated from an API preview to a generally available API. The [preview header](https://docs.github.com/rest/overview/api-previews) is no longer required to access these endpoints. - known_issues: - - The GitHub Packages 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. - - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.' - - En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador. - - Las reglas personalizadas del cortafuegos no se mantienen durante una mejora. - - 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. - deprecations: - - - heading: Deprecation of GitHub Enterprise Server 2.20 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.20 was discontinued on March 2, 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.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: Deprecation of GitHub Enterprise Server 2.21 - notes: - - '**{% data variables.product.prodname_ghe_server %} 2.21 will be discontinued on June 9, 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.1/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: Obsoletización de los Eventos de Webhook tradicionales de las GitHub Apps - notes: - - 'Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, dos eventos de webhook relacionados con GitHub Apps se obsoletizaron y eliminaron en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Los eventos obsoletizados de `integration_installation` and `integration_installation_repositories` tienen eventos equivalentes que serán compatibles. Puedes encontrar más información en la [publicación del blog acerca de los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-the-installation-and-installation-repositories-events/).' - - - heading: Obsoletización de la terminal tradicional para las GitHub Apps - notes: - - Comenzando con {% data variables.product.prodname_ghe_server %} 2.21.0, la terminal tradicional de GitHub Apps para crear tokens de acceso a las instalaciones se obsoletizó y se eliminará en la versión 3.2.0 de {% data variables.product.prodname_ghe_server %}. Puedes encontrar más información disponible en la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/). - - - heading: Obsoletización de la API de aplicaciones OAuth - notes: - - 'GitHub ya no es compatible con las terminales de la aplicación de OAuth que contengan `access_token` como parámetro de ruta. Hemos incluído terminales nuevas que te permiten administrar los tokens para las apps de OAuth de forma segura al mover a `access_token` al cuerpo de solicitud. Aunque se hayan obsoletizado, aún se puede acceder a las terminales en esta versión. Intentamos eliminar estas terminales en la versión 3.4 de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la [publicación del blog sobre los anuncios de obsoletización](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/).' - - - heading: Deprecation of GitHub Actions short SHA support - notes: - - 'GitHub Actions will remove support for referencing actions using the shortened version of a git commit SHA. This may cause some workflows in your repository to break. To fix these workflows, you will need to update the action reference to use the full commit SHA. For more information, see "[Security hardening for GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)."' - backups: - - '{% data variables.product.prodname_ghe_server %} 3.1 requires at least [GitHub Enterprise Backup Utilities 3.1.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.1/admin/configuration/configuring-backups-on-your-appliance).' 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/creating-actions/about-actions.md b/translations/es-XL/content/actions/creating-actions/about-actions.md deleted file mode 100644 index 99d732fb04..0000000000 --- a/translations/es-XL/content/actions/creating-actions/about-actions.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -title: Acerca de acciones -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: - - /articles/about-actions - - /github/automating-your-workflow-with-github-actions/about-actions - - /actions/automating-your-workflow-with-github-actions/about-actions - - /actions/building-actions/about-actions -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' - github-ae: '*' -type: overview -topics: - - Action development - - Fundamentals ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de acciones - -Puedes crear acciones escribiendo 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. - -{% if currentVersion == "free-pro-team@latest" %} -Puedes escribir tus propias acciones para usar en tu flujo de trabajo o compartir las acciones que crees con la comunidad de {% data variables.product.prodname_dotcom %}. Para compartir las acciones que creaste, tu repositorio debe ser público. -{% endif %} - -Las acciones pueden ejecutarse directamente en una máquina o en un contenedor Docker. Puedes definir las entradas, las salidas y las variables de entorno de una acción. - -### Tipos de acciones - -Puedes crear acciones de contenedor Docker y JavaScript. Las acciones requieren un archivo de metadatos para definir las entradas, salidas y puntos de entrada para tu acción. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)" - -| Tipo | Sistema operativo | -| ----------------------------- | --------------------- | -| Contenedor Docker | Linux | -| JavaScript | Linux, MacOS, Windows | -| Pasos de ejecución compuestos | Linux, MacOS, Windows | - -#### Acciones del contenedor Docker - -Los contenedores Docker empaquetan el entorno con el código {% data variables.product.prodname_actions %}. Esto crea una unidad de trabajo más consistente y confiable, ya que el consumidor de la acción no necesita preocuparse por las herramientas o las dependencias. - -Un contenedor Docker te permite usar versiones específicas de un sistema operativo, dependencias, herramientas y código. Para las acciones que se deben ejecutar en una configuración de entorno específica, Docker es una opción ideal porque puedes personalizar el sistema operativo y las herramientas. Debido a la latencia para crear y recuperar el contenedor, las acciones del contenedor Docker son más lentas que las acciones de JavaScript. - -Las acciones de contenedor de Docker solo pueden ejecutarse en ejecutores con un sistema operativo Linux. {% data reusables.github-actions.self-hosted-runner-reqs-docker %} - -#### Acciones de JavaScript - -Las acciones de JavaScript pueden ejecutarse directamente en una máquina del ejecutor y separar el código de acción del entorno utilizado para ejecutar el código. El uso de una acción de JavaScript simplifica el código de acción y se ejecuta más rápido que una acción de contenedor Docker. - -{% data reusables.github-actions.pure-javascript %} - -Si estás desarrollando un proyecto Node.js, el conjunto de herramientas de las {% data variables.product.prodname_actions %} te ofrece paquetes que puedes usar en tu proyecto para acelerar el desarrollo. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit). - -#### Acciones compuestas de los pasos de ejecución - -Una acción para los _pasos de ejecución compuestos_ te permite combinar varios pasos de ejecuciónes de flujo de trabajo en una misma acción. Por ejemplo, puedes utilizar esta característica para agrupar varios comandos de ejecución en una acción y después tener un flujo de trabajo que ejecute estos comandos agrupados en un solo paso utilizando esta acción. Para ver un ejemplo, revisa la sección "[Crear una acción de pasos de ejecución compuestos](/actions/creating-actions/creating-a-composite-run-steps-action)". - -### Elegir una ubicación para tu acción - -Si estás desarrollando una acción para que otras personas la utilicen, te recomendamos mantener la acción en su propio repositorio en lugar de agruparla con otro código de aplicación. Esto te permite versionar, rastrear y lanzar la acción como cualquier otro software. - -{% if currentVersion == "free-pro-team@latest" %} -Con el almacenamiento de una acción en su propio repositorio es más fácil para la comunidad de {% data variables.product.prodname_dotcom %} descubrir la acción, reduce el alcance de la base de código para que los desarrolladores solucionen problemas y extiendan la acción, y desacopla el control de versiones de otro código de aplicación. -{% endif %} - -Si estás creando una acción que no planeas poner a disposición del público, puedes almacenar los archivos de la acción en cualquier ubicación de tu repositorio. Si tienes la intención de combinar la acción, el flujo de trabajo y el código de aplicación en un único repositorio, es recomendable que almacenes las acciones en el directorio `.github`. Por ejemplo, `.github/actions/action-a` y `.github/actions/action-b`. - -### Utilizar la administración de lanzamientos para las acciones - -Para garantizar de que tu acción es compatible con {% data variables.product.prodname_ghe_server %}, debes asegurarte de que no utilices ninguna referencia escrita a mano para las URL de la API de {% data variables.product.prodname_dotcom %}. En vez de esto, utiliza variables de ambiente para referirte a la API de {% data variables.product.prodname_dotcom %}: - -- Crear y validar un lanzamiento en una rama de lanzamiento (tal como `release/v1`) antes de crear la etiqueta de lanzamiento (por ejemplo, `v1.0.2`). -- Para el caso de GraphQL, utiliza la variable de ambiente `GITHUB_GRAPHQL_URL`. - -Para obtener más información, consulta la sección "[Variables de ambiente predeterminadas](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables)." - -### Utilizar la administración de lanzamientos para las acciones - -Esta sección explica cómo puedes utilizar la administración de lanzamientos para distribuir actualizaciones a tus acciones de forma predecible. - -#### Buenas prácticas para la administración de lanzamientos - -Si estás desarrollando una acción para que la utilicen otras personas, te recomendamos utilizar la administración de lanzamientos para controlar cómo distribuyes las actualizaciones. Los usuarios pueden esperar que una versión mayor de una acción incluya correcciones críticas y parches de seguridad necesarios y que se mantenga compatible con los flujos de trabajo existentes. Deberías considerar lanzar una versión mayor cada que tus cambios afecten la compatibilidad. - -Bajo este acercamiento de administración de lanzamientos, los usuarios no deberían referenciar una rama `master` de una acción, ya que es probable que contenga el código más reciente y, en consecuencia, podría ser inestable. En vez de esto, puedes recomendar a tus usuarios que especifiquen una versión mayor cuando utilicen tu acción, y únicamente dirigirlos a una versión más específica si encuentran algún problema. - -Para utilizar una versión específica de la acción, los usuarios pueden configurar su flujo de trabajo de {% data variables.product.prodname_actions %} para apuntar a una etiqueta, el SHA de una confirmación o a una rama denominada para un lanzamiento. - -#### Utilizar etiquetas para la administración de lanzamientos - -Te recomendamos utilizar etiquetas para la administración de lanzamientos de acciones. Al utilizar este acercamiento, tus usuarios pueden distinguir claramente entre las versiones mayores y menores: - -- Crear y validar un lanzamiento en una rama de lanzamiento (tal como `release/v1`) antes de crear la etiqueta de lanzamiento (por ejemplo, `v1.0.2`). -- Crear un lanzamiento utilizando un versionamiento semántico. Para obtener más información, consulta "[Creating releases](/articles/creating-a-label/) (Crear lanzamientos)". -- Mover la etiqueta de versión mayor (tal como `v1`, `v2`) para apuntar a la referencia de Git en el lanzamiento actual. Para obtener más información, consulta [Conceptos básicos de Git: etiquetas](https://git-scm.com/book/en/v2/Git-Basics-Tagging)". -- Introducir una etiqueta de versión mayor (`v2`) para los cambios que modificarán sustancialmente los flujos de trabajo existentes. Por ejemplo, un cambio importante será cambiar las entradas de una acción. -- Las versiones mayores pueden lanzarse inicialmente con una etiqueta de `beta` para indicar su estado, por ejemplo, `v2-beta`. La etiqueta `-beta` puede eliminarse entonces cuando esté listo. - -Este ejemplo demuestra como un usuario puede referenciar una etiqueta de un lanzamiento mayor: - -```yaml -steps: - - uses: actions/javascript-action@v1 -``` - -Este ejemplo demuestra como un usuario puede referenciar una etiqueta de un lanzamiento de parche: - -```yaml -steps: - - uses: actions/javascript-action@v1.0.1 -``` - -#### Utilizar ramas para la administración de lanzamientos - -Si prefieres utilizar nombres de rama para la administración de lanzamientos, este ejemplo demuestra como referenciar una rama nombrada: - -```yaml -steps: - - uses: actions/javascript-action@v1-beta -``` - -#### Utilizar el SHA de las confirmaciones para la administración de lanzamientos - -Cada confirmación de Git recibe un valor calculado de SHA, el cual es único e inmutable. Los usuarios de tus acciones podrían preferir obtener un valor de SHA para la confirmación, ya que este acercamiento puede ser más confiable que especificar una etiqueta, la cual podría borrarse o moverse. Sin embargo, esto significa que los usuarios no recibirán ls actualizaciones posteriores que se hagan a la acción. Utilizar el valor completo de SHA de una confirmación en vez de su valor abreviado puede ayudar a prevenir que las personas utilicen una confirmación malintencionada que utilice la misma abreviación. - -```yaml -steps: - - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89 -``` - -### Crear un archivo README para tu acción - -Si tienes la intención de compartir públicamente tu acción, te recomendamos crear un archivo README para ayudar a las personas a que aprendan a usar tu acción. Puedes incluir esta información en tu `README.md`: - -- Una descripción detallada de lo que hace la acción. -- Argumentos necesarios de entrada y salida. -- Argumentos opcionales de entrada y salida. -- Secretos que utiliza la acción. -- Variables de entorno que utiliza la acción. -- Un ejemplo de cómo usar tu acción en un flujo de trabajo. - -### Comparar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_github_apps %} - -{% data variables.product.prodname_marketplace %} ofrece herramientas para mejorar tu flujo de trabajo. Comprender las diferencias y los beneficios de cada herramienta te permitirá seleccionar la mejor herramienta para tu trabajo. Para obtener más información acerca de la creacción de acciones y apps, consulta las secciones "[Acerca de Github Actions](/actions/getting-started-with-github-actions/about-github-actions)" y "[Acerca de las apps](/apps/about-apps/)". - -#### Fortalezas de las acciones y las aplicaciones de GitHub - -Mientras que tanto las {% data variables.product.prodname_actions %} como las {% data variables.product.prodname_github_app %} proporcionan formas de construir herramientas de automatización y flujo de trabajo, cada una tiene fortalezas que las hacen útiles de diferentes maneras. - -{% data variables.product.prodname_github_apps %}: -* Se ejecutan de manera persistente y pueden reaccionar rápidamente a los eventos. -* Funcionan bien cuando se necesitan datos de manera persistente. -* Funcionan mejor con las solicitudes de API que no consumen mucho tiempo. -* Se ejecutan en un servidor o infraestructura de computación que proporciones. - -{% data variables.product.prodname_actions %}: -* Brindan automatización que puede realizar una integración continua y una implementación continua. -* Pueden ejecutarse directamente en máquinas de ejecutor o en contenedores Docker. -* Pueden incluir acceso a un clon de tu repositorio, lo que permite que las herramientas de implementación y publicación, los formateadores de código y las herramientas de la línea de comando accedan a tu código. -* No necesitan que implementas un código o que sirvas una aplicación. -* Tienen una interfaz simple para crear y usar secretos, que permite que las acciones interactúen con servicios de terceros sin la necesidad de almacenar las credenciales de la persona que utiliza la acción. - -### Leer más - -- "[Herramientas de desarrollo para {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)" diff --git a/translations/es-XL/content/actions/creating-actions/creating-a-composite-run-steps-action.md b/translations/es-XL/content/actions/creating-actions/creating-a-composite-run-steps-action.md deleted file mode 100644 index 4e4f6ed6cb..0000000000 --- a/translations/es-XL/content/actions/creating-actions/creating-a-composite-run-steps-action.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: Crear una acción para pasos de ejecución compuestos -intro: En esta guía aprenderás cómo crear una acción para los pasos de ejecución compuestos. -product: '{% data reusables.gated-features.actions %}' -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' - github-ae: '*' -type: tutorial -topics: - - Action development ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Introducción - -En esta guía aprenderás sobre los componentes básicos que se requieren para crear y utilizar una acción de pasos de ejecución compuestos empacada. 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`. - -Una vez que completes este proyecto, deberás entender cómo construir tu accion para pasos de ejecución compuestos para probarla en un flujo de trabajo. - -### Prerrequisitos - -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 %}. Puedes elegir cualquier nombre de repositorio o utilizar el siguiente ejemplo de `hello-world-composite-run-steps-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)". - -1. Desde tu terminal, cambia los directorios en el repositorio nuevo. - - ```shell - cd hello-world-composite-run-steps-action - ``` - -2. En el repositorio `hello-world-composite-run-steps-action`, crea un archivo nuevo que se llame `goodbye.sh` y agrega el siguiente código de ejemplo: - - ```bash - echo "Goodbye" - ``` - -1. Desde tu terminal, haz ejecutable a `goodbye.sh` y verifícalo en tu repositorio. - - ```shell - chmod +x goodbye.sh - ``` - -1. Desde tu terminal, ingresa tu archivo `goodbye.sh`. - ```shell - git add goodbye.sh - git commit -m "Add goodbye script" - git push - ``` - -### Crear un archivo de metadatos de una acción - -1. En el repositorio `hello-world-composite-run-steps-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 encontrar los pasos de ejecución compuestos](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-run-steps-actions)". - - {% raw %} - **action.yml** - ```yaml - name: 'Hello World' - description: 'Greet someone' - inputs: - who-to-greet: # id of input - description: 'Who to greet' - required: true - default: 'World' - outputs: - random-number: - description: "Random number" - value: ${{ steps.random-number-generator.outputs.random-id }} - runs: - using: "composite" - steps: - - run: echo Hello ${{ inputs.who-to-greet }}. - shell: bash - - id: random-number-generator - run: echo "::set-output name=random-id::$(echo $RANDOM)" - shell: bash - - run: ${{ github.action_path }}/goodbye.sh - 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`. También le dice al ejecutor cómo ejecutar la acción de los pasos de ejecución compuestos. - - Para obtener más información acerca de cómo administrar las alidas, consulta la secicón "[`outputs` para los pasos de ejecución compuestos](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-run-steps-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)". - -1. Crear una etiqueta nueva. Este ejemplo utiliza una etiqueta llamada `v1` para la rama principal. Para obtener más información, consulta la sección "[Crear una etiqueta](/github/managing-your-work-on-github/creating-a-label)". - -### Probar tu acción en un flujo de trabajo - -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-run-steps-action#creating-an-action-metadata-file)". - -Copia el código del flujo de trabajo en un archivo `.github/workflows/main.yml` en otro repositorio, pero reemplaza a `actions/hello-world-composite-run-steps-action@v1` con el prepositorio y la etiqueta que creaste. También puedes reemplazar la entrada `who-to-greet` con tu nombre. - -{% raw %} -**.github/workflows/main.yml** -```yaml -on: [push] - -jobs: - hello_world_job: - runs-on: ubuntu-latest - name: A job to say hello - steps: - - uses: actions/checkout@v2 - - id: foo - uses: actions/hello-world-composite-run-steps-action@v1 - with: - who-to-greet: 'Mona the Octocat' - - run: echo random-number ${{ steps.foo.outputs.random-number }} - shell: bash -``` -{% endraw %} - -Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. La salida deberá incluir "Hello Mona the Octocat", el resultado del script de "Goodbye" y un número aleatorio. diff --git a/translations/es-XL/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/es-XL/content/actions/creating-actions/creating-a-docker-container-action.md deleted file mode 100644 index 1111bedd20..0000000000 --- a/translations/es-XL/content/actions/creating-actions/creating-a-docker-container-action.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -title: Crear una acción de contenedor de Docker -intro: Esta guía te muestra los pasos mínimos necesarios para desarrollar una acción de contenedor Docker. -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /articles/creating-a-docker-container-action - - /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action - - /actions/automating-your-workflow-with-github-actions/creating-a-docker-container-action - - /actions/building-actions/creating-a-docker-container-action -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial -topics: - - Action development - - Docker ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Introducción - -Esta guía te muestra los pasos mínimos necesarios para desarrollar una acción de contenedor de Docker. 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" en los registros o "Hello [who-to-greet]"si proporcionas un nombre personalizado. - -Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción de contenedor Docker y probarla en un flujo de trabajo. - -{% data reusables.github-actions.self-hosted-runner-reqs-docker %} - -### Prerrequisitos - -Puede resultar útil tener un conocimiento básico de las variables de entorno de las {% data variables.product.prodname_actions %} y del sistema de archivos del contenedor de Docker: - -- "[Usar variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" -- "[Entornos virtuales para {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem)" - -Antes de comenzar, necesitarás crear un repositorio GitHub. - -1. Crea un repositorio nuevo en {% data variables.product.product_location %}. Puedes elegir cualquier nombre de repositorio o usar "hello-world-docker-action" como este ejemplo. 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)". - -1. Desde tu terminal, cambia los directorios en el repositorio nuevo. - - ```shell - cd hello-world-docker-action - ``` - -### Crear un Dockerfile - -En tu nuevo directorio `hello-world-docker-action`, crea un nuevo archivo `Dockerfile`. Para obtener más información, consulta al "[Sporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)". - -**Dockerfile** -```dockerfile -# Imagen del contenedor que ejecuta tu código -FROM alpine:3.10 - -# Copias tu archivo de código de tu repositorio de acción a la ruta `/`del contenedor -COPY entrypoint.sh /entrypoint.sh - -# Archivo del código a ejecutar cuando comienza el contedor del docker (`entrypoint.sh`) -ENTRYPOINT ["/entrypoint.sh"] -``` - -### Crear un archivo de metadatos de una acción - -Crear un nuevo archivo `action.yml` en el directorio `hello-world-docker` que creaste anteriormente. 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)". - -{% raw %} -**action.yml** -```yaml -# action.yml -name: 'Hello World' -description: 'Greet someone and record the time' -inputs: - who-to-greet: # id of input - description: 'Who to greet' - required: true - default: 'World' -outputs: - time: # id of output - description: 'The time we greeted you' -runs: - using: 'docker' - image: 'Dockerfile' - args: - - ${{ inputs.who-to-greet }} -``` -{% endraw %} - -Este metado define un parámetro de entrada `who-to-greet` y uno de salida `time`. Para pasar las entradas al contenedor Docker, debes declarar la entrada usando `inputs` y pasar la entrada a la palabra clave `args`. - -{% data variables.product.prodname_dotcom %} creará una imagen desde tu `Dockerfile` y ejecutar comandos en nuevo contenedor usando esta imagen. - -### Escribir el código de la acción - -Puedes elegir cualquier imagen de Docker base y, por lo tanto, cualquier idioma para tu acción. El siguiente ejemplo de script shell usa la variable de entrada `who-to-greet` para imprimir "Hello [who-to-greet]" en el archivo de registro. - -A continuación, el script obtiene la hora actual y la establece como una variable de salida que pueden usar las acciones que se ejecutan posteriormente en unt rabajo. Para que {% data variables.product.prodname_dotcom %} reconozca las variables de salida, debes usar un comando de flujo de trabajo en una sintaxis específica: `echo ":: set-Output Name =::"`. Para obtener más información, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)". - -1. Crea un archivo `entrypoint.sh` nuevo en el directorio `hello-world-docker-action`. - -1. Convierte tu archivo `entrypoint.sh` en ejecutable: - - ```shell - chmod +x entrypoint.sh - ``` - -1. Agrega el siguiente código a tu archivo `entrypoint.sh`. - - **entrypoint.sh** - ```shell - #!/bin/sh -l - - echo "Hello $1" - time=$(date) - echo "::set-output name=time::$time" - ``` - - Si `entrypoint.sh` se ejecuta sin errores, el estado de la acción se establece en `exitoso`. También puedes establecer explícitamente códigos de salida en el código de tu acción para proporcionar el estado de una acción. Para obtener más información, consulta la sección "[Configurar los códigos de salida para las acciones](/actions/creating-actions/setting-exit-codes-for-actions)". - -### Crear un README - -Puedes crear un archivo README para que las personas sepan cómo usar tu acción. Un archivo README resulta más útil cuando planificas el intercambio de tu acción públicamente, pero también es una buena manera de recordarle a tu equipo cómo usar la acción. - -En tu directorio <`hello-world-docker-action`, crea un archivo `README.md` que especifique la siguiente información: - -- Una descripción detallada de lo que hace la acción. -- Argumentos necesarios de entrada y salida. -- Argumentos opcionales de entrada y salida. -- Secretos que utiliza la acción. -- Variables de entorno que utiliza la acción. -- Un ejemplo de cómo usar tu acción en un flujo de trabajo. - -**README.md** -```markdown -# Acción de docker Hello world - -Esta acción imprime "Hello World" o "Hello" + el nombre de una persona a quien saludar en el registro. - -## Entradas - -### `who-to-greet` - -**Obligatorio** El nombre de la persona a quien saludar. Default `"World"`. - -## Outputs - -### `time` - -El tiempo en que lo saludamos. - -## Ejemplo de uso - -uses: actions/hello-world-docker-action@v1 -with: - who-to-greet: 'Mona the Octocat' -``` - -### Confirmar, etiquetar y subir tu acción a GitHub - -Desde tu terminal, confirma tus archivos `action.yml`, `entrypoint.sh`, `Dockerfile`, y `README.md`. - -También se recomienda agregarles una etiqueta de versión a los lanzamientos de tu acción. Para obtener más información sobre el control de versiones de tu acción, consulta la sección "[Acerca de las acciones](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)". - -```shell -git add action.yml entrypoint.sh Dockerfile README.md -git commit -m "Mi primera acción está lista" -git tag -a -m "Mi primera versión de acción" v1 -git push --follow-tags -``` - -### Probar tu acción en un flujo de trabajo - -Ahora estás listo para probar tu acción en un flujo de trabajo. Cuando una acción esté en un repositorio privado, la acción solo puede usarse en flujos de trabajo en el mismo repositorio. Las acciones públicas pueden ser usadas por flujos de trabajo en cualquier repositorio. - -{% data reusables.actions.enterprise-marketplace-actions %} - -#### Ejemplo usando una acción pública - -El siguiente código de flujo de trabajo usa la acción completa hello world en el repositorio público [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action). Copia el siguiente código de ejemplo de flujo de trabajo en un archivo `.github/workflows/main.yml`, pero reemplaza `actions/hello-world-docker-action` por tu nombre de repositorio y acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. - -{% raw %} -**.github/workflows/main.yml** -```yaml -on: [push] - -jobs: - hello_world_job: - runs-on: ubuntu-latest - name: A job to say hello - steps: - - name: Hello world action step - id: hello - uses: actions/hello-world-docker-action@v1 - with: - who-to-greet: 'Mona the Octocat' - # Use the output from the `hello` step - - name: Get the output time - run: echo "The time was ${{ steps.hello.outputs.time }}" -``` -{% endraw %} - -#### Ejemplo usando una acción privada - -Copia el siguiente ejemplo de código de flujo de trabajo en un archivo `.github/workflows/main.yml` en tu repositorio de acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. - -{% raw %} -**.github/workflows/main.yml** -```yaml -on: [push] - -jobs: - hello_world_job: - runs-on: ubuntu-latest - name: A job to say hello - steps: - # To use this repository's private action, - # you must check out the repository - - name: Checkout - uses: actions/checkout@v2 - - name: Hello world action step - uses: ./ # Uses an action in the root directory - id: hello - with: - who-to-greet: 'Mona the Octocat' - # Use the output from the `hello` step - - name: Get the output time - run: echo "The time was ${{ steps.hello.outputs.time }}" -``` -{% endraw %} - -Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. Deberías ver "Hello Mona the Octocat" o el nombre que usaste para la entrada `who-to-greet` y la marcación de hora impresa en el registro. - -![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/docker-action-workflow-run.png) diff --git a/translations/es-XL/content/actions/creating-actions/creating-a-javascript-action.md b/translations/es-XL/content/actions/creating-actions/creating-a-javascript-action.md deleted file mode 100644 index 795103a330..0000000000 --- a/translations/es-XL/content/actions/creating-actions/creating-a-javascript-action.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -title: Crear una acción de JavaScript -intro: 'En esta guía, aprenderás como desarrollar una acción de JavaScript usando el kit de herramientas de acciones.' -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /articles/creating-a-javascript-action - - /github/automating-your-workflow-with-github-actions/creating-a-javascript-action - - /actions/automating-your-workflow-with-github-actions/creating-a-javascript-action - - /actions/building-actions/creating-a-javascript-action -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial -topics: - - Action development - - JavaScript ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Introducción - -En esta guía, aprenderás acerca de los componentes básicos necesarios para crear y usar una acción de JavaScript 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" en los registros o "Hello [who-to-greet]"si proporcionas un nombre personalizado. - -Esta guía usa el módulo Node.js del kit de herramientas {% data variables.product.prodname_actions %} para acelerar el desarrollo. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit). - -Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción de JavaScript y probarla en un flujo de trabajo. - -{% data reusables.github-actions.pure-javascript %} - -### Prerrequisitos - -Antes de comenzar, necesitarás descargar Node.js y crear un repositorio GitHub. - -1. Descarga e instala Node.js 12.x, que incluye npm. - - https://nodejs.org/en/download/current/ - -1. Crea un repositorio nuevo en {% data variables.product.product_location %}. Puedes elegir cualquier nombre de repositorio o usar "hello-world-javascript-action" como este ejemplo. 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)". - -1. Desde tu terminal, cambia los directorios en el repositorio nuevo. - - ```shell - cd hello-world-javascript-action - ``` - -1. Desde tu terminal, inicializa el directorio con un archivo `package.json`. - - ```shell - npm init -y - ``` - -### Crear un archivo de metadatos de una acción - -Crea un nuevo archivo `action.yml` en el directorio `hello-world-javascript-action` con el siguiente código de ejemplo. 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)". - - -**action.yml** -```yaml -name: 'Hello World' -description: 'Greet someone and record the time' -inputs: - who-to-greet: # id of input - description: 'Who to greet' - required: true - default: 'World' -outputs: - time: # id of output - description: 'The time we greeted you' -runs: - using: 'node12' - main: 'index.js' -``` - -Este archivo define la entrada `who-to-greet` y la salida `time`. También informa al ejecutador de la acción cómo empezar a ejecutar esta acción de JavaScript. - -### Añadir paquetes de kit de herramientas de acciones - -El kit de herramientas de acciones es una recopilación de los paquetes Node.js que te permiten desarrollar rápidamente acciones de JavaScript con más consistencia. - -El paquete del kit de herramientas [`@actions/Core`](https://github.com/actions/toolkit/tree/master/packages/core) brinda una interfaz a los comandos del flujo de trabajo, variables de entrada y salida, estados de salida y mensajes de depuración. - -El kit de herramientas también ofrece un paquete [`@actions/github`](https://github.com/actions/toolkit/tree/master/packages/github) que devuelve un cliente autenticado Octokit REST y acceso a los contextos de acciones de GitHub. - -El kit de herramientas ofrece más de un paquete `core` y `github`. Para obtener más información, consulta el repositorio [actions/toolkit](https://github.com/actions/toolkit). - -En tu terminal, instala los paquetes `core` and `github` del kit de herramientas de acciones. - -```shell -npm install @actions/core -npm install @actions/github -``` - -Ahora deberías ver un directorio `node_modules` con los módulos que acabas de instalar y un archivo `package-lock.json` con las dependencias del módulo instalado y las versiones de cada módulo instalado. - -### Escribir el código de la acción - -Esta acción usa el kit de herramientas para obtener la variable de entrada `who-to-greet` requerida en el archivo de metadatos de la acción e imprime "Hello [who-to-greet]" en un mensaje de depuración del registro. A continuación, el script obtiene la hora actual y la establece como una variable de salida que pueden usar las acciones que se ejecutan posteriormente en unt rabajo. - -Las Acciones de GitHub proporcionan información de contexto sobre el evento de webhooks, las referencias de Git, el flujo de trabajo, la acción y la persona que activó el flujo de trabajo. Para acceder a la información de contexto, puedes usar el paquete `github`. La acción que escribirás imprimirá el evento de webhook que carga el registro. - -Agrega un archivo nuevo denominado `index.js`, con el siguiente código. - -**index.js** -```javascript -const core = require('@actions/core'); -const github = require('@actions/github'); - -try { - // `who-to-greet` input defined in action metadata file - const nameToGreet = core.getInput('who-to-greet'); - console.log(`Hello ${nameToGreet}!`); - const time = (new Date()).toTimeString(); - core.setOutput("time", time); - // Get the JSON webhook payload for the event that triggered the workflow - const payload = JSON.stringify(github.context.payload, undefined, 2) - console.log(`The event payload: ${payload}`); -} catch (error) { - core.setFailed(error.message); -} -``` - -Si se lanza un error en el ejemplo anterior `index.js`, `core.setFailed(error.message);` usa el paquete del kit de herramientas de acciones [`@actions/core`](https://github.com/actions/toolkit/tree/master/packages/core) para registrar un mensaje y establecer un código de salida defectuoso. Para obtener más información, consulta la sección "[Configurar los códigos de salida para las acciones](/actions/creating-actions/setting-exit-codes-for-actions)". - - -### Crear un README - -Puedes crear un archivo README para que las personas sepan cómo usar tu acción. Un archivo README resulta más útil cuando planificas el intercambio de tu acción públicamente, pero también es una buena manera de recordarle a tu equipo cómo usar la acción. - -En tu directorio `hello-world-javascript-action`, crea un archivo `README.md` que especifique la siguiente información: - -- Una descripción detallada de lo que hace la acción. -- Argumentos necesarios de entrada y salida. -- Argumentos opcionales de entrada y salida. -- Secretos que utiliza la acción. -- Variables de entorno que utiliza la acción. -- Un ejemplo de cómo usar tu acción en un flujo de trabajo. - -**README.md** -```markdown -# Hello world docker action - -Esta acción imprime "Hello World" o "Hello" + el nombre de una persona a quien saludar en el registro. - -## Entradas - -### `who-to-greet` - -**Obligatorio** El nombre de la persona a quien saludar. Default `"World"`. - -## Outputs - -### `time` - -El tiempo en que lo saludamos. - -## Example usage - -uses: actions/hello-world-javascript-action@v1.1 -with: - who-to-greet: 'Mona the Octocat' -``` - -### Confirmar, etiquetar y subir tu acción a GitHub - -{% data variables.product.product_name %} descarga cada acción ejecutada en un flujo de trabajo durante el tiempo de ejecución y la ejecuta como un paquete completo de código antes de que puedas usar comandos de flujo de trabajo como `run` para interactuar con la máquina del ejecutor. Eso significa que debes incluir cualquier dependencia del paquete requerida para ejecutar el código de JavaScript. Necesitarás verificar los paquetes `core` y `github` del kit de herramientas para el repositorio de tu acción. - -Desde tu terminal, confirma tus archivos `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json` y `README.md`. Si agregaste un archivo `.gitignore` que enumera `node_modules`, deberás eliminar esa línea para confirmar el directorio `node_modules`. - -También se recomienda agregarles una etiqueta de versión a los lanzamientos de tu acción. Para obtener más información sobre el control de versiones de tu acción, consulta la sección "[Acerca de las acciones](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)". - - -```shell -git add action.yml index.js node_modules/* package.json package-lock.json README.md -git commit -m "Mi primera acción está lista" -git tag -a -m "Mi primera versión de acción" v1 -git push --follow-tags -``` - -Como alternativa para verificar tu directorio de `node_modules`, puedes utilizar una herramienta que se llama [`@vercel/ncc`](https://github.com/vercel/ncc) para compilar tu código y módulos en un archivo que se utilice para la distribución. - -1. Instala `vercel/ncc` ejecutando este comando en tu terminal. `npm i -g @vercel/ncc` - -1. Compila tu archivo `index.js`. `ncc build index.js --license licenses.txt` - - Verás un nuevo archivo `dist/index.js` con tu código y los módulos compilados. También verás un archivo asociado de `dist/licenses.txt` que contiene todas las licencias de los `node_modules` que estás utilizando. - -1. Cambia la palabra clave `main` en tu archivo `action.yml` para usar el nuevo archivo `dist/index.js`. `main: 'dist/index.js'` - -1. Si ya has comprobado tu directorio `node_modules`, eliminínalo. `rm -rf node_modules/*` - -1. Desde tu terminal, confirma las actualizaciones para tu `action.yml`, `dist/index.js` y `node_modules`. -```shell -git add action.yml dist/index.js node_modules/* -git commit -m "Use vercel/ncc" -git tag -a -m "My first action release" v1 -git push --follow-tags -``` - -### Probar tu acción en un flujo de trabajo - -Ahora estás listo para probar tu acción en un flujo de trabajo. Cuando una acción esté en un repositorio privado, la acción solo puede usarse en flujos de trabajo en el mismo repositorio. Las acciones públicas pueden ser usadas por flujos de trabajo en cualquier repositorio. - -{% data reusables.actions.enterprise-marketplace-actions %} - -#### Ejemplo usando una acción pública - -El siguiente código de flujo de trabajo usa la acción hello world completada en el repositorio `actions/hello-world-javascript-action`. Copia el código de flujo de trabajo en un archivo `.github/workflows/main.yml`, pero reemplaza el repositorio `actions/hello-world-javascript-action` con el repositorio que creaste. También puedes reemplazar la entrada `who-to-greet` con tu nombre. - -{% raw %} -**.github/workflows/main.yml** -```yaml -on: [push] - -jobs: - hello_world_job: - runs-on: ubuntu-latest - name: A job to say hello - steps: - - name: Hello world action step - id: hello - uses: actions/hello-world-javascript-action@v1.1 - with: - who-to-greet: 'Mona the Octocat' - # Use the output from the `hello` step - - name: Get the output time - run: echo "The time was ${{ steps.hello.outputs.time }}" -``` -{% endraw %} - -#### Ejemplo usando una acción privada - -Copia el siguiente ejemplo de código de flujo de trabajo en un archivo `.github/workflows/main.yml` en tu repositorio de acción. También puedes reemplazar la entrada `who-to-greet` con tu nombre. - -{% raw %} -**.github/workflows/main.yml** -```yaml -on: [push] - -jobs: - hello_world_job: - runs-on: ubuntu-latest - name: A job to say hello - steps: - # To use this repository's private action, - # you must check out the repository - - name: Checkout - uses: actions/checkout@v2 - - name: Hello world action step - uses: ./ # Uses an action in the root directory - id: hello - with: - who-to-greet: 'Mona the Octocat' - # Use the output from the `hello` step - - name: Get the output time - run: echo "The time was ${{ steps.hello.outputs.time }}" -``` -{% endraw %} - -Desde tu repositorio, da clic en la pestaña de **Acciones** y selecciona la última ejecución de flujo de trabajo. Deberías ver "Hello Mona the Octocat" o el nombre que usaste para la entrada `who-to-greet` y la marcación de hora impresa en el registro. - -![Captura de pantalla del uso de tu acción en un flujo de trabajo](/assets/images/help/repository/javascript-action-workflow-run.png) diff --git a/translations/es-XL/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/es-XL/content/actions/creating-actions/dockerfile-support-for-github-actions.md deleted file mode 100644 index dcfa3cd718..0000000000 --- a/translations/es-XL/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -title: Soporte de Dockerfile para GitHub Actions -shortTitle: Docker -intro: 'Cuando creas un "Dockerfile" para una acción de un contenedor de Docker, debes estar consciente de cómo interactúan algunas instrucciones de Docker con GitHub Actions y con el archivo de metadatos de la acción.' -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /actions/building-actions/dockerfile-support-for-github-actions -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: reference ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de las instrucciones de Dockerfile - -Un `Dockerfile` contiene instrucciones y argumentos que definen el contenido y comportamiento inicial de un contenedor de Docker. Para obtener más información acerca de las instrucciones compatibles con Docker, consulta la sección "[Dockerfile reference](https://docs.docker.com/engine/reference/builder/)" en la documentación de Docker. - -### Instrucciones e invalidaciones de Dockerfile - -Algunas instrucciones de Docker interactúan con GitHub Actions, y un archivo de metadatos de la acción puede invalidar algunas instrucciones de Docker. Asegúrate de que estás familiarizado con la manera en que tu Dockerfile interactúa con {% data variables.product.prodname_actions %} para prevenir cualquier comportamiento inesperado. - -#### USER - -Las acciones de Docker deben ejecutarse mediante el usuario predeterminado de Docker (root). No utilices la instrucción `USER` en tu `Dockerfile`, ya que no podrás acceder a `GITHUB_WORKSPACE`. Para obtener más información, consulta la sección "[Utilizar variables del ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" y [USER reference](https://docs.docker.com/engine/reference/builder/#user) en la documentación de Docker. - -#### FROM - -La primera instrucción en el `Dockerfile` debe ser `FROM`, la cual selecciona una imagen base de Docker. Para obtener más información, consulta la sección "[FROM reference](https://docs.docker.com/engine/reference/builder/#from) en la documentación de Docker. - -Estas son algunas de las mejores prácticas para configurar el argumento `FROM`: - -- Se recomienda utilizar imágenes oficiales de Docker. Por ejemplo, `python` o `ruby`. -- Utiliza una etiqueta de versión si es que existe, preferentemente con una versión mayor. Por ejemplo, utiliza `node:10` en vez de `node:latest`. -- Se recomienda utilizar imágenes de Docker que se basen en el sistema operativo [Debian](https://www.debian.org/). - -#### WORKDIR - -{% data variables.product.product_name %} configura la ruta del directorio de trabajo en la variable de ambiente `GITHUB_WORKSPACE`. No se recomienda utilizar la instrucción `WORKDIR` en tu `Dockerfile`. Antes de que se ejecute la acción, {% data variables.product.product_name %} montará el directorio `GITHUB_WORKSPACE`sobre cualquiera que fuera la ubicación en la imagen de Docker y configurará a `GITHUB_WORKSPACE` como el directorio de trabajo. Para obtener más información, consulta la sección "[Utilizar variables de ambiente](/actions/configuring-and-managing-workflows/using-environment-variables)" y [WORKDIR reference](https://docs.docker.com/engine/reference/builder/#workdir) en la documentación de Docker. - -#### ENTRYPOINT - -Si defines el `entrypoint` en un archivo de metadatos de una acción, este invalidará el `ENTRYPOINT` definido 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/#runsentrypoint)". - -La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`. Para obtener más información acerca de las formas _exec_ y _shell_, consulta la sección [ENTRYPOINT reference](https://docs.docker.com/engine/reference/builder/#entrypoint) en la documentación de Docker. - -Si configuras tu contenedor para que utilice la forma _exec_ de la instrucción `ENTRYPOINT`, entonces el `args` configurado en el archivo de metadatos de la acción no se ejecutará en un shell de comandos. Si el `args` de la accion contiene una variable de ambiente, ésta no se sustituirá. Por ejemplo, utilizar el siguiente formato _exec_ no imprimirá los valores almacenados en `$GITHUB_SHA`, si no que imprimirá `"$GITHUB_SHA"`. - -``` -ENTRYPOINT ["echo $GITHUB_SHA"] -``` - - Si quieres la sustitución de variables, entonces puedes utilizar la forma _shell_ o ejecutar el shell directamente. Por ejemplo, al utilizar el siguiente formato _exec_ puedes ejecutar un shell para imprimir el valor almacenado en la variable de ambiente `GITHUB_SHA`. - -``` -ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"] -``` - - Para proporcionar el `args` que se definió en el archivo de metadatos de la acción en un contenedor de Docker que utiliza la forma _exec_ en el `ENTRYPOINT`, recomendamos crear un script de shell llamado `entrypoint.sh` al que puedas llamar desde la instrucción `ENTRYPOINT`: - -##### *Dockerfile* de ejemplo -``` -# Container image that runs your code -FROM debian:9.5-slim - -# Copies your code file from your action repository to the filesystem path `/` of the container -COPY entrypoint.sh /entrypoint.sh - -# Executes `entrypoint.sh` when the Docker container starts up -ENTRYPOINT ["/entrypoint.sh"] -``` - -##### Archivo *entrypoint.sh* de ejemplo - -Al utilizar el Dockerfile de ejemplo que se muestra anteriormente, {% data variables.product.product_name %} enviará el `args` configurado en el archivo de metadatos de la acción como un argumento de `entrypoint.sh`. Agrega el `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) hasta arriba del archivo `entrypoint.sh` para utilizar explicitamente el shell compilante [POSIX](https://en.wikipedia.org/wiki/POSIX) del sistema. - -``` sh -#!/bin/sh - -# `$*` expands the `args` supplied in an `array` individually -# or splits `args` in a string separated by whitespace. -sh -c "echo $*" -``` - -Tu código debe ser ejecutable. Asegúrate que el archivo `entrypoint.sh` tiene permisos de `execute` antes de utilizarlo en un flujo de trabajo. Puedes modificar los permisos de tu terminal si utilizas este comando: - ``` sh - chmod +x entrypoint.sh - ``` - -Cuando un script de shell de `ENTRYPOINT` no es ejecutable, recibirás un error similar al siguiente: - -``` sh -Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown -``` - -#### 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 utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos: - -{% data reusables.github-actions.dockerfile-guidelines %} - -### Capacidades de Linux compatibles - -{% data variables.product.prodname_actions %} es compatible con las capacidades predeterminadas de Linux que acepta Docker. Estas capacidades no se pueden añadir ni eliminar. Para obtener más información acerca de las capacidades predeterminadas de Linux con las cuales es compatible Docker, consulta "[Runtime priovilege and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)" en la documentación de Docker. Para conocer más acerca de las capacidades de Linux, consulta "[Overview of Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html) en las páginas man de Linux. diff --git a/translations/es-XL/content/actions/creating-actions/index.md b/translations/es-XL/content/actions/creating-actions/index.md deleted file mode 100644 index 412dc82ca1..0000000000 --- a/translations/es-XL/content/actions/creating-actions/index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Crear acciones -intro: 'Puedes crear tus propias acciones, usar y personalizar acciones compartidas por la comunidad {% data variables.product.prodname_dotcom %} o escribir y compartir las acciones que construyes.' -redirect_from: - - /articles/building-actions - - /github/automating-your-workflow-with-github-actions/building-actions - - /actions/automating-your-workflow-with-github-actions/building-actions - - /actions/building-actions - - /articles/creating-a-github-action/ -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /about-custom-actions - - /creating-a-docker-container-action - - /creating-a-javascript-action - - /creating-a-composite-action - - /metadata-syntax-for-github-actions - - /dockerfile-support-for-github-actions - - /setting-exit-codes-for-actions - - /publishing-actions-in-github-marketplace ---- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/es-XL/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-XL/content/actions/creating-actions/metadata-syntax-for-github-actions.md deleted file mode 100644 index cb11cf33e5..0000000000 --- a/translations/es-XL/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ /dev/null @@ -1,761 +0,0 @@ ---- -title: Sintaxis de metadatos para acciones de GitHub -shortTitle: Sintaxis de metadatos -intro: Puedes crear acciones para realizar tareas en tu repositorio. Las acciones requieren un archivo de metadatos que use la sintaxis YAML. -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /articles/metadata-syntax-for-github-actions - - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions - - /actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions - - /actions/building-actions/metadata-syntax-for-github-actions -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: reference ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### 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)." - -### **`name (nombre)`** - -**Requerido** El nombre de tu acción. {% data variables.product.prodname_dotcom %} muestra el `name` (nombre) en la pestaña **Actions** (Acciones) para ayudarte a identificar visualmente las acciones en cada trabajo. - -### **`autor`** - -**Opcional** El nombre del autor de las acciones. - -### **`descripción`** - -**Requerido** Una descripción breve de la acción. - -### **`inputs (entradas)`** - -**Opcional** Los parámetros de entrada te permiten especificar datos que la acción espera para usar durante el tiempo de ejecución. {% data variables.product.prodname_dotcom %} almacena parámetros de entrada como variables de entorno. Las Id de entrada con letras mayúsculas se convierten a minúsculas durante el tiempo de ejecución. Recomendamos usar Id de entrada en minúsculas. - -#### 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` (con), consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)". - - -```yaml -inputs: - numOctocats: - description: 'Number of Octocats' - required: false - default: '1' - octocatEyeColor: - description: 'Eye color of the Octocats' - required: true -``` - - -Cuando especificas una entrada para una acción en un archivo de flujo de trabajo o usas un valor de entrada predeterminado, {% data variables.product.prodname_dotcom %} crea una variable de entorno para la entrada con el nombre `INPUT_`. La variable de entorno creada convierte los nombre de entrada en letras mayúscula y reemplaza los espacios con los caracteres `_`. - -Por ejemplo, si un flujo de trabajo definió las entradas numOctocats y octocatEyeColor, el código de acción podría leer los valores de las entradas usando las variables de entorno `INPUT_NUMOCTOCATS` y `INPUT_OCTOCATEYECOLOR`. - -#### **`inputs.`** - -**Requerido** Un identificador `string` (cadena) para asociar con la entrada. El valor de `` es un mapa con los metadatos de la entrada. `` debe ser un identificador único dentro del objeto `inputs` (entradas). El ``> debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`. - -#### **`inputs..description`** - -**Requerido** Una descripción de `string` del parámetro de entrada. - -#### **`inputs..required`** - -**Requerido** Un `boolean` (booleano) para indicar si la acción requiere el parámetro de entrada. Establecer en `true` cuando se requiera el parámetro. - -#### **`inputs..default`** - -**Opcional** Una `string` que representa el valor predeterminado. El valor predeterminado se usa cuando un parámetro de entrada no se especifica en un archivo de flujo de trabajo. - -### **`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. - -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)". - -#### Ejemplo - -```yaml -outputs: - sum: # id of the output - description: 'The sum of the inputs' -``` - -#### **`outputs.`** - -**Requerido** Un identificador `string` para asociar con la salida. El valor de `` es un mapa con los metadatos de la salida. `` debe ser un identificador único dentro del objeto `outputs` (salidas). El ``> debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`. - -#### **`outputs..description`** - -**Requerido** Una descripción de `string` del parámetro de salida. - -### **`outputs`** para acciones de pasos de ejecución compuestos - -Los `outputs` **Opcionales** utilizan los mismos parámetros que los `outputs.` and los `outputs..description` (consulta la sección "[`outputs` para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), pero también incluyen el token de `value`. - -#### Ejemplo - -{% raw %} -```yaml -outputs: - random-number: - description: "Random number" - value: ${{ steps.random-number-generator.outputs.random-id }} -runs: - using: "composite" - steps: - - id: random-number-generator - run: echo "::set-output name=random-id::$(echo $RANDOM)" - shell: bash -``` -{% endraw %} - -#### **`outputs.`** -**Requerido** El valor al cual se mapeará el parámetro de salida. Puedes configurarlo a una `string` o a una expresión con contexto. Por ejemplo, puedes utilizar el contexto `steps` para configurar el `value` de una salida al valor de salida de un paso. - -Para obtener más información sobre cómo utilizar la sintaxis de contexto y de expresión, consulta la sección "[Sintaxis de contexto y de expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". - -### **`runs`** para acciones de JavaScript - -**Requerido** Configura la ruta al código de la acción y a la aplicación que se utiliza para ejecutar dicho código. - -#### Ejemplo usando Node.js - -```yaml -runs: - using: 'node12' - main: 'main.js' -``` - -#### **`runs.using`** - -**Requerido** La aplicación utilizada para el código especificado en [`main`](#runsmain). - -#### **`runs.main`** - -**Requerido** El archivo que contiene tu código de acción. La aplicación especificada en [`using`](#runsusing) ejecuta este archivo. - -#### **`pre`** - -**Opcional** Te permite ejecutar un script al inicio de un job, antes de que la acción `main:` comience. Por ejemplo, puedes utilizar `pre:` para ejecutar un script de configuración de pre-requisitos. La aplicación especificada con la sintaxis [using](#runsusing) (mediante) ejecutará este archivo. La acción `pre:` siempre se ejecuta predeterminadamente pero puedes invalidarla utilizando [`pre-if`](#pre-if). - -En este ejemplo, la acción `pre:` ejecuta un script llamado `setup.js`: - -```yaml -runs: - using: 'node12' - pre: 'setup.js' - main: 'index.js' - post: 'cleanup.js' -``` - -#### **`pre-if`** - -**Opcional** Te permite definir las condiciones para la ejecución de la acción `pre:`. La acción `pre:` únicamente se ejecutará si se cumplen las condiciones en `pre-if`. Si no se configura, `pre-if` se configurará predefinidamente como `always()`. Nota que el contexto `step` no está disponible, ya que no se ha ejecutado ningún paso todavía. - -En este ejemplo, `cleanup.js` se ejecuta únicamente en los ejecutores basados en linux: - -```yaml - pre: 'cleanup.js' - pre-if: 'runner.os == linux' -``` - -#### **`publicación`** - -**Opcional** Te permite ejecutar un script al final de un job, una vez que se haya completado la acción `main:`. Por ejemplo, puedes utilizar `post:` para finalizar algunos procesos o eliminar los archivos innecesarios. La aplicación especificada con la sintaxis [using](#runsusing) (mediante) ejecutará este archivo. - -En este ejemplo, la acción `post:` ejecuta un script llamado `cleanup.js`: - -```yaml -runs: - using: 'node12' - main: 'index.js' - post: 'cleanup.js' -``` - -La acción `post:` siempre se ejecuta predeterminadamente, pero la puedes invalidar utilizando `post-if`. - -#### **`post-if`** - -**Opcional** Te permite definir condiciones para la ejecución de la acción `post:`. La acción `post` únicamente se ejecutará si se cumplen las condiciones en `post-if`. Si no se configura, `pre-if` se configurará predeterminadamente como `always()`. - -Por ejemplo, este `cleanup.js` únicamente se ejecutará en ejecutores basados en Linux: - -```yaml - post: 'cleanup.js' - post-if: 'runner.os == linux' -``` - -### **`runs`** para acciones de pasos de ejecución compuestos - -**Requerido** Configura la ruta a la acción compuesta, y la aplicación que se utiliza para ejecutar el código. - -#### **`runs.using`** - -**Requerido** Para utilizar una acción de pasos de ejecución compuestos, configúrala como `"composite"`. - -#### **`runs.steps`** - -**Requerido** Los pasos de ejecución que planeas ejecutar en esta acción. - -##### **`runs.steps.run`** - -**Requerido** El comando que quieres ejecutar. Este puede estar dentro de la línea o ser un script en tu repositorio de la acción: -```yaml -runs: - using: "composite" - steps: - - run: ${{ github.action_path }}/test/script.sh - shell: bash -``` - -Como alternativa, puedes utilizar `$GITHUB_ACTION_PATH`: - -```yaml -runs: - using: "composite" - steps: - - run: $GITHUB_ACTION_PATH/script.sh - shell: bash -``` - -Para obtener más información, consulta la sección "[``](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". - -##### **`runs.steps.shell`** - -**Requerido** El shell en donde quieres ejecutar el comando. Puedes utilizar cualquiera de los shells listados [aquí](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell). - -##### **`runs.steps.name`** - -**Opcional** El nombre del paso de ejecución compuesto. - -##### **`runs.steps.id`** - -**Opcional** Un identificador único para el paso. Puede usar el `id` para hacer referencia al paso en contextos. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". - -##### **`runs.steps.env`** - -**Opcional** Configura un `map` de variables de ambiente únicamente para este paso. Si quieres modificar la variable de ambiente en el flujo de trabajo, utiliza `echo "::set-env name={name}::{value}"` en un paso de ejecución compuesto. - -##### **`runs.steps.working-directory`** - -**Opcional** Especifica el directorio de trabajo en donde se ejecuta un comando. - -### **`runs`** para acciones de Docker - -**Requerido** Configura la imagen utilizada para la acción de Docker. - -#### Ejemplo utilizando un Dockerfile en tu repositorio - -```yaml -runs: - using: 'docker' - image: 'Dockerfile' -``` - -#### Ejemplo usando un contenedor de registro Docker público - -```yaml -runs: - using: 'docker' - image: 'docker://debian:stretch-slim' -``` - -#### **`runs.using`** - -**Requerido** Debes configurar este valor como `'docker'`. - -#### **`pre-entrypoint`** - -**Opcional** Te permite ejecutar un script antes de que comience la acción `entrypoint`. Por ejemplo, puedes utilizar `pre-entrypoint` para ejecutar un script de configuración de pre-requisitos. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción, y ejecuta el script dentro de un contenedor nuevo que utiliza la misma imagen base. Esto significa que el estado del tiempo de ejecución difiere de el contenedor principal `entrypoint`, y se deberá acceder a cualquier estado que requieras ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `pre-entrypoint:` siempre se ejecuta predeterminadamente pero la puedes invalidar utilizando [`pre-if`](#pre-if). - -La aplicación especificada con la sintaxis [using](#runsusing) (mediante) ejecutará este archivo. - -En este ejemplo, la acción `pre.entrypoint:` ejecuta un script llamado `setup.sh`: - -```yaml -runs: - using: 'docker' - image: 'Dockerfile' - args: - - 'bzz' - pre-entrypoint: 'setup.sh' - entrypoint: 'main.sh' -``` - -#### **`runs.image`** - -**Requerido** La imagen de Docker a utilizar como el contenedor para ejecutar la acción. El valor puede ser el nombre de la imagen base de Docker, un `Dockerfile` local en tu repositorio, o una imagen pública en Docker Hub u otro registro. Para hacer referencia a un `Dockerfile` local en tu repositorio, usa una ruta relativa a tu archivo de metadatos de acción. La aplicación `docker` ejecutará este archivo. - -#### **`runs.env`** - -**Opcional** Especifica mapa clave/de valores de las variables del ambiente para configurar en el ambiente del contenedor. - -#### **`runs.entrypoint`** - -**Opcional** Invalida el `ENTRYPOINT` de Docker en el `Dockerfile`, o lo configura si no se había especificado anteriormente. Utiliza `entrypoint` cuando el `Dockerfile` no especifique un `ENTRYPOINT` o cuando quieras invalidar la instrucción de `ENTRYPOINT`. Si omites el `entrypoint`, se ejecutarán los comandos que especifiques en la instrucción `ENTRYPOINT` de Docker. La instrucción `ENTRYPOINT` de Docker tiene una forma de _shell_ y una de _exec_. La documentación de `ENTRYPOINT` de Docker recomienda utilizar la forma de _exec_ de la instrucción `ENTRYPOINT`. - -Para obtener más información acerca de cómo se ejecuta el `entrypoint`, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)". - -#### **`post-entrypoint`** - -**Opcional** Te permite ejecutar un script de limpieza una vez que se haya completado la acción de `runs.entrypoint`. {% data variables.product.prodname_actions %} utiliza `docker run` para lanzar esta acción. Ya que {% data variables.product.prodname_actions %} ejecuta el script dentro de un contenedor nuevo utilizando la misma imagen base, el estado de tiempo de ejecución es diferente del contenedor principal de `entrypoint`. Puedes acceder a cualquier estado que necesites, ya sea en el espacio de trabajo, `HOME`, o como una variable `STATE_`. La acción `post-entrypoint:` siempre se ejecuta predeterminadamente, pero puedes invalidarla utilizando [`post-if`](#post-if). - -```yaml -runs: - using: 'docker' - image: 'Dockerfile' - args: - - 'bzz' - entrypoint: 'main.sh' - post-entrypoint: 'cleanup.sh' -``` - -#### **`runs.args`** - -**Opcional** Una matriz de secuencias que defina las entradas para un contenedor de Docker. Las entradas pueden incluir cadenas codificadas de forma rígida. {% data variables.product.prodname_dotcom %} comunica los `args`en el `ENTRYPOINT` del contenedor cuando se inicia el contenedor. - -Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si usas `CMD` en tu `Dockerfile`, usa los lineamientos ordenados por preferencia: - -{% data reusables.github-actions.dockerfile-guidelines %} - -Si necesitas pasar variables de ambiente a una acción, asegúrate que ésta ejecute un shell de comandos para realizar la sustitución de variables. Por ejemplo, si se configura tu atributo `entrypoint` como `"sh -c"`, entoces `args` se ejecutará en un shell de comandos. Como alternativa, si tu `Dockerfile` utiliza un `ENTRYPOINT` para ejecutar el mismo comando (`"sh -c"`), entonces `args` se ejecutará en un shell de comandos. - -Para obtener más información sobre el uso de la instrucción `CMD` con {% data variables.product.prodname_actions %}, consulta la sección "[Soporte de Dockerfile para {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)". - -##### Ejemplo - -{% raw %} -```yaml -runs: - using: 'docker' - image: 'Dockerfile' - args: - - ${{ inputs.greeting }} - - 'foo' - - 'bar' -``` -{% endraw %} - -### **`branding (marca)`** - -Puedes usar un color y un icono [Pluma](https://feathericons.com/) para crear un distintivo para personalizar y distinguir tu acción. Las insignias se muestran junto a tu nombre de la acción en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). - -#### Ejemplo - -```yaml -branding: - icon: 'award' - color: 'green' -``` - -#### **`branding.color`** - -El color de fondo de la insignia. Puede ser: `blanco`, `amarillow`, `azul`, `verde`, `anaranjado`, `rojo`, `púrpura` o `gris oscuro`. - -#### **`branding.icon`** - -El nombre del icono de [Pluma](https://feathericons.com/) que se debe usar. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    actividadradiodifusiónalerta-círculoalerta-octágono
    alerta-triánguloalinear-centroalinear-justificaralinear-izquierda
    alinear-derechaanclaaperturaarchivar
    flecha-abajo-círculoflecha-abajo-izquierdaflecha-abajo-derechaflecha-abajo
    flecha-izquierda-círculoflecha-izquierdaflecha-derecha-círculoflecha-derecha
    flecha-arriba-círculoflecha-arriba-izquierdaflecha-arriba-derechaflecha-arriba
    en-cartelpremiobarra-cuadro-2barra-cuadro
    batería-cargabateríacampana-apagadocampana
    bluetoothnegritalibro-abiertolibro
    marcadorcajamaletíncalendario
    cámara-apagadocámaramoldeverificar-círculo
    verificar-cuadradoverificarcomilla angular-abajocomilla angular-izquierda
    comillas angulares-derehcacomilla angular- arribacomillas angulares-abajocomillas angulares-izquierda
    comillas angulares-derechacomillas angulares- arribacírculoportapapeles
    relojnube-lloviznanube-rayonube-apagado
    nube-lluvianube-nievenubecódigo
    comandobrújulacopiarángulo-abajo-izquierdo
    ángulo-abajo-derechoángulo-izquierdo-abajoángulo-arriba-izquierdoángulo-derecho-abajo
    ángulo-derecho-arribaángulo-arriba-izquierdoángulo-arriba-derechacpu
    tarjeta-de-créditocortarpunto de mirabase de datos
    eliminardiscodólar-signodescargar-nube
    descargargotaeditar-2editar-3
    editarexterno-enlacedesviar la miradaojo
    facebookavance rápidoplumaarchivo-menos
    archivo-másarchivo-textoarchivopelícula
    filtrobanderacarpeta-menoscarpeta-más
    carpetaobsequiogit-ramagit-confirmar
    git-fusionargit-solicitud-extracciónglobocuadrícula
    disco-durohashauricularescorazón
    ayuda-círculohogarimagenbandeja de entrada
    infocursivacapasdiseño
    vida-boyaenlace-2enlacelista
    cargadorbloqueariniciar-sesióncerrar-sesión
    correoasignar-pinasignarmaximizar-2
    maximizar -menúmensaje-círculomensaje-cuadrado
    mic-apagadomicminimizar-2minimizar
    menos-círculomenos-cuadradomenosmonitor
    lunamás-horizontalmás-verticalmover
    músicanavegación-2navegaciónoctágono
    paquetesujetapapelespausa-círculopausar
    porcentajellamada-telefónicateléfono-transferenciateléfono-entrante
    teléfono-perdidoteléfono-apagadoteléfono-salidateléfono
    gráfico-circularreproducir-círculoreproducirmás-círculo
    más-cuadradomásbolsillopotencia
    impresoraradioactualizar-ccwactualizar-cw
    repetirretrocederrotar-ccwrotar-cw
    rssguardartijerasbuscar
    enviarservidorparámetroscompartir-2
    compartirescudo-apagarescudobolsa-de-compras
    carro-de-comprasaleatoriobarra lateralomitir-atrás
    omitir-adelantebarradeslizadoressmartphone
    parlantecuadradoestrelladetener-círculo
    solamaneceratardecertablet
    etiquetadestinoterminaltermómetro
    pulgares-abajopulgares-arribaalternar-izquierdaalternar-derecha
    papelera-2papeleratendencia-abajotendencia-arriba
    triángulocamiónTVtype
    paraguassubrayardesbloquearcargar-nube
    cargarusuario-comprobarusuario-menosusuario-más
    usuario-xusuariousuariosvideo-apagar
    videocorreo de vozvolumen-1volumen-2
    volumen-xvolumenverwifi-apagar
    wifivientox-círculox-cuadrado
    xdestruir-apagadodestruiracercarse
    alejarse
    diff --git a/translations/es-XL/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/es-XL/content/actions/creating-actions/publishing-actions-in-github-marketplace.md deleted file mode 100644 index e62e69c6cb..0000000000 --- a/translations/es-XL/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Publicar acciones en GitHub Marketplace -intro: 'Puedes publicar acciones en {% data variables.product.prodname_marketplace %} y compartir acciones que has creado con la comunidad de {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /github/automating-your-workflow-with-github-actions/publishing-actions-in-github-marketplace - - /actions/automating-your-workflow-with-github-actions/publishing-actions-in-github-marketplace - - /actions/building-actions/publishing-actions-in-github-marketplace -versions: - fpt: '*' -type: how_to ---- - -Debes aceptar los términos de servicio para publicar acciones en {% data variables.product.prodname_marketplace %}. - -### Acerca de la publicación de acciones - -Antes de que puedas publicar una acción, deberás crear una acción en tu repositorio. Para obtener más información, consulta la sección "[Crear acciones](/actions/creating-actions)". - -Cuando planeas publicar tu acción en {% data variables.product.prodname_marketplace %}, necesitarás asegurarte de que el repositorio solo incluya el archivo de metadatos, el código y los archivos necesarios para la acción. Crear un repositorio único para la acción te permite etiquetar, lanzar y empaquetar el código en una sola unidad. {% data variables.product.prodname_dotcom %} también usa los metadatos de la acción en tu página de {% data variables.product.prodname_marketplace %}. - -Las acciones se publican en {% data variables.product.prodname_marketplace %} inmediatamente y no son revisadas por {% data variables.product.prodname_dotcom %} siempre que cumplan con estos requisitos: - -- La acción debe estar en un repositorio público. -- Cada repositorio debe contener una única acción. -- El archivo de metadatos de la acción (`action.yml` o `action.yaml`) debe estar en el directorio raíz del repositorio. -- El `Nombre` en el archivo de metadatos de la acción debe ser único. - - El `Nombre` no debe coincidir con el nombre de una acción existente publicada en {% data variables.product.prodname_marketplace %}. - - El `Nombre` no debe coincidir con un usuario u organización en {% data variables.product.prodname_dotcom %}, excepto que el usuario o el propietario de la organización publique la acción. Por ejemplo, solo la organización {% data variables.product.prodname_dotcom %} puede publicar una acción denominada `Github`. - - El `Nombre` no debe coincidir con una categoría existente de {% data variables.product.prodname_marketplace %}. - - {% data variables.product.prodname_dotcom %} reserva los nombres de las funciones de {% data variables.product.prodname_dotcom %}. - -### Publicar una acción - -Puedes agregar la acción que has creado para {% data variables.product.prodname_marketplace %} etiquetándola como un lanzamiento nuevo y publicándola. - -Para preparar un nuevo lanzamiento y publicar la acción en {% data variables.product.prodname_marketplace %}, sigue estas instrucciones: - -{% data reusables.repositories.navigate-to-repo %} -1. Cuando un repositorio contiene un archivo de metadatos de acción (`action.yml` o `action.yaml`), verás un mensaje emergente para publicar la acción en {% data variables.product.prodname_marketplace %}. Haz clic en **Draft a release (Crear el borrador de un lanzamiento)**. ![Publicar esta acción en el botón de Marketplace](/assets/images/help/repository/publish-github-action-to-markeplace-button.png) -1. Selecciona **Publish this action to the (Publicar esta acción en) {% data variables.product.prodname_marketplace %}**. Si no puedes seleccionar la casilla de verificación **Publish this action to the (Publicar esta acción en) {% data variables.product.prodname_marketplace %}**, deberás leer y aceptar el acuerdo primero {% data variables.product.prodname_marketplace %}. ![Selecciona publicar en Marketplace](/assets/images/help/repository/marketplace_actions_publish.png) -1. Si las etiquetas en tu archivo de metadatos contienen algún problema, verás un mensaje de error. ![Ver notificación](/assets/images/help/repository/marketplace_actions_fixerrors.png) -1. Si ves alguna sugerencia en pantalla, la solucionas actualizando tu archivo de metadatos. Una vez que esté completo, verás un mensaje "Everything looks Good" (Todo se ve bien). ![Corregir errores](/assets/images/help/repository/marketplace_actions_looksgood.png) -1. Elige una "Primary Category" (Categoría principal) y, de manera opcional, "Another Category" (Otra categoría) que ayudará a las personas a encontrar tu acción en {% data variables.product.prodname_marketplace %}. ![Elegir categoría](/assets/images/help/repository/marketplace_actions_categories.png) -1. Etiqueta tu acción con una versión y agrega un título de lanzamiento. Esto permite que las personas conozcan qué cambios o características incluye el lanzamiento. Las personas verán la versión en la página dedicada a la acción de {% data variables.product.prodname_marketplace %}. ![Etiquetar una versión](/assets/images/help/repository/marketplace_actions_version.png) -1. Completa todos los demás campos y haz clic en **Publish release (Publicar versión)**. La publicación requiere que uses la autenticación de dos factores. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication/)". ![Publica el lanzamiento](/assets/images/help/repository/marketplace_actions_publishrelease.png) - -### Eliminar una acción de {% data variables.product.prodname_marketplace %} - -Para eliminar una acción publicada del {% data variables.product.prodname_marketplace %}, necesitarás actualizar cada lanzamiento publicado. Realiza los siguientes pasos para cada lanzamiento de la acción que has publicado en {% data variables.product.prodname_marketplace %}. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.releases %} -3. En la página Lanzamientos, a la derecha del lanzamiento que deseas editar, haz clic en **Editar**. ![Botón Editar lanzamiento](/assets/images/help/releases/release-edit-btn.png) -4. Selecciona **Publish this action to the (Publicar esta acción en) {% data variables.product.prodname_marketplace %}** para eliminar el tilde de la casilla. ![Botón para publicar esta acción](/assets/images/help/repository/actions-marketplace-unpublish.png) -5. Haz clic en **Update release (Actualizar versión)** en la parte inferior de la página. ![Botón para actualizar el lanzamiento](/assets/images/help/repository/actions-marketplace-update-release.png) diff --git a/translations/es-XL/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/es-XL/content/actions/creating-actions/setting-exit-codes-for-actions.md deleted file mode 100644 index 15e18de48b..0000000000 --- a/translations/es-XL/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Configurar códigos de salida para acciones -shortTitle: Configurar códigos de salida -intro: 'Puedes usar códigos de salida para establecer el estado de una acción. {% data variables.product.prodname_dotcom %} muestra los estados para indicar las acciones que se pasan o fallan.' -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /actions/building-actions/setting-exit-codes-for-actions -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: how_to ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de los códigos de salida - -{% data variables.product.prodname_dotcom %} utiliza el código de salida para configurar el estado de verificación de ejecución de las acciones, el cual puede ser `success` o `failure`. - -| Estado de salida | Estado de ejecución de verificación | Descripción | -| ---------------------- | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `0` | `success` | La acción se completó con éxito y pueden comenzar otras tareas que dependen de ella. | -| Valor distinto de cero | `failure` | Cualquier otro código de salida indica que la acción fracasó. Cuando una acción fracasa, todas las acciones simultáneas se cancelan y las acciones futuras se omiten. La ejecución de verificación y el conjunto de verificaciones obtienen un estado `failure`. | - -### Establecer un código de salida fallida en una acción JavaScript - -Si vas a crear una acción JavaScript, puedes usar el paquete del kit de herramientas [`@actions/core`](https://github.com/actions/toolkit/tree/master/packages/core) para registrar un mensaje y establecer un código de salida fallida. Por ejemplo: - -```javascript -try { - // something -} catch (error) { - core.setFailed(error.message); -} -``` - -Para obtener más información, consulta "[Crear una acción JavaScript](/articles/creating-a-javascript-action)". - -### Establecer un código de salida fallida en una acción de contenedor Docker - -Si vas a crear una acción de contenedor Docker, puedes establecer un código de salida fallida en tu script `entrypoint.sh`. Por ejemplo: - -``` -if ; then - echo "Game over!" - exit 1 -fi -``` - -Para obtener más información, consulta "[Crear una acción de contenedor Docker](/articles/creating-a-docker-container-action)". diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/es-XL/content/actions/hosting-your-own-runners/about-self-hosted-runners.md deleted file mode 100644 index af63895c14..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Acerca de los ejecutores autoalojados -intro: 'Puedes alojar tus propios ejecutores y personalizar el entorno utilizado para ejecutar trabajos en tus flujos de trabajo de {% data variables.product.prodname_actions %}.' -redirect_from: - - /github/automating-your-workflow-with-github-actions/about-self-hosted-runners - - /actions/automating-your-workflow-with-github-actions/about-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: overview ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### 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. - -Puedes agregar ejecutores auto-hospedados en varios niveles dentro de la jerarquía de administración: -- Los ejecutores a nivel de repositorio están dedicados a un solo repositorio. -- Los ejecutores a nivel de organización pueden procesar jobs para varios repositorios dentro de una organización. -- Los ejecutores a nivel de empresa puede asignarse a varias organizaciones en una cuenta empresarial. - -La máquina de tu ejecutor se conecta a{% data variables.product.product_name %} utilizando la aplicación para ejecutores auto-hospedados de {% data variables.product.prodname_actions %}. {% data reusables.github-actions.runner-app-open-source %} Cuando se lanza una nueva versión, la aplicación del ejecutor se actualiza automáticamente cuando se asigna un job al ejecutor, o dentro de una semana de lanzamiento si dicho ejecutor no se ha asignado a ningún job. - -{% 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 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 - -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. -- Son administrados y mantenidos por {% data variables.product.prodname_dotcom %}. -- 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:** -- 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 - -Puedes utilizar cualquier máquina como ejecutor auto-hospedado mientras cumpla con los siguientes requisitos: - -* Puedes instalar y ejecutar la aplicación del ejecutor autoalojado en la máquina. Para obtener más información, consulta "[Sistemas operativos compatibles para ejecutores autoalojados](#supported-operating-systems-for-self-hosted-runners)." -* 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)." -* 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. - -### Sistemas operativos compatibles para ejecutores autoalojados - -Los siguientes sistemas operativos son compatibles con la aplicación del ejecutor auto-hospedado. - -#### Linux - -- Red Hat Enterprise Linux 7 -- CentOS 7 -- Oracle Linux 7 -- Fedora 29 o posterior -- Debian 9 o posterior -- Ubuntu 16.04 o posterior -- Linux Mint 18 o posterior -- openSUSE 15 o posterior -- SUSE Enterprise Linux (SLES) 12 SP2 o posterior - -#### Windows - -- Windows 7 64-bit -- Windows 8.1 64-bit -- Windows 10 64-bit -- Windows Server 2012 R2 64-bit -- Windows Server 2016 64-bit -- Windows Server 2019 64-bit - -#### MacOS - -- macOS 10.13 (High Sierra) o posterior - -{% if currentVersion != "free-pro-team@latest" %} - -### La comunicación entre ejecutores autoalojados y {% 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)." - -{% endif %} - -### 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 trabajos de {% data variables.product.prodname_actions %}. - -{% if currentVersion == "free-pro-team@latest" %} - -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. - -``` -github.com -api.github.com -*.actions.githubusercontent.com -``` - -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](/github/setting-up-and-managing-organizations-and-teams/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-account/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 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)." - -### Seguridad de ejecutores autoalojdados con repositorios públicos - -{% data reusables.github-actions.self-hosted-runner-security %} - -Esto no es un problema con los ejecutores alojados en {% data variables.product.prodname_dotcom %} porque cada ejecutor alojado 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 no confiables que se ejecuten en tu ejecutor auto-hospedado representan riesgos de seguridad significativos para tu máquina y tu ambiente de red, especialmente si tu máquina persiste su ambiente entre jobs. Algunos de estos riesgos incluyen: - -* Programas maliciosos que se ejecutan en la máquina. -* Escapar del entorno Sandbox del ejecutor de la máquina. -* Exponer el acceso al entorno de red de la máquina. -* Mantener datos peligrosos o no deseados en la máquina. diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/es-XL/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md deleted file mode 100644 index 12449c3ce9..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Agregar ejecutores autoalojados -intro: 'Puedes agregar un ejecutor auto-hospedado a {% data variables.product.prodname_actions %}.' -redirect_from: - - /github/automating-your-workflow-with-github-actions/adding-self-hosted-runners - - /actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-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)." - -{% warning %} - -**Advertencia:** {% data reusables.github-actions.self-hosted-runner-security %} - -Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." - -{% endwarning %} - -### Agregar un ejecutor auto-hospedado a un repositorio - -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 un repositorio de la organización, debes ser propietario de la organización o tener acceso de administrador al repositorio. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -1. Debajo de "ejecutores auto-hospedados", da clic en **Agregar ejecutor**. -{% data reusables.github-actions.self-hosted-runner-configure %} -{% data reusables.github-actions.self-hosted-runner-check-installation-success %} - -### 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. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.settings-sidebar-actions %} -1. Debajo de "Ejecutores auto-hospedados", da clic en **Agregar nuevo** y luego en **Ejecutor nuevo**. -{% data reusables.github-actions.self-hosted-runner-configure %} -{% data reusables.github-actions.self-hosted-runner-check-installation-success %} - -### 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" %} -Para agregar un ejecutor auto-hospedado a una cuenta empresarial, debes ser un propietario de la empresa. -{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21"%} -Para agregar un ejecutor auto-hospedado al nivel de una empresa de {% data variables.product.product_location %}, debes ser un administrador de sitio. -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21"%} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% endif %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -1. Da clic en la pestaña de **Ejecutores auto-hospedados**. -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)". -{% data reusables.github-actions.self-hosted-runner-configure %} -{% data reusables.github-actions.self-hosted-runner-check-installation-success %} diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/es-XL/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md deleted file mode 100644 index b8ad02c57c..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -title: Configurar la aplicación del ejecutor autoalojado como un servicio -intro: Puedes configurar la aplicación del ejecutor autoalojado como un servicio para iniciar automáticamente la aplicación del ejecutor cuando se inicia la máquina. -redirect_from: - - /actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial -defaultPlatform: linux ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -{% 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 %} -{% capture service_nonwindows_intro %} Debes agregar un ejecutor a {% data variables.product.product_name %} antes de que puedas configurar la aplicación del ejecutor auto-hospedado como servicio. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."{% endcapture %} -{% capture service_win_name %}actions.runner.*{% endcapture %} - - -{% linux %} - -{{ service_nonwindows_intro }} - -Para los sistemas Linux que usan `systemd`, puedes usar el script `svc.sh` distribuido con la aplicación del ejecutor autoalojado para instalar y administrar el uso de la aplicación como un servicio. - -{{ service_non_windows_intro_shell }} - -{% endlinux %} - -{% windows %} - -{% note %} - -**Nota:** Configurar la aplicación del ejecutor autoalojado como un servicio en Windows es parte del proceso de configuración de la aplicación. Si ya configuraste la aplicación del ejecutor auto-hospedado pero no elegiste configurarla como servicio, debes eliminar el ejecutor de {% data variables.product.prodname_dotcom %} y volver a configurar la aplicación. Cuando vuelvas a configurar la aplicación, elige la opción para configurar la aplicación como un servicio. - -Para obtener más información, consulta "[Eliminar ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners) y [Agregar ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners)." - -{% endnote %} - -Puedes administrar el servicio de ejecutor en la aplicación de **Servicios** de Windows, o puedes usar PowerShell para ejecutar los comandos que se indican a continuación. - -{% endwindows %} - -{% mac %} - -{{ service_nonwindows_intro }} - -{{ service_non_windows_intro_shell }} - -{% endmac %} - -{% linux %} - -### Instalar el servicio - -{{ service_first_step }} -1. Instala el servicio con el siguiente comando: - - ```shell - sudo ./svc.sh install - ``` - -{% endlinux %} -{% mac %} - -### Instalar el servicio - -{{ service_first_step }} -1. Instala el servicio con el siguiente comando: - - ```shell - ./svc.sh install - ``` -{% endmac %} - -### Iniciar el servicio - -Inicia el servicio con el siguiente comando: - -{% linux %} -```shell -sudo ./svc.sh start -``` -{% endlinux %} -{% windows %} -```shell -Start-Service "{{ service_win_name }}" -``` -{% endwindows %} -{% mac %} -```shell -./svc.sh start -``` -{% endmac %} - -### Comprobar el estado del servicio - -Verifica el estado del servicio con el siguiente comando: - -{% linux %} -```shell -sudo ./svc.sh status -``` -{% endlinux %} -{% windows %} -```shell -Get-Service "{{ service_win_name }}" -``` -{% endwindows %} -{% mac %} -```shell -./svc.sh status -``` -{% endmac %} - - Para obtener más información sobre la visualización del estado de tu ejecutor auto-hospedado, consulta la sección "[Monitoreo y solución de problemas para ejecutores auto-hospedados](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)". - -### Detener el servicio - -Detiene el servicio con el siguiente comando: - -{% linux %} -```shell -sudo ./svc.sh stop -``` -{% endlinux %} -{% windows %} -```shell -Stop-Service "{{ service_win_name }}" -``` -{% endwindows %} -{% mac %} -```shell -./svc.sh stop -``` -{% endmac %} - -### Desinstalar el servicio - -1. Detiene el servicio si se está ejecutando actualmente. -1. Desinstala el servicio con el siguiente comando: - - {% linux %} - ```shell - sudo ./svc.sh uninstall - ``` - {% endlinux %} - {% windows %} - ```shell - Remove-Service "{{ service_win_name }}" - ``` - {% endwindows %} - {% mac %} - ```shell - ./svc.sh uninstall - ``` - {% endmac %} - - -{% linux %} - -### Personalizar el servicio del ejecutor auto-hospedado - -Si no quieres utilizar la configuración de servicio predeterminada para `systemd` antes mencionada, puedes crear un servicio personalizado o utilizar cualquier mecanismo de servicio que prefieras. Considera utilizar la plantilla de `serviced` en `actions-runner/bin/actions.runner.service.template` como referencia. Si utilizas un servicio personalizado, el servicio del ejecutor auto-hospedado siempre debe invocarse utilizando el punto de entrada `runsvc.sh`. - -{% endlinux %} - -{% mac %} - -### Personalizar el servicio del ejecutor auto-hospedado - -Si no quieres utilizar la configuración predeterminada del servicio launchd antes mencionada, puedes crear un servicio personalizado o cualquier mecanismo de servicio que prefieras. Considera utilizar la plantilla de `plist` en `actions-runner/bin/actions.runner.plist.template` como referencia. Si utilizas un servicio personalizado, el servicio del ejecutor auto-hospedado siempre debe invocarse utilizando el punto de entrada `runsvc.sh`. - -{% endmac %} diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/index.md b/translations/es-XL/content/actions/hosting-your-own-runners/index.md deleted file mode 100644 index f6a1531b73..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Alojar tus propios corredores -intro: Puedes crear ejecutores autohospedados para ejecutar flujos de trabajo en un entorno altamente personalizable. -redirect_from: - - /github/automating-your-workflow-with-github-actions/hosting-your-own-runners - - /actions/automating-your-workflow-with-github-actions/hosting-your-own-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /about-self-hosted-runners - - /adding-self-hosted-runners - - /autoscaling-with-self-hosted-runners - - /configuring-the-self-hosted-runner-application-as-a-service - - /using-a-proxy-server-with-self-hosted-runners - - /using-labels-with-self-hosted-runners - - /using-self-hosted-runners-in-a-workflow - - /managing-access-to-self-hosted-runners-using-groups - - /monitoring-and-troubleshooting-self-hosted-runners - - /removing-self-hosted-runners ---- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/es-XL/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md deleted file mode 100644 index fe7b5bc3f0..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Administrar el acceso a los ejecutores auto-hospedados utilizando grupos -intro: Puedes utilizar políticas para limitar el acceso a los ejecutores auto-hospedados que se hayan agregado a una organización o empresa. -redirect_from: - - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de los grupos de ejecutores auto-hospedados - -{% if currentVersion == "free-pro-team@latest" %} -{% note %} - -**Nota:** Todas las organizaciones tienen un solo grupo de ejecutores auto-hospedados predeterminado. Solo las cuentas empresariales y las organizaciones que pertenezcan a una cuenta empresarial pueden crear y administrar grupos adicionales de ejecutores auto-hospedados. - -{% endnote %} -{% endif %} - -Los grupos de ejecutores auto-hospedados se utilizan para controlar el acceso a los ejecutores auto-hospedados a nivel de empresas y organizaciones. Los administradores de la empresa pueden configurar políticas de acceso que controlan qué organizaciones en la empresa tienen acceso al grupo de ejecutores. Los administradores de las organizaciones pueden configurar políticas de acceso que controlen qué repositorios en una organización tienen acceso al grupo de ejecutores. - -Cuando un administrador de empresa otorga acceso a una organización para un grupo de ejecutores, los administradores de organización pueden ver que dicho grupo se lista en la configuración del ejecutor auto-hospedado de la organización. Los administradores de la organización pueden entonces asignar políticas de acceso adicionales para repositorios granulares en el grupo de ejecutores de la empresa. - -Cuando se crean nuevos ejecutores, se asignan automáticamente al grupo predeterminado. Los ejecutores solo pueden estar en un grupo a la vez. Puedes mover los ejecutores del grupo predeterminado a otro grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](#moving-a-self-hosted-runner-to-a-group)". - -### Crear un grupo de ejecutores auto-hospedados para una organización - -Todas las organizaciones tienen un solo grupo predeterminado de ejecutores auto-hospedados. Las organizaciones dentro de una cuenta empresarial pueden crear grupos auto-hospedados adicionales. Los administradores de la organización pueden permitir el acceso de los repositorios individuales a un grupo de ejecutores. - -Los ejecutores auto-hospedados se asignan automáticamente al grupo predeterminado cuando se crean y solo pueden ser miembros de un grupo a la vez. Puedes mover un ejecutor del grupo predeterminado a cualquier grupo que crees. - -Cuando creas un grupo, debes elegir una política que defina qué repositorios tienen acceso al grupo ejecutor. Puedes configurar un grupo ejecutor para que una lista específica de repositorios tenga acceso a él, o para que todos los repositorios de la organización lo tengan. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.settings-sidebar-actions %} -1. En la sección de **Ejecutores auto-hospedados** da clic en **Agregar nuevo** y luego en **Grupo nuevo**. - - ![Agregar un grupo de ejecutores](/assets/images/help/settings/actions-org-add-runner-group.png) -1. Ingresa un nombre para tu grupo ejecutor y selecciona una política de acceso de la lista desplegable **Acceso al repositorio**. - - ![Agregar opciones de un grupo de ejecutores](/assets/images/help/settings/actions-org-add-runner-group-options.png) -1. Da clic en **Guardar grupo** para crear el grupo y aplicar la política. - -### Crear un grupo de ejecutores auto-hospedados para una empresa - -Las empresas pueden agregar sus ejecutores auto-hospedados a grupos para su administración de accesos. Las empresas pueden crear grupos de ejecutores auto-hospedados a los cuales puedan acceder organizaciones específicas en la cuenta empresarial. Los administradores de la organización pueden entonces asignar políticas de acceso adicionales para los repositorios granulares a estos grupos de ejecutores para las empresas. - -Los ejecutores auto-hospedados se asignan automáticamente al grupo predeterminado cuando se crean y solo pueden ser miembros de un grupo a la vez. Puedes asignar el ejecutor a un grupo específico durante el proceso de registro o puedes moverlo después desde el grupo predeterminado a un grupo personalizado. - -Cuando creas un grupo, debes elegir una política que otorgue acceso a todas las organizaciones en la empresa o elegir las organizaciones específicas por separado. - -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21"%} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% endif %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -1. Da clic en la pestaña de **Ejecutores auto-hospedados**. -1. Da clic en **Agregar nuevo** y luego en **Grupo nuevo**. - - ![Agregar un grupo de ejecutores](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) -1. Ingresa un nombre para tu grupo ejecutor y selecciona una política de acceso desde la lista desplegable de **Acceso a la organización**. - - ![Agregar opciones de un grupo de ejecutores](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png) -1. Da clic en **Guardar grupo** para crear el grupo y aplicar la política. - -### Cambiar la política de acceso de un grupo de ejecutores auto-hospedados - -Puedes actualizar la política de acceso de un grupo ejecutor o renombrarlo. - -{% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} - -### Mover un ejecutor auto-hospedado a un grupo - -Los ejecutores auto-hospedados nuevos se asignan automáticamente al grupo predeterminado y entonces pueden moverse a otro grupo. - -1. En la sección **Ejecutores auto-hospedados** de la página de configuración, ubica el grupo actual del ejecutor que quieras mover de grupo y expande la lista de miembros de dicho 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) - -### Eliminar un grupo de ejecutores auto-hospedados - -Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina. - -1. En la sección de **Ejecutores auto-hospedados** de la página de configuración, ubica el grupo que quieras eliminar y da 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) - -1. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**. diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/es-XL/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md deleted file mode 100644 index bb0d839005..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -title: Monitorear y solucionar problemas para los ejecutores auto-hospedados -intro: Puedes monitorear tus ejecutores auto-hospedados para ver su actividad y diagnosticar problemas comunes. -redirect_from: - - /actions/hosting-your-own-runners/checking-the-status-of-self-hosted-runners - - /github/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners - - /actions/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial -defaultPlatform: linux ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Comprobar el estado de un ejecutor autoalojado utilizando {% 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) - - El estado puede ser uno de los siguientes: - - * **Idle (Inactivo)**: El ejecutor está conectado a {% data variables.product.product_name %} y está listo para ejecutar puestos de trabajo. - * **Active (Activo)**: Actualmente, el ejecutor está ejecutando un puesto de trabajo. - * **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 - -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 - -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 - -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: - -```shell -$ cat ~/actions-runner/.service -actions.runner.octo-org-octo-repo.runner01.service -``` - -Puedes utilizar `journalctl` para monitorear la actividad del ejecutor auto-hospedado en tiempo real: - -```shell -$ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f -``` - -En este ejemplo de salida, puedes ver como inicia `runner01`, recibe un job llamado `testAction`, y luego muestra el estado resultante: - -```shell -Feb 11 14:57:07 runner01 runsvc.sh[962]: Starting Runner listener with startup type: service -Feb 11 14:57:07 runner01 runsvc.sh[962]: Started listener process -Feb 11 14:57:07 runner01 runsvc.sh[962]: Started running service -Feb 11 14:57:16 runner01 runsvc.sh[962]: √ Connected to GitHub -Feb 11 14:57:17 runner01 runsvc.sh[962]: 2020-02-11 14:57:17Z: Listening for Jobs -Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Running job: testAction -Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Job testAction completed with result: Succeeded -``` - -Para ver la configuración de systemd, puedes ubicar archivo de servicio aquí: `/etc/systemd/system/actions.runner.-..service`. Si quieres personalizar el servicio de la aplicación del ejecutor auto-hospedado, no modifiques directamente este archivo. Sigue las instrucciones descritas en la sección "[Configurar la aplicación del ejecutor auto-hospedado como un servicio](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)". - -{% endlinux %} - -{% mac %} - -### 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: - -```shell -% cat ~/actions-runner/.service -/Users/exampleUsername/Library/LaunchAgents/actions.runner.octo-org-octo-repo.runner01.plist -``` - -El script `svc.sh` utiliza `launchctl` para revisar si la aplicación se está ejecutando. Por ejemplo: - -```shell -$ ./svc.sh status -status actions.runner.example.runner01: -/Users/exampleUsername/Library/LaunchAgents/actions.runner.example.runner01.plist -Started: -379 0 actions.runner.example.runner01 -``` - -La salida generada incluye la ID del proceso y el nombre del servicio launchd de la aplicación. - -Para ver la configuración de launchd, puedes ubicar el archivo del servicio aquí: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. Si quieres personalizar el servicio de la aplicación del ejecutor auto-hospedado, no modifiques directamente este archivo. Sigue las instrucciones descritas en la sección "[Configurar la aplicación del ejecutor auto-hospedado como un servicio](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)". - -{% endmac %} - - -{% windows %} - -### 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: - -```shell -PS C:\actions-runner> Get-Content .service -actions.runner.octo-org-octo-repo.runner01.service -``` - -Puedes ver el estado del ejecutor en la aplicación _Services_ de Windows (`services.msc`). También puedes utilizar PowerShell para revisar si el servicio se está ejecutando: - -```shell -PS C:\actions-runner> Get-Service "actions.runner.octo-org-octo-repo.runner01.service" | Select-Object Name, Status -Name Status ----- ------ -actions.runner.octo-org-octo-repo.runner01.service Running -``` - -Puedes utilizar PowerShell para revisar la actividad reciente del ejecutor auto-hospedado. En este ejemplo de salida, puedes ver que la aplicación comienza, recibe un job llamado `testAction`, y después muestra el estado resultante: - -```shell -PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerService - - Index Time EntryType Source InstanceID Message - ----- ---- --------- ------ ---------- ------- - 136 Mar 17 13:45 Information ActionsRunnerService 100 2020-03-17 13:45:48Z: Job Greeting completed with result: Succeeded - 135 Mar 17 13:45 Information ActionsRunnerService 100 2020-03-17 13:45:34Z: Running job: testAction - 134 Mar 17 13:41 Information ActionsRunnerService 100 2020-03-17 13:41:54Z: Listening for Jobs - 133 Mar 17 13:41 Information ActionsRunnerService 100 û Connected to GitHub - 132 Mar 17 13:41 Information ActionsRunnerService 0 Service started successfully. - 131 Mar 17 13:41 Information ActionsRunnerService 100 Starting Actions Runner listener - 130 Mar 17 13:41 Information ActionsRunnerService 100 Starting Actions Runner Service - 129 Mar 17 13:41 Information ActionsRunnerService 100 create event log trace source for actions-runner service -``` - -{% endwindows %} - -### 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. - -Puedes ver las actividades de actualización en los archivos de bitácora *Runner_*. Por ejemplo: - -```shell -[Feb 12 12:37:07 INFO SelfUpdater] An update is available. -``` - -Adicionalmente, puedes encontrar más información en los archivos de bitácora _SelfUpdate_ ubicados en el directorio `_diag`. - -{% linux %} - -### Solucionar problemas en los contenedores de los ejecutores auto-hospedados - -#### 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. - -Puedes utilizar `systemctl` para revisar el estado del servicio: - -```shell -$ sudo systemctl is-active docker.service -active -``` - -Si no se ha instalado Docker, entonces las acciones dependientes fallarán con los siguientes errores: - -```shell -[2020-02-13 16:56:10Z INFO DockerCommandManager] Which: 'docker' -[2020-02-13 16:56:10Z INFO DockerCommandManager] Not found. -[2020-02-13 16:56:10Z ERR StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker' -``` - -#### Revisar los permisos de Docker - -Si tu job falla con el siguiente error: - -```shell -dial unix /var/run/docker.sock: connect: permission denied -``` - -Revisa que la cuenta de servicio del ejecutor auto-hospedado tenga permiso de utilizar el servicio de Docker. Puedes identificar esta cuenta revisando la configuración del ejecutor auto-hospedado en systemd. Por ejemplo: - -```shell -$ sudo systemctl show -p User actions.runner.octo-org-octo-repo.runner01.service -User=runner-user -``` - -{% endlinux %} diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/es-XL/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md deleted file mode 100644 index fab0edca3b..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Eliminar ejecutores autoalojados -intro: 'Puedes eliminar permanentemente un ejecutor auto-hospedado de {% data variables.product.prodname_actions %}.' -redirect_from: - - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners - - /actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Eliminar un ejecutor de un repositorio - -{% note %} - -**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} - -{% data reusables.github-actions.self-hosted-runner-auto-removal %} - -{% endnote %} - -Para eliminar un ejecutor auto-hospedado de un repositorio e usuario debes ser el propietario del mismo. Para un repositorio de la organización, debes ser propietario de la organización o tener acceso de administrador al repositorio. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. - -{% data reusables.github-actions.self-hosted-runner-reusing %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} - -### Eliminar el ejecutor de una organización - -{% note %} - -**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} - -{% data reusables.github-actions.self-hosted-runner-auto-removal %} - -{% 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. - -{% data reusables.github-actions.self-hosted-runner-reusing %} - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.repositories.settings-sidebar-actions %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} - -### Eliminar un ejecutor de una empresa - -{% note %} - -**Nota:** {% data reusables.github-actions.self-hosted-runner-removal-impact %} - -{% data reusables.github-actions.self-hosted-runner-auto-removal %} - -{% endnote %} - -{% if currentVersion == "free-pro-team@latest" %} -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. -{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21"%} -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. -{% endif %} - -{% data reusables.github-actions.self-hosted-runner-reusing %} - -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.enterprise-accounts.access-enterprise %} -{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21"%} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% endif %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -{% data reusables.github-actions.self-hosted-runner-removing-a-runner %} diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/es-XL/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md deleted file mode 100644 index 4ea92a8e82..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Usar un servidor proxy con ejecutores autoalojados -intro: 'Puedes configurar los ejecutores autoalojados para usar un servidor proxy para comunicarte con {% data variables.product.product_name %}.' -redirect_from: - - /actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Configurar un servidor proxy mediante variables de entorno - -Si necesitas un ejecutor autoalojado para comunicarte a través de un servidor proxy, la aplicación del ejecutor autoalojado usa configuraciones de proxy establecidas en las siguientes variables de entorno: - -* `https_proxy`: URL del proxy para el tráfico HTTPS. También puedes incluir credenciales de autenticación básicas, si es necesario. Por ejemplo: - * `http://proxy.local` - * `http://192.168.1.1:8080` - * `http://username:password@proxy.local` -* `http_proxy`: URL del proxy para el tráfico HTTP. También puedes incluir credenciales de autenticación básicas, si es necesario. Por ejemplo: - * `http://proxy.local` - * `http://192.168.1.1:8080` - * `http://username:password@proxy.local` -* `no_proxy`: Lista de hosts separados por comas que no deberían usar un proxy. Solo se permiten nombres de host en `no_proxy`, no puedes usar direcciones IP. Por ejemplo: - * `example.com` - * `example.com,myserver.local:443,example.org` - -Las variables de entorno de proxy se leen cuando se inicia la aplicación del ejecutor autoalojado, por lo que debes establecer las variables de entorno antes de configurar o iniciar la aplicación del ejecutor autoalojado. Si cambia la configuración de tu proxy, debes reiniciar la aplicación del ejecutor autoalojado. - -En las máquinas Windows, los nombres de las variables de entorno proxy no distinguen mayúsculas de minúsculas. En las máquinas Linux y macOS, te recomendamos que uses todas las variables de entorno en minúsculas. Si tienes una variable de entorno tanto en minúsculas como en mayúsculas en Linux o macOS, por ejemplo `https_proxy` y `HTTPS_PROXY`, la aplicación del ejecutor autoalojado usa la variable de entorno en minúscula. - -### Usar un archivo.env para establecer la configuración del proxy - -Si establecer variables de entorno no es práctico, puedes establecer las variables de configuración de proxy en un archivo llamado _.env_ en el directorio de la aplicación del ejecutor autoalojado. Por ejemplo, esto puede ser necesario si deseas configurar la aplicación del ejecutor como un servicio en una cuenta de sistema. Cuando se inicia la aplicación del ejecutor, lee las variables establecidas en _.env_ para la configuración del proxy. - -A continuación se muestra un ejemplo de configuración del proxy _.env_: - -``` -https_proxy=http://proxy.local:8080 -no_proxy=example.com,myserver.local:443 -``` - -### Establecer la configuración del proxy para contenedores Docker - -Si usas las acciones del contenedor Docker o los contenedores de servicio en tus flujos de trabajo, es posible que también debas configurar Docker para usar tu servidor proxy además de establecer las variables de entorno anteriores. - -Para obtener información sobre la configuración de Docker que se necesita, consulta "[Configurar Docker para usar un servidor proxy](https://docs.docker.com/network/proxy/)" en la documentación de Docker. diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/es-XL/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md deleted file mode 100644 index 373775e977..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Utilizar etiquetas con ejecutores auto-hospedados -intro: Puedes utilizar etiquetas para organizar tus ejecutores auto-hospedados según sus características. -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -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)". - -{% data reusables.github-actions.self-hosted-runner-management-permissions-required %} - -### Crear una etiqueta personalizada - -{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} -{% data reusables.github-actions.self-hosted-runner-list %} -{% data reusables.github-actions.self-hosted-runner-list-group %} -{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} -1. En el campo "Filtrar etiquetas", teclea el nombre de tu nueva etiqueta y da clic en **Crear nueva etiqueta**. ![Etiqueta de agregar ejecutor](/assets/images/help/settings/actions-add-runner-label.png) - -La etiqueta personalizada se creará y asignará al ejecutor auto-hospedado. Las etiquetas personalizadas pueden eliminarse de los ejecutores auto-hospedados, pero actualmente no pueden eliminarse manualmente. {% data reusables.github-actions.actions-unused-labels %} - -### Asignar una etiqueta a un ejecutor auto-hospedado - -{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} -{% data reusables.github-actions.self-hosted-runner-list %} -{% data reusables.github-actions.self-hosted-runner-list-group %} -{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} -1. Da clic en la etiqueta para asignarla a tu ejecutor auto-hospedado. - -### Eliminar una etiqueta personalizada de un ejecutor auto-hospedado - -{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} -{% data reusables.github-actions.self-hosted-runner-list %} -{% data reusables.github-actions.self-hosted-runner-list-group %} -{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %} -1. Da clic en la etiqueta asignada para eliminarla de tu ejecutor auto-hospedado. {% data reusables.github-actions.actions-unused-labels %} - -### Utilizar el script de configuración para crear y asignar etiquetas - -Puedes utilizar el script de configuración en el ejecutor auto-hospedado para crear y asignar etiquetas personalizadas. Por ejemplo, este comando asigna una etiqueta llamada `gpu` al ejecutor auto-hospedado. - -```shell -./config.sh --labels gpu -``` - -La etiqueta se creará si no existe. También puedes utilizar este acercamiento para asignar etiquetas predeterminadas a los ejecutores, tales como `x64` o `linux`. Cuando se asignan etiquetas predeterminadas utilizando el script de configuración, {% data variables.product.prodname_actions %} las acepta como asignadas y no valida si el ejecutor está utilizando ese sistema operativo o arquitectura. - -Puedes utilizar separación por comas para asignar etiquetas múltiples. Por ejemplo: - -```shell -./config.sh --labels gpu,x64,linux -``` - -{% note %} - -** Nota:** Si reemplazaste un ejecutor existente, entonces deberás volver a asignar cualquier etiqueta personalizada. - -{% endnote %} diff --git a/translations/es-XL/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/es-XL/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md deleted file mode 100644 index 4919ed2b95..0000000000 --- a/translations/es-XL/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Usar ejecutores autoalojados en un flujo de trabajo -intro: 'Para usar los ejecutores autoalojados en un flujo de trabajo, puedes usar etiquetas para especificar el tipo de ejecutores para un trabajo.' -redirect_from: - - /github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow - - /actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow -versions: - fpt: '*' - ghes: '*' - ghae: '*' -type: tutorial ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -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)". - -### Usar ejecutores autoalojados en un flujo de trabajo - -Las etiquetas te permiten enviar jobs de flujo de trabajo a tipos específicos de ejecutores auto-hospedados, de acuerdo con sus características compartidas. Por ejemplo, si tu job requiere una componente de hardware o paquete de software específico, puedes asignar una etiqueta personalizada a un ejecutor y después configurar tu job para que solo se ejecute en los ejecutores con esta etiqueta. - -{% data reusables.github-actions.self-hosted-runner-labels-runs-on %} - -Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)". - -### Utilizar etiquetas predeterminadas para enrutar jobs - -Un ejecutor auto-hospedado recibe ciertas etiquetas automáticamente cuando se agrega a {% data variables.product.prodname_actions %}. Estas se utilizan para indicar su sistema operativo y plataforma de hardware: - -* `autoalojado`: Etiqueta por defecto aplicada a todos los ejecutores autoalojados. -* `linux`, `windows`, o `macOS`: Se aplican dependiendo del sistema operativo. -* `x86`, `x64`, `ARM`, o `ARM64`: Se aplican dependiendo de la arquitectura del hardware. - -Puedes utilizar el YAML de tu flujo de trabajo para mandar jobs a las diferentes combinaciones de estas etiquetas. En este ejemplo, un ejecutor auto-hospedado que empate con las tres etiquetas será elegible para ejecutar el job: - -```yaml -runs-on: [self-hosted, linux, ARM64] -``` - -- `self-hosted` - Ejecuta este job en un ejecutor auto-hospedado. -- `linux` - Utiliza únicamente un ejecutor basado en Linux. -- `ARM64` - Utiliza únicamente un ejecutor basado en hardware ARM64. - -Las etiquetas predeterminadas son fijas y no se pueden cambiar ni eliminar. Considera utilizar etiquetas personalizadas si necesitas más control sobre el enrutamiento de los jobs. - -### Utilizar etiquetas personalizadas para enrutar jobs - -Puedes crear etiquetas personalizadas y asignarlas a tus ejecutores auto-hospedados en cualquier momento. Las etiquetas personalizadas te permiten enviar jobs a tipos particulares de ejecutores auto-hospedados, basándose en cómo se etiquetan. - -Por ejemplo, si tienes un job que requiere un tipo específico de hardware de gráficos, puedes crear una etiqueta personalizada llamada `gpu` y asignarla a los ejecutores que tengan instalado este hardware. Un ejecutor auto-hospedado que empate con las etiquetas asignadas será entonces elegible para ejecutar el job. - -Este ejemplo muestra un job que combina etiquetas predeterminadas y personalizadas: - -```yaml -runs-on: [self-hosted, linux, x64, gpu] -``` - -- `self-hosted` - Ejecuta este job en un ejecutor auto-hospedado. -- `linux` - Utiliza únicamente un ejecutor basado en Linux. -- `x64` - Utiliza únicamente un ejecutor basado en hardware x64. -- `gpu` - Esta etiqueta personalizada se asignó manualmente a los ejecutores auto-hospedados con hardware de GPU instalado. - -Estas etiquetas operan acumulativamente, así que las etiquetas de un ejecutor auto-hospedado deberán empatar con los cuatro criterios para poder ser elegibles para procesar el job. - -### Precedencia de enrutamiento para los ejecutores auto-hospedados - -Si utilizas ejecutores tanto a nivel de repositorio como a nivel de organización, {% data variables.product.prodname_dotcom %} sigue un orden de precedencia cuando enruta los jobs hacia los ejecutores auto-hospedados: - -1. Se procesan las etiquetas de `runs-on` del job. Entonces, {% data variables.product.prodname_dotcom %} intenta ubicar un ejecutor que coincida con los requisitos de la etiqueta: -2. El job se envía a un ejecutor a nivel de repositorio que coincida con las etiquetas del mismo. Si no hay un ejecutor a nivel de repositorio disponible (ya sea que esté ocupado, sin conexión, o no tenga etiquetas que coincidan): -3. El job se envía a un ejecutor de nivel organizacional que coincida con las etiquetas del mismo. Si hay un ejecutor de nivel organizacional disponible, el la solicitud del job falla con un error. diff --git a/translations/es-XL/content/actions/index.md b/translations/es-XL/content/actions/index.md deleted file mode 100644 index a57214431a..0000000000 --- a/translations/es-XL/content/actions/index.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Documentación de GitHub Actions -shortTitle: GitHub Actions -intro: 'Automatiza, personaliza y ejecuta tus flujos de trabajo de desarrollo de software directamente en tu repositorio con {% data variables.product.prodname_actions %}. Puedes descubrir, crear y compartir acciones para realizar cualquier trabajo que quieras, incluido CI/CD, y combinar acciones en un flujo de trabajo completamente personalizado.' -featuredLinks: - guides: - - /actions/learn-github-actions - - /actions/guides/about-continuous-integration - - /actions/guides/about-packaging-with-github-actions - - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting - guideCards: - - /actions/guides/setting-up-continuous-integration-using-workflow-templates - - /actions/guides/publishing-nodejs-packages - - /actions/guides/building-and-testing-powershell - popular: - - /actions/learn-github-actions/workflow-syntax-for-github-actions - - /actions/learn-github-actions - - /actions/learn-github-actions/events-that-trigger-workflows - - /actions/learn-github-actions/contexts - - /actions/learn-github-actions/expressions - - /actions/learn-github-actions/environment-variables - - /actions/security-guides/encrypted-secrets -redirect_from: - - /articles/automating-your-workflow-with-github-actions/ - - /articles/customizing-your-project-with-github-actions/ - - /github/automating-your-workflow-with-github-actions - - /actions/automating-your-workflow-with-github-actions/ - - /categories/automating-your-workflow-with-github-actions - - /marketplace/actions - - /actions/guides - - /actions/reference -layout: product-landing -versions: - fpt: '*' - ghes: '*' - ghae: '*' -introLinks: - overview: /actions/learn-github-actions/understanding-github-actions - quickstart: /actions/quickstart -changelog: - label: actions - prefix: 'GitHub Actions: ' -product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU' -children: - - /quickstart - - /learn-github-actions - - /creating-actions - - /security-guides - - /automating-builds-and-tests - - /deployment - - /managing-issues-and-pull-requests - - /publishing-packages - - /using-containerized-services - - /advanced-guides - - /managing-workflow-runs - - /monitoring-and-troubleshooting-workflows - - /using-github-hosted-runners - - /hosting-your-own-runners - - /migrating-to-github-actions ---- - diff --git a/translations/es-XL/content/actions/reference/context-and-expression-syntax-for-github-actions.md b/translations/es-XL/content/actions/reference/context-and-expression-syntax-for-github-actions.md deleted file mode 100644 index 381587aa6d..0000000000 --- a/translations/es-XL/content/actions/reference/context-and-expression-syntax-for-github-actions.md +++ /dev/null @@ -1,475 +0,0 @@ ---- -title: Sintaxis de contexto y de expresiones para acciones de GitHub -shortTitle: Sintaxis de contexto y de expresiones -intro: Puedes acceder a información de contexto y evaluar expresiones en flujos de trabajo y acciones. -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /articles/contexts-and-expression-syntax-for-github-actions - - /github/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions - - /actions/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions - - /actions/reference/contexts-and-expression-syntax-for-github-actions -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' - github-ae: '*' ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de los contextos y 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 literales, referencias de contexto y funciones usando operadores. - -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. - -Debes usar una sintaxis específica para decirle a {% data variables.product.prodname_dotcom %} que evalúe una expresión en lugar de tratarla como una cadena. - -{% raw %} -`${{ }}` -{% endraw %} - -{% data reusables.github-actions.expression-syntax-if %} Para obtener más información acerca de los condicionales `if`, consulta la sección "[sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)". - -#### Expresión de ejemplo en un condicional `if` - -```yaml -steps: - - uses: actions/hello-world-javascript-action@v1.1 - if: {% raw %}${{ }}{% endraw %} -``` - -#### Ejemplo de parámetros en una variable de entorno - -{% raw %} -```yaml -env: - my_env_var: ${{ }} -``` -{% endraw %} - -### Contextos - -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. - -{% raw %} -`${{ }}` -{% endraw %} - -| Nombre del contexto | Tipo | Descripción | -| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `github` | `objeto` | Información sobre la ejecución del flujo de trabajo. Para obtener más información, consulta [github context](#github-context). | -| `env` | `objeto` | Contiene variables de entorno establecidas en un flujo de trabajo, trabajo o paso. Para obtener más información, consulta contexto de [`env`](#env-context). | -| `job` | `objeto` | Información sobre el trabajo actualmente en ejecución. Para obtener más información, consulta contexto de [`job`](#job-context). | -| `pasos` | `objeto` | Información sobre los pasos que se han ejecutado en este trabajo. Para obtener más información, consulta contexto de [`steps`](#steps-context). | -| `runner` | `objeto` | Incluye información sobre el ejecutor que está realizando el trabajo actual. Para más información, consulta [Contexto del `ejecutador (runner)`](#runner-context). | -| `secrets` | `objeto` | Habilita el acceso a los secretos. Para más información sobre secretos, consulta "[Creando y usando secretos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." | -| `strategy` | `objeto` | Brinda acceso a los parámetros de estrategia configurados y a la información sobre el puesto actual. Los parámetros de estrategia incluyen `fail-fast`, `job-index`, `job-total` y `max-parallel`. | -| `matrix` | `objeto` | Brinda acceso a los parámetros de la matriz que configuraste para el puesto actual. Por ejemplo, si configuraste una matriz de construcción con las versiones `os` y `node`, el objeto de contexto `matrix` incluye las versiones `os` y `node` del puesto actual. | -| `needs` | `objeto` | Habilita el acceso de las salidas de todos los jobs que se definen como una dependencia para el job actual. Para obtener más información, consulta [`needs` context](#needs-context). | - -Como parte de una expresión, puedes acceder a la información del contexto usando una de dos sintaxis. -- Sintaxis de índice: `github['sha']` -- Sintaxis de desreferencia de propiedad: `github.sha` - -Para usar la sintaxis de desreferencia de propiedad, el nombre de la propiedad debe cumplir con lo siguiente: -- comenzar con `a-Z` o `_`. -- estar seguida por `a-Z` `0-9` `-` o `_`. - -#### **contexto `github`** - -El contexto de `github` contiene información sobre la ejecución del flujo de trabajo y el evento que desencadenó la ejecución. Puedes leer la mayoría de los datos de contexto de `github` en las variables del entorno. Para más información sobre las variables de entorno, consulta "[Utilizando variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)." - -{% data reusables.github-actions.github-context-warning %} - -| Nombre de la propiedad | Tipo | Descripción | -| ------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `github` | `objeto` | El contexto de nivel superior disponible durante cualquier trabajo o paso en un flujo de trabajo. | -| `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_path` | `secuencia` | La ruta a la carga del webhook del evento completo en el ejecutor. | -| `github.workflow` | `secuencia` | El nombre del flujo de trabajo. Si el archivo de flujo de trabajo no especifica un `name`, el valor de esta propiedad es la ruta completa del archivo del flujo de trabajo en el repositorio. | -| `github.job` | `secuencia` | El [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) del job actual. | -| `github. run_id` | `secuencia` | {% data reusables.github-actions.run_id_description %} | -| `github. run_number` | `secuencia` | {% data reusables.github-actions.run_number_description %} | -| `github.actor` | `secuencia` | El inicio de sesión del usuario que inició la ejecución del flujo de trabajo. | -| `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.event_name` | `secuencia` | El nombre del evento que activó la ejecución del flujo de trabajo. | -| `github.sha` | `secuencia` | El SHA de confirmación que activó la ejecución del flujo de trabajo. | -| `github.ref` | `secuencia` | La rama o ref de etiqueta que activó la ejecución del flujo de trabajo. | -| `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 una `pull_request`. | -| `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 una `pull_request`. | -| `github.token` | `secuencia` | Un token para autenticar en nombre de la aplicación de GitHub instalada en tu repositorio. Funcionalmente, esto equivale 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.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.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 con las acciones de los pasos de ejecución compuestos. | - -#### **contexto de `env`** - -El contexto de `Env` contiene las variables de entorno que se han establecido en un flujo de trabajo, puesto o paso. Para obtener más información acerca de la configuración de variables de entorno en tu flujo de trabajo, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)". - -La sintaxis de contexto `env` te permite usar el valor de una variable de entorno en tu archivo de flujo de trabajo. Si quieres usar el valor de una variable de entorno dentro de un ejecutor, usa el método normal del sistema operativo del ejecutor para leer las variables de entorno. - -Solo puedes usar el contexto de `env` en el valor de las llaves `with` y `name`, o en un condicional `if` del paso. Para obtener más información sobre la sintaxis del paso, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)". - -| Nombre de la propiedad | Tipo | Descripción | -| ---------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------- | -| `env` | `objeto` | Este contexto cambia para cada paso de un trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | -| `Env.` | `secuencia` | El valor de una variable de entorno específica. | - - -#### **contexto de `job`** - -El contexto `trabajo` contiene información sobre el trabajo de ejecución actual. - -| Nombre de la propiedad | Tipo | Descripción | -| ----------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `job` | `objeto` | Este contexto cambia para cada trabajo de una ejecución de flujo de trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | -| `job.status` | `secuencia` | El estado actual del trabajo. Los valores posibles son `success`, `failure` o `cancelled`. | -| `job.container` | `objeto` | Información sobre el contenedor del trabajo. Para obtener más información sobre los contenedores, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)". | -| `job.container.network` | `secuencia` | La Id. de la red del contenedor. El ejecutor crea la red usada por todos los contenedores en un trabajo. | -| `job.container.id` | `secuencia` | La Id. de la red del contenedor. | -| `job.services` | `objeto` | Los contenedores de servicios creados para un trabajo. Para obtener más información sobre los contenedores de servicios, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)". | -| `job.services..id` | `secuencia` | La Id del contenedor de servicio. | -| `job.services..ports` | `objeto` | Los puertos expuestos del contenedor del servicio. | -| `job.services..network` | `secuencia` | La Id de la red del contenedor de servicio. El ejecutor crea la red usada por todos los contenedores en un trabajo. | - -#### **contexto de `steps`** - -El contexto `steps` contiene información sobre los pasos en el trabajo actual que ya se ha ejecutado. - -| Nombre de la propiedad | Tipo | Descripción | -| --------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `pasos` | `objeto` | Este contexto cambia para cada paso de un trabajo. Puedes acceder a este contexto desde cualquier paso en un trabajo. | -| `steps..outputs` | `objeto` | El conjunto de salidas definido para el paso. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)". | -| `steps..outputs.` | `secuencia` | El valor de un resultado específico. | -| `steps..outcome` | `secuencia` | El resultado de un paso completado antes de que se aplique [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error). Los valores posibles son `success`, `failure`, `cancelled`, o `skipped`. Cuando falla un paso de `continue-on-error`, el `outcome` es `failure`, pero la `conclusion` final es `success`. | -| `steps..conclusion` | `secuencia` | El resultado de un paso completado después de que se aplica [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error). Los valores posibles son `success`, `failure`, `cancelled`, o `skipped`. Cuando falla un paso de `continue-on-error`, el `outcome` es `failure`, pero la `conclusion` final es `success`. | - -#### **Contexto de `runner`** - -El contexto de `runner` contiene información sobre el ejecutor que está ejecutando el trabajo actual. - -| Nombre de la propiedad | Tipo | Descripción | -| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `runner.os` | `secuencia` | El sistema operativo del ejecutor que ejecuta el trabajo. Los valores posibles son `Linux`, `Windows` o `macOS`. | -| `runner.temp` | `secuencia` | La ruta del directorio temporal para el ejecutor. Se garantiza que este directorio estará vacío al inicio de cada trabajo, incluso en los ejecutores autoalojados. | -| `runner.tool_cache` | `secuencia` | La ruta del directorio que contiene algunas de las herramientas preinstaladas para los ejecutores alojados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Software instalado en los ejecutores alojados por GitHub](/actions/automating-your-workflow-with-github-actions/software-installed-on-github-hosted-runners)". | - -#### **Contexto `needs`** - -El contexto `needs` contiene salidas de todos los jobs que se definen como dependencia del job actual. Para obtener más información sobre la definición de dependencias de jobs, consulta la sección "[Sintaxis de flujos de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)". - -| Nombre de la propiedad | Tipo | Descripción | -| -------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------- | -| `needs.` | `objeto` | Un solo job del cual depende el job actual. | -| `needs..result` | `secuencia` | El resultado de un job del cual depende el job actual. Los valores posibles son `success`, `failure` o `cancelled`. | -| `needs..outputs` | `objeto` | El conjunto de resultados de un job del cual depende el job actual. | -| `needs..outputs.` | `secuencia` | El valor de un resultado específico para un job del cual depende el job actual. | - -#### Ejemplo de impresión de información de contexto de un archivo de registro - -Para inspeccionar la información accesible en cada contexto, puedes utilizar este ejemplo de archivo de flujo de trabajo. - -{% data reusables.github-actions.github-context-warning %} - -**.github/workflows/main.yml** -{% raw %} -```yaml -on: push - -jobs: - one: - runs-on: ubuntu-16.04 - steps: - - name: Dump GitHub context - env: - GITHUB_CONTEXT: ${{ toJson(github) }} - run: echo "$GITHUB_CONTEXT" - - name: Dump job context - env: - JOB_CONTEXT: ${{ toJson(job) }} - run: echo "$JOB_CONTEXT" - - name: Dump steps context - env: - STEPS_CONTEXT: ${{ toJson(steps) }} - run: echo "$STEPS_CONTEXT" - - name: Dump runner context - env: - RUNNER_CONTEXT: ${{ toJson(runner) }} - run: echo "$RUNNER_CONTEXT" - - name: Dump strategy context - env: - STRATEGY_CONTEXT: ${{ toJson(strategy) }} - run: echo "$STRATEGY_CONTEXT" - - name: Dump matrix context - env: - MATRIX_CONTEXT: ${{ toJson(matrix) }} - run: echo "$MATRIX_CONTEXT" -``` -{% endraw %} - -### Literales - -Como parte de una expresión, puedes usar tipos de datos `boolean`, `null`, `number` o `string`. Los literales booleanos no distinguen minúsculas de mayúsculas, por lo que puedes usar `true` o `True`. - -| Tipo de datos | Valor literal | -| ------------- | --------------------------------------------------------------------------------------- | -| `boolean` | `true` o `falso` | -| `null` | `null` | -| `number` | Cualquier formato de número compatible con JSON. | -| `secuencia` | Debes usar comillas simples. Escapar comillas simples literales con una comilla simple. | - -#### Ejemplo - -{% raw %} -```yaml -env: - myNull: ${{ null }} - myBoolean: ${{ false }} - myIntegerNumber: ${{ 711 }} - myFloatNumber: ${{ -9.2 }} - myHexNumber: ${{ 0xff }} - myExponentialNumber: ${{ -2.99-e2 }} - myString: ${{ 'Mona the Octocat' }} - myEscapedString: ${{ 'It''s open source!' } }} -``` -{% endraw %} - -### Operadores - -| Operador | Descripción | -| ------------------------- | -------------------------- | -| `( )` | Agrupación lógica | -| `[ ]` | Índice | -| `.` | Desreferencia de propiedad | -| `!` | No | -| `<` | Menos que | -| `<` | Menor o igual | -| `>` | Mayor que | -| `>=` | Mayor o igual | -| `==` | Igual | -| `!=` | No es igual | -| `&&` | Y | -| \|\| | O | - -{% data variables.product.prodname_dotcom %} realiza comparaciones de igualdad flexible. - -* Si los tipos no coinciden, {% data variables.product.prodname_dotcom %} fuerza el tipo a un número. {% data variables.product.prodname_dotcom %} fusiona los tipos de datos con un número usando estas conversiones: - - | Tipo | Resultado | - | ------- | ------------------------------------------------------------------------------------------------------------------------------- | - | Null | `0` | - | Boolean | `true` devuelve `1`
    `falso` devuelve `0` | - | Cadena | Analizado desde cualquier formato de número JSON legal, de lo contrario `NaN`.
    Nota: la cadena vacía devuelve `0`. | - | Array | `NaN` | - | Object | `NaN` | -* Una comparación de un `NaN` con otro `NaN` no genera `true`. Para obtener más información, consulta "[Documentos de Mozilla NaN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)". -* {% data variables.product.prodname_dotcom %} ignora las mayúsculas y minúsculas al comparar cadenas. -* Los objetos y matrices solo se consideran iguales cuando son la misma instancia. - -### Funciones - -{% data variables.product.prodname_dotcom %} ofrece un conjunto de funciones integradas que puedes usar en expresiones. Algunas funciones fusionan valores en una cadena para realizar las comparaciones. {% data variables.product.prodname_dotcom %} fusiona los tipos de datos con una cadena usando estas conversiones: - -| Tipo | Resultado | -| ------- | ------------------------------------------------- | -| Null | `''` | -| Boolean | `'true'` o `'falso'` | -| Number | Formato decimal, exponencial para grandes números | -| Array | Las matrices no se convierten en cadenas | -| Object | Los objetos no se convierten en cadenas | - -#### Contiene - -`contiene (buscar, elemento)` - -Arroja `true` si `search` contiene `item`. Si `search` es una matriz, esta función arroja `true` si el `item` es un elemento de la matriz. Si `search` es una cadena, esta función arroja `true` si el `item` es una subcadena de `search`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena. - -##### Ejemplo usando una matriz - -`contains(github.event.issue.labels.*.name, 'bug')` - -##### Ejemplo usando una cadena - -`contains('Hello world', 'llo')` devuelve `true` - -#### startsWith - -`startsWith( searchString, searchValue )` - -Devuelve `true` cuando `searchString` contiene `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena. - -##### Ejemplo - -`startsWith('Hello world', 'He')` regresa a `true` - -#### endsWith - -`endsWith( searchString, searchValue )` - -Devuelve `true` si `searchString` contiene `searchValue`. Esta función no distingue mayúsculas de minúsculas. Fusiona valores en una cadena. - -##### Ejemplo - -`endsWith('Hello world', 'He')` devuelve `true` - -#### format - -`format( string, replaceValue0, replaceValue1, ..., replaceValueN)` - -Reemplaza valores en la `cadena`, con la variable `replaceValueN`. Las variables en la `cadena` se especifican con la sintaxis `{N}`, donde `N` es un entero. Debes especificar al menos un `replaceValue` y una `cadena`. No existe un máximo para el número de variables (`replaceValueN`) que puedes usar. Escapar llaves usando llaves dobles. - -##### Ejemplo - -Devuelve 'Hello Mona the Octocat' - -`format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')` - -##### Ejemplo de evasión de llaves - -Devuelve '{Hello Mona the Octocat!}' - -{% raw %} -```js -format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat') -``` -{% endraw %} - -#### join - -`join( array, optionalSeparator )` - -El valor para `array` puede ser una matriz o una cadena. Todos los valores en `array` se concatenan en una cadena. Si proporcionas `optionalSeparator`, se inserta entre los valores concatenados. De lo contrario, se usa el separador predeterminado `,`. Fusiona valores en una cadena. - -##### Ejemplo - -`join(github.event.issue.labels.*.name, ', ')` puede devolver 'bug, help wanted' - -#### toJson - -`toJSON(value)` - -Devuelve una representación JSON con formato mejorado de `valor`. Puedes usar esta función para depurar la información suministrada en contextos. - -##### Ejemplo - -`toJSON(job)` puede devolver `{ "status": "Success" }` - -#### fromJson - -`fromJSON(value)` - -Devuelve un objeto de JSON para `value`. Puedes utilizar esta función para proporcionar un objeto de JSON como una expresión evaluada. - -##### Ejemplo - -Este flujo de trabajo configura una matriz de JSON en un job, y lo pasa al siguiente job utilizando un resultado y `fromJSON`. - -{% raw %} -```yaml -name: build -on: push -jobs: - job1: - runs-on: ubuntu-latest - outputs: - matrix: ${{ steps.set-matrix.outputs.matrix }} - steps: - - id: set-matrix - run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}" - job2: - needs: job1 - runs-on: ubuntu-latest - strategy: - matrix: ${{fromJson(needs.job1.outputs.matrix)}} - steps: - - run: build -``` -{% endraw %} - -#### hashFiles - -`hashFiles(path)` - -Arroja un solo hash para el conjunto de archivos que coincide con el patrón de `path`. Puedes proporcionar un patrón de `path` o `path` múltiples se parados por comas. El `path` está relacionado con el directorio `GITHUB_WORKSPACE` y solo puede incluir archivos dentro del directorio `GITHUB_WORKSPACE`. Esta función calcula un hash SHA-256 individual para cada archivo coincidente, y luego usa esos hashes para calcular un hash SHA-256 final para el conjunto de archivos. Para más información sobre SHA-256, consulta "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)". - -Puedes usar caracteres de coincidencia de patrones para encontrar nombres de archivos. La coincidencia de patrones no distingue mayúsculas de minúsculas en Windows. Para obtener más información acerca de los caracteres compatibles con los patrones, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)". - -##### Ejemplo con un solo patrón - -Encuentra cualquier archivo `package-lock.json` en el repositorio. - -`hashFiles('**/package-lock.json')` - -##### Ejemplo con patrones múltiples - -Crea un hash para cualquier archivo de `package-lock.json` y de `Gemfile.lock` en el repositorio. - -`hashFiles('**/package-lock.json', '**/Gemfile.lock')` - -### Funciones de verificación de estado del trabajo - -Puedes usar las siguientes funciones de verificación de estado como expresiones en condicionales `if` (si). Si la expresión `if` no contiene ninguna de las funciones de estado, se obtendrá automáticamente con `success()`. Para obtener información sobre los condicionales `if`, consulta "[Sintaxis de flujo de trabajo para acciones de GitHub](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)". - -#### success - -Arroja `true` cuando no falló ni se canceló ninguno de los pasos anteriores. - -##### Ejemplo - -```yaml -Pasos: - ... - - name: The job has succeeded - if: {% raw %}${{ success() }}{% endraw %} -``` - -#### always - -Siempre arroja `true`, incluso cuando se cancela. No se ejecutará un trabajo o paso cuando una falla crítica impida que la tarea se ejecute. Por ejemplo, si fallaron las fuentes. - -##### Ejemplo - -```yaml -if: {% raw %}${{ always() }}{% endraw %} -``` - -#### cancelled - -Devuelve `true` si se canceló el flujo de trabajo. - -##### Ejemplo - -```yaml -if: {% raw %}${{ cancelled() }}{% endraw %} -``` - -#### failure - -Arroja `true` cuando falla cualquiera de los pasos anteriores de un trabajo. - -##### Ejemplo - -```yaml -Pasos: - ... - - name: The job has failed - if: {% raw %}${{ failure() }}{% endraw %} -``` - -### Filtros de objetos - -Puedes usar la sintaxis `*` para aplicar un filtro y seleccionar los elementos coincidentes en una recopilación. - -Por ejemplo, considera una matriz de objetos llamada `fruits`. - -```json -[ - { "name": "apple", "quantity": 1 }, - { "name": "orange", "quantity": 2 }, - { "name": "pear", "quantity": 1 } -] -``` - -El filtro `fruits.*.name` devuelve la matriz `[ "apple", "orange", "pear" ]` diff --git a/translations/es-XL/content/actions/reference/events-that-trigger-workflows.md b/translations/es-XL/content/actions/reference/events-that-trigger-workflows.md deleted file mode 100644 index 8afcbeec48..0000000000 --- a/translations/es-XL/content/actions/reference/events-that-trigger-workflows.md +++ /dev/null @@ -1,645 +0,0 @@ ---- -title: Eventos que desencadenan flujos de trabajo -intro: 'Puedes configurar tus flujos de trabajo para que se ejecuten cuando ocurre una actividad específica en {% data variables.product.product_name %}, en un horario programado o cuando se produce un evento fuera de {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.actions %}' -miniTocMaxHeadingLevel: 4 -redirect_from: - - /articles/events-that-trigger-workflows - - /github/automating-your-workflow-with-github-actions/events-that-trigger-workflows - - /actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' - github-ae: '*' ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de los eventos de flujo de trabajo - -Puedes configurar tu flujo de trabajo para que se ejecute cuando se creen eventos de webhook a partir de una actividad en {% data variables.product.product_name %}. Los flujos de trabajo pueden usar más de un evento de webhook para desencadenar la ejecución de un flujo de trabajo. Para obtener más información, consulta la sección "[webhooks](/webhooks)". Para obtener más información sobre la sintaxis `on`, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#on)". - -Los siguientes pasos se producen para activar una ejecución de flujo de trabajo: - -1. Se produce un evento en tu repositorio, y el webhook del evento resultante tiene una confirmación de SHA y una referencia de Git asociadas. -1. El directorio `.github/workflows` en tu repositorio se busca para los archivos de flujo de trabajo en la confirmación SHA o la referencia de Git asociadas. Los archivos de flujo de trabajo deben estar presentes en la confirmación SHA o la referencia de Git que se debe tener en cuenta. - - Por ejemplo, si el evento se produjo en una rama particular del repositorio, los archivos de flujo de trabajo deben estar presentes en el repositorio en esa rama. -1. Se inspeccionarán los archivos de flujo de trabajo para esa confirmación de SHA y referencia de Git, y se activará una nueva ejecución de flujo de trabajo para cualquier flujo de trabajo que tenga valores `on:` que coincidan con el evento desencadenante. - - El flujo de trabajo se ejecuta en el código de tu repositorio en la misma confirmación SHA y la referencia de Git que desencadenó el evento. Cuando se ejecuta un flujo de trabajo, {% data variables.product.product_name %} establece las variables de entorno `GITHUB_SHA` (confirmar SHA) y `GITHUB_REF` (referencia de Git) en el entorno del ejecutor. Para obtener más información, consulta "[Usar variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)". - -{% note %} - -**Nota:** No puedes activar nuevas ejecuciones de flujo de trabajo usando el `GITHUB_TOKEN`. Para obtener más información, consulta "[Activar nuevos flujos de trabajo mediante un token de acceso personal](#triggering-new-workflows-using-a-personal-access-token)". - -{% endnote %} - -{% data reusables.github-actions.actions-on-examples %} - -### Eventos de webhook - -Puedes configurar tu flujo de trabajo para que se ejecute cuando se crean eventos de webhook en GitHub. 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. - -#### `check_run` - -Ejecuta tu flujo de trabajo en cualquier momento que se produzca el evento `check_run`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[Ejecuciones de verificación](/v3/checks/runs/)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`check_run`](/webhooks/event-payloads/#check_run) | - `created`
    - `rerequested`
    - `completed`
    - `requested_action` | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una comprobación de ejecución ha sido `resolicitada` o `requested_action`. - -```yaml -on: - check_run: - types: [rerequested, requested_action] -``` - -#### `check_suite` - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `check_suite`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección de "[conjuntos de verificaciones](/v3/checks/suites/)". - -{% data reusables.github-actions.branch-requirement %} - -{% note %} - -**Nota:** Para evitar flujos de trabajo recurrentes, este evento no activa flujos de trabajo si la comprobación de suite fue creada por {% data variables.product.prodname_actions %}. - -{% endnote %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------ | -------------------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`check_suite`](/webhooks/event-payloads/#check_suite) | - `completed`
    - `requested`
    - `rerequested`
    | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una comprobación de ejecución ha sido `resolicitada` o `completada`. - -```yaml -on: - check_suite: - types: [rerequested, completed] -``` - -#### `create (crear)` - -Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una rama o etiqueta, que activa el evento `crear`. Para obtener más información sobre la API de REST, consulta la sección "[Crear una referencia](/v3/git/refs/#create-a-reference)". - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------- | ------------------ | ------------------------------------------------ | ---------------------- | -| [`create (crear)`](/webhooks/event-payloads/#create) | n/a | Última confirmación en la rama o etiqueta creada | Rama o etiqueta creada | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `crear`. - -```yaml -on: - create -``` - -#### `eliminar` - -Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una rama o etiqueta, que activa el evento `eliminar`. Para obtener más información sobre la API de REST, consulta la sección "[Borrar una referencia](/v3/git/refs/#delete-a-reference)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------- | ------------------ | ------------------------------------------ | ---------------- | -| [`eliminar`](/webhooks/event-payloads/#delete) | n/a | Última confirmación en la rama por defecto | Rama por defecto | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `eliminar`. - -```yaml -on: - delete -``` - -#### `deployment` - -Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una implementación, que activa el evento `implementación`. Las implementaciones creadas con SHA de confirmación pueden no tener una referencia de Git. Para obtener más información acerca de la API de REST, consulta la sección "[Despliegues](/v3/repos/deployments/)". - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------- | ------------------ | ------------------------------ | ------------------------------------------------------------------ | -| [`deployment`](/webhooks/event-payloads/#deployment) | n/a | Confirmación de implementación | Rama o etiqueta que se debe implementar (vacío si está confirmada) | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `implementación`. - -```yaml -on: - deployment -``` - -#### `deployment_status` - -Ejecuta tu flujo de trabajo en cualquier momento en que un tercero proporcione un estado de implementación, que activa un evento de `deployment_status`. Las implementaciones creadas con SHA de confirmación pueden no tener una referencia de Git. Para obtener más información acerca de la API de REST, consulta la sección "[Crear un estado de despliegue](/v3/repos/deployments/#create-a-deployment-status)". - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------------------ | ------------------ | ------------------------------ | ------------------------------------------------------------------ | -| [`deployment_status`](/webhooks/event-payloads/#deployment_status) | n/a | Confirmación de implementación | Rama o etiqueta que se debe implementar (vacío si está confirmada) | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `implementación`. - -```yaml -on: - deployment_status -``` - -#### `bifurcación` - -Ejecuta tu flujo de trabajo en cualquier momento en que alguien bifurque un repositorio, lo que activa el evento de `bifurcación`. Para obtener más información sobre la API de REST, consulta la sección "[Crear una bifurcación](/v3/repos/forks/#create-a-fork)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ----------------------------------------------- | ------------------ | ------------------------------------------ | ---------------- | -| [`bifurcación`](/webhooks/event-payloads/#fork) | n/a | Última confirmación en la rama por defecto | Rama por defecto | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento de `bifurcación`. - -```yaml -on: - fork -``` - -#### `gollum` - -Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree o actualice una página Wiki, que activa el evento `gollum`. - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------- | ------------------ | ------------------------------------------ | ---------------- | -| [`gollum`](/webhooks/event-payloads/#gollum) | n/a | Última confirmación en la rama por defecto | Rama por defecto | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `gollum`. - -```yaml -on: - gollum -``` - -#### `comentario_propuesta` - -Ejecuta tu flujo de trabajo en cualquier momento que se produzca el evento `issue_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[comentarios de un informe de problemas](/v3/issues/comments/)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ----------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`comentario_propuesta`](/v3/activity/event_types/#issue_comment) | - `created`
    - `edited`
    - `deleted`
    | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un miembro ha sido `creado` o `eliminado`. - -```yaml -on: - issue_comment: - types: [created, deleted] -``` - -#### `propuestas` - -Ejecuta tu flujo de trabajo en cualquier momento que se produzca el evento de `propuestas`. {% data reusables.developer-site.multiple_activity_types %} Para obtener información acerca de la API de REST, consulta la sección "[informes de problemas](/v3/issues)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`propuestas`](/webhooks/event-payloads/#issues) | - `opened`
    - `edited`
    - `deleted`
    - `transferred`
    - `pinned`
    - `unpinned`
    - `closed`
    - `reopened`
    - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `locked`
    - `unlocked`
    - `milestoned`
    - `demilestoned` | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una propuesta ha sido `abierta`, `editada`, o `marcada como hito`. - -```yaml -on: - issues: - types: [opened, edited, milestoned] -``` - -#### `etiqueta` - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento de `etiquetado`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Etiquetas](/v3/issues/labels/)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| --------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`etiqueta`](/webhooks/event-payloads/#label) | - `created`
    - `edited`
    - `deleted`
    | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un miembro ha sido `creado` o `eliminado`. - -```yaml -on: - label: - types: [created, deleted] -``` - -#### `hito` - -Ejecuta tu flujo de trabajo en cualquier momento que se produzca el evento de `milestone`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Hitos](/v3/issues/milestones/)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`hito`](/webhooks/event-payloads/#milestone) | - `created`
    - `closed`
    - `opened`
    - `edited`
    - `deleted`
    | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un hito ha sido `abierto` o `eliminado`. - -```yaml -on: - milestone: - types: [opened, deleted] -``` - -#### `page_build` - -Ejecuta tu flujo de trabajo en cualquier momento en que alguien suba a una {% data variables.product.product_name %} Rama habilitada para páginas, que activa el evento `page_build`. Para obtener más información acerca de la API de REST, consulta la sección "[Páginas](/v3/repos/pages/)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------- | ------------------ | ------------------------------------------ | ------------ | -| [`page_build`](/webhooks/event-payloads/#page_build) | n/a | Última confirmación en la rama por defecto | n/a | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `page_build`. - -```yaml -on: - page_build -``` - -#### `project` - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento de `project`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Proyectos](/v3/projects/)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`project`](/webhooks/event-payloads/#project) | - `created`
    - `updated`
    - `closed`
    - `reopened`
    - `edited`
    - `deleted`
    | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un proyecto ha sido `creado` o `eliminado`. - -```yaml -on: - project: - types: [created, deleted] -``` - -#### `project_card` - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `project_card`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Tarjetas de proyecto](/v3/projects/cards)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`project_card`](/webhooks/event-payloads/#project_card) | - `created`
    - `moved`
    - `converted` to an issue
    - `edited`
    - `deleted` | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un proyecto ha sido `abierto` o `eliminado`. - -```yaml -on: - project_card: - types: [opened, deleted] -``` - -#### `project_column` - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `project_column`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Columnas de proyecto](/v3/projects/columns)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------------ | --------------------------------------------------------------------------- | ------------------------------------------ | ---------------- | -| [`project_column`](/webhooks/event-payloads/#project_column) | - `created`
    - `updated`
    - `moved`
    - `deleted` | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una columna de proyecto ha sido `creado` o `eliminado`. - -```yaml -on: - project_column: - types: [created, deleted] -``` - -#### `public` - -Ejecuta tu flujo de trabajo en cualquier momento en que alguien haga público un repositorio privado, que activa el evento `público`. Para obtener más información acerca de la API de REST, consulta la sección "[Editar repositorios](/v3/repos/#edit)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------- | ------------------ | ------------------------------------------ | ---------------- | -| [`public`](/webhooks/event-payloads/#public) | n/a | Última confirmación en la rama por defecto | Rama por defecto | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `público`. - -```yaml -on: - public -``` - -#### `solicitud_extracción` - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento de `pull_request`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Solicitudes de extraccións](/v3/pulls)". - -{% note %} - -**Nota:** Por defecto, un flujo de trabajo solo se ejecuta cuando un tipo de actividad `pull_request` está `abierto`, `sincronizado`, o `reabierto`. Para activar los flujos de trabajo para más tipos de actividades, usa la palabra clave `tipos`. - -{% endnote %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------ | -| [`solicitud_extracción`](/webhooks/event-payloads/#pull_request) | - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `opened`
    - `edited`
    - `closed`
    - `reopened`
    - `synchronize`
    - `ready_for_review`
    - `locked`
    - `unlocked`
    - `review_requested`
    - `review_request_removed` | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | - -Puedes extender o limitar los tipos de actividad por defecto usando la palabra clave `types`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)". - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una solicitud de extracción ha sido `assigned` (asignada), `opened`, `syncronize` o `reopened`. - -```yaml -on: - pull_request: - types: [assigned, opened, synchronize, reopened] -``` - -{% data reusables.developer-site.pull_request_forked_repos_link %} - -#### `revisión_solicitud de extracción` - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `pull_request_review`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Revisiones de solicitudes de extracción](/v3/pulls/reviews)". - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ----------------------------------------------------------------------------------- | ---------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------ | -| [`revisión_solicitud de extracción`](/webhooks/event-payloads/#pull_request_review) | - `submitted`
    - `edited`
    - `dismissed` | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una revisión de solicitud de extracción ha sido `editada` o `descartada`. - -```yaml -on: - pull_request_review: - types: [edited, dismissed] -``` - -{% data reusables.developer-site.pull_request_forked_repos_link %} - -#### `comentarios _revisiones_solicitudes de extracción` - -Ejecuta tu flujo de trabajo en cualquier momento en que se modifique una diferencia unificada de solicitud de extracción, que activa el evento `pull_request_review_comment`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección [Revisar comentarios](/v3/pulls/comments). - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------ | ----------------------------------------------------- | ------------------------------------------------ | -| [`comentarios _revisiones_solicitudes de extracción`](/webhooks/event-payloads/#pull_request_review_comment) | - `created`
    - `edited`
    - `deleted` | Última confirmación de fusión en la rama `GITHUB_REF` | Rama de fusión de PR `refs/pull/:prNumber/merge` | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un comentario de revisión de solicitud de extracción ha sido `creado` o `eliminado`. - -```yaml -on: - pull_request_review_comment: - types: [created, deleted] -``` - -{% data reusables.developer-site.pull_request_forked_repos_link %} - -#### `pull_request_target` - -Este evento es similar al de `pull_request`, con la diferencia de que se ejecuta en el contexto del repositorio base de la solicitud de extracción en vez de en la confirmación de fusión. Esto significa que puedes poner tus secretos como disponibles de forma más seguro en los flujos de trabajo que active la solicitud de extracción, ya que solo se ejecutan los flujos de trabajo que se definan en la confirmación del repositorio base. Por ejemplo, este evento te permite crear flujos de trabajo que etiquetan y comentan en las solicitudes de extracción con base en el contenido de la carga útil del evento. - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------------- | -| [`solicitud_extracción`](/webhooks/event-payloads/#pull_request) | - `assigned`
    - `unassigned`
    - `labeled`
    - `unlabeled`
    - `opened`
    - `edited`
    - `closed`
    - `reopened`
    - `synchronize`
    - `ready_for_review`
    - `locked`
    - `unlocked`
    - `review_requested`
    - `review_request_removed` | Última confirmación en la rama base de la solicitud de extracción | Rama base de la solicitud de extracción | - -Predeterminadamente, un flujo de trabajo se ejecuta únicamente cuando el tipo de actividad de un `pull_request_target` se encuentra como `opened`, `synchronize`, o `reopened`. Para activar los flujos de trabajo para más tipos de actividades, usa la palabra clave `tipos`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)". - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando una solicitud de extracción ha sido `assigned` (asignada), `opened`, `syncronize` o `reopened`. - -```yaml -on: pull_request_target - types: [assigned, opened, synchronize, reopened] -``` - -#### `subir` - -{% note %} - -**Nota:** La carga disponible del webhook para las Acciones de GitHub no incluye los atributos `añadidos`, `eliminados`, y `modificados` en el objeto de `confirmación`. Puedes recuperar el objeto de confirmación completo usando la API REST. Para obtener más información, consulta la sección "[Obtener una sola confirmación](/v3/repos/commits/#get-a-single-commit)". - -{% endnote %} - -Ejecuta tu flujo de trabajo cuando alguien sube una rama a tu repositorio, lo que activa el evento `push`. - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ----------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------- | --------------- | -| [`subir`](/webhooks/event-payloads/#push) | n/a | Confirmación subida, a menos que se elimine una rama (cuando se trata de la rama por defecto) | Ref actualizado | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento `push`. - -```yaml -on: - push -``` - -#### `registry_package` - -Ejecuta tu flujo de trabajo en cualquier momento en que un paquete es `publish` (publicado) o `updated` (actualizado). Para obtener más información, consulta "[Administrar paquetes con {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)". - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------------------------------------- | ----------------------------------- | ---------------------------------- | ------------------------------------- | -| [`registry_package`](/webhooks/event-payloads/#package) | - `published`
    - `updated` | Confirmación del paquete publicado | Rama o etiqueta del paquete publicado | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un paquete ha sido `publicado`. - -```yaml -on: - registry_package: - types: [published] -``` - -#### `lanzamiento` - -{% note %} - -**Nota:** El evento `release` no se activará para los lanzamientos en borrador. - -{% endnote %} - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento de `lanzamiento`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información sobre la API de REST, consulta la sección "[Lanzamientos](/v3/repos/releases/)". - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------- | -| [`lanzamiento`](/webhooks/event-payloads/#release) | - `published`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
    - `unpublished`
    - `created`
    - `edited`
    - `deleted`
    - `prereleased`
    - `released`{% endif %} | Última confirmación en el lanzamiento etiquetado | Etiqueta de lanzamiento | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando un lanzamiento ha sido `publicado`. - -```yaml -on: - release: - types: [published] -``` - -#### `estado` - -Ejecuta tu flujo de trabajo en cualquier momento en que alguien cree una rama o etiqueta, que activa el evento `crear`. Para obtener más información acerca de la API de REST, consulta la sección "[Estados](/v3/repos/statuses/)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------- | ------------------ | ------------------------------------------ | ------------ | -| [`estado`](/webhooks/event-payloads/#status) | n/a | Última confirmación en la rama por defecto | n/a | - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando se produzca el evento de `estado`. - -```yaml -on: - status -``` - -#### `ver` - -Ejecuta tu flujo de trabajo en cualquier momento en que se produzca el evento `ver`. {% data reusables.developer-site.multiple_activity_types %} Para obtener más información acerca de la API de REST, consulta la sección "[Marcar con una estrella](/v3/activity/starring/)". - -{% data reusables.github-actions.branch-requirement %} - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------- | ------------------ | ------------------------------------------ | ---------------- | -| [`ver`](/webhooks/event-payloads/#watch) | - `started` | Última confirmación en la rama por defecto | Rama por defecto | - -{% data reusables.developer-site.limit_workflow_to_activity_types %} - -Por ejemplo, puedes ejecutar un flujo de trabajo cuando alguien coloca una estrella en un repositorio, que es el tipo de actividad `comenzado` que activa el evento Ver. - -```yaml -on: - watch: - types: [started] -``` - -#### `workflow_run` - -{% data reusables.webhooks.workflow_run_desc %} - -Si necesitas filtrar las ramas de este evento, puedes utilizar `branches` o `branches-ignore`. - -En este ejemplo, se configuró la ejecución de un flujo de trabajo después de que se completen las "Pruebas de ejecución" por separado para el mismo. - -```yaml -on: - workflow_run: - workflows: ["Run Tests"] - branches: [main] - types: - - completed - - requested -``` - -### Eventos programados - -El evento `schedule` te permite activar un flujo de trabajo en una hora programada. - -#### `programación` - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ------------------------ | ------------------ | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| n/a | n/a | Última confirmación en la rama por defecto | Rama por defecto | Cuando se establece la ejecución del flujo de trabajo programado. Un flujo de trabajo programado usa[sintaxis cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Para obtener más información, consulta "[Desencadenar un flujo de trabajo con eventos](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)". | - -{% data reusables.repositories.actions-scheduled-workflow-example %} - -La sintaxis de cron tiene cinco campos separados por un espacio, y cada campo representa una unidad de tiempo. - -``` -┌───────────── minuto (0 - 59) -│ ┌───────────── hora (0 - 23) -│ │ ┌───────────── día del mes (1 - 31) -│ │ │ ┌───────────── mes (1 - 12 o EN-DIC) -│ │ │ │ ┌───────────── día de la semana (0 - 6 o DOM-SÁB) -│ │ │ │ │ -│ │ │ │ │ -│ │ │ │ │ -* * * * * -``` - -Puedes usar estos operadores en cualquiera de los cinco campos: - -| Operador | Descripción | Ejemplo | -| -------- | -------------------------------- | ----------------------------------------------------------------------------------------------------------- | -| * | Cualquier valor | `* * * * *` se ejecuta todos los días a cada minuto. | -| , | Separador de la lista de valores | `2,10 4,5 * * *` se ejecuta en el minuto 2 y 10 de la cuarta y quinta hora de cada día. | -| - | Rango de valores | `0 4-6 * * *` se ejecuta en el minuto 0 de la cuarta, quinta y sexta hora. | -| / | Valores del paso | `20/15 * * * *` se ejecuta cada 15 minutos a partir del minuto 20 hasta el minuto 59 (minutos 20, 35 y 50). | - -{% note %} - -**Nota:** {% data variables.product.prodname_actions %} no es compatible con la sintaxis que no es estándar `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly` y `@reboot`. - -{% endnote %} - -Puedes usar [contrab guru](https://crontab.guru/) para generar tu sintaxis de cron y confirmar a qué hora se ejecutará. Para que puedas comenzar, hay también una lista de [ejemplos de crontab guru](https://crontab.guru/examples.html). - -### Eventos manuales - -Puedes activar ejecuciones de flujo de trabajo manualmente. Para activar flujos de trabajo específicos en un repositorio, utiliza el evento `workflow_dispatch`. Para activar más de un flujo de trabajo en un repositorio y crear eventos personalizados y tipos de eventos, utiliza el evento `repository_dispatch`. - -#### `workflow_dispatch` - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| ---------------------------------------------------------------- | ------------------ | ---------------------------------------------- | ------------------------- | -| [workflow_dispatch](/webhooks/event-payloads/#workflow_dispatch) | n/a | Última confirmacion en la rama de `GITHUB_REF` | Rama que recibió el envío | - -Puedes activar una ejecución de flujo de trabajo manualmente si utilizas la API de {% data variables.product.product_name %} y desde {% data variables.product.product_name %}. Para activar el evento de webhook personalizado de `workflow_dispatch` utilizando la API de REST, debes enviar una solicitud de `POST` a la terminal de la API de {% data variables.product.prodname_dotcom %} y proporcionar la `ref` y cualquier `input` relacionado. Para obtener más información, consulta terminal "[Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)" de la API de REST. - - Cuando activas el evento en {% data variables.product.prodname_dotcom %}, puedes proporcionar la `ref` y cualquier `input` directamente en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Configurar un flujo de trabajo](/actions/configuring-and-managing-workflows/configuring-a-workflow#manually-running-a-workflow)." - -#### `repository_dispatch` - -| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | -| -------------------------------------------------------------------- | ------------------ | ---------------------------------------------- | ------------------------- | -| [repository_dispatch](/webhooks/event-payloads/#repository_dispatch) | n/a | Última confirmacion en la rama de `GITHUB_REF` | Rama que recibió el envío | - -{% data reusables.github-actions.branch-requirement %} - -Puedes utilizar la API de {% data variables.product.product_name %} para desencadenar un evento de webhook llamado [`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) cuando quieras desencadenar un flujo de trabajo para una actividad que sucede fuera de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Crear un evento de envío de repositorio](/v3/repos/#create-a-repository-dispatch-event)". - -Para desencadenar el evento de webhook `repository_dispatch` personalizado, debes enviar una solicitud de `POST` a un punto final de una API de {% data variables.product.product_name %} y dar un nombre de `event_type` para describir el tipo de actividad. Para desencadenar la ejecución de un flujo de trabajo, también debes configurar tu flujo de trabajo para usar el evento `repository_dispatch`. - -##### Ejemplo - -Predeterminadamente, todos los `event_types` desencadenan la ejecución de un flujo de trabajo. Puedes limitar tu flujo de trabajo para que se ejecute cuando un valor específico de `event_type` se envíe en la carga útil del webhook de `repository_dispatch`. Tú defines los tipos de evento enviados en la carga útil de `repository_dispatch` cuando creas el repositorio. - -```yaml -on: - repository_dispatch: - types: [opened, deleted] -``` - -### Activar nuevos flujos de trabajo mediante un token de acceso personal - -{% data reusables.github-actions.actions-do-not-trigger-workflows %} Para obtener más información, consulta "[Autenticar con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)". - -Si deseas activar un flujo de trabajo desde una ejecución de flujo de trabajo, puedes desencadenar el evento mediante un token de acceso personal. Necesitaras crear un token de acceso personal y almacenarlo como un secreto. Para minimizar tus costos de uso de {% data variables.product.prodname_actions %}, asegúrate de no crear ejecuciones de flujo de trabajo recurrentes o involuntarias. Para obtener más información, consulta "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". diff --git a/translations/es-XL/content/actions/reference/index.md b/translations/es-XL/content/actions/reference/index.md deleted file mode 100644 index b9be0497ab..0000000000 --- a/translations/es-XL/content/actions/reference/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Referencia -intro: 'Documentación de referencia para la construcción de acciones, la creación de flujos de trabajo y otras herramientas e información sobre las {% data variables.product.prodname_actions %}.' -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' - github-ae: '*' -redirect_from: - - /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow -children: - - /workflow-syntax-for-github-actions - - /context-and-expression-syntax-for-github-actions - - /workflow-commands-for-github-actions - - /events-that-trigger-workflows - - /authentication-in-a-workflow - - /encrypted-secrets - - /environments - - /environment-variables - - /usage-limits-billing-and-administration ---- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/es-XL/content/actions/reference/workflow-commands-for-github-actions.md b/translations/es-XL/content/actions/reference/workflow-commands-for-github-actions.md deleted file mode 100644 index 8687d7287b..0000000000 --- a/translations/es-XL/content/actions/reference/workflow-commands-for-github-actions.md +++ /dev/null @@ -1,216 +0,0 @@ ---- -title: Comandos de flujo de trabajo para Acciones de GitHub -shortTitle: Comandos de flujo de trabajo -intro: Puedes usar comandos de flujo de trabajo cuando ejecutas comandos de Shell en un flujo de trabajo o en el código de una acción. -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /articles/development-tools-for-github-actions - - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions - - /actions/automating-your-workflow-with-github-actions/development-tools-for-github-actions - - /actions/reference/development-tools-for-github-actions - - /actions/reference/logging-commands-for-github-actions -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' - github-ae: '*' ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de los comandos de flujo - -Las acciones pueden comunicarse con la máquina del ejecutor para establecer variables de entorno, valores de salida utilizados por otras acciones, agregar mensajes de depuración a los registros de salida y otras tareas. - -Los comandos de flujo de trabajo usan el comando `echo` en un formato específico. - -``` bash -echo ":: Workflow-Command Parameter1 ={data}, parameter2 ={data}::{command value}" -``` - -{% note %} - -**Nota:** los nombres de comandos y parámetros de flujo de trabajo no distinguen mayúsculas de minúsculas. - -{% endnote %} - -{% warning %} - -**Advertencia:** si estás usando el símbolo del sistema, omite los caracteres de comillas dobles (`"`) cuando uses comandos de flujo de trabajo. - -{% endwarning %} - -### Utilizar comandos de flujo de trabajo para acceder a las funciones de toolkit - -El [actions/toolkit](https://github.com/actions/toolkit) incluye varias funciones que se pueden ejecutar como comandos de flujo de trabajo. Utiliza la sintaxis `::` para ejecutar los comandos de flujo de trabajo dentro de tu archivo YAML; estos comandos se envían entonces a través de `stdout`. Por ejemplo, en vez de utilizar el código para configurar una variable de ambiente, como se muestra a continuación: - -```javascript -core.exportVariable('SELECTED_COLOR', 'green'); -``` - -Puedes utilizar el comando `set-env` en tu flujo de trabajo para configurar el mismo valor: - -``` yaml - - name: Set selected color - run: echo '::set-env name=SELECTED_COLOR::green' - - name: Get color - run: echo 'The selected color is' $SELECTED_COLOR -``` - -La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles dentro de un flujo de trabajo: - -| Funcion del Toolkit | Comando equivalente del flujo de trabajo | -| --------------------- | ----------------------------------------------------------- | -| `core.addPath` | `add-path` | -| `core.debug` | `debug` | -| `core.error` | `error` | -| `core.endGroup` | `endgroup` | -| `core.exportVariable` | `set-env` | -| `core.getInput` | Accesible utilizando la variable de ambiente `INPUT_{NAME}` | -| `core.getState` | Accesible utilizando la variable de ambiente`STATE_{NAME}` | -| `core.isDebug` | Accesible utilizando la variable de ambiente `RUNNER_DEBUG` | -| `core.saveState` | `save-state` | -| `core.setFailed` | Utilizada como un atajo para `::error` y `exit 1` | -| `core.setOutput` | `set-output` | -| `core.setSecret` | `add-mask` | -| `core.startGroup` | `grupo` | -| `core.warning` | `warning file` | - -### Configurar una variable de ambiente - -`::set-env name={name}::{value}` - -Crea o actualiza una variable de entorno para todas las acciones que se ejecutan a continuación en un puesto. La acción que crea o actualiza la variable de entorno no tiene acceso al nuevo valor, pero todas las acciones subsiguientes en un puesto tendrán acceso. Las variables de entorno distinguen mayúsculas de minúsculas y puedes incluir puntuación. - -#### Ejemplo - -``` bash -echo "::set-env name=action_state::yellow" -``` - -### Configurar un parámetro de salida - -`::set-output name={name}::{value}` - -Establece un parámetro de salida de la acción. - -Opcionalmente, también puedes declarar parámetros de salida en el archivo de metadatos de una acción. Para obtener más información, consulta "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)". - -#### Ejemplo - -``` bash -echo "::set-output name=action_fruit::strawberry" -``` - -### Agregar una ruta de sistema - -`::add-path::{path}` - -Anexa un directorio a la variable de `RUTA` del sistema para todas las acciones subsiguientes en el puesto actual. La acción que se ejecuta actualmente no puede acceder a la nueva variable de ruta. - -#### Ejemplo - -``` bash -echo "::add-path::/path/to/dir" -``` - -### Agregar un mensaje de depuración - -`::debug::{message}` - -Imprime un mensaje de depuración para el registro. Debes crear un archivo `ACTIONS_STEP_DEBUG` designado secretamente con el valor `true` para ver los mensajes de depuración establecidos por este comando en el registro. Para obtener más información, consulta la sección "[Administrar la ejecución de un flujo de trabajo](/actions/configuring-and-managing-workflows/managing-a-workflow-run#enabling-debug-logging)". - -#### Ejemplo - -``` bash -echo "::debug::Set the Octocat variable" -``` - -### Configurar un mensaje de advertencia - -`::warning file={name},line={line},col={col}::{message}` - -Crea un mensaje de advertencia e imprime el mensaje en el registro. Opcionalmente, puedes brindar un nombre de archivo (`file`), número de línea (`line`), y columna (`col`) donde se produjo la advertencia. - -#### Ejemplo - -``` bash -echo "::warning file=app.js,line=1,col=5::Missing semicolon" -``` - -### Configurar un mensaje de error - -`::error file={name},line={line},col={col}::{message}` - -Crea un mensaje de error e imprime el mensaje en el registro Opcionalmente, puedes brindar un nombre de archivo (`file`), número de línea (`line`), y columna (`col`) donde se produjo la advertencia. - -#### Ejemplo - -``` bash -echo "::error file=app.js,line=10,col=15::Something went wrong" -``` - -### Enmascarar un valor en el registro - -`::add-mask::{value}` - -El enmascaramiento de un valor impide que una cadena o variable se imprima en el registro. Cada palabra enmascarada separada por un espacio en blanco se reemplaza con el carácter `*`. Puedes usar una variable de entorno o cadena para el `valor` de la máscara. - -#### Ejemplo de enmascaramiento de una cadena - -Cuando imprimas `"Mona The Octocat"` en el registro, verás `"***"`. - -```bash -echo "::add-mask::Mona The Octocat" -``` - -#### Ejemplo de enmascaramiento de una variable de entorno - -Cuando imprimes la variable `MY_NAME` o el valor `"Mona The Octocat"` en el registro, verás `"***"` en lugar de `"Mona The Octocat"`. - -```bash -MY_NAME="Mona The Octocat" -echo "::add-mask::$MY_NAME" -``` - -### Detener e iniciar comandos de flujo de trabajo - -`::stop-commands::{endtoken}` - -Detiene el procesamiento de cualquier comando de flujo de trabajo. Este comando especial te permite registrar cualquier cosa sin ejecutar accidentalmente un comando de flujo de trabajo. Por ejemplo, podrías dejar de registrar para producir un script completo que tenga comentarios. - -#### Ejemplo deteniendo comandos de flujo de trabajo - -``` bash -echo "::stop-commands::pause-logging" -``` - -Para iniciar los comandos de flujo de trabajo, pasa el token que usaste para detener los comandos de flujo de trabajo. - -`::{endtoken}::` - -#### Ejemplo de inicio de comandos de flujo - -``` bash -echo "::pause-logging::" -``` - -### Enviar valores a las acciones pre y post - -Puedes utilizar el comando `save-state` para crear variables de ambiente para compartir con tus acciones `pre:` o `post:` de flujo de trabajo. Por ejemplo, puedes crear un archivo con la acción `pre:`, pasar la ubicación del archivo a la acción `main:`, y después, utilizar la acción `post:` para borrar el archivo. Como alternativa, puedes crear un archivo con la acción `main:`, pasar la ubicación del archivo a la acción `post:`, y también utilizar la acción `post:` para borrar el archivo. - -Si tienes varias acciones `pre:` o `post:`, solo podrás acceder al valor que se guardó en la acción donde se utilizó `save-state`. Para obtener más información sobre la acción `post:`, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#post)". - -El comando `save-state` solo puede ejecutarse dentro de una acción y no está disponible para archivos YAML. El valor guardado se almacena en un valor de ambiente con el prefijo `STATE_`. - -Este ejemplo utiliza JavaScript para ejecutar el comando `save-state`. La variable de ambiente resultante se nombra `STATE_processID` con el valor de `12345`: - -``` javascript -console.log('::save-state name=processID::12345') -``` - -La variable `STATE_processID` se encontrará entonces exclusivamente disponible para el script de limpieza que se ejecuta bajo la acción `main`. Este ejemplo se ejecuta en `main` y utiliza JavaScript para mostrar el valor asignado a la variable de ambiente `STATE_processID`: - -``` javascript -console.log("The running PID from the main action is: " + process.env.STATE_processID); -``` diff --git a/translations/es-XL/content/actions/reference/workflow-syntax-for-github-actions.md b/translations/es-XL/content/actions/reference/workflow-syntax-for-github-actions.md deleted file mode 100644 index 0cd61dc3bf..0000000000 --- a/translations/es-XL/content/actions/reference/workflow-syntax-for-github-actions.md +++ /dev/null @@ -1,1111 +0,0 @@ ---- -title: Sintaxis de flujo de trabajo para acciones de GitHub -shortTitle: Sintaxis de flujos de trabajo -intro: Un flujo de trabajo es un proceso automatizado configurable formado por uno o más trabajos. Debes crear un archivo YAML para definir tu configuración de flujo de trabajo. -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /articles/workflow-syntax-for-github-actions - - /github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions - - /actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' - github-ae: '*' ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de la sintaxis de YAML para flujos de trabajo - -Los archivos de flujo de trabajo usan la sintaxis YAML y deben tener una extensión de archivo `.yml` o `.yaml`. Si eres nuevo en YAML y deseas conocer más, consulta "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". - -Debes almacenar los archivos de flujos de trabajo en el directorio `.github/workflows` en tu repositorio. - -### Límites de uso - -{% data reusables.github-actions.github-actions-usage-limits %} - -### **`name (nombre)`** - -El nombre de tu flujo de trabajo. {% data variables.product.prodname_dotcom %} muestra los nombres de tus flujos de trabajo en la página de acciones de tu repositorio. Si omites `nombre`, {% data variables.product.prodname_dotcom %} lo establece en la ruta del archivo de flujo de trabajo en relación con la raíz del repositorio. - -### **`on`** - -**Obligatorio** El nombre del evento {% data variables.product.prodname_dotcom %} que activa el flujo de trabajo. Puedes proporcionar una única `cadena` de eventos, `matriz` de eventos, `matriz` de `tipos` de eventos o `mapa` de configuración de eventos que programe un flujo de trabajo o restrinja la ejecución de un flujo de trabajo para archivos, etiquetas o cambios de rama específicos. Para obtener una lista de eventos disponibles, consulta "[Eventos que desencadenan flujos de trabajo](/articles/events-that-trigger-workflows)". - -{% data reusables.github-actions.actions-on-examples %} - -### **`on..types`** - -Selecciona los tipos de actividad que desencadenarán una ejecución de flujo de trabajo. La mayoría de los eventos GitHub son desencadenados por más de un tipo de actividad. Por ejemplo, el evento para el recurso release (lanzamiento) se activa cuando se `publica`, `se cancela la publicación`, `se crea`, `edita`, `elimina` o `lanza previamente` una publicación. La palabra clave `types` (tipos) te permite reducir la actividad que hace que se ejecute el flujo de trabajo. Cuando solo un tipo de actividad activa el evento webhook, la palabra clave `types` (tipos) es innecesaria. - -Puedes usar una matriz de `tipos` de eventos. Para obtener más información acerca de cada evento y sus tipos de actividad, consulta "[Eventos que desencadenan flujos de trabajo](/articles/events-that-trigger-workflows#webhook-events)". - -```yaml -# Activa el flujo de trabajo en la actividad de la solicitud de extracción -on: - release: - # Solo usa la palabra clave de tipos para reducir los tipos de actividad que activarán tus flujos de trabajo. - types: [published, created, edited] -``` - -### **`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 usan los caracteres comodines `*` y `**` para encontrar más de un nombre de rama o etiqueta. Para obtener más información, consulta "[Hoja de referencia de patrones de filtro](#filter-pattern-cheat-sheet)". - -#### Ejemplo que incluye ramas y etiquetas - -Los patrones definidos en `branches` y `tags` se evalúan con el nombre de ref de Git. Por ejemplo, al definir el patrón `mona/octocat` en `branches`, se encontrará la ref de Git `refs/heads/mona/octocat`. El patrón `releases/**` encontrará la ref de Git `refs/heads/releases/10`. - -```yaml -on: - push: - # Sequence of patterns matched against refs/heads - branches: - # Push events on master branch - - master - # Push events to branches matching refs/heads/mona/octocat - - 'mona/octocat' - # Push events to branches matching refs/heads/releases/10 - - 'releases/**' - # Sequence of patterns matched against refs/tags - tags: - - v1 # Push events to v1 tag - - v1.* # Push events to v1.0, v1.1, and v1.9 tags -``` - -#### Ejemplo de ignorar ramas y etiquetas - -Cada vez que un patrón coincida con el patrón `branches-ignore` o `tags-ignore`, no se ejecutará el flujo de trabajo. Los patrones definidos en `branches-ignore` y `tags-ignore` se evalúan con el nombre de ref de Git. Por ejemplo, al definir el patrón `mona/octocat` en `branches`, se encontrará la ref de Git `refs/heads/mona/octocat`. El patrón `releases/**-alpha` en `branches` encontrará la ref de Git `refs/releases/beta/3-alpha`. - -```yaml -on: - push: - # Sequence of patterns matched against refs/heads - branches-ignore: - # Push events to branches matching refs/heads/mona/octocat - - 'mona/octocat' - # Push events to branches matching refs/heads/releases/beta/3-alpha - - 'releases/**-alpha' - # Sequence of patterns matched against refs/tags - tags-ignore: - - v1.* # Push events to tags v1.0, v1.1, and v1.9 -``` - -#### Excluir ramas y etiquetas - -Puedes usar dos tipos de filtros para evitar que un flujo de trabajo se ejecute en las subidas y las solicitudes de extracción a las etiquetas y las ramas. -- `branches` o `branches-ignore`: no puedes usar ambos filtros `branches` y `branches-ignore` para el mismo evento de un flujo de trabajo. Usa el filtro `branches` cuando debas filtrar ramas de coincidencias positivas y para excluir ramas. Usa el filtro `branches-ignore` cuando solo debas excluir nombres de ramas. -- `tags` o `tags-ignore`: no puedes usar ambos filtros `tags` y `tags-ignore` para el mismo evento de un flujo de trabajo. Usa el filtro `tags` cuando debas filtrar etiquetas de coincidencias positivas y para excluir etiquetas. Usa el filtro `tags-ignore` cuando solo debas excluir nombres de etiquetas. - -#### Ejemplo de uso de patrones positivos y negativos - -Puedes excluir `etiquetas` y `ramas` usando el caracter `!`. El orden en que defines los patrones importa. - - Un patrón negativo de coincidencia (con prefijo `!`) luego de una coincidencia positiva excluirá la ref de Git. - - Un patrón positivo de coincidencia luego de una coincidencia negativa volverá a incluir la ref de Git. - -El siguiente flujo de trabajo se ejecutará en las subidas a `releases/10` o `releases/beta/mona`, pero no en `releases/10-alpha` o `releases/beta/3-alpha` porque el patrón negativo `!releases/**-alpha` le sigue al patrón positivo. - -```yaml -on: - push: - branches: - - 'releases/**' - - '!releases/**-alpha' -``` - -### **`on..paths`** - -Cuando uses los eventos `push` y `pull_request`, puedes configurar que se ejecute un flujo de trabajo cuando al menos un archivo no coincida con `paths-ignore` o al menos uno de los archivos modificados coincida con las `rutas` configuradas. Los filtros de ruta no se evalúan para las subidas a etiquetas. - -Las palabras clave `paths-ignore` y `paths` aceptan los patrones globales que usan los caracteres comodines `*` y `**` para encontrar más de un nombre de ruta. Para obtener más información, consulta "[Hoja de referencia de patrones de filtro](#filter-pattern-cheat-sheet)". - -#### Ejemplo de ignorar rutas - -Cada vez que un nombre de ruta coincida con `paths-ignore`, no se ejecutará el flujo de trabajo. {% data variables.product.prodname_dotcom %} evalúa los patrones definidos en `paths-ignore` para compararlos con el nombre de ruta. Un flujo de trabajo con el siguiente filtro de ruta solo se ejecutará en los eventos de `subida` que incluyan al menos un archivo externo al directorio `docs` en la raíz del repositorio. - -```yaml -on: - push: - paths-ignore: - - 'docs/**' -``` - -#### Ejemplo de incluir rutas - -Si al menos una ruta coincide con un patrón del filtro de `rutas`, se ejecuta el flujo de trabajo. Para desencadenar una compilación cada vez que subes un archivo JavaScript, puedes usar un patrón comodín. - -```yaml -on: - push: - paths: - - '**.js' -``` - -#### Excluir rutas - -Puedes excluir rutas usando dos tipos de filtros. No puedes usar ambos filtros para el mismo evento de un flujo de trabajo. -- `paths-ignore`: usa el filtro `paths-ignore` cuando solo debas excluir nombres de ruta. -- `paths`: usa el filtro `paths` cuando debas filtrar rutas de coincidencias positivas y excluir rutas. - -#### Ejemplo de uso de patrones positivos y negativos - -Puedes excluir `rutas` usando el caracter `!`. El orden en que defines los patrones importa: - - Una coincidencia de patrón negativo (con prefijo `!`) luego de una coincidencia positiva excluirá la ruta. - - Un patrón de coincidencia positiva luego de una coincidencia negativa excluirá nuevamente la ruta. - -Este ejemplo se ejecuta cada vez que el evento de `subida` incluye un archivo en el directorio `sub-project` o sus subdirectorios, a menos que el archivo esté en el directorio `sub-project/docs`. Por ejemplo, una subida que haya cambiado `sub-project/index.js` o `sub-project/src/index.js` desencadenará una ejecución de flujo de trabajo, pero una subida que cambie solo `sub-project/docs/readme.md` no lo hará. - -```yaml -on: - push: - paths: - - 'sub-project/**' - - '!sub-project/docs/**' -``` - -#### Comparaciones de diferencias de Git - -{% note %} - -**Nota:** Si subes más de 1.000 confirmaciones, o si {% data variables.product.prodname_dotcom %} no genera la diferencia debido a una interrupción (diferencias que son diferencias demasiado grandes), siempre se ejecutará el flujo de trabajo. - -{% endnote %} - -El filtro determina si un flujo de trabajo se debe ejecutar al evaluar los archivos modificados y al ejecutarlos comparándolos con la lista de `paths-ignore` o `paths`. Si no hay archivos modificados, no se ejecutará el flujo de trabajo. - -{% data variables.product.prodname_dotcom %} genera la lista de archivos modificados usando diferencias de dos puntos para las subidas y de tres puntos para las solicitudes de extracción: -- **Solicitudes de extracción:** las diferencias de tres puntos son una comparación entre la versión más reciente de la rama de tema y la confirmación, cuando la rama de tema se sincronizó por última vez con la rama base. -- **Subidas a ramas existentes:** una diferencia de dos puntos compara las SHA de encabezado y de base directamente entre sí. -- **Subidas a ramas nuevas:** una diferencia de dos puntos comparada con el padre del antepasado de la confirmación más profunda subida. - -Para obtener más información, consulta "[Acerca de comparar ramas en las solicitudes de extracción](/articles/about-comparing-branches-in-pull-requests)". - -### **`on.schedule`** - -{% data reusables.repositories.actions-scheduled-workflow-example %} - -Para obtener más información acerca de la sintaxis cron, consulta "[Eventos que activan flujos de trabajo](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)." - -### **`env`** - -Un `mapa` de las variables de entorno que están disponibles para todas las tareas y los pasos del flujo de trabajo. También puedes configurar variables de entorno que estén solo disponibles para una tarea o paso. Para obtener más información, consulta [`jobs..env`](#jobsjob_idenv) y [`jobs..steps.env`](#jobsjob_idstepsenv). - -{% data reusables.repositories.actions-env-var-note %} - -#### Ejemplo - -```yaml -env: - SERVER: production -``` - -### **`defaults`** - -Un `map` de configuración predeterminada que se aplicará a todos los jobs en el flujo de trabajo. También puedes configurar los ajustes predeterminados que solo estén disponibles para un job. Para obtener más información, consulta la sección [`jobs..defaults`](#jobsjob_iddefaults). - -{% data reusables.github-actions.defaults-override %} - -### **`defaults.run`** - -Puedes proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](#jobsjob_idstepsrun) en un flujo de trabajo. También puedes configurar ajustes predeterminados para `run` que solo estén disponibles para un job. Para obtener más información, consulta [`jobs..defaults.run`](#jobsjob_iddefaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave. - -{% data reusables.github-actions.defaults-override %} - -#### Ejemplo - -```yaml -defaults: - run: - shell: bash - working-directory: scripts -``` - -### **`Trabajos`** - -Una ejecución de flujo de trabajo está compuesta por uno o más trabajos. De forma predeterminada, los trabajos se ejecutan en paralelo. Para ejecutar trabajos de manera secuencial, puedes definir dependencias en otros trabajos utilizando la palabra clave `jobs..needs`. - -Cada trabajo se ejecuta en un entorno especificado por `runs-on`. - -Puedes ejecutar una cantidad ilimitada de trabajos siempre que estés dentro de los límites de uso del flujo de trabajo. Para obtener más información, consulta "[Límites de uso](#usage-limits)". - -Si necesitas encontrar el identificador único de un trabajo que se ejecuta en una ejecución de flujo de trabajo, puedes usar el API {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Jobs de los Flujos de Trabajo](/v3/actions/workflow-jobs)". - -### **`jobs.`** - -Cada trabajo debe tener una identificación para asociarse con el trabajo. La clave `job_id` es una cadena y su valor es un mapa de los datos de configuración del trabajo. Debes reemplazar `` con una cadena que sea exclusiva del objeto `jobs`. El `` debe comenzar con una letra o `_` y debe contener solo caracteres alfanuméricos, `-`, o `_`. - -#### Ejemplo - -```yaml -jobs: - my_first_job: - name: My first job - my_second_job: - name: My second job -``` - -### **`jobs..name`** - -El nombre del trabajo que se muestra en {% data variables.product.prodname_dotcom %}. - -### **`jobs..needs`** - -Identifica los trabajos que se deben completar con éxito antes de que se ejecute este trabajo. Puede ser una cadena o matriz de cadenas. Si un trabajo falla, todos los trabajos que lo necesiten estarán omitidos a menos que los trabajos usen una declaración condicional que haga que el trabajo continúe. - -#### Ejemplo - -```yaml -jobs: - job1: - job2: - needs: job1 - job3: - needs: [job1, job2] -``` - -En este ejemplo, `job1` debe completarse con éxito antes de que `job2` comience, y `job3` espera a que`job1` y `job2` se completen. - -En este ejemplo, los trabajos se ejecutan de manera secuencial: - -1. `job1` -2. `job2` -3. `job3` - -### **`jobs..runs-on`** - -**Obligatorio** El tipo de máquina en la que se ejecuta el trabajo. La máquina puede ser un ejecutor alojado {% data variables.product.prodname_dotcom %} o un ejecutor autoalojado. - -{% data reusables.actions.enterprise-github-hosted-runners %} - -#### Ejecutores alojados {% data variables.product.prodname_dotcom %} - -Si usas un ejecutor alojado {% data variables.product.prodname_dotcom %}, cada trabajo se ejecuta en una nueva instancia de un entorno virtual especificado por `runs-on`. - -Los tipos de ejecutores alojados {% data variables.product.prodname_dotcom %} disponibles son: - -{% data reusables.github-actions.supported-github-runners %} - -{% data reusables.github-actions.ubuntu-runner-preview %} - -##### **Ejemplo** - -```yaml -runs-on: ubuntu-latest -``` - -Para obtener más información, consulta "[Entornos virtuales para ejecutores alojados de {% data variables.product.prodname_dotcom %}](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". - -#### Ejecutores autoalojados - -{% data reusables.github-actions.self-hosted-runner-labels-runs-on %} - -##### **Ejemplo** - -```yaml -runs-on: [self-hosted, linux] -``` - -Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/about-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)". - -### **`jobs..outputs`** - -Un `map` de salidas para un job. Las salidas de un job se encuentran disponibles para todos los jobs descendentes que dependan de este job. Para obtener más información sobre la definición de dependencias, consulta [`jobs..needs`](#jobsjob_idneeds). - -Las salidas de un job son secuencias, y las salidas de un job que contienen expresiones se evalúan en el ejecutor al final de cada job. Las salidas que contienen secretos se redactan en el ejecutor y no se envían a {% data variables.product.prodname_actions %}. - -Para utilizar salidas de jobs en un job dependiente, puedes utilizar el contexto `needs`. Para obtener más información, consulta "[Sintaxis de contexto y expresión para las {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#needs-context)." - -#### **Ejemplo** - -{% raw %} -```yaml -jobs: - job1: - runs-on: ubuntu-latest - # Map a step output to a job output - outputs: - output1: ${{ steps.step1.outputs.test }} - output2: ${{ steps.step2.outputs.test }} - steps: - - id: step1 - run: echo "::set-output name=test::hello" - - id: step2 - run: echo "::set-output name=test::world" - job2: - runs-on: ubuntu-latest - needs: job1 - steps: - - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}} -``` -{% endraw %} - -### **`jobs..env`** - -Un `mapa` de las variables de entorno que están disponibles para todos los pasos de la tarea. También puedes establecer las variables de entorno para todo el flujo de trabajo o para un paso en particular. Para obtener más información, consulta [`env`](#env) y [`jobs..steps.env`](#jobsjob_idstepsenv). - -{% data reusables.repositories.actions-env-var-note %} - -#### **Ejemplo** - -```yaml -jobs: - job1: - env: - FIRST_NAME: Mona -``` - -### **`jobs..defaults`** - -Un `map` de configuración predeterminada que se aplicará a todos los pasos del job. También puedes configurar ajustes predeterminados para todo el flujo de trabajo. Para obtener más información, consulta [`defaults`](#defaults). - -{% data reusables.github-actions.defaults-override %} - -### **`jobs..defaults.run`** - -Proporciona `shell` y `working-directory` predeterminados a todos los pasos de `run` en el job. No se permiten las expresiones ni contexto en esta sección. - -Puedes proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](#jobsjob_idstepsrun) en un job. También puedes configurar ajustes predeterminados para `run` para todo el flujo de trabajo. Para obtener más información, consulta [`jobs.defaults.run`](#defaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave. - -{% data reusables.github-actions.defaults-override %} - -#### Ejemplo - -```yaml -jobs: - job1: - runs-on: ubuntu-latest - defaults: - run: - shell: bash - working-directory: scripts -``` - -### **`jobs..if`** - -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 %} Para obtener más información, consulta la sección "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". - -### **`jobs..steps`** - -Un trabajo contiene una secuencia de tareas llamadas `pasos`. Los pasos pueden ejecutar comandos, tareas de configuración o una acción en tu repositorio, un repositorio público o una acción publicada en un registro de Docker. Not all steps run actions, but all actions run as a step. Cada paso se ejecuta en su propio proceso en el entorno del ejecutor y tiene acceso al espacio de trabajo y al sistema de archivos. Debido a que los pasos se ejecutan en su propio proceso, los cambios en las variables de entorno no se conservan entre los pasos. {% data variables.product.prodname_dotcom %} proporciona pasos integrados para configurar y completar un trabajo. - -Puedes ejecutar un número de pasos ilimitado siempre que estés dentro de los límites de uso del flujo de trabajo. Para obtener más información, consulta "[Límites de uso](#usage-limits)". - -#### Ejemplo - -{% raw %} -```yaml -name: Greeting from Mona - -on: push - -jobs: - my-job: - name: My Job - runs-on: ubuntu-latest - steps: - - name: Print a greeting - env: - MY_VAR: Hi there! My name is - FIRST_NAME: Mona - MIDDLE_NAME: The - LAST_NAME: Octocat - run: | - echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME. -``` -{% endraw %} - -#### **`jobs..steps.id`** - -Un identificador único para el paso. Puede usar el `id` para hacer referencia al paso en contextos. Para obtener más información, consulta "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". - -#### **`jobs..steps.if`** - -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 %} Para obtener más información, consulta la sección "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". - -##### Ejemplos usando contextos - - Este paso solo se ejecuta cuando el tipo de evento es una `pull_request` y la acción del evento está `sin asignar`. - - ```yaml -steps: - - name: My first step - if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %} - run: echo This event is a pull request that had an assignee removed. -``` - -##### Ejemplo usando 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. Para obtener más información, consulta "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions)". - -```yaml -steps: - - name: My first step - uses: monacorp/action-name@master - - name: My backup step - if: {% raw %}${{ failure() }}{% endraw %} - uses: actions/heroku@master -``` - -#### **`jobs..steps.name`** - -Un nombre para que tu paso se muestre en {% data variables.product.prodname_dotcom %}. - -#### **`jobs..steps.uses`** - -Selecciona una acción para ejecutar como parte de un paso en tu trabajo. Una acción es una unidad de código reutilizable. Puedes usar una acción definida en el mismo repositorio que el flujo de trabajo, un repositorio público o en una [imagen del contenedor Docker publicada](https://hub.docker.com/). - -Te recomendamos encarecidamente que incluyas la versión de la acción que estás utilizando y especifiques un número de etiqueta de Git ref, SHA o Docker. Si no especificas una versión, podrías interrumpir tus flujos de trabajo o provocar un comportamiento inesperado cuando el propietario de la acción publique una actualización. -- El uso del SHA de confirmación de una versión de acción lanzada es lo más seguro para la estabilidad y la seguridad. -- 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. -- Usar la rama `principal` de una acción puede ser conveniente, pero si alguien lanza una nueva versión principal con un cambio importante, tu flujo de trabajo podría romperse. - -Algunas acciones requieren entradas que se deben establecer usando la palabra clave [`with`](#jobsjob_idstepswith) (con). Revisa el archivo README de la acción para determinar las entradas requeridas. - -Las acciones son archivos JavaScript o contenedores Docker. Si la acción que estás usando es un contenedor Docker, debes ejecutar el trabajo en un entorno Linux. Para obtener más detalles, consulta [`runs-on`](#jobsjob_idruns-on). - -##### Ejemplo usando acciones versionadas - -```yaml -steps: - # Reference a specific commit - - uses: actions/setup-node@74bc508 - # Reference the major version of a release - - uses: actions/setup-node@v1 - # Reference a minor version of a release - - uses: actions/setup-node@v1.2 - # Reference a branch - - uses: actions/setup-node@master -``` - -##### Ejemplo usando una acción pública - -`{owner}/{repo}@{ref}` - -Puedes usar ramas, ref o SHA específicos en un repositorio público {% data variables.product.prodname_dotcom %}. - -```yaml -jobs: - my_first_job: - steps: - - name: My first step - # Uses the master branch of a public repository - uses: actions/heroku@master - - name: My second step - # Uses a specific version tag of a public repository - uses: actions/aws@v2.0.1 -``` - -##### Ejemplo usando una acción pública en un subdirectorio - -`{owner}/{repo}/{path}@{ref}` - -Un subdirectorio en un repositorio público de {% data variables.product.prodname_dotcom %} en una rama específica, ref o SHA. - -```yaml -jobs: - my_first_job: - steps: - - name: My first step - uses: actions/aws/ec2@master -``` - -##### Ejemplo usando la acción en el mismo repositorio que el flujo de trabajo - -`./path/to/dir` - -La ruta al directorio que contiene la acción en el repositorio de tu flujo de trabajo. Debes revisar tu repositorio antes de usar la acción. - -```yaml -jobs: - my_first_job: - steps: - - name: Check out repository - uses: actions/checkout@v2 - - name: Use local my-action - uses: ./.github/actions/my-action -``` - -##### Ejemplo usando una acción Docker Hub - -`docker://{image}:{tag}` - -Una imagen de Docker publicada en [Docker Hub](https://hub.docker.com/). - -```yaml -jobs: - my_first_job: - steps: - - name: My first step - uses: docker://alpine:3.8 -``` - -##### Ejemplo usando una acción de registro público de Docker - -`docker://{host}/{image}:{tag}` - -Una imagen de Docker en un registro público. - -```yaml -jobs: - my_first_job: - steps: - - name: My first step - uses: docker://gcr.io/cloud-builders/gradle -``` - -#### **`jobs..steps.run`** - -Ejecuta programas de la línea de comandos usando el shell del sistema operativo. Si no proporcionas un `nombre`, el paso de establecimiento de nombre se completará por defecto con el texto especificado en el comando `run`. - -Por defecto, los comandos se ejecutan utilizando shells sin inicio de sesión. Puedes elegir un shell diferente y personalizar el shell utilizado para ejecutar los comandos. Para obtener más información, consulta "[Usar un shell específico](#using-a-specific-shell)". - -Cada palabra clave `run` representa un nuevo proceso y shell en el entorno del ejecutor. Cuando proporcionas comandos de varias líneas, cada línea se ejecuta en el mismo shell. Por ejemplo: - -* Comando de una sola línea: - - ```yaml - - name: Install Dependencies - run: npm install - ``` - -* Comando de varias líneas: - - ```yaml - - name: Clean install dependencies and build - run: | - npm ci - npm run build - ``` - -Usando la palabra clave `working-directory`, puedes especificar el directorio de trabajo de dónde ejecutar el comando. - -```yaml -- name: Clean temp directory - run: rm -rf * - working-directory: ./temp -``` - -##### Uso de un shell específico - -Puedes anular los parámetros predeterminados del shell en el sistema operativo del ejecutor utilizando la palabra clave `shell`. Puedes usar palabras clave incorporadas de `shell` keywords, o puedes definir un conjunto personalizado de opciones de shell. - -| Plataforma compatible | parámetro `shell` | Descripción | Comando ejecutado interamente | -| --------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- | -| Todas | `bash` | El shell predeterminado en plataformas que no son de Windows con una reserva para `sh`. Al especificar un bash shell en Windows, se usa el bash shell incluido con Git para Windows. | `bash --noprofile --norc -eo pipefail {0}` | -| Todas | `pwsh` | Powershell Core. {% data variables.product.prodname_dotcom %} agrega la extensión `.ps1` al nombre de tu script. | `pwsh -command "& '{0}'"` | -| Todas | `python` | Ejecuta el comando python. | `python {0}` | -| Linux / macOS | `sh` | El comportamiento de reserva para plataformas que no son Windows si no se proporciona un shell y `bash` no se encuentra en la ruta. | `sh -e {0}` | -| Windows | `cmd` | {% data variables.product.prodname_dotcom %} agrega la extensión `.cmd` a tu nombre de script y la sustituye por `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. | -| Windows | `powershell` | Este es el shell predeterminado que se usa en Windows. El Desktop PowerShell. {% data variables.product.prodname_dotcom %} agrega la extensión `.ps1` al nombre de tu script. | `powershell -command "& '{0}'"`. | - -##### Ejemplo de ejecución de un script mediante bash - -```yaml -steps: - - name: Display the path - run: echo $PATH - shell: bash -``` - -##### Ejemplo de ejecución de un script mediante `cmd` de Windows - -```yaml -steps: - - name: Display the path - run: echo %PATH% - shell: cmd -``` - -##### Ejemplo de ejecución de un script mediante PowerShell Core - -```yaml -steps: - - name: Display the path - run: echo ${env:PATH} - shell: pwsh -``` - -##### Ejemplo de ejecución de un script de python - -```yaml -steps: - - name: Display the path - run: | - import os - print(os.environ['PATH']) - shell: python -``` - -##### Shell personalizado - -Puede establecer el valor `shell` en una cadena de plantilla utilizando el comando `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interpreta la primera palabra delimitada por espacios en blanco de la cadena como el comando, e inserta el nombre del archivo para el script temporal en `{0}`. - -##### Códigos de salida y preferencia de acción de error - -Para palabras clave shell incorporadas, brindamos los siguientes valores predeterminados accionados por los ejecutadores alojados por {% data variables.product.prodname_dotcom %}. Deberías usar estos lineamientos al ejecutar scripts shell. - -- `bash`/`sh`: - - Comportamiento a prueba de fallos utilizando `set -e o pipefail`: valor predeterminado para `bash` y `shell` incorporado. También es el valor predeterminado cuando no proporcionas una opción en plataformas que no son de Windows. - - Puedes excluir la función de falla rápida y tomar el control total al proporcionar una cadena de plantilla a las opciones del shell. Por ejemplo, `bash {0}`. - - Los shells tipo sh salen con el código de salida del último comando ejecutado en un script, que también es el comportamiento predeterminado para las acciones. El ejecutor informará el estado del paso como fallido o exitoso según este código de salida. - -- `powershell`/`pwsh` - - Comportamiento de falla rápida cuando sea posible. Para el shell incorporado `pwsh` y `powershell`, vamos a anteponer `$ErrorActionPreference = 'stop'` a los contenidos del script. - - Añadimos `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` a los scripts de powershell para que los estados de acción reflejen el último código de salida del script. - - Los usuarios siempre pueden optar por no usar el shell incorporado y proporcionar una opción de shell personalizada como: `pwsh -File {0}`, o `powershell -Command "& '{0}'"`, según la necesidad. - -- `cmd` - - No parece haber una manera de optar por completo por un comportamiento de falla rápida que no sea escribir tu script para verificar cada código de error y responder en consecuencia. Debido a que en realidad no podemos proporcionar ese comportamiento por defecto, debes escribir este comportamiento en tu script. - - `cmd.exe` saldrá con el nivel de error del último programa que ejecutó y devolverá el código de error al ejecutor. Este comportamiento es internamente coherente con el comportamiento predeterminado anterior `sh` y `pwsh` y es el valor predeterminado `cmd.exe`, por lo que este comportamiento permanece intacto. - -#### **`jobs..steps.with`** - -Un `mapa` de los parámetros de entrada definidos por la acción. Cada parámetro de entrada es un par clave/valor. Los parámetros de entrada se establecen como variables del entorno. La variable tiene el prefijo `INPUT_` y se convierte en mayúsculas. - -##### Ejemplo - -Define los tres parámetros de entrada (`first_name`, `middle_name`, and `last_name`) definidos por la acción `hello_world`. Es posible acceder a estas variables de entrada con la acción `hello-world` como `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME` y las variables de entorno `INPUT_LAST_NAME`. - -```yaml -jobs: - my_first_job: - steps: - - name: My first step - uses: actions/hello_world@master - with: - first_name: Mona - middle_name: The - last_name: Octocat -``` - -#### **`jobs..steps.with.args`** - -Una `cadena` que define las entradas para un contenedor Docker. {% data variables.product.prodname_dotcom %} comunica los `args`en el `ENTRYPOINT` del contenedor cuando se inicia el contenedor. Una `matriz de cadenas` no es compatible para este parámetro. - -##### Ejemplo - -{% raw %} -```yaml -steps: - - name: Explain why this job ran - uses: monacorp/action-name@master - with: - entrypoint: /bin/echo - args: The ${{ github.event_name }} event triggered this step. -``` -{% endraw %} - -Los `args` se usan en el lugar de la instrucción `CMD` en un `Dockerfile`. Si usas `CMD` en tu `Dockerfile`, usa los lineamientos ordenados por preferencia: - -1. Los documentos requerían argumentos en el README de las acciones y las omiten desde la instrucción `CMD`. -1. Usa los valores predeterminados que permiten usar la acción sin especificar ningún `args`. -1. Si la acción expone un indicador `--help` o algo similar, usa ese como el valor predeterminado para que la acción se documente automáticamente. - - -#### **`jobs..steps.with.entrypoint`** - -Anula el Docker `ENTRYPOINT` en el `Dockerfile` o lo establece si es que no tiene uno especificado. A diferencia de la instrucción Docker `ENTRYPOINT` que tiene un shell y formulario de ejecución, la palabra clave `entrypoint` acepta solo una cadena que define el ejecutable que se ejecutará. - -##### Ejemplo - -```yaml -steps: - - name: Run a custom command - uses: monacorp/action-name@master - with: - entrypoint: /a/different/executable -``` - -La palabra clave `punto de entrada` se usa con acciones del contenedor Docker, pero también puedes usarla con acciones JavaScript que no definen las entradas. - -#### **`jobs..steps.env`** - -Establece variables de entorno para los pasos a utilizar en el entorno del ejecutor. También puedes establecer las variables de entorno para todo el flujo de trabajo o para una tarea. Para obtener más información, consulta [`env`](#env) y [`jobs..env`](#jobsjob_idenv). - -{% 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`. Para obtener más información, consulta "[Usar variables de entorno](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" y "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". - -##### Ejemplo - -{% raw %} -```yaml -steps: - - name: My first action - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - FIRST_NAME: Mona - LAST_NAME: Octocat -``` -{% endraw %} - -#### **`jobs..steps.continue-on-error`** - -Impide que un trabajo falle cuando falla un paso. Se lo debe establecer en `true` para permitir que un trabajo pase cuando falla este paso. - -#### **`jobs..steps.timeout-minutes`** - -El número máximo de minutos para ejecutar el paso antes de terminar el proceso. - -### **`jobs..timeout-minutes`** - -La cantidad máxima de minutos para permitir que un trabajo se ejecute antes que {% data variables.product.prodname_dotcom %} lo cancele automáticamente. Predeterminado: 360 - -### **`jobs..strategy`** - -Una estrategia crea una matriz de construcción para tus trabajos. Puedes definir diferentes variaciones de un entorno para ejecutar cada trabajo. - -#### **`jobs..strategy.matrix`** - -Puedes definir una matriz de diferentes configuraciones de trabajo. Una matriz te permite crear múltiples trabajos realizando la sustitución de variables en una definición de trabajo único. Por ejemplo, puedes usar una matriz para crear trabajos para más de una versión compatible de un lenguaje de programación, sistema operativo o herramienta. Una matriz reutiliza la configuración del trabajo y crea un trabajo para cada matriz que configuras. - -{% data reusables.github-actions.matrix-limits %} - -Cada opción que definas en la `matriz` tiene una clave y un valor. Las claves que defines se convierten en propiedades en el contexto `matriz` y puedes hacer referencia a la propiedad en otras áreas de tu archivo de flujo de trabajo. Por ejemplo, si defines la clave `os` que contiene una matriz de sistemas operativos, puedes usar la propiedad `matrix.os` como el valor de la palabra clave `runs-on` para crear un trabajo para cada sistema operativo. Para obtener más información, consulta "[Sintaxis de contexto y expresión para {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)". - -El orden en que defines una `matriz` importa. La primera opción que definas será el primer trabajo que se ejecuta en tu flujo de trabajo. - -##### Ejemplo de ejecución con más de una versión de Node.js - -Puedes especificar una matriz proporcionando una variedad de opciones de configuración. Por ejemplo, si el ejecutor admite las versiones 6, 8 y 10 de Node.js, puedes especificar una matriz de esas versiones en la `matriz`. - -Este ejemplo crea una matriz de tres trabajos estableciendo la clave `node` para una matriz de tres versiones de Node.js. Para usar la matriz, el ejemplo establece la propiedad de contexto `matrix.node` como el valor del parámetro `node-version` de la entrada de la acción `setup-node`. Como resultado, se ejecutarán tres trabajos, cada uno usando una versión diferente de Node.js. - -{% raw %} -```yaml -strategy: - matrix: - node: [6, 8, 10] -steps: - # Configura la versión del nodo usada en los ejecutores alojados de GitHub - - uses: actions/setup-node@v1 - with: - # La versión de Node.js a configurar - node-version: ${{ matrix.node }} -``` -{% endraw %} - -La acción `setup-node` es la forma recomendada de configurar una versión de Node.js cuando se usan ejecutores alojados {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la acción [`setup-node`](https://github.com/actions/setup-node). - -##### Ejemplo de ejecución con más de un sistema operativo - -Puedes crear una matriz para ejecutar flujos de trabajo en más de un sistema operativo del ejecutor. También puedes especificar más de una configuración de matriz. Este ejemplo crea una matriz de 6 trabajos: - -- 2 sistemas operativos especificados en la matriz `os` -- 3 versiones de Node.js especificadas en la matriz `node` - -{% data reusables.repositories.actions-matrix-builds-os %} - -{% raw %} -```yaml -runs-on: ${{ matrix.os }} -strategy: - matrix: - os: [ubuntu-16.04, ubuntu-18.04] - node: [6, 8, 10] -steps: - - uses: actions/setup-node@v1 - with: - node-version: ${{ matrix.node }} -``` -{% endraw %} - -Para encontrar opciones de configuración compatibles para ejecutores alojados {% data variables.product.prodname_dotcom %}, consulta "[Entornos virtuales para ejecutores alojados {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)". - -##### Ejemplo que incluye valores adicionales en combinaciones - -Puedes agregar más opciones de configuración a un trabajo de una matriz de construcción ya existente. Por ejemplo, si quieres usar una versión específica de `npm` cuando se ejecuta el trabajo que usa `windows-latest` y la versión 4 de `node`, puedes usar `incluir` para especificar esa opción adicional. - -{% raw %} -```yaml -runs-on: ${{ matrix.os }} -strategy: - matrix: - os: [macos-latest, windows-latest, ubuntu-18.04] - node: [4, 6, 8, 10] - include: - # includes a new variable of npm with a value of 2 - # for the matrix leg matching the os and version - - os: windows-latest - node: 4 - npm: 2 -``` -{% endraw %} - -##### Ejemplo que incluye combinaciones nuevas - -Puedes utilizar `include` para agregar jobs nuevos a una matriz de compilaciones. Cualquier configuración de "include" sin coincidencia exacta e agregará a la matriz. Por ejemplo, si quieres utilizar `node` versión 12 para compilar en varios sistemas operativos, pero quieres un job experimental extra que utilice node versión 13 en Ubintu, puedes utilizar `include` para especificar este job adicional. - - -{% raw %} -```yaml -runs-on: ${{ matrix.os }} -strategy: - matrix: - node: [12] - os: [macos-latest, windows-latest, ubuntu-18.04] - include: - - node: 13 - os: ubuntu-18.04 - experimental: true -``` -{% endraw %} - -##### Ejemplos que excluyen configuraciones de una matriz - -Puedes eliminar una configuración específica definida en la matriz de construcción mediante la opción `exclude`. Si usas `exclude`, se elimina un puesto definido por la matriz de construcción. El número de puestos es el producto cruzado de la cantidad de sistemas operativos (`os`) incluidos en las matrices que brindas, menos todas las sustracciones (`exclude`). - -{% raw %} -```yaml -runs-on: ${{ matrix.os }} -strategy: - matrix: - os: [macos-latest, windows-latest, ubuntu-18.04] - node: [4, 6, 8, 10] - exclude: - # excluye el nodo 4 en macOS - - os: macos-latest - node: 4 -``` -{% endraw %} - -{% note %} - -**Nota:** Todas las combinaciones de `include` se procesan después de `exclude`. Esto te permite utilizar `include` para volver a agregar combinaciones que se excluyeron previamente. - -{% endnote %} - -### **`jobs..strategy.fail-fast`** - -Cuando se establece en `true`, {% data variables.product.prodname_dotcom %} cancela todos los trabajos en curso si falla cualquier trabajo de `matriz`. Predeterminado: `true` - -### **`jobs..strategy.max-parallel`** - -La cantidad máxima de trabajos que se pueden ejecutar de manera simultánea cuando se utiliza una estrategia de trabajo `matrix`. De manera predeterminada, {% data variables.product.prodname_dotcom %} maximizará el número de trabajos ejecutados en paralelo dependiendo de los ejecutadores disponibles en las máquinas virtuales alojadas en {% data variables.product.prodname_dotcom %}. - -```yaml -strategy: - max-parallel: 2 -``` - -### **`jobs..continue-on-error`** - -Previene que una ejecución de flujo de trabajo falle cuando un job falle. Configúralo como `true` para permitir que la ejecución del flujo de trabajo pase cuando este job falle. - -#### Ejemplo que previene que un job específico de una matiz fallida haga que falle una ejecución de flujo de trabajo - -Puedes permitir que ciertos jobs en una matriz de jobs fallen sin que la ejecución de flujo de trabajo falle. Por ejemplo, si querías permitir que fallara únicamente un job experimental con el `node` configurado en `13` sin que fallara la ejecución del flujo de trabajo. - -{% raw %} -```yaml -runs-on: ${{ matrix.os }} -continue-on-error: ${{ matrix.experimental }} -strategy: - fail-fast: false - matrix: - node: [11, 12] - os: [macos-latest, ubuntu-18.04] - experimental: [false] - include: - - node: 13 - os: ubuntu-18.04 - experimental: true -``` -{% endraw %} - -### **`jobs..container`** - -Un contenedor para ejecutar todos los pasos de un trabajo que aún no especifica un contenedor. Si tienes pasos que usan tanto acciones de script como de contenedor, las acciones de contenedor se ejecutarán como contenedores hermanos en la misma red con los mismos montajes de volumen. - -Si no configuras un `container`, todos los pasos se ejecutan directamente en el host especificado por `runs-on` a menos que un paso se refiera a una acción configurada para ejecutarse en un contenedor. - -#### Ejemplo - -```yaml -jobs: - my_job: - container: - image: node:10.16-jessie - env: - NODE_ENV: development - ports: - - 80 - volumes: - - my_docker_volume:/volume_mount - options: --cpus 1 -``` - -Cuando solo especificas una imagen de contenedor, puedes omitir la palabra clave `image`. - -```yaml -jobs: - my_job: - container: node:10.16-jessie -``` - -#### **`jobs..container.image`** - -La imagen de Docker para usar como el contenedor para ejecutar la acción. El valor puede ser el nombre de la imagen de Docker Hub o un nombre de registro de docker público. - -#### **`jobs..container.env`** - -Establece una `mapa` de variables de entorno en el contenedor. - -#### **`jobs..container.ports`** - -Establece una `matriz` de puertos para exponer en el contenedor. - -#### **`jobs..container.volumes`** - -Establece una `matriz` de volúmenes para que el contenedor los use. Puedes usar volúmenes para compartir datos entre servicios u otros pasos en un trabajo. Puedes especificar volúmenes Docker con nombre, volúmenes Docker anónimos o montajes de enlace en el host. - -Para especificar un volumen, especifica la ruta de origen y destino: - -`:`. - -`` es un nombre de volumen o una ruta absoluta en la máquina host, y `` es una ruta absoluta en el contenedor. - -##### Ejemplo - -```yaml -volumes: - - my_docker_volume:/volume_mount - - /data/my_data - - /source/directory:/destination/directory -``` - -#### **`jobs..container.options`** - -Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta las opciones "[`docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". - -### **`jobs..services`** - -{% data reusables.github-actions.docker-container-os-support %} - -Se usa para hospedar contenedores de servicio para un trabajo en un flujo de trabajo. Los contenedores de servicio son útiles para crear bases de datos o servicios de caché como Redis. El ejecutor crea automáticamente una red Docker y administra el ciclo de vida de los contenedores de servicio. - -Si configuras tu trabajo para que se ejecute en un contenedor, o si tu paso usa acciones del contenedor, no necesitas asignar puertos para acceder al servicio o a la acción. Docker expone automáticamente todos los puertos entre contenedores en la misma red de puente definida por el usuario de Docker. Puedes hacer referencia directamente al contenedor de servicio por su nombre de host. El nombre del host se correlaciona automáticamente con el nombre de la etiqueta que configuraste para el servicio en el flujo de trabajo. - -Si configuras el trabajo para que se ejecute directamente en la máquina del ejecutor y tu paso no usa una acción de contenedor, debes asignar cualquier puerto del contenedor de servicio Docker que sea necesario para el host Docker (la máquina del ejecutor). Puedes acceder al contenedor de servicio utilizando host local y el puerto asignado. - -Para obtener más información acerca de las diferencias entre los contenedores de servicios de red, consulta "[Acerca de los contenedores de servicio](/actions/automating-your-workflow-with-github-actions/about-service-containers)". - -#### Ejemplo de uso de host local - -Este ejemplo crea dos servicios: nginx y Redis. Cuando especificas el puerto del host de Docker pero no el puerto del contenedor, el puerto del contenedor se asigna aleatoriamente a un puerto gratuito. {% data variables.product.prodname_dotcom %} establece el puerto del contenedor asignado en el contexto {% raw %}`$ {{job.services..ports}}`{% endraw %}. En este ejemplo, puedes acceder a los puertos del contenedor de servicio utilizando los contextos {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} y {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %}. - -```yaml -services: - nginx: - image: nginx - # Asignar puerto 8080 en el host de Docker al puerto 80 en el contenedor nginx - ports: - - 8080:80 - redis: - image: redis - # Asignar puerto TCP 6379 en el host de Docker a un puerto gratuito aleatorio en el contenedor Redis - ports: - - 6379/tcp -``` - -#### **`jobs..services.image`** - -La imagen de Docker para usar como el contenedor de servicios para ejecutar la acción. El valor puede ser el nombre de la imagen base de Docker o un Docker Hub o registro público. - -#### **`jobs..services.env`** - -Establece un `mapa` de variables de entorno en el contenedor de servicio. - -#### **`jobs..services.ports`** - -Establece una `matriz` de puertos para exponer en el contenedor de servicios. - -#### **`jobs..services.volumes`** - -Establece una `matriz` de volúmenes para que el contenedor de servicios los use. Puedes usar volúmenes para compartir datos entre servicios u otros pasos en un trabajo. Puedes especificar volúmenes Docker con nombre, volúmenes Docker anónimos o montajes de enlace en el host. - -Para especificar un volumen, especifica la ruta de origen y destino: - -`:`. - -`` es un nombre de volumen o una ruta absoluta en la máquina host, y `` es una ruta absoluta en el contenedor. - -##### Ejemplo - -```yaml -volumes: - - my_docker_volume:/volume_mount - - /data/my_data - - /source/directory:/destination/directory -``` - -#### **`jobs..services.options`** - -Opciones adicionales de recursos del contenedor Docker. Para obtener una lista de opciones, consulta las opciones "[`docker create`](https://docs.docker.com/engine/reference/commandline/create/#options)". - -### Hoja de referencia de patrones de filtro - -Puedes usar caracteres especiales en los filtros de ruta, de rama y de etiqueta. - -- `*`: Coincide con cero o más caracteres, pero no coincide con el caracter `/`. Por ejemplo, `Octo*` coincide con `Octocat`. -- `**`: Coincide con cero o más de cualquier caracter. -- `?`: Coincide con cero o un solo carácter. Por ejemplo, `Octoc?t` coincide con `Octocat`. -- `+`: Empata con uno o más de los caracteres precedentes. -- `[]` Coincide con un caracter que aparece en los corchetes o que se incluye en los rangos. Los rangos solo pueden incluir `a-z`, `A-Z` y `0-9`. Por ejemplo, el rango`[0-9a-f]` coincide con cualquier dígito o letra minúscula. Por ejemplo, `[CB]at` coincide con `Cat` o `Bat` y `[1-2]00` coincide con `100` y `200`. -- `!`: Al comienzo de un patrón hace que niegue los patrones positivos previos. No tiene ningún significado especial si no es el primer caracter. - -Los caracteres `*`, `[` y `!` son caracteres especiales en YAML. Si comienzas un patrón con `*`, `[` o `!`, tienes que encerrar el patrón entre comillas. - -```yaml -# Valid -- '**/README.md' - -# Invalid - creates a parse error that -# prevents your workflow from running. -- **/README.md -``` - -Para obtener más información acerca de la sintaxis de filtro de ramas, de etiquetas y de rutas, consulta "[`on..`](#onpushpull_requestbranchestags)" y "[`on..paths`](#onpushpull_requestpaths)". - -#### Patrones para encontrar ramas y etiquetas - -| Patrón | Descripción | Ejemplo de coincidencias | -| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -| `feature/*` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). | -`feature/my-branch`
    -`feature/your-branch` | -| `feature/**` | El comodín `**` encuentra cualquier caracter, incluida la barra (`/`) en los nombres de ramas y etiquetas. | -`feature/beta-a/my-branch`
    -`feature/your-branch`
    -`feature/mona/the/octocat` | -| -`master`
    -`releases/mona-the-octcat` | Encuentra el nombre exacto de una rama o el nombre de etiqueta. | -`master`
    -`releases/mona-the-octocat` | -| `'*'` | Encuentra todos los nombres de rama o de etiqueta que no contienen barra (`/`). El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | -`master`
    -`releases` | -| `'**'` | Encuentra todos los nombres de rama y de etiqueta. Este es el comportamiento predeterminado cuando no usas un filtro de `ramas` o `etiquetas`. | -`all/the/branches`
    -`every/tag` | -| `'*feature'` | El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | -`mona-feature`
    -`feature`
    -`ver-10-feature` | -| `v2*` | Encuentra los nombres de rama y de etiqueta que comienzan con `v2`. | -`v2`
    -`v2.0`
    -`v2.9` | -| `v[12].[0-9]+.[0-9]+` | Encuentra todas las etiquetas de versión semántica con las versiones principales 1 o 2 | -`v1.10.1`
    -`v2.0.0` | - -#### Patrones para encontrar rutas de archivos - -Los patrones de ruta deben coincidir con toda la ruta y comenzar desde la raíz del repositorio. - -| Patrón | Descripción de coincidencias | Ejemplo de coincidencias | -| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------- | -| `'*'` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). El caracter `*` es un caracter especial en YAML. Cuando comiences un patrón con `*`, debes usar comillas. | -`README.md`
    -`server.rb` | -| `'*.jsx?'` | El caracter `?` encuentra cero o uno de los caracteres de procedimiento. | -`page.js`
    -`page.jsx` | -| `'**'` | El comodín `*` encuentra cualquier caracter, incluida la barra (`/`). Este es el comportamiento predeterminado cuando no usas un filtro de `rutas`. | -`all/the/files.md` | -| `'*.js'` | El comodín `*` encuentra cualquier caracter, pero no encuentra la barra (`/`). Encuentra todos los archivos `.js` en la raíz del repositorio. | -`app.js`
    -`index.js` | -| `'**.js'` | Encuentra todos los archivos `.js` en el repositorio. | -`index.js`
    -`js/index.js`
    -`src/js/app.js` | -| `docs/*` | Todos los archivos dentro de la raíz del directorio `docs` en la raíz del repositorio. | -`docs/README.md`
    -`docs/file.txt` | -| `docs/**` | Todos los archivos en el directorio `docs` en la raíz del repositorio. | -`docs/README.md`
    -`docs/mona/octocat.txt` | -| `docs/**/*.md` | Un archivo con un sufijo `.md` en cualquier parte del directorio `docs`. | -`docs/README.md`
    -`docs/mona/hello-world.md`
    -`docs/a/markdown/file.md` | -| `'**/docs/**'` | Cualquier archivo en un directorio `docs` en cualquier parte del repositorio. | -`/docs/hello.md`
    -`dir/docs/my-file.txt`
    -`space/docs/plan/space.doc` | -| `'**/README.md'` | Un archivo README.md en cualquier parte del repositorio. | -`README.md`
    -`js/README.md` | -| `'**/*src/**'` | Cualquier archivo en una carpeta con un sufijo `src` en cualquier parte del repositorio. | -`a/src/app.js`
    -`my-src/code/js/app.js` | -| `'**/*-post.md'` | Un archivo con el sufijo `-post.md` en cualquier parte del repositorio. | -`my-post.md`
    -`path/their-post.md` | -| `'**/migrate-*.sql'` | Un archivo con el prefijo `migrate-` y el sufijo `.sql` en cualquier parte del repositorio. | -`migrate-10909.sql`
    -`db/migrate-v1.0.sql`
    -`db/sept/migrate-v1.sql` | -| -`*.md`
    -`!README.md` | Usar un signo de exclamación (`!`) frente a un patrón lo niega. Cuando un archivo coincida con un patrón y también coincida con un patrón negativo definido más adelante en el archivo, no se incluirá el archivo. | -`hello.md`
    _Does not match_
    -`README.md`
    -`docs/hello.md` | -| -`*.md`
    -`!README.md`
    -`README*` | Los patrones se marcan de forma secuencial. Un patrón que niega un patrón previo volverá a incluir las rutas del archivo. | -`hello.md`
    -`README.md`
    -`README.doc` | diff --git a/translations/es-XL/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-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md deleted file mode 100644 index 2178e29c21..0000000000 --- a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Permitir autenticación integrada para usuarios fuera de tu proveedor de identidad -intro: 'Puedes configurar una autenticación integrada para autenticar usuarios que no tienen acceso a tu proveedor de identidad que usa LDAP, SAML o CAS.' -redirect_from: - - /enterprise/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider - - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider - - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider -versions: - ghes: '*' -topics: - - Accounts - - Authentication - - Enterprise - - Identity ---- -### Acerca de la autenticación integrada para usuarios fuera de tu proveedor de identidad - -Puedes utilizar la autenticación integrada para usuarios externos cuando no puedes agregar cuentas específicas a tu proveedor de identidad (IdP), como cuentas para contratistas o usuarios de equipos. También puedes usar la autenticación integrada para acceder a una cuenta de reserva si el proveedor de identidad no está disponible. - -Una vez que se configura la autenticación integrada y un usuario autentica exitosamente con SAML o CAS, ya no tendrá la opción de autenticar con un nombre de usuario y una contraseña. Si un usuario autentica exitosamente con LDAP, las credenciales ya no se consideran internas. - -La autenticación integrada para un IdP se desactiva por defecto. - -{% warning %} - -**Advertencia:** Si desactivas la autenticación integrada, debes suspender individualmente a todo usuario que ya no debe tener acceso a la instancia. Para obtener más información, consulta [Suspender y anular suspensión de usuarios](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)." - -{% endwarning %} - -### Configurar autenticación integrada para usuarios fuera de tu proveedor de identidad - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -4. Selecciona tu proveedor de identidad. ![Seleccionar la opción proveedor de identidad](/assets/images/enterprise/management-console/identity-provider-select.gif) -5. Selecciona **Permitir la creación de cuentas con autenticación integrada**. ![Seleccionar la opción autenticación integrada](/assets/images/enterprise/management-console/built-in-auth-identity-provider-select.png) -6. Lee la advertencia, luego haz clic en **Aceptar**. - -{% data reusables.enterprise_user_management.two_factor_auth_header %} -{% data reusables.enterprise_user_management.2fa_is_available %} - -### Invitar a usuarios fuera de tu proveedor de identidad a autenticar tu instancia - -Cuando un usuario acepta la invitación, puede utilizar su nombre de usuario y contraseña para iniciar sesión en lugar de iniciar sesión a través del IdP. - -{% data reusables.enterprise_site_admin_settings.sign-in %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} -{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} - -### Leer más - -- "[Usar LDAP](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap)" -- "[Usar SAML](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-saml)" -- "[Usar CAS](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-cas)" diff --git a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/changing-authentication-methods.md b/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/changing-authentication-methods.md deleted file mode 100644 index 190fd2ec83..0000000000 --- a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/changing-authentication-methods.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Modificar los métodos de autenticación -intro: 'Puedes modificar la manera en que {% data variables.product.prodname_ghe_server %} se autentica con tus cuentas existentes en cualquier momento.' -redirect_from: - - /enterprise/admin/user-management/changing-authentication-methods - - /enterprise/admin/authentication/changing-authentication-methods - - /admin/authentication/changing-authentication-methods -versions: - ghes: '*' -topics: - - Accounts - - Authentication - - Enterprise - - Identity ---- -Cuando modificas el método de autenticación, las cuentas de usuario en {% data variables.product.product_location_enterprise %} se conservan y los usuarios seguirán iniciando sesión en la misma cuenta siempre que su nombre de usuario no cambie. - -Si el nuevo método de autenticación modifica los nombres de usuario, se crearán nuevas cuentas. Como administrador, puedes renombrar usuarios a través de los ajustes de administrador del sitio o utilizando [la API de Administración de Usuarios](/enterprise/{{currentVersion}}/v3/enterprise-admin/users/#rename-an-existing-user). - -Otras cuestiones que deberías tener en cuenta son las siguientes: - -* **Contraseñas:** Si comienzas a usar la autenticación integrada para tu instancia, los usuarios deben [configurar una contraseña](/enterprise/user/articles/how-can-i-reset-my-password/) una vez completado el cambio. - -* **Administradores del sitio:** Los privilegios administrativos son [controlados por tu proveedor de identidad cuando usas SAML](/enterprise/admin/guides/user-management/using-saml/#saml-attributes) y pueden ser [controlados por los miembros del grupo cuando usas LDAP](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance). - -* **Miembros del equipo:** Solo LDAP te permite [controlar los miembros del equipo](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance) desde tu servidor de directorios. - -* **Suspensión de usuario:** cuando usas LDAP para autenticar, se puede controlar el acceso al {% data variables.product.prodname_ghe_server %} mediante _grupos restringidos_. Después de cambiar a LDAP, si se configuran grupos restringidos, los usuarios existentes que no estén en uno de esos grupos serán suspendidos. La suspensión ocurrirá cuando inicien sesión o durante la siguiente sincronización LDAP. - -* **Miembros del grupo:** Cuando usas LDAP para autenticar, [se suspende y se anula la suspensión](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) de los usuarios automáticamente, en función de los miembros del grupo con restricciones y los estados de cuenta con Active Directory. - -* **Autenticación Git:** SAML y CAS solo admiten la autenticación Git a través de HTTP o HTTPS usando un [token de acceso personal](/articles/creating-an-access-token-for-command-line-use). No se admite la autenticación de contraseña a través de HTTP o HTTPS. LDAP admite la autenticación Git basada en contraseña por defecto, pero te recomendamos [desactivar ese método](/enterprise/admin/authentication/using-ldap#disabling-password-authentication-for-git-operations) y forzar la autenticación mediante un token de acceso personal o clave SSH. - -* **Autenticación de API:** SAML y CAS solo admiten la autenticación de API usando un [token de acceso personal](/articles/creating-an-access-token-for-command-line-use). No se admite la autenticación básica. - -* **Autenticación de dos factores:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %} - -* **Autenticación integrada para usuarios fuera de tu proveedor de identidad:** Puedes invitar usuarios a autenticar {% data variables.product.product_location_enterprise %} sin agregarlos a tu proveedor de identidad. Para obtener más información, consulta "[Permitir autenticación integrada para usuarios fuera de tu proveedor de identidad](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider)". diff --git a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md b/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md deleted file mode 100644 index 4326ee255c..0000000000 --- a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Desactivar los registros no autenticados -redirect_from: - - /enterprise/admin/articles/disabling-sign-ups/ - - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups - - /enterprise/admin/authentication/disabling-unauthenticated-sign-ups - - /admin/authentication/disabling-unauthenticated-sign-ups -intro: 'Si usas la autenticación integrada, puedes impedir que las personas no autenticadas puedan crear una cuenta.' -versions: - ghes: '*' -topics: - - Accounts - - Authentication - - Enterprise ---- -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.privacy %} -3. Quita la marca de selección en **Activar registro**. ![Habilitar casilla de registro](/assets/images/enterprise/management-console/enable-sign-up.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md b/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md deleted file mode 100644 index 48ac4c88fe..0000000000 --- a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Autenticar usuarios para tu instancia de servidor de GitHub Enterprise -intro: 'Puedes usar la autenticación integrada de {% data variables.product.prodname_ghe_server %} o elegir entre CAS, LDAP o SAML para integrar tus cuentas existentes y administrar centralmente el acceso de usuarios para {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/categories/authentication/ - - /enterprise/admin/guides/installation/user-authentication/ - - /enterprise/admin/articles/inviting-users/ - - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance/ - - /enterprise/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance - - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance -versions: - ghes: '*' -topics: - - Enterprise -children: - - /using-built-in-authentication - - /disabling-unauthenticated-sign-ups - - /using-cas - - /using-saml - - /using-ldap - - /allowing-built-in-authentication-for-users-outside-your-identity-provider - - /changing-authentication-methods ---- - diff --git a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md b/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md deleted file mode 100644 index c15c5d45e7..0000000000 --- a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Usar la autenticación integrada -intro: 'Cuando usas el método de autenticación predeterminado, todos los detalles de autenticación se almacenan dentro de {% data variables.product.product_location_enterprise %}. La autenticación integrada es el método predeterminado, si ya no tienes un proveedor de autenticación establecido, como LDAP, SAML o CAS.' -redirect_from: - - /enterprise/admin/user-management/using-built-in-authentication - - /enterprise/admin/authentication/using-built-in-authentication - - /admin/authentication/using-built-in-authentication -versions: - ghes: '*' -topics: - - Accounts - - Authentication - - Enterprise - - Identity ---- -Puedes crear mensajes personalizados que los usuarios verán en las páginas de inicio de sesión y de cierre de sesión. Para obtener más información, consulta "[Personalizar mensajes de usuario en tu instancia](/enterprise/admin/user-management/customizing-user-messages-on-your-instance)." - -### Configurar la autenticación integrada - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -4. Selecciona **Autenticación integrada**. ![Seleccionar la opción autenticación integrada](/assets/images/enterprise/management-console/built-in-auth-select.png) - -{% data reusables.enterprise_user_management.two_factor_auth_header %} -{% data reusables.enterprise_user_management.2fa_is_available %} - -### Crear tu cuenta y agregar usuarios - -Una vez que se ha creado tu instancia, necesitarás crear tu propia cuenta de administrador y usarla para aprovisionar usuarios. - -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 %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} -{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} diff --git a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md b/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md deleted file mode 100644 index 4924f82d6f..0000000000 --- a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Usar CAS -redirect_from: - - /enterprise/admin/articles/configuring-cas-authentication/ - - /enterprise/admin/articles/about-cas-authentication/ - - /enterprise/admin/user-management/using-cas - - /enterprise/admin/authentication/using-cas - - /admin/authentication/using-cas -intro: 'CAS es un protocolo de inicio de sesión único (SSO) para varias aplicaciones web. Una cuenta de usuario CAS no usa un {% if currentVersion ver_gt "enterprise-server@2.16" %}asiento{% else %}de licencia de usuario{% endif %} hasta que el usuario inicia sesión.' -versions: - ghes: '*' -topics: - - Accounts - - Authentication - - Enterprise - - Identity - - SSO ---- -{% data reusables.enterprise_user_management.built-in-authentication %} - -### Consideraciones sobre el nombre de usuario con CAS - -{% data reusables.enterprise_management_console.username_normalization %} - -{% data reusables.enterprise_management_console.username_normalization_sample %} - -{% data reusables.enterprise_user_management.two_factor_auth_header %} -{% data reusables.enterprise_user_management.external_auth_disables_2fa %} - -### Atributos de CAS - -Están disponibles los siguientes atributos. - -| Nombre del atributo | Tipo | Descripción | -| ------------------- | --------- | ----------------------------------------------------------------------------- | -| `nombre de usuario` | Requerido | El nombre de usuario {% data variables.product.prodname_ghe_server %}. | - -### Configurar CAS -{% warning %} - -**Advertencia:** Antes de configurar CAS en {% data variables.product.product_location_enterprise %}, ten en cuenta que los usuarios no podrán usar sus nombres de usuario ni contraseñas CAS para autenticar las solicitudes de API o las operaciones Git a través de HTTP/HTTPS. En cambio, será necesario que [creen un token de acceso](/enterprise/{{ currentVersion }}/user/articles/creating-an-access-token-for-command-line-use). - -{% endwarning %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -3. Selecciona **CAS**. ![Seleccionar CAS](/assets/images/enterprise/management-console/cas-select.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación autenticación integrada](/assets/images/enterprise/management-console/cas-built-in-authentication.png) -5. En el campo **URL del servidor**, escribe la URL completa de tu servidor CAS. Si tu servidor CAS usa un certificado que no puede ser validado por {% data variables.product.prodname_ghe_server %}, puedes usar el comando `ghe-ssl-ca-certificate-install` para instalarlo como un certificado de confianza. diff --git a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md b/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md deleted file mode 100644 index 1d561b4339..0000000000 --- a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -title: Usar LDAP -redirect_from: - - /enterprise/admin/articles/configuring-ldap-authentication/ - - /enterprise/admin/articles/about-ldap-authentication/ - - /enterprise/admin/articles/viewing-ldap-users/ - - /enterprise/admin/hidden/enabling-ldap-sync/ - - /enterprise/admin/hidden/ldap-sync/ - - /enterprise/admin/user-management/using-ldap - - /enterprise/admin/authentication/using-ldap - - /admin/authentication/using-ldap -intro: 'LDAP te permite autenticar el {% data variables.product.prodname_ghe_server %} en tus cuentas existentes y administrar de manera centralizada el acceso a los repositorios. LDAP es un protocolo de aplicación popular para acceder a servicios de información de directorios y mantenerlos, y uno de los protocolos más comunes que se usan para integrar software de terceros con directorios de usuarios de empresas grandes.' -versions: - ghes: '*' -topics: - - Accounts - - Authentication - - Enterprise - - Identity ---- -{% data reusables.enterprise_user_management.built-in-authentication %} - -### Servicios LDAP admitidos - -El {% data variables.product.prodname_ghe_server %} se integra con los siguientes servicios LDAP: - -* Active Directory -* FreeIPA -* Oracle Directory Server Enterprise Edition -* OpenLDAP -* Open Directory -* 389-ds - -### Consideraciones sobre el nombre de usuario con LDAP - -{% data reusables.enterprise_management_console.username_normalization %} - -{% data reusables.enterprise_management_console.username_normalization_sample %} - -{% data reusables.enterprise_user_management.two_factor_auth_header %} -{% data reusables.enterprise_user_management.2fa_is_available %} - -### Configurar LDAP con {% data variables.product.product_location_enterprise %} - -Una vez configurado LDAP, los usuarios podrán iniciar sesión en tu instancia con sus credenciales LDAP. Cuando los usuarios inician sesión por primera vez, sus nombres de perfil, direcciones de correo electrónico y claves SSH se establecen con los atributos de LDAP desde tu directorio. - -Cuando configuras el acceso de LDAP para los usuarios a través de {% data variables.enterprise.management_console %}, tus licencias de usuario no se utilizarán sino hasta que los usuarios ingresen en tu instancia por primera vez. Sin embargo, si creas una cuenta manualmente utilizando la configuración de administrador para el sitio, esta licencia de usuario se tomará en cuenta. - -{% warning %} - -**Advertencia:** Antes de configurar LDAP en {% data variables.product.product_location_enterprise %}, asegúrate de que tu servicio LDAP admita resultados paginados. - -{% endwarning %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -3. En "Authentication" (Autenticación), selecciona **LDAP**. ![Seleccionar LDAP](/assets/images/enterprise/management-console/ldap-select.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación autenticación integrada LDAP](/assets/images/enterprise/management-console/ldap-built-in-authentication.png) -5. Agrega tus parámetros de configuración. - -### Atributos de LDAP -Usa estos atributos para terminar de configurar LDAP para {% data variables.product.product_location_enterprise %}. - -| Nombre del atributo | Tipo | Descripción | -| --------------------------------------------------------------------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Host` | Requerido | El host LDAP, p. ej. `ldap.example.com` o `10.0.0.30`. Si el nombre del host solo está disponible desde tu red interna, es posible que primero debas configurar el DNS de {% data variables.product.product_location_enterprise %} para que pueda resolver el nombre del host usando tus servidores de nombres internos. | -| `Port (Puerto)` | Requerido | El puerto que están escuchando los servicios LDAP. Los ejemplos incluyen: 389 y 636 (para LDAPS). | -| `Encryption (Cifrado)` | Requerido | El método de cifrado usado para garantizar las comunicaciones con el servidor LDAP. Los ejemplos incluyen el normal (sin cifrado), el SSL/LDAPS (cifrado desde el principio) y el StartTLS (se actualiza a comunicación cifrada una vez que se conecta). | -| `Domain search user (Usuario de búsqueda de dominio)` | Opcional | El usuario LDAP que realiza las búsquedas de usuario para autenticar otros usuarios cuando inician sesión. Esto suele ser una cuenta de servicio creada específicamente para integraciones de terceros. Usa un nombre certificado completo, como `cn=Administrator,cn=Users,dc=Example,dc=com`. Con Active Directory, también puedes usar la sintaxis `[DOMAIN]\[USERNAME]` (p. ej.,`WINDOWS\Administrator`) para el usuario de búsqueda de dominio. | -| `Domain search password (Contraseña de búsqueda de dominio)` | Opcional | La contraseña para el usuario de búsqueda de dominio. | -| `Administrators group (Grupo de administradores)` | Opcional | Los usuarios de este grupo son promovidos a administradores del sitio cuando inician sesión en tu aparato. Si no configuras un Grupo de administradores LDAP, la primera cuenta de usuario LDAP que inicie sesión en tu aparato será promovida automáticamente a administrador del sitio. | -| `Domain base (Base de dominio)` | Requerido | El `Nombre Distintivo` (DN) completamente calificado de un subárbol LDAP que quieras buscar para usuarios y grupos. Puedes agregar tantos como quieras; sin embargo, cada grupo debe estar definido en la misma base de dominio que los usuarios que le pertenecen. Si especificas grupos de usuarios con restricciones, solo los usuarios que pertenecen a esos grupo estarán al alcance. Te recomendamos que especifiques el primer nivel de tu árbol de directorios LDAP como tu base de dominio y que uses grupos de usuarios con restricciones para controlar el acceso. | -| `Restricted user groups (Grupos de usuarios con restricciones)` | Opcional | Si se especifica, solo los usuarios de estos grupos tendrán permiso para iniciar sesión. Solo necesitas especificar los nombres comunes (CN) de los grupos y puedes agregar tantos grupos como quieras. Si no se especifica ningún grupo, *todos* los usuarios dentro del alcance de la base de dominio especificada podrán iniciar sesión en tu instancia del {% data variables.product.prodname_ghe_server %}. | -| `User ID (Identificación de usuario)` | Requerido | El atributo de LDAP que identifica al usuario LDAP que intenta una autenticación. Una vez que se establece una asignación, los usuarios pueden modificar sus nombres de usuario del {% data variables.product.prodname_ghe_server %}. El campo debería ser `sAMAccountName` para la mayoría de las instalaciones de Active Directory, pero puede ser `uid` para otras soluciones LDAP, como OpenLDAP. El valor predeterminado es `uid`. | -| `Nombre de perfil` | Opcional | El nombre que aparecerá en la página de perfil del {% data variables.product.prodname_ghe_server %} del usuario. A menos que la sincronización LDAP esté activada, los usuarios pueden modificar sus nombres de perfil. | -| `Emails (Correos electrónicos)` | Opcional | Las direcciones de correo electrónico para la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. | -| `SSH keys (Claves SSH)` | Opcional | Las claves SSH públicas vinculadas a la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. Las claves deben ser en formato OpenSSH. | -| `Claves GPG` | Opcional | Las claves GPG vinculadas a la cuenta del {% data variables.product.prodname_ghe_server %} de un usuario. | -| `Disable LDAP authentication for Git operations (Desactivar la autenticación LDAP para las operaciones de Git)` | Opcional | Si está seleccionado, [desactiva](#disabling-password-authentication-for-git-operations) la posibilidad del usuario de usar contraseñas LDAP para autenticar las operaciones de Git. | -| `Enable LDAP certificate verification (Activar la verificación de certificado LDAP)` | Opcional | Si está seleccionado, [activa](#enabling-ldap-certificate-verification) la verificación de certificado LDAP. | -| `Synchronization (Sincronización)` | Opcional | Si está seleccionado, [activa](#enabling-ldap-sync) la sincronización LDAP. | - -#### Desactivar la autenticación de contraseña para las operaciones de Git - -Selecciona **Disable username and password authentication for Git operations** (Desactivar la autenticación de nombre de usuario y contraseña para las operaciones de Git) en los parámetros de tu LDAP para implementar el uso de los tokens de acceso personal o las claves SSH para el acceso a Git, que pueden ayudarte a prevenir que tu servidor se sobrecargue de solicitudes de autenticación LDAP. Recomendamos esta configuración, ya que un servidor LDAP de respuesta lenta, en especial combinado con una gran cantidad de solicitudes debido al sondeo, suele ser una causa de problemas e interrupciones. - -![Desactivar la casilla de verificación autenticación de contraseña LDAP](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png) - -Cuando se selecciona esta opción, si un usuario intenta usar una contraseña para las operaciones de Git a través de la línea de comando, recibirá un mensaje de error que dice: `La autenticación de contraseña no está permitida para las operaciones de Git. Debes usar un token de acceso personal.` - -#### Activar la verificación de certificado LDAP - -Selecciona **Enable LDAP certificate verification** (Activar verificación de certificado LDAP) en tus parámetros LDAP para validar el certificado del servidor LDAP que usas con TLS. - -![Casilla de verificación de certificado LDAP](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png) - -Cuando se selecciona esta opción, el certificado se valida para garantizar que: -- Si el certificado contiene al menos un nombre alternativo del firmante (SAN), uno de los SAN coincida con el nombre del host de LDAP. De lo contrario, que el nombre común (CN) coincida con el nombre del host de LDAP. -- El certificado no haya vencido. -- El certificado esté firmado por una entidad de certificación (CA) de confianza. - -#### Activar la sincronización LDAP - -La sincronización LDAP te permite sincronizar usuarios y miembros del equipo del {% data variables.product.prodname_ghe_server %} con tus grupos LDAP establecidos. Esto te permite establecer un control de acceso basado en roles para los usuarios desde tu servidor LDAP, en lugar de hacerlo de forma manual dentro del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Crear equipos](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)". - -Para activar la sincronización LDAP, en tus parámetros LDAP, selecciona **Synchronize Emails** (Sincronizar correos electrónicos), **Synchronize SSH Keys** (Sincronizar claves SSH) o **Synchronize GPG Keys** (Sincronizar claves GPG). - -![Casilla de verificación de Sincronización](/assets/images/enterprise/management-console/ldap-synchronize.png) - -Una vez que actives la sincronización LDAP, se ejecutará un trabajo de sincronización en el intervalo de tiempo especificado para realizar las siguientes operaciones en cada cuenta de usuario: - -- Si has permitido la autenticación integrada para usuarios externos a tu proveedor de identidad, y el usuario está usando la autenticación integrada, pasa al siguiente usuario. -- Si no existe una asignación LDAP para el usuario, intenta asignar el usuario a una entrada LDAP en el directorio. Si el usuario no se puede asignar a una entrada LDAP, suspéndelo y pasa al siguiente usuario. -- Si hay una asignación LDAP y falta la entrada LDAP correspondiente en el directorio, suspende el usuario y pasa al siguiente usuario. -- Si la entrada LDAP correspondiente se marcó como desactivada, y el usuario aún no se suspendió, suspéndelo y pasa al siguiente usuario. -- Si la entrada LDAP correspondiente no se marcó como desactivada, el usuario está suspendido y _Reactivate suspended users_ (Reactivar usuarios suspendidos) está activado en el centro de administración, anula la suspensión del usuario. -- Si la entrada LDAP correspondiente incluye un atributo `name`, actualiza el nombre de perfil del usuario. -- Si la entrada LDAP correspondiente está en el grupo de administradores, promueve al usuario a administrador del sitio. -- Si la entrada LDAP correspondiente no está en el grupo de administradores, degrada al usuario a una cuenta normal. -- Si un campo de usuario LDAP está definido para correos electrónicos, sincroniza los parámetros del correo electrónico del usuario con la entrada LDAP. Establece la primera entrada `mail` LDAP como el correo electrónico principal. -- Si un campo de usuario LDAP está definido para claves públicas SSH, sincroniza las claves SSH públicas del usuario con la entrada LDAP. -- Si un campo de usuario LDAP está definido para claves GPG, sincroniza las claves GPG del usuario con la entrada LDAP. - -{% note %} - -**Nota**: Las entradas LDAP solo pueden estar marcadas como desactivadas si usas Active Directory y el atributo `userAccountControl` está presente y marcado con `ACCOUNTDISABLE`. - -{% endnote %} - -También se ejecutará un trabajo de sincronización en el intervalo de tiempo especificado para realizar las siguientes operaciones en cada equipo que haya sido asignado a un grupo LDAP: - -- Si se eliminó el grupo LDAP correspondiente de un equipo, elimina todos los miembros del equipo. -- Si las entradas de miembros LDAP se eliminaron del grupo LDAP, elimina los usuarios correspondientes del equipo. Si como resultado el usuario pierde acceso a algún repositorio, elimina toda bifurcación privada que el usuario tenga de esos repositorios. -- Si las entradas de miembros LDAP se agregaron al grupo LDAP, agrega los usuarios correspondientes al equipo. Si como resultado el usuario recupera el acceso a algún repositorio, restablece toda bifurcación privada de los repositorios que haya sido eliminada debido a que el usuario perdió acceso en los últimos 90 días. - -{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} - -{% warning %} - -**Advertencia de seguridad:** - -Cuando la sincronización LDAP está activada, los administradores del sitio y los propietarios de la organización pueden buscar en el directorio LDAP los grupos a los cuales asignar el equipo. - -Esto posibilita divulgar información organizativa confidencial a contratistas u otros usuarios sin privilegios, incluidos los siguientes: - -- La existencia de grupos LDAP específicos visibles para el *Usuario de búsqueda de dominio*. -- Los miembros del grupo LDAP que tienen cuentas de usuario del {% data variables.product.prodname_ghe_server %}, que se divulga cuando se crea un equipo sincronizado con ese grupo LDAP. - -Si no se desea divulgar dicha información, su empresa u organización debe restringir los permisos del *Usuario de búsqueda de dominio* en la consola de administración. Si no es posible aplicar dicha restricción, comuníquese con el {% data variables.contact.contact_ent_support %}. - -{% endwarning %} - -#### Clases de objetos del grupo LDAP admitidas - -El {% data variables.product.prodname_ghe_server %} admite estas clases de objetos del grupo LDAP. Los grupos se pueden anidar. - -- `grupo` -- `groupOfNames` -- `groupOfUniqueNames` -- `posixGroup` - -### Ver y crear usuarios LDAP - -Puedes ver la lista completa de usuarios LDAP que tienen acceso a tu instancia y aprovisionar nuevos usuarios. - -{% data reusables.enterprise_site_admin_settings.sign-in %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -3. En la barra lateral izquierda, haz clic en **LDAP users** (Usuarios LDAP). ![Pestaña LDAP users (Usuarios LDAP)](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png) -4. Para buscar un usuario, escribe un nombre de usuario completo o parcial y haz clic en **Search** (Buscar). Se mostrarán los usuarios existentes en los resultados de búsqueda. Si un usuario no existe, haz clic en **Create** (Crear) para aprovisionar la nueva cuenta de usuario. ![Búsqueda LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-search.png) - -### Actualizar cuentas LDAP - -A menos que [la sincronización LDAP esté activada](#enabling-ldap-sync), las modificaciones de las cuentas LDAP no se sincronizan automáticamente con el {% data variables.product.prodname_ghe_server %}. - -* Para usar un nuevo grupo de administración LDAP, los usuarios deben ser promovidos y degradados de forma manual en el {% data variables.product.prodname_ghe_server %} para reflejar las modificaciones en LDAP. -* Para agregar o eliminar cuentas LDAP de los grupos de administración LDAP, [promueve o degrada las cuentas en el {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/promoting-or-demoting-a-site-administrator). -* Para eliminar las cuentas LDAP, [suspende las cuentas del {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users). - -#### Sincronizar cuentas LDAP de forma manual - -{% data reusables.enterprise_site_admin_settings.sign-in %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user %} -{% data reusables.enterprise_site_admin_settings.click-user %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -5. En "LDAP", haz clic en **Sync now** (Sincronizar ahora) para actualizar de forma manual la cuenta con los datos de tu servidor LDAP. ![Botón LDAP sync now (Sincronizar LDAP ahora)](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) - -También puedes [utilizar la API para activar una sincronización manual](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap). - -### Revocar acceso a {% data variables.product.product_location_enterprise %} - -Si [la sincronización LDAP está activada](#enabling-ldap-sync), al eliminar las credenciales LDAP de un usuario, se suspenderá su cuenta hasta la siguiente ejecución de sincronización. - -Si la sincronización LDAP **no** está activada, debes suspender de forma manual la cuenta del {% data variables.product.prodname_ghe_server %} después de eliminar las credenciales LDAP. Para obtener más información, consulta "[Suspender y anular suspensión de usuarios](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users)". diff --git a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md b/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md deleted file mode 100644 index 7c27b5b9e7..0000000000 --- a/translations/es-XL/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -title: Usar SAML -redirect_from: - - /enterprise/admin/articles/configuring-saml-authentication/ - - /enterprise/admin/articles/about-saml-authentication/ - - /enterprise/admin/user-management/using-saml - - /enterprise/admin/authentication/using-saml - - /admin/authentication/using-saml -intro: 'SAML es un estándar basado en XML para autenticación y autorización. {% data variables.product.prodname_ghe_server %} puede actuar como un proveedor de servicios (SP) con tu proveedor de identidad (IdP) SAML interno.' -versions: - ghes: '*' -topics: - - Accounts - - Authentication - - Enterprise - - Identity - - SSO ---- -{% data reusables.enterprise_user_management.built-in-authentication %} - -### Servicios SAML admitidos - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.saml.saml-single-logout-not-supported %} - -### Consideraciones sobre el nombre de usuario con SAML - -Cada nombre de usuario {% data variables.product.prodname_ghe_server %} lo determina una de las siguientes aserciones en la respuesta SAML, ordenadas por prioridad: - -- El atributo de nombre de usuario personalizado, si está definido y si hay uno. -- Una aserción `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`, si hay una. -- Una aserción `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` assertion, si hay una. -- El elemento `NameID`. - -Se requiere el elemento `NameID`, incluso si hay otros atributos. - -Se crea una asignación entre el `NameID` y el nombre de usuario {% data variables.product.prodname_ghe_server %}, para que el `NameID` sea persistente, único y no esté sujeto a cambios durante el ciclo de vida del usuario. - -{% note %} - -**Nota**: Si la `NameID` de un usuario sí cambia en el IdP, el usuario verá un mensaje de error cuando intente ingresar en tu instancia de {% data variables.product.prodname_ghe_server %}. {% if currentVersion ver_gt "enterprise-server@2.21" %}Para restablecer el acceso del usuario, necesitarás actualizar el mapeo de la `NameID` de la cuenta del usuario. Para obtener más información, consulta la sección "[Actualizar la `NameID`](#updating-a-users-saml-nameid) de SAML de un usuario.{% else %} Para obtener más información, consulta "[Error: "Otro usuario ya tiene esta cuenta"](#error-another-user-already-owns-the-account)".{% endif %} - -{% endnote %} - -{% data reusables.enterprise_management_console.username_normalization %} - -{% data reusables.enterprise_management_console.username_normalization_sample %} - -{% data reusables.enterprise_user_management.two_factor_auth_header %} -{% data reusables.enterprise_user_management.external_auth_disables_2fa %} - -### Metadatos SAML - -Los metadatos del proveedor de servicios de tu instancia {% data variables.product.prodname_ghe_server %} están disponible en `http(s)://[hostname]/saml/metadata`. - -Para configurar tu proveedor de identidad de forma manual, la URL del Servicio de consumidor de aserciones (ACS) es `http(s)://[hostname]/saml/consume`. Esta usa el enlace `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. - -### Atributos de SAML - -Estos atributos están disponibles. Puedes modificar el nombre del atributo en [Consola de administración](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), a excepción del atributo `administrator`. - -| Nombre de atributo predeterminado | Tipo | Descripción | -| --------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ID del nombre` | Requerido | Un identificador de usuario persistente. Se puede usar cualquier formato de identificador de nombre persistente. El elemento `NameID` se usará para un nombre de usuario {% data variables.product.prodname_ghe_server %}, a menos que se proporcione una de las aserciones alternativas. | -| `administrador` | Opcional | Cuando el valor es "true", el usuario será promovido automáticamente como un administrador. Cualquier otro valor o un valor no existente degradará al usuario a una cuenta de usuario normal. | -| `nombre de usuario` | Opcional | El nombre de usuario {% data variables.product.prodname_ghe_server %}. | -| `nombre_completo` | Opcional | El nombre del usuario que se muestra en su página de perfil. Los usuarios pueden cambiar sus nombres después del aprovisionamiento. | -| `correos electrónicos` | Opcional | Las direcciones de correo electrónico para el usuario. Se puede especificar más de una. | -| `claves_públicas` | Opcional | Las claves SSH públicas para el usuario. Se puede especificar más de una. | -| `claves_gpg` | Opcional | Las claves GPG para el usuario. Se puede especificar más de una. | - -### Configurar parámetros SAML - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.authentication %} -3. Selecciona **SAML**. ![Autenticación SAML](/assets/images/enterprise/management-console/auth-select-saml.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Seleccionar la casilla de verificación Autenticación integrada SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -5. Opcionalmente, para activar el SSO de respuesta no solicitada, selecciona **IdP initiated SSO**. Por defecto, {% data variables.product.prodname_ghe_server %} responderá a una solicitud iniciada por un proveedor de identidad (IdP) no solicitada con una `AuthnRequest` de vuelta al IdP. ![SSO del IdP SAML](/assets/images/enterprise/management-console/saml-idp-sso.png) - - {% tip %} - - **Nota**: Te recomendamos mantener este valor **sin seleccionar**. Debes activar esta función **solo** en el caso inusual que tu implementación SAML no admita el SSO iniciado del proveedor de servicios y que {% data variables.contact.enterprise_support %} lo aconseje. - - {% endtip %} - -5. Selecciona **Disable administrator demotion/promotion (Desactivar la degradación/promoción del administrador)** si **no** quieres que tu proveedor de SAML determine los derechos del administrador para los usuarios en {% data variables.product.product_location_enterprise %}. ![Configuración de administración para desactivar SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) -6. En el campo **URL de inicio de sesión único**, escribe la HTTP o el extremo HTTPS en tu IdP para las solicitudes de inicio de sesión único. Este valor lo provee la configuración de tu IdP. Si el host solo está disponible desde tu red interna, es posible que sea necesario [configurar {% data variables.product.product_location_enterprise %} para usar los servidores de nombres internos](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). ![Autenticación SAML](/assets/images/enterprise/management-console/saml-single-sign-url.png) -7. También puedes escribir tu nombre de emisor de SAML en el campo **Emisor**. Esto verifica la autenticidad de los mensajes enviados a {% data variables.product.product_location_enterprise %}. ![Emisor SAML](/assets/images/enterprise/management-console/saml-issuer.png) -8. En los menúes desplegables **Método de firma** y **Método de resumen**, elige el algoritmo de hash que usa tu emisor SAML para verificar la integridad de las respuestas desde {% data variables.product.product_location_enterprise %}. Especifica el formato con el menú desplegable **Formato de identificador de nombre**. ![Método SAML](/assets/images/enterprise/management-console/saml-method.png) -9. Dentro de **Verification certificate (Certificado de comprobación)**, haz clic en **Choose File (Elegir archivo)** y elige un certificado para validar las respuestas SAML desde el IdP. ![Autenticación SAML](/assets/images/enterprise/management-console/saml-verification-cert.png) -10. Modifica los nombres de atributo de SAML para hacerlos coincidir con tu IdP, si es necesario, o acepta los nombres predeterminados. ![Nombres de atributo de SAML](/assets/images/enterprise/management-console/saml-attributes.png) - -{% if currentVersion ver_gt "enterprise-server@2.21" %} - -### Revocar acceso a {% data variables.product.product_location_enterprise %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -2. Selecciona **SAML**. !["All users" sidebar item in site administrator settings](/assets/images/enterprise/site-admin-settings/all-users.png) -3. En la lista de usuarios, da clic en el nombre de usuario del cual te gustaría actualizar el mapeo de la `NameID`. ![Username in list of instance user accounts](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) -{% data reusables.enterprise_site_admin_settings.security-tab %} -5. Dentro de **Verification certificate (Certificado de comprobación)**, haz clic en **Choose File (Elegir archivo)** y elige un certificado para validar las respuestas SAML desde el IdP. !["Edit" button under "SAML authentication" and to the right of "Update SAML NameID"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) -6. En el campo de "NameID", teclea la `NameID` nueva para el usuario. !["NameID" field in modal dialog with NameID typed](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) -7. Da clic en **Actualizar NameID**. !["Update NameID" button under updated NameID value within modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) - -{% endif %} - -### Revocar acceso a {% data variables.product.product_location_enterprise %} - -Si eliminas un usuario desde tu proveedor de identidad, también debes suspenderlos de forma manual. De lo contrario, seguirán estando disponibles para autenticarse usando los tokens de acceso o las claves SSH. Para obtener más información, consulta "[Suspender y anular suspensión de usuarios](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". - -### Requisitos para los mensajes de respuesta - -El mensaje de respuesta debe cumplir con los siguientes requisitos: - -- Se debe proporcionar el elemento `` en el documento de respuesta raíz y empatar la URL ACS únicamente cuando dicho documento se firme. Si la aserción está firmada, ésta se ignorará. -- Siempre deberá proporcionarse el elemento `` como parte del elemento ``. Siempre deberá proporcionarse el elemento `` como parte del elemento ``. Ésta es la URL para la instancia de {% data variables.product.prodname_ghe_server %}, tal como `https://ghe.corp.example.com`. -- Cada aserción en la respuesta **debe** estar protegida por una firma digital. Esto se puede lograr firmando cada elemento `` individual o firmando el elemento ``. -- Un elemento `` se debe proporcionar como parte del elemento ``. Se puede usar cualquier formato de identificador de nombre persistente. -- El atributo `Recipient` debe estar presente y establecido en la URL ACS. Por ejemplo: - -```xml - - - - ... - - - - - - - monalisa - - - - -``` - -### Autenticación SAML - -de entidad del {% data variables.product.prodname_ghe_server %}, se presentará el siguiente mensaje de error en el registro de autenticación: Para obtener más información sobre los requisitos de respuesta de SAML, consulta la sección "[Requisitos de mensaje de respuesta](#response-message-requirements)". - -#### Error: "Otro usuario ya tiene la cuenta" - -Cuando un usuario ingresa en {% data variables.product.prodname_ghe_server %} por primera vez con la autenticación de SAML, {% data variables.product.prodname_ghe_server %} crea una cuenta de usuario en la instancia y mapea la `NameID` de SAML hacia la cuenta. - -Cuando el usuario vuelve a ingresar, {% data variables.product.prodname_ghe_server %} compara el mapeo de la `NameID` de la cuenta con la respuesta del IdP. Si la `NameID` en la respuesta del IdP ya no empata con la `NameID` que {% data variables.product.prodname_ghe_server %} espera para el usuario, el inicio de sesión fallará. El usuario verá el siguiente mensaje. - -> Another user already owns the account. Please have your administrator check the authentication log. - -The message typically indicates that the person's username or email address has changed on the IdP. {% if currentVersion ver_gt "enterprise-server@2.21" %}Ensure that the `NameID` mapping for the user account on {% data variables.product.prodname_ghe_server %} matches the user's `NameID` on your IdP. For more information, see "[Updating a user's SAML `NameID`](#updating-a-users-saml-nameid)."{% else %}For help updating the `NameID` mapping, contact {% data variables.contact.contact_ent_support %}.{% endif %} - -#### Si la respuesta SAML no está firmada o la firma no coincide con los contenidos, se presentará el siguiente mensaje de error en el registro de autenticación: - -Si el `Recipient` no coincide con la URL ACS, se presentará el siguiente mensaje de error en el registro de autenticación: - -``` -El destinatario en la respuesta SAML no debe estar en blanco. -``` - -``` -El destinatario en la respuesta SAML no era válido. -``` - -Ensure that you set the value for `Recipient` on your IdP to the full ACS URL for your {% data variables.product.prodname_ghe_server %} instance. Por ejemplo, `https://ghe.corp.example.com/saml/consume`. - -#### Error: "SAML Response is not signed or has been modified" - -If your IdP does not sign the SAML response, or the signature does not match the contents, the following error message will appear in the authentication log. - -``` -La respuesta SAML no está firmada o ha sido modificada. -``` - -Ensure that you configure signed assertions for the {% data variables.product.prodname_ghe_server %} application on your IdP. - -#### Error: "Audience is invalid" or "No assertion found" - -If the IdP's response has a missing or incorrect value for `Audience`, the following error message will appear in the authentication log. - -```shell -La audiencia es no válida. Audience attribute does not match https://YOUR-INSTANCE-URL -``` - -Ensure that you set the value for `Audience` on your IdP to the `EntityId` for your {% data variables.product.prodname_ghe_server %} instance, which is the full URL to your {% data variables.product.prodname_ghe_server %} instance. Por ejemplo, `https://ghe.corp.example.com`. diff --git a/translations/es-XL/content/admin/authentication/index.md b/translations/es-XL/content/admin/authentication/index.md deleted file mode 100644 index 9a8e03d38e..0000000000 --- a/translations/es-XL/content/admin/authentication/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Autenticación -intro: 'Puedes usar la autenticación integrada de {% data variables.product.prodname_ghe_server %} o elegir entre CAS, LDAP o SAML para integrar tus cuentas existentes y administrar centralmente el acceso de usuarios para {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/authentication -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /authenticating-users-for-your-github-enterprise-server-instance - - /managing-identity-and-access-for-your-enterprise - - /configuring-authentication-and-provisioning-with-your-identity-provider ---- -### Índice diff --git a/translations/es-XL/content/admin/configuration/configuring-advanced-security-features/configuring-code-scanning-for-your-appliance.md b/translations/es-XL/content/admin/configuration/configuring-advanced-security-features/configuring-code-scanning-for-your-appliance.md deleted file mode 100644 index f0ca9a2495..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-advanced-security-features/configuring-code-scanning-for-your-appliance.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Configuring code scanning for your appliance -shortTitle: Configurar el escaneo de código -intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location_enterprise %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.' -product: '{% data reusables.gated-features.code-scanning %}' -miniTocMaxHeadingLevel: 4 -redirect_from: - - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance - - /admin/configuration/configuring-code-scanning-for-your-appliance -versions: - enterprise-server: '>=2.22' -topics: - - Enterprise ---- -{% data reusables.code-scanning.beta %} - -### Acerca de {% data variables.product.prodname_code_scanning %} - -{% data reusables.code-scanning.about-code-scanning %} - -The table below summarizes the available types of analysis for {% data variables.product.prodname_code_scanning %}, and provides links on enabling the feature for individual repositories. - -{% data reusables.code-scanning.enabling-options %} - -For the users of {% data variables.product.product_location_enterprise %} to be able to enable and use {% data variables.product.prodname_code_scanning %} in their repositories, you need, as a site administrator, to enable this feature for the whole appliance. - -### How do I know if {% data variables.product.prodname_code_scanning %} is enabled for my appliance - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -1. Check if there is an **{% data variables.product.prodname_advanced_security %}** entry in the left sidebar. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) - -If you can't see **{% data variables.product.prodname_advanced_security %}** 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 %}. The {% data variables.product.prodname_advanced_security %} license gives you and your users access to features that help you make your repositories and code more secure. - -### Habilitar {% data variables.product.prodname_code_scanning %} - -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} - -{% 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 "{% data variables.product.prodname_advanced_security %}," click **{% 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) -{% data reusables.enterprise_management_console.save-settings %} - - -### Running {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %} - -#### Setting up a self-hosted runner - -If you are enrolled in the {% data variables.product.prodname_actions %} beta, then {% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." - -#### Provisioning the action -To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate action must be available locally. You can make the action 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)." -- 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_enterprise %} 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_enterprise %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer. -- You can create a local copy of the action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository with the action. For example, if you want to use the {% data variables.product.prodname_codeql %} action, 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. - - -##### 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)." -2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location_enterprise %}. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." -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. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." - -After you configure a self-hosted runner, users can enable {% data variables.product.prodname_code_scanning %} for individual repositories on {% data variables.product.product_location_enterprise %}. El flujo de trabajo predeterminado de {% data variables.product.prodname_code_scanning %} utiliza el evento `on.push` para activar el escaneo de código cada vez que alguien carga información a cualquier rama que contenga el archivo de flujo de trabajo. - -### Running {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %} -If your organization isn't taking part in the beta for {% data variables.product.prodname_actions %}, or if you don't want to use {% data variables.product.prodname_actions %}, you can run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_runner %}. - -The {% data variables.product.prodname_codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)." - -### Inhabilitar las {% data variables.product.prodname_code_scanning %} - -{% data reusables.enterprise_management_console.enable-disable-code-scanning %} - -{% 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 "{% data variables.product.prodname_advanced_security %}", unselect **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/code-scanning-disable.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/configuration/configuring-advanced-security-features/index.md b/translations/es-XL/content/admin/configuration/configuring-advanced-security-features/index.md deleted file mode 100644 index 9edbc6a0f0..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-advanced-security-features/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Configuring Advanced Security features -shortTitle: Configuring Advanced Security -intro: 'You can enable or disable {% data variables.product.prodname_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, on your instance.' -redirect_from: - - /enterprise/admin/configuration/configuring-advanced-security-features -versions: - enterprise-server: '>=2.22' -topics: - - Enterprise -children: - - /configuring-code-scanning-for-your-appliance ---- - diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md deleted file mode 100644 index b2f70de9ef..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Configurar un nombre del host -intro: Recomendamos establecer un nombre del host para tu aparato en lugar de utilizar una dirección IP codificada de forma rígida. -redirect_from: - - /enterprise/admin/guides/installation/configuring-hostnames/ - - /enterprise/admin/installation/configuring-a-hostname - - /enterprise/admin/configuration/configuring-a-hostname - - /admin/configuration/configuring-a-hostname -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure ---- -Si configuras un nombre del host en lugar de una dirección IP codificada de forma rígida, podrás cambiar el hardware físico que ejecuta {% data variables.product.product_location_enterprise %} sin afectar a los usuarios o al software del cliente. - -La configuración del nombre de host en la {% data variables.enterprise.management_console %} debe ajustarse a un nombre de dominio adecuado y que cumpla con todos los requisitos (FQDN) el cual se pueda resolver en la internet o dentro de tu red interna. Por ejemplo, tu configuración de nombre del host podría ser `github.companyname.com.` También recomendamos habilitar el aislamiento de subdominio para el nombre del host elegido a fin de mitigar varias vulnerabilidades del estilo cross-site scripting. Para obtener más información, consulta [Sección 2.1 del HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). - -{% data reusables.enterprise_installation.changing-hostname-not-supported %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.hostname-menu-item %} -4. Escribe el nombre del host que quieres establecer para {% data variables.product.product_location_enterprise %}. ![Campo para establecer un nombre del host](/assets/images/enterprise/management-console/hostname-field.png) -5. Para probar las configuraciones de DNS y SSL para el nombre del host nuevo, haz clic en **Configuraciones del dominio de prueba**. ![Botón Test domain settings (Probar configuraciones del dominio)](/assets/images/enterprise/management-console/test-domain-settings.png) -{% data reusables.enterprise_management_console.test-domain-settings-failure %} -{% data reusables.enterprise_management_console.save-settings %} - -Después de configurar un nombre del host, recomendamos que habilites el aislamiento de subdominio para {% data variables.product.product_location_enterprise %}. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md deleted file mode 100644 index 172a61e503..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Configurar un servidor proxy web fuera de banda -intro: 'Un servidor proxy proporciona otro nivel de seguridad para {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/guides/installation/configuring-a-proxy-server/ - - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server - - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server - - /admin/configuration/configuring-an-outbound-web-proxy-server -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Networking ---- -Cuando se habilita un servidor proxy para {% data variables.product.product_location_enterprise %}, 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_enterprise %} 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)." - -{% endnote %} - -{% 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) -5. De manera opcional, en **Exclusión de servidor proxy HTTP**, escribe cualquier host que no exija acceso proxy, separando los hosts con comas. ![Campo para escribir cualquier Exclusión de Proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md deleted file mode 100644 index d079892712..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -title: Configurar las reglas de firewall incorporado -intro: 'Puedes ver las reglas de firewall predeterminadas y personalizar reglas para {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/guides/installation/configuring-firewall-settings/ - - /enterprise/admin/installation/configuring-built-in-firewall-rules - - /enterprise/admin/configuration/configuring-built-in-firewall-rules - - /admin/configuration/configuring-built-in-firewall-rules -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Networking ---- -### Acerca del firewell de {% data variables.product.product_location_enterprise %} - -{% data variables.product.prodname_ghe_server %} utiliza Ubuntu's Uncomplicated Firewall (UFW) en el aparato virtual. Para obtener más información, consulta "[UFW](https://help.ubuntu.com/community/UFW)" en la documentación de Ubuntu. Con cada lanzamiento, {% data variables.product.prodname_ghe_server %} actualiza automáticamente la lista blanca de los servicios permitidos del firewell. - -Después de que instales {% data variables.product.prodname_ghe_server %}, se abren automáticamente todos los puertos de red obligatorios para aceptar las conexiones. Cada puerto no obligatorio se configura automáticamente en `deny` (rechazar), y la directiva predeterminada resultante se configura en `allow` (permitir). Se habilita el rastreo con estado para todas las conexiones nuevas. Estas suelen ser paquetes de red con el conjunto de bits `SYN`. Para obtener más información, consulta "[Puertos de red](/enterprise/admin/guides/installation/network-ports)." - -El firewall de UFW también abre varios puertos más que son obligatorios para que {% data variables.product.prodname_ghe_server %} funcione correctamente. Para obtener más información sobre el conjunto de reglas de UFW, consulta [el README de UFW](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213). - -### Ver las reglas de firewell predeterminadas - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Para ver las reglas de firewall predeterminadas, utiliza el comando `sudo ufw status`. Debes ver un resultado similar a este: - ```shell - $ sudo ufw status - > Status: active - > To Action From - > -- ------ ---- - > ghe-1194 ALLOW Anywhere - > ghe-122 ALLOW Anywhere - > ghe-161 ALLOW Anywhere - > ghe-22 ALLOW Anywhere - > ghe-25 ALLOW Anywhere - > ghe-443 ALLOW Anywhere - > ghe-80 ALLOW Anywhere - > ghe-8080 ALLOW Anywhere - > ghe-8443 ALLOW Anywhere - > ghe-9418 ALLOW Anywhere - > ghe-1194 (v6) ALLOW Anywhere (v6) - > ghe-122 (v6) ALLOW Anywhere (v6) - > ghe-161 (v6) ALLOW Anywhere (v6) - > ghe-22 (v6) ALLOW Anywhere (v6) - > ghe-25 (v6) ALLOW Anywhere (v6) - > ghe-443 (v6) ALLOW Anywhere (v6) - > ghe-80 (v6) ALLOW Anywhere (v6) - > ghe-8080 (v6) ALLOW Anywhere (v6) - > ghe-8443 (v6) ALLOW Anywhere (v6) - > ghe-9418 (v6) ALLOW Anywhere (v6) - ``` - -### Agregar reglas de firewell personalizadas - -{% warning %} - -**Advertencia:** Antes de que agregues reglas de cortafuegos personalizadas, respalda tus reglas actuales en caso de que necesites restablecerlas a algún punto funcional. Si estás bloqueado de tu servidor, comunícate con {% data variables.contact.contact_ent_support %} para reconfigurar las reglas originales del firewall. Restaurar las reglas originales del firewall implica tiempo de inactividad para tu servidor. - -{% endwarning %} - -1. Configura una regla de firewall personalizada. -2. Verifica el estado de cada nueva regla con el comando `estado numerado`. - ```shell - $ sudo ufw status numbered - ``` -3. Para hacer una copia de seguridad de tus reglas de firewall personalizadas, utiliza el comando `cp` para pasar las reglas a un archivo nuevo. - ```shell - $ sudo cp -r /lib/ufw ~/ufw.backup - ``` - -Después de actualizar {% data variables.product.product_location_enterprise %}, debes volver a aplicar tus reglas de firewall personalizadas. Recomendamos que crees un script para volver a aplicar las reglas de firewall personalizadas. - -### Restaurar las reglas de firewell predeterminadas - -Si algo sale mal después de que cambies las reglas de firewell, puedes restablecer las reglas desde la copia de seguridad original. - -{% warning %} - -**Advertencia:** Si no respaldaste las reglas originales antes de hacer cambios al cortafuegos. contacta a {% data variables.contact.contact_ent_support %} para obtener más asistencia. - -{% endwarning %} - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Para restablecer las reglas de la copia de seguridad anterior, vuélvelas a copiar en el firewell con el comando `cp`. - ```shell - $ sudo cp -f ~/ufw.backup/*rules /lib/ufw - ``` -3. Vuelve a iniciar el firewell con el comando `systemctl`. - ```shell - $ sudo systemctl restart ufw - ``` -4. Confirma que las reglas recuperaron su forma predeterminada con el comando `ufw status` (estado de ufw). - ```shell - $ sudo ufw status - > Status: active - > To Action From - > -- ------ ---- - > ghe-1194 ALLOW Anywhere - > ghe-122 ALLOW Anywhere - > ghe-161 ALLOW Anywhere - > ghe-22 ALLOW Anywhere - > ghe-25 ALLOW Anywhere - > ghe-443 ALLOW Anywhere - > ghe-80 ALLOW Anywhere - > ghe-8080 ALLOW Anywhere - > ghe-8443 ALLOW Anywhere - > ghe-9418 ALLOW Anywhere - > ghe-1194 (v6) ALLOW Anywhere (v6) - > ghe-122 (v6) ALLOW Anywhere (v6) - > ghe-161 (v6) ALLOW Anywhere (v6) - > ghe-22 (v6) ALLOW Anywhere (v6) - > ghe-25 (v6) ALLOW Anywhere (v6) - > ghe-443 (v6) ALLOW Anywhere (v6) - > ghe-80 (v6) ALLOW Anywhere (v6) - > ghe-8080 (v6) ALLOW Anywhere (v6) - > ghe-8443 (v6) ALLOW Anywhere (v6) - > ghe-9418 (v6) ALLOW Anywhere (v6) - ``` diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md deleted file mode 100644 index 65488bd5e5..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Configurar servidores de nombres DNS -intro: '{% data variables.product.prodname_ghe_server %} utiliza el protocolo de configuración dinámica de host (DHCP) para los ajustes DNS cuando las concesiones de DHCP ofrecen servidores de nombres. Si una concesión del protocolo de configuración dinámica de host (DHCP) no proporciona los servidores de nombres o si debes utilizar ajustes DNS particulares, puedes especificar los servidores de nombres de manera manual.' -redirect_from: - - /enterprise/admin/guides/installation/about-dns-nameservers/ - - /enterprise/admin/installation/configuring-dns-nameservers - - /enterprise/admin/configuration/configuring-dns-nameservers - - /admin/configuration/configuring-dns-nameservers -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Networking ---- -Los servidores de nombres que especifiques deben resolver el nombre del host de {% data variables.product.product_location_enterprise %}. - -{% data reusables.enterprise_installation.changing-hostname-not-supported %} - -### Configurar servidores de nombres utilizando la consola de la máquina virtual - -{% data reusables.enterprise_installation.open-vm-console-start %} -2. Configurar servidores de nombres para tu instancia. -{% data reusables.enterprise_installation.vm-console-done %} - -### Configurar servidores de nombres utilizando el shell administrativo - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Para editar tus servidores de nombres, ingresa lo siguiente: - ```shell - $ sudo vim /etc/resolvconf/resolv.conf.d/head - ``` -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. Para agregar tus entradas nuevas de servidores de nombres en {% data variables.product.product_location_enterprise %}, ingresa lo siguiente: - ```shell - $ sudo service resolvconf restart - ``` diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console.md deleted file mode 100644 index 245625bbb4..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Configurar la dirección IP usando la consola de la máquina virtual -intro: 'Por defecto, {% data variables.product.prodname_ghe_server %} recupera las configuraciones de red a través del protocolo de configuración dinámica de host (DHCP). Si es compatible con tu plataforma, o si el DHCP no está disponible, también puedes establecer las configuraciones de red usando la consola de la máquina virtual.' -redirect_from: - - /enterprise/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console - - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console - - /admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Networking ---- -{% data reusables.enterprise_installation.open-vm-console-start %} -3. Para configurar, elige el protocolo `IPv4` o `IPv6`. ![Opciones para elegir el protocolo IPv4 o el IPv6](/assets/images/enterprise/network-configuration/IPv4-or-IPv6-protocol.png) -4. Configura las opciones para el protocolo que elegiste. ![Menú con opciones de protocolo IP](/assets/images/enterprise/network-configuration/network-settings-selection.png) -{% data reusables.enterprise_installation.vm-console-done %} diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-tls.md deleted file mode 100644 index 65e966511e..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/configuring-tls.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Configurar TLS -intro: 'Puedes configurar la Seguridad de la capa de transporte (TLS) en {% data variables.product.product_location_enterprise %} para poder usar un certificado firmado por una entidad de certificación confiable.' -redirect_from: - - /enterprise/admin/articles/ssl-configuration/ - - /enterprise/admin/guides/installation/about-tls/ - - /enterprise/admin/installation/configuring-tls - - /enterprise/admin/configuration/configuring-tls - - /admin/configuration/configuring-tls -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Networking - - Security ---- -### Acerca de la Seguridad de la capa de transporte - -El TLS, que reemplazó al SSL, se habilita y configura con un certificado autofirmado cuando se inicia el {% data variables.product.prodname_ghe_server %} por primera vez. Como los certificados autofirmados no son confiables para los navegadores web y los clientes de Git, estos clientes informarán advertencias de certificados hasta que inhabilites TLS o cargues un certificado firmado por una entidad confiable, como Let's Encrypt. - -El aparato {% data variables.product.prodname_ghe_server %} enviará encabezados de Seguridad de transporte estricta de HTTP mientras SSL esté habilitado. Inhabilitar TLS hará que los usuarios pierdan acceso al aparato, porque sus navegadores no permitirán que un protocolo se degrade a HTTP. Para obtener más información, consulta "[Seguridad de transporte estricta de HTTP (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" en Wikipedia. - -{% data reusables.enterprise_installation.terminating-tls %} - -Para permitir que los usuarios utilicen FIDO U2F para la autenticación de dos factores, debes habilitar TLS para tu instancia. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". - -### Prerrequisitos - -Para utilizar TLS en la producción, debes tener un certificado en un formato de PEM no cifrado firmado por una entidad de certificación confiable. - -Tu certificado también deberá tener configurados Nombres alternativos de sujeto para los subdominios detallados en "[Habilitar aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" y deberá incluir toda la cadena de certificación si lo firmó una entidad de certificación intermedia. Para obtener más información, consulta "[Nombre alternativo de sujeto](http://en.wikipedia.org/wiki/SubjectAltName)" en Wikipedia. - -Puedes generar una solicitud de firma de certificados (CSR) para tu instancia usando el comando `ghe-ssl-generate-csr`. Para obtener más información, consulta "[utilidades de línea de comandos](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)" - -### Cargar un certificado TLS personalizado - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.privacy %} -{% data reusables.enterprise_management_console.select-tls-only %} -4. En "TLS Protocol support" (Asistencia de protocolo TLS), selecciona los protocolos que quieres permitir. ![Botones de radio con opciones para elegir protocolos TLS](/assets/images/enterprise/management-console/tls-protocol-support.png) -5. En "Certificate" (Certificado), haz clic en **Choose File** (Elegir archivo) para elegir el certificado TLS o la cadena de certificación (en formato de PEM) que quieras instalar. Este archivo suele tener una extensión *.pem*, *.crt* o *.cer*. ![Botón para encontrar archivo de certificado TLS](/assets/images/enterprise/management-console/install-tls-certificate.png) -6. En "Unencrypted key" (Clave no cifrada), haz clic en **Choose File** (Elegir archivo) para elegir la clave TLS (en formato de PEM) que quieras instalar. Ese archivo suele tener una extensión *.key*. ![Botón para encontrar archivo de clave TLS](/assets/images/enterprise/management-console/install-tls-key.png) - - {% warning %} - - **Advertencia**: Tu clave TLS no debe tener contraseña. Para obtener más información, consulta "[Eliminar la contraseña de tu archivo clave](/enterprise/{{ currentVersion }}/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)". - - {% endwarning %} -{% data reusables.enterprise_management_console.save-settings %} - -### Acerca de la asistencia de Let's Encrypt - -Let's Encrypt es una entidad de certificación pública que emite certificados TLS gratuitos y automáticos que son confiables para los navegadores que usan el protocolo ACME. De hecho, puedes obtener y renovar los certificados de Let's Encrypt para tu aparato sin la necesidad de realizar ningún mantenimiento manual. - -{% data reusables.enterprise_installation.lets-encrypt-prerequisites %} - -Cuando habilites la automatización de la gestión de certificado TLS con Let's Encrypt, {% data variables.product.product_location_enterprise %} se contactará con los servidores de Let's Encrypt para obtener un certificado. Para renovar un certificado, los servidores de Let's Encrypt deben validar el control del nombre de dominio configurado con las solicitudes HTTP entrantes. - -También puedes usar la utilidad de la línea de comando `ghe-ssl-acme` en {% data variables.product.product_location_enterprise %} para generar un certificado de Let's Encrypt de manera automática. Para obtener más información, consulta "[Utilidades de la línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-ssl-acme)." - -### Configurar TLS usando Let's Encrypt - -{% data reusables.enterprise_installation.lets-encrypt-prerequisites %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.privacy %} -{% data reusables.enterprise_management_console.select-tls-only %} -5. Selecciona **Enable automation of TLS certificate management using Let's Encrypt** (Habilitar la automatización de la gestión de certificado TLS con Let's Encrypt). ![Casilla de verificación para habilitar Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png) -{% 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. Haz clic en **Save configuration** (Guardar configuración). diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md deleted file mode 100644 index d5d43eff8d..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Habilitar el aislamiento de subdominio -intro: 'Puedes configurar el aislamiento de subdominio para separar en forma segura el contenido suministrado por el usuario de las demás partes de tu aparato {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/guides/installation/about-subdomain-isolation/ - - /enterprise/admin/installation/enabling-subdomain-isolation - - /enterprise/admin/configuration/enabling-subdomain-isolation - - /admin/configuration/enabling-subdomain-isolation -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Networking - - Security ---- -### Acerca del aislamiento de subdominio - -El aislamiento de subdominio mitiga las vulnerabilidades del estilo cross-site scripting y otras vulnerabilidades relacionadas. Para obtener más información, consulta "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" en Wikipedia. Es altamente recomendable que habilites el aislamiento de subdominio en {% data variables.product.product_location_enterprise %}. - -Cuando el aislamiento de subdominio está habilitado, {% data variables.product.prodname_ghe_server %} reemplaza varias rutas con subdominios. - -{% if currentVersion ver_gt "enterprise-server@2.21" %} -To use Docker with {% data variables.product.prodname_registry %}, you must also enable subdomain isolation. For more information, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/enterprise/{{ currentVersion }}/user/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." - -{% data reusables.package_registry.packages-ghes-release-stage %} -| -{% endif %} -| Ruta sin aislamiento de subdominio | Ruta con aislamiento de subdominio | -| --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| N/A, Docker with {% data variables.product.prodname_registry %} will not work with subdomain isolation disabled. | `http(s)://uploads.HOSTNAME/` | -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} - -### Prerrequisitos - -{% data reusables.enterprise_installation.disable-github-pages-warning %} - -Antes de que habilites el aislamiento de subdominio, debes configurar tus ajustes de red para el nuevo dominio. - -- Especifica un nombre de dominio válido como tu nombre del host, en lugar de una dirección IP. Para obtener más información, consulta "[Configurar un nombre del host](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-a-hostname)." - -{% data reusables.enterprise_installation.changing-hostname-not-supported %} - -- Configura un registro de Sistema de nombres de dominio (DNS) de carácter comodín o registros DNS individuales para los subdominios detallados más arriba. Recomendamos crear un registro A para `*.HOSTNAME` que apunte a la dirección IP de tu servidor así no tienes que crear múltiples registros para cada subdominio. -- Obtén un certificado de Seguridad de la capa de transporte (TLS) de carácter comodín para `*.HOSTNAME` con un Nombre alternativo del firmante (SAN) para el `HOSTNAME` y para el `*.HOSTNAME` de dominio de carácter comodín. Por ejemplo, si tu nombre del host es `*.github.octoinc.com` obtén un certificado con el valor del nombre común configurado en `*.github.octoinc.com` y un valor SAN configurado en `github.octoinc.com` y `*.github.octoinc.com`. -- Habilita TLS en tu aparato. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls/)." - -### Habilitar el aislamiento de subdominio - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.hostname-menu-item %} -4. Selecciona **Subdomain isolation (recommended)** (Aislamiento de subdominio [recomendado]). ![Casilla de verificación para habilitar el aislamiento de subdominio](/assets/images/enterprise/management-console/subdomain-isolation.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/index.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/index.md deleted file mode 100644 index 839828cc46..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Configurar los ajustes de red -redirect_from: - - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl/ - - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings/ - - /enterprise/admin/articles/configuring-dns-ssl-and-subdomain-settings/ - - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings/ - - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings - - /enterprise/admin/configuration/configuring-network-settings -intro: 'Configura {% data variables.product.prodname_ghe_server %} con los servidores de nombres y el nombre del host DNS necesarios para tu red. También puedes configurar un servidor proxy o reglas de firewall. Debes permitir el acceso a determinados puertos con fines administrativos y relacionados con el usuario.' -versions: - ghes: '*' -topics: - - Enterprise -children: - - /configuring-the-ip-address-using-the-virtual-machine-console - - /configuring-dns-nameservers - - /configuring-a-hostname - - /validating-your-domain-settings - - /configuring-tls - - /enabling-subdomain-isolation - - /configuring-an-outbound-web-proxy-server - - /configuring-built-in-firewall-rules - - /network-ports - - /using-github-enterprise-server-with-a-load-balancer ---- - diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/network-ports.md deleted file mode 100644 index 445c3cd140..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/network-ports.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Puertos de red -redirect_from: - - /enterprise/admin/articles/configuring-firewalls/ - - /enterprise/admin/articles/firewall/ - - /enterprise/admin/guides/installation/network-configuration/ - - /enterprise/admin/guides/installation/network-ports-to-open/ - - /enterprise/admin/installation/network-ports - - /enterprise/admin/configuration/network-ports - - /admin/configuration/network-ports -intro: 'Abre los puertos de red de forma selectiva en base a los servicios de red que necesitas exponer a los administradores, usuarios finales y apoyo de correo electrónico.' -versions: - ghes: '*' -topics: - - Enterprise - - Infrastructure - - Networking - - Security ---- -### Puertos administrativos - -Se requieren algunos puertos administrativos para configurar {% data variables.product.product_location_enterprise %} y ejecutar determinadas funciones. No se requieren puertos administrativos para el uso de la aplicación básica por parte de los usuarios finales. - -| Port (Puerto) | Servicio | Descripción | -| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 8443 | HTTPS | {% data variables.enterprise.management_console %} segura basada en la web. Requerida para la instalación y la configuración básicas. | -| 8080 | HTTP | {% data variables.enterprise.management_console %} basada en la web de texto simple. No se requiere excepto que el SSL esté inhabilitado de forma manual. | -| 122 | SSH | Acceso shell para {% data variables.product.product_location_enterprise %}. Se requiere para abrir las conexiones entrantes de todos los otros nodos en la configuración de alta disponibilidad. El puerto SSH predeterminado (22) está destinado al tráfico de red de la aplicación SSH y Git. | -| 1194/UDP | VPN | Túnel de red de replicación segura en la configuración de alta disponibilidad. Se requiere que esté abierto para todos los otros nodos en la configuración. | -| 123/UDP | NTP | Se requiere para operar el protocolo de tiempo. | -| 161/UDP | SNMP | Se requiere para operar el protocolo de revisión de red. | - -### Puertos de la aplicación para usuarios finales - -Los puertos de la aplicación permiten que los usuarios finales accedan a Git y a la aplicación web. - -| Port (Puerto) | Servicio | Descripción | -| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 443 | HTTPS | Acceso a la aplicación web y a Git por HTTPS. | -| 80 | HTTP | Acceso a la aplicación web. Todas las solicitudes se redireccionan al puerto HTTPS cuando se habilita SSL. | -| 22 | SSH | Acceso a Git por SSH. Admite las operaciones clonar, extraer y subir a los repositorios privados y públicos. | -| 9418 | Git | El puerto de protocolo Git admite las operaciones clonar y extraer a los repositorios públicos con comunicación de red desencriptada. | - -{% data reusables.enterprise_installation.terminating-tls %} - -### Puertos de correo electrónico - -Los puertos de correo electrónico deben ser accesibles directamente o por medio de la retransmisión del correo electrónico entrante para los usuarios finales. - -| Port (Puerto) | Servicio | Descripción | -| ------------- | -------- | ---------------------------------------------- | -| 25 | SMTP | Soporte para SMTP con encriptación (STARTTLS). | diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md deleted file mode 100644 index f27011233c..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Utilizar el servidor de GitHub Enterprise con un balanceador de carga -intro: 'Utiliza un balanceador de carga frente a un aparato único del {% data variables.product.prodname_ghe_server %} o un par de aparatos en una configuración de alta disponibilidad.' -redirect_from: - - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer/ - - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer - - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer - - /admin/configuration/using-github-enterprise-server-with-a-load-balancer -versions: - ghes: '*' -topics: - - Enterprise - - High availability - - Infrastructure - - Networking ---- -{% data reusables.enterprise_clustering.load_balancer_intro %} - -{% data reusables.enterprise_clustering.load_balancer_dns %} - -### Manejar información de conexión de clientes - -Debido a que las conexiones de cliente al {% data variables.product.prodname_ghe_server %} provienen del balanceador de carga, se puede perder la dirección IP del cliente. - -{% data reusables.enterprise_clustering.proxy_preference %} - -{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %} - -#### Habilitar soporte para protocolo de PROXY en {% data variables.product.product_location_enterprise %} - -Recomendamos firmemente habilitar el soporte para protocolo de PROXY para tu aparato y el balanceador de carga. Utiliza las instrucciones provistas por tu proveedor para habilitar el protocolo PROXY en tu balanceador de carga. Para obtener más información, consulta [la documentación de protocolo PROXY](http://www.haproxy.org/download/1.6/doc/proxy-protocol.txt). - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.privacy %} -3. Dentro de **External load balancers (Balanceadores de carga externos)**, selecciona **Enable support for PROXY protocol (Habilitar soporte para el protocolo de PROXY)**. ![Casilla de verificación para habilitar el soporte para el protocolo PROXY](/assets/images/enterprise/management-console/enable-proxy.png) -{% data reusables.enterprise_management_console.save-settings %} - -{% data reusables.enterprise_clustering.proxy_protocol_ports %} - -#### Habilitar soporte para X-Forwarded-For en {% data variables.product.product_location_enterprise %} - -{% data reusables.enterprise_clustering.x-forwarded-for %} - -{% data reusables.enterprise_installation.terminating-tls %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.privacy %} -3. Dentro de **External load balancers (Balanceadores de carga externos)**, selecciona **Allow HTTP X-Forwarded-For header (Permitir encabezados HTTP X-Forwarded-For)**. ![Casilla de verificación para permitir el encabezado de HTTP X-Forwarded-For](/assets/images/enterprise/management-console/allow-xff.png) -{% data reusables.enterprise_management_console.save-settings %} - -{% data reusables.enterprise_clustering.without_proxy_protocol_ports %} - -### Configurar la revisión de estado - -Las comprobaciones de estado permiten que un balanceador de carga deje de enviar tráfico a un nodo que no responde si una comprobación preconfigurada falla en ese nodo. Si el aparato está fuera de línea debido a un mantenimiento o una falla inesperada, el balanceador de carga puede mostrar una página de estado. En una configuración de alta disponibilidad (HA), un balanceador de carga puede usarse como parte de una estrategia de conmutación por error. Sin embargo, no está admitida la conmutación por error automática de los pares de HA. Debes impulsar de forma manual el aparato réplica antes de que comience con las consultas activas. Para obtener más información, consulta "[Configurar {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." - -{% data reusables.enterprise_clustering.health_checks %} -{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} diff --git a/translations/es-XL/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md b/translations/es-XL/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md deleted file mode 100644 index 18d49ee652..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Validar tus parámetros de dominio -intro: 'Asegúrate de que tus parámetros de dominio estén configurados adecuadamente antes de arrancar {% data variables.product.product_location_enterprise %} por primera vez.' -redirect_from: - - /enterprise/admin/installation/validating-your-domain-settings - - /enterprise/admin/configuration/validating-your-domain-settings - - /admin/configuration/validating-your-domain-settings -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Networking ---- -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.hostname-menu-item %} -4. Para probar los parámetros DNS y SSL de tu aparato, haz clic en **Test domain settings (Pruebar parámetros de dominio)**. ![Botón Test domain settings (Probar configuraciones del dominio)](/assets/images/enterprise/management-console/test-domain-settings.png) -{% data reusables.enterprise_management_console.test-domain-settings-failure %} -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md deleted file mode 100644 index 4a56c2536d..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Acceder al shell administrativo (SSH) -redirect_from: - - /enterprise/admin/articles/ssh-access/ - - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access/ - - /enterprise/admin/guides/installation/administrative-shell-ssh-access/ - - /enterprise/admin/articles/troubleshooting-ssh-permission-denied-publickey/ - - /enterprise/admin/2.13/articles/troubleshooting-ssh-permission-denied-publickey/ - - /enterprise/admin/2.14/articles/troubleshooting-ssh-permission-denied-publickey/ - - /enterprise/admin/2.15/articles/troubleshooting-ssh-permission-denied-publickey/ - - /enterprise/admin/installation/accessing-the-administrative-shell-ssh - - /enterprise/admin/configuration/accessing-the-administrative-shell-ssh - - /admin/configuration/accessing-the-administrative-shell-ssh -intro: 'El acceso al SSH te permite ejecutar las utilidades de la línea de comando del {% data variables.product.prodname_ghe_server %} y es útil para la solución de problemas, para ejecutar copias de seguridad y para configurar la replicación.' -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - SSH ---- -### Acerca del acceso al shell administrativo - -Si tienes acceso SSH al shell administrativo, puedes ejecutar las utilidades de la línea de comando del {% data variables.product.prodname_ghe_server %}. El acceso SSH también es útil para la solución de problemas, para ejecutar copias de seguridad y para configurar la replicación. El acceso SSH administrativo se administra por separado desde el acceso SSH de Git y es accesible solo desde el puerto 122. - -### Habilitar el acceso al shell administrativo por medio de SSH - -Para habilitar el acceso SSH administrativo, debes agregar tu llave pública SSH a tu lista de llaves autorizadas de la instancia. - -{% tip %} - -**Consejo:** Los cambios en las claves SSH entran en vigor de inmediato. - -{% endtip %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -3. En "SSH access" (Acceso SSH), pega tu clave en el cuadro de texto, luego haz clic en **Add key** (Agregar clave). ![Cuadro te texto y botón para agregar una clave SSH](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png) -{% data reusables.enterprise_management_console.save-settings %} - -### Conectarse con el shell administrativo por SSH - -Después de que hayas agregado tu clave SSH a la lista, conéctate a la instancia por SSH como el usuario `admin` en el puerto 122. - -```shell -$ ssh -p 122 admin@github.example.com -Último inicio de sesión: dom 9 de nov 07:53:29 2014 desde 169.254.1.1 -admin@github-example-com:~$ █ -``` - -#### Solucionar problemas de conexión al SSH - -Si te encuentras con el error `Permiso denegado (publickey)` cuando intentas conectarte a {% data variables.product.product_location_enterprise %} por medio de SSH, confirma que te estés conectando por el puerto 122. Puede que debas especificar de manera explícita qué clave SSH privada utilizar. - -Para especificar una clave SSH utilizando la línea de comando, ejecuta `ssh` con el argumento `-i`. - -```shell -ssh -i /path/to/ghe_private_key -p 122 admin@hostname -``` - -También puedes especificar una clave SSH privada utilizando el archivo de configuración de SSH (`~/.ssh/config`). - -```shell -Host hostname - IdentityFile /path/to/ghe_private_key - Usuario Admin - Puerto 122 -``` - -### Acceder al shell administrativo utilizando la consola local - -En una situación de emergencia, por ejemplo, si el SSH no está disponible, puedes acceder al shell administrativo de manera local. Inicia sesión como usuario `admin` y utiliza la contraseña establecida durante la configuración inicial de {% data variables.product.prodname_ghe_server %}. - -### Limitaciones de acceso al shell administrativo - -El acceso al shell administrativo se permite solo para la solución de problemas y para realizar procedimientos de operaciones documentadas. Si modificas archivos del sistema y de la aplicación, ejecutas programas o instalas paquetes de software incompatibles se puede invalidar tu contrato de asistencia. Contáctate con {% data variables.contact.contact_ent_support %} si tienes alguna pregunta acerca de las actividades que permite tu contrato de asistencia. diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md deleted file mode 100644 index 1fa6158db6..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Acceder a la consola de administración -intro: 'Utiliza la {% data variables.enterprise.management_console %} para configurar y establecer {% data variables.product.product_location %}, programa las ventanas de mantenimiento, soluciona problemas y administra tu licencia.' -redirect_from: - - /enterprise/admin/articles/about-the-management-console/ - - /enterprise/admin/articles/management-console-for-emergency-recovery/ - - /enterprise/admin/articles/web-based-management-console/ - - /enterprise/admin/categories/management-console/ - - /enterprise/admin/articles/accessing-the-management-console/ - - /enterprise/admin/guides/installation/web-based-management-console/ - - /enterprise/admin/installation/accessing-the-management-console - - /enterprise/admin/configuration/accessing-the-management-console - - /admin/configuration/accessing-the-management-console -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals ---- -### Acerca de {% data variables.enterprise.management_console %} - -Utiliza {% data variables.enterprise.management_console %} para las actividades administrativas básicas: -- **Configuración inicial**: Atraviesa el proceso de configuración inicial durante el primer lanzamiento {% data variables.product.product_location_enterprise %} visitando la dirección IP de {% data variables.product.product_location_enterprise %} en tu navegador. -- **Establecer configuraciones básicas para tu instancia**: Configura DNS, nombre del host, SSL, autenticación de usuario, correo electrónico, servicios de monitoreo y redireccionamiento de registro en la página de Configuraciones. -- **Programar ventanas de mantenimiento**: Trabaja sin conexión en tu {% data variables.product.product_location_enterprise %} mientras realizas mantenimiento con {% data variables.enterprise.management_console %} o el shell administrativo. -- **Solucionar problemas**: Genera un paquete de soporte o visualiza la información de diagnóstico de alto nivel. -- **Administración de licencias**: Visualiza o actualiza tu licencia {% data variables.product.prodname_enterprise %}. - -También puedes acceder a {% data variables.enterprise.management_console %} utilizando la dirección IP de {% data variables.product.product_location_enterprise %}, incluso cuando la instancia se encuentre en modo de mantenimiento o si ocurre una falla crítica en la aplicación o si están mal configurados el nombre del host o la SSL. - -Para acceder a {% data variables.enterprise.management_console %}, debes utilizar la contraseña de administrador establecida durante la configuración inicial de {% data variables.product.product_location_enterprise %}. También debes poder conectarte con el host de la máquina virtual en el puerto 8443. Si tienes problemas para acceder a {% data variables.enterprise.management_console %}, controla las configuraciones del firewall intermedio y del grupo de seguridad. - -### 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. Para obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/installation/managing-your-github-enterprise-license)". - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.type-management-console-password %} - -### Acceder a {% data variables.enterprise.management_console %} como usuario sin autenticación - -1. Visita esta URL en tu navegador, reemplazando el `nombre del host` por tu nombre del host o tu dirección IP actuales {% data variables.product.prodname_ghe_server %}: - ```shell - http(s)://HOSTNAME/setup - ``` -{% data reusables.enterprise_management_console.type-management-console-password %} - -### Desbloquear {% data variables.enterprise.management_console %} después de los intentos de inicio de sesión fallidos - -Los bloqueos de la {% data variables.enterprise.management_console %} después de diez intentos de inicio de sesión fallidos se hacen en el transcurso de diez minutos. Debes esperar para que la pantalla de inicio de sesión se desbloquee automáticamente antes de intentar iniciar sesión nuevamente. La pantalla de inicio de sesión se desbloquea automáticamente siempre que el período de diez minutos previo contenga menos de diez intentos de inicio de sesión fallidos. El contador se reinicia después de que ocurra un inicio de sesión exitoso. - -Para desbloquear de inmediato la {% data variables.enterprise.management_console %}, utilice el comando `ghe-reactivate-admin-login` a través del shell administrativo. Para obtener más información, consulta "[Utilidades de la línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md deleted file mode 100644 index d4b319d0ee..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ /dev/null @@ -1,822 +0,0 @@ ---- -title: Utilidades de la línea de comando -intro: '{% data variables.product.prodname_ghe_server %} incluye una gama de utilidades para ayudar a resolver problemas particulares o realizar tareas específicas.' -redirect_from: - - /enterprise/admin/articles/viewing-all-services/ - - /enterprise/admin/articles/command-line-utilities/ - - /enterprise/admin/installation/command-line-utilities - - /enterprise/admin/configuration/command-line-utilities - - /admin/configuration/command-line-utilities -miniTocMaxHeadingLevel: 3 -versions: - ghes: '*' -topics: - - Enterprise - - SSH ---- -Puedes ejecutar estos comandos desde cualquier lugar en la VM después de iniciar sesión como usuario administrador de SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." - -### General - -#### ghe-announce - -Esta utilidad establece un mensaje emergente en la parte superior de cada página {% data variables.product.prodname_enterprise %}. Puedes usarlo para difundir un mensaje entre tus usuarios. - -{% if currentVersion ver_gt "enterprise-server@2.21" %} -You can also set an announcement banner using the enterprise settings on {% data variables.product.product_name %}. Para obtener más información, consulta "[Personalizar mensajes de usuario en tu instancia](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)." -{% endif %} - -```shell -# Establece un mensaje que es visible para todos -$ ghe-announce -s MESSAGE -> Mensaje de anuncio establecido. -# Elimina un mensaje establecido previamente -$ ghe-announce -u -> Eliminó el mensaje de anuncio -``` - -#### ghe-check-disk-usage - -Esta utilidad busca en el disco los archivos grandes o los archivos que se han eliminado, pero siguen teniendo identificadores de archivo abiertos. Esto se debería ejecutar cuando intentes liberar espacio en la partición raíz. - -```shell -ghe-check-disk-usage -``` - -#### ghe-cleanup-caches - -Esta utilidad borra una variedad de cachés que podrían ocupar espacio extra del disco en el volumen raíz. Si notas que el uso del espacio de disco del volumen raíz aumenta de manera considerable, sería buena idea ejecutar esta utilidad para ver si ayuda a reducir el uso general. - -```shell -ghe-cleanup-caches -``` -#### ghe-cleanup-settings - -Esta utilidad borra todas las configuraciones {% data variables.enterprise.management_console %} existentes. - -{% tip %} - -**Consejo**: {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} - -{% endtip %} - -```shell -ghe-cleanup-settings -``` - -#### ghe-config - -Con esta utilidad, puedes recuperar y modificar los ajustes de configuración de {% data variables.product.product_location_enterprise %}. - -```shell -$ ghe-config core.github-hostname -# Obtiene el valor de configuración de `core.github-hostname` -$ ghe-config core.github-hostname 'example.com' -# Establece el valor de configuración de `core.github-hostname` en `example.com` -$ ghe-config -l -# Detalla todos los valores de configuración -``` -Te permite encontrar el uuid de tu nodo en `cluster.conf`. - -``` shell - $ ghe-config _hostname_.uuid -``` - -{% if currentVersion ver_gt "enterprise-server@2.21" %} -Allows you to exempt a list of users from API rate limits. Para obtener más información, consulta la sección "[Limites de tasa](/enterprise/{{ currentVersion }}/v3/#rate-limiting)." - -``` shell -$ ghe-config app.github.rate_limiting_exempt_users "hubot github-actions" -# Exempts the users hubot and github-actions from rate limits -``` -{% endif %} - -#### ghe-config-apply - -Esta utilidad aplica configuraciones {% data variables.enterprise.management_console %}, vuelve a cargar servicios del sistema, prepara un dispositivo de almacenamiento y ejecuta cualquier migración de base de datos pendiente. Es equivalente a dar clic en **Guardar configuración** en la IU web de {% data variables.enterprise.management_console %} o a enviar una solicitud de POST a [la terminal `/setup/api/configure`](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console). - -Probablemente, nunca la debas ejecutar en forma manual, pero está disponible si quieres automatizar el proceso de guardar tus configuraciones a través de SSH. - -```shell -ghe-config-apply -``` - -#### ghe-console - -Esta utilidad abre la consola GitHub Rails en tu aparato {% data variables.product.prodname_enterprise %}. {% data reusables.command_line.use_with_support_only %} - -```shell -ghe-console -``` - -#### ghe-dbconsole - -Esta utilidad abre una sesión de base de datos de MySQL en tu aparato {% data variables.product.prodname_enterprise %}. {% data reusables.command_line.use_with_support_only %} - -```shell -ghe-dbconsole -``` - -#### ghe-es-index-status -Esta utilidad genera un resumen de los índices de Elasticsearch en formato CSV. - -Imprime un resumen de los índices con un encabezado para `STDOUT`: -```shell -$ ghe-es-index-status -do -> warning: parser/current is loading parser/ruby23, which recognizes -> warning: 2.3.3-compliant syntax, but you are running 2.3.4. -> warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri. -> Name,Primary,Searchable,Writable,UpToDate,RepairProgress,Version -> code-search-1,true,true,true,true,100.0,72e27df7c631b45e026b42bfef059328fa040e17 -> commits-5,true,true,true,true,100.0,7ed28813100c47813ef654c0ee2bb9abf21ab744 -> gists-4,true,true,true,true,100.0,cf8e7d04fcf2564c902e2873c424a279cc41079d -> issues-4,false,false,false,true,100.0,d0bb08f71eebf6e7b070572aa399b185dbdc8a76 -> issues-5,true,true,true,true,100.0,d0bb08f71eebf6e7b070572aa399b185dbdc8a76 -> projects-2,true,true,true,true,100.0,c5cac1c4b3c66d42e609d088d174dbc3dd44469a -> pull-requests-6,true,true,true,true,100.0,6a466ad6b896a3499509990979bf9a18d7d41de3 -> repos-6,true,true,true,true,100.0,6c8b5fbba0fc1e409558db411d05e092c1387082 -> users-5,true,true,true,true,100.0,38984875552bb826c9ec42999f409cb2e95556eb -> wikis-4,true,true,true,true,100.0,2613dec44bd14e14577803ac1f9e4b7e07a7c234 -``` - -Imprime un resumen de los índices y canaliza los resultados en `columnas` para mejor legibilidad: - -```shell -$ ghe-es-index-status -do | column -ts, -> warning: parser/current is loading parser/ruby23, which recognizes -> warning: 2.3.3-compliant syntax, but you are running 2.3.4. -> warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri. -> Nombre Principal Se puede buscar Editable Actualizado Avance reparación Versión -> code-search-1 true true true true 100.0 72e27df7c631b45e026b42bfef059328fa040e17 -> commits-5 true true true true 100.0 7ed28813100c47813ef654c0ee2bb9abf21ab744 -> gists-4 true true true true 100.0 cf8e7d04fcf2564c902e2873c424a279cc41079d -> issues-4 falso falso falso true 100.0 d0bb08f71eebf6e7b070572aa399b185dbdc8a76 -> issues-5 true true true true 100.0 d0bb08f71eebf6e7b070572aa399b185dbdc8a76 -> projects-2 true true true true 100.0 c5cac1c4b3c66d42e609d088d174dbc3dd44469a -> pull-requests-6 true true true true 100.0 6a466ad6b896a3499509990979bf9a18d7d41de3 -> repos-6 true true true true 100.0 6c8b5fbba0fc1e409558db411d05e092c1387082 -> users-5 true true true true 100.0 38984875552bb826c9ec42999f409cb2e95556eb -> wikis-4 true true true true 100.0 2613dec44bd14e14577803ac1f9e4b7e07a7c234 -``` - -#### ghe-legacy-github-services-report - -Esta utilidad enumera los repositorios de tu aparato que usan Servicios {% data variables.product.prodname_dotcom %}, un método de integración que se interrumpirá el 1 de octubre de 2018. Los usuarios de tu aparato pueden tener configurados servicios {% data variables.product.prodname_dotcom %} para crear notificaciones de subidas a determinados repositorios. Para obtener más información, consulta la sección "[Anunciar la obsoletización de servicios de {% data variables.product.prodname_dotcom %} ](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" en {% data variables.product.prodname_blog %} o la sección "[Reemplazar servicios de {% data variables.product.prodname_dotcom %}](/v3/guides/replacing-github-services/)". Para obtener más información acerca de este comando o para conocer otras opciones, utiliza la marca `-h`. - -```shell -ghe-legacy-github-services-report - -``` - -#### ghe-logs-tail - -Esta utilidad te permite hacer un registro final de todos los archivos de registro relevantes desde tu instalación. Puedes aprobar opciones para limitar los registros a conjuntos específicos. Utiliza la marca -h para más opciones. - -```shell -ghe-logs-tail -``` - -#### ghe-maintenance - -Esta utilidad te permite controlar el estado del modo de mantenimiento de la instalación. Está diseñada para que la use principalmente la {% data variables.enterprise.management_console %} en segundo plano, pero también se puede usar directamente. - -```shell -ghe-maintenance -h -``` - -{% if currentVersion ver_gt "enterprise-server@2.17" %} -#### ghe-motd - -Esta utilidad vuelve a mostrar el mensaje del día (MOTD) en el que los administradores ven cuando se accede a la isntancia a través del shell administrativo. El resultado contiene un resumen del estado de la instancia. - -```shell -ghe-motd -``` -{% endif %} - -#### ghe-nwo - -Esta utilidad genera un nombre y propietario de repositorio en función del Id. del repositorio. - -```shell -ghe-nwo REPOSITORY_ID -``` - -#### ghe-org-admin-promote - -Usa este comando para otorgarles privilegios de propietario de la organización a los usuarios con privilegios de administrador del sitio sobre el aparato o para otorgarle privilegios de propietario de la organización a cualquier usuario único de una organización única. Debes especificar un usuario o una organización. El comando `ghe-org-admin-promote` siempre pedirá confirmación antes de ejecutarse, a menos que uses la marca `-y` para omitir la confirmación. - -Puedes usar las siguientes opciones con la utilidad: - -- La marca `-u` especifica un nombre de usuario. Usa esta marca para otorgarle privilegios de propietario de la organización a un usuario específico. Omite la marca `-u` para promover todos los administradores del sitio a la organización específica. -- La marca `-o` especifica una organización. Usa esta marca para otorgar privilegios de propietario en una organización específica. Omite la marca `-o` para otorgarle permisos de propietario en todas las organizaciones al administrador del sitio especificado. -- La marca `-a` otorga privilegios de propietario en todas las organizaciones a todos los administradores del sitio. -- La marca `-y` omite la confirmación manual. - -Esta utilidad no puede promover una cuenta de usuario que no sea administrador del sitio a propietario de todas las organizaciones. Puedes promover una cuenta de usuario común a administrador del sitio con [ghe-user-promote](#ghe-user-promote). - -Otorga privilegios de propietario de la organización en una organización específica a un usuario único - -```shell -ghe-org-admin-promote -u USERNAME -o ORGANIZATION -``` - -Otorga privilegios de propietario de la organización en todas las organizaciones a un administrador del sitio específico - -```shell -ghe-org-admin-promote -u USERNAME -``` - -Otorga privilegios de propietario de la organización en una organización específica a todos los administradores del sitio - -```shell -ghe-org-admin-promote -o ORGANIZATION -``` - -Otorga privilegios de propietario de la organización en todas las organizaciones a todos los administradores del sitio - -```shell -ghe-org-admin-promote -a -``` - -#### ghe-reactivate-admin-login - -Usa este comando para desbloquear de inmediato la {% data variables.enterprise.management_console %} después de 10 intentos fallidos de inicio de sesión en el transcurso de 10 minutos. - -```shell -$ ghe-reactivate-admin-login -``` - -#### ghe-resque-info - -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. - -Esta utilidad puede ayudar a identificar si el servidor Resque está teniendo problemas para procesar los trabajos de segundo plano. Cualquiera de los siguientes escenarios puede ser indicativo de un problema con Reque: - -* 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. - -Si sospechas que Resque está fallando, contáctate con {% data variables.contact.contact_ent_support %} para obtener ayuda. - -Con este comando, también puedes detener o reanudar los trabajos en cola. - -```shell -$ ghe-resque-info -# detalla las colas y la cantidad de trabajos actualmente en cola -$ ghe-resque-info -p QUEUE -# detiene la cola especificada -$ ghe-resque-info -r QUEUE -# reanuda la cola especificada -``` - -#### ghe-saml-mapping-csv - -Esta utilidad puede ayudar a mapear los registros de SAML. - -Para crear un archivo CSV que contenga todo el mapeo de SAML para tus usuarios de {% data variables.product.product_name %}: -```shell -$ ghe-saml-mapping-csv -d -``` - -Para realizar una simulación de actualización de mapeo de SAML con nuevos valores: -```shell -$ ghe-saml-mapping-csv -u -n -f /path/to/file -``` - -Para actualizar el mapeo de SAML con nuevos valores: -```shell -$ ghe-saml-mapping-csv -u -f /path/to/file -``` - -#### ghe-service-list - -Esta utilidad enumera todos los servicios que se han iniciado o detenido (en ejecución o en espera) en tu aparato. - -```shell -$ ghe-service-list -start/running - - github-resqued, process 12711 - - github-unicorn, process 12726 - - github-gitauth, process 12743 - - git-daemon, process 12755 - - babeld, process 12771 - - github-svn-proxy, process 12802 - - gist-unicorn, process 12832 - - gist-resqued, process 12881 - - render-unicorn, process 12939 - - hookshot-unicorn, process 13076 - - nodeload2, process 13192 - - slumlord-unicorn, process 13304 - - ghe-storage, process 2012 - - enterprise-manage-unicorn, process 2024 - - enterprise-manage-resque, process 2053 - -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). - -```shell -ghe-set-password -``` - -#### ghe-ssh-check-host-keys - -Esta utilidad compara las claves del host de SSH existentes con la lista de claves del host de SHH filtradas conocidas. - -```shell -$ ghe-ssh-check-host-keys -``` - -Si se encuentra una clave del host filtrada, se cierra la utilidad en un estado `1` y con un mensaje: -```shell -> Una o más de tus claves del host de SHH aparecen en la lista negra. -> Restablece tus claves del host usando ghe-ssh-roll-host-keys. -``` - -Si no se encontró una clave del host filtrada, se cierra la utilidad en un estado `0` y con un mensaje: -```shell -> Las claves del host de SSH no se encontraron en la lista negra de claves del host de SSH. -> No se requieren/recomiendan más pasos en este momento. -``` - -#### ghe-ssh-roll-host-keys - -Esta utilidad rota las claves del host de SSH y las reemplaza con claves que se generan nuevas. - -```shell -$ sudo ghe-ssh-roll-host-keys -¿Quieres proceder con la rotación de claves del host de SSH? Esto eliminará las -las claves existentes en /etc/ssh/ssh_host_* y generará nuevas. [y/N] - -# Presiona 'Y' para confirmar la eliminación o utiliza el modificador -y para omitir esta pregunta - -> Las claves del host de SSH se han rotado con éxito. -``` - -#### ghe-ssh-weak-fingerprints - -Esta utilidad genera un informe de claves de SSH débiles conocidas que están almacenadas en el aparato {% data variables.product.prodname_enterprise %}. Opcionalmente, puedes revocar las claves de usuario como acción masiva. La utilidad informará las claves de sistema débiles que puedes revocar en forma manual en la [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). - -```shell -# Imprime un informe de usuario y claves SSH del sistema débiles -$ ghe-ssh-weak-fingerprints - -# Revoca todas las claves de usuario débiles -$ ghe-ssh-weak-fingerprints --revoke -``` - -#### ghe-ssl-acme - -Esta utilidad te permite instalar un certificado de Let's Encrypt en tu aparato {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)." - -Puede utilizar la etiqueta `-x` para eliminar la configuración ACME. - -```shell -ghe-ssl-acme -e -``` - -#### ghe-ssl-ca-certificate-install - -Esta utilidad te termine instalar un certificado CA de raíz personalizado en tu servidor {% data variables.product.prodname_enterprise %}. El certificado debe tener un formato PEM. Además, si tu proveedor de certificación incluye varios certificados CA en un único archivo, debes separarlos en archivos individuales que luego pasarás a `ghe-ssl-ca-certificate-install` de a uno por vez. - -Ejecuta esta utilidad para agregar una cadena de certificación para la verificación de firma de confirmación S/MIME. Para obtener más información, consulta "[Acerca de la verificación de firma de confirmación](/enterprise/{{ currentVersion }}/user/articles/about-commit-signature-verification/)". - -Ejecuta esta utilidad cuando {% data variables.product.product_location_enterprise %} no pueda conectarse con otro servidor porque el segundo está usando un certificado SSL autofirmado o un certificado SSL para el cual no proporciona el paquete de soporte CA necesario. Una manera de confirmar esto es ejecutar `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` desde {% data variables.product.product_location_enterprise %}. Si el certificado SSL del servidor remoto se puede verificar, tu `SSL-Session` debe tener un código de retorno de 0, como se muestra a continuación. - -``` -SSL-Session: - Protocol : TLSv1 - Cipher : AES128-SHA - Session-ID: C794EBCC3CBC10F747C9AFC029C03C1048FC99CFC34D13D7444E0F267C58DF4C - Session-ID-ctx: - Master-Key: 02A7C47CFD6EEC87D3C710E9DD87390E04EF82DDD7514AE03127D5DC1945FC0CAEFB5395791AEA598667EFA61B9EA8C5 - Key-Arg : None - Start Time: 1394581597 - Timeout : 300 (sec) - Verify return code: 0 (ok) -``` - -Si, de lo contrario, el certificado SSL del servidor remoto *no* se puede verificar, tu `SSL-Session` debería tener un código de retorno distinto de cero: - -``` -SSL-Session: - Protocol : TLSv1 - Cipher : AES128-SHA - Session-ID: 82CB288051A6DB66094C50A69CF1292AEE7E54C6B01B659B98AB336F8C33863E - Session-ID-ctx: - Master-Key: 01B025B2F764043A27919A8D1355AAECD8844FF0831B1D664042334790574A6F4025BAB085D4ED71D71AAB3091B849E5 - Key-Arg : None - Start Time: 1394581782 - Timeout : 300 (sec) - Verify return code: 27 (certificate not trusted) -``` - -Puedes usar estas opciones adicionales con la utilidad: -- La marca `-r` te permite desinstalar un certificado CA. -- La marca `-h` muestra más información de uso. - -```shell -ghe-ssl-ca-certificate-install -c /path/to/certificate -``` - -#### ghe-ssl-generate-csr - -Esta utilidad te permite generar una clave privada y una solicitud de firma de certificado (CSR), que puedes compartir con una autoridad de certificación comercial o privada para obtener un certificado válido para utilizar con tu instancia. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-tls)." - -Para obtener más información acerca de este comando o para conocer otras opciones, utiliza la marca `-h`. - -```shell -ghe-ssl-generate-csr -``` - -#### ghe-storage-extend - -Algunas plataformas exigen este script para ampliar el volumen de usuarios. Para obtener más información, consulta "[Aumentar la capacidad de almacenamiento](/enterprise/admin/guides/installation/increasing-storage-capacity/)". - -```shell -$ ghe-storage-extend -``` - -#### ghe-version - -Esta utilidad imprime la versión, la plataforma y la compilación de {% data variables.product.product_location_enterprise %}. - -```shell -$ ghe-version -``` - -#### ghe-webhook-logs - -Esta utilidad genera registros de entregas de webhooks para que los administradores los revisen e identifiquen cualquier problema. - -```shell -ghe-webhook-logs -``` - -Para mostrar todas las entregas fallidas del gancho en el día anterior: -```shell -ghe-webhook-logs -f -a YYYYMMDD -``` - -Para mostrar todos los resultados, carga útil y excepciones del gancho para la entrega: -```shell -ghe-webhook-logs -g delivery-guid -v -``` - -Para mostrar las entregas globales de webhook: -```shell -ghe-webhook-logs --global -``` - -### Agrupación - -#### estado ghe-dpages - -Esta utilidad le permite gestionar el servidor {% data variables.product.prodname_pages %} distribuido. - -```shell -$ ghe-cluster-status -``` - -#### ghe-cluster-support-bundle - -Esta utilidad crea un tarball de paquetes de soporte que contiene registros importantes de cada nodo, tanto en la configuración de Replicación geográfica como de Agrupación. - -Por defecto, el comando crea el tarball en */tmp*, pero también puedes tener `cat` el tarball en `STDOUT` para una fácil transmisión por SSH. Esto es útil en caso de que la UI web no responda o que no funcione descargar un paquete de soporte desde */setup/support*. Debes usar este comando si quieres generar un paquete *ampliado* que contenga registros antiguos. También puedes usar este comando para cargar el paquete de soporte de agrupación directamente para {% data variables.product.prodname_enterprise %} recibir asistencia. - -Para crear un paquete estándar: -```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz -``` - -Para crear un paquete extendido: -```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz -``` - -Para enviar un paquete a {% data variables.contact.github_support %}: -```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -u' -``` - -Para mandar un paquete a {% data variables.contact.github_support %} y asociarlo con un ticket: -```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -t ticket-id' -``` - -{% if currentVersion ver_gt "enterprise-server@2.21" %} -#### ghe-cluster-failover - -Fail over from active cluster nodes to passive cluster nodes. For more information, see "[Initiating a failover to your replica cluster](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)." - -```shell -ghe-cluster-failover -``` -{% endif %} - -#### ghe-dpages - -Esta utilidad le permite gestionar el servidor {% data variables.product.prodname_pages %} distribuido. - -```shell -ghe-dpages -``` - -Para mostrar un resumen de la ubicación y salud del repositorio: -```shell -estado ghe-dpages -``` - -Para evacuar un servicio de almacenamiento {% data variables.product.prodname_pages %} antes de evacuar un nodo de agrupación: -``` shell -ghe-dpages evacuate pages-server- -``` - -#### ghe-spokes - -Esta utilidad te permite administrar las tres copias de cada repositorio en los servidores de git distribuidos. - -```shell -ghe-spokes -``` - -Para mostrar un resumen de la ubicación y salud del repositorio: - -```shell -estado ghe-spokes -``` - -Para mostrar los servidores en donde el repositorio se encuentra almacenado: - -```shell -ruta ghe-spokes -``` - -Para evacuar los servicios de almacenamiento en un nodo de la agrupación: - -``` shell -ghe-spokes server evacuate git-server- -``` - -#### ghe-storage - -Esta utilidad te permite evacuar todos los servicios de almacenamiento antes de evacuar un nodo de agrupación. - -``` shell -ghe-storage evacuate storage-server- -``` - -### Git - -#### ghe-btop - -Una interfaz del tipo `top` para las operaciones actuales de Git. - -```shell -ghe-btop [ | --help | --usage ] -``` - -#### ghe-repo - -Esta utilidad te permite cambiar a un directorio del repositorio y abrir un shell interactivo como el de usuario de `git`. Puedes realizar inspecciones o mantenimientos manuales de un repositorio a través de comandos como `git-*` o `git-nw-*`. - -```shell -ghe-repo username/reponame -``` - -#### ghe-repo-gc - -Esta utilidad reempaqueta en forma manual una red de repositorios para optimizar el almacenamiento de paquetes. Si tienes un repositorio grande, ejecutar este comando puede ayudar a reducir su tamaño general. {% data variables.product.prodname_enterprise %} ejecuta en forma automática este comando durante toda tu interacción con una red de repositorios. - -Puedes agregar el argumento opcional `--prune` para eliminar los objetos de Git inaccesibles que no están referenciados desde una rama, una etiqueta o cualquier otra referencia. Esto es útil, en especial, para eliminar de inmediato [información sensible previamente suprimida](/enterprise/user/articles/remove-sensitive-data/). - -```shell -ghe-repo-gc username/reponame -``` - -### Importar y exportar - -#### ghe-migrator - -`ghe-migrator` es una herramienta de alta fidelidad que te ayuda a realizar migraciones desde una instancia de GitHub a otra. Puedes consolidar tus instancias o mover tu organización, usuarios, equipos y repositorios desde GitHub.com a {% data variables.product.prodname_enterprise %}. - -Para obtener más información, consulta nuestra guía en [migrar datos de usuarios, organizaciones y repositorios](/enterprise/admin/guides/migrations/). - -#### git-import-detect - -Con una URL, detecta qué tipo de sistema de administración de control de fuente hay en el otro extremo. Durante una importación manual, probablemente ya lo sepas, pero puede ser muy útil en scripts automáticos. -```shell -git-import-detect -``` - -#### git-import-hg-raw - -Esta utilidad importa un repositorio de Mercurial a este repositorio de Git. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." -```shell -git-import-hg-raw -``` - -#### git-import-svn-raw - -Esta utilidad importa los datos del archivo y el historial de Subversion en una rama de Git. Es una copia exacta del árbol, que ignora cualquier distinción de tronco o rama. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." -```shell -git-import-svn-raw -``` - -#### git-import-tfs-raw - -Esta utilidad importa desde el Control de Versiones de Team Foundation. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." -```shell -git-import-tfs-raw -``` - -#### git-import-rewrite - -Esta utilidad reescribe el repositorio importado. Esto te permite renombrar a los autores y, en el caso de TFS y Subversion, produce ramas de Git basadas en carpetas. Para obtener más información, consulta "[importar datos de sistemas de control de versiones de terceros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." -```shell -git-import-rewrite -``` - -### Asistencia - -#### ghe-diagnostics - -Esta utilidad realiza varias comprobaciones y reúne información acerca de tu instalación que puedes enviar a la asistencia para que te ayude a diagnosticar los problemas que tienes. - -Actualmente, el resultado de esta utilidad es similar a descargar la información de diagnóstico en la {% data variables.enterprise.management_console %}, pero con el tiempo se pueden agregar otras mejoras que no están disponibles en la UI web. Para obtener más información, consulta "[Crear y compartir archivos de diagnóstico](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)." - -```shell -ghe-diagnostics -``` - -#### ghe-support-bundle - -{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} -Esta utilidad crea un tarball de paquetes de soporte que contiene registros importantes de tu instancia. - -Por defecto, el comando crea el tarball en */tmp*, pero también puedes tener `cat` el tarball en `STDOUT` para una fácil transmisión por SSH. Esto es útil en caso de que la UI web no responda o que no funcione descargar un paquete de soporte desde */setup/support*. Debes usar este comando si quieres generar un paquete *ampliado* que contenga registros antiguos. También puedes usar este comando para cargar el paquete de soporte directamente en la asistencia de {% data variables.product.prodname_enterprise %}. - -Para crear un paquete estándar: -```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz -``` - -Para crear un paquete extendido: -```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -x -o' > support-bundle.tgz -``` - -Para enviar un paquete a {% data variables.contact.github_support %}: -```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -u' -``` - -Para mandar un paquete a {% data variables.contact.github_support %} y asociarlo con un ticket: - -```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -t ticket-id' -``` - -#### ghe-support-upload - -Esta utilidad envía información desde tu aparato a la asistencia de {% data variables.product.prodname_enterprise %}. Puedes especificar un archivo local u ofrecer una transmisión de hasta 100MB de datos a través de `STDIN`. Opcionalmente, los datos cargados se pueden asociar a un ticket de asistencia. - -Para enviar un archivo a {% data variables.contact.github_support %} y asociarlo con un ticket: -```shell -ghe-support-upload -f path/to/your/file -t ticket-id -``` - -Para subir datos a través de `STDIN` y asociarlos con un ticket: -```shell -ghe-repl-status -vv | ghe-support-upload -t ticket-id -d "Verbose Replication Status" -``` - -En este ejemplo, `ghe-repl-status -vv` envía información de estado detallada desde un aparato réplica. Debes reemplazar `ghe-repl-status -vv` con los datos específicos que quieras transmitir a `STDIN` y `Verbose Replication Status` (Estado de replicación detallado) con una breve descripción de los datos. {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} - -### Actualizar {% data variables.product.prodname_ghe_server %} - -#### ghe-upgrade - -Esta utilidad instala o verifica un paquete actualizado. También puedes usar esta utilidad para revertir un lanzamiento de patch si falla o se interrumpe una actualización. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)". - -Para verificar un paquete de mejora: -```shell -ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME -``` - -Para instalar un paquete de mejora: -```shell -ghe-upgrade UPGRADE-PACKAGE-FILENAME -``` - -{% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} - -#### ghe-upgrade-scheduler - -Esta utilidad administra la instalación programada de paquetes de actualización. Puedes mostrar, crear nuevas o eliminar las actualizaciones programadas. Debes crear cronogramas usando expresiones cron. Para obtener más información, consulta [Entrada de Cron en Wikipedia](https://en.wikipedia.org/wiki/Cron#Overview). - -Para programar una nueva instalación para un paquete: -```shell -$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME -``` - -Para mostrar las instalaciones programadas para un paquete: -```shell -$ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME -> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s UPGRADE-PACKAGE-FILENAME > /data/user/common/UPGRADE-PACKAGE-FILENAME.log 2>&1 -``` - -Para eliminar las instalaciones programadas para un paquete: -```shell -$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME -``` - -#### ghe-update-check - -Esta utilidad buscará si hay disponible un nuevo lanzamiento de patch de {% data variables.product.prodname_enterprise %}. Si lo hay, y si hay espacio disponible en tu instancia, descargará el paquete. Por defecto, se guarda en */var/lib/ghe-updates*. Luego, un administrador puede [realizar la actualización](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/). - -En */var/lib/ghe-updates/ghe-update-check.status* puedes acceder a un archivo que contiene el estado de la descarga. - -Para buscar el último lanzamiento de {% data variables.product.prodname_enterprise %}, usa el modificador `-i`. - -```shell -$ ssh -p 122 admin@hostname -- 'ghe-update-check' -``` - -### Gestión de usuarios - -#### 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)". - -Predeterminadamente, la lista de usuarios en el JSON resultante se encuentra cifrada. Usa la marca `-h` para obtener más opciones. - -```shell -ghe-license-usage -``` - -#### ghe-org-membership-update - -Esta utilidad aplicará la visibilidad de la membresía a la organización predeterminada mostrando todos los miembros de tu instancia. Para obtener más información, consulta la sección "[Configurar la visibilidad para la membrecía de la organización](/enterprise/{{ currentVersion }}/admin/guides/user-management/configuring-visibility-for-organization-membership)". Las opciones de configuración son `public` o `private`. - -```shell -ghe-org-membership-update --visibility=SETTING -``` - -#### ghe-user-csv - -Esta utilidad exporta una lista de todos los usuarios en la instalación a un formato CSV. El archivo CSV incluye las direcciones de correo electrónico, el tipo de usuario que son (p. ej., administrador, usuario), cuántos repositorios tienen, cuántas claves SSH tienen, la cantidad de membresías a la organización, la última dirección IP que inició sesión, etc. Usa la marca `-h` para obtener más opciones. - -```shell -ghe-user-csv -o > users.csv -``` - -#### ghe-user-demote - -Esta utilidad baja de categoría al usuario especificado del estado de administrador al de usuario normal. Recomendamos usar la UI web para realizar esta acción, pero proporcionamos esta utilidad en caso de que la utilidad `ghe-user-promote` se ejecute con error, y debas volver a bajar de categoría a un usuario desde la CLI (interfaz de línea de comandos). - -```shell -ghe-user-demote some-user-name -``` - -#### ghe-user-promote - -Esta utilidad promueve la cuenta de usuario especificada a administrador del sitio. - -```shell -ghe-user-promote some-user-name -``` - -#### ghe-user-suspend - -Esta utilidad suspende el usuario especificado, evitando que inicie sesión, suba o extraiga datos de tu repositorio. - -```shell -ghe-user-suspend some-user-name -``` - -#### ghe-user-unsuspend - -Esta utilidad anula la suspensión del usuario especificado, otorgándole acceso para iniciar sesión, subir o extraer datos de tu repositorio. - -```shell -ghe-user-unsuspend some-user-name -``` diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-applications.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-applications.md deleted file mode 100644 index 33b1f462ba..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-applications.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Configurar aplicaciones -intro: 'Puedes establecer configuraciones de solicitud interna para {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/installation/configuring-applications - - /enterprise/admin/configuration/configuring-applications - - /admin/configuration/configuring-applications -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals ---- -### Ajustar el almacenamiento en caché de las imágenes - -Puedes elegir la cantidad de tiempo que {% data variables.product.product_location_enterprise %} almacena en caché los avatares. Cuando aumentas el tiempo de almacenamiento en caché, aumentas la cantidad de tiempo que tardará en cargar el avatar de un usuario. Configurar el tiempo de almacenamiento en caché con un valor demasiado bajo puede sobrecargar {% data variables.product.product_location_enterprise %} los procesos de trabajo. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -3. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones). ![Pestaña de solicitudes de la barra lateral de configuraciones](/assets/images/enterprise/management-console/sidebar-applications.png) -4. Debajo de "Avatar image cache time (seconds)" (Tiempo de almacenamiento en caché del avatar [en segundos]), escribe la cantidad de segundos que quieres que {% data variables.product.product_location_enterprise %} almacene en caché las imágenes de avatar.![Campo de formulario de almacenamiento en caché de imagen de avatar](/assets/images/enterprise/management-console/add-image-caching-value-field.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md deleted file mode 100644 index 094a210d1d..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -title: Configurar copias de seguridad en tu aparato -redirect_from: - - /enterprise/admin/categories/backups-and-restores/ - - /enterprise/admin/articles/backup-and-recovery/ - - /enterprise/admin/articles/backing-up-github-enterprise/ - - /enterprise/admin/articles/restoring-github-enterprise/ - - /enterprise/admin/articles/backing-up-repository-data/ - - /enterprise/admin/articles/restoring-enterprise-data/ - - /enterprise/admin/articles/restoring-repository-data/ - - /enterprise/admin/articles/backing-up-enterprise-data/ - - /enterprise/admin/guides/installation/backups-and-disaster-recovery/ - - /enterprise/admin/installation/configuring-backups-on-your-appliance - - /enterprise/admin/configuration/configuring-backups-on-your-appliance - - /admin/configuration/configuring-backups-on-your-appliance -intro: 'Como parte de un plan de recuperación ante desastres, puedes proteger los datos de producción en {% data variables.product.product_location_enterprise %} configurando copias de seguridad automáticas.' -versions: - ghes: '*' -topics: - - Backups - - Enterprise - - Fundamentals - - Infrastructure ---- -### Acerca de {% data variables.product.prodname_enterprise_backup_utilities %} - -{% data variables.product.prodname_enterprise_backup_utilities %} es un sistema de copias de seguridad que instalas en un host separado, el cual realiza instantáneas de copias de seguridad de {% data variables.product.product_location_enterprise %} en intervalos regulares a través de una conexión de red SSH segura. Puedes utilizar una instantánea para restablecer una instancia existente del {% data variables.product.prodname_ghe_server %} a su estado previo desde el host de copias de seguridad. - -Solo se transferirán por la red y ocuparán espacio de almacenamiento físico adicional los datos que se hayan agregado después de esa última instantánea. Para minimizar el impacto en el rendimiento, las copias de seguridad se realizan en línea con la prioridad CPU/IO más baja. No necesitas programar una ventana de mantenimiento para realizar una copia de seguridad. - -Para obtener información más detallada sobre las funciones, los requisitos y el uso avanzado, consulta [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme). - -### Prerrequisitos - -Para utilizar {% data variables.product.prodname_enterprise_backup_utilities %}, debes tener un sistema de host Linux o Unix separado de {% data variables.product.product_location_enterprise %}. - -También puedes incorporar {% data variables.product.prodname_enterprise_backup_utilities %} en un entorno existente para almacenar los datos críticos de manera permanente y a largo plazo. - -Recomendamos que exista una distancia geográfica entre el host de copias de seguridad y {% data variables.product.product_location_enterprise %}. Esto asegura que las copias de seguridad estén disponibles para su recuperación en el caso de que ocurra un desastre significativo o una interrupción de red en el sitio principal. - -Los requisitos de almacenamiento físico variarán en función del uso del disco del repositorio de Git y de los patrones de crecimiento esperados: - -| Hardware | Recomendación | -| ------------------ | ---------------------------------------------------------------- | -| **vCPU** | 2 | -| **Memoria** | 2 GB | -| **Almacenamiento** | Cinco veces el almacenamiento asignado de la instancia principal | - -Es posible que se requieran más recursos según su uso, como la actividad del usuario y las integraciones seleccionadas. - -### Instalar {% data variables.product.prodname_enterprise_backup_utilities %} - -{% note %} - -**Nota:** Para asegurar que un aparato recuperado esté disponible de inmediato, realiza copias de seguridad apuntando a la instancia principal, incluso en una configuración de replicación geográfica. - -{% endnote %} - -1. Desgarga el último lanzamiento de [{% data variables.product.prodname_enterprise_backup_utilities %} ](https://github.com/github/backup-utils/releases) y extrae el archivo con el comando `tar`. - ```shell - $ tar -xzvf /path/to/github-backup-utils-vMAJOR.MINOR.PATCH.tar.gz - ``` -2. Copia el archivo incluido `backup.config-example` en `backup.config` y ábrelo en un editor. -3. Configura el valor `GHE_HOSTNAME` al {% data variables.product.prodname_ghe_server %} primario del nombre del host de tu instancia o dirección IP. -4. Configura el valor `GHE_DATA_DIR` en la ubicación del sistema de archivos donde deseas almacenar las instantáneas de copia de seguridad. -5. Abre la página de configuración de tu instancia primaria en `https://HOSTNAME/setup/settings` y agrega la clave SSH del host de copia de seguridad a la lista de claves SSH autorizadas. Para obtener más información, consulta [Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/). -5. Verifica la conectividad SSH con {% data variables.product.product_location_enterprise %} con el comando `ghe-host-check`. - ```shell - $ bin/ghe-host-check - ``` - 6. Para crear una copia de respaldo completa inicial, ejecuta el comando `ghe-backup`. - ```shell - $ bin/ghe-backup - ``` - -Para obtener más información sobre uso avanzado, consulta el archivo README en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). - -### Programar una copia de seguridad - -Puedes programar copias de seguridad regulares en el host de copia de seguridad utilizando el comando `cron(8)` o un servicio de programación de comando similar. La frecuencia de copias de seguridad configurada dictará el peor caso de Punto Objetivo de Recuperación (RPO) de tu plan de recuperación. Por ejemplo, si has programado que la copia de seguridad se ejecute todos los días a la medianoche, podrías perder hasta 24 horas de datos en un escenario de desastre. Recomendamos comenzar con un cronograma de copias de seguridad por hora, que garantice un peor caso máximo de una hora de pérdida de datos, si los datos del sitio principal se destruyen. - -Si los intentos de copias de seguridad se superponen, el comando `ghe-backup` se detendrá con un mensaje de error que indicará la existencia de una copia de seguridad simultánea. Si esto ocurre, recomendamos que disminuyas la frecuencia de tus copias de seguridad programadas. Para obtener más información, consulta la sección "Programar copias de seguridad" del archivo README en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#scheduling-backups). - -### Recuperar una copia de seguridad - -En el caso de una interrupción de red prolongada o de un evento catastrófico en el sitio principal, puedes restablecer {% data variables.product.product_location_enterprise %} proporcionando otro aparato para {% data variables.product.prodname_enterprise %} y haciendo un restablecimiento desde el host de copias de seguridad. Debes agregar la clave SSH del host de copias de seguridad en el aparato objetivo {% data variables.product.prodname_enterprise %} como una clave SSH autorizada antes de restablecer un aparato. - -Para restablecer {% data variables.product.product_location_enterprise %} desde la última instantánea exitosa, usa el comando `ghe-restore`. Debes ver un resultado similar a este: - -```shell -$ ghe-restore -c 169.154.1.1 -> Comprobando claves filtradas en la instantánea de respaldo que se está restableciendo ... -> * No se encontraron claves filtradas -> Conectarse a 169.154.1.1:122 OK (v2.9.0) - -> ADVERTENCIA: Todos los datos del aparato GitHub Enterprise 169.154.1.1 (v2.9.0) -> se sobrescribirán con los datos de la instantánea 20170329T150710. -> Antes de continuar, verifica que sea el host de restauración correcto. -> Escribe 'yes' (sí) para continuar: yes - -> Comenzando la restauración de 169.154.1.1:122 desde la instantánea 20170329T150710 -# ...resultado truncado -> Restauración completa de 169.154.1.1:122 desde la instantánea 20170329T150710 -> Visita https://169.154.1.1/setup/settings para revisar la configuración del aparato. -``` - -{% note %} - -**Nota:** Los ajustes de red están excluidos de la instantánea de copias de seguridad. Debes configurar manualmente la red en el aparato objetivo para el {% data variables.product.prodname_ghe_server %} como obligatoria para tu entorno. - -{% endnote %} - -Puedes utilizar estas otras opciones con el comando `ghe-restore`: -- La marca `-c` sobrescribe los ajustes, el certificado y los datos de licencia en el host objetivo, incluso si ya está configurado. Omite esta marca si estás configurando una instancia de preparación con fines de prueba y si quieres conservar la configuración existente en el objetivo. Para obtener más información, consulta la sección "Utilizar una copia de seguridad y restablecer los comandos" de [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands). -- La marca `-s` te permite seleccionar otra instantánea de copias de seguridad. diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-on-your-appliance.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-on-your-appliance.md deleted file mode 100644 index 5495a82693..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-on-your-appliance.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Configurar las Páginas de GitHub en su aparato -intro: 'Puedes habilitar o inhabilitar {% data variables.product.prodname_pages %} en tu instancia. También puedes elegir hacer que los sitios {% data variables.product.prodname_pages %} sean de acceso público.' -redirect_from: - - /enterprise/admin/guides/installation/disabling-github-enterprise-pages/ - - /enterprise/admin/guides/installation/configuring-github-enterprise-pages/ - - /enterprise/admin/installation/configuring-github-pages-on-your-appliance - - /enterprise/admin/configuration/configuring-github-pages-on-your-appliance - - /admin/configuration/configuring-github-pages-on-your-appliance -versions: - enterprise-server: '*' ---- -### Making {% data variables.product.prodname_pages %} publicly accessible - -El modo privado está habilitado en tu aparato, el público no puede acceder a los sitios {% data variables.product.prodname_pages %} alojados en {% data variables.product.product_location_enterprise %}. - -{% warning %} - -**Advertencia:** Si habilitas los sitios públicos {% data variables.product.prodname_pages %}, todos los sitios {% data variables.product.prodname_pages %} de cada repositorio de tu instancia serán de acceso público. - -{% endwarning %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.pages-tab %} -4. Selecciona **Public Pages** (Páginas públicas). ![Casilla de verificación para habilitar páginas públicas](/assets/images/enterprise/management-console/public-pages-checkbox.png) -{% data reusables.enterprise_management_console.save-settings %} - -### Inhabilitar {% data variables.product.prodname_pages %} en {% data variables.product.product_location_enterprise %} - -Si el aislamiento de subdominio está inhabilitado para {% data variables.product.product_location_enterprise %}, también debes inhabilitar {% data variables.product.prodname_pages %} para protegerte a ti mismo contra posibles vulnerabilidades de seguridad. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation)." - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.pages-tab %} -4. Anula la selección de **Enable Pages** (Habilitar páginas). ![Casilla de verificación para inhabilitar {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png) -{% data reusables.enterprise_management_console.save-settings %} - -### Leer más - -- "[Habilitar el modo privado](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-private-mode)" diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md deleted file mode 100644 index 59a038cdfa..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Configurar límites de tasa -intro: 'Puedes configurar límites de tasa para {% data variables.product.prodname_ghe_server %} usando la {% data variables.enterprise.management_console %}.' -redirect_from: - - /enterprise/admin/installation/configuring-rate-limits - - /enterprise/admin/configuration/configuring-rate-limits - - /admin/configuration/configuring-rate-limits -versions: - ghes: '*' -topics: - - Enterprise - - Infrastructure - - Performance ---- -### Habilitar límites de tasa para {% data variables.product.prodname_enterprise_api %} - -Habilitar límites de tasa en {% data variables.product.prodname_enterprise_api %} puede evitar el uso excesivo de recursos por parte de usuarios individuales o sin autenticación. Para obtener más información, consulta la sección "[Limites de tasa](/enterprise/{{ currentVersion }}/v3/#rate-limiting)." - -{% if currentVersion ver_gt "enterprise-server@2.21" %} -You can exempt a list of users from API rate limits using the `ghe-config` utility in the administrative shell. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-config)." -{% endif %} - -{% note %} - -**Nota:** La {% data variables.enterprise.management_console %} detalla el período de tiempo (por minuto o por hora) de cada límite de tasa. - -{% endnote %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. En "Limitación de tasa", selecciona **Enable API Rate Limiting** (Habilitar la limitación de tasa de API). ![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 %} - -### Habilitar límites de tasa de abuso - -Establecer límites de tasa de abuso protege el nivel general de servicio en {% data variables.product.product_location_enterprise %}. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -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) -3. Escribe límites para las solicitudes totales, límite de CPU y límite de CPU para búsquedas, o acepta los límites predeterminados que aparecen completados. -{% data reusables.enterprise_management_console.save-settings %} - -### Habilitar límites de tasa de Git - -Puedes aplicar límites de tasa de Git por red de repositorios o por Id. de usuario. Los límites de tasa de Git se expresan en operaciones simultáneas por minuto y se adaptan en función de la carga de CPU actual. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. En "Limitación de tasa", selecciona **Enable Git Rate Limiting** (Habilitar limitación de tasa de Git). ![Casilla para habilitar la limitación de tasa de Git](/assets/images/enterprise/management-console/git-rate-limits-checkbox.png) -3. Escribe los límites para cada red de repositorios o ID de usuario. ![Campos para la red de repositorios y límites de ID de usuario](/assets/images/enterprise/management-console/example-git-rate-limits.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md deleted file mode 100644 index ef50d87d27..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Configurar la sincronización de hora -intro: '{% data variables.product.prodname_ghe_server %} sincroniza automáticamente el reloj conectándose con los servidores NTP. Puedes establecer los servidores NTP que se utilicen para sincronizar el reloj o puedes usar los servidores NTP predeterminados.' -redirect_from: - - /enterprise/admin/articles/adjusting-the-clock/ - - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings/ - - /enterprise/admin/articles/setting-ntp-servers/ - - /enterprise/admin/categories/time/ - - /enterprise/admin/installation/configuring-time-synchronization - - /enterprise/admin/configuration/configuring-time-synchronization - - /admin/configuration/configuring-time-synchronization -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Networking ---- -### Cambiar los servidores NTP predeterminados - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. En la barra lateral izquierda, haz clic en **Time** (Hora). ![El botón de la hora en la barra lateral {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/sidebar-time.png) -3. En "Servidor NTP principal", escribe el nombre del host del servidor NTP principal. En "Servidor NTP secundario", escribe el nombre del host del servidor NTP secundario. ![Los campos para los servidores NTP principal y secundario en la {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/ntp-servers.png) -4. Al final de la página, haz clic en **Save settings** (Guardar configuraciones). ![El botón de guardar en la {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png) -5. Espera a que la configuración se ejecute por completo. - -### Corregir un desface de tiempo prolongado - -El protocolo NTP corrige permanentemente las pequeñas discrepancias de sincronización de hora. Puedes usar el shell administrativo para sincronizar la hora de inmediato. - -{% note %} - -**Notas:** - - No puedes modificar la zona horaria universal coordinada (UTC). - - Debes evitar que tu hipervisor trate de configurar el reloj de la máquina virtual. Para obtener más información, consulta la documentación proporcionada por el proveedor de virtualización. - -{% endnote %} - -- Utiliza el comando `chronyc` para sincronizar el servidor con el servidor NTP configurado. Por ejemplo: - -```shell -$ sudo chronyc -a makestep -``` diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md deleted file mode 100644 index 67492de6e4..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Habilitar y programar el modo de mantenimiento -intro: 'Algunos procedimientos de mantenimiento estándar, como la actualización {% data variables.product.product_location_enterprise %} o la restauración de copias de seguridad, exigen que la instancia esté sin conexión para el uso normal.' -redirect_from: - - /enterprise/admin/maintenance-mode/ - - /enterprise/admin/categories/maintenance-mode/ - - /enterprise/admin/articles/maintenance-mode/ - - /enterprise/admin/articles/enabling-maintenance-mode/ - - /enterprise/admin/articles/disabling-maintenance-mode/ - - /enterprise/admin/guides/installation/maintenance-mode/ - - /enterprise/admin/installation/enabling-and-scheduling-maintenance-mode - - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode - - /admin/configuration/enabling-and-scheduling-maintenance-mode -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Maintenance - - Upgrades ---- -### Acerca del modo de mantenimiento - -Algunos tipos de operaciones exigen que desconectes tu {% data variables.product.product_location_enterprise %} y la pongas en modo de mantenimiento: -- Actualizar a una versión nueva de tu {% data variables.product.prodname_ghe_server %} -- Aumentar los recursos de CPU, memoria o almacenamiento asignados a la máquina virtual -- Migrar datos desde una máquina virtual a otra -- Restaurar datos desde una instantánea de {% data variables.product.prodname_enterprise_backup_utilities %} -- Solucionar ciertos tipos de problemas críticos de solicitud - -Recomendamos que programe una ventana de mantenimiento para, al menos, los siguientes 30 minutos para darle a los usuarios tiempo para prepararse. Cuando está programada una ventana de mantenimiento, todos los usuarios verán un mensaje emergente al acceder al sitio. - -![Mensaje emergente para el usuario final acerca del mantenimiento programado](/assets/images/enterprise/maintenance/maintenance-scheduled.png) - -Cuando la instancia está en modo de mantenimiento, se rechazan todos los accesos HTTP y Git. Las operaciones de extracción, clonación y subida de Git también se rechazan con un mensaje de error que indica que temporalmente el sitio no se encuentra disponible. Al visitar el sitio desde un navegador aparece una página de mantenimiento. - -![La pantalla de presentación del modo de mantenimiento](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png) - -### Habilitar el modo de mantenimiento de inmediato o programar una ventana de mantenimiento para más tarde - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. En la parte superior de la {% data variables.enterprise.management_console %}, haz clic en **Mantenimiento**. ![Pestaña de mantenimiento](/assets/images/enterprise/management-console/maintenance-tab.png) -3. En "Habilitar y Programar", decide si habilitas el modo de mantenimiento de inmediato o programas una ventana de mantenimiento para otro momento. - - Para habilitar el modo de mantenimiento de inmediato, usa el menú desplegable y haz clic en **now** (ahora). ![Menú desplegable con la opción para habilitar el modo de mantenimiento ahora seleccionado](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png) - - Para programar una ventana de mantenimiento para otro momento, usa el menú desplegable y haz clic en un horario de inicio. ![Menú desplegable con la opción para programar una ventana de mantenimiento](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png) -4. Selecciona **Habilitar el modo de mantenimiento**. ![Casilla de verificación para habilitar o programar el modo de mantenimiento](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png) -{% data reusables.enterprise_management_console.save-settings %} - -### Programar el modo de mantenimiento con {% data variables.product.prodname_enterprise_api %} - -Puedes programar el mantenimiento para horarios o días diferentes con {% data variables.product.prodname_enterprise_api %}. Para obtener más información, consulta la sección "[Consola de Administración](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)". - -### Habilitar o inhabilitar el modo de mantenimientos para todos los nodos de una agrupación - -Con la herramienta `ghe-cluster-maintenance`, puedes configurar o anular la configuración del modo de mantenimiento para cada nodo de una agrupación. - -```shell -$ ghe-cluster-maintenance -h -# Muestra opciones -$ ghe-cluster-maintenance -q -# Consulta el modo actual -$ ghe-cluster-maintenance -s -# Configura el modo de mantenimiento -$ ghe-cluster-maintenance -u -# Anula la configuración del modo de mantenimiento -``` diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md deleted file mode 100644 index a8730a61f3..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Habilitar el modo privado -intro: 'En el modo privado, {% data variables.product.prodname_ghe_server %} exige que todos los usuarios inicien sesión para acceder a la instalación.' -redirect_from: - - /enterprise/admin/articles/private-mode/ - - /enterprise/admin/guides/installation/security/ - - /enterprise/admin/guides/installation/securing-your-instance/ - - /enterprise/admin/installation/enabling-private-mode - - /enterprise/admin/configuration/enabling-private-mode - - /admin/configuration/enabling-private-mode -versions: - ghes: '*' -topics: - - Access management - - Authentication - - Enterprise - - Fundamentals - - Infrastructure - - Networking - - Privacy - - Security ---- -Debes habilitar el modo privado si {% data variables.product.product_location_enterprise %} es de acceso público por internet. En el modo privado, los usuarios no pueden clonar repositorios en forma anónima por `git://`. Si también está habilitada la autenticación incorporada, un administrador debe invitar a los nuevos usuarios para que creen una cuenta en la instancia. Para obtener más información, consulta "[Usar la autenticación incorporada](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-built-in-authentication)." - -{% data reusables.enterprise_installation.image-urls-viewable-warning %} - -Con el modo privado habilitado, puedes permitir que operaciones de Git sin autenticación (y cualquiera con acceso de red a {% data variables.product.product_location_enterprise %}) lean un código de repositorio público de tu instancia con acceso de lectura anónimo de Git habilitado. Para obtener más información, consulta "[Permitir que los administradores habiliten el acceso de lectura anónimo de Git para los repositorios públicos](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)." - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.privacy %} -4. Selecciona **Private mode** (Modo privado). ![Casilla de verificación para habilitar el modo privado](/assets/images/enterprise/management-console/private-mode-checkbox.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/index.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/index.md deleted file mode 100644 index 63a063c441..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/index.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Configurar tu empresa -intro: 'Una vez que {% data variables.product.prodname_ghe_server %} esté en funcionamiento, puedes configurar el aparato para que se adapte a las necesidades de tu organización.' -redirect_from: - - /enterprise/admin/guides/installation/basic-configuration/ - - /enterprise/admin/guides/installation/administrative-tools/ - - /enterprise/admin/articles/restricting-ssh-access-to-specific-hosts/ - - /enterprise/admin/guides/installation/configuring-the-github-enterprise-appliance/ - - /enterprise/admin/installation/configuring-the-github-enterprise-server-appliance - - /enterprise/admin/configuration/configuring-your-enterprise -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /about-enterprise-configuration - - /initializing-github-ae - - /accessing-the-management-console - - /accessing-the-administrative-shell-ssh - - /enabling-and-scheduling-maintenance-mode - - /configuring-backups-on-your-appliance - - /site-admin-dashboard - - /enabling-private-mode - - /managing-github-for-mobile-for-your-enterprise - - /configuring-email-for-notifications - - /verifying-or-approving-a-domain-for-your-enterprise - - /configuring-rate-limits - - /configuring-applications - - /troubleshooting-ssl-errors - - /configuring-time-synchronization - - /command-line-utilities - - /restricting-network-traffic-to-your-enterprise - - /configuring-github-pages-for-your-enterprise - - /configuring-the-referrer-policy-for-your-enterprise ---- - diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md deleted file mode 100644 index 25dcee7290..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ /dev/null @@ -1,208 +0,0 @@ ---- -title: Tablero de administración del sitio -intro: 'El tablero de administración del sitio brinda una cantidad de herramientas para ayudarte a administrar {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/articles/site-admin-dashboard/ - - /enterprise/admin/installation/site-admin-dashboard - - /enterprise/admin/configuration/site-admin-dashboard - - /admin/configuration/site-admin-dashboard -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Fundamentals ---- -Para acceder al tablero, en la esquina superior derecha de cualquier página, haz clic en {% octicon "rocket" aria-label="The rocket ship" %}. ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) - -{% if currentVersion ver_gt "enterprise-server@2.21" %} - -### Buscar - -Aquí puedes iniciar la {% data variables.enterprise.management_console %} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL. - -{% else %} - -### Información de la licencia & buscar - -Consulta esta sección del tablero de administración del sitio para controlar tu licencia {% data variables.product.prodname_enterprise %} actual, para buscar usuarios y repositorios y para consultar el [registro de auditoría](#audit-log). - -{% endif %} - -### {% data variables.enterprise.management_console %} - -Aquí puedes iniciar la {% data variables.enterprise.management_console %} para administrar las configuraciones del aparato virtual como el dominio, la autenticación y SSL. - -### Explorar - -Los datos para la [página de tendencia][] de GitHub se calculan en lapsos de tiempo diarios, semanales y mensuales para ambos repositorios y programadores. Puedes ver cuándo estos datos fueron almacenados en caché por última vez y poner en cola las tareas nuevas de cálculo de tendencia desde la sección **Explore (Explorar)**. - -### Registro de auditoría - -{% data variables.product.prodname_enterprise %} mantiene un registro continuo de las acciones auditadas que puedes consultar. - -Por defecto, el registro de auditoría te muestra una lista de todas las acciones auditadas en orden cronológico reverso. Puedes filtrar esta lista al ingresar pares de valores clave en el casillero de texto de **Query (Consulta)** y después hacer clic en **Search (Buscar)**, como se explicó en "[Buscar el registro de auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)." - -Para obtener más información acerca de las bitácoras de auditoria en general, consulta "[Bitácoras de Auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)". Para encontrar una lista completa de las acciones auditadas, consulta la sección "[Acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)". - -### Informes - -Si necesitas obtener información sobre los usuarios, organizaciones y repositorios en {% data variables.product.product_location_enterprise %}, comúnmente extraerías datos JSON a través de la [API de GitHub](/rest). Lamentablemente, es posible que la API no proporcione todos los datos que deseas y se requiera algo de conocimiento técnico para usarla. Este tablero de administración del sitio ofrece una sección de **Reports (Informes)** como una alternativa, haciendo que sea fácil descargar informes CSV con la mayoría de la información que probablemente necesites para los usuarios, las organizaciones y los repositorios. - -Específicamente, puedes descargar informes CSV que enumeren a - -- todos los usuarios -- todos los usuarios que han estado activos dentro del último mes -- todos los usuarios que han estado inactivos durante un mes o más -- todos los usuarios que han sido suspendidos -- todas las organizaciones -- todos los repositorios - -También puedes acceder a estos informes mediante programación a través de una autenticación estándar de HTTP con una cuenta de administrador del sitio. Debes utilizar un token de acceso personal con alcance de `site_admin`. 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)". - -Por ejemplo, así es como descargarías el informe "todos los usuarios" utilizando cURL: - -```shell -curl -L -u username:token http(s)://hostname/stafftools/reports/all_users.csv -``` - -Para acceder a otros informes mediante programación, reemplaza `all_users` con `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, o `all_repositories`. - -{% note %} - -**Nota:** La solicitud `curl` inicial devolverá una respuesta 202 HTTP si no hay informes en caché disponibles; se generará un informe en segundo plano. Puedes enviar una segunda solicitud para descargar el informe. Puedes utilizar una contraseña o un token de OAuth con el alcance `site_admin` en lugar de la contraseña. - -{% endnote %} - -#### Informes del usuario - -| Clave | Descripción | -| ------------------------:| --------------------------------------------------------------------------------- | -| `created_at (creado en)` | Cuándo fue creada la cuenta de usuario (como una marca de tiempo ISO 8601) | -| `id` | ID de la cuenta para el usuario o la organización | -| `login` | Nombre de inicio de sesión de la cuenta | -| `correo electrónico` | Dirección principal de correo electrónico de la cuenta | -| `rol` | Si la cuenta es de un usuario administrador o de un usuario común | -| `suspended?` | Si la cuenta ha sido suspendida | -| `last_logged_ip` | La dirección IP más reciente que se registró en la cuenta | -| `repos` | Cantidad de repositorios que posee la cuenta | -| `ssh_keys` | Cantidad de claves SSH registradas en la cuenta | -| `org_memberships` | Cantidad de organizaciones a las que pertenece la cuenta | -| `dormant?` | Si la cuenta está inactiva | -| `last_active` | Cuándo la cuenta estuvo activa por última vez (como una marca de tiempo ISO 8601) | -| `raw_login` | Información de inicio de sesión sin procesar (en formato JSON) | -| `2fa_enabled?` | Si el usuario ha habilitado autenticación de dos factores | - -#### Informes de la organización - -| Clave | Descripción | -| ------------------------:| ------------------------------------------------------------ | -| `id` | ID de la organización | -| `created_at (creado en)` | Cuándo se creó la organización | -| `login` | Nombre de inicio de sesión de la organización | -| `correo electrónico` | Dirección principal de correo electrónico de la organización | -| `owners` | Cantidad de propietarios de la organización | -| `members` | Cantidad de miembros de la organización | -| `equipos` | Cantidad de equipos de la organización | -| `repos` | Cantidad de repositorios de la organización | -| `2fa_required?` | Si la organización requiere autenticación de dos factores | - -#### Informes del repositorio - -| Clave | Descripción | -| ------------------------:| ------------------------------------------------------------------ | -| `created_at (creado en)` | Cuándo fue creado el repositorio | -| `owner_id` | ID del propietario del repositorio | -| `owner_type` | Si el repositorio es propiedad de un usuario o de una organización | -| `owner_name` | Nombre del propietario del repositorio | -| `id` | ID del repositorio | -| `name (nombre)` | Nombre del repositorio | -| `visibilidad` | Si el repositorio es público o privado | -| `readable_size` | El tamaño del repositorio en un formato legible | -| `raw_size` | Tamaño del repositorio como un número | -| `collaborators` | Cantidad de colaboradores del repositorio | -| `fork?` | Si el repositorio es una bifurcación | -| `deleted?` | Si el repositorio ha sido borrado | - -### Indexar - -Las funciones de [búsqueda de código][] de GitHub son propulsadas por [ElasticSearch][]. Esta sección del tablero de administración del sitio muestra el estado actual de tu agrupación de ElasticSearch y brinda diversas herramientas para controlar el comportamiento de búsqueda e indexación. Estas herramientas están separadas en las siguientes tres categorías. - -#### Búsqueda de código - -Esto te permite habilitar o deshabilitar tanto las operaciones de búsqueda como de indexación en el código fuente. - -#### Reparación del índice de búsqueda de código - -Esto controla cómo se repara el índice de búsqueda de código. Puedes - -- habilitar o inhabilitar tareas de reparación de índices -- comenzar una nueva tarea de reparación de índice -- restablecer todos los estados de reparación de índices - -{% data variables.product.prodname_enterprise %} utiliza tareas de reparación para compaginar el estado del índice de búsqueda con los datos almacenados en una base de datos (propuestas, solicitudes de extracción, repositorios y usuarios) y los datos almacenados en los repositorios de Git (código fuente). Esto sucede cuando - -- se crea un nuevo índice de búsqueda; -- faltan datos que se deben reponer; o -- los datos de búsqueda antiguos deben ser actualizados. - -En otras palabras, las tareas de reparación se inician según se necesiten y se ejecutan en segundo plano, no están programados por los administradores del sitio de ningún modo. - -Además, las tareas de reparación utilizan una "compensación de reparación" para la paralelización. Esto es una compensación dentro de la tabla de base de datos para el registro que se está compaginando. Múltiples tareas en segundo plano pueden sincronizar el trabajo en base a esta compensación. - -Una barra de progreso muestra el estado actual de la tarea de reparación a través de todos sus trabajadores en segundo plano. Es la diferencia de porcentaje de la compensación de reparación con el ID de registro más alto en la base de datos. No te preocupes sobre el valor que se muestra en la barra de progreso después de que una tarea de reparación se haya completado: ya que muestra la diferencia entre la compensación de reparación y el ID del registro más alto en la base de datos, disminuirá a medida que se agreguen más repositorios a {% data variables.product.product_location_enterprise %} incluso aquellos repositorios que están de hecho indexados. - -Puedes comenzar una nueva tarea de reparación de índice de búsqueda de código en cualquier momento. Utilizará una CPU única ya que compagina el índice de búsqueda con la base de datos y los datos del repositorio de Git. Para minimizar los efectos que esto tendrá en el desempeño de I/O y reducir las posibilidades de que las operaciones queden inactivas, trata de ejecutar una tarea de reparación durante las horas valle en primer lugar. Controla las cargas promedio de tu sistema y el uso de tu CPU con una herramienta como `top`; si no notas cambios significativos, debería ser seguro ejecutar una tarea de reparación de índice también durante las horas pico. - -#### Reparación de índice de propuestas - -Esto controla de qué manera se repara el [índice de propuestas][]. Puedes - -- habilitar o inhabilitar tareas de reparación de índices -- comenzar una nueva tarea de reparación de índice -- restablecer todos los estados de reparación de índices - -{% if currentVersion ver_gt "enterprise-server@2.21" %} - -### Todos los usuarios - -Aquí puedes ver todos los usuarios que han sido suspendidos en {% data variables.product.product_location_enterprise %}, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). - -{% endif %} - -### Repositorios - -Es una lista de los repositorios en {% data variables.product.product_location_enterprise %}. Puedes hacer clic en un nombre de repositorio y acceder a las funciones para administrar el repositorio. - -- [Bloquear empujes forzados en un repositorio](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) -- [Configurar {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository) -- [Archivar y desarchivar repositorios](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/) - -### Todos los usuarios - -Aquí puedes ver todos los usuarios en {% data variables.product.product_location_enterprise %}—, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). - -### Administrador del sitio - -Aquí puedes ver todos los administradores en {% data variables.product.product_location_enterprise %}, e [iniciar una auditoría clave en SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). - -### Usuarios inactivos - -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_enterprise %}. Una cuenta de usuario se considera inactiva ("dormant") cuando: - -- Ha existido durante más tiempo del umbral de inactividad que está establecido para {% data variables.product.product_location_enterprise %}. -- No ha generado ninguna actividad dentro de ese período. -- No es un administrador del sitio. - -{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} Para obtener más información, consulta "[Administrar usuarios inactivos](/enterprise/{{ currentVersion }}/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)." - -### Usuarios suspendidos - -Aquí puedes ver todos los usuarios que han sido suspendidos en {% data variables.product.product_location_enterprise %}, e [iniciar una auditoría clave de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). - - [página de tendencia]: https://github.com/blog/1585-explore-what-is-trending-on-github - - [búsqueda de código]: https://github.com/blog/1381-a-whole-new-code-search - [ElasticSearch]: http://www.elasticsearch.org/ - - [índice de propuestas]: https://github.com/blog/831-issues-2-0-the-next-generation diff --git a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md b/translations/es-XL/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md deleted file mode 100644 index 254dc35e3e..0000000000 --- a/translations/es-XL/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: Errores de solución de problemas de SSL -intro: 'Si te encuentras con problemas de SSL en tu aparato, puedes tomar medidas para resolverlos.' -redirect_from: - - /enterprise/admin/articles/troubleshooting-ssl-errors/ - - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration/ - - /enterprise/admin/installation/troubleshooting-ssl-errors - - /enterprise/admin/configuration/troubleshooting-ssl-errors - - /admin/configuration/troubleshooting-ssl-errors -versions: - ghes: '*' -topics: - - Enterprise - - Errors - - Infrastructure - - Networking - - Security - - Troubleshooting ---- -### Eliminar la contraseña de un archivo clave - -Si tienes una máquina linux con OpenSSL instalado, puedes eliminar tu contraseña. - -1. Renombrar tu archivo clave original. - ```shell - $ mv yourdomain.key yourdomain.key.orig - ``` -2. Generar una nueva clave sin una contraseña. - ```shell - $ openssl rsa -in yourdomain.key.orig -out yourdomain.key - ``` - -Se te pedirá la contraseña de la clave cuando ejecutes este comando. - -Para más información sobre OpenSSL, consulta la documentación de OpenSSL [](https://www.openssl.org/docs/). - -### Convertir tu certificado SSL o tu clave a un formato PEM - -Si tienes instalado OpenSSL, puedes convertir tu clave en formato PEM usando el comando `openssl`. Por ejemplo, puedes convertir una clave de formato DER a formato PEM. - -```shell -$ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM -``` - -De lo contrario, puedes utilizar la herramienta SSL Converter para convertir tu certificado a formato PEM. Para obtener más información, consulta la [Documentación de la herramienta SSL Converter](https://www.sslshopper.com/ssl-converter.html). - -### Instalación sin respuesta después de cargar una clave - -Si {% data variables.product.product_location_enterprise %} no tiene respuesta después de cargar una clave SSL, contacta [al {% data variables.product.prodname_enterprise %} Soporte](https://enterprise.github.com/support) con detalles específicos, incluida una copia de tu certificado SSL. - -### Errores de validez de certificado - -Los clientes como navegadores web y líneas de comando Git mostrarán un mensaje de error si no pueden verificar la validez de un certificado SSL. Esto sucede con frecuencia con los certificados autofirmados y los certificados de "raíz encadenada" emitidos por un certificado raíz intermedio que no es reconocido por el cliente. - -Si estás usando un certificado firmado por una autoridad de certificación (CA), el archivo del certificado que cargaste a {% data variables.product.prodname_ghe_server %} debe incluir una cadena de certificado con ese certificado raíz de CA. Para crear dicho archivo, concatena tu cadena de certificado entera (o "paquete de certificado") al final de tu certificado, garantizando que el certificado principal con tu nombre del host aparezca primero. En la mayoría de los sistemas puedes hacer esto con un comando similar a: - -```shell -$ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt -``` - -Deberías poder descargar un paquete de certificado (por ejemplo, `bundle-certificates.crt`) desde tu proveedor de SSL o de la autoridad de certificación. - -### Instalar certificados raíz de autoridad de certificación (CA) autofirmados o que no son de confianza - -Si tu aparato {% data variables.product.prodname_ghe_server %} interactúa con otras máquinas en tu red que utilizan un certificado autofirmado o que no es de confianza, deberás importar el certificado raíz de la CA firmante en el almacenamiento de certificado de todo el sistema para poder acceder a estos sistemas por HTTPS. - -1. Obtén el certificado raíz de la CA de tu autoridad de certificación local y asegúrate que esté en formato PEM. -2. Copia el archivo a tu aparato {% data variables.product.prodname_ghe_server %} por SSH como el usuario "administrador" en el puerto 122. - ```shell - $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin - ``` -3. Conecta a la shell administrativa {% data variables.product.prodname_ghe_server %} por SSH como el usuario "administrador" en el puerto 122. - ```shell - $ ssh -p 122 admin@HOSTNAME - ``` -4. Importa el certificado al almacenamiento de certificado de todo el sistema. - ```shell - $ ghe-ssl-ca-certificate-install -c rootCA.crt - ``` diff --git a/translations/es-XL/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/es-XL/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md deleted file mode 100644 index aa3b7b0656..0000000000 --- a/translations/es-XL/content/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Enabling alerts for vulnerable dependencies on GitHub Enterprise Server -intro: 'You can connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_ghe_cloud %} and enable {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} alerts for vulnerable dependencies in repositories in your instance.' -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 -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 {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}.' -versions: - enterprise-server: '*' -topics: - - Enterprise - - Security ---- - -### About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %} - -{% data reusables.repositories.tracks-vulnerabilities %} For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." - -You can connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_dotcom_the_website %}, then sync vulnerability data to your instance and generate {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} alerts in repositories with a vulnerable dependency. - -After connecting {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_dotcom_the_website %} and enabling {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} 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_enterprise %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. - -{% if currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.product_location_enterprise %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and send {% data variables.product.prodname_dependabot_short %} alerts to owners and people with admin access in those repositories. They can customize how they receive {% data variables.product.prodname_dependabot_short %} alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/#configuring-notifications-for-github-dependabot-alerts)." -{% endif %} - -{% if currentVersion ver_lt "enterprise-server@2.21" or currentVersion == "enterprise-server@2.21" %}When {% data variables.product.product_location_enterprise %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and send security alerts to owners and people with admin access in those repositories. They can customize how they receive security alerts. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/#configuring-notifications-for-security-alerts)." -{% endif %} - -{% if currentVersion ver_gt "enterprise-server@2.21" %} -### Enabling {% data variables.product.prodname_dependabot_short %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %} -{% else %} -### Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %} -{% endif %} - -Before enabling {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} alerts for vulnerable dependencies 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 {% 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)." - -{% if currentVersion ver_gt "enterprise-server@2.20" %} - -{% if currentVersion ver_gt "enterprise-server@2.21" %}We recommend configuring {% data variables.product.prodname_dependabot_short %} 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_short %} alerts as usual.{% endif %} - -{% if currentVersion == "enterprise-server@2.21" %}We recommend configuring security alerts without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive security alerts as usual.{% endif %} - -{% endif %} - -{% data reusables.enterprise_site_admin_settings.sign-in %} -1. In the administrative shell, enable the {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.product_location_enterprise %}: - ``` shell -$ ghe-dep-graph-enable -``` -3. Return to {% data variables.product.prodname_ghe_server %}. -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.github-connect-tab %}{% if currentVersion ver_gt "enterprise-server@2.20" %} -5. 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**.{% else %} -5. Under "Repositories can be scanned for vulnerabilities", use the drop-down menu and select **Enabled**. -{% endif %} - ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) - -### Viewing vulnerable dependencies on {% data variables.product.prodname_ghe_server %} - -You can view all vulnerabilities in {% data variables.product.product_location_enterprise %} 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/es-XL/content/admin/configuration/index.md b/translations/es-XL/content/admin/configuration/index.md deleted file mode 100644 index 00c70ddbd2..0000000000 --- a/translations/es-XL/content/admin/configuration/index.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Configurar GitHub Enterprise -shortTitle: Configurar GitHub Enterprise -intro: 'Una vez que se haya instalado y configurado {% data variables.product.prodname_ghe_server %}, podrás configurar el aplicativo de acuerdo con las necesidades de tu organización.' -redirect_from: - - /enterprise/admin/configuration -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /configuring-your-enterprise - - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud ---- -### Índice - - - - - - diff --git a/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud.md b/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud.md deleted file mode 100644 index 407296da6d..0000000000 --- a/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Conectar el servidor de GitHub Enterprise a GitHub Enterprise Cloud -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_enterprise %} 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 -permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} 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: '*' -topics: - - Enterprise - - GitHub Connect - - Infrastructure - - Networking ---- -### 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_enterprise %} y en tu cuenta de empresa u organización de {% data variables.product.prodname_ghe_cloud %}. - -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)." - -Después de habilitar {% data variables.product.prodname_github_connect %}, podrás habilitar características, como búsqueda unificada y contribuciones unificadas. Para obtener más información acerca de todas las características disponibles, consulta "[Administrar conexiones entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud)." - -Cuando conectas {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_ghe_cloud %}, un registro en {% data variables.product.prodname_dotcom_the_website %} almacena información sobre la conexión: -- 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 %} -- El nombre del host de {% data variables.product.product_location_enterprise %} -- La versión de {% data variables.product.product_location_enterprise %} -- La cuenta de empresa u organización en {% data variables.product.prodname_dotcom_the_website %} está conectada a {% data variables.product.product_location_enterprise %} -- El token de autenticación que usa {% data variables.product.product_location_enterprise %} 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.prodname_ghe_server %} usa las credenciales de {% data variables.product.prodname_github_app %} para hacerle solicitudes a {% data variables.product.prodname_dotcom_the_website %}. - -{% 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 - -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.prodname_ghe_server %}. - -{% if currentVersion ver_gt "enterprise-server@2.18" %} -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](/v4/guides/managing-enterprise-accounts)". -{% endif %} -### Habilitar {% data variables.product.prodname_github_connect %} - -1. Iniciar sesión en {% data variables.product.product_location_enterprise %} y {% data variables.product.prodname_dotcom_the_website %}. -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.github-connect-tab %} -5. En "{% data variables.product.prodname_dotcom_the_website %} aún no está habilitado", haz clic en **Enable {% data variables.product.prodname_github_connect %}** (Habilitar). Al hacer clic en **Enable {% data variables.product.prodname_github_connect %}** (Habilitar), aceptas el Anexo {% data variables.product.prodname_github_connect %} al Acuerdo de licencia {% data variables.product.prodname_enterprise %}. ![Habilitar el botón Conectar de GitHub](/assets/images/enterprise/business-accounts/enable-github-connect-button.png) -6. 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) - -### Desconectar una {% data variables.product.prodname_ghe_cloud %} organización o cuenta de empresa de {% data variables.product.product_location_enterprise %} - -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_enterprise %} se eliminan. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.github-connect-tab %} -5. 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 %}). ![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) -6. 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) diff --git a/translations/es-XL/content/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.md b/translations/es-XL/content/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.md deleted file mode 100644 index d05796852f..0000000000 --- a/translations/es-XL/content/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.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -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 -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: '*' -topics: - - Enterprise - - GitHub Connect - - Licensing ---- -### 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. Para obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/{{currentVersion}}/admin/installation/managing-your-github-enterprise-license)". - -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 "[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)." - -### 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 "[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)." - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.github-connect-tab %} -5. 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-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md b/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md deleted file mode 100644 index f7b1cba080..0000000000 --- a/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Habilitar aportes unificados entre el Servidor de GitHub Enterprise y GitHub.com -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.prodname_ghe_server %} 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 -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 unified contributions between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.' -versions: - ghes: '*' -topics: - - Enterprise - - GitHub Connect ---- -Como un administrador del sitio, puedes habilitar a los usuarios finales para que envíen sus recuentos de contribuciones de manera anónima por sus trabajos desde {% data variables.product.prodname_ghe_server %} a sus gráficos de contribuciones {% data variables.product.prodname_dotcom_the_website %}. - -Después de habilitar {% data variables.product.prodname_github_connect %} y habilitar {% data variables.product.prodname_unified_contributions %} en ambos entornos, los usuarios finales a tu instancia pueden conectarse a sus {% data variables.product.prodname_dotcom_the_website %} cuentas y enviar recuentos de contribuciones desde {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} Para obtener más información, consulta "[Enviar tus contribuciones {% data variables.product.prodname_ghe_server %} a tu perfil {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile/)." - -Si el administrador del sitio inhabilita la funcionalidad o la opción de los programadores de la conexión, los recuentos de contribuciones {% data variables.product.prodname_ghe_server %} se borrarán en {% 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.prodname_ghe_server %} **únicamente** envía el recuento de contribución y la fuente ({% data variables.product.prodname_ghe_server %}) de 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_enterprise %}, debes conectar {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_dotcom_the_website %}. 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)." - -{% data reusables.github-connect.access-dotcom-and-enterprise %} -{% data reusables.enterprise_site_admin_settings.access-settings %}{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.github-connect-tab %} -4. En "Los usuarios pueden compartir recuentos de contribuciones en {% data variables.product.prodname_dotcom_the_website %}", haz clic en **Request access (Solicita acceso)**. ![Solicitud para acceder a la opción de contribuciones unificadas](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png) -5. [Inicia sesión](https://enterprise.github.com/login) en el sitio {% data variables.product.prodname_ghe_server %} para recibir más instrucciones. - -Cuando solicitas acceso, te redireccionaremos al sitio {% data variables.product.prodname_ghe_server %} para comprobar tus términos de servicio actuales. Si {% data variables.product.product_location_enterprise %} utiliza los términos de servicio estándar, la solicitud automáticamente te redireccionará a las instrucciones para habilitar {% data variables.product.prodname_unified_contributions %}. Si estás utilizando los términos de servicio personalizados, registraremos tu solicitud y te contactaremos para configurar el acceso. diff --git a/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom.md b/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom.md deleted file mode 100644 index 5f3322d244..0000000000 --- a/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Habilitar la búsqueda unificada entre el Servidor de GitHub Enterprise y GitHub.com -intro: 'Después de habilitar {% data variables.product.prodname_github_connect %}, puedes permitir la búsqueda de {% data variables.product.prodname_dotcom_the_website %} desde {% data variables.product.product_location_enterprise %}.' -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 -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 unified search between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.' -versions: - ghes: '*' -topics: - - Enterprise - - GitHub Connect - - GitHub search ---- -Cuando habilitas la búsqueda unificada, los usuarios pueden ver los resultados de la búsqueda desde contenido público y privado en {% data variables.product.prodname_dotcom_the_website %} cuando buscan desde {% data variables.product.product_location_enterprise %}. - -Los usuarios no podrán buscar {% data variables.product.product_location_enterprise %} 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 %}. Para obtener más información, consulta "[Acerca de la búsqueda en {% data variables.product.prodname_dotcom %}](/articles/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" y "[Habilitar la búsqueda de repositorio privado {% data variables.product.prodname_dotcom_the_website %} en tu cuenta {% data variables.product.prodname_ghe_server %}](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)." - -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 %}. - -{% data reusables.github-connect.access-dotcom-and-enterprise %} -{% data reusables.enterprise_site_admin_settings.access-settings %}{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.github-connect-tab %} -5. 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) -6. 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 - -- "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)" diff --git a/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/index.md b/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/index.md deleted file mode 100644 index bc7bd1ec36..0000000000 --- a/translations/es-XL/content/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Administrar conexiones entre el servidor de GitHub Enterprise y GitHub Enterprise Cloud -intro: 'Con {% data variables.product.prodname_github_connect %}, puedes compartir determinadas características y datos entre {% data variables.product.product_location_enterprise %} 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 -versions: - ghes: '*' -topics: - - Enterprise -children: - - /connecting-github-enterprise-server-to-github-enterprise-cloud - - /enabling-unified-search-between-github-enterprise-server-and-githubcom - - /enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server - - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud ---- - diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/about-cluster-nodes.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/about-cluster-nodes.md deleted file mode 100644 index 3fd18bcaee..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/about-cluster-nodes.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Acerca de los nodos de agrupación -intro: 'Los "nodos" son instancias de {% data variables.product.prodname_ghe_server %} que operan en una agrupación. Cada nodo ejecuta un conjunto de servicios que se suministra a la agrupación y; por último, a los usuarios.' -redirect_from: - - /enterprise/admin/clustering/about-cluster-nodes - - /enterprise/admin/enterprise-management/about-cluster-nodes - - /admin/enterprise-management/about-cluster-nodes -versions: - ghes: '*' -topics: - - Clustering - - Enterprise ---- -{% data reusables.enterprise_clustering.clustering-requires-https %} - -### Recomendaciones mínimas de hardware -Cada nodo debe tener un volumen raíz, así como un volumen de datos separado. Estas son las recomendaciones mínimas. Es posible que se requieran más recursos según su uso, como la actividad del usuario y las integraciones seleccionadas. - -| Servicios | Mínimo de memoria requerida | Mínimo de espacio libre de volumen de datos requerido | -|:----------------------------------------------------------------------------------------------:|:---------------------------:|:-----------------------------------------------------:| -| `job-server`,
    `memcache-server`,
    `web-server` | 14 GB | 1 GB | -| `consul-server`,
    `mysql-server`,
    `redis-server` | 14 GB | 10 GB | -| `git-server`,
    `metrics-server`,
    `pages-server`,
    `storage-server` | 7 GB | 10 GB | -| `elasticsearch-server` | 14 GB | 10 GB | - -### Servicios requeridos para agrupamiento -Para una redundancia adecuada, usa estos nodos mínimos para poner en funcionamiento cada servicio. - -{% tip %} - -**Nota:** Las necesidades de escalabilidad de tu organización dependerán de muchos factores, entre los que se incluyen el tamaño y la cantidad de repositorios, la cantidad de usuarios y la utilización general. - -{% endtip %} - -| Servicios | Mínimo de nodos requeridos | -|:---------------------------------------------------------------------------------------------:|:--------------------------:| -| `job-server`,
    `memcache-server`,
    `metrics-server`,
    `web-server` | 2 | -| `mysql-server`,
    `redis-server` | 2 | -| `consul-server` | 3 | -| `git-server`,
    `pages-server`,
    `storage-server` | 3 | -| `elasticsearch-server` | 3 | - -### Recomendaciones de diseño de agrupación - -La agrupación permite que los servicios que constituyen {% data variables.product.prodname_ghe_server %} experimenten un aumento gradual independientemente de los demás. Esta flexibilidad puede usarse para diseñar e implementar una agrupación que se adapta a las organizaciones con diferentes requisitos de escalabilidad. Por ejemplo, es posible que algunas organizaciones necesiten una mayor capacidad de almacenamiento para extracciones frecuentes o de gran tamaño, pero el uso del servidor web puede ser relativamente bajo. Otra organización puede tener un buen rendimiento con menos recursos de almacenamiento, pero se necesitan más nodos que ejecuten `pages-server` or `elasticsearch-server`. Hay muchas combinaciones diferentes posibles. Trabaja con tu representante de cuenta para determinar la mejor configuración de agrupación para tus necesidades específicas. - -- Esparcir nodos redundantes por todo el hardware independiente. Si compartes su CPU, memoria o dispositivos de almacenamiento, reducirás el rendimiento e introducirás puntos de falla únicos. Los componentes de trabajo en red compartidos también pueden reducir la capacidad y aumentar el riesgo de pérdida de conectividad en caso de una interrupción. -- Uso de almacenamiento rápido. Por lo general, las redes del área de almacenamiento (SAN, por sus siglas en inglés) se optimizan para obtener una máxima utilización de espacio, disponibilidad y tolerancia a fallas, y no un rendimiento absoluto. La agrupación de {% data variables.product.prodname_ghe_server %} brinda redundancia y disponibilidad, y ofrecerá un mejor rendimiento en el almacenamiento más rápido disponible. Se recomienda el almacenamiento SSD local. -- Establecer niveles de nodos que tengan sentido para tu organización. Un ejemplo de configuración: - - Nivel de cara al usuario con dos nodos y los siguientes servicios: - - `web-server` - - `jobs-server` - - `memcache-server` - - Nivel de base de datos con tres nodos y los siguientes servicios: - - `consul-server` - - `mysql-server` - - `redis-server` - - Nivel de búsqueda con tres nodos y el siguiente servicio: - - `elasticsearch-server` - - Nivel de almacenamiento con tres nodos y los siguientes servicios: - - `git-server` - - `pages-server` - - `storage-server` - - `metrics-server` - -#### Ejemplo del diagrama de agrupación -{% note %} - -**Nota: Este es solo un ejemplo.** El diseño de agrupamiento óptimo de tu organización dependerá de tus necesidades exclusivas. Habla con tu representante dedicado o con {% data variables.contact.contact_enterprise_sales %} para que te podamos ayudar a determinar la mejor configuración del clúster. - -{% endnote %} - -Ejemplo de agrupamiento diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/about-clustering.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/about-clustering.md deleted file mode 100644 index 4cc802c199..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/about-clustering.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Acerca de las agrupaciones -intro: 'La agrupación {% data variables.product.prodname_ghe_server %} permite que los servicios que la componen {% data variables.product.prodname_ghe_server %} sean escalados a múltiples nodos.' -redirect_from: - - /enterprise/admin/clustering/overview - - /enterprise/admin/clustering/about-clustering - - /enterprise/admin/clustering/clustering-overview/ - - /enterprise/admin/enterprise-management/about-clustering - - /admin/enterprise-management/about-clustering -versions: - ghes: '*' -topics: - - Clustering - - Enterprise ---- -### Arquitectura de agrupación - -{% data variables.product.prodname_ghe_server %} está compuesto por un conjunto de servicios. En una agrupación, estos servicios se ejecutan en múltiples nodos y las solicitudes son un balanceador de carga entre ellos. Los cambios se almacenan automáticamente con copias redundantes en nodos separados. La mayoría de los servicios son pares iguales con otras instancias del mismo servicio. Las excepciones a esto son los servicios `mysql-server` and `redis-server`. Estos operan con un solo nodo _principal_ o más nodos _réplica_. - -Aprende más sobre los [servicios requeridos para los agrupamientos](/enterprise/{{ currentVersion }}/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering). - -### ¿Es adecuada la agrupación para mi organización? - -{% data reusables.enterprise_clustering.clustering-scalability %} Sin embargo, la configuración de un agrupación redundante y escalable puede ser compleja y requiere de una planificación cuidadosa. Se deberá planificar esta complejidad adicional para situaciones durante la instalación, situaciones de recuperación ante desastre y actualizaciones. - -{% data variables.product.prodname_ghe_server %} requiere una baja latencia entre los nodos y no está hecho para redundancia en todas las ubicaciones geográficas. - -La agrupación brinda redundancia, pero no pretende reemplazar una configuración de Alta disponibilidad. Para obtener más información, consulta [Configuración de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). Una configuración de conmutación primaria/secundaria es mucho más simple que la agrupación y permitirá satisfacer las necesidades de muchas organizaciones. Para obtener más información, consulta [Diferencias entre agrupación y alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/). - -### ¿Cómo obtengo acceso a la agrupación? - -La agrupación está diseñada para situaciones de escalada específica y no pretende ser usada para cada organización. Si te gustaría considerar la agrupación, por favor contacta a tu representante dedicado o a {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md deleted file mode 100644 index 9ffbe6f3fc..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Configuración de la red de agrupaciones -intro: 'La agrupación de {% data variables.product.prodname_ghe_server %} se basa en la resolución de nombre de DNS pertinente, balanceo de carga y comunicación entre los nodos para operar de manera adecuada.' -redirect_from: - - /enterprise/admin/clustering/cluster-network-configuration - - /enterprise/admin/enterprise-management/cluster-network-configuration - - /admin/enterprise-management/cluster-network-configuration -versions: - ghes: '*' -topics: - - Clustering - - Enterprise - - Infrastructure - - Networking ---- -### Consideraciones de red - -El diseño de red más simple para una agrupación es colocar los nodos en una LAN única. If a cluster must span subnets, we do not recommend configuring any firewall rules between the networks. The latency between nodes should be less than 1 millisecond. - -{% if currentVersion ver_gt "enterprise-server@2.21" %}For high availability, the latency between the network with the active nodes and the network with the passive nodes must be less than 70 milliseconds. We don't recommend configuring a firewall between the two networks.{% endif %} - -#### Puertos de la aplicación para usuarios finales - -Los puertos de la aplicación permiten que los usuarios finales accedan a Git y a la aplicación web. - -| Port (Puerto) | Descripción | Cifrado | -|:------------- |:------------------------------------------------------------------------- |:---------------------------------------------------------------------- | -| 22/TCP | Git sobre SSH | Sí | -| 25/TCP | SMTP | Requiere STARTTLS | -| 80/TCP | HTTP | No
    (Cuando SSL está habilitado, este puerto redirige a HTTPS) | -| 443/TCP | HTTPS | Sí | -| 9418/TCP | Puerto de protocolo de Git simple
    (Inhabilitado en modo privado) | No | - -#### Puertos administrativos - -No se requieren puertos administrativos para el uso de la aplicación básica por parte de los usuarios finales. - -| Port (Puerto) | Descripción | Cifrado | -|:------------- |:--------------------------- |:---------------------------------------------------------------------- | -| ICMP | Ping de ICMP | No | -| 122/TCP | SSH administrativo | Sí | -| 161/UDP | SNMP | No | -| 8080/TCP | Consola de gestión HTTP | No
    (Cuando SSL está habilitado, este puerto redirige a HTTPS) | -| 8443/TCP | Consola de gestión de HTTPS | Sí | - -#### Puertos de comunicación de agrupación - -Si un cortafuego de nivel de red se coloca entre los nodos estos puertos deberán estar accesibles. La comunicación entre los nodos no está cifrada. Estos puertos no deberían estar accesibles externamente. - -| Port (Puerto) | Descripción | -|:------------- |:------------------------------------- | -| 1336/TCP | API interna | -| 3033/TCP | Acceso SVN interno | -| 3037/TCP | Acceso SVN interno | -| 3306/TCP | MySQL | -| 4486/TCP | Acceso del gobernador | -| 5115/TCP | Respaldo de almacenamiento | -| 5208/TCP | Acceso SVN interno | -| 6379/TCP | Redis | -| 8001/TCP | Grafana | -| 8090/TCP | Acceso a GPG interno | -| 8149/TCP | Acceso al servidor de archivos GitRPC | -| 8300/TCP | Consul | -| 8301/TCP | Consul | -| 8302/TCP | Consul | -| 9000/TCP | Git Daemon | -| 9102/TCP | Servidor de archivos de páginas | -| 9105/TCP | Servidor LFS | -| 9200/TCP | ElasticSearch | -| 9203/TCP | Servicio de código semántico | -| 9300/TCP | ElasticSearch | -| 11211/TCP | Memcache | -| 161/UDP | SNMP | -| 8125/UDP | Statsd | -| 8301/UDP | Consul | -| 8302/UDP | Consul | -| 25827/UDP | Collectd | - - -### Configurar un balanceador de carga - - Recomendamos un balanceador de carga externo basado en TCP que respalde el protocolo PROXY para distribuir el tráfico a través de los nodos. Considera estas configuraciones del balanceador de carga: - - - Los puertos TCP (que se muestra a continuación) deberán ser reenviados a los nodos que ejecutan el servicio `web-server`. Estos son los únicos nodos que sirven a las solicitudes de clientes externos. - - Las sesiones pegajosas no deberían habilitarse. - -{% data reusables.enterprise_installation.terminating-tls %} - -### Manejar información de conexión de clientes - -Dado que las conexiones de clientes con el agrupamiento provienen del balanceador de carga, no se puede perder la dirección IP de cliente. Para capturar adecuadamente la información de la conexión de clientes, se requiere una consideración adicional. - -{% data reusables.enterprise_clustering.proxy_preference %} - -{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %} - -#### Habilitar el soporte PROXY en {% data variables.product.prodname_ghe_server %} - -Recomendamos firmemente habilitar el soporte PROXY para tu instancia y el balanceador de carga. - - - Para tu instancia, usa este comando: - ```shell - $ ghe-config 'loadbalancer.proxy-protocol' 'true' && ghe-cluster-config-apply - ``` - - Para el balanceador de carga, usa las instrucciones proporcionadas por tu proveedor. - - {% data reusables.enterprise_clustering.proxy_protocol_ports %} - -#### Habilitar el soporte X-Forwarded-For en {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_clustering.x-forwarded-for %} - -Para habilitar el encabezado `X-Fowarded-For`, usa este comando: - -```shell -$ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply -``` - -{% data reusables.enterprise_clustering.without_proxy_protocol_ports %} - -#### Configurar revisiones de estado -Las comprobaciones de estado permiten que un balanceador de carga deje de enviar tráfico a un nodo que no responde si una comprobación preconfigurada falla en ese nodo. Si un nodo de agrupación falla, las revisiones de estado emparejadas con nodos redundantes brindan alta disponibilidad. - -{% data reusables.enterprise_clustering.health_checks %} -{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} - -### Requisitos de DNS - -{% data reusables.enterprise_clustering.load_balancer_dns %} diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md deleted file mode 100644 index bfd800e85a..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md +++ /dev/null @@ -1,349 +0,0 @@ ---- -title: Configuring high availability replication for a cluster -intro: 'You can configure a passive replica of your entire {% data variables.product.prodname_ghe_server %} cluster in a different location, allowing your cluster to fail over to redundant nodes.' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster - - /admin/enterprise-management/configuring-high-availability-replication-for-a-cluster -versions: - ghes: '*' -topics: - - Clustering - - Enterprise - - High availability - - Infrastructure ---- -### About high availability replication for clusters - -You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests without data loss. - -In high availability mode, each active node syncs regularly with a corresponding passive node. The passive node runs in standby and does not serve applications or process user requests. - -We recommend configuring high availability as a part of a comprehensive disaster recovery plan for {% data variables.product.prodname_ghe_server %}. We also recommend performing regular backups. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/admin/configuration/configuring-backups-on-your-appliance)" - -### Prerrequisitos - -#### Hardware and software - -For each existing node in your active cluster, you'll need to provision a second virtual machine with identical hardware resources. For example, if your cluster has 11 nodes and each node has 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage, you must provision 11 new virtual machines that each have 12 vCPUs, 64 GB of RAM, and 750 GB of attached storage. - -On each new virtual machine, install the same version of {% data variables.product.prodname_ghe_server %} that runs on the nodes in your active cluster. You don't need to upload a license or perform any additional configuration. Para obtener más información, consulta "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)." - -{% note %} - -**Note**: The nodes that you intend to use for high availability replication should be standalone {% data variables.product.prodname_ghe_server %} instances. Don't initialize the passive nodes as a second cluster. - -{% endnote %} - -#### Red - -You must assign a static IP address to each new node that you provision, and you must configure a load balancer to accept connections and direct them to the nodes in your cluster's front-end tier. - -We don't recommend configuring a firewall between the network with your active cluster and the network with your passive cluster. The latency between the network with the active nodes and the network with the passive nodes must be less than 70 milliseconds. For more information about network connectivity between nodes in the passive cluster, see "[Cluster network configuration](/enterprise/admin/enterprise-management/cluster-network-configuration)." - -### Creating a high availability replica for a cluster - -- [Assigning active nodes to the primary datacenter](#assigning-active-nodes-to-the-primary-datacenter) -- [Adding passive nodes to the cluster configuration file](#adding-passive-nodes-to-the-cluster-configuration-file) -- [Example configuration](#example-configuration) - -#### Assigning active nodes to the primary datacenter - -Before you define a secondary datacenter for your passive nodes, ensure that you assign your active nodes to the primary datacenter. - -{% data reusables.enterprise_clustering.ssh-to-a-node %} - -{% data reusables.enterprise_clustering.open-configuration-file %} - -3. Note the name of your cluster's primary datacenter. The `[cluster]` section at the top of the cluster configuration file defines the primary datacenter's name, using the `primary-datacenter` key-value pair. By default, the primary datacenter for your cluster is named `default`. - - ```shell - [cluster] - mysql-master = HOSTNAME - redis-master = HOSTNAME - primary-datacenter = default - ``` - - - Optionally, change the name of the primary datacenter to something more descriptive or accurate by editing the value of `primary-datacenter`. - -4. {% data reusables.enterprise_clustering.configuration-file-heading %} Under each node's heading, add a new key-value pair to assign the node to a datacenter. Use the same value as `primary-datacenter` from step 3 above. For example, if you want to use the default name (`default`), add the following key-value pair to the section for each node. - - datacenter = default - - When you're done, the section for each node in the cluster configuration file should look like the following example. {% data reusables.enterprise_clustering.key-value-pair-order-irrelevant %} - - ```shell - [cluster "HOSTNAME"] - datacenter = default - hostname = HOSTNAME - ipv4 = IP ADDRESS - ... - ... - ``` - - {% note %} - - **Note**: If you changed the name of the primary datacenter in step 3, find the `consul-datacenter` key-value pair in the section for each node and change the value to the renamed primary datacenter. For example, if you named the primary datacenter `primary`, use the following key-value pair for each node. - - consul-datacenter = primary - - {% endnote %} - -{% data reusables.enterprise_clustering.apply-configuration %} - -{% data reusables.enterprise_clustering.configuration-finished %} - -After {% data variables.product.prodname_ghe_server %} returns you to the prompt, you've finished assigning your nodes to the cluster's primary datacenter. - -#### Adding passive nodes to the cluster configuration file - -To configure high availability, you must define a corresponding passive node for every active node in your cluster. The following instructions create a new cluster configuration that defines both active and passive nodes. You will: - -- Create a copy of the active cluster configuration file. -- Edit the copy to define passive nodes that correspond to the active nodes, adding the IP addresses of the new virtual machines that you provisioned. -- Merge the modified copy of the cluster configuration back into your active configuration. -- Apply the new configuration to start replication. - -For an example configuration, see "[Example configuration](#example-configuration)." - -1. For each node in your cluster, provision a matching virtual machine with identical specifications, running the same version of {% data variables.product.prodname_ghe_server %}. Note the IPv4 address and hostname for each new cluster node. For more information, see "[Prerequisites](#prerequisites)." - - {% note %} - - **Note**: If you're reconfiguring high availability after a failover, you can use the old nodes from the primary datacenter instead. - - {% endnote %} - -{% data reusables.enterprise_clustering.ssh-to-a-node %} - -3. Back up your existing cluster configuration. - - cp /data/user/common/cluster.conf ~/$(date +%Y-%m-%d)-cluster.conf.backup - -4. Create a copy of your existing cluster configuration file in a temporary location, like _/home/admin/cluster-passive.conf_. Delete unique key-value pairs for IP addresses (`ipv*`), UUIDs (`uuid`), and public keys for WireGuard (`wireguard-pubkey`). - - grep -Ev "(?:|ipv|uuid|vpn|wireguard\-pubkey)" /data/user/common/cluster.conf > ~/cluster-passive.conf - -5. Remove the `[cluster]` section from the temporary cluster configuration file that you copied in the previous step. - - git config -f ~/cluster-passive.conf --remove-section cluster - -6. Decide on a name for the secondary datacenter where you provisioned your passive nodes, then update the temporary cluster configuration file with the new datacenter name. Replace `SECONDARY` with the name you choose. - - ```shell - sed -i 's/datacenter = default/datacenter = SECONDARY/g' ~/cluster-passive.conf - ``` - -7. Decide on a pattern for the passive nodes' hostnames. - - {% warning %} - - **Warning**: Hostnames for passive nodes must be unique and differ from the hostname for the corresponding active node. - - {% endwarning %} - -8. Open the temporary cluster configuration file from step 3 in a text editor. For example, you can use Vim. - - ```shell - sudo vim ~/cluster-passive.conf - ``` - -9. In each section within the temporary cluster configuration file, update the node's configuration. {% data reusables.enterprise_clustering.configuration-file-heading %} - - - Change the quoted hostname in the section heading and the value for `hostname` within the section to the passive node's hostname, per the pattern you chose in step 7 above. - - Add a new key named `ipv4`, and set the value to the passive node's static IPv4 address. - - Add a new key-value pair, `replica = enabled`. - - ```shell - [cluster "NEW PASSIVE NODE HOSTNAME"] - ... - hostname = NEW PASSIVE NODE HOSTNAME - ipv4 = NEW PASSIVE NODE IPV4 ADDRESS - replica = enabled - ... - ... - ``` - -10. Append the contents of the temporary cluster configuration file that you created in step 4 to the active configuration file. - - ```shell - cat ~/cluster-passive.conf >> /data/user/common/cluster.conf - ``` - -11. Designate the primary MySQL and Redis nodes in the secondary datacenter. Replace `REPLICA MYSQL PRIMARY HOSTNAME` and `REPLICA REDIS PRIMARY HOSTNAME` with the hostnames of the passives node that you provisioned to match your existing MySQL and Redis primaries. - - ```shell - git config -f /data/user/common/cluster.conf cluster.mysql-master-replica REPLICA MYSQL PRIMARY HOSTNAME - git config -f /data/user/common/cluster.conf cluster.redis-master-replica REPLICA REDIS PRIMARY HOSTNAME - ``` - -12. Enable MySQL to fail over automatically when you fail over to the passive replica nodes. - - ```shell - git config -f /data/user/common/cluster.conf cluster.mysql-auto-failover true - ``` - - {% warning %} - - **Warning**: Review your cluster configuration file before proceeding. - - - In the top-level `[cluster]` section, ensure that the values for `mysql-master-replica` and `redis-master-replica` are the correct hostnames for the passive nodes in the secondary datacenter that will serve as the MySQL and Redis primaries after a failover. - - In each section for an active node named `[cluster "ACTIVE NODE HOSTNAME"]`, double-check the following key-value pairs. - - `datacenter` should match the value of `primary-datacenter` in the top-level `[cluster]` section. - - `consul-datacenter` should match the value of `datacenter`, which should be the same as the value for `primary-datacenter` in the top-level `[cluster]` section. - - Ensure that for each active node, the configuration has **one** corresponding section for **one** passive node with the same roles. In each section for a passive node, double-check each key-value pair. - - `datacenter` should match all other passive nodes. - - `consul-datacenter` should match all other passive nodes. - - `hostname` should match the hostname in the section heading. - - `ipv4` should match the node's unique, static IPv4 address. - - `replica` should be configured as `enabled`. - - Take the opportunity to remove sections for offline nodes that are no longer in use. - - To review an example configuration, see "[Example configuration](#example-configuration)." - - {% endwarning %} - -13. Initialize the new cluster configuration. {% data reusables.enterprise.use-a-multiplexer %} - - ```shell - ghe-cluster-config-init - ``` - -14. After the initialization finishes, {% data variables.product.prodname_ghe_server %} displays the following message. - - ```shell - Finished cluster initialization - ``` - -{% data reusables.enterprise_clustering.apply-configuration %} - -{% data reusables.enterprise_clustering.configuration-finished %} - -17. Configure a load balancer that will accept connections from users if you fail over to the passive nodes. For more information, see "[Cluster network configuration](/enterprise/admin/enterprise-management/cluster-network-configuration#configuring-a-load-balancer)." - -You've finished configuring high availability replication for the nodes in your cluster. Each active node begins replicating configuration and data to its corresponding passive node, and you can direct traffic to the load balancer for the secondary datacenter in the event of a failure. For more information about failing over, see "[Initiating a failover to your replica cluster](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)." - -#### Example configuration - -The top-level `[cluster]` configuration should look like the following example. - -```shell -[cluster] - mysql-master = HOSTNAME OF ACTIVE MYSQL MASTER - redis-master = HOSTNAME OF ACTIVE REDIS MASTER - primary-datacenter = PRIMARY DATACENTER NAME - mysql-master-replica = HOSTNAME OF PASSIVE MYSQL MASTER - redis-master-replica = HOSTNAME OF PASSIVE REDIS MASTER - mysql-auto-failover = true -... -``` - -The configuration for an active node in your cluster's storage tier should look like the following example. - -```shell -... -[cluster "UNIQUE ACTIVE NODE HOSTNAME"] - datacenter = default - hostname = UNIQUE ACTIVE NODE HOSTNAME - ipv4 = IPV4 ADDRESS - consul-datacenter = default - consul-server = true - git-server = true - pages-server = true - mysql-server = true - elasticsearch-server = true - redis-server = true - memcache-server = true - metrics-server = true - storage-server = true - vpn = IPV4 ADDRESS SET AUTOMATICALLY - uuid = UUID SET AUTOMATICALLY - wireguard-pubkey = PUBLIC KEY SET AUTOMATICALLY -... -``` - -The configuration for the corresponding passive node in the storage tier should look like the following example. - -- Important differences from the corresponding active node are **bold**. -- {% data variables.product.prodname_ghe_server %} assigns values for `vpn`, `uuid`, and `wireguard-pubkey` automatically, so you shouldn't define the values for passive nodes that you will initialize. -- The server roles, defined by `*-server` keys, match the corresponding active node. - -```shell -... -[cluster "UNIQUE PASSIVE NODE HOSTNAME"] - replica = enabled - ipv4 = IPV4 ADDRESS OF NEW VM WITH IDENTICAL RESOURCES - datacenter = SECONDARY DATACENTER NAME - hostname = UNIQUE PASSIVE NODE HOSTNAME - consul-datacenter = SECONDARY DATACENTER NAME - consul-server = true - git-server = true - pages-server = true - mysql-server = true - elasticsearch-server = true - redis-server = true - memcache-server = true - metrics-server = true - storage-server = true - vpn = DO NOT DEFINE - uuid = DO NOT DEFINE - wireguard-pubkey = DO NOT DEFINE -... -``` - -### Monitoring replication between active and passive cluster nodes - -Initial replication between the active and passive nodes in your cluster takes time. The amount of time depends on the amount of data to replicate and the activity levels for {% data variables.product.prodname_ghe_server %}. - -You can monitor the progress on any node in the cluster, using command-line tools available via the {% data variables.product.prodname_ghe_server %} administrative shell. For more information about the administrative shell, see "[Accessing the administrative shell (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)." - -- Monitor replication of databases: - - /usr/local/share/enterprise/ghe-cluster-status-mysql - -- Monitor replication of repository and Gist data: - - estado ghe-spokes - -- Monitor replication of attachment and LFS data: - - ghe-storage replication-status - -- Monitor replication of Pages data: - - ghe-dpages replication-status - -You can use `ghe-cluster-status` to review the overall health of your cluster. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-cluster-status)." - -### Reconfiguring high availability replication after a failover - -After you fail over from the cluster's active nodes to the cluster's passive nodes, you can reconfigure high availability replication in two ways. - -#### Provisioning and configuring new passive nodes - -After a failover, you can reconfigure high availability in two ways. The method you choose will depend on the reason that you failed over, and the state of the original active nodes. - -1. Provision and configure a new set of passive nodes for each of the new active nodes in your secondary datacenter. - -2. Use the old active nodes as the new passive nodes. - -The process for reconfiguring high availability is identical to the initial configuration of high availability. For more information, see "[Creating a high availability replica for a cluster](#creating-a-high-availability-replica-for-a-cluster)." - - -### Disabling high availability replication for a cluster - -You can stop replication to the passive nodes for your cluster deployment of {% data variables.product.prodname_ghe_server %}. - -{% data reusables.enterprise_clustering.ssh-to-a-node %} - -{% data reusables.enterprise_clustering.open-configuration-file %} - -3. In the top-level `[cluster]` section, delete the `mysql-auto-failover`, `redis-master-replica`, and `mysql-master-replica` key-value pairs. - -4. Delete each section for a passive node. For passive nodes, `replica` is configured as `enabled`. - -{% data reusables.enterprise_clustering.apply-configuration %} - -{% data reusables.enterprise_clustering.configuration-finished %} - -After {% data variables.product.prodname_ghe_server %} returns you to the prompt, you've finished disabling high availability replication. diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md deleted file mode 100644 index 57afd4044c..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Diferencias entre los agrupamientos y la disponibilidad alta (HA) -intro: '{% data variables.product.prodname_ghe_server %} La configuración de alta disponibilidad es una configuración de conmutación primaria/secundaria que brinda redundancia mientras que el agrupamiento brinda redundancia y escalabilidad al distribuir cargas de lectura y escritura entre múltiples nodos.' -redirect_from: - - /enterprise/admin/clustering/differences-between-clustering-and-high-availability-ha - - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha - - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha -versions: - ghes: '*' -topics: - - Clustering - - Enterprise - - High availability - - Infrastructure ---- -### Escenarios de fallas - -Tanto la alta disponibilidad (HA, por sus siglas en inglés) como el agrupamiento brindan redundancia al eliminar el nodo único como punto de falla. Pueden brindar disponibilidad en estos escenarios: - -{% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %} - -### Escalabilidad - -{% data reusables.enterprise_clustering.clustering-scalability %} En HA, la escala de este aparato depende exclusivamente del nodo principal y la cara no se distribuye al servidor de réplica. - -### Diferencias en el método de conmutación y configuración - -| Característica | Configuración de conmutación | Método de conmutación | -|:------------------------------------ |:--------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------- | -| Configuración de alta disponibilidad | Registro de DNS con un TTL bajo que apunta al aparato principal o balanceador de carga. | Debes impulsar manualmente el aparato de réplica en las configuraciones de conmutación DNS y balanceador de carga. | -| Agrupación | El registro DNS debe apuntar a un balanceador de carga. | Si falla un nodo detrás de un balanceador de carga, el tráfico se envía automáticamente a los otros nodos de funcionamiento. | - -### Copias de seguridad y recuperación ante desastres - -HA y Clustering no deben ser considerados como un reemplazo para copias de seguridad regulares. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)" - -### Supervisar - -Las características de disponibilidad, especialmente las que tienen conmutación automática como Agrupación, pueden enmascarar una falla dado que el servicio generalmente no se ve interrumpido cuando algo falla. Ya sea que esté usando HA o Agrupación, supervisar el estado de cada instancia es importante para que puedas estar al tanto cuando se produce una falla. Para obtener más información sobre la supervisión, consulta " -[Umbrales de alerta recomendados](/enterprise/{{ currentVersion }}/admin/guides/installation/recommended-alert-thresholds/)" y [Supervisar nodos de agrupación](/enterprise/{{ currentVersion}}/admin/guides/clustering/monitoring-cluster-nodes/)".

    - - - -### Leer más - -- Para obtener más información acerca del {% data variables.product.prodname_ghe_server %} Agrupamiento, visite la sección de "[Acerca del agrupamiento](/enterprise/{{ currentVersion}}/admin/guides/clustering/about-clustering/)." -- Para obtener más información sobre HA, consulta "[Configurar {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)". diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md deleted file mode 100644 index a9fa830805..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Evacuar un nodo de agrupación -intro: Puedes evacuar los servicios de datos en un nodo de agrupación. -redirect_from: - - /enterprise/admin/clustering/evacuating-a-cluster-node - - /enterprise/admin/enterprise-management/evacuating-a-cluster-node - - /admin/enterprise-management/evacuating-a-cluster-node -versions: - ghes: '*' -topics: - - Clustering - - Enterprise ---- -Si solo tienes tres nodos en tu agrupación de servicios de datos, no puedes evacuar los nodos, porque `ghe-spokes` no tiene otro lugar para realizar una copia. Si tienes cuatro o más, `ghe-spokes` moverá todos los repositorios del nodo evacuado. - -Si colocas fuera de línea un nodo que tiene otros servicios de datos (como git, páginas o almacenamiento), debes evacuar cada nodo antes de ponerlo fuera de línea. - -1. Encuentra la `uuid` del nodo con el comando `ghe-config`. - - ``` - $ ghe-config cluster._hostname_.uuid - ``` - -2. Deberás supervisar el estado de tu nodo mientras se copian los datos. Idealmente, el nodo no debería estar fuera de línea hasta que se complete la copia. Para supervisar el estado de tu nodo, ejecuta alguno de los siguientes comandos: - - Para Git - ``` - ghe-spokes evac-status - ``` - Para {% data variables.product.prodname_pages %} - ``` - echo "select count(*) from pages_replicas where host = 'pages-server-'" | ghe-dbconsole -y - ``` - Para almacenamiento - ``` - ghe-storage evacuation-status - ``` - -3. Una vez que la copia esté completa, puedes evacuar el servicio de almacenamiento. Ejecuta alguno de los siguientes comandos: - - Para Git - ``` - ghe-spokes server evacuate git-server- - ``` - Para {% data variables.product.prodname_pages %} - ``` - ghe-dpages evacuate pages-server- - ``` - Para almacenamiento, coloca el nodo fuera de línea - ``` - ghe-storage offline storage-server- - ``` - luego evacúa - ``` - ghe-storage evacuate storage-server- - ``` diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/index.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/index.md deleted file mode 100644 index 0e4f5f8d2a..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/index.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Configurar el agrupamiento -intro: Aprende sobre agrupaciones y diferencias con alta disponibilidad. -redirect_from: - - /enterprise/admin/clustering/setting-up-the-cluster-instances - - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster - - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster/ - - /enterprise/admin/enterprise-management/configuring-clustering -versions: - ghes: '*' -topics: - - Enterprise -children: - - /about-clustering - - /differences-between-clustering-and-high-availability-ha - - /about-cluster-nodes - - /cluster-network-configuration - - /initializing-the-cluster - - /upgrading-a-cluster - - /monitoring-cluster-nodes - - /replacing-a-cluster-node - - /evacuating-a-cluster-node - - /configuring-high-availability-replication-for-a-cluster - - /initiating-a-failover-to-your-replica-cluster ---- - diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md deleted file mode 100644 index 845d721e15..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: Inicializar la agrupación -intro: 'Una agrupación de {% data variables.product.prodname_ghe_server %} se debe configurar con una licencia y se debe inicializar mediante un shell administrativo (SSH).' -redirect_from: - - /enterprise/admin/clustering/initializing-the-cluster - - /enterprise/admin/enterprise-management/initializing-the-cluster - - /admin/enterprise-management/initializing-the-cluster -versions: - ghes: '*' -topics: - - Clustering - - Enterprise ---- -{% data reusables.enterprise_clustering.clustering-requires-https %} - -### Instalar {% data variables.product.prodname_ghe_server %} - -1. En cada nodo de agrupación, suministra e instala {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Configurar una instancia {% data variables.product.prodname_ghe_server %} ](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." -2. Mediante el shell administrativo o DHCP, configura **solo** la dirección IP de cada nodo. No configures los otros parámetros. - -### Configurar el primer nodo - -1. Realiza una conexión con el nodo que será designado como `mysqu.-master` en `clussster.conf`. Para obtener más información, consulta "[Acerca del archivo de configuración de agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)." -2. En tu navegador web, visita `https://:8443/setup/`. -{% data reusables.enterprise_installation.upload-a-license-file %} -{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} -{% data reusables.enterprise_installation.instance-will-restart-automatically %} - -### Inicializar la agrupación - -Para inicializar la agrupación, necesitas un archivo de configuración de agrupación (`cluster.conf`). Para obtener más información, consulta "[Acerca del archivo de configuración de agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)". - -1. Desde el primer nodo que se configuró, ejecuta `ghe-cluster-config. init`. De esta manera, se inicializará la agrupación si existen nodos en el archivo de configuración de la agrupación que no están configurados. -2. Ejecuta `ghe-cluster-config-apply`. Esto validará el archivo `cluster.conf`, aplicará la configuración a cada archivo del nodo y traerá los servicios configurados en cada nodo. - -Para comprobar el estado de una agrupación en funcionamiento, usa el comando `ghe-cluster-status`. - -### Acerca del archivo de configuración de la agrupación - -El archivo de configuración de la agrupación (`cluster.conf`) define los nodos en la agrupación, y los servicios que ejecutan. Para obtener más información, consulta "[Acerca de los nodos de agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-cluster-nodes)". - -Este ejemplo `cluster.conf` define una agrupación con cinco nodos. - - - Dos nodos (llamados `ghe-app-node-\*`) ejecutan los servicios `web-server` y `job-server` responsables de atender las solicitudes de los clientes. - - Tres nodos (llamados `ghe-data-node-\*`) ejecutan los servicios responsables del almacenamiento y la recuperación de los datos de {% data variables.product.prodname_ghe_server %}. - -Los nombres de los nodos pueden ser cualquier nombre de host válido que elijas. Los nombres son conjuntos de nombres de host de cada nodo y también se agregarán a `/etc/hosts` en cada nodo, de manera que los nodos puedan ser resolubles localmente entre sí. - -Especifica el primer nodo de agrupación que configuraste como MySQL principal mediante `mysql-server` y `mysql-master`. - -``` -[cluster] - mysql-master = ghe-data-node-1 - redis-master = ghe-data-node-1 - primary-datacenter = default -[cluster "ghe-app-node-1"] - hostname = ghe-app-node-1 - ipv4 = 192.168.0.2 - # ipv6 = fd12:3456:789a:1::2 - web-server = true - job-server = true -[cluster "ghe-app-node-2"] - hostname = ghe-app-node-2 - ipv4 = 192.168.0.3 - # ipv6 = fd12:3456:789a:1::3 - web-server = true - job-server = true -[cluster "ghe-data-node-1"] - hostname = ghe-data-node-1 - ipv4 = 192.168.0.4 - # ipv6 = fd12:3456:789a:1::4 - consul-server = true - consul-datacenter = default - git-server = true - pages-server = true - mysql-server = true - elasticsearch-server = true - redis-server = true - memcache-server = true - metrics-server = true - storage-server = true -[cluster "ghe-data-node-2"] - hostname = ghe-data-node-2 - ipv4 = 192.168.0.5 - # ipv6 = fd12:3456:789a:1::5 - consul-server = true - consul-datacenter = default - git-server = true - pages-server = true - mysql-server = true - elasticsearch-server = true - redis-server = true - memcache-server = true - metrics-server = true - storage-server = true -[cluster "ghe-data-node-3"] - hostname = ghe-data-node-3 - ipv4 = 192.168.0.6 - # ipv6 = fd12:3456:789a:1::6 - consul-server = true - consul-datacenter = default - git-server = true - pages-server = true - mysql-server = true - elasticsearch-server = true - redis-server = true - memcache-server = true - metrics-server = true - storage-server = true -``` - -Crea el archivo `/data/user/common/cluster.conf` en el primer nodo configurado. Por ejemplo, usando `vim`: - - ```shell - ghe-data-node-1:~$ sudo vim /data/user/common/cluster.conf - ``` diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/initiating-a-failover-to-your-replica-cluster.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/initiating-a-failover-to-your-replica-cluster.md deleted file mode 100644 index c4ee7c9c84..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/initiating-a-failover-to-your-replica-cluster.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Initiating a failover to your replica cluster -intro: 'If your {% data variables.product.prodname_ghe_server %} cluster fails, you can fail over to the passive replica .' -redirect_from: - - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster - - /admin/enterprise-management/initiating-a-failover-to-your-replica-cluster -versions: - ghes: '*' -topics: - - Clustering - - Enterprise - - High availability - - Infrastructure ---- -### About failover to your replica cluster - -In the event of a failure at your primary datacenter, you can fail over to the replica nodes in the secondary datacenter if you configure a passive replica node for each node in your active cluster. - -The time required to fail over depends on how long it takes to manually promote the replica cluster and redirect traffic. - -Promoting a replica cluster does not automatically set up replication for the existing cluster. After promoting a replica cluster, you can reconfigure replication from the new active cluster. For more information, see "[Configuring high availability for a cluster](/enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster#reconfiguring-high-availability-replication-after-a-failover)." - -### Prerrequisitos - -To fail over to passive replica nodes, you must have configured high availability for your cluster. For more information, see "[Configuring high availability for a cluster](/enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster)." - -### Initiating a failover to your replica cluster - -1. SSH into any passive node in the secondary datacenter for your cluster. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)." - -2. Initialize the failover to the secondary cluster and configure it to act as the active nodes. - - ```shell - ghe-cluster-failover - ``` - -{% data reusables.enterprise_clustering.configuration-finished %} - -3. Update the DNS record to point to the IP address of the load balancer for your passive cluster. El tráfico es direccionado a la réplica después de que transcurra el período TTL. - -After {% data variables.product.prodname_ghe_server %} returns you to the prompt and your DNS updates have propagated, you've finished failing over. Users can access {% data variables.product.prodname_ghe_server %} using the usual hostname for your cluster. diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md deleted file mode 100644 index 79ffeef67b..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -title: Monitoring cluster nodes -intro: 'A {% data variables.product.prodname_ghe_server %} cluster is comprised of redundant services that are distributed across two or more nodes. If an individual service or an entire node were to fail, it should not be immediately apparent to users of the cluster. However since performance and redundancy are affected, it is important to monitor the health of a {% data variables.product.prodname_ghe_server %} cluster.' -redirect_from: - - /enterprise/admin/clustering/monitoring-cluster-nodes - - /enterprise/admin/enterprise-management/monitoring-cluster-nodes - - /admin/enterprise-management/monitoring-cluster-nodes -versions: - ghes: '*' -topics: - - Clustering - - Enterprise - - Fundamentals - - Infrastructure - - Monitoring - - Performance ---- -### Manually checking cluster status - -{% data variables.product.prodname_ghe_server %} has a built-in command line utility for monitoring the health of the cluster. From the administrative shell, running the `ghe-cluster-status` command executes a series of health checks on each node including verification of connectivity and service status. The output shows all test results including the text `ok` or `error`. For example, to only display failing tests, run: - -```shell -admin@ghe-data-node-0:~$ ghe-cluster-status | grep error -> mysql-replication ghe-data-node-0: error Stopped -> mysql cluster: error -``` -{% note %} - -**Note:** If there are no failing tests, this command produces no output. This indicates the cluster is healthy. - -{% endnote %} - -### Monitoring cluster status with Nagios - -You can configure [Nagios](https://www.nagios.org/) to monitor {% data variables.product.prodname_ghe_server %}. In addition to monitoring basic connectivity to each of the cluster nodes, you can check the cluster status by configuring Nagios to use the `ghe-cluster-status -n` command. This returns output in a format that Nagios understands. - -#### Prerequisites -* Linux host running Nagios. -* Network access to the {% data variables.product.prodname_ghe_server %} cluster. - -#### Configuring the Nagios host -1. Generate an SSH key with a blank passphrase. Nagios uses this to authenticate to the {% data variables.product.prodname_ghe_server %} cluster. - ```shell - nagiosuser@nagios:~$ ssh-keygen -t rsa -b 4096 - > Generating public/private rsa key pair. - > Enter file in which to save the key (/home/nagiosuser/.ssh/id_rsa): - > Enter passphrase (empty for no passphrase): leave blank by pressing enter - > Enter same passphrase again: press enter again - > Your identification has been saved in /home/nagiosuser/.ssh/id_rsa. - > Your public key has been saved in /home/nagiosuser/.ssh/id_rsa.pub. - ``` - {% danger %} - - **Security Warning:** An SSH key without a passphrase can pose a security risk if authorized for full access to a host. Limit this key's authorization to a single read-only command. - - {% enddanger %} -2. Copy the private key (`id_rsa`) to the `nagios` home folder and set the appropriate ownership. - ```shell - nagiosuser@nagios:~$ sudo cp .ssh/id_rsa /var/lib/nagios/.ssh/ - nagiosuser@nagios:~$ sudo chown nagios:nagios /var/lib/nagios/.ssh/id_rsa - ``` - -3. To authorize the public key to run *only* the `ghe-cluster-status -n` command, use a `command=` prefix in the `/data/user/common/authorized_keys` file. From the administrative shell on any node, modify this file to add the public key generated in step 1. For example: `command="/usr/local/bin/ghe-cluster-status -n" ssh-rsa AAAA....` - -4. Validate and copy the configuration to each node in the cluster by running `ghe-cluster-config-apply` on the node where you modified the `/data/user/common/authorized_keys` file. - - ```shell - admin@ghe-data-node-0:~$ ghe-cluster-config-apply - > Validating configuration - > ... - > Finished cluster configuration - ``` - -5. To test that the Nagios plugin can successfully execute the command, run it interactively from Nagios host. - ```shell - nagiosuser@nagios:~$ /usr/lib/nagios/plugins/check_by_ssh -l admin -p 122 -H hostname -C "ghe-cluster-status -n" -t 30 - > OK - No errors detected - ``` - -6. Create a command definition in your Nagios configuration. - ###### Example definition - - ``` - define command { - command_name check_ssh_ghe_cluster - command_line $USER1$/check_by_ssh -H $HOSTADDRESS$ -C "ghe-cluster-status -n" -l admin -p 122 -t 30 - } - ``` -7. Add this command to a service definition for a node in the {% data variables.product.prodname_ghe_server %} cluster. - - ###### Example definition - - ``` - define host{ - use generic-host - host_name ghe-data-node-0 - alias ghe-data-node-0 - address 10.11.17.180 - } - - define service{ - use generic-service - host_name ghe-data-node-0 - service_description GitHub Cluster Status - check_command check_ssh_ghe_cluster - } - ``` - -Once you add the definition to Nagios, the service check executes according to your configuration. You should be able to see the newly configured service in the Nagios web interface. - -![Nagios Example](/assets/images/enterprise/cluster/nagios-example.png) diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/replacing-a-cluster-node.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/replacing-a-cluster-node.md deleted file mode 100644 index a438bdf5fd..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/replacing-a-cluster-node.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Reemplazar un nodo de agrupación -intro: 'Para reemplazar un nodo {% data variables.product.prodname_ghe_server %}, debes marcar los nodos fuera de línea afectados en el archivo de configuración de la agrupación (`cluster.conf`) y agregar los nodos de reemplazo. Esto puede ser necesario en caso de que un nodo falle, o para agregar un nodo con más recursos a fin de aumentar el rendimiento.' -redirect_from: - - /enterprise/admin/clustering/replacing-a-cluster-node - - /enterprise/admin/enterprise-management/replacing-a-cluster-node - - /admin/enterprise-management/replacing-a-cluster-node -versions: - ghes: '*' -topics: - - Clustering - - Enterprise - - Infrastructure ---- -{% warning %} - -**Advertencia** El nodo de reemplazo debe usar un nodo de nombre de host que no haya sido usado anteriormente en la agrupación para evitar conflictos. - -{% endwarning %} - -### Reemplazar un nodo funcional -{% data reusables.enterprise_clustering.replacing-a-cluster-node-provision %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-admin-configure-ip %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-modify-cluster-conf %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-initialize-new-node %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-config-node %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-need-three-nodes %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-mark-offline %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-validate-config %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-replacement-name %} - -### Reemplazar un nodo en una emergencia -{% data reusables.enterprise_clustering.replacing-a-cluster-node-provision %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-admin-configure-ip %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-mark-offline %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-validate-config %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-modify-cluster-conf %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-replacement-name %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-initialize-new-node %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-config-node %} -{% data reusables.enterprise_clustering.replacing-a-cluster-node-need-three-nodes %} diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md b/translations/es-XL/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md deleted file mode 100644 index 5ce7a6df5f..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Actualizar una agrupación -intro: 'Usa el shell administrativo (SSH) para actualizar una agrupación de {% data variables.product.prodname_ghe_server %} a la última versión.' -redirect_from: - - /enterprise/admin/clustering/upgrading-a-cluster - - /enterprise/admin/enterprise-management/upgrading-a-cluster - - /admin/enterprise-management/upgrading-a-cluster -versions: - ghes: '*' -topics: - - Clustering - - Enterprise - - Upgrades ---- -### Actualizar con un hotpatch -{% data reusables.enterprise_installation.hotpatching-explanation %}El script de instalación de hotpatch instala el hotpatch en cada nodo de la agrupación y reinicia los servicios en su secuencia adecuada para evitar el tiempo de inactividad. - -1. Realiza una copia de seguridad de tus datos con [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). -2. Desde el shell administrativo de cualquier nodo, usa el comando ` ghe-cluster-hotpatch` para instalar el último hotpatch. Puedes proporcionar una URL para un hotpatch, o descargar manualmente el hotpatch y especificar un nombre de archivo local. - ```shell - $ ghe-cluster-hotpatch https://HOTPATCH-URL/FILENAME.hpkg - ``` - -### Actualizar con un paquete de actualización -Usa un paquete de actualización para actualizar una agrupación de {% data variables.product.prodname_ghe_server %} a la última característica de lanzamiento. Por ejemplo, puedes actualizar desde `2.11` hasta `2.13`. - -#### Preparar para una actualización - -1. Revisa la [Configuración de red de la agrupación](/enterprise/admin/guides/clustering/cluster-network-configuration) para la versión a la que deseas avanzar y realiza las actualizaciones conforme sea necesario. -2. Realiza una copia de seguridad de tus datos con [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). -3. Planifica una ventana de mantenimiento para los usuarios finales de tu agrupación de {% data variables.product.prodname_ghe_server %}, dado que no estará disponible para usar normalmente durante la actualización. El modo de mantenimiento bloquea el acceso de los usuarios e impide que se realicen cambios en los datos mientras la actualización de la agrupación está en curso. -4. En [{% data variables.product.prodname_ghe_server %} Descargar página](https://enterprise.github.com/download), copia la URL para el archivo de actualización *.pkg* en el portapapeles. -5. Desde el shell administrativo de cualquier nodo, usa el comando `ghe-cluster-each` combinado con `curl` para descargar el paquete de lanzamiento para cada nodo en un solo paso. Usa la URL que copiaste en el paso anterior como argumento. - ```shell - $ ghe-cluster-each -- "cd /home/admin && curl -L -O https://PACKAGE-URL.pkg" - > ghe-app-node-1: % Total % Received % Xferd Average Speed Time Time Time Current - > ghe-app-node-1: Dload Upload Total Spent Left Speed - > 100 496M 100 496M 0 0 24.2M 0 0:00:20 0:00:20 --:--:-- 27.4M - > ghe-data-node-2: % Total % Received % Xferd Average Speed Time Time Time Current - > ghe-data-node-2: Dload Upload Total Spent Left Speed - > 100 496M 100 496M 0 0 21.3M 0 0:00:23 0:00:23 --:--:-- 25.8M - > ghe-data-node-1: % Total % Received % Xferd Average Speed Time Time Time Current - > ghe-data-node-1: Dload Upload Total Spent Left Speed - > 100 496M 100 496M 0 0 19.7M 0 0:00:25 0:00:25 --:--:-- 25.6M - > ghe-app-node-2: % Total % Received % Xferd Average Speed Time Time Time Current - > ghe-app-node-2: Dload Upload Total Spent Left Speed - > 100 496M 100 496M 0 0 19.8M 0 0:00:25 0:00:25 --:--:-- 17.6M - > ghe-data-node-3: % Total % Received % Xferd Average Speed Time Time Time Current - > ghe-data-node-3: Dload Upload Total Spent Left Speed - > 100 496M 100 496M 0 0 19.7M 0 0:00:25 0:00:25 --:--:-- 25.5M - ``` -6. Identifica el nodo MySQL principal, que se definió como `mysql-master = ` en `cluster.conf`. Este será el último nodo que se actualizará. - -#### Actualizar los nodos de la agrupación - -1. Habilita el modo de mantenimiento de acuerdo con tu ventana planificada conectando el shell administrativo de cualquier nodo de agrupación y ejecutando `ghe-cluster-maintenance -s`. -2. **Con la excepción del nodo primario de MySQL**, conéctate al shell administrativo de cada uno de los nodos de {% data variables.product.prodname_ghe_server %}. Ejecuta el comando `ghe-upgrade`, suministrando el nombre del archivo del paquete que descargaste en el Paso 4 de [Preparar una actualización](#preparing-to-upgrade): - ```shell - $ ghe-upgrade PACKAGE-FILENAME.pkg - > *** verifying upgrade package signature... - > 497MB 0:00:04 [ 117MB/s] [==========================================>] 100% - > gpg: Signature made Fri 19 Feb 2016 02:33:50 PM UTC using RSA key ID 0D65D57A - > gpg: checking the trustdb - > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model - > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u - > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > " - ``` -3. El proceso de actualización reiniciará el nodo MySQL principal una vez que esté completo. Verifica que puedes `hacer ping` en cada nodo luego del reinicio. -4. Conecta con el shell administrativo del nodo MySQL principal. Ejecuta el comando `ghe-upgrade`, suministrando el nombre del archivo del paquete que descargaste en el Paso 4 de [Preparar una actualización](#preparing-to-upgrade): - ```shell - $ ghe-upgrade PACKAGE-FILENAME.pkg - > *** verifying upgrade package signature... - > 497MB 0:00:04 [ 117MB/s] [==========================================>] 100% - > gpg: Signature made Fri 19 Feb 2016 02:33:50 PM UTC using RSA key ID 0D65D57A - > gpg: checking the trustdb - > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model - > 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. Verifica que puedes `hacer ping` en cada nodo luego del reinicio. -6. Cierra el modo de mantenimiento desde el shell administativo de cualquier nodo al ejecutar `ghe-cluster-maintenance -u`. diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md deleted file mode 100644 index d787cb4c77..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Acerca de la Replicación geográfica -intro: 'La Replicación geográfica en {% data variables.product.prodname_ghe_server %} utiliza múltiples réplicas activas para responder las solicitudes de los centros de datos distribuidos geográficamente.' -redirect_from: - - /enterprise/admin/installation/about-geo-replication - - /enterprise/admin/enterprise-management/about-geo-replication - - /admin/enterprise-management/about-geo-replication -versions: - ghes: '*' -topics: - - Enterprise - - High availability ---- -Contar con múltiples réplicas puede permitir una menor distancia a la réplica más cercana. Por ejemplo, una organización con oficinas en San Francisco, Nueva York y Londres podrían ejecutar el aparato principal en un centro de datos cercano a Nueva York y dos réplicas en centros de datos cercanos a San Francisco y Londres. Al usar DNS con información de geolocalización, se puede dirigir a los usuarios al servidor disponible más cercano para que accedan a los datos más rápido. Designar como principal el aparato cercano a Nueva York ayuda a reducir la latencia entre los hosts, a diferencia de si se designa como principal el aparato cercano a San Francisco, que tiene mayor latencia con Londres. - -Los proxies de la réplica activa solicitan que no se pueda procesar esta misma para la instancia principal. Las réplicas funcionan como un punto de presencia al terminar todas las conexiones SSL. El tráfico entre los servidores se envía a través de una conexión VPN encriptada, similar a una configuración de dos nodos de alta disponibilidad sin replicación geográfica. - -Las solicitudes de Git y las solicitudes del servidor de archivo, como LFS y las cargas de archivos, se pueden atender directamente desde la réplica sin cargar ningún dato desde el principal. Las solicitudes web siempre se enrutan hacia el principal, pero si la réplica está más cerca del usuario, las solicitudes son más rápidas porque la terminación SSL está más cerca. - -Se solicita un DNS geográfico, como [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo), para que la replicación geográfica funcione sin problemas. El nombre del host para la instancia se debe resolver con la réplica más cercana a la ubicación del usuario. - -### Limitaciones - -Escribir solicitudes para la réplica exige que se envíen los datos al principal y a todas las réplicas. Esto significa que el rendimiento de todas las escrituras está limitado por la réplica más lenta {% if currentVersion ver_gt "enterprise-server@2.17" %}, aunque las nuevas réplicas geográficas pueden poblar la mayoría de sus datos de las réplicas geográficas ubicadas en el mismo lugar, en lugar del primario{% endif %}. La replicación geográfica no le agregará capacidad a una instancia de {% data variables.product.prodname_ghe_server %} ni resolverá problemas de rendimiento relacionados con recursos de CPU o de memoria insuficientes. Si el aparato principal está fuera de línea, las réplicas activas no podrán atender ninguna solicitud de lectura o escritura. - -### Monitorear la configuración de una replicación geográfica - -{% data reusables.enterprise_installation.monitoring-replicas %} - -### Leer más -- "[Crear réplicas de replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)" diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md deleted file mode 100644 index 86b4af6ea9..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md +++ /dev/null @@ -1,186 +0,0 @@ ---- -title: Acerca de la configuración de alta disponibilidad -intro: 'En una configuración de alta disponibilidad, un aparato secundario {% data variables.product.prodname_ghe_server %} totalmente redundante se mantiene en sincronización con el aparato principal mediante la replicación de todos los almacenes de datos importantes.' -redirect_from: - - /enterprise/admin/installation/about-high-availability-configuration - - /enterprise/admin/enterprise-management/about-high-availability-configuration - - /admin/enterprise-management/about-high-availability-configuration -versions: - ghes: '*' -topics: - - Enterprise - - High availability - - Infrastructure ---- -Cuando configuras la alta disponibilidad, hay una configuración automática unidireccional, una replicación asincrónica de todos los almacenes de datos (repositorios de Git, MySQL, Redis y Elasticsearch) desde el aparato principal hacia la réplica. - -{% data variables.product.prodname_ghe_server %} admite una configuración activa/pasiva, en la que el aparato réplica se ejecuta como en un modo de espera con los servicios de base de datos ejecutándose en modo de replicación, pero con los servicios de aplicación detenidos. - -### Escenarios de fallas específicas - -Utiliza la configuración de alta disponibilidad para la protección contra lo siguiente: - -{% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %} - -Una configuración de alta disponibilidad no es una buena solución para lo siguiente: - - - **Escalar**. Mientras que puede distribuir el tráfico geográficamente utilizando la replicación geográfica, el rendimiento de las escrituras queda limitado a la velocidad y la disponibilidad del aparato principal. Para obtener más informació, consulta "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)." - - **Generar copias de seguridad de tu aparato principal**. Una réplica de alta disponibilidad no reemplaza las copias de seguridad externas en tu plan de recuperación ante desastres. Algunas formas de corrupción o pérdida de datos se pueden replicar de inmediato desde el aparato principal hacia la réplica. Para asegurar una reversión segura a un estado antiguo estable, debes realizar copias de seguridad de rutina con instantáneas históricas. - - **Actualizaciones del tiempo de inactividad en cero**. Para evitar la pérdida de datos y las situaciones de cerebro dividido en escenarios de promoción controlados, coloca el aparato principal en el modo de mantenimiento y espera a que se completen todas las escrituras entes de promover la réplica. - -### Estrategias de conmutación por error del tráfico de red - -Durante la conmutación por error, debes configurar por separado y administrar el tráfico de red de redireccionamiento desde el aparato principal hacia la réplica. - -#### Conmutación por error de DNS - -Con la conmutación por error de DNS, utiliza valores TTL cortos en los registros DNS que se dirijan al aparato principal {% data variables.product.prodname_ghe_server %}. Recomendamos un TTL de entre 60 segundos y cinco minutos. - -Durante la conmutación por error, debes colocar el aparato principal en modo de mantenimiento y redirigir sus registros DNS hacia la dirección IP del aparato réplica. El tiempo necesario para redirigir el tráfico desde el aparato principal hacia la réplica dependerá de la configuración TTL y del tiempo necesario para actualizar los registros DNS. - -Si estás utilizando la replicación geográfica, debes configurar Geo DNS en tráfico directo hacia la réplica más cercana. Para obtener más informació, consulta "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)." - -#### Balanceador de carga - -{% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %} - -Durante la conmutación por error, debes colocar el aparato principal en el modo de mantenimiento. Puedes configurar el balanceador de carga para que detecte automáticamente cuando la réplica se haya promovido a principal, o puede que se requiera un cambio de configuración manual. Debes promover manualmente la réplica a principal antes de que responda al tráfico de usuarios. Para obtener más información, consulta "[Utilizar {% data variables.product.prodname_ghe_server %} con un balanceador de carga](/enterprise/{{ currentVersion }}/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/)." - -{% data reusables.enterprise_installation.monitoring-replicas %} - -### Utilidades para la administración de la replicación - -Para administrar la replicación en {% data variables.product.prodname_ghe_server %}, haz uso de estas utilidades de la línea de comando conectándote al aparato réplica con SSH. - -#### ghe-repl-setup - -El comando `ghe-repl-setup` coloca un aparato {% data variables.product.prodname_ghe_server %} en modo de espera de réplica. - - - Un túnel cifrado {% if currentVersion ver_gt "enterprise-server@2.17" %}WireGuard VPN{% else %}OpenVPN{% endif %} está configurado para la comunicación entre los dos aparatos. - - Se configuran los servicios de bases de datos para la replicación y se inician. - - Se inhabilitan los servicios de aplicaciones. Los intentos de acceder al aparato réplica por HTTP, Git u otros protocolos compatibles generarán una página de mantenimiento o un mensaje de error de "aparato en modo réplica". - -```shell -admin@169-254-1-2:~$ ghe-repl-setup 169.254.1.1 -Verificar la conectividad ssh con 169.254.1.1 ... -Comprobación de conexión exitosa. -Configurando la replicación de base de datos en oposición al principal... -Success: Replica mode is configured against 169.254.1.1. -To disable replica mode and undo these changes, run `ghe-repl-teardown'. -Ejecuta `ghe-repl-start' para comenzar la replicación en oposición al principal recientemente configurado. -``` - -#### ghe-repl-start - -El comando `ghe-repl-start` inicia la replicación activa de todos los almacenes de datos. - -```shell -admin@169-254-1-2:~$ ghe-repl-start{% if currentVersion ver_lt "enterprise-server@2.18" %} -Starting OpenVPN tunnel ... {% endif %} -Starting MySQL replication ... -Iniciando la replicación de Redis... -Iniciando la replicación de ElasticSearch... -Iniciando la replicación de Páginas... -Iniciando la replicación de Git... -Exitoso: La replicación se está ejecutando para todos los servicios. -Utiliza `ghe-repl-status' para monitorear el estado y el progreso de la replicación. -``` - -#### ghe-repl-status - -El comando `ghe-repl-status` muestra un estado de `OK`, `ADVERTENCIA` o `CRÍTICO` para cada corriente de replicación de almacén de datos. Cuando cualquiera de los canales de replicación está en estado `ADVERTENCIA`, el comando se cerrará con el código `1`. Del mismo modo, cuando cualquiera de los canales esté en un estado `CRÍTICO`, el comando se cerrará con el código `2`. - -```shell -admin@169-254-1-2:~$ ghe-repl-status -OK: replicación de mysql en sinc -OK: la replicación de redis está en sinc -OK: la agrupación de elasticsearch está en sinc -OK: los datos de git están en sinc (10 repos, 2 wikis, 5 gists) -OK: los datos de páginas están en sinc -``` - -Las opciones `-v` y `-vv` dan detalles sobre cada uno de los estados de replicación de almacén de datos: - -```shell -$ ghe-repl-status -v -OK: replicación de mysql en sinc - | IO en ejecución: Sí, SQL en ejecución: Sí, Demora: 0 - -OK: la replicación de redis está en sinc - | master_host:169.254.1.1 - | master_port:6379 - | master_link_status:up - | master_last_io_seconds_ago:3 - | master_sync_in_progress:0 - -OK: la agrupación de elasticsearch está en sinc - | { - | "cluster_name" : "github-enterprise", - | "status" : "green", - | "timed_out" : falso, - | "number_of_nodes" : 2, - | "number_of_data_nodes" : 2, - | "active_primary_shards" : 12, - | "active_shards" : 24, - | "relocating_shards" : 0, - | "initializing_shards" : 0, - | "unassigned_shards" : 0 - | } - -OK: los datos de git están en sinc (366 repos, 31 wikis, 851 gists) - | TOTAL OK FALLA PENDIENTE CON DEMORA - | repositorios 366 366 0 0 0.0 - | wikis 31 31 0 0 0.0 - | gists 851 851 0 0 0.0 - | total 1248 1248 0 0 0.0 - -OK: los datos de páginas están en sinc - | Las páginas están en sinc -``` - -#### ghe-repl-stop - -El comando `ghe-repl-stop` inhabilita temporalmente la replicación de todos los almacenes de datos y detiene los servicios de replicación. Para reanudar la replicación, utiliza el comando [ghe-repl-start](#ghe-repl-start). - -```shell -admin@168-254-1-2:~$ ghe-repl-stop -Deteniendo la replicación de Páginas... -Deteniendo la replicación de Git... -Deteniendo la replicación de MySQL... -Deteniendo la replicación de Redis... -Deteniendo la replicación de Elasticsearch ...{% if currentVersion ver_lt "enterprise-server@2.18" %} -Deteniendo el túnel OpenVPN ...{% endif %} -Exitoso: se detuvo la replicación para todos los servicios. -``` - -#### ghe-repl-promote - -El comando `ghe-repl-promote` inhabilita la replicación y convierte el aparato réplica en principal. El aparato se configura con los mismos ajustes que el principal original y se habilitan todos los servicios. - -{% data reusables.enterprise_installation.promoting-a-replica %} - -```shell -admin@168-254-1-2:~$ ghe-repl-promote -Habilitando el modo de mantenimiento en el aparato principal para evitar escrituras... -Deteniendo la replicación... - | Deteniendo la replicación de Páginas... - | Deteniendo la replicación de Git... - | Deteniendo la replicación de MySQL... - | Deteniendo la replicación de Redis... - | Deteniendo la replicación de Elasticsearch ...{% if currentVersion ver_lt "enterprise-server@2.18" %} - | Deteniendo el túnel OpenVPN ...{% endif %} - | Exitoso: se detuvo la replicación para todos los servicios. -Cambiando del modo réplica... - | Exitoso: se eliminó la configuración de la replicación. - | Ejecuta `ghe-repl-setup' para volver a habilitar el modo réplica. -Aplicando la configuración e iniciando los servicios... -Exitoso: la réplica se promovió a principal y ahora está aceptando solicitudes. -``` - -#### ghe-repl-teardown - -El comando `ghe-repl-teardown` inhabilita el modo de replicación por completo, eliminando la configuración de la réplica. - -### Leer más - -- "[Crear una réplica de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica)" diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md deleted file mode 100644 index dd35e00e28..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Crear una réplica de alta disponibilidad -intro: 'En una configuración activa/pasiva, el aparato réplica es una copia redundante del aparato principal. Si el aparato principal falla, el modo de alta disponibilidad permite que la réplica actúe como aparato principal, lo que posibilita que la interrupción del servicio sea mínima.' -redirect_from: - - /enterprise/admin/installation/creating-a-high-availability-replica - - /enterprise/admin/enterprise-management/creating-a-high-availability-replica - - /admin/enterprise-management/creating-a-high-availability-replica -versions: - ghes: '*' -topics: - - Enterprise - - High availability - - Infrastructure ---- -### Crear una réplica de alta disponibilidad - -1. Configurar un aparato para el {% data variables.product.prodname_ghe_server %} nuevo en la plataforma que desees. El aparato réplica debe espejar la CPU, la RAM y los ajustes de almacenamiento del aparato principal. Recomendamos que instales el aparato réplica en un entorno separado. El hardward subyacente, el software y los componentes de red deben estar aislados de los del aparato principal. Si estás usando un proveedor de nube, utiliza una región o zona separada. Para obtener más información, consulta ["Configurar una instancia {% data variables.product.prodname_ghe_server %}"](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance). -2. Desde un navegador, dirígete a la nueva dirección IP del aparato réplica y carga tu licencia de {% data variables.product.prodname_enterprise %}. -3. Establece una contraseña de administrador que coincida con la contraseña del aparato principal y continúa. -4. Haz clic en **Configure as Replica** (Configurar como réplica). ![Opciones de instalación con enlace para configurar tu nueva instancia como una réplica](/assets/images/enterprise/management-console/configure-as-replica.png) -5. En "Add new SSH key" (Agregar nueva clave SSH), escribe tu clave SSH. ![Agrega la clave SSH](/assets/images/enterprise/management-console/add-ssh-key.png) -6. Haz clic en **Add key** (Agregar clave), luego haz clic en **Continue** (Continuar). -6. Conectarse a la dirección IP del aparato réplica usando SSH. - ```shell - $ ssh -p 122 admin@REPLICA IP - ``` -7. Para generar un par de claves para la replicación, usa el comando `ghe-repl-setup` con la dirección IP del aparato principal y copia la clave pública que este devuelve. - ```shell - $ ghe-repl-setup PRIMARY IP - ``` -{% data reusables.enterprise_installation.add-ssh-key-to-primary %} -9. Para verificar la conexión con la primaria y habilitar el modo de réplica para una nueva réplica, ejecuta nuevamente `ghe-repl-setup`. - ```shell - $ ghe-repl-setup PRIMARY IP - ``` -{% data reusables.enterprise_installation.replication-command %} -11. Para verificar el estado de cada canal de replicación del almacén de datos, utiliza el comando `ghe-repl-status`. - ```shell - $ ghe-repl-status - ``` - -### Crear réplicas de replicación geográfica - -Esta configuración de ejemplo utiliza una réplica primaria y dos réplicas, que se encuentran en tres regiones geográficas diferentes. Aunque los tres nodos pueden estar en redes diferentes, se necesitan todos los nodos para que sean accesibles desde todos los demás nodos. Como mínimo, los puertos administrativos requeridos deben estar abiertos para todos los demás nodos. Para obtener más información acerca de los requisitos de puerto, consulta "[Puertos de red](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports/#administrative-ports)." - -1. Crea la primera réplica de la misma manera en que lo harías para una configuración de dos nodos estándar ejecutando `ghe-repl-setup` en la primera réplica. - ```shell - (replica1)$ ghe-repl-setup PRIMARY IP - (replica1)$ ghe-repl-start - ``` -2. Crea una segunda réplica y utiliza el comando `ghe-repl-setup --add`. La marca `--add` evita que sobrescriba la configuración de la replicación existente y agrega la nueva réplica a la configuración. - ```shell - (replica2)$ ghe-repl-setup --add PRIMARY IP - (replica2)$ ghe-repl-start - ``` -3. Por defecto, las réplicas se configuran en el mismo centro de datos{% if currentVersion ver_gt "enterprise-server@2.17" %}, e intentarán iniciar desde un nodo existente en el mismo centro de datos{% endif %}. Configura las réplicas para diferentes centros de datos estableciendo un valor diferente para la opción de centro de datos. Los valores específicos pueden ser los que tú quieras, siempre que sean diferentes entre sí. Ejecuta el comando `ghe-repl-node` en cada nodo y especifica el centro de datos. - - En la primaria: - ```shell - (primary)$ ghe-repl-node --datacenter [PRIMARY DC NAME] - ``` - En la primera réplica: - ```shell - (replica1)$ ghe-repl-node --datacenter [FIRST REPLICA DC NAME] - ``` - En la segunda réplica: - ```shell - (replica2)$ ghe-repl-node --datacenter [SECOND REPLICA DC NAME] - ``` - {% tip %} - - **Consejo:** puedes establecer las opciones `--datacenter` y `--active` al mismo tiempo. - - {% endtip %} -4. Un nodo de réplica activo almacenará copias de los datos del aparato y responderá las solicitudes de usuario final. Un nodo inactivo almacenará copias de los datos del aparato, pero no podrá atender las solicitudes de usuario final. Habilita el modo activo usando la marca `--active` o el modo inactivo usando la marca `--inactive`. - - En la primera réplica: - ```shell - (replica1)$ ghe-repl-node --active - ``` - En la segunda réplica: - ```shell - (replica2)$ ghe-repl-node --active - ``` -5. Para aplicar la configuración, usa el comando `ghe-config-apply` en el principal. - ```shell - (primary)$ ghe-config-apply - ``` - -### Configurar el DNS para replicación geográfica - -Configurar Geo DNS usando las direcciones IP de los nodos primarios y réplica. También puedes crear un DNS CNAME para el nodo principal (p. ej., `primary.github.example.com`) para acceder al nodo principal a través de SSH o hacerle una copia de seguridad a través de `backup-utils`. - -Para probarlo, puedes agregar entradas al archivo de `hosts` de la estación de trabajo local (por ejemplo, `/etc/hosts`). Estas entradas de ejemplo resolverán las solicitudes de `HOSTNAME` para `replica2`. Puedes apuntar a hosts específicos comentando en diferentes líneas. - -``` -# HOSTNAME -# HOSTNAME - HOSTNAME -``` - -### Leer más - -- "[Acerca de la configuración de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration)" -- "[Utilidades para la gestión de replicaciones](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" -- "[Acerca de la replicación geográfica](/enterprise/{{ currentVersion }}/admin/guides/installation/about-geo-replication/)" diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/index.md b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/index.md deleted file mode 100644 index 0862161d22..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Configurar la disponibilidad alta -redirect_from: - - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability - - /enterprise/admin/guides/installation/high-availability-cluster-configuration/ - - /enterprise/admin/guides/installation/high-availability-configuration/ - - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability/ - - /enterprise/admin/enterprise-management/configuring-high-availability -intro: '{% data variables.product.prodname_ghe_server %} admite un modo de alta disponibilidad de funcionamiento diseñado para minimizar la interrupción del servicio en caso que ocurra una falla de hardware o una interrupción de red importante que afecte al aparato principal.' -versions: - ghes: '*' -topics: - - Enterprise -children: - - /about-high-availability-configuration - - /creating-a-high-availability-replica - - /initiating-a-failover-to-your-replica-appliance - - /recovering-a-high-availability-configuration - - /removing-a-high-availability-replica - - /about-geo-replication ---- - diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md deleted file mode 100644 index 97db99b3bd..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Iniciar una tolerancia de fallos a tu aparato de réplica -intro: 'Puedes tener tolerancia de fallos en un aparato de réplica {% data variables.product.prodname_ghe_server %} por medio de la línea de comando para mantenimiento y pruebas, o si falla el aparato principal.' -redirect_from: - - /enterprise/admin/installation/initiating-a-failover-to-your-replica-appliance - - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance - - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance -versions: - ghes: '*' -topics: - - Enterprise - - High availability - - Infrastructure ---- -El tiempo requerido para la tolerancia de fallos depende de cuánto le tome para impulsar la réplica y redireccionar el tráfico de forma manual. El tiempo promedio varía entre 2 y 10 minutos. - -{% data reusables.enterprise_installation.promoting-a-replica %} - -1. Para permitir que la replicación finalice antes de cambiar aparatos, pon el aparato principal en modo mantenimiento: - - Para usar el administrador de consola, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)" - - También puedes usar el comando `ghe-maintenance -s`. - ```shell - $ ghe-maintenance -s - ``` -2. Cuando el número de operaciones Git activas llega a cero, espera 30 segundos. -3. Para verificar que todos los canales de replicación informan `OK`, utiliza el comando `ghe-repl-status -vv`. - ```shell - $ ghe-repl-status -vv - ``` -4. Para frenar la replicación e impulsar el aparato de réplica a un estado primario, utiliza el comando `ghe-repl-promote`. Esto también pondrá de forma automática al nodo primario en nodo mantenimiento si es accesible. - ```shell - $ ghe-repl-promote - ``` -5. Actualiza el registro de DNS para que apunte a la dirección IP de la réplica. El tráfico es direccionado a la réplica después de que transcurra el período TTL. Si estás utilizando un balanceador de carga, asegúrate de que esté configurado para enviar el tráfico a la réplica. -6. Notifica a los usuarios que pueden retomar las operaciones normales. -7. Si se desea, configura una replicación desde el aparato principal nuevo al aparato existente y el principal anterior. Para obtener más información, consulta "[Acerca de la configuración de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)." - -### Leer más - -- "[Utilidades para la gestión de replicaciones](/enterprise/{{ currentVersion }}/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)" diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md deleted file mode 100644 index 70eea8354c..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Recuperar una configuración de disponibilidad alta -intro: 'Después de la conmutación por error de un aparato {% data variables.product.prodname_ghe_server %}, debes recuperar redundancia tan pronto como sea posible en lugar de depender de un aparato único.' -redirect_from: - - /enterprise/admin/installation/recovering-a-high-availability-configuration - - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration - - /admin/enterprise-management/recovering-a-high-availability-configuration -versions: - ghes: '*' -topics: - - Enterprise - - High availability - - Infrastructure ---- -Puedes utilizar el aparato principal antiguo como el nuevo aparato de réplica si la conmutación por error fue planeada o no estaba relacionada con la salud del aparato. Si la conmutación por error estaba relacionado con un problema con el aparato primario, es posible que prefieras crear un nuevo aparato de réplica. Para obtener más información, consulta "[Crear una réplica de alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/creating-a-high-availability-replica/)." - -### Configurar un aparato principal antiguo como una nueva réplica - -1. Conéctate a la dirección IP del aparato principal antiguo utilizando SSH. - ```shell - $ ssh -p 122 admin@FORMER PRIMARY IP - ``` -2. En el aparato principal antiguo, ejecuta el comando `ghe-repl-setup` con la dirección IP de la réplica antigua. - ```shell - $ ghe-repl-setup FORMER REPLICA IP - ``` -{% data reusables.enterprise_installation.add-ssh-key-to-primary %} -4. Para verificar la conexión con el aparato principal nuevo y habilitar el modo réplica para la nueva réplica, ejecuta nuevamente `ghe-repl-setup`. - ```shell - $ ghe-repl-setup FORMER REPLICA IP - ``` -{% data reusables.enterprise_installation.replication-command %} diff --git a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/removing-a-high-availability-replica.md b/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/removing-a-high-availability-replica.md deleted file mode 100644 index 08716620bb..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/configuring-high-availability/removing-a-high-availability-replica.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Quitar una réplica de disponibilidad alta -intro: 'Puedes detener una replicación a una réplica {% data variables.product.prodname_ghe_server %} de forma temporal, o quitar la replicación de forma permanente.' -redirect_from: - - /enterprise/admin/installation/removing-a-high-availability-replica - - /enterprise/admin/enterprise-management/removing-a-high-availability-replica - - /admin/enterprise-management/removing-a-high-availability-replica -versions: - ghes: '*' -topics: - - Clustering - - High availability - - Enterprise - - Infrastructure ---- -### Detener una replicación de forma temporal - -1. Si es necesario, puedes detener una replicación geográfica del tráfico de usuario activo al quitar las entradas Geo DNS para la réplica. -2. En la réplica donde deseas detener la replicación de forma temporal, ejecuta ghe-repl-stop. - ```shell - $ ghe-repl-stop - ``` -3. Para comenzar la replicación nuevamente, ejecuta `ghe-repl-start`. - ```shell - $ ghe-repl-start - ``` - -### Quitar la replicación de forma permanente - -1. Si es necesario, puedes detener una replicación geográfica del tráfico de usuario activo al quitar las entradas Geo DNS para la réplica. -2. En la réplica donde deseas quitar la replicación, ejecuta `ghe-repl-stop`. - ```shell - $ ghe-repl-stop - ``` -3. En la réplica, para acabar con el estado de replicación, ejecuta `ghe-repl-teardown`. - ```shell - $ ghe-repl-teardown - ``` diff --git a/translations/es-XL/content/admin/enterprise-management/index.md b/translations/es-XL/content/admin/enterprise-management/index.md deleted file mode 100644 index ddd3224b80..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: 'Monitoring, managing, and updating your enterprise' -intro: 'You can monitor your appliance, upgrade to a newer version, and configure clustering or high availability' -redirect_from: - - /enterprise/admin/enterprise-management -versions: - ghes: '*' -topics: - - Enterprise -children: - - /monitoring-your-appliance - - /updating-the-virtual-machine-and-physical-resources - - /configuring-clustering - - /configuring-high-availability ---- - diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md b/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md deleted file mode 100644 index 8c6c542ace..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Acceder al tablero del monitor -intro: '{% data variables.product.prodname_ghe_server %} incluye un tablero de monitoreo en la web que muestra los datos históricos sobre tu aparato {% data variables.product.prodname_ghe_server %}, como la CPU y el uso del almacenamiento, los tiempos de respuesta de la aplicación y de la autenticación y la salud general del sistema.' -redirect_from: - - /enterprise/admin/installation/accessing-the-monitor-dashboard - - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard - - /admin/enterprise-management/accessing-the-monitor-dashboard -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Monitoring - - Performance ---- -### Acceder al tablero del monitor - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. En la parte superior de la página, haga clic en **Monitor**. ![Enlace al Tablero del monitor](/assets/images/enterprise/management-console/monitor-dash-link.png) - -### Solucionar problemas de la asignación de los recursos comunes en su aparato - -{% note %} - -**Nota**: Porque el sondeo regular de {% data variables.product.product_location_enterprise %} con integración continua (CI) o la construcción de servidores puede causar efectivamente un rechazo del ataque al servicio que genera problemas, te recomendamos que utilice webhooks para subir las actualizaciones. Para obtener más información, consulte "[Acerca de webhooks](/enterprise/{{ currentVersion }}/user/articles/about-webhooks/)". - -{% endnote %} - -Utiliza el tablero del monitor para mantenerse informado sobre la salud del recurso de su aparato y tomar decisiones sobre cómo corregir los problemas de alto uso. - -| Problema | Posible(s) causa(s) | Recomendaciones | -| ------------------------------------------- | ----------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Alto uso de la CPU | Conexión a la VM desde otros servicios o programas que se ejecutan en el mismo host | De ser posible, vuelve a configurar los otros servicios o programas para utilizar menos recursos de la CPU. Para aumentar los recursos totales de la CPU para la VM, consulte "[Aumentar los recursos de CPU o de memoria](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-cpu-or-memory-resources/)." | -| Alto uso de la memoria | Conexión a la VM desde otros servicios o programas que se ejecutan en el mismo host | De ser posible, vuelve a configurar otros servicios o programas para utilizar menos memoria. Para aumentar la memoria total disponible en la VM, consulta "[Aumentar los recursos de CPU o de memoria](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-cpu-or-memory-resources/)." | -| Baja disponibilidad de espacio en el disco | Binarios grandes o archivos de registro que consumen espacio del disco | De ser posible, aloje los binarios grandes en un servidor separado y comprima o archive los archivos de registro. De ser necesario, aumenta el espacio del disco en la VM siguiendo los pasos de tu plataforma en "[Aumentar la capacidad de almacenamiento](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity/)." | -| Tiempos de respuesta más altos que lo común | Los suelen causar alguna de las propuestas anteriores | Identifica y corrige las propuestas subyacentes. Si los tiempos de respuesta siguen altos, contáctate con {% data variables.contact.contact_ent_support %}. | -| Índices de error elevados | Propuestas de software | Contáctate con {% data variables.contact.contact_ent_support %} e incluye tu paquete de soporte. Para obtener más información, consulta "[Proporcionar datos para {% data variables.product.prodname_enterprise %} Asistencia](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." | diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md deleted file mode 100644 index 82cd7cdc76..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Configurar collectd -intro: '{% data variables.product.prodname_enterprise %} puede reunir datos con `collectd` y enviarlos a un servidor `collectd` externo. Entre otras métricas, reunimos un conjunto estándar de datos, como la utilización de la CPU, el consumo de memoria y de disco, el tráfico y los errores de la interfaz de red y la carga general de la VM.' -redirect_from: - - /enterprise/admin/installation/configuring-collectd - - /enterprise/admin/articles/configuring-collectd/ - - /enterprise/admin/enterprise-management/configuring-collectd - - /admin/enterprise-management/configuring-collectd -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Monitoring - - Performance ---- -### Configura un servidor `collectd` externo - -Si aún no has configurado un servidor `collectd` externo, tendrás que hacerlo antes de habilitar el redireccionamiento `collectd` en {% data variables.product.product_location_enterprise %}. Tu servidor `collectd` se debe ejecutar con una versión 5.x o posterior de `collectd`. - -1. Inicia sesión en tu servidor `collectd`. -2. Crea o edita el archivo de configuración `collectd` para cargar el plugin de red y completar las directivas del servidor y del puerto con los valores adecuados. En la mayoría de las distribuciones, este se ubica en `/etc/collectd/collectd.conf` - -Un ejemplo *collectd.conf* para ejecutar un servidor `collectd`: - - Red LoadPlugin - ... - ... - - Escucha "0.0.0.0" "25826" - - -### Habilita el redireccionamiento collectd en {% data variables.product.prodname_enterprise %} - -Por defecto, el redireccionamiento `collectd` está inhabilitado en {% data variables.product.prodname_enterprise %}. Sigue los pasos que aparecen a continuación para habilitar y configurar el redireccionamiento `collectd`: - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -1. A continuación aparecen los ajustes de redireccionamiento, selecciona **Enable collectd forwarding** (Habilitar el redireccionamiento collectd). -1. En el campo **Server addres** (Dirección del servidor), escribe la dirección del servidor `collectd` al cual quisieras redirreccionar las estadísticas del aparato {% data variables.product.prodname_enterprise %}. -1. En el campo **Port** (Puerto), escribe el puerto utilizado para canectarse al servidor `collectd`. (Predeterminados en 25826) -1. En el menú desplegable **Cryptographic setup** (Configuración criptográfica), selecciona el nivel de seguridad de las comunicaciones con el servidor `collectd`. (Ninguno, paquetes firmados o paquetes encriptados). -{% data reusables.enterprise_management_console.save-settings %} - -### Exportar los datos collectd con `ghe-export-graphs` - -La herramienta de la línea de comando `ghe-export-graphs` exportará los datos que `collectd` almacene en las bases de datos RRD. Este comando convierte los datos a XML y los exporta a un tarball único (.tgz). - -Su uso principal es proporcionarle al equipo de {% data variables.contact.contact_ent_support %} los datos sobre el desempeño de una VM, sin la necesidad de descargar un paquete de soporte completo. No se debe incluir en tus exportaciones de copias de seguridad regulares y no existe una contraparte de importación. Si te contactas con {% data variables.contact.contact_ent_support %}, puede que te solicitemos estos datos para ayudarte a solucionar los problemas. - -#### Uso - -```shell -ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz . -``` - -### Solución de problemas - -#### El servidor collectd central no recibe datos - -{% data variables.product.prodname_enterprise %} viene con la versión 5.x de `collectd`. `collectd` 5.x no es retrocompatible con la serie de lanzamientos 4.x. Tu servidor `collectd` central debe tener al menos la versión 5.x para aceptar los datos que se envían desde {% data variables.product.product_location_enterprise %}. - -Para obtener ayuda con más preguntas o problemas, contacta a {% data variables.contact.contact_ent_support %}. diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/index.md deleted file mode 100644 index d8549223e6..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Monitorear tu aplicativo -intro: 'Debido a que el uso {% data variables.product.product_location_enterprise %} aumenta con el tiempo, se incrementará la utilización de recursos del sistema, como el CPU, la memoria, y el almacenamiento. Puedes configurar una revisión y alertas para que estar al tanto de problemas potenciales antes de que se vuelvan lo suficientemente críticos para impactar de forma negativa en el desempeño de la aplicación o su disponibilidad.' -redirect_from: - - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting/ - - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance/ - - /enterprise/admin/installation/monitoring-your-github-enterprise-server-appliance - - /enterprise/admin/enterprise-management/monitoring-your-appliance -versions: - ghes: '*' -topics: - - Enterprise -children: - - /accessing-the-monitor-dashboard - - /recommended-alert-thresholds - - /setting-up-external-monitoring - - /configuring-collectd - - /monitoring-using-snmp ---- - diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/log-forwarding.md b/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/log-forwarding.md deleted file mode 100644 index fae820cda8..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/log-forwarding.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Redireccionamiento de registro -intro: '{% data variables.product.prodname_enterprise %} utiliza `syslog-ng` para redireccionar los registros de la aplicación y del sistema al servidor que especifiques en los parámetros {% data variables.enterprise.management_console %}.' -redirect_from: - - /enterprise/admin/articles/log-forwarding/ - - /enterprise/admin/installation/log-forwarding - - /enterprise/admin/enterprise-management/log-forwarding - - /admin/enterprise-management/log-forwarding -versions: - enterprise-server: '*' ---- -Es compatible cualquier sistema de recopilación de registro que admita los flujos de registro syslog-style (p. ej., [Logstash](http://logstash.net/) y [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)). - -### Habilitar redireccionamiento de registro - -1. En la página de parámetros {% data variables.enterprise.management_console %}, en la barra lateral izquierda, haz clic en **(Monitoring) Revisar**. -1. Selecciona **Enable log forwarding (Habilitar redireccionamiento de registro)**. -1. En el campo **Server address (Dirección del servidor)**, escribe la dirección del servidor al que desees redireccionar los registros. Puedes especificar varias direcciones en una lista de separación por coma. -1. En el menú desplegable de Protocolo, selecciona el protocolo a utilizar para que se comunique con el servidor de registro. El protocolo se aplicará a todos los destinos de registro especificados. -1. Selecciona **Enable TLS (Habilitar TLS)**. -1. Haz clic en **Choose File (Elegir el archivo)** y elige un certificado CA para encriptar la comunicación entre puntos de conexión syslog. Se validará la cadena de certificado completa, y debe terminar en un certificado raíz. Para obtener más información, consulta [Opciones TLS en la documentación de syslog-ng](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599). - -### Solución de problemas - -Si encuentras problemas con el redireccionamiento de registro, contacta a {% data variables.contact.contact_ent_support %} y adjunta el archivo de salida de `http(s)://[hostname]/setup/diagnostics` to your email. diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md deleted file mode 100644 index 14e16e8b47..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -title: Supervisar por medio de SNMP -intro: '{% data variables.product.prodname_enterprise %} proporciona datos sobre el uso del disco, la utilización del CPU, el uso de la memoria y más sobre SNMP.' -redirect_from: - - /enterprise/admin/installation/monitoring-using-snmp - - /enterprise/admin/articles/monitoring-using-snmp/ - - /enterprise/admin/enterprise-management/monitoring-using-snmp - - /admin/enterprise-management/monitoring-using-snmp -versions: - ghes: '*' -topics: - - Enterprise - - Infrastructure - - Monitoring - - Performance ---- -SNMP es una norma común para controlar dispositivos en una red. Recomendamos firmemente habilitar SNMP para que puedas controlar la salud de {% data variables.product.product_location_enterprise %} y saber cuándo agregar más memoria, almacenamiento, o rendimiento del procesador a la máquina del servidor. - -{% data variables.product.prodname_enterprise %} tiene una instalación SNMP estándar, para poder aprovechar los [diversos plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) disponibles para Nagios o para cualquier otro sistema de control. - -### Configurar SNMP v2c - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.access-monitoring %} -{% data reusables.enterprise_management_console.enable-snmp %} -4. En el campo **Community string (Cadena de la comunidad)**, ingresa una nueva cadena de comunidad. Si se deja en blanco, queda predeterminado como `públicp`. ![Campo para añadir la cadena de comunidad](/assets/images/enterprise/management-console/community-string.png) -{% data reusables.enterprise_management_console.save-settings %} -5. Prueba tu configuración SNMP al ejecutar el siguiente comando en una estación de trabajo por separado con soporte de SNMP en tu red: - ```shell - # community-string is your community string - # hostname is the IP or domain of your Enterprise instance - $ snmpget -v 2c -c community-string -O e hostname hrSystemDate.0 - ``` - -Debería devolver la hora del sistema en el host {% data variables.product.product_location_enterprise %}. - -### Seguridad basada en el usuario - -Si habilitas el SNMP v3, puedes aprovechar la seguridad en base al usuario aumentada a través de User Security Model (USM). Para cada usuario único, puedes especificar un nivel de seguridad: -- `noAuthNoPriv`: este nivel de seguridad no brinda autenticación ni privacidad. -- `authNoPriv`: este nivel de seguridad brinda autenticación pero no privacidad. Para consultar al aparato deberás usar un nombre de usuario y una contraseña (que debe tener como mínimo ocho caracteres). La información se envía sin encriptación, similar a SNMPv2. El protocolo de autenticación puede ser MD5 o SHA o SHA como predeterminado. -- `authPriv`: este nivel de seguridad brinda autenticación con privacidad. Se requiere autenticación, incluida una contraseña de autenticación de ocho caracteres como mínimo, y las respuestas están encriptadas. No se requiere una contraseña de privacidad, pero si se proporciona debe tener como mínimo ocho caracteres. Si no se proporciona una contraseña de privacidad, se usa la contraseña de autenticación. El protocolo de privacidad puede ser DES o AES y queda AES como predeterminado. - -### Configurando usuarios para SNMP v3 - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.access-monitoring %} -{% data reusables.enterprise_management_console.enable-snmp %} -4. Selecciona **SNMP v3**. ![Botón para habilitar SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png) -5. En "Username (Nombre de usuario)", escribe el nombre de usuario único de tu usuario SNMP v3.![Campo para escribir el nombre de usuario SNMP v3](/assets/images/enterprise/management-console/snmpv3-username.png) -6. En el menú desplegable **Security Level (Nivel de seguridad)**, haz clic en el nivel de seguridad para tu usuario SNMP v3. ![Menú desplegable para el nivel de seguridad del usuario SNMP v3](/assets/images/enterprise/management-console/snmpv3-securitylevel.png) -7. Para usuarios SNMP v3 con el nivel de seguridad `authnopriv`: ![Configuración para el nivel de seguridad authnopriv](/assets/images/enterprise/management-console/snmpv3-authnopriv.png) - - {% data reusables.enterprise_management_console.authentication-password %} - - {% data reusables.enterprise_management_console.authentication-protocol %} -8. Para usuarios SNMP v3 con el nivel de seguridad `authpriv`: ![Configuración para el nivel de seguridad authpriv](/assets/images/enterprise/management-console/snmpv3-authpriv.png) - - {% data reusables.enterprise_management_console.authentication-password %} - - {% data reusables.enterprise_management_console.authentication-protocol %} - - De forma opcional, en "Privacy password" (Contraseña de privacidad), escribe la contraseña de privacidad. - - Hacia la derecha de "Privacy password" (Contraseña de privacidad), en el menú desplegable **Protocol (Protocolo)**, haz clic en el método de protocolo de privacidad que deseas usar. -9. Haz clic en **Add secret (Agregar secreto)**. ![Botón para añadir usuario SNMP v3](/assets/images/enterprise/management-console/snmpv3-adduser.png) -{% data reusables.enterprise_management_console.save-settings %} - -##### Consultar datos de SNMP - -Tanto la información del nivel de software como de hardware sobre tu aparato está disponible con SNMP v3. Debido a la falta de encriptación y privacidad para los niveles de seguridad `noAuthNoPriv` y `authNoPriv`, excluimos la tabla `hrSWRun` (1.1.3.6.1.2.1.25.41) de los informes SNMP resultantes. Incluimos esta tabla si estás usando el nivel de seguridad `authPriv`. - -Con SNMP v2c, solo está disponible la información del nivel de hardware de tu aparato. Estas aplicaciones y servicios dentro de {% data variables.product.prodname_enterprise %} no tienen configurado OID para informar métricas. Hay varios MIB disponibles, que puedes ver ejecutando `snmpwalk` en una estación de trabajo separada con soporte SNMP en tu red: - -```shell -# community-string es tu cadena de comunidad -# hostname es la IP o dominio de tu instancia de empresa -$ snmpwalk -v 2c -c community-string -O e hostname -``` - -De los MIB disponibles para SNMP, el más útil es `HOST-RESOURCES-MIB` (.1.3.6.1.2.1.25). Consulta la tabla de abajo para ver algunos objetos importantes en este MIB: - -| Nombre | OID | Descripción | -| -------------------------- | ------------------------- | ----------------------------------------------------------------------------------------------- | -| hrSystemDate.2 | .1.3.6.1.2.1.25.1.2 | La noción de servidores de los datos locales y de la hora del día. | -| hrSystemUptime.0 | .1.3.6.1.2.1.25.1.1.0 | Cuánto tiempo ha pasado desde que el servidor se inició por última vez. | -| hrMemorySize.0 | .1.3.6.1.2.1.25.2.2.0 | La cantidad de RAM en el servidor. | -| hrSystemProcesses.0 | .1.3.6.1.2.1.25.1.6.0 | La cantidad de contextos de proceso actualmente cargados o ejecutándose en el servidor. | -| hrStorageUsed.1 | .1.3.6.1.2.1.25.2.3.1.6.1 | La cantidad de espacio de almacenamiento consumido en el servidor, en hrStorageAllocationUnits. | -| hrStorageAllocationUnits.1 | .1.3.6.1.2.1.25.2.3.1.4.1 | El tamaño, en bytes, de una hrStorageAllocationUnit | - -Por ejemplo, para consultar `hrMemorySize` con SNMP v3, ejecuta el siguiente comando en una estación de trabajo separada con apoyo de SNMP en tu red: -```shell -# username es el nombre de usuario único de tu usuario SNMP v3 -# auth password es la contraseña de autenticación -# privacy password es la contraseña de privacidad -# hostname es la IP o el dominio de tu instancia de empresa -$ snmpget -v 3 -u username -l authPriv \ - -A "auth password" -a SHA \ - -X "privacy password" -x AES \ - -O e hostname HOST-RESOURCES-MIB::hrMemorySize.0 -``` - -Con SNMP v2c, para consultar `hrMemorySize`, ejecuta el siguiente comando en una estación de trabajo separada con apoyo de SNMP en tu red: -```shell -# community-string es tu cadena de comunidad -# hostname es la IP o el dominio de tu instancia de empresa -snmpget -v 2c -c community-string hostname HOST-RESOURCES-MIB::hrMemorySize.0 -``` - -{% tip %} - -**Nota:** para evitar que se filtre información sobre los servicios que se están ejecutando en tu aparato, excluimos la tabla `hrSWRun` (1.1.3.6.1.2.1.25.41) de los informes SNMP resultantes excepto que estés usando el nivel de seguridad `authPriv` con SNMP v3. Si estás utilizando el nivel de seguridad `authPriv`, incluimos la tabla `hrSWRun`. - -{% endtip %} - -Para obtener más información sobre los mapeos OID para los atributos de sistema comunes en SNMP, consulta "[OID SNMP de Linux para CPU, memoria y estadísticas de disco](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)". diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md b/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md deleted file mode 100644 index 9bb34db39c..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Límites de alerta recomendados -intro: 'Puedes configurar una alerta para notificar los problemas de tus recursos de sistema antes de que afecten el desempeño de tu aparato {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/guides/installation/about-recommended-alert-thresholds/ - - /enterprise/admin/installation/about-recommended-alert-thresholds - - /enterprise/admin/installation/recommended-alert-thresholds - - /enterprise/admin/enterprise-management/recommended-alert-thresholds - - /admin/enterprise-management/recommended-alert-thresholds -versions: - ghes: '*' -topics: - - Enterprise - - Infrastructure - - Monitoring - - Performance - - Storage ---- -### Controlar el almacenamiento - -Recomendamos que controles los dispositivos de almacenamiento de usuario y raíz y configures una alerta con valores que permitan un gran tiempo de respuesta cuando el espacio de disco disponible sea bajo. - -| Gravedad | Límite | -| --------------- | ---------------------------------------------------- | -| **Advertencia** | El disco excede el 70 % del total disponible | -| **Crítico** | El uso del disco excede el 85 % del total disponible | - -Puedes ajustar estos valores en base a la cantidad total de almacenamiento asignado, los patrones de crecimiento histórico y el tiempo esperado de respuesta. Recomendamos asignar en exceso recursos de almacenamiento para permitir el crecimiento y evitar el tiempo de inactividad requerido para asignar almacenamiento adicional. - -### Controlar el uso del CPU y de la carga promedio - -A pesar de que es normal que el uso de CPU fluctúe en base a las operaciones Git que utilizan muchos recursos, recomendamos configurar una alerta para la utilización del CPU anormalmente alta, ya que spikes prolongados puede significar que tu instancia tiene un aprovisionamiento insuficiente. Recomendamos controlar la carga promedio del sistema de quince minutos para los valores que se acerquen o excedan la cantidad de núcleos de CPU asignados en la máquina virtual. - -| Gravedad | Límite | -| --------------- | --------------------------------------------------------------- | -| **Advertencia** | La carga promedio de quince minutos excede 1x de núcleos de CPU | -| **Crítico** | La carga promedio de quince minutos excede 2x de núcleos de CPU | - -También recomendamos que controles el tiempo de "robo" de virtualización para asegurar que otras máquinas virtuales ejecutándose en el mismo sistema de servidor no estén usando todos los recursos de la instancia. - -### Controla el uso de la memoria - -La cantidad de memoria física asignada a {% data variables.product.product_location_enterprise %} puede tener un gran impacto sobre el desempeño general y la capacidad de respuesta de la aplicación. El sistema está designado para realizar un uso intenso del caché del disco kernel para acelerar las operaciones Git. Recomendamos que el conjunto en funcionamiento de RSS normal se acomode dentro del 50 % del total de RAM disponible para un uso máximo. - -| Gravedad | Límite | -| --------------- | ---------------------------------------------------------------------- | -| **Advertencia** | El uso sostenido de RSS excede el 50 % del total de memoria disponible | -| **Crítico** | El uso sostenido de RSS excede el 70 % del total de memoria disponible | - -Si se acaba la memoria, el killer de OOM kernel intentará liberar recursos de memoria al sacrificar de manera forzosa procesos de aplicación con mucho uso de RAM, lo que puede dar como resultado una interrupción del servicio. Recomendamos asignar más memoria a la máquina virtual de la requerida en el curso normal de las operaciones. diff --git a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md b/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md deleted file mode 100644 index 9ecc9b3020..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Configurar la revisión externa -intro: 'Puedes revisar los recursos de sistema básicos en tu aparato {% data variables.product.prodname_ghe_server %} utilizando el SNMP o los protocolos de recopilación de estadísticas collectd.' -redirect_from: - - /enterprise/admin/installation/setting-up-external-monitoring - - /enterprise/admin/enterprise-management/setting-up-external-monitoring - - /admin/enterprise-management/setting-up-external-monitoring -versions: - ghes: '*' -topics: - - Enterprise - - Infrastructure - - Monitoring - - Performance ---- -### Acerca de SNMP - -El Protocolo de Administración de Red Simple (SNMP) es un método muy compatible para revisar los dispositivos y los servidores de red. El SNMP está inhabilitado por defecto pero puede ser configurado a través del tablero de revisión {% data variables.product.prodname_enterprise %}. El puerto UDP 161 debe abrirse y ser accesible desde tu estación de administración de red. Para obtener más información, consulta "[Revisión utilizando el SNMP](/enterprise/{{ currentVersion }}/admin/guides/installation/monitoring-using-snmp/)." - -### Acerca de collectd - -collectd es una recopilación de estadísticas de código abierto y daemon de información con apoyo integrado para escribir en archivos RRD. Las estadísticas sobre utilización de CPU, memoria y uso de disco, errores y tráfico de interfaz de red y carga de sistema pueden redireccionarse a un servidor externo collectd donde se pueden configurar los gráficos, los análisis y las alertas utilizando un amplia gama de herramientas y plugins disponibles. Para configurar el redireccionamiento de `collectd`, consulta "[Configurar collectd](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-collectd/)". - -Además, las herramientas de supervisión dentro de las plataformas de virtualización subyacentes pueden también usarse para supervisar y alertar sobre los recursos de sistema. Para obtener más información, consulta la documentación [Amazon CloudWatch](http://aws.amazon.com/cloudwatch/) y [Supervisión de VMware vSphere ](http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-monitoring-performance-guide.pdf). diff --git a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md b/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md deleted file mode 100644 index 8e1b2d7bfa..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Habilitar comprobaciones de actualización automáticas -intro: 'Puedes habilitar comprobaciones de actualización automáticas para que {% data variables.product.product_location_enterprise %} busque y descargue el último lanzamiento del {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/installation/enabling-automatic-update-checks - - /enterprise/admin/enterprise-management/enabling-automatic-update-checks - - /admin/enterprise-management/enabling-automatic-update-checks -versions: - ghes: '*' -topics: - - Enterprise - - Upgrades ---- -Cuando un paquete de actualizaciones se descarga automáticamente para {% data variables.product.product_location_enterprise %}, recibirás un mensaje informándote que puedes actualizar el {% data variables.product.prodname_ghe_server %}. Descarga de paquetes para el directorio `/var/lib/ghe-updates` en {% data variables.product.product_location_enterprise %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server)." - -Si está disponible un hotpatch para una actualización, el `.hpkg` se descargará automáticamente. En la consola de administración puedes elegir instalar el hotpatch de inmediato o programar la instalación para otro momento. Para obtener más información, consulta "[Actualizar con un hotpatch](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)." - -{% tip %} - -**Consejo:** Para habilitar comprobaciones de actualización automáticas, {% data variables.product.product_location_enterprise %} se debe poder conectar a `https://github-enterprise.s3.amazonaws.com`. - -{% endtip %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.updates-tab %} -4. Haz clic en **Yes, automatically check for updates** (Sí, buscar actualizaciones automáticamente). ![Botón para habilitar actualizaciones automáticas](/assets/images/enterprise/management-console/enable_updates_button.png) -{% data reusables.enterprise_management_console.save-settings %} - -Para saber si tu instancia está actualizada, busca el mensaje emergente en la pestaña de actualizaciones. - -![Mensaje emergente que indica tu lanzamiento del servidor de GitHub Enterprise](/assets/images/enterprise/management-console/up-to-date-banner.png) - -En **Logs** (Registros), puedes ver el estado de la búsqueda de actualizaciones más reciente. - -![Registros para actualización](/assets/images/enterprise/management-console/update-log.png) diff --git a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md b/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md deleted file mode 100644 index bea8755a6d..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Aumentar el CPU o los recursos de memoria -intro: 'Si las operaciones en {% data variables.product.product_location_enterprise %} son lentas, es posible que necesites agregar CPU o recursos de memoria.' -redirect_from: - - /enterprise/admin/installation/increasing-cpu-or-memory-resources - - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources - - /admin/enterprise-management/increasing-cpu-or-memory-resources -versions: - ghes: '*' -topics: - - Enterprise - - Infrastructure - - Performance ---- -{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} - -### Agregar CPU o recursos de memoria para AWS - -{% note %} - -**Nota:** Para agregar CPU o recursos de memoria para AWS, debes estar familiarizado con el uso de la consola de administración de AWS o la interfaz de la línea de comando `aws ec2` para administrar instancias EC2. Para obtener antecedentes y detalles sobre el uso de herramientas de AWS de tu elección para realizar el ajuste de tamaño, consulta la documentación de AWS en [ajustar el tamaño de una instancia respaldada por Amazon EBS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html). - -{% endnote %} - -#### Consideraciones relativas al ajuste de tamaño - -Antes de aumentar la CPU o los recursos de memoria para {% data variables.product.product_location_enterprise %}: - -- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %} -- **Assign an Elastic IP address to the instance**. Si no se asigna una IP elástica, deberás ajustar los registros DNS A para tu servidor {% data variables.product.prodname_ghe_server %} después de volver a iniciar para considerar el cambio de la dirección de IP pública. Una vez que tu instancia se reinicia, la IP elástica (EIP) se mantiene automáticamente si la instancia se inicia en una VPC. Si la instancia se inicia en una EC2-Classic, la IP elástica debe asociarse nuevamente de forma manual. - -#### Tipos de instancias AWS admitidos - -Debes determinar el tipo de instancia que te gustaría actualizar en base a especificaciones de CPU/memoria. -{% data reusables.enterprise_installation.aws-supported-instance-types %} - -#### Tipos de instancias AWS recomendadas - -{% data reusables.enterprise_installation.aws-recommended-instance-types %} - -{% data reusables.enterprise_installation.warning-on-scaling %} - -#### Volver a ajustar el tamaño para AWS - -{% note %} - -**Nota:** Para instancias iniciadas en EC2-Classic, escribe la dirección de IP elástica asociada con la instancia y las ID de las instancias. Una vez que reiniciaste la instancia, vuelve a asociar la dirección de IP elástica. - -{% endnote %} - -Si no es posible agregar un CPU o recursos de memoria a una instancia AWS/EC2 existente. En su lugar, debes: - -1. Frenar la instancia. -2. Cambiar el tipo de instancia. -3. Iniciar la instancia. -{% data reusables.enterprise_installation.configuration-recognized %} - -### Agregar CPU o recursos de memoria para OpenStack KVM - -No es posible agregar CPU o recursos de memoria para una instancia OpenStack KVM existente. En su lugar, debes: - -1. Tomar una instantánea para la instancia actual. -2. Frenar la instancia. -3. Seleccionar un nuevo formato de la instancia que tenga el CPU o los recursos de memoria deseados. - -### Agregar recursos de memoria o de CPU para VMware - -{% data reusables.enterprise_installation.increasing-cpus-req %} - -1. Utiliza vSphere Client para conectar al servidor de VMware ESXi. -2. Cierra {% data variables.product.product_location_enterprise %}. -3. Selecciona la máquina virtual y haz clic en **Edit Settings (Editar parámetros)**. -4. En "Hardware", ajusta el CPU o los recursos de memoria asignados a la máquina virtual según se necesite: ![Recursos de configuración de WMware](/assets/images/enterprise/vmware/vsphere-hardware-tab.png) -5. Para iniciar la máquina virtual, haz clic en **OK**. -{% data reusables.enterprise_installation.configuration-recognized %} diff --git a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md deleted file mode 100644 index 6298e5f393..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Aumentar la capacidad de almacenamiento -intro: 'Puedes aumentar o cambiar la cantidad de almacenamiento disponible para los repositorios de Git, las bases de datos, los índices de búsqueda y otros datos de aplicaciones persistentes.' -redirect_from: - - /enterprise/admin/installation/increasing-storage-capacity - - /enterprise/admin/enterprise-management/increasing-storage-capacity - - /admin/enterprise-management/increasing-storage-capacity -versions: - ghes: '*' -topics: - - Enterprise - - Infrastructure - - Performance - - Storage ---- -{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} - -A medida que se suman usuarios {% data variables.product.product_location_enterprise %}, es posible que necesites ajustar el tamaño de tu volumen de almacenamiento. Consulta la documentación de tu plataforma de virtualización para obtener más información sobre ajuste de tamaño de almacenamiento. - -### Requisitos y recomendaciones - -{% note %} - -**Nota:** Antes de ajustar el tamaño del volumen de almacenamiento del usuario, pon tu instancia en modo mantenimiento. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." - -{% endnote %} - -{% data reusables.enterprise_installation.hardware-rec-table %} - -### Aumentar el tamaño de partición de datos - -1. Ajusta el disco de volumen existente del usuario utilizando las herramientas de tu plataforma de virtualización. -{% data reusables.enterprise_installation.ssh-into-instance %} -3. Pon el aparato en modo mantenimiento. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." -4. Reinicia el aparato para detectar la nueva asignación de almacenamiento. -5. Ejecuta el comando `ghe-storage-extend` para expandir el sistema de archivos `/data`: - ```shell - $ ghe-storage-extend - ``` - -### Aumentar el tamaño de partición raíz utilizando un nuevo aparato - -1. Configura una nueva instancia {% data variables.product.prodname_ghe_server %} con un disco raíz más grande utilizando la misma versión que tu aparato actual. Para obtener más información, consulta "[Configurar una instancia {% data variables.product.prodname_ghe_server %} ](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." -2. Cierra el aparato actual. -3. Desconecta el disco de datos de tu aparato actual utilizando las herramientas de tu plataforma de virtualización. -4. Conecta el disco de datos al nuevo aparato con un disco raíz más grande. - -### Aumentar el tamaño de partición raíz utilizando un aparato existente - -1. Conecta un nuevo disco a tu aparato {% data variables.product.prodname_ghe_server %}. -2. Ejecuta el comando `parted` para formatear el disco: - ```shell - $ sudo parted /dev/xvdg mklabel msdos - $ sudo parted /dev/xvdg mkpart primary ext4 0% 50% - $ sudo parted /dev/xvdg mkpart primary ext4 50% 100% - ``` -3. Ejecuta el comando `ghe-upgrade` para instalar un paquete específico de plataforma completo al disco recientemente particionado. Un paquete de actualización de hotpatch universal, como `github-enterprise-2.11.9.hpkg` no funcionará como se espera. - ```shell - $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1 - ``` -4. Cierra el aparato. -5. En el hipervisor, quita el disco raíz anterior y agrega el nuevo disco raíz en la misma ubicación del disco raíz anterior. -6. Inicia el aparato. diff --git a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md b/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md deleted file mode 100644 index f35ea14ecc..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Actualizar la máquina virtual y los recursos físicos -intro: 'La actualización del software virtual y del hardware virtual requiere algo de tiempo de inactividad para tu instancia, por ello asegúrate de planear tu actualización de antemano.' -redirect_from: - - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-the-vm/' - - '/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-physical-resources/' - - /enterprise/admin/installation/updating-the-virtual-machine-and-physical-resources - - /enterprise/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources -versions: - ghes: '*' -topics: - - Enterprise -children: - - /upgrade-requirements - - /upgrading-github-enterprise-server - - /enabling-automatic-update-checks - - /increasing-storage-capacity - - /increasing-cpu-or-memory-resources - - /migrating-from-github-enterprise-1110x-to-2123 ---- - diff --git a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later.md b/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later.md deleted file mode 100644 index 26ab518dd7..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later.md +++ /dev/null @@ -1,132 +0,0 @@ ---- -title: Migrar índices de ElasticSearch al servidor de GitHub Enterprise 2.14 o superior -intro: 'Para prepararte para una actualización a {% data variables.product.prodname_ghe_server %} 2.14, deberás migrar tus índices a Elasticsearch 5.6 con nuestro script de migración.' -redirect_from: - - /enterprise/admin/installation/migrating-elasticsearch-indices-to-github-enterprise-2-14-or-later/ - - /enterprise/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-2-14-or-later/ - - /enterprise/admin/guides/installation/migrating-elasticsearch-indices-to-github-enterprise-server-2-14-or-later - - /enterprise/admin/enterprise-management/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later - - /admin/enterprise-management/migrating-elasticsearch-indices-to-github-enterprise-server-214-or-later -versions: - enterprise-server: '*' ---- - - - -{% data variables.product.prodname_ghe_server %} 2.14 incluye una mejora a Elasticsearch 5.6. Antes de actualizar a {% data variables.product.prodname_ghe_server %} 2.14 o superior desde la versión 2.12 o 2.13, te recomendamos descargar, instalar y ejecutar las herramientas de migración de Elasticsearch para que tus índices más grandes se migren en línea mientras tu aplicativo aún tiene acceso en línea. - -### Índices buscar - -El script de migración busca un índice `buscar` primero mientras el aparato está en línea. Migrar los índices `buscar` puede tomar desde unos minutos hasta unos días, según su tamaño. Para ejemplificar índices grandes, estos índices demoraron un par de días para migrar a nuestro entorno de prueba. - -``` -admin@ip-172-31-2-141:~$ curl -s http://localhost:9200/_cat/indices?v | sort -n -k 6 -green open blog-1 1 0 0 0 144b 144b -green open projects-1 1 0 0 0 144b 144b -green open registry-packages-1 1 0 0 0 144b 144b -green open showcases-1 1 0 0 0 144b 144b -health status index pri rep docs.count docs.deleted store.size pri.store.size -green open pull-requests-1 1 0 1 0 9.3kb 9.3kb -green open wikis-1 1 0 2 0 5kb 5kb -green open hookshot-logs-2018-05-29 5 0 25 0 124.2kb 124.2kb -green open repos-1 1 0 1638 1 1.4mb 1.4mb -green open gists-1 1 0 3531 64 291.9kb 291.9kb -green open audit_log-1-2018-06-1 1 0 11108 0 3mb 3mb -green open users-1 1 0 19866 56 2.7mb 2.7mb -green open hookshot-logs-2018-05-31 5 0 20000 0 33.4mb 33.4mb -green open hookshot-logs-2018-06-04 5 0 20000 0 32.6mb 32.6mb -green open issues-1 1 0 26405 6 82.8mb 82.8mb -green open hookshot-logs-2018-05-30 5 0 119744 0 196.8mb 196.8mb -green open audit_log-1-2018-05-1 1 0 191664 0 50mb 50mb -green open code-search-1 1 0 6932626 44 42.9gb 42.9gb -green open commits-1 1 0 63753587 1485 45.4gb 45.4gb -``` - -Los índices `buscar` comienzan con: - -- blog- -- code-search- -- commits- -- gists- -- issues- -- labels- -- marketplace-listings- -- non-marketplace-listings- -- projects- -- pull-requests- -- registry-packages- -- repos- -- showcases- -- topics- -- users- - -### Índices Webhooks - -Después de que el script de migración reconstruye los índices `buscar` necesarios en línea, el script verificará si algún índice `webhook` debe ser reconstruido. Si ejecutas tu aparato con el {% data variables.product.prodname_ghe_server %} 2.12 o 2.13 durante 14 días o más, entonces probablemente no necesitarás que tu índice `webhook` se reconstruya ya que los índices `webhook` tienen una política de retención predeterminada de siete días. Si estás actualizando tu aparato desde el {% data variables.product.prodname_enterprise %} 2.11 o inferior, entonces es posible que debas reconstruir los índices `webhook`. - -Si algún índice `webhook` debe ser reconstruido, entonces se te pedirá habilitar el modo mantenimiento antes de que el script pueda reconstruir los índices `webhook`. A pesar de que migrar los índices `webhook` requiere algo de tiempo de inactividad, no se necesitan grandes ventanas de mantenimiento o tiempo de inactividad. - -Los índices `webhook` comienzan con `hookshot-logs-`. - -### Índices disponibles - -Puedes ver los índices disponibles en tu aparato utilizando cURL. - -``` -admin@ip-172-31-2-141:~$ curl -s http://localhost:9200/_cat/indices?v | sort -n -k 6 -green open blog-1 1 0 0 0 144b 144b -green open projects-1 1 0 0 0 144b 144b -green open registry-packages-1 1 0 0 0 144b 144b -green open showcases-1 1 0 0 0 144b 144b -health status index pri rep docs.count docs.deleted store.size pri.store.size -green open pull-requests-1 1 0 1 0 9.3kb 9.3kb -green open wikis-1 1 0 2 0 5kb 5kb -green open hookshot-logs-2018-05-29 5 0 25 0 124.2kb 124.2kb -green open repos-1 1 0 1638 1 1.4mb 1.4mb -green open gists-1 1 0 3531 64 291.9kb 291.9kb -green open audit_log-1-2018-06-1 1 0 11108 0 3mb 3mb -green open users-1 1 0 19866 56 2.7mb 2.7mb -green open hookshot-logs-2018-05-31 5 0 20000 0 33.4mb 33.4mb -green open hookshot-logs-2018-06-04 5 0 20000 0 32.6mb 32.6mb -green open issues-1 1 0 26405 6 82.8mb 82.8mb -green open hookshot-logs-2018-05-30 5 0 119744 0 196.8mb 196.8mb -green open audit_log-1-2018-05-1 1 0 191664 0 50mb 50mb -green open code-search-1 1 0 6932626 44 42.9gb 42.9gb -green open commits-1 1 0 63753587 1485 45.4gb 45.4gb -``` - -### Preparar un aparato del {% data variables.product.prodname_ghe_server %} 2.12 o 2.13 - -Si actualizas a {% data variables.product.prodname_ghe_server %} 2.14 o superior sin ejecutar las herramientas de migración, los índices Elasticsearch existentes pueden ser inválidos y no funcionarán correctamente. Para ejecutar el script de migración de Elasticsearch, tu aparato del {% data variables.product.prodname_ghe_server %} debe estar ejecutando {% data variables.product.prodname_enterprise %} 2.12 o 2.13. - -{% warning %} - -**Advertencia:** -- Utilizar {% data variables.product.prodname_enterprise_backup_utilities %} destruirá los índices Elasticsearch antiguos no compatibles con 5.X después de la restauración. En este caso, es posible que sea necesaria una nueva indexación manual. -- Si {% data variables.product.prodname_ghe_server %} está configurado para alta disponibilidad, el script de migración **debe** ejecutarse mientras todavía se está ejecutando la replicación. Deben permitirse los cambios para replicar completamente al otro aparato antes de iniciar la actualización. Si la replicación no se está ejecutando mientras se ejecuta el script de migración, tus índices Elasticsearch pueden volverse inválidos. - -{% endwarning %} - -1. Autentícate en el aparato principal con alta disponibilidad habilitado utilizando SSH. -2. Descarga e instala el script de migración en el aparato: - ```shell - $ wget https://github-enterprise.s3.amazonaws.com/util/es-5x-transition-tools.tar.gz - $ sudo tar -C / -xvf es-5x-transition-tools.tar.gz - ``` - Si administras una Agrupación del {% data variables.product.prodname_ghe_server %}, autentica a uno de los nodos de servidores de Elasticsearch utilizando SSH e instala las herramientas de migración allí. Búscalos utilizando: - ```shell - $ ghe-cluster-each -r elasticsearch -p - ghe-test-data-0 - ghe-test-data-1 - ghe-test-data-2 - ``` -2. Ejecuta el script de migración: - ```shell - $ /usr/local/share/enterprise/ghe-es-5x-migration -r - ``` - {% note %} - - **Nota:** Si tiene índices `webhook` para migrar, después de ejecutar las migraciones en línea, se te pedirá que habilites el modo mantenimiento. - - {% endnote %} -3. Si estás ejecutando una Agrupación {% data variables.product.prodname_ghe_server %}, sigue la documentación oficial de actualización para VM únicos o entornos de alta disponibilidad o la guía de actualización de agrupación. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)" o "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)". diff --git a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md b/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md deleted file mode 100644 index 9057e4b6ab..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: Migrar desde GitHub Enterprise 11.10.x a 2.1.23 -redirect_from: - - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123 - - /enterprise/admin-guide/migrating/ - - /enterprise/admin/articles/migrating-github-enterprise/ - - /enterprise/admin/guides/installation/migrating-from-github-enterprise-v11-10-34x/ - - /enterprise/admin/articles/upgrading-to-a-newer-release/ - - /enterprise/admin/guides/installation/migrating-to-a-different-platform-or-from-github-enterprise-11-10-34x/ - - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23 - - /enterprise/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123 - - /admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123 -intro: 'Para migrar desde {% data variables.product.prodname_enterprise %} 11.10.x a 2.1.23, deberás configurar una nueva instancia de aparato y migrar los datos de la instancia anterior.' -versions: - ghes: '*' -topics: - - Enterprise - - Migration - - Upgrades ---- -Se admiten migraciones desde {% data variables.product.prodname_enterprise %} 11.10.348 y superior. No se admiten migraciones desde {% data variables.product.prodname_enterprise %} 11.10.348 o inferior. Primero debes actualizar a 11.10.348 en varias actualizaciones. Para obtener más información, consulta el procedimiento de actualización 11.10.348, "[Actualizar al lanzamiento más reciente](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)." - -Para actualizar a la versión más reciente {% data variables.product.prodname_enterprise %}, primero debes migrar a {% data variables.product.prodname_ghe_server %} 2.1, entonces puedes aplicar el proceso normal de actualización. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)". - -### Prepárate para la migración - -1. Revisa la guía de Abastecimiento e instalación y controla que se cumplan todos los requisitos previos necesarios para abastecer y configurar {% data variables.product.prodname_enterprise %} 2.1.23 en tu entorno. Para obtener más información, consulta "[Abastecimiento e instalación](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)." -2. Verifica que la instancia actual esté ejecutando una versión actualizada compatible. -3. Configura la versión más reciente de {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). - - Si ya has configurado copias de seguridad programadas utilizando {% data variables.product.prodname_enterprise_backup_utilities %}, asegúrate de que hayas actualizado a la versión más reciente. - - Si no estás ejecutando actualmente copias de seguridad programadas, configura {% data variables.product.prodname_enterprise_backup_utilities %}. -4. Toma una instantánea de copia de respaldo completa inicial de la instancia actual utilizando el comando `ghe-backup`. Si ya configuraste copias de seguridad programadas para tu instancia actual, no debes tomar una instantánea de tu instancia. - - {% tip %} - - **Sugerencia:** puedes dejar la instancia en línea y en uso activo durante la instantánea. Tomarás otras instantánea durante la parte de mantenimiento de la migración. Ya que las copias de seguridad son incrementales, esta instantánea inicial reduce la cantidad de datos transferidos en la instantánea final, que pueden acortar la ventana de mantenimiento. - - {% endtip %} - -5. Determina el método para cambiar el tráfico de red de usuario a la nueva instancia. Después de la migración, todo el tráfico de red de HTTP y Git se dirige a la nueva instancia. - - **DNS** - Recomendamos este método para todos los entornos, ya que es simple y funciona bien incluso cuando se migra desde una base de datos a otra. Antes de comenzar la migración, reduce los TTL de los registros DNS existentes a cinco minutos o menos y permite el cambio a propagar. Una vez que la migración se completa, actualiza los registros DNS para que apunten a la dirección IP de la nueva instancia. - - **Asignación de dirección IP** - Este método está únicamente disponible en VMware para la migración VMware y no se recomienda excepto que el método DNS no esté disponible. Antes de comenzar la migración, deberás cerrar la instancia anterior y asignar tu dirección IP a la nueva instancia. -6. Programa una ventana de mantenimiento. La ventana de mantenimiento debe incluir tiempo suficiente para transferir datos desde el servidor de seguridad a la nueva instancia y variará en base al tamaño de la instantánea de respaldo y el ancho de banda de la red disponible. Durante este tiempo tu instancia actual no estará disponible y estará en modo mantenimiento mientras migras a la nueva instancia. - -### Realiza la migración - -1. Aprovisiona una nueva instancia {% data variables.product.prodname_enterprise %} 2.1. Para obtener más información, consulta la "[Guía de aprovisionamiento e instalación](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/)" para tu plataforma destino. -2. Desde un navegador, dirígete a la nueva dirección IP del aparato réplica y carga tu licencia de {% data variables.product.prodname_enterprise %}. -3. Configura una contraseña de administrador. -5. Haz clic en **Migrate (Migrar)**. ![Elegir el tipo de instalación](/assets/images/enterprise/migration/migration-choose-install-type.png) -6. Pega tu clave SSH de acceso al servidor de respaldo en "Add new SSH key (Agregar nueva clave SSH)". ![Autorizar la copia de seguridad](/assets/images/enterprise/migration/migration-authorize-backup-host.png) -7. Da clic en **Agregar llave** y luego en **Continuar**. -8. Copia el comando `ghe-restore` que ejecutarás en el servidor de respaldo para migrar datos a la nueva instancia. ![Iniciar la migración](/assets/images/enterprise/migration/migration-restore-start.png) -9. Habilita el modo mantenimiento en la instancia anterior y espera a que se completen todos los procesos activos. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." - - {% note %} - - **Nota:** la instancia no estará disponible para el uso normal desde este punto en adelante. - - {% endnote %} - -10. En el servidor de respaldo, ejecuta el comando `ghe-backup` para tomar una instantánea de respaldo final. Esto asegura que se capturen todos los datos de la instancia anterior. -11. En el servidor de respaldo, ejecuta el comando `ghe-restore` que copiaste en la pantalla de estado de restauración de la nueva instancia para restaurar la instantánea más reciente. - ```shell - $ ghe-restore 169.254.1.1 - The authenticity of host '169.254.1.1:122' can't be established. - La clave de huella digital RSA es fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1. - ¿Estás seguro que deseas continuar conectado (sí/no)? yes - Connect 169.254.1.1:122 OK (v2.0.0) - Starting restore of 169.254.1.1:122 from snapshot 20141014T141425 - Restoring Git repositories ... - Restaurando las páginas GitHub ... - Restaurando los adjuntos de activo ... - Restaurando las entregas de enlace ... - Restaurando la base de datos MySQL ... - Restaurando la base de datos Redis ... - Restaurando las claves autorizadas de SSH ... - Restaurando los índice de ElasticSearch... - Restaurando las claves del servidor SSH ... - Completed restore of 169.254.1.1:122 from snapshot 20141014T141425 - Visit https://169.254.1.1/setup/settings to review appliance configuration. - ``` - -12. Regresa a la pantalla de estado de restauración de la nueva instancia para ver que la restauración está completa. ![Restaurar la pantalla completa](/assets/images/enterprise/migration/restore-complete-screen.png) -13. Haz clic en **Continue to settings (Continuar a configuraciones)** para revisar y ajustar la información de configuración y los parámetros que se importaron de la instancia anterior. ![Revisar los parámetros importados](/assets/images/enterprise/migration/migration-status-complete.png) -14. Haz clic en **Guardar parámetros**. - - {% note %} - - **Nota:** puedes usar la nueva instancia después de haber aplicado los parámetros de configuración y restaurar el servidor. - - {% endnote %} - -15. Cambia el tráfico de red de usuario desde la instancia anterior a la nueva instancia utilizando la asignación de DNS o la dirección IP. -16. Actualiza a la versión más reciente del lanzamiento del patch de {{ currentVersion }}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md deleted file mode 100644 index e2941f77fe..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Requisitos de actualización -intro: 'Antes de actualizar el {% data variables.product.prodname_ghe_server %}, revisa estas recomendaciones y requisitos para planificar tu estrategia de actualización.' -redirect_from: - - /enterprise/admin/installation/upgrade-requirements - - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release/ - - /enterprise/admin/enterprise-management/upgrade-requirements - - /admin/enterprise-management/upgrade-requirements -versions: - ghes: '*' -topics: - - Enterprise - - Upgrades ---- -{% note %} - -**Notas:** -- Para actualizar desde {% data variables.product.prodname_enterprise %} 11.10.348 a {% data variables.product.current-340-version %}, debes primero migrar a {% data variables.product.prodname_enterprise %} 2.1.23. Para obtener más información, consulta "[Migrar desde {% data variables.product.prodname_enterprise %} 11.10.x a 2.1.23](/enterprise/{{ currentVersion }}/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23)." -- Los paquetes de actualización están disponibles en [enterprise.github.com](https://enterprise.github.com/releases) para las versiones admitidas. Verifica la disponibilidad de los paquetes de actualización, deberás completar la actualización. Si un paquete no está disponible, contacta a {% data variables.contact.contact_ent_support %} para obtener ayuda. -- Si estás usando una Agrupación del {% data variables.product.prodname_ghe_server %}, consulta "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)" en la Guía de Agrupación del {% data variables.product.prodname_ghe_server %} para obtener instrucciones específicas únicas para agrupaciones. -- Estas notas de lanzamiento para el {% data variables.product.prodname_ghe_server %} brindan una lista detallada de las nuevas características de cada versión del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta las [páginas de lanzamiento](https://enterprise.github.com/releases). - -{% endnote %} - -### Recomendaciones - -- Incluye tantas nuevas actualizaciones como sea posible en tu proceso de actualización. Por ejemplo, en lugar de actualizar desde {% data variables.product.prodname_enterprise %} {{ enterpriseVersions.supported[2] }} a {{ enterpriseVersions.supported[1] }} a {{ enterpriseVersions.latest }}, podrías actualizar desde {% data variables.product.prodname_enterprise %} {{ enterpriseVersions.supported[2] }} a {{ enterpriseVersions.latest }}. -- Si estás varias versiones desactualizado, actualiza {% data variables.product.product_location_enterprise %} tanto como sea posible con cada paso de tu proceso de actualización. Utilizar la versión más reciente posible en cada actualización te permite aprovechar las mejoras de desempeño y las correcciones de errores. Por ejemplo, podrías actualizar desde {% data variables.product.prodname_enterprise %} 2.7 a 2.8 a 2.10, pero actualizar desde {% data variables.product.prodname_enterprise %} 2.7 a 2.9 a 2.10 utiliza una versión posterior en el segundo paso. -- Utiliza el lanzamiento de patch más reciente cuando actualices. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} -- Utiliza una instancia de preparación para probar los pasos de actualización. Para obtener más información, consulta "[Configurar una instancia de preparación](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)." -- Cuando ejecutes múltiples actualizaciones, espera por lo menos 24 horas entre las actualizaciones de características para permitir que las tareas de actualización de migraciones de datos y de datos en copias de seguridad se completen en su totalidad. - -### Requisitos - -- Debes actualizar desde una característica de lanzamiento que sea **como máximo** dos lanzamientos anteriores. Por ejemplo, para actualizar a {% data variables.product.prodname_enterprise %} {{ enterpriseVersions.latest }}, debes estar en {% data variables.product.prodname_enterprise %} {{ enterpriseVersions.supported[1] }} o {{ enterpriseVersions.supported[2] }}. -- {% data reusables.enterprise_installation.hotpatching-explanation %} -- Es posible que un hotpatch requiera tiempo de inactividad si los servicios afectados (como kernel, MySQL, o Elasticsearch) requieren un reinicio de VM o un reinicio del servicio. Se te notificará cuando se necesite reiniciar. Puedes completar el reinicio más tarde. -- Es necesario que haya un almacenamiento raíz adicional disponible cuando se actualiza a través de un hotpatch, ya que instala múltiples versiones de determinados servicios hasta que se completa la actualización. El control de prevuelo te notificará si no tienes suficiente almacenamiento de disco raíz. -- Cuando se actualiza a través de un hotpatch, tu instancia no puede estar muy cargada, ya que puede impactar el proceso del hotpatch. Los controles de pre-vuelo considerarán la carga promedio y, posteriormente, la mejora fallará si dicha carga promedio es demasiado alta. - Mejorar a {% data variables.product.prodname_ghe_server %} 2.17 migrará sus registros de auditoría de Elasicsearch a MySQL. Esta migración también incrementa la cantidad de tiempo y el espacio en disco que lleva restaurar una instantánea. Antes de migrar, controla el número de bytes en tus índices de registro de auditoría de ElasticSearch con este comando: -``` shell -curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes -``` -Utiliza el número para estimar la cantidad de espacio de disco que los registros de auditoría de MySQL necesitarán. El script también controla tu espacio libre en disco mientras la importación está en progreso. Controlar este número es especialmente útil si tu espacio libre en disco está cerca de la cantidad de espacio en disco necesaria para la migración. - -Después de revisar estas recomendaciones y requisitos, puedes actualizar el {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Actualizar {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)". diff --git a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md deleted file mode 100644 index cd87a9b6b4..0000000000 --- a/translations/es-XL/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ /dev/null @@ -1,223 +0,0 @@ ---- -title: Actualizar el servidor de GitHub Enterprise -intro: 'Actualizar el {% data variables.product.prodname_ghe_server %} para obtener las funciones y las actualizaciones de seguridad más recientes.' -redirect_from: - - /enterprise/admin/installation/upgrading-github-enterprise-server - - /enterprise/admin/articles/upgrading-to-the-latest-release/ - - /enterprise/admin/articles/migrations-and-upgrades/ - - /enterprise/admin/guides/installation/upgrading-the-github-enterprise-virtual-machine/ - - /enterprise/admin/guides/installation/upgrade-packages-for-older-releases/ - - /enterprise/admin/articles/upgrading-older-installations/ - - /enterprise/admin/hidden/upgrading-older-installations/ - - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch-early-access-program/ - - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch/ - - /enterprise/admin/guides/installation/upgrading-github-enterprise/ - - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server - - /admin/enterprise-management/upgrading-github-enterprise-server -versions: - ghes: '*' -topics: - - Enterprise - - Upgrades ---- -### Preparar para una actualización - -1. Determina una estrategia de actualización y elige una versión a la que actualizar. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." -3. Crea una copia de seguridad nueva de tu instancia principal con las {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta el archivo README.md en [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). -4. Si estás actualizando con un paquete de actualización, programa una ventana de mantenimiento para los usuarios finales del {% data variables.product.prodname_ghe_server %}. Si estás usando un hotpatch, no se necesita el modo mantenimiento. - - {% note %} - - **Nota:** la ventana de mantenimiento depende del tipo de actualización que realices. Las actualizaciones que utilizan un hotpatch por lo general no necesitan una ventana de mantenimiento. A veces se necesita reiniciar; puedes hacerlo más tarde. Siguiendo el esquema de control de versiones de MAJOR.FEATURE.PATCH, los lanzamientos de patch que utilizan un paquete de actualización normalmente necesitan menos de cinco minutos de tiempo de inactividad. Los lanzamientos de funciones que incluyen migraciones de datos toman más tiempo dependiendo del desempeño del almacenamiento y de la cantidad de datos que se migran. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." - - {% endnote %} - -### Tomar una instantánea - -Una instantánea es un punto de verificación de una máquina virtual (VM) en un momento en el tiempo. Recomendamos firmemente tomar una instantánea antes de actualizar tu máquina virtual para que si falla una actualización, puedas revertir tu VM nuevamente a la instantánea. Si no estás actualizando a un nuevo lanzamiento de característica, debes tomar una instantánea de VM. Si estás actualizando a un nuevo lanzamiento de patch, puedes adjuntar el disco de datos existente. - -Hay dos tipos de instantáneas: - -- **Las instantáneas de VM** guardan el estado completo de tu VM, incluidos los datos del usuario y los datos de configuración. Este método de instantáneas requiere una gran cantidad de espacio de disco e insume mucho tiempo. -- **Las instantáneas de disco de datos** únicamente guardan tus datos de usuario. - - {% note %} - - **Notas:** - - Algunas plataformas no permiten que tomes una instantánea solo de tu disco de datos. Para estas plataformas, necesitarás tomar una instantánea de tu VM completa. - - Si tu hipervisor no admite instantáneas de VM completas, debes tomar una instantánea de tu disco raíz y de tu disco de datos en rápida sucesión. - - {% endnote %} - -| Plataforma | Método de instantánea | URL de documentación de instantánea | -| --------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Amazon AWS | Disco | | -| Azure | VM | | -| Hyper-V | VM | | -| Google Compute Engine | Disco | | -| VMware | VM | [https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html](https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html) | -| XenServer | VM | | - -### Actualizar con un hotpatch - -{% data reusables.enterprise_installation.hotpatching-explanation %} Utilizando la {% data variables.enterprise.management_console %}, puedes instalar un hotpatch de forma inmediata o programar la instalación para más tarde. Puedes utilizar el shell administrativo para instalar un hotpatch con la herramienta `ghe-upgrade`. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." - -{% note %} - -**Note**: instalar un hotpatch utilizando la {% data variables.enterprise.management_console %} no está disponible en los entornos de agrupación. Para instalar un parche en un entorno de agrupación, consulta "[Actualizar una agrupación](/enterprise/{{ currentVersion }}/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)." - -{% endnote %} - -#### Actualizar un aparato único con un hotpatch - -##### Instalar un hotpatch utilizando la {% data variables.enterprise.management_console %} - -1. Habilitar actualizaciones automáticas. Para obtener más información, consulta "[Habilitar actualizaciones automáticas](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.updates-tab %} -4. Cuando se ha descargado un nuevo hotpatch, utiliza el menú desplegable del paquete de instalación: - - Para instalar de forma inmediata, selecciona **Now (Ahora)**: - - Para instalarlo más tarde, selecciona una fecha posterior. ![Menú desplegable de fecha de instalación de hotpatch](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png) -5. Da clic en **Instalar**. ![Botón de instalación de hotpatch](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png) - -##### Instalar un hotpatch utilizando un shell administrativo - -{% data reusables.enterprise_installation.download-note %} - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copia el URL para obtener el paquete de actualización (*.hpkg* file). -{% data reusables.enterprise_installation.download-package %} -4. Ejecuta el comando `ghe-upgrade` utilizando el nombre del archivo del paquete: - ```shell - admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.hpkg - *** verifying upgrade package signature... - ``` -5. Si se requiere un reinicio para las actualizaciones de kernel, MySQL, Elasticsearch u otros programas, el script de actualización de hotpatch te avisa. - -#### Actualizar un aparato que tiene instancias de réplica utilizando un hotpatch - -{% note %} - -**Nota**: si estás instalando un hotpatch, no necesitas entrar en modo de mantenimiento o detener la replicación. - -{% endnote %} - -Los aparatos configurados para alta disponibilidad y de replicación geográfica utilizan instancias de réplica además de las instancias principales. Para actualizar estos aparatos, necesitarás actualizar tanto la instancia principal y todas las instancias de réplica, una a la vez. - -##### Actualizar la instancia principal - -1. Actualiza la instancia principal siguiendo las instrucciones en "[Instalar un hotpatch utilizando el shell administrativo](#installing-a-hotpatch-using-the-administrative-shell)." - -##### Actualizar una instancia de réplica - -{% note %} - -**Nota:** si estás ejecutando múltiples instancias de réplica como parte de la replicación geográfica, repite este procedimiento para cada instancia de réplica, una a la vez. - -{% endnote %} - -1. Mejora la instancia de répica siguiendo las instrucciones en "[Instalar un hotpatch utilizando el shell administrativo](#installing-a-hotpatch-using-the-administrative-shell)". Si estás utilizando varias replicas para la replicación geográfica, deberás repetir este procedimiento para actualizar cada réplica una a la vez. -{% data reusables.enterprise_installation.replica-ssh %} -{% data reusables.enterprise_installation.replica-verify %} - -### Actualizar con un paquete de actualización - -Al mismo tiempo que puedes utilizar un hotpatch para actualizar al lanzamiento de patch más reciente dentro de una serie de características, debes utilizar un paquete de actualización para actualizar a un lanzamiento de característica más nuevo. Por ejemplo para actualizar de `2.11.10` a `2.12.4` debes utilizar un paquete de actualización ya que están en series de características diferentes. Para obtener más información, consulta "[Requisitos de actualización](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)." - -#### Actualizar un aparato único con un paquete de actualización - -{% data reusables.enterprise_installation.download-note %} - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Selecciona la plataforma adecuada y copia el URL para obtener el paquete de actualización (*.pkg* file). -{% data reusables.enterprise_installation.download-package %} -4. Habilita el modo mantenimiento y espera que se completen todos los procesos activos en la instancia del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." - - {% note %} - - **Nota**: cuando se actualiza el aparato primario en una configuración de alta disponibilidad, el aparato debería estar ya en modo mantenimiento si estás siguiendo las instrucciones en "[Actualizar la instancia primaria](#upgrading-the-primary-instance)." - - {% endnote %} - -5. Ejecuta el comando `ghe-upgrade` utilizando el nombre del archivo del paquete: - ```shell - admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.pkg - *** verifying upgrade package signature... - ``` -6. Confirma que te gustaría continuar con la actualización y reinicia después de que se verifique la firma del paquete. El nuevo sistema de archivos raíz escribe en la segunda partición y la instancia de forma automática se reinicia en modo mantenimiento: - ```shell - *** aplicando actualización... - This package will upgrade your installation to version version-number - Current root partition: /dev/xvda1 [version-number] - Target root partition: /dev/xvda2 - Proceed with installation? [s/N] - ``` -7. Para las actualizaciones de aparato único, deshabilita el modo mantenimiento para que los usuarios puedan utilizar {% data variables.product.product_location_enterprise %}. - - {% note %} - - **Nota**: cuando se actualizan aparatos en configuración de alta disponibilidad, deberías mantener el modo mantenimiento hasta que hayas actualizado todas las réplicas y la replicación esté en curso. Para obtener más información, consulta "[Actualizar una instancia de réplica](#upgrading-a-replica-instance)." - - {% endnote %} - -#### Actualizar un aparato que tiene instancias de réplica utilizando un paquete de actualización - -Los aparatos configurados para alta disponibilidad y de replicación geográfica utilizan instancias de réplica además de las instancias principales. Para actualizar estos aparatos, necesitarás actualizar tanto la instancia principal y todas las instancias de réplica, una a la vez. - -##### Actualizar la instancia principal - -{% warning %} - -**Advertencia:** Cuando se detiene una replicación, si falla la primaria, se perderá cualquier trabajo que se realice antes de que la réplica esté actualizada y comience nuevamente la replicación. - -{% endwarning %} - -1. En la instancia primaria, habilita el modo mantenimiento y espera a que se completen todos los procesos activos. Para obtener más información, consulta "[Habilitar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)." -{% data reusables.enterprise_installation.replica-ssh %} -3. En la instancia de réplica, o en todas las instancias de réplica si estás ejecutando múltiples instancias de réplica como parte de una replicación geográfica, ejecuta `ghe-repl-stop` para detener la replicación. -4. Actualiza la instancia primaria siguiendo las instrucciones en "[Actualizar un aparato único con un paquete de actualización](#upgrading-a-single-appliance-with-an-upgrade-package)." - -##### Actualizar una instancia de réplica - -{% note %} - -**Nota:** si estás ejecutando múltiples instancias de réplica como parte de la replicación geográfica, repite este procedimiento para cada instancia de réplica, una a la vez. - -{% endnote %} - -1. Actualiza la instancia de la réplica siguiendo las instrucciones en la sección "[Mejorar un solo aplicativo con un paquete de mejora](#upgrading-a-single-appliance-with-an-upgrade-package)". Si estás utilizando varias replicas para la replicación geográfica, deberás repetir este procedimiento para actualizar cada réplica una a la vez. -{% data reusables.enterprise_installation.replica-ssh %} -{% data reusables.enterprise_installation.replica-verify %} - -{% data reusables.enterprise_installation.start-replication %} - -{% data reusables.enterprise_installation.replication-status %} Si el comando devuelve `La replicación no se está ejecutando`, la replicación puede estar comenzando. Espera alrededor de un minuto antes de volver a ejecutar `ghe-repl-status`. - - {% note %} - - **Nota:** mientras la resincronización está en progreso, `ghe-repl-status` puede devolver mensajes esperados que indiquen que la replicación está de forma subyacente. - Por ejemplo: `CRITICO: la replicación de git está de forma subyacente de la primaria por más de 1007 repositorios o gists` - - {% endnote %} - - Si `ghe-repl-status` no devuelve `OK`, sigue los pasos de abajo para iniciar la replicación de forma manual. - - 1. En la instancia de réplica, ejecuta nuevamente `ghe-repl-setup `. - {% data reusables.enterprise_installation.start-replication %} - {% data reusables.enterprise_installation.replication-status %} -6. Cuando hayas completado la actualización de la última réplica, y se haya completado la resincronización, deshabilita el modo mantenimiento para que los usuarios puedan utilizar {% data variables.product.product_location_enterprise %}. - -### Restaurar desde una actualización fallida - -Si una actualización falla o se interrumpe, deberías revertir tu instancia a su estado anterior. El proceso para completar esto depende del tipo de actualización. - -#### Revertir un lanzamiento de patch - -Para volver a lanzar una versión de parche, usa el comando `ghe-upgrade` con el comando `--allow-patch-rollback` switch. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} - -Para obtener más información, consulta "[Herramientas de línea de comando](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-upgrade)." - -#### Revertir un lanzamiento de característica - -Para revertir un lanzamiento de característica, restaura desde una instantánea de VM para garantizar que las particiones raíz y de datos estén en un estado consistente. Para obtener más información, consulta "[Tomar una instantánea](#taking-a-snapshot)." diff --git a/translations/es-XL/content/admin/enterprise-support/index.md b/translations/es-XL/content/admin/enterprise-support/index.md deleted file mode 100644 index bac599c11d..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: 'Trabajar con {% data variables.contact.github_support %}' -intro: 'Aprende a abrir un ticket y proporciona al equipo de {% data variables.contact.enterprise_support %} la información que necesitan para resolver tus problemas.' -redirect_from: - - /enterprise/admin/enterprise-support -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /overview - - /receiving-help-from-github-support ---- -### Índice diff --git a/translations/es-XL/content/admin/enterprise-support/overview/about-github-enterprise-support.md b/translations/es-XL/content/admin/enterprise-support/overview/about-github-enterprise-support.md deleted file mode 100644 index 23ebc76d02..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/overview/about-github-enterprise-support.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Acerca del soporte de GitHub Enterprise -intro: 'El soporte de {% data variables.product.prodname_ghe_server %} puede ayudarte a resolver problemas que surjan en tu aparato {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/enterprise-support/about-github-enterprise-support - - /admin/enterprise-support/about-github-enterprise-support -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Support ---- -{% note %} - -**Nota**: {% data reusables.support.data-protection-and-privacy %} - -{% endnote %} - -### Acerca de {% data variables.contact.enterprise_support %} - -{% data variables.product.prodname_ghe_server %} incluye {% data variables.contact.enterprise_support %} en inglés y japonés. - -Puedes ponerte en contacto con {% data variables.contact.enterprise_support %} a través de nuestro portal de soporte para que te ayude con: - - Instalar y usar {% data variables.product.prodname_ghe_server %} - - Inspeccionar y verificar las causas de errores sospechados - -Además de todos los beneficios de {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} ofrece: - - 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 - - Acceso a contenido prémium - - Revisiones de estado programadas - - Servicios administrados. - -Para obtener más información, consulta "[Acerca de{% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". - -{% data reusables.support.scope-of-support %} - -### Ponerte en contacto con {% data variables.contact.enterprise_support %} - -Los clientes de {% data variables.contact.enterprise_support %} pueden utilizar el {% data variables.contact.contact_enterprise_portal %} para reportar problemas por escrito. - -### Horas de operación - -#### Soporte en inglés - -Para cuestiones estándar no urgentes, ofrecemos soporte en inglés las 24 horas del día, 5 días a la semana, excepto fines de semana y feriados nacionales en EE.○UU. holidays. El tiempo de respuesta estándar es 24 horas. - -Para asuntos urgentes, estamos disponibles las 24 horas del día, 7 días a la semana, incluso en días feriados de los EE.UU. holidays. - -#### Soporte en japonés - -Para cuestiones no urgentes, el soporte en japonés se encuentra disponible de lunes a viernes, de 9:00 a.m. a 5:00 p.m. (hora estándar en Japón), excepto los feriados nacionales en Japón. Para cuestiones urgentes, ofrecemos apoyo en inglés 24 horas al día, 7 días por semana, incluso durante las vacaciones nacionales de los Estados Unidos. holidays. - -For a complete list of U.S. Para conocer una lista de los feriados nacionales de EE. UU. y Japón observados por {% data variables.contact.enterprise_support %}, consulta el [Cronograma de feriados](#holiday-schedules)". - -### Cronograma de feriados - -For urgent issues, we can help you in English 24 hours per day, 7 days per week, including on U.S. and Japanese holidays. - -#### Feriados en los Estados Unidos - -{% data variables.contact.enterprise_support %} observa estos días festivos en Estados Unidos. {% data variables.contact.enterprise_support %} respeta estos días feriados en los EE.UU, aunque nuestro equipo de soporte global se encuentra disponible para atender tickets urgentes. - -| U.S. holiday | Festejado | -| --------------------------------- | --------------------------- | -| Año Nuevo | 1 de enero | -| Día de Martin Luther King, Jr. | Tercer lunes de enero | -| Día de los Presidentes | Tercer lunes de febrero | -| Día de los Caídos | Último lunes de mayo | -| Día de la Independencia | 4 de julio | -| Día del Trabajo | Primer lunes de septiembre | -| Día de los Veteranos | 12 de noviembre | -| Día de Acción de Gracias | Cuarto jueves de noviembre | -| Día posterior a Acción de Gracias | Cuarto viernes de noviembre | -| Nochebuena | 24 de diciembre | -| Día de Navidad | 25 de diciembre | -| Día posterior a Navidad | 26 de diciembre | -| Víspera de Año Nuevo | 31 de diciembre | - -#### Feriados en Japón - -{% data variables.contact.enterprise_support %} no proporciona soporte en idioma japonés desde el 28 de diciembre hasta el 3 de enero, así como en los días feriados listados en [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html). - -{% data reusables.enterprise_enterprise_support.installing-releases %} - -### Asignar una prioridad a un ticket de soporte - -Cuando contactas a {% data variables.contact.enterprise_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. - -{% data reusables.support.github-can-modify-ticket-priority %} - -{% data reusables.support.ghes-priorities %} - -### Resolver y cerrar tickets de soporte - -{% data reusables.support.enterprise-resolving-and-closing-tickets %} - -### Leer más - -- [Preguntas frecuentes sobre {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/faq) -- Sección 10 sobre Soporte en el "[Acuerdo de licencia de {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/license)" -- [Ibtener{% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/reaching-github-support)" -- [Prepararse para enviar un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)" -- [Enviar un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)" diff --git a/translations/es-XL/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md b/translations/es-XL/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md deleted file mode 100644 index 48bf46d8b1..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Acerca del Soporte prémium de GitHub para GitHub Enterprise Server -intro: 'El {% data variables.contact.premium_support %} es una oferta de soporte paga complementaria para clientes de {% data variables.product.prodname_enterprise %}.' -redirect_from: - - /enterprise/admin/guides/enterprise-support/about-premium-support-for-github-enterprise/ - - /enterprise/admin/guides/enterprise-support/about-premium-support/ - - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server - - /admin/enterprise-support/about-github-premium-support-for-github-enterprise-server -versions: - ghes: '*' -topics: - - Enterprise - - Support ---- -{% note %} - -**Notas:** - -- Los términos del {% data variables.contact.premium_support %} están sujetos a cambios sin aviso y entraron en vigencia a partir de septiembre de 2018. Si compraste el {% data variables.contact.premium_support %} antes del 17 de septiembre de 2018, tu plan puede ser diferente. Comunícate con el {% data variables.contact.premium_support %} para conocer más detalles. - -- {% data reusables.support.data-protection-and-privacy %} - -- Este artículo contiene los términos del {% data variables.contact.premium_support %} para clientes del {% data variables.product.prodname_ghe_server %}. Es posible que los términos sean diferentes para los clientes de la {% data variables.product.prodname_ghe_cloud %} o para los clientes de {% data variables.product.prodname_enterprise %} que adquieran el {% data variables.product.prodname_ghe_server %} y la {% data variables.product.prodname_ghe_cloud %} de manera conjunta. Para más información, vea "Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}" y "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise)." - -{% endnote %} - -### Acerca del {% data variables.contact.premium_support %} - -Además de todos los beneficios de {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} ofrece: - - Soporte técnico por escrito, en inglés, a través del portal de soporte de 24 horas al día, 7 días a la semana. - - Soporte técnico telefónico, en inglés, 24 horas al día, 7 días a la semana. - - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados - - Acceso a contenido prémium - - Revisiones de estado programadas - - Servicios administrados. - -{% data reusables.support.about-premium-plans %} - -{% data reusables.support.signing-up-for-premium-support %} - -{% data reusables.support.scope-of-support %} Para obtener más información, consulta el "[Reaching {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)" (Obtener soporte del {% data variables.product.prodname_ghe_server %}). - -{% data reusables.support.contacting-premium-support %} - -### Horas de operación - -{% data variables.contact.premium_support %} está disponible las 24 horas del día, los 7 días de la semana. Si compraste el {% data variables.contact.premium_support %} antes del 17 de septiembre de 2018, el soporte será limitado durante los feriados. Para más información sobre los días festivos que respeta el {% data variables.contact.premium_support %}, consulta la lista de feriados en "[Acerca del {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)". - -{% data reusables.support.service-level-agreement-response-times %} - -{% data reusables.enterprise_enterprise_support.installing-releases %} - -Debes instalar la versión mínima compatible del {% data variables.product.prodname_ghe_server %}, conforme a la sección Versiones compatibles del acuerdo de licencia aplicable, dentro de los 90 días posteriores a realizar el pedido del {% data variables.contact.premium_support %}. - -### Asignar una prioridad a un ticket de soporte - -Cuando contactas a {% data variables.contact.premium_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. - -{% data reusables.support.github-can-modify-ticket-priority %} - -{% data reusables.support.ghes-priorities %} - -### Resolver y cerrar tickets de soporte - -{% data reusables.support.premium-resolving-and-closing-tickets %} - -{% data reusables.support.receiving-credits %} - -{% data reusables.support.accessing-premium-content %} diff --git a/translations/es-XL/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise.md b/translations/es-XL/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise.md deleted file mode 100644 index dfd891cb9a..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Acerca del soporte prémium de GitHub para GitHub Enterprise -intro: 'El {% data variables.contact.premium_support %} es una oferta de soporte paga complementaria para clientes de {% data variables.product.prodname_enterprise %}.' -redirect_from: - - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise - - /admin/enterprise-support/about-github-premium-support-for-github-enterprise -versions: - ghes: '*' -topics: - - Enterprise - - Support ---- -{% note %} - -**Notas:** - -- Los términos de {% data variables.contact.premium_support %} están sujetos a cambios sin aviso y están vigentes a partir de julio de 2019. - -- {% data reusables.support.data-protection-and-privacy %} - -- Este artículo contiene los términos de {% data variables.contact.premium_support %} para clientes de {% data variables.product.prodname_enterprise %} que compran {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} de manera conjunta. Los términos de {% data variables.contact.premium_support %} pueden ser diferentes para los clientes que compran cada producto por separado. Para más información, vea "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)" y "Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}." - -{% endnote %} - -### Acerca del {% data variables.contact.premium_support %} - -Además de todos los beneficios de {% data variables.contact.enterprise_support %}, {% data variables.contact.premium_support %} ofrece: - - Soporte técnico por escrito, en inglés, a través del portal de soporte de 24 horas al día, 7 días a la semana. - - Soporte técnico telefónico, en inglés, 24 horas al día, 7 días a la semana. - - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados - - Acceso a contenido prémium - - Revisiones de estado programadas - - Servicios administrados. - -{% data reusables.support.about-premium-plans %} - -{% data reusables.support.signing-up-for-premium-support %} - -{% data reusables.support.scope-of-support %} Para obtener más información, consulta el "[Reaching {% data variables.product.prodname_ghe_server %} Support](/enterprise/admin/guides/enterprise-support/reaching-github-support)" (Obtener soporte del {% data variables.product.prodname_ghe_server %}). - -{% data reusables.support.contacting-premium-support %} - -### Horas de operación - -{% data variables.contact.premium_support %} está disponible las 24 horas del día, los 7 días de la semana. - -{% data reusables.support.service-level-agreement-response-times %} - -{% data reusables.enterprise_enterprise_support.installing-releases %} - -Debes instalar la versión mínima compatible del {% data variables.product.prodname_ghe_server %}, conforme a la sección Versiones compatibles del acuerdo de licencia aplicable, dentro de los 90 días posteriores a realizar el pedido del {% data variables.contact.premium_support %}. - -### Asignar una prioridad a un ticket de soporte - -Cuando contactas a {% data variables.contact.premium_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. - -- [Prioridades de tickets para {% data variables.product.prodname_ghe_cloud %}](#ticket-priorities-for-github-enterprise-cloud) -- [Prioridades de tickets para {% data variables.product.prodname_ghe_server %}](#ticket-priorities-for-github-enterprise-server) - -#### Prioridades de tickets para {% data variables.product.prodname_ghe_cloud %} - -{% data reusables.support.ghec-premium-priorities %} - -#### Prioridades de tickets para {% data variables.product.prodname_ghe_server %} - -{% data reusables.support.ghes-priorities %} - -### Resolver y cerrar tickets de soporte - -{% data reusables.support.premium-resolving-and-closing-tickets %} - -{% data reusables.support.receiving-credits %} - -{% data reusables.support.accessing-premium-content %} diff --git a/translations/es-XL/content/admin/enterprise-support/overview/about-support-for-advanced-security.md b/translations/es-XL/content/admin/enterprise-support/overview/about-support-for-advanced-security.md deleted file mode 100644 index 8f64fae49d..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/overview/about-support-for-advanced-security.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Acerca del soporte para Advanced Security -intro: '{% data variables.contact.enterprise_support %} puede ayudarte a solucionar problemas que encuentras mientras usas {% data variables.product.prodname_advanced_security %}.' -redirect_from: - - /enterprise/admin/enterprise-support/about-support-for-advanced-security - - /admin/enterprise-support/about-support-for-advanced-security -versions: - ghes: '*' -topics: - - Enterprise - - Support ---- -{% note %} - -**Nota**: {% data reusables.support.data-protection-and-privacy %} - -{% endnote %} - -### Acerca del soporte para {% data variables.product.prodname_advanced_security %} - -{% data variables.product.prodname_advanced_security %} incluye {% data variables.contact.enterprise_support %} en inglés, por correo electrónico. - -### Alcance del soporte técnico - -Si tu solicitud de soporte técnico está fuera del alcance de lo que puede hacer nuestro equipo para ayudarte, podemos recomendarte los siguientes pasos para resolver el problema por fuera del {% data variables.contact.enterprise_support %}. Es probable que tu solicitud de soporte técnico esté fuera del alcance del {% data variables.contact.enterprise_support %} si se trata principalmente de lo siguiente: -- Integraciones de terceros -- Configuración del hardware -- Configuración de sistemas externos -- Proyectos de código abierto -- Creando proyectos o repositorios -- Diseño de cluster LGTM -- Crear o depurar el código de nuevas consultas para {% data variables.product.prodname_codeql %} - -Si no estás seguro de si el problema está fuera de nuestro alcance, abre un ticket y nos complacerá ayudarte a determinar la mejor manera de continuar. - -### Ponerte en contacto con {% data variables.contact.enterprise_support %} - -Puedes ponerte en contacto con {% data variables.contact.enterprise_support %} a través de {% data variables.contact.contact_enterprise_portal %} para obtener ayuda: -- Instalar y usar {% data variables.product.prodname_advanced_security %} -- Identificar y verificar las causas de los errores soportados - -### Horas de operación - -Ofrecemos soporte para {% data variables.product.prodname_advanced_security %} en Inglés 24 horas al día, 5 días a la semana, excluyendo fines de semana y días festivos en Estados Unidos. holidays. El tiempo de respuesta estándar es de 1 día hábil. - -### Cronograma de feriados - -{% data variables.contact.enterprise_support %} observa estos días festivos en Estados Unidos. holidays. - -| U.S. holiday | Fecha observada en 2018 | -| --------------------------------- | --------------------------- | -| Año Nuevo | 1 de enero | -| Día de Martin Luther King, Jr. | Tercer lunes de enero | -| Día de los Presidentes | Tercer lunes de febrero | -| Día de los Caídos | Último lunes de mayo | -| Día de la Independencia | 4 de julio | -| Día del Trabajo | Primer lunes de septiembre | -| Día de los Veteranos | 12 de noviembre | -| Día de Acción de Gracias | Cuarto jueves de noviembre | -| Día posterior a Acción de Gracias | Cuarto viernes de noviembre | -| Nochebuena | 24 de diciembre | -| Día de Navidad | 25 de diciembre | -| Día posterior a Navidad | 26 de diciembre | -| Víspera de Año Nuevo | 31 de diciembre | - -### Instalando actualizaciones de {% data variables.product.prodname_advanced_security %} - -Para asegurarse de que su instancia {% data variables.product.prodname_advanced_security %} es estable, debe instalar e implementar nuevas versiones cuando estén disponibles. Esto asegura que tengas las últimas características, modificaciones y mejoras así como cualquier actualización de las características, correcciones de código, parches u otras actualizaciones generales y correcciones para {% data variables.product.prodname_advanced_security %}. - -### Asignar una prioridad a un ticket de soporte - -Cuando contactas a {% data variables.contact.enterprise_support %} para obtener ayuda con {% data variables.product.prodname_advanced_security %}, puedes escoger una de tres prioridades para el ticket: {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. - -{% data reusables.support.github-can-modify-ticket-priority %} - -| Prioridad | Descripción | -|:------------------------------------------------------------------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% data variables.product.support_ticket_priority_high %} | {% data variables.product.prodname_advanced_security %} no funciona o se detiene o se ve gravemente afectado de tal manera que el usuario final no puede seguir utilizando el software razonablemente y no hay solución disponible para solucionar el problema. | -| {% data variables.product.support_ticket_priority_normal %} | {% data variables.product.prodname_advanced_security %} está funcionando de forma inconsistente, lo que provoca un deterioro de la productividad y el uso del usuario final. | -| {% data variables.product.support_ticket_priority_low %} | {% data variables.product.prodname_advanced_security %} funciona consistentemente, pero el usuario final solicita cambios menores en el software, tales como actualizaciones de documentación, defectos cosméticos o mejoras. | - -### Resolver y cerrar tickets de soporte - -{% data reusables.support.enterprise-resolving-and-closing-tickets %} diff --git a/translations/es-XL/content/admin/enterprise-support/overview/index.md b/translations/es-XL/content/admin/enterprise-support/overview/index.md deleted file mode 100644 index e33edd2efa..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/overview/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Resumen -intro: 'Conoce las opciones de soporte disponibles para {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/enterprise-support/overview -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /about-github-enterprise-support - - /about-github-premium-support-for-github-enterprise-server - - /about-github-premium-support-for-github-enterprise - - /about-support-for-advanced-security ---- - diff --git a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/index.md b/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/index.md deleted file mode 100644 index 8f4cb0a7a4..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Recibir ayuda desde Soporte de GitHub -intro: 'Si tienes problemas con {% data variables.product.product_location_enterprise %}, {% data variables.contact.github_support %} puede ayudarte.' -redirect_from: - - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support/ - - /enterprise/admin/enterprise-support/receiving-help-from-github-support -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /reaching-github-support - - /preparing-to-submit-a-ticket - - /submitting-a-ticket - - /providing-data-to-github-support ---- - diff --git a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket.md b/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket.md deleted file mode 100644 index a0fbeb7b7b..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Prepararse para enviar un ticket -intro: 'La ayuda de {% data variables.contact.github_support %} te permitirá acelerar al seguir estas sugerencias antes de abrir un ticket de respaldo.' -redirect_from: - - /enterprise/admin/enterprise-support/preparing-to-submit-a-ticket - - /admin/enterprise-support/preparing-to-submit-a-ticket -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Support ---- -Antes de enviar un ticket, deberías: - -- Obtener información que pueda ayudar a que {% data variables.contact.github_support %} rastree, priorice, reproduzca o investigue el problema. -- Reproducir el problema, en caso de que sea posible, y prepararte para compartir los pasos. -- Estar preparado para brindar una descripción completa de la propuesta y los resultados esperados. -- Copiar de manera exacta, palabra por palabra, todos los mensajes del error relacionados con tu problema. -- Determinar si existe un número de ticket en cualquier comunicación con {% data variables.contact.github_support %} que se encuentre en curso. -- Determinar la mejor persona para ponerse en contacto {% data variables.contact.github_support %}. - -Para obtener más información, consulta "[Enviar un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". - -### Elegir una persona de contacto - -Especialmente para los tickets con prioridad {% data variables.product.support_ticket_priority_urgent %}, la persona que contacte a {% data variables.contact.github_support %} deberá: - - - Tener conocimiento de tus sistemas internos, herramientas, políticas y prácticas. - - Ser un usuario experto de {% data variables.product.prodname_ghe_server %}. - - Tener acceso y permisos completos a cualquier servicio que se requiera para solucionar los problemas en cuestión. - - Estar autorizado para realizar los cambios recomendados a tu red y a todos los productos aplicables. diff --git a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md b/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md deleted file mode 100644 index 5f773eaec4..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -title: Proporcionar datos al soporte de GitHub -intro: 'Dado que {% data variables.contact.github_support %} no tiene acceso a tu entorno, te solicitaremos información adicional.' -redirect_from: - - /enterprise/admin/guides/installation/troubleshooting/ - - /enterprise/admin/articles/support-bundles/ - - /enterprise/admin/guides/enterprise-support/providing-data-to-github-enterprise-support/ - - /enterprise/admin/enterprise-support/providing-data-to-github-support - - /admin/enterprise-support/providing-data-to-github-support -versions: - ghes: '*' -topics: - - Enterprise - - Support ---- -### Crear y compartir archivos de diagnóstico - -Los diagnósticos son una descripción general de los parámetros de una instancia de {% data variables.product.prodname_ghe_server %} y del entorno que contiene: - -- Información de licencia de cliente, incluido el nombre de la empresa, fecha de validez y cantidad de licencias de usuario -- Números de versión y SHAs -- Arquitectura VM -- Nombre de host, modo privado, entorno de SSL -- Cargar y procesar listas -- Parámetros de red -- Método y detalles de autenticación -- Número de repositorios, usuarios y otros datos de instalación - -Puedes descargar el diagnóstico para tu instancia desde la {% data variables.enterprise.management_console %} o al ejecutar la utilidad de la línea de comando `ghe-diagnostics`. - -#### Crear un archivo de diagnóstico desde {% data variables.enterprise.management_console %} - -Puedes usar este método si no tienes tu clave SSH fácilmente disponible. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.type-management-console-password %} -{% data reusables.enterprise_management_console.support-link %} -5. Haz clic en **Download diagnostics info** (Descargar información de diagnóstico). - -#### Crear un archivo de diagnóstico mediante SSH - -Puedes usar este método sin iniciar sesión en {% data variables.enterprise.management_console %}. - -Usa la utilidad de la línea de comando [ghe-diagnostics](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-diagnostics) para recuperar el diagnóstico para tu instancia. - -```shell -$ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt -``` - -### Crear y compartir paquetes de soporte - -Después de que emites tu solicitud de soporte, podríamos pedirte que compartas un paquete de soporte con nuestro equipo. El paquete de soporte es un archivo tar comprimido en gzip que incluye diagnósticos y registros importantes desde tu instancia, como: - -- Registros relacionados con la autenticación que pueden resultar útiles al solucionar problemas de errores de autenticación, o configurar LDAP, CAS o SAML -- Registro {% data variables.enterprise.management_console %} -- `github-logs/exceptions.log`: Información sobre 500 errores encontrados en el sitio -- `github-logs/audit.log`: registros de auditoría {% data variables.product.prodname_ghe_server %} -- `babeld-logs/babeld.log`: registros proxy Git -- `system-logs/haproxy.log`: registros HAProxy -- `elasticsearch-logs/github-enterprise.log`: registros Elasticsearch -- `configuration-logs/ghe-config.log`: registros de configuración {% data variables.product.prodname_ghe_server %} -- `collectd/logs/collectd.log`: registros Collectd -- `mail-logs/mail.log`: registros de entrega por correo electrónico SMTP -- `hookshot-logs/exceptions.log`: errores de entrea de Webhook - -Para obtener más información, consulta "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging) (Registro de auditoría". - -Los paquetes de soporte incluyen registros de los dos últimos días. Para obtener registros de los últimos siete días, puedes descargar un paquete de soporte extendido. Para obtener más información, consulta "[Crear y compartir paquete de soporte extendido](#creating-and-sharing-extended-support-bundles)". - -{% tip %} - -**Sugerencias:** Cuando te comuniques con {% data variables.contact.github_support %}, recibirás un correo electrónico de confirmación con un enlace de referencia del ticket. Si {% data variables.contact.github_support %} te pide que cargues un paquete de soporte, puedes usar el enlace de referencia del ticket para cargar el paquete de soporte. - -{% endtip %} - -#### Crear un paquete de soporte desde la {% data variables.enterprise.management_console %} - -Puedes usar estos pasos para crear y compartir un paquete de soporte si puedes acceder a la {% data variables.enterprise.management_console %} basada en la web y tienes acceso a internet de salida. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.type-management-console-password %} -{% data reusables.enterprise_management_console.support-link %} -5. Haz clic en **Download support bundle** (Descargar paquete de soporte). -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} -{% data reusables.enterprise_enterprise_support.upload-support-bundle %} - -#### Crear un paquete de soporte mediante SSH - -Puedes usar estos pasos para crear y compartir un paquete de soporte si tienes acceso a SSH para tu aparato {% data variables.product.prodname_ghe_server %} y tiene acceso a Internet de salida. - -{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} - -1. Descargar el paquete de soporte mediante SSH: - ```shell - $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz - ``` - Para obtener más información acerca del comando `ghe-support-bundle`, consulta "[Utilidades de la línea de comandos](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)". -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} -{% data reusables.enterprise_enterprise_support.upload-support-bundle %} - -#### Cargar un paquete de soporte utilizando tu cuenta empresarial - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.enterprise-licensing-tab %} -4. Debajo de "Ayuda de {% data variables.product.prodname_enterprise %}", da clic en **Cargar un paquete de soporte**. ![Carga un enlace al paquete de soporte](/assets/images/enterprise/support/upload-support-bundle.png) -5. Debajo de "Selecciona una cuenta empresarial", selecciona la cuenta asociada al paquete de soporte del menú desplegable. ![Elige la cuenta empresarial del paquete de soporte](/assets/images/enterprise/support/support-bundle-account.png) -6. Debajo de "Cargar un paquete de soporte para {% data variables.contact.enterprise_support %}", para seleccionar tu paquete de soporte, da clic en **Elegir archivo**, o arrastra tu archivo de paquete de soporte hacia **Escoger archivo**. ![Cargar archivo de paquete de soporte](/assets/images/enterprise/support/choose-support-bundle-file.png) -7. Da clic en **Cargar**. - -#### Cargar paquete de soporte mediante SSH - -Puedes cargar directamente un paquete de soporte a nuestro servidor si: -- Tienes acceso a SSH para tu aparato {% data variables.product.prodname_ghe_server %}. -- Las conexiones HTTPS de salida sobre el puerto TCP 443 están permitidas desde tu aparato {% data variables.product.prodname_ghe_server %}. - -1. Cargar el paquete a nuestro servidor de paquete de soporte: - ```shell - $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u' - ``` - -### Crear y compartir paquetes de soporte extendido - -Los paquetes de soporte incluyen registros de los últimos dos días, mientras que los paquetes de soporte _extendidos_ incluyen registros de los últimos siete días. Si los eventos que {% data variables.contact.github_support %} estás investigando se produjeron hace más de dos días, es posible que te pidamos que compartas un paquete de soporte extendido. Deberás tener acceso a SSH para descargar un soporte extendido, no puedes descargar un paquete extendido desde {% data variables.enterprise.management_console %}. - -Para evitar que los paquetes sean demasiado grandes, solo pueden contener registros que no hayan sido rotados y comprimidos. La rotación de los registros en {% data variables.product.prodname_ghe_server %} se produce en diferentes frecuencias (diarias o semanales) para los diferentes archivos de registro, según el tamaño que pretendamos que tengan los registros. - -#### Crear un paquete de soporte extendido mediante SSH - -Puedes usar estos pasos para crear y compartir un paquete de soporte extendido si tienes acceso a SSH para tu aparato {% data variables.product.prodname_ghe_server %} y tienes acceso a internet de salida. - -1. Descarga el paquete de soporte extendido mediante SSH al agregar el marcador `-x` al comando `ghe-support-bundle`: - ```shell - $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o -x' > support-bundle.tgz - ``` -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} -{% data reusables.enterprise_enterprise_support.upload-support-bundle %} - -#### Cargar un paquete de soporte extendido directamente usando SSH - -Puedes cargar directamente un paquete de soporte a nuestro servidor si: -- Tienes acceso a SSH para tu aparato {% data variables.product.prodname_ghe_server %}. -- Las conexiones HTTPS de salida sobre el puerto TCP 443 están permitidas desde tu aparato {% data variables.product.prodname_ghe_server %}. - -1. Cargar el paquete a nuestro servidor de paquete de soporte: - ```shell - $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u -x' - ``` - -### Leer más - -- "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)" -- "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". diff --git a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md b/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md deleted file mode 100644 index cf2ac62bb8..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Obtener soporte de GitHub -intro: 'Comunícate con {% data variables.contact.github_support %} mediante el {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} o el portal de soporte.' -redirect_from: - - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support/ - - /enterprise/admin/enterprise-support/reaching-github-support - - /admin/enterprise-support/reaching-github-support -versions: - ghes: '*' -topics: - - Enterprise - - Support ---- -### Usar sistemas de tickets automatizado - -Si bien haremos todo lo mejor por responder a solicitudes de soporte automatizado, habitualmente necesitamos más información que un sistema de tickets automatizado que nos permita resolver tu problema. Siempre que sea posible, inicia las solicitudes de soporte de una persona o una máquina con la que {% data variables.contact.github_support %} pueda interactuar. Para obtener más información, consulta "[Prepararse para enviar un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)". - -### Ponerte en contacto con {% data variables.contact.enterprise_support %} - -Los clientes de {% data variables.contact.enterprise_support %} pueden abrir un ticket de soporte mediante {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} o {% data variables.contact.contact_enterprise_portal %}. Marca la prioridad del ticket como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. Para obtener más información, consulta la sección "[Asignar una prioridad al ticket de soporte](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)" y "[Emitir un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". - -#### Ver tickets de soporte anteriores - -Puedes usar el {% data variables.contact.enterprise_portal %} para ver tickets de soporte anteriores. - -1. Navega por el {% data variables.contact.contact_enterprise_portal %}. -2. Da clic en **Mist tickets**. ![Ver los tickets emitidos anteriormente](/assets/images/enterprise/support/view-past-tickets.png) - -### Comunicarse con {% data variables.contact.premium_support %} - -Los clientes de {% data variables.contact.enterprise_support %} pueden abrir un ticket de soporte mediante {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} o {% data variables.contact.contact_enterprise_portal %}. Marca su prioridad como {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o {% data variables.product.support_ticket_priority_low %}. Para obtener más información, consulta la sección "[Asignar una prioridad al ticket de soporte](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server#assigning-a-priority-to-a-support-ticket)" y "[Emitir un ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)". - -### Contacto de ventas - -Para las preguntas relacionadas con precios, licenciamiento, renovaciones, cotizaciones, pagos y otras relacionadas, contacta a {% data variables.contact.contact_enterprise_sales %} o llama al [+1 (877) 448-4820](tel:+1-877-448-4820). - -### Contacto de capacitación - -Para conocer más sobre las opciones de capacitación, incluida la capacitación personalizada, consulta el sitio de capacitación de [{% data variables.product.company_short %}](https://services.github.com/). - -{% note %} - -**Nota:** La capacitación está incluida en el {% data variables.product.premium_plus_support_plan %}. Para obtener más información, consulta "[Acerca de{% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". - -{% endnote %} - -### Leer más - -- "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)" -- "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". diff --git a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md b/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md deleted file mode 100644 index 3bee4a9df9..0000000000 --- a/translations/es-XL/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Emitir un ticket -intro: 'Enviar un ticket de soporte mediante el {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} o el portal de soporte. Puedes marcar un ticket como urgente cuando tu sistema de producción {% data variables.product.prodname_ghe_server %} esté caído o en un estado inutilizable.' -redirect_from: - - /enterprise/admin/enterprise-support/submitting-a-ticket - - /admin/enterprise-support/submitting-a-ticket -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Support ---- -### Acerca del envío de tickets - -Antes de enviar un ticket, deberías recopilar información útil para {% data variables.contact.github_support %} y elegir una persona de contacto. Para obtener más información, consulta "[Prepararse para enviar un ticket](/enterprise/admin/guides/enterprise-support/preparing-to-submit-a-ticket)". - -Después de enviar una solicitud de soporte e información de diagnóstico opcional, {% data variables.contact.github_support %} puede solicitarte que descargues y compartas un paquete de soporte con nosotros. Para obtener más información, consulta "[Proporcionar datos a {% data variables.contact.github_support %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)". - -### Emitir un ticket utilizando el {% data variables.contact.enterprise_portal %} - -1. Navega por el {% data variables.contact.contact_enterprise_portal %}. -5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} -{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} - -### Emitir un ticket utilizando tu cuenta empresarial - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.enterprise-licensing-tab %} -4. Debajo de "Ayuda de {% data variables.product.prodname_enterprise %}", da clic en **Portal de {% data variables.contact.enterprise_support %}**. ![Enlace para navegar al sitio de soporte empresarial](/assets/images/enterprise/support/enterprise-support-link.png) -5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} -{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} - -### Enviar un ticket mediante el {% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.type-management-console-password %} -{% data reusables.enterprise_management_console.support-link %} -5. Si deseas incluir los diagnósticos con tu ticket de soporte, en "Diagnostics" (Diagnóstico), haz clic en **Download diagnostic info** (Descargar información de diagnóstico) y guarda el archivo localmente. Adjuntarás este archivo a tu ticket de soporte posteriormente. ![Botón para descargar información de diagnóstico](/assets/images/enterprise/support/download-diagnostics-info-button.png) -6. En "Open Support Request" (Abrir solicitud de soporte", haz clic en **New support request** (Nueva solicitud de soporte). ![Botón para abrir una solicitud de soporte](/assets/images/enterprise/management-console/open-support-request.png) -5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} -14. Para incluir los diagnósticos con tu ticket de soporte, haz clic en **Add file** (Agregar archivo), luego adjunta el archivo de diagnóstico que descargaste. ![Añadir botón de archivo](/assets/images/enterprise/support/support-ticket-add-file.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} -7. Haz clic en **Submit** (enviar). - -### Leer más - -- "[Acerca de {% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support)" -- "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)". diff --git a/translations/es-XL/content/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server.md b/translations/es-XL/content/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server.md deleted file mode 100644 index 43ef1aa876..0000000000 --- a/translations/es-XL/content/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: About using GitHub.com actions on GitHub Enterprise Server -intro: '{% data variables.product.prodname_ghe_server %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server -versions: - enterprise-server: '>=2.22' ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -{% data reusables.actions.enterprise-no-internet-actions %} - -### Official actions bundled with {% data variables.product.prodname_ghe_server %} - -Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}, and are captured at a point in time from {% data variables.product.prodname_marketplace %}. When your {% data variables.product.prodname_ghe_server %} instance receives updates, the bundled official actions are also updated. - -The bundled official actions include `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler`, and various `actions/setup-` actions, among others. To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://{% data variables.product.product_url %}/actions. - -Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. - -{% note %} - -**Note:** When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.prodname_ghe_server %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." - -{% endnote %} - -### Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} - -If users on your enterprise instance need access to other actions from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}, there are a few configuration options. - -You can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." - -Alternatively, you can enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %} by connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} 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)". diff --git a/translations/es-XL/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/es-XL/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md deleted file mode 100644 index 003f24e239..0000000000 --- a/translations/es-XL/content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Enabling automatic access to GitHub.com actions using GitHub Connect -intro: 'To allow {% data variables.product.prodname_actions %} on your enterprise instance to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_ghe_cloud %}.' -permissions: 'Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.' -redirect_from: - - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect -versions: - enterprise-server: '>=2.22' - github-ae: next -topics: - - Actions - - Enterprise - - GitHub Connect ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.prodname_ghe_server %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). - -To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can connect {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} using {% data variables.product.prodname_github_connect %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)." - -### 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 {% data variables.product.product_location_enterprise %}, you must connect {% data variables.product.product_location_enterprise %} to {% 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)." - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.github-connect-tab %} -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) diff --git a/translations/es-XL/content/admin/github-actions/enabling-github-actions-and-configuring-storage.md b/translations/es-XL/content/admin/github-actions/enabling-github-actions-and-configuring-storage.md deleted file mode 100644 index 6827b16ec1..0000000000 --- a/translations/es-XL/content/admin/github-actions/enabling-github-actions-and-configuring-storage.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Enabling GitHub Actions and configuring storage -intro: 'External storage must be configured as part of enabling {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' -permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' -redirect_from: - - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage -versions: - enterprise-server: '>=2.22' ---- - -{% if currentVersion == "enterprise-server@2.22" %} -{% note %} - -**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/). - -{% endnote %} -{% endif %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### About external storage requirements - -To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage. - -{% data variables.product.prodname_actions %} uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. - -{% data variables.product.prodname_actions %} supports these storage providers: - -* Amazon S3 -* Azure Blob storage -* S3-compatible MinIO Gateway for NAS - -#### Amazon S3 permissions - -If you use Amazon S3, {% data variables.product.prodname_actions %} requires the following permissions for your AWS access key ID and secret: - -* `s3:PutObject` -* `s3:GetObject` -* `s3:ListBucketMultipartUploads` -* `s3:ListMultipartUploadParts` -* `s3:AbortMultipartUpload` -* `s3:DeleteObject` - -### Enabling {% data variables.product.prodname_actions %} - -{% if currentVersion == "enterprise-server@2.22" %} -{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. [Sign up for the beta](https://resources.github.com/beta-signup/). -{% endif %} - -### Leer más - -- "Hardware considerations" for your platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)" diff --git a/translations/es-XL/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md b/translations/es-XL/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md deleted file mode 100644 index fbf58a6803..0000000000 --- a/translations/es-XL/content/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -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 -versions: - enterprise-server: '>=2.22' - github-ae: '*' -topics: - - Actions - - Enterprise - - Policies ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### About {% data variables.product.prodname_actions %} permissions for your enterprise - -When you enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, it is enabled for all organizations in your enterprise. 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 an organization. - -### Managing {% data variables.product.prodname_actions %} permissions for your enterprise - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -{% data reusables.actions.enterprise-actions-permissions %} - -{% if currentVersion ver_gt "enterprise-server@2.22" %} -### Habilitar flujos de trabajo para las bifurcaciones de repositorios privados - -{% data reusables.github-actions.private-repository-forks-overview %} - -#### Configuring the private fork policy for your enterprise - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% 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-XL/content/admin/github-actions/index.md b/translations/es-XL/content/admin/github-actions/index.md deleted file mode 100644 index a185b88f9f..0000000000 --- a/translations/es-XL/content/admin/github-actions/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Managing GitHub Actions for your enterprise -intro: 'Enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, and manage {% data variables.product.prodname_actions %} policies and settings.' -redirect_from: - - /enterprise/admin/github-actions -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /using-github-actions-in-github-ae - - /enabling-github-actions-for-github-enterprise-server - - /managing-access-to-actions-from-githubcom - - /advanced-configuration-and-troubleshooting ---- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} -### Índice diff --git a/translations/es-XL/content/admin/github-actions/managing-access-to-actions-from-githubcom.md b/translations/es-XL/content/admin/github-actions/managing-access-to-actions-from-githubcom.md deleted file mode 100644 index 2d6e832608..0000000000 --- a/translations/es-XL/content/admin/github-actions/managing-access-to-actions-from-githubcom.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Managing access to actions from GitHub.com -intro: 'Controlling which actions on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %} can be used in your enterprise.' -mapTopic: true -redirect_from: - - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom -versions: - enterprise-server: '>=2.22' - github-ae: next -topics: - - Enterprise ---- - diff --git a/translations/es-XL/content/admin/github-actions/manually-syncing-actions-from-githubcom.md b/translations/es-XL/content/admin/github-actions/manually-syncing-actions-from-githubcom.md deleted file mode 100644 index 184e397993..0000000000 --- a/translations/es-XL/content/admin/github-actions/manually-syncing-actions-from-githubcom.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Manually syncing actions from GitHub.com -intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your {% data variables.product.prodname_ghe_server %} instance.' -redirect_from: - - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom -versions: - enterprise-server: '>=2.22' - github-ae: next -topics: - - Enterprise ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -{% data reusables.actions.enterprise-no-internet-actions %} - -To make specific actions from {% data variables.product.prodname_dotcom_the_website %} available to use in workflows, you can use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise instance. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "[About using {% data variables.product.prodname_dotcom_the_website %} actions on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server)." - -### About the `actions-sync` tool - -The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.prodname_ghe_server %} instance's API. The machine doesn't need to be connected to both at the same time. - -If your machine has access to both systems at the same time, you can do the sync with a single `actions-sync sync` command. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. - -The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. - -### Prerrequisitos - -* Before using the the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating organizations](/enterprise/admin/user-management/creating-organizations)." -* You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. 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)". - -### Example: Using the `actions-sync` tool - -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 %} - -**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 {% data variables.product.prodname_ghe_server %} 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. Download and extract the latest [`actions-sync` release](https://github.com/actions/actions-sync/releases) for your machine's operating system. -1. Create a directory to store cache files for the tool. -1. Run the `actions-sync sync` command: - - ```shell - ./actions-sync sync \ - --cache-dir "cache" \ - --destination-token "aabbccddeeffgg" \ - --destination-url "https://my-ghes-instance" \ - --repo-name "docker/build-push-action:synced-actions/docker-build-push-action" - ``` - - The above command uses the following arguments: - - * `--cache-dir`: The cache directory on the machine running the command. - * `--destination-token`: A personal access token for the destination enterprise instance. - * `--destination-url`: The URL of the destination enterprise instance. - * `--repo-name`: The action repository to sync. This takes the format of `owner/repository:destination_owner/destination_repository`. - - * The above example syncs the [`docker/build-push-action`](https://github.com/docker/build-push-action) repository to the `synced-actions/docker-build-push-action` repository on the destination {% data variables.product.prodname_ghe_server %} instance. You must create the organization named `synced-actions` on your enterprise instance before running the above command. - * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise instance. Before running the command, you must create a new organization on your instance that matches the owner name of the action. Consider using a central organization to store the synced actions on your instance, as this means you will not need to create multiple new organizations if you sync actions from different owners. - * You can sync multiple actions by replacing the `--repo-name` parameter with `--repo-name-list` or `--repo-name-list-file`. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync). -1. After the action repository is created on your enterprise instance, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above: - - ``` - uses: synced-actions/docker-build-push-action@v1 - ``` - - Para obtener más información, consultala sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)". diff --git a/translations/es-XL/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/es-XL/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md deleted file mode 100644 index cafde18c3e..0000000000 --- a/translations/es-XL/content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: Setting up the tool cache on self-hosted runners without internet access -intro: 'To use the the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.' -redirect_from: - - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access -versions: - enterprise-server: '>=2.22' - github-ae: next -topics: - - Enterprise ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### About the included setup actions and the runner tool cache - -{% data reusables.actions.enterprise-no-internet-actions %} - -Most official {% data variables.product.prodname_dotcom %}-authored actions are automatically bundled with {% data variables.product.prodname_ghe_server %}. However, self-hosted runners without internet access will require some configuration before they can use the included `actions/setup-LANGUAGE` actions, such as `setup-node`. - -The `actions/setup-LANGUAGE` actions normally need internet access to download the required environment binaries into the runner's tool cache. Self-hosted runners without internet access can't download the binaries, so you must manually populate the tool cache on the runner. - -You can populate the runner tool cache by running a {% data variables.product.prodname_actions %} workflow on {% data variables.product.prodname_dotcom_the_website %} that uploads a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache as an artifact, which you can then transfer and extract on your internet-disconnected self-hosted runner. - -{% note %} - -**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "Virtual environments for GitHub-hosted runners." - -{% endnote %} - -### Prerrequisitos - -* Determine which development environments your self-hosted runners will need. The following example demonstrates how to populate a tool cache for the `setup-node` action, using Node.js versions 10 and 12. -* Access to a repository on {% data variables.product.prodname_dotcom_the_website %} that you can use to run a workflow. -* Access to your self-hosted runner's file system to populate the tool cache folder. - -### Populating the tool cache for a self-hosted runner - -1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repostory that you can use to run a {% data variables.product.prodname_actions %} workflow. -1. Create a new workflow file in the repository's `.github/workflows` folder that uploads an artifact containing the {% data variables.product.prodname_dotcom %}-hosted runner's tool cache. - - The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 18.04 environment, using the `setup-node` action with Node.js versions 10 and 12. - - {% raw %} - ```yaml - name: Upload Node.js 10 and 12 tool cache - on: push - jobs: - upload_tool_cache: - runs-on: ubuntu-18.04 - steps: - - name: Clear any existing tool cache - run: | - mv "${{ runner.tool_cache }}" "${{ runner.tool_cache }}.old" - mkdir -p "${{ runner.tool_cache }}" - - name: Setup Node 10 - uses: actions/setup-node@v1 - with: - node-version: 10.x - - name: Setup Node 12 - uses: actions/setup-node@v1 - with: - node-version: 12.x - - name: Archive tool cache - run: | - cd "${{ runner.tool_cache }}" - tar -czf tool_cache.tar.gz * - - name: Upload tool cache artifact - uses: actions/upload-artifact@v2 - with: - path: ${{runner.tool_cache}}/tool_cache.tar.gz - ``` - {% endraw %} -1. Download the tool cache artifact from the workflow run. For instructions on downloading artifacts, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts#downloading-and-deleting-artifacts-after-a-workflow-run-is-complete)." -1. Transfer the tool cache artifact to your self hosted runner and extract it to the local tool cache directory. The default tool cache directory is `RUNNER_DIR/_work/_tool`. If the runner hasn't processed any jobs yet, you might need to create the `_work/_tool` directories. - - After extracting the tool cache artifact uploaded in the above example, you should have a directory structure on your self-hosted runner that is similar to the following example: - - ``` - RUNNER_DIR - ├── ... - └── _work - ├── ... - └── _tool - └── node - ├── 10.22.0 - │   └── ... - └── 12.18.3 - └── ... - ``` - -Your self-hosted runner without internet access should now be able to use the `setup-node` action. If you are having problems, make sure that you have populated the correct tool cache for your workflows. For example, if you need to use the `setup-python` action, you will need to populate the tool cache with the Python environment you want to use. diff --git a/translations/es-XL/content/admin/index.md b/translations/es-XL/content/admin/index.md deleted file mode 100644 index c67abc2890..0000000000 --- a/translations/es-XL/content/admin/index.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Enterprise Administrators -redirect_from: - - /github/installing-and-configuring-github-insights/exploring-your-usage-of-github-enterprise - - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights - - /github/installing-and-configuring-github-insights/key-metrics-for-collaboration-in-pull-requests - - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports - - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.21/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.20/github/site-policy/github-insights-and-data-protection-for-your-organization - - /insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise - - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise - - /github/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise - - /insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise - - /insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights - - /github/installing-and-configuring-github-insights/about-github-insights - - /insights/installing-and-configuring-github-insights/about-github-insights - - /github/installing-and-configuring-github-insights/installing-github-insights - - /insights/installing-and-configuring-github-insights/installing-github-insights - - /github/installing-and-configuring-github-insights/system-overview-for-github-insights - - /insights/installing-and-configuring-github-insights/system-overview-for-github-insights - - /github/installing-and-configuring-github-insights/updating-github-insights - - /insights/installing-and-configuring-github-insights/updating-github-insights - - /insights/installing-and-configuring-github-insights/about-data-in-github-insights - - /github/installing-and-configuring-github-insights/managing-data-in-github-insights - - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights - - /insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports - - /github/installing-and-configuring-github-insights/managing-contributors-and-teams - - /insights/installing-and-configuring-github-insights/managing-contributors-and-teams - - /github/installing-and-configuring-github-insights/creating-and-managing-events - - /insights/installing-and-configuring-github-insights/managing-events - - /github/installing-and-configuring-github-insights/creating-and-managing-goals - - /insights/installing-and-configuring-github-insights/managing-goals - - /github/installing-and-configuring-github-insights/managing-organizations - - /insights/installing-and-configuring-github-insights/managing-organizations - - /github/installing-and-configuring-github-insights/managing-repositories - - /insights/installing-and-configuring-github-insights/managing-repositories - - /insights/exploring-your-usage-of-github-enterprise - - /insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights - - /insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights - - /insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights - - /insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports - - /insights - - /insights/installing-and-configuring-github-insights/configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise - - /insights/installing-and-configuring-github-insights/configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise - - /insights/installing-and-configuring-github-insights/configuring-github-insights - - /insights/installing-and-configuring-github-insights/configuring-github-insights/managing-permissions-in-github-insights - - /insights/installing-and-configuring-github-insights - - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights/about-github-insights - - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights - - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights/installing-github-insights - - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights/system-overview-for-github-insights - - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights/updating-github-insights - - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/about-data-in-github-insights - - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights - - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-available-metrics-and-reports - - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-contributors-and-teams - - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-events - - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-goals - - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-organizations - - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-repositories - - /admin/configuration/configuring-your-enterprise/configuring-data-encryption-for-your-enterprise -intro: 'Guías paso a paso para administradores de empresas, administradores de sistemas y especialistas en seguridad que implementan, configuran y administran una instancia de GitHub Enterprise.' -versions: - ghes: '*' - ghae: '*' -children: - - /overview - - /installation - - /configuration - - /authentication - - /user-management - - /policies - - /enterprise-management - - /github-actions - - /packages - - /enterprise-support - - /advanced-security - - /guides - - /release-notes - - /all-releases ---- - diff --git a/translations/es-XL/content/admin/installation/index.md b/translations/es-XL/content/admin/installation/index.md deleted file mode 100644 index 52d22b0155..0000000000 --- a/translations/es-XL/content/admin/installation/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: 'Instalar {% data variables.product.prodname_enterprise %}' -shortTitle: Instalar -intro: 'Los administradores de sistema y los especialistas de seguridad y de operaciones pueden instalar {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin-guide/ - - /enterprise/admin/guides/installation/ - - /enterprise/admin/categories/customization/ - - /enterprise/admin/categories/general/ - - /enterprise/admin/categories/logging-and-monitoring/ - - /enterprise/admin/installation -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Set up -children: - - /setting-up-a-github-enterprise-server-instance ---- - -Para obtener más información, o para comprar {% data variables.product.prodname_enterprise %}, consulta [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). - -{% data reusables.enterprise_installation.request-a-trial %} - -Si tienes preguntas sobre el proceso de instalación, consulta "[Trabajar con el soporte {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/enterprise-support/)." -### Índice diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md deleted file mode 100644 index bfd7c78a46..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Configurar una instancia del servidor de GitHub Enterprise -intro: 'Puede instalar {% data variables.product.prodname_ghe_server %} en la plataforma de virtualización soportada de tu elección.' -redirect_from: - - /enterprise/admin/installation/getting-started-with-github-enterprise-server - - /enterprise/admin/guides/installation/supported-platforms/ - - /enterprise/admin/guides/installation/provisioning-and-installation/ - - /enterprise/admin/guides/installation/setting-up-a-github-enterprise-instance/ - - /enterprise/admin/installation/setting-up-a-github-enterprise-server-instance -versions: - ghes: '*' -topics: - - Enterprise -children: - - /installing-github-enterprise-server-on-aws - - /installing-github-enterprise-server-on-azure - - /installing-github-enterprise-server-on-google-cloud-platform - - /installing-github-enterprise-server-on-hyper-v - - /installing-github-enterprise-server-on-openstack-kvm - - /installing-github-enterprise-server-on-vmware - - /installing-github-enterprise-server-on-xenserver - - /setting-up-a-staging-instance ---- - diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md deleted file mode 100644 index 9a88667724..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Instalar el servidor de GitHub Enterprise en AWS -intro: 'Para instalar el {% data variables.product.prodname_ghe_server %} en Amazon Web Services (AWS), debes iniciar una instancia de Amazon Elastic Compute Cloud (EC2) y crear y adjuntar un volumen de datos separado de Amazon Elastic Block Store (EBS).' -redirect_from: - - /enterprise/admin/guides/installation/installing-github-enterprise-on-aws/ - - /enterprise/admin/installation/installing-github-enterprise-server-on-aws - - /admin/installation/installing-github-enterprise-server-on-aws -versions: - ghes: '*' -topics: - - Enterprise ---- -### Prerrequisitos - -- {% data reusables.enterprise_installation.software-license %} -- Debes tener una cuenta AWS capaz de iniciar instancias EC2 y crear volúmenes EBS. Para obtener más información, consulta el [Sitio web de Amazon Web Services](https://aws.amazon.com/). -- La mayoría de las acciones necesarias para iniciar {% data variables.product.product_location_enterprise %} también pueden realizarse por medio de la consola de administración de AWS. Sin embargo, recomendamos instalar la interfaz de línea de comando de AWS (CLI) para la configuración inicial. Abajo se incluyen ejemplos que utilizan AWS CLI. Para obtener más información, consulta las guías de Amazon "[Trabajar con la consola de administración de AWS](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" y "[Qué es la interfaz de línea de comando de AWS](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)." - -Esta guía supone que estás familiarizado con los siguientes conceptos de AWS: - - - [Iniciar instancias de EC2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html) - - [Administrar volúmenes de EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html) - - [Utilizar grupos de seguridad](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (para administrar el acceso de red a tu instancia) - - [Direcciones IP elásticas (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (altamente recomendadas para los entornos de producción) - - [EC2 y Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (si planeas iniciar dentro de Virtual Private Cloud) - -### Consideraciones relativas al hardware - -{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} - -### Determinar el tipo de instancia - -Antes de iniciar {% data variables.product.product_location_enterprise %} en AWS, deberás determinar el tipo de máquina virtual que mejor se adapte a las necesidades de tu organización. - -#### Tipos de instancias admitidas - -{% data reusables.enterprise_installation.aws-supported-instance-types %} - -#### Tipos de instancias recomendadas - -{% data reusables.enterprise_installation.aws-recommended-instance-types %} - -{% data reusables.enterprise_installation.warning-on-scaling %} - -### Seleccionar la AMI del {% data variables.product.prodname_ghe_server %} - -Puedes seleccionar una Amazon Machine Image (AMI) para el {% data variables.product.prodname_ghe_server %} utilizando el portal del {% data variables.product.prodname_ghe_server %} o la CLI de AWS. - -Las AMIs para {% data variables.product.prodname_ghe_server %} se encuentran disponibles en la región de AWS GovCloud (EE.UU. Este y EE.UU. Oeste). Esto permite que los clientes de EE. UU. con requisitos reglamentarios específicos ejecuten el {% data variables.product.prodname_ghe_server %} en un entorno de nube que cumpla con los requisitos a nivel federal. Para obtener más información sobre el cumplimiento de AWS de las normas federales y otras normas, consulta la [Página de GovCloud (EE. UU.) de AWS](http://aws.amazon.com/govcloud-us/) y la [Página de cumplimiento de AWS](https://aws.amazon.com/compliance/). - -#### Utilizar el portal {% data variables.product.prodname_ghe_server %} para seleccionar una AMI - -{% data reusables.enterprise_installation.enterprise-download-procedural %} -{% data reusables.enterprise_installation.download-appliance %} -3. En el menú desplegable Select your platform (Selecciona tu plataforma), haz clic en **Amazon Web Services**. -4. En el menú desplegable Select your AWS region (Selecciona tu región AWS), elige tu región deseada. -5. Toma nota de la ID de AMI que se muestra. - -#### Utilizar la CLI de AWS para seleccionar una AMI - -1. Utilizando una CLI de AWS, obtén una lista de imágenes publicadas del {% data variables.product.prodname_ghe_server %} por ID de propietarios de AWS de {% data variables.product.prodname_dotcom %} (`025577942450` para GovCloud, y `895557238572` para otras regiones). Para obtener más información, consulta "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" en los documentos de AWS. - ```shell - aws ec2 describe-images \ - --owners OWNER ID \ - --query 'sort_by(Images,&Name)[*].{Name:Name,ImageID:ImageId}' \ - --output=text - ``` -2. Toma nota del ID de AMI de la última imagen del {% data variables.product.prodname_ghe_server %}. - -### Crear un grupo de seguridad - -Si estás configurando tu AMI por primera vez, deberás crear un grupo de seguridad y agregar una nueva regla de grupo de seguridad para cada puerto en la tabla de abajo. Para más información, consulta la guía AWS "[Usar grupos de seguridad](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)." - -1. Crea un nuevo grupo de seguridad utilizando la CLI de AWS. Para obtener más información, consulta "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" en los documentos de AWS. - ```shell - $ aws ec2 create-security-group --group-name SECURITY_GROUP_NAME --description "SECURITY GROUP DESCRIPTION" - ``` - -2. Toma nota del ID del grupo de seguridad (`sg-xxxxxxxx`) de tu grupo de seguridad recientemente creado. - -3. Crea una regla de grupo de seguridad para cada puerto en la tabla de abajo. Para obtener más información, consulta "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" en los documentos de AWS. - ```shell - $ aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID --protocol PROTOCOL --port PORT_NUMBER --cidr SOURCE IP RANGE - ``` - Esta tabla identifica para qué se utiliza cada puerto. - - {% data reusables.enterprise_installation.necessary_ports %} - -### Crear la instancia de {% data variables.product.prodname_ghe_server %} - -Para crear la instancia, deberás lanzar una instancia de EC2 con tu AMI {% data variables.product.prodname_ghe_server %} y adjuntarle volumen de almacenamiento adicional para los datos de tu instancia. Para obtener más información, consulta "[Consideraciones relativas al hardware](#hardware-considerations)." - -{% note %} - -**Nota:** puedes cifrar el disco de datos para obtener un nivel adicional de seguridad y estar seguro de que los datos que escribas en tu instancia están protegidos. Hay un leve impacto de desempeño cuando usas discos encriptados. Si decides cifrar tu volumen, recomendamos firmemente hacerlo **antes** de comenzar tu instancia por primera vez. Para más información, consulta la guía de Amazon [sobre el cifrado EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html). - -{% endnote %} - -{% warning %} - -**Advertencia:** si decides habilitar la encriptación después de configurar tu instancia, deberás migrar tus datos al volumen encriptado, que producirá tiempo de inactividad para tus usuarios. - -{% endwarning %} - -#### Lanzar una instancia de EC2 - -En la CLI de AWS, inicia una instancia de EC2 utilizando tu AMI y el grupo de seguridad que has creado. Adjunta un nuevo dispositivo de bloque para utilizarlo como volumen de almacenamiento para tus datos de la instancia y configura el tamaño de acuerdo con la cantidad de licencias de usuario que tengas. Para obtener más información, consulta "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" en los documentos de AWS. - -```shell -aws ec2 run-instances \ - --security-group-ids SECURITY_GROUP_ID \ - --instance-type INSTANCE_TYPE \ - --image-id AMI_ID \ - --block-device-mappings '[{"DeviceName":"/dev/xvdf","Ebs":{"VolumeSize":SIZE,"VolumeType":"TYPE"}}]' \ - --region REGION \ - --ebs-optimized -``` - -#### Asignar una IP elástica y asociarla con la instancia - -Si esta es una instancia de producción, recomendamos firmemente asignar una IP elástica (EIP) y asociarla con la instancia antes de continuar con la configuración del {% data variables.product.prodname_ghe_server %}. De lo contrario, la dirección IP pública de la instancia no se conservará después de que se reinicie la instancia. Para obtener más información, consulta "[Asignar una dirección IP elástica](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" y "[Asociar una dirección IP elástica con una instancia en ejecución](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" en la documentación de Amazon. - -Tanto en la instancia principal y en la de réplica deberían asignarse EIP separadas en las configuraciones de alta disponibilidad de producción. Para obtener más información, consulta "[Configurar {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." - -### Configurar la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} -{% data reusables.enterprise_installation.upload-a-license-file %} -{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." -{% data reusables.enterprise_installation.instance-will-restart-automatically %} -{% data reusables.enterprise_installation.visit-your-instance %} - -### Leer más - -- "[Descripción del sistema](/enterprise/admin/guides/installation/system-overview)" diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md deleted file mode 100644 index 462b673daa..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -title: Instalar el servidor de GitHub Enterprise en Azure -intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Azure, debes implementar en una instancia de serie DS y usar almacenamiento Premium-LRS.' -redirect_from: - - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure/ - - /enterprise/admin/installation/installing-github-enterprise-server-on-azure - - /admin/installation/installing-github-enterprise-server-on-azure -versions: - ghes: '*' -topics: - - Enterprise ---- -Puedes implementar {% data variables.product.prodname_ghe_server %} en Azure mundial o Azure Government. - -### Prerrequisitos - -- {% data reusables.enterprise_installation.software-license %} -- Debes tener una cuenta Azure capaz de abastecer nuevas máquinas. Para obtener más información, consulta el [sitio web de Microsoft Azure](https://azure.microsoft.com). -- La mayoría de las acciones necesarias para lanzar tu máquina virtual (VM) también se podrían realizar por medio del Portal Azure. Sin embargo, recomendamos instalar la interfaz de la línea de comando de Azure (CLI) para la configuración inicial. Abajo se incluyen ejemplos que utilizan Azure CLI 2.0. Para obtener más información, consulta la guía de Azure "[Instalar Azure CLI 2.0](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)." - -### Consideraciones relativas al hardware - -{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} - -### Determinar el tipo de máquina virtual - -Antes de iniciar {% data variables.product.product_location_enterprise %} en Azure, deberás determinar el tipo de máquina virtual que mejor se adapte a las necesidades de tu organización. - -#### Tipos y regiones de VM admitidas - -El aparato {% data variables.product.prodname_ghe_server %} requiere un disco de datos de almacenamiento prémium, y es compatible con cualquier Azure VM que admita almacenamiento prémium. Para obtener más información, consulta "[VM admitidos](https://docs.microsoft.com/en-us/azure/storage/common/storage-premium-storage#supported-vms)" en la documentación de Azure. Para obtener información general sobre los VM disponibles, consulta [la página de descripción de máquinas virtuales de Azure](http://azure.microsoft.com/en-us/pricing/details/virtual-machines/#Linux). - -{% data variables.product.prodname_ghe_server %} admite cualquier región que sea compatible con tu tipo de VM. Para obtener más información sobre las regiones admitidas para cada VM, consulte los productos de Azure "[disponibles por región](https://azure.microsoft.com/en-us/regions/services/)." - -#### Tipos de VM recomendados - -Te recomendamos que uses un tipo de instancia DS v2 con 14 GB de RAM como mínimo. Puedes usar cualquier tipo de VM admitido. De acuerdo con el número de licencias de usuario con las que cuentes, recomendamos los siguientes tipos de instancia. - -| Asientos | Tipo recomendado | -|:----------------------------------------:|:------------------:| -| Prueba, Demo o 10 usuarios no frecuentes | Standard_DS11_v2 | -| 10 - 3000 | Standard_DS12_v2 | -| 3000 - 8000 | Standard_DS14_v2 | -| 8000 - 10000+ | Standard_DS15_v2 | - -{% data reusables.enterprise_installation.warning-on-scaling %} - -### Crear la máquina virtual{% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.create-ghe-instance %} - -1. Encuentra la imagen de aparato más reciente {% data variables.product.prodname_ghe_server %}. Para obtener más información sobre el comando `vm image list`, consulta "[lista de imagen vm de az](https://docs.microsoft.com/en-us/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" en la documentación de Microsoft. - ```shell - $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V - ``` - -2. Crea una nueva VM utilizando la imagen de aparato que encontraste. Para obtener más información, consulta "[crear vm de az](https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az_vm_create)" en la documentación de Microsoft. - - Aprueba opciones para el nombre de tu VM, el grupo de recurso, el tamaño de tu VM, el nombre de tu región Azure preferida, el nombre de la imagen de tu aparato VM que enumeraste en el paso anterior y el almacenamiento SKU para un almacenamiento prémium. Para obtener más información sobre grupos de recursos, consulta "[Grupos de recursos](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview#resource-groups)" en la documentación de Microsoft. - - ```shell - $ az vm create -n VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --storage-sku Premium_LRS - ``` - -3. Configura los parámetros de seguridad en tu VM para abrir los puertos requeridos. Para obtener más información, consulta "[abrir puerto de vm de az](https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" en la documentación de Microsoft. Consulta la tabla de abajo para obtener una descripción de cada puerto para determinar qué puertos debes abrir. - - ```shell - $ az vm open-port -n VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER - ``` - - Esta tabla identifica para qué se utiliza cada puerto. - - {% data reusables.enterprise_installation.necessary_ports %} - -4. Crea y adjunta a la VM un nuevo disco de datos descifrado y configura su tamaño con base en la cantidad de licencias que tengas. Para obtener más información, consulta "[adjuntar un disco de vm de az](https://docs.microsoft.com/en-us/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" en la documentación de Microsoft. - - Aprueba opciones para el nombre de tu VM (por ejemplo, `ghe-acme-corp`), el grupo de recurso, el almacenamiento prémium de SKU, el tamaño del disco (por ejemplo, `100`) y un nombre para el VHD resultante. - - ```shell - $ az vm disk attach --vm-name VM_NAME -g RESOURCE_GROUP --sku Premium_LRS --new -z SIZE_IN_GB --name ghe-data.vhd --caching ReadWrite - ``` - - {% note %} - - **Nota:** para instancias no productivas que tengan suficiente rendimiento de E/S, el tamaño mínimo recomendado es de 40 GiB con caché de lectura/escritura activado (`--caching ReadWrite`). - - {% endnote %} - -### Configurara la máquina virtual {% data variables.product.prodname_ghe_server %} - -1. Antes de configurar el VM, debes esperar que pase al estado ReadyRole. Controla el estado del VM con el comando `vm list`. Para obtener más información, consulta "[lista de vm de az](https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az_vm_list)" en la documentación de Microsoft. - ```shell - $ az vm list -d -g RESOURCE_GROUP -o table - > Name ResourceGroup PowerState PublicIps Fqdns Location Zones - > ------ --------------- ------------ ------------ ------- ---------- ------- - > VM_NAME RESOURCE_GROUP VM running 40.76.79.202 eastus - - ``` - {% note %} - - **Nota:** Azure no crea automáticamente una entrada FQDNS para el VM. Para obtener más información, consulta la guía de Azure sobre cómo "[Crear un nombre de dominio certificado completo en el portal de Azure para una VM de Linux](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/portal-create-fqdn)." - - {% endnote %} - - {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} - {% data reusables.enterprise_installation.upload-a-license-file %} - {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." - {% data reusables.enterprise_installation.instance-will-restart-automatically %} - {% data reusables.enterprise_installation.visit-your-instance %} - - - ### Leer más - - - "[Descripción del sistema](/enterprise/admin/guides/installation/system-overview)" diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md deleted file mode 100644 index d5891ea148..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -title: Instalar el servidor de GitHub Enterprise en Google Cloud Platform -intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Google Cloud Platform, debes implementar un tipo de máquina soportado y utilizar un disco estándar persistente o un SSD persistente.' -redirect_from: - - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform/ - - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform - - /admin/installation/installing-github-enterprise-server-on-google-cloud-platform -versions: - ghes: '*' -topics: - - Enterprise ---- -### Prerrequisitos - -- {% data reusables.enterprise_installation.software-license %} -- Debes tener una cuenta de Google Cloud Platform capaz de iniciar instancias de la máquina virtual (VM) de Google Compute Engine (GCE). Para obtener más información, consulta el [Sitio web de Google Cloud Platform](https://cloud.google.com/) y la [Documentación de Google Cloud Platform](https://cloud.google.com/docs/). -- La mayoría de las acciones necesarias para iniciar tu instancia pueden también realizarse utilizando la [Consola de Google Cloud Platform](https://cloud.google.com/compute/docs/console). Sin embargo, recomendamos instalar la herramienta de línea de comando de gcloud compute para la configuración inicial. Se incluyen abajo ejemplos que utilizan la herramienta de línea de comando de gcloud compute. Para obtener más información, consulta la guía de instalación y configuración en la documentación de Google de "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)". - -### Consideraciones relativas al hardware - -{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} - -### Determinar el tipo de máquina - -Antes de iniciar {% data variables.product.product_location_enterprise %} en Google Cloud Platform, deberás determinar el tipo de máquina que mejor se adapte a las necesidades de tu organización. - -#### Tipos de máquinas admitidas - -{% data variables.product.prodname_ghe_server %} es compatible en los siguientes tipo de máquinas de Google Compute Engine (GCE). Para obtener más información, consulta el [artículo sobre tipos de máquinas de Google Cloud Platform](https://cloud.google.com/compute/docs/machine-types). | -{% if currentVersion != "free-pro-team@latest" %} -| | Memoria alta | -| | ------------- | -| | n1-highmem-4 | -| | n1-highmem-8 | -| | n1-highmem-16 | -| | n1-highmem-32 | -| | n1-highmem-64 | -| | n1-highmem-96 | -{% endif %} - -#### Tipos recomendados de máquina - -Recomendamos estos tipos de máquina con base en la cantidad de licencias que tengas. - -| Asientos | Tipo recomendado | -|:----------------------------------------:|:----------------:| -| Prueba, Demo o 10 usuarios no frecuentes | n1-standard-4 | -| 10 - 3000 | n1-standard-8 | -| 3000 - 5000 | n1-highmem-8 | -| 5000 - 8000 | n1-highmem-16 | -| 8000 - 10000+ | n1-highmem-32 | - -{% data reusables.enterprise_installation.warning-on-scaling %} - -### Seleccionar la imagen {% data variables.product.prodname_ghe_server %} - -1. Utilizando la herramienta de línea de comando de [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/), enumera las imágenes públicas{% data variables.product.prodname_ghe_server %}: - ```shell - $ gcloud compute images list --project github-enterprise-public --no-standard-images - ``` - -2. Toma nota del nombre de la imagen para la última imagen de GCE de {% data variables.product.prodname_ghe_server %}. - -### Configurar el firewall - -Las máquinas virtuales de GCE se crean como un miembro de la red, que tiene un firewall. Para la red asociada con la VM {% data variables.product.prodname_ghe_server %}, deberás configurar el firewall para permitir los puertos requeridos en la tabla de abajo. Para obtener más información sobre las reglas de firewall en Google Cloud Platform, consulta la guía de Google "[Descripción de las reglas de firewall](https://cloud.google.com/vpc/docs/firewalls)." - -1. Crea la red utilizando la herramienta de línea de comando de gcloud compute. Para obtener más información, consulta "[crea redes de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" en la documentación de Google. - ```shell - $ gcloud compute networks create NETWORK-NAME --subnet-mode auto - ``` -2. Crea una regla de firewall para cada uno de los puertos en la tabla de abajo. Para obtener más información, consulta las "[reglas de firewall de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" en la documentación de Google. - ```shell - $ gcloud compute firewall-rules create RULE-NAME \ - --network NETWORK-NAME \ - --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp - ``` - Esta tabla identifica los puertos requeridos y para qué se usa cada puerto. - - {% data reusables.enterprise_installation.necessary_ports %} - -### Asignar una IP estática y atribuirla a una VM - -Si es un aparato de producción, recomendamos firmemente reservar una dirección de IP estática externa y asignarla a la VM {% data variables.product.prodname_ghe_server %}. En caso contrario, la dirección de IP pública de la VM no se mantendrá después de que se reinicie. Para obtener más información, consulta la guía de Google "[Reservar una dirección estática de IP externa](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)." - -En las configuraciones de alta disponibilidad de producción, tantos en el aparato principal como en la réplica deberían asignarse direcciones estáticas de IP separadas. - -### Crear la instancia de {% data variables.product.prodname_ghe_server %} - -Para crear la instancia {% data variables.product.prodname_ghe_server %}, deberás crear una instancia de GCE con tu imagen {% data variables.product.prodname_ghe_server %} y adjuntarle volumen de almacenamiento adicional para los datos de tu instancia. Para obtener más información, consulta "[Consideraciones relativas al hardware](#hardware-considerations)." - -1. Crea un disco de datos para utilizar como un volumen de almacenamiento adjunto para tu instancia de datos utilizando la herramienta de línea de comandos para cálculo gcloud y configura el tamaño con base en la cantidad de licencias que tengas. Para obtener más información, consulta "[crea discos de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" en la documentación de Google. - ```shell - $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE - ``` - -2. Después crea una instancia utilizando el nombre de la imagen {% data variables.product.prodname_ghe_server %} que seleccionaste, y adjunta el disco de datos. Para obtener más información, consulta "[crea instancias de gcloud compute](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" en la documentación de Google. - ```shell - $ gcloud compute instances create INSTANCE-NAME \ - --machine-type n1-standard-8 \ - --image GITHUB-ENTERPRISE-IMAGE-NAME \ - --disk name=DATA-DISK-NAME \ - --metadata serial-port-enable=1 \ - --zone ZONE \ - --network NETWORK-NAME \ - --image-project github-enterprise-public - ``` - -### Configurar la instancia - -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} -{% data reusables.enterprise_installation.upload-a-license-file %} -{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." -{% data reusables.enterprise_installation.instance-will-restart-automatically %} -{% data reusables.enterprise_installation.visit-your-instance %} - -### Leer más - -- "[Descripción del sistema](/enterprise/admin/guides/installation/system-overview)" diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md deleted file mode 100644 index 0e0958e67b..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Instalar el servidor de GitHub Enterprise en Hyper-V -intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Hyper-V, debes implementarlo en una máquina ejecutando Windows Server 2008 a través de Windows Server 2016.' -redirect_from: - - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v/ - - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v - - /admin/installation/installing-github-enterprise-server-on-hyper-v -versions: - ghes: '*' -topics: - - Enterprise ---- -### Prerrequisitos - -- {% data reusables.enterprise_installation.software-license %} -- Debes tener Windows Server 2008 a través de Windows Server 2016, que admita Hyper-V. -- La mayoría de las acciones necesarias para crear tu máquina virtual (VM) también se pueden realizar utilizando el [Administrador de Hyper-V](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). Sin embargo, recomendamos utilizar la shell de la línea de comando de Windows PowerShell para la configuración inicial. Abajo se incluyen ejemplos que utilizan PowerShell. Para obtener más información, consulta la guía de Microsoft "[Instrucciones para Windows PowerShell](https://docs.microsoft.com/en-us/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)." - -### Consideraciones relativas al hardware - -{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} - -### Descargar la imagen del {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.enterprise-download-procedural %} -{% data reusables.enterprise_installation.download-license %} -{% data reusables.enterprise_installation.download-appliance %} -4. Selecciona {% data variables.product.prodname_dotcom %} locales, después haz clic en **Hyper-V (VHD)**. -5. Haz clic en **Download for Hyper-V (VHD) (Descarga para Hyper-V (VHD))**. - -### Crear la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.create-ghe-instance %} - -1. Crea una nueva máquina virtual de Generación 1 en PowerShell, configura el tamaño de acuerdo con la cantidad de licencias que tengas, y adjunta la imagen de {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener más información, consulta "[VM nuevo](https://docs.microsoft.com/en-us/powershell/module/hyper-v/new-vm?view=win10-ps)" en la documentación de Microsoft. - ```shell - PS C:\> New-VM -Generation 1 -Name VM_NAME -MemoryStartupBytes MEMORY_SIZE -BootDevice VHD -VHDPath PATH_TO_VHD - ``` -{% data reusables.enterprise_installation.create-attached-storage-volume %} Reemplaza la `PATH_TO_DATA_DISK` con la ruta a la ubicación donde creas el disco. Para obtener más información, consulta "[VHD nuevo](https://docs.microsoft.com/en-us/powershell/module/hyper-v/new-vhd?view=win10-ps)" en la documentación de Microsoft. - ```shell - PS C:\> New-VHD -Path PATH_TO_DATA_DISK -SizeBytes DISK_SIZE - ``` -3. Adjunta el disco de datos a tu instancia. Para obtener más información, consulta "[Add-VMHardDiskDrive](https://docs.microsoft.com/en-us/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" en la documentación de Microsoft. - ```shell - PS C:\> Add-VMHardDiskDrive -VMName VM_NAME -Path PATH_TO_DATA_DISK - ``` -4. Inicia la VM. Para obtener más información, consulta "[Iniciar la VM](https://docs.microsoft.com/en-us/powershell/module/hyper-v/start-vm?view=win10-ps)" en la documentación de Microsoft. - ```shell - PS C:\> Start-VM -Name VM_NAME - ``` -5. Obtén la dirección de IP de tu VM. Para obtener más información, consulta "[Get-VMNetworkAdapter](https://docs.microsoft.com/en-us/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" en la documentación de Microsoft. - ```shell - PS C:\> (Get-VMNetworkAdapter -VMName VM_NAME).IpAddresses - ``` -6. Copia la dirección de IP de la VM y pégala en el explorador web. - -### Configurar la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} -{% data reusables.enterprise_installation.upload-a-license-file %} -{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." -{% data reusables.enterprise_installation.instance-will-restart-automatically %} -{% data reusables.enterprise_installation.visit-your-instance %} - -### Leer más - - - "[Descripción del sistema](/enterprise/admin/guides/installation/system-overview)" diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md deleted file mode 100644 index 207d3eaab3..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Instalar el servidor de GitHub Enterprise en OpenStack KVM -intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en OpenStack KVM, debes tener acceso a OpenStack y descargar la imagen QCOW2 {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm/ - - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm - - /admin/installation/installing-github-enterprise-server-on-openstack-kvm -versions: - ghes: '*' -topics: - - Enterprise ---- -### Prerrequisitos - -- {% data reusables.enterprise_installation.software-license %} -- Debes tener acceso a una instalación de OpenStack Horizon, la interfaz de usuario con base en la web para los servicios de OpenStack. Para obtener más información, consulta la [Documentación de Horizon](https://docs.openstack.org/horizon/latest/). - -### Consideraciones relativas al hardware - -{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} - -### Descargar la imagen del {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.enterprise-download-procedural %} -{% data reusables.enterprise_installation.download-license %} -{% data reusables.enterprise_installation.download-appliance %} -4. Selecciona {% data variables.product.prodname_dotcom %} locales, después haz clic en **OpenStack KVM (QCOW2) (Abrir Stack KVM (QCOW2))**. -5. Haz clic en **Download for OpenStack KVM (QCOW2) (Descargar para OpenStack KVM (QCOW2))**. - -### Crear la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.create-ghe-instance %} - -1. En OpenStack Horizon, carga la imagen {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, dirígete a la sección "Cargar una imagen" en la guía de OpenStack "[Cargar y administrar imágenes](https://docs.openstack.org/horizon/latest/user/manage-images.html)". -{% data reusables.enterprise_installation.create-attached-storage-volume %} Para encontrar instrucciones, consulta la guía de OpenStack "[Crear y administrar volúmenes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)". -3. Crea un grupo de seguridad, y agrega una nueva regla de grupo de seguridad para cada puerto en la tabla de abajo. Para obtener instrucciones, consulta la guía de OpenStack "[Configurar acceso y seguridad para instancias](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)." - - {% data reusables.enterprise_installation.necessary_ports %} -4. De forma opcional, asocia una IP flotante a la instancia. Según tu configuración de OpenStack, es posible que necesites asignar una IP flotante al proyecto y asociarla a la instancia. Contacta a tu administrador de sistema para determinar si este es tu caso. Para obtener más información, consulta "[Asignar una dirección de IP flotante a una instancia](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" en la documentación de OpenStack. -5. Inicia {% data variables.product.product_location_enterprise %} utilizando la imagen, el volumen de datos y el grupo de seguridad creado en los pasos previos. Para obtener instrucciones, consulta la guía OpenStack "[Iniciar y administrar instancias](https://docs.openstack.org/horizon/latest/user/launch-instances.html)." - -### Configurar la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} -{% data reusables.enterprise_installation.upload-a-license-file %} -{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." -{% data reusables.enterprise_installation.instance-will-restart-automatically %} -{% data reusables.enterprise_installation.visit-your-instance %} - -### Leer más - - - "[Descripción del sistema](/enterprise/admin/guides/installation/system-overview)" diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md deleted file mode 100644 index 626dc72ae9..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Instalar el servidor de GitHub Enterprise en VMare -intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en VMware, debes descargar el cliente vSphere de VMware, y después descargar y desplegar el software de {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/articles/getting-started-with-vmware/ - - /enterprise/admin/articles/installing-vmware-tools/ - - /enterprise/admin/articles/vmware-esxi-virtual-machine-maximums/ - - /enterprise/admin/guides/installation/installing-github-enterprise-on-vmware/ - - /enterprise/admin/installation/installing-github-enterprise-server-on-vmware - - /admin/installation/installing-github-enterprise-server-on-vmware -versions: - ghes: '*' -topics: - - Enterprise ---- -### Prerrequisitos - -- {% data reusables.enterprise_installation.software-license %} -- Debes tener un VMware vSphere ESXi Hypervisor, aplicado a una máquina de metal expuesto que ejecutará {% data variables.product.product_location_enterprise %}. Admitimos versiones 5.5 a 6.7. El Hipervisor de ESXi es gratuito y no incluye el vCenter Server (opcional). Para obtener más información, consulta la [Documentación de VMware ESXi](https://www.vmware.com/products/esxi-and-esx.html). -- Deberás acceder a vSphere Client. Si tienes vCenter Server puedes usar vSphere Web Client. Para obtener más información, consulta la guía de VMware "[Registrarse en vCenter Server al utilizar vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)." - -### Consideraciones relativas al hardware - -{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} - -### Descargar la imagen del {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.enterprise-download-procedural %} -{% data reusables.enterprise_installation.download-license %} -{% data reusables.enterprise_installation.download-appliance %} -4. Selecciona {% data variables.product.prodname_dotcom %} local, después haz clic en **VMware ESXi/vSphere (OVA)**. -5. Haz clic en **Download for VMware ESXi/vSphere (OVA) (Descargar para VMware ESXi/vSphere (OVA))**. - -### Crear la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.create-ghe-instance %} - -1. Por medio de vSphere Windows Client o vCenter Web Client, importa la imagen del {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, consulta la guía de VMware "[Implementar una plantilla OVF u OVA](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)." - - Cuando seleccionas un almacén de datos, elige uno con suficiente espacio para alojar los discos de la VM. Para encontrar las especificaciones mínimas recomendadas de hardware para tu instancia, consulta las "[Consideraciones de hardware](#hardware-considerations)". Te recomendamos un aprovisionamiento robusto con lazy zeroing. - - Deja el casillero **Power on after deployment (Encender después de la implementación)** sin marcar, ya que necesitarás agregar un volumen de almacenamiento adjunto para tus datos del repositorio después de aprovisionar la VM. -{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obtener instrucciones, consulta la guía de VMware "[Agregar un nuevo disco duro a una máquina virtual](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)." - -### Configurar la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} -{% data reusables.enterprise_installation.upload-a-license-file %} -{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." -{% data reusables.enterprise_installation.instance-will-restart-automatically %} -{% data reusables.enterprise_installation.visit-your-instance %} - -### Leer más - - - "[Descripción del sistema](/enterprise/admin/guides/installation/system-overview)" diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md deleted file mode 100644 index f9ed0dca07..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Instalar el servidor de GitHub Enterprise en XenServer -intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en XenServer, debes implementar la imagen de disco {% data variables.product.prodname_ghe_server %} a un servidor XenServer.' -redirect_from: - - /enterprise/admin/guides/installation/installing-github-enterprise-on-xenserver/ - - /enterprise/admin/installation/installing-github-enterprise-server-on-xenserver - - /admin/installation/installing-github-enterprise-server-on-xenserver -versions: - ghes: '*' -topics: - - Enterprise ---- -### Prerrequisitos - -- {% data reusables.enterprise_installation.software-license %} -- Debes instalar el XenServer Hypervisor en la máquina que ejecutará tu máquina virtual (VM) {% data variables.product.prodname_ghe_server %}. Admitimos versiones 6.0 a 7.0. -- Recomendamos utilizar XenCenter Windows Management Console para la configuración inicial. Abajo se incluyen instrucciones utilizando XenCenter Windows Management Console. Para obtener más información, consulta la guía de Citrix "[Cómo descargar e instalar una nueva versión de XenCenter](https://support.citrix.com/article/CTX118531)." - -### Consideraciones relativas al hardware - -{% data reusables.enterprise_installation.hardware-considerations-all-platforms %} - -### Descargar la imagen del {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.enterprise-download-procedural %} -{% data reusables.enterprise_installation.download-license %} -{% data reusables.enterprise_installation.download-appliance %} -4. Selecciona {% data variables.product.prodname_dotcom %} local, después haz clic en **XenServer (VHD)**. -5. Para descargar tu archivo de licencia, haz clic en **Download license (Descargar licencia)**. - -### Crear la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.create-ghe-instance %} - -1. En XenCenter, importa la imagen {% data variables.product.prodname_ghe_server %} que descargaste. Para obtener instrucciones, consulta la guía de XenCenter "[Importar imágenes de disco](https://docs.citrix.com/en-us/xencenter/current-release/vms-importdiskimage.html)." - - Para el paso "Enable Operating System Fixup (Habilitar Ajuste del sistema en funcionamiento)", selecciona **Don't use Operating System Fixup (No usar Ajuste del sistema en funcionamiento)**. - - Deja la VM apagada cuando hayas finalizado. -{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obtener instrucciones, consulta la guía de XenCenter "[Agregar discos virtuales](https://docs.citrix.com/en-us/xencenter/current-release/vms-storage-addnewdisk.html)." - -### Configurar la instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} -{% data reusables.enterprise_installation.upload-a-license-file %} -{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obtener más información, consulta "[Configurar el aparato del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." -{% data reusables.enterprise_installation.instance-will-restart-automatically %} -{% data reusables.enterprise_installation.visit-your-instance %} - -### Leer más - - - "[Descripción del sistema](/enterprise/admin/guides/installation/system-overview)" diff --git a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md deleted file mode 100644 index c36aa67d2e..0000000000 --- a/translations/es-XL/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Configurar una instancia de preparación -intro: 'Puedes utilizar una *instancia de preparación* para probar las modificaciones antes de que se apliquen a {% data variables.product.product_location_enterprise %}. Por ejemplo, podrías utilizar una instancia de preparación para probar nuevas actualizaciones del {% data variables.product.prodname_ghe_server %} o para practicar importar datos de migración.' -redirect_from: - - /enterprise/admin/installation/setting-up-a-staging-instance - - /admin/installation/setting-up-a-staging-instance -versions: - ghes: '*' -topics: - - Enterprise - - Infrastructure - - Upgrades ---- -{% tip %} - -**Sugerencia:** puedes volver a usar tu archivo de licencia existente de {% data variables.product.prodname_enterprise %} siempre que la instancia de preparación no se use para producción. - -{% endtip %} - -Para probar en profundidad un aparato del {% data variables.product.prodname_ghe_server %} deberás considerar los sistemas externos que interactúan con este. Algunos factores que considerar probar son: - - - La autenticación, en especial si se está usando un proveedor externo de autenticación - - La integración con un sistema externo de vales - - La integración con un servidor de integración continua - - Los scripts externos o el software que usan {% data variables.product.prodname_enterprise_api %} - - El servidor externo SMTP para notificaciones por correo electrónico - -1. Realiza una copia de seguridad de tu instancia de producción utilizando {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta la sección "Acerca de {% data variables.product.prodname_enterprise_backup_utilities %}" en "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#about-github-enterprise-server-backup-utilities)." -2. Configura una nueva instancia para que actúe como tu entorno de preparación. Puedes utilizar las mismas guías para aprovisionar e instalar tu instancia de preparación como hiciste para tu instancia de producción. Para obtener más información, consulta "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/)." -3. Restaura tu copia de seguridad a tu instancia de preparación. Para obtener más información, consulta la sección "Restaurar una copia de seguridad" en "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance#restoring-a-backup)." diff --git a/translations/es-XL/content/admin/overview/about-enterprise-accounts.md b/translations/es-XL/content/admin/overview/about-enterprise-accounts.md deleted file mode 100644 index 7134b00bf1..0000000000 --- a/translations/es-XL/content/admin/overview/about-enterprise-accounts.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Acerca de las cuentas de empresa -intro: 'Con {% data variables.product.prodname_ghe_server %}, puedes crear una cuenta empresarial para darle a los administradores una visibilidad centralizada y la administración de su uso de licencia y su facturación.' -redirect_from: - - /enterprise/admin/installation/about-enterprise-accounts - - /enterprise/admin/overview/about-enterprise-accounts -versions: - ghes: '*' - ghae: '*' -topics: - - Accounts - - Enterprise - - Fundamentals ---- - -### Acerca de las cuentas empresariales en {% data variables.product.prodname_ghe_server %} - -Una cuenta empresarial te permite administrar diversas organizaciones de {% data variables.product.prodname_dotcom %} e instancias de {% data variables.product.prodname_ghe_server %}. Tu cuenta de empresa debe tener un controlador, como una organización o cuenta personal en {% data variables.product.prodname_dotcom %}. Los administradores de empresas pueden administrar los parámetros y las referencias, como: - -- El acceso de los miembros y la administración (miembros de la organización, colaboradores externos). -- Facturación y uso (instancias de {% data variables.product.prodname_ghe_server %}, licencias de usuario, paquetes de {% data variables.large_files.product_name_short %}) -- Seguridad (inicio de sesión único, autenticación de dos factores). -- Solicitudes y paquetes de soporte compartidos con {% data variables.contact.enterprise_support %} - -{% data reusables.enterprise-accounts.enterprise-accounts-billing %} - -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 %}](/articles/githubs-products)". Para mejorar tu cuenta a {% data variables.product.prodname_enterprise %} o para comenzar con una cuenta empresarial, contacta a {% data variables.contact.contact_enterprise_sales %}. - -### Administrar las licencias de {% data variables.product.prodname_ghe_server %} enlazadas con tu cuenta empresarial - -{% data reusables.enterprise-accounts.admin-managing-licenses %} diff --git a/translations/es-XL/content/admin/overview/about-the-github-enterprise-server-api.md b/translations/es-XL/content/admin/overview/about-the-github-enterprise-server-api.md deleted file mode 100644 index e5c5c1889e..0000000000 --- a/translations/es-XL/content/admin/overview/about-the-github-enterprise-server-api.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Acerca de la API de servidor de GitHub Enterprise -intro: '{% data variables.product.prodname_ghe_server %} admite la misma poderosa API disponible en {% data variables.product.prodname_dotcom_the_website %} y su propio conjunto de puntos de conexión de API.' -redirect_from: - - /enterprise/admin/installation/about-the-github-enterprise-server-api - - /enterprise/admin/articles/about-the-enterprise-api/ - - /enterprise/admin/articles/using-the-api/ - - /enterprise/admin/categories/api/ - - /enterprise/admin/overview/about-the-github-enterprise-server-api -versions: - enterprise-server: '*' ---- - -Para encontrar toda la documentación para la {% data variables.product.prodname_enterprise_api %}, consulta la sección [Documentos de referencia para la API de REST de {% data variables.product.prodname_enterprise_api %}](/enterprise/{{ currentVersion }}/v3/). Con la API, puedes automatizar muchas tareas administrativas. Algunos ejemplos incluyen los siguientes: - -- Realizar cambios en {% data variables.enterprise.management_console %}. Para obtener más información, consulta la secicón "[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#management-console)". -- Recopila estadísticas acerca de tu instancia. Para obtener más información, consulta la sección "[Estadísticas de administrador](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#admin-stats)." -- Configura la sincronización de LDAP. Para obtener más información, consulta la sección "[LDAP](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#ldap)."{% if currentVersion ver_gt "enterprise-server@2.18" %} -- Administra tu cuenta Enterprise. Para obtener más información, consulta "[Cuentas Enterprise](/v4/guides/managing-enterprise-accounts)"{% endif %} diff --git a/translations/es-XL/content/admin/overview/index.md b/translations/es-XL/content/admin/overview/index.md deleted file mode 100644 index 3d1d6ff877..0000000000 --- a/translations/es-XL/content/admin/overview/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Resumen -intro: 'Con {% data variables.product.prodname_enterprise %} puedes administrar cuentas y acceder a las licencias y a la facturación.' -redirect_from: - - /enterprise/admin/overview -versions: - ghes: '*' - ghae: '*' -children: - - /about-github-ae - - /about-upgrades-to-new-releases - - /about-data-residency - - /about-enterprise-accounts - - /system-overview - - /about-the-github-enterprise-api ---- - -Para obtener más información, o para comprar {% data variables.product.prodname_enterprise %}, consulta [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise). - -### Índice diff --git a/translations/es-XL/content/admin/overview/managing-billing-for-github-enterprise.md b/translations/es-XL/content/admin/overview/managing-billing-for-github-enterprise.md deleted file mode 100644 index 1aa573389f..0000000000 --- a/translations/es-XL/content/admin/overview/managing-billing-for-github-enterprise.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Administrar la facturación para GitHub Enterprise -intro: 'Puedes ver el uso de licencias, facturas, historial de pagos, y otra información de facturación para tu cuenta empresarial y para las instancias de {% data variables.product.prodname_ghe_server %}.' -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /enterprise/admin/installation/managing-billing-for-github-enterprise - - /enterprise/admin/overview/managing-billing-for-github-enterprise -versions: - enterprise-server: '*' ---- - -### Acerca de la facturación para las cuentas de empresa - -Las cuentas empresariales actualmente están disponibles para los clientes de {% data variables.product.prodname_enterprise %} que pagan por factura. La facturación para todas las organizaciones e instancias de {% data variables.product.prodname_ghe_server %} conectadas con tu cuenta empresarial se conjunta en un solo cargo por factura para todos tus servicios pagados de {% data variables.product.prodname_dotcom_the_website %} (incluyendo las licencias pagadas en organizaciones, paquetes de datos de {% data variables.large_files.product_name_long %}, y suscripciones a las apps de {% data variables.product.prodname_marketplace %}). - -Los propietarios de la empresa y los gerente de facturación pueden acceder y administrar todas las configuraciones de facturación para las cuentas de empresa. Para obtener más información acerca de las cuentas empresariales, consulta la sección "[Roles de una cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account)". Para obtener más información acerca de administrar a los gerente de facturación, consulta [Invitar a personas para que administren tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account)". - -### Visualizar tu factura actual - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.billing-tab %} -4. Dabajo de "Acciones Rápidas", da 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 %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.billing-tab %} -4. Dabajo de "Acciones Rápidas", da 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 - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.billing-tab %} -4. Dabajo de "Acciones Rápidas", da clic en **Descargar factura actual**. ![Enlace de descarga de factura actual](/assets/images/help/business-accounts/download-current-invoice.png) - -### Ver tu historial de pagos - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.billing-tab %} -4. Debajo de "Facturación", da clic en **Facturas pasadas** para ver un resumen de tu actividad de facturación pasada. ![Pestaña de ver historial de pago](/assets/images/help/business-accounts/view-payment-history.png) diff --git a/translations/es-XL/content/admin/overview/managing-your-github-enterprise-license.md b/translations/es-XL/content/admin/overview/managing-your-github-enterprise-license.md deleted file mode 100644 index 57233e8952..0000000000 --- a/translations/es-XL/content/admin/overview/managing-your-github-enterprise-license.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Administrar tu licencia de GitHub Enterprise -intro: 'Puedes ver, gestionar y actualizar tu licencia de {% data variables.product.prodname_enterprise %}.' -redirect_from: - - /enterprise/admin/installation/managing-your-github-enterprise-license - - /enterprise/admin/categories/licenses/ - - /enterprise/admin/articles/license-files/ - - /enterprise/admin/installation/about-license-files/ - - /enterprise/admin/articles/downloading-your-license/ - - /enterprise/admin/installation/downloading-your-license/ - - /enterprise/admin/articles/upgrading-your-license/ - - /enterprise/admin/installation/updating-your-license/ - - /enterprise/admin/installation/managing-your-github-enterprise-server-license - - /enterprise/admin/overview/managing-your-github-enterprise-license -versions: - enterprise-server: '*' -topics: - - Enterprise ---- - -### Acerca de las licencias {% data variables.product.prodname_enterprise %} - -Cuando compras o renuevas {% data variables.product.prodname_enterprise %}, recibes un archivo de licencia para validar tu aplicación. Un archivo de licencia tiene una fecha de caducidad y controla la cantidad de licencias de usuario que puedes agregar a {% data variables.product.prodname_enterprise %}. Después de que hayas descargado e instalado {% data variables.product.prodname_enterprise %}, subir el archivo de licencia desbloquea la aplicación para que la puedas usar. - -Puedes asignar las licencias de usuario incluidas en tu licencia de {% data variables.product.prodname_enterprise %} a los usuarios en {% data variables.product.product_location_enterprise %} y en una cuenta empresarial de {% data variables.product.prodname_ghe_cloud %}. Cuando agregas un usuario a algún entorno, se consumirá una licencia. Si un usuario tiene cuentas en ambos ambientes, para consumir únicamente una licencia, su dirección de correo primaria de {% data variables.product.prodname_enterprise %} debe ser la misma que su dirección de correo verificada de {% data variables.product.prodname_ghe_cloud %}. Puedes sincronizar la cantidad de licencias y el uso entre los ambientes. - -Si tu licencia vence {% data variables.product.prodname_ghe_server %}, no podrás acceder a {% data variables.product.product_location_enterprise %} por medio de un navegador web o 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 %}. - -### Subir una nueva licencia a {% data variables.product.prodname_ghe_server %} - -Después de que compras una nueva licencia o actualizas una licencia existente de {% data variables.contact.contact_enterprise_sales %}, debes descargar tu nuevo archivo de licencia. Posteriormente, carga el archivo a {% data variables.product.prodname_ghe_server %} para desbloquear tu nueva licencia de usuario. - -Si quisieras renovar o agregar licencias de usuario a {% data variables.product.prodname_enterprise %}, 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. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.enterprise-licensing-tab %} -4. 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) -5. Inicia sesión en tu instancia de {% data variables.product.prodname_ghe_server %} como administrador de sitio. -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.license-tab %} -12. Dentro de "Quick links (Vínculos rápidos)", haz clic en **Update license (Actualizar licencia)**. ![Actualizar enlace de la licencia](/assets/images/enterprise/business-accounts/update-license-link.png) -13. Para seleccionar tu licencia, da clic en **Archivo de licencia**, o arrastra tu archivo de licencia a **Archivo de licencia**. ![Sube el archivo de licencia](/assets/images/enterprise/management-console/upload-license.png) -14. Da clic en **Cargar**. ![Comienza la actualización](/assets/images/enterprise/management-console/begin-upload.png) - -### Ver el uso de la licencia - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.enterprise-licensing-tab %} -4. Revisa tus licencias actuales de {% data variables.product.prodname_enterprise %}, así como las licencias de usuario disponibles y consumidas. - -### Sincronizar de forma automática el uso de la licencia de usuario con {% data variables.product.prodname_ghe_cloud %} - -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 %}](/enterprise/{{currentVersion}}/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)." - -### Sincronizar el uso de licencias de usuario manualmente entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} - -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. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.license-tab %} -5. Dentro de "Quick links (Vínculos rápidos)", para descargar un archivo que contiene tu uso de licencia actual en {% data variables.product.prodname_ghe_server %}, haz clic en **Export license usage (Exportar uso de licencia)**. ![Exporta el vínculo de uso de la licencia](/assets/images/enterprise/business-accounts/export-license-usage-link.png) -6. Ve a {% data variables.product.prodname_ghe_cloud %}. -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.enterprise-licensing-tab %} -10. Debajo de "Instancias de Enterprise Server", da clic en **Agregar uso del servidor**. ![Sube el vínculo de uso de los servidores de GitHub Enterprise](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) -11. Sube el archivo JSON que descargaste de {% data variables.product.prodname_ghe_server %}. ![Arrastra y suelta o selecciona un archivo para cargar](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) diff --git a/translations/es-XL/content/admin/overview/system-overview.md b/translations/es-XL/content/admin/overview/system-overview.md deleted file mode 100644 index 22d911ab80..0000000000 --- a/translations/es-XL/content/admin/overview/system-overview.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -title: Descripción del sistema -intro: 'El {% data variables.product.prodname_ghe_server %} es la copia privada de tu organización de {% data variables.product.prodname_dotcom %} contenida dentro de un aparato virtual, alojada localmente o en la nube, que configuras y controlas.' -redirect_from: - - /enterprise/admin/installation/system-overview - - /enterprise/admin/overview/system-overview -versions: - ghes: '*' -topics: - - Enterprise - - Fundamentals - - Infrastructure - - Security - - Storage ---- - -### Arquitectura de almancenamiento - -El {% data variables.product.prodname_ghe_server %} requiere dos volúmenes de almacenamiento, uno instalado en la ruta del *sistema de archivos raíz* (`/`) y otro en la ruta del *sistema de archivos del usuario* (`/data/user`). Esta arquitectura simplifica los procedimientos de actualización, reversión y recuperación al separar el entorno del software que se ejecuta de los datos de aplicación persistentes. - -El sistema de archivos raíz está incluido en la imagen de máquina distribuida. Contiene el sistema operativo base y el entorno de aplicación del {% data variables.product.prodname_ghe_server %}. El sistema de archivos raíz debería tratarse como efímero. Cualquier dato en el sistema de archivos raíz será reemplazado cuando se actualice con futuros lanzamientos del {% data variables.product.prodname_ghe_server %}. - -El sistema de archivos raíz contiene: - - Los certificados de autoridad de certificación personalizados (CA) (en */usr/local/share/ca-certificates*) - - Las configuraciones de red personalizadas - - Las configuraciones de firewall personalizadas - - El estado de replicación - -El sistema de archivos del usuario contiene la configuración y los datos del usuario, tales como: - - Repositorios Git - - Bases de datos - - Índices de búsqueda - - Contenido publicado en los sitios {% data variables.product.prodname_pages %} - - Archivos grandes de {% data variables.large_files.product_name_long %} - - Entornos de enlaces de pre-recepción - -### Opciones de implementación - -Puedes implementar el {% data variables.product.prodname_ghe_server %} como un aparato virtual único, o en una configuración de alta disponibilidad. Para obtener más información, consulta "[Configurar {% data variables.product.prodname_ghe_server %} para alta disponibilidad](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." - -Algunas organizaciones con decenas de miles de programadores podrían también beneficiarse de una Agrupación del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Acerca de las agrupaciones](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-clustering)." - -### Retención de datos y redundancia de centro de datos - -{% danger %} - -Antes de usar {% data variables.product.prodname_ghe_server %} en un entorno de producción, recomendamos firmemente que configures copias de seguridad y un plan de recuperación ante desastres. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)". - -{% enddanger %} - -El {% data variables.product.prodname_ghe_server %} incluye soporte para copias de seguridad en línea e incrementales con [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils). Puedes tomar instantáneas incrementales sobre un enlace de red seguro (el puerto administrativo SSH) sobre grandes distancias para el almacenamiento externo o geográficamente disperso. Puedes restaurar instantáneas a través de la red en un nuevo aparato virtual recientemente aprovisionado al momento de la recuperación en el caso de un desastre en el centro de datos principal. - -Además se admiten las copias de seguridad de red, las instantáneas de disco AWS (EBS) y VMware de los volúmenes de almacenamiento del usuario mientras que el aparato está fuera de línea o en modo mantenimiento. Las instantáneas de volumen regulares pueden usarse como una alternativa de bajo costo y baja complejidad para las copias de seguridad de red con {% data variables.product.prodname_enterprise_backup_utilities %} si tus requisitos de nivel de servicio permiten un mantenimiento fuera de línea regular. - -Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)". - -### Seguridad - -El {% data variables.product.prodname_ghe_server %} es un aparato virtual que se ejecuta en tu infraestructura y está gobernado por tus controles de seguridad de información existentes, como cortafuegos, IAM, monitoreo y VPN. Usar el {% data variables.product.prodname_ghe_server %} puede ayudarte a evitar problemas de cumplimiento regulatorio que surgen de las soluciones basadas en la nube. - -El {% data variables.product.prodname_ghe_server %} también incluye características de seguridad adicionales. - -- [Sistema operativo, software y parches](#operating-system-software-and-patches) -- [Seguridad de la red](#network-security) -- [Seguridad de la aplicación](#application-security) -- [Servicios externos y acceso de soporte](#external-services-and-support-access) -- [Comunicación encriptada](#encrypted-communication) -- [Usuarios y permisos de acceso](#users-and-access-permissions) -- [Autenticación](#authentication) -- [Auditoría y registro de acceso](#audit-and-access-logging) - -#### Sistema operativo, software y parches - -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. - -#### Seguridad de la red - -El cortafuegos interno del {% data variables.product.prodname_ghe_server %} restringe el acceso de la red a los servicios del aparato. Están disponibles en la red únicamente los servicios necesarios para que el aparato funcione. Para obtener más información, consulta "[Puertos de red](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports)." - -#### Seguridad de la aplicación - -El equipo de seguridad de la aplicación de {% data variables.product.prodname_dotcom %} se centra en la evaluación de vulnerabilidad, la prueba de penetración y la revisión del código para los productos de {% data variables.product.prodname_dotcom %} , incluido el {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} también contrata firmas de seguridad externas para proporcionar evaluaciones de seguridad puntuales de los productos de {% data variables.product.prodname_dotcom %}. - -#### Servicios externos y acceso de soporte - -El {% data variables.product.prodname_ghe_server %} puede funcionar sin ningún acceso de salida de tu red a servicios externos. De forma opcional, puedes habilitar la integración con servicios externos para la entrega de correo electrónico, el monitoreo externo y el reenvío de registros. Para más información, consulta "[Configurar correo electrónico para notificaciones](/enterprise/{{ currentVersion }}/admin/user-management/configuring-email-for-notifications)," "[Configurar el monitoreo externo](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)" y "[Reenvío de registros](/enterprise/{{ currentVersion }}/admin/installation/log-forwarding)." - -Puedes recopilar y enviar manualmente datos de resolución de problemas a {% data variables.contact.github_support %}. Para obtener más información, consulta "[Proporcionar datos a {% data variables.contact.github_support %}](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)." - -#### Comunicación encriptada - -{% data variables.product.prodname_dotcom %} diseña {% data variables.product.prodname_ghe_server %} para ejecutar detrás de tu cortafuegos corporativo. Para asegurar la comunicación a través del cable, te alentamos a habilitar la seguridad de la capa de transporte (TLS). El {% data variables.product.prodname_ghe_server %} admite certificados TLS comerciales de 2048 bits y superiores para el tráfico HTTPS. Para obtener más información, consulta "[Configurar TLS](/enterprise/{{ currentVersion }}/admin/installation/configuring-tls)." - -Por defecto, el aparato también ofrece acceso a Secure Shell (SSH) para el acceso al repositorio utilizando Git y con fines administrativos. Para obtener más información, consulta "[Acerca de SSH](/enterprise/user/articles/about-ssh)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." - -#### Usuarios y permisos de acceso - -El {% data variables.product.prodname_ghe_server %} proporciona tres tipos de cuentas. - -- La cuenta de usuario de Linux del `administrador` ha controlado el acceso al sistema operativo subyacente, incluido el sistema de archivos directo y el acceso a la base de datos. Un pequeño conjunto de administradores de confianza debería tener acceso a esta cuenta, a la que pueden acceder por medio de SSH. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." -- Las cuentas de usuario en la aplicación web del aparato tienen acceso completo a sus propios datos y a cualquier dato que otros usuarios u organizaciones concedan de manera explícita. -- Los administradores del sitio en la aplicación web del aparato son cuentas de usuario que pueden administrar los ajustes de aplicaciones web y de aparatos de alto nivel, la configuración de cuenta de usuario y de organización y los datos del repositorio. - -Para más información sobre los permisos de usuario del {% data variables.product.prodname_ghe_server %}, consulta "[Permisos de acceso en GitHub](/enterprise/user/articles/access-permissions-on-github)." - -#### Autenticación - -El {% data variables.product.prodname_ghe_server %} proporciona cuatro métodos de autenticación. - -- La autenticación de claves públicas SSH proporciona acceso del repositorio usando Git y el shell administrativo. Para obtener más información, consulta "[Acerca de SSH](/enterprise/user/articles/about-ssh)" y "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)." -- El nombre de usuario y la autenticación de contraseña con cookies HTTP proporciona acceso a la aplicación web y la gestión de sesiones, con autenticación opcional de dos factores (2FA). Para obtener más información, consulta "[Usar la autenticación incorporada](/enterprise/{{ currentVersion }}/admin/user-management/using-built-in-authentication)." -- La autenticación externa LDAP, SAML o CAS mediante un servicio LDAP, SAML Identity Provider (IdP) u otro servicio compatible proporciona acceso a la aplicación web. Para más información, consulta "[Autenticar usuarios para tu instancia de servidor de GitHub Enterprise](/enterprise/{{ currentVersion }}/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance)." -- OAuth y los token de acceso personal proporcionan acceso a los datos del repositorio de Git y a API para clientes externos y servicios. 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)". - -#### Auditoría y registro de acceso - -El {% data variables.product.prodname_ghe_server %} almacena tanto registros tradicionales de sistema operativo como de aplicación. La aplicación también escribe registros de auditoría y de seguridad detallados, que el {% data variables.product.prodname_ghe_server %} almacena de forma permanente. Puedes reenviar ambos tipos de registros en tiempo real a múltiples destinos a través del protocolo `syslog-ng`. Para obtener más información, consulta "[Redireccionamiento de registro](/enterprise/{{ currentVersion }}/admin/installation/log-forwarding)." - -Los registros de acceso y de auditoría incluyen información como la siguiente. - -##### Registros de acceso - -- Registros completos de servidor web tanto para el navegador como para el acceso a la API -- Registros completos para acceder a los datos del repositorio por medio de protocolos Git, HTTPS y SSH -- Registros de acceso administrativo por medio de HTTPS y SSH - -##### Registros de auditoría - -- Inicios de sesión del usuario, restablecimientos de contraseña, solicitudes 2FA, cambios en la configuración del correo electrónico y cambios en aplicaciones autorizadas y API -- Acciones de administrador del sitio, como desbloquear cuentas de usuario y repositorios -- Eventos push de repositorio, permisos de acceso, transferencias y renombres -- Cambios de membresía de la organización, incluida la creación y la destrucción de equipo - -### Dependencias de código abierto para {% data variables.product.prodname_ghe_server %} - -Puedes consultar una lista completa de dependencias en la versión de tu aparato de {% data variables.product.prodname_ghe_server %}, y la licencia de cada proyecto, en `http(s)://HOSTNAME/site/credits`. - -Están disponibles en tu aparato los tarballes con una lista completa de dependencias y metadatos asociados: -- Para conocer las dependencias comunes a todas las plataformas, ingresa en `/usr/local/share/enterprise/dependencies--base.tar.gz`. -- Para conocer las dependencias específicas de una plataforma, ingresa en `/usr/local/share/enterprise/dependencies--.tar.gz`. - -También están disponibles los tarballes, con una lista completa de las dependencias y los metadatos, en `https://enterprise.github.com/releases//download.html`. - -### Leer más - -- "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)" -- "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)" -- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap` diff --git a/translations/es-XL/content/admin/packages/configuring-packages-support-for-your-enterprise.md b/translations/es-XL/content/admin/packages/configuring-packages-support-for-your-enterprise.md deleted file mode 100644 index c5ce3fa95d..0000000000 --- a/translations/es-XL/content/admin/packages/configuring-packages-support-for-your-enterprise.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Configuring packages support for your enterprise -intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by enabling or disabling each package ecosystem.' -redirect_from: - - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise - - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise -versions: - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -You can enable or disable each package ecosystem for your instance. You can set an ecosystem you previously enabled to **Read-Only** to prevent new packages from being uploaded, while allowing existing packages to be downloaded. - -To use {% data variables.product.prodname_registry %} with Docker, you must have subdomain isolation enabled for your instance. For more information, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_site_admin_settings.packages-tab %} -1. Under "Ecosystem Toggles", for each package type, select **Enabled**, **Read-Only**, or **Disabled**. ![Ecosystem toggles](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/packages/configuring-third-party-storage-for-packages.md b/translations/es-XL/content/admin/packages/configuring-third-party-storage-for-packages.md deleted file mode 100644 index b4b83facf1..0000000000 --- a/translations/es-XL/content/admin/packages/configuring-third-party-storage-for-packages.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Configuring third-party storage for packages -intro: 'You can configure the third-party service that {% data variables.product.prodname_registry %} uses to store your enterprise''s packages.' -redirect_from: - - /enterprise/admin/packages/configuring-third-party-storage-for-packages - - /enterprise/admin/packages/configuring-third-party-storage-for-packages -versions: - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -### About third-party storage for {% data variables.product.prodname_registry %} - -{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}. - -At this time, {% data variables.product.prodname_registry %} supports blob storage with Amazon Web Services (AWS) S3. MinIO is also supported, but configuration is not currently implemented in the {% data variables.product.product_name %} interface. You can use MinIO for storage by following the instructions for AWS S3, entering the analagous information for your MinIO configuration. - -For the best experience, we recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. - -### Configuring AWS S3 as storage for {% data variables.product.prodname_registry %} - -{% warning %} - -**Warning:** Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. - -{% endwarning %} - -Before you configure AWS as storage for {% data variables.product.prodname_registry %}, make sure your AWS access key ID and secret have the following permissions: - - `s3:PutObject` - - `s3:GetObject` - - `s3:ListBucketMultipartUploads` - - `s3:ListMultipartUploadParts` - - `s3:AbortMultipartUpload` - - `s3:DeleteObject` - - `s3:ListBucket` - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_site_admin_settings.packages-tab %} -1. Under "AWS Service URL", type the S3 endpoint URL for your bucket's region. ![AWS Service URL field](/assets/images/enterprise/site-admin-settings/storage-service-url.png) -1. Under "AWS S3 Bucket", type the name of the S3 bucket you want to use to store package artifacts. ![AWS S3 Bucket field](/assets/images/enterprise/site-admin-settings/aws-s3-bucket.png) -1. Under "AWS S3 Access Key", type your access key for S3. ![AWS S3 Access Key field](/assets/images/enterprise/site-admin-settings/aws-s3-access-key.png) -1. Under "AWS S3 Secret Key", type your secret key for S3. ![AWS S3 Secret Key field](/assets/images/enterprise/site-admin-settings/aws-s3-secret-key.png) -1. Under "AWS S3 Region", type your region for S3. ![AWS S3 Region field](/assets/images/enterprise/site-admin-settings/aws-s3-region.png) -{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-XL/content/admin/packages/enabling-github-packages-for-your-enterprise.md b/translations/es-XL/content/admin/packages/enabling-github-packages-for-your-enterprise.md deleted file mode 100644 index 9a6ae84e24..0000000000 --- a/translations/es-XL/content/admin/packages/enabling-github-packages-for-your-enterprise.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Enabling GitHub Packages for your enterprise -intro: 'You can start using {% data variables.product.prodname_registry %} on your instance by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' -redirect_from: - - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise - - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise - - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise -versions: - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -1. After you've been invited to join the beta, to enable {% data variables.product.prodname_registry %} for your instance, follow the instructions from your account representative. -1. Configure third-party storage for your enterprise's packages. For more information, see "[Configuring third-party storage for packages](/enterprise/admin/packages/configuring-third-party-storage-for-packages)." -1. Enable or disable each package ecosystem for your enterprise. For more information, see "[Configuring packages support for your enterprise](/enterprise/admin/packages/configuring-packages-support-for-your-enterprise)." -1. If subdomain isolation is enabled for your instance, which is required to use {% data variables.product.prodname_registry %} with Docker, create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Make sure each package host URL includes `https://`. - - You can create the certificate manually or using Let's Encrypt. If you already use Let's Encrypt, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)." diff --git a/translations/es-XL/content/admin/packages/index.md b/translations/es-XL/content/admin/packages/index.md deleted file mode 100644 index ef45de2cd3..0000000000 --- a/translations/es-XL/content/admin/packages/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Managing GitHub Packages for your enterprise -shortTitle: Paquetes de GitHub -intro: 'You can enable {% data variables.product.prodname_registry %} for your enterprise and manage {% data variables.product.prodname_registry %} settings and allowed packaged types.' -redirect_from: - - /enterprise/admin/packages -versions: - ghes: '*' -topics: - - Enterprise -children: - - /getting-started-with-github-packages-for-your-enterprise - - /enabling-github-packages-with-aws - - /enabling-github-packages-with-azure-blob-storage - - /enabling-github-packages-with-minio - - /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages - - /configuring-package-ecosystem-support-for-your-enterprise ---- -{% data reusables.package_registry.packages-ghes-release-stage %} diff --git a/translations/es-XL/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/es-XL/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md deleted file mode 100644 index ec299f0ecd..0000000000 --- a/translations/es-XL/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -title: Enforcing repository management policies in your enterprise -intro: 'Enterprise owners can enforce certain repository management policies for all organizations owned by an enterprise account, or allow policies to be set in each organization.' -redirect_from: - - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance - - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility - - /enterprise/admin/user-management/preventing-users-from-changing-a-repositorys-visibility - - /enterprise/admin/user-management/restricting-repository-creation-in-your-instance - - /enterprise/admin/user-management/preventing-users-from-deleting-organization-repositories - - /enterprise/admin/installation/setting-git-push-limits - - /enterprise/admin/guides/installation/git-server-settings/ - - /enterprise/admin/articles/setting-git-push-limits/ - - /enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories - - /enterprise/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories - - /enterprise/admin/developer-workflow/blocking-force-pushes-on-your-appliance - - /enterprise/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization - - /enterprise/admin/developer-workflow/blocking-force-pushes-to-a-repository - - /enterprise/admin/articles/blocking-force-pushes-on-your-appliance/ - - /enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access-to-a-repository/ - - /enterprise/admin/user-management/preventing-users-from-changing-anonymous-git-read-access - - /enterprise/admin/articles/blocking-force-pushes-to-a-repository/ - - /enterprise/admin/articles/block-force-pushes/ - - /enterprise/admin/articles/blocking-force-pushes-for-a-user-account/ - - /enterprise/admin/articles/blocking-force-pushes-for-an-organization/ - - /enterprise/admin/articles/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization/ - - /enterprise/admin/developer-workflow/blocking-force-pushes - - /enterprise/admin/policies/enforcing-repository-management-policies-in-your-enterprise - - /admin/policies/enforcing-repository-management-policies-in-your-enterprise -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Policies - - Security ---- -### Configuring the default visibility of new repositories on your appliance - -Each time someone creates a new repository on {% data variables.product.product_location_enterprise %}, that person must choose a visibility for the repository. When you configure a default visibility setting for the instance, you choose which visibility is selected by default. For more information on repository visibility, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." - -If a site administrator disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Restricting repository creation in your instance](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)." - -{% tip %} - -**Tip:** You can restrict the ability to change repository visibility to site administrators only. For more information, see "[Preventing users from changing a repository's visibility](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility)." - -{% endtip %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -1. Under "Default repository visibility", use the drop-down menu and select a default visibility. - ![Drop-down menu to choose the default repository visibility for your instance](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png) - -{% data reusables.enterprise_installation.image-urls-viewable-warning %} - -### Setting a policy for changing a repository's visibility - -When you prevent members from changing repository visibility, only site administrators have the ability to make public repositories private or make private repositories public. - -If a site administrator has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If a site administrator has restricted member repository creation to private repositories only, then members will only be able to change repositories from public to private. For more information, see "[Setting a policy for repository creation](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)." - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.repositories-tab %} -5. Under "Repository visibility change", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} - -{% data reusables.enterprise-accounts.repository-visibility-policy %} - -### Setting a policy for repository creation - -{% data reusables.organizations.repo-creation-constants %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.repositories-tab %} -5. Under "Repository creation", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -{% if currentVersion ver_gt "enterprise-server@2.19" %} -{% data reusables.enterprise-accounts.repo-creation-policy %} -{% data reusables.enterprise-accounts.repo-creation-types %} -{% else %} -6. Under "Repository creation", use the drop-down menu and choose a policy. - ![Drop-down menu with repository creation policies](/assets/images/enterprise/site-admin-settings/repository-creation-drop-down.png) -{% endif %} - -### Setting a policy for repository deletion and transfer - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.repositories-tab %} -5. Under "Repository deletion and transfer", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} - -{% data reusables.enterprise-accounts.repository-deletion-policy %} - -### Setting a policy for Git push limits - -To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories on your instance. - -By default, when you enforce repository upload limits, people cannot add or update files larger than 100 MB. - -{% if currentVersion ver_lt "enterprise-server@2.20" %} -{% tip %} - -**Note:** Only files larger than {% data variables.large_files.warning_size %} will be checked against the Git push limit. If you need to set a lower push limit, contact {% data variables.contact.contact_ent_support %} for assistance. - -{% endtip %} -{% endif %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -4. Under "Repository upload limit", use the drop-down menu and click a maximum object size. -![Drop-down menu with maximum object size options](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png) -5. Optionally, to enforce a maximum upload limit for all repositories on {% data variables.product.product_location_enterprise %}, select **Enforce on all repositories** -![Enforce maximum object size on all repositories option](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png) - -### Configuring the merge conflict editor for pull requests between repositories - -Requiring users to resolve merge conflicts locally on their computer can prevent people from inadvertently writing to an upstream repository from a fork. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -1. Under "Conflict editor for pull requests between repositories", use the drop-down menu, and click **Disabled**. - ![Drop-down menu with option to disable the merge conflict editor](/assets/images/enterprise/settings/conflict-editor-settings.png) - -### Configuring force pushes - -Each repository inherits a default force push setting from the settings of the user account or organization to which it belongs. Likewise, each organization and user account inherits a default force push setting from the force push setting for the entire appliance. If you change the force push setting for the appliance, it will change for all repositories owned by any user or organization. - -#### Blocking all force pushes on your appliance - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -4. Under "Force pushes", use the drop-down menu, and click **Allow**, **Block** or **Block to the default branch**. -![Force pushes dropdown](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png) -5. Optionally, select **Enforce on all repositories**, which will override organization and repository level settings for force pushes. - -#### Blocking force pushes to a specific repository - -{% data reusables.enterprise_site_admin_settings.override-policy %} - -{% data reusables.enterprise_site_admin_settings.sign-in %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.repository-search %} -{% data reusables.enterprise_site_admin_settings.click-repo %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -4. Select **Block** or **Block to the default branch** under **Push and Pull**. - ![Block force pushes](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png) - -#### Blocking force pushes to repositories owned by a user account or organization - -Repositories inherit force push settings from the user account or organization to which they belong. User accounts and organizations in turn inherit their force push settings from the force push settings for the entire appliance. - -You can override the default inherited settings by configuring the settings for a user account or organization. - -{% data reusables.enterprise_site_admin_settings.sign-in %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user-or-org %} -{% data reusables.enterprise_site_admin_settings.click-user-or-org %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -5. Under "Repository default settings" in the "Force pushes" section, select - - **Block** to block force pushes to all branches. - - **Block to the default branch** to only block force pushes to the default branch. - ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png) -6. Optionally, select **Enforce on all repositories** to override repository-specific settings. Note that this will **not** override an appliance-wide policy. - ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png) - -### Configuring anonymous Git read access - -{% data reusables.enterprise_user_management.disclaimer-for-git-read-access %} - -If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) on your instance, you can allow repository administrators to enable anonymous Git read access to public repositories. - -Enabling anonymous Git read access allows users to bypass authentication for custom tools on your instance. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.prodname_ghe_server %}) will have read access to the repository without authentication. - -If necessary, you can prevent repository administrators from changing anonymous Git access settings for repositories on {% data variables.product.product_location_enterprise %} by locking the repository's access settings. After you lock a repository's Git read access setting, only a site administrator can change the setting. - -{% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %} - -{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %} - -#### Setting anonymous Git read access for all repositories - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -4. Under "Anonymous Git read access", use the drop-down menu, and click **Enabled**. -![Anonymous Git read access drop-down menu showing menu options "Enabled" and "Disabled"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png) -3. Optionally, to prevent repository admins from changing anonymous Git read access settings in all repositories on your instance, select **Prevent repository admins from changing anonymous Git read access**. -![Select checkbox to prevent repository admins from changing anonymous Git read access settings for all repositories on your instance](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png) - -#### Setting anonymous Git read access for a specific repository - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.repository-search %} -{% data reusables.enterprise_site_admin_settings.click-repo %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -6. Under "Danger Zone", next to "Enable Anonymous Git read access", click **Enable**. -!["Enabled" button under "Enable anonymous Git read access" in danger zone of a repository's site admin settings ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png) -7. Review the changes. To confirm, click **Yes, enable anonymous Git read access.** -![Confirm anonymous Git read access setting in pop-up window](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png) -8. Optionally, to prevent repository admins from changing this setting for this repository, select **Prevent repository admins from changing anonymous Git read access**. -![Select checkbox to prevent repository admins from changing anonymous Git read access for this repository](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png) 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 deleted file mode 100644 index 74f0f89501..0000000000 --- a/translations/es-XL/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Requerir políticas para tu empresa -redirect_from: - - /enterprise/admin/policies/enforcing-policies-for-your-enterprise -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /enforcing-repository-management-policies-in-your-enterprise - - /restricting-email-notifications-for-your-enterprise - - /enforcing-policies-for-advanced-security-in-your-enterprise ---- - diff --git a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md b/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md deleted file mode 100644 index 3c0c26cad2..0000000000 --- a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Acerca de ganchos de pre-recepción -intro: 'Los *ganchos de pre-recepción* son scripts que se ejecutan en el aparato {% data variables.product.prodname_ghe_server %} que puedes usar para implementar controles de calidad.' -redirect_from: - - /enterprise/admin/developer-workflow/about-pre-receive-hooks - - /enterprise/admin/policies/about-pre-receive-hooks - - /admin/policies/about-pre-receive-hooks -versions: - ghes: '*' -topics: - - Enterprise - - Policies - - Pre-receive hooks ---- -Cuando se produce una subida, cada script se ejecuta en un entorno aislado y puede realizar verificaciones en el contenido que se subió. Los scripts provocarán la aceptación de la subida si el estado de salida es 0, o rechazado si el estado de salida no es cero. - -### Escenarios de uso -Usa los ganchos de pre-recepción para satisfacer las reglas comerciales, implementar el cumplimiento regulatorio y prevenir determinados errores comunes. - -Ejemplos de cómo usar los ganchos de pre-recepción: - -- Requerir mensajes de confirmación para seguir un patrón o formato específico, como incluir un número de ticket válido o finalizar luego de una determinada duración. -- Buscar una rama o repositorio al rechazar todas las subidas. -- Impedir que se agreguen datos sensibles al repositorio al bloquear palabras clave, patrones o tipos de archivo. -- Impedir que un autor PR se fusione con sus propios cambios. - -### Impactar en el rendimiento y los flujos de trabajo flujo de trabajo -El impacto que causa en los programadores y sus flujos de trabajo puede ser significativo y debe considerarse cuidadosamente. Los ganchos de pre-recepción que se basan en necesidades comerciales y se implementan cuidadosamente brindarán la mayor cantidad de beneficios a la organización en conjunto. - -Los ganchos de pre-recepción pueden tener efectos no deseados sobre el rendimiento de {% data variables.product.product_location_enterprise %} y deberían implementarse y revisarse cuidadosamente. diff --git a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md b/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md deleted file mode 100644 index 3150f00bb9..0000000000 --- a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: Crear un entorno de gancho de pre-recepción -intro: 'Para ejecutar los ganchos de pre-recepción, usa el entorno de pre-recepción predeterminado o crea un entorno personalizado.' -redirect_from: - - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-environment - - /enterprise/admin/policies/creating-a-pre-receive-hook-environment - - /admin/policies/creating-a-pre-receive-hook-environment -versions: - ghes: '*' -topics: - - Enterprise - - Policies - - Pre-receive hooks ---- -Un entorno de pre-recepción para el {% data variables.product.prodname_ghe_server %} es un entorno Linux [`chroot`](https://en.wikipedia.org/wiki/Chroot). Dado que los ganchos de pre-recepción se ejecutan en todos los eventos de extracción, deberían ser rápidos y livianos. Normalmente, el entorno necesario para tales verificaciones será mínimo. - -El {% data variables.product.prodname_ghe_server %} brinda un entorno predeterminado que incluye estos paquetes: `awk`, `bash`, `coreutils`, `curl`, `find`, `gnupg`, `grep`, `jq`, `sed`. - -Si tu entorno no cumple con uno de los requisitos específicos, como respaldo para un idioma en particular, puedes crear y cargar tu propio entorno `chroot` en Linux de 64 bits. - -### Crear un entorno de gancho de pre-recepción mediante Docker - -Puedes usar una herramienta de administración de contenedores de Linux para crear un entorno de gancho de pre-recepción. Este ejemplo usa [Alpine Linux](http://www.alpinelinux.org/) y [Docker](https://www.docker.com/). - -{% data reusables.linux.ensure-docker %} -2. Crea el archivo `Dockerfile.alpine-3.3` que contiene esta información: - - ``` - FROM gliderlabs/alpine:3.3 - RUN apk add --no-cache git bash - ``` -3. Desde el directorio de trabajo que contiene `Dockerfile.dev`, crea una imagen: - - ```shell - $ docker build -f Dockerfile.alpine-3.3 -t pre-receive.alpine-3.3 . - > Sending build context to Docker daemon 12.29 kB - > Step 1 : FROM gliderlabs/alpine:3.3 - > ---> 8944964f99f4 - > Step 2 : RUN apk add --no-cache git bash - > ---> Using cache - > ---> 0250ab3be9c5 - > Successfully built 0250ab3be9c5 - ``` -4. Crea un contenedor: - - ```shell - $ docker create --name pre-receive.alpine-3.3 pre-receive.alpine-3.3 /bin/true - ``` -5. Exporta el contenedor Docker a un archivo `tar` comprimido como `gzip`: - - ```shell - $ docker export pre-receive.alpine-3.3 | gzip > alpine-3.3.tar.gz - ``` - - Este archivo `alpine-3.3.tar.gz` está listo para subirse al aparato del {% data variables.product.prodname_ghe_server %}. - -### Crear un entorno de gancho de pre-recepción mediante chroot - -1. Crea un entorno `chroot` en Linux. -2. Crea un archivo `tar` comprimido como `gzip` del directorio `chroot`. - ```shell - $ cd /path/to/chroot - $ tar -czf /path/to/pre-receive-environment.tar.gz . - ``` - - {% note %} - - **Notas:** - - No incluyas las rutas iniciales del directorio en los archivos dentro del tar, tales como `/path/to/chroot`. - - La ruta `/bin/sh` debe existir y ser ejecutable como punto de entrada al ambiente chroot. - - A diferencia de los chroots tradicionales, el ambiente de chroot para ganchos de pre-recepción no requiere el directorio `dev`. - - {% endnote %} - -Para obtener más información acerca de la creación de un entorno chroot, consulta "[Chroot](https://wiki.debian.org/chroot)" desde *Debian Wiki*, "[BasicChroot](https://help.ubuntu.com/community/BasicChroot)" desde *Ubuntu Community Help Wiki* o "[Instalar Alpine Linux en un chroot](http://wiki.alpinelinux.org/wiki/Installing_Alpine_Linux_in_a_chroot)" desde *Alpine Linux Wiki*. - -### Cargar un entorno de pre-recepción en el {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. Haz clic en **Manage environments** (Administrar entornos). ![Administrar entornos](/assets/images/enterprise/site-admin-settings/manage-pre-receive-environments.png) -6. Haz clic en **Add environment** (Agregar entorno). ![Agregar entorno](/assets/images/enterprise/site-admin-settings/add-pre-receive-environment.png) -7. Escribe el nombre que desees en el campo **Environment name** (Nombre del entorno). ![Nombre del entorno](/assets/images/enterprise/site-admin-settings/pre-receive-environment-name.png) -8. Escribe la URL del archivo `*.tar.gz` que contiene tu entorno. ![Cargar un entorno desde una URL](/assets/images/enterprise/site-admin-settings/upload-environment-from-url.png) -9. Haz clic en **Add environment** (Agregar entorno). ![Agregar el botón de entorno](/assets/images/enterprise/site-admin-settings/add-environment-button.png) - -### Cargar un entorno de pre-recepción mediante el shell administrativo -1. Carga un archivo `*.tar.gz` legible que contenga tu entorno a un host web y copia la URL o transfiere el archivo al aparato del {% data variables.product.prodname_ghe_server %} mediante `scp`. Al usar `scp`, es posible que necesites ajustar los permisos del archivo `*.tar.gz` para que todos puedan leerlo. -1. Conecta con el shell administrativo. -2. Usa el comando `ghe-hook-env-create` y escribe el nombre que desees para el entorno como primer argumento y la ruta local completa o la dirección URL de un archivo `*.tar.gz` que contenga tu entorno como segundo argumento. - - ```shell - admin@ghe-host:~$ ghe-hook-env-create AlpineTestEnv /home/admin/alpine-3.3.tar.gz - > Pre-receive hook environment 'AlpineTestEnv' (2) has been created. - ``` diff --git a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md deleted file mode 100644 index d7acbe0f7f..0000000000 --- a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md +++ /dev/null @@ -1,206 +0,0 @@ ---- -title: Crear un script de ganchos de pre-recepción -intro: Usa los scripts de los ganchos de pre-recepción para crear requisitos para aceptar o rechazar una subida en función de los contenidos. -redirect_from: - - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-script - - /enterprise/admin/policies/creating-a-pre-receive-hook-script - - /admin/policies/creating-a-pre-receive-hook-script -versions: - ghes: '*' -miniTocMaxHeadingLevel: 3 -topics: - - Enterprise - - Policies - - Pre-receive hooks ---- -Puedes ver los ejemplos de los ganchos de pre-recepción para {% data variables.product.prodname_ghe_server %} en el repositorio [`github/platform-samples`](https://github.com/github/platform-samples/tree/master/pre-receive-hooks). - -### Escribir un script de ganchos de pre-recepción -Un script de gancho de pre-recepción se ejecuta en un entorno de gancho de pre-recepcion en el aparato {% data variables.product.prodname_ghe_server %}. Cuando crees un script de gancho de pre-recepción, considera la entrada, salida, el estado de salida y las variables de entorno. - -#### Entrada (stdin) -Después de que se produce la subida y antes de que las ref se actualicen en el repositorio remoto, el proceso `git-receive-pack` invoca el script del gancho de pre-recepción con la entrada estándar de una línea por ref que se actualizará: - -` SP SP LF` - -Esta cadena representa estos argumentos: - -| Argumento | Descripción | -|:------------------- |:-------------------------------------------------------------------------------------------------------------------- | -| `` | Nombre del objeto antiguo almacenado en la `ref`.
    Cuando *creas* una nueva`ref`, esto equivale a 40 ceros. | -| `` | El nombre del objeto nuevo se almacenará en la `ref`.
    Cuando *eliminas* una `ref`, equivale a 40 ceros. | -| `` | El nombre completo de la `ref`. | - -Para obtener más información sobre `git-receive-pack`, consulta "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" en la documentación de Git. Para obtener más información sobre `refs`, consulta "[Referencias de Git](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" en *Pro Git*. - -#### Salida (stdout) - -La salida del script (`stdout`) se vuelve a pasar al cliente, de manera que los enunciados `eco` estén visibles para el usuario en la línea de comando o en la interfaz del usuario. - -#### Estado de salida - -El `estado de salida` de un script de pre-recepción determina si la subida se aceptará. - -| Valor del estado de salida | Acción | -|:--------------------------:|:-------------------------:| -| 0 | La subida será aceptada. | -| no cero | La subida será rechazada. | - -#### Variables del entorno -Fuera de los valores que se brindan a `stdin`, existen variables adicionales que están disponibles para un script de gancho de pre-recepción en {% data variables.product.prodname_ghe_server %}. - -| Variable | Descripción | -|:------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| $GITHUB_USER_LOGIN | El id de usuario que creó el `ref`. | -| $GIT_DIR | La ruta del repositorio remoto en el aparato. | -| $GITHUB_USER_IP | La dirección IP del usuario que realiza la subida. | -| $GITHUB_REPO_NAME | El nombre en el formato `owner`/`repo` del repositorio que se actualiza. | -| $GITHUB_PULL_REQUEST_AUTHOR_LOGIN | El ID de usuario para el autor de una solicitud de extracción en tu instancia. | -| $GITHUB_REPO_PUBLIC | Un valor booleano que cuando `true` representa un repositorio público, y cuando `false` representa un repositorio privado. | -| $GITHUB_PUBLIC_KEY_FINGERPRINT | La huella digital de clave pública del usuario. | -| $GITHUB_PULL_REQUEST_HEAD | Una cadena en el formato: `user:branch` para el HEAD del PR.
    Ejemplo: `octocat:fix-bug` | -| $GITHUB_PULL_REQUEST_BASE | Una secuencia en el formato: `user:branch` para la BASE de la Solicitud de Extracción.
    Ejemplo: `octocat:main` | -| $GITHUB_VIA | Método usado para crear la ref.
    **Valores posibles:**
    - `auto-merge deployment api`
    - `blob edit`
    - `branch merge api`
    - `branches page delete button`
    - `git refs create api`
    - `git refs delete api`
    - `git refs update api`
    - `merge api`
    - `pull request branch delete button`
    - `pull request branch undo button`
    - `pull request merge api`
    - `pull request merge button`
    - `pull request revert button`
    - `releases delete button`
    - `stafftools branch restore`
    - `slumlord (#{sha})` | -| $GIT_PUSH_OPTION_COUNT | El número de opciones de extracción que envió el cliente. Para obtener más información sobre las opciones de subida, consulta "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" en la documentación de Git. | -| $GIT_PUSH_OPTION_N | Donde N es un número entero que comienza con 0, esta variable contiene la cadena de opción de subida que envió el cliente. La primera opción que se envió se almacenó en GIT_PUSH_OPTION_0, la segunda opción que se envió se almacenó en GIT_PUSH_OPTION_1, y así sucesivamente. Para obtener más información sobre las opciones de subida, consulta "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" en la documentación de Git. |{% if currentVersion ver_gt "enterprise-server@2.21" %} -| $GIT_USER_AGENT | The user-agent string sent by the client that pushed the changes. |{% endif %} - -### Establecer permisos y subidas a un ganchos de pre-recepción para {% data variables.product.prodname_ghe_server %} - -Un script de gancho de pre-recepción se encuentra en un repositorio en el aparato {% data variables.product.prodname_ghe_server %}. Un administrador del sitio debe tener en cuenta los permisos del repositorio y garantizar que solo los usuarios correspondientes tengan acceso. - -Recomendamos los ganchos de consolidación a un solo repositorio. Si el repositorio de gancho consolidado es público, `README.md` puede usarse para explicar los cumplimientos de la política. Además, las contribuciones pueden aceptarse mediante solicitudes de extracción. Sin embargo, los ganchos de pre-recepción solo pueden agregarse desde la rama por defecto. Para un flujo de trabajo de prueba, se deben usar las bifurcaciones del repositorio con la configuración. - -1. Para usuarios de Mac, asegúrate de que los scripts tengan permisos de ejecución: - - ```shell - $ sudo chmod +x SCRIPT_FILE.sh - ``` - Para usuarios de Windows, asegúrate de que los scripts tengan permisos de ejecución: - - ```shell - git update-index --chmod=+x SCRIPT_FILE.sh - ``` - -2. Confirmar y subir a tus repositorio de ganchos pre-recibidos en la instancia {% data variables.product.prodname_ghe_server %}. - - ```shell - $ git commit -m "YOUR COMMIT MESSAGE" - $ git push - ``` - -3. [Crear la instancia de ganchos de pre-recepción](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) on the {% data variables.product.prodname_ghe_server %}. - -### Probar scripts de pre-recepción localmente -Puedes probar un script de gancho de pre-recepción localmente antes de crear o actualizar en tu aparato {% data variables.product.prodname_ghe_server %}. Un método es crear un entorno de Docker local para que actúe como un repositorio remoto que pueda ejecutar el gancho de pre-recepción. - -{% data reusables.linux.ensure-docker %} - -2. Crear un archivo denominado `Dockerfile.dev` que contenga: - - ``` - FROM gliderlabs/alpine:3.3 - RUN \ - apk add --no-cache git openssh bash && \ - ssh-keygen -A && \ - sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ - adduser git -D -G root -h /home/git -s /bin/bash && \ - passwd -d git && \ - su git -c "mkdir /home/git/.ssh && \ - ssh-keygen -t rsa -b 4096 -f /home/git/.ssh/id_rsa -P '' && \ - mv /home/git/.ssh/id_rsa.pub /home/git/.ssh/authorized_keys && \ - mkdir /home/git/test.git && \ - git --bare init /home/git/test.git" - - VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] - WORKDIR /home/git - - CMD ["/usr/sbin/sshd", "-D"] - ``` - -3. Crear un script de pre-recepción de prueba denominado `always_reject.sh`. Este script del ejemplo rechazará todas las subidas, lo cual es útil para bloquear un repositorio: - - ``` - #!/usr/bin/env bash - - echo "error: rejecting all pushes" - exit 1 - ``` - -4. Asegúrate de que los scripts `always_reject.sh` tengan permisos de ejecución: - - ```shell - $ chmod +x always_reject.sh - ``` - -5. Desde el directorio que contiene `Dockerfile.dev`, crea una imagen: - - ```shell - $ docker build -f Dockerfile.dev -t pre-receive.dev . - > Sending build context to Docker daemon 3.584 kB - > Step 1 : FROM gliderlabs/alpine:3.3 - > ---> 8944964f99f4 - > Step 2 : RUN apk add --no-cache git openssh bash && ssh-keygen -A && sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && adduser git -D -G root -h /home/git -s /bin/bash && passwd -d git && su git -c "mkdir /home/git/.ssh && ssh-keygen -t rsa -b 4096 -f /home/git/.ssh/id_rsa -P ' && mv /home/git/.ssh/id_rsa.pub /home/git/.ssh/authorized_keys && mkdir /home/git/test.git && git --bare init /home/git/test.git" - > ---> Running in e9d79ab3b92c - > fetch http://alpine.gliderlabs.com/alpine/v3.3/main/x86_64/APKINDEX.tar.gz - > fetch http://alpine.gliderlabs.com/alpine/v3.3/community/x86_64/APKINDEX.tar.gz - ....truncated output.... - > OK: 34 MiB in 26 packages - > ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 - > Password for git changed by root - > Generating public/private rsa key pair. - > Your identification has been saved in /home/git/.ssh/id_rsa. - > Your public key has been saved in /home/git/.ssh/id_rsa.pub. - ....truncated output.... - > Initialized empty Git repository in /home/git/test.git/ - > Successfully built dd8610c24f82 - ``` - -6. Ejecutar un contenedor de datos que contiene una clave SSH generada: - - ```shell - $ docker run --name data pre-receive.dev /bin/true - ``` - -7. Copiar el ganchos de pre-recepción de prueba `always_reject.sh` en el contenedor de datos: - - ```shell - $ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive - ``` - -8. Poner en marcha un contenedor de la aplicación que corre `sshd` y ejecuta el gancho. Toma nota del id del contenedor que se devolvió: - - ```shell - $ docker run -d -p 52311:22 --volumes-from data pre-receive.dev - > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58 - ``` - -9. Copilar la clave SSH generada desde el contenedor de datos hasta la máquina local: - - ```shell - $ docker cp data:/home/git/.ssh/id_rsa . - ``` - -10. Modificar el remoto de un repositorio de prueba y subirlo al repositorio `test.git` dentro del contenedor Docker. Este ejemplo usa `git@github.com:octocat/Hello-World.git` pero puedes usar cualquier repositorio que desees. Este ejemplo asume que tu máquina local (127.0.01) es el puerto vinculante 52311, pero puedes usar una dirección IP diferente si el docker está ejecutándose en una máquina remota. - - ```shell - $ git clone git@github.com:octocat/Hello-World.git - $ cd Hello-World - $ git remote add test git@127.0.0.1:test.git - $ GIT_SSH_COMMAND="ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 52311 -i ../id_rsa" git push -u test master - > Warning: Permanently added '[192.168.99.100]:52311' (ECDSA) to the list of known hosts. - > Counting objects: 7, done. - > Delta compression using up to 4 threads. - > Compressing objects: 100% (3/3), done. - > Writing objects: 100% (7/7), 700 bytes | 0 bytes/s, done. - > Total 7 (delta 0), reused 7 (delta 0) - > remote: error: rejecting all pushes - > To git@192.168.99.100:test.git - > ! [remote rejected] master -> master (pre-receive hook declined) - > error: failed to push some refs to 'git@192.168.99.100:test.git' - ``` - - Observa que la subida fue rechazada después de ejecutar el ganchos de pre-recepción y de hace eco la salida del script. - -### Leer más - - "[Personalizar Git - Un ejemplo de la política activa de Git](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" desde el *sitio web de Pro Git* diff --git a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/index.md b/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/index.md deleted file mode 100644 index c33b96e1be..0000000000 --- a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Requerir políticas para los ganchos de pre-recepción -intro: Usar ganchos de pre-recepción para implementar estándares de flujo de trabajo dentro de tu organización. Los ganchos de pre-recepción requieren un código para aprobar un conjunto de verificaciones de calidad predefinido antes de que la extracción sea aceptada en el repositorio. -redirect_from: - - /enterprise/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy - - /enterprise/admin/policies/enforcing-policy-with-pre-receive-hooks -versions: - ghes: '*' -topics: - - Enterprise -children: - - /about-pre-receive-hooks - - /creating-a-pre-receive-hook-environment - - /creating-a-pre-receive-hook-script - - /managing-pre-receive-hooks-on-the-github-enterprise-server-appliance ---- - diff --git a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md deleted file mode 100644 index e50c602e2c..0000000000 --- a/translations/es-XL/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Administrar ganchos de pre-recepción en el aparato del Servidor de GitHub Enterprise -intro: 'Configura cómo las personas usarán sus ganchos de pre-recepción dentro de su aparato del {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance - - /enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-appliance/ - - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance - - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance -versions: - ghes: '*' -topics: - - Enterprise - - Policies - - Pre-receive hooks ---- -### Crear ganchos de pre-recepción - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -4. Haz clic en **Add pre-receive hook** (Agregar gancho de pre-recepción). ![Agregar un gancho de pre-recepción](/assets/images/enterprise/site-admin-settings/add-pre-receive-hook.png) -5. En el campo **Hook name** (Nombre de gancho), escribe el nombre del gancho que deseas crear. ![Nombrar los ganchos de pre-recepción](/assets/images/enterprise/site-admin-settings/hook-name.png) -6. En el menú desplegable **Environment** (Entorno), selecciona el entorno en el que deseas ejecutar el gancho. ![Entornos para ganchos](/assets/images/enterprise/site-admin-settings/environment.png) -7. Debajo de **Script**, desde el menú desplegable **Select hook repository** (Seleccionar repositorio de gancho), selecciona el repositorio que contiene tu script de gancho de pre-recepción. Desde el menú desplegable **Select file** (Seleccionar archivo), selecciona el nombre de archivo o el script del gancho de pre-recepción. ![Script para ganchos](/assets/images/enterprise/site-admin-settings/hook-script.png) -8. Selecciona **Use the exit-status to accept or reject pushes** (Usar el estado de salida para aceptar o rechazar subidas) para imponer tu script. Al quitar la marca de selección de esta opción podrás probar el script mientras se ignora el valor del estado de salida. En este modo, el resultado del script estará visible para el usuario en la línea de comando, pero no en la interfaz web. ![Usar el estado de salida](/assets/images/enterprise/site-admin-settings/use-exit-status.png) -9. Selecciona **Enable this pre-receive hook on all repositories by default ** (Habilitar este gancho de pre-recepción en todos los repositorios por defecto) si quieres que el gancho de pre-recepción se ejecute en todos los repositorios. ![Habilitar gachos para todos los repositorios](/assets/images/enterprise/site-admin-settings/enable-hook-all-repos.png) -10. Selecciona **Administrators can enable and disable this hook** (Los administradores pueden habilitar e inhabilitar este gancho) para permitir que los miembros de la organización con permisos de administración o propietario seleccionen si desean habilitar o inhabilitar este gancho de pre-recepción. ![Los administradores habilitan o inhabilitan los ganchos](/assets/images/enterprise/site-admin-settings/admins-enable-hook.png) - -### Editar ganchos de pre-recepción - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -1. Junto al gancho de pre-recepción que deseas editar, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. ![Editar pre-recepción](/assets/images/enterprise/site-admin-settings/edit-pre-receive-hook.png) - -### Eliminar ganchos de pre-recepción - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -2. Junto al gancho de pre-recepción que deseas eliminar, haz clic en {% octicon "x" aria-label="X symbol" %}. ![Editar pre-recepción](/assets/images/enterprise/site-admin-settings/delete-pre-receive-hook.png) - -### Configura ganchos de pre-recepción para una organización - -Un administrador de la organización solo puede configurar permisos de gancho para una organización si el administrador del sitio seleccionó la opción **Administrators can enable o disable this hook** (Los administradores pueden habilitar o inhabilitar este gancho) al crear el gancho de pre-recepción. Para configurar ganchos de pre-recepción para un repositorio, debes ser administrador o propietario de una organización. - -{% data reusables.profile.enterprise_access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -4. En la barra lateral izquierda, haz clic en **Hooks** (Ganchos). ![Barra lateral de ganchos](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png) -5. Junto al gancho de pre-recepción que deseas configurar, haz clic en el menú desplegable **Hook permissions** (Permisos del gancho). Selecciona si deseas habilitar o inhabilitar el gancho de pre-recepción o permite que lo configuren los administradores del repositorio. ![Permisos para ganchos](/assets/images/enterprise/orgs-and-teams/hook-permissions.png) - -### Configura ganchos de pre-recepción para un repositorio - -Un propietario de repositorio solo puede configurar un gancho si el administrador del sitio seleccionó la opción **Administrators can enable or disable this hook** (Los administradores pueden habilitar o inhabilitar este gancho) al crear el gancho de pre-recepción. En una organización, el propietario de la organización también debe haber seleccionado el permiso de gancho **Configurable**. Para configurar ganchos de pre-recepción para un repositorio, debes ser propietario del repositorio. - -{% data reusables.profile.enterprise_access_profile %} -2. Haz clic en **Repositories** (Repositorios) y selecciona el repositorio para el que deseas configurar los ganchos de pre-recepción. ![Repositorios](/assets/images/enterprise/repos/repositories.png) -{% data reusables.repositories.sidebar-settings %} -4. En la barra lateral izquierda, haz clic en **Hooks & Services** (Ganchos y Servicios). ![Ganchos y servicios](/assets/images/enterprise/repos/hooks-services.png) -5. Junto al gancho de pre-recepción que deseas configurar, haz clic en el menú desplegable **Hook permissions** (Permisos del gancho). Selecciona si deseas habilitar o inhabilitar el gancho de pre-recepción. ![Permisos para ganchos de repositorios](/assets/images/enterprise/repos/repo-hook-permissions.png) diff --git a/translations/es-XL/content/admin/policies/index.md b/translations/es-XL/content/admin/policies/index.md deleted file mode 100644 index 11f9b63a90..0000000000 --- a/translations/es-XL/content/admin/policies/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Configurar las políticas para tu empresa -intro: 'Puedes configurar políticas en {% data variables.product.prodname_enterprise %} para reducir el riesgo e incrementar la calidad.' -redirect_from: - - /enterprise/admin/developer-workflow - - /enterprise/admin/policies -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /enforcing-policies-for-your-enterprise - - /enforcing-policy-with-pre-receive-hooks ---- -### Índice diff --git a/translations/es-XL/content/admin/user-management/index.md b/translations/es-XL/content/admin/user-management/index.md deleted file mode 100644 index 0ec944843f..0000000000 --- a/translations/es-XL/content/admin/user-management/index.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: 'Administrar usuarios, organizaciones y repositorios' -shortTitle: 'Administrar usuarios, organizaciones y repositorios' -redirect_from: - - /enterprise/admin/categories/user-management/ - - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration - - /enterprise/admin/migrations - - /enterprise/admin/clustering - - /enterprise/admin/user-management -intro: 'En esta guía, se describen los métodos de autenticación para los usuarios que inician sesión en la instancia {% data variables.product.prodname_enterprise %}, cómo crear organizaciones y equipos para el acceso a repositorios y la colaboración, así como recomendaciones sobre las buenas prácticas para la seguridad del usuario.' -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /managing-users-in-your-enterprise - - /managing-organizations-in-your-enterprise - - /managing-repositories-in-your-enterprise - - /monitoring-activity-in-your-enterprise - - /migrating-data-to-and-from-your-enterprise ---- -### Índice diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md deleted file mode 100644 index d3a83accdb..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Agregar personas a los equipos -redirect_from: - - /enterprise/admin/articles/adding-teams/ - - /enterprise/admin/articles/adding-or-inviting-people-to-teams/ - - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams/ - - /enterprise/admin/user-management/adding-people-to-teams - - /admin/user-management/adding-people-to-teams -intro: 'Una vez que se ha creado un equipo, los administradores de la organización pueden agregar usuarios desde {% data variables.product.product_location_enterprise %} al equipo y determinar a qué repositorios tienen acceso.' -versions: - ghes: '*' -topics: - - Access management - - Enterprise - - Teams - - User account ---- -Cada equipo tiene sus propios premisos de acceso definidos de manera individual [ para repositorios que le pertenecen a tu organización](/articles/permission-levels-for-an-organization). - -- Los miembros con el rol de propietario pueden agregar o eliminar miembros existentes de la organización de todos los equipos. -- Los miembros de equipos que dan permisos de administración solo pueden modificar los repositorios y las membresías de equipos para ese equipo. - -### Configurar un equipo - -{% data reusables.profile.enterprise_access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.invite_to_team %} -{% data reusables.organizations.review-team-repository-access %} - -### Asignar equipos a los grupos LDAP (para instancias que usan la sincronización LDAP para la autenticación de usuario) - -{% data reusables.enterprise_management_console.badge_indicator %} - -Para agregar un nuevo miembro a un equipo sincronizado con un grupo LDAP, agrega el usuario como un miembro del grupo LDAP o comunícate con el administrador LDAP. diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md deleted file mode 100644 index ff14270fc7..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Configurar visibilidad para los miembros de la organización -intro: Puedes establecer la visibilidad para nuevos miembros de la organización en toda tu instancia como pública o privada. También puedes hacer que los miembros no puedan modificar su visibilidad de la establecida por defecto. -redirect_from: - - /enterprise/admin/user-management/configuring-visibility-for-organization-membership - - /admin/user-management/configuring-visibility-for-organization-membership -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Organizations - - User account ---- -También puedes implementar tu configuración por defecto en todos los miembros actuales de la organización en tu instancia usando una utilidad de línea de comandos. Por ejemplo, si quieres solicitar que la visibilidad de cada miembro de la organización sea pública, puedes establecer la configuración predeterminada como pública e implementar la predeterminada para todos los nuevos miembros en los parámetros de administración, y luego usar la utilidad de línea de comandos para implementar la configuración pública en los miembros existentes. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -3. En "Visibilidad predeterminada de los miembros de la organización", usa el menú desplegable y haz clic en **Private (Privada)** o **Public (Pública)**. ![Menú desplegable con opción para configurar la visibilidad predeterminada de los miembros de la organización como pública o privada](/assets/images/enterprise/site-admin-settings/default-organization-membership-visibility-drop-down-menu.png) -4. Opcionalmente, para evitar que los miembros modifiquen la visibilidad de su membresía respecto de la predeterminada, selecciona **Implementar en los miembros de la organización**. ![Casilla de verificación para implementar la configuración predeterminada en todos los miembros](/assets/images/enterprise/site-admin-settings/enforce-default-org-membership-visibility-setting.png) -5. Si quieres implementar tu nueva configuración de visibilidad en todos los miembros existentes, usa la utilidad de línea de comandos `ghe-org-membership-update`. Para obtener más información, consulta "[Utilidades de línea de comandos](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-membership-update)." diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md deleted file mode 100644 index 370840397b..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Integración continua mediante Jenkins -intro: 'Puedes activar automáticamente la creación de trabajos en un servidor Jenkins cuando las extracciones se realizan a un repositorio en {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/developer-workflow/continuous-integration-using-jenkins - - /enterprise/admin/user-management/continuous-integration-using-jenkins - - /admin/user-management/continuous-integration-using-jenkins -versions: - ghes: '*' -topics: - - CI - - Enterprise ---- -### Requisitos - -- Sigue nuestra documentación técnica "[Guía práctica para CI con Jenkins y GitHub](https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/)" para conocer las instrucciones detalladas sobre cómo puedes activar automáticamente la creación de trabajos en un servidor Jenkins cuando las extracciones de realizan en un repositorio en {% data variables.product.product_location_enterprise %}. diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/creating-organizations.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/creating-organizations.md deleted file mode 100644 index 5e7d9c00fb..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/creating-organizations.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Crear organizaciones -redirect_from: - - /enterprise/admin/articles/creating-organizations/ - - /enterprise/admin/user-management/creating-organizations - - /admin/user-management/creating-organizations -intro: Puedes elegir establecer una nueva organización o convertir una cuenta personal existente en una organización. -versions: - enterprise-server: '*' ---- -Una organización es un conjunto de cuentas de usuario que posee repositorios. Las organizaciones tienen uno o más propietarios, que tienen privilegios administrativos para la organización. Las organizaciones también se pueden usar para un espacio de nombres —por ejemplo, `http(s)://[hostname]/[organization name]/` te lleva al perfil de una organización en el {% data variables.product.prodname_ghe_server %}, mientras que `http(s)://[hostname]/[organization name]/[repository name]/` te lleva al perfil de un repositorio. - -Cuando creas una organización, esta no tiene repositorios asociados a ella. En cualquier momento, [los miembros de la organización con el rol de Propietario pueden agregar nuevos repositorios](/enterprise/{{ currentVersion }}/user/articles/permission-levels-for-an-organization) o transferir repositorios existentes. Para obtener más información, consulta "[Transferir un repositorio](/enterprise/{{ currentVersion }}/user/articles/transferring-a-repository)". - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.organizations %} -3. En la sección "Organizaciones", haz clic en **New organization** (Nueva organización). ![Botón de la nueva organización](/assets/images/help/settings/new-org-button.png) -4. En "Nombre de la organización", asígnale un nombre a la organización. ![Nombre de la nueva organización](/assets/images/help/organizations/new-org-name.png) -5. En "Correo electrónico de contacto", escribe la dirección de correo electrónico de una persona que pueda ser contactada para obtener más información acerca de la organización. -6. Haz clic en **Create organization** (Crear organización). diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md deleted file mode 100644 index 923c2c20b0..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Crear equipos -intro: 'Los equipos les permiten a las organizaciones crear grupos de miembros y controlar el acceso a los repositorios. A los miembros del equipo se les pueden otorgar permisos de lectura, escritura o administración para repositorios específicos.' -redirect_from: - - /enterprise/admin/user-management/creating-teams - - /admin/user-management/creating-teams -versions: - ghes: '*' -topics: - - Access management - - Enterprise - - Teams - - User account ---- -Los equipos son centrales para muchas de las características colaborativas de {% data variables.product.prodname_dotcom %}, como las @menciones del equipo para notificar a las partes correspondientes que les quieres solicitar su colaboración o atención. Para obtener más información, consulta "[Niveles de permisos para el repositorio de una organizazión](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)". - -Un equipo puede representar a un grupo dentro de tu empresa o incluir personas con ciertos intereses o experiencia. Por ejemplo, un equipo de expertos en accesibilidad en {% data variables.product.product_location_enterprise %} podría estar compuesto por personas de diferentes departamentos. Los equipos pueden representar inquietudes de carácter funcional que complementan la jerarquía divisional existente de una empresa. - -Las organizaciones pueden crear varios niveles de equipos anidados para reflejar la estructura de jerarquía de una empresa o grupo. Para obtener más información, consulta "[Acerca de los equipos](/enterprise/{{ currentVersion }}/user/articles/about-teams/#nested-teams)". - -### Crear un equipo - -Una combinación prudente de equipos es una manera eficaz de controlar el acceso a los repositorios. Por ejemplo, si tu organización solo permite que tu equipo de ingeniería en lanzamientos suba código a la rama predeterminada de cualquier repositorio, puedes otorgar únicamente a este equipo el permiso de **administrador** para los repositorios de tu organización y darle al resto de los equipos permisos de **lectura**. - -{% data reusables.profile.enterprise_access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.new_team %} -{% data reusables.organizations.team_name %} -{% data reusables.organizations.team_description %} -{% data reusables.organizations.team_visibility %} -{% data reusables.organizations.create-team-choose-parent %} -{% data reusables.organizations.create_team %} - -### Crear equipos con la sincronización LDAP activada - -Las instancias que usan LDAP para la autenticación de usuarios pueden usar la sincronización LDAP para administrar los miembros de un equipo. Al poner el **Nombre Distintivo** (DN) del grupo en el campo **LDAP group** (Grupo LDAP), se le asignará un equipo a un grupo LDAP en tu servidor LDAP. Si usas la sincronización LDAP para administrar los miembros de un equipo, no podrás administrar tu equipo dentro de {% data variables.product.product_location_enterprise %}. Cuando la sincronización LDAP está activada, el equipo asignado sincroniza sus miembros en segundo plano de manera periódica con el intervalo configurado. Para obtener más información, consulta "[Activar sincronización LDAP](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)". - -{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} - -{% warning %} - -**Notas:** -- La sincronización LDAP solo administra la lista de miembros del equipo. Debes administrar los permisos y repositorios del equipo desde dentro del {% data variables.product.prodname_ghe_server %}. -- Si se elimina un grupo LDAP asignado a un DN, o si se borra un grupo LDAP, todos los miembros se eliminan del equipo sincronizado del {% data variables.product.prodname_ghe_server %}. Para solucionar esto, asigna el equipo a un nuevo DN, vuelve a agregar a los miembros del equipo y [sincroniza de forma manual la asignación](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap/#manually-syncing-ldap-accounts). -- Si se elimina a una persona de un repositorio cuando la sincronización LDAP está activada, perderá el acceso, pero sus bifurcaciones no se borrarán. Si se agrega a esa persona a un equipo con acceso al repositorio original de la organización dentro de los tres meses posteriores, en la siguiente sincronización, se reestablecerá automáticamente su acceso a las bifurcaciones. - -{% endwarning %} - -1. Asegúrate de que [La sincronización LDAP esté activada](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap#enabling-ldap-sync). -{% data reusables.profile.enterprise_access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.new_team %} -{% data reusables.organizations.team_name %} -6. Busca el DN de un grupo LDAP al que asignar el equipo. Si no conoces el DN, escribe el nombre del grupo LDAP. El {% data variables.product.prodname_ghe_server %} buscará y completará automáticamente cualquier coincidencia. ![Asignar al DN del grupo LDAP](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) -{% data reusables.organizations.team_description %} -{% data reusables.organizations.team_visibility %} -{% data reusables.organizations.create-team-choose-parent %} -{% data reusables.organizations.create_team %} diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/index.md deleted file mode 100644 index c5e42dcf11..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Administrar las organizaciones en tu empresa -redirect_from: - - /enterprise/admin/articles/adding-users-and-teams/ - - /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. Los repositorios públicos que pertenecen a una organización son accesibles para los usuarios de otras organizaciones, mientras que los repositorios privados son inaccesibles para cualquiera, salvo para los miembros de la organización.' -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /configuring-visibility-for-organization-membership - - /preventing-users-from-creating-organizations - - /requiring-two-factor-authentication-for-an-organization - - /creating-teams - - /adding-people-to-teams - - /removing-users-from-teams-and-organizations - - /managing-projects-using-jira - - /continuous-integration-using-jenkins ---- - diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md deleted file mode 100644 index 4c54dabd2a..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Administrar proyectos mediante JIRA -intro: 'Puedes integrar JIRA con {% data variables.product.prodname_enterprise %} para la administración de proyectos.' -redirect_from: - - /enterprise/admin/guides/installation/project-management-using-jira/ - - /enterprise/admin/articles/project-management-using-jira/ - - /enterprise/admin/developer-workflow/managing-projects-using-jira - - /enterprise/admin/developer-workflow/customizing-your-instance-with-integrations - - /enterprise/admin/user-management/managing-projects-using-jira - - /admin/user-management/managing-projects-using-jira -versions: - ghes: '*' -topics: - - Enterprise - - Project management ---- -### Conectar JIRA a una organización {% data variables.product.prodname_enterprise %} - -1. Inicia sesión en tu cuenta de {% data variables.product.prodname_enterprise %} en http[s]://[hostname]/login. -1. En el ángulo superior derecho de cualquier página, haz clic en el icono de ajustes (engranaje) de la cuenta. -1. En la barra lateral izquierda, haz clic en el nombre de tu organización. -1. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones). -1. En el ángulo superior derecho del cuadro **Organization applications** (Aplicaciones de la organización), haz clic en **Register new application** (Registrar aplicación nueva). -1. Completa los parámetros de la aplicación: - - En el campo **Application name** (Nombre de la aplicación), escribe "JIRA". - - En el campo **Homepage URL** (URL de inicio de sesión), escribe la URL completa de tu instancia JIRA. - - En el campo **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa de tu instancia JIRA. -1. Haz clic en **Register application** (Registrar aplicación). -1. En la parte inferior de la página, observa el **Client ID** (ID de cliente) y **Client Secret** (Secreto de cliente). Necesitarás estos datos para configurar tu instancia JIRA. - -### Configuración de instancia de JIRA - -1. En tu instancia de JIRA, inicia sesión en una cuenta con acceso administrativo. -1. En la parte superior de la página, haz clic en el icono de ajustes (engranaje). -1. En el desplegable de los parámetros, elige **Add-ons** (Adicionales). -1. En la barra lateral izquierda, debajo de **Source control** (Control de origen), haz clic en **DVCS accounts** (Cuentas de DVCS). -1. Haz clic en **Link Bitbucket or GitHub account** (Enlazar cuenta de Bitbucket o GitHub). -1. En el modal **Add New Account** (Agregar nueva cuenta), completa tus parámetros de {% data variables.product.prodname_enterprise %}: - - En el menú desplegable **Host**, elige **GitHub Enterprise**. - - En el campo **Team or User Account** (Cuenta de equipo o usuario), escribe el nombre de tu organización {% data variables.product.prodname_enterprise %} o cuenta personal. - - En el campo **OAuth Key** (Clave OAuth), escribe el ID de cliente de tu aplicación de programador de {% data variables.product.prodname_enterprise %}. - - En el campo **OAuth Secret** (OAuth secreto), escribe el secreto de cliente para tu aplicación de programador de {% data variables.product.prodname_enterprise %}. - - Si no quieres vincular los repositorios nuevos que pertenecen a tu organización o cuenta personal de {% data variables.product.prodname_enterprise %}, quita la marca de selección de **Auto Link New Repositories** (Vincular automáticamente repositorios nuevos). - - Si no quieres habilitar las confirmaciones inteligentes, quita la marca de selección **Enable Smart Commits** (Habilitar confirmaciones inteligentes). - - Da clic en **Agregar**. -1. Revisa los permisos que concedes a tu cuenta de {% data variables.product.prodname_enterprise %} y haz clic en **Authorize application** (Autorizar aplicación). -1. Si es necesario, escribe tu contraseña para continuar. diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md deleted file mode 100644 index 1595bd4b91..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Impedir que los usuarios creen organizaciones -redirect_from: - - /enterprise/admin/articles/preventing-users-from-creating-organizations/ - - /enterprise/admin/hidden/preventing-users-from-creating-organizations/ - - /enterprise/admin/user-management/preventing-users-from-creating-organizations - - /admin/user-management/preventing-users-from-creating-organizations -intro: 'Puedes hacer que los miembros no puedan crear organizaciones en tu aparato {% data variables.product.prodname_ghe_server %}.' -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Organizations - - Policies ---- -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -4. En "Los usuarios pueden crear organizaciones", usa el menú desplegable y haz clic en **Activado** o **Desactivado**. ![Desplegable Los usuarios pueden crear organizaciones](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png) diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md deleted file mode 100644 index ed20151b0a..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Eliminar usuarios de equipos y organizaciones -intro: 'Si un miembro de tu organización ya no necesita acceso a ciertos repositorios, puedes eliminarlo del equipo que permite ese acceso. Si un miembro de tu organización ya no necesita acceso a ningún repositorio que le pertenezca a tu organización, puedes eliminarlo de la organización.' -redirect_from: - - /enterprise/admin/user-management/removing-users-from-teams-and-organizations - - /admin/user-management/removing-users-from-teams-and-organizations -versions: - ghes: '*' -topics: - - Access management - - Accounts - - Enterprise - - Teams ---- -Solo los propietarios o los administradores del equipo pueden eliminar miembros de la organización. Cuando se elimina un usuario de un equipo o una organización, sus propuestas, solicitudes de extracción y comentarios en los repositorios de la organización permanecen intactos y siguen siendo atribuidos al usuario. - -{% warning %} - -**Advertencia**: cuando eliminas un usuario de una organización, perderán el acceso a cualquier bifurcación privada que tengan en los **repositorios privados** de tu organización. Puede seguir teniendo copias locales de esas bifurcaciones. Sin embargo, no podrá sincronizarlas con los repositorios de tu organización. Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. Si el usuario eliminado de tu organización era un miembro de la organización, su acceso a las bifurcaciones privadas de los repositorios de la organización se pueden restablecer si el usuario es [reinstalado como un miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses de haber sido eliminado de una organización. - -{% endwarning %} - -### Eliminar un miembro del equipo - -{% warning %} - -**Nota:** {% data reusables.enterprise_management_console.badge_indicator %} - -Para eliminar un miembro existente de un equipo sincronizado a un grupo LDAP, comunícate con tu administrador LDAP. - -{% endwarning %} - -{% data reusables.profile.enterprise_access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -4. Selecciona la persona o las personas que quieres eliminar. ![Casilla junto al miembro de la organización](/assets/images/help/teams/team-member-check-box.png) -5. Arriba de la lista de miembros del equipo, utiliza el menú desplegable y haz clic en **Eliminar del equipo**. ![Menú desplegable con opción para cambiar el rol](/assets/images/help/teams/bulk-edit-drop-down.png) - -### Eliminar un usuario de una organización - -{% data reusables.profile.enterprise_access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Al lado del nombre de los usuarios que quieras eliminar de la organización, haz clic en la casilla de verificación. ![Casilla de verificación Eliminar usuario](/assets/images/help/organizations/Organization-remove-user.png) -5. En la parte superior de la página, debajo del nombre de la organización, haz clic en **Eliminar de la organización**. ![Botón para eliminar de la organización ](/assets/images/help/organizations/Organization-remove-from-organization-button.png) - -{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} diff --git a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md b/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md deleted file mode 100644 index 980dab24e2..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Solicitar autenticación de dos factores para una organización -intro: 'Le puedes solicitar a los miembros de la organización y a los colaboradores externos que activen la autenticación de dos factores para sus cuentas personales en una organización, para que sea más difícil para los actores maliciosos acceder a los parámetros y los repositorios de una organización.' -redirect_from: - - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization - - /admin/user-management/requiring-two-factor-authentication-for-an-organization -versions: - ghes: '*' -topics: - - 2FA - - Enterprise - - Organizations - - Policies - - Security ---- -Al usar la autenticación integrada o LDAP, el aparato {% data variables.product.prodname_ghe_server %} admite la autenticación de dos factores. Los administradores de la organización le pueden solicitar a los miembros que tengan la autenticación de dos factores activada. - -{% data reusables.enterprise_user_management.external_auth_disables_2fa %} - -Para obtener más información, consulta [este cuadro sobre métodos de autenticación que admiten 2FA](/enterprise/{{ currentVersion }}/user/articles/about-two-factor-authentication/#authentication-methods-that-support-2fa). - -### Requisitos para aplicar la autenticación de dos factores - -Antes de poder solicitarle a los miembros de la organización y a los colaboradores externos que usen 2FA, debes [activar la autenticación de dos factores](/enterprise/{{ currentVersion }}/user/articles/securing-your-account-with-two-factor-authentication-2fa/) para tu cuenta personal propia. - -{% warning %} - -**Advertencias:** - -- Cuando solicitas la autenticación de dos factores, los miembros y los colaboradores externos (incluidas cuentas bot) que no usan la 2FA serán eliminados de la organización y perderán acceso a sus repositorios, incluidas sus bifurcaciones de los repositorios privados. Si activan la 2FA para su cuenta personal dentro de los tres meses de haber sido eliminados de la organización, puedes [reinstalar sus parámetros y sus privilegios de acceso](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization). -- Cuando se solicita la 2FA, los miembros de la organización o los colaboradores externos que desactiven la 2FA se eliminarán automáticamente de la organización. -- Si eres el único propietario de una organización que requiere autenticación de dos factores, no podrás inhabilitar la 2FA de tu cuenta personal sin inhabilitar la autenticación de dos factores para la organización. - -{% endwarning %} - -Antes de solicitar el uso de la autenticación de dos factores, te recomendamos notificar a los miembros de la organización y a los colaboradores externos y pedirles que configuren la 2FA para sus cuentas. Puedes [ ver si los miembros y los colaboradores externos ya usan 2FA](/enterprise/{{ currentVersion }}/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) en la pestaña Personas de una organización. - -{% data reusables.profile.enterprise_access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.organizations.require_two_factor_authentication %} -{% data reusables.organizations.removed_outside_collaborators %} - -### Ver las personas que se eliminaron de tu organización - -Para ver las personas que fueron automáticamente eliminadas de tu organización por no cumplir cuando solicitaste la autenticación de dos factores, puedes [buscar el registro de auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log/) usando el campo de búsqueda `reason:two_factor_requirement_non_compliance`. - -{% data reusables.audit_log.octicon_icon %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.audit_log.audit_log_sidebar_for_site_admins %} -4. Ingresa tu consulta de búsqueda usando `reason:two_factor_requirement_non_compliance`. ![Evento de registro de auditoría de herramientas de plantilla que muestra un usuario eliminado por no cumplir con la 2FA](/assets/images/help/2fa/2fa_noncompliance_stafftools_audit_log_search.png) Para limitar tu búsqueda para: - - Miembros de organizaciones eliminados, ingresa `action:org.remove_member AND reason:two_factor_requirement_non_compliance` - - Colaboradores externos eliminados, ingresa `action:org.remove_outside_collaborator AND reason:two_factor_requirement_non_compliance` - - También puedes ver las personas eliminadas de una organización en particular usando el nombre de la organización en tu búsqueda: - - `org:octo-org AND reason:two_factor_requirement_non_compliance` -5. Click **Search**. - -### Ayudar a que los miembros y colaboradores externos eliminados se vuelvan a unir a tu organización - -Si algún miembro o colaborador externo se eliminó de la organización cuando habilitaste el uso requerido de autenticación de dos factores, recibirá un correo electrónico que le notifique que ha sido eliminado. Debe entonces habilitar la 2FA para su cuenta personal y contactarse con un propietario de la organización para solicitar acceso a tu organización. - -### Leer más - -- "[Ver si los usuarios de tu organización tienen la 2FA activada](/enterprise/{{ currentVersion }}/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" -- "[Asegurar tu cuenta con autenticación de dos factores (2FA)](/enterprise/{{ currentVersion }}/user/articles/securing-your-account-with-two-factor-authentication-2fa)" -- "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization)" -- "[Reinstalar el acceso a tu organización para un colaborador externo antiguo](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md b/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md deleted file mode 100644 index 0db218520d..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -title: Configurar el almacenamiento de archivos grandes de Git para tu empresa -intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' -redirect_from: - - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise/ - - /enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server - - /enterprise/admin/installation/configuring-git-large-file-storage - - /enterprise/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server - - /enterprise/admin/installation/migrating-to-a-different-git-large-file-storage-server - - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository/ - - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization/ - - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance/ - - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server/ - - /enterprise/admin/user-management/configuring-git-large-file-storage-for-your-enterprise - - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise -versions: - ghes: '*' - ghae: '*' -topics: - - Git - - Enterprise - - LFS - - Storage ---- -### Acerca de {% data variables.large_files.product_name_long %} - -{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} Puedes usar {% data variables.large_files.product_name_long %} con un repositorio único, con todos tus repositorios personales o de la organización, o con todos los repositorios de {% data variables.product.product_location_enterprise %}. Antes de poder habilitar {% data variables.large_files.product_name_short %} para repositorios u organizaciones específicas, debes habilitar {% data variables.large_files.product_name_short %} para tu aparato. - -{% data reusables.large_files.storage_assets_location %} -{% data reusables.large_files.rejected_pushes %} - -Para obtener más información, consulta "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)", "[Control de versiones de archivos grandes](/enterprise/user/articles/versioning-large-files/)," y el sitio del proyecto [{% data variables.large_files.product_name_long %} ](https://git-lfs.github.com/). - -{% data reusables.large_files.can-include-lfs-objects-archives %} - -### Configurar {% data variables.large_files.product_name_long %} para tu aparato - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -4. Dentro del "acceso de {% data variables.large_files.product_name_short %}", usa el menú desplegable y haz clic en **Enabled (Habilitado)** o **Disabled (Inhabilitado)**. ![Acceso a LFS de Git](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png) - -### Configurar {% data variables.large_files.product_name_long %} para un repositorio individual - -{% data reusables.enterprise_site_admin_settings.override-policy %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.repository-search %} -{% data reusables.enterprise_site_admin_settings.click-repo %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} - -### Configurar {% data variables.large_files.product_name_long %} para cada repositorio que pertenezca a una cuenta de usuario u organización - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user-or-org %} -{% data reusables.enterprise_site_admin_settings.click-user-or-org %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} - -### Configurar Almacenamiento de archivos de gran tamaño Git para usar un servidor de terceros - -{% data reusables.large_files.storage_assets_location %} -{% data reusables.large_files.rejected_pushes %} - -1. Inhabilita {% data variables.large_files.product_name_short %} en el aparato del {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Configurar {% data variables.large_files.product_name_long %}](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage#configuring-git-large-file-storage-for-your-appliance)." - -2. Crea un archivo de configuración {% data variables.large_files.product_name_short %} que apunte al servidor de terceros. - ```shell - # Show default configuration - $ git lfs env - > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) - > git version 2.7.4 (Apple Git-66) -   - > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) -   - # Create .lfsconfig that points to third party server. - $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo - $ git lfs env - > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) - > git version 2.7.4 (Apple Git-66) -   - > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none) -   - # Show the contents of .lfsconfig - $ cat .lfsconfig - [remote "origin"] - lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo - ``` - -3. Para mantener la misma configuración {% data variables.large_files.product_name_short %} para cada usuario, confirma un archivo `.lfsconfig` personalizado para el repositorio. - ```shell - $ git add .lfsconfig - $ git commit -m "Adding LFS config file" - ``` -3. Migra cualquier activo {% data variables.large_files.product_name_short %} existente. Para obtener más información, consulta la sección "[Migrarse a un servidor diferente de {% data variables.large_files.product_name_long %}](#migrating-to-a-different-git-large-file-storage-server)". - -### Migrar a un servidor de Git Large File Storage diferente - -Antes de migrar a un servidor {% data variables.large_files.product_name_long %} diferente, debes configurar {% data variables.large_files.product_name_short %} para usar un servidor de un tercero. Para obtener más información, consulta la sección "[Configurar {% data variables.large_files.product_name_long %} para utilizar un servidor de terceros](#configuring-git-large-file-storage-to-use-a-third-party-server)". - -1. Configura un repositorio con un segundo remoto. - ```shell - $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo -   - $ git lfs env - > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) - > git version 2.7.4 (Apple Git-66) -   - > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) - > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none) - ``` - -2. Extrae todos los objetos del remoto anterior. - ```shell - $ git lfs fetch origin --all - > Scanning for all objects ever referenced... - > ✔ 16 objects found - > Fetching objects... - > Git LFS: (16 de 16 archivos) 48.71 MB / 48.85 MB - ``` - -3. Extrae todos los objetos a un nuevo remoto. - ```shell - $ git lfs push NEW-REMOTE --all - > Scanning for all objects ever referenced... - > ✔ 16 objects found - > Pushing objects... - > Git LFS: (16 de 16 archivos) 48.00 MB / 48.85 MB, 879.10 KB pasados por alto - ``` - -### Leer más - -- [Sitio del proyecto {% data variables.large_files.product_name_long %}](https://git-lfs.github.com/) diff --git a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-github-enterprise-server.md b/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-github-enterprise-server.md deleted file mode 100644 index 716ab24148..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-github-enterprise-server.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Inhabilitar el acceso SSH de Git en el servidor de GitHub Enterprise -redirect_from: - - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account/ - - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account/ - - /enterprise/admin/hidden/disabling-ssh-access-for-your-appliance/ - - /enterprise/admin/articles/disabling-ssh-access-for-your-appliance/ - - /enterprise/admin/hidden/disabling-ssh-access-for-an-organization/ - - /enterprise/admin/articles/disabling-ssh-access-for-an-organization/ - - /enterprise/admin/hidden/disabling-ssh-access-to-a-repository/ - - /enterprise/admin/articles/disabling-ssh-access-to-a-repository/ - - /enterprise/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise/ - - /enterprise/admin/installation/disabling-git-ssh-access-on-github-enterprise-server - - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server - - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server -intro: 'Puedes evitar que las personas usen Git por SSH para determinados repositorios o para todos ellos en {% data variables.product.product_location_enterprise %}.' -versions: - enterprise-server: '*' ---- -### Inhabilitar el acceso SSH de Git para un repositorio específico - -{% data reusables.enterprise_site_admin_settings.override-policy %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.repository-search %} -{% data reusables.enterprise_site_admin_settings.click-repo %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -1. En "Acceso SSH de Git", usa el menú desplegable y haz clic en **Disabled** (Inhabilitado). ![Menú desplegable del acceso SSH de Git con la opción de inhabilitación seleccionada](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png) - -### Inhabilitar el acceso SSH de Git para todos los repositorios que le pertenecen a un usuario o a una organización - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user-or-org %} -{% data reusables.enterprise_site_admin_settings.click-user-or-org %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -7. En "Acceso SSH de Git", usa el menú desplegable y haz clic en **Disabled** (Inhabilitado). Luego selecciona **Enforce on all repositories** (Aplicar en todos los repositorios). ![Menú desplegable del acceso SSH de Git con la opción de inhabilitación seleccionada](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png) - -### Inhabilitar el acceso SSH de Git para todos los repositorios de un aparato - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -7. En "Acceso SSH de Git", usa el menú desplegable y haz clic en **Disabled** (Inhabilitado). Luego selecciona **Enforce on all repositories** (Aplicar en todos los repositorios). ![Menú desplegable del acceso SSH de Git con la opción de inhabilitación seleccionada](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png) diff --git a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/index.md b/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/index.md deleted file mode 100644 index c69765ece9..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Administrar repositorios en tu empresa -intro: 'Puedes administrar los parámetros disponibles para los administradores de repositorios en tu aparato {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/user-management/repositories - - /enterprise/admin/user-management/managing-repositories-in-your-enterprise -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /configuring-git-large-file-storage-for-your-enterprise - - /migrating-to-internal-repositories - - /disabling-git-ssh-access-on-your-enterprise - - /troubleshooting-service-hooks ---- - diff --git a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md b/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md deleted file mode 100644 index 76b7f70a49..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Migrar hacia repositorios internos -intro: 'Puedes migrar hacia repositorios internos para unificar la experiencia de innersource para los desarolladores que utilicen tanto {% data variables.product.prodname_ghe_server %} como {% data variables.product.prodname_ghe_cloud %}.' -redirect_from: - - /enterprise/admin/installation/migrating-to-internal-repositories - - /enterprise/admin/user-management/migrating-to-internal-repositories - - /admin/user-management/migrating-to-internal-repositories -permissions: Site administrators can migrate to internal repositories. -versions: - ghes: '*' -topics: - - Enterprise - - Privacy - - Repositories - - Security ---- -### 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 %} para obtener más información, consulta "[Acerca de la visibilidad en los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility#about-internal-repositories)." - -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 %}. - -Para prepararse para estos cambios, si has habilitado el modo privado, puedes ejecutar una migración en tu instancia para convertir los repositorios públicos en internos. Esta migración es opcional actualmente. Esto sirve para permitirte probar los cambios en una instancia no productiva. La migración será obligatoria en el futuro. - -Cuando ejecutas la migración, todos los repositorios públicos propiedad de las organizaciones en tu instancia se convertirán en repositorios internos. En caso de que cualquiera de estos repositorios tenga ramificaciones, estas se convertirán en privadas. Los repositorios privados permanecerán como privados. - -Todos los repositorios públicos propiedad de cuentas de usuario en tu instancia se convertirán en repositorios privados. Si cualquiera de estos repositorios tienen ramificaciones, éstas también se convertirán en privadas. A cada dueño de una ramificación se le otorgarán permisos de lectura para el directorio padre de la misma. - -Se inhabilitará el acceso de lectura anónimo para Git en cada repositorio público que se convierta en interno o privado. - -Si tu visibilidad predeterminada actual para los repositorios es pública, ahora se convertirá en interna. Si la predeterminada es privada, entonces no cambiará. Puedes cambiar esta configuración predeterminada en cualquier momento. Para encontrar más información, visita "[Configurar la visibilidad predeterminada de repositorios nuevos en tu aplicativo](/enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance)." - -La política de creación de repositorios para la instancia cambiará para inhabilitar los repositorios públicos y permitir los privados e internos. Puedes actualizar la política en cualquier momento. Para obtener más información, consulta "[Restringir la creación de repositorios en tu instancia](/enterprise/admin/user-management/restricting-repository-creation-in-your-instance)." - -El script de migración no tendrá efecto si no tienes el modo privado habilitado. - -### Ejecutar la migración - -1. Conecta con el shell administrativo. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh)." -2. Navega hacia el directorio `/data/github/current`. - ``` - cd /data/github/current - ``` -3. Ejecuta el comando de migración. - ``` - sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log - ``` - -Se mostrará el registro de salida en la terminal y quedará en `/tmp/convert_public_ghes_repos_to_internal.log`. - -### Leer más - -- "[Habilitar el modo privado](/enterprise/admin/installation/enabling-private-mode)" diff --git a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md b/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md deleted file mode 100644 index dc404e8512..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Solución de problemas con ganchos de servicio -intro: 'Si las cargar no se están entregando, comprueba estos problemas comunes.' -redirect_from: - - /enterprise/admin/articles/troubleshooting-service-hooks/ - - /enterprise/admin/developer-workflow/troubleshooting-service-hooks - - /enterprise/admin/user-management/troubleshooting-service-hooks - - /admin/user-management/troubleshooting-service-hooks -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise ---- -### Obtener información sobre las entregas - -Puedes buscar información para la última respuesta de todas las entregas de ganchos de servicio en cualquier repositorio. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -2. Explorar en el repositorio que estás investigando. -3. Haz clic en el enlace **Hooks** (Ganchos) en la barra lateral de navegación. ![Barra lateral de ganchos](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) -4. Haz clic en el enlace **Latest Delivery** (Última entrega) bajo el gancho de servicio que tiene problemas. ![Detalles de ganchos](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png) -5. En **Remote Calls** (Llamadas remotas), verás los encabezados que se usaron al publicar en el servidor remoto junto con la respuesta que el servidor remoto volvió a enviar a tu instalación. - -### Ver la carga - -{% data reusables.enterprise_site_admin_settings.access-settings %} -2. Explorar en el repositorio que estás investigando. -3. Haz clic en el enlace **Hooks** (Ganchos) en la barra lateral de navegación. ![Barra lateral de ganchos](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) -4. Haz clic en el enlace **Latest Delivery** (Última entrega) bajo el gancho de servicio que tiene problemas. -5. Da clic en **Entrega**. ![Ver la carga](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png) - -### Ver entregas anteriores - -Las entregas se almacenan durante 15 días. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -2. Explorar en el repositorio que estás investigando. -3. Haz clic en el enlace **Hooks** (Ganchos) en la barra lateral de navegación. ![Barra lateral de ganchos](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png) -4. Haz clic en el enlace **Latest Delivery** (Última entrega) bajo el gancho de servicio que tiene problemas. -5. Para ver otras entregas para ese gancho específico, haz clic en **More for this Hook ID** (Más para este ID de gancho): ![Ver más entregas](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png) diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md deleted file mode 100644 index 1db4c428fd..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Auditar claves SSH -intro: Los administradores del sitio pueden iniciar una auditoría en todas las instancias de las claves SSH. -redirect_from: - - /enterprise/admin/articles/auditing-ssh-keys/ - - /enterprise/admin/user-management/auditing-ssh-keys - - /admin/user-management/auditing-ssh-keys -versions: - ghes: '*' - ghae: '*' -topics: - - Auditing - - Enterprise - - Security - - SSH ---- -Una vez iniciada, la auditoría desactiva todas las claves SSH existentes y obliga a los usuarios a aprobarlas o rechazarlas antes de que sea posible clonarlas, extraerlas o subirlas a cualquier repositorio. Una auditoría es útil cuando un empleado o contratista se va de la empresa y necesitas asegurarte de que todas las claves estén verificadas. - -### Iniciar una auditoría - -Puedes iniciar una auditoría de claves SSH desde la pestaña "Todos los usuarios" del tablero de administrador del sitio: - -![Iniciar una auditoría de clave pública](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png) - -Una vez que haces clic en el botón "Iniciar auditoría de clave pública", serás redirigido a la pantalla de confirmación que explica lo que sucederá a continuación: - -![Confirmación de la auditoría](/assets/images/enterprise/security/Enterprise-Begin-Audit.png) - -Una vez que haces clic en el botón "Comenzar auditoría", todas las claves SSH son invalidadas y se necesitará aprobación. Verás una notificación que indica que la auditoría ha comenzado. - -### Lo que los usuarios ven - -Si un usuario intenta realizar cualquier operación Git a través de SSH, fallará y se indicará el siguiente mensaje: - -```shell -ERROR: Hola nombre de usuario. Estamos realizando una auditoría de clave SSH. -Visita http(s)://hostname/settings/ssh/audit/2 -para aprobar esta clave y saber que es segura. -Huella digital: ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91 -fatal: El final remoto ha colgado inesperadamente. -``` - -Cuando el usuario sigue el enlace, se le solicita aprobar las claves en su cuenta: - -![Auditoría de claves](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg) - -Una vez que se aprueban o se rechazan sus claves, podrá interactuar con los repositorios como siempre. - -### Agregar una clave SSH - -Cuando los usuarios nuevos agreguen una clave SSH, se les solicitará su contraseña: - -![Confirmación de contraseña](/assets/images/help/settings/sudo_mode_popup.png) - -Cuando un usuario agrega una clave, recibirá un correo electrónico de notificación que se verá como esto: - - Se agregó la siguiente clave SSH a tu cuenta: - - [title] - ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91 - - Si crees que esta clave se agregó por error, puedes eliminar la clave y desactivar el acceso a la siguiente ubicación: - - http(s)://HOSTNAME/settings/ssh diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-instance.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-instance.md deleted file mode 100644 index 51f944beb0..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-instance.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -title: Auditar usuarios a través de tu instancia -intro: 'El tablero de registro de auditoría {% data variables.product.prodname_ghe_server %} le muestra a los administradores del sitio las acciones realizadas por todos los usuarios y organizaciones a través de {% data variables.product.product_location_enterprise %} dentro de los últimos 90 días. Incluye detalles como quién realizó la acción, de qué acción se trata y cuándo se realizó.' -redirect_from: - - /enterprise/admin/guides/user-management/auditing-users-across-an-organization/ - - /enterprise/admin/user-management/auditing-users-across-your-instance - - /admin/user-management/auditing-users-across-your-instance -versions: - enterprise-server: '*' ---- -### Acceder al registro de auditoría {% data variables.product.prodname_ghe_server %} - -El tablero de registro de auditoría te brinda una presentación visual de los datos de auditoría a través de {% data variables.product.product_location_enterprise %}. - -![Tablero de registro de auditoría en toda la instancia](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png) - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.audit-log-tab %} - -Dentro del mapa, puedes usar panorámica y zoom para ver eventos en todo el mundo. Mantén el puntero sobre un país para ver un recuento rápido de los eventos de ese país. - -### Buscar eventos a través de tu instancia - -El registro de auditoría detalla la siguiente información acerca de las acciones realizadas dentro de {% data variables.product.product_location_enterprise %}: - -* [El repositorio](#search-based-on-the-repository) en el cual una acción fue realizada. -* [El usuario](#search-based-on-the-user) que realizó la acción. -* [La organización](#search-based-on-the-organization) a la cual pertenece la acción. -* [La acción](#search-based-on-the-action-performed) que fue realizada. -* [El país](#search-based-on-the-location) en el que la acción fue realizada. -* [La fecha y la hora](#search-based-on-the-time-of-action) en que ocurrió la acción. - -{% warning %} - -**Notas:** - -- Si bien no puedes utilizar texto para buscar entradas de auditoría, puedes crear consultas de búsqueda usando una variedad de filtros. Se admiten muchos operadores para [buscar a través de {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/searching-github). -- Para buscar eventos de más de 90 días, usa el calificador `created`. - -{% endwarning %} - -#### Búsqueda basada en el repositorio - -El calificador `repo` limita las acciones a un repositorio específico que le pertenece a tu organización. Por ejemplo: - -* `repo:my-org/our-repo` encuentra todos los eventos que ocurrieron para el repositorio `our-repo` en la organización `my-org`. -* `repo:my-org/our-repo repo:my-org/another-repo` encuentra todos los eventos que ocurrieron tanto para los repositorios `our-repo` como `another-repo` en la organización `my-org`. -* `-repo:my-org/not-this-repo` excluye todos los eventos que ocurrieron para el repositorio `not-this-repo` en la organización `my-org`. - -Debes incluir el nombre de tu organización dentro del calificador `repo`; si buscas solo `repo:our-repo` no funcionará. - -#### Búsqueda basada en el usuario - -El calificador `actor` examina eventos basados en el miembro de tu organización que realizó la acción. Por ejemplo: - -* `actor:octocat` encuentra todos los eventos realizados por `octocat`. -* `actor:octocat actor:hubot` encuentra todos los eventos realizados tanto por `octocat` como por `hubot`. -* `-actor:hubot` excluye todos los eventos realizados por `hubot`. - -Solo puedes usar un nombre de usuario {% data variables.product.prodname_ghe_server %}, no el nombre real de un individuo. - -#### Búsqueda basada en la organización - -El calificador `org` limita las acciones a una organización específica. Por ejemplo: - -* `org:my-org` encuentra todos los eventos que ocurrieron para la organización `my-org`. -* `org:my-org action:team` encuentra todos los eventos del equipo realizados dentro de la organización `my-org`. -* `-org:my-org` excluye todos los eventos que ocurrieron para la organizción `my-org`. - -#### Búsqueda basada en la acción realizada - -El calificador `action` busca los eventos específicos, agrupados dentro de categorías. Para obtener más información sobre los eventos asociados con estas categorías, consulta "[Acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)". - -| Nombre de la categoría | Descripción | -| ---------------------- | ----------------------------------------------------------------------------------------------------- | -| `gancho` | Contiene todas las actividades relacionadas con los webhooks. | -| `org` | Contiene todas las actividades relacionadas con los miembros de la organización. | -| `repo` | Contiene todas las actividades relacionadas con los repositorios que le pertenecen a tu organización. | -| `equipo` | Contiene todas las actividades relacionadas con los equipos en tu organización. | - -Puedes buscar conjuntos específicos de acciones utilizando estos términos. Por ejemplo: - -* `action:team` encuentra todos los eventos agrupados dentro de la categoría de equipo. -* `-action:billing` excluye todos los eventos en la categoría de facturación. - -Cada categoría tiene un conjunto de eventos asociados con los que puedes filtrar. Por ejemplo: - -* `action:team.create` encuentra todos los eventos donde se creó un equipo. -* `-action:billing.change_email` excluye todos los eventos donde se modificó el correo electrónico de facturación. - -#### Búsqueda basada en la ubicación - -El calificador `country` filtra las acciones por el país de origen. -- Puedes utilizar un código corto de dos letras del país o el nombre completo. -- Los países con espacios en sus nombres deben encerrarse entre comillas. Por ejemplo: - * `country:de` encuentra todos los eventos ocurridos en Alemania. - * `country:Mexico` encuentra todos los eventos ocurridos en México. - * `country:"United States"` encuentra todos los eventos que ocurrieron en Estados Unidos. - -#### Búsqueda basada en la fecha de acción - -El calificador `created` filtra las acciones por la fecha en la que ocurrieron. -- Define fechas usando el formato `YYYY-MM-DD`-- es decir, año, seguido del mes, seguido del día. -- Las fechas admiten [ calificadores mayor que, menor que y rango](/enterprise/{{ currentVersion }}/user/articles/search-syntax). Por ejemplo: - * `created:2014-07-08` encuentra todos los eventos ocurridos el 8 de julio de 2014. - * `created:>=2014-07-01` encuentra todos los eventos ocurridos el 8 de julio de 2014 o posteriormente. - * `created:<=2014-07-01` encuentra todos los eventos ocurridos el 8 de julio de 2014 o anteriormente. - * `created:2014-07-01..2014-07-31` encuentra todos los eventos ocurridos en el mes de julio de 2014. diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md deleted file mode 100644 index ac90cdf2d5..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Las mejores prácticas para la seguridad del usuario -intro: 'Fuera de las medidas de seguridad de nivel de instancia (SSL, aislamiento de subdominio, configuración de firewall) que un administrador de sitio puede implementar, hay pasos que tus usuarios pueden tomar para ayudar a proteger {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/user-management/best-practices-for-user-security - - /admin/user-management/best-practices-for-user-security -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Security - - User account ---- -### Activar autenticación de dos factores - -La autenticación de dos factores (2FA) es una manera de iniciar sesión en sitios web y servicios que requieren de un segundo factor además de una contraseña para la autenticación. En el caso de {% data variables.product.prodname_ghe_server %}, este segundo factor es un código de autenticación de un solo uso generado por una aplicación en el smartphone de un usuario. Te recomendamos que le solicites a tus usuarios activar la autenticación de dos factores en sus cuentas. Con la autenticación de dos factores, tanto la contraseña del usuario como su smartphone deben verse comprometidos para permitir que la propia cuenta se vea comprometida. - -Para obtener más información sobre cómo configurar la autenticación de dos factores, consulta "[Acerca de la autenticación de dos factores](/enterprise/{{ currentVersion }}/user/articles/about-two-factor-authentication)". - -### Solicitar un administrador de contraseñas - -Te recomendamos que le solicites a tus usuarios que instalen y usen un administrador de contraseñas, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/), o [Keeper](https://keepersecurity.com/), en cualquier equipo que usen para conectarse a {% data variables.product.product_location_enterprise %}. 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 - -Para limitar la posible superficie expuesta a ataques en el caso de una vulneración de la seguridad, te recomendamos que se le de a los usuarios acceso solo a los equipos y los repositorios que realmente necesiten para realizar su trabajo. Ya que los miembros con rol de propietario pueden acceder a todos los equipos y los repositorios en la organización, te recomendamos que este equipo sea lo más pequeño posible. - -Para obtener más información sobre la configuración de los equipos y de los permisos del equipo, consulta "[Niveles de permisos para el repositorio de una organizazión](/enterprise/{{ currentVersion }}/user/articles/repository-permission-levels-for-an-organization/)". diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/configuring-email-for-notifications.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/configuring-email-for-notifications.md deleted file mode 100644 index f7c39a3087..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/configuring-email-for-notifications.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: Configurar el correo electrónico para notificaciones -redirect_from: - - /enterprise/admin/guides/installation/email-configuration/ - - /enterprise/admin/articles/configuring-email/ - - /enterprise/admin/articles/troubleshooting-email/ - - /enterprise/admin/articles/email-configuration-and-troubleshooting/ - - /enterprise/admin/user-management/configuring-email-for-notifications - - /admin/user-management/configuring-email-for-notifications -intro: 'Para que sea fácil para los usuarios responder de forma rápida a una actividad en {% data variables.product.prodname_ghe_server %}, puedes configurar tu instancia para enviar notificaciones por correo electrónico en una propuesta, una solicitud de extracción y comentarios sobre confirmación de cambios, así como parámetros adicionales para permitir respuestas a los correos electrónicos entrantes. Los correos electrónicos para notificaciones se envían si hay una actividad en un repositorio que un usuario está observando, si hay una actividad en una solicitud de extracción o en una propuesta en la que están participando o si el usuario o equipo del que son un miembro son @mencionados en un comentario.' -versions: - enterprise-server: '*' ---- -### Configurar SMTP - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. En la parte superior de la página, haz clic en **Parámetros**. ![Pestaña Parámetros](/assets/images/enterprise/management-console/settings-tab.png) -3. En la barra lateral de la izquierda, haz clic en **Correo electrónico**. ![Pestaña Correo electrónico](/assets/images/enterprise/management-console/email-sidebar.png) -4. Selecciona **Activar correo electrónico**. Esto activará tanto el correo electrónico de salida como el de entrada, sin embargo para trabajar con el correo electrónico entrante también necesitarás configurar los parámetros de tu DNS como se describe a continuación en ["Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)". ![Activar correo electrónico de salida](/assets/images/enterprise/management-console/enable-outbound-email.png) -5. Completa los parámetros de tu servidor de correo electrónico: - - En el campo **Dirección del servidor**, escribe la dirección de tu servidor SMTP. - - En el campo **Puerto**, escribe el puerto que usa tu servidor SMTP para enviar correo electrónico. - - En el campo **Dominio**, escribe el nombre de dominio que enviará tu servidor SMTP con una respuesta HELO, de ser el caso. - - En el desplegable **Autenticación**, elige el tipo de cifrado usado por tu servidor SMTP. - - En el campo **Dirección de correo electrónico sin respuesta**, escribe la dirección de correo electrónico para usar en los campos De y Para para todos los correos electrónicos para notificaciones. - - {% note %} - - **Nota:** si seleccionas la casilla de verificación **Send from author (Enviar desde autor)** en el webhook del correo electrónico **Services (Servicios)** de un repositorio, el correo electrónico de salida para ese repositorio se enviará desde el autor y no desde el correo electrónico sin respuesta. Para obtener más información, consulta la sección "[Acerca de las notificaciones por correo electrónico para las cargas a tu repositorio](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)". - - {% endnote %} - -6. Si quieres descartar todos los correos electrónicos entrantes que estén dirigidos al correo electrónico sin respuesta, selecciona **Descartar correo electrónico dirigido a la dirección de correo electrónico sin respuesta**. ![Casilla de verificación para descartar los correos electrónicos dirigidos a la dirección de correo electrónico sin respuesta](/assets/images/enterprise/management-console/discard-noreply-emails.png) -7. En **Soporte**, elige un tipo de enlace para ofrecer un soporte adicional a tus usuarios: - - **Correo electrónico:** Una dirección de correo electrónico interna. - - **URL:** Un enlace a un sitio de soporte interno. Debes incluir tanto `http://` como `https://`. ![Correo de soporte técnico o URL](/assets/images/enterprise/management-console/support-email-url.png) -8. [Prueba de entrega del correo electrónico](#testing-email-delivery). - -### Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes - -Si quieres permitir respuestas de correo electrónico para las notificaciones, debes configurar los parámetros de tu DNS. - -1. Asegúrate de que el puerto 25 en la instancia esté accesible para tu servidor SMTP. -2. Crea un registro A que apunte a `reply.[hostname]`. Dependiendo de tu proveedor DNS y de la configuración del host de instancia, es posible que puedas crear un registro A único que apunte a `*.[hostname]`. -3. Crea un registro MX que apunte a `reply.[hostname]` para que los correos electrónicos para ese dominio sean enrutados a la instancia. -4. Crea un registro MX que apunte a `noreply.[hostname]` para `[hostname]` para que las respuestas a la dirección `cc` en los correos electrónicos para notificación sean enrutados a la instancia. Para obtener más información, consulta la sección {% if currentVersion ver_gt "enterprise-server@2.20" %}"[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Acerca de las notificaciones por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}". - -Con la configuración de tu DNS, ahora puedes probar si la configuración funciona. - -### Probar entrega del correo electrónico - -1. En la parte superior de la sección **Correo electrónico**, haz clic en **Probar parámetros del correo electrónico**. ![Probar parámetros del correo electrónico](/assets/images/enterprise/management-console/test-email.png) -2. En el campo **Enviar correo electrónico de prueba**, escribe una dirección donde enviar el correo electrónico de prueba. ![Probar dirección de correo electrónico](/assets/images/enterprise/management-console/test-email-address.png) -3. Haz clic en **Enviar correo electrónico de prueba**. ![Enviar correo electrónico de prueba](/assets/images/enterprise/management-console/test-email-address-send.png) - - {% tip %} - - **Sugerencia:** Si ocurren errores SMTP mientras se envía un correo electrónico de prueba, como un error de entrega inmediato o un error de configuración del correo saliente, los verás en el cuadro de diálogo de los parámetros del Correo electrónico de prueba. - - {% endtip %} - -4. Si el correo electrónico de prueba falla, [soluciona los problemas de los parámetros de tu correo electrónico](#troubleshooting-email-delivery). -5. Cuando el correo electrónico de prueba es exitoso, en la parte inferior de la página, haz clic en **Guardar parámetros**. ![Botón Guardar parámetros](/assets/images/enterprise/management-console/save-settings.png) -6. Espera que se complete la fase de configuración. ![Configurar tu instancia](/assets/images/enterprise/management-console/configuration-run.png) - -### Solución de problemas de entrega de correo electrónico - -#### Crea un Paquete de soporte - -Si no puedes determinar qué está mal desde el mensaje de error mostrado, puedes descargar un [paquete de soporte](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) que contiene toda la conversación SMTP entre tu servidor de correo y {% data variables.product.prodname_ghe_server %}. Una vez que hayas descargado el paquete, verifica las entradas en *enterprise-manage-logs/unicorn.log* de todo el registro de conversación SMTP y cualquier error relacionado. - -El registro unicornio debería mostrar una transacción similar a la siguiente: - -```shell -This is a test email generated from https://10.0.0.68/setup/settings -Connection opened: smtp.yourdomain.com:587 --> "220 smtp.yourdomain.com ESMTP nt3sm2942435pbc.14\r\n" -<- "EHLO yourdomain.com\r\n" --> "250-smtp.yourdomain.com at your service, [1.2.3.4]\r\n" --> "250-SIZE 35882577\r\n" --> "250-8BITMIME\r\n" --> "250-STARTTLS\r\n" --> "250-ENHANCEDSTATUSCODES\r\n" --> "250 PIPELINING\r\n" -<- "STARTTLS\r\n" --> "220 2.0.0 Ready to start TLS\r\n" -TLS connection started -<- "EHLO yourdomain.com\r\n" --> "250-smtp.yourdomain.com at your service, [1.2.3.4]\r\n" --> "250-SIZE 35882577\r\n" --> "250-8BITMIME\r\n" --> "250-AUTH LOGIN PLAIN XOAUTH\r\n" --> "250-ENHANCEDSTATUSCODES\r\n" --> "250 PIPELINING\r\n" -<- "AUTH LOGIN\r\n" --> "334 VXNlcm5hbWU6\r\n" -<- "dGhpc2lzbXlAYWRkcmVzcy5jb20=\r\n" --> "334 UGFzc3dvcmQ6\r\n" -<- "aXRyZWFsbHl3YXM=\r\n" --> "535-5.7.1 Username and Password not accepted. Learn more at\r\n" --> "535 5.7.1 http://support.yourdomain.com/smtp/auth-not-accepted nt3sm2942435pbc.14\r\n" -``` - -Este registro muestra que el aparato: - -* Abrió una conexión con el servidor SMTP (`Connection opened: smtp.yourdomain.com:587`). -* Realizó una conexión exitosa y eligió usar TLS (`TLS connection started`). -* Fue realizado el tipo de autenticación `login` (`<- "AUTH LOGIN\r\n"`). -* El servidor SMTP rechazó la autenticación como inválida (`-> "535-5.7.1 Username and Password not accepted.`). - -#### Consultar los registros {% data variables.product.product_location_enterprise %} - -Si necesitas verificar que tu correo electrónico entrante está funcionando, hay dos archivos de registro que puedes examinar en tu instancia: para verificar */var/log/mail.log* y */var/log/mail-replies/metroplex.log*. - -*/var/log/mail.log* verifica que los mensajes estén alcanzando tu servidor. Este es un ejemplo de una respuesta de correo electrónico exitosa: - -``` -Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: connect from st11p06mm-asmtp002.mac.com[17.172.124.250] -Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: 51DC9163323: client=st11p06mm-asmtp002.mac.com[17.172.124.250] -Oct 30 00:47:19 54-171-144-1 postfix/cleanup[13216]: 51DC9163323: message-id= -Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: from=, size=5048, nrcpt=1 (queue active) -Oct 30 00:47:19 54-171-144-1 postfix/virtual[13217]: 51DC9163323: to=, relay=virtual, delay=0.12, delays=0.11/0/0/0, dsn=2.0.0, status=sent (delivered to maildir) -Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: removed -Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asmtp002.mac.com[17.172.124.250] -``` - -Ten en cuenta que el cliente primero se conecta; luego, la cola se vuelve activa. Entonces, el mensaje es entregado, el cliente es retirado de la cola y la sesión se desconecta. - -*/var/log/mail-replies/metroplex.log* muestra si los correos electrónicos entrantes están siendo procesados para agregarse a las propuestas y a las solicitudes de extracción como respuestas. Este es un ejemplo de un mensaje exitoso: - -``` -[2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing -[2014-10-30T00:47:23.333 DEBUG (5284) #] Matched /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie -[2014-10-30T00:47:23.334 DEBUG (5284) #] Moving /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie => /data/user/incoming-mail/success -``` - -Notarás que `metroplex` captura el mensaje entrante, lo procesa y luego desplaza el archivo a `/data/user/incoming-mail/success`. - -#### Verificar los parámetros de tu DNS - -Para procesar los correos electrónicos entrantes de manera adecuada, debes configurar un Registro A válido (o CNAME), así como un Registro MX. Para obtener más información, consulta "[Configurar DNS y parámetros de firewall para permitir correos electrónicos entrantes](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." - -#### Controlar los parámetros de AWS Security Group o firewall - -Si {% data variables.product.product_location_enterprise %} está detrás de un firewall o está siendo servido a través de un AWS Security Group, asegúrate de que el puerto 25 esté abierto a todos los servidores de correo que envíen correos electrónicos a `reply@reply.[hostname]`. - -#### Contactar con soporte técnico - -Si aún no puedes resolver el problema, comunícate con {% data variables.contact.contact_ent_support %}. Adjunta el archivo de salida desde `http(s)://[hostname]/setup/diagnostics` en tu correo electrónico para ayudarnos a resolver tu problema. diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-on-your-instance.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-on-your-instance.md deleted file mode 100644 index a63726c078..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-on-your-instance.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Personalizar mensajes de usuario en tu instancia -redirect_from: - - /enterprise/admin/user-management/creating-a-custom-sign-in-message/ - - /enterprise/admin/user-management/customizing-user-messages-on-your-instance - - /admin/user-management/customizing-user-messages-on-your-instance -intro: 'Puedes crear mensajes personalizados {% if currentVersion ver_gt "enterprise-server@2.15" %} que los usuarios verán en las páginas de inicio y de cierre de sesión {% else %}un mensaje personalizado que los usuarios verán en la página de inicio de sesión {% endif %}.' -versions: - enterprise-server: '*' ---- -Puedes usar Markdown para dar formato al mensaje. 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/)." - -{% note %} - -**Nota:** Si usas SAML para la autenticación, tu proveedor de identidad presenta la página de inicio de sesión y no es personalizable a través de {% data variables.product.prodname_ghe_server %}. - -{% endnote %} - -### Crear un mensaje de inicio de sesión personalizado - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.messages-tab %} -5. En la "Página de inicio de sesión", haz clic en **Agregar mensaje** o **Editar mensaje**. ![Botón Editar mensaje](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. En **Mensaje de inicio de sesión**, escribe el mensaje que quisieras que vean los usuarios. ![Mensaje de inicio](/assets/images/enterprise/site-admin-settings/sign-in-message.png) -{% data reusables.enterprise_site_admin_settings.click-preview %} - ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) -8. Revisar el mensaje presentado. ![Mensaje de inicio presentado](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} - -### Crear un mensaje de cierre de sesión personalizado - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.messages-tab %} -5. En la "Página de cierre de sesión", haz clic en **Agregar mensaje** o **Editar mensaje**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. En **Mensaje de cierre de sesión**, escribe el mensaje que quieras que vean los usuarios. ![Mensaje de inicio encabezado de autent de dos factores](/assets/images/enterprise/site-admin-settings/sign-out-message.png) -{% data reusables.enterprise_site_admin_settings.click-preview %} - ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) -8. Revisar el mensaje presentado. ![Mensaje de salida presentado](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} - -{% if currentVersion ver_gt "enterprise-server@2.21" %} -### Creating a global announcement banner - -You can set a global announcement banner to be displayed to all users at the top of every page. - -You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.messages-tab %} -1. En la "Página de cierre de sesión", haz clic en **Agregar mensaje** o **Editar mensaje**. ![Botón Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) -1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Optionally, under "Expires on", use the calendar drop-down menu, and select an expiration date. ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png) -1. En la "Página de inicio de sesión", haz clic en **Agregar mensaje** o **Editar mensaje**. ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/preview-announcement-button.png) -1. Haz clic en **Guardar cambios**. ![Botón Editar mensaje](/assets/images/enterprise/site-admin-settings/save-announcement-button.png) -{% endif %} diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/index.md deleted file mode 100644 index ae3c96a964..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/index.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Administrar los usuarios en tu empresa -intro: 'Una vez que los usuarios pueden autenticar para {% data variables.product.product_location_enterprise %}, querrán configurar algunos parámetros de perfil personalizados básicos como un avatar y notificaciones por correo electrónico.' -redirect_from: - - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons/ - - /enterprise/admin/user-management/basic-account-settings - - /enterprise/admin/user-management/user-security - - /enterprise/admin/user-management/managing-users-in-your-enterprise -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /promoting-or-demoting-a-site-administrator - - /best-practices-for-user-security - - /auditing-users-across-your-enterprise - - /managing-dormant-users - - /suspending-and-unsuspending-users - - /placing-a-legal-hold-on-a-user-or-organization - - /auditing-ssh-keys - - /customizing-user-messages-for-your-enterprise - - /rebuilding-contributions-data - - /managing-global-webhooks ---- - diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md deleted file mode 100644 index 4ae444d545..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Managing dormant users -redirect_from: - - /enterprise/admin/articles/dormant-users/ - - /enterprise/admin/articles/viewing-dormant-users/ - - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant/ - - /enterprise/admin/user-management/managing-dormant-users - - /admin/user-management/managing-dormant-users -intro: A user account is considered to be dormant if it has not been active for at least a month. You may choose to suspend dormant users to free up user licenses. -versions: - ghes: '*' - ghae: '*' -topics: - - Accounts - - Enterprise - - Licensing ---- -"Activity" includes, but is not limited to: -- Signing in to {% data variables.product.prodname_ghe_server %}. -- Commenting on issues and pull requests. -- Creating, deleting, watching, and starring repositories. -- Pushing commits.{% if currentVersion ver_gt "enterprise-server@2.21" %} -- Accessing resources by using a personal access token or SSH key.{% endif %} - -### Viewing dormant users - -You can view a list of all dormant users who have not been suspended and who are not site administrators. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -3. In the left sidebar, click **Dormant users**. -![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png) -4. To suspend all the dormant users in this list, at the top of the page, click **Suspend all**. -![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png) - -### Determining whether a user account is dormant - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user %} -{% data reusables.enterprise_site_admin_settings.click-user %} -5. In the **User info** section, a red dot with the word "Dormant" indicates the user account is dormant, and a green dot with the word "Active" indicates the user account is active. -![Dormant user account](/assets/images/enterprise/stafftools/dormant-user.png) -![Active user account](/assets/images/enterprise/stafftools/active-user.png) - -### Configuring the dormancy threshold - -{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% if currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.enterprise-accounts.policies-tab %} -{% else %} -{% data reusables.enterprise-accounts.settings-tab %} -{% endif %} -{% data reusables.enterprise-accounts.options-tab %} -4. Under "Dormancy threshold", use the drop-down menu, and click the desired dormancy threshold. -![The Dormancy threshold drop-down menu](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png) diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks.md deleted file mode 100644 index 7f4ccfd983..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Administrar webhooks globales -intro: 'Los administradores del sitio pueden ver, agregar, editar y eliminar webhooks globales para realizar un seguimiento de los eventos en el nivel de instancia.' -redirect_from: - - /enterprise/admin/user-management/about-global-webhooks - - /enterprise/admin/user-management/managing-global-webhooks - - /admin/user-management/managing-global-webhooks -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise - - Webhooks ---- -### Acerca de los webhooks locales - -Puedes utilizar los webhooks globales para controlar, responder o aplicar reglas automáticamente para la administración de usuarios y de organizaciones en tu instancia. Por ejemplo, puedes configurar tus webhooks para ejecutar lo siguiente: -- Se crea o se elimina una cuenta de usuario. -- Se crea o se borra una organización -- Se agrega o se elimina un colaborador desde un repositorio. -- Se bifurca un repositorio - -![Listado de webhooks globales](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png) - -{% data reusables.enterprise_user_management.manage-global-webhooks-api %} - - -### Agregar un webhook local - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. Haz clic en **Add webhook** (Agregar webhook). ![Botón Agregar webhook en la página webhooks en el centro de administración](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png) -6. Escribe la URL donde quisieras recibir las cargas. ![Campo para escribir una URL de carga](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png) -7. Opcionalmente, usa el menú desplegable **Tipo de contenido** y haz clic en un formato de carga. ![Menú desplegable que detalla las opciones de tipo de contenido](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png) -8. Opcionalmente, en el campo **Secreto**, escribe una cadena para usar como una clave `secret`. ![Campo para escribir una cadena para usar como clave secreta](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png) -9. Opcionalmente, si no quieres que {% data variables.product.prodname_ghe_server %} verifique los certificados SSL cuando se entregan las cargas, haz clic en **Desactivar la verificación SSL**. Lee la información sobre verificación SSL, luego haz clic en **Entiendo que mis webhooks pueden no ser seguros**. ![Botón para desactivar la verificación SSL](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png) - - {% warning %} - - **Advertencia:** La verificación SSL ayuda a garantizar que las cargas de enganche se entreguen de forma segura. No es recomendable desactivar la verificación SSL. - - {% endwarning %} -10. Decide si quieres que esta webhook se dispare para cada evento o para eventos seleccionados: ![Botones de selección con opciones para recibir cargas para cada evento o eventos seleccionados](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png) - - Para cada evento, selecciona **Enviarme todo**. - - Para elegir eventos específicos, selecciona **Dejarme seleccionar eventos individuales**. -11. Si eliges seleccionar eventos individuales, selecciona si se disparará este webhook para una actividad de usuario o de organización. ![Casillas de verificación para eventos de usuario y de organización](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png) -12. Confirma que la casilla de verificación **Activo** esté seleccionada (se selecciona por defecto). ![Casilla de verificación Activo seleccionada](/assets/images/enterprise/site-admin-settings/add-global-webhook-active-checkbox.png) -13. Haz clic en **Add webhook** (Agregar webhook). - -### Editar un webhook global - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. Al lado del webhook que quieres editar, haz clic en **Editar**. ![Botón Editar al lado de una webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png) -6. Actualiza los parámetros del webhook. -7. Haz clic en **Actualizar webhook**. - -### Eliminar un webhook global - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. Al lado del webhook que quieres eliminar, haz clic en **Eliminar**. ![Botón Eliminar al lado de una webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png) -6. Lee la información sobre cómo eliminar un webhook, luego haz clic en **Sí, eliminar webhook**. ![Casilla emergente con información de advertencia y botón para confirmar la eliminación del webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png) - -### Visualizar respuestas y entregas recientes - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -5. En la lista de webhooks, haz clic en el webhook del que quieres ver las entregas. ![Lista de webhooks con los enlaces para visualizar cada webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png) -6. En "Entregas recientes", haz clic en una entrega para ver los detalles. ![Lista de entregas recientes de webhooks con los enlaces para visualizar los detalles](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png) diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization.md deleted file mode 100644 index 3ea5ef4619..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Asignar un titular legal a un usuario o una organización -intro: 'Puedes asignar un titular legal a un usuario o una organización para garantizar que los repositorios que poseen no se puedan eliminar de forma permanente desde {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/user-management/placing-a-legal-hold-on-a-user-or-organization - - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization -versions: - ghes: '*' - ghae: '*' -topics: - - Accounts - - Auditing - - Enterprise - - Organizations - - User account ---- -Generalmente, si alguien elimina un repositorio, estará disponible en el disco por 90 días y se puede restablecer mediante el tablero de administración del sitio. Después de los 90 días, el repositorio se purga y se elimina para siempre. Si asignas un titular legal a un usuario o una organización, los repositorios que ellos poseen se pueden restablecer indefinidamente. - -{% data reusables.enterprise_site_admin_settings.sign-in %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user-or-org %} -{% data reusables.enterprise_site_admin_settings.click-user-or-org %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -5. Haz clic en **Asignar titular legal**. ![Botón Asignar titular legal](/assets/images/enterprise/site-admin-settings/place-legal-hold-button.png) diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md deleted file mode 100644 index f48c41d292..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Promover o degradar a un administrador del sitio -redirect_from: - - /enterprise/admin/articles/promoting-a-site-administrator/ - - /enterprise/admin/articles/demoting-a-site-administrator/ - - /enterprise/admin/user-management/promoting-or-demoting-a-site-administrator - - /admin/user-management/promoting-or-demoting-a-site-administrator -intro: 'Los administradores del sitio pueden promover cualquier cuenta de usuarios normales a un administrador del sitio, así como degradar a otros administradores del sitio a usuarios normales.' -versions: - ghes: '*' -topics: - - Access management - - Accounts - - User account - - Enterprise ---- -{% tip %} - -**Nota:** Si [ la sincronización LDAP está activada](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) y se establece el atributo `Administrators group` cuando [se configura el acceso LDAP para usuarios](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance), estos usuarios tendrán automáticamente acceso de administrador del sitio para tu instancia. En este caso, no puedes promover usuarios manualmente con los siguientes pasos, debes agregarlos al grupo de administradores LDAP. - -{% endtip %} - -Para obtener información sobre cómo promover un usuario a un propietario de la organización, consulta la sección `ghe-org-admin-promote` de "[Utilidades de línea de comandos](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-org-admin-promote)". - -### Promover un usuario desde los parámetros de empresa - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.people-tab %} -{% data reusables.enterprise-accounts.administrators-tab %} -5. En la esquina superior derecha de la página, haz clic en **Agregar propietario**. ![Botón para agregar un administrador](/assets/images/help/business-accounts/business-account-add-admin-button.png) -6. En el campo Buscar, escribe el nombre del usuario y haz clic en **Agregar**. ![Campo de búsqueda para agregar un administrador](/assets/images/help/business-accounts/business-account-search-to-add-admin.png) - -### Degradar un administrador del sitio desde los parámetros de empresa - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.people-tab %} -{% data reusables.enterprise-accounts.administrators-tab %} -1. En la esquina superior izquierda de la página, en el campo de búsqueda "Find an administrator" (Encontrar un administrador), escribe el nombre de usuario de la persona que deseas degradar. ![Campo de búsqueda para encontrar un administrador](/assets/images/help/business-accounts/business-account-search-for-admin.png) - -1. In the search results, find the username of the person you want to demote, then use the {% octicon "gear" %} drop-down menu, and select **Remove owner**. ![Eliminar de la opción de empresa](/assets/images/help/business-accounts/demote-admin-button.png) - -### Promover un usuario desde la línea de comandos - -1. [SSH](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/) en tu aparato. -2. Ejecuta [ghe-user-promote](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-promote) con el nombre de usuario a promover. - ```shell - $ ghe-user-promote username - ``` - -### Degradar un administrador del sitio desde la línea de comandos - -1. [SSH](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/) en tu aparato. -2. Ejecuta [ghe-user-demote](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-demote) con el nombre de usuario a degradar. - ```shell - $ ghe-user-demote username - ``` diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md deleted file mode 100644 index 2042f1985a..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Reconstruir datos de contribuciones -intro: Es posible que necesites reconstruir los datos de contribuciones para vincular las confirmaciones de cambios a una cuenta de usuario. -redirect_from: - - /enterprise/admin/articles/rebuilding-contributions-data/ - - /enterprise/admin/user-management/rebuilding-contributions-data - - /admin/user-management/rebuilding-contributions-data -versions: - ghes: '*' -topics: - - Enterprise - - Repositories - - User account ---- -Siempre que se sube una confirmación de cambios a {% data variables.product.prodname_enterprise %}, se vincula a una cuenta de usuario, si ambas están asociadas con la misma dirección de correo electrónico. Sin embargo, las confirmaciones de cambio existentes *no* se vinculan de forma retroactiva cuando un usuario registra una dirección de correo electrónico nueva o crea una cuenta nueva. - -1. Visita la página de perfil de usuario. -{% data reusables.enterprise_site_admin_settings.access-settings %} -3. En el lado izquierdo de la página, haz clic en **Administrar**. ![Pestaña Administrar](/assets/images/enterprise/site-admin-settings/admin-tab.png) -4. En **Datos de contribuciones**, haz clic en **Reconstruir**. ![Botón Reconstruir](/assets/images/enterprise/site-admin-settings/rebuild-button.png) - -{% data variables.product.prodname_enterprise %} ahora iniciará trabajos en segundo plano para volver a vincular las confirmaciones de cambios con esa cuenta de usuario. ![Trabajos de reconstrucción en cola](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png) diff --git a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md b/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md deleted file mode 100644 index a68d38d084..0000000000 --- a/translations/es-XL/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -title: Suspender y anular suspensión de usuarios -redirect_from: - - /enterprise/admin/articles/suspending-a-user/ - - /enterprise/admin/articles/unsuspending-a-user/ - - /enterprise/admin/articles/viewing-suspended-users/ - - /enterprise/admin/articles/suspended-users/ - - /enterprise/admin/articles/suspending-and-unsuspending-users/ - - /enterprise/admin/user-management/suspending-and-unsuspending-users - - /admin/user-management/suspending-and-unsuspending-users -intro: 'Si un usuario se va o se traslada a un lugar diferente de la empresa, deberías eliminar o modificar su posibilidad de acceder a {% data variables.product.product_location_enterprise %}.' -versions: - ghes: '*' -topics: - - Access management - - Enterprise - - Security - - User account ---- -Puedes suspender las cuentas de usuario de {% data variables.product.prodname_ghe_server %} de aquellos que abandonen la compañía para abrir licencias de usuario en tu licencia de {% data variables.product.prodname_enterprise %} preservando las propuestas, comentarios, repositorios, gists y otros datos que hayan creado. Los usuarios suspendidos no pueden iniciar sesión en tu instancia, y no pueden subir ni extraer un código. - -Cuando suspendes un usuario, la modificación entra en efecto de inmediato sin notificar al usuario. Si el usuario intenta extraer o subir un repositorio, recibirá el siguiente error: - -```shell -$ git clone git@[hostname]:john-doe/test-repo.git -Cloning into 'test-repo'... -ERROR: Tu cuenta está suspendida. Consulta a tu administrador de instalación. -fatal: El extremo remoto colgó inesperadamente -``` - -Antes de suspender administradores del sitio, debes degradarlos a usuarios normales. Para obtener más información, consulta "[Promover o degradar a un administrador del sitio](/enterprise/admin/user-management/promoting-or-demoting-a-site-administrator)." - -{% tip %} - -**Nota:** Si [la sincronización LDAP está activada](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) para {% data variables.product.product_location_enterprise %}, los usuarios son suspendidos automáticamente cuando son eliminados del servidor de directorios LDAP. Cuando la sincronización LDAP está activada para tu instancia, los métodos de suspensión de usuario normal están desactivados. - -{% endtip %} - -### Suspender un usuario desde el tablero de administrador de usuarios - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.search-user %} -{% data reusables.enterprise_site_admin_settings.click-user %} -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -5. En "Suspensión de cuenta", en el cuadro rojo de Zona de peligro, haz clic en **Suspender**. ![Botón Suspender](/assets/images/enterprise/site-admin-settings/suspend.png) -6. Indica un motivo para suspender al usuario. ![Motivo de suspensión](/assets/images/enterprise/site-admin-settings/suspend-reason.png) - -### Anular la suspensión de un usuario desde el tablero de administrador de usuarios - -Como cuando se suspende un usuario, anular la suspensión entra en efecto de inmediato. El usuario no será notificado. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -3. En la barra lateral de la izquierda, haz clic en **Usuarios suspendidos**. ![Pestaña Usuarios suspendidos](/assets/images/enterprise/site-admin-settings/user/suspended-users-tab.png) -2. Haz clic en el nombre de la cuenta de usuario de la que quieres anular la suspensión. ![Usuario suspendido](/assets/images/enterprise/site-admin-settings/user/suspended-user.png) -{% data reusables.enterprise_site_admin_settings.admin-top-tab %} -{% data reusables.enterprise_site_admin_settings.admin-tab %} -4. En "Suspensión de cuenta", en el cuadro rojo de Zona de peligro, haz clic en **Anular suspensión**. ![Botón Anular suspensión](/assets/images/enterprise/site-admin-settings/unsuspend.png) -5. Indica un motivo para anular la suspensión del usuario. ![Motivo de anulación de suspensión](/assets/images/enterprise/site-admin-settings/unsuspend-reason.png) - -### Suspender un usuario desde la línea de comandos - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Ejecuta [ghe-user-suspend](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-suspend) con el nombre de usuario a suspender. - ```shell - $ ghe-user-suspend username - ``` - -### Crear un mensaje personalizado para usuarios suspendidos - -Puedes crear un mensaje personalizado que los usuarios suspendidos verán cuando intenten iniciar sesión. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.messages-tab %} -5. Haz clic en **Agregar mensaje**. ![Agregar mensaje](/assets/images/enterprise/site-admin-settings/add-message.png) -6. Escribe tu mensaje en el cuadro **Mensaje para usuario suspendido**. Puedes escribir Markdown o usar la barra de herramientas Markdown para diseñar tu mensaje. ![Mensaje para usuario suspendido](/assets/images/enterprise/site-admin-settings/suspended-user-message.png) -7. Haz clic en el botón **Vista previa** en el campo **Mensaje para usuario suspendido** para ver el mensaje representado. ![Botón Vista previa](/assets/images/enterprise/site-admin-settings/suspended-user-message-preview-button.png) -8. Revisar el mensaje presentado. ![Mensaje presentado de usuario suspendido](/assets/images/enterprise/site-admin-settings/suspended-user-message-rendered.png) -{% data reusables.enterprise_site_admin_settings.save-changes %} - -### Anular la suspensión de un usuario desde la línea de comandos - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Ejecuta [ghe-user-suspend](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities#ghe-user-suspend) con el nombre de usuario a anular la suspensión. - ```shell - $ ghe-user-unsuspend username - ``` - -### Leer más -- "[Suspender a un usuario](/enterprise/{{ currentVersion }}/v3/enterprise-admin/users/#suspend-a-user)" diff --git a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md deleted file mode 100644 index 55651d7f36..0000000000 --- a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Acerca de las migraciones -intro: 'Una migración es un proceso de transferencia de datos desde una ubicación *origen* (ya sea una organización {% data variables.product.prodname_dotcom_the_website %} o una instancia {% data variables.product.prodname_ghe_server %}) a una instancia *objetivo* {% data variables.product.prodname_ghe_server %}. Las migraciones se pueden utilizar para la transferencia de datos al cambiar de plataforma o actualizar el hardware en la instancia.' -redirect_from: - - /enterprise/admin/migrations/about-migrations - - /enterprise/admin/user-management/about-migrations - - /admin/user-management/about-migrations -versions: - ghes: '*' -topics: - - Enterprise - - Migration ---- -### Tipos de migraciones - -Existen tres tipos de migraciones que se pueden realizar: - -- Una migración de una instancia {% data variables.product.prodname_ghe_server %} a otra instancia {% data variables.product.prodname_ghe_server %}. Puedes migrar la cantidad de repositorios que desees de cualquier usuario u organización en la instancia. Antes de hacer una migración, debes tener acceso de administrador del sitio en ambas instancias. -- Una migración de una organización {% data variables.product.prodname_dotcom_the_website %} a una instancia {% data variables.product.prodname_ghe_server %}. Puedes migrar la cantidad de repositorios de la organización que desees. Antes de efectuar una migración, debes tener [ acceso administrativo ](/enterprise/user/articles/permission-levels-for-an-organization/) a la organización {% data variables.product.prodname_dotcom_the_website %}, así como acceso de administrador del sitio a la instancia de destino. -- *Las ejecuciones de prueba *son migraciones que importan datos a una [instancia de preparación](/enterprise/admin/guides/installation/setting-up-a-staging-instance/). Estas pueden ser útiles para ver qué *sucedería* si se aplicara una migración {% data variables.product.product_location_enterprise %}. **Se recomienda encarecidamente que se lleve a cabo una ejecución de prueba en una instancia de preparación antes de importar datos a la instancia de producción.** - -### Datos migrados - -En una migración, todo gira en torno a un repositorio. La mayoría de los datos asociados con un repositorio se pueden migrar. Por ejemplo, un repositorio dentro de una organización migrará el repositorio *y* la organización, así como los usuarios, equipos, propuestas y solicitudes de extracción asociados con el repositorio. - -Los elementos de la tabla a continuación se pueden migrar con un repositorio. Los elementos que no se muestren en la lista de datos migrados no se pueden migrar. - -{% data reusables.enterprise_migrations.fork-persistence %} - -| Datos asociados con un repositorio migrado | Notas | -| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Usuarios | Las **@menciones** de los usuarios se reescriben para coincidir con el objetivo. | -| Organizaciones | El nombre y los datos de una organización se migran. | -| Repositorios | Los enlaces a árboles Git, blobs, confirmaciones de cambios y líneas se reescriben para coincidir con el objetivo. El migrador sigue un máximo de tres redirecciones de repositorio. | -| Wikis | Todos los datos de la wiki se migran. | -| Equipos | Las **@menciones** de los equipos se reescriben para coincidir con el objetivo. | -| Hitos | Los registros horarios se conservan. | -| Tableros de proyecto | Los tableros de proyectos asociados con el repositorio y con la organización que posee el repositorio se migran. | -| Problemas | Las referencias de propuestas y los registros horarios se conservan. | -| Comentarios de propuestas | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. | -| Solicitudes de extracción | Las referencias cruzadas a las solicitudes de extracción se reescriben para coincidir con el objetivo. Los registros horarios se conservan. | -| Revisiones de solicitudes de extracción | Las revisiones de solicitudes de extracción y los datos asociados se migran. | -| Comentarios sobre revisiones de solicitudes de extracción | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. Los registros horarios se conservan. | -| Comentarios sobre confirmación de cambios | Las referencias cruzadas a los comentarios se reescriben para la instancia de destino. Los registros horarios se conservan. | -| Lanzamientos | Todos los datos de las versiones se migran. | -| Medidas adoptadas en las solicitudes de extracción o propuestas | Todas las modificaciones a las solicitudes de extracción o propuestas, como la asignación de usuarios, el cambio de nombre de título y la modificación de etiquetas se conservan, junto con los registros horarios de cada acción. | -| Archivos adjuntos | [Los archivos adjuntos a las propuestas y las solicitudes de extracción](/articles/file-attachments-on-issues-and-pull-requests) se migran. Puedes elegir inhabilitar esta opción como parte de la migración. | -| Webhooks | Solo se migran los webhooks activos. | -| Llaves de implementación de repositorios | Las llaves de implementación de repositorios se migran. | -| Ramas protegidas | La configuración de las ramas protegidas y los datos asociados se migran. | diff --git a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md b/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md deleted file mode 100644 index b7a316c8f1..0000000000 --- a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Exportar datos de migración desde GitHub.com -intro: 'Puedes exportar los dtos de migración desde una organización en {% data variables.product.prodname_dotcom_the_website %} si utilizas la API para seleccionar los repositorios que deseas migrar y luego generas un archivo de migración que puedas importar en una instancia de {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-com - - /enterprise/admin/migrations/exporting-migration-data-from-githubcom - - /enterprise/admin/migrations/preparing-the-githubcom-source-organization - - /enterprise/admin/migrations/exporting-the-githubcom-organizations-repositories - - /enterprise/admin/guides/migrations/preparing-the-github-com-source-organization - - /enterprise/admin/guides/migrations/exporting-the-github-com-organization-s-repositories - - /enterprise/admin/user-management/exporting-migration-data-from-githubcom - - /admin/user-management/exporting-migration-data-from-githubcom -versions: - ghes: '*' -topics: - - API - - Enterprise - - Migration ---- -### Preparar la orgnanización origen en {% data variables.product.prodname_dotcom %} - -1. Asegúrate de tener [permisos de propietario](/articles/permission-levels-for-an-organization/) en los repositorios de la organización de origen. - -2. {% data reusables.enterprise_migrations.token-generation %} en {% data variables.product.prodname_dotcom_the_website %}. - -{% data reusables.enterprise_migrations.make-a-list %} - -### Exportar los repositorios de la organización - -{% data reusables.enterprise_migrations.fork-persistence %} - -Para exportar datos del repositorio desde {% data variables.product.prodname_dotcom_the_website %}, usa la API de Migraciones. - -La API de Migraciones se encuentra actualmente en un período de previsualización, lo que significa que los puntos finales y los parámetros pueden cambiar en el futuro. Para acceder a la API de Migraciones, debes proporcionar un [tipo de medio](/v3/media) personalizado en el encabezado `Accept` (Aceptar): `application/vnd.github.wyandotte-preview+json`. Los ejemplos a continuación incluyen el tipo de medio personalizado. - -### Generar un archivo de migración - -{% data reusables.enterprise_migrations.locking-repositories %} - -1. Notifica a los miembros de tu organización que harás una migración. La exportación puede durar varios minutos, en función de la cantidad de repositorios que se exporten. La migración completa, incluida la importación, puede durar varias horas. Por lo tanto, te recomendamos que hagas una prueba para determinar cuánto tiempo tomará el proceso completo. Para obtener más información, consulta "[Acerca de las migraciones](/enterprise/admin/migrations/about-migrations#types-of-migrations)". - -2. Inicia una migración mediante `POST` al punto final de migración. Necesitarás: - * Tu token de acceso para autenticación. - * Una [lista de los repositorios](/v3/repos/#list-organization-repositories) que deseas migrar: - ```shell - curl -H "Autorización: token GITHUB_ACCESS_TOKEN" -X POST \ - -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ - -d'{"lock_repositories":true,"repositories":["orgname/reponame", "orgname/reponame"]}' \ - https://api.github.com/orgs/orgname/migrations - ``` - * Si deseas bloquear los repositorios antes de migrarlos, asegúrate de que `lock_repositories`esté establecido en `true` (true). Esto es altamente recomendable. - * Puedes excluir archivos adjuntos pasando `exclude_attachments: true` al punto final. {% data reusables.enterprise_migrations.exclude-file-attachments %} El tamaño final del archivo debe ser inferior a 20 GB. - - Esta solicitud devuelve un `id` único que representa tu migración. Lo necesitarás para solicitudes posteriores a la API de Migraciones. - -3. Envía una solicitud de `GET` al punto final del estado de la migración para extraer el estado de una migración. Necesitarás: - * Tu token de acceso para autenticación. - * El `id` único de la migración: - ```shell - curl -H "Autorización: token GITHUB_ACCESS_TOKEN" \ - -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ - https://api.github.com/orgs/orgname/migrations/id - ``` - - Una migración puede estar en uno de los siguientes estados: - * `pending` (pendiente), lo que significa que la migración aún no se ha iniciado. - * `exporting` (exportando), lo que significa que la migración está en curso. - * `exported` (exportada), lo que significa que la migración finalizó correctamente. - * `failed` (fallida), lo que significa que la migración falló. - -4. Una vez que se haya exportado tu migración, descarga el archivo de migración enviando una solicitud de `GET` al punto final de descarga de migración. Necesitarás: - * Tu token de acceso para autenticación. - * El `id` único de la migración: - ```shell - curl -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ - -u GITHUB_USERNAME:GITHUB_ACCESS_TOKEN \ - -L -o migration_archive.tar.gz \ - https://api.github.com/orgs/orgname/migrations/id/archive - ``` - -5. El archivo de migración se elimina automáticamente después de siete días. Si prefieres eliminarlo antes, puedes enviar una solicitud `DELETE` al punto final de eliminación del archivo de migración. Necesitarás: - * Tu token de acceso para autenticación. - * El `id` único de la migración: - ```shell - curl -H "Autorización: token GITHUB_ACCESS_TOKEN" -X DELETE \ - -H "Aceptar: application/vnd.github.wyandotte-preview+json" \ - https://api.github.com/orgs/orgname/migrations/id/archive - ``` -{% data reusables.enterprise_migrations.ready-to-import-migrations %} diff --git a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md deleted file mode 100644 index 246c978d37..0000000000 --- a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Exportar los datos de migración de tu empresa -intro: 'Para cambiar las plataformas o migrarse de una instancia de pruebas a una productiva, puedes exportar los datos de migración de una instancia de {% data variables.product.prodname_ghe_server %} si preparas la instancia, bloqueas los repositorios, y generas un archivo de migración.' -redirect_from: - - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise/ - - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server - - /enterprise/admin/migrations/preparing-the-github-enterprise-server-source-instance - - /enterprise/admin/migrations/exporting-the-github-enterprise-server-source-repositories - - /enterprise/admin/guides/migrations/preparing-the-github-enterprise-source-instance/ - - /enterprise/admin/guides/migrations/exporting-the-github-enterprise-source-repositories/ - - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise - - /admin/user-management/exporting-migration-data-from-your-enterprise -versions: - ghes: '*' -topics: - - API - - Enterprise - - Migration ---- -### Preparar la instancia origen de {% data variables.product.prodname_ghe_server %} - -1. Verifica que eres un administrador del sitio en el origen {% data variables.product.prodname_ghe_server %}. La mejor manera de hacerlo es verificar que puedes usar [SSH en la instancia](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/). - -2. {% data reusables.enterprise_migrations.token-generation %} en la instancia de origen {% data variables.product.prodname_ghe_server %}. - -{% data reusables.enterprise_migrations.make-a-list %} - -### Exportar los repositorios origen de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_migrations.locking-repositories %} - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Para preparar un repositorio para la exportación, usa el comando `ghe-migrator add` con la URL del repositorio: - * Si estás bloqueando el repositorio, agrega el comando `--lock`. Si estás efectuando una ejecución de prueba, el comando `--lock` no es necesario. - ```shell - $ ghe-migrator add https://hostname/username/reponame --lock - ``` - * Puedes excluir archivos adjuntos agregando ` --exclude_attachments ` al comando. {% data reusables.enterprise_migrations.exclude-file-attachments %} - * Para preparar varios repositorios al mismo tiempo para exportación, crea un archivo de texto que incluya las URL del repositorio en una línea separada, y ejecuta el comando `ghe-migrator add` con el indicador `-i` y la ruta a tu archivo de texto. - ```shell - $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URLS.txt - ``` - -3. Cuando se te indique, ingresa tu nombre de usuario {% data variables.product.prodname_ghe_server %}: - ```shell - Ingresa el nombre de usuario autorizado para la migración: admin - ``` -4. Cuando se te pida un token de acceso personal, ingresa el token de acceso que creaste en"[Preparación de {% data variables.product.prodname_ghe_server %} la instancia de origen](#preparing-the-github-enterprise-server-source-instance)": - ```shell - Ingresa el token de acceso personal: ************** - ``` -5. Cuando `ghe-migrator add` haya terminado, imprimirá el "GUID de migración" único que generó para identificar esta exportación, así como una lista de los recursos que se agregaron a la exportación. Utilizarás el GUID de migración que generaste en los pasos posteriores `ghe-migrator add` y`ghe-migrator export` para indicar a `ghe-migrator` que continúe operando en la misma exportación. - ```shell - > 101 models added to export - > Migration GUID: example-migration-guid - > Number of records in this migration: - > users | 5 - > organizations | 1 - > repositories | 1 - > teams | 3 - > protected_branches | 1 - > pull_request_reviews | 1 - > milestones | 1 - > issues | 3 - > pull_requests | 5 - > pull_request_review_comments | 4 - > commit_comments | 2 - > issue_comments | 10 - > issue_events | 63 - > releases | 3 - > attachments | 4 - > projects | 2 - ``` - Cada vez que agregues un repositorio nuevo con un GUID de migración existente, se actualizará la exportación existente. Si ejecutas `ghe-migrator add` nuevamente sin un GUID de migración, comenzará una nueva exportación y generará un nuevo GUID de migración. **No vuelvas a utilizar el GUID de migración generado durante una exportación cuando comiences a preparar tu migración para importar**. - -3. Si bloqueaste el repositorio de origen, puedes usar el comando `ghe-migrator target_url` para configurar un mensaje de bloqueo personalizado en la página del repositorio que vincula con la nueva ubicación del repositorio. Pasa la URL del repositorio de origen, la URL del repositorio de destino y el GUID de migración del Paso 5: - - ```shell - $ ghe-migrator target_url https://hostname/username/reponame https://target_hostname/target_username/target_reponame -g MIGRATION_GUID - ``` - -6. Usa el comando `ghe-migrator add` con el indicador `-g` para agregar más repositorios a la misma exportación. Pasarás la nueva URL del repositorio y el GUID de migración del Paso 5: - ```shell - $ ghe-migrator add https://hostname/username/other_reponame -g MIGRATION_GUID --lock - ``` -7. Cuando hayas terminado de agregar repositorios, genera el archivo de migración con el comando `ghe-migrator export` con el indicador `-g` y el GUID de migración del Paso 5: - ```shell - $ ghe-migrator export -g MIGRATION_GUID - > Archivo guardado en: /data/github/current/tmp/MIGRATION_GUID.tar.gz - ``` - * {% data reusables.enterprise_migrations.specify-staging-path %} - -8. Cierra la conexión a {% data variables.product.product_location_enterprise %}: - ```shell - $ exit - > logout - > Connection to hostname closed. - ``` -9. Copia el archivo de migración a tu computadora con el comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp). Se te asignará al archivo de almacenamiento un nombre con el GUID de migración: - ```shell - $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop - ``` -{% data reusables.enterprise_migrations.ready-to-import-migrations %} diff --git a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md b/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md deleted file mode 100644 index 323be1db36..0000000000 --- a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Importar datos desde sistemas de control de versiones de terceros -intro: 'Usando el conjunto de herramientas git-import, puedes importar desde Subversion, Mercurial y Team Foundation Version Control a los repositorios Git en {% data variables.product.prodname_ghe_server %}.' -redirect_from: - - /enterprise/admin/migrations/importing-data-from-third-party-version-control-systems - - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems - - /admin/user-management/importing-data-from-third-party-version-control-systems -versions: - ghes: '*' -topics: - - Enterprise - - Migration ---- -### Importar proyectos de Mercurial - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Haz un clon sin procesar del proyecto mediante el comando a continuación, especificando la URL del proyecto de origen y una ruta a un repositorio temporal: - ```shell - $ git-import-hg-raw HG-CLONE-URL /PATH/REPO-NAME.git - # Crea un nuevo repositorio con uno o más ref de Git en "refs/import/" en la ruta especificada. - ``` -{% data reusables.enterprise_migrations.review-the-import-csv %} -4. Reescribe los autores y las ramas utilizando el archivo CSV: - ```shell - $ git-import-rewrite --flavor hg --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git - ``` -5. Si aún no lo has hecho, [ crea un nuevo repositorio vacío en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). -{% data reusables.command_line.switching_directories_procedural %} -7. Sube el repositorio importado a {% data variables.product.prodname_ghe_server %}: - ```shell - $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE - ``` - -### Importar proyectos de Subversion - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Haz un clon sin procesar del proyecto mediante el comando a continuación, especificando la URL del proyecto de origen y una ruta a un repositorio temporal: - ```shell - $ git-import-svn-raw SVN-CLONE-URL /PATH/REPO-NAME.git - # Crea un nuevo repositorio con uno o más ref de Git en "refs/import/" en la ruta especificada. - ``` -{% data reusables.enterprise_migrations.review-the-import-csv %} -4. Reescribe los autores y las ramas utilizando el archivo CSV: - ```shell - $ git-import-rewrite --flavor svn --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git - ``` -5. Si aún no lo has hecho, [ crea un nuevo repositorio vacío en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). -{% data reusables.command_line.switching_directories_procedural %} -7. Sube el repositorio importado a {% data variables.product.prodname_ghe_server %}: - ```shell - $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE - ``` - -### Importar proyectos de Team Foundation Version Control - -{% data reusables.enterprise_installation.ssh-into-instance %} -2. Haz un clon sin procesar del proyecto mediante el comando a continuación, especificando la URL del proyecto de origen y una ruta a un repositorio temporal: - ```shell - $ git-import-tfs-raw TEAM-FOUNDATION-CLONE-URL /PATH/REPO-NAME.git - # Crea un nuevo repositorio con uno o más ref de Git en "refs/import/" en la ruta especificada. - ``` -{% data reusables.enterprise_migrations.review-the-import-csv %} -4. Reescribe los autores y las ramas utilizando el archivo CSV: - ```shell - $ git-import-rewrite --flavor tfs --authors /PATH/AUTHORS-MAP-FILE.csv /PATH/REPO-NAME.git - ``` -5. Si aún no lo has hecho, [ crea un nuevo repositorio vacío en {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/user/articles/creating-a-new-repository). -{% data reusables.command_line.switching_directories_procedural %} -7. Sube el repositorio importado a {% data variables.product.prodname_ghe_server %}: - ```shell - $ git push --mirror PUSH-URL-ON-GITHUB-ENTERPRISE - ``` - -### Leer más - -- "[Command-line-utilities](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#import-and-export)" diff --git a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md b/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md deleted file mode 100644 index a3a32109ff..0000000000 --- a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Migrar los datos desde y hacia tu empresa -intro: 'Puedes exportar datos de usuario, organización y repositorio desde {% data variables.product.prodname_ghe_server %} o {% data variables.product.prodname_dotcom_the_website %}, y posteriormente importar los datos en {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/ - - /enterprise/admin/categories/migrations-and-upgrades/ - - /enterprise/admin/migrations/overview - - /enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise -versions: - ghes: '*' -topics: - - Enterprise -children: - - /about-migrations - - /exporting-migration-data-from-your-enterprise - - /exporting-migration-data-from-githubcom - - /preparing-to-migrate-data-to-your-enterprise - - /migrating-data-to-your-enterprise - - /importing-data-from-third-party-version-control-systems ---- - diff --git a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md b/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md deleted file mode 100644 index d4b8df1ed5..0000000000 --- a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: Migrar datos a tu empresa -intro: 'Después de generar un archivo de migración, puedes importar los datos a tu instancia de destino del {% data variables.product.prodname_ghe_server %}. Podrás revisar los cambios para detectar posibles conflictos antes de aplicar de manera permanente los cambios a tu instancia de destino.' -redirect_from: - - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise/ - - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server - - /enterprise/admin/migrations/reviewing-migration-data - - /enterprise/admin/migrations/completing-the-import-on-github-enterprise-server - - /enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise/ - - /enterprise/admin/guides/migrations/reviewing-the-imported-data/ - - /enterprise/admin/guides/migrations/completing-the-import-on-github-enterprise/ - - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/ - - /enterprise/admin/user-management/migrating-data-to-your-enterprise - - /admin/user-management/migrating-data-to-your-enterprise -versions: - ghes: '*' -topics: - - Enterprise - - Migration ---- -### Aplicar los datos importados en {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.ssh-into-target-instance %} - -2. Con el comando `ghe-migrator import`, inicia el proceso de importación. Necesitarás: - * Tu GUID de migración. - * Tu token de acceso personal para autenticación. El token de acceso personal que utilices es solo para autenticación como administrador de sitio, y no requiere ningún alcance específico. 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)". - - ```shell - $ ghe-migrator import /home/admin/MIGRATION_GUID.tar.gz -g MIGRATION_GUID -u username -p TOKEN - - > Comenzando con GitHub::Migrador - > Importación 100 % completa / - ``` - - * {% data reusables.enterprise_migrations.specify-staging-path %} - -### Revisar datos de migración - -De forma predeterminada, `ghe-migrator audit` devuelve todos los registros. También te permite filtrar los registros por: - - * Los tipos de registros. - * El estado de los registros. - -Los tipos de registro coinciden con los encontrados en los [datos migrados](/enterprise/admin/guides/migrations/about-migrations/#migrated-data). - -### Filtros de tipo de registro - -| Tipo de registro | Nombre del filtro | -| --------------------------------------------------------------- | --------------------------------------------------- | -| Usuarios | `usuario` | -| Organizaciones | `organización` | -| Repositorios | `repositorio` | -| Equipos | `equipo` | -| Hitos | `hito` | -| Tableros de proyecto | `project` | -| Problemas | `propuesta` | -| Comentarios de propuestas | `comentario_propuesta` | -| Solicitudes de extracción | `solicitud_extracción` | -| Revisiones de solicitudes de extracción | `revisión_solicitud de extracción` | -| Comentarios sobre confirmación de cambios | `comentario_confirmación de cambios` | -| Comentarios sobre revisiones de solicitudes de extracción | `comentarios _revisiones_solicitudes de extracción` | -| Lanzamientos | `lanzamiento` | -| Medidas adoptadas en las solicitudes de extracción o propuestas | `evento_propuesta` | -| Ramas protegidas | `rama_protegida` | - -### Filtros de estado de registro - -| Estado de registro | Descripción | -| --------------------- | ---------------------------------- | -| `exportar` | El registro se exportará. | -| `importar` | El registro se importará. | -| `asignar` | El registro se asignará. | -| `rename (renombrar)` | El registro se renombrará. | -| `fusionar` | El registro se fusionará. | -| `exportado` | El registro se exportó con éxito. | -| `importado` | El registro se importó con éxito. | -| `asignado` | El registro se asignó con éxito. | -| `renombrado` | El registro se renombró con éxito. | -| `fusionado` | El registro se fusionó con éxito. | -| `exportación_fallida` | El registro no se pudo exportar. | -| `importación_fallida` | El registro no se pudo importar. | -| `asignación_fallida` | El registro no se pudo asignar. | -| `renombrar_fallido` | El registro no se pudo renombrar. | -| `fusión_fallida` | El registro no se pudo fusionar. | - -### Filtrar registros auditados - -Con el comando de auditoría `ghe-migrator audit` puedes filtrar en función del tipo de registro mediante el indicador `-m`. Del mismo modo, puedes filtrar en el estado de importación mediante el indicador `-s`. El comando se ve de la siguiente manera: - -```shell -$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION_GUID -``` - -Por ejemplo, para ver cada organización y equipo importados con éxito, debes ingresar: -```shell -$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION_GUID -> model_name,source_url,target_url,state -> organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed -``` - -**Te recomendamos encarecidamente que hagas una auditoría de todas las importaciones que fallaron.** Para ello, ingresa en: -```shell -$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION_GUID -> model_name,source_url,target_url,state -> user,https://gh.source/octocat,https://gh.target/octocat,failed -> repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed -``` - -Si tienes alguna duda sobre las importaciones fallidas, comunícate con {% data variables.contact.contact_ent_support %}. - -### Completar la importación en {% data variables.product.prodname_ghe_server %} - -Después de que se aplique tu migración a tu instancia destino y la hayas revisado, desbloquearás los repositorios y los borrarás del origen. Antes de eliminar los datos de origen, se recomienda esperar alrededor de dos semanas para asegurarse de que todo funciona de acuerdo con lo esperado. - -### Desbloquear repositorios en la instancia de destino - -{% data reusables.enterprise_installation.ssh-into-instance %} -{% data reusables.enterprise_migrations.unlocking-on-instances %} - -### Desbloquear repositorios en el origen - -#### Desbloquear los repositorios de una organización en {% data variables.product.prodname_dotcom_the_website %} - -Para desbloquear los repositorios en una organización{% data variables.product.prodname_dotcom_the_website %}, debes enviar una solicitud de `DELETE` al punto final de desbloqueo de migración. Necesitarás: - * Tu token de acceso para autenticación - * El `id` único de la migración - * El nombre del repositorio a desbloquear -```shell -curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ - -H "Accept: application/vnd.github.wyandotte-preview+json" \ - https://api.github.com/orgs/orgname/migrations/id/repos/repo_name/lock -``` - -#### Borrar los repositorios de una organización en {% data variables.product.prodname_dotcom_the_website %} - -Después de desbloquear los repositorios de la organización de {% data variables.product.prodname_dotcom_the_website %}, debes borrar todos los repositorios que migraste anteriormente utilizando [la terminal de borrado de repositorios](/enterprise/{{ currentVersion }}/v3/repos/#delete-a-repository). Necesitarás tu token de acceso para la autenticación: -```shell -curl -H "Authorization: token GITHUB_ACCESS_TOKEN" -X DELETE \ - https://api.github.com/repos/orgname/repo_name -``` - -#### Desbloquear repositorios desde una instancia de {% data variables.product.prodname_ghe_server %} - -{% data reusables.enterprise_installation.ssh-into-instance %} -{% data reusables.enterprise_migrations.unlocking-on-instances %} diff --git a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md deleted file mode 100644 index 3d5b68c969..0000000000 --- a/translations/es-XL/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: Prepararse para migrar los datos a tu empresa -intro: 'Después de generar un archivo de migración, puedes importar los datos a tu instancia de destino del {% data variables.product.prodname_ghe_server %}. Podrás revisar los cambios para detectar posibles conflictos antes de aplicar de manera permanente los cambios a tu instancia de destino.' -redirect_from: - - /enterprise/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server - - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts - - /enterprise/admin/migrations/reviewing-migration-conflicts - - /enterprise/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings - - /enterprise/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise/ - - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise - - /admin/user-management/preparing-to-migrate-data-to-your-enterprise -versions: - ghes: '*' -topics: - - Enterprise - - Migration ---- -### Preparar los datos migrados para importarlos a {% data variables.product.prodname_ghe_server %} - -1. Con el comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copia el archivo de migración generado desde tu instancia u organización de origen a tu {% data variables.product.prodname_ghe_server %} destino: - - ```shell - $ scp -P 122 /path/to/archive/MIGRATION_GUID.tar.gz admin@hostname:/home/admin/ - ``` - -{% data reusables.enterprise_installation.ssh-into-target-instance %} - -3. Usa el comando `ghe-migrator prepare` para preparar el archivo para importar en la instancia de destino y generar un nuevo GUID de Migración para que uses en los pasos subsiguientes: - - ```shell - ghe-migrator prepare /home/admin/MIGRATION_GUID.tar.gz - ``` - - * Para comenzar un nuevo intento de importación, ejecuta `ghe-migrator prepare` nuevamente y obtén un nuevo GUID de migración. - * {% data reusables.enterprise_migrations.specify-staging-path %} - -### Generar una lista de conflictos de migración - -1. Con el comando `ghe-migrator conflicts` con el GUID de migración, genera un archivo *conflicts.csv*: - ```shell - $ ghe-migrator conflicts -g MIGRATION_GUID > conflicts.csv - ``` - - Si no se reporta conflicto alguno, puedes importar los datos de forma segura siguiendo los pasos en la sección "[Migrar datos a tu empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)". -2. Si hay conflictos, con el comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp), copia *conflicts.csv* a tu computadora local: - ```shell - $ scp -P 122 admin@hostname:conflicts.csv ~/Desktop - ``` -3. Continúa con "[Resolver conflictos de migración o crear asignaciones personalizadas](#resolving-migration-conflicts-or-setting-up-custom-mappings)". - -### Revisar conflictos de migración - -1. Con un editor de texto o [ un software de hoja de cálculo compatible con CSV](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support), abre *conflicts.csv*. -2. Con la guía de los ejemplos y las tablas de referencia a continuación, revisa el archivo *conflicts.csv* para asegurarte de que se tomarán las medidas adecuadas al importar. - -El archivo *conflicts.csv* contiene un *mapa de migración* de conflictos y acciones recomendadas. Un mapa de migración enumera tanto los datos que se migran desde el origen como la forma en que los datos se aplicarán al destino. - -| `model_name` | `source_url` | `target_url` | `recommended_action` | -| -------------- | ------------------------------------------------------ | ------------------------------------------------------ | -------------------- | -| `usuario` | `https://example-gh.source/octocatc` | `https://example-gh.target/octocat` | `asignar` | -| `organización` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `asignar` | -| `repositorio` | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename (renombrar)` | -| `equipo` | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `fusionar` | - -Cada fila de *conflicts.csv* proporciona la siguiente información: - -| Nombre | Descripción | -| -------------------- | -------------------------------------------------------------------- | -| `model_name` | El tipo de datos que se están cambiando. | -| `source_url` | La URL fuente de los datos. | -| `target_url` | La URL de destino esperada de los datos. | -| `recommended_action` | La acción preferida que tomará `ghe-migrator` al importar los datos. | - -#### Asignaciones posibles para cada tipo de registro - -Hay varias acciones de asignación diferentes que `ghe-migrator` puede realizar al transferir datos: - -| `Acción` | Descripción | Modelos aplicables | -| --------------------- | -------------------------------------------------------------------------------------------- | -------------------------------------- | -| `importar` | (predeterminado) Los datos del origen se importan al destino. | Todos los tipos de registro | -| `asignar` | Los datos del origen se reemplazan por los datos existentes en el destino. | Usuarios, organizaciones, repositorios | -| `rename (renombrar)` | Los datos del origen se renombran y luego se copian en el destino. | Usuarios, organizaciones, repositorios | -| `asignar_o_renombrar` | Si el destino existe, asignar a ese destino. De lo contrario, renombrar el modelo importado. | Usuarios | -| `fusionar` | Los datos del origen se combinan con los datos existentes en el destino. | Equipos | - -**Te recomendamos ampliamente que revises el archivo *conflicts.csv* y que utilices [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) para garantizar que se estén tomando las acciones adecuadas.** Si todo se ve bien, puedes continuar con las acciones para "[Migrar los datos a tu empresa](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server)". - - -### Resolver conflictos de migración o crear asignaciones personalizadas - -Si crees que `ghe-migrator` realizará un cambio incorrecto, puedes hacer correcciones cambiando los datos en *conflicts.csv*. Puedes hacer cambios en cualquiera de las filas en *conflicts.csv*. - -Por ejemplo, supongamos que observas que el usuario `octocat` del origen se está asignando a `octocat` en el destino: - -| `model_name` | `source_url` | `target_url` | `recommended_action` | -| ------------ | ------------------------------------ | ----------------------------------- | -------------------- | -| `usuario` | `https://example-gh.source/octocatc` | `https://example-gh.target/octocat` | `asignar` | - -Puedes optar por asignar el usuario a un usuario diferente en el destino. Supongamos que sabes que `octocat` en realidad debe ser `monalisa` en el destino. Puedes cambiar la columna `target_url` en *conflicts.csv* a `monalisa`: - -| `model_name` | `source_url` | `target_url` | `recommended_action` | -| ------------ | ------------------------------------ | ------------------------------------ | -------------------- | -| `usuario` | `https://example-gh.source/octocatc` | `https://example-gh.target/monalisa` | `asignar` | - -Como otro ejemplo, si deseas cambiar el nombre del repositorio `octo-org/widgets` a `octo-org/amazing-widgets` en la instancia de destino, cambia la `target_url` a `octo-org/amazing-widgets` y la `recommended_action` a `rename`: - -| `model_name` | `source_url` | `target_url` | `recommended_action` | -| ------------- | -------------------------------------------- | ---------------------------------------------------- | -------------------- | -| `repositorio` | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename (renombrar)` | - -#### Agregar asignaciones personalizadas - -Una situación común durante una migración es que los usuarios migrados tengan diferentes nombres de usuario en el destino que los que tienen en el origen. - -Dada una lista de nombres de usuario en el origen y una lista de nombres de usuario en el destino, puedes crear un archivo CSV con asignaciones personalizadas y luego aplicarlo para garantizar que el nombre de usuario y el contenido de cada usuario se atribuyan correctamente al final de la migración. - -Puedes generar rápidamente un CSV de usuarios que se migran en el formato CSV necesario para aplicar asignaciones personalizadas mediante el comando [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data): - -```shell -$ ghe-migrator audit -m user -g MIGRATION_GUID > users.csv -``` - -Ahora, puedes editar ese CSV e ingresar la nueva URL para cada usuario que quieras asignar o renombrar, y luego actualizar la cuarta columna para `asignar` o `renombrar` según corresponda. - -Por ejemplo, para cambiar el nombre del usuario `octocat` a `monalisa` en el `https://example-gh.target` de destino, debes crear una fila con el siguiente contenido: - -| `model_name` | `source_url` | `target_url` | `state` | -| ------------ | ------------------------------------ | ------------------------------------ | -------------------- | -| `usuario` | `https://example-gh.source/octocatc` | `https://example-gh.target/monalisa` | `rename (renombrar)` | - -Se puede usar el mismo proceso para crear asignaciones para cada registro que admita asignaciones personalizadas. Para obtener más información, consulta [nuestra tabla sobre las posibles asignaciones de registro](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type). - -#### Aplicar datos de migración modificados - -1. Después de hacer cambios, usa el comando [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) para aplicar el *conflicts.csv* modificado (o cualquier otro csv de asignación en el formato correcto) a la instancia de destino: - - ```shell - $ scp -P 122 ~/Desktop/conflicts.csv admin@hostname:/home/admin/ - ``` - -2. Vuelve a asignar los datos de migración con el comando `ghe-migrator map`, pasando la ruta al archivo csv modificado y al GUID de migración: - - ```shell - $ ghe-migrator map -i conflicts.csv -g MIGRATION_GUID - ``` - -3. Si el comando `ghe-migrator map -i conflicts.csv -g MIGRATION_GUID` informa que aún existen conflictos, ejecuta nuevamente el proceso de resolución de conflictos de migración. diff --git a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md b/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md deleted file mode 100644 index 574666013c..0000000000 --- a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Tablero de actividades -intro: 'El Tablero de actividades te ofrece un resumen de todas las actividades de {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/articles/activity-dashboard/ - - /enterprise/admin/installation/activity-dashboard - - /enterprise/admin/user-management/activity-dashboard - - /admin/user-management/activity-dashboard -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise ---- -El Tablero de actividades te proporciona gráficos semanales, mensuales y anuales de la cantidad de: -- Solicitudes de extracción nuevas -- Solicitudes de extracción fusionadas -- Problemas nuevos -- Problemas resueltos -- Comentarios de problemas nuevos -- Repositorios nuevos -- Cuentas de usuario nuevas -- Organizaciones nuevas -- Equipos nuevos - -![Tablero de actividades](/assets/images/enterprise/activity/activity-dashboard-yearly.png) - -Para más análisis basados en los datos de {% data variables.product.prodname_enterprise %}, puede comprar {% data variables.product.prodname_insights %}. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_insights %}](/insights/installing-and-configuring-github-insights/about-github-insights)." - -### Acceder al Tablero de actividades - -1. En la parte superior de cualquier página, haz clic en **Explore** (Explorar). ![Explorar la etiqueta](/assets/images/enterprise/settings/ent-new-explore.png) -2. En el margen izquierdo superior, haz clic en **Activity** (Actividad). ![Botón de actividades](/assets/images/enterprise/activity/activity-button.png) diff --git a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md deleted file mode 100644 index 489c7b8c94..0000000000 --- a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Registro de auditoría -intro: '{% data variables.product.prodname_enterprise %} mantiene registros usuarios, organizaciones, repositorios y eventos del sistema auditados. Los registros son útiles para la depuración y el cumplimiento interno y externo.' -redirect_from: - - /enterprise/admin/articles/audit-logging/ - - /enterprise/admin/installation/audit-logging - - /enterprise/admin/user-management/audit-logging - - /admin/user-management/audit-logging -versions: - ghes: '*' - ghae: '*' -topics: - - Auditing - - Enterprise - - Logging - - Security ---- -Para encontrar un listado completo, consulta la sección "[Acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)". Para obtener más información sobre cómo encontrar una acción en particular, consulta la sección "[Buscar la bitácora de auditoría](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)". - -### Subir registros - -Se registra cada operación de inserción de Git. Para obtener más información, consulta "[Ver registros de inserciones](/enterprise/{{ currentVersion }}/admin/guides/installation/viewing-push-logs)." - -### Eventos del sistema - -Todos los eventos del sistema auditados, incluidas las inserciones y las extracciones, se registran en `/var/log/github/audit.log`. Los registros se rotan automáticamente cada 24 horas y se mantienen durante siete días. - -El paquete de soporte incluye registros del sistema. Para obtener más información, consulta "[Proporcionar datos a {% data variables.product.prodname_dotcom %} Asistencia](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support)." - -### Paquete de soporte - -Toda la información de auditoría se registra en el archivo `audit.log` del directorio de `github-logs` de cualquier paquete de soporte. Si está habilitado el redireccionamiento de registro, puedes transmitirle estos datos a un consumidor de flujo syslog externo como [Splunk](http://www.splunk.com/) o [Logstash](http://logstash.net/). Todas las entradas de este registro utilizan la palabra clave `github_audit` y se pueden filtrar con ella. Para obtener más información, consulta "[Redireccionamiento de registro](/enterprise/{{ currentVersion }}/admin/guides/installation/log-forwarding)." - -Por ejemplo, esta entrada muestra que se creó un repositorio nuevo. - -``` -Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"} -``` - -Este ejemplo muestra que las confirmaciones se subieron a un repositorio. - -``` -Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/master" } -``` diff --git a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md deleted file mode 100644 index 04d444baa6..0000000000 --- a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -title: Acciones auditadas -intro: Puedes buscar el registro de auditoría para una gran variedad de acciones. -redirect_from: - - /enterprise/admin/articles/audited-actions/ - - /enterprise/admin/installation/audited-actions - - /enterprise/admin/user-management/audited-actions - - /admin/user-management/audited-actions -versions: - ghes: '*' - ghae: '*' -miniTocMaxHeadingLevel: 3 -topics: - - Auditing - - Enterprise - - Security ---- -#### Autenticación - -| Nombre | Descripción | -| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------ | -| `oauth_access.create` | Un [Token de acceso de OAuth][] fue [generado][generate token] para la cuenta de un usuario. | -| `oauth_access.destroy` | Un [Token de acceso de OAuth][] se eliminó de la cuenta de un usuario. | -| `oauth_application.destroy` | Una [Aplicación de OAuth][] se eliminó de la cuenta de un usuario o de una organización. | -| `oauth_application.reset_secret` | Se restableció una [clave secreta de una aplicación de OAuth][]. | -| `oauth_application.transfer` | Una [aplicación de OAuth][] se transfirió de una cuenta de usuario o de organización a otra. | -| `public_key.create` | Una clave SSH se [agregó][add key] a una cuenta de usuario o una [llave de implementación][] se agregó a un repositorio. | -| `public_key.delete` | Una clave SSH se eliminó de una cuenta de usuario o una [llave de implementación][] se eliminó de un repositorio. | -| `public_key.update` | La clave SSH de una cuenta de usuario o la llave de implementación de un [repositorio][] se actualizó. | -| `two_factor_authentication.enabled` | [Se habilitó la autenticación de dos factores][2fa] para una cuenta de usuario. | -| `two_factor_authentication.disabled` | [Se inhabilitó la autenticación de dos factores][2fa] para una cuenta de usuario. | - -#### Ganchos - -| Nombre | Descripción | -| ---------------------:| --------------------------------------------------- | -| `hook.create` | Se agregó un enlace nuevo a un repositorio. | -| `hook.config_changed` | Se cambió la configuración de un enlace. | -| `hook.destroy` | Se eliminó un enlace. | -| `hook.events_changed` | Se cambiaron los eventos configurados de un enlace. | - -#### Ajustes de configuración de la instancia - -| Nombre | Descripción | -| -------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `business.update_member_repository_creation_permission` | Un administrador del sitio restringe la creación de repositorios en las organizaciones de la instancia. Para obtener más información, consulta "[Restringir la creación de repositorios en tu instancia](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)." | -| `business.clear_members_can_create_repos` | Un administrador del sitio elimina una restricción de creación de repositorios en las organizaciones de la instancia. Para obtener más información, consulta "[Restringir la creación de repositorios en tu instancia](/enterprise/{{ currentVersion }}/admin/guides/user-management/restricting-repository-creation-in-your-instance)." | -| `enterprise.config.lock_anonymous_git_access` | Un administrador del sitio bloquea el acceso de lectura anónimo de Git para evitar que los administradores del repositorio cambien las configuraciones existentes de acceso de lectura anónimo de Git para los repositorios de la instancia. Para obtener más información, consulta "[Evitar que los usuarios cambien el acceso de lectura anónimo de Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)." | -| `enterprise.config.unlock_anonymous_git_access` | Un administrador del sitio desbloquea el acceso de lectura anónimo de Git para permitir que los administradores del repositorio cambien las configuraciones existentes de acceso de lectura anónimo de Git para los repositorios de la instancia. Para obtener más información, consulta "[Evitar que los usuarios cambien el acceso de lectura anónimo de Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)." | - -#### Propuestas y solicitudes de extracción - -| Nombre | Descripción | -| ------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `issue.update` | Cambió el texto del cuerpo de un problema (comentario inicial). | -| `issue_comment.update` | Cambió un comentario sobre un problema (diferente al inicial). | -| `pull_request_review_comment.delete` | Se detectó un comentario en una solicitud de extracción. | -| `issue.destroy` | Se eliminó un problema del repositorio. Para obtener más información, consulta "[Eliminar un problema](/enterprise/{{ currentVersion }}/user/articles/deleting-an-issue)." | - -#### Organizaciones - -| Nombre | Descripción | -| ------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org.async_delete` | Un usuario inició una tarea en segundo plano para eliminar una organización. | -| `org.delete` | Se eliminó una organización con una tarea de segundo plano iniciada por un usuario. | -| `org.transform` | Una cuenta de usuario se convirtió en una organización. Para obtener más información, consulta [Convertir un usuario en una organización](/enterprise/{{ currentVersion}}/user/articles/converting-a-user-into-an-organization/). | - -#### Ramas protegidas - -| Nombre | Descripción | -| ------------------------------------------------------------------:| ------------------------------------------------------------------------------------------------------ | -| `protected_branch.create` | La protección de rama está habilitada para una rama. | -| `protected_branch.destroy` | La protección de rama está inhabilitada para una rama. | -| `protected_branch.update_admin_enforced` | La protección de rama es obligatoria para los administradores de repositorios. | -| `protected_branch.update_require_code_owner_review` | El cumplimiento de la revisión obligatoria del propietario del código está actualizado para una rama. | -| `protected_branch.dismiss_stale_reviews` | El cumplimiento de las solicitudes de extracción en espera descartadas está actualizado para una rama. | -| `protected_branch.update_signature_requirement_enforcement_level` | El cumplimiento de la firma de confirmación obligatoria está actualizado para una rama. | -| `protected_branch.update_pull_request_reviews_enforcement_level` | El cumplimiento de la revisión obligatoria de solicitud de extracción está actualizado para una rama. | -| `protected_branch.update_required_status_checks_enforcement_level` | El cumplimiento de las verificaciones de estado obligatorias está actualizado para una rama. | -| `protected_branch.rejected_ref_update` | Se rechaza el intento de actualización de una rama. | -| `protected_branch.policy_override` | Un administrador de repositorios anula el requisito de protección de una rama. | - -#### Repositorios - -| Nombre | Descripción | -| ------------------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `repo.access` | Un repositorio privado se volvió público, o un repositorio público se volvió privado. | -| `repo.archive` | Se archivó un repositorio. Para obtener más información, consulta [Archivar y dejar de archivar repositorios](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/). | -| `repo.add_member` | Se agregó un colaborador a un repositorio. | -| `repo.config` | Un administrador de sitio bloqueó los empujes forzados. Para obtener más información, consulta [Bloquear los empujes forzados para un repositorio](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) para un repositorio. | -| `repo.create` | Se creó un repositorio. | -| `repo.destroy` | Se eliminó un repositorio. | -| `repo.remove_member` | Se eliminó un colaborador de un repositorio. | -| `repo.rename` | Se renombró un repositorio. | -| `repo.transfer` | Un usuario aceptó una solicitud para recibir un repositorio transferido. | -| `repo.transfer_start` | Un usuario envió una solicitud para transferir un repositorio a otro usuario u organización. | -| `repo.unarchive` | Un repositorio dejó de estar archivado. Para obtener más información, consulta [Archivar y dejar de archivar repositorios](/enterprise/{{ currentVersion }}/admin/guides/user-management/archiving-and-unarchiving-repositories/). | -| `repo.config.disable_anonymous_git_access` | El acceso de lectura anónimo de Git está inhabilitado para un repositorio público. Para obtener más información, consulta "[Habilitar acceso de lectura anónimo de Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)." | -| `repo.config.enable_anonymous_git_access` | El acceso de lectura anónimo de Git está habilitado para un repositorio público. Para obtener más información, consulta "[Habilitar acceso de lectura anónimo de Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)." | -| `repo.config.lock_anonymous_git_access` | La configuración del acceso de lectura anónimo de Git para un repositorio está bloqueada, lo cual evita que los administradores de repositorios cambien (habiliten o deshabiliten) esta configuración. Para obtener más información, consulta "[Evitar que los usuarios cambien el acceso de lectura anónimo de Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)." | -| `repo.config.unlock_anonymous_git_access` | La configuración del acceso de lectura anónimo de Git para un repositorio está desbloqueada, lo cual permite que los administradores del repositorio cambien (habiliten o inhabiliten) esta configuración. Para obtener más información, consulta "[Evitar que los usuarios cambien el acceso de lectura anónimo de Git](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)." | - -#### Herramientas del admin del sitio - -| Nombre | Descripción | -| --------------------:| ------------------------------------------------------------------------------------------------------------------------------- | -| `staff.disable_repo` | Un administrador del sitio inhabilitó el acceso a un repositorio y a todas sus bifurcaciones. | -| `staff.enable_repo` | Un administrador del sitio volvió a habilitar el acceso a un repositorio y a todas sus bifurcaciones. | -| `staff.fake_login` | Un administrador del sitio inició sesión en {% data variables.product.prodname_enterprise %} como otro usuario. | -| `staff.repo_unlock` | Un administrador del sitio desbloqueó (obtuvo acceso total de manera temporaria) uno de los repositorios privados del usuario. | -| `staff.unlock` | Un administrador del sitio desbloqueó (obtuvo acceso total de manera temporaria) todos los repositorios privados de un usuario. | - -#### Equipos - -| Nombre | Descripción | -| --------------:| ------------------------------------------------------------ | -| `team.create` | Se agregó una cuenta de usuario o repositorio a un equipo. | -| `team.delete` | Se eliminó una cuenta de usuario o repositorio de un equipo. | -| `team.destroy` | Se eliminó un equipo. | - -#### Usuarios - -| Nombre | Descripción | -| ---------------------------:| ------------------------------------------------------------------------------------------------------------------------- | -| `user.add_email` | Se agregó una dirección de correo electrónico a una cuenta de usuario. | -| `user.async_delete` | Se inició una tarea sincrónica para destruir una cuenta de usuario, lo que finalmente disparó `user.delete`. | -| `user.change_password` | Un usuario cambió su contraseña. | -| `user.create` | Se creó una cuenta de usuario nueva. | -| `user.delete` | Se destruyó una cuenta de usuario mediante una tarea asincrónica. | -| `user.demote` | Se disminuyó el nivel de un administrador del sitio a cuenta de usuario común. | -| `user.destroy` | Un usuario eliminó su cuenta, lo que disparó `user.async_delete`. | -| `user.failed_login` | Un usuario intentó registrarse con un nombre de usuario, contraseña o código de autenticación de dos factores incorrecto. | -| `user.forgot_password` | Un usuario solicitó un restablecimiento de contraseña a través de la página de inicio de sesión. | -| `user.login` | Un usuario inició sesión. | -| `user.promote` | Se ascendió una cuenta de usuario común a administrador del sitio. | -| `user.remove_email` | Se eliminó una dirección de correo electrónico de una cuenta de usuario. | -| `user.rename` | Se cambió un nombre de usuario. | -| `user.suspend` | Un administrador del sitio suspendió una cuenta de usuario. | -| `user.two_factor_requested` | Se solicitó un código de autenticación de dos factores a un usuario. | -| `user.unsuspend` | Un administrador del sitió dejó de suspender una cuenta de usuario. | - - [add key]: /articles/adding-a-new-ssh-key-to-your-github-account - [llave de implementación]: /guides/managing-deploy-keys/#deploy-keys - [repositorio]: /guides/managing-deploy-keys/#deploy-keys - [generate token]: /articles/creating-an-access-token-for-command-line-use - [Token de acceso de OAuth]: /v3/oauth/ - [Aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app - [clave secreta de una aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app - [aplicación de OAuth]: /guides/basics-of-authentication/#registering-your-app - [2fa]: /articles/about-two-factor-authentication - [2fa]: /articles/about-two-factor-authentication diff --git a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md b/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md deleted file mode 100644 index cbd6b968d9..0000000000 --- a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Monitorear la actividad en tu empresa -redirect_from: - - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance - - /enterprise/admin/user-management/monitoring-activity-in-your-enterprise -versions: - ghes: '*' - ghae: '*' -topics: - - Enterprise -children: - - /activity-dashboard - - /audit-logging - - /searching-the-audit-log - - /audited-actions - - /viewing-push-logs - - /log-forwarding ---- - diff --git a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md b/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md deleted file mode 100644 index 679da25b53..0000000000 --- a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Buscar el registro de auditoría -intro: 'Los administradores del sitio pueden buscar una amplia lista de [acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions) en {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/articles/searching-the-audit-log/ - - /enterprise/admin/installation/searching-the-audit-log - - /enterprise/admin/user-management/searching-the-audit-log - - /admin/user-management/searching-the-audit-log -versions: - ghes: '*' - ghae: '*' -topics: - - Auditing - - Enterprise - - Logging ---- -### Buscar sintaxis de consultas - -Redacta una consulta de búsqueda de uno o más pares de clave-valor separados por operadores lógicos y/o. - -| Clave | Valor | -| ------------------------:| -------------------------------------------------------------------------------------------------------- | -| `actor_id` | ID de la cuenta de usuario que inició la acción | -| `actor (actor)` | Nombre de la cuenta de usuario que inició la acción | -| `oauth_app_id` | ID de la aplicación OAuth asociada con la acción | -| `Acción` | Nombre de la [acción auditada](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions) | -| `user_id` | ID del usuario afectado por la acción | -| `usuario` | Nombre del usuario afectado por la acción | -| `repo_id` | ID del repositorio afectado por la acción (si corresponde) | -| `repo` | Nombre del repositorio afectado por la acción (si corresponde) | -| `actor_ip` | Dirección IP desde donde se inició la acción | -| `created_at (creado en)` | Momento en el cual ocurrió la acción | -| `from` | Vista desde donde se inició la acción | -| `note` | Información variada de evento específico (en texto simple o en formato JSON) | -| `org` | Nombre de la organización afectada por la acción (si corresponde) | -| `org_id` | ID de la organización afectada por la acción (si corresponde) | - -Por ejemplo, para ver todas las acciones que afectaron el repositorio `octocat/Spoon-Knife` desde el inicio de 2017: - - `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]` - -Para ver una lista completa de acciones, consulta "[Acciones auditadas](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)." - -### Buscar el registro de auditoría - -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.business %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.audit-log-tab %} -4. Escribe una consulta de búsqueda. ![Consulta de búsqueda](/assets/images/enterprise/site-admin-settings/search-query.png) diff --git a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md b/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md deleted file mode 100644 index beaa6cb067..0000000000 --- a/translations/es-XL/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Ver registros de subidas -intro: 'Los administradores del sitio pueden ver una lista de operaciones de subida de Git para un repositorio en {% data variables.product.product_location_enterprise %}.' -redirect_from: - - /enterprise/admin/articles/viewing-push-logs/ - - /enterprise/admin/installation/viewing-push-logs - - /enterprise/admin/user-management/viewing-push-logs - - /admin/user-management/viewing-push-logs -versions: - ghes: '*' - ghae: '*' -topics: - - Auditing - - Enterprise - - Git - - Logging ---- -Las entradas de registro de subida muestran: - -- Quién inició la subida -- Si fue un empuje forzado o no -- La rama a la que alguien subió -- El protocolo utilizado para subir -- La dirección IP inicial -- El cliente Git utilizado para subir -- Los hashes SHA de antes y después de la operación - -### Ver registros de subida de un repositorio - -1. Navegar a un repositorio. -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.security-tab %} -4. En la barra lateral izquierda, haz clic en **Push Log (Registro de subida)**. ![Pestaña de registro de subida](/assets/images/enterprise/site-admin-settings/push-log-tab.png) - -### Ver registros de subida de un repositorio en la línea de comando - -1. SSH en tu aparato. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-administrative-shell-ssh/)." -2. En el repositorio Git adecuado, abre el archivo de registro de auditoría: - ```shell - ghe-repo owner/repository -c "less audit_log" - ``` diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md deleted file mode 100644 index 1225297226..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Agregar un repositorio desde tu equipo local a GitHub Desktop -intro: 'Puedes agregar cualquier repositorio Git a {% data variables.product.prodname_desktop %}, incluso si no es un repositorio {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop - - /desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop -versions: - fpt: '*' ---- -{% tip %} - -**Sugerencia:** Puedes agregar un repositorio Git desde tu equipo local hasta GitHub Destktop arrastrando la carpeta a la ventana {% data variables.product.prodname_desktop %}. Si arrastras múltiples carpetas Git a {% data variables.product.prodname_desktop %} al mismo tiempo, cada carpeta se agregará como un repositorio Git individual. - -{% endtip %} - -{% mac %} - -1. En el menú **File** (Archivo), haz clic en **Add Local Repository** (Agregar repositorio local). ![Agrega la opción de menú Local Repository (Repositorio local)](/assets/images/help/desktop/add-local-repository-mac.png) -2. Haz clic en **Choose...** (Elegir...) y, a través de la ventana Finder (Buscador) desplázate hasta el repositorio local que deseas agregar. ![El campo Local Path en la app Mac](/assets/images/help/desktop/add-repo-choose-button-mac.png) -4. Haz clic en **Add Repository** (Agregar repositorio). ![El botón Add repository (Agregar repositorio) en la app Mac](/assets/images/help/desktop/add-repository-button-mac.png) - -{% endmac %} - -{% windows %} - -1. En el menú **File** (Archivo) haz clic en **Add Local Repository** (Agregar repositorio local). ![Agrega la opción de menú Local Repository (Repositorio local)](/assets/images/help/desktop/add-local-repository-windows.png) -2. Haz clic en **Choose...** (Elegir) y, a través de Windows Explorer, desplázate hasta el repositorio local que deseas agregar. ![El campo Local Path (Ruta local) en la app Windows](/assets/images/help/desktop/add-repo-choose-button-win.png) -4. Haz clic en **Add repository** (Agregar repositorio). ![El botón Add repository (Agregar repositorio) en la app Windows](/assets/images/help/desktop/add-repository-button-windows.png) - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md deleted file mode 100644 index f4237a4317..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Agregar un proyecto existente a GitHub usando el GitHub Desktop -intro: 'Puedes agregar un repositorio Git existente a {% data variables.product.prodname_dotcom %} usando {% data variables.product.prodname_desktop %}.' -redirect_from: - - /desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop - - /desktop/contributing-and-collaborating-using-github-desktop/adding-an-existing-project-to-github-using-github-desktop -versions: - fpt: '*' ---- -{% mac %} - -{% data reusables.git.remove-git-remote %} -2. [Agrega el repositorio al GitHub Desktop Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/). -{% data reusables.desktop.publish-repository %} -4. Escribe el nombre deseado del repositorio en el campo **Name** (Name) o usa el nombre de repositorio local actual predeterminado. ![El campo Name (Nombre)](/assets/images/help/desktop/publish-repository-name-mac.png) -5. Para publicar un repositorio público, quita la marca de selección de **Keep this code private**. ![Marca la casilla de verificación privada de este código](/assets/images/help/desktop/publish-repository-private-checkbox-mac.png) -6. Escoge la organización en el **Organization** (Organización) desplegable donde deseas publicar el repositorio, o selecciona **None** (Ninguno) para publicar el repositorio en tu cuenta personal. ![Desplegable de la organización](/assets/images/help/desktop/publish-repository-org-dropdown-mac.png) -7. Haz clic en el botón **Publish Repository** (Publicar repositorio). ![El botón Publish repository (Publicar repositorio) en el cuadro de diálogo Publish Repository (Publicar repositorio)](/assets/images/help/desktop/publish-repository-dialog-button-mac.png) - -{% endmac %} - -{% windows %} - -{% data reusables.git.remove-git-remote %} -2. [Agrega el repositorio al GitHub Desktop Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/). -{% data reusables.desktop.publish-repository %} -4. Escribe el nombre deseado del repositorio en el campo **Name** (Name) o usa el nombre de repositorio local actual predeterminado. ![El campo Name (Nombre)](/assets/images/help/desktop/publish-repository-name-win.png) -5. Para publicar un repositorio público, quita la marca de selección de **Keep this code private**. ![Marca la casilla de verificación privada de este código](/assets/images/help/desktop/publish-repository-private-checkbox-win.png) -6. Escoge la organización en el **Organization** (Organización) desplegable donde deseas publicar el repositorio, o selecciona **None** (Ninguno) para publicar el repositorio en tu cuenta personal. ![Desplegable de la organización](/assets/images/help/desktop/publish-repository-org-dropdown-win.png) -7. Haz clic en el botón **Publish Repository** (Publicar repositorio). ![El botón Publish repository (Publicar repositorio) en el cuadro de diálogo Publish repository (Publicar repositorio)](/assets/images/help/desktop/publish-repository-dialog-button-win.png) - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md deleted file mode 100644 index ce735e7f4a..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Cómo clonar un repositorio desde GitHub hasta GitHub Desktop -intro: 'Puedes usar {% data variables.product.prodname_dotcom %} para clonar repositorios remotos a {% data variables.product.prodname_desktop %}.' -redirect_from: - - /desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop - - /desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop -versions: - fpt: '*' ---- -{% tip %} - -**Sugerencia:** También puede usar {% data variables.product.prodname_desktop %} para clonar repositorios que existen en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Cómo clonar un repositorio desde {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)." - -{% endtip %} - -{% mac %} - -1. Inicia sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_desktop %} antes de comenzar la clonación. -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.open-with-github-desktop %} -5. Haz clic en **Choose...** (Elegir...) y, a través de la ventana Finder (Buscador) desplázate hasta la ruta donde deseas clonar el repositorio. ![El botón Choose (Elegir) en la pestaña URL](/assets/images/help/desktop/clone-choose-button-url-mac.png) - - {% note %} - - **Nota:** Si el repositorio está configurado para usar LFS, se te pedirá que inicies {% data variables.large_files.product_name_short %}. - - {% endnote %} - -5. Haz clic en **Clone**. ![El botón para clonar en la pestaña URL](/assets/images/help/desktop/clone-button-url-mac.png) - -{% endmac %} - -{% windows %} - -1. Inicia sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_desktop %} antes de comenzar la clonación. -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.open-with-github-desktop %} -5. Haz clic en **Choose...** (Elegir...) y, a través de Windows Explorer, desplázate hasta la ruta donde deseas clonar el repositorio. ![El botón Choose (Elegir)](/assets/images/help/desktop/clone-choose-button-url-win.png) - - {% note %} - - **Nota:** Si el repositorio está configurado para usar LFS, se te pedirá que inicies {% data variables.large_files.product_name_short %}. - - {% endnote %} - -5. Haz clic en **Clone**. ![El botón Clone (Clonar)](/assets/images/help/desktop/clone-button-url-win.png) - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md deleted file mode 100644 index b4a6f9f922..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Cómo clonar y bifurcar repositorios desde GitHub Desktop -intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} para clonar y ramificar los repositorios que están en {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /desktop/contributing-to-projects/cloning-a-repository-from-github-desktop - - /desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop - - /desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop -versions: - fpt: '*' ---- -### Clonar repositorios -Los repositorios en {% data variables.product.prodname_dotcom %} son remotos. Puedes clonar repositorios públicos de otros dueños. Puedes clonar tu propio repositorio para crear una copia local en tu computadora y sincronizarla entre las dos ubicaciones. - -También puedes clonar un repositorio directamente desde {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. Para obtener más información, visita "[Cómo clonar un repositorio desde {% data variables.product.prodname_dotcom %} hacia {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". - -{% mac %} - -{% data reusables.desktop.choose-clone-repository %} - ![Clonar opción de menú en la aplicación Mac](/assets/images/help/desktop/clone-file-menu-mac.png) -{% data reusables.desktop.cloning-location-tab %} - ![Pestañas de ubicación en el menú Clone a repository (Clonar un repositorio)](/assets/images/help/desktop/choose-repository-location-mac.png) -{% data reusables.desktop.cloning-repository-list %} -![Clonar una lista de repositorio](/assets/images/help/desktop/clone-a-repository-list-mac.png) -4. Haz clic en **Choose...** (Elegir...) y, a través de la ventana Finder (Buscador) desplázate hasta la ruta donde deseas clonar el repositorio. ![El botón Choose (Elegir)](/assets/images/help/desktop/clone-choose-button-mac.png) -5. Haz clic en **Clone**. ![El botón Clone (Clonar)](/assets/images/help/desktop/clone-button-mac.png) - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.choose-clone-repository %} - ![Opción Clone menu (Clonar menú) en la app de Windows](/assets/images/help/desktop/clone-file-menu-windows.png) -{% data reusables.desktop.cloning-location-tab %} - ![Pestañas de ubicación en el menú Clone a repository (Clonar un repositorio)](/assets/images/help/desktop/choose-repository-location-win.png) -{% data reusables.desktop.cloning-repository-list %} -![Clonar una lista de repositorio](/assets/images/help/desktop/clone-a-repository-list-win.png) -4. Haz clic en **Choose...** (Elegir...) y, a través de Windows Explorer, desplázate hasta la ruta donde deseas clonar el repositorio. ![El botón Choose (Elegir)](/assets/images/help/desktop/clone-choose-button-win.png) -5. Haz clic en **Clone**. ![El botón Clone (Clonar)](/assets/images/help/desktop/clone-button-win.png) - -{% endwindows %} - -### Ramificar repositorios -Puedes utilizar {% data variables.product.prodname_desktop %} para crear una ramificación del repositorio y contribuir con un proyecto en donde no tengas privilegios de escritura. Los cambios en tu ramificación no afectarán al repositorio original. Puedes confirmar los cambios en tu ramificación y generar una solicitud de extracción del repositorio original con los cambios que propones. Para obtener más información, visita "[Acerca de las ramificaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)." - -1. Si clonaste un repositorio en donde no tienes privilegios de escritura, intenta confirmar los cambios, {% data variables.product.prodname_desktop %} enviará una alerta de que "No cuentas con privilegios de escritura para el **REPOSITORIO**". Da clic en **crear una ramificación**. ![Crear un enlace para la ramificación](/assets/images/help/desktop/create-a-fork.png) -3. Da clic en **Ramificar este repositorio**. ![Botón para ramificar este repositorio](/assets/images/help/desktop/fork-this-repo-button.png) -4. Para ver tu ramificación en {% data variables.product.prodname_dotcom %}, da clic en tu foto de perfil en la esquina superior derecha de {% data variables.product.prodname_dotcom %} y posteriormente en **Tus repositorios**. ![Enlace a tus repositorios](/assets/images/help/profile/your-repositories.png) diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/index.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/index.md deleted file mode 100644 index fd1ac82492..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Agregar y clonar repositorios -intro: 'Añadir repositorios existentes desde su equipo local a {% data variables.product.prodname_desktop %}o clonar repositorios desde {% data variables.product.product_name %}.' -redirect_from: - - /desktop/contributing-to-projects/adding-and-cloning-repositories -versions: - fpt: '*' -children: - - /adding-a-repository-from-your-local-computer-to-github-desktop - - /adding-an-existing-project-to-github-using-github-desktop - - /cloning-and-forking-repositories-from-github-desktop - - /cloning-a-repository-from-github-to-github-desktop ---- - diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/index.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/index.md deleted file mode 100644 index f6cc32c589..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Contribuir y colaborar utilizando GitHub Desktop -shortTitle: Contribuir y colaborar -intro: 'Usa GitHub Desktop para administrar tus proyectos, crear confirmaciones significativas y realizar un seguimiento del historial del proyecto en una app en lugar de en la línea de comando.' -redirect_from: - - /desktop/contributing-to-projects -versions: - fpt: '*' -children: - - /adding-and-cloning-repositories - - /making-changes-in-a-branch - - /managing-commits - - /working-with-your-remote-repository-on-github-or-github-enterprise - - /keeping-your-local-repository-in-sync-with-github ---- -### Índice diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/index.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/index.md deleted file mode 100644 index a5c183b998..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/index.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Mantener tu repositorio local sincronizado con GitHub -intro: 'Puedes mantener tu repositorio local sincronizado con tu repositorio remoto mientras actualizas cualquiera de estos. En Git, *remoto* hace referencia al servidor donde se almacena tu código. En tu caso, ese servidor es un repositorio en {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}.' -versions: - fpt: '*' -children: - - /syncing-your-branch ---- - diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch.md deleted file mode 100644 index 5716dfde5d..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Sincronizar tu rama -intro: 'Conforme se suban las confirmaciones a tu proyecto en {% data variables.product.prodname_dotcom %}, podrás mantener una copia local de éste en sincornización si lo extraes del repositorio remoto.' -redirect_from: - - /desktop/contributing-to-projects/syncing-your-branch - - /desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch -versions: - fpt: '*' ---- -### Acerca de la sincronización de ramas - -Puedes sincronizar tu rama local con el repositorio remoto si extraes cualquier confirmación que se haya agregado a la rama en {% data variables.product.product_name %} desde la última vez que lo sincronizaste. Si realizas confirmaciones desde otro dispositivo o si muchas personas colaboran con el proyecto, necesitarás sincronizar tu rama local para mantenerla actualizada. - -Cuando extraes información a tu rama local, únicamente estás actualizando la copia local del repositorio. Para actualziar tu rama en {% data variables.product.prodname_dotcom %}, deberás subir tus cambios. Para obtener más información, consulta la sección "[Subir los cambios a {% data variables.product.prodname_dotcom %}](/desktop/contributing-to-projects/pushing-changes-to-github)". - -Para agregar cambios de una rama en otra, puedes fusionar estas ramas. Para aplicar los cambios a tu rama desde otra rama en el mismo repositorio, puedes fusionar esta otra rama con la tuya en {% data variables.product.prodname_desktop %}. Para solicitar que se fusionen los cambios de tu rama en otra rama que se encuentre en el mismo repositorio o en otro repositorio dentro de la red, puedes crear una solicitud de extracción en {% data variables.product.prodname_desktop %}. Para obtener más información, consulta las secciones "[Fusionar otra rama en tu rama de proyecto](#merging-another-branch-into-your-project-branch)" y " -Acerca de las solicitudes de extracción".

    - -Algunos flujos de trabajo requieren o se benefician con el rebase en vez de con la fusión. Al rebasar podemos reordenar, editar o combinar confirmaciones. Para obtener más información, consulta las secciones "[Acerca del rebase de Git](/articles/about-git-rebase)" y "[rebasar tu rama de proyecto en otra rama](#rebasing-your-project-branch-onto-another-branch)". - - - -### Extraer tu rama local de la rama remota - -1. En {% data variables.product.prodname_desktop %}, utiliza el menú desplegable de {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y selecciona la rama local que quieres actualizar. -2. Para verificar las confirmaciones en la rama remota, da clic en **Obtener origen** ![El botón Fetch origin (Buscar origen)](/assets/images/help/desktop/fetch-button.png) - -3. Para extraer cualquier confirmación de la rama remota, da clic en **Extraer origen** o en **Extraer origen con rebase**. ![El botón Pull origin (Extraer origen)](/assets/images/help/desktop/pull-button.png) - - {% data reusables.desktop.resolve-merge-conflicts %} - - - -### Fusionar otra rama en tu rama de proyecto - -{% data reusables.desktop.current-branch-menu %} - - - -{% data reusables.desktop.choose-a-branch-to-merge %} - - - -{% data reusables.desktop.confirm-merging-branch %} - -{% note %} - -**Nota:** Si hay conflictos de fusión, {% data variables.product.prodname_desktop %} te advertiremos sobre **Merge BRANCH (Fusionar RAMA) en el botón BRANCH** (RAMA). No podrás fusionar las ramas hasta que hayas resuelto todos los conflictos. - -{% endnote %} - -![El botón Merge (Fusionar)](/assets/images/help/desktop/merge-branch-button.png) - -{% data reusables.desktop.push-origin %} - - - -### Rebasar tu rama de proyecto en otra rama - -{% mac %} - -1. En la barra de menú, utiliza el menú desplegable de **Rama** y da clic en **Rebasar la rama actual**. ![Rebase Current Branch (Rebasar rama actual) en el desplegable de rama](/assets/images/help/desktop/mac-rebase-current-branch.png) - -2. Haz clic en la rama que deseas rebasar en la rama actual, luego haz clic en **Start rebase**. ![Botón Start rebase (Iniciar rebase)](/assets/images/help/desktop/start-rebase-button.png) - -3. Si estás seguro de que deseas rebasar, haz clic en **Begin rebase** (Comenzar rebase). ![Botón Begin rebase (Comenzar rebase)](/assets/images/help/desktop/begin-rebase-button.png) - - {% data reusables.desktop.resolve-merge-conflicts %} - -4. Para subir tus cambios locales, da clic en **Subir el origen forzadamente**. ![Origen de empuje forzado](/assets/images/help/desktop/force-push-origin.png) - -{% endmac %} - -{% windows %} - -1. Usa el desplegable ** Branch** y haz clic en **Rebase Current Branch**. ![Rebase Current Branch (Rebasar rama actual) en el desplegable de rama](/assets/images/help/desktop/windows-rebase-current-branch.png) - -2. Haz clic en la rama que deseas rebasar en la rama actual, luego haz clic en **Start rebase**. ![Botón Start rebase (Iniciar rebase)](/assets/images/help/desktop/start-rebase-button.png) - -3. Si estás seguro de que deseas rebasar, haz clic en **Begin rebase** (Comenzar rebase). ![Botón Begin rebase (Comenzar rebase)](/assets/images/help/desktop/begin-rebase-button.png) - - {% data reusables.desktop.resolve-merge-conflicts %} - -4. Para extraer tus cambios locales, haz clic en **Force push origin** (Origen de empuje forzado). ![Origen de empuje forzado](/assets/images/help/desktop/force-push-origin.png) - -{% endwindows %} - - - -### Leer más - -- "[Extraer](/github/getting-started-with-github/github-glossary#pull)" en el glosario de {% data variables.product.prodname_dotcom %} -- "[Fusionar](/github/getting-started-with-github/github-glossary#merge)" en el glosario de {% data variables.product.prodname_dotcom %} -- "[Rebasar](/github/getting-started-with-github/github-glossary#rebase)" en el glosario de {% data variables.product.prodname_dotcom %} diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md deleted file mode 100644 index f8f719a6f8..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Confirmar y revisar cambios en su proyecto -intro: '{% data variables.product.prodname_desktop %} registra todos los cambios a medida que los editas. Puedes decidir cómo agrupar los cambios para crear confirmaciones significativas.' -redirect_from: - - /desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project - - /desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project -versions: - fpt: '*' ---- -### Acerca de las confirmaciones - -{% data reusables.commits.about-commits %} También puedes agregar un coautor en cualquier confirmación en la que colabores. - -{% data reusables.desktop.update-email-address %} Para obtener más información, consulta la sección ["Configurar Git para GitHub Desktop](/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop)". - -### 1. Elegir una rama y realizar cambios - -1. [Crea una rama nueva](/desktop/guides/contributing-to-projects/managing-branches), o selecciona una rama existente dando clic - -{% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** en la barra de herramientas y seleccionando la rama de la lista. - ![Despliega el menú para cambiar tu rama actual](/assets/images/help/desktop/click-branch-in-drop-down.png) -{% data reusables.desktop.make-changes %} - -### 2. Seleccionar cambios para incluirlos en una confirmación - -A medida que realizas cambios en los archivos en tu editor de texto y que los guardas localmente, también verás los cambios en {% data variables.product.prodname_desktop %}. - -* El icono rojo {% octicon "diff-removed" aria-label="The diff removed icon color-red" %} hace referencia a los archivos eliminados. -* El icono amarillo {% octicon "diff-modified" aria-label="The diff modified icon color-yellow" %} hace referencia a los archivos modificados. -* El icono verde {% octicon "diff-added" aria-label="The diff added icon color-green" %} hace referencia a los archivos agregados. -* Para acceder a los cambios acumulados, haz clic en **Stashed Changes** (Cambios acumulados). ![Opción de cambios acumulados](/assets/images/help/desktop/stashed-changes.png) -* {% data reusables.desktop.commit-all-desc %}![Selecciona la casilla de verificación para confirmar todos los archivos cambiados](/assets/images/help/desktop/commit-all.png) -* {% data reusables.desktop.commit-some-desc %}![Selecciona las casillas de verificación junto a los archivos que deseas confirmar](/assets/images/help/desktop/commit-some.png) - -#### Crear una confirmación parcial - -Si un archivo contiene múltiples cambios, pero solo quieres que *algunos* de esos cambios se incluyan en una confirmación, puedes crear una confirmación parcial. El resto de los cambios permanecerán intactos, por lo que puedes realizar confirmaciones y modificaciones adicionales. Esto permite realizar confirmaciones separadas, significativas, como mantener cambios de interrupción de línea en una confirmación separada desde cambios en el código o la prosa. - -Cuando revises la diferencia del archivo, las líneas que se incluirán en la confirmación están resaltadas en azul. Para excluir el cambio, haz clic en la línea cambiada para que desaparezca el azul. - -![Líneas no seleccionadas en un archivo](/assets/images/help/desktop/partial-commit.png) - -#### Descartar cambios - -Puedes descartar todos los cambios no confirmados en un archivo, o rango de archivos, o descartar todos los cambios en todos los archivos desde la última confirmación. - -{% mac %} - -{% data reusables.desktop.select-discard-files %} -{% data reusables.desktop.click-discard-files %} - ![Opción Discard Changes (Descartar cambios) en el menú contextual](/assets/images/help/desktop/discard-changes-mac.png) -{% data reusables.desktop.confirm-discard-files %} - ![Botón Discard Changes (Descartar cambios) en el cuadro de diálogo de confirmación](/assets/images/help/desktop/discard-changes-confirm-mac.png) - -{% tip %} - -**Sugerencia:** Los cambios que descartaste se cargarán en un archivo fechado en la Papelera y puedes recuperarlos hasta que se vacíe la Papelera. - -{% endtip %} - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.select-discard-files %}{% data reusables.desktop.click-discard-files %} - ![Opción Discard Changes (Descartar cambios) en el menú contextual](/assets/images/help/desktop/discard-changes-win.png) -{% data reusables.desktop.confirm-discard-files %} - ![Botón Discard Changes (Descartar cambios) en el cuadro de diálogo de confirmación](/assets/images/help/desktop/discard-changes-confirm-win.png) - -{% tip %} - -**Sugerencia:** Los cambios que descartaste se guardarán en un archivo en la Papelera de reciclaje y puedes recuperarlos hasta que se vacíe. - -{% endtip %} - -{% endwindows %} - -### 3. Escribir un mensaje de confirmación y subir los cambios - -Una vez que estés satisfecho con los cambios que elegiste incluir en tu confirmación, escribe tu mensaje de confirmación y sube los cambios. Si has colaborado en una confirmación, también puedes contribuir en una confirmación de más de un autor. - -{% note %} - -**Nota**: {% data reusables.desktop.tags-push-with-commits %} Para obtener más información, consulta la sección "[Administrar las etiquetas](/desktop/contributing-to-projects/managing-tags)". - -{% endnote %} - -{% data reusables.desktop.commit-message %} - ![Campo para mensaje de confirmación](/assets/images/help/desktop/commit-message.png) -2. De manera opcional, para atribuir una confirmación a otro autor, haz clic en el icono de coautores y escribe el nombre de usuario que deseas incluir. ![Agregar un coautor al mensaje de confirmación](/assets/images/help/desktop/add-co-author-commit.png) -{% data reusables.desktop.commit-button %} - ![Botón Commit (Confirmar)](/assets/images/help/desktop/commit-button.png) -4. Si la rama a la que intentas comprometerte está protegida, Desktop te avisará. - - Para mover tus cambios, haz clic en **switch btanches (cambiar ramas)**. - - Para confirmar tus cambios en la rama protegida, haz clic en **Commit to _BRANCH_****(Enviar a _RAMA)_**. - - Para más información sobre ramas protegidas, ve "[Acerca de ramas protegidas](/github/administering-a-repository/about-protected-branches)". ![Advertencia de rama protegida](/assets/images/help/desktop/protected-branch-warning.png) -{% data reusables.desktop.push-origin %} diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md deleted file mode 100644 index ddc63bd5bf..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Realizar cambios en una rama -intro: 'Usa tu editor de texto favorito, como [Atom](https://atom.io/), para realizar cambios en el proyecto y, a continuación, utiliza {% data variables.product.prodname_desktop %} para visualizar confirmaciones útiles.' -redirect_from: - - /desktop/contributing-to-projects/making-changes-in-a-branch -versions: - fpt: '*' -children: - - /managing-branches - - /committing-and-reviewing-changes-to-your-project - - /stashing-changes - - /viewing-the-branch-history - - /pushing-changes-to-github ---- - diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md deleted file mode 100644 index e9c909b883..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -title: Administrar ramas -intro: Puedes crear una rama nueva desde la rama predeterminada de un repositorio para que puedas experimentar con los cambios de forma segura. -redirect_from: - - /desktop/contributing-to-projects/creating-a-branch-for-your-work - - /desktop/contributing-to-projects/switching-between-branches - - /desktop/contributing-to-projects/managing-branches - - /desktop/contributing-and-collaborating-using-github-desktop/managing-branches -versions: - fpt: '*' ---- -### Acerca de administrar ramas -Puedes utilizar las ramas para experimentar de forma segura con los cambios de tu proyecto. Las ramas aislan tu trabajo de desarrollo de otras ramas en el repositorio. Por ejemplo, puedes utilizar una rama para desarrollar una nueva característica o para corregir un error. - -Siempre puedes crear una rama a partir de otra rama existente. Habitualmente, puedes crear una rama desde la rama predeterminada de tu repositorio. Podrás entonces trabajar en esta rama nueva aislado de los cambios que otras personas hacen al repositorio. - -Una vez que estás satisfecho con to trabajo puedes crear una solicitud de extracción para fusionar tus cambios en la rama actual en alguna otra rama. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" y "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)". - -Siempre podrás crear una rama en {% data variables.product.prodname_desktop %} si tienes acceso de lectura en un repositorio, pero solo podrás cargar la rama a {% data variables.product.prodname_dotcom %} si tienes acceso de escritura en el repositorio en cuestión. - -{% data reusables.desktop.protected-branches %} - -### Cómo crear una rama - -{% tip %} - -**Tip:** La primera rama nueva que creas se basará en la rama predeterminada. Si tienes más de una rama, puedes elegir basar la nueva rama en aquella que has revisado actualmente o en la rama predeterminada. - -{% endtip %} - -{% mac %} - -{% data reusables.desktop.click-base-branch-in-drop-down %} - ![Menú desplegable para cambiar tu rama actual](/assets/images/help/desktop/click-branch-in-drop-down-mac.png) -{% data reusables.desktop.create-new-branch %} - ![Opción New Branch (Rama nueva) en el menú Branch (Rama)](/assets/images/help/desktop/new-branch-button-mac.png) -{% data reusables.desktop.name-branch %} - ![Campo para crear un nombre para la rama nueva](/assets/images/help/desktop/create-branch-name-mac.png) -{% data reusables.desktop.select-base-branch %} - ![Opciones de rama base](/assets/images/help/desktop/create-branch-choose-branch-mac.png) -{% data reusables.desktop.confirm-new-branch-button %} - ![Botón Create Branch (Crear rama)](/assets/images/help/desktop/create-branch-button-mac.png) - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.click-base-branch-in-drop-down %} - ![Menú desplegable para cambiar tu rama actual](/assets/images/help/desktop/click-branch-in-drop-down-win.png) -{% data reusables.desktop.create-new-branch %} - ![Opción New Branch (Rama nueva) en el menú Branch (Rama)](/assets/images/help/desktop/new-branch-button-win.png) -{% data reusables.desktop.name-branch %} - ![Campo para crear un nombre para la rama nueva](/assets/images/help/desktop/create-branch-name-win.png) -{% data reusables.desktop.select-base-branch %} - ![Opciones de rama base](/assets/images/help/desktop/create-branch-choose-branch-win.png) -{% data reusables.desktop.confirm-new-branch-button %} - ![Botón Create Branch (Crear rama)](/assets/images/help/desktop/create-branch-button-win.png) - -{% endwindows %} - -### Publicar una rama - -Si creas una rama en {% data variables.product.product_name %}, necesitarás publicarla para que se muestre disponible para colaboración en {% data variables.product.prodname_dotcom %}. - -1. En la parte superior de la app, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y luego en la rama que quieres publicar. ![Menú desplegable para seleccionar qué rama publicar](/assets/images/help/desktop/click-branch-in-drop-down-mac.png) -2. Da clic en **Publicar rama**. ![El botón de publicar rama](/assets/images/help/desktop/publish-branch-button.png) - -### Alternar entre ramas -Puedes ver y realizar confirmaciones en cualquiera de las ramas de tu repositorio. Si tienes cambios guardados, no confirmados, deberás decidir qué hacer con tus cambios antes de alternar las ramas. Puedes confirmar tus cambios en la rama actual, acumula tus cambios en la rama actual, o lleva los cambios a tu nueva rama. Si quieres confirmar tus cambios en la rama actual, sigue los pasos en [Confirmar y revisar cambios en tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project) antes de alternar entre ramas. - -{% tip %} - -**Consejo**: Puedes configurar un comportamiento predeterminado para alternar entre ramas en la configuración **Avanzada**. Para obtener más información, consulta la sección "[Configurar los ajustes básicos](/desktop/getting-started-with-github-desktop/configuring-basic-settings)". - -{% endtip %} - -{% data reusables.desktop.current-branch-menu %} -{% data reusables.desktop.switching-between-branches %} - ![Lista de ramas en el repositorio](/assets/images/help/desktop/click-branch-in-drop-down-mac.png) -3. Si tienes cambios guardados, sin confirmar, elige **Leave my changes** (Dejar mis cambios) o **Bring my changes** (Traer mis cambios) y luego haz clic en **Switch Branch** (Cambiar rama). ![Alternar ramas con opciones de cambios](/assets/images/help/desktop/stash-changes-options.png) - -### Recuperar cambios acumulados -Para acceder a los cambios que has acumulado en otra rama, vuelve a cambiar a la rama en la que acumulaste los cambios. - -{% data reusables.desktop.current-branch-menu %} -{% data reusables.desktop.switching-between-branches %} - ![Lista de ramas en el repositorio](/assets/images/help/desktop/click-branch-in-drop-down-mac.png) -3. En la barra lateral a la izquierda, haz clic en **Stashed Changes** (Cambios acumulados). ![Opción de cambios acumulados](/assets/images/help/desktop/stashed-changes.png) -4. Para eliminar tus cambios acumulados, haz clic en **Discard **, o bien, para usar tus cambios acumulados, haz clic en **Restore**. ![Descartar o restaurar cambios acumulados](/assets/images/help/desktop/discard-restore-stash-buttons.png) - -### Cómo eliminar una rama - -No puedes borrar una rama que esté actualmente asociada con una solicitud de extracción abierta. No puedes revertir el haber borrado una rama. - -{% mac %} - -{% data reusables.desktop.select-branch-to-delete %} - ![Menú desplegable para seleccionar qué rama borrar](/assets/images/help/desktop/select-branch-to-delete.png) -{% data reusables.desktop.delete-branch-mac %} - ![Opción de "borrar..." en el menú de la rama](/assets/images/help/desktop/delete-branch-mac.png) - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.select-branch-to-delete %} - ![Menú desplegable para seleccionar qué rama borrar](/assets/images/help/desktop/select-branch-to-delete.png) -{% data reusables.desktop.delete-branch-win %} - ![Opción de "borrar..." en el menú de la rama](/assets/images/help/desktop/delete-branch-win.png) - -{% endwindows %} - -### Leer más - -- [Clonar un repositorio de {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop) -- "[Rama](/articles/github-glossary/#branch)" en el glosario {% data variables.product.prodname_dotcom %} -- "[Acerca de las ramas](/articles/about-branches)" -- "[Ramas en resumen](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" en la documentación de Git diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github.md deleted file mode 100644 index 48fb79b1e3..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Cargar cambios en GitHub -shortTitle: Cargar cambios -intro: 'De manera que confirmes cambios localmente en tu proyecto, puedes cargarlos a {% data variables.product.prodname_dotcom %} para que otros puedan acceder a ellos desde el repositorio remoto.' -permissions: People with write permissions can push changes to a repository. -redirect_from: - - /desktop/contributing-to-projects/pushing-changes-to-github - - /desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github -versions: - fpt: '*' ---- -### Acerca de cargar cambios a {% data variables.product.prodname_dotcom %} - -Cuando cargas cambios, envías los cambios confirmados en tu repositorio local al repositorio remoto en {% data variables.product.prodname_dotcom %}. Si cambias tu proyecto localmente y quieres que otros tengan acceso a los cambios, deberás cargar los cambios a {% data variables.product.prodname_dotcom %}. - -Antes de cargar los cambios, debes actualizar tu rama local para que incluya cualquier confirmación que se haya agregado al repositorio remoto. Si alguien hizo confirmaciones en la rama remota, las cuales no están en tu rama local, {% data variables.product.prodname_desktop %} te solicitará conseguir las confirmaciones nuevas antes de cargar tus cambios para evitar conflictos de fusión. Para obtener más información, consulta la sección "[Sincronizar tu rama](/desktop/contributing-to-projects/syncing-your-branch)". - -{% data reusables.desktop.protected-branches %} - -### Cargar cambios a {% data variables.product.prodname_dotcom %} - -{% note %} - -**Nota:** {% data variables.product.prodname_desktop %} rechazará una carga si excede ciertos límites. - -- Una subida contiene un archivo grande de más de {% data variables.large_files.max_github_size %}. -- Una subida es de más de {% data variables.large_files.max_file_size %} en total. - -Si configuras a {% data variables.large_files.product_name_long %} para rastrear tus archivos grandes, puedes subir aquellos que normalmente se rechazarían. Para obtener más información, consulta la sección "[Acerca de {% data variables.large_files.product_name_long %} y {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)". - -{% endnote %} - -{% data reusables.desktop.push-origin %} -2. Si {% data variables.product.prodname_desktop %} te pide traer las confirmaciones nuevas de la rama remota, da clic en **Recuperar**. ![El botón de recuperar](/assets/images/help/desktop/fetch-newer-commits.png) -3. Opcionalmente, da clic en **Crear Solicitud de Extracción** para abrir una solicitud de extracción y colaborar en tus cambios. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" ![El botón de crear solicitud de extracción](/assets/images/help/desktop/create-pull-request.png) - -### Leer más -- "[Cargar](/github/getting-started-with-github/github-glossary/#push)" en el glosario de {% data variables.product.prodname_dotcom %} -- "[Confirmar y revisar los cambios hechos a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)" diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history.md deleted file mode 100644 index c882fc3730..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Visualizar el historial de ramas -intro: 'Puedes ver los detalles de cualquier confirmación en {% data variables.product.prodname_desktop %}, incluyendo una diferencia de los cambios introducidos por la confirmación.' -redirect_from: - - /desktop/contributing-to-projects/viewing-the-branch-history - - /desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history -versions: - fpt: '*' ---- -Cada confirmación muestra: - - - El mensaje de confirmación - - La hora en que se creó la confirmación - - El nombre de usuario y la foto de perfil (si está disponible) de la persona que confirma el cambio - - El hash SHA-1 de la confirmación (el ID exclusivo) - -{% data reusables.desktop.history-tab %} -2. En la pestaña **History** (Historial), haz clic en la confirmación que deseas revisar. ![Una confirmación en la pestaña History (Historial)](/assets/images/help/desktop/branch-history-commit.png) -3. Si existen múltiples archivos en la confirmación, haz clic en un archivo individual para ver los cambios que se realizan a ese archivo en esa confirmación. ![Un archivo en la confirmación](/assets/images/help/desktop/branch-history-file.png) - -### Leer más - -- [Sincronizar tu rama](/desktop/guides/contributing-to-projects/syncing-your-branch/)" diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit.md deleted file mode 100644 index 4556ac8412..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Amending a commit -intro: 'You can use {% data variables.product.prodname_desktop %} to amend your last commit.' -versions: - fpt: '*' ---- - -## About amending a commit - -Amending a commit is a way to modify the most recent commit you have made in your current branch. This can be helpful if you need to edit the commit message or if you forgot to include changes in the commit. - -You can continue to amend a commit until you push it to the remote repository. After you push a commit, the option to amend it is disabled in {% data variables.product.prodname_desktop %}. When you amend a commit, you replace the previous commit with a new commit to your current branch. Amending a commit that has been pushed to the remote repository could cause confusion for other collaborators working with the repository. - -## Amending a commit - -{% data reusables.desktop.history-tab %} -2. Right-click on the most recent commit and select **Amend commit**. - ![Amend commit context menu](/assets/images/help/desktop/amend-commit-context-menu.png) -3. Click the **Summary** field to modify the commit message. Optionally, you can modify or add information about the commit in the **Description** field. -4. Select any uncommitted changes that you would like to add to the commit. For more information about selecting changes, see "[Committing and reviewing changes to your project](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project#selecting-changes-to-include-in-a-commit)." -5. Once you have finalized your changes, click **Amend last commit**. - ![Amend last commit overview](/assets/images/help/desktop/amend-last-commit-overview.png) diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit.md deleted file mode 100644 index fb10d4c9cd..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Cherry-picking a commit -intro: You can pick a specific commit on one branch and copy the commit to another branch. -versions: - fpt: '*' -redirect_from: - - /desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit ---- -## About Git cherry-pick - -You can cherry-pick a commit on one branch to create a copy of the commit with the same changes on another branch. If you commit changes to the wrong branch or want to make the same changes to another branch, you can cherry-pick the commit to apply the changes to another branch. You can also use cherry-picking to apply specific changes before you are ready to create or merge a pull request. For example, if you commit a bug fix to a feature branch, you can cherry-pick the commit with the bug fix to other branches of your project. - -You can also use cherry-picking when collaborating with a team. Some projects incorporate contributions by cherry-picking commits. For more information, see [Distributed Git - Maintaining a Project](https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#_rebase_cherry_pick) in the Git documentation. - -## Cherry-picking a commit - -{% data reusables.desktop.current-branch-menu %} -2. In the list of branches, click the branch that has the commit that you want to cherry-pick. -{% data reusables.desktop.history-tab %} -4. Drag the commit that you want to cherry-pick to the {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** menu and drop the commit on the branch that you want to copy the commit to. - ![Dragging a commit to another branch in the Current Branch menu](/assets/images/help/desktop/cherry-picking.png) - -## Further reading -- [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/index.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/index.md deleted file mode 100644 index b9158d0f62..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Managing commits -intro: 'You can use {% data variables.product.prodname_desktop %} to amend, cherry-pick, reorder, revert, and squash commits.' -versions: - fpt: '*' -children: - - /reverting-a-commit - - /cherry-picking-a-commit - - /reordering-commits - - /squashing-commits - - /amending-a-commit - - /managing-tags ---- - diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags.md deleted file mode 100644 index 6dda5ebe6e..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Administrar etiquetas -intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} para crear, cargar y visualizar etiquetas.' -redirect_from: - - /desktop/contributing-to-projects/managing-tags - - /desktop/contributing-and-collaborating-using-github-desktop/managing-tags -versions: - fpt: '*' ---- -### Acerca de las etiquetas en {% data variables.product.prodname_desktop %} - -{% data variables.product.prodname_desktop %} te permite crear etiquetas anotadas. Puedes utilizar una etiqueta para marcar un punto individual en el historial de tu repositorio, incluyendo un número de versión para un lanzamiento. Para obtener más información acerca de las etiquetas de lanzamiento, consulta la sección "[Acerca de los lanzamientos](/github/administering-a-repository/about-releases)". - -{% data reusables.desktop.tags-push-with-commits %} - -### Crear una etiqueta - -{% data reusables.desktop.history-tab %} -{% data reusables.desktop.create-tag %} -{% data reusables.desktop.name-tag %} -{% data reusables.desktop.confirm-tag %} - -### Visualizar etiquetas - -{% data reusables.desktop.history-tab %} -2. Da clic en la confirmación. - {% note %} - - **Nota**: {% data variables.product.prodname_desktop %} muestra una flecha {% octicon "arrow-up" aria-label="The up arrow icon" %} si la etiqueta no se ha subido al repositorio remoto. - - {% endnote %} - - ![Visualizar una etiqueta en el historial](/assets/images/help/desktop/viewing-tags-in-history.png) - -3. Todas las etiquetas asociadas con la confirmación se pueden ver en los metadatos de dicha confirmación. ![Visualizar una etiqueta en la confirmación](/assets/images/help/desktop/viewing-tags-in-commit.png) diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reordering-commits.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reordering-commits.md deleted file mode 100644 index d26a0b7c7f..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reordering-commits.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Reordering commits -intro: 'You can use {% data variables.product.prodname_desktop %} to reorder commits in your branch''s history.' -versions: - fpt: '*' ---- - -## About reordering a commit - -Reordering allows you to alter your commit history to provide a more meaningful progression of commits. {% data variables.product.prodname_desktop %} allows you to drag-and-drop commits in your branch's history to reorder them. - -## Reordering a commit - -{% data reusables.desktop.current-branch-menu %} -2. In the list of branches, click the branch with the commits that you want to reorder. -{% data reusables.desktop.history-tab %} -4. Drag the commit that you want to reorder and drop it between two adjoining commits. - ![reorder drag and drop](/assets/images/help/desktop/reorder-drag-and-drop.png) -While the application reorders the commits, a **Reorder in process** dialog indicates the progress of the change. - -## Error messages when reordering commits - -When you reorder commits, you may see one of the following notifications or error messages. - -* A notification states that the requested change to the branch will require a force push to update the remote branch. This is shown when the commits that you reordered were previously pushed to the remote branch. Force pushing alters the commit history of the branch and will affect other collaborators who are working in that branch. Select **Begin reorder** to start the reorder, and then click **Force push origin** to push your changes. - - ![reorder force push dialog](/assets/images/help/desktop/reorder-force-push-dialog.png) - -* An error states that the reorder failed because there is a merge commit among the reordered commits. - - ![reorder merge commit dialog](/assets/images/help/desktop/reorder-merge-commit-dialog.png) - -* A notification is shown indicating that there are uncommitted changes present on your current branch. Select **Stash Changes and Continue** to store the changes and proceed, or select **Close** to dismiss the message and commit the changes. When there are no longer any uncommitted changes, you can reorder your commits. - - ![reorder stash dialog](/assets/images/help/desktop/reorder-stash-dialog.png) - -* A message states that there are merge conflicts that you must resolve before the application can continue reordering commits on your branch. - 1. Click **View conflicts** to see the conflicts. - {% data reusables.desktop.resolve-merge-conflicts %} - - ![reorder resolve conflicts message](/assets/images/help/desktop/reorder-resolve-conflicts.png) diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit.md deleted file mode 100644 index 3d0cd1649e..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Revertir una confirmación -intro: Puedes revertir una confirmación específica para eliminar los cambios de tu rama. -redirect_from: - - /desktop/contributing-to-projects/reverting-a-commit - - /desktop/contributing-and-collaborating-using-github-desktop/reverting-a-commit -versions: - fpt: '*' ---- -Cuando reviertes la confirmación anterior, la reversión también es una confirmación. La confirmación original también permanece en el historial del repositorio. - -{% tip %} - -**Sugerencia:** Cuando reviertes múltiples confirmaciones, es mejor revertirlas desde la más nueva hasta la más antigua. Si reviertes confirmaciones en un orden diferente, es posible que se produzcan conflictos de fusión. - -{% endtip %} - -{% mac %} - -{% data reusables.desktop.history-tab %} -{% data reusables.desktop.revert-commit %} - ![La opción Revert (Revertir) sobre la vista diferente](/assets/images/help/desktop/commit-revert-mac.png) - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.history-tab %} -{% data reusables.desktop.revert-commit %} - ![La opción Revert (Revertir) sobre la vista diferente](/assets/images/help/desktop/commit-revert-win.png) - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md deleted file mode 100644 index caf9cb8989..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Squashing commits -intro: 'You can use {% data variables.product.prodname_desktop %} to squash commits in your branch''s history.' -versions: - fpt: '*' ---- - -## About squashing a commit - -Squashing allows you to combine multiple commits in your branch's history into a single commit. This can help keep your repository's history more readable and understandable. - -## Squashing a commit - -{% mac %} - -{% data reusables.desktop.current-branch-menu %} -2. In the list of branches, select the branch that has the commits that you want to squash. -{% data reusables.desktop.history-tab %} -4. Select the commits to squash and drop them on the commit you want to combine them with. You can select one commit or select multiple commits using ⌘ or Shift. - ![squash drag and drop](/assets/images/help/desktop/squash-drag-and-drop.png) -5. Modify the commit message of your new commit. The commit messages of the selected commits you want to squash are pre-filled into the **Summary** and **Description** fields. -6. Click **Squash Commmits**. - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.current-branch-menu %} -2. In the list of branches, select the branch that has the commits that you want to squash. -{% data reusables.desktop.history-tab %} -4. Select the commits to squash and drop them on the commit you want to combine them with. You can select one commit or select multiple commits using Ctrl or Shift. - ![squash drag and drop](/assets/images/help/desktop/squash-drag-and-drop.png) -5. Modify the commit message of your new commit. The commit messages of the selected commits you want to squash are pre-filled into the **Summary** and **Description** fields. -6. Click **Squash Commmits**. - -{% endwindows %} - -## Error messages when squashing commits - -When you squash commits, you may see one of the following notifications or error messages. - -* A notification states that the requested change to the branch will require a force push to update the remote branch. Force pushing alters the commit history of the branch and will affect other collaborators who are working in that branch. Select **Begin Squash** to start the squash, and then click **Force push origin** to push your changes. - - ![squash force push dialog](/assets/images/help/desktop/squash-force-push.png) - -* An error states that the squash failed because there is a merge commit among the squashed commits. - - ![reorder merge commit dialog](/assets/images/help/desktop/squash-merge-commit-dialog.png) - -* A notification is shown indicating that there are uncommitted changes present on your current branch. Select **Stash Changes and Continue** to store the changes and proceed, or select **Close** to dismiss the message and commit the changes. When there are no longer any uncommitted changes you can squash your commits. - - ![squash stash dialog](/assets/images/help/desktop/squash-stash-dialog.png) diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop.md deleted file mode 100644 index c9337c2d1c..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Cambiar una URL remota desde el GitHub Desktop -intro: 'Puedes cambiar la URL remota para un repositorio en el que estés trabajando {% data variables.product.prodname_desktop %}. Es posible que puedas hacerlo si se ha cambiado el nombre, o si el nombre de usuario o la organización que posee el repositorio ha cambiado.' -redirect_from: - - /desktop/contributing-to-projects/changing-a-remotes-url-from-github-desktop - - /desktop/contributing-to-projects/changing-a-remote-s-url-from-github-desktop - - /desktop/contributing-and-collaborating-using-github-desktop/changing-a-remotes-url-from-github-desktop -versions: - fpt: '*' ---- -{% mac %} - -1. En el menú **Repository** (Repositorio) haz clic en **Repository Settings...** (Configuración del repositorio...). ![Opciones del menú Repository Settings (Configuración del repositorio)](/assets/images/help/desktop/repository-settings-mac.png) -2. En el campo **Primary remote repository** (Repositorio remoto principal) escribe la URL que desees. ![Campo Primary remote repository (Repositorio remoto principal)](/assets/images/help/desktop/repository-settings-remote-mac.png) -3. Haz clic en **Save (Guardar)**. ![El botón Save (Guardar)](/assets/images/help/desktop/repository-settings-save-mac.png) - -{% endmac %} - -{% windows %} - -1. En el menú **Repository** (Repositorio), haz clic en **Repository settings...** (Configuración del repositorio...). ![Opciones del menú Repository Settings (Configuración del repositorio)](/assets/images/help/desktop/repository-settings-win.png) -2. En el campo **Primary remote repository** (Repositorio remoto principal) escribe la URL que desees. ![Campo Primary remote repository (Repositorio remoto principal)](/assets/images/help/desktop/repository-settings-remote-win.png) -3. Haz clic en **Save (Guardar)**. ![El botón Save (Guardar)](/assets/images/help/desktop/repository-settings-save-win.png) - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md deleted file mode 100644 index 08bbf940cb..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Crear un nuevo informe de problemas o solicitud de extracción -intro: Puedes crear una propuesta o solicitud de extracción para proponer y colaborar en los cambios en un repositorio. -permissions: 'Anyone can create an issue in a public repository that has issues enabled. Anyone with read permissions to a repository can create a pull request, but you must have write permissions to create a branch.' -redirect_from: - - /desktop/contributing-to-projects/creating-an-issue-or-pull-request - - /desktop/contributing-to-projects/creating-a-pull-request - - /desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request -versions: - fpt: '*' ---- -### Acerca de los informes de problemas y solicitudes de extracción - -Puedes utilizar los informes de problemas para rastrear ideas, errores, tareas, y otros tipos de información que sean importantes para tu proyecto. Puedes crear un informe de problemas en el repositorio de tu proyecto con {% data variables.product.prodname_desktop %}. Para obtener más información acerca de los informes de problemas, consulta la sección "[Acerca de los informes de problemas](/github/managing-your-work-on-github/about-issues)". - -Después de que crees una rama y hagas cambios a los archivos en un proyecto, puedes crear una solicitud de extracción. Con una solicitud de extracción, puedes proponer, debatir e iterar entre los cambios antes de fusionarlos en el proyecto. Puedes crear una solicitud de extracción en el repositorio de tu proyecto con {% data variables.product.prodname_desktop %}. Para obtener más información acerca de las solicitudes de extracción, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". - -### Prerrequisitos - -Amtes de crear una solicitud de extracción, necesitarás subir los cambios a una rama en {% data variables.product.prodname_dotcom %}. -- Guardar y confirmar cualquier cambio en tu rama local. Para obtener más información, consulta la sección "[Confirmar y revisar cambios hechos a tu proyecto](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project)". -- Cambiar tus confirmaciones locales en el repositorio remoto. Para obtener más información, consulta la sección"[Subir cambios a GitHub](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github)". -- Publicar tu rama actual en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar ramas](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches)". - -### Crear una propuesta - -{% mac %} - -1. En la barra de menú, utiliza el menú desplegable de **Repositorio** y luego da clic en **Crear informe de problemas en {% data variables.product.prodname_dotcom %}**. ![Valor del repositorio en el menú de la rama](/assets/images/help/desktop/create-issue-mac.png) -2. En {% data variables.product.prodname_dotcom %}, da clic en **Empezar** para abrir una plantilla de informe de problemas o da clic en **Abrir un informe de problemas en blanco**. ![Opciones para crear nuevo informe de problemas](/assets/images/help/desktop/create-new-issue.png) - -{% endmac %} - -{% windows %} - -1. En la barra de menú, utiliza el menú desplegable de **Repositorio** y luego da clic en **Crear usuario en {% data variables.product.prodname_dotcom %}**. ![El valor del repositorio en el menú de la rama](/assets/images/help/desktop/create-issue-windows.png) -2. En {% data variables.product.prodname_dotcom %}, da clic en **Empezar** para abrir una plantilla de informe de problemas o da clic en **Abrir un informe de problemas en blanco**. ![Opciones para crear nuevo informe de problemas](/assets/images/help/desktop/create-new-issue.png) - -{% endwindows %} - -{% note %} - -**Nota**: Si no están habilitadas las plantillas de informe de problemas en tu repositorio actual, {% data variables.product.prodname_desktop %}te direccionará a un informe de problemas en blanco en {% data variables.product.prodname_dotcom %}. - -{% endnote %} - -### Agregar una solicitud de extracción - -{% mac %} - -1. Cambia a la rama para la cual quieras crear una solicitud de extracción. Para obtener más información, consulta la sección "[Cambiar entre ramas](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)". -2. Haz clic en **Create Pull Request** (Crear solicitud de extracción). {% data variables.product.prodname_desktop %} abrirá tu buscador predeterminado para llevarte a {% data variables.product.prodname_dotcom %}. ![El botón de crear solicitud de extracción](/assets/images/help/desktop/mac-create-pull-request.png) -4. En {% data variables.product.prodname_dotcom %}, confirma que la rama en el menú desplegable de **base:** se aquella en donde quieres fusionar tus cambios. Confirma que la rama en el menú desplegable de **comparar:** es la rama de tema en donde realizaste tus cambios. ![Menús desplegables para elegir la base y comparar ramas](/assets/images/help/desktop/base-and-compare-branches.png) -{% data reusables.repositories.pr-title-description %} -{% data reusables.repositories.create-pull-request %} - -{% endmac %} - -{% windows %} - -1. Cambia a la rama para la cual quieras crear una solicitud de extracción. Para obtener más información, consulta la sección "[Cambiar entre ramas](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches)". -2. Haz clic en **Create Pull Request** (Crear solicitud de extracción). {% data variables.product.prodname_desktop %} abrirá tu buscador predeterminado para llevarte a {% data variables.product.prodname_dotcom %}. ![El botón de crear solicitud de extracción](/assets/images/help/desktop/windows-create-pull-request.png) -3. En {% data variables.product.prodname_dotcom %}, confirma que la rama en el menú desplegable de **base:** se aquella en donde quieres fusionar tus cambios. Confirma que la rama en el menú desplegable de **comparar:** es la rama de tema en donde realizaste tus cambios. ![Menús desplegables para elegir la base y comparar ramas](/assets/images/help/desktop/base-and-compare-branches.png) -{% data reusables.repositories.pr-title-description %} -{% data reusables.repositories.create-pull-request %} - -{% endwindows %} - -### Leer más -- "[Informe de problemas](/github/getting-started-with-github/github-glossary#issue)" en el glosario de {% data variables.product.prodname_dotcom %} -- "[Solicitud de extracción](/github/getting-started-with-github/github-glossary#pull-request)" en el glosario de {% data variables.product.prodname_dotcom %} -- "[Rama base](/github/getting-started-with-github/github-glossary#base-branch)" en el glosario de {% data variables.product.prodname_dotcom %} -- "[Rama de tema](/github/getting-started-with-github/github-glossary#topic-branch)" en el glosario de {% data variables.product.prodname_dotcom %} diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md deleted file mode 100644 index 93bc093e2d..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Trabajar con tu repositorio remoto en GitHub o GitHub Enterprise -intro: 'A medida que realizas cambios a tu proyecto localmente, puedes mantenerlos actualizados con tu repositorio remoto. En Git, *remoto* hace referencia al servidor donde se almacena tu código. En tu caso, ese servidor es un repositorio en {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}.' -redirect_from: - - /desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise -versions: - fpt: '*' -children: - - /creating-an-issue-or-pull-request - - /viewing-a-pull-request-in-github-desktop - - /changing-a-remotes-url-from-github-desktop ---- - diff --git a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md deleted file mode 100644 index c6eec8dd6e..0000000000 --- a/translations/es-XL/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Visualizar una solicitud de extracción en GitHub Desktop -shortTitle: Visualizar una solicitud de extracción -intro: 'Puedes ver los cambios propuestos en las solicitudes de extracción abiertas en {% data variables.product.prodname_desktop %}.' -redirect_from: - - /desktop/contributing-to-projects/accessing-a-pull-request-locally - - /desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally - - /desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop -versions: - fpt: '*' ---- -### Acerca de las solicitudes de extracción en {% data variables.product.prodname_desktop %} -Puedes ver las solicitudes de extracción que tú o tus colaboradores hayan propuesto en {% data variables.product.prodname_desktop %}. Las solicitude de extracción te permiten proponer cambios a los proyectos, proporcionar retroalimentación y revisiones, y fusionar cambios en los proyectos. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." - -Cuando visualizas una solicitud de extracción en {% data variables.product.prodname_desktop %}, puedes ver un historial de confirmaciones que han hecho los colaboradores. También puedes ver qué archivos modificaron, agregaron o borraron estas confirmaciones. Desde {% data variables.product.prodname_desktop %}, puedes abrir los repositorios en tu editor de texto preferido para ver cualquier cambio o para hacer cambios adicionales. Después de recibir los cambios en una solicitud de extracción, puedes dar retroalimentación en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)". - -### Visualizar una solicitud de extracción en {% data variables.product.prodname_desktop %} -{% data reusables.desktop.current-branch-menu %} -{% data reusables.desktop.click-pull-requests %} - ![Pestaña Pull Requests en el menú desplegable de la rama actual](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) -{% data reusables.desktop.choose-pr-from-list %} - ![Lista de las solicitudes de extracción abiertas en el repositorio](/assets/images/help/desktop/click-pull-request.png) -4. Opcionalmente, para actualizar la lista de solicitudes de extracción, haz clic en {% octicon "sync" aria-label="The sync icon" %}. ![Botón Sync (Sincronizar) para actualizar](/assets/images/help/desktop/pull-request-list-sync.png) - -### Abrir una solicitud de extracción en {% data variables.product.prodname_desktop %} desde {% data variables.product.prodname_dotcom %} -{% data reusables.repositories.sidebar-pr %} -2. En la lista de solicitudes de extracción, da clic en la solicitud de extracción que te gustaría abrir en {% data variables.product.prodname_desktop %}. -3. A la derecha del título de la solicitud de extracción, da clic en el menú desplegable de **Abrir con** y después da clic en el botón de **Abrir en Desktop**. ![El botón de Abrir en Desktop](/assets/images/help/desktop/open-pr-in-desktop-button.png) diff --git a/translations/es-XL/content/desktop/index.md b/translations/es-XL/content/desktop/index.md deleted file mode 100644 index 624ceb5370..0000000000 --- a/translations/es-XL/content/desktop/index.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Documentación del Escritorio de GitHub -shortTitle: GitHub Desktop -intro: Guías paso a paso para configurar y usar GitHub Desktop a fin de administrar tu trabajo de proyecto. -versions: - fpt: '*' -children: - - /installing-and-configuring-github-desktop - - /contributing-and-collaborating-using-github-desktop ---- - diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md deleted file mode 100644 index f134c4aa4d..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Acerca de GitHub Desktop y del Almacenamiento de Archivos Grandes de Git -shortTitle: Acerca de Git LFS -intro: '{% data variables.product.prodname_desktop %} incluye a {% data variables.large_files.product_name_long %} para administrar los archivos grandes.' -redirect_from: - - /desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop - - /desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop -versions: - fpt: '*' ---- -Cuando instalas {% data variables.product.prodname_desktop %}, también se instala {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). {% data variables.large_files.product_name_short %} te permite subir archivos a {% data variables.product.prodname_dotcom %} que excedan el límite normal de {% data variables.large_files.max_github_size %}. Para obtener más información acerca de las {% data variables.large_files.product_name_short %}, consulta la sección "[Acerca del {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage)". - -Para utilizar {% data variables.large_files.product_name_short %} con {% data variables.product.prodname_desktop %}, debes configurar a {% data variables.large_files.product_name_short %} utilizando la línea de comandos. Para obtener más información, consulta la sección "[Configurar las {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage)". - -Después de que configuras a {% data variables.large_files.product_name_short %} para rastrear los archivos en un repositorio, puedes acceder sin problema y administrar archivos grandes con {% data variables.product.prodname_desktop %} como lo harías con cualquier otro archivo en el repositorio. - -### Leer más -- "[Trabajar con archivos grandes](/github/managing-large-files/working-with-large-files)" -- "[Control de versiones de archivos grandes](/github/managing-large-files/versioning-large-files)" diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md deleted file mode 100644 index e2b1843499..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Configurar un editor predeterminado -intro: Puedes configurar GitHub Desktop para abrir archivos en tu proyecto con tu editor de texto o ambiente de desarrollo integrado (IDE) preferidos. -redirect_from: - - /desktop/getting-started-with-github-desktop/configuring-a-default-editor - - /desktop/installing-and-configuring-github-desktop/configuring-a-default-editor -versions: - fpt: '*' ---- -### Editores compatibles - -{% data variables.product.prodname_desktop %} es compatible con los siguientes editores. - -{% mac %} - -- [Atom](https://atom.io/) -- [MacVim](https://macvim-dev.github.io/macvim/) -- [Visual Studio Code](https://code.visualstudio.com/) -- [Visual Studio Codium](https://vscodium.com/) -- [Sublime Text](https://www.sublimetext.com/) -- [BBEdit](http://www.barebones.com/products/bbedit/) -- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/) -- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/) -- [JetBrains Rider](https://www.jetbrains.com/rider/) -- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/) -- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/) -- [JetBrains IntelliJ IDEA](https://www.jetbrains.com/idea/) -- [JetBrains GoLand](https://www.jetbrains.com/go/) -- [TextMate](https://macromates.com/) -- [Brackets](http://brackets.io/) - - Para utilizar Brackets con {% data variables.product.prodname_desktop %}, debes instalar el atajo de la línea de comandos. Para instalar el atajo, abre Brackets, da clic en **Archivo** en la barra de menú y luego da clic en **Instalar Atajo para la Línea de Comandos**. -- [Typora](https://typora.io/) -- [CodeRunner](https://coderunnerapp.com/) -- [SlickEdit](https://www.slickedit.com/) -- [Xcode](https://developer.apple.com/xcode/) -- [Android Studio](https://developer.android.com/studio) - -{% endmac %} - -{% windows %} - -- [Atom](https://atom.io/) -- [Visual Studio Code](https://code.visualstudio.com/) -- [Visual Studio Codium](https://vscodium.com/) -- [Sublime Text](https://www.sublimetext.com/) -- [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) -- [Typora](https://typora.io/) -- [SlickEdit](https://www.slickedit.com/) -- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/) -- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/) -- [JetBrains Rider](https://www.jetbrains.com/rider/) -- [Notepad++](https://notepad-plus-plus.org/) - -{% endwindows %} - -### Configurar un editor predeterminado - -{% mac %} - -{% data reusables.desktop.mac-select-desktop-menu %} -3. En la ventana de preferencias, selecciona **Integrations** (integraciones). ![El panel de Integraciones en la ventana de Preferencias](/assets/images/help/desktop/mac-select-integrations-pane.png) -4. Utiliza el menú desplegable de "Editor Externo" y elige el editor que quieras configurar como predeterminado. ![El menú External editor (Editor externo) en la barra del menú Preferences (Preferencias)](/assets/images/help/desktop/mac-editor-menu.png) -5. Haz clic en **Save (Guardar)**. - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.windows-choose-options %} -3. En la ventana de Opciones, seleccione **Integrations** (integraciones). ![El panel de Integraciones en la ventana de Opciones](/assets/images/help/desktop/windows-select-integrations-pane.png) -4. Utiliza el menú desplegable de "Editor Externo" y elige el editor que quieras configurar como predeterminado. ![El menú External editor (Editor externo) en la barra del menú Options (Opciones)](/assets/images/help/desktop/windows-editor-menu.png) -5. Haz clic en **Save (Guardar)**. - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings.md deleted file mode 100644 index 5d8838f2a5..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Configurar parámetros básicos -intro: 'Puedes acceder a la configuración para proteger tu privacidad, conectar cuentas a GitHub Desktop, y configurar Git.' -redirect_from: - - /desktop/getting-started-with-github-desktop/configuring-basic-settings - - /desktop/installing-and-configuring-github-desktop/configuring-basic-settings -versions: - fpt: '*' ---- -{% mac %} - -{% data reusables.desktop.mac-select-desktop-menu %} -3. Para ver o cambiar tu configuración, alterna entre estos paneles:![La navegación por el menú Preferences (Preferencias)](/assets/images/help/desktop/mac-select-accounts-pane.png) -{% data reusables.desktop.preferences-options-tabs %} - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.windows-choose-options %} -2. Para ver o cambiar tu configuración, alterna entre estos paneles:![La navegación por el menú Options (Opciones)](/assets/images/help/desktop/windows-select-accounts-pane.png) -{% data reusables.desktop.preferences-options-tabs %} - -{% endwindows %} - -### Leer más - -- "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/guides/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md deleted file mode 100644 index 470dddd827..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Configurar Git para GitHub Desktop -shortTitle: Configurar Git -intro: 'Si todavía no tienes Git instalado, debes configurarlo antes de usar GitHub Desktop.' -redirect_from: - - /desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop - - /desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop -versions: - fpt: '*' ---- -{% data variables.product.prodname_desktop %} utiliza la dirección de correo electrónico que configuraste en tus ajustes locales de Git para conectar las confirmaciones con tu cuenta en {% data variables.product.product_name %}. - -{% data reusables.desktop.update-email-address %} - -{% tip %} - -**Tip**: Cualquiera podrá ver la dirección de correo electrónico en tu configuración de Git si haces confirmaciones públicas. Para obtener más información, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)." - -{% endtip %} - -{% mac %} - -{% data reusables.desktop.sign-in-choose-product %} -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -{% data reusables.desktop.copy-email-git-config %} -{% data reusables.desktop.return-to-desktop %} -{% data reusables.desktop.mac-select-desktop-menu %} -7. En la ventana de preferencias, da clic en **Git**. ![El panel de Git en el menú Preferences (Preferencias)](/assets/images/help/desktop/mac-select-git-pane.png) -{% data reusables.desktop.name-field-git-config %} - ![El campo con el nombre de la configuración de Git](/assets/images/help/desktop/mac-name-git-config.png) -{% data reusables.desktop.paste-email-git-config %} - ![La dirección de correo electrónico copiada en el campo de configuración de Git](/assets/images/help/desktop/mac-email-git-config.png) -{% data reusables.desktop.click-save-git-config %} - ![Botón de guardar en el campo de configuración de Git](/assets/images/help/desktop/mac-save-git-config.png) - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.sign-in-choose-product %} -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -{% data reusables.desktop.copy-email-git-config %} -{% data reusables.desktop.return-to-desktop %} -{% data reusables.desktop.windows-choose-options %} -8. En la ventana de Opciones, da clic en **Git**. ![El panel de Git en el menú Options (Opciones)](/assets/images/help/desktop/windows-select-git-pane.png) -{% data reusables.desktop.name-field-git-config %} - ![El campo con el nombre de la configuración de Git](/assets/images/help/desktop/windows-name-git-config.png) -{% data reusables.desktop.paste-email-git-config %} - ![La dirección de correo electrónico copiada en el campo de configuración de Git](/assets/images/help/desktop/windows-email-git-config.png) -{% data reusables.desktop.click-save-git-config %} - ![Botón de guardar en el campo de configuración de Git](/assets/images/help/desktop/windows-save-git-config.png) - -{% endwindows %} - -### Leer más - -- [Agregar una dirección de correo electrónico a tu cuenta de GitHub](/articles/adding-an-email-address-to-your-github-account/)" -- "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)." diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/index.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/index.md deleted file mode 100644 index 7d1454cd31..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Configurar y personalizar GitHub Desktop -intro: 'Cómo configurar Git, conectar tu editor predeterminado y personalizar las opciones para alinear GitHub Desktop con tu flujo de trabajo.' -redirect_from: - - /desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop -versions: - fpt: '*' -children: - - /configuring-git-for-github-desktop - - /configuring-basic-settings - - /configuring-a-default-editor - - /setting-a-theme-for-github-desktop - - /about-git-large-file-storage-and-github-desktop ---- - diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop.md deleted file mode 100644 index f703ef5f88..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Establecer un tema para GitHub Desktop -intro: Puedes establecer un tema para personalizar el aspecto de GitHub Desktop. -redirect_from: - - /desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop - - /desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop -versions: - fpt: '*' ---- -{% mac %} - -{% data reusables.desktop.mac-select-desktop-menu %} -{% data reusables.desktop.choose-a-theme %} - ![Las opciones de temas para la pestaña de Apariencia para Mac](/assets/images/help/desktop/mac-appearance-tab-themes.png) - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.windows-choose-options %} -{% data reusables.desktop.choose-a-theme %} - ![Las opciones de temas para la pestaña de Apariencia para Windows](/assets/images/help/desktop/windows-appearance-tab-themes.png) - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/index.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/index.md deleted file mode 100644 index 4cab699743..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Instalar y configurar GitHub Desktop -shortTitle: Instalar y configurar -intro: 'Configura a {% data variables.product.prodname_desktop %} para que administre el trabajo de tu proyecto. Autentícate en {% data variables.product.prodname_dotcom_the_website %} o en {% data variables.product.prodname_enterprise %}, mantén la app actualizada y revisa tu configuración preferida.' -redirect_from: - - /desktop/getting-started-with-github-desktop -versions: - fpt: '*' -children: - - /overview - - /installing-and-authenticating-to-github-desktop - - /configuring-and-customizing-github-desktop ---- -### Índice diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md deleted file mode 100644 index 1ce4762ce7..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Acerca de las conexiones a GitHub -intro: '{% data variables.product.prodname_desktop %} utiliza HTTPS para intercambiar datos de forma segura con {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /desktop/getting-started-with-github-desktop/about-connections-to-github - - /desktop/installing-and-configuring-github-desktop/about-connections-to-github -versions: - fpt: '*' ---- -{% data variables.product.prodname_desktop %} se conecta a {% data variables.product.prodname_dotcom %} cuando extraes, subes, clonas y bifurcas repositorios remotos. Para conectarse a {% data variables.product.prodname_dotcom %} desde {% data variables.product.prodname_desktop %}, debes autenticar tu cuenta. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." - -Después de que te autentiques en {% data variables.product.prodname_dotcom %}, puedes conectarte a los repositorios remotos con {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} guarda tus credenciales en caché (nombre de usuario y contraseña o token de acceso personal) y las utiliza para autenticarse en cada conexión hacia el destino remoto. - -{% data variables.product.prodname_desktop %} se conecta con {% data variables.product.prodname_dotcom %} utilizando HTTPS. Si utilizas {% data variables.product.prodname_desktop %} para acceder a los repositorios que se clonaron utilizando SSH, podrías encontrar errores. Para conectarte a un repositorio que se clonó utilizando SSH, cambia las URL del destino remoto. Para obtener más información, consulta "[Changing a remote's URL](/github/using-git/changing-a-remotes-url) (Cambiar la URL de un remoto). - -### Leer más -- "[Clonar y bifurcar repositorios desde GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)" diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md deleted file mode 100644 index 20c25d05c2..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md +++ /dev/null @@ -1,182 +0,0 @@ ---- -title: Autenticar a GitHub -shortTitle: Autenticación -intro: 'Puedes acceder de forma segura a los recursos de tu cuenta en {% data variables.product.prodname_desktop %} si te autenticas con {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /desktop/getting-started-with-github-desktop/authenticating-to-github-using-the-browser - - /desktop/getting-started-with-github-desktop/authenticating-to-github - - /desktop/installing-and-configuring-github-desktop/authenticating-to-github -versions: - fpt: '*' ---- -### Acerca de la autenticación - -Para mantener la seguridad de tu cuenta, debes autenticarte antes de que puedas utilizar {% data variables.product.prodname_desktop %} para acceder a los recursos en {% data variables.product.prodname_dotcom %}. - -Antes de realizar la autenticación, {% data reusables.desktop.get-an-account %} - -{% mac %} - -### Autenticar una cuenta en {% data variables.product.prodname_dotcom %} - -{% data reusables.desktop.mac-select-desktop-menu %} -{% data reusables.desktop.mac-select-accounts %} -3. A la derecha de "{% data variables.product.prodname_dotcom_the_website %}", da clic en **Iniciar sesión**. ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-github.png) -4. En el recuadro de "Iniciar sesión", da clic en **Iniciar sesión utilizando tu buscador**. {% data variables.product.prodname_desktop %} abrirá tu buscador predeterminado. ![Inicio de sesión mediante el enlace de su navegador](/assets/images/help/desktop/mac-sign-in-browser.png) - - {% data reusables.user_settings.password-authentication-deprecation-desktop %} - -{% data reusables.desktop.authenticate-in-browser %} -{% data reusables.desktop.2fa-in-browser %} -7. Después de que {% data variables.product.prodname_dotcom %} autentique tu cuenta, sigue las indicaciones para regresar a {% data variables.product.prodname_desktop %}. - -### Autenticar una cuenta en {% data variables.product.prodname_enterprise %} - -{% data reusables.user_settings.password-authentication-deprecation-desktop %} - -{% data reusables.desktop.mac-select-desktop-menu %} -{% data reusables.desktop.mac-select-accounts %} -{% data reusables.desktop.choose-product-authenticate %} -4. Para agregar una cuenta de {% data variables.product.prodname_enterprise %}, teclea tus credenciales bajo el campo "Dirección de Enterprise Server", y luego da clic en **Continuar**. ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-button-enterprise.png) -{% data reusables.desktop.retrieve-2fa %} - -{% endmac %} - -{% windows %} - -### Autenticar una cuenta en {% data variables.product.prodname_dotcom %} - -{% data reusables.desktop.windows-choose-options %} -{% data reusables.desktop.windows-select-accounts %} -3. A la derecha de "GitHub.com", da clic en **Iniciar sesión**. ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-github.png) -4. En el panel de inicio de sesión, haz clic en **Sign in using your browser** (Iniciar sesión usando el navegador). ![Inicio de sesión mediante el enlace de su navegador](/assets/images/help/desktop/windows-sign-in-browser.png) - - {% data reusables.user_settings.password-authentication-deprecation-desktop %} - -{% data reusables.desktop.authenticate-in-browser %} -{% data reusables.desktop.2fa-in-browser %} -7. Después de que {% data variables.product.prodname_dotcom %} autentique tu cuenta, sigue las indicaciones para regresar a {% data variables.product.prodname_desktop %}. - -### Autenticar una cuenta en {% data variables.product.prodname_enterprise %} - - -{% data reusables.user_settings.password-authentication-deprecation-desktop %} - -{% data reusables.desktop.windows-choose-options %} -{% data reusables.desktop.windows-select-accounts %} -{% data reusables.desktop.choose-product-authenticate %} -4. Para agregar una cuenta de {% data variables.product.prodname_enterprise %}, teclea tus credenciales bajo el campo "Dirección de Enterprise Server", y luego da clic en **Continuar**. ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-button-enterprise.png) -{% data reusables.desktop.retrieve-2fa %} - -{% endwindows %} - -### Solucionar problemas de autenticación - -Si {% data variables.product.prodname_desktop %} encuentra un error de autenticación, puedes utilizar los mensajes de error para solucionar los problemas. - -Si te encuentras con un error de autenticación, primero intenta salir y entrar nuevamente a tu cuenta en {% data variables.product.prodname_desktop %}. - -En el caso de algunos errores, {% data variables.product.prodname_desktop %} te solicitará que indiques el mensaje de error. Si no se te solicita esto, o si quieres encontrar información adicional sobre cualquier error, consulta los archivos de bitácora de {% data variables.product.prodname_desktop %} siguiendo estos pasos. - -{% mac %} - -1. Utiliza el menú desplegable de **Ayuda** y da clic en **Mostrar bitácoras en el buscador**. ![El botón de Mostrar Bitácoras en el Buscador](/assets/images/help/desktop/mac-show-logs.png) -2. Selecciona el archivo de bitácora desde la fecha en donde encontraste el error de autenticación. - -{% endmac %} - -{% windows %} - -1. Utiliza el menú desplegable de **Ayuda** y da clic en **Mostrar las bitácoras en el explorador**. ![El botón de Mostrar Bitácoras en el Buscador](/assets/images/help/desktop/windows-show-logs.png) -2. Selecciona el archivo de bitácora desde la fecha en donde encontraste el error de autenticación. - -{% endwindows %} - -Revisa la información de solución de problemas que se muestra a continuación dependiendo del error con el que te hayas encontrado. - -#### Credenciales incorrectas - -```shell -Error: Bad credentials -``` - -Este error significa que hay un problema con las credenciales almacenadas de tu cuenta. - -Para solucionar este problema, sal de tu cuenta en {% data variables.product.prodname_desktop %} y vuelve a firmarte. - -#### Token vacío - -```shell -info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - (empty token) -``` - -Este error significa que {% data variables.product.prodname_desktop %} no puede encontrar el token de acceso que creó en la cadena de llaves del sistema. - -Para solucionar este problema, sal de tu cuenta en {% data variables.product.prodname_desktop %} y vuelve a firmarte. - -#### No se encuentra el repositorio - -```shell -fatal: repository 'https://github.com//.git' not found - -(The error was parsed as 8: The repository does not seem to exist anymore. You may not have access, or it may have been deleted or renamed.) -``` - -Este error significa que no tienes permiso para acceder al repositorio que estás intentando clonar. - -Para solucionar los problemas, contacta a la persona que administre los permisos en tu organización. - -#### No se pudo leer del repositorio remoto - -```shell -git@github.com: Permission denied (publickey). -fatal: Could not read from remote repository. - -Please make sure you have the correct access rights and the repository exists. -``` - -Este error significa que no tienes una llave SSH válida configurada. - -Para solucionarlo, consulta la sección "[Generar una llave SSH nueva y agregarla al agente de SSH](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". - -#### No se pudo clonar - -```shell -fatal: clone of 'git@github.com:/' into submodule path '' failed -Failed to clone 'src/github.com//'. Retry scheduled -Cloning into ''... -git@github.com: Permission denied (publickey). -fatal: Could not read from remote repository. -Please make sure you have the correct access rights -and the repository exists. -``` - -Este error significa ya sea que el repositorio que intentas clonar tiene submódulos a los cuales no tienes acceso o que no tienes una llave SSH válida configurada. - -Si no tienes acceso a los submódulos, soluciona este problema contactando a la persona que administre los permisos para este repositorio. - -Si no tienes una llave SSH válida configurada, consulta la sección "[Generar una llave SSH nueva y agregarla al agente de SSH](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". - -{% windows %} - -#### No se pudo leer la respuesta de AskPass - -```shell -error: unable to read askpass response from '/Users//GitHub Desktop.app/Contents/Resources/app/static/ask-pass-trampoline.sh' -fatal: could not read Username for 'https://github.com': terminal prompts disabled -``` - -Este error se puede presentar a causa de varios eventos. - -Si se modifican las entradas del registro de `Command Processor`, {% data variables.product.prodname_desktop %} responderá con un error de `Authentication failed`. Para verificar si estas entradas de registro se modifcaron, sigue estos pasos. - -1. Abre el editor de registro (`regedit.exe`) y navega hasta las siguientes ubicaciones. `` HKEY_CURRENT_USER\Software\Microsoft\Command Processor\` ``HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\` -2. Revisa para ver si hay un valor de `Autorun` en cualquiera de las ubicaciones. -3. Si hay un valor de `Autorun`, bórralo. - -Si tu nombre de usuario de Windows tiene caracteres extendidos de Unicode, esto podría causar un error de respuesta de AskPass. Para solucionar los problemas, crea una cuenta nueva de usuario de Windows y migra tus archivos a dicha cuenta. Para obtener más información, consulta la sección "[Crear una cuenta de usuario en Windows](https://support.microsoft.com/en-us/help/13951/windows-create-user-account)" en la documentación de Microsoft. - -{% endwindows %} - -### Leer más -- "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/index.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/index.md deleted file mode 100644 index 05ca21dd8f..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Cómo instalar y autenticarse en GitHub Desktop -intro: Instalar GitHub Desktop y conectar tus cuentas de GitHub y GitHub Enterprise. -redirect_from: - - /desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop -versions: - fpt: '*' -children: - - /setting-up-github-desktop - - /installing-github-desktop - - /authenticating-to-github - - /about-connections-to-github - - /updating-github-desktop - - /uninstalling-github-desktop ---- - diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md deleted file mode 100644 index b681c6b229..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Instalar GitHub Desktop -shortTitle: Instalación -intro: Puedes instalar GitHub Desktop en sistemas operativos Windows o macOS compatibles. -redirect_from: - - /desktop/getting-started-with-github-desktop/installing-github-desktop - - /desktop/installing-and-configuring-github-desktop/installing-github-desktop -versions: - fpt: '*' ---- -### Acerca de la instalación de {% data variables.product.prodname_desktop %} - -Puedes instalar {% data variables.product.prodname_desktop %} en los sistemas operativos compatibles. Si tienes una cuenta en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, puedes conectarla a {% data variables.product.prodname_desktop %}. Para obtener más información acerca de cómo crear una cuenta, consulta la sección "[Registrar una cuenta de {% data variables.product.prodname_dotcom %} nueva](/articles/signing-up-for-a-new-github-account/)" o contacta a tu administrador de stio de {% data variables.product.prodname_enterprise %}. - -{% windows %} - -Si eres un administrador de red, puedes desplegar {% data variables.product.prodname_desktop %} en las computadoras con Windows en una red que se administre con Active Directory si utilizas el archivo de paquete de instalador para Windows (`.msi`) con la Política de grupo o con otro sistema de instalación remoto. - -El paquete de instalación de Windows extrae el instalador independiente (`.exe`) y configura a Windows para instalar {% data variables.product.prodname_desktop %} en la siguiente ocasión que el usuario ingrese a su estación de trabajo. Los usuarios deben tener permisos para instalar {% data variables.product.prodname_desktop %} en su directorio de usuario. - -Si un usuario ejecuta el paquete de instalación en Windows de {% data variables.product.prodname_desktop %} directamente, para completar la instalación, el usuario debe salir de su sesión en su estación de trabajo y volverse a firmar. - -{% endwindows %} - -### Descargar e instalar {% data variables.product.prodname_desktop %} - -{% mac %} - -Puedes instalar {% data variables.product.prodname_desktop %} en {% data variables.desktop.mac-osx-versions %}. - -{% data reusables.desktop.download-desktop-page %} -2. Da clic en **Descargar para macOS**. ![El botón de Descargar para MacOS](/assets/images/help/desktop/download-for-mac.png) -3. En la carpeta `Download` (Descargas) de tu computadora, haz doble clic en el archivo comprimido **{% data variables.product.prodname_desktop %}**. ![El archivo de GitHubDesktop.zip](/assets/images/help/desktop/mac-zipfile.png) -4. Una vez que se descomprima el archivo, haz doble clic en **{% data variables.product.prodname_desktop %}**. -5. {% data variables.product.prodname_desktop %} se lanzará después de que se complete la instalación. - -{% endmac %} - -{% windows %} - -Puedes instalar {% data variables.product.prodname_desktop %} en {% data variables.desktop.windows-versions %}. - -{% warning %} - -**Advertencia**: Debes tener un sistema operativo de 64 bits para ejecutar {% data variables.product.prodname_desktop %}. - -{% endwarning %} - -{% data reusables.desktop.download-desktop-page %} -2. Da clic en **Descargar para Windows**. ![El botón de Descargar para Windows](/assets/images/help/desktop/download-for-windows.png) -3. En la carpeta `Download` de tu computadora, da doble clic en el archivo de configuración de **{% data variables.product.prodname_desktop %}**. ![El archivo de GitHubDesktopSetup](/assets/images/help/desktop/windows-githubdesktopsetup.png) -4. {% data variables.product.prodname_desktop %} se lanzará después de que se complete la instalación. - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md deleted file mode 100644 index a78a022d4b..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Configurar GitHub Desktop -shortTitle: Configuración -intro: 'Puedes configurar a {% data variables.product.prodname_desktop %} para que se ajuste a tus necesidades y así contribuir con proyectos.' -redirect_from: - - /desktop/getting-started-with-github-desktop/setting-up-github-desktop - - /desktop/installing-and-configuring-github-desktop/setting-up-github-desktop -versions: - fpt: '*' ---- -### Parte 1: Instalar {% data variables.product.prodname_desktop %} - -Puedes instalar {% data variables.product.prodname_desktop %} o cualquier sistema operativo compatible. Para obtener más información, consulta la sección "[Sistemas Operativos Compatibles](/desktop/getting-started-with-github-desktop/supported-operating-systems)". - -Para instalar {% data variables.product.prodname_desktop %}, navega a [https://desktop.github.com/](https://desktop.github.com/) y descarga la versión adecuada de {% data variables.product.prodname_desktop %} para tu sistema operativo. Sigue las instrucciones para completar la instalación. Para obtener más información, consulta la sección "[Instalar {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-github-desktop)". - -### Parte 2: Configurar tu cuenta - -Si tienes una cuenta en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, puedes utilizar {% data variables.product.prodname_desktop %} para intercambiar datos entre tus repositorios locales y remotos. - -#### Crear una cuenta -Si no tienes una cuenta de {% data variables.product.prodname_dotcom %} aún, consulta la sección "[Registrarte para obtener una cuenta nueva de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account/)". - -Si eres parte de una organización que utiliza {% data variables.product.prodname_enterprise %} y no tienes una cuenta, contacta a tu administrador de sitio de {% data variables.product.prodname_enterprise %}. - -#### Autenticarse en {% data variables.product.prodname_dotcom %} -Para conectase a {% data variables.product.prodname_desktop %} con {% data variables.product.prodname_dotcom %}, necesitarás autenticar tu cuenta. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." - -Después de autenticar tu cuenta, estarás listo para contribuir con y administrar proyectos con {% data variables.product.prodname_desktop %}. - -### Parte 3: Configurar Git -Debes tener instalado Git antes de utilizar {% data variables.product.prodname_desktop %}. Si aún no tienes Git instalado, puedes descargar e instalar la última versión de Git desde [https://git-scm.com/downloads](https://git-scm.com/downloads). - -Después de que instales Git, necesitarás configurarlo para {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar a Git para {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop)". - -### Parte 4: Personalizar {% data variables.product.prodname_desktop %} -Puedes ajustar las características predeterminadas y las configuraciones para ajustar a {% data variables.product.prodname_desktop %} según tus necesidades. - -#### Elegir un editor de texto predeterminado -Puedes abrir un editor de texto desde {% data variables.product.prodname_desktop %} para manipular los archivos y repositorios. {% data variables.product.prodname_desktop %} es compatible con varios editores de textos y ambientes de desarrollo integrados (IDE) para Windows y macOS. Puedes elegir un editor predeterminado en la configuración de {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar un editor predeterminado](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)". - -#### Elegir un tema -{% data variables.product.prodname_desktop %} cuenta con varios temas disponibles para personalizar el aspecto y el estilo de la app. Puedes elegir un tema en la configuración de {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)". diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop.md deleted file mode 100644 index 8df0dd7bce..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Desinstalar GitHub Desktop -intro: Puedes desinstalar GitHub Desktop de tu computadora en cualquier momento. -redirect_from: - - /desktop/getting-started-with-github-desktop/uninstalling-github-desktop - - /desktop/installing-and-configuring-github-desktop/uninstalling-github-desktop -versions: - fpt: '*' ---- -{% mac %} - -1. En una ventana de búsqueda, desplázate hasta la carpeta de Aplicaciones. ![Carpeta de aplicaciones en la ventana del Buscador](/assets/images/help/desktop/applications-folder.png) -2. Mientras presionas el botón de **Control** en tu teclado, da clic en **{% data variables.product.prodname_desktop %}**. -3. Elige **Move to Trash** (Mover a Papelera). ![La opción de mover a la papelera](/assets/images/help/desktop/mac-move-to-trash.png) -4. En la barra de menú, utiliza el menú desplegable de **Buscador** y luego da clic en **Vaciar la papelera**. ![La opción de vaciar la papelera en la barra de menú](/assets/images/help/desktop/mac-empty-trash-menu.png) -5. Lee la advertencia en el cuadro emergente y haz clic en **Empty Trash** (Vaciar Papelera). ![El botón de vaciar la papelera](/assets/images/help/desktop/mac-empty-trash-button.png) - -{% endmac %} - -{% windows %} - -1. Aber el panel de control. Para obtener más información, consulta la sección [¿Dónde está el Panel de Control?](https://support.microsoft.com/en-us/help/13764/windows-where-is-control-panel) en la ayuda de Windows. -2. Debajo de "Programas", da clic en **Desinstalar un programa**. ![La opción de desinstalar programa en el panel de control](/assets/images/help/desktop/windows-uninstall-a-program.png) -3. Da clic derecho en la entrada que se llama **{% data variables.product.prodname_desktop %}**, y luego da clic en **Desinstalar**. ![La opción de desinstalar](/assets/images/help/desktop/windows-click-uninstall.png) - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop.md deleted file mode 100644 index bb27bbce99..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Actualizar GitHub Desktop -intro: GitHub Desktop automáticamente descarga las actualizaciones y las instala al reiniciar. También puedes verificar las actualizaciones manualmente. -redirect_from: - - /desktop/getting-started-with-github-desktop/updating-github-desktop - - /desktop/installing-and-configuring-github-desktop/updating-github-desktop -versions: - fpt: '*' ---- -{% mac %} - -1. En el menú **GitHub Desktop**, haz clic en **Acerca de GitHub Desktop**. ![Acerca de la opción de menú de GitHub Desktop](/assets/images/help/desktop/desktop-menu-about-desktop-mac.png) -2. Haz clic en **Check for Updates** (Comprobar actualizaciones). ![Botón Check for Updates (Comprobar actualizaciones)](/assets/images/help/desktop/check-for-updates.png) -3. Si hay una actualización disponible, cierre y vuelva a abrir {% data variables.product.prodname_desktop %} para instalar la actualización. - -{% endmac %} - -{% windows %} - -1. En el menú **Help** (Ayuda), haz clic en **Acerca de GitHub Desktop**. ![Acerca de la opción de menú de GitHub Desktop](/assets/images/help/desktop/help-about-desktop-win.png) -2. Haz clic en **Check for Updates** (Comprobar actualizaciones). ![Botón Check for Updates (Comprobar actualizaciones)](/assets/images/help/desktop/check-for-updates.png) -3. Si hay una actualización disponible, cierre y vuelva a abrir {% data variables.product.prodname_desktop %} para instalar la actualización. - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md deleted file mode 100644 index d81996a35e..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: Crear el primer repositorio mediante GitHub Desktop -shortTitle: Crear tu primer repositorio -intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} para crear y administrar un repositorio de Git sin utilizar la línea de comandos.' -redirect_from: - - /desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop - - /desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop -versions: - fpt: '*' ---- -### Introducción -{% 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. Al final de esta guía, habrás utilizado {% data variables.product.prodname_desktop %} para crear un repositorio, hacer cambios en éste y publicarlos en {% data variables.product.product_name %}. - -Después de instalar {% data variables.product.prodname_desktop %} y de iniciar sesión en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, deberás crear y clonar un repositorio de tutorial. El tutorial te presentará lo básico de trabajar con Git y con {% data variables.product.prodname_dotcom %}, incluyendo el instalar un editor de texto, crear una rama, hacer una confirmación, cargarla a {% data variables.product.prodname_dotcom_the_website %} y abrir una solicitud de extracción. El tutorial está disponible si aún no tienes ningún repositorio en {% data variables.product.prodname_desktop %}. - -Te recomendamos completar el tutorial, pero si quieres explorar {% data variables.product.prodname_desktop %} creando un nuevo repositorio, esta guía te describirá cómo utilizar {% data variables.product.prodname_desktop %} para trabajar en un repositorio de Git. - -### Parte 1: Instalar {% data variables.product.prodname_desktop %} y autenticar tu cuenta -Puedes instalar {% data variables.product.prodname_desktop %} o cualquier sistema operativo compatible. Después de instalar la app, necesitarás iniciar sesión y autenticarte en tu cuenta de {% data variables.product.prodname_dotcom %} o de {% data variables.product.prodname_enterprise %} antes de que puedas crear y clonar un repositorio de tutorial. - -Para obtener más información sobre la instalación y autenticación, consulta la sección "[Configurar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop)". - -### Parte 2: Crear un repositorio nuevo -Si no tienes ningún repositorio asociado con {% data variables.product.prodname_desktop %}, tendrás una vista de "Let's get started!", en donde podrás elegir crear y clonar un repositorio de tutorial, clonar un repositorio existente desde internet, crear un repositorio nuevo, o agregar un repositorio existente desde tu disco duro. ![¡Comencemos! screen](/assets/images/help/desktop/lets-get-started.png) - -#### Crear y clonar un repositorio de tutorial -Te recomendamos que tu primer poyecto sea crear y clonar un repositorio de tutorial para practicar cómo utilizar {% data variables.product.prodname_desktop %}. - -1. Haz clic en **Create a tutorial repository and clone it** (Crear un repositorio de tutorial y clonarlo). ![Crear y clonar un botón de repositorio de tutorial](/assets/images/help/desktop/getting-started-guide/create-and-clone-a-tutorial-repository.png) -2. Sigue las instrucciones en el tutorial para instalar un editor de texto, crear una rama, editar un archivo, hacer una confirmación, publicar en {% data variables.product.prodname_dotcom %} y abrir una solicitud de extracción. - -#### Crear un repositorio nuevo -Si no quieres crear y clonar un repositorio de tutorial, puedes crear un repositorio nuevo. - -1. Haz clic en **Crear un nuevo repositorio en tu disco duro...** ![Crear un repositorio nuevo](/assets/images/help/desktop/getting-started-guide/creating-a-repository.png) -2. Llena los campos y selecciona tus opciones preferidas. ![Crear un repositorio de opciones](/assets/images/help/desktop/getting-started-guide/create-a-new-repository-options.png) - - "Name" (Nombre) define el nombre de tu repositorio a nivel local y en {% data variables.product.product_name %}. - - "Description" (Descripción) es un campo opcional que puedes usar para brindar más información sobre el objetivo de tu repositorio. - - "Local path" (Ruta local) establece la ubicación de tu repositorio en tu computadora. De manera predeterminada, {% data variables.product.prodname_desktop %} crea una carpeta _GitHub_ en tu carpeta _Documents_ (Documentos) para almacenar tus repositorios, pero puedes elegir cualquier ubicación en tu computadora. Tu nuevo repositorio será una carpeta dentro de la ubicación elegida. Por ejemplo, si colocas el nombre `Tutorial` a tu repositorio, se creará la carpeta _Tutorial_ dentro de la carpeta que seleccionaste en tu ruta local. {% data variables.product.prodname_desktop %} recuerda tu ubicación elegida la próxima vez que crees o clones un repositorio nuevo. - - **Si inicializas este repositorio con un README** (Léeme), se crea una confirmación inicial con un archivo _README.md_. README ayuda a las personas a comprender el objetivo de tu proyecto, por lo que recomendamos seleccionarlo y completarlo con información útil. Cuando alguien visita tu repositorio en {% data variables.product.product_name %}, el archivo README es lo primero que verán a medida que aprenden sobre tu proyecto. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)". - - El menú desplegable **Git ignore** (Ignorar Git) te permite agregar un archivo personalizado para ignorar los archivos específicos en tu repositorio local que no deseas almacenar en el control de la versión. Si hay un lenguaje o marco de trabajo que estarás utilizando, puedes seleccionar una opción de la lista disponible. Si recién estás comenzando, puedes omitir esta selección. Para obtener más información, consulta "[Ignorar archivos](/articles/ignoring-files)". - - El menú desplegable **License** (Licencia) te permite agregar una licencia de código abierto para un archivo _LICENSE_ (Licencia) en tu repositorio. No tienes que preocuparte por aprender cómo agregar una licencia inmediatamente. Para obtener más información sobre las licencias de código abierto disponibles y cómo agregarlas a tu repositorio, consulta "[Licenciar un repositorio](/articles/licensing-a-repository)". -3. Haz clic en **Crear repositorio**. - -### Parte 3: Explorar {% data variables.product.prodname_desktop %} -En el menú del archivo en la parte superior de la pantalla, puedes acceder a la configuración y a las acciones que puedes realizar en {% data variables.product.prodname_desktop %}. La mayoría de las acciones tienen atajos del teclado para ayudarte a trabajar con más eficacia. Para encontrar un listado completo de atajos de teclado, consulta la sección "[Atajos de teclado](/desktop/getting-started-with-github-desktop/keyboard-shortcuts)". - -#### La barra de menú de {% data variables.product.prodname_desktop %} -En la parte superior de la app de {% data variables.product.prodname_desktop %}, verás una barra que muestra el estado actual de tu repositorio. - - **Current repository** (Repositorio actual) muestra el nombre del repositorio en el que estás trabajando. Puedes hacer clic en **Current repository** (Repositorio actual) para alternar a un repositorio diferente en {% data variables.product.prodname_desktop %}. - - **Current branch** (Rama actual) muestra el nombre de la rama en la que estás trabajando. Puedes hacer clic en **Current branch** (Rama actual) para ver todas las ramas en tu repositorio, alternar a una rama diferente o crear una rama nueva. Una vez que creaste solicitud de extracción en tu repositorio, también puedes verlas haciendo clic en **Current branch** (Rama actual). - - **Publish repository** (Publicar repositorio) aparece porque todavía no has publicado tu repositorio en {% data variables.product.product_name %}. que harás a continuación en el próximo paso. Esta sección de la barra cambiará con base en el estado de tu repositorio y rama actuales. Varias acciones dependientes del contexto estarán disponibles, las cuales te permitirán intercambiar datos entre tus repositorios locales y remotos. - - ![Explorar el escritorio de GitHub](/assets/images/help/desktop/getting-started-guide/explore-github-desktop.png) - -#### Cambios e Historial -En la barra lateral a la izquierda, encontrarás la vista **Changes** (Cambios) y la vista**History** (Historial). ![Las pestañas de cambios y de historial](/assets/images/help/desktop/changes-and-history.png) - - - La vista **Changes** (Cambios) muestra los cambios que realizaste a los archivos en tu rama actual pero aún no confirmaste en tu repositorio local. En la parte inferior, encontrarás un recuadro con cajas de texto para "Resumen" y "Descripción", y un botón de **Confirmar a RAMA**. Aquí es donde confirmarás los campos nuevos. El botón de **Confirmar a RAMA** es dinámico y mostrará a qué rama estás confirmando tus cambios. ![Área de confirmación de cambios](/assets/images/help/desktop/getting-started-guide/commit-area.png) - - - La vista **History** (Historial) muestra las confirmaciones previas en la rama actual de tu repositorio. Deberías ver una "Initial commit" (Confirmación inicial) que fue creada por {% data variables.product.prodname_desktop %} cuando creaste tu repositorio. A la derecha de la confirmación, según las opciones que seleccionaste al crear tu repositorio, es posible que veas los archivos _.gitattributes_, _.gitignore_, _LICENSE_, o _README_. Puedes hacer clic en cada archivo para ver una diferencia para ese archivo, que son los cambios realizados en el archivo en esa confirmación. La diferencia solo muestra las partes del archivo que han cambiado, no slo los contenidos completos del archivo. ![Vista de historial](/assets/images/help/desktop/getting-started-guide/history-view.png) - -### Parte 4: Publicar tu repositorio en {% data variables.product.product_name %} -Cuando creas un repositorio nuevo, éste solo existirá en tu computadora y serás el único que pueda acceder a él. Puedes publicar tu repositorio en {% data variables.product.product_name %} para mantenerlo sincronizado a través de varias computadoras y permitir que otras personas accedan a él. Para publicar tu repositorio, sube tus cambios locales a {% data variables.product.product_name %}. - -1. Da clic en **Publicar repositorio** en la barra de menú. ![Publicar repositorio](/assets/images/help/desktop/getting-started-guide/publish-repository.png) - - {% data variables.product.prodname_desktop %} llenará los campos de "Nombre" y "Descripción" automáticamente con la información que ingresaste cuando creaste el repositorio. - - La opción de **Mantener este código como privado** te permite controlar quién puede ver tu proyecto. Si no seleccionas esta opción, otros usuarios en {% data variables.product.product_name %} podrán ver tu código. Si seleccionas esta opción, tu código no estará disponible al público en general. - - El menú desplegable de **Organización**, si es que lo hay, te permite publicar tu repositorio en una organización específica en {% data variables.product.product_name %} a la cual pertenezcas. - - ![Publicar pasos del repositorio](/assets/images/help/desktop/getting-started-guide/publish-repository-steps.png) - 2. Haz clic en el botón **Publish Repository** (Publicar repositorio). - 3. Puedes acceder al repositorio en {% data variables.product.prodname_dotcom_the_website %} desde el interior de {% data variables.product.prodname_desktop %}. En el menú del archivo, haz clic en **Repository** (Repositorio), luego haz clic en **View on GitHub** (Ver en GitHub). Esto te llevará directamente hasta el repositorio en tu navegador predeterminado. - -### Parte 5: Hacer, confirmar y subir cambios -Ahora que creaste y publicaste tu repositorio, estás listo para hacer cambios en tu proyecto y comenzar a crear tu primera confirmación para este repositorio. - -1. Para lanzar tu editor externo desde dentro de {% data variables.product.prodname_desktop %}, da clic en **Repositorio**, luego da clic en **Abrir en EDITOR**. Para obtener más información, consulta la sección "[Configurar un editor predeterminado](/desktop/getting-started-with-github-desktop/configuring-a-default-editor)". ![Abrir en editor](/assets/images/help/desktop/getting-started-guide/open-in-editor.png) - -2. Haz algunos cambios al archivo _README.md_ que hayas creado previamente. Puedes agregar información que describa tu proyecto, como por ejemplo, que es lo que hace y por qué es útil. Cuando estés satisfecho con los cambios, guárdalos en tu editor de texto. -3. En {% data variables.product.prodname_desktop %}, navega a la vista de **Cambios**. En la lista de archivos, deberías ver tu _README.md_. La marca de verificación a la izquierda del archivo _README.md_ indica que los cambios que has hecho al archivo serán parte de la confirmación que haces. En el futuro, es posible que realices cambios a múltiples archivos pero solo quieras confirmar los cambios que realizaste en alguno de los archivos. Si das clic en la marca de verificación contigua a un archivo, este archivo no se incluirá en la confirmación. ![Ver cambios](/assets/images/help/desktop/getting-started-guide/viewing-changes.png) - -4. En la parte inferior de la lista **Changes** (Cambios), escribe un mensaje de confirmación. A la derecha de tu imagen de perfil, escribe una descripción breve de la confirmación. Dado que estamos cambiando el archivo _README.md_, "Agregar información sobre el objetivo del proyecto" sería un buen resumen de la confirmación. Debajo del resumen, verás un campo de texto de "Descripción" en donde podrás teclear una descripción más amplia de los cambios en la confirmación, lo cual es de gran ayuda cuando regresas a ver el historial de un proyecto y entiendes por qué se realizaron los cambios. Dado que estás realizando una actualización básica de un archivo _README.md_, puedes omitir la descripción. ![Commit message](/assets/images/help/desktop/getting-started-guide/commit-message.png) <<<<<<< HEAD -5. Da clic en **Confirmar al NOMBRE DE RAMA**. El botón de confirmación muestra tu rama actual, así que puedes estar seguro de confirmar a la rama que quieras. -![Confirmar a una rama](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png) -======= -5. Haz clic en **Committ to master** (Confirmar en principal). El botón de confirmación te muestra tu rama actual, que en este caso es `master`, para que sepas hacia qué rama estás haciendo la confirmación. ![Confirmar al principal](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png) -> > > > > > > principal -6. Para subir los cambios al repositorio remoto en {% data variables.product.product_name %}, haz clic en **Push origin** (Subir origen). ![Subir origen](/assets/images/help/desktop/getting-started-guide/push-to-origin.png) - - El botón de **Subir el origen** es el mismo en el que diste clic para publicar tu repositorio en {% data variables.product.product_name %}. Este botón cambia contextualmente con base en el punto en el que estés en el flujo de trabajo de Git. Ahora debería decir `Subir el origen` con un `1` en un costado, indicando que hay una confirmación que no se ha subido a {% data variables.product.product_name %}. - - El "origen" en **Subir el origen** significa que estás subiendo los cambios al repositorio remoto llamado `origin`, que en este caso es el repositorio de tu proyecto en {% data variables.product.prodname_dotcom_the_website %}. Hasta que hayas subido alguna de las nuevas confirmaciones {% data variables.product.product_name %}, habrá diferencias entre el repositorio de tu proyecto en tu computadora y el repositorio del proyecto en {% data variables.product.prodname_dotcom_the_website %}. Esto te permite trabajar localmente y solo subir tus cambios a {% data variables.product.prodname_dotcom_the_website %} cuando estés listo. -7. En la ventana, a la derecha de la vista de **Cambios**, verás las sugerencias para las acciones que puedes hacer después. Para abrir el repositorio en {% data variables.product.product_name %} en tu buscador, da clic en **Ver en {% data variables.product.product_name %}**. ![Acciones disponibles](/assets/images/help/desktop/available-actions.png) -8. En tu navegador, haz clic en **2 commits** (2 confirmaciones). Verás una lista de las confirmaciones en este repositorio en {% data variables.product.product_name %}. La primera confirmación deberá ser aquella que acabas de realizar en {% data variables.product.prodname_desktop %}. ![Hacer clic en dos confirmaciones](/assets/images/help/desktop/getting-started-guide/click-two-commits.png) - -### Conclusión -Ya creaste un repositorio, lo publicaste en {% data variables.product.product_name %}, hiciste una confirmación y subiste tus cambios a {% data variables.product.product_name %}. Puedes seguir este flujo de trabajo cuando colabores con otros proyectos que crees o en los cuales colabores. - -### Leer más -- "[Aprender más sobre Git](/github/using-git/learning-about-git)" -- "[Aprender más sobre {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" -- "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)" diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md deleted file mode 100644 index 02d320c917..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: Comenzar con GitHub Desktop -intro: 'Aprende cómo ajustar, autenticar y configurar {% data variables.product.prodname_desktop %} para permitirte contribuir en proyectos directamente desde tu máquina.' -miniTocMaxHeadingLevel: 3 -versions: - fpt: '*' -redirect_from: - - /desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop ---- -### Introducción -{% data variables.product.prodname_desktop %} es una aplicación que te habilita para interactuar con {% data variables.product.prodname_dotcom %} utilizando una GUI en vez de la línea de comandos o de un buscador web. {% data variables.product.prodname_desktop %} fomenta que tú y tu equipo colaboren utilizando las mejoras prácticas con Git y {% data variables.product.prodname_dotcom %}. Puedes utilizar {% data variables.product.prodname_desktop %} para completar la mayoría de los comandos de Git desde tu computadora de escritorio con confirmaciones visuales para los cambios. Puedes subir, extraer y clonar repositorios remotos con {% data variables.product.prodname_desktop %} y utilizar herramientas colaborativas tales como atribuir confirmaciones y crear solicitudes de extracción. - -Esta guía te ayudará a iniciar con {% data variables.product.prodname_desktop %} mediante la configuración de la aplicación, la autenticación en tu cuenta, la configuración de ajustes básicos y la introducción de las bases fundamentales para administrar los proyectos con {% data variables.product.prodname_desktop %}. Podrás utilizar {% data variables.product.prodname_desktop %} para colaborar en proyectos y conectarte a repositorios remotos después de seguir esta guía. - -Puede que te sea útil el entender los conceptos básicos de Git y de {% data variables.product.prodname_dotcom %} antes de comenzar a utilizar {% data variables.product.prodname_desktop %}. Para obtener más información, consulta los siguientes artículos. - -- "[Aprender más sobre Git](/github/using-git/learning-about-git)" -- "[Aprender más sobre {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)" -- "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)" - -{% data variables.product.prodname_desktop %} es un proyecto de código abierto. Puedes ver el itinerario, contribuir con el proyecto, o abrir un informe de problemas para proporcionar retroalimentación o solicitudes de características. Para obtener más información, consulta el repositorio [`desktop/desktop`](https://github.com/desktop/desktop). - -### Parte 1: Instalación y autenticación -Puedes instalar {% data variables.product.prodname_desktop %} o cualquier sistema operativo compatible. Para obtener más información, consulta la sección "[Sistemas operativos compatibles](/desktop/getting-started-with-github-desktop/supported-operating-systems)". - -Para instalar {% data variables.product.prodname_desktop %}, visita la página de descargas para [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). Para obtener más información, consulta la sección "[Instalar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/installing-github-desktop)". - -Después de que hayas instalado {% data variables.product.prodname_desktop %}, puedes autenticar la aplicación con tu cuenta en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}. Esta autenticación te permite conectarte remotamente a los repositorios en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}. - -{% mac %} - -1. Antes de que te puedas autenticar en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, necesitarás una cuenta. Para obtener más información acerca de cómo crear una cuenta, consulta la sección "[Registrar una cuenta de {% data variables.product.prodname_dotcom %} nueva](/github/getting-started-with-github/signing-up-for-a-new-github-account)" o contacta a tu administrador de stio de {% data variables.product.prodname_enterprise %}. - -2. En el menú desplegable de {% data variables.product.prodname_desktop %}, da clic en **Preferencias**. En la ventana de preferencias, da clic en **Cuentas** y sigue los pasos para iniciar sesión. Para obtener más información sobre la autenticación, consulta la sección "[Autenticarte en {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)". ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-github.png) - -{% endmac %} - -{% windows %} - -1. Antes de que te puedas autenticar en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, necesitarás una cuenta. Para obtener más información acerca de cómo crear una cuenta, consulta la sección "[Registrar una cuenta de {% data variables.product.prodname_dotcom %} nueva](/github/getting-started-with-github/signing-up-for-a-new-github-account)" o contacta a tu administrador de stio de {% data variables.product.prodname_enterprise %}. - -2. En el menú desplegable de archivo, da clic en **Opciones**. En la ventana de opciones, da clic en **Cuentas** y sigue los pasos para iniciar sesión. Para obtener más información sobre la autenticación, consulta la sección "[Autenticarte en {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)". ![El botón Sign In (Iniciar sesión) para GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-github.png) - -{% endwindows %} - -### Parte 2: Configurar y personalizar {% data variables.product.prodname_desktop %} -Después de que instales {% data variables.product.prodname_desktop %}, puedes configurar y personalizar la app para que se adapte mejor a tus necesidades. - -{% mac %} - -Puedes conectar o eliminar cuentas en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, elegir un editor de texto o shell predeterminado, editar tu configuración de Git, cambiar la apariencia de {% data variables.product.prodname_desktop %}, personalizar los diálogos de sistema y configurar las preferencias de privacidad en la ventana de Preferencias de {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar los ajustes básicos](/desktop/getting-started-with-github-desktop/configuring-basic-settings)". - - ![Los ajustes básicos en la ventana de Preferencias](/assets/images/help/desktop/mac-appearance-tab-themes.png) - -{% endmac %} - -{% windows %} - -Puedes conectar o eliminar cuentas en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}, elegir un editor de texto o shell predeterminado, editar tu configuración de Git, cambiar la apariencia de {% data variables.product.prodname_desktop %}, personalizar los diálogos de sistema y configurar las preferencias de privacidad en la ventana de Opciones de {% data variables.product.prodname_desktop %}. Para obtener más información, consulta la sección "[Configurar los ajustes básicos](/desktop/getting-started-with-github-desktop/configuring-basic-settings)". - - ![Los ajustes básicos en la ventana de Opciones](/assets/images/help/desktop/windows-appearance-tab-themes.png) - -{% endwindows %} - -### Parte 3: Colaborar en proyectos con {% data variables.product.prodname_desktop %} -Después deinstalar, autenticarte y configurar la app, estás listo para comenzar a utilizar {% data variables.product.prodname_desktop %}. Puedes crear, agregar, o clonar los repositorios y utilizar {% data variables.product.prodname_desktop %} para administrar las contribuciones a tus repositorios. - -#### Crear, agregar y clonar repositorios -Puedes crear un repositorio nuevo si seleccionas el menú de archivo y das clic en **Repositorio nuevo...**. Para obtener más información, consulta la sección "[Crear tu primer repositorio utilizando {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop)". - -Puedes agregar un repositorio desde tu computadora local si seleccionas el menú de Archivo y das clic en **Agregar Repositorio Local...**. Para obtener más información, consulta la sección [Agregar un repositorio a {% data variables.product.prodname_desktop %} desde tu computadora local](/desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop)". - -Puedes clonar un repositorio desde {% data variables.product.prodname_dotcom %} si seleccionas el menú de Archivo y das clic en **Clonar Repositorio...**. Para obtener más información, consulta la sección "[Clonar y Bifurcar Repositorios desde {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)". - -{% mac %} - - ![Las opciones del menú de Archivo para crear, agregar, y clonar repositorios](/assets/images/help/desktop/mac-file-menu.png) - -{% endmac %} - -{% windows %} - - ![Las opciones del menú de Archivo para crear, agregar, y clonar repositorios](/assets/images/help/desktop/windows-file-menu.png) - -{% endwindows %} - -#### Realizar cambios en una rama -Puedes utilizar {% data variables.product.prodname_desktop %} para crearuna rama de un proyecto. Las ramas aislan tu trabajo de desarrollo de otras ramas en el repositorio para que puedas experimentar con varios cambios de manera segura. Para obtener más información, consulta la sección "[Administrar ramas](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches)". - - ![El botón de Rama Nueva](/assets/images/help/desktop/new-branch-button-mac.png) - -Después de que hagas cambios a una rama, puedes revisarlos en {% data variables.product.prodname_desktop %} y hacer una confirmación para controlar dichos cambios. Para obtener más información, consulta la sección "[Confirmar y revisar cambios hechos a tu proyecto](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project)". - - ![Viualizar y hacer confirmaciones](/assets/images/help/desktop/commit-button.png) - -Si quieres acceder a tus cambios de manera remota o si quieres compartirlos con otras personas, puedes cargar tus confirmaciones en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Subir los cambios a {% data variables.product.prodname_dotcom %}](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github)". - -#### Colaborar con {% data variables.product.prodname_desktop %} -Puedes utilizar {% data variables.product.prodname_desktop %} para crear informes de problemas o solicitudes de extracción para colaborar en proyectos con otras personas. Los informes de problemas te ayudan a llevar un seguimiento de las ideas y debatir los posibles cambios a los proyectos. Las solicitudes de extracción te permiten compartir tus cambios propuestos con los demás, recibir retroalimentación y fusionar los cambios en un proyecto. Para obtener más información, consulta la sección "[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request)."'' - -Puedes ver tus propias solicitudes de extracción o las de tus colaboradores en {% data variables.product.prodname_desktop %}. El visualizar una solicitud de extracción en {% data variables.product.prodname_desktop %} te permite ver cualquier cambio propuesto y hacer cambios adicionales si abres los repositorios y archivos del proyecto en tu editor de texto predeterminado. Para obtener más información, consulta la sección "[Visualizar una solicitud de extracción en {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop)". - -#### Mantener tu repositorio local sincronizado -Cuando haces cambios a tus repositorios locales o cuando otros hacen cambios a los repositorios remotos, necesitarás sincronizar tu copia local del proyecto con el repositorio remoto. {% data variables.product.prodname_desktop %} puede mantener sincronizada tu copia local de un proyecto con la versión remota al subir y extraer las confirmaciones. Para obtener más información, consulta la sección "[Sincronizar tu rama](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)". - -### Leer más -- "[Instalar y autenticarse en {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop)" -- "[Colaborar y contribuir utilizando {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop)" diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/index.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/index.md deleted file mode 100644 index 25cec896d2..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Resumen -intro: Conozca GitHub Desktop y cree rápidamente su primer repositorio. -redirect_from: - - /desktop/getting-started-with-github-desktop/overview -versions: - fpt: '*' -children: - - /getting-started-with-github-desktop - - /creating-your-first-repository-using-github-desktop - - /supported-operating-systems - - /keyboard-shortcuts - - /launching-github-desktop-from-the-command-line ---- - diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md deleted file mode 100644 index 93779be743..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -title: Atajos del teclado -intro: 'Puedes usar los atajos de teclado en {% data variables.product.prodname_desktop %}.' -redirect_from: - - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop/ - - /desktop/getting-started-with-github-desktop/keyboard-shortcuts - - /desktop/installing-and-configuring-github-desktop/keyboard-shortcuts -versions: - fpt: '*' ---- -{% mac %} - -Atajos de teclado de GitHyb Desktop en macOS - -### Atajos en todo el sitio - -| Atajo del teclado | Descripción | -| ------------------------------------ | ------------------------------------------------------------------------ | -| ⌘, | Ir a Preferences (Preferencias) | -| ⌘H | Ocultar la aplicación {% data variables.product.prodname_desktop %} | -| ⌥⌘H | Ocultar todas las otras aplicaciones | -| ⌘Q | Dejar {% data variables.product.prodname_desktop %} | -| ⌃⌘F | Alternar vista de pantalla completa | -| ⌘0 | Restablecer zoom al tamaño de texto predeterminado | -| ⌘= | Acercar para textos y gráficos más grandes | -| ⌘- | Alejar para textos y gráficos más pequeños | -| ⌥⌘I | Alternar herramientas del desarrollador | - -### Repositorios - -| Atajo del teclado | Descripción | -| ------------------------------------ | ------------------------------------------------------------------------------------ | -| ⌘N | Agregar un repositorio nuevo | -| ⌘O | Agregar un repositorio local | -| ⇧⌘O | Clonar un repositorio desde {% data variables.product.prodname_dotcom %} | -| ⌘T | Mostrar una lista de tus repositorios | -| ⌘P | Subir las últimas confirmaciones a {% data variables.product.prodname_dotcom %} | -| ⇧⌘P | Bajar los últimos cambios de {% data variables.product.prodname_dotcom %} | -| ⌘⌫ | Eliminar un repositorio existente | -| ⇧⌘G | Ver el repositorio en {% data variables.product.prodname_dotcom %} | -| ⌃` | Abrir el repositorio en tu herramienta de terminal preferida | -| ⇧⌘F | Mostrar el repositorio en Finder | -| ⇧⌘A | Abrir el repositorio en tu herramienta de editor preferida | -| ⌘I | Crear un informe de problemas en {% data variables.product.prodname_dotcom %} | - -### Ramas - -| Atajo del teclado | Descripción | -| ------------------------------------ | ---------------------------------------------------------------------------------------------- | -| ⌘1 | Mostrar todos los cambios antes de confirmar | -| ⌘2 | Mostrar tu historial de confirmaciones | -| ⌘B | Mostrar todas tus ramas | -| ⌘G | Ir al campo de resumen de confirmaciones | -| espacio | Selecciona o deselecciona todos los archivos resaltados | -| ⇧⌘N | Crear una rama nueva | -| ⇧⌘R | Renombrar la rama actual | -| ⇧⌘D | Eliminar la rama actual | -| ⇧⌘U | Actualizar desde la rama predeterminada | -| ⇧⌘B | Comparar con una rama existente | -| ⇧⌘M | Fusionar en una rama actual | -| ⌃H | Mostrar u ocultar cambios acumulados | -| ⇧⌘C | Comparar ramas en {% data variables.product.prodname_dotcom %} | -| ⌘R | Mostrar la solicitud de extracción actual en {% data variables.product.prodname_dotcom %} | - -{% endmac %} - -{% windows %} - -Atajos de teclado de GitHub Desktop en Windows - -### Atajos en todo el sitio - -| Atajo del teclado | Descripción | -| ------------------------------------------- | -------------------------------------------------- | -| Ctrl, | Ir a Options (Opciones) | -| F11 | Alternar vista de pantalla completa | -| Ctrl0 | Restablecer zoom al tamaño de texto predeterminado | -| Ctrl= | Acercar para textos y gráficos más grandes | -| Ctrl- | Alejar para textos y gráficos más pequeños | -| CtrlShiftI | Alternar herramientas del desarrollador | - -### Repositorios - -| Atajo del teclado | Descripción | -| ------------------------------------------- | ------------------------------------------------------------------------------------ | -| CtrlN | Agregar un repositorio nuevo | -| CtrlO | Agregar un repositorio local | -| CtrlShiftO | Clonar un repositorio desde {% data variables.product.prodname_dotcom %} | -| CtrlT | Mostrar una lista de tus repositorios | -| CtrlP | Subir las últimas confirmaciones a {% data variables.product.prodname_dotcom %} | -| CtrlShiftP | Bajar los últimos cambios de {% data variables.product.prodname_dotcom %} | -| CtrlDelete | Eliminar un repositorio existente | -| CtrlShiftG | Ver el repositorio en {% data variables.product.prodname_dotcom %} | -| Ctrl` | Abrir el repositorio en tu herramienta de línea de comando preferida | -| CtrlShiftF | Mostrar el repositorio en Explorador | -| CtrlShiftA | Abrir el repositorio en tu herramienta de editor preferida | -| CtrlI | Crear un informe de problemas en {% data variables.product.prodname_dotcom %} | - -### Ramas - -| Atajo del teclado | Descripción | -| ------------------------------------------- | ---------------------------------------------------------------------------------------------- | -| Ctrl1 | Mostrar todos los cambios antes de confirmar | -| Ctrl2 | Mostrar tu historial de confirmaciones | -| CtrlB | Mostrar todas tus ramas | -| CtrlG | Ir al campo de resumen de confirmaciones | -| espacio | Selecciona o deselecciona todos los archivos resaltados | -| CtrlShiftN | Crear una rama nueva | -| CtrlShiftR | Renombrar la rama actual | -| CtrlShiftD | Eliminar la rama actual | -| CtrlShiftU | Actualizar desde la rama predeterminada | -| CtrlShiftB | Comparar con una rama existente | -| CtrlShiftM | Fusionar en una rama actual | -| CtrlH | Mostrar u ocultar cambios acumulados | -| CtrlShiftC | Comparar ramas en {% data variables.product.prodname_dotcom %} | -| CtrlR | Mostrar la solicitud de extracción actual en {% data variables.product.prodname_dotcom %} | - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md deleted file mode 100644 index 701a057ed2..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Lanzar GitHub Desktop desde la línea de comando -shortTitle: Lanzar desde la línea de comandos -intro: Puedes lanzar GitHub Desktop desde la línea de comando. -redirect_from: - - /desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line - - /desktop/installing-and-configuring-github-desktop/launching-github-desktop-from-the-command-line -versions: - fpt: '*' ---- -{% mac %} - -1. En la barra de menú, selecciona el menú de **{% data variables.product.prodname_desktop %}** y luego da clic en **Instalar la Herramienta de Línea de Comandos**. ![Opción para Instalar la Herramienta de Línea de Comandos en el menú desplegable de {% data variables.product.prodname_desktop %}](/assets/images/help/desktop/mac-install-command-line-tool.png) -2. Abre Terminal. -3. {% data reusables.desktop.launch-desktop-from-command-line %} - - ```shell - $ github /path/to/repo - ``` - - También puedes cambiar tu ruta de repositorio y luego teclear `github .` para abrir ese repositorio. - - ```shell - $ cd /path/to/repo - [repo]$ github . - ``` - -{% endmac %} - -{% windows %} - -1. Abre un símbolo del sistema. -2. {% data reusables.desktop.launch-desktop-from-command-line %} - - ```shell - C:\Users\octocat> github path\to\repo - ``` - - También puedes cambiar tu ruta de repositorio y luego teclear `github .` para abrir ese repositorio. - - ```shell - C:\Users\octocat> cd repo\myrepo - C:\Users\octocat\repo\myrepo> github . - ``` - -{% endwindows %} diff --git a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems.md b/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems.md deleted file mode 100644 index b2e5540226..0000000000 --- a/translations/es-XL/content/desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Sistemas operativos compatibles -intro: 'Puedes utilizar {% data variables.product.prodname_desktop %} en cualquier sistema operativo compatible.' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /desktop/getting-started-with-github-desktop/supported-operating-systems - - /desktop/installing-and-configuring-github-desktop/supported-operating-systems -versions: - fpt: '*' ---- -### Acerca de los sistemas operativos compatibles - -Estos son los sistemas operativos compatibles para {% data variables.product.prodname_desktop %}. -- {% data variables.desktop.mac-osx-versions %} -- {% data variables.desktop.windows-versions %}. Debes tener un sistema operativo de 64 bits para ejecutar {% data variables.product.prodname_desktop %}. - -### Solución de problemas en macOS -Si te encuentras con algún problema al utilizar {% data variables.product.prodname_desktop %} en macOS, aquí tienes algunas resoluciones que puedes intentar. Para obtener más información, consulta la sección [`known-issues`](https://github.com/desktop/desktop/blob/development/docs/known-issues.md). - -#### El error `The username or passphrase you entered is not correct` se muestra después de iniciar sesión en tu cuenta - -Este error puede ocurrir cuando {% data variables.product.prodname_desktop %} no puede acceder a tus credenciales almacenadas en la cadena de llaves. - -Para solucionar este error, sigue estos pasos. - -1. Abre la app de "Acceso a la cadena de llaves". -2. Da clic derecho en **inicio de sesión** y luego da clic en **Bloquear el "inicio de sesión" de la cadena de llaves**. ![La opción de "Bloquear el "inicio de sesión" en la cadena de llaves](/assets/images/help/desktop/mac-lock-keychain.png) -3. Da clic derecho en **inicio de sesión** y luego da clic en **Desbloquear el "inicio de sesión" de la cadena de llaves**. Sigue las instrucciones en la pantalla para terminar de desbloquear el "inicio de sesión" de la cadena de llaves ![La opción de "Desbloquear el inicio de sesión en la "cadena de llaves"](/assets/images/help/desktop/mac-unlock-keychain.png) -4. Vuelve a autenticarte en tu cuenta en {% data variables.product.prodname_dotcom %} o en {% data variables.product.prodname_enterprise %}. - -#### El error de `Could not create temporary directory: Permission denied` se muestra después de verificar si hay actualizaciones - -Este error puede estarse causando debido a que no existen los permisos para el directorio `~/Library/Caches/com.github.GitHubClient.ShipIt`. {% data variables.product.prodname_desktop %} utiliza este directorio para crear y desempacar archivos temporales como parte de la actualización de la aplicación. - -Para solucionar este error, sigue estos pasos. - -1. Cierra {% data variables.product.prodname_desktop %}. -2. Abre el "Buscador" y navega hasta `~/Library/Caches/`. -3. Da clic derecho en `com.github.GitHubClient.ShipIt` y luego da clic en **Obtener Información**. -4. Da clic en la flecha a la izquierda de "Compartir & Permisos." -5. Si el privilegio a la derecha de tu cuenta de usuario no dice "Lectura & Escritura", da clic en el texto y luego en **Lectura & Escritura**. ![Las opciones de "Compartir & Permisos"](/assets/images/help/desktop/mac-adjust-permissions.png) -6. Abre {% data variables.product.prodname_desktop %} y verifica si hay actualizaciones. - -### Solución de problemas en Windows -Si te encuentras con algún problema al utilizar {% data variables.product.prodname_desktop %} en Windows, aquí tienes algunas resoluciones que puedes intentar. Para obtener más información, consulta la sección [`known-issues`](https://github.com/desktop/desktop/blob/development/docs/known-issues.md). - -#### Error de `The revocation function was unable to check revocation for the certificate.` - -Este error puede suscitarse si estás utilizando {% data variables.product.prodname_desktop %} en una red corporativa que blqouea a Windows para verificar el estado de revocación de un certificado. - -Para solucionar este problema, contacta al administrador de tu sistema. - -#### Error de `git clone failed` al clonar un repositorio configurado con Redirección de Carpetas - -{% data variables.product.prodname_desktop %} no es compatible con repositorios que se hayan configurado con la Redirección de Carpetas. - -#### Error de `cygheap base mismatch detected` - -Este error se suscita cuando se habilita el ASLR mandatorio. Habilitar el ASLR Mandatorio afecta la librería central de MSYS2, de la cual depende {% data variables.product.prodname_desktop %} para emular la bifurcación de procesos. - -Para solucionar este error, puedes ya sea inhabilitar el ASLR Mandatorio o permitir explícitamente todos los ejecutables bajo `\usr\bin` los cuales dependen en MSYS2. diff --git a/translations/es-XL/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/es-XL/content/developers/apps/building-github-apps/authenticating-with-github-apps.md deleted file mode 100644 index 8880f36159..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Autenticarse con GitHub Apps -intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}' -redirect_from: - - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/ - - /apps/building-github-apps/authentication-options-for-github-apps/ - - /apps/building-github-apps/authenticating-with-github-apps - - /developers/apps/authenticating-with-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -{% data reusables.pre-release-program.machine-man-preview %} -{% data reusables.pre-release-program.api-preview-warning %} -{% endif %} - -### Generar una llave privada - -Después de que creas una GitHub App, necesitarás generar una o más llaves privadas. Utilizarás la llave privada para firmar las solicitudes de token de acceso. - -Puedes crear varias llaves privadas y rotarlas para prevenir el tiempo de inactividad si alguna llave se pone en riesgo o se pierde. Para verificar que una llave privada empata con una llave pública, consulta la sección [Verificar llaves privadas](#verifying-private-keys). - -Para generar una llave privada: - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -{% data reusables.user-settings.modify_github_app %} -5. En "Llaves privadas", da clic en **Generar una llave privada**. ![Generar llave privada](/assets/images/github-apps/github_apps_generate_private_keys.png) -6. Verás una llave privada en formato PEM que se descarga en tu ordenador. Asegúrate de almacenar este archivo, ya que GitHub solo almacena la porción pública de la llave. - -{% note %} - -**Nota:** Si estás utilizando una biblioteca que requiere de un formato de archivo específico, el archivo PEM que descargues se encontrará en formato `PKCS#1 RSAPrivateKey`. - -{% endnote %} - -### Verificar las llaves privadas -{% data variables.product.product_name %} genera una huella digital para cada par de llaves pública y privada utilizando una función de hash {% if currentVersion ver_lt "enterprise-server@2.23" %}SHA-1{% else %}SHA-256{% endif %}. Puedes verificar que tu llave privada empate con la llave pública almacenada en {% data variables.product.product_name %} generando la huella digital de tu llave privada y comparándola con la huella digital que se muestra en {% data variables.product.product_name %}. - -Para verificar una llave privada: - -1. Encuentra la huella digital del par de llaves pública y privada que quieras verificar en la sección "Llaves privadas" de tu página de configuración de desarrollador de {% data variables.product.prodname_github_app %}. Para obtener más información, consulta la sección [Generar una llave privada](#generating-a-private-key). ![Huella digital de llave privada](/assets/images/github-apps/github_apps_private_key_fingerprint.png) -2. Genera la huella digital de tu llave privada (PEM) localmente utilizando el siguiente comando: - ```shell - $ openssl rsa -in PATH_TO_PEM_FILE -pubout -outform DER | openssl {% if currentVersion ver_lt "enterprise-server@2.23" %}sha1 -c{% else %}sha256 -binary | openssl base64{% endif %} - ``` -3. Compara los resultados de la huella digital generada localmente con aquella que ves en {% data variables.product.product_name %}. - -### Borra las llaves privadas -Puedes eliminar una llave privada que se haya perdido o puesto en riesgo si la borras, pero debes de tener por lo menos una llave privada. Cuando solo tienes una llave, necesitas generar una nueva antes de borrar la anterior. ![Borrar la última llave privada](/assets/images/github-apps/github_apps_delete_key.png) - -### Autenticarse como una {% data variables.product.prodname_github_app %} - -El autenticarte como una {% data variables.product.prodname_github_app %} te permite hacer un par de cosas: - -* Puedes recuperar información administrativa de alto nivel acerca de tu {% data variables.product.prodname_github_app %}. -* Puedes solicitar tokens de acceso para una instalación de la app. - -Para autenticarte como una {% data variables.product.prodname_github_app %}, [genera una llave privada](#generating-a-private-key) en formato PEM y descárgala a tu máquina local. Utilizarás esta llave para firmar un [Token Web (JWT) de JSON](https://jwt.io/introduction) y cifrarlo utilizando el algoritmo `RS256`. {% data variables.product.product_name %} revisa que la solicitud se autentique verificando el token con la llave pública almacenada de la app. - -Aquí se muestra rápidamente un script de Ruby que puedes utilizar para generar un JWT. Nota que tendrás que ejecutar `gem install jwt` antes de utilizarlo. - - - -```ruby -require 'openssl' -require 'jwt' # https://rubygems.org/gems/jwt - -# Private key contents -private_pem = File.read(YOUR_PATH_TO_PEM) -private_key = OpenSSL::PKey::RSA.new(private_pem) - -# Generate the JWT -payload = { - # issued at time - iat: Time.now.to_i, - # JWT expiration time (10 minute maximum) - exp: Time.now.to_i + (10 * 60), - # {% data variables.product.prodname_github_app %}'s identifier - iss: YOUR_APP_ID -} - -jwt = JWT.encode(payload, private_key, "RS256") -puts jwt -``` - -`YOUR_PATH_TO_PEM` y `YOUR_APP_ID` son los valores que debes reemplazar. - -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. - -Después de crear el JWT, configura el `Header` de la solicitud de la API: - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -```shell -$ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.machine-man-preview+json" {% data variables.product.api_url_pre %}/app -``` -{% else %} -```shell -$ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github.v3+json" {% data variables.product.api_url_pre %}/app -``` -{% endif %} - -`YOUR_JWT` es el valor que debes reemplazar. - -El ejemplo anterior utiliza el tiempo de caducidad máximo de 10 minutos, después del cual, la API comenzará a devolver el error `401`: - -```json -{ - "message": "'Expiration' claim ('exp') must be a numeric value representing the future time at which the assertion expires.", - "documentation_url": "{% data variables.product.doc_url_pre %}/v3" -} -``` - -Necesitarás crear un nuevo JWT después de que el tiempo caduque. - -### Acceder a terminales de API como una {% data variables.product.prodname_github_app %} - -Para obtener una lista de las terminales de API de REST que puedes utilizar para obtener información de alto nivel acerca de una {% data variables.product.prodname_github_app %}, consulta la sección "[GitHub Apps](/v3/apps/)". - -### 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. Las {% data variables.product.prodname_github_app %} utilizan estos tokes de acceso a la instalación para autenticarse. - -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](/v3/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. - -Para crear un token de acceso de instalación, incluye el JWT [previamente generado](#jwt-payload) en el encabezado de autorización en la solicitud de la API: - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -```shell -$ curl -i -X POST \ --H "Authorization: Bearer YOUR_JWT" \ --H "Accept: application/vnd.github.machine-man-preview+json" \ -{% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens -``` -{% else %} -```shell -$ curl -i -X POST \ --H "Authorization: Bearer YOUR_JWT" \ --H "Accept: application/vnd.github.v3+json" \ -{% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens -``` -{% endif %} - -La respuesta incluirá tu token de acceso de instalación, la fecha de caducidad, los permisos del token, y los repositorios a los cuales tiene acceso. Para obtener más información acerca del formato de respuesta, consulta la terminal [Crear un token de acceso de instalación para una app](/v3/apps/#create-an-installation-access-token-for-an-app). - -Para autenticarte con un token de acceso de instalación, inclúyela en el encabezado de Autorización en la solicitud de la API: - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -```shell -$ curl -i \ --H "Authorization: token YOUR_INSTALLATION_ACCESS_TOKEN" \ --H "Accept: application/vnd.github.machine-man-preview+json" \ -{% data variables.product.api_url_pre %}/installation/repositories -``` -{% else %} -```shell -$ curl -i \ --H "Authorization: token YOUR_INSTALLATION_ACCESS_TOKEN" \ --H "Accept: application/vnd.github.v3+json" \ -{% data variables.product.api_url_pre %}/installation/repositories -``` -{% endif %} - -`YOUR_INSTALLATION_ACCESS_TOKEN` es el valor que debes reemplazar. - -### Acceder a las terminales de la API como una instalación - -Para encontrar un listado de las terminales de la API de REST disponibles para utilizarse con {% data variables.product.prodname_github_app %} utilizando un token de acceso de instalación, consulta la sección "[Terminales Disponibles](/v3/apps/available-endpoints/)". - -Para encontrar un listad de terminales relacionado con las instalaciones, consulta la sección "[Instalaciones](/v3/apps/installations/)". - -### Acceso a Git basado en HTTP mediante una instalación - -Las instalaciones con [permisos](/apps/building-github-apps/setting-permissions-for-github-apps/) en los `contents` de un repositorio pueden utilizar su token de acceso de instalación para autenticarse para acceso a Git. Utiliza el token de acceso de instalación como la contraseña HTTP: - -```shell -git clone https://x-access-token:<token>@github.com/owner/repo.git -``` diff --git a/translations/es-XL/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md b/translations/es-XL/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md deleted file mode 100644 index be9c31b046..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Crear una insignia personalizada para tu GitHub App -intro: '{% data reusables.shortdesc.creating_custom_badges_github_apps %}' -redirect_from: - - /apps/building-github-apps/creating-custom-badges-for-github-apps - - /developers/apps/creating-a-custom-badge-for-your-github-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -Predeterminadamente, una GitHUb App tendrá un [identicon](https://github.com/blog/1586-identicons) generado automáticamente. Una insignia de identicon se ve más o menos así: - -![Identicon](/assets/images/identicon.png) - -Después de crear una GitHub App, puedes personalizar la insignia de tu app si subes un logo y seleccionas un color de fondo. Una insignia es una imagen de logo cuadrado dentro de una insignia circular. Puedes escoger un color de fondo para la insignia, el cual puede distinguir visualmente a tu app. - -Tu logo debe ser un archivo en PNG, JPG, o GIF de menos de 1 MB de tamaño. Para obtener la mejor calidad, te recomendamos un tamaño de por lo menos 200px x 200px. {% if currentVersion == "free-pro-team@latest" %}Consulta la sección "[Tips para las imagenes de logos e insignias](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)" para obtener lineamientos adicionales sobre la personalización de insignias.{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -Puedes cambiar una insignia personalizada para una GitHub App que ya tenga una lista de Marketplace aprobada si navegas a https://github.com/marketplace/manage. - -{% endif %} - -Para crear una insignia personalizada: - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -{% data reusables.user-settings.modify_github_app %} -5. En "Mostrar información", arrastra y suelta una imagen de una carpeta local, o da clic en **Cargar un logo** para seleccionar una imagen de tu ordenador. ![Cargar un logo](/assets/images/github-apps/github_apps_upload_logo.png) -6. Recorta tu imagen. Cuando termines, da clic en **Confirmar avatar nuevo**. ![Cortar y confirmar logo ](/assets/images/github-apps/github_apps_crop_and_set_avatar.png) -7. En "Color de fondo de la insignia", teclea el [código hexadecimal de color](http://www.color-hex.com/) para el color de fondo de tu insignia. {% if currentVersion == "free-pro-team@latest" %}**Nota:** El campo de ingreso para el "Color de fondo de la insignia" únicamente aparecerá después de que cargues un logo para la aplicación.{% endif %} ![Color de fondo de la insignia](/assets/images/github-apps/github_apps_badge_background_color.png) - -{% if currentVersion == "free-pro-team@latest" %} - -### Pasos siguientes - -Para obtener más información acerca de cómo crear un listado de Marketplace para esta app, consulta la sección "[Listados en GitHub Marketplace](/marketplace/listing-on-github-marketplace/)". - -{% endif %} diff --git a/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md b/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md deleted file mode 100644 index 22c5cb1167..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: Crear una GitHub App a partir de un manifiesto -intro: 'Un Manifiesto de una GitHub App es una GitHub App preconfigurada que puedes compartir con cualquiera que desée utilizar tu app en sus repositorios personales. El flujo del manifiesto les permite a los usuarios crear, instalar y comenzar a extender una GitHub App rápidamente sin necesidad de registrarla o de conectar el registro al código hospedado de la app.' -redirect_from: - - /apps/building-github-apps/creating-github-apps-from-a-manifest - - /developers/apps/creating-a-github-app-from-a-manifest -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -### Acerca de los Manifiestos de las GitHub Apps - -Cuando alguien crea una GitHub App desde un manifiesto, únicamente necesitan seguir una URL y nombrar a la app. El manifiesto incluye los permisos, eventos, y URL de los webhooks que se necesiten para registrar la app automáticamente. El flujo del manifiesto crea el registro de la GitHub App y recupera el secreto del webhook, llave privada (archivo PEM), e ID de la GitHub App. Quien sea que cree la app desde el manifiesto será el propietario de la misma y podrá elegir [editar los ajustes de la configuración de seguridad de la app](/apps/managing-github-apps/modifying-a-github-app/), eliminarlos, o transferirlos a otra persona en GitHub. - -Puedes utilizar al [Probot](https://probot.github.io/) para comenzar a utilizar los Manifiestos de las GitHub Apps o ver un ejemplo de implementación. Consulta la sección "[Utilizar al Probot para implementar el flujo del Manifiesto de las GitHub Apps](#using-probot-to-implement-the-github-app-manifest-flow)" para obtener más información. - -Aquí te mostramos algunos escenarios en donde podrías utilizar los Manifiestos de las GitHub Apps para crear apps preconfiguradas: - -* Para ayudar a los miembros nuevos del equipo a que se familiaricen rápidamente con el desarrollo de las GitHub Apps. -* Para permitir que otros extiendan una GitHub App utilizando las API de GitHub sin que necesiten configurar dicha app. -* Para crear diseños de referencia de GitHub Apps y compartirlos con la comunidad de GitHub. -* Para garantizar que despliegas GitHub Apps en los ambientes de desarrollo y de producción utilizando la misma configuración. -* Para rastrear las revisiones hechas en la configuración de una GitHub App. - -### Implementar el flujo del Manifiesto de una GitHub App - -El flujo del Manifiesto de una GitHub App utiliza un proceso de intercambio similar al del [flujo de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). El flujo utiliza un manifiesto para [registrar una GitHub App](/apps/building-github-apps/creating-a-github-app/) y recibe un `code` temporal que se utiliza para recuperar la llave privada, webhoo, secreto, e ID de la misma. - -{% note %} - -**Nota:** Tienes solo una hora para completar los tres pasos del flujo del Manifiesto de la GitHub App. - -{% endnote %} - -Sigue estos pasos par aimplementar el flujo del Manifiesto de la GitHub App: - -1. Redireccionas a las personas a GitHub para crear una GitHub App Nueva. -1. GitHub redirige a las personas de vuelta a tu sitio. -1. Intercambias el código temporal para recuperar la configuración de la app. - -#### 1. Redireccionas a las personas a GitHub para crear una GitHub App Nueva - -Para redireccionar a las personas a crear una GitHub App nueva, [proporciona un enlace](#examples) para que ellos den clic y envíen una solicitud de `POST` a `https://github.com/settings/apps/new` para una cuenta de usuario o a `https://github.com/organizations/ORGANIZATION/settings/apps/new` para una cuenta de organización, reemplazando `ORGANIZATION` con el nombre de la cuenta de organización en donde se creará la app. - -Debes incluir los [Parámetros del Manifiesto de la GitHub App](#github-app-manifest-parameters) como una secuencia cifrada con JSON en un parámetro que se llame `manifest`. También puedes incluir un [parámetro](#parameters) de `state` para agregar seguridad adicional. - -Se redirigirá al creador de la app a una página de GitHub en donde encontrará un campo de entrada y ahí podrá editar el nombre de la app que incluiste en el parámetro de `manifest`. Si no incluyes un `name` en el `manifest`, podrán configurar un nombre de su elección para la app en este campo. - -![Crear un Manifiesto de una GitHub App](/assets/images/github-apps/create-github-app-manifest.png) - -##### Parámetros del Manifiesto de la GitHub App - - | Nombre | Tipo | Descripción | - | --------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - | `name (nombre)` | `secuencia` | El nombre dela GitHub App. | - | `url` | `secuencia` | **Requerido.** La página principal de tu GitHub App. | - | `hook_attributes` | `objeto` | La configuración del webhook de la GitHub App. | - | `redirect_url` | `secuencia` | La URL completa a la cual se redireccionará a la persona después de que instale la GitHub App. | - | `descripción` | `secuencia` | Una descripción de la GitHub App. | - | `public` | `boolean` | Configúralo como `true` cuando tu GitHub App esté disponible al público o como `false` si solo puede acceder el propietario de la misma. | - | `default_events` | `array` | La lista de [eventos](/webhooks/event-payloads) a la cual se suscribe la GitHub App. | - | `default_permissions` | `objeto` | El conjunto de [permisos](/v3/apps/permissions/) que requiere la GitHub App. El formato del objeto utiliza el nombre del permiso para la clave (por ejemplo, `issues`) y el tipo de acceso para el valor (por ejemplo, `write`). | - -El objeto `hook_attributes` tiene la siguiente clave: - -| Nombre | Tipo | Descripción | -| -------- | ----------- | --------------------------------------------------------------------------------------------- | -| `url` | `secuencia` | **Requerido.** La URL del servidor que recibirá las solicitudes de `POST` del webhook. | -| `active` | `boolean` | Entrega detalles del evento cuando se activa este gancho y su valor predeterminado es "true". | - -##### Parámetros - - | Nombre | Tipo | Descripción | - | ------- | ----------- | ------------------------------------------------ | - | `state` | `secuencia` | {% data reusables.apps.state_description %} | - -##### Ejemplos - -Este ejemplo utiliza un formato en una página web con un botón que activa la solicitud de tipo `POST` para una cuenta de usuario: - -``` -
    - Create a GitHub App Manifest:
    - -
    - - -``` -Este ejemplo utiliza un formato en una página web con un botón que activa la solicitud de tipo `POST` para una cuenta de organización. Reemplaza a `ORGANIZATION` con el nombre de la cuenta de organización en donde quieras crear la app. - -``` -
    - Create a GitHub App Manifest:
    - -
    - - -``` - -#### 2. GitHub redirige a las personas de vuelta a tu sitio - -Cuando la persona dé clic en **Crear GitHub App**, Github lo redirigirá a la `redirect_url` con un `code` temporal en un parámetro de código. Por ejemplo: - - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679 - -Si proporcionaste un parámetro de `state`, también verás este parámetro en la `redirect_url`. Por ejemplo: - - https://example.com/callback?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123 - -#### 3. Intercambias el código temporal para recuperar la configuración de la app - -Para completar el intercambio, envía el `code` temporal en una solicitud de tipo `POST` a la terminal [Crear una Github App a partir de un manifiesto](/v3/apps/#create-a-github-app-from-a-manifest). La respuesta incluirá la `id` (GitHub App ID), la `pem` (llave privada), y el `webhook_secret`. GitHub crea un secreto de webhook para la app de forma automática. Puedes almacenar estos valores en variables de ambiente dentro del servidor de la app. Por ejemplo, si tu app utiliza [dotenv](https://github.com/bkeepers/dotenv) para almacenar las variables de ambiente, almacenarías las variables en el archivo `.env` de tu app. - -Tienes solo una hora para completar este paso en el flujo del Manifiesto de la GitHub App. - -{% note %} - -**Nota:** Esta terminal tiene un límite de tasa. Consulta la sección [Límites de tasa](/v3/rate_limit/) para aprender cómo obtener tu estado actual de límite de tasa. - -{% endnote %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %} -{% data reusables.pre-release-program.fury-pre-release %} -{% data reusables.pre-release-program.api-preview-warning %} -{% endif %} - - POST /app-manifests/:code/conversions - -Para obtener más información acerca de la respuesta de la terminal, consulta la sección [Crear una GitHub App desde un manifiesto](/v3/apps/#create-a-github-app-from-a-manifest). - -Cuando se complete el último paso del flujo del manifiesto, la persona que cree la app desde el flujo será el propietario de una GitHub App registrada que podrá instalar en cualquiera de sus repositorios personales. En cualquier momento podrán elegir extender la app utilizando las API de GitHub, transferir la propiedad a alguien más, o borrarla. - -### Utilizar el Probot par aimplementar el flujo del Manifiesto de la GitHub App - -El [Probot](https://probot.github.io/) es un marco de trabajo que se creó con [Node.js](https://nodejs.org/) y que realiza muchas de las tareas que todas las GitHub Apps requieren, como el validar webhooks y llevar a cabo la autenticación. El Probot implementa el [flujo del manifiesto de las GitHub Apps](#implementing-the-github-app-manifest-flow), lo cual facilita el crear y compartir los diseños de referencia de las GitHub Apps con la comunidad de GtiHub. - -Para crear una App de Probot que puedas compartir, sigue estos pasos: - -1. [Genera una GitHub App Nueva](https://probot.github.io/docs/development/#generating-a-new-app). -1. Abre el proyecto que creaste y personaliza la configuración en el archivo `app.yml`. El Probot utiliza la configuración en `app.yml` como los [parámetros del manifiesto dela GitHub App](#github-app-manifest-parameters). -1. Agrega el código personalizado de tu aplicación. -1. [Ejecuta la GitHub App localmente](https://probot.github.io/docs/development/#running-the-app-locally) u [hospédala en donde quieras](#hosting-your-app-with-glitch). Cuando navegues a la URL de la app hospedada, encontrarás una página web con un botón de **Registrar GitHub App** en el que as personas podrán dar clic para crear una app preconfigurada. La siguiente página web es la implementación del Probot para el [paso 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) en el flujo del Manifiesto de la GitHub App: - -![Registrar una GitHub App de Probot](/assets/images/github-apps/github_apps_probot-registration.png) - -Al utilizar [dotenv](https://github.com/bkeepers/dotenv), el Probot crea un archivo de tipo `.env` y configura las variables de ambiente para la `APP_ID`, `PRIVATE_KEY`, y el `WEBHOOK_SECRET` con los valores que [recupera de la configuración de la app](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration). - -#### Hospedar tu app con Glitch - -Puedes ver un ejemplo de una [App de Probot de muestra](https://glitch.com/~auspicious-aardwolf) que utiliza [Glitch](https://glitch.com/) para hospedar y compartir la app. El ejemplo utiliza la [API de verificaciones](/v3/checks/) y selecciona los eventos necesarios de la misma y los permisos en el archivo `app.yml`. Glitch es una herramienta que te permite "Remezclar tus propias apps". El remezclar una app crea una copia de la app que Glitch hospeda y despliega. Consulta la sección "[Acerca de Glitch](https://glitch.com/about/)" para aprender sobre cómo remezclar las apps de Glitch. diff --git a/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md deleted file mode 100644 index 3ac20492d7..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -title: Creating a GitHub App using URL parameters -intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.' -redirect_from: - - /apps/building-github-apps/creating-github-apps-using-url-parameters - - /developers/apps/creating-a-github-app-using-url-parameters -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -### About {% data variables.product.prodname_github_app %} URL parameters - -You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account: -* **User account:** `https://github.com/settings/apps/new` -* **Organization account:** `https://github.com/organizations/:org/settings/apps/new` - -The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app. - -The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation: - - ``` - https://github.com/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_url=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite - ``` - -The complete list of available query parameters, permissions, and events is listed in the sections below. - -### {% data variables.product.prodname_github_app %} configuration parameters - - Name | Type | Description ------|------|------------- -`name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. -`description` | `string` | A description of the {% data variables.product.prodname_github_app %}. -`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage. -`callback_url` | `string` | The full URL to redirect to after someone authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests. -`request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app. -`setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation. -`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed. -`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app. -`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to. -`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details. -`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`. -`domain` | `string` | The URL of a content reference. -`single_file_name` | `string` | When you grant `read` or `write` access to the `single_file` permission, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. - -### {% data variables.product.prodname_github_app %} permissions - -You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission. - -Permission | Description ----------- | ----------- -[`administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -[`blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Grants access to the [Blocking Users API](/v3/users/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -[`checks`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Grants access to the [Checks API](/v3/checks/). Can be one of: `none`, `read`, or `write`. -`content_references` | Grants access to the "[Create a content attachment](/v3/apps/installations/#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`. -[`contents`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`. -[`deployments`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`. -[`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Grants access to the [Emails API](/v3/users/emails/). Can be one of: `none`, `read`, or `write`. -[`followers`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Grants access to the [Followers API](/v3/users/followers/). Can be one of: `none`, `read`, or `write`. -[`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Grants access to the [GPG Keys API](/v3/users/gpg_keys/). Can be one of: `none`, `read`, or `write`. -[`issues`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Grants access to the [Issues API](/v3/issues/). Can be one of: `none`, `read`, or `write`. -[`keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Grants access to the [Public Keys API](/v3/users/keys/). Can be one of: `none`, `read`, or `write`. -[`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% if currentVersion == "free-pro-team@latest" %} -[`metadata`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}. -[`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Grants access to "[Update an organization](/v3/orgs/#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %} -[`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`. -`organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/v3/orgs/#get-an-organization)" endpoint. Can be one of: `none` or `read`. -[`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`.{% if currentVersion == "free-pro-team@latest" %} -[`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Grants access to the [Blocking Organization Users API](/v3/orgs/blocking/). Can be one of: `none`, `read`, or `write`.{% endif %} -[`pages`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`. -`plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/v3/users/#get-a-user)" endpoint. Can be one of: `none` or `read`. -[`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`. -[`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Grants access to the [Repository Webhooks API](/v3/repos/hooks/). Can be one of: `none`, `read`, or `write`. -[`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Grants access to the [Projects API](/v3/projects/). Can be one of: `none`, `read`, `write`, or `admin`. -[`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/v3/repos/contents/). Can be one of: `none`, `read`, or `write`. -[`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/v3/activity/starring/). Can be one of: `none`, `read`, or `write`. -[`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/v3/repos/statuses/). Can be one of: `none`, `read`, or `write`. -[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/v3/teams/discussions/) and the [Team Discussion Comments API](/v3/teams/discussion_comments/). Can be one of: `none`, `read`, or `write`. -`vulnerability_alerts`| Grants access to receive security alerts for vulnerable dependencies in a repository. See "[About security alerts for vulnerable dependencies](/articles/about-security-alerts-for-vulnerable-dependencies)" to learn more. Can be one of: `none` or `read`. -`watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. - -### {% data variables.product.prodname_github_app %} webhook events - -Webhook event name | Required permission | Description ------------------- | ------------------- | ----------- -[`check_run`](/webhooks/event-payloads/#check_run) |`checks` | {% data reusables.webhooks.check_run_short_desc %} -[`check_suite`](/webhooks/event-payloads/#check_suite) |`checks` | {% data reusables.webhooks.check_suite_short_desc %} -[`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %} -[`content_reference`](/webhooks/event-payloads/#content_reference) |`content_references` | {% data reusables.webhooks.content_reference_short_desc %} -[`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %} -[`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %} -[`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %} -[`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %} -[`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %} -[`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %} -[`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %} -[`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %} -[`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %} -[`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %} -[`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %} -[`milestone`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% if currentVersion == "free-pro-team@latest" %} -[`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %} -[`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %} -[`page_build`](/webhooks/event-payloads/#page_build) | `pages` | {% data reusables.webhooks.page_build_short_desc %} -[`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %} -[`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %} -[`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %} -[`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %} -[`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %} -[`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %} -[`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %} -[`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %} -[`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %} -[`repository`](/webhooks/event-payloads/#repository) |`metadata` | {% data reusables.webhooks.repository_short_desc %}{% if currentVersion == "free-pro-team@latest"%} -[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | Allows integrators using GitHub Actions to trigger custom events.{% endif %} -[`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %} -[`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %} -[`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %} -[`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %} diff --git a/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app.md deleted file mode 100644 index 68af5b14cf..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/creating-a-github-app.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Crear una GitHub App -intro: '{% data reusables.shortdesc.creating_github_apps %}' -redirect_from: - - /early-access/integrations/creating-an-integration/ - - /apps/building-integrations/setting-up-and-registering-github-apps/registering-github-apps/ - - /apps/building-github-apps/creating-a-github-app - - /developers/apps/creating-a-github-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% if currentVersion == "free-pro-team@latest" %}Para aprender cómo utilizar los manifiestos de las GitHub Apps, lo cual permite a las personas crear GitHub Apps preconfiguradas, consulta la sección "[Crear GitHub Apps a partir de un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)".{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -{% note %} - - **Nota:** {% data reusables.apps.maximum-github-apps-allowed %} - -{% endnote %} -{% endif %} - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -4. Da clic en **GitHub App Nueva**. ![Botón para crear una GitHub App nueva](/assets/images/github-apps/github_apps_new.png) -5. E "Nombre dela GitHub App", teclea el nombre de tu app. ![Campo para nombrar tu GitHub App](/assets/images/github-apps/github_apps_app_name.png) - - Pónle un nombre claro y breve a tu app. Tu app no puede tener el mismo nombre que un usuario de GitHub, a menos de que sea tu propio nombre de usuario u organización. Una versión simplificada del nombre de tu aplicación se mostrará en la interface de usuario cuando tu integración tome alguna acción. - -6. Opcionalmente, en "Descripción", teclea la descripción de tu app que verán los usuarios. ![Campo para agregar una descripción de tu GitHub App](/assets/images/github-apps/github_apps_description.png) -7. En "URL de la página principal", teclea la URL completa del sitio web de tu app. ![Campo para la URL de la página de inicio de tu GitHub App](/assets/images/github-apps/github_apps_homepage_url.png) -8. En "URL de rellamado para la autorización del usuario", teclea la URL completa a la cual se redireccionará después de que un usuario autorice una instalación. Esta URL se utiliza si tu app necesita identificar y autorizar las solicitudes de usuario a servidor. ![Campo para la URL de rellamado para la autorización del usuario de tu GitHub App](/assets/images/github-apps/github_apps_user_authorization.png) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -9. Predeterminadamente, para mejorar la seguridad de tu app, ésta utilizará un token de autorización de usuario con una vida útil limitada. Para elegir no utilizar estos tokens de usuario, debes deseleccionar la opción "Limitar la vida útil de los tokens de autorización de usuario". Para conocer más acerca de configurar un flujo de rehabilitación de tokens y acerca de los beeficios de que éstos tenga una vida útil limitada, consulta la sección "[Rehabilitar los tokens de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)". ![Opción para decidir aceptar los tokens de usuario con vida útil limitada durante la configuración de GitHub Apps](/assets/images/github-apps/expire-user-tokens-selection.png) -{% endif %} -9. Si tu app autoriza a los usuarios que utilizan el flujo de OAuth, puedes seleccionar la opción **Solicitar la autorización del usuario (OAuth) durante la instalación** para permitir que las personas den autorización a la app cuando la instalen, lo cual te ahorra un paso. Si seleccionas esta opción, la "URL de configuración" dejará de estar disponible y se redirigirá a los usuarios a tu "URL de rellamado para autorización del usuario" después de que instalen la app. Consulta la sección "[Autorizar a los usuarios durante la instalación](/apps/installing-github-apps/#authorizing-users-during-installation)" para obtener más información. ![Solicitar una autorización de usuario durante la instalación](/assets/images/github-apps/github_apps_request_auth_upon_install.png) -10. Si se requiere hacer ajustes adicionales después de la instalación, agrega una "URL de configuración" para redireccionar a los usuarios después de que instalen tu app. ![Campo para configurar la URL de tu GitHub App ](/assets/images/github-apps/github_apps_setup_url.png) - - {% note %} - - **Nota:** Cuando seleccionas **Solicitar la autorización del usuario (OAuth) durante la instalación** en el paso anterior, este campo dejará de estar disponible y se redirigirá a los usuarios a tu "URL de rellamado para autorización del usuario" después de que instalen la app. - - {% endnote %} - -11. En "URL del Webhook", teclea la URL a la cual los eventos harán POST. Cada app recibe su propio webhook, el cual te notificará cada que se instale o modifique dicha app, así como sobre cualquier otor evento al cual se suscriba. ![Campo para la URL del webhook de tu GitHub App](/assets/images/github-apps/github_apps_webhook_url.png) - -12. Opcionalmente, en "Secreto del Webhook", teclea un token secreto opcional que se utilizará para asegurar tus webhooks. ![Campo para agregar un token secreto para tu Webhook](/assets/images/github-apps/github_apps_webhook_secret.png) - - {% note %} - - **Nota:** Te recomendamos ampliamente que configures un token secreto. Para obtener más información, consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)". - - {% endnote %} - -13. En "Permisos", elige aquellos permisos que solicitará tu app. Para cada tipo de permiso, utiliza el menú desplegable, y da clic en **Solo lectura**, **Lectura& escritura**, o **Sin acceso**. ![Varios permisos para tu GitHub App](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png) -14. En "Suscribirse a los eventos", elige si quieres suscribir a tu app a los eventos de **Etiquetas**, **Públicos**, **Repositorios**, o **Observar**. ![Opciones de suscripción a los eventos para tu GitHub App](/assets/images/github-apps/github_apps_subscribe_to_events.png) -15. Para elegir si la app se podrá instalar, selecciona ya sea **Únicamente en esta cuenta** o **Cualquier cuenta**. Para obtener más información sobre las opciones de instalación, selecciona "[Convertir una GitHub App en pública o privada](/apps/managing-github-apps/making-a-github-app-public-or-private/)". ![Opciones de instalación para tu GitHub App](/assets/images/github-apps/github_apps_installation_options.png) -16. Da clic en **Crear GitHub App**. ![Botón para crear tu GitHub App](/assets/images/github-apps/github_apps_create_github_app.png) diff --git a/translations/es-XL/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/es-XL/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md deleted file mode 100644 index 496141bacc..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ /dev/null @@ -1,930 +0,0 @@ ---- -title: Identifying and authorizing users for GitHub Apps -intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}' -redirect_from: - - /early-access/integrations/user-identification-authorization/ - - /apps/building-integrations/setting-up-and-registering-github-apps/identifying-users-for-github-apps/ - - /apps/building-github-apps/identifying-and-authorizing-users-for-github-apps - - /developers/apps/identifying-and-authorizing-users-for-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% data reusables.pre-release-program.expiring-user-access-tokens-beta %} - -When your GitHub App acts on behalf of a user, it performs user-to-server requests. These requests must be authorized with a user's access token. User-to-server requests include requesting data for a user, like determining which repositories to display to a particular user. These requests also include actions triggered by a user, like running a build. - -{% data reusables.apps.expiring_user_authorization_tokens %} - -### Identifying users on your site - -To authorize users for standard apps that run in the browser, use the [web application flow](#web-application-flow). - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -To authorize users for headless apps without direct access to the browser, such as CLI tools or Git credential managers, use the [device flow](#device-flow). The device flow uses the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628). -{% endif %} - -### Web application flow - -Using the web application flow, the process to identify users on your site is: - -1. Users are redirected to request their GitHub identity -2. Users are redirected back to your site by GitHub -3. Your GitHub App accesses the API with the user's access token - -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 - - GET {% data variables.product.oauth_host_code %}/login/oauth/authorize - -When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. - -##### Parameters - -Name | Type | Description ------|------|------------ -`client_id` | `string` | **Required.** The client ID for your GitHub App. You can find this in your [GitHub App settings](https://github.com/settings/apps) when you select your app. -`redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to the URL you provided in the **User authorization callback URL** field when setting up your GitHub App and can't contain any additional parameters. -`state` | `string` | This should contain a random string to protect against forgery attacks and could contain any other arbitrary data. -`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. - -{% note %} - -**Note:** You don't need to provide scopes in your authorization request. Unlike traditional OAuth, the authorization token is limited to the permissions associated with your GitHub App and those of the user. - -{% endnote %} - -#### 2. Users are redirected back to your site by GitHub - -If the user accepts your request, GitHub redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. If the states don't match, the request was created by a third party and the process should be aborted. - -{% note %} - -**Note:** If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, GitHub returns a temporary `code` that you will need to exchange for an access token. The `state` parameter is not returned when GitHub initiates the OAuth flow during app installation. - -{% endnote %} - -Exchange this `code` for an access token. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Every time you refresh the token, you get a new refresh token. For more information, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." - -Expiring user tokens are currently part of the user-to-server token expiration beta and subject to change. To opt-in to the user-to-server token expiration beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} - - POST {% data variables.product.oauth_host_code %}/login/oauth/access_token - -##### Parameters - -Name | Type | Description ------|------|------------ -`client_id` | `string` | **Required.** The client ID for your GitHub App. -`client_secret` | `string` | **Required.** The client secret for your GitHub App. -`code` | `string` | **Required.** The code you received as a response to Step 1. -`redirect_uri` | `string` | The URL in your application where users are sent after authorization. -`state` | `string` | The unguessable random string you provided in Step 1. - -##### Response - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - -By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`, and `refresh_token_expires_in` are only returned when you enable the beta for expiring user-to-server access tokens. - -``` -{ - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", - "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", - "refresh_token_expires_in": "15811200", - "scope": "", - "token_type": "bearer" -} -``` -{% else %} - -By default, the response takes the following form: - - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer - -{% endif %} - -#### 3. Your GitHub App accesses the API with the user's access token - -The user's access token allows the GitHub App to make requests to the API on behalf of a user. - - Authorization: token OAUTH-TOKEN - GET {% data variables.product.api_url_code %}/user - -For example, in curl you can set the Authorization header like this: - -```shell -curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user -``` - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -### Device flow - -{% note %} - -**Note:** The device flow is in public beta and subject to change.{% if currentVersion == "free-pro-team@latest" %} To enable this beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} - -{% endnote %} - -The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. - -For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)". - -{% endif %} - -### Check which installation's resources a user can access - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -{% data reusables.pre-release-program.machine-man-preview %} -{% data reusables.pre-release-program.api-preview-warning %} -{% endif %} - -Once you have an OAuth token for a user, you can check which installations that user can access. - - Authorization: token OAUTH-TOKEN - GET /user/installations - -You can also check which repositories are accessible to a user for an installation. - - Authorization: token OAUTH-TOKEN - GET /user/installations/:installation_id/repositories - -More details can be found in: [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) and [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token). - -### Handling a revoked GitHub App authorization - -If a user revokes their authorization of a GitHub App, the app will receive the [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization) webhook by default. GitHub Apps cannot unsubscribe from this event. {% data reusables.webhooks.authorization_event %} - -### User-level permissions - -You can add user-level permissions to your GitHub App to access user resources, such as user emails, that are granted by individual users as part of the [user authorization flow](#identifying-users-on-your-site). User-level permissions differ from [repository and organization-level permissions](/v3/apps/permissions/), which are granted at the time of installation on an organization or user account. - -You can select user-level permissions from within your GitHub App's settings in the **User permissions** section of the **Permissions & webhooks** page. For more information on selecting permissions, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." - -When a user installs your app on their account, the installation prompt will list the user-level permissions your app is requesting and explain that the app can ask individual users for these permissions. - -Because user-level permissions are granted on an individual user basis, you can add them to your existing app without prompting users to upgrade. You will, however, need to send existing users through the user authorization flow to authorize the new permission and get a new user-to-server token for these requests. - -### User-to-server requests - -While most of your API interaction should occur using your server-to-server installation access tokens, certain endpoints allow you to perform actions via the API using a user access token. Your app can make the following requests using [GraphQL v4](/v4/) or [REST v3](/v3/) endpoints. - -#### Supported endpoints - -{% if currentVersion == "free-pro-team@latest" %} -##### Actions Runners - -* [List runner applications for a repository](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) -* [List self-hosted runners for a repository](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) -* [Get a self-hosted runner for a repository](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) -* [Delete a self-hosted runner from a repository](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) -* [Create a registration token for a repository](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) -* [Create a remove token for a repository](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) -* [List runner applications for an organization](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) -* [List self-hosted runners for an organization](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) -* [Get a self-hosted runner for an organization](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) -* [Delete a self-hosted runner from an organization](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) -* [Create a registration token for an organization](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) -* [Create a remove token for an organization](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) - -##### Actions Secrets - -* [Get a repository public key](/v3/actions/secrets/#get-a-repository-public-key) -* [List repository secrets](/v3/actions/secrets/#list-repository-secrets) -* [Get a repository secret](/v3/actions/secrets/#get-a-repository-secret) -* [Create or update a repository secret](/v3/actions/secrets/#create-or-update-a-repository-secret) -* [Delete a repository secret](/v3/actions/secrets/#delete-a-repository-secret) -* [Get an organization public key](/v3/actions/secrets/#get-an-organization-public-key) -* [List organization secrets](/v3/actions/secrets/#list-organization-secrets) -* [Get an organization secret](/v3/actions/secrets/#get-an-organization-secret) -* [Create or update an organization secret](/v3/actions/secrets/#create-or-update-an-organization-secret) -* [List selected repositories for an organization secret](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) -* [Set selected repositories for an organization secret](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) -* [Add selected repository to an organization secret](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) -* [Remove selected repository from an organization secret](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) -* [Delete an organization secret](/v3/actions/secrets/#delete-an-organization-secret) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -##### Artifacts - -* [List artifacts for a repository](/v3/actions/artifacts/#list-artifacts-for-a-repository) -* [List workflow run artifacts](/v3/actions/artifacts/#list-workflow-run-artifacts) -* [Get an artifact](/v3/actions/artifacts/#get-an-artifact) -* [Delete an artifact](/v3/actions/artifacts/#delete-an-artifact) -* [Download an artifact](/v3/actions/artifacts/#download-an-artifact) -{% endif %} - -##### Check Runs - -* [Create a check run](/v3/checks/runs/#create-a-check-run) -* [Get a check run](/v3/checks/runs/#get-a-check-run) -* [Update a check run](/v3/checks/runs/#update-a-check-run) -* [List check run annotations](/v3/checks/runs/#list-check-run-annotations) -* [List check runs in a check suite](/v3/checks/runs/#list-check-runs-in-a-check-suite) -* [List check runs for a Git reference](/v3/checks/runs/#list-check-runs-for-a-git-reference) - -##### Check Suites - -* [Create a check suite](/v3/checks/suites/#create-a-check-suite) -* [Get a check suite](/v3/checks/suites/#get-a-check-suite) -* [Rerequest a check suite](/v3/checks/suites/#rerequest-a-check-suite) -* [Update repository preferences for check suites](/v3/checks/suites/#update-repository-preferences-for-check-suites) -* [List check suites for a Git reference](/v3/checks/suites/#list-check-suites-for-a-git-reference) - -##### Codes Of Conduct - -* [Get all codes of conduct](/v3/codes_of_conduct/#get-all-codes-of-conduct) -* [Get a code of conduct](/v3/codes_of_conduct/#get-a-code-of-conduct) - -##### Deployment Statuses - -* [List deployment statuses](/rest/reference/repos#list-deployment-statuses) -* [Create a deployment status](/rest/reference/repos#create-a-deployment-status) -* [Get a deployment status](/rest/reference/repos#get-a-deployment-status) - -##### Deployments - -* [List deployments](/rest/reference/repos#list-deployments) -* [Create a deployment](/rest/reference/repos#create-a-deployment) -* [Get a deployment](/rest/reference/repos#get-a-deployment){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -* [Delete a deployment](/rest/reference/repos#delete-a-deployment){% endif %} - -##### Events - -* [List public events for a network of repositories](/rest/reference/activity#list-public-events-for-a-network-of-repositories) -* [List public organization events](/rest/reference/activity#list-public-organization-events) - -##### Feeds - -* [Get feeds](/rest/reference/activity#get-feeds) - -##### Git Blobs - -* [Create a blob](/v3/git/blobs/#create-a-blob) -* [Get a blob](/v3/git/blobs/#get-a-blob) - -##### Git Commits - -* [Create a commit](/v3/git/commits/#create-a-commit) -* [Get a commit](/v3/git/commits/#get-a-commit) - -##### Git Refs - -* [Create a reference](/v3/git/refs/#create-a-reference)* [Get a reference](/v3/git/refs/#get-a-reference) -* [List matching references](/v3/git/refs/#list-matching-references) -* [Update a reference](/v3/git/refs/#update-a-reference) -* [Delete a reference](/v3/git/refs/#delete-a-reference) - -##### Git Tags - -* [Create a tag object](/v3/git/tags/#create-a-tag-object) -* [Get a tag](/v3/git/tags/#get-a-tag) - -##### Git Trees - -* [Create a tree](/v3/git/trees/#create-a-tree) -* [Get a tree](/v3/git/trees/#get-a-tree) - -##### Gitignore Templates - -* [Get all gitignore templates](/v3/gitignore/#get-all-gitignore-templates) -* [Get a gitignore template](/v3/gitignore/#get-a-gitignore-template) - -##### Installations - -* [List repositories accessible to the user access token](/v3/apps/installations/#list-repositories-accessible-to-the-user-access-token) - -{% if currentVersion == "free-pro-team@latest" %} -##### Interaction Limits - -* [Get interaction restrictions for an organization](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) -* [Set interaction restrictions for an organization](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) -* [Remove interaction restrictions for an organization](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) -* [Get interaction restrictions for a repository](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) -* [Set interaction restrictions for a repository](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) -* [Remove interaction restrictions for a repository](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) -{% endif %} - -##### Issue Assignees - -* [Add assignees to an issue](/v3/issues/assignees/#add-assignees-to-an-issue) -* [Remove assignees from an issue](/v3/issues/assignees/#remove-assignees-from-an-issue) - -##### Issue Comments - -* [List issue comments](/v3/issues/comments/#list-issue-comments) -* [Create an issue comment](/v3/issues/comments/#create-an-issue-comment) -* [List issue comments for a repository](/v3/issues/comments/#list-issue-comments-for-a-repository) -* [Get an issue comment](/v3/issues/comments/#get-an-issue-comment) -* [Update an issue comment](/v3/issues/comments/#update-an-issue-comment) -* [Delete an issue comment](/v3/issues/comments/#delete-an-issue-comment) - -##### Issue Events - -* [List issue events](/v3/issues/events/#list-issue-events) - -##### Issue Timeline - -* [List timeline events for an issue](/v3/issues/timeline/#list-timeline-events-for-an-issue) - -##### Issues - -* [List issues assigned to the authenticated user](/v3/issues/#list-issues-assigned-to-the-authenticated-user) -* [List assignees](/v3/issues/assignees/#list-assignees) -* [Check if a user can be assigned](/v3/issues/assignees/#check-if-a-user-can-be-assigned) -* [List repository issues](/v3/issues/#list-repository-issues) -* [Create an issue](/v3/issues/#create-an-issue) -* [Get an issue](/v3/issues/#get-an-issue) -* [Update an issue](/v3/issues/#update-an-issue) -* [Lock an issue](/v3/issues/#lock-an-issue) -* [Unlock an issue](/v3/issues/#unlock-an-issue) - -{% if currentVersion == "free-pro-team@latest" %} -##### Jobs - -* [Get a job for a workflow run](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) -* [Download job logs for a workflow run](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) -* [List jobs for a workflow run](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) -{% endif %} - -##### Labels - -* [List labels for an issue](/v3/issues/labels/#list-labels-for-an-issue) -* [Add labels to an issue](/v3/issues/labels/#add-labels-to-an-issue) -* [Set labels for an issue](/v3/issues/labels/#set-labels-for-an-issue) -* [Remove all labels from an issue](/v3/issues/labels/#remove-all-labels-from-an-issue) -* [Remove a label from an issue](/v3/issues/labels/#remove-a-label-from-an-issue) -* [List labels for a repository](/v3/issues/labels/#list-labels-for-a-repository) -* [Create a label](/v3/issues/labels/#create-a-label) -* [Get a label](/v3/issues/labels/#get-a-label) -* [Update a label](/v3/issues/labels/#update-a-label) -* [Delete a label](/v3/issues/labels/#delete-a-label) -* [Get labels for every issue in a milestone](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) - -##### Licenses - -* [Get all commonly used licenses](/v3/licenses/#get-all-commonly-used-licenses) -* [Get a license](/v3/licenses/#get-a-license) - -##### Markdown - -* [Render a Markdown document](/v3/markdown/#render-a-markdown-document) -* [Render a markdown document in raw mode](/v3/markdown/#render-a-markdown-document-in-raw-mode) - -##### Meta - -* [Meta](/v3/meta/#meta) - -##### Milestones - -* [List milestones](/v3/issues/milestones/#list-milestones) -* [Create a milestone](/v3/issues/milestones/#create-a-milestone) -* [Get a milestone](/v3/issues/milestones/#get-a-milestone) -* [Update a milestone](/v3/issues/milestones/#update-a-milestone) -* [Delete a milestone](/v3/issues/milestones/#delete-a-milestone) - -##### Organization Hooks - -* [List organization webhooks](/rest/reference/orgs#webhooks/#list-organization-webhooks) -* [Create an organization webhook](/rest/reference/orgs#webhooks/#create-an-organization-webhook) -* [Get an organization webhook](/rest/reference/orgs#webhooks/#get-an-organization-webhook) -* [Update an organization webhook](/rest/reference/orgs#webhooks/#update-an-organization-webhook) -* [Delete an organization webhook](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) -* [Ping an organization webhook](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) - -{% if currentVersion == "free-pro-team@latest" %} -##### Organization Invitations - -* [List pending organization invitations](/v3/orgs/members/#list-pending-organization-invitations) -* [Create an organization invitation](/v3/orgs/members/#create-an-organization-invitation) -* [List organization invitation teams](/v3/orgs/members/#list-organization-invitation-teams) -{% endif %} - -##### Organization Members - -* [List organization members](/v3/orgs/members/#list-organization-members) -* [Check organization membership for a user](/v3/orgs/members/#check-organization-membership-for-a-user) -* [Remove an organization member](/v3/orgs/members/#remove-an-organization-member) -* [Get organization membership for a user](/v3/orgs/members/#get-organization-membership-for-a-user) -* [Set organization membership for a user](/v3/orgs/members/#set-organization-membership-for-a-user) -* [Remove organization membership for a user](/v3/orgs/members/#remove-organization-membership-for-a-user) -* [List public organization members](/v3/orgs/members/#list-public-organization-members) -* [Check public organization membership for a user](/v3/orgs/members/#check-public-organization-membership-for-a-user) -* [Set public organization membership for the authenticated user](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) -* [Remove public organization membership for the authenticated user](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) - -##### Organization Outside Collaborators - -* [List outside collaborators for an organization](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) -* [Convert an organization member to outside collaborator](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) -* [Remove outside collaborator from an organization](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) - -{% if currentVersion != "free-pro-team@latest" %} -##### Organization Pre Receive Hooks - -* [List pre-receive hooks for an organization](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) -* [Get a pre-receive hook for an organization](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) -* [Update pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) -* [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -##### Organization Team Projects - -* [List team projects](/v3/teams/#list-team-projects) -* [Check team permissions for a project](/v3/teams/#check-team-permissions-for-a-project) -* [Add or update team project permissions](/v3/teams/#add-or-update-team-project-permissions) -* [Remove a project from a team](/v3/teams/#remove-a-project-from-a-team) -{% endif %} - -##### Organization Team Repositories - -* [List team repositories](/v3/teams/#list-team-repositories) -* [Check team permissions for a repository](/v3/teams/#check-team-permissions-for-a-repository) -* [Add or update team repository permissions](/v3/teams/#add-or-update-team-repository-permissions) -* [Remove a repository from a team](/v3/teams/#remove-a-repository-from-a-team) - -{% if currentVersion == "free-pro-team@latest" %} -##### Organization Team Sync - -* [List idp groups for a team](/v3/teams/team_sync/#list-idp-groups-for-a-team) -* [Create or update idp group connections](/v3/teams/team_sync/#create-or-update-idp-group-connections) -* [List IdP groups for an organization](/v3/teams/team_sync/#list-idp-groups-for-an-organization) -{% endif %} - -##### Organization Teams - -* [List teams](/v3/teams/#list-teams) -* [Create a team](/v3/teams/#create-a-team) -* [Get a team by name](/v3/teams/#get-a-team-by-name) -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %} -* [Get a team](/v3/teams/#get-a-team) -{% endif %} -* [Update a team](/v3/teams/#update-a-team) -* [Delete a team](/v3/teams/#delete-a-team) -{% if currentVersion == "free-pro-team@latest" %} -* [List pending team invitations](/v3/teams/members/#list-pending-team-invitations) -{% endif %} -* [List team members](/v3/teams/members/#list-team-members) -* [Get team membership for a user](/v3/teams/members/#get-team-membership-for-a-user) -* [Add or update team membership for a user](/v3/teams/members/#add-or-update-team-membership-for-a-user) -* [Remove team membership for a user](/v3/teams/members/#remove-team-membership-for-a-user) -* [List child teams](/v3/teams/#list-child-teams) -* [List teams for the authenticated user](/v3/teams/#list-teams-for-the-authenticated-user) - -##### Organizations - -* [List organizations](/v3/orgs/#list-organizations) -* [Get an organization](/v3/orgs/#get-an-organization) -* [Update an organization](/v3/orgs/#update-an-organization) -* [List organization memberships for the authenticated user](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) -* [Get an organization membership for the authenticated user](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) -* [Update an organization membership for the authenticated user](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) -* [List organizations for the authenticated user](/v3/orgs/#list-organizations-for-the-authenticated-user) -* [List organizations for a user](/v3/orgs/#list-organizations-for-a-user) - -{% if currentVersion == "free-pro-team@latest" %} -##### Organizations Credential Authorizations - -* [List SAML SSO authorizations for an organization](/v3/orgs/#list-saml-sso-authorizations-for-an-organization) -* [Remove a SAML SSO authorization for an organization](/v3/orgs/#remove-a-saml-sso-authorization-for-an-organization) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -##### Organizations Scim - -* [List SCIM provisioned identities](/v3/scim/#list-scim-provisioned-identities) -* [Provision and invite a SCIM user](/v3/scim/#provision-and-invite-a-scim-user) -* [Get SCIM provisioning information for a user](/v3/scim/#get-scim-provisioning-information-for-a-user) -* [Set SCIM information for a provisioned user](/v3/scim/#set-scim-information-for-a-provisioned-user) -* [Update an attribute for a SCIM user](/v3/scim/#update-an-attribute-for-a-scim-user) -* [Delete a SCIM user from an organization](/v3/scim/#delete-a-scim-user-from-an-organization) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -##### Source Imports - -* [Get an import status](/v3/migrations/source_imports/#get-an-import-status) -* [Start an import](/v3/migrations/source_imports/#start-an-import) -* [Update an import](/v3/migrations/source_imports/#update-an-import) -* [Cancel an import](/v3/migrations/source_imports/#cancel-an-import) -* [Get commit authors](/v3/migrations/source_imports/#get-commit-authors) -* [Map a commit author](/v3/migrations/source_imports/#map-a-commit-author) -* [Get large files](/v3/migrations/source_imports/#get-large-files) -* [Update Git LFS preference](/v3/migrations/source_imports/#update-git-lfs-preference) -{% endif %} - -##### Project Collaborators - -* [List project collaborators](/v3/projects/collaborators/#list-project-collaborators) -* [Add project collaborator](/v3/projects/collaborators/#add-project-collaborator) -* [Remove project collaborator](/v3/projects/collaborators/#remove-project-collaborator) -* [Get project permission for a user](/v3/projects/collaborators/#get-project-permission-for-a-user) - -##### Projects - -* [List organization projects](/v3/projects/#list-organization-projects) -* [Create an organization project](/v3/projects/#create-an-organization-project) -* [Get a project](/v3/projects/#get-a-project) -* [Update a project](/v3/projects/#update-a-project) -* [Delete a project](/v3/projects/#delete-a-project) -* [List project columns](/v3/projects/columns/#list-project-columns) -* [Create a project column](/v3/projects/columns/#create-a-project-column) -* [Get a project column](/v3/projects/columns/#get-a-project-column) -* [Update a project column](/v3/projects/columns/#update-a-project-column) -* [Delete a project column](/v3/projects/columns/#delete-a-project-column) -* [List project cards](/v3/projects/cards/#list-project-cards) -* [Create a project card](/v3/projects/cards/#create-a-project-card) -* [Move a project column](/v3/projects/columns/#move-a-project-column) -* [Get a project card](/v3/projects/cards/#get-a-project-card) -* [Update a project card](/v3/projects/cards/#update-a-project-card) -* [Delete a project card](/v3/projects/cards/#delete-a-project-card) -* [Move a project card](/v3/projects/cards/#move-a-project-card) -* [List repository projects](/v3/projects/#list-repository-projects) -* [Create a repository project](/v3/projects/#create-a-repository-project) - -##### Pull Comments - -* [List review comments on a pull request](/v3/pulls/comments/#list-review-comments-on-a-pull-request) -* [Create a review comment for a pull request](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) -* [List review comments in a repository](/v3/pulls/comments/#list-review-comments-in-a-repository) -* [Get a review comment for a pull request](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) -* [Update a review comment for a pull request](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) -* [Delete a review comment for a pull request](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) - -##### Pull Request Review Events - -* [Dismiss a review for a pull request](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) -* [Submit a review for a pull request](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) - -##### Pull Request Review Requests - -* [List requested reviewers for a pull request](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) -* [Request reviewers for a pull request](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) -* [Remove requested reviewers from a pull request](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) - -##### Pull Request Reviews - -* [List reviews for a pull request](/v3/pulls/reviews/#list-reviews-for-a-pull-request) -* [Create a review for a pull request](/v3/pulls/reviews/#create-a-review-for-a-pull-request) -* [Get a review for a pull request](/v3/pulls/reviews/#get-a-review-for-a-pull-request) -* [Update a review for a pull request](/v3/pulls/reviews/#update-a-review-for-a-pull-request) -* [List comments for a pull request review](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) - -##### Pulls - -* [List pull requests](/v3/pulls/#list-pull-requests) -* [Create a pull request](/v3/pulls/#create-a-pull-request) -* [Get a pull request](/v3/pulls/#get-a-pull-request) -* [Update a pull request](/v3/pulls/#update-a-pull-request) -* [List commits on a pull request](/v3/pulls/#list-commits-on-a-pull-request) -* [List pull requests files](/v3/pulls/#list-pull-requests-files) -* [Check if a pull request has been merged](/v3/pulls/#check-if-a-pull-request-has-been-merged) -* [Merge a pull request (Merge Button)](/v3/pulls/#merge-a-pull-request) - -##### Reactions - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}* [Delete a reaction](/v3/reactions/#delete-a-reaction-legacy){% else %}* [Delete a reaction](/v3/reactions/#delete-a-reaction){% endif %} -* [List reactions for a commit comment](/v3/reactions/#list-reactions-for-a-commit-comment) -* [Create reaction for a commit comment](/v3/reactions/#create-reaction-for-a-commit-comment) -* [List reactions for an issue](/v3/reactions/#list-reactions-for-an-issue) -* [Create reaction for an issue](/v3/reactions/#create-reaction-for-an-issue) -* [List reactions for an issue comment](/v3/reactions/#list-reactions-for-an-issue-comment) -* [Create reaction for an issue comment](/v3/reactions/#create-reaction-for-an-issue-comment) -* [List reactions for a pull request review comment](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) -* [Create reaction for a pull request review comment](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) -* [List reactions for a team discussion comment](/v3/reactions/#list-reactions-for-a-team-discussion-comment) -* [Create reaction for a team discussion comment](/v3/reactions/#create-reaction-for-a-team-discussion-comment) -* [List reactions for a team discussion](/v3/reactions/#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/v3/reactions/#create-reaction-for-a-team-discussion){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -* [Delete a commit comment reaction](/v3/reactions/#delete-a-commit-comment-reaction) -* [Delete an issue reaction](/v3/reactions/#delete-an-issue-reaction) -* [Delete a reaction to a commit comment](/v3/reactions/#delete-an-issue-comment-reaction) -* [Delete a pull request comment reaction](/v3/reactions/#delete-a-pull-request-comment-reaction) -* [Delete team discussion reaction](/v3/reactions/#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/v3/reactions/#delete-team-discussion-comment-reaction){% endif %} - -##### Repositories - -* [List organization repositories](/v3/repos/#list-organization-repositories) -* [Create a repository for the authenticated user](/v3/repos/#create-a-repository-for-the-authenticated-user) -* [Get a repository](/v3/repos/#get-a-repository) -* [Update a repository](/v3/repos/#update-a-repository) -* [Delete a repository](/v3/repos/#delete-a-repository) -* [Compare two commits](/v3/repos/commits/#compare-two-commits) -* [List repository contributors](/v3/repos/#list-repository-contributors) -* [List forks](/rest/reference/repos#list-forks) -* [Create a fork](/v3/repos/forks/#create-a-fork) -* [List repository languages](/v3/repos/#list-repository-languages) -* [List repository tags](/v3/repos/#list-repository-tags) -* [List repository teams](/v3/repos/#list-repository-teams) -* [Transfer a repository](/v3/repos/#transfer-a-repository) -* [List public repositories](/v3/repos/#list-public-repositories) -* [List repositories for the authenticated user](/v3/repos/#list-repositories-for-the-authenticated-user) -* [List repositories for a user](/v3/repos/#list-repositories-for-a-user) -* [Create repository using a repository template](/v3/repos/#create-repository-using-a-repository-template) - -##### Repository Activity - -* [List stargazers](/rest/reference/activity#list-stargazers) -* [List watchers](/rest/reference/activity#list-watchers) -* [List repositories starred by a user](/rest/reference/activity#list-repositories-starred-by-a-user) -* [Check if a repository is starred by the authenticated user](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) -* [Star a repository for the authenticated user](/rest/reference/activity#star-a-repository-for-the-authenticated-user) -* [Unstar a repository for the authenticated user](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) -* [List repositories watched by a user](/rest/reference/activity#list-repositories-watched-by-a-user) - -{% if currentVersion == "free-pro-team@latest" %} -##### Repository Automated Security Fixes - -* [Enable automated security fixes](/v3/repos/#enable-automated-security-fixes) -* [Disable automated security fixes](/v3/repos/#disable-automated-security-fixes) -{% endif %} - -##### Repository Branches - -* [List branches](/v3/repos/branches/#list-branches) -* [Get a branch](/v3/repos/branches/#get-a-branch) -* [Get branch protection](/v3/repos/branches/#get-branch-protection) -* [Update branch protection](/v3/repos/branches/#update-branch-protection) -* [Delete branch protection](/v3/repos/branches/#delete-branch-protection) -* [Get admin branch protection](/v3/repos/branches/#get-admin-branch-protection) -* [Set admin branch protection](/v3/repos/branches/#set-admin-branch-protection) -* [Delete admin branch protection](/v3/repos/branches/#delete-admin-branch-protection) -* [Get pull request review protection](/v3/repos/branches/#get-pull-request-review-protection) -* [Update pull request review protection](/v3/repos/branches/#update-pull-request-review-protection) -* [Delete pull request review protection](/v3/repos/branches/#delete-pull-request-review-protection) -* [Get commit signature protection](/v3/repos/branches/#get-commit-signature-protection) -* [Create commit signature protection](/v3/repos/branches/#create-commit-signature-protection) -* [Delete commit signature protection](/v3/repos/branches/#delete-commit-signature-protection) -* [Get status checks protection](/v3/repos/branches/#get-status-checks-protection) -* [Update status check potection](/v3/repos/branches/#update-status-check-potection) -* [Remove status check protection](/v3/repos/branches/#remove-status-check-protection) -* [Get all status check contexts](/v3/repos/branches/#get-all-status-check-contexts) -* [Add status check contexts](/v3/repos/branches/#add-status-check-contexts) -* [Set status check contexts](/v3/repos/branches/#set-status-check-contexts) -* [Remove status check contexts](/v3/repos/branches/#remove-status-check-contexts) -* [Get access restrictions](/v3/repos/branches/#get-access-restrictions) -* [Delete access restrictions](/v3/repos/branches/#delete-access-restrictions) -* [List teams with access to the protected branch](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) -* [Add team access restrictions](/v3/repos/branches/#add-team-access-restrictions) -* [Set team access restrictions](/v3/repos/branches/#set-team-access-restrictions) -* [Remove team access restriction](/v3/repos/branches/#remove-team-access-restrictions) -* [List user restrictions of protected branch](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) -* [Add user access restrictions](/v3/repos/branches/#add-user-access-restrictions) -* [Set user access restrictions](/v3/repos/branches/#set-user-access-restrictions) -* [Remove user access restrictions](/v3/repos/branches/#remove-user-access-restrictions) -* [Merge a branch](/v3/repos/merging/#merge-a-branch) - -##### Repository Collaborators - -* [List repository collaborators](/v3/repos/collaborators/#list-repository-collaborators) -* [Check if a user is a repository collaborator](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) -* [Add a repository collaborator](/v3/repos/collaborators/#add-a-repository-collaborator) -* [Remove a repository collaborator](/v3/repos/collaborators/#remove-a-repository-collaborator) -* [Get repository permissions for a user](/v3/repos/collaborators/#get-repository-permissions-for-a-user) - -##### Repository Commit Comments - -* [List commit comments for a repository](/v3/repos/comments/#list-commit-comments-for-a-repository) -* [Get a commit comment](/v3/repos/comments/#get-a-commit-comment) -* [Update a commit comment](/v3/repos/comments/#update-a-commit-comment) -* [Delete a commit comment](/v3/repos/comments/#delete-a-commit-comment) -* [List commit comments](/v3/repos/comments/#list-commit-comments) -* [Create a commit comment](/v3/repos/comments/#create-a-commit-comment) - -##### Repository Commits - -* [List commits](/v3/repos/commits/#list-commits) -* [Get a commit](/v3/repos/commits/#get-a-commit) -* [List branches for head commit](/v3/repos/commits/#list-branches-for-head-commit) -* [List pull requests associated with commit](/v3/repos/commits/#list-pull-requests-associated-with-commit) - -##### Repository Community - -* [Get the code of conduct for a repository](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) -{% if currentVersion == "free-pro-team@latest" %} -* [Get community profile metrics](/v3/repos/community/#get-community-profile-metrics) -{% endif %} - -##### Repository Contents - -* [Download a repository archive](/v3/repos/contents/#download-a-repository-archive) -* [Get repository content](/v3/repos/contents/#get-repository-content) -* [Create or update file contents](/v3/repos/contents/#create-or-update-file-contents) -* [Delete a file](/v3/repos/contents/#delete-a-file) -* [Get a repository README](/v3/repos/contents/#get-a-repository-readme) -* [Get the license for a repository](/v3/licenses/#get-the-license-for-a-repository) - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -##### Repository Event Dispatches - -* [Create a repository dispatch event](/v3/repos/#create-a-repository-dispatch-event) -{% endif %} - -##### Repository Hooks - -* [List repository webhooks](/v3/repos/hooks/#list-repository-webhooks) -* [Create a repository webhook](/v3/repos/hooks/#create-a-repository-webhook) -* [Get a repository webhook](/v3/repos/hooks/#get-a-repository-webhook) -* [Update a repository webhook](/v3/repos/hooks/#update-a-repository-webhook) -* [Delete a repository webhook](/v3/repos/hooks/#delete-a-repository-webhook) -* [Ping a repository webhook](/v3/repos/hooks/#ping-a-repository-webhook) -* [Test the push repository webhook](/v3/repos/hooks/#test-the-push-repository-webhook) - -##### Repository Invitations - -* [List repository invitations](/v3/repos/invitations/#list-repository-invitations) -* [Update a repository invitation](/v3/repos/invitations/#update-a-repository-invitation) -* [Delete a repository invitation](/v3/repos/invitations/#delete-a-repository-invitation) -* [List repository invitations for the authenticated user](/v3/repos/invitations/#list-repository-invitations-for-the-authenticated-user) -* [Accept a repository invitation](/v3/repos/invitations/#accept-a-repository-invitation) -* [Decline a repository invitation](/v3/repos/invitations/#decline-a-repository-invitation) - -##### Repository Keys - -* [List deploy keys](/v3/repos/keys/#list-deploy-keys) -* [Create a deploy key](/v3/repos/keys/#create-a-deploy-key) -* [Get a deploy key](/v3/repos/keys/#get-a-deploy-key) -* [Delete a deploy key](/v3/repos/keys/#delete-a-deploy-key) - -##### Repository Pages - -* [Get a GitHub Pages site](/rest/reference/repos#get-a-github-pages-site) -* [Create a GitHub Pages site](/rest/reference/repos#create-a-github-pages-site) -* [Update information about a GitHub Pages site](/rest/reference/repos#update-information-about-a-github-pages-site) -* [Delete a GitHub Pages site](/rest/reference/repos#delete-a-github-pages-site) -* [List GitHub Pages builds](/rest/reference/repos#list-github-pages-builds) -* [Request a GitHub Pages build](/rest/reference/repos#request-a-github-pages-build) -* [Get GitHub Pages build](/rest/reference/repos#get-github-pages-build) -* [Get latest pages build](/rest/reference/repos#get-latest-pages-build) - -{% if currentVersion != "free-pro-team@latest" %} -##### Repository Pre Receive Hooks - -* [List pre-receive hooks for a repository](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) -* [Get a pre-receive hook for a repository](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) -* [Update pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) -* [Remove pre-receive hook enforcement for a repository](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) -{% endif %} - -##### Repository Releases - -* [List releases](/rest/reference/repos/#list-releases) -* [Create a release](/rest/reference/repos/#create-a-release) -* [Get a release](/rest/reference/repos/#get-a-release) -* [Update a release](/rest/reference/repos/#update-a-release) -* [Delete a release](/rest/reference/repos/#delete-a-release) -* [List release assets](/rest/reference/repos/#list-release-assets) -* [Get a release asset](/rest/reference/repos/#get-a-release-asset) -* [Update a release asset](/rest/reference/repos/#update-a-release-asset) -* [Delete a release asset](/rest/reference/repos/#delete-a-release-asset) -* [Get the latest release](/rest/reference/repos/#get-the-latest-release) -* [Get a release by tag name](/rest/reference/repos/#get-a-release-by-tag-name) - -##### Repository Stats - -* [Get the weekly commit activity](/v3/repos/statistics/#get-the-weekly-commit-activity) -* [Get the last year of commit activity](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -* [Get all contributor commit activity](/v3/repos/statistics/#get-all-contributor-commit-activity) -* [Get the weekly commit count](/v3/repos/statistics/#get-the-weekly-commit-count) -* [Get the hourly commit count for each day](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) - -{% if currentVersion == "free-pro-team@latest" %} -##### Repository Vulnerability Alerts - -* [Enable vulnerability alerts](/v3/repos/#enable-vulnerability-alerts) -* [Disable vulnerability alerts](/v3/repos/#disable-vulnerability-alerts) -{% endif %} - -##### Root - -* [Root endpoint](/v3/#root-endpoint) -* [Emojis](/v3/emojis/#emojis) -* [Get rate limit status for the authenticated user](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) - -##### Search - -* [Search code](/v3/search/#search-code) -* [Search commits](/v3/search/#search-commits) -* [Search labels](/v3/search/#search-labels) -* [Search repositories](/v3/search/#search-repositories) -* [Search topics](/v3/search/#search-topics) -* [Search users](/v3/search/#search-users) - -##### Statuses - -* [Get the combined status for a specific reference](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) -* [List commit statuses for a reference](/v3/repos/statuses/#list-commit-statuses-for-a-reference) -* [Create a commit status](/v3/repos/statuses/#create-a-commit-status) - -##### Team Discussions - -* [List discussions](/v3/teams/discussions/#list-discussions) -* [Create a discussion](/v3/teams/discussions/#create-a-discussion) -* [Get a discussion](/v3/teams/discussions/#get-a-discussion) -* [Update a discussion](/v3/teams/discussions/#update-a-discussion) -* [Delete a discussion](/v3/teams/discussions/#delete-a-discussion) -* [List discussion comments](/v3/teams/discussion_comments/#list-discussion-comments) -* [Create a discussion comment](/v3/teams/discussion_comments/#create-a-discussion-comment) -* [Get a discussion comment](/v3/teams/discussion_comments/#get-a-discussion-comment) -* [Update a discussion comment](/v3/teams/discussion_comments/#update-a-discussion-comment) -* [Delete a discussion comment](/v3/teams/discussion_comments/#delete-a-discussion-comment) - -##### Topics - -* [Get all repository topics](/v3/repos#get-all-repository-topics) -* [Replace all repository topics](/v3/repos/#replace-all-repository-topics) - -{% if currentVersion == "free-pro-team@latest" %} -##### Traffic - -* [Get repository clones](/v3/repos/traffic/#get-repository-clones) -* [Get top referral paths](/v3/repos/traffic/#get-top-referral-paths) -* [Get top referral sources](/v3/repos/traffic/#get-top-referral-sources) -* [Get page views](/v3/repos/traffic/#get-page-views) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -##### User Blocking - -* [List users blocked by the authenticated user](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) -* [Check if a user is blocked by the authenticated user](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) -* [List users blocked by an organization](/v3/orgs/blocking/#list-users-blocked-by-an-organization) -* [Check if a user is blocked by an organization](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) -* [Block a user from an organization](/v3/orgs/blocking/#block-a-user-from-an-organization) -* [Unblock a user from an organization](/v3/orgs/blocking/#unblock-a-user-from-an-organization) -* [Block a user](/v3/users/blocking/#block-a-user) -* [Unblock a user](/v3/users/blocking/#unblock-a-user) -{% endif %} - -##### User Emails - -{% if currentVersion == "free-pro-team@latest" %} -* [Set primary email visibility for the authenticated user](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) -{% endif %} -* [List email addresses for the authenticated user](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) -* [Add email address(es)](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) -* [Delete email address(es)](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) -* [List public email addresses for the authenticated user](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) - -##### User Followers - -* [List followers of a user](/v3/users/followers/#list-followers-of-a-user) -* [List the people a user follows](/v3/users/followers/#list-the-people-a-user-follows) -* [Check if a person is followed by the authenticated user](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) -* [Follow a user](/v3/users/followers/#follow-a-user) -* [Unfollow a user](/v3/users/followers/#unfollow-a-user) -* [Check if a user follows another user](/v3/users/followers/#check-if-a-user-follows-another-user) - -##### User Gpg Keys - -* [List GPG keys for the authenticated user](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) -* [Create a GPG key for the authenticated user](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) -* [Get a GPG key for the authenticated user](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) -* [Delete a GPG key for the authenticated user](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) -* [List gpg keys for a user](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) - -##### User Public Keys - -* [List public SSH keys for the authenticated user](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) -* [Create a public SSH key for the authenticated user](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) -* [Get a public SSH key for the authenticated user](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) -* [Delete a public SSH key for the authenticated user](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) -* [List public keys for a user](/v3/users/keys/#list-public-keys-for-a-user) - -##### Users - -* [Get the authenticated user](/v3/users/#get-the-authenticated-user) -* [List app installations accessible to the user access token](/v3/apps/installations/#list-app-installations-accessible-to-the-user-access-token) -{% if currentVersion == "free-pro-team@latest" %} -* [List subscriptions for the authenticated user](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) -{% endif %} -* [List users](/v3/users/#list-users) -* [Get a user](/v3/users/#get-a-user) - -{% if currentVersion == "free-pro-team@latest" %} -##### Workflow Runs - -* [List workflow runs for a repository](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) -* [Get a workflow run](/v3/actions/workflow-runs/#get-a-workflow-run) -* [Cancel a workflow run](/v3/actions/workflow-runs/#cancel-a-workflow-run) -* [Download workflow run logs](/v3/actions/workflow-runs/#download-workflow-run-logs) -* [Delete workflow run logs](/v3/actions/workflow-runs/#delete-workflow-run-logs) -* [Re run a workflow](/v3/actions/workflow-runs/#re-run-a-workflow) -* [List workflow runs](/v3/actions/workflow-runs/#list-workflow-runs) -* [Get workflow run usage](/v3/actions/workflow-runs/#get-workflow-run-usage) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -##### Workflows - -* [List repository workflows](/v3/actions/workflows/#list-repository-workflows) -* [Get a workflow](/v3/actions/workflows/#get-a-workflow) -* [Get workflow usage](/v3/actions/workflows/#get-workflow-usage) -{% endif %} diff --git a/translations/es-XL/content/developers/apps/building-github-apps/index.md b/translations/es-XL/content/developers/apps/building-github-apps/index.md deleted file mode 100644 index 789d5241b6..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Crear GitHub Apps -intro: Puedes crear GitHub Apps para uso personal o público. Aprende como registrar y configurar permisos y opciones de autenticación para GitHub Apps. -redirect_from: - - /apps/building-integrations/setting-up-and-registering-github-apps/ - - /apps/building-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps -children: - - /creating-a-github-app - - /setting-permissions-for-github-apps - - /managing-allowed-ip-addresses-for-a-github-app - - /authenticating-with-github-apps - - /identifying-and-authorizing-users-for-github-apps - - /rate-limits-for-github-apps - - /refreshing-user-to-server-access-tokens - - /creating-a-github-app-from-a-manifest - - /creating-a-github-app-using-url-parameters - - /creating-a-custom-badge-for-your-github-app ---- - diff --git a/translations/es-XL/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/es-XL/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md deleted file mode 100644 index fc1a751da5..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Límites de tasa para las GitHub Apps -intro: '{% data reusables.shortdesc.rate_limits_github_apps %}' -redirect_from: - - /early-access/integrations/rate-limits/ - - /apps/building-integrations/setting-up-and-registering-github-apps/about-rate-limits-for-github-apps/ - - /apps/building-github-apps/rate-limits-for-github-apps/ - - /apps/building-github-apps/understanding-rate-limits-for-github-apps - - /developers/apps/rate-limits-for-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -### Solicitudes de servidor a servidor - -{% if currentVersion == "free-pro-team@latest" %} - -Se aplicarán límites de tasa diferentes para las solicitudes de servidor a servidor en las {% data variables.product.prodname_github_app %}s 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 - -{% endif %} - -{% data reusables.apps.api-rate-limits-non-ghec %} - -{% if currentVersion == "free-pro-team@latest" %} - -#### Límites de tasa de servidor a servidor de {% data variables.product.prodname_ghe_cloud %} - -Las {% data variables.product.prodname_github_app %}s 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. - -{% endif %} - -### Solicitudes de usuario a servidor - -{% data reusables.apps.deprecating_password_auth %} - -Las {% data variables.product.prodname_github_app %} 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. - -{% if currentVersion == "free-pro-team@latest" %} - -Se aplicarán límites de tasa diferentes para las solicitudes de usuario a servidor en las {% data variables.product.prodname_github_app %}s si la app se encuentra instalada en organizaciones o repositorios que pertenezcan a una cuenta de {% data variables.product.prodname_ghe_cloud %} y el usuario autenticado también pertenece a dicha cuenta de {% data variables.product.prodname_ghe_cloud %}. - -#### Límites de tasa normales de usuario a servidor - -{% endif %} - -Las solicitudes de usuario a servidor tienen un límite de tasa de 5,000 solicitudes por hora y por usuario autenticado. Todas las aplicaciones de OAuth que autorice este usuario, tokens de acceso personal que le pertenezcan y solicitudes autenticadas con su nombre de usuario y contraseña compartirán la misma cuota de 5,000 solicitudes por hora para dicho usuario. - -{% if currentVersion == "free-pro-team@latest" %} - -#### Límites de tasa de usuario a servidor de {% data variables.product.prodname_ghe_cloud %} - -Cuando un usuario pertenece a una cuenta de {% data variables.product.prodname_ghe_cloud %}, las solicitudes de usuario a servidor para los recursos que pertenecen a la misma cuenta de {% data variables.product.prodname_ghe_cloud %} tienen un límite de tasa de 15,000 solicitudes por hora y por usuario autenticado. Todas las aplicaciones de OAuth que autorice este usuario, tokens de acceso personal que le pertenezcan y solicitudes autenticadas con su nombre de usuario y contraseña compartirán la misma cuota de 5,000 solicitudes por hora para dicho usuario. - -{% endif %} - -Para obtener información más detallada acerca de los límites de tasa, consulta la sección "[Limitaciones a las tasas](/rest/overview/resources-in-the-rest-api#rate-limiting)" para la API de REST y "[Limitaciones a los recursos](/graphql/overview/resource-limitations)" para la API de GraphQL. diff --git a/translations/es-XL/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/es-XL/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md deleted file mode 100644 index d79a26f25a..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Actualizar los tokens de acceso de usuario a servidor -intro: 'Para cumplir con la rotación habitual de tokens y reducir el impacto de que se ponga en riesgo alguno de ellos, puedes configurar tu {% data variables.product.prodname_github_app %} para que utilice tokens de acceso de usuario con caducidad.' -redirect_from: - - /apps/building-github-apps/refreshing-user-to-server-access-tokens - - /developers/apps/refreshing-user-to-server-access-tokens -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% data reusables.pre-release-program.expiring-user-access-tokens-beta %} - - -### Acerca de los tokens de acceso de usuario con caducidad - -Para cumplir con la rotación habitual de tokens y reducir el impacto de que se ponga en riesgo alguno de ellos, puedes configurar tu {% data variables.product.prodname_github_app %} para que utilice tokens de acceso de usuario con caducidad. Para obtener más información sobre cómo crear solicitudes de usuario a servidor, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". - -La caducidad de los tokens se alcanza después de 8 horas. Cuando recibes un token nuevo para el acceso de usuario a servidor, la respuesta también contendrá un token de actualización, el cual se puede intercambiar por un token de usuario nuevo y un token de actualización. Los tokens de actualización son válidos por 6 meses. - -### Renovar un token de usuario con un token de actualización - -Para renovar un token de acceso de usuario a servidor que esté por caducar, puedes intercambiar el `refresh_token` por un token de acceso nuevo y un `refresh_token`. - - `POST https://github.com/login/oauth/access_token` - -Esta solicitud de rellamada te enviará un token de acceso y un token de actualización nuevos. Esta solicitud de rellamada es similar a la solicitud de OAuth que utilizarías para intercambiar un `code` temporal para un token de acceso. Para obtener más información, consulta las secciones "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" y "[Información básica sobre la autenticación](/v3/guides/basics-of-authentication/#providing-a-callback)". - -#### Parámetros - -| Nombre | Tipo | Descripción | -| --------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `refresh_token` | `secuencia` | **Requerido.** El token que se genera cuando el dueño de la {% data variables.product.prodname_github_app %} habilita los tokens con caducidad y emite un token de acceso de usuario nuevo. | -| `grant_type` | `secuencia` | **Requerido.** El valor debe ser `refresh_token` (se requiere en la especificación de OAuth). | -| `client_id` | `secuencia` | **Requerido.** La ID de cliente para tu {% data variables.product.prodname_github_app %}. | -| `client_secret` | `secuencia` | **Requerido.** El secreto del cliente para tu {% data variables.product.prodname_github_app %}. | - -#### Respuesta - -```json -{ - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", - "expires_in": "28800", - "refresh_token": "r1.c1b4a2e77838347a7e420ce178f2e7c6912e1692", - "refresh_token_expires_in": "15811200", - "scope": "", - "token_type": "bearer" -} -``` -### Configurar los tokens de usuario con caducidad para una GitHub App existente - -Puedes habilitar o inhabilitar los tokens de autorización de usuario a servidor desde los ajustes de tu {% data variables.product.prodname_github_app %}. - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -4. Da clic en la opción**Editar** junto a la {% data variables.product.prodname_github_app %} que escogiste. ![Configuración para editar una GitHub App](/assets/images/github-apps/edit-test-app.png) -5. En la barra lateral izquierda, da clic en **Características del Beta**. ![Opción de menú de Características del Beta](/assets/images/github-apps/beta-features-option.png) -6. Junto a "caducidad de token de usuario a servidor", da clic en **Unirse** o en **No unirse**. Esta característica podría tardar un par de segundos para su aplicación. - -### Decidir no unirse a los tokens con caducidad para las GitHub Apps nuevas - -Cuando creas una {% data variables.product.prodname_github_app %}, ésta utilizará predeterminadamente los tokens de acceso de usuario a servidor con caducidad. - -Si quieres que tu app utlice tokens de acceso de usuario a servidor sin caducidad, puedes deseleccionar la opción "Poner caducidad en los tokens de autorización de usuario" en la página de ajustes de la app. - -![Opción para decidir aceptar los tokens de usuario con vida útil limitada durante la configuración de GitHub Apps](/assets/images/github-apps/expire-user-tokens-selection.png) - -Las {% data variables.product.prodname_github_app %} 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 habililte la caducidad de los tokens para la app en cuestión. - -Habilitar los tokens de usuario con caducidad para las {% data variables.product.prodname_github_app %} existentes requiere de enviar a 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/)". diff --git a/translations/es-XL/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md b/translations/es-XL/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md deleted file mode 100644 index f36eabf49f..0000000000 --- a/translations/es-XL/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Configurar los permisos para las GitHub Apps -intro: '{% data reusables.shortdesc.permissions_github_apps %}' -redirect_from: - - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps/ - - /apps/building-github-apps/permissions-for-github-apps/ - - /apps/building-github-apps/setting-permissions-for-github-apps - - /developers/apps/setting-permissions-for-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -Cuando creas una GitHub App, puedes seleccionar los permisos a los que necesita para acceder a los datos del usuario final. Los permisos también se pueden agregar y eliminar. Para obtener más información, consulta la sección "[Editar los permisos de una GitHub App](/apps/managing-github-apps/editing-a-github-app-s-permissions/)". - -### Permisos de metadatos - -Predeterminadamente, las GitHub Apps tienen acceso de `Read-only` a las terminales de metadatos. Los metadatos son un conjunto de terminales de solo lectura que proporcionan información general acerca de los recursos a los que puede acceder la instalación autorizada. - -{% data reusables.apps.metadata-permissions %}Para encontrar una lista de terminales de metadatos, consulta la sección "[Permisos de metadatos](/v3/apps/permissions/#metadata-permissions)". diff --git a/translations/es-XL/content/developers/apps/building-oauth-apps.md b/translations/es-XL/content/developers/apps/building-oauth-apps.md deleted file mode 100644 index 46a4dfb395..0000000000 --- a/translations/es-XL/content/developers/apps/building-oauth-apps.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Crear Apps de OAuth -intro: Puedes crear Apps de OAuth para uso personal o público. Aprende como registrar y configurar permisos y opciones de autenticación para Apps de OAuth. -mapTopic: true -redirect_from: - - /apps/building-integrations/setting-up-and-registering-oauth-apps/ - - /apps/building-oauth-apps -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - OAuth Apps ---- - diff --git a/translations/es-XL/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/es-XL/content/developers/apps/getting-started-with-apps/about-apps.md deleted file mode 100644 index c8b79a66e7..0000000000 --- a/translations/es-XL/content/developers/apps/getting-started-with-apps/about-apps.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Acerca de las apps -intro: 'Puedes crear integraciones con las API de {% data variables.product.prodname_dotcom %} para agregar flexibilidad y reducir la fricción en tu propio flujo de trabajo. También puedes compartir las integraciones con otros en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).' -redirect_from: - - /apps/building-integrations/setting-up-a-new-integration/ - - /apps/building-integrations/ - - /apps/getting-started-with-building-apps/ - - /apps/about-apps - - /developers/apps/about-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -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. {% if currentVersion == "free-pro-team@latest" %} 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 %}, Pero GitHub es compatible tanto con las {% data variables.product.prodname_oauth_app %} y con {% data variables.product.prodname_github_apps %}. Para obtener más información sobre cómo escoger un tipo de app, consulta las secciónes "[Acerca de las apps](/apps/about-apps/)" y "[Diferencias entre apps](/apps/differences-between-apps/)". - -{% data reusables.apps.general-apps-restrictions %} - -Para obtener una guía detallada del proceso de creación de una {% data variables.product.prodname_github_app %}, consulta la sección "[Crea tu primer {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)". - -### Acerca de {% data variables.product.prodname_github_apps %} - -Las {% data variables.product.prodname_github_apps %} son actores de primera clase dentro de GitHub. Una {% data variables.product.prodname_github_app %} actúa por si misma, tomando las acciones a través de la API y utilizando directamente su propia identidad, lo que significa que no necesitas mantener un bot o cuenta de servicio como un usuario separado. - -Las {% data variables.product.prodname_github_apps %} se pueden instalar directamente en las cuentas de organización y de usuario, y se les puede dar acceso a repositorios diferentes. Vienen con webhooks integrados y con permisos específicos y delimitados. Cuando configuras tu {% data variables.product.prodname_github_app %}, puedes seleccionar los repositorios a los cuales quieres acceder. Por ejemplo, puedes configurar una app llamada `MyGitHub` que escribe informes de problemas en el repositorio `octocat` y _únicamente_ en dicho repositorio. Para instalar una {% data variables.product.prodname_github_app %}, necesitas ser propietario de la organización o tener permisos administrativos en el repositorio. - -{% data reusables.apps.app_manager_role %} - -Las {% data variables.product.prodname_github_apps %} son aplicaciones que necesitan hospedarse en algún lugar. Para obtener instruciones paso a paso que cubran los temas de servidores y hospedaje, consulta la sección "[Crear tu primer {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)". - -Para mejorar tu flujo de trabajo, puedes crear una {% data variables.product.prodname_github_app %} que contenga varios scripts, o bien, una aplicación completa, y después conectarla a muchas otras herramientas. Por ejemplo, puedes conectar las {% data variables.product.prodname_github_apps %} a GitHub, Slack, a otras apps locales que tuvieras, programas de correo electrónico, o incluso a otras API. - -Toma estas ideas en consideración cuando crees {% data variables.product.prodname_github_apps %}: - -{% if currentVersion == "free-pro-team@latest" %} -* {% data reusables.apps.maximum-github-apps-allowed %} {% endif %} -* Una {% data variables.product.prodname_github_app %} debe tomar acciones independientemente del usuario (a menos de que dicha app utilice un token de [usuario a servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)). {% data reusables.apps.expiring_user_authorization_tokens %} - -* Asegúrate de que la {% data variables.product.prodname_github_app %} se integre con repositorios específicos. -* La {% data variables.product.prodname_github_app %} deberá conectarse a una cuenta personal o a una organización. -* No esperes que la {% data variables.product.prodname_github_app %} sepa y haga todo lo que puede hacer un usuario. -* No utilices a la {% data variables.product.prodname_github_app %} si solo necesitas el servicio de "Iniciar sesión en GitHub". Sin embargo, una {% data variables.product.prodname_github_app %} puede utilizar un [flujo de identificación de usuario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) para registrar a los usuarios _y_ para hacer otras cosas. -* No crees una {% data variables.product.prodname_github_app %} si _únicamente_ quieres fungir como un usuario de GitHub y hacer todo lo que puede hacer un usuario. {% if currentVersion == "free-pro-team@latest" %} -* {% data reusables.apps.general-apps-restrictions %}{% endif %} - -Para comenzar a desarrollar {% data variables.product.prodname_github_apps %}, comienza revisando la sección "[Crear una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)".{% if currentVersion == "free-pro-team@latest" %} Para aprender a utilizar los manifiestos de las {% data variables.product.prodname_github_app %}, los cuales le permiten a las personas crear {% data variables.product.prodname_github_apps %} preconfiguradas, consulta la sección "[Crear {% data variables.product.prodname_github_apps %} a partir de un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)".{% endif %} - -### Acerca de las {% data variables.product.prodname_oauth_app %} - -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. - -{% data reusables.apps.deletes_ssh_keys %} - -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. Nota que las {% data variables.product.prodname_oauth_app %} son aplicaciones que necesitan hospedarse en algún lugar. - -Considera estas ideas cuando crees {% data variables.product.prodname_oauth_app %}: - -{% if currentVersion == "free-pro-team@latest" %} -* {% 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. Con el alcance de `repo` de OAuth, Las {% data variables.product.prodname_oauth_app %} 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_app %} 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.{% if currentVersion == "free-pro-team@latest" %} -* {% data reusables.apps.oauth-apps-restrictions %}{% endif %} - -Para obtener más información sobre las {% data variables.product.prodname_oauth_app %}, consulta las secciones "[Crear una {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" y "[Registrar tu app](/v3/guides/basics-of-authentication/#registering-your-app)". - -### Tokens de acceso personal - -Un [token de acceso personal](/articles/creating-a-personal-access-token-for-the-command-line/) es una secuencia de caracteres que funciona de forma similar a un [Token de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/) en el aspecto de que puedes especificar sus permisos a través de [alcances](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Un token de acceso personal también es similar a una contraseña, pero puedes tener varios de ellos y puedes revocar el acceso de cada uno en cualquier momento. - -Com ejemplo, puedes habilitar un token de acceso personal para tener acceso de escritura en tus repositorios. Si después ejecutas un comando cURL o escribes un script que [genera un informe de problemas](/v3/issues/#create-an-issue) en tu repositorio, pasarías el token de acceso personal para autenticarte. Puedes almacenar el token de acceso personal como una variable de ambiente para evitar el tener que teclearlo cada vez que lo utilices. - -Considera estas ideas cuando utilices tokens de acceso personal: - -* Recuerda utilizar este token para que te represente únicamente a ti. -* Puedes realizar solicitudes cURL de una sola ocasión. -* Puedes ejecutar scripts personales. -* No configures un script para que lo utilice todo tu equipo o compañía. -* No configures una cuenta de usuario compartida para que actúe como un usuario bot. - -### 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 %}. La siguiente imagen te da algunas pregutnas para 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_app %} para tu integración. - -![Introducción al flujo de preguntas de apps](/assets/images/intro-to-apps-flow.png) - -Considera estas preguntas acerca de cómo necesita comportarse tu integración y a qué necesita acceder: - -* ¿Mi integración actuará únicamente como yo, o actuará más como una aplicación? -* ¿Quiero que actúe independientemente de mí como su propia entidad? -* ¿Accederá a todo lo que yo puedo acceder, o quiero limitar su acceso? -* ¿Es simple o compleja? Por ejemplo, los tokens de acceso personal sirven bien para scripts simples y cURLs, mientras que una {% data variables.product.prodname_oauth_app %} puede manejar scripts más complejos. - -### Solicitar soporte - -{% data reusables.support.help_resources %} diff --git a/translations/es-XL/content/developers/apps/getting-started-with-apps/activating-beta-features-for-apps.md b/translations/es-XL/content/developers/apps/getting-started-with-apps/activating-beta-features-for-apps.md deleted file mode 100644 index 96e745c004..0000000000 --- a/translations/es-XL/content/developers/apps/getting-started-with-apps/activating-beta-features-for-apps.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Activar las características beta para las apps -intro: 'Puedes probar nuevas características que se lanzan para el beta público para tus {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_app %}s.' -versions: - free-pro-team: '*' -redirect_from: - - /developers/apps/activating-beta-features-for-apps ---- -{% warning %} - -**Advertencia:** Las características disponibles en el beta público están sujetas a cambios. - -{% endwarning %} - -### Activar las características beta para las {% data variables.product.prodname_github_apps %} - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -3. Selecciona la {% data variables.product.prodname_github_app %} para la cual quieras habilitar la característica beta. -{% data reusables.apps.beta_feature_activation %} - -### Activar las características beta para las {% data variables.product.prodname_oauth_app %}s - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.oauth_apps %} -{% data reusables.apps.beta_feature_activation %} diff --git a/translations/es-XL/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/es-XL/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md deleted file mode 100644 index c0870ada9a..0000000000 --- a/translations/es-XL/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -title: Diferencias entre GitHub Apps y Apps de OAuth -intro: 'El entender las diferencias entre {% data variables.product.prodname_github_app %} y {% data variables.product.prodname_oauth_app %} 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/ - - /apps/differences-between-apps - - /developers/apps/differences-between-github-apps-and-oauth-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps - - OAuth Apps ---- -### ¿Quién puede instalar GitHub Apps y autorizar Apps de OAuth? - -Puedes instalar GitHub Apps en tu cuenta personal o en las organizaciones que te pertenezcan. Si tienes permisos administrativos en un repositorio, puedes instalar GitHub Apps en las cuentas de la organización. Si se instala una GitHub App en un repositorio y requiere permisos de organización, el propietario de la organización deberá aprobar la aplicación. - -{% data reusables.apps.app_manager_role %} - -Por el contrario, los usuarios _autorizan_ las Apps de OAuth, lo cual otorga a estas apps la capacidad de actuar como un usuario autenticado. Por ejemplo, puedes autorizar una App de OAuth que encuentre todas las notificaciones para el usuario autenticado. Siempre puedes retirar los permisos de las Apps de OAuth. - -{% data reusables.apps.deletes_ssh_keys %} - -| GitHub Apps | OAuth Apps | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Debes ser un propietario de la organización o tener permisos administrativos en un repositorio para instalar una GitHub App en una organización. Si se instala una GitHub App en un repositorio y requiere permisos de organización, el propietario de la organización deberá aprobar la aplicación. | Puedes autorizar una app de OAuth para que tenga acceso a los recursos. | -| Puedes instalar una GitHu App en tu repositorio personal. | Puedes autorizar una app de OAuth para que tenga acceso a los recursos. | -| Debes ser un propietario de la organización, propietario del repositorio personal, o tener permisos administrativos en un repositorio para desinstalar una GitHub App y eliminar su acceso. | Puedes borrar un token de acceso de OAuth para eliminar el acceso. | -| Debes ser un propietario de la organización o tener permisos administrativos en un repositorio para solicitar la instalación de una GitHub App. | Si está activa una política de aplicación organizacional, cualquier miembro de la organización puede solicitar la instalación de una App de OAuth en dicha organización. Un propietario de la organización deberá aprobar o negar la solicitud. | - -### ¿A qué recursos pueden acceder las GitHub Apps y las Apps de OAuth? - -Los propietarios de las cuentas pueden utilizar una {% data variables.product.prodname_github_app %} en una cuenta sin otorgarle acceso a otra cuenta. Por ejemplo, puedes instalar un servicio de compilación de terceros en la organización de tu patrón laboral, pero puedes decidir no otorgar a esa compilación acceso de servicio a los repositorios en tu cuenta personal. Una GitHub App permanece instalada si la persona que la configuró deja a la organización. - -Una App de OAuth _autorizada_ tiene acceso a todos los recursos que son accesibles para el usuario o el propietario de la organización. - -| GitHub Apps | OAuth Apps | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Instalar la GitHub App le otorga acceso a la misma en los repositorios elegidos de la cuenta de usuario o de organización. | Autorizar una App de OAuth otorga a dicha app acceso a los recursos que puede acceder el usuario. Por ejemplo, a los repositorios que puede acceder. | -| El token de instalación de una GitHub App pierde acceso a los recursos si un administrador elimina los repositorios de la instalación. | Un token de acceso de OAuth pierde acceso a los recursos cuando el usuario mismo pierde acceso a ellos, como cuando pierden el acceso de escritura a un repositorio. | -| Los tokens de acceso de la instalación se limitan a los repositorios especificados con los permisos que escogió el creador de la app. | Un token de acceso de OAuth se limita por alcances. | -| Las GitHub Apps pueden solicitar acceso por separado a los informes de problemas y a las solicitudes de extracción sin acceder al contenido real del repositorio. | Las Apps de OAuth necesitan solicitar el alcance de `repo` para obtener acceso a los informes de problemas, solicitudes de extracción, o a cualquier recurso que pertenezca al repositorio. | -| Las GitHub Apps no están sujetas a las políticas de aplicación de la organización. Una GitHub app solo tendrá acceso a los repositorios que haya otorgado el propietario de una organización. | Si una política de aplicación de la organización se encuentra activa, únicamente el propietario de la organización podrá autorizar la instalación de una App de OAuth. Si se instala, la App de OAuth obtiene acceso a todo lo que esté visible para el token que tiene el propietario de la organización dentro de la organización aprobada. | -| Las GitHub Apps reciben un evento de webhook cuando se cambia o elimina una instalación. Esto indica al creador de la app cuando han recibido más o menos accesos a los recursos organizacionales. | Las Apps de OAuth pueden perder el acceso a una organización o a un repositorio en cualquier momento con base en acceso cambiante del usuario que otorga los permisos. La App de OAuth no te informará cuando pierde el acceso a un recurso. | - -### Identificación basada en tokens - -{% note %} - -**Nota:** Las GitHub Apps también pueden utilizar un token basado en un usuario. 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/)". - -{% 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 %}{% if currentVersion == "free-pro-team@latest" %} 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. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -| Las {% data variables.product.prodname_github_app %} 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_app %} autoriza a una {% data variables.product.prodname_oauth_app %} a 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 %}. |{% endif %} - -### Solicitar niveles de permiso para recursos - -A diferencia de las apps de OAuth, las GitHub Apps tiene permisos específicos que les permiten solicitar acceso únicamente a lo que necesitan. Por ejemplo, una GitHub App de Integración Continua (IC) puede solicitar acceso de lectura al contenido del repositorio y acceso de escritura la API de estado. Puede que alguna otra GitHub App no tenga acceso de escritura o lectura al código, pero aún podrá administrar informes de problemas, etiquetas e hitos. Las Apps de OAuth no pueden utilizar permisos granulares. - -| Acceso | GitHub Apps (permisos de `read` o `write`) | OAuth Apps | -| --------------------------------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------- | -| **Para acceder a los repositorios públicos** | El repositorio público necesita elegirse durante la instalación. | alcance `public_repo`. | -| **Para acceder al código/contenido del repositorio** | Contenidos del repositorio | alcance `repo`. | -| **Para acceder a informes de problemas, etiquetas e hitos** | Problemas | alcance `repo`. | -| **Para acceder a solicitudes de extracción, etiquetas e hitos** | Solicitudes de extracción | alcance `repo`. | -| **Para acceder a estados de confirmación (para compilaciones de IC)** | Estados de confirmación | alcance `repo:status`. | -| **Para acceder a los despliegues y estados de despliegue** | Implementaciones | alcance `repo_deployment`. | -| **Para recibir eventos a través de un webhook** | Las GitHub Apps incluyen un webhook predeterminadamente. | alcance `write:repo_hook` o `write:org_hook`. | - -### Descubrimiento de repositorios - -| GitHub Apps | OAuth Apps | -| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Las GitHub Apps pueden ver a `/installation/repositories` para encontrar repositorios a los que puede acceder la instalación. | Las Apps de OAuth pueden ver a `/user/repos` para tener una vista de tipo usuario o a `/orgs/:org/repos` para tener una de tipo organización para los repositorios accesibles. | -| Las Github Apps reciben webhooks cuando los repositorios se agregan o eliminan de la instalación. | Las Apps de OAuth crean webhooks de organización para las notificaciones cuando se crea un repositorio nuevo dentro de una organización. | - -### Webhooks - -| GitHub Apps | OAuth Apps | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Predeterminadamente, las GitHub Apps tienen un solo webhook que recibe los eventos que se les ha configurado para recibir para cada repositorio al que tengan acceso. | Las Apps de OAuth solicitan el alcance de webhook para crear un webhook de repositorio para cada repositorio del cual necesiten recibir eventos. | -| Las GitHub Apps reciben algunos eventos a nivel organizacional con el permiso del miembro de la organización. | Las Apps de OAuth solicitan el alcance de webhook de la organización para crear un webhook de organización para cada organización de la cual necesiten recibir eventos de nivel organizacional. | - -### Acceso a Git - -| GitHub Apps | OAuth Apps | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Las GitHub Apps solicitan permiso a los contenidos del repositorio y utilizan tu token de instalación para autenticarte a través de [Git basado en HTTP](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | Las Apps de OAuth piden el alcance `write:public_key` y [Crean una llave de despliegue](/v3/repos/keys/#create-a-deploy-key) a través de la API. Entonces puedes utilizar esa llave para ejecutar comandos de Git. | -| El token se utiliza como la contraseña HTTP. | El token se utiliza como el nombre de usuario HTTP. | - -### Cuentas de máquina vs cuentas de bot - -Las cuentas de usuario de máquina son cuentas de usuario basadas en OAuth que segregan sistemas automatizados utilizando el sistema de usuarios de GitHub. - -Las cuentas de bot son específicas para las GitHub Apps y se crean en cada GitHub App. - -| GitHub Apps | OAuth Apps | -| ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- | -| Los bots de las GitHub Apps no consumen una plaza de {% data variables.product.prodname_enterprise %}. | Una cuenta de usuario de máquina consume una plaza de {% data variables.product.prodname_enterprise %}. | -| Ya que jamás se otorga una contraseña a un bot de una GitHub App, un cliente no podrá iniciar sesión directamente en él. | Una cuenta de usuario de máquina obtiene un nombre de usuario y contraseña para que el cliente lo administre y asegure. | diff --git a/translations/es-XL/content/developers/apps/getting-started-with-apps/index.md b/translations/es-XL/content/developers/apps/getting-started-with-apps/index.md deleted file mode 100644 index 07ce4587ad..0000000000 --- a/translations/es-XL/content/developers/apps/getting-started-with-apps/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Comenzar con las apps -intro: Aprende cómo crear apps y como configurar tu ambiente de desarrollo. -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps -children: - - /about-apps - - /activating-optional-features-for-apps - - /differences-between-github-apps-and-oauth-apps - - /migrating-oauth-apps-to-github-apps - - /setting-up-your-development-environment-to-create-a-github-app ---- - diff --git a/translations/es-XL/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md b/translations/es-XL/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md deleted file mode 100644 index 5fefe89102..0000000000 --- a/translations/es-XL/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Migrar de Apps de OAuth a GitHub Apps -intro: 'Aprende sobre las ventajas de migrarte de tu {% data variables.product.prodname_oauth_app %} a una {% data variables.product.prodname_github_app %} y sobre como migrar una {% data variables.product.prodname_oauth_app %} que no se encuentre listada en {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /apps/migrating-oauth-apps-to-github-apps - - /developers/apps/migrating-oauth-apps-to-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -Este artículo proporciona los lineamientos para los integradores existentes que están considerando migrarse de una App de OAuth a una GitHub App. - - -### Razones para cambiar a GitHub Apps - -Las [GitHub Apps](/apps/) son la forma recomendada de integrarse con GitHub, ya que ofrecen muchas ventajas sobre una integración puramente basada en OAuth: - -- [Permisos detallados](/apps/differences-between-apps/#requesting-permission-levels-for-resources) que se enfocan en la información específica a la que puede acceder una GitHub App, lo cual permite que las personas y organizaciones la utilicen más ampliamente con políticas de seguridad a diferencia de las Apps de OAuth, las cuales no se pueden limitar con permisos. -- [Tokens de vida corta](/apps/differences-between-apps/#token-based-identification) que proporcionan un método de autenticación más segura qu la de los tokens de OAuth. Un token de OAuth no caduca hasta que la persona que autorizó la App de OAuth revoque el token. Las GitHub Apps utilizan tokens que caducan rápidamente, lo cual permite tener una ventana de tiempo mucho menor para que se utilicen los tokens que se hayan puesto en riesgo, en caso de existir. -- [Webhooks integrados y centralizados](/apps/differences-between-apps/#webhooks) que reciben eventos para todos los repositorios y organizaciones a los cuales puede acceder la app. Por el contrario, las Apps de OAuth requieren configurar un webhook para cada repositorio y organización que sea accesible para el usuario. -- [Cuentas Bot](/apps/differences-between-apps/#machine-vs-bot-accounts) que no consument una plaza de {% data variables.product.prodname_ghe_server %} y permanecen instaladas aún cuando la persona que las instaló inicialmente deja la organización. -- El soporte integrado para OAuth aún estará disponible para las GitHub Apps que utilicen [terminales de usuario a servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/). -- Los [límites de tasa de la API](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) dedicados para cuentas bot se escalarán con tu integración. -- Los propietarios de los repositorios pueden [Instalar GitHub Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) en repositorios de organización. Si la configuración de una GitHub App tiene permisos que solicitan los recursos de una organización, el propietario de dicha organización debe aprobar la instalación. -- El apoyo de la comunidad de código abierto se encuentra disponible mediante las [bibliotecas Octokit](/v3/libraries/) y mediante otros marcos de trabajo, tales como el [Probot](https://probot.github.io/). -- Los integradores que crean GitHub Apps tienen la oportunidad para adoptar un acceso temprano a las API. - -### Convertir una App de OAuth en una GitHub App - -Estos lineamientos asumen que has registrado una App de OAuth{% if currentVersion == "free-pro-team@latest" %} que puede o no estar listada en GitHub Marketplace{% endif %}. A nivel superior, necesitarás llevar a cabo los siguientes pasos: - -1. [Revisar las terminales de la API disponibles para las Github Apps](#review-the-available-api-endpoints-for-github-apps) -1. [Diseñar con apego a los límites de tasa de la API](#design-to-stay-within-api-rate-limits) -1. [Registrar una GitHub App nueva](#register-a-new-github-app) -1. [Determinar los permisos que necesitará tu app](#determine-the-permissions-your-app-requires) -1. [Suscribirte a los webhooks](#subscribe-to-webhooks) -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. [Animar a los usuarios a que revoquen el acceso a tu App de OAuth](#encourage-users-to-revoke-access-to-your-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](/v3) y de las consultas de [GraphQL](/v4) 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](/v3/apps/available-endpoints/) 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. 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_app %}. - -#### Diseñar con apego a los límites de tasa de la API - -Las GitHub Apps utilizan [reglas móviles para los límites de tasa](/apps/building-github-apps/understanding-rate-limits-for-github-apps/), las cuales pueden incrementar con base en la cantidad de repositorios y usuarios de la organización. Una GitHub App también puede hacer uso de [solicitudes condicionales](/v3/#conditional-requests) o de solicitudes consolidadas si utiliza la [API de GraphQL V4](/v4/). - -#### Registrar una GitHub App nueva - -Una vez que hayas decidido hacer el cambio hacia GitHub Apps, necesitarás [crear una GitHub App nueva](/apps/building-github-apps/). - -#### Determinar los permisos que necesitará tu app - -Cuando registras tu GitHub App, necesitarás seleccionar los permisos que requiere cada terminal que se utilice en el código de tu app. Consulta la sección "[Permisos de la GitHub App](/v3/apps/permissions/)" para encontrar un listado de permisos que necesita cada terminal disponible para las GitHub Apps. - -En la configuración de tu GitHub App, puedes especificar si tu app necesita acceso de tipo `No Access`, `Read-only`, o `Read & Write` para cada tipo de permiso. Los permisos detallados le permiten a tu app obtener acceso específico a el subconjunto de datos que necesites. Te recomendamos especifcar el conjunto de datos más definido que sea posible, el cual proporcione la funcionalidad deseada. - -#### Suscribirte a los webhooks - -Después de que creaste una GitHub App nueva y seleccionaste sus permisos, puedes seleccionar los eventos de webhook a los cuales deseas suscribirte. Consulta la sección "[Editar los permisos de una GitHub App](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para aprender sobre cómo suscribirte a los webhooks. - -#### Entender los diferentes métodos de autenticación - -Las GitHub Apps utilizan principalmente una autenticación basada en tokens que caducan después de un periodo de tiempo corto, lo cual proporciona más seguirdad que un token de OAuth que no caduca. Es importante entender los diferentes métodos de autenticación que tienes disponibles cuando necesitas utilizarlos: - -* Un **Token Web de JSON (JWT)** [ se autentica como la GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app). Por ejemplo, puedes autenticarte con un **JWT** para obtener los detalles de instalación de la aplicación o para intercambiar dicho **JWT** por un **token de acceso a la instalación**. -* Un **token de acceso de la instalación** [se autentica como una instalación específica de tu GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) (también se les conoce como solicitudes de servidor a servidor). Por ejemplo, puedes autenticarte con un **token de acceso de la instalación** para abrir un informe de problemas o para proporcionar retroalimentación en una solicitud de extracción. -* Un **Token de acceso de OAuth** puede [autenticarse como un usuario de tu GitHub App](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site) (también se les conoce como solicitudes de usuario a servidor). Por ejemplo, puedes utilizar un token de acceso de OAuth para autenticarte como un usuario cuando una GitHub App necesite verificar la identidad del usuario o actuar en nombre de un usuario. - -El escenario más común es autenticarse como una instalación específica utilizando un **token de acceso de la instalación**. - -#### Dirigir a los usuarios a instalar tu GitHub App en los repositorios - -Una vez que hiciste la transición de una App de OAuth a una GitHub App, necesitarás informar a los usuarios que esta GitHub App se encuentra disponible para su instalación. Por ejemplo, puedes incluir un enlace de instalación para la GitHub App en un letrero de llamada a la acción dentro de tu aplicación. Para facilitar la transición, puedes utilizar parámetros de consulta para identificar a la cuenta de usuario o de organización que esté pasando por el flujo de instalación para tu GitHub App y pre-seleccionar cualquier repositorio al que tuviera acceso tu App de OAuth. Esto les permite a los usuarios instalar tu GitHub App en los repositorios a los que ya tengas acceso. - -##### Parámetros de consulta - -| Nombre | Descripción | -| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `suggested_target_id` | **Requerido**: La ID del usuario u organización que está instalando tu GitHub App. | -| `repository_ids[]` | Matriz de las ID de repositorio. Si se omite, seleccionaremos todos los repositorios. La cantidad máxima de repositorios que se pueden pre-seleccionar es de 100. | - -##### URL de Ejemplo -``` -https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID -``` - -Necesitarás reemplazar a `YOUR_APP_NAME` con el nombre de tu GitHub App, a `ID_OF_USER_OR_ORG` con la ID de tu usuario u organización destino, e incluir hasta 100 ID de repositorio (`REPO_A_ID` y `REPO_B_ID`). Para obtener una lista de repositorios a los cuales tiene acceso tu aplicación de OAuth, utiliza las terminales [Listar repositorios para el usuario autenticado](/v3/repos/#list-repositories-for-the-authenticated-user) y [Listar repositorios de la organización](/v3/repos/#list-organization-repositories). - -#### Eliminar cualquier gancho innecesario en los repositorios - -Una vez que ti GitHub App se haya instalado en un repositorio, deberías eliminar cualquier webhook innecesario que haya creado tu App tradicional de OAuth. Si ambas apps están instaladas en un repositorio, puede que se duplique la funcionalidad para el usuario. Para eliminar los webhooks, puedes escuchar al [webhook de `installation_repositories`](/webhooks/event-payloads/#installation_repositories) con la acción `repositories_added` y al [webhook para borrar un repositorio](/v3/repos/hooks/#delete-a-repository-webhook) en los repositorios que creó tu App de OAuth. - -#### Animar a los usuarios a que revoquen el acceso a tu App de OAuth - -En medida en que vaya creciendo tu base de instalación de la GitHub App, considera exhortar a tus usuarios para [revocar el acceso](/articles/authorizing-oauth-apps/) a la integración tradicional de OAuth. diff --git a/translations/es-XL/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/es-XL/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md deleted file mode 100644 index 3e1783be1a..0000000000 --- a/translations/es-XL/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md +++ /dev/null @@ -1,450 +0,0 @@ ---- -title: Configurar tu ambiente de desarrollo para crear una GitHub App -intro: 'Aprende los fundamentos para extender y crear {% data variables.product.prodname_github_apps %} nuevas.' -redirect_from: - - /apps/quickstart-guides/setting-up-your-development-environment - - /developers/apps/setting-up-your-development-environment-to-create-a-github-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -### Introducción - -Esta guía te mostrará los pasos necesarios para configurar una GitHub App y para ejecutarla en un servidor. Las GitHub Apps necesitan algunos pasos de configuración para administrar eventos de webhook y así conectar el registro de la App en GitHub hacia tu código. La app en esta guía sirve como una base que puedes utilizar para extender y crear GitHub Apps nuevas. - -Al finalizar esta guía habrás registrado una GitHub App y habrás configurado un servidor web para recibir eventos de webhook. Aprenderás como utilizar una herramienta llamada Smee para capturar las cargas útiles de los webhooks y reenviarlas a tu ambiente de desarrollo local. La app de plantilla que configurarás en esta sección no hará nada especial aún, pero funcionará como un marco de trabajo que puedes utilizar para comenzar a escribir tu código de aplicaciones utilizando la API o para completar otras [guías de inicio rápido](/apps/quickstart-guides/). {% if currentVersion == "free-pro-team@latest" %}Puedes revisar los ejemplos exitosos de estas aplicaciones en [GitHub Marketplace](https://github.com/marketplace) y en [Compatible con GitHub](https://github.com/works-with).{% endif %} - -Después de completar este proyecto entenderás cómo autenticarte como una GitHub App y como una instalación, así como la forma en que difieren estos métodos de autenticación. - -Aquí están los pasos que tomarás para configurar la plantilla de la GitHub App: - -1. [Inicia un canal nuevo de Smee](#step-1-start-a-new-smee-channel) -1. [Registrar una GitHub App nueva](#step-2-register-a-new-github-app) -1. [Guarda tu llave privada e ID de tu App](#step-3-save-your-private-key-and-app-id) -1. [Prepara el ambiente de ejecución](#step-4-prepare-the-runtime-environment) -1. [Revisar el código de la plantilla de la GitHub App](#step-5-review-the-github-app-template-code) -1. [Inicia el servidor](#step-6-start-the-server) -1. [Instala la app en tu cuenta](#step-7-install-the-app-on-your-account) - -{% data reusables.apps.app-ruby-guides %} - -### Prerrequisitos - -Puede que te sea útil tener un entendimiento básico de lo siguiente: - -* [GitHub Apps](/apps/about-apps) -* [Webhooks](/webhooks) -* [El lenguaje de programación Ruby](https://www.ruby-lang.org/en/) -* [Las API de REST](/v3) -* [Sinatra](http://sinatrarb.com/) - -Pero puedes seguir esta guía sin importar tu nivel de experiencia. ¡Colocaremos enlaces para la información que requieras en cada fase! - -Antes de comenzar, necesitarás clonar el repositorio con el código de la plantilla que se utiliza en esta guía de inicio rápido. Abre tu app de terminal y encuentra el directorio en donde quieras almacenar el código. Ejecuta este comando para clonar el repositorio [Plantilla de GitHub App](https://github.com/github-developer/github-app-template): - -```shell -$ git clone https://github.com/github-developer/github-app-template.git -``` - -### Paso 1. Inicia un canal nuevo de Smee - -Para ayudar a que GitHub envíe webhooks a tu máquina local sin exponerla al internet, puedes utilizar una herramienta llamada Smee. Primero, dirígete a https://smee.io y da clic en **Iniciar un canal nuevo**. Si ya estás a gusto con otras herramientas que exponen tu máquina local al internet como [ngrok](https://dashboard.ngrok.com/get-started) o [localtunnel](https://localtunnel.github.io/www/), siéntete libre para utilizarlas. - -![El botón de nuevo canal de Smee](/assets/images/smee-new-channel.png) - -El iniciar un canal de Smee nuevo crea un dominio único en donde GitHub puede enviar cargas útiles de webhooks. Necesitas saber cuál es este dominio para continuar con el siguiente paso. Aquí hay un ejemplo de un dominio único en `https://smee.io/qrfeVRbFbffd6vD`: - -![Un canal de Smee único](/assets/images/smee-unique-domain.png) - -Posteriormente, regresa a la terminal y sigue estos pasos para ejecutar el cliente de la interface de línea de comandos (CLI) de Smee: - -{% note %} - -**Nota:** Los siguientes pasos son ligeramente diferentes que las instrucciones de "Utilizar la CLI" que encuentras en la página de tu canal de Smee. **No** necesitas seguir las instrucciones de las secciones "Utilizar el cliente de Node.js" o de "Utilizar el soporte integrado de Probot". - -{% endnote %} - -1. Instalar el cliente: - - ```shell - $ npm install --global smee-client - ``` - -2. Ejecuta el cliente (reemplazando a `https://smee.io/qrfeVRbFbffd6vD` con tu propio dominio): - - ```shell - $ smee --url https://smee.io/qrfeVRbFbffd6vD --path /event_handler --port 3000 - ``` - - Deberías ver una salida como ésta: - - ```shell - Forwarding https://smee.io/qrfeVRbFbffd6vD to http://127.0.0.1:3000/event_handler - Connected https://smee.io/qrfeVRbFbffd6vD - ``` - -El comando `smee --url ` le dice a Smee que reenvíe todos los eventos de webhook que reciba el canal de Smee al cliente de Smee que se ejecuta en tu computadora. La opción `--path /event_handler` reenvía los eventos a la ruta `/event_handler`, lo cual cubriremos en una [sección subsecuente](#step-5-review-the-github-app-template-code). La opción `--port 3000` especifica al puerto 3000, el cual es aquél que escuchará tu servidor. Si utilizas Smee, tu máquina no necesita estar abierta al internet público para recibir webhooks de GitHub. También puedes abrir la URL de Smee en tu buscador para inspeccionar las cargas útiles de los webhooks como vayan llegando. - -Te recomendamos dejar abierta esta ventana de terminal y mantener a Smee conectado mientras completas el resto de los pasos de esta guía. Aunque _puedes_ desconectar y reconectar el cliente de Smee sin perder tu dominio único (a diferencia de con ngrok), puede que te sea más fácil dejarlo conectado y llevar a cabo otras tareas en la línea de comandos en una ventana diferente de la terminal. - -### Paso 2. Registrar una GitHub App nueva - -Si aún no tienes una cuenta de GitHub, ahora es un [buen momento para unirte](https://github.com/join). ¡No te olvides de verificar tu dirección de correo electrónico antes de continuar! Para registrar una app nueva, visita la [página de configuración de la app](https://github.com/settings/apps) en tu perfil de GitHub, y da clic en **GitHub App nueva**. - -![El sitio web de Github, mostrando la **App Nueva**](/assets/images/new-app.png) - -Verás un formato en el cual puedes ingresar detalles sobre tu app. Consulta la sección "[Crear una GitHub App](/apps/building-github-apps/creating-a-github-app/)" para obtener información general acerca de los campos de esta página. Para los fines de esta guía, necesitaras ingresar datos específicos en unos cuantos campos: - -{% note %} - -**Nota:** Siempre puedes actualizar esta configuración más adelante para apuntar a un servidor hospedado. - -{% endnote %} - -* En "URL de la página principal", utiliza el dominio que emitió Smee. Por ejemplo: - - ![Formato completado con el dominio de Smee para la URL de una página principal](/assets/images/homepage-url.png) - -* Para la "URL del webhook", utiliza nuevamente el dominio que emitió Smee. Por ejemplo: - - ![Formato completado con el dominio de Smee para la URl de un webhook](/assets/images/webhook-url.png) - -* Para el "Secreto del webhook", crea una contraseña para asegurar las terminales de tu webhook. Este debería ser algo que solo tú (y GitHub, a través de este formulario) sepas. El secreto es importante, ya que estarás recibiendo cargas útiles desde el internet público, y utilizarás este secreto para verificar el remitente del webhook. Nota que la configuración de la GitHub App dice que el secreto de webhook es opcional, lo cual es verdad en la mayoría de los casos, pero para que funcione el código de la plantilla de la app, debes configurar un secreto de webhook. - - ![Formato completado con el secreto de un webhook](/assets/images/webhook-secret.png) - -* En la página de permisos & webhooks, puedes especificar un conjunto de permisos para tu app, los cuales determinan la cantidad de datos a los cuales tiene acceso la misma. Deja esta página con sus valores predeterminados. Si decides extender esta app de plantilla, puedes actualizar estos permisos más adelante. - -* En la parte inferior de la página de permisos & webhooks, especifica si es una app privada o pública. Esto se refiere a quién puede instalarla: ¿solo tú, o alguien más en general? Por el momento, deja la app como privada seleccionando **Solo en esta cuenta**. - - ![Privacidad de GitHub App](/assets/images/create_app.png) - -¡Da clic en **Crear GitHub App** para crear tu app! - -### Paso 3. Guarda tu llave privada e ID de tu App - -Después de que creas tu app, se te llevará de regreso a la [página de configuración de la app](https://github.com/settings/apps). Tienes dos cosas más para hacer aquí: - -* **Generar una llave privada para tu app.** Esto es necesario para autenticar tu app más adelante. Baja en la página y da clic en **Generar una llave privada**. Guarda el archivo PEM resultante (que tiene un nombre algo similar a _`app-name`_-_`date`_-private-key.pem) en un directorio en donde lo puedas volver a encontrar después. - - ![El diálogo de generación de la llave privada](/assets/images/private_key.png) - -* **Guardar la ID de app que GitHub le asignó a ésta.** Esto se necesita para preparar tu ambiente de ejecución. - - Tu número de ID para la app - -### Paso 4. Prepara el ambiente de ejecución - -Para mantener tu información segura, te recomendamos poner todos los secretos relacionados con tu app en la memoria de tu ordenador en donde tu app pueda encontrarlos, en vez de ponerlos directamente en tu código. Esta útil herramienta de desarrollo llamada [dotenv](https://github.com/bkeepers/dotenv) carga las variables de ambiente específicas del proyecto desde un archivo `.env` hacia `ENV`. Jamás ingreses tu archivo `.env` en GitHub. Este es un archivo local que almacena la información sensible que no quieres sacar al internet público. El archivo `.env` ya se incluye en el archivo [`.gitignore`](/articles/ignoring-files/) del repositorio para prevenir esto. - -El código de la plantilla que descargaste en la [Sección de pre-requisitos](#prerequisites) ya tiene un archivo de ejemplo llamado `.env-example`. Renombra el archivo de ejemplo de `.env-example` a `.env` o crea una copia del archivo `.env-example` llamada `.env`. No has instalado dotenv aún, pero lo instalarás más adelante en esta guía de inicio rápido cuando ejecutes `bundle install`. **Nota:** Las guías de inicio rápido que hagan referencia a los pasos en ésta guía podrían incluir variables de ambiente adicionales en el archivo `.env-example`. Referencia la guía de inicio rápido para el proyecto que clonaste en GitHub para obtener orientación para configurar estas variables de ambiente adicionales. - -Necesitas agregar estas variables al archivo `.env`: - -* _`GITHUB_PRIVATE_KEY`_: Agerga la llave privada que [generaste y guardaste anteriormente](#step-3-save-your-private-key-and-app-id). Abre el archivo `.pem` con un editor de texto o utiliza la línea de comandos para mostrar el contenido del archivo: `cat path/to/your/private-key.pem`. Copia todo el contenido del archivo como el valor de `GITHUB_PRIVATE_KEY` en tu archivo `.env`. **Nota:** Ya que el archivo PEM tiene más de una línea de código, necesitarás encerrar el valor entre comillas como en el siguiente ejemplo. -* _`GITHUB_APP_IDENTIFIER`_: Utiliza la ID de app que anotaste en la sección anterior. -* _`GITHUB_WEBHOOK_SECRET`_: Agrega tu secreto de webhook. - -Aquí se muestra un ejemplo de archivo `.env`: - -``` -PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY----- -... -HkVN9... -... ------END DSA PRIVATE KEY-----" -GITHUB_APP_IDENTIFIER=12345 -GITHUB_WEBHOOK_SECRET=your webhook secret -``` - -### Paso 5. Revisar el código de la plantilla de la GitHub App - -Éste contiene código que todas las GitHub Apps necesitarán. Esta sección te muestra el código que ya existe en la plantilla de la GitHub App. No hay algún paso que necesites completar en esta sección. Si ya estás familiarizado con el código de la plantilla, puedes adelantarte al "[Paso 6. Iniciar el servidor](#step-6-start-the-server)". - -Abre el archivo `template_server.rb` en tu editor de texto favorito. Verás los comentarios a lo largo de este archivo, los cuales proporcionan contexto adicional para el código de la plantilla. Te recomendamos leer estos comentarios cuidadosamente, e incluso, agregar tus propios comentarios para complementar el código que escribas. - -En la parte superior del archivo verás `set :port 3000`, lo cual configura el puerto que se utiliza cuando inicias el servidor web para empatar con el puerto al cual redirigiste tus cargas útiles de webhook en el "[Paso 1. Iniciar un canal nuevo de Smee](#step-1-start-a-new-smee-channel)". - -El siguiente código que verás es la declaración `class GHApp < Sintra::Application`. Escribirás todo el código de tu GitHub App dentro de esta clase. - -Fuera de esta caja, la clase en la plantilla realiza lo siguiente: -* [Lee las variables de ambiente](#read-the-environment-variables) -* [Activa el inicio de sesión](#turn-on-logging) -* [Define un filtro del antes](#define-a-before-filter) -* [Define el gestor de ruta](#define-a-route-handler) -* [Define los métodos auxiliares](#define-the-helper-methods) - -#### Lee las variables de ambiente - -Lo primero que hace esta clase es leer las tres variables de ambiente que configuraste en el [Paso 4. Preparar el ambiente de ejecución](#step-4-prepare-the-runtime-environment)" y almacenarlas en variables para utilizarlas más adelante: - -``` ruby -# Expects that the private key in PEM format. Converts the newlines -PRIVATE_KEY = OpenSSL::PKey::RSA.new(ENV['GITHUB_PRIVATE_KEY'].gsub('\n', "\n")) - -# Your registered app must have a secret set. The secret is used to verify -# that webhooks are sent by GitHub. -WEBHOOK_SECRET = ENV['GITHUB_WEBHOOK_SECRET'] - -# The GitHub App's identifier (type integer) set when registering an app. -APP_IDENTIFIER = ENV['GITHUB_APP_IDENTIFIER'] -``` - -#### Activa el inicio de sesión - -Posteriormente, hay un bloqueo de código que habilita el inicio de sesión durante el desarrollo, el cual es el ambiente predeterminado en Sinatra. Este código activa el inicio de sesión a nivel de `DEBUG` para mostrar una salida útil en la terminal mientras desarrollas la app: - -``` ruby -# Turn on Sinatra's verbose logging during development -configure :development do - set :logging, Logger::DEBUG -end -``` - -#### Define un filtro del antes - -Sintatra utiliza [filtros de anterioridad](https://github.com/sinatra/sinatra#filters) que te permiten ejecutar el código antes del gestor de la ruta. El bloque `before` en la plantilla llama a cuatro [métodos auxiliares](https://github.com/sinatra/sinatra#helpers). La app de plantilla define estos métodos auxiliares en una [sección posterior](#define-the-helper-methods). - -``` ruby -# Before each request to the `/event_handler` route -before '/event_handler' do - get_payload_request(request) - verify_webhook_signature - authenticate_app - # Authenticate the app installation in order to run API operations - authenticate_installation(@payload) -end -``` - -#### Define el gestor de la ruta - -Se incluye una ruta vacía en el código de la plantilla. Este código gestiona las solicitudes de tipo `POST` hacia la ruta `/event_handler`. No escribirás este gestor de evento en esta guía de inicio rápido, sino que verás las otras [guías de inicio rápido](/apps/quickstart-guides/) para encontrar ejemplos de como extender esta app de planitlla. - -``` ruby -post '/event_handler' do - -end -``` - -#### Define los métodos auxiliares - -Los métodos auxiliares en esta plantilla hacen la mayoria del trabajo pesado. Se definen cuatro métodos auxiliares en esta sección del código. - -##### Gestionar la carga útil del webhok - -El primer método `get_payload_request` captura la carga útil del webhook y la convierte en formato JSON, lo cual hace mucho más fácil el acceder a los datos de la misma. - -##### Verificar la firma del webhook - -El segundo método `verify_webhook_signature` lleva a cabo la verificación de la firma del webhook para garantizar que GitHub generó el evento. Para aprender más acerca del código en el método auxiliar `verify_webhook_signature`, consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)". Si los webhooks son seguros, este método registrará todas las cárgas útiles en tu terminal. El código de registro es útil para verificar que tu servidor web esté trabajando, pero siempre lo puedes eliminar más adelante. - -##### Autenticarse como una GitHub App - -Para hacer llamadas a la API, estarás utilizando la [Biblioteca Octokit](http://octokit.github.io/octokit.rb/). Para que puedas hacer algo interesante con esta biblioteca necesitarás, o más bien, tu app necesitará autenticarse. GitHub Apps tiene dos métodos de autenticación: - -- Autenticación como una GitHub App utilizando un [Token Web de JSON (JWT)](https://jwt.io/introduction). -- Autenticación como una instalación específica de una GitHub App utilizando un token de acceso de instalación. - -Aprenderás cómo autenticarte como una instalación en la [siguiente sección](#authenticating-as-an-installation). - -El [autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) te permite hacer un par de cosas: - - * Puedes recuperar información administrativa de alto nivel sobre tu GitHub App. - * Puedes solicitar tokens de acceso para una instalación de la app. - -Por ejemplo, te podrías autenticar como una GitHub App para solicitar una lista de las cuentas (de organización y de persona) que han instalado tu app. Pero este método de autenticación no te permite hacer mucho con la API. Para acceder a los datos del repositorio y realizar operaciones en nombre de la instalación, necesitas autenticarte como una instalación. Para hacerlo, primero necesitarás autenticarte como una GitHub App para solicitar un token de acceso a la instalación. - -Antes de que puedas utilizar la biblioteca Octokit.rb para hacer llamados a la API, necesitarás inicializar un [cliente de Octokit](http://octokit.github.io/octokit.rb/Octokit/Client.html) autenticado como una GitHub App. ¡El método auxiliar `authenticate_app` hace exactamente eso! - -``` ruby -# Instantiate an Octokit client authenticated as a GitHub App. -# GitHub App authentication requires that you construct a -# JWT (https://jwt.io/introduction/) signed with the app's private key, -# so GitHub can be sure that it came from the app an not altererd by -# a malicious third party. -def authenticate_app - payload = { - # The time that this JWT was issued, _i.e._ now. - iat: Time.now.to_i, - - # JWT expiration time (10 minute maximum) - exp: Time.now.to_i + (10 * 60), - - # Your GitHub App's identifier number - iss: APP_IDENTIFIER - } - - # Cryptographically sign the JWT - jwt = JWT.encode(payload, PRIVATE_KEY, 'RS256') - - # Create the Octokit client, using the JWT as the auth token. - @app_client ||= Octokit::Client.new(bearer_token: jwt) -end -``` - -El código anterior genera un [Token Web de JSON (JWT)](https://jwt.io/introduction) y lo utiliza (junto con la llave privada de tu app) para inicializar el cliente de Octokit. GitHub revisa la autenticación de una solicitud verificando el token con la llave pública almacenada en la app. Para aprender más acerca de cómo funciona este código, consulta la sección "[Autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)". - -##### Autenticarse como una instalación - -Una _instalación_ se refiere a cualquier cuenta de usuario o de organización que tenga la app instalada. Aún si alguien instala la app en más de un repositorio, esto únicamente cuenta como una instalación, ya que toma lugar en la misma cuenta. El último método auxiliar `authenticate_installation` inicializa un [cliente de Octokit](http://octokit.github.io/octokit.rb/Octokit/Client.html) autenticado como una instalación. Este cliente de Octokit es lo que utilizarás para hacer llamadas autenticadas a la API. - -``` ruby -# Instantiate an Octokit client authenticated as an installation of a -# GitHub App to run API operations. -def authenticate_installation(payload) - installation_id = payload['installation']['id'] - installation_token = @app_client.create_app_installation_access_token(installation_id)[:token] - @installation_client = Octokit::Client.new(bearer_token: installation_token) -end -``` - -El método de Octokit [`create_app_installation_access_token`](http://octokit.github.io/octokit.rb/Octokit/Client/Apps.html#create_app_installation_access_token-instance_method) crea un token de instalación. Este método acepta dos argumentos: - -* Instalación (número entero): la ID de la instalación de una GitHub App -* Opciones (un hash, predeterminadamente es `{}`): un conjunto de opciones personalizables - -En cualquier momento en el que una GitHub App reciba un webhook, este incluirá un objeto de `installation` con una `id`. Utilizando el cliente autenticado como una GitHub App, pasarás la ID del método `create_app_installation_access_token` para generar un token de acceso para cada instalación. Ya que no estás pasando ninguna opción al método, ésta será un hash vacío predeterminadamente. Si te refieres a [los documentos](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation), podrás ver que la respuesta de `create_app_installation_access_token` incluye dos campos: `token` y `expired_at`. El código de la plantilla selecciona al token en la respuesta e inicializa un cliente de instalación. - -Una vez teniendo listo este métido, cada vez que tu app reciba una nueva carga útil de un webhook, este creará un cliente para la instalación que activó dicho evento. Este proceso de autenticación habilita a tu GitHub App para que trabaje para todas las instalaciones en cualquier cuenta. - -¡Ahora estás listo para comenzar a hacer llamadas a la API! - -### Paso 6. Inicia el servidor - -Tu app no _hace_ nada aún, pero en este punto, puedes ponerla a ejecutarse en el servidor. - -Mantén a Smee ejecutándose en la pestaña actual dentro de tu terminal. Abre una nueva pestaña y muévete al directorio en donde [clonaste el código de la plantilla de la app](#prerequisites) con el comando `cd`. El código de Ruby en este repositorio iniciará un servidor web de [Sinatra](http://sinatrarb.com/). Este código tiene algunas cuantas dependencias. Puedes instalarlas si ejecutas: - -```shell -$ gem install bundler -``` - -Seguido de: - -```shell -$ bundle install -``` - -Con las dependencias instaladas, puedes iniciar el servidor: - -```shell -$ ruby template_server.rb -``` - -Deberás ver una respuesta como: - -```shell -> == Sinatra (v2.0.3) has taken the stage on 3000 for development with backup from Puma -> Puma starting in single mode... -> * Version 3.11.2 (ruby 2.4.0-p0), codename: Love Song -> * Min threads: 0, max threads: 16 -> * Environment: development -> * Listening on tcp://localhost:3000 -> Use Ctrl-C to stop -``` - -Si ves un error, asegúrate de haber creado el archivo `.env` en el directorio que contiene a `template_server.rb`. - -Una vez que esté ejecutándose el servidor, puedes probarlo si vas a `http://localhost:3000` en tu buscador. Si la app funciona como se espera, verás una página de error útil: - -Página de error 404 de Sinatra - -¡Esto es bueno! Aunque es una página de error, es una página de error de _Sinatra_, lo cual significa que tu app está conectada con el servidor como lo esperabas. Estás viendo este mensaje porque no le has dado nada más que mostrar a la app. - -### Paso 7. Instala la app en tu cuenta - -Puedes probar que el servidor está escuchando a tu app si activas un evento para que lo reciba. Un evento simple con el que puedes hacer la prueba es instalar la app en tu cuenta de GitHub, la cual deberá enviar el evento [`installation`](/webhooks/event-payloads/#installation). Si la app lo recibe, deberás ver alguna salida en la pestaña de la terminal en donde iniciaste el `template_server.rb`. - -Para instalar la app, visita la [página de configuración de la app](https://github.com/settings/apps), elige tu app, y da clic en **Instalar App** en la barra lateral. Junto a tu nombre de usuario, da clic en **Instalar**. - -Se te solicitará si quieres instalar la app en todos los repositorios o solo en los seleccionados. Si no quieres instalar la app en _todos_ tus repositorios, ¡no pasa nada! Tal vez quieras crear un repositorio de entorno de pruebas para e instalar tu app ahí. - -Permisos de instalación de la aplicación - -Después de que des clic en **Instalar**, revisa la salida en tu terminal. Deberías encontrar algo como esto: - -```shell -> D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation -> D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ---- action created -> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0067 -> D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation -> D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ---- action created -> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/1.1" 200 2 0.0019 -``` - -¡Estas son buenas noticias! Esto significa que tu app recibió una notificación de que se instaló en tu cuenta de GitHub. Si ves algo como esto, tu app está ejecutándose en el servidor como lo esperabas. 🙌 - -Si no ves la salida, asegúrate de que Smee se esté ejecutando correctamente en otra pestaña de la terminal. Si necesitas reiniciar Smee, nota que también necesitarás _desinstalar_ y _reinstalar_ la app para enviar el evento de `installation` a tu app nuevamente y así ver la salida en la terminal. Si el problema no es con Smee, consulta la sección de "[Solución de problemas](#troubleshooting)" para darte otras ideas al respecto. - -Si te estás preguntando de dónde viene la salida de la terminal que ya mostramos, esto se encuentra escrito en el [código de la plantilla de la app](#prerequisites) dentro de `template_server.rb`. - -### Solución de problemas - -Aquí te mostramos algunos problemas comunes y algunas soluciones sugeridas. Si te encuentras con cualquier otro problema, puedes pedir ayuda o consejo en el {% data variables.product.prodname_support_forum_with_url %}. - -* **P:** Cuando trato de instalar el cliente de línea de comandos de Smee, me encuentro con el siguiente error: - - ```shell - > npm: command not found - ``` - - **R:** Parece que no instalaste npm. La mejor forma de isntalarlo es descargar el paquete de Node.js en https://nodejs.org y seguir las instrucciones de instalación para tu sistema. Se instalará npm junto con Node.js. - -* **P:** Cuando ejecuto el servidor me aparece el siguiente error: - - ```shell - > server.rb:38:in `initialize': Neither PUB key nor PRIV key: header too long (OpenSSL::PKey::RSAError) - ``` - - **R:** Probablemente no configuraste bien la variable de ambiente de tu llave privada. Tu variable de `GITHUB_PRIVATE_KEY` se debe ver así: - - ``` - PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY----- - ... - HkVN9... - ... - -----END RSA PRIVATE KEY-----" - ``` - - Revisa otra vez si copiaste la llave pública correcta en tu archivo `.env`. - -* **P:** Cuando ejecuto el servidor, produce un fallo con este error: - - ```shell - > Octokit::Unauthorized ... 401 - Bad credentials` - ``` - - **R:** Tal vez estés autenticado como una GitHub App pero no como una instalación. Asegúrate de seguir todos los pasos de la sección "[Autenticarte como una instalación](#authenticating-as-an-installation)", y utilizar la variable de instancia `@installation_client` (autenticado con un token de acceso de instalación) para las operaciones de tu API, y no así la variable de instancia `@app_client` (autenticado con un JWT). El `@app_client` solopuede recuperar información de alto nivel acerca de tu app y obtener tokens de acceso a la instalación. No puede más que esto en la API. - -* **P:** ¡Mi servidor no está escuchando los eventos! El cliente de Smee está ejecutándose en una ventana de la terminal, y estoy instalando la app en un repositorio con GitHub, pero no veo ninguna salida en la ventana de la terminal en donde estoy ejecutando el servidor. - - **R:** Tal vez no estés ejecutando el cliente de Smee, o tal vez no tengas el dominio correcto de Smee en la configuración de tu GitHub App. Primero revisa para asegurarte de que se esté ejecutando el cliente de Smee en la pestaña de la terminal. Si ese no es el problema, visita tu [página de configuración de la app](https://github.com/settings/apps) y revisa los campos que se muestran en el "[Paso 2. Registra una GitHub App nueva](#step-2-register-a-new-github-app)". Asegúrate que el dominio en esos campos empata con aquél que utilizaste en tu comando de `smee -u ` en el "[Paso 1. Iniciar un canal nuevo de Smee](#step-1-start-a-new-smee-channel)". - -* **P:** Veo un error 404 de `Octokit::NotFound` en mi salida de depuración: - ``` - 2018-12-06 15:00:56 - Octokit::NotFound - POST https://api.github.com/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token: - ``` - - **R:** Asegúrate que las variables en tu archivo `.env` son correctas. Asegúrate de que no has configurado variables idénticas en otros archivos de variable del ambiente como `bash_profile`. Puedes revisar las variables de ambiente que utiliza tu app si agregas una declaración de `puts` en el código de tu app y vuelves a ejecutar el código. Por ejemplo, para garantizar que tienes el conjunto de llaves correcto, podrías agregar `puts PRIVATE_KEY` al código de tu app: - - ``` - PRIVATE_KEY = OpenSSL::PKey::RSA.new(ENV['GITHUB_PRIVATE_KEY'].gsub('\n', "\n")) - puts PRIVATE_KEY - ``` - -### Conclusión - -Después de seguir esta guía, ¡habrás aprendido los fundamentos básicos para desarrollar GitHub Apps! Para revisar todo, debes: - -* Registrar una GitHub App nueva -* Utilizar Smee para recibir cargas útiles de los webhooks -* Ejecutar un servidor web simple a través de Sinatra -* Autenticarte como una GitHub App -* Autenticarte como una instalación - -### Pasos siguientes - -Ahora tienes una GitHub App ejecutándose en un servidor. Aún no hace nada especial, pero revisa en las otras [Guías de inicio rápido](/apps/quickstart-guides/) las formas en las que puedes personalizar la plantilla de GitHub App. diff --git a/translations/es-XL/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md b/translations/es-XL/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md deleted file mode 100644 index ddd6446bf2..0000000000 --- a/translations/es-XL/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md +++ /dev/null @@ -1,771 +0,0 @@ ---- -title: Crear pruebas de IC con la API de Verificaciones -intro: 'Crea un servidor de integración continua para ejecutar pruebas utilizando una {% data variables.product.prodname_github_app %} y la API de Verificaciones.' -redirect_from: - - /apps/quickstart-guides/creating-ci-tests-with-the-checks-api - - /developers/apps/creating-ci-tests-with-the-checks-api -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -### Introducción - -Esta guía te dará una introducción a las [GitHub Apps](/apps/) y a la [API de verificaciones](/v3/checks/), las cuales utilizarás para crear un servidor de Integración contínua (CI) que ejecute pruebas. - -La IC es una práctica de software que requiere código confirmado frecuente en un repositorio compartido. El código de confirmación generar errores de manera temprana frecuentemente, así como reduce la cantidad de código que necesita un desarrollador para hacer depuraciones cuando encuentra la fuente de un error. Las actualizaciones frecuentes de código facilitan también la fusión de cambios de diferentes miembros de un equipo de desarrollo de software. Esto es excelente para los desarrolladores, que pueden dedicar más tiempo a escribir código y menos tiempo a depurar errores o resolver conflictos de fusión. 🙌 - -Un servidor de IC hospeda código que ejecuta pruebas de IC, tal como los limpíadores de código (que revisan el formato del estilo), revisiones de seguridad, cobertura de código, y otras verificaciones contra las confirmaciones de código nuevas que hay en un repositorio. Los servidores de IC incluso pueden crear y desplegar código en los servidores de pruebas y en los productivos. Para encontrar algunas ejemplos de los tipos de pruebas de IC que puedes crear con una GitHub App, revisa las [apps de integración continua](https://github.com/marketplace/category/continuous-integration) que se encuentran disponibles en GitHub Marketplace. - -{% data reusables.apps.app-ruby-guides %} - -#### Resumen de la API de Verificaciones - -La [API de Verificaciones](/v3/checks/) te permite configurar las pruebas de IC que se ejecutan automáticamente contra cada confirmación de código en un repositorio. La API de Verificaciones reporta información detallada acerca de cada verificación en GitHub dentro de la pestaña de **Verificaciones** de las solicitudes de extracción. Con la API de verificaciones, puedes crear anotaciones con detalles adicionales para líneas específicas de código. Las anotaciones se encuentran visibles en la pestaña de **Verificaciones**. Cuando creas una anotación para un archivo que es parte de la solicitud de extracción, estas también se muestran en la pestaña **Archivos cambiados**. - -Un _conjunto de verificaciones_ es un grupo de _ejecuciones de verificación_ (pruebas de IC individuales). Tanto estos conjuntos como las ejecuciones contienen _estados_ que pueden visualizarse en la solicitud de extracción en GitHub. Puedes utilizar estados para determinar cuando una confirmación de código introduce errores. El utilizar estos estados con [ramas protegidas](/v3/repos/branches/) puede prevenir que las personas fusionen solicitudes de extracción prematuramente. Consulta la sección "[Habilitar las revisiones de estado requeridas](/articles/enabling-required-status-checks/)" para obtener más detalles. - -La API de Verificaciones envía el [evento de webhook `check_suite`](/webhooks/event-payloads/#check_suite) a todas las GitHub Apps que se instalan en un repositorio cada vez que se carga código nuevo a éste. Para recibir todas las acciones de los eventos de la API de Verificaciones, la app debe contar con el permiso `checks:write`. GitHub crea los eventos de `check_suite` automáticamente para las nuevas confirmaciones de código en un repositorio utilizando el flujo predeterminado, aunque puedes [Actualizar las preferencias del repositorio para los conjuntos de verificaciones](/v3/checks/suites/#update-repository-preferences-for-check-suites) si así lo quieres. Aquí te mostramos cómo funciona el flujo predeterminado: - -1. Cada que alguien carga código en el repositorio, GitHub envía el evento de `check_suite` con una acción de `requested` a todas las GitHub Apps que estén instaladas en el repositorio que tiene el permiso de `checks:write`. Este evento permite a las apps saber que se cargó código y que GitHub creó un nuevo conjunto de verificaciones automáticamente. -1. Cuando tu app recibe este evento, puede [agregar ejecuciones de verificacion](/v3/checks/runs/#create-a-check-run) a ese conjunto. -1. Tus ejecuciones de verificacion pueden incluir [anotaciones](/v3/checks/runs/#annotations-object) que se muestran en líneas de código específicas. - -**En esta guía, aprenderás cómo:** - -* Parte 1: Configurar el marco de trabajo para un servidor de IC utilizando la API de Verificaciones. - * Configurar una GitHub App como un servidor que recibe los eventos de la API de Verificaciones. - * Crear ejecuciones de verificacion nuevas para las pruebas de IC cuando un repositorio recibe cargas nuevas de confirmaciones. - * Re-ejecutar ejecuciones de verificación cuando un usuario solicita esta acción en GitHub. -* Parte 2: Compilar en el marco de trabajo del servidor de IC que creaste agregando una prueba de limpieza de IC. - * Actualizar una ejecución de verificación con un `status`, `conclusion`, y `output` details. - * Crear anotaciones en las líneas de código que muestra GitHub en las pestañas de **Verificaciones** y **Archivos Cambiados** de una solicitud de extracción. - * Arreglar automáticamente las recomendaciones del limpiador al exponer el botón "Arreglar esto" en la pestaña de **Verificaciones** de la solicitud de extracción. - -Para obtener una idea de lo que hará tu servidor de IC para la API de Verificaciones cuando completes este inicio rápido, revisa el siguiente demo: - -![Demostración de la guía de inicio rápido para el servidor de IC de la API de Verificaciones](/assets/images/github-apps/github_apps_checks_api_ci_server.gif) - -### Prerrequisitos - -Antes de que inicies, tal vez quieras familiarizarte con las [GitHub Apps](/apps/), los [Webhooks](/webhooks), y con la [API de Verificaciones](/v3/checks/), si aún no lo has hecho. Encontrarás más API en los [documentos de la API de REST](/v3/). La API de Verificaciones también se encuentra disponible para su uso en [GraphQL](/v4/), pero este inicio rápido se enfoca en REST. Consulta los objetos de [Conjuntos de Verificaciones](/v4/object/checksuite/) y [Ejecución de Verificación](/v4/object/checkrun/) de GraphQL para obtener más detalles. - -Utilizarás el [Lenguaje de Programación Ruby](https://www.ruby-lang.org/en/), el servicio de entrega de carga útil para el webhook de [Smee](https://smee.io/), la [biblioteca de Ruby Ocktokit.rb](http://octokit.github.io/octokit.rb/) para la API de REST de GitHub, y el [marco de trabajo web Sinatra](http://sinatrarb.com/) para crear tu aplicación de servidor de IC para la API de Verificaciones. - -No necesitas ser un experto en ninguna de estas herramientas o conceptos para completar este proyecto. Esta guía te mostrará todos los pasos requeridos a detalle. Antes de que comiences a crear pruebas de IC con la API de Verificaciones, necesitarás hacer lo siguiente: - -1. Clona el repositorio [Crear pruebas de IC con la API de Verificaciones](https://github.com/github-developer/creating-ci-tests-with-the-checks-api). - ```shell - $ git clone https://github.com/github-developer/creating-ci-tests-with-the-checks-api.git - ``` - - Dentro del directorio, encontrarás un archivo de nombre `template_server.rb` con el código de plantilla que utilizarás en este inicio rápido, y un archivo llamado `server.rb` con el código del proyecto completo. - -1. Sigue los pasos en la guía de inicio rápido "[Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/)" para configurar y ejecutar el servidor de la app. **Nota:** en vez de [clonar el repositorio de plantilla de GitHub App](/apps/quickstart-guides/setting-up-your-development-environment/#prerequisites), utiliza el archivo `template_server.rb` en el repositorio que clonaste en el paso anterior de esta guía de inicio rápido. - - Si ya has completado una guía de inicio rápido de GitHub App anteriormente, asegúrate de registrar una GitHub App _nueva_ y levanta un canal de Smee nuevo para utilizarlo con esta guía de inicio rápido. - - Consulta la sección [solución de problemas](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) si te encuentras con algún problema al configurar tu GitHub App de plantilla. - -### Parte 1. Crear la interface de la API de Verificaciones - -En esta parte, agregarás el código necesario para recibir eventos del webhook de `check_suite` y para las ejecuciones de verificación de creación y actualización. También aprenderás cómo crear ejecuciones de verificación cuando se re-solicite una verificación en GitHub. Al final de esta sección, podrás ver la ejecución de verificación que creaste en una solicitud de extracción de GitHub. - -En esta sección, tu ejecución de verificación no realizará ninguna verificación de código. Agregarás esa funcionalidad en la [Parte 2: Crear la prueba de IC de Octo RuboCop](#part-2-creating-the-octo-rubocop-ci-test). - -Ya deberías haber configurado el canal de Smee que reenviará las cargas útiles del webhook a tu servidor local. Tu servidor deberá estar funcionando y también estar conectado con la GitHub App que registraste e instalaste ene un repositorio de prueba. Si no has completado los pasos de "[Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/)", necesitarás hacerlo antes de que puedas continuar. - -¡Comencemos! Estos son los pasos que completarás en la Parte 1: - -1. [Actualizar los permisos de la app](#step-11-updating-app-permissions) -1. [Agregar la gestión de eventos](#step-12-adding-event-handling) -1. [Crear una ejecución de verificación](#step-13-creating-a-check-run) -1. [Actualizar una ejecución de verificación](#step-14-updating-a-check-run) - -### Paso 1.1. Actualizar los permisos de la app - -Cuando [registraste tu app por primera vez](#prerequisites), aceptaste los permisos predeterminados, lo que significa que tu app no tiene acceso a la mayoría de los recursos. Para este ejemplo, tu app necesitará el permiso de leer y escribir verificaciones. - -Para actualizar los permisos de tu app: - -1. Selecciona tu app de la [página de configuración de la app](https://github.com/settings/apps) y da clic en **Permisos & Webhooks** en la barra lateral. -1. En la sección de "Permisos", encuentra "Verificaciones"; y selecciona **Lectura & escritura** en el menú desplegable de acceso que está a un costado. -1. En la sección "Sucribirse a los eventos", selecciona **conjuntos de verificación** y **ejecución de verificación** para suscribirte a estos eventos. -{% data reusables.apps.accept_new_permissions_steps %} - -¡Genial! Tu app tiene permiso para realizar las tareas que quieres que haga. Ahora puedes agregar el código para que gestione los eventos. - -### Paso 1.2. Agregar la gestión de eventos - -Ahora que tu app está suscrita a los eventos de **conjuntos de verificaciones** y **ejecución de verificación**, comenzará a recibir los webhooks [`check_suite`](/webhooks/event-payloads/#check_suite) y [`check_run`](/webhooks/event-payloads/#check_run). GitHub envía las cargas útiles de los webhooks como solicitudes de tipo `POST`. Ya que reenviaste las cargas útiles del webhook de Smee a `http://localhost/event_handler:3000`, tu servidor recibirá las cargas útiles de la solicitud de `POST` en la ruta `post '/event_handler'`. - -Ya se incluye una ruta de `post '/event_handler'` vacía en el archivo `template_server.rb`, el cual descargaste en la sección de [prerrequisitos](#prerequisites). La ruta vacía se ve así: - -``` ruby - post '/event_handler' do - - # # # # # # # # # # # # - # ADD YOUR CODE HERE # - # # # # # # # # # # # # - - 200 # success status - end -``` - -Utiliza esta ruta para gestionar el evento `check_suite` agregando el siguiente código: - -``` ruby -# Get the event type from the HTTP_X_GITHUB_EVENT header -case request.env['HTTP_X_GITHUB_EVENT'] -when 'check_suite' - # A new check_suite has been created. Create a new check run with status queued - if @payload['action'] == 'requested' || @payload['action'] == 'rerequested' - create_check_run - end -end -``` - -Cada vento que envíe GitHub incluye un encabezado de solicitud que se llama `HTTP_X_GITHUB_EVENT`, el cual indica el tipo de evento en la solicitud de `POST`. Ahora mismo solo te interesan los eventos de tipo `check_suite`, los cuales se emiten cuando se crea un nuevo conjunto de verificaciones. Cada evento tiene un campo adicional de `action` que indica el tipo de acción que activó los eventos. Para`check_suite`, el campo `action` puede ser `requested`, `rerequested`, o `completed`. - -La acción `requested` solicita una ejecución de verificación cada vez que se carga el código al repositorio, mientras que la acción `rerequested` solicita que re-ejecutes una verificación para el código que ya existe en el repositorio. Ya que ambas acciones, `requested` y `rerequested` requieren crear una ejecución de verificación, llamarás a un ayudante llamado `create_check_run`. Vamos a escribir ese método ahora. - -### Paso 1.3. Crear una ejecución de verificación - -Agregarás este método nuevo como un [Ayudante de Sinatra](https://github.com/sinatra/sinatra#helpers) en caso de que quieras que otras rutas lo utilicen también. Debajo de `helpers do`, agrega este método de `create_check_run`: - -``` ruby -# Create a new check run with the status queued -def create_check_run - # # At the time of writing, Octokit does not support the Checks API yet, but - # it does provide generic HTTP methods you can use: - # /v3/checks/runs/#create-a-check-run - check_run = @installation_client.post( - "repos/#{@payload['repository']['full_name']}/check-runs", - { - # This header allows for beta access to Checks API - accept: 'application/vnd.github.antiope-preview+json', - # The name of your check run. - name: 'Octo RuboCop', - # The payload structure differs depending on whether a check run or a check suite event occurred. - head_sha: @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'] - } - ) -end -``` - -Este código llama a la terminal "[Crear una ejecución de verificación](/v3/checks/runs/#create-a-check-run)" utilizando el [Método HTTP de `publicación`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#post-instance_method). Este método toma dos parámetros: la URL de la terminal y los parámetros de entrada del método. - -Solo se requieren dos parámetros de entrada para crear una ejecución de flujo de trabajo: `name` y `head_sha`. Utilizaremos a [Rubocop](https://rubocop.readthedocs.io/en/latest/) para implementar la prueba de IC más adelante en esta guía de inicio rápido, y esto es por lo que se utiliza el nombre "Octo Rubocop" aquí, pero puedes elegir cualquier nombre que quieras para la ejecución de verificación. - -Ahora mismo, solo estás proporcionando los parámetros requeridos para echar a andar la funcionalidad básica, pero actualizarás la ejecución de verificación más adelante mientras recolectes más información acerca de la ejecución de verificación. Predeterminadamente, GitHub configura el `Estado` como `queued`. - -GitHub Crea una ejecución de flujo de trabajo para un SHA de confirmación específico, y es por esto que el `head_sha` es un parámetro requerido. Puedes encontrar el SHA de la confirmación en la carga útil del webhook. Aunque ahora mismo solo estás creando una ejecución de verificación para el evento `check_suite`, es bueno saber que el `head_sha` se incluye tanto en el objeto de `check_suite` como en el de `check_run` dentro de las cargas útiles del evento. - -En el código anterior, estás utilizando el [operador ternario](https://ruby-doc.org/core-2.3.0/doc/syntax/control_expressions_rdoc.html#label-Ternary+if), el cual funciona como una declaración `if/else`, para verificar si la carga útil contiene un objeto `check_run`. Si lo tiene, lees el `head_sha` desde el objeto `check_run`, de lo contrario lo leerías desde el objeto de `check_suite`. - -Para probar este código, reinicia el servidor desde tu terminal: - -```shell -$ ruby template_server.rb -``` - -{% data reusables.apps.sinatra_restart_instructions %} - -Ahora abre una solicitud de extracción en el repositorio en donde instalaste tu app. Tu app deberá responder creando una ejecución de verificación en tu solicitud de extracción. Da clic en la pestaña de **Verificaciones** y deberías ver algo como esto: - -![Ejecución de verificación en cola](/assets/images/github-apps/github_apps_queued_check_run.png) - -Si ves otras apps en la pestaña de verificaciones, significa que tienes otras apps instaladas en tu repositorio las cuales cuentan con acceso de **Lectura & escritura** en las verificaciones y que están suscritas a los eventos de **conjuntos de verificaciones** y de **ejecución de verificación**. - -¡Genial! Le has dicho a GitHub que cree una ejecución de verificación. Puedes ver junto al icono amarillo que el estado de esta ejecución de verificación se configuró como `queued`. A continuación, querrás esperar a que GitHub cree la ejecución de verificación y actualice su estado. - -### Paso 1.4. Actualizar una ejecución de verificación - -Cuando tu método de `create_check_run` se ejecuta, éste solicita a GitHub crear una ejecución de verificación nueva. Cuando GitHub termine de crear la ejecución de verificación, recibirás un evento de webhook de `check_run` con la acción como `created`. Este evento es tu señal para comenzar a ejecutar la verificación. - -Necesitas actualizar tu gestor de eventos para buscar la acción que se encuentra como `created`. Mientras actualizas el gestor de eventos, puedes agregar una condicional para la acción que se encuentra como `rerequested`. Cuando alguien re-ejecuta una sola prueba en GitHub al dar clic en el botón de "Re-ejecutar", GitHub envía a tu app el evento de ejecución de verificación que está como `rerequested`. Cuando una ejecución de verificación se pone como `rerequested`, necesitarás iniciar el proceso desde cero y crear una ejecución de verificación nueva. - -Para incluir una condición para el evento de `check_run` en la ruta de `post '/event_handler'`, agrega el siguiente código debajo de `case request.env['HTTP_X_GITHUB_EVENT']`: - -``` ruby -when 'check_run' - # Check that the event is being sent to this app - if @payload['check_run']['app']['id'].to_s === APP_IDENTIFIER - case @payload['action'] - when 'created' - initiate_check_run - when 'rerequested' - create_check_run - end - end -``` - -GitHub envía todos los eventos de las ejecuciones de verificación que se encuentran como `created` a cada app instalada en un repositorio, la cual tenga las permisiones de verificación necesarias. Esto significa que tu app recibirá las ejecuciones de verificación que creen otras apps. Una ejecución de verificación que se encuentre como `created` es un poco diferente de un conjunto de verificaciones que estén como `requested` o `rerequested` y que GitHub envía únicamente a las aplicaciones a las cuales se solicita que ejecuten una verificación. El código anterior busca la ID de aplicación de la ejecución de verificación. Esto filtra todas las ejecuciones de verificación para otras apps en el repositorio. - -A continuación, escribirás el método de `initiate_check_run`, que es donde actualizarás el estado de la ejecución de verificación y donde te prepararás para lanzar tu prueba de IC. - -En esta sección no vas a lanzar la prueba de IC aún, pero te mostraremos cómo actualizar el estado de la ejecución de verificación de `queued` a `pending` y después de `pending` a `completed` para ver el flujo general de una ejecución de verificación. En la "[Parte 2: Crear la prueba de IC de Octo RuboCop](#part-2-creating-the-octo-rubocop-ci-test)", agregarás el código responsable de llevar a cabo la prueba de IC. - -Vamos a crear el método `initiate_check_run` y a actualizar el estado de la ejecución de verificación. Agrega el siguiente código a la sección de ayudantes: - -``` ruby -# Start the CI process -def initiate_check_run - # Once the check run is created, you'll update the status of the check run - # to 'in_progress' and run the CI process. When the CI finishes, you'll - # update the check run status to 'completed' and add the CI results. - - # Octokit doesn't yet support the Checks API, but it does provide generic - # HTTP methods you can use: - # /v3/checks/runs/#update-a-check-run - updated_check_run = @installation_client.patch( - "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", - { - accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API - name: 'Octo RuboCop', - status: 'in_progress', - started_at: Time.now.utc.iso8601 - } - ) - - # ***** RUN A CI TEST ***** - - # Mark the check run as complete! - updated_check_run = @installation_client.patch( - "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", - { - # This header is necessary for beta access to Checks API - accept: 'application/vnd.github.antiope-preview+json', - name: 'Octo RuboCop', - status: 'completed', - conclusion: 'success', - completed_at: Time.now.utc.iso8601 - } - ) -end -``` - -El código anterior llama a la terminal "[Actualizar una ejecución de verificación](/v3/checks/runs/#update-a-check-run)" de la API utilizando el [Método HTTP`patch`](http://octokit.github.io/octokit.rb/Octokit/Connection.html#patch-instance_method) para actualizar la ejecución de verificación que ya creaste. - -Te explicamos lo que hace este código. Primero, actualiza el estado de la ejecución de verificación a `in_progress` y configura la hora `started_at` de acuerdo con la hora actual. En la [Parte 2](#part-2-creating-the-octo-rubocop-ci-test) de esta guía de inicio rápido, agregarás código que lanza una prueba de IC real bajo `***** RUN A CI TEST *****`. Por el momento, dejarás esta sección como un marcador de posición para que el código subsecuente simplemente estimule el éxito del proceso de IC y que todas las pruebas pasen. Por último, el código actualiza el estado de la ejecución de verificación nuevamente como `completed`. - -Notarás en los documentos de "[Actualizar una ejecución de verificación](/v3/checks/runs/#update-a-check-run)" que, cuando proporcionas un estado de `completed`, se requieren los parámetros de `conclusion` y `completed_at`. La `conclusion` resume el resultado de una ejecución de verificación, la cual se puede mostrar como `success`, `failure`, `neutral`, `cancelled`, `timed_out`, o `action_required`. Vas a configurar la conclusión como `success`, la hora de `completed_at` según la hora actual, y el estado como `completed`. - -También puedes proporcionar más detalles sobre lo que está haciendo tu verificación, pero eso lo abordaremos en la siguiente sección. Vamos a probar este código nuevamente volviendo a ejecutar `template_server.rb`: - -```shell -$ ruby template_server.rb -``` - -Diríjete a tu solicitud de extracción abierta y da clic en la pestaña **Verificaciones**. Da clic en el botón "Re-ejecutar todo" en la esquina superior derecha. Deberías ver que la ejecución de verificación cambia de `pending` a `in_progress` y termina en `success`: - -![Ejecución de verificación completada](/assets/images/github-apps/github_apps_complete_check_run.png) - -### Parte 2. Crear la prueba de IC de Octo RuboCop - -[RuboCop](https://rubocop.readthedocs.io/en/latest/) es un formateador y limpiador de código para Ruby. Revisa el código de Ruby para garantizar que se apegue a la "[Guía de Estilo de Ruby](https://github.com/rubocop-hq/ruby-style-guide)". RuboCop tiene tres funciones prncipales: - -* Limpiar para revisar el estilo del código -* Formatear el código -* Reemplazar las capacidades de limpieza nativas de Ruby utilizando `ruby -w` - -Ahora que tienes la interface que se ha creado para recibir eventos de la API de verificaciones y para crear ejecuciones de verificción, puedes crear una ejecución de verificación que implemente una prueba de IC. - -Tu app ejecutará RuboCop en el servidor CI y creará ejecuciones de verificación (en este caso, pruebas de IC) que reporten los resultados que RuboCop reporta a GitHub. - -La API de Verificaciones te permite reportar detalles enriquecidos acerca de cada ejecución de verificación, incluyendo los estados, imágenes, resúmenes, y las acciones solicitadas. - -Las anotaciones son información acerca de líneas de código específicas en un repositorio. Una anotación te permite identificar y visualizar las partes exactas del código para las cuales quieres mostrar información adicional. Esa puede ser cualquier información: por ejemplo, un comentario, un error, o una advertencia. Esta guía rápida utiliza anotaciones para visualizar los errores de RuboCop. - -Para tener una ventaja sobre las acciones solicitadas, los desarrolladores de apps pueden crear botones en la pestaña de **Verificaciones** de las solicitudes de extracción. Cuando alguien da clic en alguno de estos botones, dicho clic envía un evento de `requested_action` `check_run` a la GitHub App. El desarrollador de la app puede configurar íntegramente la acción que ésta toma. Esta guía de inicio rápido te mostrará cómo agregar un botón que permitirá a los usuarios solicitar que RuboCop corrija los errores que encuentre. RuboCop es compatible con la corrección automática de errores utilizando una opción en la línea de comandos, y configurarás la `requested_action` para aprovechar esta opción. - -¡Comencemos! Estos son los pasos que tendrás que completar en esta sección: - -1. [Agregar un archivo de Ruby](#step-21-adding-a-ruby-file) -1. [Clonar el repositorio](#step-22-cloning-the-repository) -1. [Ejecutar RuboCop](#step-23-running-rubocop) -1. [Recolectar los errores de RuboCop](#step-24-collecting-rubocop-errors) -1. [Actualizar la ejecución de verificación con los resultados de la prueba de IC](#step-25-updating-the-check-run-with-ci-test-results) -1. [Corregir automáticamente los errores de RuboCop](#step-26-automatically-fixing-rubocop-errors) -1. [Tips de seguridad](#step-27-security-tips) - -### Paso 2.1. Agregar un archivo de Ruby - -Puedes pasar archivos específicos o directorios completos para que los revise RuboCop. En esta guía de inicio rápido, ejecutarás a RuboCop en un directorio completo. Ya que RuboCop únicamente revisa el código de Ruby, querrás que por lo menos un archivo de Ruby en tu repositorio contenga errores. El archivo de ejemplo que te proporcionamos a continuación contiene unos cuantos errores. Agrega este archivo de Ruby de ejemplo al repositorio en donde se instaló tu app (asegúrate de nombrar este archivo con una extensión `.rb`, como `myfile.rb`, por ejemplo.): - -```ruby -# The Octocat class tells you about different breeds of Octocat -class Octocat - def initialize(name, *breeds) - # Instance variables - @name = name - @breeds = breeds - end - - def display - breed = @breeds.join("-") - - puts "I am of #{breed} breed, and my name is #{@name}." - end -end - -m = Octocat.new("Mona", "cat", "octopus") -m.display -``` - -### Paso 2.2. Clonar el repositorio - -RuboCop se encuentra disponible como una utilidad de línea de comandos. Eso significa que tu GitHub App necesitará clonar una copia local del repositorio en el servidor de IC para que RuboCop analice los archivos. Para ejecutar las operaciones de Git en tu app de Ruby, puedes usar la gema [ruby-git](https://github.com/ruby-git/ruby-git). - -El `Gemfile` en el repositorio `building-a-checks-api-ci-server` ya incluye la gema ruby-git, y lo instalaste cuando ejecutaste `bundle install` en los [pasos de pre-requisitos](#prerequisites). Para utilizar la gema, agrega este código a la parte superior de tu archivo `template_server.rb`: - -``` ruby -require 'git' -``` - -Tu app necesita el permiso de lectura para "contenido de repositorio" si quieres que clone un repositorio. Más adelante en esta guía de inicio rápido, necesitarás cargar contenido a GitHub, lo cual requiere el permiso de escritura. Continúa y configura el permiso de "contenido de repositorio" de tu app como **Lectura & escritura** ahora mismo para que no tengas que actualizarlo nuevamente más adelante. Para actualizar los permisos de tu app: - -1. Selecciona tu app de la [página de configuración de la app](https://github.com/settings/apps) y da clic en **Permisos & Webhooks** en la barra lateral. -1. En la sección de "Permisos", encuentra el "contenido del repositorio", y selecciona **Lectura & escritura** en el menú desplegable de "Acceso" que está a un costado. -{% data reusables.apps.accept_new_permissions_steps %} - -Para clonar un repositorio utilizando los permisos de tu GitHub App, puedes utilizar el token de instalación de la misma (`x-access-token:`), el cual se muestra en el siguiente ejemplo: - -```shell -git clone https://x-access-token:@github.com//.git -``` - -El código anterior clona un repositorio a través de HTTP. Éste necesita el nombre íntegro del repositorio, lo cual incluye al propietario del mismo (usuario u organización) y el nombre de éste. Por ejemplo, el repositorio [octocat Hello-World](https://github.com/octocat/Hello-World) tiene un nombre completo que se ve así: `octocat/hello-world`. - -Después de que tu app clone el repositorio, necesita extraer los últimos cambios al código y verificar una ref específica de Git. El código que hará todo esto encajará perfectamente en su propio método. Para llevar a cabo estas operaciones, el método necesita el nombre y nombre completo del repositorio y la ref de salida. La ref puede ser el SHA de una confirmación, una rama, o una etiqueta. Agrega el siguiente método a la sección del método del ayudante en `template_server.rb`: - -``` ruby -# Clones the repository to the current working directory, updates the -# contents using Git pull, and checks out the ref. -# -# full_repo_name - The owner and repo. Ex: octocat/hello-world -# repository - The repository name -# ref - The branch, commit SHA, or tag to check out -def clone_repository(full_repo_name, repository, ref) - @git = Git.clone("https://x-access-token:#{@installation_token.to_s}@github.com/#{full_repo_name}.git", repository) - pwd = Dir.getwd() - Dir.chdir(repository) - @git.pull - @git.checkout(ref) - Dir.chdir(pwd) -end -``` - -El código anterior utiliza la gema `ruby-git` para clonar el repositorio utilizando el token de instalación de la app. Este código clona el código en el mismo directorio en el que esté `template_server.rb`. Para ejecutar los comandos de Git en el repositorio, el código necesita cambiar el directorio del repositorio. Antes de cambiar de directorio, el código almacena el directorio de trabajo actual en una variable (`pwd`) para recordar a dónde regresar antes de salir del método de `clone_repository`. - -Desde el directorio del repositorio, este código obtiene y fusiona los últimos cambios (`@git.pull`), revisa la ref (`@git.checkout(ref)`), y luego cambia el directorio de vuelta al directorio de trabajo original (`pwd`). - -Ahora tienes un método que clona un repositorio y revisa una ref. A continuación, necesitarás agregar código para obtener los parámetros de entrada requeridos y llamar al nuevo método de `clone_repository`. Agrega el siguiente código debajo del comentario `***** RUN A CI TEST *****` en tu método `initiate_check_run` del ayudante: - -``` ruby -# ***** RUN A CI TEST ***** -full_repo_name = @payload['repository']['full_name'] -repository = @payload['repository']['name'] -head_sha = @payload['check_run']['head_sha'] - -clone_repository(full_repo_name, repository, head_sha) -``` - -El código anterior obtiene el nombre completo del repositorio y el SHA de encabezado de la confirmación desde la carga útil del webhook de `check_run`. - -### Paso 2.3. Ejecutar RuboCop - -¡Genial! Estás clonando el repositorio y creando ejecuciones de verificación al utilizar tu servidor de IC. Ahora te meterás en los detalles más minusciosos del [Limpiador de RuboCop](https://rubocop.readthedocs.io/en/latest/basic_usage/#rubocop-as-a-code-style-checker) y de las [Anotaciones de la API de Verificaciones](/v3/checks/runs/#create-a-check-run). - -El siguiente código ejecuta RuboCop y guarda los errores de estilo en el código con un formato JSON. Agrega el código siguiente debajo de la llamada a `clone_repository` que agregaste en el [paso anterior](#step-22-cloning-the-repository) y sobre el código que actualiza la ejecución de verificación para completarse. - -``` ruby -# Run RuboCop on all files in the repository -@report = `rubocop '#{repository}' --format json` -logger.debug @report -`rm -rf #{repository}` -@output = JSON.parse @report -``` - -Este código utiliza RuboCop en todos los archivos dentro del directorio del repositorio. La opción `--format json` es una manera útil de guardar una copia de los resultados que se han limpiado en un formato que pueda analizar la máquina. Consulta los [Documentos de RuboCop](https://rubocop.readthedocs.io/en/latest/formatters/#json-formatter) para obtener más detalles y un ejemplo del formato en JSON. - -Ya que este código almacena los resultados de RuboCop en una variable de `@report`, puede eliminar la salida del repositorio con seguridad. Este código también analiza el JSON para que puedas acceder fácilmente a las claves y valores en tu GitHub App utilizando la variable `@output`. - -{% note %} - -**Nota:** El comando que se utiliza para eliminar el repositorio (`rm -rf`) no puede deshacerse. Consulta el [Paso 2.7. Tips de seguridad](#step-27-security-tips) para aprender cómo verificar los webhooks para que no inyecten comandos maliciosos que puedan utilizarse para eliminar un directorio diferente de aquél que tu app busca eliminar. Por ejemplo, si un mal actor envía un webhook con el nombre de repositorio `./`, tu app eliminaría el directorio raíz. 😱 si por alguna razón _no_ estás utilizando el método `verify_webhook_signature` (el cual se incluye en `template_server.rb`) para validar al emisor del webhook, asegúrate de revisar que el nombre del repositorio es válido. - -{% endnote %} - -Puedes probar que este código funcione y ver los errores que reporta RuboCop en la salida de depuración de tu servidor. Inicia el servidor `template_server.rb` nuevamente y crea una solicitud de extracción nueva en el repositorio en donde estás probando tu app: - -```shell -$ ruby template_server.rb -``` - -Deberías ver los errores de limpieza en la salida de depuración, aunque no se imprimen con formato. Puedes utilizar una herramienta web como [JSON formatter](https://jsonformatter.org/) para dar formato a tu salida de JSON como en esta salida de errores de limpieza formateada que tenemos de ejemplo: - -```json -{ - "metadata": { - "rubocop_version": "0.60.0", - "ruby_engine": "ruby", - "ruby_version": "2.3.7", - "ruby_patchlevel": "456", - "ruby_platform": "universal.x86_64-darwin18" - }, - "files": [ - { - "path": "Octocat-breeds/octocat.rb", - "offenses": [ - { - "severity": "convention", - "message": "Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.", - "cop_name": "Style/StringLiterals", - "corrected": false, - "location": { - "start_line": 17, - "start_column": 17, - "last_line": 17, - "last_column": 22, - "length": 6, - "line": 17, - "column": 17 - } - }, - { - "severity": "convention", - "message": "Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.", - "cop_name": "Style/StringLiterals", - "corrected": false, - "location": { - "start_line": 17, - "start_column": 25, - "last_line": 17, - "last_column": 29, - "length": 5, - "line": 17, - "column": 25 - } - } - ] - } - ], - "summary": { - "offense_count": 2, - "target_file_count": 1, - "inspected_file_count": 1 - } -} -``` - -### Paso 2.4. Recolectar los errores de RuboCop - -La variable `@output` contiene los resultados analizados de JSON para el reporte de RuboCop. Tal como se muestra anteriormente, los resultados contienen una sección de `summary` que tu código puede ut utilizar rápidamente para determinar si hay algún error. El siguiente código configurará la ejecución de verificación en `success` cuando no haya errores reportados. RuboCop reporta errores para cada archivo en la matriz de `files`, así que, si hay errores, necesitarás extraer algunos datos del objeto del archivo. - -La API de Verificaciones te permite crear anotaciones para líneas de código específicas. Cuando creas o actualizas una ejecución de verificación, puedes agregar anotaciones. En esta guía de inicio rápido estás [actualizando la ejecución de verificación](/v3/checks/runs/#update-a-check-run) con anotaciones. - -La API de Verificaciones limita la cantidad de anotaciones a un máximo de 50 por solilcitud de API. Para crear más de 50 anotaciones, tienes que hacer solicitudes múltiples a la terminal [Actualizar una ejecución de verificación](/v3/checks/runs/#update-a-check-run). Por ejemplo, para crear 105 anotaciones necesitarías llamar a la terminal [Actualizar una ejecución de verificación](/v3/checks/runs/#update-a-check-run) tres veces. Las primeras dos contarían por 50 anotaciones cada una, y la tercera incluiría las cinco restantes. Cada vez que actualices la ejecución de verificación, se adjuntan las anotaciones a la lista de anotaciones existente para la ejecución de verificación. - -Una ejecución de verificación espera encontrar las anotaciones en una matriz de objetos. Cada objeto de anotación debe incluir `path`, `start_line`, `end_line`, `annotation_level`, y `message`. RuboCop también proporciona la `start_column` y `end_column`, para que puedas incluir estos parámetros opcionales en la anotación. Las anotaciones únicamente son compatibles con `start_column` y `end_column` en la misma línea. Consulta la documentación sobre la referencia del [objeto `annotations`](/v3/checks/runs/#annotations-object-1) para obtener más detalles. - -Extraerás la información requerida de RuboCop que necesites para crear cada anotación. Adjunta el siguiente código a aquél que agregaste en la [sección anterior](#step-23-running-rubocop): - -``` ruby -annotations = [] -# You can create a maximum of 50 annotations per request to the Checks -# API. To add more than 50 annotations, use the "Update a check run" API -# endpoint. This example code limits the number of annotations to 50. -# See /v3/checks/runs/#update-a-check-run -# for details. -max_annotations = 50 - -# RuboCop reports the number of errors found in "offense_count" -if @output['summary']['offense_count'] == 0 - conclusion = 'success' -else - conclusion = 'neutral' - @output['files'].each do |file| - - # Only parse offenses for files in this app's repository - file_path = file['path'].gsub(/#{repository}\//,'') - annotation_level = 'notice' - - # Parse each offense to get details and location - file['offenses'].each do |offense| - # Limit the number of annotations to 50 - next if max_annotations == 0 - max_annotations -= 1 - - start_line = offense['location']['start_line'] - end_line = offense['location']['last_line'] - start_column = offense['location']['start_column'] - end_column = offense['location']['last_column'] - message = offense['message'] - - # Create a new annotation for each error - annotation = { - path: file_path, - start_line: start_line, - end_line: end_line, - start_column: start_column, - end_column: end_column, - annotation_level: annotation_level, - message: message - } - # Annotations only support start and end columns on the same line - if start_line == end_line - annotation.merge({start_column: start_column, end_column: end_column}) - end - - annotations.push(annotation) - end - end -end -``` - -Este código limita la cantidad total de anotaciones a 50. Pero puedes modificarlo para actualizar la ejecución de verificación para cada lote de 50 anotaciones. El código anterior incluye la variable `max_annotations` que configura el límite a 50, el cual se utiliza en el bucle que itera a través de las faltas. - -Cuando la `offense_count` es de cero, la prueba de IC se muestra como `success`. Si hay errores, este código configura la conclusión como `neutral` para prevenir los errores estrictamente implementados desde los limpiadores de código. Pero puedes cambiar la conclusión a `failure` si quisieras garantizar que el conjunto de verificaciones falle cuando existan errores de limpieza. - -Cuando se reportan los errores, el código anterior itera a través de la matriz de `files` en el reporte de RuboCop. Para cada archivo, extrae la ruta del mismo y configura el nivel de anotcación en `notice`. Puedes incluso ir más allá y especificar ls niveles de advertencia para cada tipo de [RuboCop Cop](https://rubocop.readthedocs.io/en/latest/cops/), pero para simplificar todo aún más en esta guía rápida, todos los errores se configurarán en un nivel de `notice`. - -Este código también itera a través de cada error en la matriz de `offenses` y recolecta la ubicación de la falta y el mensaje de error. Después de extraer la información requerida, el código crea una anotación para cada error y lo almacena en la matriz de `annotations`. Ya que las anotaciones solo son compatibles con las columnas de inicio y fin en la misma línea, `start_column` y `end_column` se agregarán únicamente al objeto `annotation` si los valores iniciales y finales de la línea son los mismos. - -Este código aún no crea una anotación para la ejecución de verificación. Agregarás dicho código en la siguiente sección. - -### Paso 2.5. Actualizar la ejecución de verificación con los resultados de la prueba de IC - -Cada ejecución de verificación de GitHub contiene un objeto de `output` que incluye un `title`, `summary`, `text`, `annotations`, y `images`. El `summary` y `title` son los únicos parámetros requeridos para la `output`, pero no ofrecen muchos detalles por sí mismos, así que esta guía de inicio rápido agrega `text` y `annotations` también. Este código no agrega una imagen, pero ¡no dudes en agregarla si así lo deseas! - -Para el `summary`, este ejemplo utiliza la información de resumen de RuboCop y agrega algunas líneas nuevas (`\n`) para formatear la salida. Puedes personalizar lo que agregas en el parámetro de `text`, pero este ejemplo configura el parámetro `text` en la versión de RuboCop. Para configurar tanto `summary` como `text`, adjunta este código a aquél que agregaste en la [sección anterior](#step-24-collecting-rubocop-errors): - -``` ruby -# Updated check run summary and text parameters -summary = "Octo RuboCop summary\n-Offense count: #{@output['summary']['offense_count']}\n-File count: #{@output['summary']['target_file_count']}\n-Target file count: #{@output['summary']['inspected_file_count']}" -text = "Octo RuboCop version: #{@output['metadata']['rubocop_version']}" -``` - -Ahora tienes toda la información que necesitas para actualizar tu ejecución de verificación. En la [primera parte de esta guía de inicio rápido](#step-14-updating-a-check-run), agregaste este código para configurar el estado de la ejecución de verificación como `success`: - -``` ruby -# Mark the check run as complete! -updated_check_run = @installation_client.patch( - "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", - { - accept: 'application/vnd.github.antiope-preview+json', # This header is necessary for beta access to Checks API - name: 'Octo RuboCop', - status: 'completed', - conclusion: 'success', - completed_at: Time.now.utc.iso8601 - } -) -``` - -Necesitarás actualizar este código para utilizar la variable `conclusion` que configures con base en los resultados de RuboCop (ya sea como `success` o como `neutral`). Puedes actualizar el código con lo siguiente: - -``` ruby -# Mark the check run as complete! And if there are warnings, share them. -updated_check_run = @installation_client.patch( - "repos/#{@payload['repository']['full_name']}/check-runs/#{@payload['check_run']['id']}", - { - accept: 'application/vnd.github.antiope-preview+json', - name: 'Octo RuboCop', - status: 'completed', - conclusion: conclusion, - completed_at: Time.now.utc.iso8601, - output: { - title: 'Octo RuboCop', - summary: summary, - text: text, - annotations: annotations - }, - actions: [{ - label: 'Fix this', - description: 'Automatically fix all linter notices.', - identifier: 'fix_rubocop_notices' - }] - } -) -``` - -Ahora que estás configurando una conclusión con base en el estado de la prueba de IC y has agregado la salida de los resultados de RuboCop, !has creado una prueba de IC! Felicidades. 🙌 - -El código anterior también agrega una característica a tu servidor de IC, la cual se llama [acciones solicitadas](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/) a través del objeto `actions`. {% if currentVersion == "free-pro-team@latest" %}(Nota que esto no tiene relación con [GitHub Actions](/actions).) {% endif %}Las acciones que se solicitan agregan un botón en la pestaña **Verificaciones** en GitHub que permite a las personas solicitar que la ejecución de verificación tome acciones adicionales. Tu app puede configurar la acción adicional totalmente. Por ejemplo, ya que RuboCop tiene una característica para corregir automáticamente los errores que encuentre en el código de Ruby, tu servidor de IC puede utilizar un botón de acciones solicitadas para ayudar a que las personas soliciten correcciónes de errores automáticas. Cuando alguien da clic en el botón, la app recibe el evento de `check_run` con una acción de `requested_action`. Cada acción solicitada tiene un `identifier` que la app utiliza para determinar en qué botón se dio clic. - -El código anterior aún no hace que RuboCop corrija los errores automáticamente. Eso lo agregarás en la siguiente sección. Pero primero, observa la prueba de IC que acabas de crear iniciando nuevamente el servidor `template_server.rb` y creando una nueva solicitud de extracción: - -```shell -$ ruby template_server.rb -``` - -Las anotaciones se mostrarán en la pestaña de **Verificaciones**. - -![Anotaciones de la ejecución de verificación en la pestaña de verificaciones](/assets/images/github-apps/github_apps_checks_annotations.png) - -Nota el botón de "Arreglar esto" que creaste al agregar la acción solicitada. - -![Botón de acción solicitada para la ejecución de verificación](/assets/images/github-apps/github_apps_checks_fix_this_button.png) - -Si las anotaciones se relacionan con un archivo que ya se incluya en la solicitud de extracción, estas también se mostrarán en la pestaña de **Archivos cambiados**. - -![Anotaciones de la ejecución de verificación en la pestaña de archivos cambiados](/assets/images/github-apps/github_apps_checks_annotation_diff.png) - -### Paso 2.6. Corregir automáticamente los errores de RuboCop - -Si has llegado hasta aquí, !excelente! 👏 Ya creaste una prueba de IC. En esta sección vas a agregar una característica más que utiliza a RuboCop para corregir automáticamente los errores que encuentre. Ya agregaste el botón de "Corregir esto" en la [sección anterior](#step-25-updating-the-check-run-with-ci-test-results). Ahora agregarás el código para gestionar el evento de ejecución de verificación `requested_action` que se activa cuando alguien da clic en dicho botón. - -La herramienta de RuboCop [ofrece](https://rubocop.readthedocs.io/en/latest/basic_usage/#auto-correcting-offenses) la opción de línea de comandos `--auto-correct` para corregir automáticamente los errores que encuentre. Cuado utilizas la característica de `--auto-correct`, se aplican las actualizaciones en los archivos locales del servidor. Necesitarás cargar los cambios a GitHub después de que RuboCop haga su magia. - -Para cargar un repositorio, tu app debe tener permisos de escritura para "contenido de repositorio". Estos permisos los configuraste en el [Paso 2.2. Clonar el repositorio](#step-22-cloning-the-repository) como **Lectura & escritura**, así que estás listo. - -Para confirmar los archivos, Git debe saber qué [nombre de usuario](/articles/setting-your-username-in-git/) y [correo electrónico](/articles/setting-your-commit-email-address-in-git/) asociará con la confirmación. Agrega dos variables de ambiente adicionales en tu archivo `.env` para almacenar las configuraciones de nombre(`GITHUB_APP_USER_NAME`) y de correo electrónico (`GITHUB_APP_USER_EMAIL`). Tu nombre puede ser aquél de tu app y la dirección de correo electrónico puede ser cualquiera para este ejemplo. Por ejemplo: - -``` -GITHUB_APP_USER_NAME=Octoapp -GITHUB_APP_USER_EMAIL=octoapp@octo-org.com -``` - -Ya que hayas actualizado tu archivo `.env` con el nombre y correo electrónico del autor y del confirmante, estarás listo para agregar código para que lea las variables de ambiente y configur los ajustes de Git. Pronto agregarás este código. - -Cuando alguien da clic en el botón "Arreglar esto", tu app recibe el [webhook de ejecución de verificación](/webhooks/event-payloads/#check_run) con el tipo de acción `requested_action`. - -En el [Paso 1.4. Actualizar una ejecución de verificación](#step-14-updating-a-check-run) actualizaste tu `event_handler` para que gestionara la búsqueda de acciones en el evento `check_run`. Ya tienes una declaración de caso para gestionar los tipos de acción `created` y `rerequested`. - -``` ruby -when 'check_run' - # Check that the event is being sent to this app - if @payload['check_run']['app']['id'].to_s === APP_IDENTIFIER - case @payload['action'] - when 'created' - initiate_check_run - when 'rerequested' - create_check_run - end -end -``` - -Agrega otra declaración de `when` después del caso `rerequested` para gestionar el evento `rerequested_action`: - -``` ruby -when 'requested_action' - take_requested_action -``` - -Este código llamará aun método nuevo que gestionará todos los eventos `requested_action` para tu app. Agrega el siguiente método a la sección de métodos del ayudante para tu código: - -``` ruby -# Handles the check run `requested_action` event -# See /webhooks/event-payloads/#check_run -def take_requested_action - full_repo_name = @payload['repository']['full_name'] - repository = @payload['repository']['name'] - head_branch = @payload['check_run']['check_suite']['head_branch'] - - if (@payload['requested_action']['identifier'] == 'fix_rubocop_notices') - clone_repository(full_repo_name, repository, head_branch) - - # Sets your commit username and email address - @git.config('user.name', ENV['GITHUB_APP_USER_NAME']) - @git.config('user.email', ENV['GITHUB_APP_USER_EMAIL']) - - # Automatically correct RuboCop style errors - @report = `rubocop '#{repository}/*' --format json --auto-correct` - - pwd = Dir.getwd() - Dir.chdir(repository) - begin - @git.commit_all('Automatically fix Octo RuboCop notices.') - @git.push("https://x-access-token:#{@installation_token.to_s}@github.com/#{full_repo_name}.git", head_branch) - rescue - # Nothing to commit! - puts 'Nothing to commit' - end - Dir.chdir(pwd) - `rm -rf '#{repository}'` - end -end -``` - -El código anterior clona un repositorio tal como aquél que agregaste en el [Paso 2.2. Clonar el repositorio](#step-22-cloning-the-repository). Una declaración de tipo `if` revisará que el identificación de la acción solicitada empate con el identificador del botón de RuboCop (`fix_rubocop_notices`). Cuando empaten, el código clonará el repositorio, configurará el correo electrónico y nombre de usuario de Git, y ejecutará RuboCop con la opción `--auto-correct`. La opción `--auto-correct` aplica los cambios a los archivos locales del servidor de IC automáticamente. - -Los archivos se cambian de manera local, pero aún necesitarás cargarlos a GitHub. Utilizarás la gema útil `ruby-git` nuevamente para confirmar todos los archivos. Git tiene un comando único que organiza todos los archivos que se han modificado o borrado y los confirma: `git commit -a`. Para hacerlo lo mismo utilizando `ruby-git`, el código anterior utiliza el método `commit_all`. Después, el código carga los archivos confirmados a GitHub utilizando el token de instalación y utilizando el mismo método de autenticación que el comando `clone` de Git. Por último, elimina el directorio del repositorio para garantizar que el directorio de trabajo está preparado para el siguiente evento. - -¡Listo! El código que escribiste ahora completa tu servidor de IC para la API de Verificaciones. 💪 Reinicia nuevamente tu servidor de `template_server.rb` y crea una solicitud de extracción nueva: - -```shell -$ ruby template_server.rb -``` - -{% data reusables.apps.sinatra_restart_instructions %} - -Esta vez, da clic en el botón "Arreglar esto" para corregir automáticamente los errores que RuboCop encontró desde la pestaña de **Verificaciones**. - -En la pestaña de **Confirmaciones** encontrarás una confirmación nueva con el nombre de usuario que configuraste en los ajustes de Git. Puede que necesites actualizar tu buscador para ver esto. - -![Confirmación nueva para corregir los avisos de Octo RuboCop automáticamente](/assets/images/github-apps/github_apps_new_requested_action_commit.png) - -Ya que se cargó una confirmación nueva al repositorio, verás un conjunto de verificaciones nuevo para Octo RuboCop en la pestaña de **Verificaciones**. Pero esta vez no habrá errores, ya que RuboCop los arregló todos. 🎉 - -![Sin errores en los conjuntos de verificaciones o en la ejecución de verificación](/assets/images/github-apps/github_apps_checks_api_success.png) - -Puedes encontrar todo el código de la app que acabas de crear en el archivo `server.rb` dentro del repositorio [Crear pruebas de IC con la API de Verificaciones](https://github.com/github-developer/creating-ci-tests-with-the-checks-api). - -### Paso 2.7. Tips de seguridad - -El código de la GitHub App de plantilla ya tiene un método para verificar las cargas útiles de webhook entrantes para garantizar que vengan de una fuente confiable. Si no estás validando las cargas útiles de los webhooks, necesitarás garantizar que, cuando los nombres de repositorio se incluyan en éstas, el webhook no contenga comandos arbitrarios que puedan usarse con malas intenciones. El siguiente código valida que el nombre del repositorio solo contenga caracteres alfabeticos latinos, guiones y guiones bajos. Para proporcionarte un ejemplo completo, el código integral de `server.rb` que encuentras disponible en el [repositorio acompañante](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) para esta guía de inicio rápido incluye tanto el método para validar las cargas útiles de webhooks entrantes como esta verificación que revisa el nombre del repositorio. - -``` ruby -# This quickstart example uses the repository name in the webhook with -# command-line utilities. For security reasons, you should validate the -# repository name to ensure that a bad actor isn't attempting to execute -# arbitrary commands or inject false repository names. If a repository name -# is provided in the webhook, validate that it consists only of latin -# alphabetic characters, `-`, and `_`. -unless @payload['repository'].nil? - halt 400 if (@payload['repository']['name'] =~ /[0-9A-Za-z\-\_]+/).nil? -end -``` - -### Solución de problemas - -Aquí te mostramos algunos problemas comunes y algunas soluciones sugeridas. Si te encuentras con cualquier otro problema, puedes pedir ayuda o consejo en el {% data variables.product.prodname_support_forum_with_url %}. - -* **P:** Mi app no está cargando código a GitHub. !No veo las correcciones que RuboCop hace automáticamente! - - **R:** Asegúrate de que tienes permisos de **Lectura & escritura** para "Contenido de repositorio", y de que estás clonando el repositorio con tu token de instalación. Consulta el [Paso 2.2. Clonar el repositorio](#step-22-cloning-the-repository) para encontrar más detalles. - -* **P:** Veo un error en la salida de depuración `template_server.rb` relacionada con el clonado de mi repositorio. - - **R:** Si ves el siguiente error, no has borrado la salida del repositorio en uno o ambos de los métodos de `initiate_check_run` o `take_requested_action`: - - ```shell - 2018-11-26 16:55:13 - Git::GitExecuteError - git clone '--' 'https://x-access-token:v1.9b2080277016f797074c4debd350745f4257f8dd@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds' 2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.: - ``` - - Compara tu código con el archivo `server.rb` para garantizar que tienes el mismo código en tus métodos de `initiate_check_run` y de `take_requested_action`. - -* **P:** Las ejecuciones de verificación no se están mostrando en la pestaña de "Verificaciones" en GitHub. - - **R:** Reinicia Smee y vuelve a ejecutar tu servidor de `template_server.rb`. - -* **P:** No veo el botón de "Re-ejecutar todo" en la pestaña de "Verificaciones" de GitHub. - - **R:** Reinicia Smee y vuelve a ejecutar tu servidor de `template_server.rb`. - -### Conclusión - -Después de seguir esta guía, ¡aprendiste los puntos básicos de utilizar la API de Verificaciones para crear un servidor de IC! Para revisar todo, debes: - -* Configuraste tu servidor para recibir eventos de la API de Verificaciones y creaste ejecuciones de verificación. -* Utilizaste RuboCop para verificar el código en los repositorios y creaste anotaciones para los errores. -* Iplementaste una accion solicitada que corrijió automáticamente los errores de limpieza. - -### Pasos siguientes - -Aquí tienes algunas ideas para lo que puedes hacer después: - -* Actualmente, el botón "Arreglar esto" siempre se muestra. Actualiza el código que escribiste para que muestre el botón de "Arreglar esto" únicamente cuando RuboCop encuentre errores. -* Si prefieres que RuboCop no confirme archivos directamente en la rama principal, puedes actualizar el código a [crear una solicitud de extracción](/v3/pulls/#create-a-pull-request) con una rama nueva basada en la rama principal. diff --git a/translations/es-XL/content/developers/apps/guides/index.md b/translations/es-XL/content/developers/apps/guides/index.md deleted file mode 100644 index f52685d841..0000000000 --- a/translations/es-XL/content/developers/apps/guides/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Guías -intro: 'Aprende cómo utilizar la API de {% data variables.product.prodname_dotcom %} con tu app, integración continua, y cómo compilar con las apps.' -redirect_from: - - /apps/quickstart-guides -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps -children: - - /using-the-github-api-in-your-app - - /using-content-attachments - - /creating-ci-tests-with-the-checks-api ---- - diff --git a/translations/es-XL/content/developers/apps/guides/using-content-attachments.md b/translations/es-XL/content/developers/apps/guides/using-content-attachments.md deleted file mode 100644 index f3eb5b1cbe..0000000000 --- a/translations/es-XL/content/developers/apps/guides/using-content-attachments.md +++ /dev/null @@ -1,180 +0,0 @@ ---- -title: Utilizar adjuntos de contenido -intro: Los adjuntos de contenido permiten que una GitHub App proporcione más información en GitHub para las URL que vinculan a los dominios registrados. GitHub interpreta la información que proporciona la app bajo la URL en el cuerpo o el comentario de un informe de problemas o de una solicitud de extracción. -redirect_from: - - /apps/using-content-attachments - - /developers/apps/using-content-attachments -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% data reusables.pre-release-program.content-attachments-public-beta %} - -### Acerca de los adjuntos de contenido - -Una GitHub App puede registrar dominios que activarán los eventos de `content_reference`. Cuando alguien incluye una URL que vincule a un dominio registrado en el cuerpo o en el comentario de un informe de problemas o de una solicitud de extracción, la app recibe el [webhook de `content_reference`](/webhooks/event-payloads/#content_reference). Puedes utilizar los adjuntos de contenido para proporcionar visualmente más contenido o datos para la URL que se agregó a un informe de problemas o a una solicitud de extracción. La URL debe estar completamente calificada, comenzando ya sea con `http://` o con `https://`. Las URL que sean parte de un enlace de markdown se ignorarán y no activarán el evento de `content_reference`. - -Antes de que puedas utilizar la API de {% data variables.product.prodname_unfurls %}, necesitarás configurar las referencias de contenido para tu GitHub App: -* Concede los permisos de `Read & write` a tu app para "Referencias de contenido". -* Registra hasta 5 dominios válidos y accesibles al público cuando configures el permiso de "Referencias de contenido". No utilices direcciones IP cuando configures dominios con referencias de contenido. Puedes registrar un nombre de dominio (ejemplo.com) o un subdominio (subdominio.ejemplo.com). -* Suscribe a tu app al evento de "Referencia de contenido". - -Una vez que tu app se instale en un repositorio, los comentarios de solicitudes de extracción o de informes de problemas en éste, los cuales contengan URL para tus dominios registrados, generarán un evento de referencia de contenido. La app debe crear un adjunto de contenido en las seis horas siguientes a la publicación de la URL de referencia de contenido. - -Los adjuntos de contenido no actualizarán las URL retroactivamente. Esto solo funciona para aquellas URL que se agerguen a las solicitudes de extracción o informes de problemas después de que configuras la app utilizando los requisitos descritos anteriormente y que después alguien instale la app en su repositorio. - -Consulta la sección "[Crear una GitHub App](/apps/building-github-apps/creating-a-github-app/)" o "[Editar los permisos de las GitHub Apps](/apps/managing-github-apps/editing-a-github-app-s-permissions/)" para encontrar los pasos necesarios para configurar los permisos de las GitHub Apps y las suscripciones a eventos. - -### Implementar el flujo de los adjuntos de contenido - -El flujo de los adjuntos de contenido te muestra la relación entre la URL en el informe de problemas o en la solicitud de extracción, el evento de webhook de `content_reference`, y la terminal de la API de REST que necesitas para llamar o actualizar dicho informe de problemas o solicitud de extracción con información adicional: - -**Paso 1.** Configura tu app utilizando los lineamientos descritos en la sección [Acerca de los adjuntos de contenido](#about-content-attachments). También puedes utilizar el [ejemplo de la App de Probot](#example-using-probot-and-github-app-manifests) para iniciar con los adjuntos de contenido. - -**Paso 2.** Agrega la URL para el dominio que registraste a un informe de problemas o solicitud de extracción. Debes utilizar una URL totalmente calificada que comience con `http://` o con `https://`. - -![URL que se agregó a un informe de problemas](/assets/images/github-apps/github_apps_content_reference.png) - -**Paso 3.** Tu app recibirá el [webhook de `content_reference`](/webhooks/event-payloads/#content_reference) con la acción `created`. - -``` json -{ - "action": "created", - "content_reference": { - "id": 17, - "node_id": "MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA5", - "reference": "errors.ai" - }, - "repository": {...}, - "sender": {...}, - "installation": { - "id": 371641, - "node_id": "MDIzOkludGVncmF0aW9uSW5zdGFsbGF0aW9uMzcxNjQx" - } -} -``` - -**Paso 4.** La app utiliza la `id` de `content_reference`, para [Crear un adjunto de contenido](/v3/apps/installations/#create-a-content-attachment) utilizando la API de REST. También necesitas la `id` de la `installation` para autenticarte como una [Instalación de una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). - -{% data reusables.pre-release-program.corsair-preview %} -{% data reusables.pre-release-program.api-preview-warning %} - -El parámetro `body` puede contener lenguaje de markdown: - - ```shell - curl -X POST \ - https://api.github.com/content_references/1512/attachments \ - -H 'Accept: application/vnd.github.corsair-preview+json' \ - -H 'Authorization: Bearer $INSTALLATION_TOKEN' \ - -d '{ - "title": "[A-1234] Error found in core/models.py file", - "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()" - }' - ``` - -Para obtener más información acerca de crear un token de instalación, consulta la sección "[Autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". - -**Paso 5.** Verás como el nuevo adjunto de contenido aparece bajo el enlace en un comentario de una solicitud de extracción o informe de problemas: - -![Contenido adjunto a una referencia en un informe de problemas](/assets/images/github-apps/github_apps_content_reference_attachment.png) - -### Utilizar adjuntos de contenido en GraphQL -Proporcionamos la `node_id` en el evento de [Webhook de `content_reference` ](/webhooks/event-payloads/#content_reference) para que puedas referirte a la mutación `createContentAttachment` en la API de GraphQL. - -{% data reusables.pre-release-program.corsair-preview %} -{% data reusables.pre-release-program.api-preview-warning %} - -Por ejemplo: - -``` graphql -mutation { - createContentAttachment(input: { - contentReferenceId: "MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA1", - title: "[A-1234] Error found in core/models.py file", - body:"You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()" - }) { - contentAttachment { - ... on ContentAttachment { - id - title - body - } - } - } -} -``` -cURL de ejemplo: - -```shell -curl -X "POST" "https://api.github.com/graphql" \ - -H 'Authorization: Bearer $INSTALLATION_TOKEN' \ - -H 'Accept: application/vnd.github.corsair-preview+json' \ - -H 'Content-Type: application/json; charset=utf-8' \ - -d $'{ - "query": "mutation {\\n createContentAttachment(input:{contentReferenceId: \\"MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA1\\", title:\\"[A-1234] Error found in core/models.py file\\", body:\\"You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n\self.save()\\"}) {\\n contentAttachment {\\n id,\\n title,\\n body\\n }\\n }\\n}" -}' -``` - -Para obtener más información aacerca de `node_id`, consulta la sección "[Utilizar las Node ID Globales](/v4/guides/using-global-node-ids/)". - -### Ejemplo de uso con Probot y Manifiestos de GitHub Apps - -Para configurar rápidamente una GitHub App que pueda utilizar la API de {% data variables.product.prodname_unfurls %}, puedes utilizar el [Probot](https://probot.github.io/). Consulta la sección "[Crear Github Apps a partir de un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para aprender cómo el Probot utiliza los Manifiestos de las GitHub Apps. - -Para crear una App de Probot, sigue estos pasos: - -1. [Genera una GitHub App Nueva](https://probot.github.io/docs/development/#generating-a-new-app). -2. Abre el proyecto que creaste y personaliza la configuración en el archivo `app.yml`. Suscríbete al evento `content_reference` y habilita los permisos de escritura de `content_references`: - - ``` yml - - default_events: - - content_reference - # The set of permissions needed by the GitHub App. The format of the object uses - # the permission name for the key (for example, issues) and the access type for - # the value (for example, write). - # Valid values are `read`, `write`, and `none` - default_permissions: - content_references: write - - content_references: - - type: domain - value: errors.ai - - type: domain - value: example.org - ``` - -3. Agrega este código al archivo `index.js` para gestionar los eventos de `content_reference` y llamar a la API de REST: - - ``` javascript - module.exports = app => { - // Your code here - app.log('Yay, the app was loaded!') - app.on('content_reference.created', async context => { - console.log('Content reference created!', context.payload) - // Call the "Create a content reference" REST endpoint - await context.github.request({ - method: 'POST', - headers: { accept: 'application/vnd.github.corsair-preview+json' }, - url: `/content_references/${context.payload.content_reference.id}/attachments`, - // Parameters - title: '[A-1234] Error found in core/models.py file', - body: 'You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\nself.save()' - }) - }) - } - ``` - -4. [Ejecuta la GitHub App localmente](https://probot.github.io/docs/development/#running-the-app-locally). Navega a [localhost:3000](http://localhost:3000) y da clic en el botón de **Registrar una GitHub App**: - - ![Registrar una GitHub App de Probot](/assets/images/github-apps/github_apps_probot-registration.png) - -5. Instala la app en un repositorio de prueba. -6. Crea un informe de problemas en tu repositorio de prueba. -7. Agrega un comentario en el informe de problemas que abriste, el cual incluya la URL que configuraste en el archivo `app.yml`. -8. Revisa el comentario del informe de problemas y verás una actualización que se ve así: - - ![Contenido adjunto a una referencia en un informe de problemas](/assets/images/github-apps/github_apps_content_reference_attachment.png) diff --git a/translations/es-XL/content/developers/apps/guides/using-the-github-api-in-your-app.md b/translations/es-XL/content/developers/apps/guides/using-the-github-api-in-your-app.md deleted file mode 100644 index e41e3470ce..0000000000 --- a/translations/es-XL/content/developers/apps/guides/using-the-github-api-in-your-app.md +++ /dev/null @@ -1,236 +0,0 @@ ---- -title: Utilizar la API de GitHub en tu app -intro: Aprende cómo configurar tu app para que escuche los eventos y utilice la biblioteca de Octokit para hacer operaciones de la API de REST. -redirect_from: - - /apps/building-your-first-github-app/ - - /apps/quickstart-guides/using-the-github-api-in-your-app - - /developers/apps/using-the-github-api-in-your-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -### Introducción - -Esta guía te ayudará a crear una GitHub App y a ejecutarla en un servidor. La app que crees agregará una etiqueta a todos los informes de problemas nuevos que estén abiertos en el repositorio en donde ésta se instale. - -Este proyecto te mostrará cómo hacer lo siguiente: - -* Programar tu app para escuchar eventos -* Utilizar la biblioteca de Octokit para hacer operaciones de la API de REST - -{% data reusables.apps.app-ruby-guides %} - -Una vez que hayas seguido estos pasos, estarás listo para desarrollar otros tipos de integraciones utilizando la suite completa de las API de GItHub. {% if currentVersion == "free-pro-team@latest" %}Puedes revisar los ejemplos exitosos de estas aplicaciones en [GitHub Marketplace](https://github.com/marketplace) y en [Compatible con GitHub](https://github.com/works-with).{% endif %} - -### Prerrequisitos - -Puede que te sea útil tener un entendimiento básico de lo siguiente: - -* [GitHub Apps](/apps/about-apps) -* [Webhooks](/webhooks) -* [El lenguaje de programación Ruby](https://www.ruby-lang.org/en/) -* [Las API de REST](/v3) -* [Sinatra](http://sinatrarb.com/) - -Pero puedes seguir esta guía sin importar tu nivel de experiencia. ¡Colocaremos enlaces para la información que requieras en cada fase! - -Antes de que comiences, necesitas hacer lo siguiente: - -1. Clona el repositorio [Utilizar la API de GitHub en tu app](https://github.com/github-developer/using-the-github-api-in-your-app). - ```shell - $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git - ``` - - Dentro del directorio, encontrarás un archivo de nombre `template_server.rb` con el código de plantilla que utilizarás en este inicio rápido, y un archivo llamado `server.rb` con el código del proyecto completo. - -1. Sigue los pasos en la guía de inicio rápido "[Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/)" para configurar y ejecutar el servidor `template_server.rb` de la app. Si ya habías completado alguna guía de inicio rápido para las GitHub Apps diferente a aquella de [Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/), deberás registrar una GitHub App _nueva_ e iniciar un canal de Smee nuevo para utilizarlo con esta guía. - - Esta guía de inicio rápido incluye el mismo código de `template_server.rb` que aquella llamada [Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/). **Nota:** Mientras sigues la guía de inicio rápido de [Configurar tu ambiente de desarrollo](/apps/quickstart-guides/setting-up-your-development-environment/) asegúrate de utilizar los archivos de proyecto que se incluyen en el repositorio [Utilizar la API de GitHub para tu app](https://github.com/github-developer/using-the-github-api-in-your-app). - - Consulta la sección [Solución de problemas](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) si te encuentras con algún problema al configurar tu GitHub App de plantilla. - -### Crear la app - -Ahora que estás familiarizado con el código de `template_server.rb`, vas a crear el código que agregará la etiqueta `needs-response` automáticamente a todos los informes de problemas que estén abiertos en el repositorio en donde se instale la app. - -El archivo `template_server.rb` contiene el código de la plantilla de la app que no se ha personalizado aún. En este archivo, verás código de marcador de posición para gestionar eventos de webhook y algún otro tipo de código para inicializar el cliente de Octokit.rb. - -{% note %} - -**Nota:** El `template_server.rb` contiene muchos comentarios de código que complementan esta guía y explican detalles técnicos adicionales. Es posible que le resulte útil leer los comentarios de ese archivo ahora, antes de continuar con esta sección, para obtener resumen de cómo funciona el código. - -El código personalizado final que crees al terminar esta guía se proporciona en el archivo [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Pero, ¡intenta esperar hasta que termines para darle un vistazo! - -{% endnote %} - -Estos son los pasos que tendrás que completar para crear tu primer GitHub App: - -1. [Actualizar los permisos de la app](#step-1-update-app-permissions) -2. [Agregar la gestión de eventos](#step-2-add-event-handling) -3. [Crear una etiqueta nueva](#step-3-create-a-new-label) -4. [Agregar la gestión de etiquetas](#step-4-add-label-handling) - -### Paso 1. Actualizar los permisos de la app - -Cuando [registraste tu app por primera vez](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), aceptaste los permisos predeterminados, lo que significa que tu app no tiene acceso a la mayoría de los recursos. Para este ejemplo, tu app necesitará el permiso para leer los informes de problemas y escribir etiquetas. - -Para actualizar los permisos de tu app: - -1. Selecciona tu app de la [página de configuración de la app](https://github.com/settings/apps) y da clic en **Permisos & Webhooks** en la barra lateral. -1. En la sección de "Permisos", encuentra "Informes de problemas"; y selecciona **Lectura & Escritura** en el menú desplegable de "Acceso" que está a un costado. La descripción dice que esta opción otorga acceso tanto a informes de problemas como a etiquetas, que es exactamente lo que buscas. -1. En la sección "Suscribirse a los eventos", selecciona **Informes de problemas** para suscribirte a este evento. -{% data reusables.apps.accept_new_permissions_steps %} - -¡Genial! Tu app tiene permiso para realizar las tareas que quieres que haga. Ahora puedes agregar el código para que funcione. - -### Paso 2. Agregar la gestión de eventos - -Lo primero que tiene que hacer tu app es escuchar si se han abierto informes de problemas nuevos. Ahora que te has suscrito alevento de **Informes de problemas**, comenzarás a recibir el webhook [`issues`](/webhooks/event-payloads/#issues), el cual se activa cuando ocurren algunas acciones relacionadas con los informes de problemas. Puedes filtrar este tipo de evento para la acción específica que quieres en tu código. - -GitHub envía las cargas útiles de los webhooks como solicitudes de tipo `POST`. Ya que reenviaste las cargas útiles del webhook de Smee a `http://localhost/event_handler:3000`, tu servidor recibirá las cargas útiles de la solicitud de `POST` en la ruta `post '/event_handler'`. - -Ya se incluye una ruta de `post '/event_handler'` vacía en el archivo `template_server.rb`, el cual descargaste en la sección de [prerrequisitos](#prerequisites). La ruta vacía se ve así: - -``` ruby - post '/event_handler' do - - # # # # # # # # # # # # - # ADD YOUR CODE HERE # - # # # # # # # # # # # # - - 200 # success status - end -``` - -Utiliza esta ruta para gestionar el evento `issues` agregando el siguiente código: - -``` ruby -case request.env['HTTP_X_GITHUB_EVENT'] -when 'issues' - if @payload['action'] === 'opened' - handle_issue_opened_event(@payload) - end -end -``` - -Cada vento que envíe GitHub incluye un encabezado de solicitud que se llama `HTTP_X_GITHUB_EVENT`, el cual indica el tipo de evento en la solicitud de `POST`. Ahora mismo solo te interesan los tipos de evento `issues`. Cada evento tiene un campo adicional de `action` que indica el tipo de acción que activó los eventos. Para los `issues`, el campo de `action` puede estar como `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, o `reopened`. - -Para probar tu gestor de eventos, intenta agregar un método auxiliar temporal. Lo actualizarás más adelante cuando [Agregues la gestión de etiquetas](#step-4-add-label-handling). Por ahora, agrega el siguiente código dentro de la sección `helpers do` del mismo. Puedes poner el método nuevo arriba o abajo de cualquiera de los métodos auxiliares. El orden no importa. - -``` ruby -def handle_issue_opened_event(payload) - logger.debug 'An issue was opened!' -end -``` - -Este método recibe una carga útil de evento formateada con JSON a manera de argumento. Esto significa que puedes analizar la carga útil en el método y profundizar hacia cualquier tipo de datos específico que necesites. Podría parecerte útil el inspeccionar totalmente la carga útil en algún memoento: intenta cambiar el mensaje `logger.debug 'An issue was opened!` a `logger.debug payload`. La estructura de la carga útil que ves deberá coincidir con lo que [se muestra en los documentos del evento de webhook `issues`](/webhooks/event-payloads/#issues). - -¡Genial! Es momento de probar los cambios. - -{% data reusables.apps.sinatra_restart_instructions %} - -En tu buscador, visita el repositorio en donde instalaste tu app. Abre un informe de problemas nuevo en este repositorio. El informe de problemas puede decir lo que gustes. Esto es solo para hacer la prueba. - -Cuando regreses a ver tu terminal, deberás ver un mensaje en la salida, el cual diga, `An issue was opened!` ¡Felicidades! Acabas de agregar un gestor de eventos a tu app. 💪 - -### Paso 3. Crear una etiqueta nueva - -Bien, tu app puede decirte qué informes de problemas están abiertos. Ahora querrás que agregue la etiqueta `needs-response` a cualquier informe de problemas nuevo que esté abierto en el repositorio en donde se instale. - -Antes de que puedas _agregar_ la etiqueta a alguna parte, necesitarás _crear_ la etiqueta personalizada en tu repositorio. Solo necesitas hacer esto una vez. Para fines de esta guía, crea la etiqueta manualmente en GitHub. En tu repositorio, da clic en **Informes de problemas**, luego en **Etiquetas**, y después da clic en **Etiqueta nueva**. Nombra la nueva etiqueta como `needs-response`. - -{% tip %} - -**Tip**: ¿No sería genial si tu app pudiera crear la etiqueta mediante programación? Pues ¡[Puede hacerlo](/v3/issues/labels/#create-a-label)! Intenta agregar tú mismo el código para que lo haga después de que completes los pasos en esta guía. - -{% endtip %} - -Ahora que existe la etiqueta, puedes programar tu app para que utilice la API de REST para [agregar la etiqueta a cualquier informe de problemas recién abierto](/v3/issues/labels/#add-labels-to-an-issue). - -### Paso 4. Agregar la gestión de etiquetas - -Felicidades—llegste al último paso: agregar la gestión de etiquetas a tu app. Para esta tarea, querrás utilizar la [Biblioteca Ocktokit.rb de Ruby](http://octokit.github.io/octokit.rb/). - -En los documentos de Octokit, encuentra una lista de los [métodos de las etiquetas](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). El método que necesitarás usar es [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method). - -Una vez de regreso en el `template_server.rb`, encuentra el método que definiste previamente: - -``` ruby -def handle_issue_opened_event(payload) - logger.debug 'An issue was opened!' -end -``` - -Los documentos de [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) te muestran que necesitarás pasar tres argumentos en este método: - -* Repo (secuencia en formato `"owner/name"`) -* Número de informe de problemas (número entero) -* Etiquetas (matriz) - -Puedes analizar la carga útil para obtener tanto el repo y el número de informe de problemas. Ya que el nombre de la etiqueta siempre será el mismo (`needs-response`), podrás pasarlo como una secuencia fijada en la matriz de etiquetas. Al juntar estas piezas, tu método actualizado se podría ver más o menos así: - -``` ruby -# When an issue is opened, add a label -def handle_issue_opened_event(payload) - repo = payload['repository']['full_name'] - issue_number = payload['issue']['number'] - @installation_client.add_labels_to_an_issue(repo, issue_number, ['needs-response']) -end -``` - -¡Intenta abrir un informe de problemas nuevo en tu repositorio de prueba y ver lo que pasa! Si no pasa nada de inmediato, intenta actualizarlo. - -No verás mucho en la terminal, _pero_ deberías ver que el usuario bot agregó la etiqueta al informe de problemas. - -{% note %} - -**Nota:** Cuando las GitHub Apps toman acciones a través de la API, tales como agregar etiquetas, GitHub muestra estas acciones como si las cuentas _bot_ las realizaran. Para obtener más información, consulta la sección "[Cuentas de máquina vs cuentas de bot](/apps/differences-between-apps/#machine-vs-bot-accounts)". - -{% endnote %} - -Si es así, ¡felicidades! ¡Has creado una app funcional exitosamente! 🎉 - -Puedes ver el código final en el `server.rb` dentro del [repositorio de plantilla de app](https://github.com/github-developer/using-the-github-api-in-your-app). - -Consulta la sección "[Pasos siguientes](#next-steps)" para obtener ideas de qué puedes hacer después. - -### Solución de problemas - -Aquí te mostramos algunos problemas comunes y algunas soluciones sugeridas. Si te encuentras con cualquier otro problema, puedes pedir ayuda o consejo en el {% data variables.product.prodname_support_forum_with_url %}. - -* **P:** ¡Mi servidor no está escuchando los eventos! El cliente de Smee está ejecutándose en una ventana de la terminal, y estoy enviando eventos en GitHub.com mediante la apertura de informes de problemas nuevos, pero no veo ninguna salida en la ventana de la terminal en donde estoy ejecutando el servidor. - - **R:** Tal vez no tengas el dominio correcto de Smee en la configuración de tu app. Visita tu [página de configuración de la app](https://github.com/settings/apps) y vuelve a revisar los campos que se muestran en "[Registrar una app nueva con GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)". Asegúrate que el dominio en estos campos empate con el dominio que utilizaste en tu comando de `smee -u ` en "[Iniciar un canal de Smee nuevo](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)". - -* **P:** ¡Mi app no funciona! Abrí un nuevo informe de problemas, pero aún después de actualizar, no se le ha agregado ninguna etiqueta. - - **R:** Asegúrate de que hayas hecho todo lo siguiente: - - * [Instalaste la app](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) en el repositorio en donde estás abriendo el informe de problemas. - * Tu [cliente de Smee se está ejecutando](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) en una ventana de la terminal. - * Tu [servidor web se está ejecutando](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) sin errores en otra ventana de la terminal. - * Tu app tiene permisos de [lectura & escritura en los informes de problemas y está suscrita a los eventos de los mismos](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel). - * [Revisaste tu cuenta de correo electrónico](#step-1-update-app-permissions) después de actualizar los permisos y aceptaste los permisos nuevos. - -### Conclusión - -Después de seguir esta guía, ¡habrás aprendido los fundamentos básicos para desarrollar GitHub Apps! Para revisar todo, debes: - -* Programaste tu app para escuchar eventos -* Utilizaste la biblioteca de Octokit para hacer operaciones de la API de REST - -### Pasos siguientes - -Aquí tienes algunas ideas para lo que puedes hacer después: - -* ¡[Vuelve a escribir tu app utilizando GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)! -* ¡Vuelve a escribir tu app en Node.js utilizando al [Probot](https://github.com/probot/probot)! -* Haz que la app revise si la etiqueta `needs-response` ya existe en el informe de problemas, y si no, agrégala. -* Cuando el bot agregue la etiqueta exitosamente, muestra un mensaje en la terminal. (Pista: compara la ID de la etiqueta `needs-response` con la ID de la etiqueta en la carga útil como una condición para tu mensaje, para que así, el mensaje solo muestre cuando la etiqueta relevante se agregue y no lo haga con otra etiqueta). -* Agrega una página de llegada para tu app y conéctale una [Ruta de Sinatra](https://github.com/sinatra/sinatra#routes). -* Migra tu código a un servidor hospedado (como Heroku). No olvides actualizar la configuración de tu app con el dominio nuevo. -* Comparte tu proyecto u obtén consejos en el {% data variables.product.prodname_support_forum_with_url %}{% if currentVersion == "free-pro-team@latest" %} -* ¿Has creado una nueva y reluciente app que crees que pueda ser útil para otros? ¡[Agrégala a GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %} diff --git a/translations/es-XL/content/developers/apps/index.md b/translations/es-XL/content/developers/apps/index.md deleted file mode 100644 index 74aa79884c..0000000000 --- a/translations/es-XL/content/developers/apps/index.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Aplicaciones -intro: Puedes automatizar y transmitir tu flujo de trabajo si creas tus propias apps. -redirect_from: - - /early-access/integrations/ - - /early-access/integrations/authentication/ - - /early-access/integrations/install-an-integration/ - - /apps/adding-integrations/ - - /apps/building-integrations/setting-up-a-new-integration/about-integrations/ - - /apps - - /v3/integrations -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps -children: - - /getting-started-with-apps - - /building-github-apps - - /managing-github-apps - - /building-oauth-apps - - /managing-oauth-apps - - /guides ---- - diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/authorizing-oauth-apps.md b/translations/es-XL/content/developers/apps/managing-github-apps/authorizing-oauth-apps.md deleted file mode 100644 index 623cd0270b..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/authorizing-oauth-apps.md +++ /dev/null @@ -1,307 +0,0 @@ ---- -title: Authorizing OAuth Apps -intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}' -redirect_from: - - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps/ - - /apps/building-integrations/setting-up-and-registering-oauth-apps/directing-users-to-review-their-access/ - - /apps/building-integrations/setting-up-and-registering-oauth-apps/creating-multiple-tokens-for-oauth-apps/ - - /v3/oauth/ - - /apps/building-oauth-apps/authorization-options-for-oauth-apps/ - - /apps/building-oauth-apps/authorizing-oauth-apps - - /developers/apps/authorizing-oauth-apps -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -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){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} 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{% endif %}. - -If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow). - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - -To authorize your OAuth app, consider which authorization flow best fits your app. - -- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.) -- [device flow](#device-flow): Used for headless apps, such as CLI tools. - -{% else %} - -For standard apps that run in the browser, use the [web application flow](#web-application-flow) to obtain an authorization code and exchange it for a token. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.) - -{% endif %} - -### Web application flow - -{% note %} - -**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. - -{% endnote %} - -The web application flow to authorize users for your app is: - -1. Users are redirected to request their GitHub identity -2. Users are redirected back to your site by GitHub -3. Your app accesses the API with the user's access token - -#### 1. Request a user's GitHub identity - - GET {% data variables.product.oauth_host_code %}/login/oauth/authorize - -When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. - -##### Parameters - -Name | Type | Description ------|------|-------------- -`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% if currentVersion == "free-pro-team@latest" %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}. -`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls). -`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. -`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope. -`state` | `string` | {% data reusables.apps.state_description %} -`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups. - -#### 2. Users are redirected back to your site by GitHub - -If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process. - -Exchange this `code` for an access token: - - POST {% data variables.product.oauth_host_code %}/login/oauth/access_token - -##### Parameters - -Name | Type | Description ------|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. -`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_github_app %}. -`code` | `string` | **Required.** The code you received as a response to Step 1. -`redirect_uri` | `string` | The URL in your application where users are sent after authorization. -`state` | `string` | The unguessable random string you provided in Step 1. - -##### Response - -By default, the response takes the following form: - - access_token=e72e16c7e42f292c6912e7710c838347ae178b4a&token_type=bearer - -You can also receive the content in different formats depending on the Accept -header: - - Accept: application/json - {"access_token":"e72e16c7e42f292c6912e7710c838347ae178b4a", "scope":"repo,gist", "token_type":"bearer"} - - Accept: application/xml - - bearer - repo,gist - e72e16c7e42f292c6912e7710c838347ae178b4a - - -#### 3. Use the access token to access the API - -The access token allows you to make requests to the API on a behalf of a user. - - Authorization: token OAUTH-TOKEN - GET {% data variables.product.api_url_code %}/user - -For example, in curl you can set the Authorization header like this: - -```shell -curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user -``` - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -### Device flow - -{% note %} - -**Note:** The device flow is in public beta and subject to change.{% if currentVersion == "free-pro-team@latest" %} To enable this beta feature, see "[Activating beta features for apps](/developers/apps/activating-beta-features-for-apps)."{% endif %} - -{% endnote %} - -The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. - -#### Overview of the device flow - -1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code. -2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}. -3. The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token. - -#### Step 1: App requests the device and user verification codes from GitHub - - POST {% data variables.product.oauth_host_code %}/login/device/code - -Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication. - -##### Input Parameters - -Name | Type | Description ------|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app. -`scope` | `string` | The scope that your app is requesting access to. - -##### Response - -{% if currentVersion == "free-pro-team@latest" %} - ```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 %} - -##### Response parameters - -Name | Type | Description ------|------|-------------- -`device_code` | `string` | The device verification code is 40 characters and used to verify the device. -`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle. -`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}. -`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes. -`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error. - -#### Step 2: Prompt the user to enter the user code in a browser - -Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}. - - ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png) - -#### Step 3: App polls GitHub to check if the user authorized the device - - POST {% data variables.product.oauth_host_code %}/login/oauth/access_token - -Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)." - -The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`. - -Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user. - -##### Input parameters - -Name | Type | Description ------|------|-------------- -`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. -`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request. -`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`. - -##### Response - -```json -{ - "access_token": "e72e16c7e42f292c6912e7710c838347ae178b4a", - "token_type": "bearer", - "scope": "user" -} -``` - -#### Rate limits for the device flow - -When a user submits the verification code on the browser, there is a there is a rate limit of 50 submissions in an hour per application. - -If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). - -#### Error codes for the device flow - -| Error code | Description | -|----|----| -| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. | -| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use. -| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code. -| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. -| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow. -| `incorrect_device_code` | The device_code provided is not valid. -| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again. - -For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)." - -{% endif %} - -### Non-Web application flow - -Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/v3/auth#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. - -{% note %} - -**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with -two-factor authentication](/v3/auth/#working-with-two-factor-authentication) if -you or your users have two-factor authentication enabled. - -{% endnote %} - -### Redirect URLs - -The `redirect_uri` parameter is optional. If left out, GitHub will -redirect users to the callback URL configured in the OAuth Application -settings. If provided, the redirect URL's host and port must exactly -match the callback URL. The redirect URL's path must reference a -subdirectory of the callback URL. - - CALLBACK: http://example.com/path - - GOOD: http://example.com/path - GOOD: http://example.com/path/subdir/other - BAD: http://example.com/bar - BAD: http://example.com/ - BAD: http://example.com:8080/path - BAD: http://oauth.example.com:8080/path - BAD: http://example.org - -#### Localhost redirect urls - -The optional `redirect_uri` parameter can also be used for localhost URLs. If the application specifies a localhost URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback url for the app. - -For the `http://localhost/path` callback URL, you can use this `redirect_uri`: - - http://localhost:1234/path - -### Creating multiple tokens for OAuth Apps - -You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases. - -This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories. - -There is a limit to the number of tokens that are issued per user/application/scope combination. If your application requests enough tokens to go over one of the limits, older tokens _with the same scope being requested_ will stop working. - -{% data reusables.apps.deletes_ssh_keys %} - -### Directing users to review their access - -You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations. - -To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application. - -``` -{% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id -``` - -{% tip %} - -**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/v3/guides/discovering-resources-for-a-user/)." - -{% endtip %} - -### Troubleshooting - -* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" -* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -* "[Device flow errors](#errors-for-the-device-flow)" -{% endif %} diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/creating-a-custom-badge-for-your-oauth-app.md b/translations/es-XL/content/developers/apps/managing-github-apps/creating-a-custom-badge-for-your-oauth-app.md deleted file mode 100644 index c9339dc71c..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/creating-a-custom-badge-for-your-oauth-app.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Crear una insignia personalizada para tu App de OAuth -intro: '{% data reusables.shortdesc.creating_custom_badges_oauth_apps %}' -redirect_from: - - /apps/building-oauth-apps/creating-custom-badges-for-oauth-apps - - /developers/apps/creating-a-custom-badge-for-your-oauth-app -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - OAuth Apps ---- -Predeterminadamente, una App de OAuth nueva tendrá un [identicon](https://github.com/blog/1586-identicons) que se genera automáticamente. Una insignia de identicon se ve más o menos así: - -![Identicon](/assets/images/identicon.png) - -Después de que crees una App de OAuth, podrás personalizar la insignia de la misma si cargas un logo y seleccionas un color de fondo. Una insignia es una imagen de logo cuadrado dentro de una insignia circular. Puedes elegir un color de fondo para la insignia, la cual puede utilizarse para distinguir a tu app visualmente. - -Tu logo debe ser un archivo en PNG, JPG, o GIF de menos de 1 MB de tamaño. Para obtener la mejor calidad, te recomendamos un tamaño de por lo menos 200px x 200px. {% if currentVersion == "free-pro-team@latest" %}Consulta la sección "[Tips para las imagenes de logos e insignias](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)" para obtener lineamientos adicionales sobre la personalización de insignias.{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -Puedes cambiar una insignia personalizada para una GitHub App que ya tenga una lista de Marketplace aprobada si navegas a https://github.com/marketplace/manage. - -{% endif %} - -Para crear una insignia personalizada: - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.oauth_apps %} -{% data reusables.user-settings.modify_oauth_app %} -5. En la zona de "Logo de la aplicación", arrastra y suelta una imagen de alguna carpeta local, o da clic en **Cargar logo nuevo** para seleccionar una imagen de tu ordenador. ![Cargar un logo](/assets/images/oauth-apps/oauth_apps_upload_logo.png) -6. Recorta tu imagen. Cuando hayas terminado, da clic en **Configurar nuevo logo de la aplicación**. ![Cortar y confirmar logo](/assets/images/oauth-apps/oauth_apps_crop_and_set_logo.png) -7. En "Color de fondo de la insignia", teclea el [código hexadecimal de color](http://www.color-hex.com/) para el color de fondo de tu insignia. -{% if currentVersion == "free-pro-team@latest" %}**Nota:** El campo de entrada de "Color de fondo de la insignia" se podrá visualizar después de que se haya cargado el logo de una aplicación.{% endif %} -![Color de fondo de la insignia](/assets/images/oauth-apps/oauth_apps_badge_background_color.png) -{% data reusables.user-settings.update_oauth_app %} - -{% if currentVersion == "free-pro-team@latest" %} - -### Pasos siguientes - -Para obtener más información acerca de cómo crear un listado de Marketplace para esta app, consulta la sección "[Listados en GitHub Marketplace](/marketplace/listing-on-github-marketplace/)". - -{% endif %} diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/creating-an-oauth-app.md b/translations/es-XL/content/developers/apps/managing-github-apps/creating-an-oauth-app.md deleted file mode 100644 index 2461e72791..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/creating-an-oauth-app.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Crear una App de OAuth -intro: '{% data reusables.shortdesc.creating_oauth_apps %}' -redirect_from: - - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps/ - - /apps/building-oauth-apps/creating-an-oauth-app - - /developers/apps/creating-an-oauth-app -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - OAuth Apps ---- -{% if currentVersion == "free-pro-team@latest" %} -{% note %} - - **Nota:** {% data reusables.apps.maximum-oauth-apps-allowed %} - -{% endnote %} -{% endif %} - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.oauth_apps %} -4. Da clic en **Nueva App de OAuth**. ![Botón para crear una app de OAuth nueva](/assets/images/oauth-apps/oauth_apps_new_app.png) - - {% note %} - - **Nota:** si es la primera vez que creas una app, este botón dirá **Registrar una aplicación nueva**. - - {% endnote %} -6. Teclea el nombre de tu app en "Nombre de la aplicación". ![Campo para el nombre de tu app](/assets/images/oauth-apps/oauth_apps_application_name.png) - - {% warning %} - - **Advertencia** Utiliza solo la información que consideres pública en tu App de OAuth. Evita utilizar datos sensibles, tales como URL internas, cuando crees una App de OAuth. - - {% endwarning %} - -7. En "URL de la página principal", teclea la URL completa del sitio web de tu app. ![Campo para la URL de la página principal de tu app](/assets/images/oauth-apps/oauth_apps_homepage_url.png) -8. Opcionalmente, en "Descripción de la aplicación", teclea una descripción de tu app para que los usuarios la vean. ![Campo para la descripción de tu app](/assets/images/oauth-apps/oauth_apps_application_description.png) -9. Teclea la URL de rellamado de tu app en "URL de rellamado para autorización". ![Campo para la URL de rellamado de autorización de tu app](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png) -10. Haz clic en **Register application** (Registrar aplicación). ![Botón para registrar una aplicación](/assets/images/oauth-apps/oauth_apps_register_application.png) diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/deleting-a-github-app.md b/translations/es-XL/content/developers/apps/managing-github-apps/deleting-a-github-app.md deleted file mode 100644 index 79a94bb282..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/deleting-a-github-app.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Borrar una GitHub App -intro: '{% data reusables.shortdesc.deleting_github_apps %}' -redirect_from: - - /apps/building-integrations/managing-github-apps/deleting-a-github-app/ - - /apps/managing-github-apps/deleting-a-github-app - - /developers/apps/deleting-a-github-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -4. Selecciona la GitHub App que quieres borrar. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) -{% data reusables.user-settings.github_apps_advanced %} -6. Da clic en **Borrar GitHub App**. ![Botón para borrar una GitHub App](/assets/images/github-apps/github_apps_delete.png) -7. Teclea e nombre de la GitHub App para confirmar que la quieres borrar. ![Campo para confirmar el nombre de la GitHub App que quieres borrar](/assets/images/github-apps/github_apps_delete_integration_name.png) -8. Da clic en **Entiendo las consecuencias, borrar esta GitHub App**. ![Botón para confirmar el borrado de tu GitHub App](/assets/images/github-apps/github_apps_confirm_deletion.png) diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md b/translations/es-XL/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md deleted file mode 100644 index 807fdcc178..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Editing a GitHub App's permissions -intro: '{% data reusables.shortdesc.editing_permissions_for_github_apps %}' -redirect_from: - - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions/ - - /apps/managing-github-apps/editing-a-github-app-s-permissions - - /developers/apps/editing-a-github-apps-permissions -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% note %} - -**Note:** Updated permissions won't take effect on an installation until the owner of the account or organization approves the changes. You can use the [InstallationEvent webhook](/webhooks/event-payloads/#installation) to find out when people accept new permissions for your app. One exception is [user-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), which don't require the account owner to approve permission changes. - -{% endnote %} - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -4. Select the GitHub App whose permissions you want to change. -![App selection](/assets/images/github-apps/github_apps_select-app.png) -5. In the left sidebar, click **Permissions & webhooks**. -![Permissions and webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png) -6. Modify the permissions you'd like to change. For each type of permission, select either "Read-only", "Read & write", or "No access" from the dropdown. -![Permissions selections for your GitHub App](/assets/images/github-apps/github_apps_permissions_post2dot13.png) -7. In "Subscribe to events", select any events to which you'd like to subscribe your app. -![Permissions selections for subscribing your GitHub App to events](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png) -8. Optionally, in "Add a note to users", add a note telling your users why you are changing the permissions that your GitHub App requests. -![Input box to add a note to users explaining why your GitHub App permissions have changed](/assets/images/github-apps/github_apps_permissions_note_to_users.png) -9. Click **Save changes**. -![Button to save permissions changes](/assets/images/github-apps/github_apps_save_changes.png) diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/index.md b/translations/es-XL/content/developers/apps/managing-github-apps/index.md deleted file mode 100644 index b955192337..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Adminsitrar las GitHub Apps -intro: 'Después de que creas y registras una GitHub App, puedes hacer modificaciones a la misma, cambiar sus permisos, transferir la propiedad, y borrarla.' -redirect_from: - - /apps/building-integrations/managing-github-apps/ - - /apps/managing-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps -children: - - /installing-github-apps - - /modifying-a-github-app - - /editing-a-github-apps-permissions - - /making-a-github-app-public-or-private - - /suspending-a-github-app-installation - - /transferring-ownership-of-a-github-app - - /deleting-a-github-app ---- - diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/installing-github-apps.md b/translations/es-XL/content/developers/apps/managing-github-apps/installing-github-apps.md deleted file mode 100644 index 3a4fcac89c..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/installing-github-apps.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Instalar GitHub Apps -intro: 'Cuando tu app es pública, cualquiera puede instalarla en su repositorio a través de {% if currentVersion == "free-pro-team@latest" %}, de {% data variables.product.prodname_marketplace %} o de {% endif %}una URL de instalación. Cuando tu app es privada, solo puedes instalarla en los repositorios que te pertenezcan.' -redirect_from: - - /apps/installing-github-apps - - /developers/apps/installing-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% note %} - -**Nota:** Tu {% data variables.product.prodname_github_app %} tendra acceso a cualquier repositorio que ella misma cree, aún si alguien la instala únicamente en repositorios selectos. - -{% endnote %} - -### Instalar tu GitHub App privada en tu repositorio - -Una vez que creas una GitHub App privada, puedes instalarla en uno de tuos repositorios de usuario o de organización. Para obtener más información, consulta la sección "[Flujo de instalación privada](/apps/managing-github-apps/making-a-github-app-public-or-private/#private-installation-flow)". - -1. Selecciona tu app desde la [página de configuración de GitHub Apps](https://github.com/settings/apps). -2. En la barra lateral izquierda, da clic en **Instalar App**. -3. Da clic en **Instalar** junto a la cuenta de usuario o de organización que contiene el repositorio correcto. -4. Instala al app en todos los repositorios o selecciona los repositorios por separado. ![Permisos de instalación de la aplicación](/assets/images/install_permissions.png) -5. Una vez instalada, verás las opciones de configuración para la app en tu cuenta seleccionada. Puedes hacer cambios aquí, o repetir los pasos anteriores para instalar la app en otra cuenta. - -{% if currentVersion == "free-pro-team@latest" %} -### Ofrecer tu app en GitHub Marketplace - -Puedes ofrecer una versión gratuita o pagada de tu app en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), en donde las personas pueden uscar y ver los detalles de la misma. {% data variables.product.prodname_marketplace %} instala automáticamente una GitHub App cuando se completa una orden. - -Consulta la sección "[Comenzar con GitHub Marketplace](/marketplace/getting-started/)" para aprender más acerca de listar tu app en {% data variables.product.prodname_marketplace %}. - -Para aprender más acerca de cómo los usuarios pueden instalar tu app desde {% data variables.product.prodname_marketplace %}, consulta la sección "[Comprar e instalar apps en GitHub Marketplace](/articles/purchasing-and-installing-apps-in-github-marketplace)". - -{% endif %} - -### Permitir que las personas instalen tu app pública en su repositorio - -Puedes habilitar a otras personas para que instalen tu app pública si les proporcionas la URL de instalación en lugares como la página principal de tu app. Entonces puedes dirigirlos a la página principal de tu app desde la página de llegada en GitHub. - - Si estás migrándote desde una App de OAuth hacia una GitHub App, puedes utilizar los parámetros de consulta para preseleccionar los repositorios y la cuenta cuando instalen esta GitHub App. Consulta la secicón "[Migrar de Apps de OAuth a GitHub Apps](/apps/migrating-oauth-apps-to-github-apps/)" para aprender más. - -Estos pasos asumen que has [creado una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/): - -1. Desde la [Página de configuración de GitHub Apps](https://github.com/settings/apps), selecciona la app pública que quieres configurar para que los demás la instalen. -2. En "URL de la Página Principal", teclea la URL de la página principal de tu app y da clic en **Guardar cambios**. ![URL de la página de inicio](/assets/images/github-apps/github_apps_homepageURL.png) -3. GitHub proporciona una página de llegada para tu app, la cual incluye un enlace a la "URL de la Página Principal" de la misma. Para visitar la página de llegada en GitHub, copia la URL de "Enlace público" y pégala en un buscador. ![Enlace público](/assets/images/github-apps/github_apps_public_link.png) -4. Crea una página principal para tu app que incluya la URL de instalación de la misma: `https://github.com/apps//installations/new`. - -### Autorizar a los usuarios durante la instalación - -Puedes simplificar el proceso de autorización si lo completas durante la instalación de la app. Para hacerlo, sleecciona **Solicitar la autorización del usuario (OAuth) durante la instalación** al crear o modificar tu app en GitHub. Consulta la sección "[Crear una GitHub App](/apps/building-github-apps/creating-a-github-app/)" para aprender más al respecto. - -Una vez que alguien instale tu app, necesitarás obtener un token de acceso para el usuario. Consulta los pasos 2 y 3 en la sección "[Indentificar la los usuarios en tu sitio](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site)" para aprender más al respecto. -### Preservar el estado de una aplicación durante su instalación - -Puedes proporcionar un parámetro de `state` en la URL de instalación de una app para preservar el estado de la página de la aplicación y regresar a las personas a ese estado después de que instalen, se autentiquen, o acepten actualizaciones de tu GitHub App. Por ejemplo, puedes utilizar el `state` para correlacionar una instalación para el usuario o cuenta. - -Para preservar el estado, agrégalo a la URL de instalación: - -`https://github.com/apps//installations/new?state=AB12t` diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/es-XL/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md deleted file mode 100644 index ad11b13cdd..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Hacer pública o privada a una GitHub App -intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}' -redirect_from: - - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps/ - - /apps/building-github-apps/installation-options-for-github-apps/ - - /apps/building-integrations/managing-github-apps/changing-a-github-app-s-installation-option/ - - /apps/managing-github-apps/changing-a-github-app-s-installation-option/ - - /apps/managing-github-apps/making-a-github-app-public-or-private - - /developers/apps/making-a-github-app-public-or-private -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -Para obtener información sobre la autenticación, consulta la sección "[Autenticarse con las GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". - -### Flujo de instalación pública - -Los flujos de instalación pública tienen una página de llegada en donde los usuarios comenzarán el flujo de instalación. Este enlace se proprociona en el campo "enlace público" cuando configuras tu GitHub App. Para obtener más información, consulta la sección "[Instalar las GitHub Apps](/apps/installing-github-apps/)". - -### 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 o internas solo se pueden instalar en la cuenta de usuario o de organización del propietario. - -### Cambiar el quién puede instalar tu GitHub App - -Para cambiar quién puede instalar una GitHub App: - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% 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 deinstalación de tu GitHub App, da clic ya sea en **Convertir en pública** o en **Convertir en interna**. ![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, da clic ya sea en **Sí, convertir esta GitHub App en pública** o en **Sí, convertir esta GitHub App en interna**. ![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-XL/content/developers/apps/managing-github-apps/modifying-a-github-app.md b/translations/es-XL/content/developers/apps/managing-github-apps/modifying-a-github-app.md deleted file mode 100644 index b923ea6b3e..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/modifying-a-github-app.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Modificar una GitHub App -intro: '{% data reusables.shortdesc.modifying_github_apps %}' -redirect_from: - - /apps/building-integrations/managing-github-apps/modifying-a-github-app/ - - /apps/managing-github-apps/modifying-a-github-app - - /developers/apps/modifying-a-github-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -{% data reusables.user-settings.modify_github_app %} -5. En "Información básica", modifica la información que quieras cambiar para la GitHub App. ![Sección de información básica para tu GitHub App](/assets/images/github-apps/github_apps_basic_information.png) -6. Haz clic en **Guardar cambios**. ![Botón para guardar los cambios en tu GitHub App](/assets/images/github-apps/github_apps_save_changes.png) diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/scopes-for-oauth-apps.md b/translations/es-XL/content/developers/apps/managing-github-apps/scopes-for-oauth-apps.md deleted file mode 100644 index 6cac015740..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/scopes-for-oauth-apps.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -title: Scopes for OAuth Apps -intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' -redirect_from: - - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps/ - - /apps/building-oauth-apps/scopes-for-oauth-apps/ - - /apps/building-oauth-apps/understanding-scopes-for-oauth-apps - - /developers/apps/scopes-for-oauth-apps -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - OAuth Apps ---- -When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form. - -{% note %} - -**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." - -{% endnote %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)." -{% endif %} - -Check headers to see what OAuth scopes you have, and what the API action accepts: - -```shell -$ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I -HTTP/1.1 200 OK -X-OAuth-Scopes: repo, user -X-Accepted-OAuth-Scopes: user -``` - -* `X-OAuth-Scopes` lists the scopes your token has authorized. -* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for. - -### Available scopes - -Name | Description ------|-----------| -**`(no scope)`** | Grants read-only access to public information (includes public user profile info, public repository info, and gists){% if currentVersion != "free-pro-team@latest" %} -**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/v3/enterprise-admin).{% endif %} -**`repo`** | Grants full access to private and public repositories. That includes read/write access to code, commit statuses, repository and organization projects, invitations, collaborators, adding team memberships, deployment statuses, and repository webhooks for public and private repositories and organizations. Also grants ability to manage user projects. - `repo:status`| Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. - `repo_deployment`| Grants access to [deployment statuses](/v3/repos/deployments) for public and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code. - `public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories. - `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21"%} - `security_events` | Grants read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/v3/code-scanning).{% endif %} -**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in public and private repositories. The `repo` and `public_repo` scopes grants full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. - `write:repo_hook` | Grants read, write, and ping access to hooks in public or private repositories. - `read:repo_hook`| Grants read and ping access to hooks in public or private repositories. -**`admin:org`** | Fully manage the organization and its teams, projects, and memberships. - `write:org`| Read and write access to organization membership, organization projects, and team membership. - `read:org`| Read-only access to organization membership, organization projects, and team membership. -**`admin:public_key`** | Fully manage public keys. - `write:public_key`| Create, list, and view details for public keys. - `read:public_key`| List and view details for public keys. -**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user. -**`gist`** | Grants write access to gists. -**`notifications`** | Grants:
    * read access to a user's notifications
    * mark as read access to threads
    * watch and unwatch access to a repository, and
    * read, write, and delete access to thread subscriptions. -**`user`** | Grants read/write access to profile info only. Note that this scope includes `user:email` and `user:follow`. - `read:user`| Grants access to read a user's profile data. - `user:email`| Grants read access to a user's email addresses. - `user:follow`| Grants access to follow or unfollow other users. -**`delete_repo`** | Grants access to delete adminable repositories. -**`write:discussion`** | Allows read and write access for team discussions. - `read:discussion` | Allows read access for team discussions.{% if currentVersion == "free-pro-team@latest" %} -**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)". -**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)". -**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "[Deleting packages](/github/managing-packages-with-github-packages/deleting-a-package)".{% endif %} -**`admin:gpg_key`** | Fully manage GPG keys. - `write:gpg_key`| Create, list, and view details for GPG keys. - `read:gpg_key`| List and view details for GPG keys.{% if currentVersion == "free-pro-team@latest" %} -**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository.{% endif %} - -{% note %} - -**Note:** Your OAuth App can request the scopes in the initial redirection. You -can specify multiple scopes by separating them with a space: - - https://github.com/login/oauth/authorize? - client_id=...& - scope=user%20public_repo - -{% endnote %} - -### Requested scopes and granted scopes - -The `scope` attribute lists scopes attached to the token that were granted by -the user. Normally, these scopes will be identical to what you requested. -However, users can edit their scopes, effectively -granting your application less access than you originally requested. Also, users -can edit token scopes after the OAuth flow is completed. -You should be aware of this possibility and adjust your application's behavior -accordingly. - -It's important to handle error cases where a user chooses to grant you -less access than you originally requested. For example, applications can warn -or otherwise communicate with their users that they will see reduced -functionality or be unable to perform some actions. - -Also, applications can always send users back through the flow again to get -additional permission, but don’t forget that users can always say no. - -Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which -provides tips on handling modifiable token scopes. - -### Normalized scopes - -When requesting multiple scopes, the token is saved with a normalized list -of scopes, discarding those that are implicitly included by another requested -scope. For example, requesting `user,gist,user:email` will result in a -token with `user` and `gist` scopes only since the access granted with -`user:email` scope is included in the `user` scope. diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md b/translations/es-XL/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md deleted file mode 100644 index 8f25a9ebf3..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Suspender la instalación de una GitHub App -intro: '{% data reusables.shortdesc.suspending_a_github_app %}' -redirect_from: - - /apps/managing-github-apps/suspending-a-github-app-installation - - /developers/apps/suspending-a-github-app-installation -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -{% note %} - -**Nota:**{% data reusables.pre-release-program.suspend-installation-beta %} - -{% endnote %} -{% endif %} - -### Suspender una GitHub App - -Para suspender una {% data variables.product.prodname_github_app %}, debes ser el propietario de la cuenta o tener permisos en el repositorio u organización en donde está instalada la app que deseas suspender. - -También puedes suspender y dejar de suspender las instalaciones de una {% data variables.product.prodname_github_app %} si utilizas la API de REST. Para obtener más información, consulta la [API de REST para las GitHub Apps](/v3/apps/). - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -4. Selecciona la {% data variables.product.prodname_github_app %} que quieres suspender. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) -{% data reusables.user-settings.github_apps_advanced %} -6. Junto a la configuración de suspensión para la instalación, da clic en **Suspender** o en **Dejar de suspender**. ![Suspender una GitHub App](/assets/images/github-apps/suspend-a-github-app.png) diff --git a/translations/es-XL/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md b/translations/es-XL/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md deleted file mode 100644 index 75fb55f044..0000000000 --- a/translations/es-XL/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Transferir la propiedad de una GitHub App -intro: '{% data reusables.shortdesc.transferring_ownership_of_github_apps %}' -redirect_from: - - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app/ - - /apps/managing-github-apps/transferring-ownership-of-a-github-app - - /developers/apps/transferring-ownership-of-a-github-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.github_apps %} -4. Selecciona la GitHub App cuya propiedad quieras transferir. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) -{% data reusables.user-settings.github_apps_advanced %} -6. Da clic en **Transferir propiedad**. ![Botón para transferir la propiedad](/assets/images/github-apps/github_apps_transfer_ownership.png) -7. Teclea el nombre de la GitHub App que quieres transferir. ![Campo para ingresar el nombre de la app a transferir](/assets/images/github-apps/github_apps_transfer_app_name.png) -8. Teclea el nombre del usuario u organización al cual quieres transferir la GitHub App. ![Campo para ingresar el usuario u organización al cual se transferirá la app](/assets/images/github-apps/github_apps_transfer_new_owner.png) -9. Da clic en **Transferir esta GitHub App**. ![Botón para confirmar la transferencia de una GitHub App](/assets/images/github-apps/github_apps_transfer_integration.png) diff --git a/translations/es-XL/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md b/translations/es-XL/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md deleted file mode 100644 index ee221eda97..0000000000 --- a/translations/es-XL/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Borrar una App de OAuth -intro: '{% data reusables.shortdesc.deleting_oauth_apps %}' -redirect_from: - - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app/ - - /apps/managing-oauth-apps/deleting-an-oauth-app - - /developers/apps/deleting-an-oauth-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - OAuth Apps ---- -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.oauth_apps %} -4. Selecciona la {% data variables.product.prodname_oauth_app %} que quieres modificar. ![Seleccion de apps](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) -5. Da clic en **Borrar aplicación**. ![Botón para borrar la aplicación](/assets/images/oauth-apps/oauth_apps_delete_application.png) -6. Da clic en **Borrar esta aplicación de OAuth**. ![Botón para confirmar el borrado](/assets/images/oauth-apps/oauth_apps_delete_confirm.png) diff --git a/translations/es-XL/content/developers/apps/managing-oauth-apps/index.md b/translations/es-XL/content/developers/apps/managing-oauth-apps/index.md deleted file mode 100644 index a16780d521..0000000000 --- a/translations/es-XL/content/developers/apps/managing-oauth-apps/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Adminsitrar las Apps de OAuth -intro: 'Después de que creas y registras una App de OAuth, puedes hacerle modificaciones, cambiar sus permisos, transferir su propiedad y borrarla.' -redirect_from: - - /apps/building-integrations/managing-oauth-apps/ - - /apps/managing-oauth-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - OAuth Apps -children: - - /modifying-an-oauth-app - - /transferring-ownership-of-an-oauth-app - - /troubleshooting-authorization-request-errors - - /troubleshooting-oauth-app-access-token-request-errors - - /deleting-an-oauth-app ---- - diff --git a/translations/es-XL/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md b/translations/es-XL/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md deleted file mode 100644 index fd5498878a..0000000000 --- a/translations/es-XL/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Modificar una App de OAuth -intro: '{% data reusables.shortdesc.modifying_oauth_apps %}' -redirect_from: - - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app/ - - /apps/managing-oauth-apps/modifying-an-oauth-app - - /developers/apps/modifying-an-oauth-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - OAuth Apps ---- -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.oauth_apps %} -{% data reusables.user-settings.modify_oauth_app %} -5. Modifica la información que quieras cambiar para la {% data variables.product.prodname_oauth_app %}. -{% data reusables.user-settings.update_oauth_app %} diff --git a/translations/es-XL/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md b/translations/es-XL/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md deleted file mode 100644 index 549fd82afe..0000000000 --- a/translations/es-XL/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Transferir la propiedad de una App de OAuth -intro: '{% data reusables.shortdesc.transferring_ownership_of_oauth_apps %}' -redirect_from: - - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app/ - - /apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app - - /developers/apps/transferring-ownership-of-an-oauth-app -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - OAuth Apps ---- -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.oauth_apps %} -4. Selecciona la {% data variables.product.prodname_oauth_app %} que quieres modificar. ![Seleccion de apps](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) -5. Da clic en **Transferir propiedad**. ![Botón para transferir la propiedad](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png) -6. Teclea el nombre de la {% data variables.product.prodname_oauth_app %} que quieres transferir. ![Campo para ingresar el nombre de la app a transferir](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png) -7. Teclea el nombre del usuario u organización al cual quieres transferir la {% data variables.product.prodname_oauth_app %}. ![Campo para ingresar el usuario u organización al cual se transferirá la app](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png) -8. Da clic en **Transferir esta aplicación**. ![Botón para transferir la aplicación](/assets/images/oauth-apps/oauth_apps_transfer_application.png) diff --git a/translations/es-XL/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md b/translations/es-XL/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md deleted file mode 100644 index 8b6d6d8ebd..0000000000 --- a/translations/es-XL/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Solución de problemas para los errores de solicitud de autorización -intro: '{% data reusables.shortdesc.troubleshooting_authorization_request_errors_oauth_apps %}' -redirect_from: - - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors/ - - /apps/managing-oauth-apps/troubleshooting-authorization-request-errors - - /developers/apps/troubleshooting-authorization-request-errors -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub Apps ---- -### Aplicación suspendida - -Si la App de OAuth que configuraste se suspendió (debido a que reportaron abuso, spam, o mal uso de la API), GitHub te redirigirá a la URL de rellamado registrada utilizando los siguientes parámetros para resumir el error: - - http://your-application.com/callback?error=application_suspended - &error_description=Your+application+has+been+suspended.+Contact+support@github.com. - &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23application-suspended - &state=xyz - -Para resolver los problemas de suspensión de aplicaciones, por favor contacta a {% data variables.contact.contact_support %}. - -### Redirigir una discordancia de URI - -Si proporcionas una `redirect_uri` que no concuerde con lo que has registrado con tu aplicación, GitHub te redirigirá a la URL de rellamado registrada con los siguientes parámetros que resumirán el error: - - http://your-application.com/callback?error=redirect_uri_mismatch - &error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application. - &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23redirect-uri-mismatch - &state=xyz - -Para corregir este error, puedes ya sea proporcionar una `redirect_uri` que coincida con lo que registraste o dejar este parámetro para utilizar aquél predeterminado que se registró con tu aplicación. - -#### Acceso denegado - -Si el usuario rechaza el acceso a tu aplicación, GitHub te redirigirá a la URL de rellamado registrada con los siguientes parámetros para resumir el error: - - http://your-application.com/callback?error=access_denied - &error_description=The+user+has+denied+your+application+access. - &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23access-denied - &state=xyz - -No puedes hacer nada al respecto, ya que los usuarios tiene la libertad de elegir si no quieren utilizar tu aplicación. Lo más común es que los usuarios simplemente cierren la ventana o presionen "atrás" en su buscador, así que es probable que nunca veas este error. diff --git a/translations/es-XL/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/es-XL/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md deleted file mode 100644 index 4adc6deedb..0000000000 --- a/translations/es-XL/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Solucionar problemas para los errores de solicitud en los tokens de acceso a Apps de OAuth -intro: '{% data reusables.shortdesc.troubleshooting_access_token_reques_errors_oauth_apps %}' -redirect_from: - - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/ - - /apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors - - /developers/apps/troubleshooting-oauth-app-access-token-request-errors -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - OAuth Apps ---- -{% note %} - -**Nota:** Estos ejemplos solo muestran respuestas de JSON. - -{% endnote %} - -### Credenciales de cliente incorrectas - -Si la client\_id y/o el client\_secret que pasas son incorrectos, recibirás este error como respuesta. - -```json -{ - "error": "incorrect_client_credentials", - "error_description": "The client_id and/or client_secret passed are incorrect.", - "error_uri": "/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/#incorrect-client-credentials" -} -``` - -Para resolver este error, asegúrate de que tienes las credenciales correctas para tu {% data variables.product.prodname_oauth_app %}. Revisa dos veces la `client_id` y el `client_secret` para asegurarte de que sean correctos y de que se pasen correctamente en {% data variables.product.product_name %}. - -### Redirigir una discordancia de URI - -Si proporcionas una `redirect_uri` que no empate con lo que registraste con tu {% data variables.product.prodname_oauth_app %}, recibirás este mensaje de error: - -```json -{ - "error": "redirect_uri_mismatch", - "error_description": "The redirect_uri MUST match the registered callback URL for this application.", - "error_uri": "/apps/managing-oauth-apps/troubleshooting-authorization-request-errors/#redirect-uri-mismatch2" -} -``` - -Para corregir este error, puedes ya sea proporcionar una `redirect_uri` que coincida con lo que registraste o dejar este parámetro para utilizar aquél predeterminado que se registró con tu aplicación. - -### Código de verificación incorrecto - -```json -{ - "add_scopes": [ - "repo" - ], - "note": "admin script" -} -``` - -Si el código de verificación que pasaste es incorrecto, está caduco, o no coincide con lo que recibiste en la primera solicitud de autorización, recibirás este error. - -```json -{ - "error": "bad_verification_code", - "error_description": "The code passed is incorrect or expired.", - "error_uri": "/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/#bad-verification-code" -} -``` - -Para resolver este error, inicia el [proceso de autorización de OAuth nuevamente](/apps/building-oauth-apps/authorizing-oauth-apps/) y obtén un código nuevo. diff --git a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/about-github-marketplace.md b/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/about-github-marketplace.md deleted file mode 100644 index 135d9fae50..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/about-github-marketplace.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Acerca de Mercado GitHub -intro: 'Aprende lo básico para preparar tu app para que se le revise antes de unirte a {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /apps/marketplace/getting-started/ - - /marketplace/getting-started - - /developers/github-marketplace/about-github-marketplace -versions: - free-pro-team: '*' -topics: - - Marketplace ---- -[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) te conecta a los desarrolladores que quieren extender y mejorar sus flujos de trabajo de {% data variables.product.prodname_dotcom %}. Puedes listar herramientas gratuitas y de pago para que las utilicen los desarrolladores en {% data variables.product.prodname_marketplace %}. {% data variables.product.prodname_marketplace %} ofrece dos tipos de herramientas para los desarrolladores: {% data variables.product.prodname_actions %} y Apps, y cada herramienta requiere pasos diferentes para agregarla a {% data variables.product.prodname_marketplace %}. - -### GitHub Actions - -{% data reusables.actions.actions-not-verified %} - -Para aprender sobre cómo publicar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_marketplace %}, consulta la sección "[{% data variables.product.prodname_actions %} en {% data variables.product.prodname_marketplace %}](/marketplace/actions/)". - -### Aplicaciones - -Puedes listar las aplicaciones verificadas y sin verificar en {% data variables.product.prodname_marketplace %}. Las apps sin verificar no pasan por el ciclo de seguridad, prueba y verificación que {% data variables.product.prodname_dotcom %} necesita para las apps verificadas. - -Las apps verificadas tienen una insignia verde en {% data variables.product.prodname_marketplace %}. Las apps sin verificar tienen una insignia gris junto a su listado y solo se encuentran disponibles como apps gratuitas. - -![Insignias verde para verificado y gris para no verificado](/assets/images/marketplace/marketplace_verified_badges.png) - -Si te interesa crear una app para {% data variables.product.prodname_marketplace %}, pero eres nuevo en las {% data variables.product.prodname_github_apps %} y en las {% data variables.product.prodname_oauth_app %}, consulta la sección "[Crear apps](/apps/)". - -{% data reusables.marketplace.github_apps_preferred %}, aunque puedes listar tanto las Apps de OAuth como las {% data variables.product.prodname_github_app %} en {% data variables.product.prodname_marketplace %}. Consulta la sección "[Diferencias entre las apps de OAuth y las GitHub Apps](/apps/differences-between-apps/)" para obtener más detalles. Para aprender más acerca de cambiarse de una app de OAuth a {% data variables.product.prodname_github_apps %}, consulta la sección [Migrarse de las Apps de OAuth a las {% data variables.product.prodname_github_app %}](/apps/migrating-oauth-apps-to-github-apps/). - -Si tienes preguntas acerca de {% data variables.product.prodname_marketplace %}, por favor contacta directamente a {% data variables.contact.contact_support %}. - -#### Apps sin verificar - -Las apps sin verificar no necesitan cumplir con los "[Requisitos para listar una app en {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)" o pasar por el "[Proceso de revisión de seguridad](/marketplace/getting-started/security-review-process/)". - -Las {% data reusables.marketplace.unverified-apps %} que tengan un plan de pago publicado te impediran que puedas emitir una app sin verificar. Debes eliminar los planes de pago o mantenerlos en modo de borrador antes de publicar una app sin verificar. - -Para listar tu app sin verificar en {% data variables.product.prodname_marketplace %}, solo necesitas crear un "[Listado en {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)" y emitirlo como un listado sin verificar. - -{% data reusables.marketplace.launch-with-free %} - -#### Apps verificadas - -Si ya creaste una app y estás interesado en emitir un listado verificado en {% data variables.product.prodname_marketplace %}, comienza aquí: - -1. [Comenzar en {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)
    Aprende acerca de los requisitos, lineamientos y del proceso de emisión de apps. - -1. [Integrarse con la API de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/)
    Antes de que puedas listar tu app en {% data variables.product.prodname_marketplace %}, necesitarás integrar los flujos de facturación utilizando la API de {% data variables.product.prodname_marketplace %} y los eventos de webhook. - -1. [Listar en {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/)
    Crear un listado de {% data variables.product.prodname_marketplace %} en borrador, configurar ajustes de webhooks, y configurar los planes de precios. - -1. [Vender tu app](/marketplace/selling-your-app/)
    Aprende acerca de los planes de precios, ciclos de facturación, y sobre como recibir pagos de {% data variables.product.prodname_dotcom %} por tu app. - -1. [Perspectivas de {% data variables.product.prodname_marketplace %}](/marketplace/github-marketplace-insights/)
    Ve como se desempeña tu app en {% data variables.product.prodname_marketplace %}. Puedes utilizar métricas que recolecta {% data variables.product.prodname_dotcom %} para guiar tu campaña de marketing y tener éxito en {% data variables.product.prodname_marketplace %}. - -1. [Transacciones de {% data variables.product.prodname_marketplace %}](/marketplace/github-marketplace-transactions/)
    Descarga y visualiza los datos de transacción para tu listado de {% data variables.product.prodname_marketplace %}. - -### Revisar tu app - -Queremos asegurarnos que las apps que se ofrecen en {% data variables.product.prodname_marketplace %} sean seguras, confiables y que hayan tenido pruebas adecuadas. Los especialistas de integración de {% data variables.product.prodname_marketplace %} revisarán tu app para garantizar que cumple con todos los requisitos. Sigue lis lineamientos de estos artículos antes de emitir tu app: - - -* [Requisitos para listar una app en {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) -* [Proceso de revisión de seguridad](/marketplace/getting-started/security-review-process/) diff --git a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/index.md b/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/index.md deleted file mode 100644 index ff2dd5cd20..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Crear apps para GitHub Marketplace -intro: 'Puedes listar herramientas gratuitas y de pago para que las utilicen los desarrolladores en {% data variables.product.prodname_marketplace %}.' -versions: - fpt: '*' -topics: - - Marketplace -children: - - /requirements-for-listing-an-app - - /security-best-practices-for-apps - - /customer-experience-best-practices-for-apps - - /viewing-metrics-for-your-listing - - /viewing-transactions-for-your-listing ---- - diff --git a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md deleted file mode 100644 index 1a9cce5637..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Requisitos para listar una app -intro: 'Las apps en {% data variables.product.prodname_marketplace %} deben cumplir con los requisitos detallados en esta página antes de que nuestros especialistas de incorporación a {% data variables.product.prodname_marketplace %} aprueben el listado.' -redirect_from: - - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - - /apps/marketplace/getting-started-with-github-marketplace-listings/requirements-for-listing-an-app-on-github-marketplace/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/ - - /apps/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/ - - /marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace - - /developers/github-marketplace/requirements-for-listing-an-app -versions: - fpt: '*' -topics: - - Marketplace ---- -Antes de que emias tu app para revisión, debes leer y aceptar las condiciones del "[Acuerdo de desarrollador de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)". Aceptarás las condiciones dentro de tu [borrador de listado](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) en {% data variables.product.product_name %}. Una vez que hayas emitido tu app, uno de los especialistas de incorporación de {% data variables.product.prodname_marketplace %} te contactará y te dará más información sobre el proceso de incorporación, y revisará tu app asegurarse de que cumple con estos requisitos: - -### Experiencia del usuario - -- Las {% data variables.product.prodname_github_app %} deben contar con un mínimo de 100 instalaciones. -- Las {% data variables.product.prodname_oauth_app %} deben tener un mínimo de 200 usuarios. -- Las apps deben proporcionar valor a los clientes e integrarse con la plataforma de alguna forma más allá de la autenticación. -- Las apps deben estar disponibles al público en {% data variables.product.prodname_marketplace %} y no pueden estar en fase beta o únicamente disponibles con invitación. -- Las apps no pueden persuadir activamente a los usuarios para salir de {% data variables.product.product_name %}. -- Los materiales de marketing para la app deben representar con precisión el comportamiento de ésta. -- Las apps deben incluir enlaces para la documentación de cara al cliente que describa cómo configurarlas y configurarlas. -- Cuando un cliente compra una app y GitHub los redirige a la URL de instalación de la misma, la app debe comenzar inmediatamente con el flujo de OAuth. Para encontrar más detalles, consulta la sección "[Gestionar las compras nuevas y los periodos de prueba gratuitos](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/#step-3-authorization)". - -- Los clientes deben poder instalar tu app y seleccionar repositorios tanto en una cuenta personal como en una organizacional. Debe poder ver y administrar esas cuentas por separado. - -### Marca y listado - -- Las apps que utilizan los logos de GitHub deben seguir los lineamientos de "[Logos y uso de {% data variables.product.product_name %}](https://github.com/logos)". -- Las apps deben tener un logo, tarjeta de características, e imágenes de impresión de pantalla que cumplan con las recomendaciones que se proporcionan en "[Escribir las descripciones de los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". -- Los listados deben incluir descripciones que estén bien escritas y no tengan errores gramaticales. Para obtener orientación sobre cómo escribir tu listado, consulta la sección "[Escribir las descripciones de los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". - -### Seguridad - -Las apps pasarán por una revisión de seguridad antes de que se listen en {% data variables.product.prodname_marketplace %}. Para tener una revisión exitosa, se debe cumplir con los requisitos y seguir las mejores prácticas de seguridad listadas en "[Proceso de revisión de seguridad](/marketplace/getting-started/security-review-process/)". Para obtener información sobre el proceso de revisión, contacta a [marketplace@github.com](mailto:marketplace@github.com). - -### Flujos de facturación - -Tu app debe integrar [flujos de facturación](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) utilizando el [evento de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). - -#### Apps gratuitas - -{% data reusables.marketplace.free-apps-encouraged %} Si estás listando una app gratuita, necesitarás cumplir con estos requisitos: - -- Los clientes deben poder ver que tienen un plan gratuito en la sección de configuración de facturación, perfil o cuenta de la app. -- Cuando un cliente cancela tu app, debes seguir el flujo de [cancelación de planes](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/). - -#### Apps de pago - -Para ofrecer tu app como un servicio de pago, necestiarás cumplir con estos requisitos para listar la app en {% data variables.product.prodname_marketplace %}: - -- Para vender tu app en {% data variables.product.prodname_marketplace %}, esta debe utilizar el sistema de facturación de GigtHub. Tu app no necesita gestionar pagos, pero sí necesita utilizar los "[eventos de compra de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" para administrar las compras, actualizaciones, decrementos, cancelaciones y periodos de prueba gratuitos nuevos. Consulta la sección "[Flujos de facturación](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" para aprender más sobre cómo integrar estos eventos en tu app. Utilizar el sistema de facturación de GitHub permite a los clientes comprar una app sin salir de GitHub y pagar por el servicio con el método de pago que ya está adjunto a su cuenta de {% data variables.product.product_name %}. -- Las apps deben permitir facturación mensual y anual para las compras de sus sucripciones de pago. -- Los listados pueden ofrecer cualquier combienación de planes gratuitos y de pago. Los planes gratuitos son opcionales, pero se les fomenta. Para obtener más información, consulta la sección "[Configurar un plan de precios para los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". -{% data reusables.marketplace.marketplace-billing-ui-requirements %} diff --git a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-review-process-for-submitted-apps.md b/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-review-process-for-submitted-apps.md deleted file mode 100644 index 1c98ee817b..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-review-process-for-submitted-apps.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Proceso de revisión de seguridad para las apps emitidas -intro: 'El equipo de seguridad de GitHub revisa todas las apps emitidas a {% data variables.product.prodname_marketplace %} para garantizar que cumplen los requisitos de seguridad. Sigue estas mejores prácticas para estar preparado para el proceso de revisión.' -redirect_from: - - /apps/marketplace/getting-started/security-review-process/ - - /marketplace/getting-started/security-review-process - - /developers/github-marketplace/security-review-process-for-submitted-apps -versions: - free-pro-team: '*' ---- -Después de que hayas emitido tu app para su aprobación, el equipo de seguridad de GitHub te solicitará que completes un cuestionario de seguridad acerca de tu app y de un programa general de seguridad. Como parte de la revisión, tendrás la opción de prorporcionar documetnación para apoyar tus respuestas. Debes emitir dos documentos necesarios para que tu app se apruebe en {% data variables.product.prodname_marketplace %}: un [plan de respuesta a incidentes](#incident-response-plan) y un [flujo de trabajo para administración de vulnerabilidades](#vulnerability-management-workflow). - - -### Mejores prácticas de seguridad - -Sigue estas mejores prácticas para tener éxito en tu revisión de seguridad y para proporcionar una experiencia de usuario segura. - -#### Autorización, autenticación, y control de accesos - -Te recomendamos emitir una GitHub App en vez de una App de OAuth. {% data reusables.marketplace.github_apps_preferred %}. Consulta la sección "[Diferencias entre las GitHub Apps y las Apps de OAuth](/apps/differences-between-apps/)" para encontrar más detalles. -- Las apps deben utilizar el "[principio del menor privilegio necesario](https://en.wikipedia.org/wiki/Principle_of_least_privilege)" y únicamente deben solicitar los alcances de OAuth y los permisos de GitHub Apps que la app necesite para llevar a cabo su funcionalidad prevista. -- Las apps deben proporcionar a los clientes una forma de borrarla de sus cuentas sin tener que mandar un correo electrónico o llamar al personal de soporte. -- Las apps no deben compartir tokens entre las diferentes implementaciones de la misma. Por ejemplo, una app de escritorio debe tener un token separado de aquella que es basada en web. Los tokens individuales permiten a cada app solicitar el acceso necesario a los recursos de GitHub por separado. -- Diseña tu app con diferentes roles de usuario, dependiendo de la funcionalidad que necesita cada tipo de usuario. Por ejemplo, un usuario estándar no debe tener acceso a la funcionalidad de administrador, y los gerentes de facturación podrían no requerir acceso de carga al código de un repositorio. -- Tu app no debe compartir cuentas de servicio tales como el correo electrónico o los servicios de base de datos para administrar tu servicio de SaaS. -- Todos los servicios que se utilicen en tu app deben contar con credenciales únicas de nombre de inicio de sesión y contraseña. -- El acceso privilegiado de administrador para la infraestructura de alojamiento productiva solo se deberá otorgar a los ingenieros y empleados con obligaciones administrativas. -- Las apps no pueden utilizar tokens de acceso personal para autenticarse, y deben hacerlo como una [App de OAuth](/apps/about-apps/#about-oauth-apps) o una [GitHub App](/apps/about-apps/#about-github-apps): - - Las Apps de OAuth deben autenticarse utilizando un [Token de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). - - Las GitHub Apps deben autenticarse utilizando ya sea un [Token Web de JSON (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), un [Token de OAuth](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), o un[token de acceso a la instalación](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). - -#### Protección de datos - -- Las apps deben cifrar los datos que transfieran a través del internet público utilizando HTTPS, con SSH o con un certificado TLS válido para Git. -- Las apps deben almacenar las llaves secretas de ID y de cliente de manera segura. Te recomendamos almacenarlas como [variables de ambiente](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). -- Las apps deben borrar todos los datos del usuario de GitHub en los primeros 30 días de recibir la solicitud de dicho cliente, o dentro de los primeros 30 días del final de la relación legal del usuario para con GitHub. -- Las apps no pueden requerir que el usuario proporcione su contraseña de GitHub. -- Las apps deben cifrar los tokens, ID de cliente y secretos de cliente. - -#### Registro y monitoreo - -- Las apps deben tener la capacidad de registro y monitoreo. Las bitácoras de la app deben conservarse por lo menos por 30 días y archivarse por lo menos durante un año. Un log de seguirdad debería incluir: - - Eventos de autenticación y autorización - - Cambios a la configuración del servicio - - Escritura y lectura de objetos - - Todos los cambios de permisos de usuarios y grupos - - Elevación de rol a aquel de administrador - - Marca de tiempo consistente para cada evento - - Usuarios orgien, direcciones IP, y/o nombres de host para todas las acciones registradas - -#### Flujo de trabajo de respuesta a incidentes - -- Para asociarte con GitHub se te solicita tener un [plan de respuesta a incidentes](#incident-response-plan) activo antes de emitir tu listado de app de {% data variables.product.prodname_marketplace %}. -- Te recomendamos tener un equipo de respuesta a incidentes para operaciones y de seguridad en tu compañía en vez de utilizar un proveedor tercero. -- Debes poder notificar a Github dentro de las primeras 24 horas de que se confirme un incidente. -- Debes familiarizarte con las secciones 3.7.5 - 3.7.5.6 del [Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/github/site-policy/github-marketplace-developer-agreement#3-restrictions-and-responsibilities), el cual incluye detalles adicionales sobre los requisitos del flujo de trabajo para respuesta a incidentes. - -#### Administración de vulnerabilidades y flujo de trabajo de parchado - -- Debes llevar a cabo escaneos de vulnerabilidades frecuentes para la infraestructura productiva. -- Debes clasificar los resultados de los escaneos de vulnerabilidades y definir un tiempo en el que acuerdes remediar dichas vulnerabilidades. -- Debes familiarizarte con la sección 3.7.3 del [Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/github/site-policy/github-marketplace-developer-agreement#3-restrictions-and-responsibilities), la cual incluye detalles adicionales sobre los requisitos de la administración de vulnerabilidades y de los flujos de trabajo del parchado. - -### Documentación del programa de seguridad - -Durante la revisión de seguridad de Marketplace, se te solicitará emitir tu plan de respuesta a incidentes y el flujo de trabajo de la administración de vulnerabilidades. Cada documento debe incluir una declaración con la marca de la compañía y con la firma y fecha por parte de la gerencia. - -#### Plan de respuesta a incidentes -Tu documentación del plan de respuesta a incidentes debe incluir el proceso actual que sigue tu compañía, quién es el responsable, y la persona a contactar o de la cual esperar el contacto en caso de que ocurra un incidente. La "[Guía de Seguridad para Gestión de Incidentes del NIST](http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf)" es un excelente ejemplo de un documento que cubre los temas generales sobre la respuesta a incidentes. La sección 2.3 "Creación de Políticas, Planes y Procedimientos para la Respuesta a Incidentes" cubre específicamente la política. Otro excelente ejemplo es la "[Política de Respuesta a Filtraciones de Datos del SANS](https://www.sans.org/security-resources/policies/general/pdf/data-breach-response)". - -#### Flujo de trabajo para la administración de vulnerabilidades -Tu documentación del flujo de trabajo para la administración de vulnerabilidades debe incluir los procesos actuales que sigue tu compañía para la administración de vulnerabilidades, así como para el proceso de parchado que utiliza. Si no tienes un programa de administración de vulnerabilidades completo, sería de gran ayuda el comenzar a crear un proceso de parchado. Para obtener orientación sobre la creación de una política de administración de parches, lee el artículo "[Establecer una política de administración de parches](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)". - -{% note %} - -**Nota:** No se espera que los documentos del flujo de trabajo para respuesta a incidentes y de administración de vulnerabilidades constituyan una documentación de programación o una política formal masivos. Es más valioso tener una o dos páginas acerca de lo que haces que una plantilla de política extensa. - -{% endnote %} - -#### Cuestionario del programa de seguridad de GitHub Marketplace - -Durante el proceso de emisión de la app, nuestro equipo de incorporación de {% data variables.product.prodname_marketplace %} también te enviará un cuestionario solicitando información acerca de tus prácticas de seguridad. Este documento servirá como un registro escrito que da fe de: - -- El método de autenticación y alcances que requiere tu app. -- Que no estás solicitando más alcances o acceso a {% data variables.product.product_name %} de lo que tu app requiere para llevar a cabo su funcionalidad esperada, tomando en consideración las limitaciones de OAuth y el uso de las {% data variables.product.prodname_github_app %}. -- La utilización de cualquier servicio o infraestructura de terceros, tales como SaaS, PaaS, o LaaS. -- Que existe un procedimiento de respuesta a incidentes. -- El método de tu app para gestionar llaves/tokens. -- Que existe una política y proceso de divulgación responsables, o bien, planes para implementarla en los próximos seis meses. -- Tu programa o flujo de trabajo de administración de vulnerabilidades. -- Que tienes capacidades de registro y monitoreo. También debes proprocionar evidencia de que cualquier bitácora relevante de la app se mantiene por lo menos por 30 días y se archiva por lo menos por un año. diff --git a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md deleted file mode 100644 index 3f20cab536..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Visualizar las métricas para tu listado -intro: 'La página de perspectivas de {% data variables.product.prodname_marketplace %} muestra métricas para tu {% data variables.product.prodname_github_app %}. Puedes utilizar las métricas para rastrear el desempeño de tu {% data variables.product.prodname_github_app %} y tomar decisiones informadas acerca de los precios, planes, periodos de prueba gratuitos, y de cómo visualizar los efectos de las campañas de marketing.' -redirect_from: - - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing/ - - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing/ - - /apps/marketplace/github-marketplace-insights/ - - /marketplace/github-marketplace-insights - - /developers/github-marketplace/viewing-metrics-for-your-listing -versions: - fpt: '*' -topics: - - Marketplace ---- -Puedes ver las métricas del día anterior (24 horas), de la semana, el mes, o de la duración total de tiempo que ha estado listada tu {% data variables.product.prodname_github_app %}. - -{% note %} - -**Nota:** Ya que el agregar datos es tardado, notarás un atraso ligero en las fechas que se muestran. Cuando seleccionas un periodo de tiempo, puedes ver las fechas exactas para las métricas en la parte superior de la página. - -{% endnote %} - -### Métricas de rendimiento - -La página de perspectivas muestra estas métricas de rendimiento para el periodo de tiempo que selecciones: - -* **Valor de la suscripción:** La ganancia total posible (en dólares estadounidenses) de las suscripciones. Este valor representa la ganancia posible si no se cancela ningún plan o periodo de prueba gratuito para que todas las transacciones de tarjetas bancarias tengan éxito. El valor de la suscripción incluye el valor total de los planes que comeinzan con un periodo de prueba gratuito en el periodo de tiempo seleccionado, aún cuando no hay transacciones financieras en dicho periodo de tiempo. El valor de la suscripción también incluye un valor completo de los planes actualizados en el periodo de tiempo seleccionado pero no incluye la cantidad prorrateada. Para ver y descargar las transacciones individuales, consulta la sección "[transacciones de GitHub Marketplace](/marketplace/github-marketplace-transactions/)". -* **Visitantes:** Cantidad de personas que han visto una página en tu listado de GitHub Apps. Esta cantidad incluye tanto a los visitantes que han iniciado sesión como a los que salen de sesión. -* **Visualizaciones de página:** Cantidad de visualizaciones que han recibido las páginas en tu listado de GitHub Apps. Un solo visitante puede generar más de una visualización de página. - -{% note %} - -**Nota:** El valor estimado de tu suscripción podría ser mucho mayor que el de las transacciones procesadas durante este periodo de tiempo. - -{% endnote %} - -#### Rendimiento de conversión - -* **Visitantes únicos en la página de llegada:** Cantidad de personas que vieron la página de llegada de tu GitHub App. -* **Visitantes únicos de la página pago:** Cantidad de personas que vieron una de tus páginas de pago para tu GitHub App. -* **Página de pago para suscripciones nuevas:** La cantidad total de suscripciones pagadas, periodos de prueb gratuitos, y suscripciones gratuitas. Consulta la sección "Desglose del total de las suscripciones" para encontrar la cantidad específcia de cada tipo de suscripción. - -![Perspectivas de Marketplace](/assets/images/marketplace/marketplace_insights.png) - -Para acceder a las perspectivas de {% data variables.product.prodname_marketplace %}: - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.marketplace_apps %} -4. Selecciona la {% data variables.product.prodname_github_app %} para la cual quisieras ver las perspectivas. -{% data reusables.user-settings.edit_marketplace_listing %} -6. Da clic en la pestaña **Perspectivas**. -7. Opcionalmente, selecciona cualquier periodo de tiempo diferente dando clic en el menú desplegable de dicho periodo en la esquina superior derecha de la página de perspectivas. ![Periodo de tiempo de Marketplace](/assets/images/marketplace/marketplace_insights_time_period.png) diff --git a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md b/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md deleted file mode 100644 index db3d2ff38d..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Visualizar las transacciones para tu listado -intro: 'La página de transacciones de {% data variables.product.prodname_marketplace %} te permite descargar y visualizar todas las transacciones de tu listado de {% data variables.product.prodname_marketplace %}. Puedes ver las transacciones del día anterior (24 horas), de la semana, el mes, o de la duración total de tiempo que ha estado listada tu {% data variables.product.prodname_github_app %}.' -redirect_from: - - /marketplace/github-marketplace-transactions - - /developers/github-marketplace/viewing-transactions-for-your-listing -versions: - fpt: '*' -topics: - - Marketplace ---- -{% note %} - -**Nota:** Ya que el agregar datos es tardado, notarás un atraso ligero en las fechas que se muestran. Cuando seleccionas un periodo de tiempo, puedes ver las fechas exactas para las métricas en la parte superior de la página. - -{% endnote %} - - -Puedes visualizar o descargar los datos de las transacciones para dar seguimiento a la actividad de tus suscripciones. Da clic en el botón de **Exportar CSV** para descargar un archivo de tipo `.csv`. También puedes seleccionar un periodo de tiempo que quieras ver en la página de transacciones para hacer búsquedas dentro de éste. - -### Campos de datos de las transacciones - -* **date:** La fecha de la transacción en formato `aaa-mm-dd`. -* **app_name:** El nombre de la app. -* **user_login:** La información de inicio de sesión del usuario con la suscripción. -* **user_id:** La id del usuario con la suscripción. -* **user_type:** El tipo de cuenta de GitHub, ya sea `User` o `Organization`. -* **country:** El código de tres letras del país. -* **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. - -![Perspectivas de Marketplace](/assets/images/marketplace/marketplace_transactions.png) - -### Acceder a las transacciones de {% data variables.product.prodname_marketplace %} - -Para acceder a las transacciones de {% data variables.product.prodname_marketplace %}: - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -{% data reusables.user-settings.marketplace_apps %} -4. Selecciona la {% data variables.product.prodname_github_app %} para la cual quieras visualizar las transacciones. -{% data reusables.user-settings.edit_marketplace_listing %} -6. Da clic en la pestaña de **Transacciones**. -7. Opcionalmente, selecciona un periodo de tiempo diferente dando clic en el menú desplegable de "Periodo" en la esquina superior derecha de la página de Transacciones. ![Periodo de tiempo de Marketplace](/assets/images/marketplace/marketplace_insights_time_period.png) diff --git a/translations/es-XL/content/developers/github-marketplace/index.md b/translations/es-XL/content/developers/github-marketplace/index.md deleted file mode 100644 index fb648317ce..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Mercado GitHub -intro: 'Lista tus herramientas en {% data variables.product.prodname_dotcom %} Marketplace para que los desarrolladores las utilicen o las compren.' -redirect_from: - - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace/ - - /apps/marketplace/ - - /marketplace -versions: - fpt: '*' -topics: - - Marketplace -children: - - /github-marketplace-overview - - /creating-apps-for-github-marketplace - - /using-the-github-marketplace-api-in-your-app - - /listing-an-app-on-github-marketplace - - /selling-your-app-on-github-marketplace ---- - diff --git a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md deleted file mode 100644 index abfc284abb..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Configurar un webhook para que te notifique sobre los cambios de plan -intro: 'Después de [crear un listado de {% data variables.product.prodname_marketplace %} en borrador] (/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), puedes configurar un webhook que te notifique cuando sucedan cambios en los planes de la cuenta de los clientes. Después de que configures el webhook, puedes [gestionar los tipos de evento de `marketplace_purchase`] (/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) en tu app.' -redirect_from: - - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing/ - - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing/ - - /apps/marketplace/setting-up-github-marketplace-webhooks/creating-a-webhook-for-a-github-marketplace-listing/ - - /apps/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/ - - /marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook - - /developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes -versions: - fpt: '*' -topics: - - Marketplace ---- -El webhook de evento de {% data variables.product.prodname_marketplace %} solo puede configurarse desde la página de listado de {% data variables.product.prodname_marketplace %} de tu aplicación. Puedes configurar el resto de los eventos desde la [página de configuración del desarrollador de la aplicación](https://github.com/settings/developers). Si no has creado un listado de {% data variables.product.prodname_marketplace %}, lee la sección "[Crear un borrador de listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" para aprender cómo hacerlo. - -### Crear un webhook - -Para crear un webhook para tu listado de {% data variables.product.prodname_marketplace %}, da clic en **Webhooks** en la barra lateral de tu [página de listado de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Verás las siguientes opciones que se necesitan para configurar tu webhook: - -#### URL de la carga útil - -{% data reusables.webhooks.payload_url %} - -#### Tipo de contenido - -{% data reusables.webhooks.content_type %} GitHub te recomienda utilizar el tipo de contenido `application/json`. - -#### Secreto - -{% data reusables.webhooks.secret %} - -#### Activo - -Predeterminadamente, las entregas de webhook están "Activas". También puedes elegir inhabilitar la entrega de cargas útiles de webhooks durante el desarrollo si deseleccionas "Activo". Si inhabilitaste las entregas de los webhooks, necesitarás seleccionar "Activo" antes de que emitas tu app para su revisión. - -### Visualizar las entregas de los webhooks - -Una vez que hayas configurado tu webhook de {% data variables.product.prodname_marketplace %}, podrás inspecionar las cargas útiles de las solicitudes de tipo `POST` desde la página del **Webhooks** del [listado de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage) de tu aplicación. GitHub no reenvía los intentos fallidos de entrega. Asegúrate de que tu app pueda recibir toda la carga útil del webhook que envíe GitHub. - -![Inspeccionar las entregas de webhooks de {% data variables.product.prodname_marketplace %} recientes](/assets/images/marketplace/marketplace_webhook_deliveries.png) diff --git a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md b/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md deleted file mode 100644 index eac4561ade..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Hacer un borrador de un listado para tu app -intro: 'Cuando creas un listado de {% data variables.product.prodname_marketplace %}, GitHub lo guarda en modo borrador hasta que emitas la app para su aprobación. Tu listado muestra a los clientes cómo pueden utilizar tu app.' -redirect_from: - - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/ - - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/ - - /apps/marketplace/getting-started-with-github-marketplace-listings/listing-an-app-on-github-marketplace/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/listing-an-app-on-github-marketplace/ - - /apps/adding-integrations/managing-listings-on-github-marketplace/removing-a-listing-from-github-marketplace/ - - /apps/marketplace/managing-github-marketplace-listings/removing-a-listing-from-github-marketplace/ - - /apps/adding-integrations/managing-listings-on-github-marketplace/editing-a-github-marketplace-listing/ - - /apps/marketplace/managing-github-marketplace-listings/editing-a-github-marketplace-listing/ - - /apps/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/ - - /marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing - - /developers/github-marketplace/drafting-a-listing-for-your-app -versions: - fpt: '*' -topics: - - Marketplace ---- -### Crear un borrador nuevo de un listado de {% data variables.product.prodname_marketplace %} - -Solo puedes crear borradores de listados para las apps que sean públicas. Antes de crear tu borrador de listado puedes leer los siguientes lineamientos para escribir y configurar los ajustes en tu listado de {% data variables.product.prodname_marketplace %}: - -* [Escribir descripciones de los listados de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/) -* [Configurar un plan de precios para el listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/) -* [Configurar el Webhook de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/) - -Para crear un listado de {% data variables.product.prodname_marketplace %}: - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.developer_settings %} -3. En la barra lateral izquierda, da clic ya sea en **Apps de OAuth** o **GitHub Apps** dependiendo del tipo de app que estés agregando a {% data variables.product.prodname_marketplace %}. - - {% note %} - - **Nota**: También puedes agregar un listado si navegas a https://github.com/marketplace/new, ves tus apps disponibles, y das clic en **Crear un borrador de un lsitado**. - - {% endnote %} - - ![Selección del tipo de app](/assets/images/settings/apps_choose_app.png) - -4. Selecciona la app que quisieras agregar a {% data variables.product.prodname_marketplace %}. ![Selección de aplicaciones para el listado de {% data variables.product.prodname_marketplace %}](/assets/images/github-apps/github_apps_select-app.png) -{% data reusables.user-settings.edit_marketplace_listing %} -5. Una vez que hayas creado un borrador nuevo de un listado, verás un resumen de las secciones que necesitas visitar antes de que tu listado de {% data variables.product.prodname_marketplace %} esté completo. ![Listado de GitHub Marketplace](/assets/images/marketplace/marketplace_listing_overview.png) - - -{% note %} - -**Nota:** En la sección de "información de contacto" de tu listado, te recomendamos utilizar direcciones de correo electrónico individuales en vez de direcciones grupales como support@domain.com. GitHub utilizará estas direcciones de correo electrónico para contactarte con respecto a las actualizaciones a {% data variables.product.prodname_marketplace %} que pudieran afectar tu listado, a los lanzamientos de nuevas características, a las oportunidades de marketing, a los pagos, y a la información sobre conferencias y patrocinios. - -{% endnote %} - -### Editar tu listado - -Ya que hayas creado un borrador de listado de {% data variables.product.prodname_marketplace %}, puedes regresar a modificar la información de éste en cualquier momento. Si tu app ya se aprobó y está en {% data variables.product.prodname_marketplace %}, puedes editar la información e imágenes en tu listado, pero no podrás cambiar los planes de precios que ya estén publicados. Consulta la sección "[Configurar el plan de pagos de un listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". - -### Emitir tu app - -Ya que hayas completado tu listado de {% data variables.product.prodname_marketplace %}, puedes emitirlo para su revisión a través de la página **Resumen**. Necesitas leer y aceptar el "[Acuerdo de Desarrollador de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-developer-agreement/)", y luego puedes dar clic en **Emitir para revisión**. Después de emitir tu app para su revisión, el equipo de incorporación de {% data variables.product.prodname_marketplace %} te contactará con información adicional acerca del proceso de incorporación. Puedes aprender más acerca del proceso de integración y revisión de seguridad en la sección "[Comenzar con {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/)". - -### Eliminar un listado de {% data variables.product.prodname_marketplace %} - -Si ya no quieres listar tu app en {% data variables.product.prodname_marketplace %}, contacta a [marketplace@github.com](mailto:marketplace@github.com) para eliminar tu listado. diff --git a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md b/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md deleted file mode 100644 index df57b2e5a4..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Listar una app en GitHub Marketplace -intro: 'Aprende sobre los requisitos y mejores prácticas para listar tu app en {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /apps/adding-integrations/listing-apps-on-github-marketplace/ - - /apps/marketplace/listing-apps-on-github-marketplace/ - - /apps/marketplace/getting-started-with-github-marketplace-listings/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/ - - /apps/adding-integrations/managing-listings-on-github-marketplace/ - - /apps/marketplace/managing-github-marketplace-listings/ - - /apps/marketplace/listing-on-github-marketplace/ - - /marketplace/listing-on-github-marketplace -versions: - fpt: '*' -topics: - - Marketplace -children: - - /drafting-a-listing-for-your-app - - /writing-a-listing-description-for-your-app - - /setting-pricing-plans-for-your-listing - - /configuring-a-webhook-to-notify-you-of-plan-changes - - /submitting-your-listing-for-publication ---- - diff --git a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md deleted file mode 100644 index 58472e0112..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Configurar planes de precios para tu listado -intro: 'Cuando [listas tu app en {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/), puedes elegir proporcionarla como un servicio gratuito o venderla. Si planeas vender tu app, puedes crear planes de precio diferentes para los diferentes escalones de características.' -redirect_from: - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/pricing-payments-and-free-trials/setting-a-github-marketplace-listing-s-pricing-plan/ - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans/ - - /apps/marketplace/pricing-payments-and-free-trials/about-github-marketplace-pricing-plans/ - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/managing-github-marketplace-listings/changing-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/ - - /marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan - - /developers/github-marketplace/setting-pricing-plans-for-your-listing -versions: - fpt: '*' -topics: - - Marketplace ---- -### Crear planes de precios - -Para aprender sobre los planes de precios que ofrece {% data variables.product.prodname_marketplace %}, consulta la sección "[Planes de Precios de {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/github-marketplace-pricing-plans/)". También te resultarán útiles los lineamientos de facturación que se encuentran en "[Vender tu app](/marketplace/selling-your-app/)". - -Los planes de precios pueden estar publicados o en forma de borrador. Si no has emitido tu listado de {% data variables.product.prodname_marketplace %} para su aprobación, un listado publicado funcionará de la misma forma que un listado en borrador hasta que se apruebe tu app y se liste en {% data variables.product.prodname_marketplace %}. Los listados en borrador te permiten crear y guardar planes de precios nuevos sin ponerlos como disponibles en tu página de listado de {% data variables.product.prodname_marketplace %}. Una vez que publicas el plan de precios, este se mostrará disponible para que los clientes lo compren de inmediato. Puedes publicar hasta 10 planes de precios. - -Para crear un plan de precios para tu listado de {% data variables.product.prodname_marketplace %}, da clic en **Planes y precios** en la barra lateral izquierda de tu [página de listado de{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Si aún no creas un listado de {% data variables.product.prodname_marketplace %}, lee la sección "[Crear un borrador de listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" para aprender cómo hacerlo. - -Cuando das clic en **Nuevo borrador de plan**, verás un formato que te permite personalizar tu plan de precios. Necesitarás configurar los siguientes cambios para crear un plan de precios: - -#### Nombre del plan - -El nombre de tu plan de precios aparecerá en la página de llegada de tu app en {% data variables.product.prodname_marketplace %}. Puedes personalizar el nombre de tu plan de precios para apegarte a los recursos del plan, al tamaño de la compañía que lo utilizará, o lo que sea. - -#### Modelos de precios - -##### Planes gratuitos - -{% data reusables.marketplace.free-apps-encouraged %} Un plan gratuito aún necesitará que gestiones los flujos de facturación para las [compras nuevas](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/) y las [cancelaciones](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/). Consulta la sección "[Flujos de facturación](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)" para obtener más detalles. - -##### Planes de tasa fija - -Los planes de tasa fija te permiten ofrecer tu servicio a los clientes por una cuota fija. {% data reusables.marketplace.marketplace-pricing-free-trials %} - -Debes configurar un precio tanto mensual como anual para las suscripciones en dólares estadounidenses para los planes de tasa fija. estadounidenses para los planes de tasa fija. - -##### Planes por unidad - -Los precios por unidad te permiten ofrecer tu app en unidades. Por ejemplo, una unidad puede ser una persona, una plaza o un usuario. Necesitarás proporcionar un nombre para la unidad y configurar un precio tanto mensual como anual para las suscripciones en dólares estadounidenses. estadounidenses. - -#### Disponible para - -Los planes de precios de {% data variables.product.prodname_marketplace %} pueden aplicar para las **cuentas de organización y personales**, **únicamente para cuentas personales**, o **únicamente para cuentas de organización**. Por ejemplo, si tu plan de precios es por unidad y proporciona plazas múltioples, seleccionarías **únicamente para cuentas de organización**, ya que no hay manera de asignar plazas a las personas de la organización desde una cuenta personal. - -#### Descripción corta - -Escribe un resumen de los detalles del plan de precios. La descripción puede incluir el tipo de cliente para el cual se creó el plan o los recursos que dicho plan incluye. - -#### Viñetas - -Puedes escribir hasta cuatro viñetas que incluyan más detalles acerca de tu plan de precios. Estas viñetas pueden incluir los casos de uso de tu app o listar información más detallada acerca de los recursos o de las características que incluye el plan. - -### Cambiar un plan de precios del listado de {% data variables.product.prodname_marketplace %}. - -Si ya no se necesita un plan de precios para tu plan de {% data variables.product.prodname_marketplace %} o si necesitas ajustar los detalles de tus precios, puedes eliminarlo. - -![Botón para eliminar tu plan de precios](/assets/images/marketplace/marketplace_remove_this_plan.png) - -Una vez que publicas un plan de precios para una app que ya esté listada en {% data variables.product.prodname_marketplace %}, no podrás hacer cambios al plan. En vez de ésto, necesitarás eliminar el plan de precios. Los clientes que ya compraron el plan de precios que se eliminó seguirán utilizándolo hasta que decidan abandonarlo y migrarse a un plan de precios nuevo. Para encontrar más información acerca de los planes de precios, consulta la sección "[planes de precios en {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/github-marketplace-pricing-plans/)". - -Una vez que elimines el plan de precios, los usuarios ya no podrán comprar tu app utilizando dicho plan. Los usuarios existentes del plan que eliminaste seguirán en ese plan hasta que cancelen su suscripción. - -{% note %} - -**Nota:** {% data variables.product.product_name %} no puede eliminar a los usuarios de un plan de precios que ya no existe. Puedes lanzar una campaña para exhortar a los usuarios a mejorar o degradar su suscripción para el plan de precios que eliminaste hacia un plan nuevo. - -{% endnote %} - -Puedes inhabilitar los periodos de prueba gratuitos en GitHub Marketplace sin retirar el plan de precios, pero esto te impide inciar periodos de prueba gratuitos en el futuro para este plan. Si eliges inhabilitar los periodos de prueba gratuitos para un plan de precios, los usuarios que ya se hayan registrado pueden completar su periodo de prueba gratuito. - -Después de dar de baja un plan de precios, puedes crear uno nuevo con el mismo nombre que aquél que eliminaste. Por ejemplo, si tienes un plan de precios "Pro" pero necesitas cambiar el precio de tasa fija, puedes eliminar el plan "Pro" y crear uno nuevo, que también sea "Pro" con un precio actualizado. Los usuarios podrán comprar el nuevo plan de precios inmediatamente. diff --git a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-review.md b/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-review.md deleted file mode 100644 index f95c1d4168..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-review.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Emitir tu listado para revisión -intro: 'Puedes emitir tu listado como una app verificada o sin verificar para que la utilice la comunidad de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review - - /developers/github-marketplace/submitting-your-listing-for-review -versions: - free-pro-team: '*' ---- -Una vez que hayas completado el listado de tu app, verás dos botones que te permiten emitirla, uno para las verificadas y otro para las no verificadas. El botón de **Solicitud** para publicar sin verificación no estará disponible si publicaste algún plan de precios pagado. - -![Botón para solicitudes verificadas y sin verificar](/assets/images/marketplace/marketplace-request-button.png) - -{% data reusables.marketplace.launch-with-free %} - -Antes de que emitas una app verificada, necesitarás integrar el flujo de facturación y webhook de {% data variables.product.prodname_marketplace %} a tu app existente. Consulta las [Apps verificadas](/marketplace/#verified-apps) para encontrar los pasos necesarios para emitir tu app. - -Si cumpliste con los [requisitos](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/) para verificar un listado de {% data variables.product.prodname_marketplace %} y te integraste con la API de {% data variables.product.prodname_marketplace %}, ¡puedes emitir tu listado! - -Después de que emitas tu listado para su revisión, el equipo de incorporación de {% data variables.product.prodname_marketplace %} te contactará para darte información adicional. diff --git a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md deleted file mode 100644 index 1e7aa18c10..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: Escribir la descripción de un listado para tu app -intro: 'Para [Listar tu app](/marketplace/listing-on-github-marketplace/) en {% data variables.product.prodname_marketplace %}, necesitarás escribir una descripción de ésta y proporcionar imágenes que se apeguen a los lineamientos de GitHub.' -redirect_from: - - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions/ - - /apps/adding-integrations/listing-apps-on-github-marketplace/guidelines-for-creating-a-github-marketplace-listing/ - - /apps/marketplace/listing-apps-on-github/guidelines-for-creating-a-github-marketplace-listing/ - - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-creating-github-marketplace-listing-images/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/creating-github-marketplace-listing-images/ - - /apps/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/ - - /marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions - - /developers/github-marketplace/writing-a-listing-description-for-your-app -versions: - fpt: '*' -topics: - - Marketplace ---- -Aquí te mostramos los lineamientos de los campos que necesitas llenar en la sección **Listar descripción** del borrador de tu listado. - -### Nomencltura y enlaces - -#### Nombre del listado - -El nombre de tu app se mostrará en la [página de inicio de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). El nombre se limita a 255 caracteres. - -#### Descripción muy corta - -La comunidad verá la descripción "muy corta" debajo del nombre de tu app en la [página principal de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). - -![Descripción corta de la app en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_short_description.png) - -##### Longitud - -Te remcomendamos mantener un largo de 40 a 80 caracteres para las descripciones cortas. Aunque se te permite utilizar más caracteres, las descripciones concisas son más fáciles de leer y más rápidas de entender para los clientes. - -##### Contenido - -- Describe la funcionalidad de la app. No utilices este espaccio para un llamado a la acción. Por ejemplo: - - **RECOMENDADO:** Una administración de proyectos ligera para los informes de problemas de GitHub - - **NO RECOMENDADO:** Administración de proyectos e informes de problemas en GitHub - - **Tip:** Pon los verbos en tercera persona del singular en las llamadas a la acción para convertirlas en una descripción aceptable: _Administra tus proyectos e informes de problemas en GitHub_ - -- No repitas el nombre de la app en la descripción. - - **RECOMENDADO:** Una herramienta de integración contínua nativa para el contenedor - - **NO RECOMENDADO:** Skycap es una herramienta de integración contínua nativa para el contenedor - -##### Formato - -- Apégate siempre al uso de mayúsculas correcto en las oraciones. Utiliza mayúsucula únicamente en la primera letra y en los nombres propios. - -- No uses puntuación al final de tu descripción corta. Las descripciones cortas no deben incluir oraciones completas, y en definitiva, no deben incluir más de una oración. - -- Usa mayúscula inicial únicamente en nombres propios. Por ejemplo: - - **RECOMENDADO:** Automatización de entrega en un solo click para desarrolladores web - - **NO RECOMENDADO:** Automatización de entrega en un solo click para Desarrolladores Web - -- Utiliza siempre una [coma serial](https://en.wikipedia.org/wiki/Serial_comma) en las listas. - -- Evita referirte a la comunidad de GitHub como "usuarios". - - **RECOMENDADO:** Crea informes de problemas automáticamente para las personas de tu organización - - **NO RECOMENDADO:** Crea informes de problemas automáticamente para los usuarios de una organización - -- Evita utilizar acrónimos a menos de que estén bien establecidos (tal como API). Por ejemplo: - - **RECOMENDADO:** Tableros de tareas ágiles, estimados y reportes sin salir de GitHub - - **NO RECOMENDADO:** Tableros de tareas ágiles, estimados, y reportes sin dejar la IU de GitHub - -#### Categorías - -Las apps en {% data variables.product.prodname_marketplace %} se pueden mostrar por categoría. Selecciona la categoría que describa mejor la funcionalidad principal de tu app en el menú desplegable de **Categoría principal** y, opcionalmente, selecciona una **Categoría secundaria** si es que describe mejor a tu app. - -#### Lenguajes compatibles - -Si tu app funciona únicamente con lenguajes específicos, selecciona hasta 10 lenguajes de programación que sean compatibles con ella. Estos lenguajes se muestran en la página del listado de {% data variables.product.prodname_marketplace %} de tu app. Este campo es opcional. - -#### Listar las URL - -**URL Requeridas** -* **URL de servicio al cliente:** La URL de una página web a la que llegarán tus clientes cuando tienen preguntas de la cuenta, producto o soporte técnico. -* **URL de la política de privacidad:** La página web que muestra la política de privacidad de tu app. -* **URL de la instalación:** Este campo se muestra únicamente para las apps de OAuth. (Las GitHub Apps no utilizan esta URL porque utilizan la URL de configuración opcional de la página de su página de configuración). Cuando un cliente compra tu App de OAuth, GitHub redireccionará a los clientes a la URL de la instalación después de que la instalen. Necesitarás redirigir a los clientes a `https://github.com/login/oauth/authorize` para comenzar el flujo de autorizaciones de OAuth. Consulta la sección "[Compras nuevas de Apps de OAuth](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para recibir más detalles al respecto. Omite este campo si estás listando una GitHub App. - -**URL opcionales** -* **URL de la empresa:** Un enlace al sitio web de tu empresa. -* **URL de estado:** Un enlace a la página web que muestra el estado de tu app. Las páginas de estado incluyen reportes de incidentes actuales y en forma de historial, el estado de tiempo activo de la aplicación web, y los periodos programados de mantenimiento. -* **URL de Documentación:** Un enlace a la documentación que muestra a los clientes cómo utilizar tu app. - -### Logo y tarjeta de características - -{% data variables.product.prodname_marketplace %} muestra todos los listados con un logo de imagen cuadrada dentro de una insignia circular para distinguir a las apps visualmente. - -![Imágenes de logo e insignia en GitHub marketplace](/assets/images/marketplace/marketplace-logo-and-badge.png) - -Una tarjeta de características consiste en el logo, nombre e imagen personalizada de fondo para tu app, la cual captura la personalidad de ésta. {% data variables.product.prodname_marketplace %} muestra esta tarjeta si tu app es una de las cuatro apps que se presentan aleatoriamente en la parte superior de la [página principal](https://github.com/marketplace). Cada descripción muy corta de las apps se muestra debajo de su tarjeta de características. - -![Tarjeta de características](/assets/images/marketplace/marketplace_feature_card.png) - -En medidad que subas imágenes y selecciones los colores, tu borrador de listado de {% data variables.product.prodname_marketplace %} mostrará una vista previa de tu logo y de tu tarjeta de características. - -##### Lineamientos para los logos - -Debes cargar una imagen personalizada para el logo. Para el caso de la insignia, elige un color de fondo. - -- Carga una imagen de logo que tenga por lo menos 200 pixeles por 200 pixeles para que éste no tenga que escalarse ascendentemente cuando se publique tu listado. -- Los logos se cortarán en forma de cuadrado. Te recomendamos cargar un archivo de imagen cuadrado con tu logo en el centro. -- Para obtener los mejores resultados, carga una imagen de logo con un fondo transparente. -- Para darle la apariencia contínua a la insignia, elige un color de fondo que empate con el color (o con la transparencia) de tu imagen de logo. -- Evita utilizar las imágenes de logo que tienen texto o palabras. Los logos con texto no se escalan bien en pantallas pequeñas. - -##### Lineamientos para las tarjetas de características - -Debes cargar una imagen personalizada de fondo para la tarjeta de características. Elige el color del texto para el nombre de la app. - -- Utiliza un patrón o textura en la imagen de fondo para dar a tu tarjeta una identidad visual específica y ayudar a que resalten contra el fondo oscuro de la página de inicio de {% data variables.product.prodname_marketplace %}. Las tarjetas de caracetrísticas capturan la personalidad de la marca de tu app. -- La imagen de fondo mide 065 pixeles x 482 pixeles (ancho x alto). -- Elige un color de texto para el nombre de tu app, el cual se muestre claramente sobre la imagen de fondo. - -### Detalles del listado - -Para obtener la página de llegada de tu app, da clic en su nombre desde la página principal de {% data variables.product.prodname_marketplace %} o desde su página de categoría. La página de llegada muestra una descripción más larga de tu app, la cual incluye dos partes: una "Descripción de introducción" y una "Descripción detallada". - -Tu "Descripción de introducción" se muestra en la parte superior de la página de llegada de {% data variables.product.prodname_marketplace %} para tu app. - -![Descripción de introducción en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_intro_description.png) - -El dar clic en **Leer más...** mostrará la "Descripción detallada". - -![Descripción detallada en {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_detailed_description.png) - -Sigue estos lineamientos para escribir estas descripciones. - -#### Longitud - -Te recomendamos escribir un resumen de alto nivel que se componga de una o dos oraciones de entre 150 y 250 caracteres en el campo "Descripción de introducción" cuando [listes tu aplicación](/marketplace/listing-on-github-marketplace/). Aunque se te permite utilizar más caracteres, los resúmenes concisos son más fáciles de leer y más rápidas de entender para los clientes. - -Puedes agregar más información en el campo opcional "Descripción detallada". Encuentras esta descripción al dar clic en **Leer más...** debajo de la descripción de introducción en la página de llegada de tu app. Una descripción detallada consiste en 3-5 [propuestas de valor](https://en.wikipedia.org/wiki/Value_proposition) con 1-2 oraciones que se describen una a la otra. Puedes utilizar hasta 1,000 caracteres para esta descripción. - -#### Contenido - -- Inicia siempre con el nombre de tu aplicación en las descripciones de introducción. - -- Escribe siempre las descripciones y propuestas de valor utilizando la voz activa. - -#### Formato - -- Utiliza siempre las mayúsculas adecuadamente en las oraciones de los títulos para las propuestas de valor. Utiliza mayúsucula únicamente en la primera letra y en los nombres propios. - -- Utiliza puntos en tus descripciones. Evita los signos de admiración. - -- No utilices signos de puntuación al final de tus títulos para las propuestas de valor. Los títulos de propuestas de valor no deben incluir oraciones completas ni más de una oración. - -- Para cada propuesta de valor, incluye un título seguido de un párrafo de descripción. Da formato al título como un [encabezado nivel tres](/articles/basic-writing-and-formatting-syntax/#headings) utilizando lenguaje de marcado (Markdown). Por ejemplo: - - - ### Adquiere las habilidades que necesitas - - GitHub Learning Lab te puede ayudar a aprender cómo utilizar GitHub, a comunicarte de forma más efectiva con el lenguaje de Markdown, a gestionar conflictos de fusión, y más. - -- Usa mayúscula inicial únicamente en nombres propios. - -- Utiliza siempre la [coma serial](https://en.wikipedia.org/wiki/Serial_comma) en las listas. - -- Evita referirte a la comunidad de GitHub como "usuarios". - - **RECOMENDADO:** Crea informes de problemas automáticamente para las personas de tu organización - - **NO RECOMENDADO:** Crea informes de problemas automáticamente para los usuarios de una organización - -- Evita utilizar acrónimos a menos de que estén bien establecidos (tal como API). - -### Impresiones de pantalla de los productos - -Puedes cargar hasta cinco impresiones de pantalla para tu app para que se muestren en su página de llegada. Agrega una captura opcional a cada impresión de pantalla para proporcionar contexto. Después de cargar tus impresiones de pantalla, puedes arrastrarlas para que tomen el órden en el que quieras que se muestren dentro de la página de llegada. - -#### Lineamientos para las impresiones de pantalla - -- Las imágenes deben tener resolución alta (por lo menos 1200px de ancho). -- Todas las imágenes deben tener la misma altura y ancho (proporción de aspecto) para evitar los saltos de página cuando las personas den clic de una imagen a otra. -- Muestra tanto de la interface de usuario como sea posible para que las personas pueden ver lo que hace tu app. -- Cuando tomes una impresión de pantalla de tu app en un buscador, incluye solamente el contenido en la ventana a mostrar. Evita incluir la barra de dirección, la barra de título o los iconos de la barra de herramientas, ya que estos no se escalan bien cuando se miran desde pantallas más pequeñas. -- GitHub muestra las impresiones de pantalla que cargues en una caja dentro de la página de llegada de tu app, así que no necesitas agregar cajas o márgenes al rededor de tus impresiones de pantalla. -- Las capturas son más efectivas cuando son cortas y concisas. - -![Imagen de impresión de pantalla en GitHub Marketplace](/assets/images/marketplace/marketplace-screenshots.png) diff --git a/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md b/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md deleted file mode 100644 index c302aa7507..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Facturar a los clientes -intro: 'Las apps en {% data variables.product.prodname_marketplace %} deben apegarse a los lineamientos de facturación de GitHub y apoyar a los servicios recomendados. El seguir nuestros lineamientos ayuda a los clientes a navegar en el proceso de facturación sin ninguna sorpresa.' -redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace/ - - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace/ - - /marketplace/selling-your-app/billing-customers-in-github-marketplace - - /developers/github-marketplace/billing-customers -versions: - fpt: '*' -topics: - - Marketplace ---- -### Entender el ciclo de facturación - -Los clientes pueden escoger un ciclo mensual o anual cuando compran tu app. Todos los cambios que los clientes hagan a los ciclos de facturación y a la selección de plan activaran un evento de `marketplace_purchase`. Puedes referirte a la carga útil del webhook de `marketplace_purchase` para ver qué ciclo de facturación selecciona un usuario y cuándo comienza la siguiente fecha de facturación (`effective_date`). Para obtener más información acerca de las cargas útiles de los webhooks, consulta la sección "[eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)". - -### Proporcionar servicios de facturación en la IU de tu app - -Los clientes deben poder realizar las siguientes acciones desde el sitio web de tu app: -- Los clientes deben poder modificar o cancelar sus planes de {% data variables.product.prodname_marketplace %} para las cuentas de organización y personales por separado. -{% data reusables.marketplace.marketplace-billing-ui-requirements %} - -### Servicios de facturación para mejoras, decrementos y cancelaciones - -Sigue estos lineamientos para las mejoras, decrementos y cancelaciones para mantener un proceso de facturación limpio y consistente. Para obtener instrucciones más detalladas acerca de los eventos de compra de {% data variables.product.prodname_marketplace %}, consulta la sección "[Flujos de facturación](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)". - -Puedes utilizar la llave de `effective_date` del webhook de `marketplace_purchase` para determinar cuando ocurrirá un cambio de plan y sincronizar la [Lista de cuentas para un plan](/v3/apps/marketplace/#list-accounts-for-a-plan) de vez en cuando. - -#### Mejoras - -Cuando un cliente mejora su plan de precios o cambia su ciclo de facturación de mensual a anual, deberás hacerles el cambio efectivo inmediatamente. Tienes que aplicar un descuento prorrateado para el plan nuevo y cambiar el ciclo de facturación. - -{% data reusables.marketplace.marketplace-failed-purchase-event %} - -Para obtener información acerca de los flujos de trabajo de mejora y decremento en tu app, consulta la sección "[Mejorar y decrementar los planes](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)". - -#### Decrementos y cancelaciones - -Los decrementos ocurren cuando un cliente se cambia de un plan pagado a uno gratuito, selecciona un plan con un costo menor al actual, o cambia su ciclo de facturación de anual a mensual. Cuando suceden los decrementos o cancelaciones, no necesitas proporcionar un reembolso. En vez de esto, el plan actual se mantendrá activo hasta el último día del ciclo de facturación actual. El evento `marketplace_purchase` se enviará cuando el nuevo plan entre en vigor al inicio del siguiente ciclo de facturación del cliente. - -Cuando un cliente cancela un plan, debes: -- Degradarlos automáticamente al plan gratuito, si es que existe. - - {% data reusables.marketplace.cancellation-clarification %} -- Habilitarlos para mejorar el plan a través de GitHub si es que quisieran continuar con él más adelante. - -Para obtener información acerca de construir flujos de trabajo de cancelación en tu app, consulta la sección "[Planes de cancelación](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)". diff --git a/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md b/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md deleted file mode 100644 index 10c790afd7..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Vender tu app en GitHub Marketplace -intro: 'Aprende sobre los requisitos y mejores prácticas para vender tu app en {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/ - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/ - - /apps/marketplace/pricing-payments-and-free-trials/ - - /apps/marketplace/selling-your-app/ - - /marketplace/selling-your-app -versions: - fpt: '*' -topics: - - Marketplace -children: - - /pricing-plans-for-github-marketplace-apps - - /billing-customers - - /receiving-payment-for-app-purchases ---- - diff --git a/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md deleted file mode 100644 index 811c4c7d01..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Planes de precios para las apps de GitHub Marketplace -intro: 'Los planes de precios te permiten darle a tu app diferentes recursos o niveles de servicio. Puedes ofrecer hasta 10 planes de precios en tu listado de {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans/ - - /marketplace/selling-your-app/github-marketplace-pricing-plans - - /developers/github-marketplace/pricing-plans-for-github-marketplace-apps -versions: - fpt: '*' -topics: - - Marketplace ---- -Los planes de precios en {% data variables.product.prodname_marketplace %} pueden ser gratuitos o por unidad, y GitHub lista los precios en dólares estadounidenses. Los clientes compran tu app utilizando un método de pago adjunto a sus cuentas de {% data variables.product.product_name %}, sin tener que salir de GitHub.com. No tienes que escribir ningún tipo de código para realizar transacciones de facturación, pero tendrás que gestionar los [flujos de facturación](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows) para los eventos de compra. - -Si la app que estás listando en {% data variables.product.prodname_marketplace %} tiene opciones de plan múltiples, puedes configurar los planes de precios correspondientes. Por ejemplo, si tu app tiene dos opciones de plan, u plan de código abierto y un plan profesional, puedes configurar un plan de precios gratuito para tu plan de código abierto y un plan de tasa fija para tu plan profesional. Cada listado de {% data variables.product.prodname_marketplace %} debe tener un precio mensual y anual para cada plan que se liste. - -Para obtener más información sobre cómo crear un plan de precios, consulta la sección "[Configurar un plan de precios del listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". - -{% note %} - -**Nota:** Si estás listando una app en {% data variables.product.prodname_marketplace %}, no puedes listarla con un plan de precios gratuito si ofreces un servicio de pago fuera de {% data variables.product.prodname_marketplace %}. - -{% endnote %} - -### Tipos de planes de precios - -Los **planes de precios gratuitos** son completamente gratuitos para los usuarios. Si configuras un plan de precios gratuito, no puedes cobrar a los usuarios que elijan dicho plan por utilizar tu app. Puedes crear planes tanto de pago como gratuitos para tu listado. Las apps gratuitas sin verificar no necesitan implementar ningún flujo de facturación. Las apps gratuitas que se verifican en GitHub necesitan implementar flujos de facturación para las compras nuevas y las cancelaciones, pero no necesitan implementarlos para los periodos de prueba gratuitos, las mejoras y las degradaciones. Si agregas un plan de pago a un app que ya listaste en {% data variables.product.prodname_marketplace %} como un servicio gratuito, necesitarás volver a emitir la app para su revisión. - -Los **planes de precios de tasa fija** cobran una cuota fija mensual o anualmente. - -Los **planes de precios por unidad** cobran una cuota fija por un periodo mensual o anual para una unidad que especifiques. Una "unidad" puede ser lo que tu escojas (por ejemplo, un usuario, una plaza, una persona). - -Los **periodos de prueba gratuitos de Marketplace** proporcionan periodos de prueba gratuitos de 14 días para los clientes en aplicaciones de OAuth o GitHub Apps. Cuando [configuras un plan de precios de Marketplace](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/), puedes seleccionar la opción para porporcionar un periodo de prueba gratuito para los planes de tasa fija o de unidad. - -### Periodos de prueba gratuitos - -Los clientes pueden iniciar un periodo de prueba gratuito para cualquier plan de pago en un listado de Marketplace, pero no podremos crear más de un periodo de prueba gratuito por producto de Marketplace. - -Los periodos de prueba gratuitos tienen una longitud fija de 14 días. Se les notifica a los clientes 4 días antes del fin de su periodo de pruebas gratuito (en el día 11 del este periodo) sobre la mejora que se hará a su plan. Al final del periodo de pruebas gratuito, los clientes se matricularán automáticamente en el plan desde el cual estaban generando el periodo gratuito en caso de que no lo cancelen. - -Consulta la sección "[Compras nuevas y periodos de prueba gratuitos](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para obtener los de talles de cómo manejar los periodos de prueba gratuitos en tu app. - -{% note %} - -**Nota:** GitHub espera que borres cualquier dato privado del cliente dentro de los primeros 30 días después de que se cancela una prueba, iniciando con la recepción del evento de cancelación. - -{% endnote %} diff --git a/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md b/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md deleted file mode 100644 index b163f42bd7..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Recibir pagos por las compras de las apps -intro: 'Al final de cada mes, recibiras los pagos de tus listados de {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing/ - - /apps/marketplace/pricing-payments-and-free-trials/receiving-payment-for-a-github-marketplace-listing/ - - /apps/marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings/ - - /marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings - - /developers/github-marketplace/receiving-payment-for-app-purchases -versions: - fpt: '*' -topics: - - Marketplace ---- -Después de que se cree y apruebe tu listado de {% data variables.product.prodname_marketplace %}, proporcionaras los detalles de pago a {% data variables.product.product_name %} como parte del proceso de incorporación. - -Una vez que tu ganancia alcance un mínimo de $500 dólares. S. Durante el mes, recibirás un pago electrónico de {% data variables.product.product_name %} por 75% del precio de las ventas. - -{% data reusables.apps.marketplace_revenue_share %} diff --git a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md b/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md deleted file mode 100644 index 07f010ec63..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Gestionar las compras nuevas y las pruebas gratuitas -intro: 'Cuando un cliente compra un plan de pago, una prueba gratuita, o la versión gratuita de tu app de {% data variables.product.prodname_marketplace %}, recibirás el webhook de [evento de `marketplace_purchase`] (/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) con la acción `comprado`, lo cual inicia el flujo de compra.' -redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps/ - - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/ - - /marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials - - /developers/github-marketplace/handling-new-purchases-and-free-trials -versions: - fpt: '*' -topics: - - Marketplace ---- -{% warning %} - -Si ofreces una GitHub App en {% data variables.product.prodname_marketplace %}, ésta debe identificar a los usuarios utilizando el flujo de autorización de OAuth. No necesitas configurar un a App de OAuth por separado para apoyar a este flujo. Consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obtener más información. - -{% endwarning %} - -### Paso 1. Compra inicial y evento de webhook - -Antes de qeu un cliente compre tu app de {% data variables.product.prodname_marketplace %}, ellos elligen un [plan del listado](/marketplace/selling-your-app/github-marketplace-pricing-plans/). También eligen si quieren comprar la app desde su cuenta personal o su cuenta de organización. - -El cliente completa la compra dando clic en **Completar orden y comenzar con la instalación**. - -Entonces GitHub envía a tu app el webhook de la [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) con la acción `purchased`. - -Lee el objeto `effective_date` y `marketplace_purchase` del webhook de `marketplace_purchase` para determinar qué plan compró el cliente, cuándo inicia el ciclo de facturación, y cuándo comienza el siguiente ciclo de facturación. - -Si tu app ofrece una prueba gratuita, lee el atributo `marketplace_purchase[on_free_trial]` del webhook. Si el valor es `true`, tu app necesitará rastrear la fecha de inicio de la prueba gratuita (`effective_date`) y la fecha en la cual termina éste (`free_trial_ends_on`). Utiliza la fecha `free_trial_ends_on` para mostrar los días restantes en una prueba gratuita en la IU de tu app. Puedes hacerlo ya sea en un letrero o en tu [IU de facturación](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). Para aprender cómo manejar las cancelaciones antes de que finalice una prueba gratuita, consulta la sección "[Cancelar planes](/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/)". Consulta la sección "[Actualizar y degradar planes](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/)" para encontrar cómo hacer la transición de una prueba gratuita a un plan de pago cuando ésta caduque. - -Consulta la sección "[eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" para encontrar un ejemplo de la carga últil del evento `marketplace_purchase`. - -### Paso 2. Instalación - -Si tu app es una GitHub App, GitHub pide al cliente que seleccione a qué repositorios puede acceder la app cuando la compran. Entonces, GitHub instala la app en la cuenta que escogió el cliente y le otorga acceso a los repositorios seleccionados. - -En este punto, si especificaste una **URL de configuración** en los ajustes de tu GitHub App, GitHub redirigirá al cliente hacia esa URL. Si no especificas una URL de configuración, no podrás gestionar las compras de tu GitHub App. - -{% note %} - -**Nota** La **URL de configuración** se describe como opcional en los ajustes de la GitHub App, pero es un campo requerido si quieres ofrecer tu app en {% data variables.product.prodname_marketplace %}. - -{% endnote %} - -Si tu app es una App de OAuth, GitHub no la instala en ningún lugar. En vez de esto, GitHub redirige al usuario a la **URL de instalación** que especificaste en tu [listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). - -Cuando un cliente compra una App de OAuth, GitHub lo redirige a la URL que escoges (ya sea de configuración o de instalación) y ésta nicluye el plan de precios que eligió el cliente como un parámetro de consulta: `marketplace_listing_plan_id`. - -### Paso 3. Autorización - -Cuando un cliente compra tu app, debes enviar a dicho cliente a través del flujo de autorización de OAuth: - -* Si tu app es una GitHub App, inicia el flujo tan pronto GitHub redireccione al cliente a la **URL de configuración**. Sigue los pasos en la sección "[Identificar y autorizar a los usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". - -* Si tu app es una App de OAuth, inicia el flujo de autorización tan pronto como GitHub redirija al usuario a la **URL de instalación**. Sigue los pasos de la sección "[Autorizar las Apps de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/)". - -Para cualquier tipo de app, el primer paso es redirigir al cliente a https://github.com/login/oauth/authorize. - -Después de que el ciente complete la autorización, tu app recibirá un token de acceso de OAuth para el cliente. Necesitas este token para el siguiente paso. - -{% note %} - -**Nota:** Cuando autorices a un cliente para una prueba gratuita, otórgales el mismo acceso que tendrían en el plan de pago. Los migrarás al plan pagado después de que termine el periodo de pruebas. - -{% endnote %} - -### Paso 4. Aprovisionar las cuentas de los clientes - -Tu app debe aprovisionar una cuenta de cliente para cada compra nueva. Mediante el uso del token de acceso que recibiste para el cliente en el [Paso 3. Autorización](#step-3-authorization), llama a la terminal "[Listar suscripciones para el usuario autenticado](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user)". La respuesta incluirá la información de `account` del cliente y mostrará si están en una prueba gratuita (`on_free_trial`). Utiliza esta información para completar el aprovisionamiento y la configuración. - -{% data reusables.marketplace.marketplace-double-purchases %} - -Si la compra es para una organización y es por usuario, puedes solicitar al cliente que escoja qué miembros de la organización tendrán acceso a la app que se compró. - -Puedes personalizar la forma en la que los miembros de la organización reciben acceso a tu app. Aquí hay algunas sugerencias: - -**Precios con tasa fija:** Si la compra se hace para una organización que utiliza precios de tasa fija, tu app puede [obtener todos los miembros de la organización](/v3/orgs/members/#list-organization-members) a través de la API y solicitar al administrador de la organización que elija qué miembros tendrán usuarios en plan de pago de lado del integrador. - -**Precios por unidad:** Un método para aprovisionar plazas por unidad es permitir a los usuarios que ocupen una plaza conforme inicien sesión en la app. Una vez que el cliente llegue al umbral de conteo de plazas, tu app puede notificarle que necesita mejorar el plan a través de {% data variables.product.prodname_marketplace %}. diff --git a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md b/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md deleted file mode 100644 index 380f2e5cbe..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Gestionar las cancelaciones de plan -intro: 'El cancelar una app de {% data variables.product.prodname_marketplace %} activa el webhook del [evento `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) con la acción `cancelada`, lo cual inicia el flujo de cancelación.' -redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/ - - /marketplace/integrating-with-the-github-marketplace-api/cancelling-plans - - /developers/github-marketplace/handling-plan-cancellations -versions: - fpt: '*' -topics: - - Marketplace ---- -Para obtener más información acerca de las cancelaciones de acuerdo a como se relaciona con la facturación, consulta la sección "[Cobrar a los usuarios en {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)". - -### Paso 1. Evento de cancelación - -Si un cliente decide cancelar una orden de {% data variables.product.prodname_marketplace %}, GitHub envía un webhook de [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) conla acción `cancelled` a tu app cuando tome efecto dicha cancelación. Si el cliente cancela durante un periodo de prueba gratuito, tu app recibirá el vento de inmediato. Cuando un cliente cancela un plan pagado, la cancelación tomará lugar al final del ciclo de facturación del cliente. - -### Paso 2. Desactivar las cuentas de usuario - -Cuando un cliente cancela un plan pagado o gratuito, tu app debe llevar a cabo estos pasos para completar la cancelación: - -1. Desactivar la cuenta del cliente que canceló su plan. -1. Revocar el token de OAuth que recibió tu app para el cliente. -1. Si tu app es una App de OAuth, eliminar todos los webhooks que creó tu app para los repositorios. -1. Eliminar todos los datos del cliente en los primeros 30 días de que se recibió el evento `cancelled`. - -{% note %} - -**Nota:** Te recomendamos utilizar la `effective_date` del webhook [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) para determinar cuándo ocurrirá un cambio de plan y así sincronizar a menudo el [Listar las cuentas para un plan](/v3/apps/marketplace/#list-accounts-for-a-plan). Para obtener más informació sobre los webhooks, consulta la sección "[eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)". - -{% endnote %} diff --git a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md deleted file mode 100644 index d78a96e93e..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Gestionar cambios de plan -intro: 'El mejorar y degradar una app de {% data variables.product.prodname_marketplace %} activa el webhook del [evento `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) con la acción `cambiada`, lo cual inicia el flujo de mejora o degradación.' -redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/ - - /marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans - - /developers/github-marketplace/handling-plan-changes -versions: - fpt: '*' -topics: - - Marketplace ---- -Para obtener más información acerca de mejorar y degradar los planes de acuerdo a como se relaciona con la facturación, consulta la sección "[Integrarse con la API de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/)". - -### Paso 1. Evento de cambio en el plan de precios - -GitHub envía el webhook `marketplace_purchase` con la acción `changed` a tu app cuando el cliente hace cualquiera de estos cambios a su orden de {% data variables.product.prodname_marketplace %}: -* Mejorar a un plan de precios más caro o degradarlo a uno más barato. -* Agregar o eliminar plazas a su plan existente. -* Cambiar el ciclo de facturación. - -GitHub enviará el webhook cuando el cambio entre en vigor. Por ejemplo, cuando un cliente degrada un plan, GitHub envía el webhook al final del ciclo de facturación del cliente. GitHub envía un webhook a tu app inmediatamente cuando un cliente mejora su plan para permitirle el acceso al servicio nuevo de inmediato. Si un cliente cambia de un ciclo mensual a uno anual, esto se considera como una mejora. Consulta la sección "[Cobrar a los clientes en {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" para aprender más acerca de las acciones que se consideran una mejora o una degradación. - -Lee `effective_date`, `marketplace_purchase`, y `previous_marketplace_purchase` del webhook de `marketplace_purchase` para actualizar la fecha de inicio del plan y hacer cambios al ciclo de facturació y plan de precios del cliente. Consulta la sección "[eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" para encontrar un ejemplo de la carga últil del evento `marketplace_purchase`. - -Si tu app ofrece periodos de prueba gratuitos, recibirás el webhook de `marketplace_purchase` con la acción `changed` cuando caduque este periodo de prueba. Si el periodo de prueba gratuito del cliente caduca, mejora al cliente a la versión pagada del plan de prueba gratuito. - -### Paso 2. Actualizar las cuentas de usuario - -Necesitarás actualizar la información de las cuentas de usuario para que se reflejen los cambios en el ciclo de facturación y en el plan de precios que el cliente hizo en su orden de {% data variables.product.prodname_marketplace %}. Muestra las mejoras al plan de precios, `seat_count` (para planes de precios por unidad), y ciclo de facturación en el sitio web de tu app de Marketplace en la IU de la misma cuando recibas el webhook de la acción `changed`. - -Cuando un cliente degrada un plan, se recomienda revisar si éste excedió los límites del mismo y contactarlos directamente en tu IU o por teléfono o correo electrónico. - -Para motivar a las personas a mejorar el plan, puedes mostrar una URL de mejora en la IU de tu app. Consulta la sección "[Acerca de las URL de mejora](#about-upgrade-urls)" para obtener más detalles. - -{% note %} - -**Nota:** Te recomendamos llevar a cabo una sincronización frecuente utilizando `GET /marketplace_listing/plans/:id/accounts` para asegurarte de que tu app tiene el plan, información de ciclo de facturación y conteo de unidades (para los precios por unidad) correctos para cada cuenta. - -{% endnote %} - -### Pagos de mejora fallidos - -{% data reusables.marketplace.marketplace-failed-purchase-event %} - -### Acerca de las URL de mejora - -Puedes redirigir a los usuarios desde la IU de tu app para que mejoren su plan en GitHub a través de una URL de mejora: - -``` -https://www.github.com/marketplace//upgrade// -``` - -Por ejemplo, si notas que el cliente tiene un plan de 5 personas y necesita cambiar a uno de 10, puedes mostrar un boton en la IU de tu app, el cual diga "Te mostramos como mejorar tu plan", o bien, mostrar un letrero con un enlace a la URL de mejora. La URL de mejora llevará al cliente a la página de confirmación de mejora para el plan de tu listado. - -Utiliza el `LISTING_PLAN_NUMBER` para el plan que el cliente quisiera comprar. Cuando creas planes de precios nuevos, estos reciben un `LISTING_PLAN_NUMBER`, lo cual es específico para cada plan en tu listado, y también reciben una `LISTING_PLAN_ID`, que es específica para cada plan en {% data variables.product.prodname_marketplace %}. Puedes encontrar estos números cuando [Listas los planes](/v3/apps/marketplace/#list-plans), los cuales identifican a los planes de precios en tus listados. Utiliza la `LISTING_PLAN_ID` y la terminal "[Listar cuentas para un plan](/v3/apps/marketplace/#list-accounts-for-a-plan)" para obtener la `CUSTOMER_ACCOUNT_ID`. - - -{% note %} - -**Nota:** Si un cliente mejora su cantidad adicional de unidades (como las plazas), aún puedes enviarlos al plan adecuado para su compra, pero no podemos dar soporte para los parámetros de `unit_count` en este momento. - -{% endnote %} diff --git a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md b/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md deleted file mode 100644 index 620bfc16b7..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Utilizar la API de GitHub Marketplace en tu app -intro: 'Aprende cómo integrar la API y eventos de webhook de {% data variables.product.prodname_marketplace %} en tu app para {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /apps/marketplace/setting-up-github-marketplace-webhooks/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/ - - /marketplace/integrating-with-the-github-marketplace-api -versions: - fpt: '*' -topics: - - Marketplace -children: - - /rest-endpoints-for-the-github-marketplace-api - - /webhook-events-for-the-github-marketplace-api - - /testing-your-app - - /handling-new-purchases-and-free-trials - - /handling-plan-changes - - /handling-plan-cancellations ---- - diff --git a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md b/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md deleted file mode 100644 index 26474550bd..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Terminales de REST para la API de GitHub Marketplace -intro: 'Para ayudarte a administrar tu app en {% data variables.product.prodname_marketplace %}, utiliza estas terminales de la API de {% data variables.product.prodname_marketplace %}.' -redirect_from: - - /apps/marketplace/github-marketplace-api-endpoints/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints/ - - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints - - /developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api -versions: - fpt: '*' -topics: - - Marketplace ---- -Aquí te mostramos algunas terminales útiles que están disponibles para los listados de Marketplace: - -* [Listar planes](/v3/apps/marketplace/#list-plans) -* [Listar cuentas para un plan](/v3/apps/marketplace/#list-accounts-for-a-plan) -* [Obtener un plan de suscripción para una cuenta](/v3/apps/marketplace/#get-a-subscription-plan-for-an-account) -* [Listar las suscripciones del usuario autenticado](/v3/apps/marketplace/#list-subscriptions-for-the-authenticated-user) - -Consulta estas páginas para encontrar más detalles sobre cómo autenticarte cuando utilices la API de {% data variables.product.prodname_marketplace %}: - -* [Opciones de autorización para las Apps de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/) -* [Opciones de autenticación para las GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/) - -{% note %} - -**Nota:** [Los límites de tasa para la API de REST](/v3/#rate-limiting) aplican para todas las terminales de la API de {% data variables.product.prodname_marketplace %}. - -{% endnote %} diff --git a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md b/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md deleted file mode 100644 index f20b8aefd6..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Probar tu app -intro: 'GitHub te recomienda probar tu app con las API y los webhooks antes de emitir tu listado a {% data variables.product.prodname_marketplace %} para que puedas proporcionar una experiencia ideal para los clientes. Antes de que el equipo de incorporación de {% data variables.product.prodname_marketplace %} apruebe tu app, esta debe gestionar adecuadamente los [flujos de facturación](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows).' -redirect_from: - - /apps/marketplace/testing-apps-apis-and-webhooks/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ - - /marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps - - /developers/github-marketplace/testing-your-app -versions: - fpt: '*' -topics: - - Marketplace ---- -### Probar las apps - -Puedes utilizar un [borrador de listado de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) para estimular a cada uno de los [flujos de facturación](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows). Un listado en estado de borrador significa que no se ha emitido para aprobación. Cualquier compra que hagas utilizando un borrador de listado de {% data variables.product.prodname_marketplace %} _no_ creará transacciones reales, y GitHub no hará cargos a tu tarjeta de crédito. - -#### Utilizar una app de desarrollo con un borrador de listado para probar los cambios - -Un listado de {% data variables.product.prodname_marketplace %} únicamente puede asociarse con un solo registro de app, y cada app puede acceder únicamente a su propio listado de {% data variables.product.prodname_marketplace %}. Es por esto que te recomendamos configurar una app de desarrollo por separado con la misma configuración que la productiva, y que crees un _borrador_ de listado de {% data variables.product.prodname_marketplace %} que puedas utilizar para las pruebas. El borrador del listado de {% data variables.product.prodname_marketplace %} te permite probar los cambios sin afectar a los usuarios activos de tu app productiva. Nunca tendrás que emitir tu listado de desarrollo de {% data variables.product.prodname_marketplace %}, ya que solo lo utilizarás para las pruebas. - -Ya que solo puedes crear un borrador de listado de {% data variables.product.prodname_marketplace %} para las apps públicas, debes poner tu app de desarrollo como pública. Las apps públicas no pueden descubrirse fuera de los listados publicados de {% data variables.product.prodname_marketplace %} mientras no compartas la URL de éstas. Solo el dueño de la aplicación podrá ver el lsitado de Marketplace en su estado de borrador. - -Una vez que cuentes con una app de desarrollo con un listado en estado de borrador, puedes utilizarla para probar los cambios que hagas a dicha app mientras que lo integras con la API y los webhooks de {% data variables.product.prodname_marketplace %}. - -{% warning %} - -No hagas compras de prueba con las apps que están activas en {% data variables.product.prodname_marketplace %}. - -{% endwarning %} - -#### Simular eventos de compra en Marketplace - -Tus escenarios de prueba podrían requerir que configures los planes de los listados que ofrecen periodos de prueba gratuitos y que cambies entre las suscripciones de pago y gratuitas. Ya que los decrementos y las cancelaciones no toman efecto sino hasta el siguiente ciclo de facturación, GitHub proporciona una característica exclusiva para desarrolladores para "Aplicar el Cambio Pendiente", la cual fuerza las acciones de `changed` y `cancelled` para que tomen efecto inmediatamente. Puedes acceder a la opción de **Aplicar Cambios Pendientes** para las apps con listados de Marketplace en estado de _borrador_ en https://github.com/settings/billing#pending-cycle: - -![Aplicar el cambio pendiente](/assets/images/github-apps/github-apps-apply-pending-changes.png) - -### Probar las API - -También proporcionamos terminales de prueba para muchas de las terminales de las API de {% data variables.product.prodname_marketplace %}, las cuales devuelven datos falsos de código predefinido que puedes utilizar para hacer pruebas. Para recibir datos de prueba, debes especificar las URL de prueba que incluyan `/stubbed` en la ruta (por ejemplo, `/user/marketplace_purchases/stubbed`). Para obtener una lista de terminales que son compatibles con este acercamiento de datos de prueba, consulta la sección de [terminales de {% data variables.product.prodname_marketplace %}](/v3/apps/marketplace/#github-marketplace). - -### Probar los webhooks - -GitHub proporciona herramientas para probar tus cárgas útiles desplegadas. Para obtener más información, consulta la sección "[Probar los webhooks](/webhooks/testing/)". diff --git a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md b/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md deleted file mode 100644 index 8b9031a12c..0000000000 --- a/translations/es-XL/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Eventos de webhook para la API de GitHub Marketplace -intro: 'Una app de {% data variables.product.prodname_marketplace %} recibe información acerca de los cambios en el plan de un usuario desde el webhook del evento de compra en Marketplace. Un evento de compra de marketplace se activa cuando un usuario compra, cancela o cambia su plan de pago. Para encontrar más detalles sobre cómo responder a cada uno de estos tipos de eventos, consulta la sección "[Flujos de facturación](/marketplace/integrating-with-the-github-marketplace-api/#billing-flows)."' -redirect_from: - - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ - - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events - - /developers/github-marketplace/webhook-events-for-the-github-marketplace-api -versions: - fpt: '*' -topics: - - Marketplace ---- -### Carga útil del webhook de compras en {% data variables.product.prodname_marketplace %} - -Las solicitudes de `POST` de los webhooks tienen encabezados especiales. Consulta la sección "[Encabezados de entrega de Webhooks](/webhooks/event-payloads/#delivery-headers)" para encontrar más detalles. GitHub no reenvía los intentos fallidos de entrega. Asegúrate de que tu app pueda recibir toda la carga útil del webhook que envíe GitHub. - -Las cancelaciones y disminuciones de categoría toman efecto el primer día del siguiente ciclo de facturación. Los eventos para las cancelaciones y disminuciones de categoría se envían cuando el nuevo plan entre en vigor al inicio del siguiente ciclo de facturación. Los eventos para las nuevas compras y mejoras de categoría comienzan inmediatamente. Utiliza `effective_date` en la carga útil del webhook para determinar cuándo comenzará un cambio. - -{% data reusables.marketplace.marketplace-malicious-behavior %} - -Cada carga útil de webhook de una `marketplace_purchase` tendrá la siguiente información: - - -| Clave | Tipo | Descripción | -| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada para generar el webhook. Puede ser `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, o `changed`. Para obtener más información, consulta los ejemplos de cargas útiles de webhook a continuación. **Nota:** las cargas útiles de `pending_change` y `pending_change_cancelled` contienen las mismas claves que se muestra en el [ejemplo de carga útil de `changed`](#example-webhook-payload-for-a-changed-event). | -| `effective_date` | `secuencia` | La fecha en la que la `action` se hace efectiva. | -| `sender` | `objeto` | La persona que tomó la `action` que activó el webhook. | -| `marketplace_purchase` | `objeto` | La información de compra de {% data variables.product.prodname_marketplace %}. | - -El objeto `marketplace_purchase` tiene las siguientes claves: - -| Clave | Tipo | Descripción | -| -------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `cuenta` | `objeto` | La cuenta de `organización` o `usuario` asociada con la suscripción. Las cuentas de organización incluirán `organization_billing_email`, que es la dirección de correo electrónico administrativa de la misma. Para encontrar direcciones de correo electrónico para cuentas personales, puedes utilizar la terminal [Obtener el usuario autenticado](/v3/users/#get-the-authenticated-user). | -| `billing_cycle` | `secuencia` | Puede ser `yearly` o `monthly`. Cuando el dueño de la `account` tiene un plan gratuito de GitHub y compra un plan gratuito de {% data variables.product.prodname_marketplace %}, el `billing_cycle` será `nil`. | -| `unit_count` | `número` | Cantidad de unidades compradas. | -| `on_free_trial` | `boolean` | Es `true` cuando la `account` está en un periodo de prueba gratuito. | -| `free_trial_ends_on` | `secuencia` | La fecha en la que caduca el periodo de prueba gratuito. | -| `next_billing_date` | `secuencia` | La fecha en la que comenzará el siguiente ciclo de facturación. Cuando el dueño de la `account` tiene un plan gratuito de GitHub.com y compra un plan gratuito de {% data variables.product.prodname_marketplace %}, el `next_billing_date` será `nil`. | -| `plan` | `objeto` | El plan que compra el `user` u `organization`. | - -El objeto `plan` tiene las siguientes claves: - -| Clave | Tipo | Descripción | -| ------------------------ | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `número` | El identificador único para este plan. | -| `name (nombre)` | `secuencia` | El nombre del plan. | -| `descripción` | `secuencia` | La descripción de este plan. | -| `monthly_price_in_cents` | `número` | El precio mensual de este plan en centavos (Divisa de los EEUU). Por ejemplo, un listado que cuesta 10 dólares de EEUU por mes sería de 1000 centavos. | -| `yearly_price_in_cents` | `número` | El precio anual para este plan en centavos (Divisa de los EEUU). Por ejemplo, un listado que cuesta 100 dólares de EEUU por mes sería de 10000 centavos. | -| `price_model` | `secuencia` | El modelo de precios para este listado. Puede ser alguno de entre `flat-rate`, `per-unit`, o `free`. | -| `has_free_trial` | `boolean` | es `true` cuando este listado ofrece un periodo de prueba gratuito. | -| `unit_name` | `secuencia` | El nombre de la unidad. Si el modelo de precios no es `per-unit`, éste será `nil`. | -| `bullet` | `conjunto de secuencias` | Los nombres de los puntos configurados en el plan de precios. | - -
    - -#### Ejemplo de la carga útil de un webhook para un evento de `purchased` -Este ejemplo proporciona la carga útil del evento `purchased`. - -{{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} - -#### Ejemplo de la carga útil de un webhook para un evento de `changed` - -Los cambios en un plan incluyen mejoras y degradaciones. Este ejemplo representa las cargas útiles de los eventos `changed`,`pending_change`, y `pending_change_cancelled`. La acción identifica cuál de estos tres eventos ha ocurrido. - -{{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }} - -#### Ejemplo de carga útil del webhook para un evento de `cancelled` - -{{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }} diff --git a/translations/es-XL/content/developers/index.md b/translations/es-XL/content/developers/index.md deleted file mode 100644 index 2a3f0ba389..0000000000 --- a/translations/es-XL/content/developers/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Desarrolladores -intro: 'Saca más provecho de {% data variables.product.prodname_dotcom %} integrándote con nuestras API, personalizando tu flujo de trabajo de {% data variables.product.prodname_dotcom %}, y creando y compartiendo apps con la comunidad.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /overview - - /webhooks-and-events - - /apps - - /github-marketplace ---- - diff --git a/translations/es-XL/content/developers/overview/about-githubs-apis.md b/translations/es-XL/content/developers/overview/about-githubs-apis.md deleted file mode 100644 index 7d2d22e46a..0000000000 --- a/translations/es-XL/content/developers/overview/about-githubs-apis.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Acerca de las API de GitHub -intro: 'Aprende sobre las API de {% data variables.product.prodname_dotcom %} para extender y personalizar tu experiencia en {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /v3/versions -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} - -Hay dos versiones estables de la API de GitHub: la [API de REST](/v3/) y la [API de GraphQL](/v4/). - -{% else %} - -La última versión estable de la API de GitHub es la [API de REST](/v3/). - -{% endif %} - -Cuando utilizas la API de REST, te exhortamos a que [solicites la v3 a través del encabezado de `Accept`](/v3/media/#request-specific-version). - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} - -Para obtener más información sobre cómo utilizar la API de GraphQL, consulta los [documentos de la v4](/v4/). - -{% endif %} - -## Versiones obsoletas - -### beta - -Se hizo obsoleta la API beta el 22 de abril de 2014. - -### v2 - -Eliminamos el soporte para la API v2 en el 12 de junio de 2012. - -### v1 - -Eliminamos el soporte para la API v1 en el 12 de junio de 2012. diff --git a/translations/es-XL/content/developers/overview/github-developer-program.md b/translations/es-XL/content/developers/overview/github-developer-program.md deleted file mode 100644 index 61426ff7be..0000000000 --- a/translations/es-XL/content/developers/overview/github-developer-program.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Programa de Desarrollador de GitHub -intro: 'Si creas herramientas que se integren con {% data variables.product.prodname_dotcom %}, puedes unirte al Programa de Desarrollador de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /program -versions: - fpt: '*' -topics: - - API ---- - -¿Estás creando una aplicación que se integra con GitHub? ¡Regístrate para nuestro Programa de Desarrollador! Las posibilidades son infinitas, y disfrutarás del reconocimiento de la comunidad. [Regístrate ahora](https://github.com/developer/register) - -## Permanece informado - -Sé el primero en saber acerca de los cambios a la API y prueba características nuevas antes de que se lanzen en el [Blod del desarrollador](https://developer.github.com/changes/). - -## Quítate la tentación - -Crea tus propias herramientas que se integren de manera continua con el lugar en donde cargas código todos los días. - -## Házte cargo de la empresa - -[Obten licencias de desarrollador](http://github.com/contact?form%5Bsubject%5D=Development+licenses) para crear y probar tu aplicación contra el {% data variables.product.prodname_ghe_server %}. - - -## ¿Tienes una integración que opera con GitHub? - -¡Genial! Nos gustaría que fueras parte del programa. Aquí te mostramos como puedes correr la voz:

    -* [Infórmanos sobre tu integración](https://github.com/contact?form[subject]=New+GitHub+Integration) -* Utiliza el [Logo de Octocat o de GitHub](https://github.com/logos) para denotar que tu producto se integra con GitHub -* Publica un video o un blog en tu sitio web que explique esta integración - -## ¿Estás listo para unirte al Programa de Desarrollador de GitHub? - -La membrecía está disponible para los desarrolladores individuales y para las comañías que tienen: - -* Una integración en producción o desarrollo que utilice la API de GitHub. -* Una dirección de correo electrónico en donde los usuarios de GitHub puedan contactarte para soporte. diff --git a/translations/es-XL/content/developers/overview/index.md b/translations/es-XL/content/developers/overview/index.md deleted file mode 100644 index df13b10ce3..0000000000 --- a/translations/es-XL/content/developers/overview/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Resumen -intro: 'Aprende sobre las API de {% data variables.product.prodname_dotcom %}, asegura tus despliegues, y únete al Programa de Desarrollador de {% data variables.product.prodname_dotcom %}.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /about-githubs-apis - - /managing-deploy-keys - - /viewing-deployment-history - - /using-ssh-agent-forwarding - - /secret-scanning-partner-program - - /replacing-github-services - - /github-developer-program ---- -### Índice diff --git a/translations/es-XL/content/developers/overview/managing-deploy-keys.md b/translations/es-XL/content/developers/overview/managing-deploy-keys.md deleted file mode 100644 index e006492f38..0000000000 --- a/translations/es-XL/content/developers/overview/managing-deploy-keys.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Administrar las llaves de despliegue -intro: Aprende las diversas formas de administrar llaves SSH en tus servidores cuando automatizas los scripts de desplegue y averigua qué es lo mejor para ti. -redirect_from: - - /guides/managing-deploy-keys/ - - /v3/guides/managing-deploy-keys -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -Puedes administrar llaves SSH en tus servidores cuando automatices tus scripts de despliegue utilizando el reenvío del agente de SSH, HTTPS con tokens de OAuth, o usuarios máquina. - -### Reenvío del agente SSH - -En muchos casos, especialmente al inicio de un proyecto, el reenvío del agente SSH es el método más fácil y rápido a utilizar. El reenvío de agentes utiliza las mismas llaves SSH que utiliza tu ordenador de desarrollo local. - -##### Pros - -* No tienes que generar o llevar registros de las llaves nuevas. -* No hay administración de llaves; los usuarios tienen los mismos permisos en el servidor y localmente. -* No se almacenan las llaves en el servidor, así que, en caso de que el servidor se ponga en riesgo, no necesitas buscar y eliminar las llaves con este problema. - -##### Contras - -* Los usuarios **deben** ingresar cno SSH para hacer los despliegues; no pueden utilizarse los procesos de despliegue automatizados. -* El reenvío del agente SSH puede ser difícil de ejecutar para usuarios de Windows. - -##### Configuración - -1. Habilita el reenvío de agente localmente. Consulta [nuestra guía sobre el redireccionamiento del agente SSH][ssh-agent-forwarding] para obtener más información. -2. Configura tus scripts de despliegue para utilizar el reenvío de agente. Por ejemplo, el habilitar el reenvío de agentes en un script de bash se vería más o menos así: `ssh -A serverA 'bash -s' < deploy.sh` - -### Clonado de HTTPS con tokens de OAuth - -Si no quieres utilizar llaves SSH, puedes utilizar [HTTPS con tokens de OAuth][git-automation]. - -##### Pros - -* Cualquiera que tenga acceso al servidor puede desplegar el repositorio. -* Los usuarios no tienen que cambiar su configuración local de SSH. -* No se necesitan tokens múltiples (uno por usuario); un token por servidor es suficiente. -* Los tokens se pueden revocar en cualquier momento, convirtiéndolos esencialmente en una contraseña de un solo uso. -* Se puede generar nuevos tokens con scripts si se utiliza [la API de OAuth](/rest/reference/oauth-authorizations#create-a-new-authorization). - -##### Contras - -* Debes asegurarte de que configuras tu token con los alcances de acceso correctos. -* Los tokens son prácticamente contraseñas, y deben protegerse de la misma manera. - -##### Configuración - -Consulta [nuestra guía sobre la automatización de tokens en Git][git-automation]. - -### Llaves de implementación - -{% data reusables.repositories.deploy-keys %} - -{% data reusables.repositories.deploy-keys-write-access %} - -##### Pros - -* Cualquiera que tenga acceso al repositorio y al servidor tiene la capacidad de desplegar el proyecto. -* Los usuarios no tienen que cambiar su configuración local de SSH. -* Las llaves de despliegue son de solo lectura predeterminadamente, pero les puedes otorgar acceso de escritura cuando las agregas a un repositorio. - -##### Contras - -* Las llaves de despliegue solo otorgan acceso a un solo repositorio. Los proyectos más complejos pueden tener muchos repositorios que extraer del mismo servidor. -* Las llaves de lanzamiento habitualmente no están protegidas con una frase de acceso, lo cual hace que se pueda acceder fácilmente a ellas si el servidor estuvo en riesgo. - -##### Configuración - -1. [Ejecuta el procedimiento de `ssh-keygen`][generating-ssh-keys] en tu servidor, y recuerda en donde guardaste el par de llaves pública/privada de rsa. -2. En la esquina superior derecha de cualquier página de {% data variables.product.product_name %}, da clic en tu foto de perfil y luego da clic en **Tu perfil**. ![Navegación al perfil](/assets/images/profile-page.png) -3. En tu página de perfil, da clic en **Repositorios** y luego en el nombre de tu repositorio. ![Enlace de los repositorios](/assets/images/repos.png) -4. Desde tu repositorio, da clic en **Configuración**. ![Configuración del repositorio](/assets/images/repo-settings.png) -5. En la barra lateral, da clic en **Desplegar llaves** y luego en **Agregar llave de despliegue**. ![Enlace para agregar llaves de despliegue](/assets/images/add-deploy-key.png) -6. Proporciona un título, pégalo en tu llave pública. ![Página de la llave de despliegue](/assets/images/deploy-key.png) -7. Selecciona **Permitir acceso de escritura** si quieres que esta llave tenga acceso de escritura en el repositorio. Una llave de despliegue con acceso de escritura permite que un despliegue cargue información al repositorio. -8. Da clic en **Agregar llave**. - -### Usuarios máquina - -Si tu servidor necesita acceder a repositorios múltiples, puedes crear una nueva cuenta de {% data variables.product.product_name %} y adjuntar una llave SSH que se utilizará exclusivamente para fines de automatización. Ya que ninguna persona utilizará esta cuenta de {% data variables.product.product_name %}, se le llama _usuario máquina_. Puedes agregar el usuario máquina como [colaborador][collaborator] en un repositorio personal (otorgándole acceso de lectura y escritura), como un [colaborador externo][outside-collaborator] en el repositorio de una organización (otorgándole acceso de lectura, escritura y administrador), o a un [equipo][team] con acceso a los repositorios que necesite para la automatización (otorgándole los permisos del equipo). - -{% if currentVersion == "free-pro-team@latest" %} - -{% tip %} - -**Tip:** En nuestras [condiciones de servicio][tos] se declara que: - -> *No se permiten las cuentas que registren ni los "bots", ni otros métodos automatizados.* - -Esto significa que no puedes automatizar la creación de las cuentas. Pero si quieres crear un solo usuario máquina para automatizar las tareas como el despliegue de scripts en tu proyecto u organización, eso está perfecto. - -{% endtip %} - -{% endif %} - -##### Pros - -* Cualquiera que tenga acceso al repositorio y al servidor tiene la capacidad de desplegar el proyecto. -* No se necesitan usuarios (humanos) para cambiar su configuración local de SSH. -* No se necesitan llaves múltiples; una por servidor está bien. - -##### Contras - -* Únicamente las organizaciones pueden restringir a los usuarios máquina para que tengan acceso de solo lectura. Los repositorios personales siempre otorgan a los colaboradores acceso de lectura/escritura. -* Las llaves de los usuarios máquina, tal como las llaves de despliegue, a menudo no se encuentran protegidas con una frase de acceso. - -##### Configuración - -1. [Ejecuta el procedimiento de `ssh-keygen`][generating-ssh-keys] en tu servidor y adjunta la llave pública a la cuenta del usuario máquina. -2. Otorga a la cuenta del usuario máquina el acceso a los repositorios que quieras automatizar. Puedes hacer esto si agregas la cuenta como un [colaborador][collaborator], como un [colaborador externo][outside-collaborator], o a un [equipo][team] en una organización. - -[ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/ -[generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key -[tos]: /articles/github-terms-of-service/ -[git-automation]: /articles/git-automation-with-oauth-tokens -[git-automation]: /articles/git-automation-with-oauth-tokens -[collaborator]: /articles/inviting-collaborators-to-a-personal-repository -[outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization -[team]: /articles/adding-organization-members-to-a-team diff --git a/translations/es-XL/content/developers/overview/replacing-github-services.md b/translations/es-XL/content/developers/overview/replacing-github-services.md deleted file mode 100644 index bb118b073c..0000000000 --- a/translations/es-XL/content/developers/overview/replacing-github-services.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Reemplazar los GitHub Services -intro: 'Si aún estás dependiendo de los {% data variables.product.prodname_dotcom %} Services obsoletizados, aprende cómomigrar los ganchos de tu servicio a webhooks.' -redirect_from: - - /guides/replacing-github-services/ - - /v3/guides/automating-deployments-to-integrators/ - - /v3/guides/replacing-github-services -versions: - fpt: '*' - ghes: '*' -topics: - - API ---- - - -Hemos obsoletizado los GitHub Services para favorecer la integración con los webhooks. Esta guía te ayuda a hacer la transición hacia los webhooks de GitHub Services. Para obtener más información acerca de este anuncio, consulta la [Publicación del blog](https://developer.github.com/changes/2018-10-01-denying-new-github-services). - -{% note %} - -Como una alternativa al servicio de correo electrónico, ahora puedes comenzar a utilizar las notificaciones para las cargas de información a tu repositorio. Consulta la sección "[Acerca de las notificaciones de correo electrónico para las cargas a tu repositorio](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" para aprender cómo configurar las notificaciones por correo electrónico de las confirmaciones. - -{% endnote %} - - -### Línea del tiempo de la obsoletización - -- **1 de octubre de 2018**: GitHub descontinuó el permitir que los usuarios instalen servicios. Eliminamos los GitHub Services de la interface de usuario de GitHub.com. -- **29 de enero de 2019**: Como alternativa al servicio de correo electrónico, ahora puedes comenzar a utilizar las notificaciones por correo electrónico para las cargas a tu repositorio. Consulta la sección "[Acerca de las notificaciones de correo electrónico para las cargas a tu repositorio](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" para aprender cómo configurar las notificaciones por correo electrónico de las confirmaciones. -- **31 de enero de 2019**: GitHub dejará de entregar los eventos de los servicios instalados en GitHub.com. - -### Antecedentes de GitHub Services - -GitHub Services (a veces conocido como Ganchos de Servicio) es el método tradicional de integración en donde GitHub hospedó una porción de los servicios de nuestros integradores a través [del repositorio`github-services`](https://github.com/github/github-services). Las acciones que se realizan en GitHub activan estos servicios, y puedes utilizarlos a su vez para activar acciones fuera de GitHub. - -{% if currentVersion != "free-pro-team@latest" %} -### Encontrar los repositorios que utilizan GitHub Services -Proporcionamos un script de línea de comandos que te ayuda a identificar los repositorios de tu aplicativo que utilizan GitHub Services. Para obtener más información, consulta [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %} - -### GitHub Services vs webhooks - -Las diferencias clave entre GitHub Services y los webhooks son: -- **Configuración**: Los GitHub Services tienen opciones de configuración específicas para los servicioes, mientras que los webhooks se configuran simplemente especificando una URL y un conjunto de eventos. -- **Lógica personalizada**: Los GitHub Services pueden tener una lógica personalizada para responder con acciones múltiples como parte de procesar solo un evento, mientras que los webhooks no tienen lógica personalizada. -- **Tipos de solicitudes**: Los GitHub Services pueden hacer solicitudes tanto de HTTP como no-HTTP, mientras que los webhooks solo hacen solicitudes HTTP. - -### Reemplazar los Servicios con webhooks - -Para reemplazar los GitHub Services con Webhooks: - -1. Identifica los eventos de webhook relevantes a los que necesitas suscribirte desde [esta lista](/webhooks/#events). - -2. Cambia tu configuración dependiendo de cómo utilizas los GitHub Services actualmente: - - - Para las **GitHub Apps**: Actualiza los permisos y eventos suscritos de tu app para configurarla para recibir los eventos de webhook reelevantes. - - Para las **Apps de OAuth**: Solicita ya sea el(los) alcance(s) `repo_hook` y/o `org_hook` para administrar los eventos relevantes a nombre de los usuarios. - - Para los **proveedores de GitHub Services**: solicita que los usuarios configuren manualmente un webhook con los eventos relevantes que se te envían, o aprovecha esta oportunidad para crear una app para administrar esta funcionalidad. Para obtener más información, consulta "[Acerca de las apps](/apps/about-apps/)." - -3. Migra las configuraciones adicionales desde fuera de GitHub. Algunos GitHub Services necesitan configuraciones personalizadas adicionales en la página de configuración dentro de GitHub. Si tu servicio hace esto, necesitarás migrar esta funcionalidad en tu aplicación o depender de GitHub o de las Apps de OAuth conforme esto aplique. - -### Compatibilidad con {% data variables.product.prodname_ghe_server %} - -- **{% data variables.product.prodname_ghe_server %} 2.17**: El {% data variables.product.prodname_ghe_server %} con lanzamiento 2.17 y superior descontinuará el permitir que los administradores instalen servicios. Los aministradores podrán seguir modificando los ganchos de servicio existentes y recibiendo ganchos en el {% data variables.product.prodname_ghe_server %} con lanzamiento 2.17 hasta el 2.19. Como una alternativa al servicio de correo electrónico, podrás utilizar las notificaciones de correo electrónico para las cargas de información a tu repositorio en el {% data variables.product.prodname_ghe_server %} 2.17 y superior. Consulta [esta publicación del blog](https://developer.github.com/changes/2019-01-29-life-after-github-services) para conocer más al respecto. -- **{% data variables.product.prodname_ghe_server %} 2.20**: El {% data variables.product.prodname_ghe_server %} con lanzamiento 2.20 y superior dejará de entregar cualquier evento de los servicios instalados. - -El lanzamiento 2.17 de {% data variables.product.prodname_ghe_server %} será el primer lanzamiento que no permite a los administradores instalar GitHub Services. Únicamente admitiremos los GitHub Services existentes hasta el lanzamiento 2.20 de {% data variables.product.prodname_ghe_server %}. También aceptaremos cualquier parche crítico para tu Github Service que se ejecute en el {% data variables.product.prodname_ghe_server %} hasta el 1 de octubre de 2019. - -### Migrarte con nuestra ayuda - -Por favor [contáctanos](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) si tienes cualquier pregunta. - -Como un resumen de alto nivel, el proceso de migración involucra habitualmente: - - Identificar cómo y dónde tu producto está utilizando los GitHub Services. - - Identificar los eventos de webhook correspondientes que necesites configurar para poder migrarlos a webhooks sencillos. - - Implementar el diseño utilizando ya sea [{% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/) o [{% data variables.product.prodname_github_app %}. Se prefieren las {% data variables.product.prodname_github_app %}](/apps/building-github-apps/). Para aprender más acerca del porqué se prefieren las {% data variables.product.prodname_github_app %}, consulta la sección "[Razones para cambiar a {% data variables.product.prodname_github_app %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)". diff --git a/translations/es-XL/content/developers/overview/secret-scanning.md b/translations/es-XL/content/developers/overview/secret-scanning.md deleted file mode 100644 index 78ad1600de..0000000000 --- a/translations/es-XL/content/developers/overview/secret-scanning.md +++ /dev/null @@ -1,283 +0,0 @@ ---- -title: Escaneo de secretos -intro: 'Como proveedor de servicios, puedes asociarte con {% data variables.product.prodname_dotcom %} para que se aseguren nuestros formatos de token secretos a través de un escaneo de secretos, el cual busca las confirmaciones accidentales de tus formatos secretos y puede enviarse a la terminal de verificación de un proveedor de servicios.' -redirect_from: - - /partnerships/token-scanning/ - - /partnerships/secret-scanning -versions: - free-pro-team: '*' -miniTocMaxHeadingLevel: 4 -topics: - - API ---- - - -{% data variables.product.prodname_dotcom %} escanea los repositorios en busca de formatos secretos para prevenir el uso fraudulento de las credenciales que se confirmaron por accidente. El escaneo de secretos ocurre predeterminadamente en los repositorios públicos, y se puede habilitar en los privados por parte de los administradores de dicho repositorio o de los propietarios de la organización. Como proveedor de servicios, puedes asociarte con {% data variables.product.prodname_dotcom %} para que tus formatos secretos se incluyan en nuestro escaneo de secretos. - -Cuando se encuentra una coincidencia de tu formato secreto en un repositorio público, se envía una carga útil a una terminal HTTP de tu elección. - -Cuando se encuentra una coincidencia de tu formato secreto en un repositorio privado configurado para el escaneo de secretos, entonces se les alerta a los administradores del repositorio y estos pueden ver y administrar los resultados del escaneo de secretos en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Administrar alertas del escaneo de secretos](/github/administering-a-repository/managing-alerts-from-secret-scanning)". - -{% note %} - -**Nota:** El escaneo de secretos para repositorios privados se encuentra actualmente en beta. - -{% endnote %} - -Este artículo describe cómo puedes asociarte con {% data variables.product.prodname_dotcom %} como un proveedor de servicios y unirte al programa de escaneo de secretos. - -### El proceso de escaneo de secretos - -##### Cómo funciona el escaneo de secretos en un repositorio público - -El siguiente diagrama resume el proceso de escaneo de secretos para los repositorios públicos y cualquier coincidencia se envía a una terminal de verificación de un proveedor de servicios. - -![Diagrama de flujo que muestra el proceso de escaneo para un secreto y el envío de coincidencias a una terminal de verificación del proveedor de servicios](/assets/images/secret-scanning-flow.png "Flujo de escaneo de secretos") - -### Unirse al programa de escaneo de secretos en {% data variables.product.prodname_dotcom %} - -1. Contacta a {% data variables.product.prodname_dotcom %} para iniciar el proceso. -1. Identifica los secretos relevantes que quieres escanear y crea expresiones regulares para capturarlos. -1. Para las coincidencias de secretos que estén en repositorios públicos, crea un servicio de alerta de secretos que acepte webhooks de {% data variables.product.prodname_dotcom %} que contengan la carga útil del mensaje del escaneo de secretos. -1. Implementa la verificación de firmas en tu servicio de alerta secreto. -1. Implementa la revocación de secretos y las notificaciones al usuario en tu servicio de alerta de secretos. - -#### Contacta a {% data variables.product.prodname_dotcom %} para iniciar el proceso - -Para iniciar con el proceso de inscripción, manda un mensaje de correo electrónico a secret-scanning@github.com. - -Recibirás los detalles del programa de escane de secretos, y necesitarás aceptar las condiciones de participación de {% data variables.product.prodname_dotcom %} antes de seguir con el proceso. - -#### Identifica tus secretos y crea expresiones regulares - -Para escanear en busca de tus secretos, {% data variables.product.prodname_dotcom %} necesita saber los siguientes detalles de cada secreto que quieras incluir en el programa de escaneo de secretos: - -* Un nombre único y legible para las personas para el tipo de secreto. Lo utilizaremos para generar el valor `Type` en la carga útil del mensaje más adelante. -* Una expresión regular que encuentre el tipo de secreto. Sé tan preciso como sea posible, ya que esto reducirá la cantidad de falsos positivos. -* La URL de la terminal que recibe mensajes de {% data variables.product.prodname_dotcom %}. Esto no tiene que ser único para cada tipo de secreto. - -Envía esta información a secret-scanning@github.com. - -#### Crea un servicio de alerta de secretos - -Crea una terminal HTTP pública y accesible desde la internet en la URL que nos proporcionaste. Cuando se encuentre una coincidencia de tu expresión regular en un repositorio público, {% data variables.product.prodname_dotcom %} enviará un mensaje HTTP de tipo `POST` a tu terminal. - -##### Ejemplo del POST que se envía a tu terminal - -``` -POST / HTTP/1.1 -Host: HOST -Accept: */* -Content-Type: application/json -GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a -GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICop4nvIgmcY4+mBG6Ek= -Content-Length: 0123 - -[ - { - "token": "X-Header-Bearer: as09dalkjasdlfkjasdf09a", - "type": "ACompany_API_token", - "url": "https://github.com/octocat/Hello-World/commit/123456718ee16e59dabbacb1b4049abc11abc123" - } -] -``` - -El cuerpo del mensaje es una matriz de JSON que contiene uno o más objetos con el siguiente contenido. Cuando se encuentran coincidencias múltiples, {% data variables.product.prodname_dotcom %} podría enviar un solo mensaje con más de una coincidencia del secreto. - -* **Token**: El valor de la coincidencia del secreto. -* **Tipo**: El nombre único que proporcionaste para identificar tu expresión regular. -* **URL**: La URL de la confirmación pública en donde se encontró la coincidencia. - -#### Implementa la verificación de firmas en tu servicio de alerta de secretos - -Te recomendamos que implementes la validación de firmas en tu servicio de alerta de secretos para garantizar que los mensajes que recibes son auténticamente de {% data variables.product.prodname_dotcom %} y no son malintencionados. - -Puedes recuperar la llave pública del escaneo de secretos de {% data variables.product.prodname_dotcom %} desde https://api.github.com/meta/public_keys/secret_scanning y validar el mensaje utilizando el algoritmo `ECDSA-NIST-P256V1-SHA256`. - -Asumiendo que recibes el siguiente mensaje, los extractos de código que presentamos a continuación demuestran cómo pudiste realizar la validación de firmas. El código también asume que configuraste una variable de ambiente llamada `GITHUB_PRODUCTION_TOKEN` con un PAT generado (https://github.com/settings/tokens). El token no necesita que se configure ningún permiso. - -**Mensaje de ejemplo que se envía a tu terminal de verificación** -``` -POST / HTTP/1.1 -Host: HOST -Accept: */* -content-type: application/json -GITHUB-PUBLIC-KEY-IDENTIFIER: 90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a -GITHUB-PUBLIC-KEY-SIGNATURE: MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc= -Content-Length: 0000 - -[{"token": "some_token", "type": "some_type", "url": "some_url"}] -``` - -**Ejemplo de validación en Go** -```golang -package main - -import ( - "crypto/ecdsa" - "crypto/sha256" - "crypto/x509" - "encoding/asn1" - "encoding/base64" - "encoding/json" - "encoding/pem" - "errors" - "fmt" - "math/big" - "net/http" - "os" -) - -func main() { - payload := `[{"token": "some_token", "type": "some_type", "url": "some_url"}]` - - kID := "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a" - - kSig := "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=" - - // Fetch the list of GitHub Public Keys - req, err := http. NewRequest("GET", "https://api.github.com/meta/public_keys/token_scanning", nil) - if err != nil { - fmt. Printf("Error preparing request: %s\n", err) - os. Exit(1) - } - - if len(os.Getenv("GITHUB_PRODUCTION_TOKEN")) == 0 { - fmt. Println("Need to define environment variable GITHUB_PRODUCTION_TOKEN") - os. Exit(1) - } - - req. Header.Add("Authorization", "Bearer "+os.Getenv("GITHUB_PRODUCTION_TOKEN")) - - resp, err := http. DefaultClient.Do(req) - if err != nil { - fmt. Printf("Error requesting GitHub signing keys: %s\n", err) - os. Exit(2) - } - - decoder := json. NewDecoder(resp.Body) - var keys GitHubSigningKeys - if err := decoder. Decode(&keys); err != nil { - fmt. Printf("Error decoding GitHub signing key request: %s\n", err) - os. Exit(3) - } - - // Find the Key used to sign our webhook - pubKey, err := func() (string, error) { - for _, v := range keys. PublicKeys { - if v. KeyIdentifier == kID { - return v. Key, nil - - } - } - return "", errors. New("specified key was not found in GitHub key list") - }() - - if err != nil { - fmt. Printf("Error finding GitHub signing key: %s\n", err) - os. Exit(4) - } - - // Decode the Public Key - block, _ := pem.Decode([]byte(pubKey)) - if block == nil { - fmt. Println("Error parsing PEM block with GitHub public key") - os. Exit(5) - } - - // Create our ECDSA Public Key - key, err := x509.ParsePKIXPublicKey(block.Bytes) - if err != nil { - fmt. Printf("Error parsing DER encoded public key: %s\n", err) - os. Exit(6) - } - - // Because of documentation, we know it's a *ecdsa.PublicKey - ecdsaKey, ok := key.(*ecdsa.PublicKey) - if !ok { - fmt. - Exit(7) - } - - // Parse the Webhook Signature - parsedSig := asn1Signature{} - asnSig, err := base64.StdEncoding.DecodeString(kSig) - if err != nil { - fmt. Printf("unable to base64 decode signature: %s\n", err) - os. Exit(8) - } - rest, err := asn1.Unmarshal(asnSig, &parsedSig) - if err != nil || len(rest) != 0 { - fmt. Printf("Error unmarshalling asn.1 signature: %s\n", err) - os. Exit(9) - } - - // Verify the SHA256 encoded payload against the signature with GitHub's Key - digest := sha256.Sum256([]byte(payload)) - keyOk := ecdsa. Verify(ecdsaKey, digest[:], parsedSig.R, parsedSig.S) - - if keyOk { - fmt. - Println("the payload is invalid :(") - os. Exit(10) - } -} - -type GitHubSigningKeys struct { - PublicKeys []struct { - KeyIdentifier string `json:"key_identifier"` - Key string `json:"key"` - IsCurrent bool `json:"is_current"` - } `json:"public_keys"` -} - -// asn1Signature is a struct for ASN.1 serializing/parsing signatures. -type asn1Signature struct { - R *big.Int - S *big.Int -} -``` - -**Ejemplo de validación en Ruby** -```ruby -require 'openssl' -require 'net/http' -require 'uri' -require 'json' -require 'base64' - -payload = <<-EOL -[{"token": "some_token", "type": "some_type", "url": "some_url"}] -EOL - -payload = payload - -signature = "MEUCICxTWEpKo7BorLKutFZDS6ie+YFg6ecU7kEA6rUUSJqsAiEA9bK0Iy6vk2QpZOOg2IpBhZ3JRVdwXx1zmgmNAR7Izpc=" - -key_id = "90a421169f0a406205f1563a953312f0be898d3c7b6c06b681aa86a874555f4a" - -url = URI.parse('https://api.github.com/meta/public_keys/token_scanning') - -raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN'] -request = Net::HTTP::Get.new(url.path) -request['Authorization'] = "Bearer #{ENV['GITHUB_PRODUCTION_TOKEN']}" - -http = Net::HTTP.new(url.host, url.port) -http.use_ssl = (url.scheme == "https") - -response = http.request(request) - -parsed_response = JSON.parse(response.body) - -current_key_object = parsed_response["public_keys"].find { |key| key["key_identifier"] == key_id } - -current_key = current_key_object["key"] - -openssl_key = OpenSSL::PKey::EC.new(current_key) - -puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), payload.chomp) -``` - -#### Implementa la revocación de secretos y la notificación a usuarios en tu servicio de alerta de secretos - -Para escanear secretos en los repositorios públicos, puedes ampliar tu servicio de alerta de secretos para revocar los secretos expuestos y notificar a los usuarios afectados. Depende de ti el cómo implementas esto en tu servicio de alerta de secretos, pero te recomendamos considerar cualquier secreto del cual {% data variables.product.prodname_dotcom %} te envíe mensajes de que es público y está puesto en riesgo. diff --git a/translations/es-XL/content/developers/overview/using-ssh-agent-forwarding.md b/translations/es-XL/content/developers/overview/using-ssh-agent-forwarding.md deleted file mode 100644 index eae9c97894..0000000000 --- a/translations/es-XL/content/developers/overview/using-ssh-agent-forwarding.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -title: Utilizar el reenvío del agente SSH -intro: 'Para simplificar los despliegues en un servidor, puedes configurar el reenvío del agente SSH para utilizar las llaves SSH locales de forma segura.' -redirect_from: - - /guides/using-ssh-agent-forwarding/ - - /v3/guides/using-ssh-agent-forwarding -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -El reenvío del agente de SSH puede utilizarse para hacer despliegues a un servidor simple. Te permite utilizar llaves SSH locales en vez de dejar las llaves (¡sin frases de acceso!) en tu servidor. - -Si ya configuraste una llave SSH para que interactúe con {% data variables.product.product_name %}, probablemente estás familiarizado con el `ssh-agent`. Es un programa que se ejecuta en segundo plano y que mantiene tu llave cargada en la memoria para que no tengas que ingresar tu frase deacceso cada que quieres utilizar esta llave. Lo ingenioso de esto es que puedes elegir dejar que los servidores accedan a tu `ssh-agent` local como si ya se estuvieran ejecutando en el servidor. Esto es como pedirle a un amigo que ingrese su contraseña para que puedas utilizar su computadora. - -Revisa la sección [Guía de Tips Técnicos de Steve Friedl][tech-tips] para obtener una explicación más exacta del reenvío del agente SSH. - -### Configurar el reenvío del agente SSH - -Asegúrate de que tu propia llave SSH está configurada y funciona. Puedes utilizar [nuestra guía para generar llaves SSH][generating-keys] si aún no lo has hecho. - -Puedes probar que tu llave local funciona si ingresas `ssh -T git@github.com` en la terminal: - -```shell -$ ssh -T git@github.com -# Attempt to SSH in to github -> Hi username! You've successfully authenticated, but GitHub does not provide -> shell access. -``` - -Estamos empezando muy bien. Vamso a configurar SSH para permitir el reenvío del agente en tu servidor. - -1. Utilizando tu editor de texto preferido, abre el archivo en `~/.ssh/config`. Si este archivo no existe, puedes crearlo si ingresas `touch ~/.ssh/config` en la terminal. - -2. Ingresa el siguiente texto en el archivo, reemplazando `example.com` con el nombre de dominio o la IP de tu servidor: - - Host example.com - ForwardAgent yes - -{% warning %} - -**Advertencia:** Podrías estar tentado a utilizar un comodín como `Host *` para aplicar esta configuración únicamente a todas las conexiones SSH. No es realmente una buena idea, ya que compartirías tus llaves SSH locales con *todos* los servidores en los que ingreses con SSH. No tendrán acceso directo a las llaves, pero podrán utilizarlas *como si fueran tú* mientras que se establece la conexión. **Deberías agregar únicamente los servidores en los que confías y que pretendes usar con el reenvío del agente.** - -{% endwarning %} - -### Probar el reenvío del agente SSH - -Para probar que el reenvío del agente funciona en tu servidor, puedes ingresar con SSH en tu servidor y ejecutar `ssh -T git@github.com` una vez más. Si todo sale bien, te regresará el mismo mensaje que salió cuando lo hiciste localmente. - -Si no estás seguro de que se esté utilizando tu llave local, también puedes inspeccionar la variable `SSH_AUTH_SOCK` en tu servidor: - -```shell -$ echo "$SSH_AUTH_SOCK" -# Print out the SSH_AUTH_SOCK variable -> /tmp/ssh-4hNGMk8AZX/agent.79453 -``` - -Si no se ha configurado la variable, esto significa que el reenvío del agente no funciona: - -```shell -$ echo "$SSH_AUTH_SOCK" -# Print out the SSH_AUTH_SOCK variable -> [No output] -$ ssh -T git@github.com -# Try to SSH to github -> Permission denied (publickey). -``` - -### Solucionar problemas del reenvío del agente SSH - -Aquí te mostramos algunos puntos en los cuales tener cuidado cuando intentes solucionar problemas relacionados con el reenvío del agente SSH. - -#### Debes utilizar una URL con SSH para revisar el código - -El reenvío SSH funciona únicamente con URL con SSH, no con aquellas de HTTP(s). Revisa el archivo *.git/config* en tu servidor y asegúrate de que la URL es de estilo SSH como se muestra a continuación: - -```shell -[remote "origin"] - url = git@github.com:yourAccount/yourProject.git - fetch = +refs/heads/*:refs/remotes/origin/* -``` - -#### Tus llaves SSH deben funcionar localmente - -Antes de que hagas que tus llaves funcionen a través del reenvío del agente, primero deben funcionar localmente. [Nuestra guía para generar llaves SSH][generating-keys] puede ayudarte a configurar tus llaves SSH localmente. - -#### Tu sistema debe permitir el reenvío del agente SSH - -Algunas veces, la configuración del sistema deja de permitir el reenvío del agente SSH. Puedes verificar si se está utilizando un archivo de configuración del sistema ingresando el siguiente comando en la terminal: - -```shell -$ ssh -v example.com -# Connect to example.com with verbose debug output -> OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011 -> debug1: Reading configuration data /Users/you/.ssh/config -> debug1: Applying options for example.com -> debug1: Reading configuration data /etc/ssh_config -> debug1: Applying options for * -$ exit -# Returns to your local command prompt -``` - -En este ejemplo, el archivo *~/.ssh/config* se carga primero, luego se lee el */etc/ssh_config*. Podemos inspeccionar ese archivo para ver si está anulando nuestras opciones si ejecutamos los siguientes comandos: - -```shell -$ cat /etc/ssh_config -# Print out the /etc/ssh_config file -> Host * -> SendEnv LANG LC_* -> ForwardAgent no -``` - -En este ejemplo, nuestro archivo */etc/ssh_config* dice específicamente `ForwardAgent no`, lo cual es una manera de bloquear el reenvío del agente. Si borramos esta línea del archivo deberíamos poder hacer funcionar el reenvío del agente nuevamente. - -#### Tu servidor debe permitir el reenvío del agente SSH en las conexiones entrantes - -El reenvío del agente también puede bloquearse en tu servidor. Puedes verificar que se permita este reenvío si entras al servidor mediante SSH y ejecutas `sshd_config`. La salida de este comando deberá indicar que se configuró `AllowAgentForwarding`. - -#### Tu `ssh-agent` local debe estar ejecutándose - -En la mayoría de las computadoras, el sistema operativo lanza el `ssh-agent` automáticamente. Sin embargo, en Windows, tienes que hacerlo manualmente. Tenemos [una guía de cómo empezar con el `ssh-agent` cuando abres Git Bash][autolaunch-ssh-agent]. - -Para verificar que el `ssh-agent` se está ejecutando en tu computadora, teclea el siguiente comando en la terminal: - -```shell -$ echo "$SSH_AUTH_SOCK" -# Print out the SSH_AUTH_SOCK variable -> /tmp/launch-kNSlgU/Listeners -``` - -#### Tu llave debe estar disponible para el `ssh-agent` - -Puedes verificar que tu llave esté visible para el `ssh-agent` si ejecutas el siguiente comando: - -```shell -ssh-add -L -``` - -Si el comando dice que no hay identidad disponible, necesitarás agregar tu llave: - -```shell -$ ssh-add yourkey -``` - -{% tip %} - -En Mac OS X, `ssh-agent` "olvidará" esta llave una vez que se reinicie. Pero puedes importar tus llaves SSH en Keychain si utilizas este comando: - -```shell -$ ssh-add -K yourkey -``` - -{% endtip %} - -[tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html -[generating-keys]: /articles/generating-ssh-keys -[generating-keys]: /articles/generating-ssh-keys -[autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows diff --git a/translations/es-XL/content/developers/webhooks-and-events/events/github-event-types.md b/translations/es-XL/content/developers/webhooks-and-events/events/github-event-types.md deleted file mode 100644 index d1f937bb10..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/events/github-event-types.md +++ /dev/null @@ -1,250 +0,0 @@ ---- -title: Tipos de evento de GitHub -intro: 'Para la API de Eventos de {% data variables.product.prodname_dotcom %}, aprende acerca de cada tipo de evento, la acción que los desencadena en {% data variables.product.prodname_dotcom %}, y las propiedades exclusivas de cada evento.' -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /v3/activity/event_types - - /developers/webhooks-and-events/github-event-types -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Events ---- -La API de eventos puede devolver diferentes tipos de ventos que se activan de acuerdo a la actividad en GitHub. Cada respuesta de evento contiene propiedades compartidas, pero tiene un objeto único de `payload` que se determina por su tipo de evento. Las [propiedades comunes del objeto de los eventos](#event-object-common-properties) describen aquellas propiedades que comparten todos los eventos, y cada tipo de evento describe las propiedades de la `payload` que son exclusivas para éste. - -{% if currentVersion == "free-pro-team@latest" %} - -{% endif %} - - -### Propiedades comunes del objeto de los eventos - -Los objetos de los eventos que se devuelven de las terminales de la API de Eventos tienen la misma estructura. - -| Nombre del atributo de la API del Evento | Descripción | -| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | Identificador único para el evento. | -| `type` | El tipo de evento. Los eventos utilizan PascalCase para el nombre. | -| `actor (actor)` | El usuario que activó el evento. | -| `actor.id` | El identificador único para el actor. | -| `actor.login` | El nombre de usuario para el actor. | -| `actor.display_login` | El formato de visualización específico para el nombre de usuario. | -| `actor.gravatar_id` | El identificador único del perfil de Gravatar para el actor. | -| `actor.url` | La URL de la API de REST que se utiliza para recuperar el objeto del usuario, el cual incluye información adicional del usuario. | -| `actor.avatar_url` | La URL de la imagen de perfil del actor. | -| `repo` | El objeto del repositorio en donde ocurrió el evento. | -| `repo.id` | El identificador único del repositorio. | -| `repo.name` | El nombre del repositorio, el cual incluye también al nombre del propietario. Por ejemplo, el nombre del repositorio `hello-world`, cuyo propietario es la cuenta de usuario `octocat`, es `octocat/hello-world`. | -| `repo.url` | La URL de la API de REST que se utiliza para recuperar el objeto del repositorio, el cual incluye información adicional sobre dicho repositorio. | -| `payload` | El objeto de la carga útil del evento que es exclusivo para el tipo de evento. En el siguiente ejemplo puedes ver el tipo de evento para el objeto de `payload` de la API de eventos. | - -#### Ejemplo con el objeto de evento WatchEvent - -Este ejemplo te muestra el formato de la respuesta de [WatchEvent](#watchevent) cuando utilizas la [API de Eventos](/v3/activity/events). - -``` -HTTP/1.1 200 OK -Link: ; rel="next", - ; rel="last" -``` -```json -[ - { - "type": "WatchEvent", - "public": true, - "payload": { - }, - "repo": { - "id": 3, - "name": "octocat/Hello-World", - "url": "https://api.github.com/repos/octocat/Hello-World" - }, - "actor": { - "id": 1, - "login": "octocat", - "gravatar_id": "", - "avatar_url": "https://github.com/images/error/octocat_happy.gif", - "url": "https://api.github.com/users/octocat" - }, - "org": { - "id": 1, - "login": "github", - "gravatar_id": "", - "url": "https://api.github.com/orgs/github", - "avatar_url": "https://github.com/images/error/octocat_happy.gif" - }, - "created_at": "2011-09-06T17:26:27Z", - "id": "12345" - } -] -``` - -### CommitCommentEvent - -{% data reusables.webhooks.commit_comment_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.commit_comment_properties %} - -### CreateEvent - -{% data reusables.webhooks.create_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.create_properties %} - -### DeleteEvent - -{% data reusables.webhooks.delete_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.delete_properties %} - -### ForkEvent - -{% data reusables.webhooks.fork_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.fork_properties %} - -### GollumEvent - -{% data reusables.webhooks.gollum_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.gollum_properties %} - -### IssueCommentEvent - -{% data reusables.webhooks.issue_comment_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.issue_comment_webhook_properties %} -{% data reusables.webhooks.issue_comment_properties %} - -### IssuesEvent - -{% data reusables.webhooks.issues_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.issue_event_api_properties %} -{% data reusables.webhooks.issue_properties %} - -### MemberEvent - -{% data reusables.webhooks.member_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.member_event_api_properties %} -{% data reusables.webhooks.member_properties %} - -### PublicEvent - -{% data reusables.webhooks.public_short_desc %} - -#### Objeto de `payload` del evento - -Este evento devuelve un objeto de `payload` vacío. - -### PullRequestEvent - -{% data reusables.webhooks.pull_request_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.pull_request_event_api_properties %} -{% data reusables.webhooks.pull_request_properties %} - -### PullRequestReviewCommentEvent - -{% data reusables.webhooks.pull_request_review_comment_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.pull_request_review_comment_event_api_properties %} -{% data reusables.webhooks.pull_request_review_comment_properties %} - -### PushEvent - -{% data reusables.webhooks.push_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -| Clave | Tipo | Descripción | -| -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `push_id` | `número` | Identificador único para la carga. | -| `tamaño` | `número` | La cantidad de confirmaciones de la carga. | -| `distinct_size` | `número` | La cantidad de confimraciones distintas para la carga. | -| `ref` | `secuencia` | Toda la [`git ref`](/v3/git/refs/) que se cargó. Ejemplo: `refs/heads/master`. | -| `encabezado` | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga. | -| `before` | `secuencia` | El SHA de la confirmación más reciente en `ref` antes de la carga. | -| `commits` | `array` | 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](/v3/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[][sha]` | `secuencia` | El SHA 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. | - -### ReleaseEvent - -{% data reusables.webhooks.release_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.release_event_api_properties %} -{% data reusables.webhooks.release_properties %} - -{% if currentVersion == "free-pro-team@latest" %} -### SponsorshipEvent - -{% data reusables.webhooks.sponsorship_short_desc %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.sponsorship_event_api_properties %} -{% data reusables.webhooks.sponsorship_properties %} -{% endif %} - -### WatchEvent - -{% data reusables.webhooks.watch_short_desc %} - -{% data reusables.webhooks.events_api_payload %} - -#### Objeto de `payload` del evento - -{% data reusables.webhooks.watch_properties %} diff --git a/translations/es-XL/content/developers/webhooks-and-events/events/index.md b/translations/es-XL/content/developers/webhooks-and-events/events/index.md deleted file mode 100644 index 51a96d2e2f..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/events/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Eventos -intro: 'Tus integraciones pueden suscribirse y reaccionar a los eventos en {% data variables.product.prodname_dotcom %}.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Events -children: - - /github-event-types - - /issue-event-types ---- - diff --git a/translations/es-XL/content/developers/webhooks-and-events/events/issue-event-types.md b/translations/es-XL/content/developers/webhooks-and-events/events/issue-event-types.md deleted file mode 100644 index 1c84aceadb..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/events/issue-event-types.md +++ /dev/null @@ -1,735 +0,0 @@ ---- -title: Tipos de eventos de los informes de problemas -intro: 'Para la API de Eventos de Informes de Problemas y la API de Línea de Tiempo, aprende sobre cada tipo de evento, la acción que los activa en {% data variables.product.prodname_dotcom %} y las propiedades exclusivas de cada uno de ellos.' -redirect_from: - - /v3/issues/issue-event-types - - /developers/webhooks-and-events/issue-event-types -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Events ---- -Los eventos de informes de problemas se activan dependiendo de la actividad en las solicitudes de extracción e informes de problemas y se encuentran disponibles en la [API de eventos de informes de problemas](/v3/issues/events) y en la [API de Eventos de la Línea de Tiempo](/v3/issues/timeline). Cada tipo de evento especifica si éste está disponible en la API de Eventos de los Informes de Problemas o en la de Eventos de la Línea de tiempo. - - -La API de REST de GitHub considera a cada solicitud de extracción como un informe de problemas, pero no todos los informes de problemas consitutyen una solicitud de extracción. Por esta razón, las terminales de los Eventos de Informes de Problemas y las de Eventos de la Línea de Tiempo podrían devolver tanto informes de problemas como solicitudes de extracción en su respuesta. Las solicitudes de extracción tienen una propiedad de `pull_request` en el objeto del `issue`. Ya que todas las solicitudes de extracción son informes de problemas, las cantidades de unas y de otras no se duplican en un repositorio. Por ejemplo, si abres tu primer informe de problemas en un repositorio, la cantidad será de 1. Si después abres una solicitud de extracción, a cantidad será de 2. Cada tipo de evento especifica si éste ocurre en solicitudes de extracción, informes de problemas, o en ambos. - -### Propiedades comunes del objeto del evento de los informes de problemas - -Los eventos de los informes de problemas tienen la misma estructura de objeto, excepto aquellos eventos que solo se encuentran disponibles en la API de Eventos de la Línea de Tiempo. Algunos eventos también incluyen propiedades adicionales que proporcionan más contexto acerca de los recursos de éstos. Consulta el evento específico para encontrar más detalles sobre cualquier propiedad que difiera de este formato de objeto. - -{% data reusables.issue-events.issue-event-common-properties %} - -### added_to_project - -El informe de problemas o solicitud de extracción se agregó a un tablero de proyecto. {% data reusables.projects.disabled-projects %} - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitud de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.pre-release-program.starfox-preview %} -{% data reusables.pre-release-program.api-preview-warning %} - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.project-card-properties %} - -### assigned - -El informe de problemas o solicitud de extracción se asignó al usuario. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.assignee-properties %} - -### automatic_base_change_failed - -GitHub intentó cambiar la rama base de la solicitud de extracción automáticamente y sin éxito. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### automatic_base_change_succeeded - -GitHub intentó cambiar la rama base de la solicitud de extracción automáticamente con éxito. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### base_ref_changed - -La rama base de referencia de la solicitud de extracción cambió. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | | - - ### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### closed - -Se cerró el informe de problemas o la solicitud de extracción. Cuando está presente la `commit_id`, esta identifica a la confirmación que cerró el informe de problemas utilizando la sintaxis de "cerrados/arreglados". Para obtener más información acerca de la sintaxis, consulta la sección "[Enlazar una solicitud de extracción con un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### commented - -Un comentario se agregó al informe de problemas o solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.timeline_events_object_properties %} - -| Nombre | Tipo | Descripción | -| ------------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `url` | `secuencia` | La URL de la API de REST que recuperará el comentario del informe de problemas. | -| `html_url` | `secuencia` | La URL de HTML para el comentario del informe de problemas. | -| `issue_url` | `secuencia` | La URL de HTML para el informe de problemas. | -| `id` | `número` | El identificador único del evento. | -| `node_id` | `secuencia` | La [ID de Nodo Global](/v4/guides/using-global-node-ids) del evento. | -| `usuario` | `objeto` | La persona que comentó en el informe de problemas. | -| `created_at (creado en)` | `secuencia` | La marca de tiempo que indica cuándo se agregó el comentario. | -| `updated_at` | `secuencia` | La marca de tiempo que indica cuándo se actualizó o creó el comentario en caso de que éste jamás se haya actualizado. | -| `author_association` | `secuencia` | Los permisos que tiene el usuario en el repositorio del informe de problemas. Por ejemplo, el valor sería `"OWNER"` si el propietario del repositorio creó un comentario. | -| `cuerpo` | `secuencia` | El cuerpo de texto del comentario. | -| `event` | `secuencia` | El valor del evento es `"commented"`. | -| `actor (actor)` | `objeto` | La persona que generó el evento. | - -### committed - -Una confirmación se agregó a la rama `HEAD` de la solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.timeline_events_object_properties %} - -| Nombre | Tipo | Descripción | -| -------------------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `sha` | `secuencia` | El SHA de la confirmación en la solicitud de extracción. | -| `node_id` | `secuencia` | La [ID de Nodo Global](/v4/guides/using-global-node-ids) del evento. | -| `url` | `secuencia` | La URL de la API de REST que recuperará la confirmación. | -| `html_url` | `secuencia` | La URL de HTML de la confirmación. | -| `autor` | `objeto` | La persona que autorizó la confirmación. | -| `persona que confirma el cambio` | `objeto` | La persona que confirmó la confirmación en nombre del autor. | -| `árbol` | `objeto` | El árbol de Git de la confirmación. | -| `message` | `secuencia` | El mensaje de la confirmación. | -| `parents` | `matriz de objetos` | Una lista de confirmaciones padre. | -| `verfication` | `objeto` | El resultado de verificar la firma de la confirmación. Para obtener más información, consulta la sección "[Objeto de verificación de firmas](/v3/git/commits/#signature-verification-object)". | -| `event` | `secuencia` | El valor del evento es `"committed"`. | - -### connected - -El informe de problemas o solicitud de extracción se vinculó a otro informe de problemas o solicitud de extracción. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### convert_to_draft - -La solicitud de extracción se convirtió a modo borrador. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### converted_note_to_issue - -El informe de problemas se creó convirtiendo una nota en un tablero de proyecto para un informe de problemas. {% data reusables.projects.disabled-projects %} - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.pre-release-program.starfox-preview %} -{% data reusables.pre-release-program.api-preview-warning %} - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.project-card-properties %} - -### cross-referenced - -El informe de problemas o solicitud de extración se referenció desde otro informe de problemas o solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.timeline_events_object_properties %} - -| Nombre | Tipo | Descripción | -| ------------------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `actor (actor)` | `objeto` | La persona que generó el evento. | -| `created_at (creado en)` | `secuencia` | La marca de tiempo que indica cuándo se agregó la referencia cruzada. | -| `updated_at` | `secuencia` | La marca de tiempo que indica cuándo se actualizó o creó la referencia cruzada en caso de que ésta jamás se haya actualizado. | -| `source` | `objeto` | La solicitud de extracción o informe de problemas que agregó la referencia cruzada. | -| `source[type]` | `secuencia` | Este valor siempre será `"issue"` ya que las solicitudes de extracción son un tipo de informe de rpoblemas. En la API de Eventos de la Línea de Tiempo solo se devolverán los eventos de referencia cruzada que se activen con informes de problemas o solicitudes de extracción. Puedes verificar si existe el objeto `source[issue][pull_request` para determinar si el informe de problemas que activó el evento es una solicitud de extracción. | -| `source[issue]` | `objeto` | El objeto del `issue` que agregó la referencia cruzada. | -| `event` | `secuencia` | El valor del evento es `"cross-referenced"`. | - -### demilestoned - -El informe de problemas o solicitud de extracción se elimnó de un hito. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -`milestone` | `object` | El objeto del hito. `milestone[title]` | `string` | El título del hito. - -### deployed - -Se desplegó la solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### deployment_environment_changed - -El ambiente de despliegue de la solicitud de extracción cambió. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### disconnected - -El informe de problemas o solicitud de extracción se desvinculó de otro informe de problemas o solicitud de extracción. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### head_ref_deleted - -Se eliminó la rama `HEAD` de la solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### head_ref_restored - -Se restauró la rama `HEAD` de la solicitud de extracción a su última confirmación conocida. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### labeled - -Se agregó una etiqueta al informe de problemas o solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.label-properties %} - -### locked - -Se bloqueó el informe de problemas o la solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -{% data reusables.pre-release-program.sailor-v-preview %} -{% data reusables.pre-release-program.api-preview-warning %} -{% endif %} - -{% data reusables.issue-events.issue-event-common-properties %} -`lock_reason` | `string` | La razón por la cual se bloqueó un informe de problemas o solicitud de extracción, si es que se proporcionó alguna. - -### mentioned - -Se `@mentioned` al `actor` en el cuerpo de un informe de problemas o solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### marked_as_duplicate - -Un usuario con permisos de escritura marcó un informe de problemas como el duplicado de otro, o el mismo caso con alguna solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### fusionado - -Se fusionó la solicitud de extracción. El atributo de `commit_id` es el SHA1 de la confirmación `HEAD` que se fusionó. El `commit_repository` siempre es el mismo que el repositorio principal. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### milestoned - -El informe de problemas o solicitud de extracción se agregó a un hito. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -`milestone` | `object` | El objeto del hito. `milestone[title]` | `string` | El título del hito. - -### moved_columns_in_project - -El informe de problemas o solicitud de extracción se movió entre columnas en un tablero de proyecto. {% data reusables.projects.disabled-projects %} - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.pre-release-program.starfox-preview %} -{% data reusables.pre-release-program.api-preview-warning %} - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.project-card-properties %} -`previous_column_name` | `string` | El nombre de la columna desde la cual se movió el informe de problemas. - -### pinned - -Se fijó el informe de problemas. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### ready_for_review - -Se creó una solicitud de extracción que no está en modo borrador. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### referenced - -Se referenció al informe de problemas desde un mensaje de confirmación. El atributo `commit_id` es la confirmación de tipo SHA1 de donde eso sucedió y el commit_repository es el lugar donde se cargó esa confirmación. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### removed_from_project - -El informe de problemas o solicitud de extracción se eliminó de un tablero de proyecto. {% data reusables.projects.disabled-projects %} - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.pre-release-program.starfox-preview %} -{% data reusables.pre-release-program.api-preview-warning %} - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.project-card-properties %} - -### renombrado - -Se cambió el informe de problemas o la solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -`rename` | `object` | Los detalles del nombre. `rename[from]` | `string` | El nombre anterior. `rename[to]` | `string` | El nombre nuevo. - -### reopened - -El informe de problemas o solicitud de extracción se reabrió. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### review_dismissed - -Se destituyó la revisión de la solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.review-dismissed-properties %} - -### review_requested - -Se solicitó una revisión de una solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.review-request-properties %} - -### review_request_removed - -Se eliminó una solicitud de revisión para una solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.review-request-properties %} - -### reviewed - -Se revisió la solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Solicitudes de extracción
    | | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.timeline_events_object_properties %} - -| Nombre | Tipo | Descripción | -| -------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `número` | El identificador único del evento. | -| `node_id` | `secuencia` | La [ID de Nodo Global](/v4/guides/using-global-node-ids) del evento. | -| `usuario` | `objeto` | La persona que comentó en el informe de problemas. | -| `cuerpo` | `secuencia` | El texto de resúmen de la revisión. | -| `commit_id` | `secuencia` | El SHA de la última confirmación en la soicitud de extracción al momento de la revisión. | -| `submitted_at` | `secuencia` | La marca de tiempo que indica cuándo se emitió la revisión. | -| `state` | `secuencia` | El estado de la revisión emitida. Puede ser uno de entre: `commented`, `changes_requested`, o `approved`. | -| `html_url` | `secuencia` | La URL de HTML para la revisión. | -| `pull_request_url` | `secuencia` | La URL de la API de REST que recuperará la solicitud de extracción. | -| `author_association` | `secuencia` | Los permisos que tiene el usuario en el repositorio del informe de problemas. Por ejemplo, el valor sería `"OWNER"` si el propietario del repositorio creó un comentario. | -| `_links` | `objeto` | El `html_url` y `pull_request_url`. | -| `event` | `secuencia` | El valor del evento es `"reviewed"`. | - -### subscribed - -Alguien se suscribió para recibir notificaciones para un informe de problemas o solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### transferred - -El informe de problemas se transfirió a otro repositorio. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### unassigned - -De desasignó a un usuario del informe de problemas. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.assignee-properties %} - -### unlabeled - -La etiqueta se eliminó del informe de problemas. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} -{% data reusables.issue-events.label-properties %} - -### unlocked - -Se desbloqueó el informe de problemas. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -{% data reusables.pre-release-program.sailor-v-preview %} -{% data reusables.pre-release-program.api-preview-warning %} -{% endif %} - -{% data reusables.issue-events.issue-event-common-properties %} -`lock_reason` | `string` | La razón por la cual se bloqueó un informe de problemas o solicitud de extracción, si es que se proporcionó alguna. - -### unmarked_as_duplicate - -Un informe de problemas que algún usuario había marcado previamente como duplicado de otro informe de problemas ya no se considera como duplicado, o el mismo caso con solicitudes de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### unpinned - -El informe de problemas dejó de fijarse. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -### unsubscribed - -Alguien se desuscribió de recibir notificaciones para un informe de problemas o solicitud de extracción. - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -{% if currentVersion == "free-pro-team@latest" %} -### user_blocked - -El propietario de una organización bloqueó a un usuario de la misma. Esto se hizo [a través de uno de los comentarios del usuario bloqueado sobre el informe de problemas](/articles/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment). - -#### Disponibilidad - -| Tipo de Informe de Problemas | API de eventos de Informes de Problemas | API de eventos de la línea de Tiempo | -|:---------------------------- |:---------------------------------------:|:------------------------------------:| -|
    • Problemas
    • Solicitudes de extracción
    | **X** | **X** | - -#### Propiedades del objeto del evento - -{% data reusables.issue-events.issue-event-common-properties %} - -{% endif %} diff --git a/translations/es-XL/content/developers/webhooks-and-events/index.md b/translations/es-XL/content/developers/webhooks-and-events/index.md deleted file mode 100644 index b7e804f92b..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Webhooks y eventos -intro: 'Puedes configurar, probar y asegurar los webhooks para que tus integraciones puedan suscribirse y reaccionar a los eventos en {% data variables.product.prodname_dotcom %}.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Webhooks - - Events -children: - - /webhooks - - /events ---- -### Índice diff --git a/translations/es-XL/content/developers/webhooks-and-events/webhooks/about-webhooks.md b/translations/es-XL/content/developers/webhooks-and-events/webhooks/about-webhooks.md deleted file mode 100644 index ab2b477c04..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/webhooks/about-webhooks.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: About webhooks -intro: Learn the basics of how webhooks work to help you build and set up integrations. -redirect_from: - - /webhooks - - /developers/webhooks-and-events/about-webhooks -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Webhooks ---- -Webhooks allow you to build or set up integrations, such as [{% data variables.product.prodname_github_app %}s](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_app %}s](/apps/building-oauth-apps/), which subscribe to certain events on GitHub.com. When one of those events is triggered, we'll send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. You're only limited by your imagination. - -Webhooks can be installed on{% if currentVersion != "free-pro-team@latest" %} a [{% data variables.product.prodname_ghe_server %} instance](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} an [organization][org-hooks], a specific [repository][repo-hooks], or a {% data variables.product.prodname_github_app %}. Once installed, the webhook will be sent each time one or more subscribed events occurs. - -You can create up to {% if currentVersion != "free-pro-team@latest" %}250{% else %}20{% endif %} webhooks for each event on each installation target {% if currentVersion != "free-pro-team@latest" %}({% data variables.product.prodname_ghe_server %} instance, specific organization, or specific repository).{% else %}(specific organization or specific repository).{% endif %} - -### Events - -{% data reusables.webhooks.webhooks_intro %} - -Each event corresponds to a certain set of actions that can happen to your organization and/or repository. For example, if you subscribe to the `issues` event you'll receive detailed payloads every time an issue is opened, closed, labeled, etc. - -See "[Webhook event payloads](/webhooks/event-payloads)" for the list of available webhook events and their payloads. - -### Ping event - -{% data reusables.webhooks.ping_short_desc %} - -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]: /v3/repos/hooks/ diff --git a/translations/es-XL/content/developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads.md b/translations/es-XL/content/developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads.md deleted file mode 100644 index 963c240019..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Configurar tu servidor para recibir cargas útiles -intro: Aprende a conigurar un servidor para administrar las cargas útiles de webhook entrantes. -redirect_from: - - /webhooks/configuring - - /developers/webhooks-and-events/configuring-your-server-to-receive-payloads -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Webhooks ---- -Ahora que tu webhook está listo para entregar mensajes, configuraremos un servidor básico de Sinatra para gestionar las cargas útiles entrantes. - -Recuerda que configuramos nuestra URL del webhook específicamente como `http://localhost:4567/payload`. Ya que estamos desarrollando localmente, necesitaremos exponer nuestro ambiente de desarrollo local a la internet para que GitHub pueda enviar mensajes y para que nuestro servidor local los pueda procesar. - -Nota: puedes descargar el código fuente completo para este proyecto [del repositorio de ejemplos de plataforma][platform samples]. - -### Utilizando ngrok - -Primero, instalaremos un programa para exponer nuestro host local a la internet. Utilizaremos ngrok para hacerlo. [ngrok es una descarga gratuita](https://ngrok.com/download) disponible para todos los sistemas operativos principales. - -Cuando termines de hacerlo, puedes exponer tu localhost si ejecutas `./ngrok http 4567` en la línea de comandos. Deberías ver una línea que se ve más o menos así: - -```shell -$ Forwarding http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567 -``` - -¡Copia esa URL rara de `*.ngrok.io`! Ahora vamos a *regresar* a la URL de la carga útil y vamos a pegar este servidor en ese campo. Se vería ver más o menos como `http://7e9ea9dc.ngrok.io/payload`. - -Cuando lo hacemos, nos hemos preparado para exponer nuestro localhost a la internet en la ruta `/payload`. - -### Escribir el servidor - -¡Ahora viene lo divertido! Queremos que nuestro servidor escuche a las solicitudes de `POST`, en `/payload`, porque es donde le dijimos a GitHub que estaba nuestra URL. Ya que ngrok expone nuestro ambiente local, no necesitamos configurar un servidor real en línea, y podemos probar nuestro código felizmente de manera local. - -Vamos a configurar una pequeña app de Sinatra para que haga algo con la información. Nuestra configuración inicial se verá más o menos así: - -``` ruby -require 'sinatra' -require 'json' - -post '/payload' do - push = JSON.parse(request.body.read) - puts "I got some JSON: #{push.inspect}" -end -``` - -(Si no estás familiarizado con como funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra].) - -Inicia este servidor. - -Ya que configuramos nuestros webhooks para escuchar a los eventos que tengan que ver con `Issues`, continúa y crea un informe de problemas nuevo en el repositorio en el cual estés haciendo las pruebas. Una vez que lo hayas creado, regresa a tu terminal. Deberías ver algo más o menos como esto en tu salida: - -```shell -$ ~/Developer/platform-samples/hooks/ruby/configuring-your-server $ ruby server.rb -> == Sinatra/1.4.4 has taken the stage on 4567 for development with backup from Thin -> >> Thin web server (v1.5.1 codename Straight Razor) -> >> Maximum connections set to 1024 -> >> Listening on localhost:4567, CTRL+C to stop -> I got some JSON: {"action"=>"opened", "issue"=>{"url"=>"... -``` - -¡Exito! Configuraste exitosamente tu servidor para que escuche a los webhooks. Ahora tu servidor puede procesar esta información en cualquier manera que te parezca pertinente. Por ejemplo, si estuvieras configurando una aplicación web "real", tal vez quisieras registrar algo de la salida de JSON en una base de datos. - -Para obtener información adicional sobre cómo trabajar con los webhooks por diverción y por ganancias, dirígete a la guía de cómo [Probar los Webhooks](/webhooks/testing). - -[platform samples]: https://github.com/github/platform-samples/tree/master/hooks/ruby/configuring-your-server -[Sinatra]: http://www.sinatrarb.com/ diff --git a/translations/es-XL/content/developers/webhooks-and-events/webhooks/creating-webhooks.md b/translations/es-XL/content/developers/webhooks-and-events/webhooks/creating-webhooks.md deleted file mode 100644 index 5a979fa4a0..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/webhooks/creating-webhooks.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Crear webhooks -intro: 'Aprende a crear un webhook, escoger los eventos a los cuales escuchará en {% data variables.product.prodname_dotcom %} y cómo configurar un servidor para recibir y administrar su carga útil.' -redirect_from: - - /webhooks/creating - - /developers/webhooks-and-events/creating-webhooks -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Webhooks ---- -Ahora que entendemos [lo básico de los webhooks][webhooks-overview], vamos a revisar el proceso de creación de nuestra propia integración impulsada por webhooks. En este tutorial, crearemos un webhook de repositorio que será responsable de listar qué tan popular es nuestro repositorio con base en la cantidad de informes de problemas que recibe diariamente. - -Crear un webhook es un proceso de dos pasos. Primero necesitas configurar la forma en la que quieres que se comporte tu webhook a través de {% data variables.product.product_name %}, es decir: a qué eventos quieres que escuche. Después, configurarás tu servidor para recibir y administrar la carga útil. - -### Configurar un Webhook - -Puedes instalar webhooks en una organización o en un repositorio específico. - -Para configurar un webhook, ve a la página de configuración de tu repositorio u organización. Desde ahí, da clic en **Webhooks**, y luego en **Agregar webhook**. - -Como alternativa, puedes elegir el crear y administrar un webhook [através de la API de Webhooks][webhook-api]. - -Los Webhooks necesitan configurar algunas de sus opciones antes de que los puedas utilizar. Vamos a ver cada una de éstas opciones a continuación. - -### URL de la carga útil - -{% data reusables.webhooks.payload_url %} - -Ya que estamos desarrollando todo localmente para nuestro tutorial, configurémosla como `http://localhost:4567/payload`. Te explicaremos por qué en los documentos de [Configurar tu Servidor](/webhooks/configuring/). - -### Tipo de Contenido - -{% data reusables.webhooks.content_type %} Para efecto de este tutorial, está bien si usas el tipo de contenido predeterminado de `application/json`. - -### Secreto - -{% data reusables.webhooks.secret %} - -### Verificación de SSL - -{% data reusables.webhooks.webhooks_ssl %} - -### Activo - -Predeterminadamente, las entregas de webhook están "Activas". También puedes elegir inhabilitar la entrega de cargas útiles de webhooks si deseleccionas "Activo". - -### Eventos - -Los eventos son el núcleo de los webhooks. Estos webhooks se disparan cuando se toma alguna acción específica en el repositorio, la cual intercepta tu URL de carga útil de l servidor para actuar sobre ella. - -Puedes encontrar un listado completo de eventos de webhook y del cuándo se ejecutan en la referencia de [la API de webhooks][hooks-api]. - -Ya que nuestro webhook trata con informes de problemas en un repositorio, vamos a dar clic en **Permíteme seleccionar eventos individuales** y, posteriormente, en **Informes de problemas**. Asegúrate de seleccionar **Activo** para recibir eventos de los informes de problemas para los webhooks que se activen. También puedes seleccionar todos los eventos utilizando la opción predeterminada. - -Cuando hayas terminado, da clic en **Agregar webhook**. ¡Uf! Ahora que creaste el webhook, es momento de configurar nuestro servidor local para probarlo. Dirígete a [Configurar tu Servidor](/webhooks/configuring/) para aprender cómo hacerlo. - -#### Evento de Comodín - -Para configurar un webhook para todos los eventos, utiliza el caracter de comodín (`*`) para especificar dichos eventos. Cuando agregas el evento de comodín, reemplazaremos cualquier evento existente que hayas configurado con el evento de comodín se te enviarán las cargas útiles para todos los eventos compatibles. También obtendrás automáticamente cualquier evento nuevo que pudiéramos agregar posteriormente. - -[webhooks-overview]: /webhooks/ -[webhook-api]: /v3/repos/hooks/ -[hooks-api]: /webhooks/#events diff --git a/translations/es-XL/content/developers/webhooks-and-events/webhooks/index.md b/translations/es-XL/content/developers/webhooks-and-events/webhooks/index.md deleted file mode 100644 index 650d99b774..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/webhooks/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Webhooks -intro: 'Aprende a configurar, probar y asegurar los webhooks para integrarte con {% data variables.product.prodname_dotcom %}.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Webhooks -children: - - /about-webhooks - - /creating-webhooks - - /configuring-your-server-to-receive-payloads - - /testing-webhooks - - /securing-your-webhooks - - /webhook-events-and-payloads ---- - diff --git a/translations/es-XL/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/es-XL/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md deleted file mode 100644 index f11f569711..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Asegurar tus webhooks -intro: 'Asegúrate de que tu servidor está recibiendo únicamente las solicitudes de {% data variables.product.prodname_dotcom %} esperadas por razones de seguridad.' -redirect_from: - - /webhooks/securing - - /developers/webhooks-and-events/securing-your-webhooks -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Webhooks ---- -Una vez que tu servidor se configure para recibir cargas útiles, éste escuchará a cualquiera de ellas que se envíe a la terminal que configuraste. Por razones de seguridad, probablemente quieras limitar las solicitudes a aquellas que vengan de GitHub. Hay algunas formas de solucionar esto, por ejemplo, podrías decidir el permitir las solicitudes que vengan de la dirección IP de GitHub, pero una manera mucho más fácil es configurar un token secreto y validar la información. - - -### Configurar tu token secreto - -Necesitarás configurar tu token secreto en dos lugares: GitHub y tu servidor. - -Para configurar tu token en GitHub: - -1. Navega al repositorio en donde configuraste tu webhook. -2. Llena la caja de texto del secreto. Utiliza una secuencia aleatoria con entropía alta (por ejemplo, tomando la salida de `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` en la terminal). ![Campo de webhook y de token secreto](/assets/images/webhook_secret_token.png) -3. Da clic en **Actualizar Webhook**. - -Después, configura una variable de ambiente en tu servidor, la cual almacene este token. Por lo general, esto es tan simple como el ejecutar: - -```shell -$ export SECRET_TOKEN=your_token -``` - -¡**Jamás** preprogrames el token en tu app! - -### Validar cargas útiles de GitHub - -Cuando configuras tu token secreto, GitHub lo utiliza para crear una firma de hash con cada carga útil. - -Esta firma de hash se pasa entre cada solicitud en los encabezados como una `X-Hub-Signature`. Supongamos que tienes un servidor básico escuchando a los webhooks y que se ve así: - -``` ruby -require 'sinatra' -require 'json' - -post '/payload' do - push = JSON.parse(params[:payload]) - "I got some JSON: #{push.inspect}" -end -``` - -La meta es calcular el hash utilizando tu `SECRET_TOKEN`, y garantizar que el hash de GitHub empate con éste. GitHub utiliza un hexdigest de HMAC para calcular el hash, así que podrías cambiar tu servidor para que se vea así: - -``` ruby -post '/payload' do - request.body.rewind - payload_body = request.body.read - verify_signature(payload_body) - push = JSON.parse(params[:payload]) - "I got some JSON: #{push.inspect}" -end - -def verify_signature(payload_body) - signature = 'sha1=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha1'), ENV['SECRET_TOKEN'], payload_body) - return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_HUB_SIGNATURE']) -end -``` - -Obviamente, tus implementaciones de lenguaje y de servidor podrían diferir de este código. Hay un par de cosas muy importantes que señalar, sin embargo: - -* Sin importar qué implementación utilices, a firma de hash comienza con `sha1=`, utilizando la llave de tu token secreto y el cuerpo de tu carga útil. - -* **No se recomienda** utilizar un simple operador de `==`. Un método tal como [`secure_compare`][secure_compare] lleva a cabo una comparación de secuencias en "tiempo constante", lo cual la hace segura contra ciertos ataques de tiempo contra los operadores de igualdad habitual. - -[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare diff --git a/translations/es-XL/content/developers/webhooks-and-events/webhooks/testing-webhooks.md b/translations/es-XL/content/developers/webhooks-and-events/webhooks/testing-webhooks.md deleted file mode 100644 index 24579ab47f..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/webhooks/testing-webhooks.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Probar los webhooks -intro: 'Revisa tus entregas de webhook en {% data variables.product.prodname_dotcom %}, incluyendo la solicitud HTTP y la carga útil, así como la respuesta.' -redirect_from: - - /webhooks/testing - - /developers/webhooks-and-events/testing-webhooks -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Webhooks ---- -Ahor que [configuraste tu servidor local](/webhooks/configuring/), podrías estar interesado en llevar tu código a sus límites. Para ello, la vista de webhooks de GitHub te proporciona herramientas para probar tus cargas útiles desplegadas. - -### Listar las entregas recientes - -Cada webhook tiene su propia sección de "Entregas Recientes", la cual lista de un vistazo si el despliegue fue exitoso (paloma verde) o fallido (x roja). También puedes identificar cuando se intentó cada entrega. - -{% data variables.product.product_name %} mantiene una bitácora de cada entrega de webhook para {% if currentVersion == "free-pro-team@latest" %}30 {% else %} 8 {% endif %} días. - -![Vista de entregas recientes](/assets/images/webhooks_recent_deliveries.png) - -### Profundizar en los resultados - -Si expandes una entrega individual podrás presenciar *exactamente* qué información de GitHub se está intentando enviar a tu servidor. Esto incluye tanto la solicitud de HTTP como la respuesta. - -#### Solicitud - -La vista de entregas del webhook te proporciona información sobre qué encabezados se enviaron a través de GitHub. También incluye detalles acerca de la carga útil de JSON. - -![Visualizar la solicitud de una carga útil](/assets/images/payload_request_tab.png) - -#### Respuesta - -La pestaña de respuesta lista la forma en que tu servidor respondió una vez que recibió la carga útil de GitHub. Esto incluye al código de estado, a los encabezados y a cualquier dato adicional dentro del cuerpo de la respuesta. - -![Visualizar la respuesta de una carga útil](/assets/images/payload_response_tab.png) diff --git a/translations/es-XL/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/es-XL/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md deleted file mode 100644 index bccb23a915..0000000000 --- a/translations/es-XL/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ /dev/null @@ -1,1324 +0,0 @@ ---- -title: Eventos y cargas útiles de un Webhook -intro: 'Para cada evento de webhook, puedes revisar cuándo ocurre el evento, una carga útil de ejemplo, y las descripciones de los parámetros del objeto de dicha carga útil.' -product: '{% data reusables.gated-features.enterprise_account_webhooks %}' -redirect_from: - - /early-access/integrations/webhooks/ - - /v3/activity/events/types/ - - /webhooks/event-payloads - - /developers/webhooks-and-events/webhook-events-and-payloads -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - Webhooks ---- -{% if currentVersion == "free-pro-team@latest" %} - -{% endif %} - -{% data reusables.webhooks.webhooks_intro %} - -Puedes crear webhooks que se suscriban a los eventos listados en esta página. Cada evento de webhook incluye una descripción de las propiedades de dicho webhook y un ejemplo de carga útil. Para obtener más información, consulta "[Crear webhooks](/webhooks/creating/)". - - -### Propuiedades comunes del objeto de la carga útil del webhook - -Cada carga útil del evento del webhook contiene propiedades únicas de dicho evento. Puedes encontrar estas propiedades únicas en las secciones individuales de tipo de evento. - -| Clave | Tipo | Descripción | -| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ | -| `Acción` | `secuencia` | La mayoría de las cargas útiles de webhooks contienen una propiedad de `action` que contiene la actividad específica que activa el evento. | - -{% data reusables.webhooks.sender_desc %} Esta propiedad se incluye en cada carga útil del webhook. -{% data reusables.webhooks.repo_desc %} Las cargas útiles del webhook contienen la propiedad - -`repository` cuando el evento ocurre desde una actividad en un repositorio. -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} Para obtener más información, consulta la sección "[Crear una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)". - -Las propiedades únicas de un evento de webhook son las mismas que encontrarás en la propiedad `payload` cuando utilices la [API de eventos](/v3/activity/events/). Una excepción es el [evento `push`](#push). Las propiedades únicas de la carga útil del evento `push` del webhook y la propiedad `payload` en la API de Eventos difieren entre ellos. La carga útil del webhook contiene información más detallada. - -{% tip %} - -**Nota:** Las cargas útiles se limitan a los 25 MB. Si tu evento genera una carga útil mayor, el webhook no se lanzará. Esto puede pasar, por ejemplo, en un evento de `create` si muchas ramas o etiquetas se cargan al mismo tiempo. Te sugerimos monitorear el tamaño de tu carga útil para garantizar la entrega. - -{% endtip %} - -#### Encabezados de entrega - -Las cargas útiles de HTTP POST que se entregan a la terminal URL configurada para tu webhook contendrán varios encabezados especiales: - -| Encabezado | Descripción | -| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-GitHub-Event` | Nombre del evento que desencadenó la entrega. | -| `X-GitHub-Delivery` | Un [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) para identificar la entrega.{% if currentVersion != "free-pro-team@latest" %} -| `X-GitHub-Enterprise-Version` | La versión de la instancia de {% data variables.product.prodname_ghe_server %} que envía la carga útil del HTTP POST. | -| `X-GitHub-Enterprise-Host` | El nombre del host para la instancia del {% data variables.product.prodname_ghe_server %} que envió la carga útil de HTTP POST.{% endif %} -| `X-Hub-Signature` | El resumen hexadecimal de HMAC del cuerpo de la respuesta. Este encabezado se enviará si el webhook se configura con un [`secret`](/v3/repos/hooks/#create-hook-config-params). El resumen hexadecimal de HMAC se genera utilizando la función hash `sha1` y el `secret` como la `key` de HMAC. | - -También, el `User-Agent` para las solicitudes tendrá el prefijo `GitHub-Hookshot/`. - -#### Ejemplo de entrega - -```shell -> POST /payload HTTP/1.1 - -> Host: localhost:4567 -> X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% if currentVersion != "free-pro-team@latest" %} -> X-GitHub-Enterprise-Version: 2.15.0 -> X-GitHub-Enterprise-Host: example.com{% endif %} -> X-Hub-Signature: sha1=7d38cdd689735b008b3c702edd92eea23791c5f6 -> User-Agent: GitHub-Hookshot/044aadd -> Content-Type: application/json -> Content-Length: 6615 -> X-GitHub-Event: issues - -> { -> "action": "opened", -> "issue": { -> "url": "{% data variables.product.api_url_pre %}/repos/octocat/Hello-World/issues/1347", -> "number": 1347, -> ... -> }, -> "repository" : { -> "id": 1296269, -> "full_name": "octocat/Hello-World", -> "owner": { -> "login": "octocat", -> "id": 1, -> ... -> }, -> ... -> }, -> "sender": { -> "login": "octocat", -> "id": 1, -> ... -> } -> } -``` - -### check_run - -{% data reusables.webhooks.check_run_short_desc %} - -{% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} - -#### Disponibilidad - -- 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 -- Las {% data variables.product.prodname_github_app %}s 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_app %}s con el `checks:write` se suscriben automáticamente a este evento de webhook. - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.check_run_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.check_run.created }} - -### check_suite - -{% data reusables.webhooks.check_suite_short_desc %} - -{% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} - -#### Disponibilidad - -- 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 -- Las {% data variables.product.prodname_github_app %}s 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_app %}s con el `checks:write` se suscriben automáticamente a este evento de webhook. - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.check_suite_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.check_suite.completed }} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -### comentario_confirmación de cambios - -{% data reusables.webhooks.code_scanning_alert_event_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `contents` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.code_scanning_alert_event_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -`sender` | `object` | 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` estará vacío en el resto de las acciones. - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }} - -### comentario_confirmación de cambios - -{% data reusables.webhooks.commit_comment_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `contents` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.commit_comment_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.commit_comment.created }} -{% endif %} - -### content_reference - -{% data reusables.webhooks.content_reference_short_desc %} - -Los eventos de webhook se desencadenan basándose en la especificidad del dominio que registres. Por ejemplo, si registras un subdominio (`https://subdomain.example.com`), entonces la única URL para el subdominio activarán este evento. Si registras un dominio (`https://example.com`) entonces las URL para el dominio y todos sus subdominios activarán este evento. Consulta la sección "[Crear un adjunto de contenido](/v3/apps/installations/#create-a-content-attachment)" para crear un nuevo adjunto de contenido. - -Solo las {% data variables.product.prodname_github_app %}s podrán recibir este evento. Las {% data variables.product.prodname_github_app %}s deben tener el permiso `content_references` `write` para suscribirse a este evento. - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.content_reference.created }} - -### create (crear) - -{% data reusables.webhooks.create_short_desc %} - -{% note %} - -**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo. - -{% endnote %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `contents` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.create_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.create }} - -### eliminar - -{% data reusables.webhooks.delete_short_desc %} - -{% note %} - -**Nota:** No recibirás un webhook para este evento cuando borres más de tres etiquetas al mismo tiempo. - -{% endnote %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `contents` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.delete_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.delete }} - -### deploy_key - -{% data reusables.webhooks.deploy_key_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.deploy_key_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.deploy_key.created }} - -### deployment - -{% data reusables.webhooks.deployment_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `deployments` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ------------ | --------------------------------------------------------------- | ---------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -| `Acción` | `secuencia` | La acción realizada. Puede ser `created`.{% endif %} -| `deployment` | `objeto` | El [lanzamiento](/v3/repos/deployments/#list-deployments). | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.deployment }} - -### deployment_status - -{% data reusables.webhooks.deployment_status_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `deployments` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ---------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -| `Acción` | `secuencia` | La acción realizada. Puede ser `created`.{% endif %} -| `deployment_status` | `objeto` | El [Estado del lanzamiento](/v3/repos/deployments/#list-deployment-statuses). | -| `deployment_status["state"]` | `secuencia` | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`. | -| `deployment_status["target_url"]` | `secuencia` | El enlace opcional agregado al estado. | -| `deployment_status["description"]` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado. | -| `deployment` | `objeto` | El [lanzamiento](/v3/repos/deployments/#list-deployments) con el que se asocia este estado. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.deployment_status }} - -{% if currentVersion != "free-pro-team@latest" %} - -### empresa - -{% data reusables.webhooks.enterprise_short_desc %} - -#### Disponibilidad - -- Webhooks de GitHub Enterprise. Para obtener más información, consulta "[Webhooks globales](/v3/enterprise-admin/global_webhooks/)". - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------- | ----------- | ---------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser `anonymous_access_enabled` o `anonymous_access_disabled`. | - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }} - -{% endif %} - -### bifurcación - -{% data reusables.webhooks.fork_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `contents` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.fork_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.fork }} - -### github_app_authorization - -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 %} 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_app %}s](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". - -#### Disponibilidad - -- {% data variables.product.prodname_github_app %}s - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------- | ----------- | ----------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser `revoked`. | -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }} - -### gollum - -{% data reusables.webhooks.gollum_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `contents` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.gollum_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.gollum }} - -### instalación - -{% data reusables.webhooks.installation_short_desc %} - -{% note %} - -**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo. - -{% endnote %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -{% note %} - -**Nota:**{% data reusables.pre-release-program.suspend-installation-beta %}Para obtener más información, consulta la sección "[Suspender la instalación de una {% data variables.product.prodname_github_app %}](/apps/managing-github-apps/suspending-a-github-app-installation/)". - -{% endnote %} -{% endif %} - -#### Disponibilidad - -- {% data variables.product.prodname_github_app %}s - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.installation_properties %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.installation.deleted }} - -### installation_repositories - -{% data reusables.webhooks.installation_repositories_short_desc %} - -{% note %} - -`repository` cuando el evento ocurre desde una actividad en un repositorio. - -{% endnote %} - -#### Disponibilidad - -- {% data variables.product.prodname_github_app %}s - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.installation_repositories_properties %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.installation_repositories.added }} - -### comentario_propuesta - -{% data reusables.webhooks.issue_comment_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `issues` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.issue_comment_webhook_properties %} -{% data reusables.webhooks.issue_comment_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.issue_comment.created }} - -### propuestas - -{% data reusables.webhooks.issues_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `issues` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.issue_webhook_properties %} -{% data reusables.webhooks.issue_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook cuando alguien edita un informe de problemas - -{{ webhookPayloadsForCurrentVersion.issues.edited }} - -### etiqueta - -{% data reusables.webhooks.label_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `metadata` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ---------------------- | ----------- | --------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`, `edited`, o `deleted`. | -| `etiqueta` | `objeto` | La etiqueta que se añadió. | -| `changes` | `objeto` | Los cambios a la etiqueta si la acción se `edited` (editó). | -| `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | -| `changes[color][from]` | `secuencia` | La versión previa del color si la acción se `edited` (editó). | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.label.deleted }} - -{% if currentVersion == "free-pro-team@latest" %} -### marketplace_purchase - -Actividad relacionada con una compra en GitHub Marketplace. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta el "[GitHub Marketplace](/marketplace/)". - -#### Disponibilidad - -- {% data variables.product.prodname_github_app %}s - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada para un plan de [GitHub Marketplace](https://github.com/marketplace). Puede ser una de las siguientes:
    • `purchased` - Alguien compró un plan de GitHub Marketplace. El cambio deberá entrar en vigor en la cuenta inmediatamente.
    • `pending_change` - Reicbirás el evento `pending_change` cuando alguien haya degradado o cancelado un plan de GitHub Marketplace para indicar que ocurrirá un cambio en la cuenta. El nuevo plan o cancelación entra en vigor al final del ciclo de facturación. El tipo de evento `cancelled` o `changed` se enviará cuando haya concluido el ciclo de facturación y la cancelación o plan nuevo deberán entrar en vigor.
    • `pending_change_cancelled` - Alguien canceló un cambio pendiente. Los cambios pendientes incluyen cancelaciones y degradaciones de planes que entrarán en vigor al final del ciclo de facturación.
    • `changed` - Alguien mejoró o degradó un plan de GitHub Marketplace y el cambio deberá entrar en vigor en la cuenta de inmediato.
    • `cancelled` - Alguien canceló un plan de GitHub marketplace y el último ciclo de facturación ya terminó. El cambio deberá entrar en vigor en la cuenta inmediatamente.
    | - -Para obtener una descripción detallada de esta carga útil y de aquella para cada tipo de `action`, consulta los [eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). - -#### Ejemplo de carga útil de webhook cuando alguien compra el plan - -{{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} - -{% endif %} - -### member - -{% data reusables.webhooks.member_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `members` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.member_webhook_properties %} -{% data reusables.webhooks.member_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.member.added }} - -### membership - -{% data reusables.webhooks.membership_short_desc %} - -#### Disponibilidad - -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `members` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.membership_properties %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.membership.removed }} - -### meta - -Se eliminó el evento para el cual se configuró este webhook. Este evento únicamente escuchará los cambios del gancho particular en el cual se instaló. Por lo tanto, debe seleccionarse para cada gancho para el cual quieras recibir metaeventos. - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| --------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser `deleted`. | -| `hook_id` | `número` | La id del webhook modificado. | -| `gancho` | `objeto` | El webhook modificado. Este contendrá claves diferentes con base en el tipo de webhook que sea: de repositorio, organización, negocio, app, o GitHub Marketplace. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.meta.deleted }} - -### hito - -{% data reusables.webhooks.milestone_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `pull_requests` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.milestone_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.milestone.created }} - -### organización - -{% data reusables.webhooks.organization_short_desc %} - -#### Disponibilidad - -{% if currentVersion != "free-pro-team@latest" %} -- Los webhooks de GitHub Enterprise reciben únicamente eventos de `created` y `deleted`. Para obtener más información, consulta los "[webhooks globales](/v3/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_app %}s con el permiso `members` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre:{% if currentVersion != "free-pro-team@latest" %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, o `member_invited`. | -| `invitación` | `objeto` | La invitación para el usuario o correo electrónico si la acción es `member_invited`. | -| `membership` | `objeto` | La membrecía entre el usuario y la organización. No está presente cuando la cción es `member_invited`. | -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.organization.member_added }} - -{% if currentVersion == "free-pro-team@latest" %} - -### org_block - -{% data reusables.webhooks.org_block_short_desc %} - -#### Disponibilidad - -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `organization_administration` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------------- | ----------- | ----------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser `blocked` o `unblocked`. | -| `blocked_user` | `objeto` | Información acerca del usuario que se bloqueó o desbloqueó. | -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.org_block.blocked }} - -### paquete - -Actividad relacionada con el {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST "[bloquear a usuarios de una organización](/v3/orgs/blocking/)". Para obtener más información, consulta la sección "[Administrar paquetes con el {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" para aprender más sobre el {% data variables.product.prodname_registry %}. - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.package_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.package.published }} -{% endif %} - -### page_build - -{% data reusables.webhooks.page_build_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `pages` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ------------- | -------- | ----------------------------------------------------------------------------------------------------------- | -| `id` | `número` | El idientificador único de la compilación de la página. | -| `compilación` | `objeto` | La misma terminal de [Listar las compilaciones de GitHub Pages](/v3/repos/pages/#list-github-pages-builds). | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.page_build }} - -### ping - -{% data reusables.webhooks.ping_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- Las {% data variables.product.prodname_github_app %}s reciben un evento de ping con un `app_id` que se utiliza para registrar la app - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `zen` | `secuencia` | Secuencia aleatoria de GitHub zen. | -| `hook_id` | `número` | La ID del webhook que activó el ping. | -| `gancho` | `objeto` | La [configuración del webhook](/v3/repos/hooks/#get-a-repository-webhook). | -| `hook[app_id]` | `número` | Cuando registras una {% data variables.product.prodname_github_app %} nueva, {% data variables.product.product_name %} envía un evento de ping a la **URL del webhook** que especificaste durante el registro. El evento contiene la `app_id`, la cual se requiere para [autenticar](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) una app. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.ping }} - -### project_card - -{% data reusables.webhooks.project_card_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- Las {% data variables.product.prodname_github_app %}s con el permiso `repository_projects` o `organization_projects` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.project_card_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.project_card.created }} - -### project_column - -{% data reusables.webhooks.project_column_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- Las {% data variables.product.prodname_github_app %}s con el permiso `repository_projects` o `organization_projects` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.project_column_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.project_column.created }} - -### project - -{% data reusables.webhooks.project_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- Las {% data variables.product.prodname_github_app %}s con el permiso `repository_projects` o `organization_projects` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.project_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.project.created }} - -### public - -{% data reusables.webhooks.public_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `metadata` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ----- | ---- | ----------- | -| | | | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.public }} - -### solicitud_extracción - -{% data reusables.webhooks.pull_request_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `pull_requests` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.pull_request_webhook_properties %} -{% data reusables.webhooks.pull_request_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -Las entregas para los eventos `review_requested` y `review_request_removed` tendrán un campo adicional llamado `requested_reviewer`. - -{{ webhookPayloadsForCurrentVersion.pull_request.opened }} - -### revisión_solicitud de extracción - -{% data reusables.webhooks.pull_request_review_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `pull_requests` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.pull_request_review_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }} - -### comentarios _revisiones_solicitudes de extracción - -{% data reusables.webhooks.pull_request_review_comment_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `pull_requests` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.pull_request_review_comment_webhook_properties %} -{% data reusables.webhooks.pull_request_review_comment_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }} - -### subir - -{% data reusables.webhooks.push_short_desc %} - -{% note %} - -**Nota:** No recibirás un webhook para este evento cuando cargues más de tres etiquetas al mismo tiempo. - -{% endnote %} - -{% tip %} - -**Nota**: El ejemplo de la carga útil del webhook siguiendo la tabla difiere significativamente de la carga útil de la API de Eventos descrita en la misma. Entre otras diferencias, la carga útil del webhook incluye ambos objetos, `sender` y `pusher`. El remitente y cargador son el mismo usuario que inició el evento `push`, pero el objeto `sender` contiene más detalles. - -{% endtip %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `contents` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `secuencia` | Toda la [`git ref`](/v3/git/refs/) que se cargó. Ejemplo: `refs/heads/master`. | -| `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` | `array` | 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](/v3/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[][sha]` | `secuencia` | El SHA 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. | -| `pusher` | `objeto` | El usuario que subió la confirmación. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.push }} - -### lanzamiento - -{% data reusables.webhooks.release_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `contents` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.release_webhook_properties %} -{% data reusables.webhooks.release_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.release.published }} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -### repository_dispatch - -Este evento ocurre cuando una {% data variables.product.prodname_github_app %} envía una solicitud de `POST` a la terminal "[Crear un evento de despacho de repositorio](/v3/repos/#create-a-repository-dispatch-event)". - -#### Disponibilidad - -- Las {% data variables.product.prodname_github_app %}s deben tener el permiso `contents` para recibir este webhook. - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.repository_dispatch }} -{% endif %} - -### repositorio - -{% data reusables.webhooks.repository_short_desc %} - -#### Disponibilidad - -- Los webhooks de repositorio reciben todos los eventos excepto los de `deleted` -- Webhooks de organización -- Las {% data variables.product.prodname_github_app %}s con el permiso `metadata` reciben todos los tipos de evento menos los de `deleted` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------- | ----------- | ---------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Esta puede ser una de las siguientes:
    • `created` - Un repositorio se crea.
    • Un repositorio se borra. Este tipo de evento se encuentra disponible únicamente para los [ganchos de organización](/v3/orgs/hooks/)
    • `archived` - Un repositorio se archiva.
    • `unarchived` - Un repositorio se desarchiva.
      • {% if currentVersion != "free-pro-team@latest" %}
    • `anonymous_access_enabled` - Se [habilita el acceso anónimo de Git](/v3/previews/#anonymous-git-access-to-repositories) para un repositorio, `anonymous_access_disabled` - Se [inhabilita el acceso anónimo de Git](/v3/previews/#anonymous-git-access-to-repositories) para un repositorio
      • {% endif %}
    • `edited` - Se edita la información de un repositorio.
    • `renamed` - Un repositorio se renombra.
    • `transferred` - Un repositorio se transfiere.
    • `publicized` - Un repositorio se hace público.
    • `privatized` - Un repositorio se hace privado.
    | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.repository.publicized }} - -{% if currentVersion == "free-pro-team@latest"%} -### repository_import - -{% data reusables.webhooks.repository_import_short_desc %} Para recibir este evento para un repositorio personal, debes crear un repositorio vacío antes de la importación. Este evento puede activarse utilizando ya sea el [Importador de GitHub](/articles/importing-a-repository-with-github-importer/) o la [API de importaciones fuente](/v3/migrations/source_imports/). - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.repository_import_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.repository_import }} - -### repository_vulnerability_alert - -{% data reusables.webhooks.repository_vulnerability_alert_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.repository_vulnerability_alert_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }} - -{% endif %} - -### security_advisory - -Actividad relacionada con una asesoría de seguridad. Una asesoría de seguridad proporciona información acerca de las vulnerabilidades relacionadas con la seguridad en el software dentro de GitHub. El conjunto de datos de la asesoría de seguridad también impulsa las alertas de seguridad de Github, consulta la sección "[Acerca de las alertas de seguridad para dependencias vulnerables](/articles/about-security-alerts-for-vulnerable-dependencies/)". - -#### Disponibilidad - -- {% data variables.product.prodname_github_app %}s with the `security_events` permission - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. La acción puede ser una de entre `published`, `updated`, o `performed` en el caso de todos los eventos nuevos. | -| `security_advisory` | `objeto` | Los detalles de la asesoría de seguridad, incluyendo el resumen, descripción, y severidad. | - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.security_advisory.published }} - -{% if currentVersion == "free-pro-team@latest" %} -### sponsorship - -{% data reusables.webhooks.sponsorship_short_desc %} - -Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Configurar webhooks para eventos en tu cuenta patrocinada](/github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)". - -#### Disponibilidad - -- Cuentas patrocinadas - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.sponsorship_webhook_properties %} -{% data reusables.webhooks.sponsorship_properties %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil de un webhook cuando alguien crea un patrocinio - -{{ webhookPayloadsForCurrentVersion.sponsorship.created }} - -#### Ejemplo de carga útil de un webhook cuando alguien degrada un patrocinio - -{{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }} - -{% endif %} - -### estrella - -{% data reusables.webhooks.star_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.star_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.star.created }} - -### estado - -{% data reusables.webhooks.status_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `statuses` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `número` | El identificador único del estado. | -| `sha` | `secuencia` | El SHA de la confirmación. | -| `state` | `secuencia` | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`. | -| `descripción` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado. | -| `target_url` | `secuencia` | El enlace opcional agregado al estado. | -| `ramas` | `array` | Un conjunto de objetos de la rama que contiene el SHA del estado. Cada rama contiene el SHA proporcionado, pero éste puede ser o no el encabezado de la rama. El conjunto incluye un máximo de 10 ramas. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.status }} - -### equipo - -{% data reusables.webhooks.team_short_desc %} - -#### Disponibilidad - -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `members` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| ----------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `created`, `deleted`, `edited`, `added_to_repository`, o `removed_from_repository`. | -| `equipo` | `objeto` | El equipo mismo. | -| `changes` | `objeto` | Los cambios al equipo si la acción está como `edited`. | -| `changes[description][from]` | `secuencia` | La versión previa de la descripción si la acción está como `edited`. | -| `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | -| `changes[privacy][from]` | `secuencia` | La versión previa de la privacidad del equipo si ésta se encuentra como `edited`. | -| `changes[repository][permissions][from][admin]` | `boolean` | La versión previa de los permisos de `admin` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | -| `changes[repository][permissions][from][pull]` | `boolean` | La versión previa de los permisos de `pull` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | -| `changes[repository][permissions][from][push]` | `boolean` | La versión previa de los permisos de `push` del miembro del equipo en un repositorio si la acción se encuentra como `edited`. | -| `repositorio` | `objeto` | El repositorio que se agregó o eliminó del alcance del equipo si la acción se encuentra como `added_to_repository`, `removed_from_repository`, o `edited`. Para las acciones que estén como `edited`, el `repository` también contendrá los nuevos niveles de permiso del equipo para dicho repositorio. | -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.team.added_to_repository }} - -### team_add - -{% data reusables.webhooks.team_add_short_desc %} - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `members` - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------- | -------- | -------------------------------------------------------------------------------------------------------------------- | -| `equipo` | `objeto` | El [equipo](/v3/teams/) que se modificó. **Nota:** Los eventos anteriores podrían no incluir esto en la carga útil. | -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.team_add }} - -{% if currentVersion != "free-pro-team@latest" %} - -### usuario - -Cuando se aplica `created` o `deleted` a un usuario. - -#### Disponibilidad -- Webhooks de GitHub Enterprise. Para obtener más información, consulta "[Webhooks globales](/v3/enterprise-admin/global_webhooks/)". - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.user.created }} - -{% endif %} - -### ver - -{% data reusables.webhooks.watch_short_desc %} - -El actor del evento es el [usuario](/v3/users/) que marcó el repositorio con una estrella, y el repositorio del evento es el [repositorio](/v3/repos/) que se marcó con una estrella. - -#### Disponibilidad - -- Webhooks de repositorio -- Webhooks de organización -- {% data variables.product.prodname_github_app %}s con el permiso `metadata` - -#### Objeto de carga útil del webhook - -{% data reusables.webhooks.watch_properties %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.watch.started }} - -{% if currentVersion == "free-pro-team@latest" %} -### workflow_dispatch - -Este evento ocurre cuando alguien activa una ejecución de flujo de trabajo en GitHub o cuando envía una solicitud de tipo `POST` a la terminal [Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)". Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". - -#### Disponibilidad - -- Las {% data variables.product.prodname_github_app %}s deben tener el permiso `contents` para recibir este webhook. - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.workflow_dispatch }} -{% endif %} - - -### workflow_run - -Cuando una ejecución de flujo de trabajo de {% data variables.product.prodname_actions %} se solicita o se completa. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_run)". - -#### Disponibilidad - -- En {% data variables.product.prodname_github_app %}s con los permisos de `actions` o de `contents`. - -#### Objeto de carga útil del webhook - -| Clave | Tipo | Descripción | -| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ | -| `Acción` | `secuencia` | La mayoría de las cargas útiles de webhooks contienen una propiedad de `action` que contiene la actividad específica que activa el evento. | -{% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.repo_desc %} -{% data reusables.webhooks.sender_desc %} - -#### Ejemplo de carga útil del webhook - -{{ webhookPayloadsForCurrentVersion.workflow_run }} diff --git a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/about-merge-methods-on-github.md deleted file mode 100644 index b47945ffaf..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Acerca de los métodos de fusión en GitHub -intro: 'Puedes permitirle a los colaboradores con acceso de escritura a tu repositorio fusionar sus solicitudes de extracción en {% data variables.product.product_location %} con diferentes opciones de fusión o implementar un método de fusión específico para todas las solicitudes de extracción de tu repositorio.' -redirect_from: - - /articles/about-merge-methods-on-github - - /github/administering-a-repository/about-merge-methods-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% 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. - -{% data reusables.pull_requests.default_merge_option %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -El método de fusión predeterminado crea una confirmación de fusión. Puedes impedir que cualquiera suba confirmaciones de fusión en una rama protegida imponiendo un historiar de confirmaciones linear. Para obtener más información, consulta "[Requerir un historial de confirmaciones linear](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} - -### Combinar tus confirmaciones de fusión - -{% data reusables.pull_requests.squash_and_merge_summary %} - -Antes de activar combinar confirmaciones, considera estas desventajas: -- Se pierde información acerca de cuándo se hicieron originalmente los cambios específicos y quién es el autor de las confirmaciones combinadas. -- Si sigues trabajando en la rama principal de una solicitud de extracción después de combinar y fusionar, y luego creas una solicitud de extracción nueva entre las mismas ramas, las confirmaciones que ya hayas combinado y fusionado se listarán en la solicitud de extracción nueva. También podrías tener conflictos que tienes que resolver constantemente en cada solicitud de extracción sucesiva. Para obtener más información, consulta "[Acerca de las fusiones de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)". -- Es posible que sea más difícil usar algunos comandos de Git que usan el ID "SHA" o "hash", ya que se pierde el ID SHA para las confirmaciones originales. Por ejemplo, es posible que no sea tan efectivo usar [`git rerere`](https://git-scm.com/docs/git-rerere). - -Para obtener más información, consulta "[Configurar la combinación de confirmaciones para las solicitudes de extracción](/articles/configuring-commit-squashing-for-pull-requests)". - -### Cambiar de base y fusionar tus confirmaciones - -{% data reusables.pull_requests.rebase_and_merge_summary %} - -Antes de activar cambiar de base las confirmaciones, considera estas desventajas: -- Es posible que los colaboradores del repositorio tengan que cambiar de base en la línea de comandos, resolver cualquier conflicto y realizar un empuje forzado de sus cambios a la rama de tema de la solicitud de extracción (o rama de encabezado remota) antes de poder usar la opción **cambiar de base y fusionar** en {% data variables.product.product_location %}. El empuje forzado se debe realizar cuidadosamente para que los colaboradores no sobreescriban un trabajo en el que otros se hayan basado. Para conocer más sobre cuando la opción **Cambiar de base y fusionar** está desactivada en {% data variables.product.product_location %} y el flujo de trabajo para volver a activarlo, consulta "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)". - -Para obtener más información, consulta [Configurar el cambio de base de las solicitudes de extracción](/articles/configuring-commit-rebasing-for-pull-requests)". diff --git a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md deleted file mode 100644 index c7a8af7f31..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Configurar rebase de confirmación para las solicitudes de extracción -intro: 'Puedes hacer cumplir, permitir o inhabilitar rebases de confirmación para todas las fusiones de las solicitudes de extracción en {% data variables.product.product_location %} en tu repositorio.' -redirect_from: - - /articles/configuring-commit-rebasing-for-pull-requests - - /github/administering-a-repository/configuring-commit-rebasing-for-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% data reusables.pull_requests.configure_pull_request_merges_intro %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En "Merge button" (Fusionar botón), selecciona **Allow rebase merging** (Permitir fusión de rebase). Esto permite que los colaboradores fusionen una solicitud de extracción al rebasar sus confirmaciones individuales en la rama base. Si también seleccionas otro método de fusión, los colaboradores podrán elegir el tipo de confirmación de fusión al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Confirmaciones de rebase de solicitudes de extracción](/assets/images/help/repository/pr-merge-rebase.png) diff --git a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md deleted file mode 100644 index 4f630dd692..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Configurar combinación de confirmaciones para las solicitudes de extracción -intro: 'Puedes hacer cumplir, permitir o inhabilitar combinaciones de confirmación para todas las fusiones de las solicitudes de extracción en {% data variables.product.product_location %} en tu repositorio.' -redirect_from: - - /articles/configuring-commit-squashing-for-pull-requests - - /github/administering-a-repository/configuring-commit-squashing-for-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% data reusables.pull_requests.configure_pull_request_merges_intro %} - -{% data reusables.pull_requests.default-commit-message-squash-merge %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En "Merge button" (Fusionar botón), selecciona **Allow merge commits** (Permitir fusión de confirmaciones). Esto permite que los colaboradores fusionen una solicitud de extracción con un historial completo de confirmaciones. ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png) -4. En "Merge button" (Fusionar botón), selecciona **Allow rebase merging** (Permitir fusión de combinación). Esto permite que los colaboradores fusionen una solicitud de extracción al combinar todas las confirmaciones en una confirmación única. Si seleccionas otro método de fusión además de **Allow squash merging** (Permitir combinación de fusiones), los colaboradores podrán elegir el tipo de confirmación de fusiones al fusionar una solicitud de extracción. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![Confirmaciones combinadas de solicitudes de extracción](/assets/images/help/repository/pr-merge-squash.png) - -### Leer más - -- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" -- "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)" diff --git a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/index.md b/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/index.md deleted file mode 100644 index 141fef72d4..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Configurar fusiones de solicitudes de extracción -intro: 'Puedes configurar las fusiones de las solicitudes de extracción en {% data variables.product.product_location %} para que coincidan con tu flujo de trabajo y preferencias de administración del historial de Git al habilitar, inhabilitar o hacer cumplir las confirmaciones de las fusiones estándar, las confirmaciones combinadas, o las confirmaciones de rebase en todas las solicitudes de extracción de tu repositorio.' -redirect_from: - - /articles/configuring-pull-request-merges -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /about-merge-methods-on-github - - /configuring-commit-squashing-for-pull-requests - - /configuring-commit-rebasing-for-pull-requests - - /managing-auto-merge-for-pull-requests-in-your-repository - - /managing-the-automatic-deletion-of-branches ---- - diff --git a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md b/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md deleted file mode 100644 index f9fc8465fd..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Administrar la eliminación automática de ramas -intro: Puedes hacer que se eliminen automáticamente ramas centrales después de que se fusionen solicitudes de extracción en tu repositorio. -redirect_from: - - /articles/managing-the-automatic-deletion-of-branches - - /github/administering-a-repository/managing-the-automatic-deletion-of-branches -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Cualquier persona con permisos de administrador a un repositorio puede habilitar e inhabilitar la eliminación automática de ramas. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Dentro de "Merge button" (Botón fusionar), selecciona o deselecciona **Automatically delete head branches (Eliminar automáticamente ramas centrales)**. ![Casilla de verificación para habilitar o inhabilitar la eliminación automática de ramas](/assets/images/help/repository/automatically-delete-branches.png) - -### Leer más -- "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)" -- "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-branch-restrictions.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-branch-restrictions.md deleted file mode 100644 index e0c47e9e54..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-branch-restrictions.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Acerca de las restricciones de rama -intro: 'Las ramas dentro de los repositorios que pertenecen a organizaciones pueden ser configuradas para que solo ciertos usuarios{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %},{% else %} o{% endif %} equipos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, o aplicaciones{% endif %} pueden empujar a la rama.' -product: '{% data reusables.gated-features.branch-restrictions %}' -redirect_from: - - /articles/about-branch-restrictions - - /github/administering-a-repository/about-branch-restrictions -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cuando habilitas las restricciones de rama, únicamente los usuarios de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %},{% else %} o los {% endif %} equipos de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, o las palicaciones de {% endif %} a los que se les haya otorgado permiso pueden subir información a la rama protegida. Para obtener más información, consulta "[Habilitar restricciones de rama ](/articles/enabling-branch-restrictions)" y "[Acerca de las ramas protegidas](/articles/about-protected-branches)." Puedes ver y editar los usuarios{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %},{% else %} o{% endif %} los equipos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, o las aplicaciones{% endif %} con acceso a la escritura para una rama protegida en las configuraciones de la rama protegida. - -Solo puedes brindar acceso de escritura para las ramas protegidas a los usuarios{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %},{% else %} o los{% endif %} equipos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, o {% data variables.product.prodname_github_apps %}{% endif %} instalado con acceso de `write` para un repositorio. - -Las personas{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} y las aplicaciones{% endif %} con permisos de administración a un repositorio siempre pueden subir a una rama protegida. - -{% tip %} - -**Nota:** Si seleccionas "Incluir administradores", habrás habilitado la revisión de estado requerida en la rama, y si cualquier revisión de estado falla, entonces cualquier intento de subir cambios a la rama protegida también fallará, incluso para las personas {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}y aplicaciones {% endif %} con permisos de usuario. Para obtener más información, consulta "[Habilitar las verificaciones de estado requeridas](/articles/enabling-required-status-checks)." - -{% endtip %} - -### Leer más - -- "[Acerca de las ramas protegidas](/articles/about-protected-branches)" -- "[Configurar ramas protegidas](/articles/configuring-protected-branches)" -- "[Acerca de las verificaciones de estado requeridas](/articles/about-required-status-checks)" -- "[Activar verificaciones de estado requeridas](/articles/enabling-required-status-checks)" diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md deleted file mode 100644 index 1300a76a22..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Acerca de las ramas protegidas -intro: 'Las ramas protegidas garantizan que los colaboradores en tu repositorio no puedan realizar cambios irrevocables a las ramas. Activar las ramas protegidas también te permite activar otros requisitos y verificaciones opcionales, como las verificaciones de estado requeridas y as revisiones requeridas.' -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/about-protected-branches - - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks - - /articles/about-branch-restrictions - - /github/administering-a-repository/about-branch-restrictions - - /articles/about-required-status-checks - - /github/administering-a-repository/about-required-status-checks - - /articles/types-of-required-status-checks - - /github/administering-a-repository/types-of-required-status-checks - - /articles/about-required-commit-signing - - /github/administering-a-repository/about-required-commit-signing - - /articles/about-required-reviews-for-pull-requests - - /github/administering-a-repository/about-required-reviews-for-pull-requests - - /github/administering-a-repository/about-protected-branches -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% data reusables.pull_requests.about-protected-branches %} Puedes decidir imponer restricciones de cómo se fusionan las solicitudes de extracción en tu repositorio. - -Los propietarios del repositorio y las personas con permisos de administrador para un repositorio pueden implementar ciertos flujos de trabajo o requisitos, antes de que un colaborador pueda fusionar una rama en tu repositorio al crear las reglas de rama protegida. - -{% data reusables.repositories.branch-rules-example %} Para obtener más información, consulta "[Configurar ramas protegidas](/articles/configuring-protected-branches/)". - -### Priorización de las reglas de la rama protegida - -Si un repositorio tiene varias reglas de rama protegida que afectan las mismas ramas, las reglas que incluyen el nombre de una rama específica tienen la mayor prioridad. Si hay más de una regla de rama protegida que hace referencia al mismo nombre de rama específico, entonces la regla de rama creada primera tendrá la prioridad más alta. - -Las reglas de rama protegida que mencionen un caracter especial, como `*`, `?` o `]`, se aplican en el orden que fueron creadas, así que las reglas más antiguas con estos caracteres tienen la prioridad más alta. - -### Parámetros de protección de rama - -Cuando creas una regla de protección de rama en un repositorio, los colaboradores no pueden forzar la subidas de información en ramas protegidas, ni borrar las ramas {% if currentVersion == "free-pro-team@latest" %} predeterminadamente {% endif %}. Puedes habilitar otras configuraciones de protección de rama. Para obtener más información, consulta "[Definir la capacidad de fusión de las solicitudes de extracción](/github/administering-a-repository/defining-the-mergeability-of-pull-requests)." - -### Leer más - -- "[Acerca de las verificaciones de estado requeridas](/articles/about-required-status-checks)" -- "[Acerca de las revisiones requeridas para las solicitudes de extracción](/articles/about-required-reviews-for-pull-requests)" -- "[Acerca de la firma de confirmación requerida](/articles/about-required-commit-signing)" diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-commit-signing.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-commit-signing.md deleted file mode 100644 index 97f03c9bb1..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-commit-signing.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Acerca de la firma de confirmación requerida -intro: La firma de confirmación requerida garantiza que los colaboradores solo puedan subir confirmaciones firmadas verificadas para una rama protegida. -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/about-required-commit-signing - - /github/administering-a-repository/about-required-commit-signing -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Si has implementado protecciones de rama en tu repositorio, puedes configurar la firma de confirmación requerida. Para obtener más información, consulta "[Configurar las ramas protegidas](/articles/configuring-protected-branches/)". - -Cuando habilitas la firma de confirmación requerida en una rama, los contribuyentes {% if currentVersion == "free-pro-team@latest" %} y bots {% endif %} únicamente podrán subir confirmaciones que se hayan firmado y verificado en la rama. Para obtener más información, consulta "[Acerca de la verificación de firmas en las confirmaciones](/articles/about-commit-signature-verification)." - -Siempre puedes subir confirmaciones locales a la rama si estas se firmaron y verificaron. {% if currentVersion == "free-pro-team@latest" %}También puedes fusionar las confirmaciones firmadas y verificadas en la rama utilizando una solicitud de extracción en {% data variables.product.product_name %}. Sin embargo, no puedes combinar y fusionar una solicitud de extracción en la rama en {% data variables.product.product_name %} a menos de que seas el autor de dicha solicitud.{% else %} Sin embargo, no puedes fusionar solicitudes de extracción en la rama en {% data variables.product.product_name %}.{% endif %} Puedes {% if currentVersion == "free-pro-team@latest" %}combinar y {% endif %}fusionar las solicitudes de extracción localmente. Para obtener más información, consulta "[revisar las solicitudes de extracción localmente](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)."{% if currentVersion == "free-pro-team@latest" %} Para obtener más información acerca de los métodos de fusión, consulta "[Acerca de los métodos de fusión en {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %} - -{% note %} - -**Nota:** Activar la firma de confirmación requerida en una rama hará que sea más difícil colaborar con la misma. Si un colaborador sube una confirmación sin firmar a una rama que tiene la firma de confirmación requerida activada, necesitará cambiar de base su confirmación para incluir una firma verificada y realizar un empuje forzado de la confirmación reescrita a la rama. - -{% endnote %} - -Los administradores de un repositorio pueden subir confirmaciones locales que no hayan sido firmadas y verificadas, sin embargo, les puedes solicitar a los administradores que estén sujetos a la firma de confirmación requerida. Para obtener más información, consulta "[Activar la firma de confirmación requerida](/articles/enabling-required-commit-signing)". - -### Leer más - -- "[Acerca de las ramas protegidas](/articles/about-protected-branches)" diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-reviews-for-pull-requests.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-reviews-for-pull-requests.md deleted file mode 100644 index 1f62f26f9c..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-reviews-for-pull-requests.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Acerca de las revisiones requeridas para las solicitudes de extracción -intro: Las revisiones requeridas garantizan que las solicitudes de extracción tengan una cantidad específica de revisiones aprobadas antes de que los colaboradores puedan realizar cambios en una rama protegida. -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/about-required-reviews-for-pull-requests - - /github/administering-a-repository/about-required-reviews-for-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Si has implementado protecciones de rama en tu repositorio, puedes configurar las revisiones requeridas. Para obtener más información acerca de la implementación de las protecciones de rama, consulta "[Configurar ramas protegidas](/articles/configuring-protected-branches/)". Para obtener más información acerca de la configuración de las revisiones requeridas, consulta "[Activar las revisiones requeridas para las solicitudes de extracción](/articles/enabling-required-reviews-for-pull-requests)". - -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -Si una persona con permisos de *administrador* elige la opción **Solicitar cambios** en una revisión, entonces esa persona debe aprobar la solicitud de extracción antes de que se pueda fusionar. Si un revisor que solicita los cambios en una solicitud de extracción no está disponible, cualquiera con permiso de *administrador* o de *escritura* para el repositorio puede descartar la revisión que bloquea la solicitud de extracción. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/articles/dismissing-a-pull-request-review)". - -{% note %} - -**Nota:** Los administradores de repositorio pueden restringir la posibilidad de descartar las revisiones de la solicitud de extracción para personas o equipos específicos. Para obtener más información, consulta "[Activar las revisiones requeridas para las solicitudes de extracción](/articles/enabling-required-reviews-for-pull-requests/)". - -{% endnote %} - -Si subes una confirmación de modificación de código a la rama de una solicitud de extracción aprobada, dicha aprobación podría descartarse si los administradores del repositorio han configurado el descartar las revisiones en espera. Para obtener más información, consulta "[Activar las revisiones requeridas para las solicitudes de extracción](/articles/enabling-required-reviews-for-pull-requests/)". Esto no aplica si subes confirmaciones que no modifiquen el código, como fusionar las ramas base en tu solicitud de extracción de la rama. Para obtener información acerca de las ramas base, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." - -A menos de que se configuren las revisiones requeridas para que incluyan a los administradores del repositorio, las personas con permisos de *administrador* pueden fusionar una solicitud de extracción sin importar las revisiones de otros administradores. - -{% data reusables.repositories.review-policy-overlapping-commits %} - -No puedes fusionar una solicitud de extracción en una rama protegida hasta que alguien con permisos de *escritura* o de *administración* la apruebe. Si hay revisiones pendientes o rechazadas, recibirás un mensaje de error: - -```shell -remote: error: GH006: Protected branch update failed for refs/heads/main. -remote: error: Changes have been requested. -``` diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-status-checks.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-status-checks.md deleted file mode 100644 index 12dc6e7b13..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-required-status-checks.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Acerca de las verificaciones de estado requeridas -intro: Las verificaciones de estado requeridas garantizan que todas las pruebas de integración continua (CI) requeridas sean aprobadas antes de que los colaboradores puedan realizar cambios en una rama protegida. -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/about-required-status-checks - - /github/administering-a-repository/about-required-status-checks -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de las verificaciones de estado requeridas - -Si has implementado protecciones de rama en tu repositorio, puedes configurar las revisiones de estado requeridas. Si has implementado protecciones de rama en tu repositorio, puedes configurar las revisiones de estado requeridas. Para obtener más información, consulta "[Configurar ramas protegidas](/articles/configuring-protected-branches/)" y "[Activar verificaciones de estado requeridas](/articles/enabling-required-status-checks)". Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/github/administering-a-repository/enabling-required-status-checks)". - -Una vez activadas las verificaciones de estado requeridas, todas las verificaciones de estado requeridas deber ser aprobadas antes de que se puedan fusionar las ramas en la rama protegida. Una vez que hayan pasado todas las verificaciones de estado requeridas, cualquier confirmación deberá ya sea subirse en otra rama y después fusionarse, o subirse directo a la rama protegida. - -![Fusionar una rama protegida ](/assets/images/help/repository/req-status-check-all-passed.png) - -{% tip %} - -**Nota:** Cualquier persona o integración con permisos de escritura en un repositorio puede establecer el estado de cualquier comprobación de estado en el repositorio. {% data variables.product.product_name %} no verifica que el autor de una comprobación está autorizado para crear un determinado nombre o modificar un estado existente. Antes de fusionar una solicitud de extracción, deberás verificar que se esté esperando al autor de cada estado, los cuales se encuentran listados en la caja de fusión. - -{% endtip %} - -Los administradores de un repositorio pueden fusionar una rama protegida incluso si las verificaciones de estado requeridas han fallado o están pendientes. Le puedes solicitar a los administradores que estén sujetos a las verificaciones de estado requeridas. Para obtener más información, consulta "[Habilitar las verificaciones de estado requeridas](/github/administering-a-repository/enabling-required-status-checks)." - -![Fusión del administrador de la rama protegida](/assets/images/help/repository/req-status-check-admin-merge.png) - -Los administradores también pueden fusionar una rama protegida incluso si la rama está desactualizada con la rama base. - -### Configuración de las verificaciones de estado requeridas - -Puedes configurar las verificaciones para que sean laxas o estrictas, dependiendo de lo que quieras que tu rama tenga actualizado con respecto a la rama base antes de la fusión. Para obtener más información, consulta "[Tipos de verificación de estado requerido](/github/administering-a-repository/types-of-required-status-checks)." - -### Solución de problemas para verificaciones de estado requeridas - -Si tienes una revisión y un estado con el mismo nombre y seleccionas el nombre como una verificación de estado requerida, tanto la revisión como el estado se requerirán. Para obtener más información, consulta las "[Verificaciones](/v3/checks/)". - -Una vez que has configurado las verificaciones de estado requeridas, tu rama debe estar actualizada con la rama base antes de fusionarse. Esto garantiza que tu rama ha sido probada con el último código desde la rama base. Si tu rama no está actualizada, necesitarás fusionar la rama base en tu rama. - -{% note %} - -**Nota:** También puedes actualizar tu rama con la rama base utilizando Git rebase. Para obtener más información, consulta [Accerca del rebase de Git](/github/using-git/about-git-rebase)." - -{% endnote %} - -![Rama desactualizada](/assets/images/help/repository/req-status-check-out-of-date.png) - -No podrás subir cambios locales a una rama protegida hasta que se hayan aprobado todas las verificaciones de estado requeridas. En su lugar, recibirás un mensaje de error similar al siguiente: - -```shell -remote: error: GH006: Protected branch update failed for refs/heads/main. -remote: error: Required status check "ci-build" is failing -``` -{% note %} - -**Nota:** Las solicitudes de extracción que están actualizadas y aprobaron las verificaciones de estado requeridas pueden ser fusionadas localmente y subidas a la rama protegida. Esto se puede hacer sin las verificaciones de estado ejecutándose en la propia confirmación de fusión. - -{% endnote %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} - -Algunas veces, los resultados de las verificaciones de estado para la confirmación de la prueba de fusión y de la confirmación principal entrarán en conflicto. Si la confirmación de la prueba de fusion tiene un estado, deberá pasar. De otra manera, el estado de la confirmación principal deberá pasar antes de que puedas fusionar la rama. Para obtener más información acerca de cómo hacer una prueba de fusión de las confirmaciones, consulta la sección "[Solicitudes de extracción](/v3/pulls/#response-1)." - -![Ramas con conflictos en las confirmaciones de fusión](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) -{% endif %} - -### Leer más - -- "[Acerca de las verificaciones de estado](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/configuring-protected-branches.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/configuring-protected-branches.md deleted file mode 100644 index a516149c00..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/configuring-protected-branches.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Configurar ramas protegidas -intro: 'Si eres un propietario de repositorio o si tienes permisos de administrador en un repositorio, puedes personalizar las protecciones de la rama en el repositorio y exige determinados flujos de trabajo, como requerir más de una revisión de solicitud de extracción o solicitar la aprobación de determinadas comprobaciones de estado antes de permitir la fusión de una solicitud de extracción.' -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/configuring-protected-branches - - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks - - /github/administering-a-repository/configuring-protected-branches -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.repositories.branch-rules-example %} - -También puedes configurar una protección de rama automática para todas las ramas en tu repositorio con la sintaxis de comodín `*`. Ya que {% data variables.product.prodname_dotcom %} utiliza el indicador `File::FNM_PATHNAME` para la sintaxis `File.fnmatch` el comodín no empata con los separadores de directorio (`/`). Por ejemplo, `qa/*` empatará con todas las ramas que comiencen con `qa/` y contengan una sola diagonal. Puedes incluir múltiples barras oblicuas con `qa/**/a`, y puedes extender la cadena `qa` con `qa**/**/*` para que sea más inclusivo. Para más información sobre las opciones de sintaxis para las reglas de la rama, consulta la [documentación fnmatch](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). - -Para crear una excepción a una regla de rama existente, puedes crear una nueva regla de protección de rama que sea una prioridad superior, como una regla de rama para un nombre de rama específico. Para obtener más información acerca del orden de prioridad y otras configuraciones para las reglas de ramas protegidas, consulta "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)." - -{% note %} - -**Nota:** Para crear una regla de rama, la rama que especifiques no debe existir en el repositorio. - -{% endnote %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.repository-branches %} -{% data reusables.repositories.add-branch-protection-rules %} -6. Opcionalmente, puedes configurar los parámetros de regla de rama específicos. ![Parámetros de regla de rama protegida](/assets/images/help/branches/branch-rule-settings.png) -7. Para confirmar la regla de protección de la rama, haz clic en **Create** (Crear) o **Save changes** (Guardar cambios). - -### Leer más - -- "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" -- "[Acerca de las verificaciones de estado requeridas](/github/administering-a-repository/about-required-status-checks)" -- "[Activar verificaciones de estado requeridas](/github/administering-a-repository/enabling-required-status-checks)" -- "[Acerca de las restricciones de rama](/github/administering-a-repository/about-branch-restrictions)" -- "[Habilitar restricciones de rama](/github/administering-a-repository/enabling-branch-restrictions)" -- "[Acerca de la firma de confirmación requerida](/github/administering-a-repository/about-required-commit-signing)" diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-branch-restrictions.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-branch-restrictions.md deleted file mode 100644 index d2628392a2..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-branch-restrictions.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Habilitar restricciones de rama -intro: 'Puedes imponer restricciones de rama para que solo ciertos usuarios {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %},{% else %} o{% endif %} equipos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, o aplicaciones{% endif %} puedan subir información a las ramas protegidas en los repositorios que sean propiedad de tu organización.' -product: '{% data reusables.gated-features.branch-restrictions %}' -redirect_from: - - /articles/enabling-branch-restrictions - - /github/administering-a-repository/enabling-branch-restrictions -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cualquiera que tenga permisos de administrador en un repositorio que pertenezca a una organización puede habilitar las restricciones de rama. - -{% data reusables.repositories.protected-branches-options %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.repository-branches %} -{% data reusables.repositories.add-branch-protection-rules %} -{% data reusables.repositories.include-administrators %} -6. Selecciona **Restringir quién puede subir información a las ramas correspondientes** bajo "Proteger las ramas correspondientes". ![Casilla de verificación para restricción de rama](/assets/images/help/repository/restrict-branch.png) -8. Busca y selecciona a las personas {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %},{% else %} o{% endif %} equipos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, o aplicaciones{% endif %} que tendrán permiso de subir información a la rama protegida. ![Búsqueda de restricciones de rama](/assets/images/help/repository/restrict-branch-search.png) -9. Haz clic en **Create** (crear). - -### Leer más - -- "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" -- "[Configurar ramas protegidas](/github/administering-a-repository/configuring-protected-branches)" -- "[Acerca de las verificaciones de estado requeridas](/github/administering-a-repository/about-required-status-checks)" -- "[Activar verificaciones de estado requeridas](/github/administering-a-repository/enabling-required-status-checks)" diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-deletion-of-a-protected-branch.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-deletion-of-a-protected-branch.md deleted file mode 100644 index 9638436dcb..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-deletion-of-a-protected-branch.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Habilitar la eliminación de una rama protegida -intro: Puedes permitir que cualquiera que tenga acceso de escritura para un repositorio borre una rama protegida. -product: '{% data reusables.gated-features.protected-branches %}' -versions: - free-pro-team: '*' - enterprise-server: '>=2.20' -redirect_from: - - /github/administering-a-repository/enabling-deletion-of-a-protected-branch ---- -Cualquiera con permisos de administrador para un repositorio puede habilitar eliminaciones de ramas. - -Por defecto, no puedes eliminar una rama protegida. Cuando habilitas la eliminación a una rama protegida, cualquiera con al menos permisos de escritura en el repositorio puede eliminar la rama incluyendo aquellos con permisos de administración. - -{% data reusables.repositories.protected-branches-options %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.repository-branches %} -{% data reusables.repositories.add-branch-protection-rules %} -6. En la sección "Reglas aplicadas a todos, incluidos los administradores", selecciona **Allow deletions**. ![Opción para habilitar las eliminaciones de ramas](/assets/images/help/repository/allow-branch-deletions.png) -7. Haz clic en **Create** (crear). diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-force-pushes-to-a-protected-branch.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-force-pushes-to-a-protected-branch.md deleted file mode 100644 index 6a53eda79e..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-force-pushes-to-a-protected-branch.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Enabling force pushes to a protected branch -intro: You can allow force pushes to a protected branch. -product: '{% data reusables.gated-features.protected-branches %}' -versions: - free-pro-team: '*' - enterprise-server: '>=2.20' -redirect_from: - - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch ---- -Anyone with admin permissions to a repository can enable force pushes. - -### About force pushes to protected branches - -By default, force pushes are blocked on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. - -Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch. - -{% if currentVersion != "free-pro-team@latest" %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a user account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." - -If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %} - -{% data reusables.repositories.protected-branches-options %} - -### Enabling force pushes - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.repository-branches %} -{% data reusables.repositories.add-branch-protection-rules %} -6. Under "Rules applied to everyone including administrators", select **Allow force pushes**. -![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png) -7. Click **Create**. diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-commit-signing.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-commit-signing.md deleted file mode 100644 index 71e284bdbe..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-commit-signing.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Habilitar la firma de confirmación requerida -intro: Los administradores de repositorios pueden implementar la firma de confirmación requerida en una rama para bloquear todas las confirmaciones que no estén firmadas y verificadas. -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/enabling-required-commit-signing - - /github/administering-a-repository/enabling-required-commit-signing -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Antes de habilitar la firma de confirmación requerida en una rama, debes configurar primero la rama como rama protegida. Para obtener más información, consulta "[Configurar ramas protegidas](/github/administering-a-repository/configuring-protected-branches)". - -{% data reusables.repositories.protected-branches-options %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.repository-branches %} -{% data reusables.repositories.add-branch-protection-rules %} -5. Selecciona **Requerir confirmaciones firmadas**. ![Opción Requerir confirmaciones firmadas](/assets/images/help/repository/require-signed-commits.png) -6. También puedes seleccionar **Incluir administradores**. Esto exige las confirmaciones firmadas requeridas en el repositorio. ![Casilla de verificación Incluir administradores](/assets/images/help/repository/include-admins-protected-branches.png) -7. Haz clic en **Create** (crear). diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-reviews-for-pull-requests.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-reviews-for-pull-requests.md deleted file mode 100644 index 9e6862dea7..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-reviews-for-pull-requests.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Habilitar revisiones requeridas para las solicitudes de extracción -intro: Los administradores del repositorio pueden exigir revisiones requeridas para que las solicitudes de extracción tengan un número específico de revisiones para su aprobación antes de la fusión. -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/enabling-required-reviews-for-pull-requests - - /github/administering-a-repository/enabling-required-reviews-for-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Antes de habilitar las revisiones requeridas en una rama, debes configurar primero la rama como rama protegida. Para obtener más información, consulta "[Configurar ramas protegidas](/github/administering-a-repository/configuring-protected-branches)". - -{% data reusables.repositories.protected-branches-options %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.repository-branches %} -{% data reusables.repositories.add-branch-protection-rules %} -5. Selecciona **Requerir revisiones de solicitudes de extracción antes de la fusión**. ![Casilla de verificación Restricción de revisión de solicitud de extracción](/assets/images/help/repository/PR-reviews-required.png) -6. En el menú desplegable de revisiones para la aprobación, selecciona el número de revisiones para la aprobación que deseas en esa rama. ![Menú desplegable para seleccionar el número de aprobaciones de revisión requeridas](/assets/images/help/repository/number-of-required-review-approvals.png) -7. También puedes **Descartar aprobaciones de solicitudes de extracción en espera cuando se suben nuevas confirmaciones**. Esto descarta la revisión de aprobación de una solicitud de extracción cuando una confirmación que modifica el código se sube a la rama. ![Casilla de verificación Descartar aprobaciones de solicitudes de extracción en espera cuando se suben nuevas confirmaciones](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) -8. También puedes seleccionar **Requerir revisión de los propietarios del código** para requerir la revisión por parte de un propietario del código cuando la solicitud de extracción afecta el código que tiene un propietario designado. Para obtener más información, consulta "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Requerir revisión de los propietarios del código](/assets/images/help/repository/PR-review-required-code-owner.png) -9. Si el repositorio es parte de una organización, también puedes seleccionar **Restringir quién puede descartar revisiones de solicitud de extracción** para buscar y seleccionar las personas o los equipos que pueden descartar revisiones de solicitudes de extracción. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review)". esta opción no se encuentra disponible para repositorios personales. ![Restringir quién puede descartar la casilla de verificación de revisiones de solicitudes de extracción](/assets/images/help/repository/PR-review-required-dismissals.png) -{% data reusables.repositories.include-administrators %} -11. Haz clic en **Create** (crear). - -### Leer más - -- "[Acerca de las revisiones requeridas para las solicitudes de extracción](/github/administering-a-repository/about-required-reviews-for-pull-requests)" -- "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" -- "[Acerca de las verificaciones de estado requeridas](/github/administering-a-repository/about-required-status-checks)" diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-status-checks.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-status-checks.md deleted file mode 100644 index f3ea3e331c..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/enabling-required-status-checks.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Habilitar verificaciones de estado requeridas -intro: Los administradores de repositorios pueden exigir verificaciones de estado requeridas antes de que una rama se fusione con una solicitud de extracción o antes de que las confirmaciones en una rama local puedan subirse a la rama remota protegida. -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/enabling-required-status-checks - - /github/administering-a-repository/enabling-required-status-checks -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.repositories.protected-branches-options %} - -Antes de que puedas habilitar las verificaciones de estado requeridas, debes configurar el repositorio para utilizar la API de estado. Para obtener más información, consulta la sección "[Construir un servidor de IC](/guides/building-a-ci-server/)". - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.repository-branches %} -{% data reusables.repositories.add-branch-protection-rules %} -6. Selecciona **Requerir verificaciones de estado para pasar antes de fusionar** debajo de "Proteger ramas correspondientes". ![Opción Verificaciones de estado requeridas](/assets/images/help/repository/required-status-checks.png) -7. Opcionalmente, selecciona **requerir que las ramas estén actualizadas antes de fusionar**. Al seleccionar esta opción, te aseguras de que la rama se pruebe con el código más reciente en la rama base. ![Casilla de verificación de estado estricta o poco estricta](/assets/images/help/repository/protecting-branch-loose-status.png) -7. Selecciona las verificaciones que quieres requerir de la lista de verificaciones de estado disponibles. ![Lista de verificaciones de estado disponibles](/assets/images/help/repository/required-statuses-list.png) -{% data reusables.repositories.include-administrators %} -9. Haz clic en **Create** (crear). - -{% data reusables.repositories.required-status-merge-tip %} diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/index.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/index.md deleted file mode 100644 index e0c1049be8..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Definir la capacidad de fusión de las solicitudes de extracción -intro: 'Puedes requerir que las solicitudes de extracción superen un conjunto de verificaciones antes de que se las pueda fusionar. Por ejemplo, puedes bloquear las solicitudes de extracción que no superan las verificaciones de estado o puedes requerir que las solicitudes de extracción tengan un número específico de revisiones aprobadas antes de que las pueda fusionar.' -redirect_from: - - /articles/defining-the-mergeability-of-a-pull-request/ - - /articles/defining-the-mergeability-of-pull-requests - - /enterprise/admin/developer-workflow/establishing-pull-request-merge-conditions -product: '{% data reusables.gated-features.protected-branches %}' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /about-protected-branches - - /managing-a-branch-protection-rule - - /troubleshooting-required-status-checks ---- - diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/requiring-a-linear-commit-history.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/requiring-a-linear-commit-history.md deleted file mode 100644 index 8e30d61a36..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/requiring-a-linear-commit-history.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Requerir un historial de confirmaciones linear -intro: Puedes requerir un historial de confirmaciones linear para bloquear todas las confirmaciones de fusión en una rama protegida. -product: '{% data reusables.gated-features.protected-branches %}' -versions: - free-pro-team: '*' - enterprise-server: '>=2.20' -redirect_from: - - /github/administering-a-repository/requiring-a-linear-commit-history ---- -Cualquiera con permisos de administrador para un repositorio puede requerir un historial de confirmaciones lineal. - -### Acerca de imponer un historial de confirmaciones linear - -Imponer un historial de confirmaciones linear previene que las confirmaciones de fusión se suban a la rama protegida. Esto significa que cualquier solicitud de extracción fusionada con la rama protegida deberá utilizar una fusión combinada o una fusión de rebase. Un historial de confirmaciones estrictamente linear puede ayudar a que los equipos retrocedan los cambios de manera más eficiente. Para obtener más información acerca de los métodos de fusión, consulta "[Acerca de la fusión de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)." - -{% data reusables.repositories.protected-branches-options %} - -Antes de poder requerir un historial de confirmaciones linear, tu repositorio deberá permitir fusiones combinadas o fusiones de rebase. Para obtener más información, consulta "[Configurar las fusiones de solicitud de extracción](/github/administering-a-repository/configuring-pull-request-merges)." - - -### Implementar un historial de commit lineal - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.repository-branches %} -{% data reusables.repositories.add-branch-protection-rules %} -6. Debajo de "Proteger ramas correspondientes", selecciona **Requerir historial linear**. ![Opción para requerir historial linear](/assets/images/help/repository/required-linear-history.png) -{% data reusables.repositories.include-administrators %} -7. Haz clic en **Create** (crear). diff --git a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/types-of-required-status-checks.md b/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/types-of-required-status-checks.md deleted file mode 100644 index bc2f65f7fb..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/defining-the-mergeability-of-pull-requests/types-of-required-status-checks.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Tipos de verificaciones de estado requeridas -intro: Puedes configurar las verificaciones de estado requeridas para que sean "laxas" o "estrictas". El tipo de verificación de estado requerida que elijas determina si se requiere que tu rama esté actualizada con la rama base antes de la fusión. -product: '{% data reusables.gated-features.protected-branches %}' -redirect_from: - - /articles/types-of-required-status-checks - - /github/administering-a-repository/types-of-required-status-checks -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -| Tipo de verificación de estado requerida | Parámetro | Requisitos de fusión | Consideraciones | -| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Estricta** | La casilla **Require branches to be up-to-date before merging** (Las ramas deben estar actualizadas antes de la fusión) está marcada. | La rama **debe** estar actualizada con la rama de base antes de la fusión. | Este es el comportamiento predeterminado para las verificaciones de estado requeridas. Se pueden requerir más construcciones, ya que deberás actualizar la rama de encabezado después de que otros colaboradores fusionen las solicitudes de extracción con la rama de base protegida. | -| **Flexible** | La casilla **Require branches to be up-to-date before merging** (Las ramas deben estar actualizadas antes de la fusión) **no** está marcada. | La rama **no debe** estar actualizada con la rama de base antes de la fusión. | Tendrás menos construcciones requeridas, ya que no necesitarás actualizar la rama de encabezado después de que otros colaboradores fusionen las solicitudes de extracción. Las verificaciones de estado pueden fallar después de que fusiones tu rama si hay cambios incompatibles con la rama de base. | -| **Inhabilitada** | La casilla **Require status checks to pass before merging** (Se deben superar las verificaciones de estado antes de la fusión) **no** está marcada. | La rama no tiene restricciones de fusión. | Si las verificaciones de estado requeridas no están habilitadas, los colaboradores pueden fusionar la rama en cualquier momento, independientemente de si está actualizada con la rama de base. Esto aumenta la posibilidad de cambios incompatibles. | - -### Leer más - -- "[Acerca de las verificaciones de estado requeridas](/articles/about-required-status-checks)" -- "[Activar verificaciones de estado requeridas](/articles/enabling-required-status-checks)" diff --git a/translations/es-XL/content/github/administering-a-repository/index.md b/translations/es-XL/content/github/administering-a-repository/index.md deleted file mode 100644 index dd4c08d4b0..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/index.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Administrar un repositorio -redirect_from: - - /categories/administering-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /managing-repository-settings - - /managing-branches-in-your-repository - - /configuring-pull-request-merges - - /defining-the-mergeability-of-pull-requests - - /releasing-projects-on-github - - /finding-information-in-a-repository ---- -### Índice - {% if currentVersion == "free-pro-team@latest" %} - {% endif %} - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/about-github-dependabot-version-updates.md b/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/about-github-dependabot-version-updates.md deleted file mode 100644 index 4b037608b2..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/about-github-dependabot-version-updates.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Acerca de las actualizaciones de versión del Dependabot de GitHub -intro: 'Puede utilizar el {% data variables.product.prodname_dependabot %} para mantener los paquetes que utilizas actualizados a su versión más reciente.' -redirect_from: - - /github/administering-a-repository/about-github-dependabot - - /github/administering-a-repository/about-github-dependabot-version-updates -versions: - free-pro-team: '*' ---- -{% data reusables.dependabot.beta-note %} - -### Acerca de {% data variables.product.prodname_dependabot_version_updates %} - -El {% data variables.product.prodname_dependabot %} hace el esfuerzo de mantener tus dependencias. Puedes utilizarlo para garantizar que tu repositorio se mantenga automáticamente con los últimos lanzamientos de los paquetes y aplicaciones de los que depende. - -Puedes habilitar {% data variables.product.prodname_dependabot_version_updates %} si seleccionas el archivo de configuración en tu repositorio. El archivo de configuración especifica la ubicación del manifiesto, u otros archivos de definición de paquetes, almacenado en tu repositorio. El {% data variables.product.prodname_dependabot_short %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot_short %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Cuando el {% data variables.product.prodname_dependabot_short %} identifica una dependencia desactualizada, levanta una solicitud de extracción para actualizar el manifiesto a su última versión de la dependencia. Verificas que tu prueba pase, revisas el registro de cambios y notas de lanzamiento que se incluyan en el resumen de la solicitud de extracción y, posteriormente, lo fusionas. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". - -Si habilitas las actualizaciones de seguridad, el {% data variables.product.prodname_dependabot %} también levantará las solicitudes de extracción para actualizar las dependencias vulnerables. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)". - -{% data reusables.dependabot.dependabot-tos %} - -### Frecuencia de las solicitudes de extracción del {% data variables.product.prodname_dependabot %} - -Tú eres quien especifica qué tan a menudo se revisa cada ecosistema para encontrar nuevas versiones en el archivo de configuración: diario, semanalmente, o mensualmente. - -{% data reusables.dependabot.initial-updates %} - -Si habilitaste las actualizaciones de seguridad, algunas veces verás solicitudes de extracción adicionales para actualizaciones de seguridad. Esto se activa con una alerta del {% data variables.product.prodname_dependabot_short %} para una dependencia en tu rama predeterminada. El {% data variables.product.prodname_dependabot %} levanta automáticamente una solicitud de extracción para actualizar la dependencia vulnerable. - -### Repositorios y ecosistemas compatibles - -{% note %} - -{% data reusables.dependabot.private-dependencies %} - -{% endnote %} - -Puedes configurar las actualizaciones de versión para los repositorios que contengan un manifiesto de dependencias o un archivo fijado para alguno de los administradores de paquetes compatibles. - -{% data reusables.dependabot.supported-package-managers %} - -Si tu repositorio ya utiliza una integración para la administración de dependencias, necesitarás inhabilitarlo antes de habilitar el {% data variables.product.prodname_dependabot %}. Para obtener más información, consulta la sección "[Acerca de las integraciones](/github/customizing-your-github-workflow/about-integrations)". diff --git a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md deleted file mode 100644 index ee79f8e130..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md +++ /dev/null @@ -1,593 +0,0 @@ ---- -title: Opciones de configuración para actualizaciones de dependencias -intro: 'La información detallada para todas las opciones que puedes utilizar para personalizar como el {% data variables.product.prodname_dependabot %} mantiene tus repositorios.' -permissions: 'Las personas con permisos de escritura en un repositorio pueden configurar {% data variables.product.prodname_dependabot %} para el mismo.' -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/configuration-options-for-dependency-updates ---- -{% data reusables.dependabot.beta-note %} - -### Acerca del archivo *dependabot.yml* - -El archivo de configuración del {% data variables.product.prodname_dependabot %}, *dependabot.yml*, utiliza la sintaxis YAML. Si eres nuevo en YAML y deseas conocer más, consulta "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". - -Debes almacenar este archivo en el directorio `.github` de tu repositorio. Cuando agregas o actualizas el archivo *dependabot.yml*, esto activa una revisión inmediata de las actualizaciones de la versión. Cualquier opción que también afecte a las actualizaciones de seguridad se utilizará en la siguiente ocasión que una alerta de seguridad active una solicitud de extracción para una alerta de seguridad. Para obtener más información, consulta las secciónes "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)" y "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)". - -### Opciones de configuración para *dependabot.yml* - -El archivo *dependabot.yml* debe comenzar con `version: 2`, seguido de un conjunto de `updates`. - -| Opción | Requerido | Descripción | -|:-------------------------------------------------------------------------- |:---------:|:--------------------------------------------------------------------------------------------- | -| [`package-ecosystem`](#package-ecosystem) | **X** | Administrador de paquetes a utilizar | -| [`directorio`](#directory) | **X** | Ubicación de los manifiestos del paquete | -| [`schedule.interval`](#scheduleinterval) | **X** | Qué tan a menudo se revisará si hay actualizaciones | -| [`allow`](#allow) | | Personalizar qué actualizaciones se permitirán | -| [`asignatarios`](#assignees) | | Los asignados a configurar en las solicitudes de extracción | -| [`commit-message`](#commit-message) | | Preferencias de mensaje de confirmación | -| [`ignore`](#ignore) | | Ignorar ciertas dependencias o versiones | -| [`etiquetas`](#labels) | | Las etiquetas a configurar en las solicitudes de extracción | -| [`hito`](#milestone) | | Hito a configurar en las solicitudes de extracción | -| [`open-pull-requests-limit`](#open-pull-requests-limit) | | Limitar la cantidad de solicitudes de extracción abiertas para las actualizaciones de versión | -| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) | | Cambiar el separador para los nombres de rama de la solicitud de extracción | -| [`rebase-strategy`](#rebase-strategy) | | Inhabilitar el rebase automático | -| [`reviewers`](#reviewers) | | Los revisores a configurar en las solicitudes de extracción | -| [`schedule.day`](#scheduleday) | | Día de la semana para revisar si hay actualizaciones | -| [`schedule.time`](#scheduletime) | | Hora del día para revisar si hay actualizaciones (hh:mm) | -| [`schedule.timezone`](#scheduletimezone) | | Huso horario para la hora del día (identificador de zona) | -| [`target-branch`](#target-branch) | | Rama contra la cual se creará la solicitud de extracción | -| [`versioning-strategy`](#versioning-strategy) | | Cómo actualizar los requisitos de la versión del manifiesto | - -Estas opciones caen a groso modo en las siguientes categorías. - -- Opciones de configuración esenciales que debes incluir en todas las configuraciones: [`package-ecosystem`](#package-ecosystem), [`directory`](#directory),[`schedule.interval`](#scheduleinterval). -- Opciones para personalizar el calendario de actualización: [`schedule.time`](#scheduletime), [`schedule.timezone`](#scheduletimezone), [`schedule.day`](#scheduleday). -- Opciones para controlar qué dependencias se actualizan: [`allow`](#allow), [`ignore`](#ignore). -- Opciones para agregar metadatos a las solicitudes de extracción: [`reviewers`](#reviewers), [`assignees`](#assignees), [`labels`](#labels), [`milestone`](#milestone). -- Opciones para cambiar el comportamiento de las solicitudes de extracción: [`target-branch`](#target-branch), [`versioning-strategy`](#versioning-strategy), [`commit-message`](#commit-message), [`rebase-strategy`](#rebase-strategy), [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator). - -Adicionalmente, la opción [`open-pull-requests-limit`](#open-pull-requests-limit) cambia la cantidad máxima de solicitudes de extracción para las actualizaciones de versión que puede abrir el {% data variables.product.prodname_dependabot %}. - -{% note %} - -**Nota:** Algunas de estas opciones de configuración también pueden afectar a las solicitudes de extracción que se levantan para las actualizaciones de seguridad de los manifiestos delos paquetes vulnerables. - -Las actualizaciones de seguridad se levantan para los manifiestos de paquetes vulnerables únicamente en la rama predeterminada. Cuando se establecen las opciones de configuración para la misma rama (como "true" a menos de que utilices `target-branch`), y se especifica un `package-ecosystem` y `directory` para el manifiesto vulnerable, entonces las solicitudes de extracción para las actualizaciones de seguridad utilizan las opciones relevantes. - -En general, las actualizaciones de seguridad utilizan cualquier opción de configuración que afecte las solicitudes de extracción, por ejemplo, agregar metadatos o cambiar su comportamiento. Para obtener más información acerca de las actualizaciones de seguridad, consulta la sección "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)". - -{% endnote %} - -### `package-ecosystem` - -**Requerido** Agregas un elemento de `package-ecosystem` para cada administrador de paquetes que quieras que el {% data variables.product.prodname_dependabot %} monitoree para revisar si hay nuevas versiones. El repositorio también debe contener un manifiesto de dependencia o archivo fijado de estos administradores de paquete. - -{% data reusables.dependabot.supported-package-managers %} - -```yaml -# Basic set up for three package managers - -version: 2 -updates: - - # Maintain dependencies for GitHub Actions - - package-ecosystem: "github-actions" - directory: "/" - schedule: - interval: "daily" - - # Maintain dependencies for npm - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - - # Maintain dependencies for Composer - - package-ecosystem: "composer" - directory: "/" - schedule: - interval: "daily" -``` - -### `directorio` - -**Requerido** Debes definir la ubicación de los manifiestos de paquete para cada administrador de paquete (por ejemplo, el *package.json* o *Gemfile*). Tú definierás el directorio relativo a la raíz del repositorio para todos los ecosistemas, menos para GitHub Actions. Para GitHub Actions, configura el directorio para que sea `/` y así revisar los archivos de flujo de trabajo en `.github/workflows`. - -```yaml -# Specify location of manifest files for each package manager - -version: 2 -updates: - - package-ecosystem: "composer" - # Files stored in repository root - directory: "/" - schedule: - interval: "daily" - - - package-ecosystem: "npm" - # Files stored in `app` directory - directory: "/app" - schedule: - interval: "daily" - - - package-ecosystem: "github-actions" - # Workflow files stored in the - # default location of `.github/workflows` - directory: "/" - schedule: - interval: "daily" -``` - -### `schedule.interval` - -**Requerido** Debes definir qué tan a menudo se debe revisar si hay nuevas versiones y levantar solicitudes de extracción para las actualizaciones de versión en cada administrador de paquetes. Predeterminadamente, esto ocurre a las 5am UTC. Para modificar esto, utiliza [`schedule.time`](#scheduletime) and [`schedule.timezone`](#scheduletimezone). - -- `daily`—se ejecuta en cada día de la semana, de Lunes a Viernes. -- `weekly`—se ejecuta una vez cada semana. Predeterminadamente, esto ocurre los lunes. Para modificar esto, utiliza [`schedule.day`](#scheduleday). -- `monthly`—se ejecuta una vez al mes. Esto ocurre en el primer día de cada mes. - -```yaml -# Set update schedule for each package manager - -version: 2 -updates: - - - package-ecosystem: "github-actions" - directory: "/" - schedule: - # Check for updates to GitHub Actions every weekday - interval: "daily" - - - package-ecosystem: "composer" - directory: "/" - schedule: - # Check for updates managed by Composer once a week - interval: "weekly" -``` - -### `allow` - -{% data reusables.dependabot.default-dependencies-allow-ignore %} - -Utiliza la opción `allow` para personalizar qué dependencias se actualizan. Esto no impacta en las actualizaciones de seguridad para las dependencias vulnerables. Puedes utilizar las siguientes opciones: - -- `dependency-name`—se utiliza para permitir actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId`, por ejemplo: `org.kohsuke:github-api`. -- `dependency-type`—utilízalo para permitir actualizaciones para dependencias de tipos específicos. - - | Tipos de dependencia | Administradores de paquete compatibles | Permitir actualizaciones | - | -------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | - | `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). | - | `todos` | 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` | Únicamente las dependencias en el "Grupo de dependencias del producto". | - | `development` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Únicamente las dependencias en el "Grupo de dependencias de desarrollo". | - -```yaml -# Customizing the dependencies to maintain with `allow` - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - allow: - # Allow updates for Lodash - - dependency-name: "lodash" - # Allow updates for React and any packages starting "react" - - dependency-name: "react*" - - - package-ecosystem: "composer" - directory: "/" - schedule: - interval: "daily" - allow: - # Allow both direct and indirect updates for all packages - - dependency-type: "all" - - - package-ecosystem: "pip" - directory: "/" - schedule: - interval: "daily" - allow: - # Allow only direct updates for - # Django and any packages starting "django" - - dependency-name: "django*" - dependency-type: "direct" - # Allow only production updates for Sphinx - - dependency-name: "sphinx" - dependency-type: "production" -``` - -### `asignatarios` - -Utiliza `assignees` para especificar a los asignados individuales para todas las solicitudes de extracción levantadas para un administrador de paquete. - -{% data reusables.dependabot.option-affects-security-updates %} - -```yaml -# Specify assignees for pull requests - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Add assignees - assignees: - - "octocat" -``` - -### `commit-message` - -Predeterminadamente, el {% data variables.product.prodname_dependabot %} intenta detectar tus preferencias de mensajes de confirmación y utiliza patrones similares. Utiliza la opción`commit-message` para especificar tus preferencias explícitamente. - -Opciones compatibles - -- `prefix` especifica un prefijo para todos los mensajes de confirmación. -- `prefix-development` especifica un prefijo separado para todos los mensajes de confirmación que actualizan dependencias en el grupo de dependencias de desarrollo. Cuando especificas un valor para esta opción, `prefix` se utiliza únicamente para las actualizaciones a las dependencias en el grupo de dependencias de producción. Esto es compatible con: `bundler`, `composer`, `mix`, `maven`, `npm`, y `pip`. -- `include: "scope"` especifica que cualquier prefijo es sucedido por una lista de dependencias actualizadas en la confirmación. - -{% data reusables.dependabot.option-affects-security-updates %} - -```yaml -# Customizing commit messages - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - commit-message: - # Prefix all commit messages with "npm" - prefix: "npm" - - - package-ecosystem: "composer" - directory: "/" - schedule: - interval: "daily" - # Prefix all commit messages with "Composer" - # include a list of updated dependencies - commit-message: - prefix: "Composer" - include: "scope" - - - package-ecosystem: "pip" - directory: "/" - schedule: - interval: "daily" - # Include a list of updated dependencies - # with a prefix determined by the dependency group - commit-message: - prefix: "pip prod" - prefix-development: "pip dev" - include: "scope" -``` - -### `ignore` - -{% data reusables.dependabot.warning-ignore-option %} - -#### Revisar por preferencias ignoradas existentes - -Antes de que agreges una opción de `ignore` al archivo de configuración, revisa si has utilizado previamente cualquiera de los comandos de `@dependabot ignore` en una solicitud de extracción de actualizaciones de seguridad o de versión. El {% data variables.product.prodname_dependabot %} almacena estas preferencias para cada administrador de paquetes centralmente, y esta información se sobreescribe mediante la opción `ignore`. Para obtener más información acerca de los comandos de `@dependabot ignore`, consulta la sección "[Administrar las solicitudes de extracción para las actualizaciones de dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)". - -Puedes revisar si un repositorio ha almacenado las preferencias si buscas dicho repositorio con `"@dependabot ignore" in:comments`. Si revias alguna solicitud de extracción en los resultados, puedes decidir si quieres o no especificar esas dependencias o versiones ignoradas en el archivo de configuración. - -#### Especificar dependencias y versiones para ignorar - -{% data reusables.dependabot.default-dependencies-allow-ignore %} - -Puedes utilizar la opción `ignore` para personalizar qué dependencias se actualizarán. La opción `ignore` es compatible con las siguientes opciones. - -- `dependency-name`—se utiliza para ignorar actualizaciones para las dependencias con nombres coincidentes, opcionalmente, utiliza `*` para empatar cero o más caracteres. Para las dependencias de Java, el formato del atributo `dependency-name` es: `groupId:artifactId`, por ejemplo: `org.kohsuke:github-api`. -- `versions`—se utiliza para ignorar versiones o rangos específicos de las versiones. Si quieres definir un rango, utiliza el patrón estándar del administrador de paquetes (por ejemplo: `^1.0.0` para npm, o `~> 2.0` para Bundler). - -{% data reusables.dependabot.option-affects-security-updates %} - -```yaml -# Customizing the dependencies to maintain with `ignore` - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - ignore: - - dependency-name: "express" - # For Express, ignore all updates for version 4 and 5 - versions: ["4.x", "5.x"] - # For Loadash, ignore all updates - - dependency-name: "loadash" -``` - -{% note %} - -Las {% data variables.product.prodname_dependabot_version_updates %} no pueden ejecutar actualizaciones de versiones para ninguna dependencia en los manifiestos que contengan dependencias privadas de git o registros privados de git, aún si agregas las dependencias privadas a la opción de `ignore` en tu archivo de configuración. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-github-dependabot#supported-repositories-and-ecosystems)". - -{% endnote %} - -### `etiquetas` - -{% data reusables.dependabot.default-labels %} - -Utiliza `labels` para anular las etiquetas predeterminadas y especificar las etiquetas alternas para todas las solicitudes de extracción que se levante para un administrador de paquete. Si ninguna de estas etiquetas se define en el repositorio, entonces se ha ignorado. Para inhabilitar todas las etiquetas, incluyendo aquellas predeterminadas, utiliza `labels: [ ]`. - -{% data reusables.dependabot.option-affects-security-updates %} - -```yaml -# Specify labels for pull requests - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Specify labels for npm pull requests - labels: - - "npm" - - "dependencies" -``` - -### `hito` - -Utiliza `milestone` para asociar todas las solicitudes de extracción que se han levantado para un administrador de paquete con un hito. Necesitas especificar el identificador numérico del hito y, no así, su etiqueta. Si ves un hito, la parte final de la URL de la página, después de `milestone`, es el identificador. Por ejemplo: `https://github.com///milestone/3`. - -{% data reusables.dependabot.option-affects-security-updates %} - -```yaml -# Specify a milestone for pull requests - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Associate pull requests with milestone "4" - milestone: 4 -``` - -### `open-pull-requests-limit` - -Predeterminadamente, {% data variables.product.prodname_dependabot %} abre un máximo de cinco solicitudes de extracción para las actualizaciones de versión. Una vez que haya cinco solicitudes de extracción abiertas, las nuevas solicitudes se bloquearán hasta que fusiones o cierres alguna de las que están abiertas. Utiliza `open-pull-requests-limit` para cambiar este límite. Esto también proporciona una forma simple de inhabilitar temporalmente las actualizaciones de versión para un administrador de paquete. - -Esta opción no tiene impacto en las actualizaciones de seguridad que tienen un límite separado e interno de diez solicitudes de extracción abiertas. - -```yaml -# Changing the number of open pull requests allowed - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Disable version updates for npm dependencies - open-pull-requests-limit: 0 - - - package-ecosystem: "pip" - directory: "/" - schedule: - interval: "daily" - # Allow up to 10 open pull requests for pip dependencies - open-pull-requests-limit: 10 -``` - -### `pull-request-branch-name.separator` - -El {% data variables.product.prodname_dependabot %} genera una rama para cada solicitud de extracción. Cada nombre de rama incluye `dependabot`, y el administrador de paquete y la dependencia que se actualizaron. Predeterminadamente, estas partes están separadas por un símbolo de `/`, por ejemplo: `dependabot/npm_and_yarn/next_js/acorn-6.4.1`. - -Utiliza `pull-request-branch-name.separator` para especificar un separador diferente. Este puede ser alguno de entre: `"-"`, `_` o `/`. El símbolo de guión debe estar entre comillas porque, de lo contrario, se interpretará como que está declarando una lista YAML vacía. - -{% data reusables.dependabot.option-affects-security-updates %} - -```yaml -# Specifying a different separator for branch names - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - pull-request-branch-name: - # Separate sections of the branch name with a hyphen - # for example, `dependabot-npm_and_yarn-next_js-acorn-6.4.1` - separator: "-" -``` - -### `rebase-strategy` - -Predeterminadamente, el {% data variables.product.prodname_dependabot %} rebasa automáticamente las solicitudes de extracción abiertas cuando detecta conflictos. Utiliza `rebase-strategy` para inhabilitar este comportamiento. - -Estrategias de rebase disponibles - -- `disabled` para inhabilitar el rebase automático. -- `auto` para utilizar el comportamiento predeterminado y rebasar las solicitudes de extracción abiertas cuando se detecten conflictos. - -{% data reusables.dependabot.option-affects-security-updates %} - -```yaml -# Disabling automatic rebasing - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Disable rebasing for npm pull requests - rebase-strategy: "disabled" -``` - -### `reviewers` - -Utiliza `reviewers` para especificar los revisores o equipos individuales de revisores para las solicitudes de extracción que se levantaron para un administrador de paquete. Debes utilizar el nombre completo del equipo, incluyendo la organización, como si lo estuvieras @mencionando. - -{% data reusables.dependabot.option-affects-security-updates %} - -```yaml -# Specify reviewers for pull requests - -version: 2 -updates: - - package-ecosystem: "pip" - directory: "/" - schedule: - interval: "daily" - # Add reviewers - reviewers: - - "octocat" - - "my-username" - - "my-org/python-team" -``` - -### `schedule.day` - -Cuando configuras un calendario de actualización en `weekly`, predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa las nuevas versiones los lunes a las 05:00 UTC. Utiliza `schedule.day` para especificar un día alterno para revisar si hay actualizaciones. - -Valores compatibles - -- `monday` -- `tuesday` -- `wednesday` -- `thursday` -- `friday` -- `saturday` -- `sunday` - -```yaml -# Specify the day for weekly checks - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "weekly" - # Check for npm updates on Sundays - day: "sunday" -``` - -### `schedule.time` - -Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones a las 05:00 UTC. Utiliza `schedule.time` para especificar una hora alterna para revisar si hay actualizaciones (formato: `hh:mm`). - -```yaml -# Set a time for checks -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Check for npm updates at 9am UTC - time: "09:00" -``` - -### `schedule.timezone` - -Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones a las 05:00 UTC. 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 - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - time: "09:00" - # Use Japan Standard Time (UTC +09:00) - timezone: "Asia/Tokyo" -``` - -### `target-branch` - -Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay archivos de manifiesto en las ramas predeterminadas y levanta solicitudes de extracción para las actualizaciones de versión contra dicha rama. Utiliza `target-branch` para especificar una rama diferente para los archivos de manifiesto y para las solicitudes de extracción. Cuando utilizas esta opción, la configuración para este administrador de paquete ya no afectará ninguna solicitud de extracción que se haya levantado para las actualizaciones de seguridad. - -```yaml -# Specify a non-default branch for pull requests for pip - -version: 2 -updates: - - package-ecosystem: "pip" - directory: "/" - schedule: - interval: "daily" - # Raise pull requests for version updates - # to pip against the `develop` branch - target-branch: "develop" - # Labels on pull requests for version updates only - labels: - - "pip dependencies" - - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "weekly" - # Check for npm updates on Sundays - day: "sunday" - # Labels on pull requests for security and version updates - labels: - - "npm dependencies" -``` - -### `versioning-strategy` - -Cuando el {% data variables.product.prodname_dependabot %} edita un archivo de manifiesto para actualizar una versión, utiliza las siguientes estrategias generales: - -- Para las apps, los requisitos de versión se incrementan, por ejemplo: npm, pip y Composer. -- Para las bibliotecas, el rango de versiones se amplía, por ejemplo: Bundler y Cargo. - -Utiliza la opción `versioning-strategy` para cambiar este comportamiento para los administradores de paquete compatibles. - -{% data reusables.dependabot.option-affects-security-updates %} - -Estrategias de actualización disponibles - -| Opción | Compatible con | Acción | -| ----------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `lockfile-only` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Crear únicamente solicitudes de extracción para actualizar los archivos fijados. Ignorar cualquier versión nueva que pudiera requerir cambios en el paquete del manifiesto. | -| `auto` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Seguir la estrategia predeterminada descrita anteriormente. | -| `widen` | `composer`, `npm` | Relajar el requisito de versión para que incluya tanto la versión nueva como la anterior, cuando sea posible. | -| `increase` | `bundler`, `composer`, `npm` | Siempre incrementar el requisito de versión para que empate con la versión nueva. | -| `increase-if-necessary` | `bundler`, `composer`, `npm` | Incrementar el requisito de versión únicamente cuando lo requiera la versión nueva. | - -```yaml -# Customizing the manifest version strategy - -version: 2 -updates: - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Update the npm manifest file to relax - # the version requirements - versioning-strategy: widen - - - package-ecosystem: "composer" - directory: "/" - schedule: - interval: "daily" - # Increase the version requirements for Composer - # only when required - versioning-strategy: increase-if-necessary - - - package-ecosystem: "pip" - directory: "/" - schedule: - interval: "daily" - # Only allow updates to the lockfile for pip and - # ignore any version updates that affect the manifest - versioning-strategy: lockfile-only -``` diff --git a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md b/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md deleted file mode 100644 index 62b607e5ec..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/customizing-dependency-updates.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -title: Personalizar las actualizaciones de las dependencias -intro: 'Puedes personalizar cómo el {% data variables.product.prodname_dependabot %} mantiene tus dependencias.' -permissions: 'Las personas con permisos de escritura en un repositorio pueden configurar {% data variables.product.prodname_dependabot %} para el mismo.' -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/customizing-dependency-updates ---- -{% data reusables.dependabot.beta-note %} - -### Acerca de personalizar las actualizaciones de las dependencias - -Después de que hayas habilitado la actualización de versiones, puedes personalizar como el {% data variables.product.prodname_dependabot %} mantiene tus dependencias si agregas más opciones al archivo *dependabot.yml*. Por ejemplo, podrías: - -- Especifica en qué día de la semana se abrirán las solicitudes de extracción para la actualización de versiones: `schedule.day` -- Establece revisores, asignados y etiquetas para cada administrador de paquete: `reviewers`, `assignees`, y `labels` -- Define una estrategia de versionamiento para los cambios que se realicen en cada archivo de manifiesto: `versioning-strategy` -- Cambia la cantidad máxima de solicitudes de extracción abiertas para actualizaciones de versión del valor predeterminado que es 5: `open-pull-requests-limit` -- Abre solicitudes de extracción para actualizaciones de versión para seleccionar una rama específica en vez de la rama predeterminada: `target-branch` - -Para obtener más información acerca de las opciones de configuración, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". - -Cuando actualizas el archivo *dependabot.yml* en tu repositorio, el {% data variables.product.prodname_dependabot %} ejecuta una revisión inmediata con la nueva configuración. Podrás ver una lista actualizada de dependencias pocos minutos después en la pestaña del **{% data variables.product.prodname_dependabot_short %}**, esto podría tardar más si el repositorio tiene muchas dependencias. También puedes ver las solicitudes de extracción nuevas para las actualizaciones de versión. Para obtener más información, consulta la sección "[Listar dependencias configuradas para actualizaciones de versión](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)". - -### Impacto de los cambios de configuración en las actualizaciones de seguridad - -Si personalizas el archivo *dependabot.yml*, podrías notar algunos cambios en las solicitudes de extracción que se levantan para las actualizaciones de seguridad. Estas solicitudes de extracción siempre se activan mediante una asesoría de seguridad para una dependencia en vez de mediante un calendario de programación del {% data variables.product.prodname_dependabot %}. Sin embargo, estas heredan la configuración de ajustes relevante del archivo *dependabot.yml* a menos de que especifiques una rama destino diferente para las actualizaciones de versión. - -Por ejemplo, consulta la sección "[Configurar etiquetas personalizadas](#setting-custom-labels)" a más adelante. - -### Modificar la programación - -Cuando configuras una actualización de tipo `daily`, predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones a las 05:00 UTC. Puedes utilizar `schedule.time` para especificar una hora alterna para que revise actualizaciones (en formato: `hh:mm`). - -El archivo *dependabot.yml* de ejemplo a continuación expande la configuración de npm para especificar cuándo el {% data variables.product.prodname_dependabot %} debería revisar si hay actualizaciones de versión para las dependencias. - -```yaml -# dependabot.yml file with -# customized schedule for version updates - -version: 2 -updates: - # Keep npm dependencies up to date - - package-ecosystem: "npm" - directory: "/" - # Check the npm registry for updates at 2am UTC - schedule: - interval: "daily" - time: "02:00" -``` - -### Configurar los revisores y asignados - -Predeterminadamente, el {% data variables.product.prodname_dependabot %} levanta solicitudes de extracción sin ningún revisor o asignado. - -Puedes utilizar `reviewers` y `assignees` para especificar los revisores y asignados para todas las solicitudes de extracción que se levanten para un administrador de paquete. Cuando especificas un equipo, debes utilizar el nombre completo de éste, como si estuvieras @mencionándolo (incluyendo la organización). - -El ejemplo de archivo *dependabot.yml* mostrado a continuación cambia las configuraciones npm para que todas las solicitudes de extracción que se hayan abierto con actualizaciones de versión y de seguridad para npm tengan dos revisores y un asignado. - -```yaml -# dependabot.yml file with -# reviews and an assignee for all npm pull requests - -version: 2 -updates: - # Keep npm dependencies up to date - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Raise all npm pull requests with reviewers - reviewers: - - "my-org/team-name" - - "octocat" - # Raise all npm pull requests with an assignee - assignees: - - "user-name" -``` - -### Configurar las etiquetas personalizadas - -{% data reusables.dependabot.default-labels %} - -Puedes utilizar `labels` para anular las etiquetas predeterminadas y especificar etiquetas alternas para todas las solicitudes de extracción que se han levantado para un administrador de paquete. No puedes crear etiquetas nuevas en el archivo *dependabot.yml*, así que las etiquetas alternas ya deben existir en el repositorio. - -El siguiente ejemplo de archivo *dependabot.yml* cambia la configuración de npm para que las solicitudes de extracción abiertas con actualizaciones de versión y de seguridad para npm tengan etiquetas personalizadas. También cambia la configuración de Docker para revisar las actualizaciones de versión contra una rama personalizada y para levantar solicitudes de extracción con etiquetas personalizadas contra dicha rama personalizada. Los cambios en Docker no afectarán las solicitudes de extracción para actualizaciones de seguridad, ya que dichas actualizaciones de seguridad siempre se hacen contra la rama predeterminada. - -{% note %} - -**Nota:** La nueva `target-branch` deberá contener un Dockerfile para actualizar, de lo contrario, este cambio tendrá el efecto de inhabilitar las actualizaciones de versión para Docker. - -{% endnote %} - -```yaml -# dependabot.yml file with -# customized npm configuration - -version: 2 -updates: - # Keep npm dependencies up to date - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Raise all npm pull requests with custom labels - labels: - - "npm dependencies" - - "triage-board" - - # Keep Docker dependencies up to date - - package-ecosystem: "docker" - directory: "/" - schedule: - interval: "daily" - # Raise pull requests for Docker version updates - # against the "develop" branch. The Docker configuration - # no longer affects security update pull requests. - target-branch: "develop" - # Use custom labels on pull requests for Docker version updates - labels: - - "Docker dependencies" - - "triage-board" -``` - -### Más ejemplos - -Para obtener más ejemplos, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". diff --git a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates.md b/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates.md deleted file mode 100644 index d4b32280f8..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -title: Habilitar e inhabilitar las actualizaciones de versión -intro: 'Puedes configurar tu repositorio para que el {% data variables.product.prodname_dependabot %} actualice automáticamente los paquetes que utilizas.' -permissions: 'Las personas con permisos de escritura en un repositorio pueden habilitar o inhabilitar las {% data variables.product.prodname_dependabot_version_updates %} para el mismo.' -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/enabling-and-disabling-version-updates ---- -{% data reusables.dependabot.beta-note-no-link %} - -### Acerca de las actualizaciones de versión para las dependencias - -Habilitarás {% data variables.product.prodname_dependabot_version_updates %} mediante la selección de un archivo de configuración de *dependabot.yml* en el directorio `.github` dentro de tu repositorio. El {% data variables.product.prodname_dependabot_short %} levanta entonces las solicitudes de extracción para mantener actualizadas las dependencias que configuras. Para cada dependencia del administrador de paquete que quieras actualizar, debes especificar la ubicación de los archivos de manifiesto de dicho paquete, así como la periodicidad en la que quieres buscar actualizaciones para las dependencias listadas en esos archivos. Para obtener información acerca de las actualizaciones de seguridad, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)". - -{% data reusables.dependabot.initial-updates %} Para obtener más información, consulta la sección "[Personalizar las actualizaciones de las dependencias](/github/administering-a-repository/customizing-dependency-updates)". - -### Habilitar {% data variables.product.prodname_dependabot_version_updates %} - -{% note %} - -{% data reusables.dependabot.private-dependencies %} - -{% endnote %} - -{% data reusables.dependabot.create-dependabot-yml %} -1. Utiliza `package-ecosystem` para especificar los administradores de paquete que se deben monitorear. -1. Para cada administrador de paquete, utiliza: - - `directory` para especificar la ubicación del manifiesto u otros archivos de definición. - - `schedule.interval` para especificar qué tan a menudo se debe revisar si hay nuevas versiones. -{% data reusables.dependabot.check-in-dependabot-yml %} - -#### Archivo *dependabot.yml* de ejemplo - -El archivo de ejemplo *dependabot.yml* que se muestra a continuación configura las actualizaciones de versión para dos administradores de paquete: npm y Docker. Cuando se registra este archivo, el {% data variables.product.prodname_dependabot %} revisa los archivos de manifiesto en la rama predeterminada par ver si hay dependencias desactualizadas. Si encuentra dependencias desactualizadas, levantará solicitudes de extracción contra la rama predeterminada para actualizar estas dependencias. - -```yaml -# Basic dependabot.yml file with -# minimum configuration for two package managers - -version: 2 -updates: - # Enable version updates for npm - - package-ecosystem: "npm" - # Look for `package.json` and `lock` files in the `root` directory - directory: "/" - # Check the npm registry for updates every day (weekdays) - schedule: - interval: "daily" - - # Enable version updates for Docker - - package-ecosystem: "docker" - # Look for a `Dockerfile` in the `root` directory - directory: "/" - # Check for updates once a week - schedule: - interval: "weekly" -``` - -En el ejemplo anterior, si las dependencias de Docker estuvieran muy desactualizadas, tal vez quisieras comenzar con una programación de tipo `daily` hasta que las dependencias estén bien actualizadas y, posteriormente, tomar una programación semanal. - -#### Habilitar las actualizaciones de versión en las bifurcaciones - -Si quieres habilitar las actualizaciones de versión en las bifurcaciones, hay un paso extra que debes tomar. Las actualizaciones de versión no se habilitan automáticamente en las bifurcaciones cuando existe un archivo de configuración *dependabot.yml*. Esto garantiza que los dueños de la bifurcación no habiliten las actualizaciones de versión accidentalmente cuando suben cambios, incluyendo el archivo de configuración *dependabot.yml* del repositorio original. - -En una bifurcación, también necesitas habilitar explícitamente el {% data variables.product.prodname_dependabot %}. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.click-dependency-graph %} -{% data reusables.dependabot.click-dependabot-tab %} -5. Debajo de "Habilitar el Dependabot", da clic en **Enable Dependabot**. - -### Revisar el estado de las actualizaciones de versión - -Después de que habilitas las actualizaciones de versión, verás una nueva pestaña de **Dependabot** en la gráfica de dependencias del repositorio. Esta pestaña muestra los administradores de paquetes para los cuales se ha configurado el {% data variables.product.prodname_dependabot %} para monitorear y cuándo el {% data variables.product.prodname_dependabot_short %} los revisió por última vez para encontrar nuevas versiones. - -![Pestaña de perspectivas de repositorio, gráfica de dependencias, pestaña de dependabot](/assets/images/help/dependabot/dependabot-tab-view-beta.png) - -Para obtener más información, consulta la sección "[Listar las dependencias configuradas para las actualizaciones de versión](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)". - -### Inhabilitar las {% data variables.product.prodname_dependabot_version_updates %} - -Puedes inhabilitar las actualizaciones de versión completamente si eliminas el archivo *dependabot.yml* de tu repositorio. Normalmente, tal vez quieras inhabilitar las actualizaciones temporalmente para una o más dependencias o administradores de paquete. - -- Administradores de paquete: inhabilítalas configurando `open-pull-requests-limit: 0` o dejando de comentar el `package-ecosystem` relevante en el archivo de configuración. -- Dependencias específicas: inhabilítalas agregando los atributos de `ignore` para los paquetes o aplicaciones que quieras excluir de las actualizaciones. - -Cuando inhabilitas las dependencias, puedes utilizar comodines para empatar con un conjunto de bibliotecas relacionadas. También puedes especificar qué versiones excluir. Esto es particularmente útil si necesitas bloquear actualizaciones en una biblioteca, el trabajo pendiente para apoyar un cambio sustancial en su API, pero quieres quieres obtener cualquier arreglo de seguridad para la versión que utilices. - -#### Ejemplo de inhabilitar las actualizaciones de versión para algunas dependencias - -En este archivo de *dependabot.yml* de ejemplo se incluyen ejemplos de las formas diferentes para inhabilitar las actualizaciones en algunas dependencias, mientras que se permite que otras actualizaciones continuen. - -```yaml -# dependabot.yml file with updates -# disabled for Docker and limited for npm - -version: 2 -updates: - # Configuration for Dockerfile - - package-ecosystem: "docker" - directory: "/" - schedule: - interval: "weekly" - # Disable all pull requests for Docker dependencies - open-pull-requests-limit: 0 - - # Configuration for npm - - package-ecosystem: "npm" - directory: "/" - schedule: - interval: "daily" - # Overwrite any ignores created using `@dependabot ignore` commands - ignore: - # Ignore updates to packages that start 'aws' - # Wildcards match zero or more arbitrary characters - - dependency-name: "aws*" - # Ignore some updates to the 'express' package - - dependency-name: "express" - # Ignore only new versions for 4.x and 5.x - versions: ["4.x", "5.x"] -``` - -{% data reusables.dependabot.warning-ignore-option %} - -Para obtener más información acerca de revisar si existen preferencias para ignorar, consulta la sección "[Opciones de configuración para las actualizaciones de depdendencias](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)". diff --git a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/index.md b/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/index.md deleted file mode 100644 index 64d2b7d23b..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Mantener tus dependencias actualizadas automáticamente -intro: 'El {% data variables.product.prodname_dependabot %} puede mantener tus dependencias de repositorio automáticamente.' -versions: - free-pro-team: '*' -children: - - /about-github-dependabot-version-updates - - /enabling-and-disabling-version-updates - - /listing-dependencies-configured-for-version-updates - - /managing-pull-requests-for-dependency-updates - - /customizing-dependency-updates - - /configuration-options-for-dependency-updates - - /keeping-your-actions-up-to-date-with-github-dependabot ---- - diff --git a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-github-dependabot.md b/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-github-dependabot.md deleted file mode 100644 index 1d5ec3b13f..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-github-dependabot.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Mantener tus acciones actualizadas con el Dependabot de GitHub -intro: 'Puedes utilizar el {% data variables.product.prodname_dependabot %} para mantener las acciones que utilizas actualizadas en sus versiones más recientes.' -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot ---- -{% data reusables.dependabot.beta-note %} - -### Acerca de {% data variables.product.prodname_dependabot_version_updates %} para las acciones - -Las acciones a menudo se actualizan con correcciones de errores y con nuevas características para que los procesos automatizados sean más confiables, rápidos y seguros. Cundo habilitas las {% data variables.product.prodname_dependabot_version_updates %} para {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} te ayudará a asegurarte de que las referencias para las acciones en el archivo *workflow.yml* de un repositorio se mantengan actualizadas. El {% data variables.product.prodname_dependabot_short %} verifica la referencia de la acción para cada una de ellas en el archivo (habitualmente un número de versión o identificador de confirmación que se asocie con la acción) contra la última versión. Si alguna versión más reciente de la acción está disponible, el {% data variables.product.prodname_dependabot_short %} te enviará una solicitud de extracción que actualice la referencia en el archivo de flujo de trabajo a su última versión. Para obtener más información acerca de las {% data variables.product.prodname_dependabot_version_updates %}, consulta la sección "[Acerca del {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-github-dependabot-version-updates)". Para obtener más información acerca de configurar flujos de trabajo para {% data variables.product.prodname_actions %}, consulta la sección "[Configurar un flujo de trabajo](/actions/configuring-and-managing-workflows/configuring-a-workflow)". - -### Habilitar las {% data variables.product.prodname_dependabot_version_updates %} para las acciones - -{% data reusables.dependabot.create-dependabot-yml %}Si ya habilitaste las {% data variables.product.prodname_dependabot_version_updates %} para otros ecosistemas o administradores de paquetes, simplemente abre el archivo *dependabot.yml* existente. -1. Especifica `"github-actions"` como el `package-ecosystem` a monitorear. -1. Configura el `directory` como `"/"` para verificar los archivos de flujo de trabajo en `.github/workflows`. -1. Configura un `schedule.interval` para especificar la frecuencia en la que se revisará si hay versiones nuevas. -{% data reusables.dependabot.check-in-dependabot-yml %}Si editaste un archivo existente, guarda tus cambios. - -También puedes habilitar las {% data variables.product.prodname_dependabot_version_updates %} en las bifurcaciones. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates#enabling-version-updates-on-forks)". - -#### Archivo de ejemplo de *dependabot.yml* para {% data variables.product.prodname_actions %} - -El siguiente ejemplo de archivo de *dependabot.yml* configura las actualizaciones de versión para {% data variables.product.prodname_actions %}. El `directory` debe configurarse como `"/"` para verificar los archivos de flujo de trabajo en `.github/workflows`. El `schedule.interval` se configura en `"daily"`. Después de que se verifique o actualice este archivo, el {% data variables.product.prodname_dependabot %} revisará si hay versiones nuevas de tus acciones. El {% data variables.product.prodname_dependabot_short %} levantará solicitudes de extracción para las actualizaciones de versión de cualquier acción desactualizada que encuentre. Después de las actualizaciones de versión iniciales, el {% data variables.product.prodname_dependabot_short %} seguirá buscando versiones desactualizadas para las acciones una vez por día. - -```yaml -# Set update schedule for GitHub Actions - -version: 2 -updates: - - - package-ecosystem: "github-actions" - directory: "/" - schedule: - # Check for updates to GitHub Actions every weekday - interval: "daily" -``` - -### Configurar las {% data variables.product.prodname_dependabot_version_updates %} para las acciones - -Cuando habilitas las {% data variables.product.prodname_dependabot_version_updates %} para las acciones, debes especificar los valores de `package-ecosystem`, `directory`, y `schedule.interval`. Hay muchas más propiedades opcionales que puedes configurar para personalizar tus actualizaciones de versión aún más. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates)". - -### Leer más - -- "[Acerca de GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)" diff --git a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md b/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md deleted file mode 100644 index 37ab441e68..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Listar dependencias configuradas para las actualizaciones de versión -intro: 'Puedes ver las dependencias que monitorea el {% data variables.product.prodname_dependabot %} pára encontrar actualizaciones.' -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/listing-dependencies-configured-for-version-updates ---- -{% data reusables.dependabot.beta-note %} - -### Visualizar dependencias que monitorea el {% data variables.product.prodname_dependabot %} - -Después de que habilites las actualizaciones de versión, puedes confirmar que tu configuración es la correcta si utilizas la pestaña de **{% data variables.product.prodname_dependabot_short %}** en la gráfica de dependencias para el repositorio. Para obtener más información, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.click-dependency-graph %} -{% data reusables.dependabot.click-dependabot-tab %} -5. Opcionalmente, para ver los archivos que se monitorean para un administrador de paquete, da clic en el {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} asociado. ![Archivos de dependencia monitoreados](/assets/images/help/dependabot/monitored-dependency-files.png) - -Si no encuentras alguna dependencia, revisa los archivos de bitácora para ver los errores. En caso de que no encuentres algún administrador de paquete, revisa el archivo de configuración. - -### Visualizar los archivos de bitácora del {% data variables.product.prodname_dependabot %} - -1. En la **pestaña de {% data variables.product.prodname_dependabot_short %}**, da clic en **Revisado por última vez hace *TIME*** para ver el archivo de bitácora que generó el {% data variables.product.prodname_dependabot %} durante su última verificación de actualizaciones de versión. ![Ver el archivo de bitácora](/assets/images/help/dependabot/last-checked-link.png) -2. Opcionalmente, para volver a ejecutar la revisión de versión, da clic en **Revisar si hay actualizaciones**. ![Revisar si hay actualizaciones](/assets/images/help/dependabot/check-for-updates.png) diff --git a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md b/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md deleted file mode 100644 index 62589c81e1..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Administrar las solicitudes de extracción para las actualizaciones de dependencia -intro: 'Administrarás las solicitudes de extracción que levante el {% data variables.product.prodname_dependabot %} de casi la misma forma que cualquier otra solicitud de extracción, pero hay algunas opciones adicionales.' -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/managing-pull-requests-for-dependency-updates ---- -{% data reusables.dependabot.beta-note %} - -### Acerca de las solicitudes de extracción del {% data variables.product.prodname_dependabot %} - -El {% data variables.product.prodname_dependabot %} levanta solicitudes de extracción para actualizar las dependencias. Dependiendo de cómo se configure tu repositorio, el {% data variables.product.prodname_dependabot_short %} podría levantar solicitudes de extracción para las actualizaciones de versión y/o para las alertas de seguridad. Administrarás estas solicitudes de la misma forma que cualquier otra solicitud de extracción, pero también hay comandos extra disponibles. Para obtener más información sobre cómo habilitar las actualizaciones de dependencias del {% data variables.product.prodname_dependabot %}, consulta las secciones "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)" y "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)". - -Cuando el {% data variables.product.prodname_dependabot %} levanta una solicitud de extracción, se te notificará con el método que hayas escogido para el repositorio. Cada solicitud de extracción contiene información detallada sobre el cambio propuesto, que se toma del sistema administrador de paquete. Estas solicitudes de extracción siguen las revisiones y pruebas normales que se definieron en tu repositorio. Adicionalmente, si hay información suficiente disponible, verás una puntuación de compatibilidad. Esto también podría ayudarte a decidir si quieres fusionar el cambio o no. Para obtener más información acerca de esta puntuación, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)". - -Si tienes muchas dependencias para administrar, tal vez quieras personalizar la configuración para cada administrador de paquete y que así, las solicitudes de extracción tengan revisores, asignados, y etiquetas específicos. Para obtener más información, consulta la sección "[Personalizar actualizaciones de dependencias](/github/administering-a-repository/customizing-dependency-updates)". - -### Visualizar las solicitudes de extracción del {% data variables.product.prodname_dependabot %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-pr %} -1. Cualquier solicitud de extracción para actualizaciones de versión o de seguridad se puede identificar fácilmente. - - El autor es [dependabot](https://github.com/dependabot), la cuenta bot que utiliza la app del {% data variables.product.prodname_dependabot %}. - - Predeterminadamente, tienen la etiqueta `dependencies`. - -### Cambiar la estrategia de rebase para las solicitudes de extracción del {% data variables.product.prodname_dependabot %} - -Predeterminadamente, el {% data variables.product.prodname_dependabot %} rebasa automáticamente las solicitudes de extracción para resolver cualquier conflicto. Si prefieres manejar los conflictos de fusión manualmente, puedes inhabilitar esta opción utilizando la opción de `rebase-strategy`. Para obtener más detalles, consulta la sección "[Opciones de configuración para actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#rebase-strategy)". - -### Administrar las solicitudes de extracción del {% data variables.product.prodname_dependabot %} con comandos de comentario - -El {% data variables.product.prodname_dependabot %} responde a comandos simples en los comentarios. Cada solicitud de extracción contiene detalles de los comandos que puedes utilizar para procesarla, por ejemplo: fusionar, combinar, reabrir, cerrar o rebasar dicha solicitud. El objetivo es facilitar tanto como sea posible el que se pueda clasificar automáticamente las solicitudes de extracción generadas. - -Si ejecutas cualquiera de los comandos para ignorar las dependencias o las versiones, el {% data variables.product.prodname_dependabot %} almacena las preferencias para el repositorio centralmente. Si bien esta es una solución rápida, para aquellos repositorios con más de un colaborador, es mejor definir explícitamente las dependencias y versiones a ignorar en el archivo de configuración. Esto hace que todos los colaboradores puedan ver más fácilmente por qué una dependencia en particular no se está actualizando automáticamente. Para obtener más información, consulta la sección "[Opciones de configuración para las actualizaciones de dependencias](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)". diff --git a/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md deleted file mode 100644 index f254b3c9cb..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Eliminar y restaurar ramas en una solicitud de extracción -intro: 'Si tienes acceso de escritura en un repositorio, puedes eliminar las ramas asociadas con solicitudes de extracción cerradas o fusionadas. No puedes eliminar las ramas asociadas con solicitudes de extracción abiertas.' -redirect_from: - - /articles/tidying-up-pull-requests/ - - /articles/restoring-branches-in-a-pull-request/ - - /articles/deleting-unused-branches/ - - /articles/deleting-and-restoring-branches-in-a-pull-request - - /github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### Borrar la rama utilizada para una solicitud de extracción - -Puedes borrar la rama que se asocia con una solicitud de extracción si la han fusionado o cerrado y no hay ninguna otra solicitud de extracción abierta que haga referencia a dicha rama. Para obtener información sobre cerrar ramas que no están asociadas con solicitudes de extracción, consulta la sección "[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)". - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-pr %} -{% data reusables.repositories.list-closed-pull-requests %} -4. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que se asocie con la rama que deseas eliminar. -5. Junto a la parte inferior de la solicitud de extracción, haz clic en **Eliminar rama**. ![Botón Eliminar rama](/assets/images/help/pull_requests/delete_branch_button.png) - - Este botón no se muestra si hay alguna solicitud de extracción abierta para esta rama actualmente. - -### Restaurar una rama eliminada - -Puedes restaurar la rama de encabezado de una solicitud de extracción cerrada. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-pr %} -{% data reusables.repositories.list-closed-pull-requests %} -4. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que se asocie con la rama que deseas restaurar. -5. Junto a la parte inferior de la solicitud de extracción, haz clic en **Restaurar rama**. ![Botón Restaurar rama eliminada](/assets/images/help/branches/branches-restore-deleted.png) - -### Leer más - -- "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -- "[Administrar el borrado automático de ramas](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)" -{% endif %} diff --git a/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/index.md b/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/index.md deleted file mode 100644 index ca80d8d89a..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Administrar ramas en tu repositorio -intro: 'Cada vez que propones un cambio en Git, [creas una nueva rama](/articles/creating-and-deleting-branches-within-your-repository/). La administración de ramas es una parte importante del flujo de trabajo de Git. Después de algún tiempo, tu lista de ramas puede crecer, por lo que es una buena idea eliminar las ramas fusionadas o antiguas.' -redirect_from: - - /articles/managing-branches-in-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /viewing-branches-in-your-repository - - /renaming-a-branch - - /changing-the-default-branch - - /deleting-and-restoring-branches-in-a-pull-request ---- - diff --git a/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md deleted file mode 100644 index 4e783a9a41..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Ver las ramas en tu repositorio -intro: 'Las ramas son centrales para la colaboración en {% data variables.product.product_name %}, y la mejor manera de verlas es en la pagina de ramas.' -redirect_from: - - /articles/viewing-branches-in-your-repository - - /github/administering-a-repository/viewing-branches-in-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% 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: - - **Tus ramas**: en los repositorios a los que puedes tener acceso de escritura, la vista **Yours** (Tuyas) muestra todas las ramas a las que has subido contenido, y las más recientes se muestran 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. - -![La página de ramas para el repositorio Atom](/assets/images/help/branches/branches-overview-atom.png) - -### Leer más - -- "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" -- "[Eliminar ramas no utilizadas](/articles/deleting-unused-branches)" diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md deleted file mode 100644 index 82657dda63..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Acerca de las notificaciones por correo electrónico para las inserciones en tu repositorio -intro: Puedes elegir enviar notificaciones por correo electrónico automáticamente a una dirección en específico cuando alguien suba información a tu repositorio. -permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository. -redirect_from: - - /articles/managing-notifications-for-pushes-to-a-repository/ - - /articles/receiving-email-notifications-for-pushes-to-a-repository/ - - /articles/about-email-notifications-for-pushes-to-your-repository/ - - /github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository - - /github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% if currentVersion != "free-pro-team@latest" %}{% data reusables.notifications.outbound_email_tip %}{% endif %} - -Cada notificación por correo electrónico para una subida a un repositorio enumera las confirmaciones nuevas y las vincula a una diferencia que solo contenga esas confirmaciones. En la notificación por correo electrónico verás: - -- El nombre del repositorio donde se realizó la confirmación. -- La rama en la que se realizó la confirmación. -- El SHA1 de la confirmación, incluido un enlace a la diferencia en {% data variables.product.product_name %}. -- El autor de la confirmación. -- La fecha en que se realizó la confirmación. -- Los archivos que fueron modificados como parte de la confirmación. -- El mensaje de confirmación - -Puedes filtrar las notificaciones por correo electrónico que recibes para las inserciones en un repositorio. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Acerca de los mensajes de notificación por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications)". También puedes apagar las notificaciones por correo electrónico para las cargas de información. Para obtener más información, consulta la sección "[Escoger el método de entrega para las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}". - -### Habilitar las notificaciones por correo electrónico para las subidas de información en tu repositorio - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.sidebar-notifications %} -5. Escribe hasta dos direcciones de correo electrónico, separadas por espacio en blanco, donde quieras que se envíen las notificaciones. Si quieres enviar los correos electrónicos a más de dos cuentas, configura una de las direcciones de correo electrónico a una dirección de correo electrónico del grupo. ![Cuadro de texto dirección de correo electrónico](/assets/images/help/settings/email_services_addresses.png) -6. Si operas tu propio servidor, puedes verificar la integridad de los correos electrónicos mediante el token **Secreto**. Este token se envía con el correo electrónico como el encabezado `Aprobado`. Si el encabezado `Aprobado` coincide con el token que enviaste, puedes confiar en que el correo electrónico es de {% data variables.product.product_name %}. ![Cuadro de texto correo electrónico secreto](/assets/images/help/settings/email_services_token.png) -7. Opcionalmente, selecciona **Enviar desde autor** para que los correos electrónicos se envíen usando la dirección de correo electrónico de la persona que confirma el cambio. De lo contrario, los correos electrónicos se envían desde {% data variables.notifications.no_reply_address %}. ![Casilla de autor del correo electrónico](/assets/images/help/settings/email_services_author.png) -8. Haz clic en **Guardar parámetros**. ![Botón Guardar parámetros](/assets/images/help/settings/save_notification_settings.png) - -### Leer más -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" -{% else %} -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Escoger el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" -- "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" -- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %} diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics.md deleted file mode 100644 index 1e2fa33349..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Classifying your repository with topics -intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.' -redirect_from: - - /articles/about-topics/ - - /articles/classifying-your-repository-with-topics - - /github/administering-a-repository/classifying-your-repository-with-topics -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### About topics - -With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% if currentVersion == "free-pro-team@latest" %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}. - -![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png) - -To browse the most used topics, go to https://github.com/topics/. - -{% if currentVersion == "free-pro-team@latest" %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %} - -Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% if currentVersion == "free-pro-team@latest" %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %} - -Public 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)." - -### Adding topics to your repository - -{% data reusables.repositories.navigate-to-repo %}{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -2. Under your repository description, click **Add topics**. - ![Add topics link on a repository's main page](/assets/images/help/repository/add-topics-link.png) -3. Type the topic you want to add to your repository, then type a space. - ![Form to enter topics](/assets/images/help/repository/add-topic-form.png) -4. After you've finished adding topics, click **Done**. - ![Form with a list of topics and Done button](/assets/images/help/repository/add-topics-done-button.png) -{% else %} -2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}. - ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png) -3. Under "Topics", type the topic you want to add to your repository, then type a space. - ![Form to enter topics](/assets/images/help/repository/add-topic-form.png) -4. After you've finished adding topics, click **Save changes**. - !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png) -{% endif %} diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md deleted file mode 100644 index fde91fa61b..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Configurar enlaces automáticos para referenciar recursos externos -intro: 'Puedes agregar enlaces automáticos a recursos externos, como propuestas de JIRA y tickets de Zendesk, para ayudar a optimizar tu flujo de trabajo.' -product: '{% data reusables.gated-features.autolinks %}' -redirect_from: - - /articles/configuring-autolinks-to-reference-external-resources - - /github/administering-a-repository/configuring-autolinks-to-reference-external-resources -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Cualquiera con permisos administrativos en un repositorio puede configurar las referencias auto-vinculadas para vincular informes de problemas, solicitudes de extracción,{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} mensajes de confirmación, y descripciones de lanzamientos{% else %} y mensajes de confirmación {% endif %} a 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. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En la barra lateral izquierda, haz clic en **Autolink references** (Referencias de enlace automático). ![Pestaña Autolink references (Referencias de enlace automático) en la barra lateral izquierda](/assets/images/help/repository/autolink-references-tab.png) -4. Haz clic en **Add autolink reference** (Agregar referencia de enlace automático). ![Botón para completar con información de la referencia de enlace automático](/assets/images/help/repository/add-autolink-reference-details.png) -5. Debajo de "Reference prefix" (Prefijo de referencia), escribe un prefijo corto y significativo que quieras que los colaboradores utilicen para generar enlaces automáticos para el recurso externo. ![Campo para escribir la abreviación para el sistema externo](/assets/images/help/repository/add-reference-prefix-field.png) -6. Debajo de "Target URL" (URL de destino), escribe el enlace al sistema externo al que te quieras vinculr. Asegúrate de conservar `` como variable para el número de referencia. ![Campo para escribir la URL al sistema externo](/assets/images/help/repository/add-target-url-field.png) -7. Haz clic en **Add autolink reference** (Agregar referencia de enlace automático). ![Botón para agregar referencia de enlace automático](/assets/images/help/repository/add-autolink-reference.png) diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/customizing-how-changed-files-appear-on-github.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/customizing-how-changed-files-appear-on-github.md deleted file mode 100644 index 742c0fc866..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/customizing-how-changed-files-appear-on-github.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Personalizar cómo aparecen los archivos cambiados en GitHub -intro: 'Para evitar que determinados archivos se muestren en diferencias de manera predeterminada, o que contribuyan al lenguaje del repositorio, puedes marcarlos con el atributo `linguist-generated` en un archivo *.gitattributes*.' -redirect_from: - - /articles/customizing-how-changed-files-appear-on-github - - /github/administering-a-repository/customizing-how-changed-files-appear-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Usa un archivo *.gitattributes* para marcar los archivos que coincidan con un "patrón" determinado con los atributos específicos. Un archivo *.gitattributes* usa las mismas reglas para coincidir como archivo _.gitignore_. Para obtener más información, consulta [FORMATO DE PATRONES](https://www.git-scm.com/docs/gitignore#_pattern_format) en la documentación de Git. - -1. A menos de que ya exista el archivo *.gitattributes* créalo en la raíz del repositorio. -2. Usa el atributo `linguist-generated` para marcar o desmarcar las rutas que deseas que se ignoren para las estadísticas de lenguaje del repositorio y las que deseas que se oculten de manera predeterminada en las diferencias. - - Por ejemplo, para marcar `search/index.json` como archivo generado, agrega esta línea a *.gitattributes*: - - ``` -search/index.json linguist-generated=true - ``` - -### Leer más -- "[Código generado](https://github.com/github/linguist/#generated-code)" en la documentación del lingüista -- "[Crear archivos nuevos](/articles/creating-new-files/)" diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/customizing-your-repositorys-social-media-preview.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/customizing-your-repositorys-social-media-preview.md deleted file mode 100644 index e46f554553..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/customizing-your-repositorys-social-media-preview.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Personalizar la vista previa de las redes sociales de tu repositorio -intro: Puedes personalizar la imagen que se muestra en las plataformas de las redes sociales cuando alguien usa un enlace a tu repositorio. -redirect_from: - - /articles/customizing-your-repositorys-social-media-preview - - /github/administering-a-repository/customizing-your-repositorys-social-media-preview -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Hasta que agregues una imagen, los enlaces al repositorio se expanden para mostrar información básica acerca del repositorio y del avatar del propietario. Agregar una imagen a tu repositorio puede ayudar a identificar tu proyecto entre distintas plataformas de redes sociales. - -Puedes cargar una imagen a un repositorio privado, pero tu imagen solo se puede compartir desde un repositorio público. - -{% tip %} -Tip: Your image should be a PNG, JPG, or GIF file under 1 MB in size. Para presentar la mejor calidad, recomendamos mantener la imagen alrededor de 640 por 320 píxeles. -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En "Vista previa de las redes sociales", haz clic en **Editar**. - - Para agregar una nueva imagen, haz clic en **Cargar imagen...**. - - Para eliminar un imagen, haz clic en **Eliminar imagen**. - - ![Menú desplegable de vista previa de redes sociales](/assets/images/help/repository/social-preview.png) diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/deleting-a-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/deleting-a-repository.md deleted file mode 100644 index 2341965894..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/deleting-a-repository.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Eliminar un repositorio -intro: Puedes eliminar cualquier repositorio o bifurcación si eres un propietario de la organización o si tienes permisos de administración para el repositorio o la bifurcación. Eliminar un repositorio bifurcado no elimina el repositorio ascendente. -redirect_from: - - /delete-a-repo/ - - /deleting-a-repo/ - - /articles/deleting-a-repository - - /github/administering-a-repository/deleting-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% data reusables.organizations.owners-and-admins-can %} elimina un repositorio de la organización. Si se ha deshabilitado **Permitir que los miembros eliminen o transfieran repositorios para esta organización**, solo los propietarios de la organización pueden eliminar los repositorios de la organización. {% data reusables.organizations.new-repo-permissions-more-info %} - -{% if currentVersion == "free-pro-team@latest" %} -{% warning %} - -**Advertencia**: Eliminar un repositorio borrará de manera **permanente** los archivos adjuntos de lanzamiento y los permisos de equipo. Esta acción **no** se puede deshacer. - -{% endwarning %} -{% endif %} - -Recuerde lo siguiente: -- Eliminar un repositorio privado eliminará todas sus bifurcaciones. -- Eliminar un repositorio público no eliminará sus bifurcaciones. - -{% if currentVersion == "free-pro-team@latest" %} -Puede restaurar algunos de los repositorios eliminados en un plazo de 90 días. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/articles/restoring-a-deleted-repository)". -{% endif %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -2. En la Zona de peligro, haz clic en **Eliminar este repositorio**. ![Botón Eliminar repositorio](/assets/images/help/repository/repo-delete.png) -3. **Lee las advertencias**. -4. Para verificar que está eliminando el repositorio correcto, escribe el nombre del repositorio que deseas eliminar. ![Etiqueta de eliminación](/assets/images/help/repository/repo-delete-confirmation.png) -5. Haga clic en **Comprendo las consecuencias. Eliminar este repositorio**. diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/disabling-or-limiting-github-actions-for-a-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/disabling-or-limiting-github-actions-for-a-repository.md deleted file mode 100644 index 96fa0c3959..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/disabling-or-limiting-github-actions-for-a-repository.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Inhabilitar o limitar las acciones de GitHub para un repositorio -intro: 'Los dueños de repositorios pueden inhabilitar, habilitar y limitar {% data variables.product.prodname_actions %} para un repositorio específico.' -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' - github-ae: '*' -topics: - - Repositories -redirect_from: - - /github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository ---- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de los permisos de {% data variables.product.prodname_actions %} para tu repositorio - -{% data reusables.github-actions.disabling-github-actions %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". - -Puedes habilitar {% data variables.product.prodname_actions %} para tu repositorio. {% data reusables.github-actions.enabled-actions-description %} Puedes inhabilitar {% data variables.product.prodname_actions %} totalmente para tu repositorio. {% data reusables.github-actions.disabled-actions-description %} - -De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} en tu repositorio, pero limitar las acciones que un flujo de trabajo puede ejecutar. {% data reusables.github-actions.enabled-local-github-actions %} - -### Administrar los permisos de {% data variables.product.prodname_actions %} para tu repositorio - -{% 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. Para obtener más información, consulta la sección "[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)" o la sección "[Requerir las políticas de {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account)". - -{% endnote %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -4. Selecciona una opción debajo de "Permisos de las acciones". ![Habilita, inhabilita o limita las acciones para este repositorio](/assets/images/help/repository/enable-repo-actions.png) - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -### Habilitar flujos de trabajo para las bifurcaciones de repositorios privados - -{% data reusables.github-actions.private-repository-forks-overview %} - -#### Configurar la política de bifurcaciones privadas para un repositorio - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.settings-sidebar-actions %} -{% data reusables.github-actions.private-repository-forks-configure %} -{% endif %} diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository.md deleted file mode 100644 index a4c523e445..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: Botón para mostrar un patrocinador en tu repositorio -intro: Puedes agregar un botón de patrocinador en tu repositorio para aumentar la visibilidad de las opciones de financiación para tu proyecto de código abierto. -redirect_from: - - /github/building-a-strong-community/displaying-a-sponsor-button-in-your-repository - - /articles/displaying-a-sponsor-button-in-your-repository - - /github/administering-a-repository/displaying-a-sponsor-button-in-your-repository -versions: - free-pro-team: '*' -topics: - - Repositories ---- -### Acerca de los archivos FUNDING - -Puedes configurar tu botón de patrocinador editando un archivo _FUNDING.yml_ en la carpeta `.github` de tu repositorio, o bien en la rama predeterminada. Puedes configurar el botón para que incluya programadores patrocinados en {% data variables.product.prodname_sponsors %}, plataformas de financiamiento externo o URL de financiamiento personalizadas. Para obtener mas información acerca de {% data variables.product.prodname_sponsors %}, consulta "[Acerca de los patrocinadores de GitHub](/articles/about-github-sponsors)". - -Puedes agregar un nombre de usuario, un nombre de paquete o un nombre de proyecto por plataforma de financiamiento externo y hasta cuatro URL personalizadas. Puedes añadir hasta cuatro organizaciones o desarrolladores patrocinadores en {% data variables.product.prodname_sponsors %}. Agrega cada plataforma en una línea nueva, usando la siguiente sintaxis: - -| Plataforma | Sintaxis | -| ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | -| [CommunityBridge](https://communitybridge.org) | `community_bridge: PROJECT-NAME` | -| [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors) | `github: USERNAME` o `github: [USERNAME, USERNAME, USERNAME, USERNAME]` | -| [IssueHunt](https://issuehunt.io/) | `issuehunt: USERNAME` | -| [Ko-fi](https://ko-fi.com/) | `ko_fi: USERNAME` | -| [Liberapay](https://en.liberapay.com/) | `liberapay: USERNAME` | -| [Open Collective](https://opencollective.com/) | `open_collective: USERNAME` | -| [Otechie](https://otechie.com/) | `otechie: USERNAME` | -| [Patreon](https://www.patreon.com/) | `patreon: USERNAME` | -| [Tidelift](https://tidelift.com/) | `tidelift: PLATFORM-NAME/PACKAGE-NAME` | -| URL personalizada | `custom: LINK1` or `custom: [LINK1, LINK2, LINK3, LINK4]` | - -Para Tidelift, usa la sintaxis `platform-name/package-name` con los siguientes nombres de plataforma: - -| Lenguaje | Nombre de la plataforma | -| ---------- | ----------------------- | -| JavaScript | `npm` | -| Python | `pypi` | -| Ruby | `rubygems` | -| Java | `maven` | -| PHP | `packagist` | -| C# | `nuget` | - -A continuación, un ejemplo de un archivo _FUNDING.yml_: -``` -github: [octocat, surftocat] -patreon: octocat -tidelift: npm/octo-package -custom: ["https://www.paypal.me/octocat", octocat.com] -``` - -{% note %} - -**Nota:** Si una URL personalizada en una matriz incluye `:`, debes encerrar la URL entre comillas. Por ejemplo, `"https://www.paypal.me/octocat"`. - -{% endnote %} - -Puedes crear un botón patrocinador predeterminado para tu organización o cuenta de usuario. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)" - -{% note %} - -Los enlaces de financiamiento permiten que los proyectos de código abierto reciban apoyo financiero directo de su comunidad. El uso de enlaces de financiamiento para otros fines, como la publicidad o el apoyo a grupos solidarios, comunitarios o políticos no está admitido. Si tienes consultas acerca de si los fines con que deseas usar estos enlaces está admitido, comunícate con {% data variables.contact.contact_support %}. - -{% endnote %} - -### Botón para mostrar un patrocinador en tu repositorio - -Cualquier usuario que cuente con permisos de administración puede habilitar un botón de patrocinador en un repositorio. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En Características, selecciona **Patrocinios**. ![Casilla de verificación para habilitar Patrocinios](/assets/images/help/sponsors/sponsorships-checkbox.png) -4. Da clic en **Configurar botón de patrocinador** o **Invalidad enlaces de financiamiento** debajo de la opción "Patrocionios". ![Botón para configurar el botón del patrocinador](/assets/images/help/sponsors/sponsor-set-up-button.png) -5. En el editor de archivos, sigue la instrucciones en el archivo _FUNDING.yml_ para agregar enlaces a las ubicaciones de tus fuentes de financiamiento. ![Edita el archivo FUNDING para añadir enlaces a ubicaciones de fondeo](/assets/images/help/sponsors/funding-yml-file.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -### Leer más -- "[Acerca de {% data variables.product.prodname_sponsors %} para colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" -- "[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-XL/content/github/administering-a-repository/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md deleted file mode 100644 index 7941c54e26..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Activar el acceso de lectura Git anónimo para un repositorio -intro: 'Como administrador de un repositorio, puedes habilitar o inhabilitar el acceso de lectura Git anónimo para repositorios públicos que cumplen con determinados requisitos.' -redirect_from: - - /articles/enabling-anonymous-git-read-access-for-a-repository - - /github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository -versions: - enterprise-server: '*' ---- -Los administradores de repositorios pueden cambiar el acceso de lectura Git anónimo y establecer un repositorio específico en los siguientes casos: -- Si un administrador del sitio ha habilitado el modo privado y el acceso de lectura Git anónimo. -- Si el repositorio es público en la instancia y no es una bifurcación. -- Si un administrador del sitio no ha inhabilitado el acceso de lectura Git anónimo para el repositorio. - -{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Junto a "Habilitar el acceso de lectura Git anónimo", haz clic en **Habilitar**. ![Botón "Habilitado" en "Acceso de lectura Git anónimo"](/assets/images/help/repository/enable-git-read-access-for-a-repo.png) -4. Revisa los cambios. Para confirmar, escribe el nombre del repositorio y haz clic en **Comprendo. Habilitar el acceso de lectura Git.** diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/index.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/index.md deleted file mode 100644 index a60a7ec1c3..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/index.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Administrar configuraciones de repositorios -intro: 'Los administradores de repositorios y los propietarios de organizaciones pueden cambiar varias configuraciones, incluidos los nombres y la propiedad de un repositorio y la visibilidad pública o privada de un repositorio. También pueden eliminar un repositorio.' -redirect_from: - - /articles/managing-repository-settings -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /setting-repository-visibility - - /managing-teams-and-people-with-access-to-your-repository - - /classifying-your-repository-with-topics - - /customizing-how-changed-files-appear-on-github - - /about-email-notifications-for-pushes-to-your-repository - - /displaying-a-sponsor-button-in-your-repository - - /customizing-your-repositorys-social-media-preview - - /viewing-deployment-activity-for-your-repository - - /managing-the-forking-policy-for-your-repository - - /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository - - /disabling-or-limiting-github-actions-for-a-repository - - /enabling-or-disabling-github-discussions-for-a-repository - - /disabling-project-boards-in-a-repository - - /disabling-issues - - /managing-git-lfs-objects-in-archives-of-your-repository - - /managing-security-and-analysis-settings-for-your-repository - - /enabling-anonymous-git-read-access-for-a-repository - - /configuring-autolinks-to-reference-external-resources - - /renaming-a-repository - - /transferring-a-repository - - /deleting-a-repository - - /restoring-a-deleted-repository ---- - diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md deleted file mode 100644 index 30613f9e70..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Administrar los objetos de LFS de Git en los archivos de tu repositorio -shortTitle: 'Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos' -intro: 'Puedes 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 de código fuente, tales como los archivos ZIP y .tar, que {% data variables.product.product_name %} crea para tu repositorio.' -permissions: 'People with admin permissions for a repository can manage whether {% data variables.large_files.product_name_short %} objects are included in archives of the repository.' -versions: - free-pro-team: '*' - enterprise-server: '>3.0' - github-ae: '*' -topics: - - Repositories -redirect_from: - - /github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository ---- -### Acerca de los objetos de {% data variables.large_files.product_name_short %} en los archivos - -{% data variables.product.product_name %} crea archivos de código fuente para tu repositorio en forma de archivos ZIP y .tar. Las personas pueden descargar estos archivos en la página principal de tu repositorio o en forma de activos del lanzamiento. Predeterminadamente, los objetos de {% data variables.large_files.product_name_short %} no se incluyen en estos archivos, únicamente los archivos de puntero a estos objetos. Para mejorar la usabilidad de los archivos para tu repositorio, puedes elegir incluir los objetos de {% data variables.large_files.product_name_short %} en su lugar. - -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 %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage)". - -### Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Debajo de "Archivos", sleecciona o deselecciona **Incluir los objetos de {% data variables.large_files.product_name_short %} en los archivos**. ![Casilla para incluir los objetos de {% data variables.large_files.product_name_short %} en los archivos](/assets/images/help/repository/include-git-lfs-objects-checkbox.png) diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md deleted file mode 100644 index 5707ae34b1..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Gestionar equipos y personas con acceso a tu repositorio -intro: Puedes ver a todo aquél que ha accedido a tu repositorio y ajustar los permisos. -permissions: Repository administrators can manage teams and people with access to a repository. -redirect_from: - - /github/administering-a-repository/managing-people-and-teams-with-access-to-your-repository - - /github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository -versions: - free-pro-team: '*' -topics: - - Repositories ---- -### Acerca de gestionar el acceso a tu repositorio - -Puedes ver un resumen de cada equipo o persona con acceso a tu repositorio para todo aquél que administres en {% data variables.product.prodname_dotcom %}. Desde este resumen, también puedes invitar a nuevos equipos o personas, cambiar los permisos de ellos, o eliminar su acceso al repositorio. - -Este resumen puede ayudarte a auditar el acceso a tu repositorio, incorporar o retirar personal externo o empleados, y responder con efectividad a los incidentes de seguridad. - -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](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." - -![Resumen de gestión de accesos](/assets/images/help/repository/manage-access-overview.png) - -### Filtrar la lista de equipos y personas - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-manage-access %} -4. Debajo de "Administrar acceso" en el campo de búsqueda, comienza a teclear el nombre del equipo o persona que quieres encontrar. ![Campo de búsqueda para filtrar la lista de equipos o personas con acceso](/assets/images/help/repository/manage-access-filter.png) - -### Cambiar permisos para un equipo o persona - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-manage-access %} -4. Encuentra el equipo o persona cuyos permisos quieres cambiar debajo de "Administrar acceso", posteriormente, utiliza el menú desplegable de **Rol** para seleccionar nuevos permisos. ![Utilizar el menú desplegable de "Rol" para seleccionar nuevos permisos para un equipo o persona](/assets/images/help/repository/manage-access-role-drop-down.png) - -### Invitar a un equipo o persona - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-manage-access %} -{% data reusables.organizations.invite-teams-or-people %} -5. En el campo de búsqueda, comienza a teclear el nombre del equipo o persona que quieres invitar y da clic en el mismo dentro de la lista de coincidencias. ![Campo de búsqueda para teclear el nombre del equipo o persona que deseas invitar al repositorio](/assets/images/help/repository/manage-access-invite-search-field.png) -6. Debajo de "Escoje un rol", selecciona los permisos que quieres otorgar al equipo o persona, posteriormente, da clic en **Añadir NOMBRE a REPOSITORIO**. ![Seleccionar los permisos para el equipo o persona](/assets/images/help/repository/manage-access-invite-choose-role-add.png) - -### Eliminar el acceso de un equipo o persona - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-manage-access %} -4. Debajo de "Administrar acceso", encuentra al equipo o persona de quien quieras eliminar el acceso y da clic{% octicon "trashcan" aria-label="The trashcan icon" %}. ![Icono de papelera para eliminar el acceso](/assets/images/help/repository/manage-access-remove.png) - -### Leer más - -- "[Configurar la visibilidad de un repositorio](/github/administering-a-repository/setting-repository-visibility)" -- "[Configurar los permisos básicos para una organización](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-the-forking-policy-for-your-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-the-forking-policy-for-your-repository.md deleted file mode 100644 index aa1c14d6dd..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/managing-the-forking-policy-for-your-repository.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Administrar la política de ramificación para tu repositorio -intro: 'Puedes permitir o prevenir la ramificación de un repositorio privado {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o interno {% endif %} en específico que sea propiedad de una organización.' -redirect_from: - - /articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization - - /github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization - - /github/administering-a-repository/managing-the-forking-policy-for-your-repository -permissions: People with admin permissions for a repository can manage the forking policy for the repository. -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -El propietario de la organización debe permitir que las ramificaciones de repositorios privados {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} e internos {% endif %} a nivel organizacional antes de que puedas permitir o impedir las ramificaciones de un repositorio específico. Para obtener más información, consulta "[Administrar la política de ramificación para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)." - -{% data reusables.organizations.internal-repos-enterprise %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En "Features" (Características), selecciona **Allow forking** (Permitir bifurcación). ![Casilla de verificación para permitir o prohibir la bifurcación de un repositorio privado](/assets/images/help/repository/allow-forking-specific-org-repo.png) - -### Leer más - -- "[Acerca de las bifurcaciones](/articles/about-forks)" -- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/renaming-a-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/renaming-a-repository.md deleted file mode 100644 index 402b9997e9..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/renaming-a-repository.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Renombrar un repositorio -intro: Puedes renombrar un repositorio si eres propietario de la organización o tienes permisos de administrador para el repositorio. -redirect_from: - - /articles/renaming-a-repository - - /github/administering-a-repository/renaming-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Cuando cambias el nombre de un repositorio, toda la información existente, a excepción de las URL del sitio del proyecto, se redirige automáticamente al nuevo nombre, incluyendo: - -* Problemas -* Wikis -* Estrellas -* Seguidores - -Para obtener más información sobre los sitios del proyecto, consulta "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)" - -Adicionalmente a redirigir el tráfico web, todas las operaciones de `git clone`, `git fetch`, o`git push` que apunten a la ubicación anterior seguirán funcionando como si se hubieran hecho en la nueva. Sin embargo, para evitar la confusión, recomendamos ampliamente actualizar cualquier clon local para que lleve a la URL del nuevo repositorio. Puedes hacer esto utilizando `git remote` en la línea de comandos: - -```shell -$ git remote set-url origin new_url -``` - -Para obtener más información, consulta "[Cambiar la URL de un remoto](/github/using-git/changing-a-remotes-url)." - -{% if currentVersion == "free-pro-team@latest" %} - -Si planeas renombrar un repositorio que tenga un sitio {% data variables.product.prodname_pages %}, recomendamos utilizar un dominio personalizado para el mismo. Esto garantiza que la URL del sitio no se vea impactada cuando se renombre el repositorio. Para obtener más información, consulta "[Acerca de los dominios personalizados y sitio de {% data variables.product.prodname_pages %} ](/github/working-with-github-pages/about-custom-domains-and-github-pages)." - -{% endif %} - -{% tip %} - -**Sugerencia:** {% data reusables.organizations.owners-and-admins-can %} renombra un repositorio. {% data reusables.organizations.new-repo-permissions-more-info %} - -{% endtip %} - -{% warning %} - -**Advertencia**: Si en el futuro creas un nuevo repositorio bajo tu cuenta, no reutilices el nombre original del repositorio renombrado. Si lo haces, los redireccionamientos al repositorio renombrado fallarán. - -{% endwarning %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En **Repository Name** (Nombre del repositorio), escribe el nombre nuevo de tu repositorio. ![Renombrar repositorio](/assets/images/help/repository/repository-name-change.png) -4. Haz clic en **Rename** (renombrar). ¡Lo has hecho! diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/restoring-a-deleted-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/restoring-a-deleted-repository.md deleted file mode 100644 index 2ae95a162a..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/restoring-a-deleted-repository.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Restaurando un repositorio eliminado -intro: Puede restaurar algunos de los repositorios eliminados para recuperar su contenido. -redirect_from: - - /articles/restoring-a-deleted-repository - - /github/administering-a-repository/restoring-a-deleted-repository -versions: - free-pro-team: '*' -topics: - - Repositories ---- -Cualquier usuario puede restaurar repositorios eliminados que le pertenecieron a su propia cuenta de usuario. Los propietarios de la organización pueden restaurar repositorios eliminados que le pertenecieron a la organización. - -### Acerca de la restauración de repositorios - -Un repositorio eliminado se puede restaurar en un plazo de 90 días, a menos que el repositorio haya sido parte de una red de bifurcaciones que actualmente no está vacía. Una red de bifurcaciones consiste en un repositorio padre, las bifurcaciones del repositorio y las bifurcaciones de las bifurcaciones del repositorio. Si tu repositorio forma parte de una red de bifurcaciones, no se puede restaurar a menos que se elimine cualquier otro repositorio de la red o que se haya separado de la red. Para obtener más información acerca de las bifurcaciones, consulta "[Acerca de las bifurcaciones](/articles/about-forks)". - -Si quieres restaurar un repositorio que era parte de una red de bifurcaciones que actualmente no está vacía, te puedes contactar con {% data variables.contact.contact_support %}. - -Puede tardar hasta una hora después de que se elimine un repositorio antes de que ese repositorio esté disponible para la restauración. - -Restaurar un repositorio no restaurará los archivos adjuntos de lanzamiento o los permisos de equipo. Issues that are restored will not be labeled. - -### Restaurar un repositorio eliminado que le pertenecía a una cuenta de usuario - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.repo-tab %} -{% data reusables.user_settings.deleted-repos %} -{% data reusables.user_settings.restore-repo %} -{% data reusables.user_settings.restore-confirmation %} - -### Restaurar un repositorio eliminado que le pertenecía a una organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.deleted-repos %} -{% data reusables.user_settings.restore-repo %} -{% data reusables.user_settings.restore-confirmation %} - -### Leer más - -- "[Borrar un repositorio](/articles/deleting-a-repository)" diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/setting-repository-visibility.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/setting-repository-visibility.md deleted file mode 100644 index 8b20c7c2f1..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/setting-repository-visibility.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: Configurar la visibilidad de un repositorio -intro: Puedes elegir quién puede ver tu repositorio. -redirect_from: - - /articles/making-a-private-repository-public/ - - /articles/making-a-public-repository-private/ - - /articles/converting-a-public-repo-to-a-private-repo/ - - /articles/setting-repository-visibility - - /github/administering-a-repository/setting-repository-visibility -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### Acerca de los cambios a la visibilidad de un 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 "[Restringir los cambios a la visibilidad del repositorio en tu organización](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)." - -Te recomendamos revisar las siguientes consideraciones antes de que cambies la visibilidad de un repositorio. - -#### Convertir un repositorio en privado - - * {% data variables.product.prodname_dotcom %} separará las bifurcaciones públicas del repositorio público y las pondrá en una red nueva. Las bifurcaciones públicas no se hacen privadas. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Si cambias la visibilidad de un repositorio de interno a privado, {% data variables.product.prodname_dotcom %} eliminará las bifurcaciones que pertenezcan a cualquier usuario que no tenga acceso al repositorio privado nuevo.{% endif %} Para obtener más información, consulta la sección "[¿Qué pasa con las bifurcaciones cuando se borra un repositorio o cuando se cambia su visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-public-repository-to-a-private-repository)". - {% if currentVersion == "free-pro-team@latest" %}* Si estás utilizando un {% data variables.product.prodname_free_user %} para las cuentas de usuario u organizaciones, algunas características no estarán disponibles en el repositorio después de que cambias la visibilidad a privado. {% data reusables.gated-features.more-info %} - * Cualquier sitio {% data variables.product.prodname_pages %} publicado se despublicará de forma automática. Si agregaste un dominio personalizado al sitio {% data variables.product.prodname_pages %}, deberías eliminar o actualizar tus registros de DNS antes de convertir el repositorio en privado, para evitar el riesgo de una adquisición de dominio. 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)". - * {% data variables.product.prodname_dotcom %} ya no inlcuirá el repositorio en el {% data variables.product.prodname_archive %}. Para obtener más información, consulta la sección "[Acerca de archivar contenido y datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)".{% endif %} - {% if currentVersion != "free-pro-team@latest" %}* Ya no está disponible el acceso de lectura anónimo de Git. Para obtener más información, consulta la sección "[Habilitar el acceso de lectura anónimo de Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)".{% endif %} - -#### Convertir un repositorio en público - - * {% data variables.product.prodname_dotcom %} separará a las bifurcaciones privadas y las convertirá en un repositorio privado independiente. Para obtener más información, consulta "[¿Qué le sucede a las bifurcaciones cuando se elimina un repositorio o cambia la visibilidad?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)" - * Si estás convirtiendo tu repositorio privado en un repositorio público como parte de una mudanza para crear un proyecto de código abierto, consulta las [Guías de código abierto](http://opensource.guide) para obtener consejos y pautas útiles.{% if currentVersion == "free-pro-team@latest" %} También puedes hacer un curso gratuito sobre administrar un proyecto de código abierto con [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Una vez que tu repositorio es público, también puedes ver el perfil de la comunidad de tu repositorio para ver si tu proyecto cumple con las mejoras prácticas para los colaboradores de apoyo. Para obtener más información, consulta "[Ver el perfil de tu comunidad](/articles/viewing-your-community-profile)"{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - -### Cambiar la visibilidad de un repositorio - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Debajo de "Zona de Peligro", a la derecha de "Cambiar la visibilidad del repositorio", da clic en **Cambiar la visibilidad**. ![Botón de cambiar la visibilidad](/assets/images/help/repository/repo-change-vis.png) -4. Selecciona una visibilidad. ![Diálogo de opciones para la visbilidad del repositorio](/assets/images/help/repository/repo-change-select.png) -5. Para verificar que estás cambiando la visibilidad del repositorio correcto, teclea el nombre del repositorio para el cual quieres cambiar la visibilidad. -6. Da clic en **Entiendo, cambiar la visibilidad del repositorio**. ![Botón de confirmar cambio para la visibilidad de un repositorio](/assets/images/help/repository/repo-change-confirm.png) - -{% endif %} - -{% if currentVersion ver_lt "enterprise-server@2.22" %} - -### Convertir un repositorio en privado - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Under "Danger Zone", next to "Make this repository private", click **Make private**. ![Botón para convertir en privado](/assets/images/help/repository/repo-makeprivate.png) -4. Lee las advertencias acerca de convertir un repositorio en privado. ![Ventana emergente de advertencias](/assets/images/help/repository/repo-privateconfirm.png) -5. Escribe el nombre del repositorio que deseas convertir en privado, por ejemplo `accountname/reponame`. -6. Click **I understand, make this repository private**. - -### Convertir un repositorio en público - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Under "Danger Zone", next to "Make this repository public", click **Make public**. ![Botón para convertir en público](/assets/images/help/repository/repo-makepublic.png) -4. Lee las advertencias acerca de convertir un repositorio en público. ![Ventana emergente con información sobre convertir un repositorio privado en público](/assets/images/help/repository/repo-publicconfirm.png) -5. Escribe el nombre del repositorio que deseas convertir en público, por ejemplo `accountname/reponame`. -6. Click **I understand, make this repository public**. - -{% if currentVersion ver_gt "enterprise-server@2.19" %} -### Convertir un repositorio en interno - -{% data reusables.organizations.internal-repos-enterprise %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Under "Danger Zone", next to "Make this repository internal", click **Make internal**. ![Botón para convertir en interno](/assets/images/help/repository/repo-makeinternal.png) -4. Lee las advertencias acerca de convertir un repositorio en interno. ![Ventana emergente de advertencias](/assets/images/help/repository/repo-internalconfirm.png) -5. Escribe el nombre del repositorio que deseas convertir en interno, por ejemplo `accountname/reponame`. -6. Click **I understand, make this repository internal**. -{% endif %} - -{% endif %} - -### Leer más -- "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)" diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/transferring-a-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/transferring-a-repository.md deleted file mode 100644 index 99199ea0cb..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/transferring-a-repository.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Transferir un repositorio -intro: Puedes transferir repositorios a otros usuarios o cuentas de organización. -redirect_from: - - /articles/about-repository-transfers/ - - /move-a-repo/ - - /moving-a-repo/ - - /articles/what-is-transferred-with-a-repository/ - - /articles/what-is-transferred-with-a-repo/ - - /articles/how-to-transfer-a-repo/ - - /articles/how-to-transfer-a-repository/ - - /articles/transferring-a-repository-owned-by-your-personal-account/ - - /articles/transferring-a-repository-owned-by-your-organization/ - - /articles/transferring-a-repository - - /github/administering-a-repository/transferring-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### Acerca de las transferencias de repositorios - -Cuando transfieres un repositorio a un propietario nuevo, puede administrar de inmediato los contenidos, propuestas, solicitudes de extracción, lanzamientos, tableros de proyecto y parámetros del repositorio. - -Requisitos previos para las transferencias de repositorios: {% if currentVersion == "free-pro-team@latest" %} -- Cuando le transfieras un repositorio que te pertenece a otra cuenta de usuario, el propietario recibirá un correo electrónico de confirmación. El correo electrónico de confirmación incluye instrucciones para aceptar la transferencia. Si el propietario nuevo no acepta la transferencia en el transcurso de un día, la invitación se vencerá.{% endif %} -- Para transferirle un repositorio que te pertenece a una organización, debes tener permiso para crear un repositorio en la organización de destino. -- La cuenta objetivo no debe tener un repositorio con el mismo nombre o una bifurcación en la misma red. -- El propietario original del repositorio se agrega como colaborador en el repositorio transferido. Los demás colaboradores del repositorio transferido permanecen intactos. -- Las bifurcaciones privadas no se pueden transferir. - -{% if currentVersion == "free-pro-team@latest" %}Si transfieres un repositorio privado a una cuenta de usuario u organización de {% data variables.product.prodname_free_user %}, éste perderá acceso a características como ramas protegidas y {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %} - -#### ¿Qué se transfiere con un repositorio? - -Cuando transfieres un repositorio, también se transfieren sus propuestas, solicitudes de extracción, wiki, estrellas y observadores. Si el repositorio transferido contiene webhooks, servicios, secretos, o llaves de implementación, estos permanecerán asociados después de que se complete la transferencia. Se preserva la información de Git acerca de las confirmaciones, incluidas las contribuciones. Asimismo: - -- Si el repositorio transferido es una bifurcación, sigue asociado con el repositorio ascendente. -- Si el repositorio transferido tiene alguna bifurcación, esas bifurcaciones seguirán asociadas al repositorio después de que se complete la transferencia. -- Si el repositorio transferido utiliza {% data variables.large_files.product_name_long %}, todos {% data variables.large_files.product_name_short %} los objetos se mueven automáticamente. Esta transferencia ocurre en segundo plano; por lo tanto, si tienes una gran cantidad de {% data variables.large_files.product_name_short %} objetos o si los {% data variables.large_files.product_name_short %} objetos en sí mismos son grandes, puede llevar algún tiempo que se complete la transferencia.{% if currentVersion == "free-pro-team@latest" %} Antes de transferir un repositorio que utilice {% data variables.large_files.product_name_short %}, asegúrate de que la cuenta receptora tenga suficientes paquetes de datos para almacenar los {% data variables.large_files.product_name_short %} objetos que moverás. Para obtener más información acerca de agregar almacenamiento para las cuentas de usuario, consulta "[Subir de categoría {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)".{% endif %} -- Cuando se transfiere un repositorio entre dos cuentas de usuario, las asignaciones de propuestas se dejan intactas. Cuando transfieres un repositorio desde una cuenta de usuario a una organización, las propuestas asignadas a los miembros de la organización permanecen intactas, y todos los demás asignatarios de propuestas se eliminan. Solo los propietarios de la organización están autorizados a crear asignaciones de propuestas nuevas. Cuando transfieres un repositorio desde una organización a una cuenta de usuario, solo se mantienen las propuestas asignadas al propietario del repositorio, y se eliminan todos los demás asignatarios de propuestas. -- Si el repositorio transferido contiene un {% data variables.product.prodname_pages %} sitio, se redirigen los enlaces al repositorio de Git en la web y a través de la actividad de Git. Sin embargo, no redirigimos {% data variables.product.prodname_pages %} asociadas al repositorio. -- Todos los enlaces a la ubicación anterior del repositorio se redirigen de manera automática hacia la ubicación nueva. Cuando utilices `git clone`, `git fetch` o `git push` en un repositorio transferido, estos comando redirigirán a la ubicación del repositorio o URL nueva. Sin embargo, para evitar confusiones, es altamente recomendable actualizar cualquier clon local existente para que apunte a la nueva URL del repositorio. Puedes hacerlo utilizando `git remote` en la línea de comando: - - ```shell - $ git remote set-url origin new_url - ``` - -Para obtener más información, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)". - -#### Transferencias de repositorios y organizaciones - -Para transferir repositorios a una organización, debes tener permisos de creación de repositorios en la organización receptora. Si los propietarios de la organización inhabilitaron la creación de repositorios para los miembros de la organización, solo los propietarios de la organización pueden transferir repositorios hacia fuera o dentro de la organización. - -Una vez que se transfiere un repositorio a una organización, los parámetros de permiso del repositorio de la organización predeterminados y los privilegios de membresía predeterminados se aplicarán al repositorio transferido. - -### Transferir un repositorio que le pertenece a tu cuenta de usuario - -Puedes transferir tu repositorio a cualquier cuenta de usuario que acepte la transferencia de tu repositorio. Cuando se transfiere un repositorio entre dos cuentas de usuario, el propietario del repositorio original y los colaboradores se agregan automáticamente como colaboradores al repositorio nuevo. - -{% if currentVersion == "free-pro-team@latest" %}Si publicaste un {% data variables.product.prodname_pages %} sitio en un repositorio privado y agregaste un dominio personalizado, antes de transferir el repositorio, puede que quieras eliminar o actualizar tus registros DNS para evitar un riesgo de adquisición del dominio. 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)".{% endif %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.transfer-repository-steps %} - -### Transferir un repositorio que le pertenece a tu organización - -Si tienes permisos de propietario en una organización o permisos de administración para uno de sus repositorios, puedes transferir un repositorio que le pertenece a tu organización a tu cuenta de usuario o a otra organización. - -1. Inicia sesión en tu cuenta de usuario que tiene permisos de administración o de propietario en la organización a la que le pertenece el repositorio. -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.transfer-repository-steps %} diff --git a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/viewing-deployment-activity-for-your-repository.md b/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/viewing-deployment-activity-for-your-repository.md deleted file mode 100644 index 18f82b3293..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/managing-repository-settings/viewing-deployment-activity-for-your-repository.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Ver la actividad de implementación de tu repositorio -intro: Puedes ver la información acerca de las implementaciones de tu repositorio completo o de una solicitud de extracción específica. -redirect_from: - - /articles/viewing-deployment-activity-for-your-repository - - /github/administering-a-repository/viewing-deployment-activity-for-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% note %} - -**Nota:** el tablero de implementaciones está actualmente en beta y es susceptible a cambios. - -{% endnote %} - -Las personas con acceso de lectura a un repositorio pueden ver un resumen de todas las implementaciones actuales y un registro de la actividad de implementación pasada, si el flujo de trabajo de implementación del repositorio está integrado con {% data variables.product.product_name %} a través de las implementaciones API o una app de [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/category/deployment). Para obtener más información, consulta la sección "[Despliegues](/v3/repos/deployments/)". - -También puedes ver información de implementación en la pestaña "Conversation" (Conversación) de una solicitud de extracción. - -### Ver el tablero de implementaciones - -{% data reusables.repositories.navigate-to-repo %} -2. Arriba de la lista de archivos, haz clic en **Environments (Entornos)**. ![Entornos por encima 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-XL/content/github/administering-a-repository/releasing-projects-on-github/about-releases.md b/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/about-releases.md deleted file mode 100644 index 21d6577ccc..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/about-releases.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Acerca de los lanzamientos -intro: 'Puedes crear un lanzamiento para empaquetar software, junto con notas de lanzamiento y enlaces a archivos binarios, para que los usen otras personas.' -redirect_from: - - /articles/downloading-files-from-the-command-line/ - - /articles/downloading-files-with-curl/ - - /articles/about-releases - - /articles/getting-the-download-count-for-your-releases - - /github/administering-a-repository/getting-the-download-count-for-your-releases - - /github/administering-a-repository/about-releases -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### Acerca de los lanzamientos - -![Un resumen de los lanzamientos](/assets/images/help/releases/releases-overview.png) - -Los lanzamientos son iteraciones de software desplegable que puedes empaquetar y poner a disposición de una audiencia más amplia para su descarga y uso. - -Los lanzamientos se basan en las [etiquetas Git](https://git-scm.com/book/en/Git-Basics-Tagging), que marcan un punto específico en el historial de tu repositorio. Una fecha de etiqueta puede ser diferente a una fecha de lanzamiento ya que ambas pueden crearse en momentos diferentes. Para obtener más información sobre cómo visualizar tus etiquetas existentes, consulta "[Ver las etiquetas y lanzamientos de tu repositorio](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)." - -Puedes recibir notificaciones cuando se publican nuevos lanzamientos en un repositorio sin recibir notificaciones sobre otras actualizaciones del repositorio. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Observar y dejar de observar los lanzamientos de un repositorio](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}". - -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)." - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -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 %} - -{% if currentVersion == "free-pro-team@latest" %} -Si un lanzamiento arregla una vulnerabilidad de seguridad, deberás publicar una asesoría de seguridad en tu repositorio. {% data variables.product.prodname_dotcom %} revisa cada asesoría de seguridad publicada y podria utilizarla para enviar alertas de {% data variables.product.prodname_dependabot_short %} a los repositorios afectados. Para obtener más información, consulta la sección "[Acerca de las Asesorías de Seguridad de GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)". - -Puedes ver la pestaña de **Dependientes** de la gráfica de dependientes para ver qué repositorios y paquetes dependen del código en tu repositorio, y podrían entonces verse afectados con un nuevo lanzamiento. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". -{% endif %} - -También puedes usar la API de releases para recopilar información, como la cantidad de veces que las personas descargan un recurso de lanzamiento. Para obtener más información, consulta "[Releases](/v3/repos/releases/)." - -{% if currentVersion == "free-pro-team@latest" %} -### Cuotas de ancho de banda y de almacenamiento - - Cada archivo incluido en un lanzamiento debe ser de menos de {% data variables.large_files.max_file_size %}. No hay un límite para el tamaño total de un lanzamiento, ni para el uso de ancho de banda. - -{% endif %} diff --git a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md b/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md deleted file mode 100644 index 165de3280b..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Automatización de los formularios de lanzamiento con parámetros de consulta -intro: 'Para crear lanzamientos al completar automáticamente el nuevo formulario de lanzamiento con información personalizada, puedes agregar los parámetros de consulta a la URL para la página del formulario de lanzamiento.' -redirect_from: - - /articles/automation-for-release-forms-with-query-parameters - - /github/administering-a-repository/automation-for-release-forms-with-query-parameters -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Los parámetros de consulta son partes opcionales de una URL que puedes personalizar para compartir una vista de página web específica, como los resultados de filtro de búsqueda, una plantilla de propuestas o la página del formulario de lanzamiento en {% data variables.product.prodname_dotcom %}. Para crear tus propios parámetros de consulta, debes hacer coincidir el par de clave y valor. - -Debes tener los permisos adecuados para cualquier acción para usar el parámetro de consulta equivalente. Por ejemplo, debes tener permiso para crear lanzamientos para completar previamente los formularios de lanzamiento. Para obtener más información, consulta "[Administrar lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)." - -Si creas una URL no válida usando los parámetros de consulta o si no tienen los permisos adecuados, la URL devolverá una página de error 404. - -### Parámetros de consulta admitidos - -| Parámetro de consulta | Ejemplo | -| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `etiqueta` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1` create un lanzamiento en función de la etiqueta denominada "v1.0.1". | -| `destino` | `https://github.com/octo-org/octo-repo/releases/new?target=release-1.0.1` create un lanzamiento en función de la última confirmación a la rama "release-1.0.1". | -| `título` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1&title=octo-1.0.1` crea un lanzamiento denominado "octo-1.0.1" basado en una etiqueta denominada "v1.0.1". | -| `cuerpo` | `https://github.com/octo-org/octo-repo/releases/new?body=Adds+widgets+support` crea un lanzamiento con la descripción "Adds widget support" (Agrega soporte de widget) en el cuerpo del lanzamiento. | -| `lanzamiento previo` | `https://github.com/octo-org/octo-repo/releases/new?prerelease=1` crea un lanzamiento que será identificado como listo para no producción. | - -### Leer más - -- "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" diff --git a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/comparing-releases.md b/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/comparing-releases.md deleted file mode 100644 index e260466fd0..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/comparing-releases.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Comparar lanzamientos -intro: Puedes comparar etiquetas de lanzamiento para ver los cambios en tu repositorio entre diferentes lanzamientos. -permissions: People with read access to a repository can view and compare releases. -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Repositories -redirect_from: - - /github/administering-a-repository/comparing-releases ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.releases %} -3. Da clic en **Comparar** a un costado del lanzamiento que deseas utilizar como tu base. ![Menú de comparación de etiquetas de lanzamiento](/assets/images/help/releases/compare-tags-menu.png) -4. Utiliza el menú desplegable "Comparar" y selecciona las etiquetas que quieras comparar. ![Opciones del menú de comparación de etiquetas de lanzamiento](/assets/images/help/releases/compare-tags-menu-options.png) diff --git a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/index.md b/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/index.md deleted file mode 100644 index 4f5f6f9675..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Lanzar proyectos en GitHub -intro: 'Puedes crear un lanzamiento para consolidad software, notas de lanzamiento y archivos binarios para que los demás lo descarguen.' -redirect_from: - - /categories/85/articles/ - - /categories/releases/ -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /about-releases - - /managing-releases-in-a-repository - - /viewing-your-repositorys-releases-and-tags - - /linking-to-releases - - /comparing-releases - - /automation-for-release-forms-with-query-parameters ---- - diff --git a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/linking-to-releases.md b/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/linking-to-releases.md deleted file mode 100644 index acf4b9c557..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/linking-to-releases.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Vincular a lanzamientos -intro: Puedes compartir cada lanzamiento que crees en GitHub con una URL única. -redirect_from: - - /articles/linking-to-releases - - /github/administering-a-repository/linking-to-releases -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.releases %} -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) - -Para enlazarlo directamente con una descarga de tu último activo de lanzamiento, enlaza a `/owner/name/releases/latest/download/nombre-de-activo.zip`. diff --git a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository.md deleted file mode 100644 index 5e954d9118..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Administrar lanzamientos en un repositorio -intro: Puedes crear lanzamientos que desees poner en conjunto y entregar iteraciones de un proyecto a los usuarios. -redirect_from: - - /articles/creating-releases - - /articles/listing-and-editing-releases/ - - /articles/editing-and-deleting-releases - - /articles/managing-releases-in-a-repository - - /github/administering-a-repository/creating-releases - - /github/administering-a-repository/editing-and-deleting-releases - - /github/administering-a-repository/managing-releases-in-a-repository -permissions: 'Repository collaborators and people with write access to a repository can create, edit, and delete a release.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### Acerca de la administración de lanzamientos - -También puedes publicar una acción para 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 %}](/actions/creating-actions/publishing-actions-in-github-marketplace)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -Puedes 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 .tar que cree {% data variables.product.product_name %} 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 %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also manage releases using the {% data variables.product.prodname_cli %}. For more information, see "[`gh release`](https://cli.github.com/manual/gh_release)" in the {% data variables.product.prodname_cli %} documentation. - -{% endtip %} -{% endif %} - -### Crear un lanzamiento - -{% 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. Escribe un número de versión para tu lanzamiento. Las versiones se basan en [etiquetas Git](https://git-scm.com/book/en/Git-Basics-Tagging). Te recomendamos darles a las etiquetas nombres que se adapten al [control semántico de versiones](http://semver.org/). ![Versión de lanzamientos con etiquetas](/assets/images/help/releases/releases-tag-version.png) -5. Utiliza el menú desplegable para seleccionar la rama que contiene el proyecto que quieres lanzar. ![Rama de lanzamientos con etiquetas](/assets/images/help/releases/releases-tag-branch.png) -6. Escribe un título y una descripción para tu lanzamiento. ![Descripción de lanzamientos](/assets/images/help/releases/releases_description.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) -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) - -También puedes crear un lanzamiento automáticamente desde la línea de comandos o en un script. Para obtener más información, consulta la sección "[Lanzamientos](/v3/repos/releases/#create-a-release)." - -### Editar un lanzamiento - -{% 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. Edita los detalles del lanzamiento en el formato, después, da clic en **Actualizar lanzamiento**. ![Actualizar un lanzamiento](/assets/images/help/releases/update-release.png) - -### Eliminar un lanzamiento - -Debes eliminar todos los archivos binarios adjuntos a un lanzamiento antes de poder eliminarlo. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.releases %} -3. Da clic en el nombre del lanzamiento que quieres eliminar. ![Enlace para ver el lanzamiento](/assets/images/help/releases/release-name-link.png) -4. En la esquina superior derecha de la página, haz clic en **Eliminar**. ![Botón para eliminar lanzamiento](/assets/images/help/releases/delete-release.png) -5. Da clic en **Eliminar este lanzamiento**. ![Confirmar la eliminación del lanzamiento](/assets/images/help/releases/confirm-delete-release.png) diff --git a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md deleted file mode 100644 index f57a42da5b..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Visualizar los lanzamientos y etiquetas de tu repositorio -intro: 'Puedes ver el historial cronológico de tu repositorio por lanzamiento, nombre o número de versión de la etiqueta.' -redirect_from: - - /articles/working-with-tags/ - - /articles/viewing-your-repositorys-tags - - /github/administering-a-repository/viewing-your-repositorys-tags - - /github/administering-a-repository/viewing-your-repositorys-releases-and-tags -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also view a release using the {% data variables.product.prodname_cli %}. For more information, see "[`gh release view`](https://cli.github.com/manual/gh_release_view)" in the {% data variables.product.prodname_cli %} documentation. - -{% endtip %} -{% endif %} - -### Visualizar lanzamientos - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.releases %} -2. En la parte superior de la página de lanzamientos, da clic en **Lanzamientos**. - -### Visualizar etiquetas - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.releases %} -2. En la parte superior de la página de lanzamiento, haz clic en **Tags** (Etiqueta). ![Página de etiquetas](/assets/images/help/releases/tags-list.png) - -### Leer más - -- "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/about-secret-scanning.md b/translations/es-XL/content/github/administering-a-repository/securing-your-repository/about-secret-scanning.md deleted file mode 100644 index f16e72af49..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/about-secret-scanning.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: Acerca del escaneo de secretos -intro: '{% data variables.product.product_name %} escanea repositorios para encontrar tipos conocidos de secretos para prevenir el uso fraudulento de aquellos que se confirmaron por accidente.' -redirect_from: - - /github/administering-a-repository/about-token-scanning - - /articles/about-token-scanning - - /articles/about-token-scanning-for-private-repositories - - /github/administering-a-repository/about-secret-scanning -versions: - free-pro-team: '*' ---- -Si tu proyecto se comunica con un servicio externo, puedes utilizar un token o llave privada para autenticación. Los tokens y llaves privadas son ejemplos de secretos que puede emitir un proveedor de servicios. Si registras un secreto en un repositorio, cualquiera que tenga acceso de lectura al mismo puede utilizarlo para acceder al servicio externo con tus privilegios. Te recomendamos que almacenes los secretos en una ubicación dedicada y segura fuera del repositorio de tu proyecto. - -Si alguien registra un secreto de un socio de {% data variables.product.company_short %} en un repositorio público o privado, {% data variables.product.prodname_secret_scanning %} puede detectarlo y ayudarte a mitigar el impacto de esta fuga. - -Los proveedores de servicio pueden asociarse con {% data variables.product.company_short %} para proporcionar sus formatos de secreto para el escaneo de los mismos. Para obtener más información, consulta "[Escaneo de secretos](/partnerships/secret-scanning)." - -### Acerca de {% data variables.product.prodname_secret_scanning %} para repositorios públicos - -Cuando subes información a un repositorio público, {% data variables.product.product_name %} escanea el contenido de las confirmaciones para los secretos. Si cambias un repositorio de privado a público, {% data variables.product.product_name %} escanea todo el repositorio en busca de secretos. - -Cuando {% data variables.product.prodname_secret_scanning %} detecta un conjunto de credenciales, notificamos al proveedor del servicio que emitió el secreto. El proveedor del servicio valida la credencial y luego decide si debería retirar el secreto, emitir uno nuevo, o contactarte directamente, lo cual dependerá de los riesgos asociados a ti o a dicho proveedor. - -Actualmente, {% data variables.product.product_name %} escanea los repositorios públicos en busca de secretos emitidos por los siguientes proveedores de servicios. - -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Datadog -- Discord -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- MessageBird -- npm -- NuGet -- Palantir -- Plivo -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio - -### Acerca de {% data variables.product.prodname_secret_scanning %} para repositorios privados - -{% data reusables.secret-scanning.beta %} - -Cuando subes confirmaciones en un repositorio privado que tiene habilitado {% data variables.product.prodname_secret_scanning %}, {% data variables.product.product_name %} escanea el contenido de las confirmaciones en busca de secretos. - -Cuando {% data variables.product.prodname_secret_scanning %} detecta un secreto en un repositorio privado, {% data variables.product.prodname_dotcom %} envía alertas. - -- {% data variables.product.prodname_dotcom %} envía una alerta por correo electrónico a los administradores del repositorio y a los propietarios de la organización. - -- {% data variables.product.prodname_dotcom %} muestra una alerta en el repositorio. Para obtener más información, consulta la sección "[Administrar alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)". - -Actualmente, {% data variables.product.product_name %} escanea los repositorios privados en busca de secretos emitidos por los siguientes proveedores de servicios. - -- Adafruit -- Alibaba Cloud -- Amazon Web Services (AWS) -- Atlassian -- Azure -- Clojars -- CloudBees CodeShip -- Databricks -- Discord -- Dropbox -- Dynatrace -- Finicity -- Frame.io -- GitHub -- GoCardless -- Google Cloud -- Hashicorp Terraform -- Hubspot -- Mailchimp -- Mailgun -- npm -- NuGet -- Palantir -- Postman -- Proctorio -- Pulumi -- Samsara -- Shopify -- Slack -- SSLMate -- Stripe -- Tencent Cloud -- Twilio - -{% note %} - -**Nota:**{% data variables.product.prodname_secret_scanning_caps %} no permite actualmente que definas tus propios parámetros para detectar secretos. - -{% endnote %} - -### Leer más - -- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" -- "[Preservar la seguridad de tu cuenta y tus datos](/github/authenticating-to-github/keeping-your-account-and-data-secure)" diff --git a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/about-securing-your-repository.md b/translations/es-XL/content/github/administering-a-repository/securing-your-repository/about-securing-your-repository.md deleted file mode 100644 index c6bef4cbe4..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/about-securing-your-repository.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Acerca de asegurar tu repositorio -intro: '{% data variables.product.product_name %} proporciona varias formas para que puedas mantener tu repositorio seguro.' -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/about-securing-your-repository ---- -### Configurar tu repositorio de forma segura - -El primer paso para asegurar un repositorio es configurar quién puede ver y modificar tu código. Para obtener más información, consulta la sección "[Administrar la configuración de los repositorios](/github/administering-a-repository/managing-repository-settings)". - -### Asegurar tu repositorio - -{% data variables.product.prodname_dotcom %} cuenta con un conjunto de características cada vez mayor que te ayuda a mantener tu código seguro. Puedes encontrarlas en la pestaña de **Seguridad** de tu repositorio. - -- **Política de seguridad** - - Facilítale a las personas el poder reportar de forma confidencial las vulnerabilidades de seguridad que hayan encontrado en tu repositorio. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository)". - -- **Asesorías de seguridad** - - Debate en privado y arregla las vulnerabilidades de seguridad en el código de tu repositorio. Puedes entonces publicar la asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad en cuestión y alentarlos a mejorar la versión que tienen actualmente. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". - -- **Alertas del {% data variables.product.prodname_dependabot_short %}** - - Ver alertas acerca de las dependencias de las cuales se sabe contienen vulnerabilidades de seguridad y elige si se generarán automáticamente las solicitudes de extracción para actualizar dichas dependencias. Para obtener más información, consulta las secciones "[Visualizar y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" y "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)". - -- **Alertas de {% data variables.product.prodname_code_scanning_capc %}** - - Detecta automáticamente las vulnerabilidades de seguridad y los errores de código en el código nuevo o modificado. Se resaltan los problemas potenciales, con información detallada, lo cual te permite arreglar el código antes de que se fusione en tu rama predeterminada. Para obtener más información, consulta la sección "[Acerca del escaneo de código"](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning). - -- **Secretos detectados** - - Ver cualquier secreto que {% data variables.product.prodname_dotcom %} haya encontrado en tu código. Deberías tratar a los tokens o las credenciales que se hayan registrado en tu repositorio como puestos en riesgo. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). - -### Explorar las dependencias -La gráfica de dependencias de {% data variables.product.prodname_dotcom %} te permite explorar: - -* Ecosistemas y paquetes de los cuales depende tu repositorio -* Repositorios y paquetes que dependen de tu repositorio - -Debes habilitar la gráfica de dependencias antes de que {% data variables.product.prodname_dotcom %} pueda generar alertas del {% data variables.product.prodname_dependabot_short %} con vulnerabilidades de seguridad. - -Puedes encontrar la gráfica de dependencias en lapestaña de **Perspectivas** para tu repositorio. 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)". diff --git a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/configuring-secret-scanning-for-private-repositories.md b/translations/es-XL/content/github/administering-a-repository/securing-your-repository/configuring-secret-scanning-for-private-repositories.md deleted file mode 100644 index effda8cca4..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/configuring-secret-scanning-for-private-repositories.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Configurar el escaneo de secretos para repositorios privados -intro: 'Puedes configurar la manera en que {% data variables.product.product_name %} escanea tus repositorios privados en busca de secretos.' -permissions: 'Las personas con permisos administrativos en un repositorio privado pueden habilitar {% data variables.product.prodname_secret_scanning %} para el repositorio.' -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories ---- -{% data reusables.secret-scanning.beta %} - -### Habilitar {% data variables.product.prodname_secret_scanning %} para repositorios privados - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-security-and-analysis %} -4. A la derecha de "Escaneo de secretos", da clic en **Habilitar**. ![Habilitar el escaneo de secretos para tu repositorio](/assets/images/help/repository/enable-secret-scanning.png) - -### Excluir alertas de {% data variables.product.prodname_secret_scanning %} en repositorios privados - -Puedes utilizar un archivo *secret_scanning.yml* para excluir los directorios de {% data variables.product.prodname_secret_scanning %}. Por ejemplo, puedes excluir directorios que contengan pruebas o contenido generado aleatoriamente. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. En el campo de nombre del archivo, teclea *.github/secret_scanning.yml*. -4. Debajo de **Editar nuevo archivo**, teclea `paths-ignore:` seguido por las rutas que quieras excluir de {% data variables.product.prodname_secret_scanning %}. - ``` yaml - paths-ignore: - - "foo/bar/*.js" - ``` - - Puedes utilizar caracteres especiales, tales como `*` para filtrar las rutas. Para obtener más información acerca de filtrar las rutas, consulta la sección "[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)". - - {% note %} - - **Notas:** - - Si hay más de 1,000 entradas en `paths-ignore`, {% data variables.product.prodname_secret_scanning %} solo excluirá de los escaneos a los primeros 1,000 directorios. - - Si *secret_scanning.yml* es mayor a 1 MB, {% data variables.product.prodname_secret_scanning %} ignorará todo el archivo. - - {% endnote %} - -También puedes ignorar alertas individuales de {% data variables.product.prodname_secret_scanning %}. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-alerts)". - -### Leer más - -- "[Administrar el {% data variables.product.prodname_secret_scanning %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization)" diff --git a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/index.md b/translations/es-XL/content/github/administering-a-repository/securing-your-repository/index.md deleted file mode 100644 index df917e5f9b..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Asegurar tu repositorio -intro: 'Asegurar las funciones como {% data variables.product.prodname_secret_scanning %} protegen los datos de tu repositorio.' -redirect_from: - - /articles/securing-your-repository -versions: - free-pro-team: '*' - enterprise-server: '>=3.0' - github-ae: '*' -topics: - - Repositories -children: - - /about-securing-your-repository - - /about-secret-scanning - - /configuring-secret-scanning-for-private-repositories - - /managing-alerts-from-secret-scanning - - /managing-security-and-analysis-settings-for-your-repository ---- - diff --git a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/managing-alerts-from-secret-scanning.md b/translations/es-XL/content/github/administering-a-repository/securing-your-repository/managing-alerts-from-secret-scanning.md deleted file mode 100644 index a049987b54..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/managing-alerts-from-secret-scanning.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Administrar las alertas del escaneo de secretos -intro: Puedes ver y cerrar las alertas para los secretos que se hayan revisado en tu repositorio. -versions: - free-pro-team: '*' -redirect_from: - - /github/administering-a-repository/managing-alerts-from-secret-scanning ---- -{% data reusables.secret-scanning.beta %} - -### Administrar alertas - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -3. En la barra lateral izquierda, da clic en **Secretos detectados**. ![pestaña "Secretos detectados"](/assets/images/help/repository/sidebar-secrets.png) -4. Debajo de "Escaneo de secretos" da clic en la alerta que quieras ver. ![Lista de alertas del escaneo de secretos](/assets/images/help/repository/secret-scanning-click-alert.png) -5. Opcionalmente, usa el menú desplegable de "Resolver" y da clic en una razón para resolver una alerta. ![Menú desplegable para resolver una alerta del escaneo de secretos](/assets/images/help/repository/secret-scanning-resolve-alert.png) - -### Asegurar los secretos en riesgo - -Cuando un secreto se haya confirmado en un repositorio, deberás considerarlo en riesgo. {% data variables.product.prodname_dotcom %} recomienda tomar las siguientes acciones para los secretos puestos en riesgo: - -- Para un token de acceso personal de {% data variables.product.prodname_dotcom %} comprometido, elimina el token comprometido, crea un nuevo token y actualiza todo servicio que use el token antiguo. Para obtener más información, consulta la sección "[Crear un token de acceso personal para la línea de comandos](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". -- Para todos los demás secretos, verifica primero que aquellos que se hayan confirmado en {% data variables.product.prodname_dotcom %} sean válidos. De ser así, crea un secreto nuevo, actualiza cualquier servicio que utilice el secreto anterior, y luego bórralo. diff --git a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/es-XL/content/github/administering-a-repository/securing-your-repository/managing-security-and-analysis-settings-for-your-repository.md deleted file mode 100644 index e9c46a77dc..0000000000 --- a/translations/es-XL/content/github/administering-a-repository/securing-your-repository/managing-security-and-analysis-settings-for-your-repository.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Administrar la configuración de seguridad y análisis para tu repositorio -intro: 'Puedes controlar las características que dan seguridad y analizan tu código en tu proyecto dentro de {% data variables.product.prodname_dotcom %}.' -permissions: People with admin permissions to a repository can manage security and analysis settings for the repository. -redirect_from: - - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories/ - - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories/ - - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization - - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization - - /github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository -versions: - free-pro-team: '*' - enterprise-server: '>=3.0' - github-ae: '*' -topics: - - Repositories ---- -### Habilitar o inhabilitar las características de seguridad y análisis - -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} - -{% data reusables.security.security-and-analysis-features-enable-read-only %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-security-and-analysis %} -4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) - -### Otorgar acceso a {% data variables.product.prodname_dependabot_alerts %} - -Después de que habilitas las {% data variables.product.prodname_dependabot_alerts %} para un repositorio en una organización, los propietarios de ésta y los administradores de los repositorios pueden ver las alertas predeterminadamente. Puedes dar acceso a equipos y personas adicionales para las alertas de un repositorio. - -{% note %} - -Organization owners and repository administrators can only grant access to view {% data variables.product.prodname_dependabot_alerts %} to people or teams who have write access to the repo. - -{% endnote %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-security-and-analysis %} -4. Debajo de "Alertas del Dependabot", en el campo de búsqueda, comienza a teclear el nombre de la persona o equipo que quieres encontrar, y luego da clic en el nombre que quieras de entre la lista de coincidencias. ![Campo de búsqueda para otorgar a las personas o equipos acceso a las alertas del Dependabot](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png) -5. Haz clic en **Guardar cambios**. ![Botón de "Guardar cambios" para los cambios en la configuración de alertas del Dependabot](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png) - -### Eliminar el acceso a {% data variables.product.prodname_dependabot_alerts %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-security-and-analysis %} -4. Debajo de "Alertas del Dependabot", a la derecha de la persona o equipo cuyo acceso quieras eliminar, da clic en el {% octicon "x" aria-label="X symbol" %}. ![Botón de "x" para eliminar el acceso de alguien a las alertas del Dependabot de tu repositorio](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png) - -### Leer más - -- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" -- "[Administrar la seguridad y la configuración de análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" diff --git a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md deleted file mode 100644 index 6e7e2dc863..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Acerca de la autenticación con el inicio de sesión único de SAML -intro: 'Puedes acceder a una organización que usa inicio de sesión único (SSO) de SAML mediante la autenticación con un proveedor de identidad (IdP). Para autenticar con la API o Git en la linea de comandos cuando una organización impone SAML SSO, debe autorizar a tu token de acceso personal o llave de SSH.' -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/about-authentication-with-saml-single-sign-on - - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on -versions: - free-pro-team: '*' - github-ae: '*' -topics: - - SSO ---- -{% 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 %}. - -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 %} - -Si te has autenticado recientemente con tu SAML IdP de la organización en tu navegador, estás autorizado automáticamente cuando accedas a la {% data variables.product.prodname_dotcom %} organización que utiliza SAML SSO. Si no te has autenticado recientemente con el SAML IdP de tu organización en tu navegador, debes hacerlo en el SAML IdP antes de acceder a la organización. - -Te debes autenticar frecuentemente con tu SAML IdP para acceder a los recursos de la organización en {% data variables.product.prodname_dotcom %}. Tu IdP especifica la duración de este período de inicio de sesión y, generalmente, es de 24 horas. Este requisito de inicio de sesión periódico limita la duración del acceso y requiere que te vuelvas a identificar para continuar. Puedes ver y administrar tus sesiones SAML activas en tus parámetros de seguridad. Para obtener más información, consulta "[Ver y administrar tus sesiones de SAML activas](/articles/viewing-and-managing-your-active-saml-sessions)". - -Para usar la API o Git en la línea de comandos para acceder a contenido protegido en una organización que usa SAML SSO, necesitarás usar un token de acceso personal autorizado a través de HTTPS o una clave SSH autorizada. Los tokens de acceso {% data variables.product.prodname_oauth_app %} están autorizados por defecto. - -Si no tienes un token de acceso personal ni una clave SSH, puedes crear un token de acceso personal para la línea de comandos o generar una clave SSH nueva. 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)" o "[Generar una nueva llave SSH y añadirla al agente de ssh](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". - -Para usar un token de acceso personal o una clave SSH nuevos o existentes con una organización que implementa SAML SSO, necesitarás autorizar el token o autorizar la clave SSH para usar con una organización de SAML SSO. Para obtener más información, consulta "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" o "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." - -Debes tener una sesión activa de SAML cada que autorices un {% data variables.product.prodname_oauth_app %}. - -### Leer más - -- "[Acerca de la administración de accesos e identidades con el inicio de sesión único de SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md deleted file mode 100644 index c85931fa58..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Autorizar un token de acceso personal para usar con un inicio de sesión único de SAML -intro: 'Para usar un token de acceso personal con una organización que usa el inicio de sesión único de SAML (SSO), primer debes autorizar el token.' -redirect_from: - - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization/ - - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on - - /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on -versions: - free-pro-team: '*' -topics: - - SSO ---- -Puedes autorizar un token de acceso personal existente, o [crear un nuevo token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token) y luego autorizarlo. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.developer_settings %} -{% data reusables.user_settings.personal_access_tokens %} -3. Junto al token que deseas autorizar, haz clic en **Enable SSO** (Habilitar SSO) o **Disable SSO** (Deshabilitar SSO). ![Botón para autorizar el token SSO](/assets/images/help/settings/sso-allowlist-button.png) -4. Busca la organización para la que deseas autorizar el token de acceso. -4. Click **Authorize**. ![Botón para autorizar el token](/assets/images/help/settings/token-authorize-button.png) - -### Leer más - -- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" -- "[Acerca de la autenticación con inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md deleted file mode 100644 index 7b3fde9950..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Autorizar una clave SSH para usar con un inicio único de SAML -intro: 'Para usar una clave SSH con una organización que usa un inicio de sesión único (SSO) de SAML, primero debes autorizar la clave.' -redirect_from: - - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization/ - - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on - - /github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on -versions: - free-pro-team: '*' -topics: - - SSO ---- -Puedes autorizar una clave SSH existente, o crear una nueva clave SSH, y luego autorizarla. Para más información sobre la creación de una nueva clave SSH, consulta "[Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". - -{% note %} - -**Nota:** Si tu autorización de clave SSH es revocada por una organización, no podrás volver a autorizar la misma clave. Deberás crear una nueva clave SSH y autorizarla. Para más información sobre la creación de una nueva clave SSH, consulta "[Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". - -{% endnote %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -3. Junto a la clave SSH que deseas autorizar, haz clic en **Enable SSO** (Habilitar SSO) o **Disable SSO** (Deshabilitar SSO). ![Botón para autorizar el token SSO](/assets/images/help/settings/ssh-sso-button.png) -4. Busca la organización para la que deseas autorizar la clave SSH. -5. Click **Authorize**. ![Botón para autorizar el token](/assets/images/help/settings/ssh-sso-authorize.png) - -### Leer más - -- "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)" -- "[Acerca de la autenticación con inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/index.md b/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/index.md deleted file mode 100644 index e31a721843..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Autenticación con inicio de sesión único de SAML -intro: 'Puedes autenticar a una organización {% data variables.product.product_name %} con inicio de sesión único (SSO) de SAML y ver tus sesiones activas.' -redirect_from: - - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on/ - - /articles/authenticating-with-saml-single-sign-on -versions: - free-pro-team: '*' - github-ae: '*' -topics: - - SSO -children: - - /about-authentication-with-saml-single-sign-on - - /authorizing-an-ssh-key-for-use-with-saml-single-sign-on - - /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on - - /viewing-and-managing-your-active-saml-sessions ---- - diff --git a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md b/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md deleted file mode 100644 index c889a2b658..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Ver y administrar tus sesiones de SAML activas -intro: Puedes ver y revocar tus sesiones de SAML activas en tus parámetros de seguridad. -redirect_from: - - /articles/viewing-and-managing-your-active-saml-sessions - - /github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions -versions: - free-pro-team: '*' -topics: - - SSO ---- -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -3. Debajo de "Sesiones" puedes ver tus sesiones activas de SAML. ![Lista de sesiones de SAML activas](/assets/images/help/settings/saml-active-sessions.png) -4. Para ver los detalles de la sesión, da clic en **Ver más**. ![Botón para abrir los detalles de la sesión de SAML](/assets/images/help/settings/saml-expand-session-details.png) -5. Para revocar una sesión, da clic en **Revocar SAML**. ![Botón para revocar una sesión de SAML](/assets/images/help/settings/saml-revoke-session.png) - - {% note %} - - **Nota:** Cuando revocas una sesión, puedes eliminar tu autenticación de SAML para esa organización. Para volver a acceder a la organización, tendrás que hacer un inicio de sesión único a través de tu proveedor de identidad. Para obtener más información, consulta "[Acerca de la autenticación con SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". - - {% endnote %} - -### Leer más - -- "[Acerca de la autenticación con SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/about-ssh.md b/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/about-ssh.md deleted file mode 100644 index 449a18649d..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/about-ssh.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Acerca de SSH -intro: 'Usando el protocolo SSH, te puedes conectar y autenticar con servicios y servidores remotos. Con las claves SSH, te puedes conectar con {% data variables.product.product_name %} sin suministrar tu nombre de usuario ni contraseña en cada visita.' -redirect_from: - - /articles/about-ssh - - /github/authenticating-to-github/about-ssh -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Cuando configuras SSH, [generarás una clave SSH y la agregarás al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) y luego [agregarás la clave a tu cuenta de {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account). Al agregar la clave SSH al ssh-agent te aseguras de que tu clave SSH tiene una capa extra de seguridad mediante el uso de una frase de contraseña. Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)". - -{% if currentVersion == "free-pro-team@latest" %}Para usar tu clave SSH con un repositorio propiedad de una organización que usa el inicio de sesión único de SAML, primero necesitarás autorizarla. Para obtener más información, consulta "[Autorizar una clave SSH para usar con una clave de organización único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %} - -Te recomendamos que regularmente [revises tu listado de claves SSH](/articles/reviewing-your-ssh-keys) y revoques cualquiera que no sea válida o que se haya visto comprometida. - -{% if currentVersion == "free-pro-team@latest" %} -Si no has usado tu clave SSH por un año, entonces {% data variables.product.prodname_dotcom %} automáticamente eliminará tu clave SSH inactiva, como medida de seguridad. Para obtener más información, consulta "[Claves SSH eliminadas o faltantes](/articles/deleted-or-missing-ssh-keys)". -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -Si eres miembro de una organización que provee certificados SSH, puedes usar tu certificado para acceder a los repositorios de esa organización sin agregar el certificado a tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta [Acerca de las autoridades de certificación de SSH](/articles/about-ssh-certificate-authorities)". -{% endif %} - -### Leer más - -- "[Comprobar claves SSH existentes](/articles/checking-for-existing-ssh-keys)" -- "[Probar tu conexión SSH](/articles/testing-your-ssh-connection)" -- Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)" -- "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)" -{%- if currentVersion == "free-pro-team@latest" %} -- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" -{%- endif %} diff --git a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md deleted file mode 100644 index f10e33ae07..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -title: Agregar una clave SSH nueva a tu cuenta de GitHub -intro: 'Para configurar tu cuenta de {% data variables.product.product_name %} a fin de usar tu clave SSH nueva (o existente), también deberás agregarla a tu cuenta de {% data variables.product.product_name %}.' -redirect_from: - - /articles/adding-a-new-ssh-key-to-your-github-account - - /github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Antes de agregar una nueva llave GPG a tu cuenta de {% data variables.product.product_name %}, deberías haber: -* [Comprobado tus claves SSH existentes](/articles/checking-for-existing-ssh-keys) -* [Generado una clave SSH nueva y haberla agregado al agente ssh](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) - -Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product.product_name %}, puedes reconfigurar los repositorios locales para usar SSH. Para obtener más información, consulta "[Alternar URL remota de HTTPS a SSH](/articles/changing-a-remote-s-url/#switching-remote-urls-from-https-to-ssh)". - -{% data reusables.ssh.dsa-support %} - -{% mac %} - -1. Copia la clave SSH a tu portapapeles. - - Si tu archivo de clave SSH tiene un nombre diferente al código del ejemplo, modifica el nombre de archivo para que concuerde con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. - - ```shell - $ pbcopy < ~/.ssh/id_rsa.pub - # Copies the contents of the id_rsa.pub file to your clipboard - ``` - - {% tip %} - - **Sugerencia:** Si `pbcopy` no está funcionando, puedes ubicar la carpeta `.ssh` oculta, abrir el archivo en tu editor de texto favorito, y copiarlo en tu portapapeles. - - {% endtip %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) -5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". -6. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) -7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) -{% data reusables.user_settings.sudo-mode-popup %} - -{% endmac %} - -{% windows %} - -1. Copia la clave SSH a tu portapapeles. - - Si tu archivo de clave SSH tiene un nombre diferente al código del ejemplo, modifica el nombre de archivo para que concuerde con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. - - ```shell - $ clip < ~/.ssh/id_rsa.pub - # Copies the contents of the id_rsa.pub file to your clipboard - ``` - - {% tip %} - - **Sugerencia:** Si `clip` no está funcionando, puedes ubicar la carpeta `.shh` oculta, abrir el archivo en tu editor de texto favorito, y copiarlo en tu portapapeles. - - {% endtip %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) -5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". -6. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) -7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) -8. Si se te solicita, confirma tu contraseña {% data variables.product.product_name %}.![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) - -{% endwindows %} - -{% linux %} - -1. Copia la clave SSH a tu portapapeles. - - Si tu archivo de clave SSH tiene un nombre diferente al código del ejemplo, modifica el nombre de archivo para que concuerde con tu configuración actual. Al copiar tu clave, no agregues líneas nuevas o espacios en blanco. - - ```shell - $ sudo apt-get install xclip - # Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`) - - $ xclip -sel clip < ~/.ssh/id_rsa.pub - # Copies the contents of the id_rsa.pub file to your clipboard - ``` - {% tip %} - - **Sugerencia:** Si `xclip` no está funcionando, puedes ubicar la carpeta `.ssh` oculta, abrir el archivo en tu editor de texto favorito, y copiarlo en tu portapapeles. - - {% endtip %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -4. Haz clic en **New SSH key** (Nueva clave SSH) o **Add SSH key** (Agregar clave SSH). ![Botón SSH Key (Clave SSH)](/assets/images/help/settings/ssh-add-ssh-key.png) -5. En el campo "Title" (Título), agrega una etiqueta descriptiva para la clave nueva. Por ejemplo, si estás usando tu Mac personal, es posible que llames a esta tecla "Personal MacBook Air". -6. Copia tu clave en el campo "Key" (Clave).![Campo de llave](/assets/images/help/settings/ssh-key-paste.png) -7. Haz clic en **Add SSH key** (Agregar tecla SSH). ![Botón Add key (Agregar llave)](/assets/images/help/settings/ssh-add-key.png) -8. Si se te solicita, confirma tu contraseña {% data variables.product.product_name %}.![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) - -{% endlinux %} - -{% if currentVersion == "free-pro-team@latest" %} -### Leer más - -- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" -{% endif %} diff --git a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md deleted file mode 100644 index 489f121a51..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Comprobar tus claves SSH existentes -intro: 'Antes de generar una clave SSH, puedes comprobar si tienes alguna clave SSH existente.' -redirect_from: - - /articles/checking-for-existing-ssh-keys - - /github/authenticating-to-github/checking-for-existing-ssh-keys -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -{% data reusables.ssh.dsa-support %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Ingresa `ls -al ~/.ssh` para ver si hay claves SSH presentes: - - ```shell - $ ls -al ~/.ssh - # Lists the files in your .ssh directory, if they exist - ``` -3. Comprueba la lista de directorio para ver si ya tiene una clave SSH pública. Por defecto, los nombres de archivos de llave pública son uno de los siguientes: - - *id_rsa.pub* - - *id_ecdsa.pub* - - *id_ed25519.pub*{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} - - *id_dsa.pub*{% endif %} - -Si no tienes un par de llaves pública y privada, o si no deseas utilizar las que están disponibles para conectarte a{% data variables.product.product_name %}, entonces [genera una llave SSH nueva](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). - -Si ves que ya hay un par de llaves pública y privada listado (por ejemplo*id_rsa.pub* y *id_rsa*) que te gustaría utilizar para conectarte a {% data variables.product.product_name %}, entonces puedes [añadir tu llave SSH al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#adding-your-ssh-key-to-the-ssh-agent). - -{% tip %} - -**Sugerencia:** Si recibes un error que *~/.ssh* no existe, 'no te preocupes! Lo crearemos cuando [generemos una nueva clave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). - -{% endtip %} diff --git a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md deleted file mode 100644 index 78e6e04c67..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: Generar una nueva clave SSH y agregarla al ssh-agent -intro: 'Una vez que has comprobado las claves SSH existentes, puedes generar una nueva clave SSH para usarla para la autenticación y luego agregarla al ssh-agent.' -redirect_from: - - /articles/adding-a-new-ssh-key-to-the-ssh-agent/ - - /articles/generating-a-new-ssh-key/ - - /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent - - /github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Si todavía no tienes una clave SSH, debes [generar una nueva clave SSH](#generating-a-new-ssh-key). Si no estás seguro de si ya tienes una clave SSH, comprueba las [claves existentes](/articles/checking-for-existing-ssh-keys). - -Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, puedes [agregar tu clave al SSH agent](#adding-your-ssh-key-to-the-ssh-agent), que gestiona tus claves SSH y recuerda tu contraseña. - -### Generar una nueva clave SSH - -{% 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 %}. - ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" - ``` - Esto crea una nueva clave ssh usando el correo electrónico proporcionado como etiqueta. - ```shell - > Generating public/private rsa 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_rsa): [Press enter] - ``` - - {% endmac %} - - {% windows %} - - ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_rsa):[Press enter] - ``` - - {% endwindows %} - - {% linux %} - - ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_rsa): [Press enter] - ``` - - {% endlinux %} - -4. Donde se indica, escribe una contraseña segura. Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)". - ```shell - > Enter passphrase (empty for no passphrase): [Type a passphrase] - > Enter same passphrase again: [Type passphrase again] - ``` - -### Agregar tu clave SSH al ssh-agent - -Antes de agregar una nueva clave SSH al ssh-agent para gestionar tus claves, debes haber [comprobado las claves SSH existentes](/articles/checking-for-existing-ssh-keys) y [generado una nueva clave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key). Cuando agregues tu clave SSH al agente, usa el comando macOS `ssh-add` y no una aplicación instalada por [macports](https://www.macports.org/), [homebrew](http://brew.sh/) o alguna otra fuente externa. - -{% mac %} - -1. {% data reusables.command_line.start_ssh_agent %} - -2. Si estás usando macOS Sierra 10.12.2 o una versión posterior, deberás modificar tu archivo `~/.ssh/config` para cargar las claves automáticamente en el ssh-agent y almacenar las contraseñas en tu keychain. - - * Primero, revisa si tu archivo `~/.ssh/config` existe en la ubicación predeterminada. - - ```shell - $ open ~/.ssh/config - > The file /Users/you/.ssh/config does not exist. - ``` - - * Si el archivo no existe, créalo. - - ```shell - $ touch ~/.ssh/config - ``` - - * Abre tu archivo `~/.ssh/config`, posteriormente, modifícalo reemplazando `~/.ssh/id_rsa` si no estás utilizando la ubicación y el nombre para tu llave `id_rsa`. - - ``` - Host * - AddKeysToAgent yes - UseKeychain yes - IdentityFile ~/.ssh/id_rsa - ``` - -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_rsa - ``` - {% note %} - - **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 clave SSH al ssh-agent. - - 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)". - - {% endnote %} - -4. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.windows_git_bash %} - -1. Verifica que el ssh-agent se esté ejecutando. Puedes utilizar las instrucciones de "Autolanzamiento del ssh-agent" que se encuentran en [Trabajar con frases de acceso de las llaves SSH](/articles/working-with-ssh-key-passphrases)" o iniciarlo manualmente: - ```shell - # start the ssh-agent in the background - $ eval $(ssh-agent -s) - > Agent pid 59566 - ``` - -2. Agrega tu llave privada SSH al ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} - {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %} - -3. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) - -{% endwindows %} - -{% linux %} - -1. {% data reusables.command_line.start_ssh_agent %} - -2. Agrega tu llave privada SSH al ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} - {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %} - -3. [Agrega la clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) - -{% endlinux %} - -### Leer más - -- "[Acerca de SSH](/articles/about-ssh)" -- Para obtener más información, consulta "[Trabajar con frases de contraseña de la clave SSH](/articles/working-with-ssh-key-passphrases)" -{%- if currentVersion == "free-pro-team@latest" %} -- "[Autorizar una clave SSH para usar con el inicio de sesión único de SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" -{%- endif %} diff --git a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/index.md b/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/index.md deleted file mode 100644 index 63ce102226..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Conectar a GitHub con SSH -intro: 'Puedes conectarte con {% data variables.product.product_name %} mediante SSH.' -redirect_from: - - /key-setup-redirect/ - - /linux-key-setup/ - - /mac-key-setup/ - - /msysgit-key-setup/ - - /articles/ssh-key-setup/ - - /articles/generating-ssh-keys/ - - /articles/generating-an-ssh-key/ - - /articles/connecting-to-github-with-ssh -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH -children: - - /about-ssh - - /checking-for-existing-ssh-keys - - /generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent - - /adding-a-new-ssh-key-to-your-github-account - - /testing-your-ssh-connection - - /working-with-ssh-key-passphrases ---- - diff --git a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/testing-your-ssh-connection.md b/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/testing-your-ssh-connection.md deleted file mode 100644 index 5756d38fd5..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/testing-your-ssh-connection.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Probar tu conexión SSH -intro: 'Después de haber configurado tu clave SSH y haberla agregado a tu {% data variables.product.product_name %} cuenta, puedes probar tu conexión.' -redirect_from: - - /articles/testing-your-ssh-connection - - /github/authenticating-to-github/testing-your-ssh-connection -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Antes de probar tu conexión SSH, debes haber hecho lo siguiente: -- [Comprobado tus claves SSH existentes](/articles/checking-for-existing-ssh-keys) -- [Generado una clave SSH nueva](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) -- [Agregado una clave SSH nueva a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) - -Cuando pruebes tu conexión, tendrás que autenticar esta acción utilizando tu contraseña, que es la contraseña de clave SSH que ya creaste. Para obtener más información acerca de trabajar con contraseñas de clave SSH, consulta ["Trabajar con contraseñas de clave SSH"](/articles/working-with-ssh-key-passphrases). - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Ingresa lo siguiente: - ```shell - $ ssh -T git@{% data variables.command_line.codeblock %} - # Attempts to ssh to {% data variables.product.product_name %} - ``` - - Puedes ver una advertencia como la siguiente: - - ```shell - > La autenticidad del host '{% data variables.command_line.codeblock %} (DIRECCIÓN IP)' no se puede establecer. - > La clave de huella digital RSA es SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8. - > ¿Estás seguro de que quieres continuar conectado (sí/no)? - ``` - -3. Comprueba que la huella digital del mensaje que ves coincida con uno de los mensajes del paso 2, luego escribe `yes` (sí): - ```shell - > Hi username! You've successfully authenticated, but GitHub does not - > provide shell access. - ``` - - {% linux %} - - Puede que veas el siguiente mensaje de error: - ```shell - ... - El agente admitió una falla para registrarse utilizando la clave. - debug1: No hay más métodos de autenticación para probar. - Permiso denegado (publickey). - ``` - - Se trata de un problema conocido con determinadas distribuciones de Linux. Para obtener más información, consulta ["Error: El agente admitió una falla para registrarse"](/articles/error-agent-admitted-failure-to-sign). - - {% endlinux %} - -4. Comprueba que el mensaje resultante contenga tu nombre de usuario. Si recibes un mensaje de "permiso denegado", consulta ["Error: Permiso denegado (publickey)"](/articles/error-permission-denied-publickey). diff --git a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md deleted file mode 100644 index 0ff15b1cfc..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: Trabajar con contraseñas de clave SSH -intro: Puedes asegurar tus claves SSH y configurar un agente de autenticación para no tener que volver a ingresar tu contraseña cada vez que uses tus claves SSH. -redirect_from: - - /ssh-key-passphrases/ - - /working-with-key-passphrases/ - - /articles/working-with-ssh-key-passphrases - - /github/authenticating-to-github/working-with-ssh-key-passphrases -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Con las claves SSH, si alguien obtiene acceso a tu computadora, también tiene acceso a cada sistema que usa esa clave. Para agregar una capa extra de seguridad, puedes incluir una contraseña a tu clave SSH. Puedes usar `ssh-agent` para guardar tu contraseña de forma segura y no tener que volver a ingresarla. - -### Agregar o cambiar una contraseña - -Puedes cambiar la contraseña por una llave privada existente sin volver a generar el par de claves al escribir el siguiente comando: - -```shell -$ ssh-keygen -p -# Comienza con el proceso de creación de clave SSH -> Enter file in which the key is (/Users/you/.ssh/id_rsa): [Hit enter] -> Key has comment '/Users/you/.ssh/id_rsa' -> Enter new passphrase (empty for no passphrase): [Type new passphrase] -> Enter same passphrase again: [One more time for luck] -> Your identification has been saved with the new passphrase. -``` - -Si tu clave ya tiene una contraseña, se te pedirá que la ingreses antes de que puedas cambiar a una nueva contraseña. - -{% windows %} - -### Auto-lanzamiento `ssh-agent` en Git para Windows - -Puedes ejecutar el `ssh-agent` automáticamente cuando abres el bash o el Git shell. Copia las siguientes líneas y pégalas en tu `~/.perfil` o archivo `~/.bashrc` en Git Shell: - -``` bash -env=~/.ssh/agent.env - -agent_load_env () { test -f "$env" && . "$env" >| /dev/null ; } - -agent_start () { - (umask 077; ssh-agent >| "$env") - . "$env" >| /dev/null ; } - -agent_load_env - -# agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2= agent not running -agent_run_state=$(ssh-add -l >| /dev/null 2>&1; echo $?) - -if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then - agent_start - ssh-add -elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then - ssh-add -fi - -unset env - -if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then - agent_start - ssh-add -elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then - ssh-add -fi - -unset env -``` - -Si tu llave privada no se almacenó en alguna de las ubicaciones predeterminadas (como `~/.ssh/id_rsa`{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} o `~/.ssh/id_dsa`{% endif %}), necesitarás decirle a tu agente de autenticación SSH dónde encontrarla. Para agregar tu clave a ssh-agent, escribe `ssh-add ~/path/to/my_key`. Para obtener más información, consulta "[Generar una nueva clave SSH y agregarla a ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)" - -{% tip %} - -**Sugerencias:** si quieres que `ssh-agent` olvide tu clave luego de un tiempo, puedes configurarlo para que lo haga ejecutando `ssh-add -t `. - -{% endtip %} - -Ahora, cuando ejecutas Git Bash por primera vez, se te pedirá tu contraseña: - -```shell -> Initializing new SSH agent... -> succeeded -> Enter passphrase for /c/Users/you/.ssh/id_rsa: -> Identity added: /c/Users/you/.ssh/id_rsa (/c/Users/you/.ssh/id_rsa) -> Welcome to Git (version 1.6.0.2-preview20080923) -> -> Run 'git help git' to display the help index. -> Run 'git help ' to display help for specific commands. -``` - -El proceso de `ssh-agent` continuará funcionando hasta que cierres sesión, apagues tu computadora o termines el proceso. - -{% endwindows %} - -{% mac %} - -### Guardar tu contraseña en keychain - -En OS X Leopard a través de OS X El Capitan, los siguientes archivos de llave privada predeterminada se manejan automáticamente: - -- *.ssh/id_rsa*{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} -- *.ssh/id_dsa*{% endif %} -- *.ssh/identity* - -La primera vez que usas tu clave, se te pedirá que ingreses tu contraseña. Si eliges guardar la contraseña con tu keychain, no necesitarás ingresarla nuevamente. - -De lo contrario, puedes almacenar tu contraseña en la keychain cuando agregues tu clave a ssh-agent. Para obtener más información, consulta "[Agregar tu clave SSH a ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)." - -{% endmac %} - -### Leer más - -- "[Acerca de SSH](/articles/about-ssh)" diff --git a/translations/es-XL/content/github/authenticating-to-github/index.md b/translations/es-XL/content/github/authenticating-to-github/index.md deleted file mode 100644 index 77f20f3ac9..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/index.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Autenticar a GitHub -shortTitle: Autenticación -intro: 'Mantén tu cuenta y datos seguros con características como autenticación de dos factores, SSH y verificación de firma de confirmación.' -redirect_from: - - /categories/56/articles/ - - /categories/ssh/ - - /mac-verify-ssh/ - - /ssh-issues/ - - /verify-ssh-redirect/ - - /win-verify-ssh/ - - /categories/92/articles/ - - /categories/gpg/ - - /categories/security/ - - /categories/authenticating-to-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - 2FA - - Identity - - Access management - - Usernames - - Device verification -children: - - /keeping-your-account-and-data-secure - - /securing-your-account-with-two-factor-authentication-2fa - - /authenticating-with-saml-single-sign-on - - /connecting-to-github-with-ssh - - /troubleshooting-ssh - - /managing-commit-signature-verification - - /troubleshooting-commit-signature-verification ---- -### Índice - - - - - - - - - - - - diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-anonymized-image-urls.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-anonymized-image-urls.md deleted file mode 100644 index acda63b7a8..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-anonymized-image-urls.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: Acerca de las URL de imágenes anonimizadas -intro: 'Si cargas una imagen a {% data variables.product.product_name %}, la URL de la imagen será modificada para que tu información no se pueda seguir.' -redirect_from: - - /articles/why-do-my-images-have-strange-urls/ - - /articles/about-anonymized-image-urls - - /github/authenticating-to-github/about-anonymized-image-urls -versions: - free-pro-team: '*' -topics: - - Identity - - Access management ---- -Para alojar tus imágenes, {% data variables.product.product_name %} usa el [Camo del proyecto de código abierto](https://github.com/atmos/camo). Camo genera un proxy de URL anónimo para cada imagen que comienza con `https://camo.githubusercontent.com/` y oculta los detalles de tu navegador y la información relacionada de otros usuarios. - -Cualquiera que reciba tu URL de imagen anonimizada, directa o indirectamente, puede ver tu imagen. Para mantener las imágenes confidenciales en privado, limítalas a una red privada o a un servidor que requiera de autenticación en lugar de usar Camo. - -### Solución de problemas con Camo - -En circunstancias excepcionales, las imágenes procesadas mediante Camo podrían no aparecer en {% data variables.product.prodname_dotcom %}. Aquí presentamos algunos pasos que puedes tomar para determinar dónde está el problema. - -{% windows %} - -{% tip %} - -Los usuarios de Windows necesitarán usar PowerShell de Git (que está instalado junto a [{% data variables.product.prodname_desktop %}](https://desktop.github.com/)) o descargar [curl para Windows](http://curl.haxx.se/download.html). - -{% endtip %} - -{% endwindows %} - -#### Una imagen no aparece - -Si una imagen aparece en tu navegador pero no en {% data variables.product.prodname_dotcom %}, puedes intentar solicitar la imagen localmente. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Solicita los encabezados de la imagen usando `curl`. - ```shell - $ curl -I https://www.my-server.com/images/some-image.png - > HTTP/1.1 200 OK - > Date: Fri, 06 Jun 2014 07:27:43 GMT - > Expires: Sun, 06 Jul 2014 07:27:43 GMT - > Content-Type: image/x-png - > Server: Google Frontend - > Content-Length: 6507 - ``` -3. Verifica el valor de `Content-Type`. En este caso, es `image/x-png`. -4. Verifica ese tipo de contenido con [la lista de tipos admitidos por Camo](https://github.com/atmos/camo/blob/master/mime-types.json). - -Si Camo no admite tu tipo de contenido, puedes probar varias acciones: - * Si eres propietario del servidor que aloja la imagen, modifícalo para que devuelva un tipo de contenido correcto para las imágenes. - * Si estás usando un servicio externo para alojar imágenes, comunícate con servicio técnico para ese servicio. - * Realiza una solicitud de extracción para que Camo agregue tu tipo de contenido a la lista. - -#### Una imagen que cambió recientemente no se está actualizando - -Si recientemente modificaste una imagen y aparece en tu navegador pero no en {% data variables.product.prodname_dotcom %}, puedes intentar restablecer la caché de la imagen. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Solicita los encabezados de la imagen usando `curl`. - ```shell - $ curl -I https://www.my-server.com/images/some-image.png - > HTTP/1.1 200 OK - > Expires: Fri, 01 Jan 1984 00:00:00 GMT - > Content-Type: image/png - > Content-Length: 2339 - > Server: Jetty(8.y.z-SNAPSHOT) - ``` - -Verifica el valor de `Cache-Control`. En este ejemplo, no hay `Cache-Control`. En ese caso: - * Si eres propietario del servidor que aloja la imagen, modifícalo para que devuelva un `Cache-Control` de `no-cache` para las imágenes. - * Si estás usando un servicio externo para alojar imágenes, comunícate con servicio técnico para ese servicio. - - Si `Cache-Control` se *configura* como `no-cache`, contacta a {% data variables.contact.contact_support %} o busca ayuda en el {% data variables.contact.community_support_forum %}. - -#### Eliminar una imagen desde la caché de Camo - -Purgar la caché fuerza a cada usuario de {% data variables.product.prodname_dotcom %} a volver a solicitar la imagen, por lo que deberías usarla con mucha prudencia y solo en el caso de que los pasos anteriores no hayan funcionado. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Purga la imagen usando `curl -X PURGE` en la URL de Camo. - ```shell - $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223.... - > {"status": "ok", "id": "216-8675309-1008701"} - ``` - -#### Visualizar imágenes en redes privadas - -Si una imagen está siendo proporcionada desde una red privada o desde un servidor que requiere de autenticación, se puede ver mediante {% data variables.product.prodname_dotcom %}. De hecho, no puede ser vista por ningún usuario sin pedirle que se registre en el servidor. - -Para solucionar esto, mueva la imagen a un servicio que esté disponible públicamente. - -### Leer más - -- "[Imágenes de usuarios de conexiones proxy](https://github.com/blog/1766-proxying-user-images)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github.md deleted file mode 100644 index f9c3cd1599..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Acerca de la autenticación en GitHub -intro: 'Puedes acceder de manera segura a los recursos de tu cuenta si te atutenticas en {% data variables.product.product_name %}, utilizando diferentes credenciales dependiendo de en donde te autenticas.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management -redirect_from: - - /github/authenticating-to-github/about-authentication-to-github ---- -### Acerca de la autenticación en {% data variables.product.prodname_dotcom %} - -Para mantener tu cuenta segura, debes autenticarte antes de que puedas acceder a algunos de los recursos en {% data variables.product.product_name %}. Cuando te autenticas en {% data variables.product.product_name %}, proporcionas o confirmas las credenciales que son específicas para ti y así compruebas de que eres exactamente quien estás declarando ser. - -Puedes acceder a tus recursos en {% data variables.product.product_name %} de muchas maneras: en el buscador, a través de {% data variables.product.prodname_desktop %} o de alguna otra aplicación de escritorio, con la API o a través de la línea de comandos. Cada forma de acceder a {% data variables.product.product_name %} es compatible con diferentes modalidades de autenticación. - -- Usuario y contraseña con autenticación de dos factores -- Token de acceso personal -- Clave SSH - - -### Autenticarte en tu buscador - -Puedes autenticarte en {% data variables.product.product_name %} desde tu bsucador en varias formas. - -- **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) - - Si habilitas la 2FA, también te pediremos que proporciones un código que genera una aplicación en tu dispositivo móvil o que mandes un mensaje de texto (SMS) después de que ingreses tu usuario y contraseña con éxito. Para obtener más información, consulta "[Acceder a {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)". - - Adicionalmente a la autenticación con una aplicación móvil o con un mensaje de texto, puedes agregar opcionalmente un método secundario de autenticación con una llave de seguridad utilizando WebAuthn. Para obtener más información, consulta la sección "[Configurar la autenticación de dos factores utilizando una llave de seguridad](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". - -### Autenticarte con {% data variables.product.prodname_desktop %} - -Puedes autenticarte con {% data variables.product.prodname_desktop %} utilizando tu buscador. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." - -### Autenticarte con la API - -Puedes autenticarte con la API de {% data variables.product.product_name %} de varias formas. - -- **Tokens de acceso personal** - - En situaciones limitadas, tales como cuando se hacen pruebas, puedes utilizar un token de acceso personal para acceder a la API. El utilizar un token de acceso personal te habilita para revocarle el acceso en cualquier momento. 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)". -- **Flujo de aplicaciones Web** - - Para las Apps de OAuth productivas, debes autenticarte utilizando el flujo de las aplicaciones web. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)". -- **GitHub Apps** - - Para las Github Apps productivas, debes autenticarte en nombre de la instalación de la app. Para obtener más información, consulta la sección "[Autenticarse con {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)". - -### Autenticarte con la línea de comandos - -Puedes acceder a los repositorios en {% data variables.product.product_name %} desde la línea de comandos en dos formas, HTTPS y SSH, y ambas tienen una forma diferente para autenticarte. El método para autenticarte se determina con base en si escoges una URL remota de HTTPS o SSH cuando clonas el repositorio. Para obtener más información acerca de en qué forma acceder, consulta la sección "[¿Qué URL remota debería usar?](/github/using-git/which-remote-url-should-i-use)" - -* 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. Cada vez que utilizas 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é con un [asistente de credenciales](/github/using-git/caching-your-github-credentials-in-git). {% data reusables.user_settings.password-authentication-deprecation %} - -* 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. Para utilizar SSH necesitas generar un par de llaves pública/privada de SSH en tu máquina local y agregar la llave pública a tu cuenta de {% data variables.product.product_name %}. 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). Para obtener más información, consulta "[Generar una nueva clave SSH y agregarla a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." - -{% if currentVersion == "free-pro-team@latest" %}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-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md deleted file mode 100644 index f18e62cb00..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Acerca de las direcciones de IP de GitHub -intro: '{% data variables.product.product_name %} proporciona aplicaciones desde varios rangos de dirección IP, que están disponibles usando la API.' -redirect_from: - - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist/ - - /categories/73/articles/ - - /categories/administration/ - - /articles/github-s-ip-addresses/ - - /articles/about-github-s-ip-addresses - - /articles/about-githubs-ip-addresses - - /github/authenticating-to-github/about-githubs-ip-addresses -versions: - free-pro-team: '*' -topics: - - Identity - - Access management ---- -Puedes recuperar una lista de direcciones IP de {% data variables.product.prodname_dotcom %} desde el punto de conexión de API [meta](https://api.github.com/meta). Para obtener más información, consulta la sección "[Meta](/v3/meta/)". - -Estos rangos están en [notación CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). Puedes usar una herramienta de conversión en línea como esta [Calculadora Supernet CIDR / VLSM](http://www.subnet-calculator.com/cidr.php) para convertir de una notación CIDR a rangos de dirección IP. - -De vez en cuando hacemos cambios en nuestras direcciones IP, y mantendremos esta API actualizada. No te recomendamos hacer una lista blanca por dirección de IP, sin embargo, si utilizas estos rangos de IP te exhortamos enfáticamente a monitorear nuestra API con frecuencia. - -Para que las aplicaciones funcionen, debes habilitar los puertos TCP 22, 80, 443 y 9418 mediante nuestros rangos de IP para `github.com`. - -### Leer más - -- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps.md deleted file mode 100644 index d677dc68e2..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Autorizar aplicaciones OAuth -intro: 'Puedes conectar tu identidad {% data variables.product.product_name %} con aplicaciones de terceros mediante OAuth. Al autorizar un {% data variables.product.prodname_oauth_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.' -redirect_from: - - /articles/authorizing-oauth-apps - - /github/authenticating-to-github/authorizing-oauth-apps -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -Cuando una {% data variables.product.prodname_oauth_app %} quiere identificarte a través de tu cuenta de {% data variables.product.product_name %}, verás una página con la información de contacto del desarrollador de la app y una lista de los datos específicos que se han solicitado. - -{% if currentVersion == "free-pro-team@latest" %} - -{% tip %} - -**Sugerencia:** Debes [verificar tu dirección de correo electrónico](/articles/verifying-your-email-address) antes de que puedas autorizar una {% data variables.product.prodname_oauth_app %}. - -{% endtip %} - -{% endif %} - -### Acceso a {% data variables.product.prodname_oauth_app %} - -Las {% data variables.product.prodname_oauth_app %} 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. - -{% tip %} - -**Sugerencia:** {% data reusables.user_settings.review_oauth_tokens_tip %} - -{% endtip %} - -#### Acerca de los alcances de OAuth - -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. Para obtener más información, consulta la sección "[Acerca de los alcances para {% data variables.product.prodname_oauth_app %}](//apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". - -{% tip %} - -**Nota:** Actualmente, no puedes demarcar el acceso al código fuente a solo lectura. - -{% endtip %} - -#### Tipos de datos solicitados - -{% data variables.product.prodname_oauth_app %} puede solicitar diferentes tipos de datos. - -| Tipos de datos | Descripción | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Estado de confirmación | Puedes otorgar acceso para una app para que informe tu estado de confirmación. El acceso al estado de confirmación permite que las apps determinen si una construcción es exitosa frente a una confirmación específica. Las apps no tendrán acceso a tu código, pero podrán leer y escribir el estado de la información frente a una confirmación específica. | -| Implementaciones | El estado de implementación permite que las apps determinen si una implementación es exitosa frente a una confirmación específica para repositorios públicos y privados. Las apps no tendrán acceso a tu código. | -| Gists | El acceso a [Gist](https://gist.github.com) permite que las apps lean o escriban en tus Gists públicos y secretos. | -| Ganchos | El acceso a [webhooks](/webhooks) permite que las apps lean o escriban configuraciones de gancho en los repositorios que administras. | -| Notificaciones | El acceso a las notificaciones permite que las apps lean tus notificaciones de {% data variables.product.product_name %}, como comentarios sobre propuestas y solicitudes de extracción. Sin embargo, las apps permanecen inhabilitadas para acceder a tus repositorios. | -| Organizaciones y equipos | El acceso a organizaciones y equipos permite que las apps accedan y administren la membresía de la organización y del equipo. | -| Datos personales del usuario | Entre los datos del usuario se incluye información que se encuentra en tu perfil de usuario, como tu nombre, dirección de correo electrónico y ubicación. | -| Repositorios | La información del repositorio incluye los nombres de los colaboradores, las ramas que creaste y los archivos actuales dentro de tu repositorio. Las apps pueden solicitar acceso a repositorios públicos o privados a nivel del usuario. | -| Eliminación de repositorio | Las apps pueden solicitar la eliminación de los repositorios que administras,, pero no tendrán acceso a tu código. | - -### Solicitar permisos actualizados - -Cuando las {% data variables.product.prodname_oauth_app %} solicitan nuevos permisos de acceso, te notificarán sobre las diferencias entre los permisos actuales y los permisos nuevos. - -{% if currentVersion == "free-pro-team@latest" %} - -### {% data variables.product.prodname_oauth_app %} 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. - -- **Para organizaciones *sin* restricciones de acceso a {% data variables.product.prodname_oauth_app %}, la aplicación automáticamente estará autorizada para acceder a los recursos de esa organización.**Por este motivo, deberías tener cuidado con respecto a las {% data variables.product.prodname_oauth_app %} que apruebas para que tengan acceso a tus recursos de cuenta personal así como a los recursos 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 %}. - -### Leer más - -- "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" -- "[Soporte técnico de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" - -{% endif %} diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md deleted file mode 100644 index 1f461c9f16..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Conectar con aplicaciones de terceros -intro: 'Puedes conectar tu identidad {% data variables.product.product_name %} con aplicaciones de terceros mediante OAuth. Al autorizar una de estas aplicaciones, 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.' -redirect_from: - - /articles/connecting-with-third-party-applications - - /github/authenticating-to-github/connecting-with-third-party-applications -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -Cuando una aplicación de terceros desea identificarte mediante tu inicio de sesión de {% data variables.product.product_name %}, verás una página con la información de contacto del programador y una lista de los datos específicos que se han solicitado. - -### Contactarse con el programador de la aplicación - -Dado que una aplicación está desarrollada por un tercero que no es {% data variables.product.product_name %}, no sabemos exactamente cómo una aplicación usa los datos a los que solicita acceso. Puedes usar la información del programador en la parte superior de la página para contactarte con el administrador de la aplicación si tienes preguntas o inquietudes sobre tu aplicación. - -![Información del propietario de {% data variables.product.prodname_oauth_app %}](/assets/images/help/platform/oauth_owner_bar.png) - -Si el programador ha elegido suministrarla, el lateral derecho de la página brinda una descripción detallada de la aplicación, así como su sitio web asociado. - -![Información de la aplicación OAuth y sitio web](/assets/images/help/platform/oauth_app_info.png) - -### Tipos de acceso a la aplicación y datos - -Las aplicaciones pueden tener acceso de *lectura* o *escritura* a tus datos de {% data variables.product.product_name %}. - -- El **acceso de lectura** solo permite que una aplicación *mire* tus datos. -- El **acceso de escritura** permite que una aplicación *cambie* tus datos. - -#### Acerca de los alcances de OAuth - -*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. Para obtener más información, consulta la sección "[Acerca de los alcances para {% data variables.product.prodname_oauth_app %}](//apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". - -{% tip %} - -**Nota:** Actualmente, no puedes demarcar el acceso al código fuente a solo lectura. - -{% endtip %} - -#### Tipos de datos solicitados - -Existen varios tipos de datos que las aplicaciones pueden solicitar. - -![Detalles de acceso a OAuth](/assets/images/help/platform/oauth_access_types.png) - -{% tip %} - -**Sugerencia:** {% data reusables.user_settings.review_oauth_tokens_tip %} - -{% endtip %} - -| Tipos de datos | Descripción | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Estado de confirmación | Puedes otorgar acceso a una aplicación de terceros para que informe tu estado de confirmación. El acceso al estado de confirmación permite que las aplicaciones determinen si una construcción es exitosa frente a una confirmación específica. Las aplicaciones no tendrán acceso a tu código, pero pueden leer y escribir la información del estado frente a una confirmación específica. | -| Implementaciones | El estado de implementación permite que las aplicaciones determinen si una implementación es exitosa frente a una confirmación específica para repositorios públicos y privados. Las aplicaciones no tendrán acceso a tu código. | -| Gists | El acceso a [Gist](https://gist.github.com) permite que las aplicaciones lean o escriban en tus Gists públicos y secretos. | -| Ganchos | El acceso a [webhooks](/webhooks) permite que las aplicaciones lean o escriban configuraciones de gancho en los repositorios que administras. | -| Notificaciones | El acceso a las notificaciones permite que las aplicaciones lean tus notificaciones de {% data variables.product.product_name %}, como comentarios sobre propuestas y solicitudes de extracción. Sin embargo, las aplicaciones permanecen inhabilitadas para acceder a tus repositorios. | -| Organizaciones y equipos | El acceso a organizaciones y equipos permite que las apps accedan y administren la membresía de la organización y del equipo. | -| Datos personales del usuario | Entre los datos del usuario se incluye información que se encuentra en tu perfil de usuario, como tu nombre, dirección de correo electrónico y ubicación. | -| Repositorios | La información del repositorio incluye los nombres de los colaboradores, las ramas que creaste y los archivos actuales dentro de tu repositorio. Las aplicaciones pueden solicitar acceso a repositorios públicos o privados a nivel del usuario. | -| Eliminación de repositorio | Las aplicaciones pueden solicitar la eliminación de los repositorios que administras,, pero no tendrán acceso a tu código. | - -### Solicitar permisos actualizados - -Las aplicaciones pueden solicitar nuevos privilegios de acceso. Al solicitar permisos actualizados, la aplicación te notificará de las diferencias. - -![Cambiar el acceso a aplicaciones de terceros](/assets/images/help/platform/oauth_existing_access_pane.png) diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token.md deleted file mode 100644 index da4e647aaa..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Crear un token de acceso personal -intro: Debes crear un token de acceso personal para utilizar como contraseña con la línea de comandos o con la API. -redirect_from: - - /articles/creating-an-oauth-token-for-command-line-use/ - - /articles/creating-an-access-token-for-command-line-use/ - - /articles/creating-a-personal-access-token-for-the-command-line - - /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line - - /github/authenticating-to-github/creating-a-personal-access-token -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -Los tokens de acceso personal (PAT) son una alternativa al uso de contraseñas para la autenticación en {% data variables.product.product_name %} cuando utilizas la [API de GitHub](/v3/auth/#via-oauth-and-personal-access-tokens) o la [línea de comandos](#using-a-token-on-the-command-line). - -{% if currentVersion == "free-pro-team@latest" %}Si quieres utilizar un PAT para acceder a los recursos que pertenecen a una organización que utiliza el SSO de SAML, debes autorizarlo. Para obtener más información, consulta las secciónes "[Acerca de la autenticación, con el inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)" y "[Autorizar un token de acceso personal para su uso con el inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)".{% endif %} - -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %} - -### Crear un token - -{% if currentVersion == "free-pro-team@latest" %}1. [Verifica tu dirección de correo electrónico](/articles/verifying-your-email-address), si aún no ha sido verificada.{% endif %} -{% 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) -5. Asígnale a tu token un nombre descriptivo. ![Campo para la descripción del token](/assets/images/help/settings/token_description.png) -6. 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**. ![Seleccionar los alcances del token](/assets/images/help/settings/token_scopes.gif) -7. Haz clic en **Generar token**. ![Generar un botón para el token](/assets/images/help/settings/generate_token.png) -8. Haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar el token en tu portapapeles. Por razones de seguridad, una vez que salgas de la página no podrás volver a ver el token.{% if currentVersion == "free-pro-team@latest" %} ![Newly created token](/assets/images/help/settings/personal_access_tokens.png){% else %} -![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png){% endif %} - - {% warning %} - - **Advertencia:**Preserva tus tokens de la misma manera que tus contraseñas y no se las reveles a nadie. Cuando trabajes con la API, usa tokens como variables del entorno en lugar de codificarlos de forma rígida en tus programas. - - {% endwarning %} -{% if currentVersion == "free-pro-team@latest" %}9. Para usar tu token a fin de autenticar a una organización que usa SAML SSO, [autoriza el token para usarlo con una organización con inicio de sesión único de SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %} - -### Usar un token en la línea de comando - -{% data reusables.command_line.providing-token-as-password %} - -Los tokens de acceso personal solo se pueden usar para operaciones HTTPS Git. Si tu repositorio usa una URL SSH remota, necesitarás [pasar de la URL SSH remota a HTTPS](/articles/changing-a-remote-s-url/#switching-remote-urls-from-ssh-to-https). - -Si no se te solicita tu nombre de usuario y contraseña, tus credenciales pueden estar almacenadas en la caché de tu computadora. Puedes [actualizar tus credenciales en la keychain](/articles/updating-credentials-from-the-osx-keychain) para reemplazar tu contraseña anterior con el token. - -### Leer más - -- "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password.md deleted file mode 100644 index 0158b09c2b..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Crear una contraseña segura -intro: 'Protege tu cuenta de {% data variables.product.product_name %} con una contraseña segura y única usando un administrador de contraseñas.' -redirect_from: - - /articles/what-is-a-strong-password/ - - /articles/creating-a-strong-password - - /github/authenticating-to-github/creating-a-strong-password -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Identity - - Access management ---- -Debes elegir o generar una contraseña para tu cuenta de {% data variables.product.product_name %} que contenga lo siguiente: -- Ocho caracteres de largo, si incluye un número o una letra minúscula, o bien -- 16 caracteres de largo con cualquier combinación de caracteres - -Para preservar la seguridad de tu cuenta, te recomendamos que sigas estas buenas prácticas: -- Utiliza un administrador de contraseñas, como [LastPass](https://lastpass.com/) o[1Password](https://1password.com/), para generar una contraseña de más de 16 caracteres. -- Genera una contraseña que sea única para {% data variables.product.product_name %}. Si usas tu contraseña de {% data variables.product.product_name %} en algún otro lugar y ese servicio se ve comprometido, los atacantes u otros actores maliciosos pueden usar esa información para acceder a tu cuenta de {% data variables.product.product_name %}. -- Configura la autenticación de dos factores para tu cuenta personal. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)". -- Nunca compartas tu contraseña con nadie, aunque se trate de un potencial colaborador. Cada persona debe usar su propia cuenta personal en {% data variables.product.product_name %}. Para obtener más información acerca de cómo colaborar, consulta: "[Invitar colaboradores a un repositorio personal](/articles/inviting-collaborators-to-a-personal-repository)," "[Acerca de los modelos de desarrollo colaborativos](/articles/about-collaborative-development-models/)," o "[Colaborar con los grupos en las organizaciones](/articles/collaborating-with-groups-in-organizations/)". - -{% data reusables.repositories.blocked-passwords %} - -Solo puedes utilizar tu contraseña para ingresar en {% data variables.product.product_name %} a través de tu buscador. Cuadno te atutenticas en {% data variables.product.product_name %} con otros medios, tales como la línea de comandos o la API, debes utilizar otras credenciales. Para obtener más información, consulta la sección "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)". - -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %} - -### Leer más - -- [Almacenar tus credenciales de {% data variables.product.product_name %} en la caché en Git](/github/using-git/caching-your-github-credentials-in-git/)" -- "[Preservar la seguridad de tu cuenta y tus datos](/articles/keeping-your-account-and-data-secure/)" diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md deleted file mode 100644 index 481af00fec..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Huellas digitales de la clave SSH de GitHub -intro: Se pueden utilizar las huellas digitales de clave pública para validar una conexión a un servidor remoto. -redirect_from: - - /articles/what-are-github-s-ssh-key-fingerprints/ - - /articles/github-s-ssh-key-fingerprints - - /articles/githubs-ssh-key-fingerprints - - /github/authenticating-to-github/githubs-ssh-key-fingerprints -versions: - free-pro-team: '*' -topics: - - Identity - - Access management ---- -Estas son las huellas digitales de clave pública de {% data variables.product.prodname_dotcom %}: - -- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) -- `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA) diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/index.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/index.md deleted file mode 100644 index c1886f73fb..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/index.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Mantener seguros tu cuenta y tus datos -intro: 'Para proteger tu información personal, debes mantener seguros tanto tu {% data variables.product.product_name %} cuenta como cualquier dato asociado.' -redirect_from: - - /articles/keeping-your-account-and-data-secure -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management -children: - - /about-authentication-to-github - - /creating-a-strong-password - - /updating-your-github-access-credentials - - /creating-a-personal-access-token - - /reviewing-your-ssh-keys - - /reviewing-your-deploy-keys - - /authorizing-oauth-apps - - /reviewing-your-authorized-integrations - - /connecting-with-third-party-applications - - /reviewing-your-authorized-applications-oauth - - /reviewing-your-security-log - - /removing-sensitive-data-from-a-repository - - /about-anonymized-urls - - /about-githubs-ip-addresses - - /githubs-ssh-key-fingerprints - - /sudo-mode - - /preventing-unauthorized-access ---- - diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/preventing-unauthorized-access.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/preventing-unauthorized-access.md deleted file mode 100644 index 292bc4983b..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/preventing-unauthorized-access.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Evitar el acceso no autorizado -intro: 'Puedes ser alertado sobre un incidente de seguridad en los medios, como el descubrimiento de [Heartbleed bug](http://heartbleed.com/), o pueden robar tu computadora mientras estás registrado en {% data variables.product.product_location %}. En dichos casos, cambiar tu contraseña previene cualquier acceso futuro no deseado a tu cuenta y a tus proyectos.' -redirect_from: - - /articles/preventing-unauthorized-access - - /github/authenticating-to-github/preventing-unauthorized-access -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Identity - - Access management ---- -{% data variables.product.product_name %} requiere una contraseña para realizar acciones confidenciales, como agregar nuevas claves SSH, autorizar aplicaciones , o modificar miembros del equipo. - -Después de cambiar tu contraseña, deberías realizar estas acciones para asegurarte que tu cuenta sea segura: - -- [Habilitar una autenticación de dos factores](/articles/about-two-factor-authentication) en tu cuenta para que el acceso requiera más de una contraseña. -- [Revisar tus claves SSH](/articles/reviewing-your-ssh-keys), [llaves de implementación](/articles/reviewing-your-deploy-keys), e [integraciones autorizadas](/articles/reviewing-your-authorized-integrations) y revocar el acceso no autorizado o desconocido en tus configuraciones de SSH y de Aplicaciones. -{% if currentVersion == "free-pro-team@latest" %} -- [Verificar todas tus direcciones de correo electrónico](/articles/verifying-your-email-address). Si un atacante agregó sus direcciones de correo electrónico a tu cuenta, esto puede permitirle forzar un restablecimiento de contraseña no deseado. -{% endif %} -- [Revisar el registro de seguridad de tu cuenta](/github/authenticating-to-github/reviewing-your-security-log). Esto brinda un resumen de varias configuraciones realizadas a tus repositorios. Por ejemplo, puedes asegurarte que no se convirtieron repositorios privados en públicos, o que no se transfirieron repositorios. -- [Revisa los webhooks](/articles/creating-webhooks) en tus repositorios. Los webhooks podrían permitir que un atacante intercepte cargas que hagas a tu repositorio. -- [Asegurarte que no se hayan creado nuevas llaves de implementación](/guides/managing-deploy-keys/#deploy-keys). Esto podría permitir que servidores externos accedan a tus proyectos. -- Revisar las confirmaciones de cambios recientes realizadas a tus repositorios. -- Revisar la lista de colaboradores de cada repositorio. diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md deleted file mode 100644 index eb4b5f4363..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -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. Para eliminar por completo los archivos no deseados del historial de un repositorio, puedes utilizar el comando `git filter-branch` o la herramienta de código abierto BFG Repo-Cleaner.' -redirect_from: - - /remove-sensitive-data/ - - /removing-sensitive-data/ - - /articles/remove-sensitive-data/ - - /articles/removing-sensitive-data-from-a-repository - - /github/authenticating-to-github/removing-sensitive-data-from-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -El comando `git filter-branch` y el BFG Repo-Cleaner reescriben el historial de tu repositorio, lo cual cambia las SHA de las confirmaciones existentes que modificas y cualquier confirmación de las dependencias. 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`. Para obtener información acerca de eliminar un archivo que se agregó con la última confirmación, consulta "[Eliminar archivos del historial de un repositorio](/articles/removing-files-from-a-repository-s-history)". - -{% warning %} - -**Advertencia: Una vez que hayas subido una confirmación en {% data variables.product.product_name %}, debes tener en cuenta cualquier dato que contenga que pueda ser riesgoso.** Si confirmaste una contraseña, ¡cámbiala! Si confirmaste una clave, genera una nueva. - -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 hacer nada con los clones o bifurcaciones existentes de tu repositorio, pero puedes eliminar de manera permanente las visualizaciones cacheadas y las referencias a los datos confidenciales en las solicitudes de extracción en {% data variables.product.product_name %} contactándote con {% data variables.contact.contact_support %}. - -{% endwarning %} - -### Purgar un archivo del historial de tu repositorio - -#### Usar el BFG - -El [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) es una herramienta construida y mantenida por la comunidad de código abierto. Proporciona una alternativa más rápida y simple que `git filter-branch` para eliminar datos no deseados. Por ejemplo, para eliminar tu archivo con datos confidenciales y dejar intacta tu última confirmación, ejecuta lo siguiente: - -```shell -$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA -``` - -Para reemplazar todo el texto detallado en `passwords.txt` donde sea que se encuentre en el historial de tu repositorio, ejecuta lo siguiente: - -```shell -$ bfg --replace-text passwords.txt -``` - -Consulta los documentos de [BFG Repo-Cleaner](http://rtyley.github.io/bfg-repo-cleaner/) para obtener todas las indicaciones para el uso y la descarga. - -#### Utilizar filter-branch - -{% warning %} - -**Advertencia:** Si ejecutas `git filter-branch` después de acumular cambios, no podrás recuperar tus cambios con otros comandos de acumulación. Antes de ejecutar `git filter-branch`, 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 [Herramientas de Git Acumulación](https://git-scm.com/book/en/v1/Git-Tools-Stashing). - -{% endwarning %} - -Para ilustrar cómo funciona `git filter-branch`, 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. 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 - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY - > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ - > remote: Counting objects: 1301, done. - > remote: Compressing objects: 100% (769/769), done. - > remote: Total 1301 (delta 724), reused 910 (delta 522) - > Receiving objects: 100% (1301/1301), 164.39 KiB, done. - > Resolving deltas: 100% (724/724), done. - ``` -2. Navega hacia el directorio de trabajo del repositorio. - ```shell - $ cd YOUR-REPOSITORY - ``` -3. 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 - - **Sobrescribir tus etiquetas existentes** - ```shell - $ git filter-branch --force --index-filter \ - "git rm --cached --ignore-unmatch PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA" \ - --prune-empty --tag-name-filter cat -- --all - > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (266/266) - > Ref 'refs/heads/master' was rewritten - ``` - - {% note %} - - **Nota:** Si se utilizó el archivo con datos confidenciales para que existiera en cualquier otra ruta (porque se movió o se renombró), debes ejecutar este comando en esas rutas también. - - {% endnote %} - -4. Agrega tu archivo con datos confidenciales a `.gitignore` para asegurar que no lo volviste a confirmar por accidente. - - ```shell - $ echo "YOUR-FILE-WITH-SENSITIVE-DATA" >> .gitignore - $ git add .gitignore - $ git commit -m "Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore" - > [master 051452f] Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore - > 1 files changed, 1 insertions(+), 0 deletions(-) - ``` -5. Comprueba que hayas eliminado todo lo que querías del historial de tu repositorio y que todas tus ramas estén revisadas. -6. Una vez que estés conforme con el estado de tu repositorio, realiza un empuje forzado de tus cambios locales para sobrescribir tu {% data variables.product.product_name %} repositorio y todas las ramas que hayas subido: - ```shell - $ git push origin --force --all - > Counting objects: 1074, done. - > Delta compression using 2 threads. - > Compressing objects: 100% (677/677), done. - > Writing objects: 100% (1058/1058), 148.85 KiB, done. - > Total 1058 (delta 590), reused 602 (delta 378) - > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git - > + 48dc599...051452f master -> master (forced update) - ``` -7. Para eliminar el archivo confidencial de [tus lanzamientos etiquetados](/articles/about-releases), también deberás realizar un empuje forzado contra tus etiquetas de Git: - ```shell - $ git push origin --force --tags - > Counting objects: 321, done. - > Delta compression using up to 4 threads. - > Compressing objects: 100% (166/166), done. - > Writing objects: 100% (321/321), 331.74 KiB | 0 bytes/s, done. - > Total 321 (delta 124), reused 269 (delta 108) - > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git - > + 48dc599...051452f master -> master (forced update) - ``` -8. 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 %}. -9. 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. -10. Después de que haya transcurrido un tiempo y estés seguro de que `git filter-branch` 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 - $ git gc --prune=now - > Counting objects: 2437, done. - > Delta compression using up to 4 threads. - > Compressing objects: 100% (1378/1378), done. - > Writing objects: 100% (2437/2437), done. - > Total 2437 (delta 1461), reused 1802 (delta 1048) - ``` - {% note %} - - **Nota:** También puedes lograrlo subiendo tu historial filtrado a un repositorio nuevo o vacío para después hacer un nuevo clon desde {% data variables.product.product_name %}. - - {% endnote %} - -## Evitar confirmaciones accidentales en el futuro - -Existen algunos trucos sencillos para evitar confirmar cosas que no quieres confirmar: - -- Utiliza un programa visual como [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) o [gitk](https://git-scm.com/docs/gitk) para confirmar los cambios. Los programas visuales suelen hacer que sea más sencillo ver exactamente qué archivos se agregarán, eliminarán y modificarán con cada confirmación. -- Evita los comandos para atrapar todo `git add .` y `git commit -a` de la línea de comando —en su lugar, utiliza `git add filename` y `git rm filename` para ordenar por etapas los archivos. -- Utiliza `git add --interactive` para revisar por separado y preparar los cambios de cada archivo. -- Utiliza `git diff --cached` para revisar los cambios que hayas preparado para la confirmación. Esta es la diferencia exacta que `git commit` generará siempre que no utilices la marca `-a`. - -### Leer más - -- [Página principal `git filter-branch`](https://git-scm.com/docs/git-filter-branch) -- [Pro Git: Herramientas de Git - Rescribir historial](https://git-scm.com/book/en/Git-Tools-Rewriting-History) diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md deleted file mode 100644 index 00fd58b4f5..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Revisar tus aplicaciones autorizadas (OAuth) -intro: 'Debes revisar tus aplicaciones autorizadas para comprobar que no se autoricen aplicaciones nuevas con permisos expansivos, como aquellas que tienen acceso a tus repositorios privados.' -redirect_from: - - /articles/reviewing-your-authorized-applications-oauth - - /github/authenticating-to-github/reviewing-your-authorized-applications-oauth -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% 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 %} - -### Leer más -{% if currentVersion == "free-pro-team@latest" %} -- "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} -- "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)" diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md deleted file mode 100644 index 60680a020d..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Revisar tus integraciones autorizadas -intro: Puedes revisar tus integraciones autorizadas para auditar el acceso que cada integración tiene a tu cuenta y a tus datos. -redirect_from: - - /articles/reviewing-your-authorized-integrations - - /github/authenticating-to-github/reviewing-your-authorized-integrations -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -### Revisar tus {% data variables.product.prodname_oauth_app %}s 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 %} - -### Revisar tus {% data variables.product.prodname_github_app %}s autorizadas - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.access_applications %} -3. Haz clic en la pestaña **Authorized {% data variables.product.prodname_github_app %}s** ({% data variables.product.prodname_github_app %}s autorizadas). ![Pestaña de {% data variables.product.prodname_github_app %}s autorizadas](/assets/images/help/settings/settings-authorized-github-apps-tab.png) -3. Revisa las {% data variables.product.prodname_github_app %}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_app %}s, haz clic en **Revoke all** (Revocar todo). ![Lista de {% data variables.product.prodname_github_app %} autorizadas](/assets/images/help/settings/revoke-github-app.png) - -### Leer más -{% if currentVersion == "free-pro-team@latest" %} -- "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} -- "[Revisar tus aplicaciones autorizadas (OAuth)](/articles/reviewing-your-authorized-applications-oauth)" diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md deleted file mode 100644 index bb7fff77d5..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Revisar tus llaves de implementación -intro: Debes revisar tus llaves de implementación para garantizar que no haya ninguna llave sin autorización (o posiblemente comprometida). También puedes aprobar llaves de implementación existentes que sean válidas. -redirect_from: - - /articles/reviewing-your-deploy-keys - - /github/authenticating-to-github/reviewing-your-deploy-keys -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En la barra lateral izquierda, haz clic en **Deploy keys** (Llaves de implementación). ![Parámetro de llaves de implementación](/assets/images/help/settings/settings-sidebar-deploy-keys.png) -4. En la página de Llaves de implementación, anota las llaves de implementación asociadas a tu cuenta. Para las que no reconozcas o que estén desactualizadas, haz clic en **Delete** (Eliminar). Si hay llaves de implementación válidas que quieres conservar, haz clic en **Approve** (Aprobar). ![Lista de llaves de implementación](/assets/images/help/settings/settings-deploy-key-review.png) - -Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/guides/managing-deploy-keys)". diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log.md deleted file mode 100644 index c2cd5402fc..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ /dev/null @@ -1,252 +0,0 @@ ---- -title: Reviewing your security log -intro: You can review the security log for your user account to better understand actions you've performed and actions others have performed that involve you. -redirect_from: - - /articles/reviewing-your-security-log - - /github/authenticating-to-github/reviewing-your-security-log -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -miniTocMaxHeadingLevel: 4 -topics: - - Identity - - Access management ---- -### Accessing your security log - -The security log lists all actions performed within the last 90 days{% if currentVersion ver_lt "enterprise-server@2.20" %}, up to 50{% endif %}. - -{% data reusables.user_settings.access_settings %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -2. In the user settings sidebar, click **Security log**. - ![Security log tab](/assets/images/help/settings/audit-log-tab.png) -{% else %} -{% data reusables.user_settings.security %} -3. Under "Security history," your log is displayed. - ![Security log](/assets/images/help/settings/user_security_log.png) -4. Click on an entry to see more information about the event. - ![Security log](/assets/images/help/settings/user_security_history_action.png) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -### Searching your security log - -{% data reusables.audit_log.audit-log-search %} - -#### Search based on the action performed -{% else %} -### Understanding events in your security log - -Actions listed in your security log are grouped within the following categories: -{% endif %} - -| Category Name | Description -|------------------|-------------------{% if currentVersion == "free-pro-team@latest" %} -| `account_recovery_token` | Contains all activities related to [adding a recovery token](/articles/configuring-two-factor-authentication-recovery-methods). -| `billing` | Contains all activities related to your billing information. -| `marketplace_agreement_signature` | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. -| `marketplace_listing` | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %} -| `oauth_access` | Contains all activities related to [{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps) you've connected with.{% if currentVersion == "free-pro-team@latest" %} -| `payment_method` | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %} -| `profile_picture` | Contains all activities related to your profile picture. -| `project` | Contains all activities related to project boards. -| `public_key` | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account). -| `repo` | Contains all activities related to the repositories you own.{% if currentVersion == "free-pro-team@latest" %} -| `sponsors` | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if currentVersion != "free-pro-team@latest" %} -| `team` | Contains all activities related to teams you are a part of.{% endif %} -| `two_factor_authentication` | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa). -| `user` | Contains all activities related to your account. - -A description of the events within these categories is listed below. - -{% if currentVersion == "free-pro-team@latest" %} - -#### The `account_recovery_token` category - -| Action | Description -|------------------|------------------- -| confirm | Triggered when you successfully [store a new token with a recovery provider](/articles/configuring-two-factor-authentication-recovery-methods). -| recover | Triggered when you successfully [redeem an account recovery token](/articles/recovering-your-account-if-you-lose-your-2fa-credentials). -| recover_error | Triggered when a token is used but {% data variables.product.prodname_dotcom %} is not able to validate it. - -#### The `billing` category - -| Action | Description -|------------------|------------------- -| change_billing_type | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}. -| change_email | Triggered when you [change your email address](/articles/changing-your-primary-email-address). - -#### The `marketplace_agreement_signature` category - -| Action | Description -|------------------|------------------- -| create | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. - -#### The `marketplace_listing` category - -| Action | Description -|------------------|------------------- -| approve | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. -| create | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. -| delist | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. -| redraft | Triggered when your listing is sent back to draft state. -| reject | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. - -{% endif %} - -#### The `oauth_access` category - -| Action | Description -|------------------|------------------- -| create | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/articles/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). - -{% if currentVersion == "free-pro-team@latest" %} - -#### The `payment_method` category - -| Action | Description -|------------------|------------------- -| clear | Triggered when [a payment method](/articles/removing-a-payment-method) on file is removed. -| create | Triggered when a new payment method is added, such as a new credit card or PayPal account. -| update | Triggered when an existing payment method is updated. - -{% endif %} - -#### The `profile_picture` category - -| Action | Description -|------------------|------------------- -| update | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/). - -#### The `project` category - -| Action | Description -|--------------------|--------------------- -| `create` | Triggered when a project board is created. -| `rename` | Triggered when a project board is renamed. -| `update` | Triggered when a project board is updated. -| `delete` | Triggered when a project board is deleted. -| `link` | Triggered when a repository is linked to a project board. -| `unlink` | Triggered when a repository is unlinked from a project board. -| `project.access` | Triggered when a project board's visibility is changed. -| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed. - -#### The `public_key` category - -| Action | Description -|------------------|------------------- -| create | Triggered when you [add a new public SSH key to your {% data variables.product.product_name %} account](/articles/adding-a-new-ssh-key-to-your-github-account). -| delete | Triggered when you [remove a public SSH key to your {% data variables.product.product_name %} account](/articles/reviewing-your-ssh-keys). - -#### The `repo` category - -| Action | Description -|------------------|------------------- -| access | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa). -| add_member | Triggered when a {% data variables.product.product_name %} user is {% if currentVersion == "free-pro-team@latest" %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository. -| add_topic | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. -| archived | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% if currentVersion != "free-pro-team@latest" %} -| config.disable_anonymous_git_access | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| config.enable_anonymous_git_access | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| config.lock_anonymous_git_access | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). -| config.unlock_anonymous_git_access | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} -| create | Triggered when [a new repository is created](/articles/creating-a-new-repository). -| destroy | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} -| disable | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| enable | Triggered when a repository is re-enabled.{% endif %} -| remove_member | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository). -| remove_topic | Triggered when a repository owner removes a topic from a repository. -| rename | Triggered when [a repository is renamed](/articles/renaming-a-repository). -| transfer | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). -| transfer_start | Triggered when a repository transfer is about to occur. -| unarchived | Triggered when a repository owner unarchives a repository. - -{% if currentVersion == "free-pro-team@latest" %} -#### The `sponsors` category - -| Action | Description -|------------------|------------------- -| repo_funding_link_button_toggle | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -| repo_funding_links_file_action | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -| sponsor_sponsorship_cancel | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| sponsor_sponsorship_create | Triggered when you sponsor a developer (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor#sponsoring-a-developer)") -| sponsor_sponsorship_preference_change | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/articles/managing-your-sponsorship)") -| sponsor_sponsorship_tier_change | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| sponsored_developer_approve | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| sponsored_developer_create | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| sponsored_developer_profile_update | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)") -| sponsored_developer_request_approval | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| sponsored_developer_tier_description_update | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)") -| sponsored_developer_update_newsletter_send | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)") -| waitlist_invite_sponsored_developer | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| waitlist_join | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -#### The `successor_invitation` category - -| Action | Description -|------------------|------------------- -| accept | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| cancel | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| create | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| decline | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -| revoke | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your user account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") -{% endif %} - -{% if currentVersion != "free-pro-team@latest" %} - -#### The `team` category - -| Action | Description -|------------------|------------------- -| add_member | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team). -| add_repository | Triggered when a team you are a member of is given control of a repository. -| create | Triggered when a new team in an organization you belong to is created. -| destroy | Triggered when a team you are a member of is deleted from the organization. -| remove_member | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of. -| remove_repository | Triggered when a repository is no longer under a team's control. - -{% endif %} - -#### The `two_factor_authentication` category - -| Action | Description -|------------------|------------------- -| enabled | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled. -| disabled | Triggered when two-factor authentication is disabled. - -#### The `user` category - -| Action | Description -|--------------------|--------------------- -| add_email | Triggered when you [add a new email address](/articles/changing-your-primary-email-address). -| create | Triggered when you create a new user account. -| remove_email | Triggered when you remove an email address. -| rename | Triggered when you rename your account. -| change_password | Triggered when you change your password. -| forgot_password | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password). -| login | Triggered when you log in to {% data variables.product.product_location %}. -| failed_login | Triggered when you failed to log in successfully. -| two_factor_requested | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication). -| show_private_contributions_count | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). -| hide_private_contributions_count | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% if currentVersion == "free-pro-team@latest" %} -| report_content | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/articles/reporting-abuse-or-spam).{% endif %} - -#### The `user_status` category - -| Action | Description -|--------------------|--------------------- -| update | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)." -| destroy | Triggered when you clear the status on your profile. - -{% if currentVersion == "free-pro-team@latest" %} - -### Exporting your security log - -{% data reusables.audit_log.export-log %} -{% data reusables.audit_log.exported-log-keys-and-values %} - -{% endif %} diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md deleted file mode 100644 index 336ac8eb84..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -title: Reviewing your SSH keys -intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your {% data variables.product.product_name %} account.' -redirect_from: - - /articles/keeping-your-application-access-tokens-safe/ - - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe/ - - /articles/reviewing-your-ssh-keys - - /github/authenticating-to-github/reviewing-your-ssh-keys -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid. - -{% mac %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. - ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) - - {% tip %} - - **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. - - {% endtip %} - -4. Open Terminal. - -5. {% data reusables.command_line.start_ssh_agent %} - -6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're using OpenSSH 6.7 or older: - ```shell - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - {% else %} - ```shell - $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) - ```{% endif %} - -7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. - -{% endmac %} - -{% windows %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. - ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) - - {% tip %} - - **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. - - {% endtip %} - -4. Open Git Bash. If you're using Git Shell, which is included in {% data variables.product.prodname_desktop %}, open Git Shell and skip to step 6. - -5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} - - {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} - -6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're using OpenSSH 6.7 or older: - ```shell - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - {% else %} - ```shell - $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) - ```{% endif %} - -7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. - -{% endwindows %} - -{% linux %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. - ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) - - {% tip %} - - **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. - - {% endtip %} - -4. Open Terminal. - -5. {% data reusables.command_line.start_ssh_agent %} - -6. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're using OpenSSH 6.7 or older: - ```shell - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - {% else %} - ```shell - $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) - ```{% endif %} - -7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. - -{% endlinux %} - -{% warning %} - -**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern. - -{% endwarning %} diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/sudo-mode.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/sudo-mode.md deleted file mode 100644 index 7f57a0afab..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/sudo-mode.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Modo sudo -intro: '{% data variables.product.product_name %} te solicita tu contraseña antes de poder modificar tu dirección de correo electrónico, autorizar aplicaciones de terceros, o agregar nuevas llaves públicas, o iniciar otras acciones *sudo-protected* (sudo-protegidas).' -redirect_from: - - /articles/sudo-mode - - /github/authenticating-to-github/sudo-mode -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Identity - - Access management ---- -Después de haber realizado una acción sudo-protegida, únicamente se te solicitará volver a autenticarte después de unas pocas horas de inactividad. Cada acción sudo-protegida reinicia este temporizador. - -![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) - -### Leer más - -- [Comando `sudo` Unix](http://en.wikipedia.org/wiki/Sudo) diff --git a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md deleted file mode 100644 index 5643f1823f..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Actualizar tus credenciales de acceso de GitHub -intro: 'Las credenciales {% data variables.product.product_name %} no solo incluyen tu contraseña, también los tokens de acceso, las claves SSH y los tokens API de la aplicación que utilizas para comunicarte con {% data variables.product.product_name %}. Si lo necesitas, puedes restablecer todas estas credenciales de acceso tú mismo.' -redirect_from: - - /articles/rolling-your-credentials/ - - /articles/how-can-i-reset-my-password/ - - /articles/updating-your-github-access-credentials - - /github/authenticating-to-github/updating-your-github-access-credentials -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -### Solicitar una contraseña nueva - -1. Para solicitar una contraseña nueva, visita {% if currentVersion == "free-pro-team@latest" %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}. -2. Ingresa la dirección de correo electrónico asociada a tu cuenta personal {% data variables.product.product_name %}, luego haz clic en **Send password reset email** (Enviar correo electrónico de restablecimiento de contraseña). El correo electrónico se enviará a la dirección de correo electrónico de respaldo si tienes configurada una. ![Diálogo de solicitud de correo electrónico de restablecimiento de contraseña](/assets/images/help/settings/password-recovery-email-request.png) -3. Te enviaremos por correo electrónico un enlace que te permitirá restablecer la contraseña. Debes hacer clic en este enlace dentro de las 3 horas posteriores a haber recibido el correo electrónico. Si no recibiste un correo electrónico de nuestra parte, asegúrate de revisar la carpeta de spam. -4. Después de hacer clic en el enlace de tu correo electrónico, se te pedirá que ingreses una contraseña nueva. ![Casilla de recuperación de contraseña](/assets/images/help/settings/password_recovery_page.png) - -{% tip %} - -Para evitar que vuelvas a perder tu contraseña, sugerimos utilizar un administrador de contraseñas seguro, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/) o [Keeper](https://keepersecurity.com/). - -{% endtip %} - -### Cambiar una contraseña existente - -{% data reusables.repositories.blocked-passwords %} - -1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}. -{% data reusables.user_settings.access_settings %} -{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -{% data reusables.user_settings.security %} -{%- else %} -{% data reusables.user_settings.account_settings %} -{%- endif %} -4. En "Change password" (Cambiar contraseña), escribe tu contraseña antigua, una contraseña segura nueva y confirma tu contraseña nueva. Para recibir ayuda para crear una contraseña segura, consulta "[Crear una contraseña segura](/articles/creating-a-strong-password)" -5. Haz clic en **Update password** (Actualizar contraseña). - -{% tip %} - -Para mayor seguridad, habilita la autenticación de dos factores además de cambiar la contraseña. Consulta [Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication) para obtener más detalles. - -{% endtip %} - -### Actualizar tus tokens de acceso - -Consulta "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)" para recibir indicaciones sobre revisar y eliminar tokens de acceso. Para generar tokens de acceso nuevos, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". - -### Actualizar tus claves SSH - -Consulta "[Revisar tus claves SSH](/articles/reviewing-your-ssh-keys)" para obtener indicaciones sobre la revisar y eliminar claves SSH. Para generar y agregar claves SSH nuevas, consulta "[Generar una clave SSH](/articles/generating-an-ssh-key)". - -### Restablecer tokens API - -Si tienes alguna aplicación registrada con {% data variables.product.product_name %}, querrás restablecer sus tokens de OAuth. Para obtener más información, consulta la terminal de "[Restablecer una autorización](/rest/reference/apps#reset-an-authorization)". - -### Evitar el acceso no autorizado - -Para obtener más sugerencias acerca de proteger tu cuenta y evitar el acceso sin autorización, consulta "[Evitar el acceso sin autorización](/articles/preventing-unauthorized-access)". diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification.md deleted file mode 100644 index 082722abfc..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Acerca de la verificación de firma de confirmación -intro: 'Usar GPG{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.14" %} o S/MIME{% endif %}, puedes firmar etiquetas y confirmaciones de cambios localmente. Estas etiquetas o confirmaciones se marcan como verificadas en {% data variables.product.product_name %}, para que otras personas puedan confiar en que los cambios vienen de una fuente confiable.' -redirect_from: - - /articles/about-gpg-commit-and-tag-signatures/ - - /articles/about-gpg/ - - /articles/about-commit-signature-verification - - /github/authenticating-to-github/about-commit-signature-verification -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -### Acerca de la verificación de firma de confirmación - -Puedes firmar confirmaciones y etiquetas localmente, para que otras personas puedan verificar que tu trabajo viene de una fuente confiable. Si una confirmación o etiqueta tienen una firma GPG o S/MINE que es criptográficamente comprobable, {% data variables.product.product_name %} marca la confirmación o etiqueta como verificada. - -![Confirmación verificada](/assets/images/help/commits/verified-commit.png) - -Si una confirmación o etiqueta tiene una firma que no puede ser comprobada, {% data variables.product.product_name %} marca la confirmación o la etiqueta como no verificada. - -Los administradores de repositorios pueden implementar la firma de confirmación requerida en una rama para bloquear todas las confirmaciones que no estén firmadas y verificadas. Para obtener más información, consulta "[Acerca de la firma de confirmación requerida](/articles/about-required-commit-signing)". - -Puedes comprobar el estado de verificación de tus confirmaciones o etiquetas firmadas en {% data variables.product.product_name %} y ver por qué las firmas de tu confirmación podrían no ser verificadas. Para obtener más información, consulta "[Comprobar la confirmación y el estado de verificación de firma de la etiqueta](/articles/checking-your-commit-and-tag-signature-verification-status)". - -{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} utilizará GPG automáticamente para firmar las confirmaciones que hagas utilizando la interface web de {% data variables.product.product_name %} con excepción de cuando combinas y fusionas una solicitud de extracción de la cual no seas autor. Las confirmaciones que firme {% data variables.product.product_name %} tendrán un estado verificado en {% data variables.product.product_name %}. Puedes verificar la firma localmente usando la clave pública disponible en https://github.com/web-flow.gpg.{% endif %} - -### Verificación de firma de confirmación GPG - -Puedes usar GPG para firmar confirmaciones con una clave GPG que generas tu mismo. - -{% data variables.product.product_name %} usa las bibliotecas OpenPGP para confirmar que tus confirmaciones y etiquetas firmadas localmente son criptográficamente comprobables con una clave pública que has agregado a tu cuenta de {% data variables.product.product_name %}. - -Para firmar confirmaciones usando GPG y que esas confirmaciones sean verificadas en {% data variables.product.product_name %}, sigue estos pasos: - -1. [Comprobar las claves GPG existentes](/articles/checking-for-existing-gpg-keys) -2. [Generar una clave GPG nueva](/articles/generating-a-new-gpg-key) -3. [Agregar una clave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account) -4. [Informarle a Git acerca de tu clave de firma](/articles/telling-git-about-your-signing-key) -5. [Firmar confirmaciones](/articles/signing-commits) -6. [Firmar etiquetas](/articles/signing-tags) - -### Verificación de firma de confirmación S/MIME - -Puedes usar S/MIME para firmar confirmaciones con una clave X.509 emitida por tu organización. - -{% data variables.product.product_name %} usa [el paquete de certificados CA Debian](https://packages.debian.org/hu/jessie/ca-certificates), el mismo almacenamiento de confianza usado por los navegadores Mozilla, para confirmar que tus confirmaciones y etiquetas firmadas localmente son criptográficamente comprobables con una clave pública en un certificado raíz de confianza. - -{% data reusables.gpg.smime-git-version %} - -Para firmar confirmaciones usando S/MIME y que esas confirmaciones sean verificadas en {% data variables.product.product_name %}, sigue estos pasos: - -1. [Informarle a Git acerca de tu clave de firma](/articles/telling-git-about-your-signing-key) -2. [Firmar confirmaciones](/articles/signing-commits) -3. [Firmar etiquetas](/articles/signing-tags) - -No es necesario cargar tu clave pública a {% data variables.product.product_name %}. - -{% if currentVersion == "free-pro-team@latest" %} -### Verificación de firma para bots - -Las organizaciones y {% data variables.product.prodname_github_app %}s 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 %} - -### Leer más - -- "[Firmar confirmaciones](/articles/signing-commits)" -- "[Firmar etiquetas](/articles/signing-tags)" -- "[Solucionar problemas de la verificación de firma de confirmación](/articles/troubleshooting-commit-signature-verification)" diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md deleted file mode 100644 index 1ffe4616b8..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Agregar una llave GPG nueva a tu cuenta de GitHub -intro: 'Para configurar tu cuenta de {% data variables.product.product_name %} a fin de usar una llave GPG nueva (o existente), también deberás agregarla a tu cuenta de {% data variables.product.product_name %}.' -redirect_from: - - /articles/adding-a-new-gpg-key-to-your-github-account - - /github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -Antes de agregar una nueva llave GPG a tu cuenta de {% data variables.product.product_name %}, cerciórate de haber: -- [Comprobado tus llaves GPG existentes](/articles/checking-for-existing-gpg-keys) -- [Generado y copiado una nueva llave GPG](/articles/generating-a-new-gpg-key) - -{% data reusables.gpg.supported-gpg-key-algorithms %} - -Al verificar una firma, extraemos la firma e intentamos analizar sus id de llave. Complementamos los id de llave con las llaves cargadas a {% data variables.product.product_name %}. Hasta que cargues tu llave de GPG a {% data variables.product.product_name %}, no podemos verificar tus firmas. - -### Agregar una llave GPG - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -3. Haz clic en **New GPG key** (Nueva llave GPG). ![Botón de llave GPG](/assets/images/help/settings/gpg-add-gpg-key.png) -4. En el campo "Clave", pega la llave GPG que copiaste cuando [generó tu llave GPG](/articles/generating-a-new-gpg-key). ![Campo de llave](/assets/images/help/settings/gpg-key-paste.png) -5. Haz clic en **Add GPG key** (Agregar llave GPG). ![Botón Add key (Agregar llave)](/assets/images/help/settings/gpg-add-key.png) -6. Para confirmar la acción, escribe tu contraseña de {% data variables.product.product_name %}. - -### Leer más - -* "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -* "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" -* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" -* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" -* "[Firmar confirmaciones y etiquetas mediante llaves GPG](/articles/signing-commits-and-tags-using-gpg)" diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md deleted file mode 100644 index 195c3deab8..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Asociar un correo electrónico con tu llave GPG -intro: 'Tu llave GPG debe estar asociada con un correo electrónico verificado de {% data variables.product.product_name %} que coincida con tu identidad de persona que confirma el cambio.' -redirect_from: - - /articles/associating-an-email-with-your-gpg-key - - /github/authenticating-to-github/associating-an-email-with-your-gpg-key -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% note %} - -Si estás usando una llave GPG que coincide con la identidad de la persona que confirma el cambio y con tu dirección de correo electrónico verificada asociada a tu {% data variables.product.product_name %} cuenta, puedes comenzar a firmar confirmaciones y firmar etiquetas. - -{% endnote %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -4. Escribe `gpg --edit-key GPG key ID`, sustituyendo la ID de la llave GPG que te gustaría usar. En el siguiente ejemplo, el ID de llave GPG es `3AA5C34371567BD2`: - ```shell - $ gpg --edit-key 3AA5C34371567BD2 - ``` -5. Escribe `gpg> adduid` para agregar los detalles de ID de usuario. - ```shell - $ gpg> adduid - ``` -6. Sigue las indicaciones para suminsitrar tu nombre real, dirección de correo electrónica o cualquier comentario. Puedes modificar tus entradas al elegir `N`, `C` o `E`. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta "[Configurar la confirmación de tu dirección de correo electrónico](/articles/setting-your-commit-email-address)."{% endif %} - ```shell - Real Name: Octocat - Email address: octocat@github.com - Comment: GitHub key - Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? - ``` -7. Escribe `O` para guardar tus selecciones. -8. Escribe la contraseña de tu llave. -9. Escribe `gpg --armor --export GPG key ID`, sustituyendo la ID de la llave GPG que te gustaría usar. En el siguiente ejemplo, el ID de llave GPG es `3AA5C34371567BD2`: - ```shell - $ gpg --armor --export 3AA5C34371567BD2 - # Prints the GPG key, in ASCII armor format - ``` -10. Carga la llave GPG al [agregarla a tu cuenta GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). - -### Leer más - -- "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -- "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" -- "[Utilizar una dirección de correo electrónico verificada en tu llave GPG](/articles/using-a-verified-email-address-in-your-gpg-key)" -- "[Agregar una llave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -- "[Firmar confirmaciones](/articles/signing-commits)" -- "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/checking-for-existing-gpg-keys.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/checking-for-existing-gpg-keys.md deleted file mode 100644 index ca75283c0d..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/checking-for-existing-gpg-keys.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Comprobar las llaves GPG existentes -intro: 'Antes de generar una llave GPG, puedes comprobar si tienes alguna clave GPG existente.' -redirect_from: - - /articles/checking-for-existing-gpg-keys - - /github/authenticating-to-github/checking-for-existing-gpg-keys -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% data reusables.gpg.supported-gpg-key-algorithms %} - -{% note %} - -**Nota:** GPG no viene instalado por defecto en OS X o Windows. Para instalar las herramientas de la línea de comando, consulta [Página de descarga de GnuPG](https://www.gnupg.org/download/). - -{% endnote %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.list-keys-with-note %} -3. Comprueba el resultado de los comandos para ver si tienes un par de llaves GPG. - * Si no hay pares de llaves GPG o no quieres usar algunas de las que están disponibles para las confirmaciones y las etiquetas firmadas, [genera una nueva llave GPG](/articles/generating-a-new-gpg-key). - * Si existe un nuevo par de llaves GPG existente y quieres usarlo para firmar confirmaciones y etiquetas, [agrega tu llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). - -### Leer más - -* "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" -* "[Agregar una llave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" -* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" -* "[Firmar confirmaciones](/articles/signing-commits)" -* "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/generating-a-new-gpg-key.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/generating-a-new-gpg-key.md deleted file mode 100644 index 89100e7cfc..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/generating-a-new-gpg-key.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Generar una llave GPG nueva -intro: 'Si no tienes una llave GPG existentes, puedes generar una nueva llave GPG para usarla para firmar confirmaciones y etiquetas.' -redirect_from: - - /articles/generating-a-new-gpg-key - - /github/authenticating-to-github/generating-a-new-gpg-key -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% data reusables.gpg.supported-gpg-key-algorithms %} - -### Generar una llave GPG - -{% note %} - -**Nota:** Antes de generar una nueva llave GPG, asegúrate de haber verificado tu dirección de correo electrónico. Si no has verificado tu dirección de correo electrónico, no podrás firmar confirmaciones y etiquetas con GPG.{% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)".{% endif %} - -{% endnote %} - -1. Descarga e instala [las herramientas de la línea de comando GPG](https://www.gnupg.org/download/) para tu sistema operativo. Generalmente recomendamos instalar la versión más reciente para tu sistema operativo. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Genera un par de la llave GPG. Ya que existen varias versiones de GPG, puede que necesites consultar la [_página man_](https://en.wikipedia.org/wiki/Man_page) relevante para encontrar el comando adecuado para la generación de llaves. Tu llave debe utilizar RSA. - - Si estás usando una versión 2.1.17 o superior, copia el siguiente texto para generar un par de la llave GPG. - ```shell - $ gpg --full-generate-key - ``` - - Si no estás usando la versión 2.1.17 ni una superior, el comando `gpg --full-generate-key` no funciona. Copia el siguiente texto y continúa con el paso 6. - ```shell - $ gpg --default-new-key-algo rsa4096 --gen-key - ``` -4. En el prompt, especifica la clase de llave que quieres, o presiona `Enter` para aceptar el `RSA y DSA` predeterminado. -5. Ingresa el tamaño de la llave que deseas. Tu llave debe ser de al menos `4096` bits. -6. Ingresa el periodo de validez que deberá tener la llave. Presiona `Enter` para especificar la selección predeterminada, indicando que la llave no expira. -7. Verifica que tus selecciones sean correctas. -8. Ingresa tu información de ID de usuario. - - {% note %} - - **Nota:** Cuando se te pida que ingreses tu dirección de correo electrónico, asegúrate de ingresar la dirección de correo electrónico verificada para tu cuenta Github. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)" and "[Establecer tu dirección de correo electrónico para confirmaciones](/articles/setting-your-commit-email-address)".{% endif %} - - {% endnote %} - -9. Escribe una contraseña segura. -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -10. Pega el siguiente texto sustituyendo el ID de la llave GPG que deseas usar. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`: - ```shell - $ gpg --armor --export 3AA5C34371567BD2 - # Prints the GPG key ID, in ASCII armor format - ``` -11. Copia tu llave GPG, comenzando con `-----BEGIN PGP PUBLIC KEY BLOCK-----` y terminando con `-----END PGP PUBLIC KEY BLOCK-----`. -12. [Agrega la llave GPG a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account). - -### Leer más - -* "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -* "[Agregar una llave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" -* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" -* "[Firmar confirmaciones](/articles/signing-commits)" -* "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/index.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/index.md deleted file mode 100644 index 3e3facde0d..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/index.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Administrar la verificación de firma de confirmación de cambios -intro: 'Puedes firmar tu trabajo de forma local utilizando GPG{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.14" %} o S/MIME{% endif %}. {% data variables.product.product_name %} verificará estas firmas para que otras personas sepan que tus confirmaciones de cambios provienen de una fuente confiable.{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.product_name %} firmará de forma automática las confirmaciones de cambios que realices utilizando la interfaz web {% data variables.product.product_name %}.{% endif %}' -redirect_from: - - /articles/generating-a-gpg-key/ - - /articles/signing-commits-with-gpg/ - - /articles/managing-commit-signature-verification -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management -children: - - /about-commit-signature-verification - - /displaying-verification-statuses-for-all-of-your-commits - - /checking-for-existing-gpg-keys - - /generating-a-new-gpg-key - - /adding-a-new-gpg-key-to-your-github-account - - /telling-git-about-your-signing-key - - /associating-an-email-with-your-gpg-key - - /signing-commits - - /signing-tags ---- - diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/signing-commits.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/signing-commits.md deleted file mode 100644 index 0c3521ae25..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/signing-commits.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Firmar confirmaciones -intro: 'Puedes firmar confirmaciones de forma local utilizando GPG{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.14" %} o S/MIME{% endif %}.' -redirect_from: - - /articles/signing-commits-and-tags-using-gpg/ - - /articles/signing-commits-using-gpg/ - - /articles/signing-commits - - /github/authenticating-to-github/signing-commits -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% data reusables.gpg.desktop-support-for-commit-signing %} - -{% tip %} - -**Sugerencias:** - -Para configurar tu cliente Git para firmar confirmaciones por defecto de un repositorio local, en versiones Git 2.0.0 y superiores, ejecuta `git config commit.gpgsign true`. Para firmar todas las confirmaciones por defecto en cualquier repositorio local en tu computadora, ejecuta `git config --global commit.gpgsign true`. - -Para almacenar tus contraseña de llave GPG para no tener que ingresarla cada vez que firmas una confirmación, recomendamos utilizando las siguientes herramientas: - - Para los usuarios de Mac, la [GPG Suite](https://gpgtools.org/) te permite almacenar tu contraseña de llave GPG en la keychain de Mac OS. - - Para los usuarios de Windows, [Gpg4win](https://www.gpg4win.org/) se integra con otras herramientas de Windows. - -También puedes configurar de forma manual [gpg-agent](http://linux.die.net/man/1/gpg-agent) para guardar tu contraseña de llave GPG, pero esta no se integra con la keychain de Mac OS como ssh-agent y requiere mayor configuración. - -{% endtip %} - -Si tienes múltiples llaves o estás intentando firmar confirmaciones o etiquetas con una llave que no coincide con tu identidad de persona que confirma el cambio, deberías [informarle a Git acerca de tu llave de firma](/articles/telling-git-about-your-signing-key). - -1. Cuando confirmas los cambios en tu rama local, agrega la marca -S al comando de confirmación de Git: - ```shell - $ git commit -S -m your commit message - # Creates a signed commit - ``` -2. Si estás utilizando GPG, después de crear tu confirmación, proporciona la contraseña que configuraste cuando [generaste tu llave GPG](/articles/generating-a-new-gpg-key). -3. Cuando terminaste de crear confirmaciones de forma local, súbelas a tu repositorio remoto en {% data variables.product.product_name %}: - ```shell - $ git push - # Pushes your local commits to the remote repository - ``` -4. En {% data variables.product.product_name %}, desplázate hasta la solicitud de extracción. -{% data reusables.repositories.review-pr-commits %} -5. Para ver información más detallada acerca de la firma verificada, haz clic en Verified (Verificada). ![Confirmación firmada](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) - -### Leer más - -* "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -* "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" -* "[Agregar una llave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -* "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" -* "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" -* "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/signing-tags.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/signing-tags.md deleted file mode 100644 index ba6355c7f3..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/signing-tags.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Firmar etiquetas -intro: You can sign tags locally using GPG or S/MIME. -redirect_from: - - /articles/signing-tags-using-gpg/ - - /articles/signing-tags - - /github/authenticating-to-github/signing-tags -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% data reusables.gpg.desktop-support-for-commit-signing %} - -1. Para firmar una etiqueta, agrega `-s` a tu comando `git tag`. - ```shell - $ git tag -s mytag - # Creates a signed tag - ``` -2. Verifica tu etiqueta firmada al ejecutar `git tag -v [tag-name]`. - ```shell - $ git tag -v mytag - # Verifies the signed tag - ``` - -### Leer más - -- [Ver las etiquetas de tu repositorio](/articles/viewing-your-repositorys-tags)" -- "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -- "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" -- "[Agregar una llave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -- "[Informar a Git sobre tu llave de firma](/articles/telling-git-about-your-signing-key)" -- "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" -- "[Firmar confirmaciones](/articles/signing-commits)" diff --git a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md deleted file mode 100644 index f9a687c62d..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -title: Informarle a Git acerca de tu clave de firma -intro: 'Para firmar confirmaciones de forma local, le debes informar a Git que hay una llave GPG{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.14" %} or X.509{% endif %} que quieres usar.' -redirect_from: - - /articles/telling-git-about-your-gpg-key/ - - /articles/telling-git-about-your-signing-key - - /github/authenticating-to-github/telling-git-about-your-signing-key -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% mac %} - -### Informarle a Git acerca de tu llave GPG - -Si estás usando una llave GPG que coincide con la identidad de la persona que confirma el cambio y con tu dirección de correo electrónico verificada asociada a tu {% data variables.product.product_name %} cuenta, puedes comenzar a firmar confirmaciones y firmar etiquetas. - -{% note %} - -Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)". - -{% endnote %} - -Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -1. Si no estás utilizando GPG Suite, pega el texto que aparece a continuación para agregar la llave GPG a tu perfil bash: - ```shell - $ test -r ~/.bash_profile && echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile - $ echo 'export GPG_TTY=$(tty)' >> ~/.profile - ``` - {% note %} - - **Nota:** Si no tienes `.bash_profile`, este comando agrega tu llave GPG al `.profile`. - - {% endnote %} - -{% data reusables.gpg.x-509-key %} - -{% endmac %} - -{% windows %} - -### Informarle a Git acerca de tu llave GPG - -Si estás usando una llave GPG que coincide con la identidad de la persona que confirma el cambio y con tu dirección de correo electrónico verificada asociada a tu {% data variables.product.product_name %} cuenta, puedes comenzar a firmar confirmaciones y firmar etiquetas. - -{% note %} - -Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)". - -{% endnote %} - -Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} - -{% data reusables.gpg.x-509-key %} - -{% endwindows %} - -{% linux %} - -{% note %} - -**Nota:** Linux no admite claves X.509. Puedes configurar gpgsm para proporcionar servicios de cifrado y firma. Sin embargo, actualmente no es compatible con {% data variables.product.product_name %}. Para obtener más información, consulta el tema [gpgsm](https://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPGSM.html) en la documentación de GnuPG. - -{% endnote %} - -### Informarle a Git acerca de tu llave GPG - -Si estás usando una llave GPG que coincide con la identidad de la persona que confirma el cambio y con tu dirección de correo electrónico verificada asociada a tu {% data variables.product.product_name %} cuenta, puedes comenzar a firmar confirmaciones y firmar etiquetas. - -{% note %} - -Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para obtener más información, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)". - -{% endnote %} - -Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar. - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.gpg.list-keys-with-note %} -{% data reusables.gpg.copy-gpg-key-id %} -{% data reusables.gpg.paste-gpg-key-id %} -1. Para agregar tu llave GPG a tu perfil bash, pega el texto que aparece a continuación: - ```shell - $ test -r ~/.bash_profile && echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile - $ echo 'export GPG_TTY=$(tty)' >> ~/.profile - ``` - {% note %} - - **Nota:** Si no tienes `.bash_profile`, este comando agrega tu llave GPG al `.profile`. - - {% endnote %} - -{% endlinux %} - -### Leer más - -- "[Comprobar llaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -- "[Generar una llave GPG nueva](/articles/generating-a-new-gpg-key)" -- "[Utilizar una dirección de correo electrónico verificada en tu llave GPG](/articles/using-a-verified-email-address-in-your-gpg-key)" -- "[Agregar una llave GPG nueva a tu cuenta de GitHub](/articles/adding-a-new-gpg-key-to-your-github-account)" -- "[Asociar un correo electrónico con tu llave GPG](/articles/associating-an-email-with-your-gpg-key)" -- "[Firmar confirmaciones](/articles/signing-commits)" -- "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md deleted file mode 100644 index 68fddb3e8d..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Acerca de la autenticación de dos factores -intro: '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. Con la 2FA, tienes que iniciar sesión con tu nombre de usuario y contraseña y proporcionar otra forma de autenticación que solo tú conoces o tienes acceso a.' -redirect_from: - - /articles/about-two-factor-authentication - - /github/authenticating-to-github/about-two-factor-authentication -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - 2FA ---- -Para {% data variables.product.product_name %}, la segunda forma de autenticación es un código que es generado por una aplicación en tu dispositivo móvil{% if currentVersion == "free-pro-team@latest" %} o enviado como mensaje de texto (SMS){% endif %}. Una vez que activas la 2FA, {% data variables.product.product_name %} genera un código de autenticación cada vez que alguien intenta iniciar sesión en tu cuenta de {% data variables.product.product_name %}. El único modo en que alguien puede iniciar sesión en tu cuenta es si conoce la contraseña y si tiene acceso al código de autenticación de tu teléfono. - -{% data reusables.two_fa.after-2fa-add-security-key %} - -También puedes configurar métodos de recuperación adicionales en caso de que pierdas el acceso a tus credenciales de autenticación de dos factores. Para obtener más información acerca de la configuración de la 2FA, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" y "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)". - -Te recomendamos **enfáticamente** que habilites la 2FA para mantener la seguridad de tu cuenta, no solo en {% data variables.product.product_name %}, sino en otros sitios web y aplicaciones que la admitan. Puedes habilitar la 2FA para acceder a {% data variables.product.product_name %} y a {% data variables.product.prodname_desktop %}. - -Para obtener más información, consulta "[Acceder a {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)". - -### Códigos de recuperación de autenticación de dos factores - -{% data reusables.two_fa.about-recovery-codes %} Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". - -{% if currentVersion == "free-pro-team@latest" %} - -{% warning %} - -**Advertencia**: {% data reusables.two_fa.support-may-not-help %} Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". - -{% endwarning %} - -{% endif %} - -### Solicitar autenticación de dos factores en tu organización - -Los propietarios de la organización pueden solicitar que los miembros{% if currentVersion == "free-pro-team@latest" %} de la organización, los gerentes de facturación, {% endif %} y los colaboradores externos usen la autenticación de dos factores para proteger sus cuentas personales. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/articles/requiring-two-factor-authentication-in-your-organization)". - -{% data reusables.two_fa.auth_methods_2fa %} diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md deleted file mode 100644 index 85057391e7..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Acceder a GitHub utilizando la autenticación de dos factores -intro: 'Cuando habilitas la 2FA, se te pedirá que proporciones tu código de 2FA así como tu contraseña al momento de iniciar sesión en {% data variables.product.product_name %}.' -redirect_from: - - /articles/providing-your-2fa-security-code/ - - /articles/providing-your-2fa-authentication-code/ - - /articles/authenticating-to-github-using-fido-u2f-via-nfc/ - - /articles/accessing-github-using-two-factor-authentication - - /github/authenticating-to-github/accessing-github-using-two-factor-authentication -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - 2FA ---- -Al tener la autenticación de dos factores habilitada, necesitarás proporcionar el código de autenticación cuando accedes a {% data variables.product.product_name %} a través de tu buscador. Si accedes a {% data variables.product.product_name %} utilizando otros métodos, tales como la API o la línea de comandos, necesitarás utilizar una forma alterna de autenticación. Para obtener más información, consulta la sección "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)". - -### Proporcionar un código 2FA al iniciar sesión en el sitio web - -Después de iniciar sesión en {% data variables.product.product_name %} con tu contraseña, se te pedirá que brindes un código de autenticación desde un mensaje de texto de {% if currentVersion == "free-pro-team@latest" %} o {% endif %} tu app TOTP. - -{% data variables.product.product_name %} solo te pedirá que brindes tu código de autenticación 2FA nuevamente si has cerrado sesión, estás usando un dispositivo nuevo o si caduca tu sesión. - -#### Generar un código a través de una aplicación TOTP - -Si decides configurar una autenticación de dos factores mediante una aplicación TOTP en tu smartphone, puedes generar un código de autenticación para {% data variables.product.product_name %} en cualquier momento. En la mayoría de los casos, el lanzamiento de la aplicación generará un código nuevo. Deberías consultar la documentación de la aplicación para conocer las instrucciones específicas. - -Si eliminas las aplicaciones móviles después de configurar la autenticación de dos factores, deberás proporcionar tu código de recuperación para obtener acceso a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si perdiste las credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" - -{% if currentVersion == "free-pro-team@latest" %} - -#### Recibir un mensaje de texto - -Si configuras una autenticación de dos factores mediante mensajes de texto, {% data variables.product.product_name %} te enviará un mensaje de texto con tu código de autenticación. - -{% endif %} - -### Usar autenticación de dos factores con la línea de comando - -Después de haber habilitado 2FA, debes usar un token de acceso personal o una clave SSH en lugar de tu contraseña al acceder a {% data variables.product.product_name %} en la línea de comando. - -#### Autenticar en la línea de comando mediante HTTPS - -Después de haber habilitado 2FA, debes crear un token de acceso personal para usar una contraseña al autenticar a {% data variables.product.product_name %} en la línea de comando mediante las URL HTTPS. - -Cuando se te solicite el nombre de usuario y la contraseña en la línea de comando, usa tu nombre de usuario {% data variables.product.product_name %} y el token de acceso personal. La indicación de la línea de comando no especificará que debes ingresar tu token de acceso personal cuando se te solicite la contraseña. - -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)". - -#### Autenticar en la línea de comandos mediante SSH - -La habilitación de 2FA no cambia el modo de autenticar a {% data variables.product.product_name %} en la línea de comando mediante las URL SSH. Para obtener más información sobre cómo establecer y usar una clave SSH, consulta "[Conectar a {% data variables.product.prodname_dotcom %} con SSH](/articles/connecting-to-github-with-ssh/)". - -### Usar autenticación de dos factores para acceder a un repositorio mediante Subversion - -Cuando accedas a un repositorio mediante Subversion, debes proporcionar un token de acceso personal en lugar de ingresar tu contraseña. 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)". - -### Solución de problemas - -Si pierdes el acceso a tus credenciales de autenticación de dos factores, puedes usar tus códigos de recuperación u otro método de recuperación (si has configurado uno) para recuperar el acceso a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". - -Si tu autenticación falla varias veces, es posible que desees sincronizar el reloj de tu teléfono con tu proveedor móvil. Frecuentemente, esto involucra la verificación de la opción "Establecer automáticamente" en el reloj de tu teléfono, en lugar de brindar tu propia zona horaria. - -### Leer más - -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" -- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" -- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" -- [Recuperar tu cuenta si pierdes tus credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md deleted file mode 100644 index c721b1146c..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Cambiar los métodos de entrega de autenticación de dos factores para tu dispositivo móvil -intro: Puedes alternar entre la recepción de código de autenticación a través de un mensaje de texto o una aplicación móvil. -redirect_from: - - /articles/changing-two-factor-authentication-delivery-methods/ - - /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device - - /github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device -versions: - free-pro-team: '*' -topics: - - 2FA ---- -{% note %} - -**Nota:** El cambio de tu método de autenticación de dos factores invalida tu configuración de método de dos factores actual. Sin embargo, esto no afecta tus códigos de recuperación o configuración SMS de reserva. Puedes actualizar tus códigos de recuperación o configuración SMS de reserva o en la página de parámetros de seguridad de tu cuenta personal, si así lo deseas. - -{% endnote %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -3. Al lado de "SMS delivery" (Entrega de SMS), haz clic en **Edit** (Editar). ![Editar opciones de entrega de SMS](/assets/images/help/2fa/edit-sms-delivery-option.png) -4. En "Delivery options" (Opciones de entrega), haz clic en **Reconfigure two-factor authentication** (Reconfirgurar autenticación de dos factores). ![Cambiar tus opciones de entrega 2FA](/assets/images/help/2fa/2fa-switching-methods.png) -5. Decide si deseas configurar la autenticación de dos factores mediante una app móvil TOTP o un mensaje de texto. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". - - Para configurar la autenticación de dos factores mediante una app móvil TOTP, haz clic en **Set up using an app** (Configurar mediante una app). - - Para configurar la autenticación de dos factores mediante un mensaje de texto (SMS), haz clic en **Set up using SMS** (Configurar mediante SMS). - -### Leer más - -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" -- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md deleted file mode 100644 index 5d94779405..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -title: Configurar la autenticación de dos factores mediante métodos de recuperación -intro: Puedes configurar diversos métodos de recuperación para acceder a tu cuenta si pierdes tus credenciales de autenticación de dos factores. -redirect_from: - - /articles/downloading-your-two-factor-authentication-recovery-codes/ - - /articles/setting-a-fallback-authentication-number/ - - /articles/about-recover-accounts-elsewhere/ - - /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere/ - - /articles/generating-and-storing-an-account-recovery-token/ - - /articles/configuring-two-factor-authentication-recovery-methods - - /github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - 2FA ---- -Además de almacenar tus códigos de recuperación de autenticación de dos factores de manera segura, recomendamos configurar uno o más métodos de recuperación adicionales. - -### Descargar tus códigos de recuperación de autenticación de dos factores - -{% data reusables.two_fa.about-recovery-codes %} También puedes descargar tus códigos de recuperación en cualquier punto luego de habilitar la autenticación de dos factores. - -Para mantener la cuenta segura, no compartas ni distribuyas tus códigos de recuperación. Recomendamos guardarlos en un administrador de contraseñas seguro, como: -- [1Password](https://1password.com/) -- [Keeper](https://keepersecurity.com/) -- [LastPass](https://lastpass.com/) - -Si generas nuevos códigos de recuperación o inhabilitas y vuelves a habilitar 2FA, los códigos de recuperación de tus parámetros de seguridad se actualizarán automáticamente. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -{% data reusables.two_fa.show-recovery-codes %} -4. Guarda tus códigos de recuperación en un lugar seguro. Tus códigos de recuperación te ayudarán a regresar a tu cuenta si pierdes acceso. - - Para guardar tus códigos de recuperación en tu dispositivo, haz clic en **Download** (Descargar). - - Para guardar una copia impresa de tus códigos de recuperación, haz clic en **Print** (Imprimir). - - Para copiar tus códigos de recuperación a fin de almacenarlo en un administrador de contraseñas, haz clic en **Copy** (Copiar). ![Lista de códigos de recuperación con opción para descargar, imprimir o copiar los códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) - -### Generar un nuevo conjunto de códigos de recuperación - -Una vez que usas un código de recuperación para recuperar el acceso a tu cuenta, no puedes volver a usarlo. Si has usado los 16 códigos de recuperación, puedes generar otra lista de códigos. La generación de un nuevo conjunto de códigos de recuperación invalidará todos los códigos que generaste previamente. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -{% data reusables.two_fa.show-recovery-codes %} -3. Para crear otro lote de códigos de recuperación, haz clic en **Generate new recovery codes** (Generar nuevos códigos de recuperación). ![Botón para generar nuevos códigos de recuperación](/assets/images/help/2fa/generate-new-recovery-codes.png) - -### Configurar una clave de seguridad como un método de autenticación de dos factores adicional - -Puedes configurar una clave de seguridad como un método de autenticación de dos factores secundario, y usar la clave de seguridad para recuperar el acceso a tu cuenta. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". - -{% if currentVersion == "free-pro-team@latest" %} - -### Configurar un número de autenticación de reserva - -Puedes brindar un segundo número para un dispositivo de reserva. Si pierdes acceso a tu dispositivo primario y a tus códigos de recuperación, un número de SMS de respaldo puede volver a brindarte acceso a tu cuenta. - -Puedes usar un número de reserva independientemente de que hayas configurado la autenticación mediante un mensaje de texto o aplicación móvil TOTP. - -{% warning %} - -**Advertencia:** Usar un número de reserva es tu último recurso. Recomendamos configurar métodos de recuperación adicionales si estableces un número de autenticación de reserva. -- Los malos actores pueden atacar a los proveedores de teléfono celular, de manera que la autenticación SMS es riesgosa. -- Los mensajes SMS solo son compatibles para determinados países fuera de los EE. UU., para conocer la lista, consulta "[Países donde la autenticación SMS es compatible](/articles/countries-where-sms-authentication-is-supported)". - -{% endwarning %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -3. Al lado de "Fallback SMS number" (Número de SMS de reserva), haz clic en **Add** (Agregar). ![Botón para agregar número de SMS de reserva](/assets/images/help/2fa/add-fallback-sms-number-button.png) -4. En "Fallback SMS number" (Número de SMS de reserva), haz clic en **Add fallbacck SMS number (Agregar número de SMS de reserva). ![Agregar texto al número de SMS de reserva](/assets/images/help/2fa/add_fallback_sms_number_text.png)

    -5 -Selecciona tu código de país y escribe el número de teléfono móvil, incluido el número de área. Cuando la información es correcta, haz clic en **Set fallback** (Establecer reserva). ![Establecer número de SMS de reserva](/assets/images/help/2fa/2fa-fallback-number.png) - -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 - -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" -- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" -- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" -- [Recuperar tu cuenta si pierdes tus credenciales de autenticación de dos factores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md deleted file mode 100644 index 1948c48070..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ /dev/null @@ -1,119 +0,0 @@ ---- -title: Configurar la autenticación de dos factores -intro: Puedes elegir entre varias opciones para añadir una segunda fuente de autenticación a tu cuenta. -redirect_from: - - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app/ - - /articles/configuring-two-factor-authentication-via-text-message/ - - /articles/configuring-two-factor-authentication-via-fido-u2f/ - - /articles/configuring-two-factor-authentication - - /github/authenticating-to-github/configuring-two-factor-authentication -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - 2FA ---- -Puedes configurar la autenticación de dos factores usando una app móvil {% if currentVersion == "free-pro-team@latest" %} o mediante un mensaje de texto{% endif %}. También puedes agregar una clave de seguridad. - -Recomendamos encarecidamente el uso de una contraseña única basada en el tiempo (TOTP) para configurar 2FA.{% if currentVersion == "free-pro-team@latest" %}Las aplicaciones TOTP son más confiables que los SMS, especialmente para las ubicaciones fuera de los EE. UU.{% endif %}Las apps TOTP respaldan las copias de seguridad de los códigos de autenticación en la nube y pueden restaurarse si pierdes acceso a tu dispositivo. - -{% warning %} - -**Advertencia:** -- Si eres un miembro{% if currentVersion == "free-pro-team@latest" %}, gerente de facturación{% endif %} o colaborador externo de un repositorio privado de una organización que requiere autenticación de dos factores, debes salir de la organización antes de que puedas inhabilitar 2FA en {% data variables.product.product_location %}. -- Si inhabilitas 2FA, automáticamente perderás acceso a la organización y a cualquier bifurcación privada que tengas de los repositorios privados de la organización. Para volver a obtener acceso a la organización y a tus bifurcaciones, habilita nuevamente la autenticación de dos factores y comunícate con un propietario de la organización. - -{% endwarning %} - -### 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: -- [1Password](https://support.1password.com/one-time-passwords/) -- [Authy](https://authy.com/guides/github/) -- [LastPass Authenticator](https://lastpass.com/auth/) - -{% tip %} - -**Sugerencia**: Para configurar la autenticación mediante TOTP en múltiples dispositivos, durante la configuración, escanea el código QR usando todos los dispositivos al mismo tiempo. Si 2FA ya está habilitado y deseas agregar otro dispositivo, debes volver a configurar 2FA desde tus parámetros de seguridad. - -{% endtip %} - -1. Descargar una app TOTP. -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -{% data reusables.two_fa.enable-two-factor-authentication %} -5. En la página de autenticación de dos factores, haz clic en **Set up using an app** (Configurar mediante una app). -{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} -8. En la página de autenticación de dos factores, realiza una de las siguientes opciones: - - Escanea el código QR con la app del dispositivo móvil. Luego de escanear, la app muestra un código de seis dígitos que puedes ingresar en {% data variables.product.product_name %}. - - Si no puedes escanear el código QR, haz clic en **enter this text code** (escribir este código de texto) para ver un código que puedas copiar e ingresar manualmente en {% data variables.product.product_name %}. ![Haz clic para ingresar este código](/assets/images/help/2fa/totp-click-enter-code.png) -9. La aplicación móvil TOTP guarda tu cuenta {% data variables.product.product_name %} y genera un nuevo código de autenticación cada algunos segundos. En {% data variables.product.product_name %}, en la página 2FA, escribe el código y haz clic en **Enable** (Habilitar). ![Campo TOTP Enable (Habilitar TOTP)](/assets/images/help/2fa/totp-enter-code.png) -{% data reusables.two_fa.test_2fa_immediately %} - -{% if currentVersion == "free-pro-team@latest" %} - -### Configurar la autenticación de dos factores mediante mensajes de texto - -Si no puedes habilitar la autenticación mediante una app móvil TOTP, puedes autenticar mediante mensajes SMS. También puedes brindar un segundo número para un dispositivo de reserva. Si pierdes acceso a tu dispositivo primario y a tus códigos de recuperación, un número de SMS de respaldo puede volver a brindarte acceso a tu cuenta. - -Antes de usar este método, asegúrate de que puedes recibir mensajes de texto. Es posible que se apliquen tarifas de protador. - -{% warning %} - -**Advertencia:** **Recomendamos enérgicamente** el uso de una aplicación TOTP para la autenticación de dos factores en lugar de SMS. {% data variables.product.product_name %} no admite el envío de mensajes SMS a teléfonos en todos los países. Antes de configurar la autenticación a través de mensaje de texto, revisa la lista de países donde {% data variables.product.product_name %} respalda la autenticación mediante SMS. Para obtener más información, consulta "[Países donde es compatible la autenticación SMS](/articles/countries-where-sms-authentication-is-supported)". - -{% endwarning %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -{% data reusables.two_fa.enable-two-factor-authentication %} -4. En la página de autenticación de dos factores, haz clic en **Set up using SMS** (Configurar mediante SMS). -{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} -7. Selecciona tu código de país y escribe el número de teléfono móvil, incluido el número de área. Cuando la información es correcta, haz clic en **Send authentication code** (Enviar código de autenticación). ![Pantalla 2FA SMS](/assets/images/help/2fa/2fa_sms_photo.png) -8. Recibirás un mensaje de texto con un código de seguridad. Escribe el código en la página de autenticación de dos factores, y haz clic en **Enable** (Habilitar). ![Campo 2FA SMS continue (Continuación de 2FA SMS)](/assets/images/help/2fa/2fa-sms-code-enable.png) -{% data reusables.two_fa.test_2fa_immediately %} - -{% endif %} - -### Configurar la autenticación de dos factores mediante una clave de seguridad - -{% data reusables.two_fa.after-2fa-add-security-key %} - -En muchos dispositivos y buscadores, puedes utilizar una llave de seguridad física por USB o NFC. Algunos buscadores utilizan un lector de huella digital, reconocimiento facial o contraseña/NIP en tu dispositivo a modo de llave de seguridad. - -La autenticación con una clave de seguridad es *secundaria* para la autenticación con una aplicación TOTP{% if currentVersion == "free-pro-team@latest" %} o un mensaje de texto{% endif %}. Si pierdes tu llave de seguridad, aún podrás utilizar tu código de teléfono para ingresar. - -1. Ya debes tener configurado 2FA mediante una app móvil TOTP{% if currentVersion == "free-pro-team@latest" %} o mediante SMS{% endif %}. -2. Asegúrate de tener una -clave se seguridad compatible {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}WebAuthn{% else %}FIDO U2F{% endif %} insertada en tu computadora. -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -5. Al lado de "Security keys" (Claves de seguridad), haz clic en **Add** (Agregar). ![Agrega la opción de las claves de seguridad](/assets/images/help/2fa/add-security-keys-option.png) -6. En "Security keys" (Claves de seguridad), haz clic en **Register new security key** (Registrar clave de seguridad nueva). - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} - ![Registrar una nueva clave de seguridad](/assets/images/help/2fa/security-key-register.png) - {% else %} - ![Registrar un nuevo dispositivo FIDO U2F](/assets/images/help/2fa/register_new_fido_u2f_device.png) - {% endif %} -7. Escribe un sobrenombre para la clave de seguridad, luego haz clic en **Add** (Agregar). - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} - ![Porporcionar un sobrenombre para una clave de seguridad](/assets/images/help/2fa/security-key-nickname.png) - {% else %} - ![Brindar un sobrenombre para un dispositivo FIDO U2F](/assets/images/help/2fa/fido_u2f_nickname.png) - {% endif %} -8. Activa tu clave de seguridad, seguida por la documentación de tu clave de seguridad. - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} - ![Solicitar una clave de seguridad](/assets/images/help/2fa/security-key-prompt.png) - {% else %} - ![Solicitar un dispositivo FIDO U2F](/assets/images/help/2fa/fido_u2f_prompt_key.png) - {% endif %} -9. Confirma que has descargado tus códigos de recuperación y puedes acceder a ellos. Si aún no lo has hecho, o si deseas generar otro conjunto de códigos, descarga tus códigos y guárdalos en un lugar seguro. Si pierdes el acceso a tu cuenta, puedes usar tus códigos de recuperación para volver a ingresar a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". ![Botón Download recovery codes (Descargar códigos de recuperación)](/assets/images/help/2fa/2fa-recover-during-setup.png) -{% data reusables.two_fa.test_2fa_immediately %} - -### Leer más - -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" -- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" -- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" -- "[Recuperar tu cuenta si pierdes tus credenciales 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" -- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md deleted file mode 100644 index 3ce5e2c917..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -title: Países donde se admite la autenticación por SMS -intro: 'Debido a las tasas de éxito de la entrega, {% data variables.product.product_name %} solo admite autenticación de dos factores mediante SMS para determinados países.' -redirect_from: - - /articles/countries-where-sms-authentication-is-supported - - /github/authenticating-to-github/countries-where-sms-authentication-is-supported -versions: - free-pro-team: '*' -topics: - - 2FA ---- -Si no admitimos la autenticación de dos factores mediante mensaje de texto para tu país de residencia, puedes establecer la autenticación mediante una aplicación móvil TOTP. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". - -### Países admitidos para autenticación SMS - -Si tu país no está en la lista, significa que actualmente no podemos entregar mensajes de texto confiables a tu país. Actualizamos esta lista periódicamente. - -
      -
    • Islas Aland
      • -
    • Algeria
      • -
    • Angola
      • -
    • Anguilla
      • -
    • Australia
      • -
    • Austria
      • -
    • Bahamas
      • -
    • Bahrain
      • -
    • Bangladesh
      • -
    • Bielorusia
      • -
    • Bélgica
      • -
    • Benin
      • -
    • Bolivia
      • -
    • Bosnia y Herzegovina
      • -
    • Brunei
      • -
    • Bulgaria
      • -
    • Burundi
      • -
    • Camboya
      • -
    • Canadá
      • -
    • Cabo Verde
      • -
    • Islas Caimán
      • -
    • Isla de Navidad
      • -
    • Cocos
      • -
    • República Democrática del Congo
      • -
    • Croacia
      • -
    • Chipre
      • -
    • República Checa
      • -
    • Dinamarca
      • -
    • Dominica
      • -
    • República Dominicana
      • -
    • Ecuador
      • -
    • Guinea Ecuatorial
      • -
    • Estonia
      • -
    • Finlandia/Islas Aland
      • -
    • Francia
      • -
    • La Gambia
      • -
    • Georgia
      • -
    • Alemania
      • -
    • Ghana
      • -
    • Gibraltar
      • -
    • Grecia
      • -
    • Guatemala
      • -
    • Guyana
      • -
    • Hungría
      • -
    • Islandia
      • -
    • India
      • -
    • Indonesia
      • -
    • Irán
      • -
    • Irlanda
      • -
    • Israel
      • -
    • Italia
      • -
    • Costa de Marfil
      • -
    • Jamaica
      • -
    • Japón
      • -
    • Jordania
      • -
    • Kazakhstan
      • -
    • Kuwait
      • -
    • Letonia
      • -
    • Libia
      • -
    • Liechtenstein
      • -
    • Lituania
      • -
    • Luxemburgo
      • -
    • Madagascar
      • -
    • Malawi
      • -
    • Malasia
      • -
    • Maldivas
      • -
    • Mali
      • -
    • Malta
      • -
    • Isla Mauricio
      • -
    • México
      • -
    • Mónaco
      • -
    • Montenegro
      • -
    • Montserrat
      • -
    • Mozambique
      • -
    • Namibia
      • -
    • Países Bajos
      • -
    • Antillas Neerlandesas
      • -
    • Nueva Zelanda
      • -
    • Nigeria
      • -
    • Noruega
      • -
    • Filipinas
      • -
    • Polonia
      • -
    • Portugal
      • -
    • Catar
      • -
    • Rumania
      • -
    • Rusia
      • -
    • Ruanda
      • -
    • Senegal
      • -
    • Serbia
      • -
    • Islas Seychelles
      • -
    • Singapur
      • -
    • Eslovaquia
      • -
    • Eslovenia
      • -
    • Sudáfrica
      • -
    • Corea del Sur
      • -
    • España
      • -
    • Sri Lanka
      • -
    • St. Lucía
      • -
    • Sudán
      • -
    • Suecia
      • -
    • Suiza
      • -
    • Taiwán
      • -
    • Tanzania
      • -
    • Togo
      • -
    • Trinidad y Tobago
      • -
    • Turcas y Caicos
      • -
    • Uganda
      • -
    • Ucrania
      • -
    • Emiratos Árabes Unidos
      • -
    • Reino Unido
      • -
    • Estados Unidos
      • -
    • Uzbekistán
      • -
    • Venezuela
      • -
    - -### Leer más - -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md deleted file mode 100644 index 791ba04030..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Inhabilitar la autenticación de dos factores para tu cuenta personal -intro: 'Si inhabilitas la autenticación de dos factores para tu cuenta personal, puedes perder acceso a las organizaciones a las que perteneces.' -redirect_from: - - /articles/disabling-two-factor-authentication-for-your-personal-account - - /github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - 2FA ---- -Te recomendamos encarecidamente que uses la autenticación de dos factores para proteger tu cuenta. Si necesitas inhabilitar la autenticación de dos factores, te recomendamos habilitarla nuevamente lo antes posible. - -{% warning %} - -**Advertencia:** Si eres un miembro,{% if currentVersion == "free-pro-team@latest" %}, gerente de facturación{% endif %} o colaborador externo de un repositorio público de una organización que requiere autenticación de dos factores y procedes a su inhabilitación, serás automáticamente eliminado de la organización y ya no podrás acceder a sus repositorios. Para volver a obtener acceso a la organización, habilita nuevamente la autenticación de dos factores y comunícate con un propietario de la organización. - -{% endwarning %} - -Si tu organización requiere autenticación de dos factores y eres un miembro, propietario o colaborador externo de un repositorio privado de tu organización, primero debes abandonar la organización para poder inhabilitar la autenticación de dos factores. - -Para eliminarte a ti mismo de la organización: - - Como miembro o propietario de la organización, consulta "[Eliminarte a ti mismo de una organización](/articles/removing-yourself-from-an-organization/)". - - Como colaborador externo, solicita a un propietario de la organización o administrador de un repositorio que te elimine de los repositorios de la organización. Para obtener más información, consulta "[Ver los roles de las personas en una organización](/articles/viewing-people-s-roles-in-an-organization)" y "[Eliminar un colaborador externo de un repositorio de la organización](/articles/removing-an-outside-collaborator-from-an-organization-repository/)". - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -3. Click **Disable**. ![Botón Inhabilitar autenticación de dos factores](/assets/images/help/2fa/disable-two-factor-authentication.png) - -### Leer más - -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" -- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" -- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/index.md deleted file mode 100644 index 474ff41e37..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/index.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Asegurar tu cuenta con autenticación de dos factores (2FA) -intro: 'Puedes configurar tu cuenta {% data variables.product.product_name %} para requerir un código de autenticación además de tu contraseña cuando te registras.' -redirect_from: - - /categories/84/articles/ - - /categories/two-factor-authentication-2fa/ - - /articles/securing-your-account-with-two-factor-authentication-2fa -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - 2FA -children: - - /about-two-factor-authentication - - /configuring-two-factor-authentication - - /configuring-two-factor-authentication-recovery-methods - - /accessing-github-using-two-factor-authentication - - /recovering-your-account-if-you-lose-your-2fa-credentials - - /changing-two-factor-authentication-delivery-methods-for-your-mobile-device - - /countries-where-sms-authentication-is-supported - - /disabling-two-factor-authentication-for-your-personal-account ---- - diff --git a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md deleted file mode 100644 index 4dcca088d1..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Recuperar tu cuenta si pierdes tus credenciales 2FA -intro: 'Si pierdes el acceso a tus credenciales de autenticación de dos factores, puedes utilizar tus códigos de recuperación, o cualquier otra opción de recuperación, para recuperar el acceso a tu cuenta.' -redirect_from: - - /articles/recovering-your-account-if-you-lost-your-2fa-credentials/ - - /articles/authenticating-with-an-account-recovery-token/ - - /articles/recovering-your-account-if-you-lose-your-2fa-credentials - - /github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - 2FA ---- -{% if currentVersion == "free-pro-team@latest" %} - -{% warning %} - -**Advertencia**: {% data reusables.two_fa.support-may-not-help %} - -{% endwarning %} - -{% endif %} - -### Utilizar un código de recuperación de autenticación de dos factores - -Utiliza uno de tus códigos de recuperación para recuperar automáticamente el ingreso a tu cuenta. Es posible que hayas guardado tus códigos de recuperación en un administrador de contraseñas o en la carpeta de descargas de tu computadora. El nombre de archivo por defecto para códigos de recuperación es `github-recovery-codes.txt`. Para obtener más información acerca de códigos de recuperación, consulta "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)." - -{% data reusables.two_fa.username-password %}{% if currentVersion == "free-pro-team@latest" %} -2. Da clic en **Ingresar un código de recuperación de dos factores** debajo de "¿Tienes Problemas?". ![Link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png){% else %} -2. En la página 2FA, dentro de "Don't have your phone?" (¿No tienes tu teléfono?), haz clic en **Enter a two-factor recovery code (Ingresar un código de recuperación de dos factores)**. ![Link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} -3. Escribe uno de tus códigos de recuperación, después haz clic en **Verify (Verificar)**. ![Campo para escribir un código de recuperación y botón Verificar](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) - -{% if currentVersion == "free-pro-team@latest" %} -### Autenticar con un número de reserva - -Si pierdes el acceso a tu app TOTP principal o número de teléfono, puedes proporcionar un código de autenticación de dos factores enviado a tu número de reserva para recuperar automáticamente el acceso a tu cuenta. -{% endif %} - -### Autenticar con una clave de seguridad - -Si has configurado autenticación de dos factores utilizando una clave de seguridad, puedes utilizar tu clave de seguridad como un método de autenticación secundario para obtener acceso a tu cuenta automáticamente. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". - -{% if currentVersion == "free-pro-team@latest" %} -### Autentificarse con un dispositivo verificado, token SSH, o token de acceso personal -Si pierdes el acceso a tus credenciales de autenticación de dos factores y no tienes tus códigos de recuperación para atutenticación de dos factores, se puede enviar una contraseña de única ocasión a tu dirección de correo electrónico verificada para comenzar el proceso de verificación y recobrar el acceso a tu cuenta. - -{% note %} - -**Nota**: Por razones de seguridad, recobrar el acceso a tu cuenta autenticándose con una contraseña de una sola ocasión puede demorar de 3 a 5 días hábiles. Las solicitudes adicionales emitidas durante este periodo no se revisarán. - -{% endnote %} - -Puedes utilizar tus credenciales de autenticación de dos factores para recobrar el acceso a tu cuenta en cualquier momento durante el periodo de espera de 3 a 5 días. - -{% data reusables.two_fa.username-password %} -2. Da clic en **¿No puedes acceder a tu dispositivo de dos factores o a tus códigos de recuperación válidos?** debajo de "¿Tienes Problemas ![Enlace si no tienes tu dispositivo de 2fa o códigos de recuperación](/assets/images/help/2fa/no-access-link.png) -3. Da clic en **Entiendo, comenzar** para solicitar un restablecimiento de tu configuración de autenticación. ![Botón de restablecimiento de configuración de autenticación](/assets/images/help/2fa/reset-auth-settings.png) -4. Da clic en **Enviar contraseña de una sola vez** para enviarla a todas las direcciones de correo electrónico asociadas con tu cuenta. ![Botón para enviar contraseña de una sola vez](/assets/images/help/2fa/send-one-time-password.png) -5. Teclea la contraseña recibida en el correo electrónico de recuperación debajo de "Contraseña de una sola vez"{% data variables.product.prodname_dotcom %}. ![Campo para contraseña de una sola vez](/assets/images/help/2fa/one-time-password-field.png) -6. Da clic en **Verificar dirección de correo electrónico**. -7. Escoge un factor de verificación alterno. - - Si has utilizado tu dispositivo actual para ingresar en esta cuenta antes y quieres utilizarlo para verificación, da clic en **Verificar este dispositivo**. - - Si has configurado una llave SSH previamente en esta cuenta y quieres utilizarla para verificación, da clic en **Llave SSH**. - - Si configuraste un token de acceso personal previamente y te gustaría utilizarlo para verificación, da clic en **Token de acceso personal**. ![Botones de verificación alternativa](/assets/images/help/2fa/alt-verifications.png) -8. Un miembro de {% data variables.contact.github_support %} revisará tu solicitud y te enviará un mensaje de correo electrónico dentro de los siguientes 3 a 5 días. Si se aprueba tu solicitud, recibirás un enlace para completar el proceso de recuperación de tu cuenta. Si se te niega la solicitud, el mensaje incluirá un medio para contactar a soporte con cualquier pregunta adicional. - -### Autenticar con un token de recuperación de cuenta - -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. - -Si te es imposible recuperar el acceso a tu cuenta, genera una contraseña de una sola vez para recuperarlo. Para obtener más información, consulta "[Autenticarse con un dispositivo verificado, token, ssh, o token de acceso personal](#authenticating-with-a-verified-device-ssh-token-or-personal-access-token)". - -{% warning %} - -**Advertencias:** -- Antes de recuperar un token de recuperación de cuenta, deberías tratar de utilizar tus [códigos de autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication) o tus códigos de recuperación de autenticación de dos factores para recuperar el acceso a tu cuenta. Para obtener más información, consulta "[Recuperar tu cuenta si pierdes tus credenciales de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". - -{% endwarning %} - -1. En Facebook, desplázate hasta tus [Configuraciones de seguridad](https://www.facebook.com/settings?tab=security), después haz clic en **Recover Accounts Elsewhere (Recuperar cuentas en otro lugar)**. ![Página de configuraciones de seguridad de Facebook con enlace Recuperar cuentas en otro lugar](/assets/images/help/settings/security-facebook-security-settings-page.png) -2. Haz clic en el token de recuperación asociado con tu cuenta {% data variables.product.product_name %}. ![Lista de tokens de recuperación almacenados en Facebook](/assets/images/help/settings/security-github-rae-token-on-facebook.png) -3. Para rescatar tu token de recuperación de cuenta, haz clic en **Recover This Account (Recuperar esta cuenta)**. Se abrirá una nueva ventana, que te llevará de vuelta a {% data variables.product.product_name %}. ![Casilla modal con información acerca de tu token de recuperación y botón Recuperar esta cuenta](/assets/images/help/settings/security-recover-account-facebook.png) -4. Contacta a {% data variables.contact.contact_support %} para hacerles saber que tu token de recuperación de cuenta está lista para revisión. -{% endif %} - -### Leer más - -- "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)" -- [Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" -- [Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)" -- "[Acceder {% data variables.product.prodname_dotcom %} utilizando autenticación de dos factores](/articles/accessing-github-using-two-factor-authentication)" diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md deleted file mode 100644 index 352b5beeba..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Comprobar el estado de verificación de firma de la confirmación y de la etiqueta -intro: 'Puedes comprobar el estado de verificación de las firmas de tu confirmación y de la etiqueta en {% data variables.product.product_name %}.' -redirect_from: - - /articles/checking-your-gpg-commit-and-tag-signature-verification-status/ - - /articles/checking-your-commit-and-tag-signature-verification-status - - /github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -### Comprobar el estado de verificación de firma de la confirmación - -1. En {% data variables.product.product_name %}, desplázate hasta la solicitud de extracción. -{% data reusables.repositories.review-pr-commits %} -3. Junto al hash de confirmación abreviado de la confirmación, existe un cuadro que muestra si la firma de la confirmación está verificada o no está verificada. ![Confirmación firmada](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png) -4. Para ver información más detallada sobre la firma de confirmación, haz clic en **Verified** (Verificada) o **Unverified** (No verificada). ![Confirmación firmada verificada](/assets/images/help/commits/gpg-signed-commit_verified_details.png) - -Si la firma de tu confirmación no está verificada, puedes aprender más sobre por qué haciendo clic en el cuadro **Unverified** (No verificado). ![Confirmación firmada no verificada](/assets/images/help/commits/gpg-signed-commit-unverified-details.png) - -### Comprobar el estado de verificación de firma de la etiqueta - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.releases %} -2. En la parte superior de la página de lanzamiento, haz clic en **Tags** (Etiqueta). ![Página de etiquetas](/assets/images/help/releases/tags-list.png) -3. Junto a la descripción de tu etiqueta, hay un cuadro que muestra si la firma de la etiqueta está verificada o no está verificada. ![firma de etiqueta verificada](/assets/images/help/commits/gpg-signed-tag-verified.png) -4. Para ver información más detallada sobre la firma de la etiqueta, haz clic en **Verified** (Verificada) o **Unverified** (No verificada). Si la firma de tu etiqueta no está verificada, puedes aprender más sobre por qué haciendo clic en el cuadro **Unverified** (No verificado). ![Etiqueta firmada verificada](/assets/images/help/commits/gpg-signed-tag-verified-details.png) - -### Leer más - -- "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" -- "[Firmar confirmaciones](/articles/signing-commits)" -- "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/index.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/index.md deleted file mode 100644 index 5f60ba4e01..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Solucionar problemas de verificación de confirmación de firma -intro: 'Puede que debas solucionar problemas imprevistos que surgen cuando se firman confirmaciones de forma local para la verificación en {% data variables.product.product_name %}.' -redirect_from: - - /articles/troubleshooting-gpg/ - - /articles/troubleshooting-commit-signature-verification -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management -children: - - /checking-your-commit-and-tag-signature-verification-status - - /updating-an-expired-gpg-key - - /using-a-verified-email-address-in-your-gpg-key ---- - diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key.md deleted file mode 100644 index 53d4edd7ce..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Actualizar una llave GPG vencida -intro: 'Cuando verifica una firma, {% data variables.product.product_name %} comprueba que la clave no esté revocada o vencida. Si tu clave de firma está revocada o vencida, {% data variables.product.product_name %} no puede verificar tus firmas. Si tu clave está revocada, utiliza la clave principal u otra clave que no esté revocada para firmar tus confirmaciones.' -redirect_from: - - /articles/updating-an-expired-gpg-key - - /github/authenticating-to-github/updating-an-expired-gpg-key -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -Si tu clave está vencida, debes [actualizar el vencimiento](https://www.gnupg.org/gph/en/manual/c235.html#AEN328), exportar la clave nueva, eliminar la clave vencida en tu cuenta de GitHub y [cargar la clave nueva para GitHub](/articles/adding-a-new-gpg-key-to-your-github-account/). Tus confirmaciones y etiquetas previas se mostrarán como verificadas, siempre que la clave reúna todos los demás requisitos de verificación. - -Si tu clave es inválida y no utilizas otra clave válida de tu conjunto de claves, pero en su lugar generas una llave GPG nueva con un conjunto nuevo de credenciales, tus confirmaciones hechas con la clave revocada o vencida se seguirán mostrando como no verificadas. Asimismo, tus credenciales nuevas no podrán volver a firmar o verificar tus confirmaciones y etiquetas antiguas. - -### Leer más - -- "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key.md deleted file mode 100644 index 8ea0fd610a..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Utilizar una dirección de correo electrónico verificada en tu llave GPG -intro: 'Cuando verifica una firma, {% data variables.product.product_name %} comprueba que la dirección de correo electrónico de la persona que confirma el cambio o del etiquetador coincida con una dirección de correo electrónico de las identidades de llave GPG y que sea una dirección de correo electrónico verificada en la cuenta del usuario. Esto garantiza que la clave te pertenece y que tú creaste la confirmación o etiqueta.' -redirect_from: - - /articles/using-a-verified-email-address-in-your-gpg-key - - /github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Identity - - Access management ---- -{% if currentVersion == "free-pro-team@latest" %} -Si debes verificar tu dirección de correo electrónico de GitHub, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address/)". -{% endif %}Si debes actualizar o agregar una dirección de correo electrónico para tu llave GPG, consulta "[Asociar un correo electrónico a tu llave GPG](/articles/associating-an-email-with-your-gpg-key)". - -Las confirmaciones y etiquetas pueden contener varias direcciones de correo electrónico. Para las confirmaciones, está el autor —la persona que escribió el código— y la persona que confirma el cambio —la persona que agregó la confirmación al árbol—. Cuando se firma una confirmación con Git, sea durante una fusión, cherry-picking o `confirmación git` normal, la dirección de correo electrónico de la persona que confirma el cambio debe ser la tuya, incluso si la dirección de correo electrónico del autor no lo es. Con las etiquetas es más simple: la dirección de correo electrónico del etiquetador es siempre la del usuario que creó la etiqueta. - -Si debes cambiar la dirección de correo electrónico de la persona que confirma el cambio o del etiquetador, consulta "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address/)". - -### Leer más - -- "[Acerca de la verificación de la firma de confirmación](/articles/about-commit-signature-verification)" diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/deleted-or-missing-ssh-keys.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/deleted-or-missing-ssh-keys.md deleted file mode 100644 index 3c49fd25f6..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/deleted-or-missing-ssh-keys.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Claves SSH eliminadas o faltantes -intro: 'Como precaución de seguridad, {% data variables.product.prodname_dotcom %} elimina automáticamente las claves SSH que no se han usado durante un año.' -redirect_from: - - /articles/deleted-or-missing-ssh-keys - - /github/authenticating-to-github/deleted-or-missing-ssh-keys -versions: - free-pro-team: '*' -topics: - - SSH ---- -{% data variables.product.prodname_dotcom %} elimina automáticamente las claves SSH inactivas para mantener la seguridad de las cuentas, por ejemplo, cuando alguien deja el trabajo o pierde su computadora. - -Puedes verificar si has usado o no una clave SSH durante un año revisando el registro de seguridad de tu cuenta. Para obtener más información, consulta "[Revisar tu registro de seguridad](/articles/reviewing-your-security-log/)". - -Una vez que tu clave SSh se ha eliminado, debes generar una nueva clave SSH y asociarla con tu cuenta. Para obtener más información, consulta "[Generar una nueva clave SSH y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)" y "[Agregar una nueva clave SSH a tu cuenta GitHub](/articles/adding-a-new-ssh-key-to-your-github-account/)". diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md deleted file mode 100644 index 932f86bdae..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: 'Error: El agente admitió una falla para registrarse' -intro: 'En circunstancias muy poco frecuentes, al conectarse con {% data variables.product.product_name %} mediante SSH en Linux produce el error "El agente admitió una falla para registrarse usando la clave". Sigue los pasos siguientes para resolver el problema.' -redirect_from: - - /articles/error-agent-admitted-failure-to-sign-using-the-key/ - - /articles/error-agent-admitted-failure-to-sign - - /github/authenticating-to-github/error-agent-admitted-failure-to-sign -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Cuando intentes implementar SSH en {% data variables.product.product_location %} en una computadora con Linux, posiblemente veas el siguiente mensaje en tu terminal: - -```shell -$ ssh -vT git@{% data variables.command_line.codeblock %} -> ... -> Agent admitted failure to sign using the key. -> debug1: No more authentication methods to try. -> Permission denied (publickey). -``` - -Para conocer más detalles, consulta este informe de propuesta. - -### Resolución - -Deberías poder solucionar este error al cargar tus claves en tu agente de SSH con `ssh-add`: - -```shell -# start the ssh-agent in the background -$ eval "$(ssh-agent -s)" -> Agent pid 59566 -$ ssh-add -> Enter passphrase for /home/you/.ssh/id_rsa: [tippy tap] -> Identity added: /home/you/.ssh/id_rsa (/home/you/.ssh/id_rsa) -``` - -Si tu clave no tiene el nombre de archivo predeterminado (`/.ssh/id_rsa`), deberás pasar esa ruta a `ssh-add`: - -```shell -# start the ssh-agent in the background -$ eval "$(ssh-agent -s)" -> Agent pid 59566 -$ ssh-add ~/.ssh/my_other_key -> Enter passphrase for /home/you/.ssh/my_other_key: [tappity tap tap] -> Identity added: /home/you/.ssh/my_other_key (/home/you/.ssh/my_other_key) -``` diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-bad-file-number.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-bad-file-number.md deleted file mode 100644 index e150baacbe..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-bad-file-number.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: 'Error: Número de archivo erróneo' -intro: 'Este error, por lo general, significa que no has podido conectarte al servidor. A menudo es causado por los firewalls y los servidores proxy.' -redirect_from: - - /articles/error-bad-file-number - - /github/authenticating-to-github/error-bad-file-number -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Cuando ejecutes comandos Git remotos o SSH, tu conexión puede quedar inactiva: - -```shell -$ ssh -vT git@{% data variables.command_line.codeblock %} -> OpenSSH_5.8p1, OpenSSL 1.0.0d 8 Feb 2011 -> debug1: Connecting to {% data variables.command_line.codeblock %} [207.97.227.239] port 22. -> debug1: connect to address 207.97.227.239 port 22: Connection timed out -> ssh: connect to host {% data variables.command_line.codeblock %} port 22: Connection timed out -> ssh: connect to host {% data variables.command_line.codeblock %} port 22: Bad file number -``` - -### Resolver el problema - -#### Usa HTTPS - -A menudo la solución más sencilla es simplemente evitar por completo el SSH. La mayoría de los firewalls y los proxys permiten el tráfico de HTTPS sin problemas. Para aprovechar esto, cambia [la URL remota](/articles/which-remote-url-should-i-use) que estás usando: - -```shell -$ git clone https://{% data variables.command_line.codeblock %}/username/reponame.git -> Cloning into 'reponame'... -> remote: Counting objects: 84, done. -> remote: Compressing objects: 100% (45/45), done. -> remote: Total 84 (delta 43), reused 78 (delta 37) -> Unpacking objects: 100% (84/84), done. -``` - -#### Prueba desde una red diferente - -Si puedes conectar la computadora a otra red que no tenga un firewall, puedes tratar de probar tu conexión de SSH a {% data variables.product.product_name %}. Si todo funciona como es debido, comunícate con tu administrador de red para que te ayude a cambiar los parámetros del firewall para permitir que tu conexión de SSH a {% data variables.product.product_name %} se establezca sin problemas. - -{% if currentVersion == "free-pro-team@latest" %} - -#### Uso de SSH a través del puerto HTTPS - -Si usar HTTPS no es una opción y tu administrador de firewall no permite las conexiones de SSH, puedes intentar usar [SSH a través del puerto HTTPS](/articles/using-ssh-over-the-https-port). - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -### Leer más - -- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" - -{% endif %} diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-key-already-in-use.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-key-already-in-use.md deleted file mode 100644 index 8f11dae364..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-key-already-in-use.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: 'Error: La clave ya está en uso' -intro: 'Este error se produce cuando intentas [agregar una clave](/articles/adding-a-new-ssh-key-to-your-github-account) que ya ha sido agregada a otra cuenta o repositorio.' -redirect_from: - - /articles/error-key-already-in-use - - /github/authenticating-to-github/error-key-already-in-use -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -### Determinar dónde se ha usado la clave - -Para determinar dónde se ha usado la clave, abre una terminal y escribe el comando `ssh`. Usa la marca `-i` para obtener la ruta a la clave que deseas verificar: - -```shell -$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} -# Connect to {% data variables.product.product_location %} using a specific ssh key -> Hi username! Has autenticado con éxito, pero GitHub no -> proporciona acceso al shell. -``` - -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). - -### Resolver el problema - -Para resolver el problema, primero elimina la clave de la otra cuenta o repositorio y luego [agrégala a tu cuenta](/articles/adding-a-new-ssh-key-to-your-github-account). - -Si no tienes permisos para transferir la clave y no puedes comunicarte con un usuario que los tenga, elimina el par de claves y [genera uno nuevo](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). - -### Llaves de implementación - -Una vez que una clave se ha vinculado a un repositorio como llave de implementación, no se la puede usar en otro repositorio. Si se te muestra este error mientras configuras las llaves de despliegue, consulta la sección "[Administrar las llaves de despliegue](/guides/managing-deploy-keys)". diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-denied-publickey.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-denied-publickey.md deleted file mode 100644 index 071514e317..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-denied-publickey.md +++ /dev/null @@ -1,281 +0,0 @@ ---- -title: 'Error: Permission denied (publickey)' -intro: 'A "Permission denied" error means that the server rejected your connection. There could be several reasons why, and the most common examples are explained below.' -redirect_from: - - /articles/error-permission-denied-publickey - - /github/authenticating-to-github/error-permission-denied-publickey -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -### Should the `sudo` command be used with Git? - -You should not be using the `sudo` command with Git. If you have a *very good reason* you must use `sudo`, then ensure you are using it with every command (it's probably just better to use `su` to get a shell as root at that point). If you [generate SSH keys](/articles/generating-an-ssh-key) without `sudo` and then try to use a command like `sudo git push`, you won't be using the same keys that you generated. - -### Check that you are connecting to the correct server - -Typing is hard, we all know it. Pay attention to what you type; you won't be able to connect to "githib.com" or "guthub.com". In some cases, a corporate network may cause issues resolving the DNS record as well. - -To make sure you are connecting to the right domain, you can enter the following command: - -```shell -$ ssh -vT git@{% data variables.command_line.codeblock %} -> OpenSSH_8.1p1, LibreSSL 2.7.3 -> debug1: Reading configuration data /Users/you/.ssh/config -> debug1: Reading configuration data /etc/ssh/ssh_config -> debug1: /etc/ssh/ssh_config line 47: Applying options for * -> debug1: Connecting to {% data variables.command_line.codeblock %} port 22. -``` - -The connection should be made on port 22{% if currentVersion == "free-pro-team@latest" %}, unless you're overriding settings to use [SSH over HTTPS](/articles/using-ssh-over-the-https-port){% endif %}. - -### Always use the "git" user - -All connections, including those for remote URLs, must be made as the "git" user. If you try to connect with your {% data variables.product.product_name %} username, it will fail: - -```shell -$ ssh -T GITHUB-USERNAME@{% data variables.command_line.codeblock %} -> Permission denied (publickey). -``` -If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/articles/changing-a-remote-s-url/). - -You should verify your connection by typing: - -```shell -$ ssh -T git@{% data variables.command_line.codeblock %} -> Hi username! You've successfully authenticated... -``` - -### Make sure you have a key that is being used - -{% mac %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're using OpenSSH 6.7 or older: - ```shell - # start the ssh-agent in the background - $ eval "$(ssh-agent -s)" - > Agent pid 59566 - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - # start the ssh-agent in the background - $ eval "$(ssh-agent -s)" - > Agent pid 59566 - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) - ``` - {% else %} - ```shell - # start the ssh-agent in the background - $ eval "$(ssh-agent -s)" - > Agent pid 59566 - $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) - ```{% endif %} - -{% endmac %} - -{% windows %} - -{% data reusables.desktop.windows_git_bash %} - -1. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} - - {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're using OpenSSH 6.7 or older: - ```shell - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) - ``` - {% else %} - ```shell - $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) - ```{% endif %} - -{% endwindows %} - -{% linux %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Verify that you have a private key generated and loaded into SSH. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're using OpenSSH 6.7 or older: - ```shell - # start the ssh-agent in the background - $ eval "$(ssh-agent -s)" - > Agent pid 59566 - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - # start the ssh-agent in the background - $ eval "$(ssh-agent -s)" - > Agent pid 59566 - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA) - ``` - {% else %} - ```shell - $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) - ```{% endif %} - - -{% endlinux %} - -The `ssh-add` command *should* print out a long string of numbers and letters. If it does not print anything, you will need to [generate a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and associate it with {% data variables.product.product_name %}. - -{% tip %} - -**Tip**: On most systems the default private keys (`~/.ssh/id_rsa` and `~/.ssh/identity`) are automatically added to the SSH authentication agent. You shouldn't need to run `ssh-add path/to/key` unless you override the file name when you generate a key. - -{% endtip %} - -#### Getting more details - -You can also check that the key is being used by trying to connect to `git@{% data variables.command_line.backticks %}`: - -```shell -$ ssh -vT git@{% data variables.command_line.codeblock %} -> ... -> debug1: identity file /Users/you/.ssh/id_rsa type -1 -> debug1: identity file /Users/you/.ssh/id_rsa-cert type -1 -> debug1: identity file /Users/you/.ssh/id_dsa type -1 -> debug1: identity file /Users/you/.ssh/id_dsa-cert type -1 -> ... -> debug1: Authentications that can continue: publickey -> debug1: Next authentication method: publickey -> debug1: Trying private key: /Users/you/.ssh/id_rsa -> debug1: Trying private key: /Users/you/.ssh/id_dsa -> debug1: No more authentication methods to try. -> Permission denied (publickey). -``` - -In that example, we did not have any keys for SSH to use. The "-1" at the end of the "identity file" lines means SSH couldn't find a file to use. Later on, the "Trying private key" lines also indicate that no file was found. If a file existed, those lines would be "1" and "Offering public key", respectively: - -```shell -$ ssh -vT git@{% data variables.command_line.codeblock %} -> ... -> debug1: identity file /Users/you/.ssh/id_rsa type 1 -> ... -> debug1: Authentications that can continue: publickey -> debug1: Next authentication method: publickey -> debug1: Offering RSA public key: /Users/you/.ssh/id_rsa -``` - -### Verify the public key is attached to your account - -You must provide your public key to {% data variables.product.product_name %} to establish a secure connection. - -{% mac %} - -1. Open Terminal. -2. Start SSH agent in the background. - ```shell - $ eval "$(ssh-agent -s)" - > Agent pid 59566 - ``` -3. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're using OpenSSH 6.7 or older: - ```shell - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - {% else %} - ```shell - $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) - ```{% endif %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -6. Compare the list of SSH keys with the output from the `ssh-add` command. -![SSH key listing in {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png) - -{% endmac %} - -{% windows %} - -1. Open the command line. -2. Start SSH agent in the background. - ```shell - $ ssh-agent -s - > Agent pid 59566 - ``` -3. Find and take a note of your public key fingerprint. {% if currentVersion ver_lt "enterprise-server@2.23" %}If you're using OpenSSH 6.7 or older: - ```shell - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - {% else %} - ```shell - $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) - ```{% endif %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -6. Compare the list of SSH keys with the output from the `ssh-add` command. -![SSH key listing in {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png) - -{% endwindows %} - -{% linux %} - -1. Open Terminal. -2. Start SSH agent in the background. - ```shell - $ eval "$(ssh-agent -s)" - > Agent pid 59566 - ``` -3. Find and take a note of your public key fingerprint. If you're using OpenSSH 6.7 or older: - ```shell - $ ssh-add -l - > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - - If you're using OpenSSH 6.8 or newer: - ```shell - $ ssh-add -l -E md5 - > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA) - ``` - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.ssh %} -6. Compare the list of SSH keys with the output from the `ssh-add` command. -![SSH key listing in {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png) - -{% endlinux %} - -If you don't see your public key in {% data variables.product.product_name %}, you'll need to [add your SSH key to {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account) to associate it with your computer. - -{% warning %} - -**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %}, for further help. An unidentified public key may indicate a possible security concern. For more information, see "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)." - -{% endwarning %} diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user.md deleted file mode 100644 index d6985725df..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: 'Error: Permiso de usuario/repo denegado a otro usuario' -intro: Este error significa que la clave con la que estás subiendo está conectada con una cuenta que no tiene acceso al repositorio. -redirect_from: - - /articles/error-permission-to-user-repo-denied-to-other-user - - /articles/error-permission-to-userrepo-denied-to-other-user - - /github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Para resolverlo, el propietario del repositorio (`user`) debe agregar tu cuenta (`other-user`) como colaborador en el repositorio o en un equipo que tenga acceso de escritura al repositorio. diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo.md deleted file mode 100644 index bba2d46a12..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: 'Error: Permiso de usuario/repo denegado al usuario/otro repo' -intro: 'Este error significa que la clave con la que estás subiendo se encuentra conectada con otro repositorio como llave de implementación, y no tiene acceso al repositorio al que estás intentado subir.' -redirect_from: - - /articles/error-permission-to-user-repo-denied-to-user-other-repo - - /articles/error-permission-to-userrepo-denied-to-userother-repo - - /github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Para resolverlo, elimina la llave de implementación del repositorio y [agrega la clave a tu cuenta](/articles/adding-a-new-ssh-key-to-your-github-account) en lugar de esa llave. - -Si la clave que estás usando está diseñada para funcionar como una llave de implementación, consulta [nuestra guía sobre llaves de implementación](/guides/managing-deploy-keys) para conocer más detalles. diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-ssh-add-illegal-option----k.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-ssh-add-illegal-option----k.md deleted file mode 100644 index e686aa7675..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-ssh-add-illegal-option----k.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: 'Error: ssh-add: opción ilegal -- K' -intro: 'Este error significa que tu versión de `ssh-add` no es compatible con la integración keychain macOS, que te permite almacenar tu contraseña en la keychain.' -redirect_from: - - /articles/error-ssh-add-illegal-option-k - - /articles/error-ssh-add-illegal-option----k - - /github/authenticating-to-github/error-ssh-add-illegal-option----k -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -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 clave SSH al ssh-agent. Si has instalado una versión diferente de `ssh-add`, es posible que no sea compatible para `-K`. - -### Resolver el problema - -Para agregar tu llave privada SSH al ssh-agent, puedes especificar la ruta a la versión de Apple de `ssh-add`: - -```shell - $ /usr/bin/ssh-add -K ~/.ssh/id_rsa -``` - -{% note %} - -**Nota:** {% data reusables.ssh.add-ssh-key-to-ssh-agent %} - -{% endnote %} - -### Leer más - -- "[Generar una clave SSH nueva y agregarla al ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" -- [Página de manual de Linux para SSH-ADD](http://man7.org/linux/man-pages/man1/ssh-add.1.html) -- Para ver la página del manual de Apple para SSH-ADD, ejecuta `man ssh-add` en Terminal. diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md deleted file mode 100644 index ad47e64f39..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: 'Error: Problema en el certificado SSL, verificar que el certif. CA esté bien' -intro: 'Este error significa que el certificado raíz de tu CA está desactualizado. Si es necesario actualizar el certificado de raíz de tu CA, no podrás subir ni extraer desde los repositorios de {% data variables.product.product_name %}.' -redirect_from: - - /articles/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok - - /github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok -versions: - free-pro-team: '*' -topics: - - SSH ---- -Probablemente recibirás el siguiente error: - -```shell -$ git push -u github.master -> fatal: 'github.master' does not appear to be a git repository -> fatal: The remote end hung up unexpectedly - -$ git pull -u github -> error: SSL certificate problem, verify that the CA cert is OK. Details: -> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed while accessing https://github.com/tqisjim/google-oauth.git/info/refs -> fatal: HTTP request failed -``` - -"CA" es la forma abreviada de "autoridad de certificado". Las autoridades de certificado son un grupo independiente responsable de manejar las conexiones seguras en la web. Estas autoridades establecen "certificados" digitales, que son una forma de asegurar que las conexiones entre dos máquinas (como tu computadora y GitHub.com) son válidas. Sin un certificado, el riesgo de seguridad entre dos máquinas es mayor. - -Cuando recibes este error, probablemente significa que tu CA está desactualizado y requiere una actualización. Por lo general, al actualizar tu sistema operativo también se actualizar tu CA y se resuelve el problema. diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md deleted file mode 100644 index 9443d19f5c..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: 'Error: Estamos haciendo una auditoría de clave SSH' -intro: Este error significa que la clave SSH que estás usando para realizar una operación Git no está verificada. -redirect_from: - - /articles/error-we-re-doing-an-ssh-key-audit - - /articles/error-were-doing-an-ssh-key-audit - - /github/authenticating-to-github/error-were-doing-an-ssh-key-audit -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -Cuando uses una clave sin verificar para realizar operaciones Git, se te indicará que debes realizar una auditoría de tus claves SSH. - -```shell -ERROR: We're doing an SSH key audit. -Reason: unverified due to lack of use -Please visit https://github.com/settings/ssh -to approve this key so we know it's safe. -Fingerprint: ab:08:46:83:ff:f6:c4:f8:a9:4e:68:6b:94:17:f2:46 -fatal: could not read from remote repository -``` -### Resolver el problema - -Para resolverlo, necesitas [revisar tus claves SSH](/articles/reviewing-your-ssh-keys) y rechazar o aprobar la clave sin verificar. Al hacer clic en el mensaje de error en el enlace de la URL, irás a la página de Configuración de SSH, donde la clave SSH aparece destacada en la lista de claves SSH. diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/index.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/index.md deleted file mode 100644 index aefc0be671..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Solucionar problemas de SSH -intro: 'Cuando utilizas SSH para conectarte y autenticarte para {% data variables.product.product_name %}, puede que debas solucionar problemas inesperados que surjan.' -redirect_from: - - /articles/troubleshooting-ssh -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH -children: - - /using-ssh-over-the-https-port - - /recovering-your-ssh-key-passphrase - - /deleted-or-missing-ssh-keys - - /error-permission-denied-publickey - - /error-bad-file-number - - /error-key-already-in-use - - /error-permission-to-userrepo-denied-to-other-user - - /error-permission-to-userrepo-denied-to-userother-repo - - /error-agent-admitted-failure-to-sign - - /error-ssh-add-illegal-option----k - - /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok - - /error-unknown-key-type - - /error-were-doing-an-ssh-key-audit ---- - diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md deleted file mode 100644 index e2131ef710..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Recuperar tu contraseña de clave SSH -intro: 'Si perdiste tu contraseña de clave SSH, según el sistema operativo que utilices, puedes recuperarla o generar una nueva contraseña de clave SSH.' -redirect_from: - - /articles/how-do-i-recover-my-passphrase/ - - /articles/how-do-i-recover-my-ssh-key-passphrase/ - - /articles/recovering-your-ssh-key-passphrase - - /github/authenticating-to-github/recovering-your-ssh-key-passphrase -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - SSH ---- -{% mac %} - -Si [configuraste tu contraseña de clave SSH con OS X Keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), quizás puedas recuperarla. - -1. En Finder (Buscador), busca la aplicación **Keychain Access** (Acceso keychain). ![Barra Spotlight Search (Búsqueda de Spotlight)](/assets/images/help/setup/keychain-access.png) -2. En Keychain Access (Acceso keychain), busca **SSH**. -3. Haz doble clic en la entrada de tu clave SSH para abrir un nuevo cuadro de diálogo. -4. En la esquina inferior izquierda, selecciona **Show password** (Mostrar contraseña). ![Diálogo Keychain access (Acceso keychain)](/assets/images/help/setup/keychain_show_password_dialog.png) -5. Se te solicitará tu contraseña administrativa. Escríbela en el cuadro de diálogo "Keychain Access" (Acceso keychain). -6. Se revelará tu contraseña. - -{% endmac %} - -{% windows %} - -Si pierdes tu contraseña de clave SSH, no hay forma de recuperarla. Tendrás que [generar un nuevo par de claves SSH comercial](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) o [cambiar a la clonación de HTTPS](/articles/changing-a-remote-s-url/#switching-remote-urls-from-ssh-to-https) para poder utilizar tu contraseña de GitHub en su lugar. - -{% endwindows %} - -{% linux %} - -Si pierdes tu contraseña de clave SSH, no hay forma de recuperarla. Tendrás que [generar un nuevo par de claves SSH comercial](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) o [cambiar a la clonación de HTTPS](/articles/which-remote-url-should-i-use/#cloning-with-https-urls) para poder utilizar tu contraseña de GitHub en su lugar. - -{% endlinux %} diff --git a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/using-ssh-over-the-https-port.md deleted file mode 100644 index 97a72d386e..0000000000 --- a/translations/es-XL/content/github/authenticating-to-github/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Uso de SSH a través del puerto HTTPS -intro: 'Algunas veces, los firewalls se niegan a permitir conexiones SSH por completo. Si el utilizar el [clonado de HTTPS con almacenamiento de credenciales en el caché](/github/using-git/caching-your-github-credentials-in-git) no es una opción, puedes intentar clonar utilizando una conexión SSH que hayas hecho a través del puerto HTTPS. La mayoría de las reglas del firewall deberían permitir esto, pero los servidores proxy pueden interferir.' -redirect_from: - - /articles/using-ssh-over-the-https-port - - /github/authenticating-to-github/using-ssh-over-the-https-port -versions: - free-pro-team: '*' -topics: - - SSH ---- -{% tip %} - -**Usuarios de GitHub Enterprise**: Actualmente, no se puede acceder a GitHub Enterprise por SSH a través del puerto HTTPS. - -{% endtip %} - -Para probar si es posible el SSH a través del puerto HTTPS, ejecuta este comando SSH: - -```shell -$ ssh -T -p 443 git@ssh.github.com -> Hi username! Has autenticado con éxito, pero GitHub no -> proporciona acceso al shell. -``` - -Si eso funcionó, ¡fantástico! De lo contrario, puede que debas [seguir nuestra guía de solución de problemas](/articles/error-permission-denied-publickey). - -### Habilitar conexiones SSH a través de HTTPS - -Si es posible el SSH en `git@ssh.{% data variables.command_line.backticks %}` a través del puerto 443, puedes 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: - -``` -Host {% data variables.command_line.codeblock %} - Hostname ssh.{% data variables.command_line.codeblock %} - Port 443 -``` - -Puedes probar que esto funcione volviéndote a conectar a {% data variables.product.product_location %}: - -```shell -$ ssh -T git@{% data variables.command_line.codeblock %} -> Hi username! Has autenticado con éxito, pero GitHub no -> proporciona acceso al shell. -``` diff --git a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/about-team-discussions.md b/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/about-team-discussions.md deleted file mode 100644 index d1068f042d..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/about-team-discussions.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Acerca de los debates de equipo -intro: 'Tu equipo puede planificar de manera conjunta, actualizarse unos a otros o hablar sobre cualquier tema que quieran en las publicaciones de debates en la página de tu equipo en una organización.' -redirect_from: - - /articles/about-team-discussions - - /github/building-a-strong-community/about-team-discussions -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.organizations.team-discussions-purpose %} - -Todo miembro de una organización puede publicar en la página de tu equipo o participar de un debate público. {% data reusables.organizations.team-discussions-permissions %} - -![Pestaña Debayes de la página del equipo con debates privados y públicos](/assets/images/help/organizations/team-page-discussions-tab.png) - -Puedes vincularte a cualquier debate de equipo para hacer referencia al mismo en otro lugar. Puedes anclar publicaciones importantes a la página de tu equipo para una referencia rápida a futuro. Para obtener más información, consulta "[Anclar un debate del equipo](/articles/pinning-a-team-discussion)". - -![Pestaña Debates anclados de la página del equipo con debate anclado](/assets/images/help/organizations/team-discussions-pinned.png) - -{% data reusables.organizations.team-discussions-default %} Los propietarios pueden desactivar debates del equipo para toda la organización. Para obtener más información, consulta "[Desactivar los debates del equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)". - -### Notificaciones para los debates del equipo - -Cuando alguien publica o responde a un debate público en la página de un equipo, los miembros del equipo y los miembros de cualquier equipo hijo reciben un correo electrónico o notificaciones web. Cuando alguien publica o responde a un debate privado en la página de un equipo, solo los miembros del equipo reciben notificaciones. - -{% tip %} - -**Sugerencia:** Dependiendo de los parámetros de tu notificación, recibirás actualizaciones por correo electrónico, la página de notificaciones web en {% data variables.product.product_name %}, o ambas. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)[Acerca de las notificaciones por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" y "[Acerca de las notificaciones web](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}". - -{% endtip %} - -Por defecto, si se menciona tu nombre de usuario en un debate del equipo, recibirás notificaciones por la publicación que menciona tu nombre de usuario y toda respuesta a esa publicación. Además, por defecto, si respondes a una publicación, recibirás notificaciones por otras respuestas a la publicación. - -Para apagar las notificaciones para los debates del equipo, puedes cancelar la suscripción a una publicación de debate específica o cambiar tus parámetros de notificación para dejar de ver o ignorar por completo los debtaes de un equipo específico. Te puedes suscribir a las notificaciones para la publicación de un debate específico incluso si dejaste de ver los debates de ese equipo. - -Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Suscribirte y desuscribirte de las notificaciones](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" y "[Equipos anidados](/articles/about-teams/#nested-teams)". - -### Leer más - -- "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)" -- [Acerca de los equipos](/articles/about-teams)" -- "[Crear un debate de equipo](/articles/creating-a-team-discussion)" -- "[Editar o eliminar un debate de equipo](/articles/editing-or-deleting-a-team-discussion)" diff --git a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/creating-a-team-discussion.md b/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/creating-a-team-discussion.md deleted file mode 100644 index 3840d5c4b2..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/creating-a-team-discussion.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Crear un debate del equipo -intro: 'Todo miembro de la organización puede crear una publicación _public_ de un debate del equipo. Para crear una publicación de un debate del equipo _private_, debes ser un miembro del equipo o un propietario de la organización.' -redirect_from: - - /articles/creating-a-team-discussion - - /github/building-a-strong-community/creating-a-team-discussion -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.organizations.team-discussions-permissions %}Para obtener más información, consulta "[Acerca de los debates del equipo](/articles/about-team-discussions)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-discussions-tab %} -6. Escribe un título para el debate del equipo y agrega un comentario para iniciar una conversación. ![Nuevo comentario de los debates del equipo](/assets/images/help/projects/team-discussions-comment.png) -7. También puedes seleccionar si deseas que tu publicación sea privada o pública usando el menú desplegable.![Menú de parámetros de privacidad de los debates del equipo](/assets/images/help/projects/team-discussions-privacy-menu.png) -8. Click **Comment**. ![Botón Crear nuevo comentario de los debates del equipo](/assets/images/help/projects/team-discussions-comment-button.png) - -### Leer más - - - "[Acerca de los debates de equipo](/articles/about-team-discussions)" - - "[Editar o eliminar un debate de equipo](/articles/editing-or-deleting-a-team-discussion)" - - "[Anclar un debate de equipo](/articles/pinning-a-team-discussion)" diff --git a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md deleted file mode 100644 index e4892d6ca5..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Editar o eliminar un debate de equipo -intro: 'Los miembros de la organización pueden editar o eliminar debates en la página del equipo. Si eres un miembro de la organización, puedes editar o eliminar el debate.' -redirect_from: - - /articles/editing-or-deleting-a-team-discussion - - /github/building-a-strong-community/editing-or-deleting-a-team-discussion -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-discussions-tab %} -6. Haz clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} junto al debate de equipo que deseas editar o eliminar. -7. Click **Edit**. También puedes hacer clic en **Eliminar**. ![Botón Editar debate de equipo](/assets/images/help/projects/edit-team-discussions-button.png) -8. Modifica el título y el comentario del debate de equipo según sea necesario, y haz clic en **Actualizar comentario**. ![Botón Actualizar comentario](/assets/images/help/projects/update-comment-button.png) - -### Leer más - - - "[Acerca de los debates de equipo](/articles/about-team-discussions)" - - "[Crear un debate de equipo](/articles/creating-a-team-discussion)" - - "[Anclar un debate de equipo](/articles/pinning-a-team-discussion)" diff --git a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/index.md b/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/index.md deleted file mode 100644 index d0f67785c4..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Colaborar con tu equipo -intro: 'Dentro de una organización, tu equipo puede trabajar en varios proyectos usando los debates de equipo.' -redirect_from: - - /articles/collaborating-with-your-team -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-team-discussions - - /creating-a-team-discussion - - /editing-or-deleting-a-team-discussion - - /pinning-a-team-discussion ---- - diff --git a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/pinning-a-team-discussion.md deleted file mode 100644 index 6bb05c3f8b..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/collaborating-with-your-team/pinning-a-team-discussion.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Anclar un debate del equipo -intro: 'Puedes anclar debates importantes en las páginas del equipo de tu organización para una referencia fácil, y desanclar debates que ya no son relevantes.' -redirect_from: - - /articles/pinning-a-team-discussion - - /github/building-a-strong-community/pinning-a-team-discussion -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-discussions-tab %} -5. Haz clic en {% octicon "pin" aria-label="The pin icon" %} al lado del debate de equipo que deseas anclar. También puedes desanclar un debate al hacer clic en el ícono. ![Anclar un debate](/assets/images/help/projects/pin-discussion-button.png) - -### Leer más - - - "[Acerca de los debates de equipo](/articles/about-team-discussions)" - - "[Crear un debate de equipo](/articles/creating-a-team-discussion)" - - "[Editar o eliminar un debate de equipo](/articles/editing-or-deleting-a-team-discussion)" diff --git a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/about-wikis.md b/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/about-wikis.md deleted file mode 100644 index 765b9ac2d9..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/about-wikis.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Acerca de las wikis -intro: 'Puedes alojar documentación para tu repositorio en una wiki, para que otros puedan usar y colaborar con tu proyecto.' -redirect_from: - - /articles/about-github-wikis/ - - /articles/about-wikis - - /github/building-a-strong-community/about-wikis -product: '{% data reusables.gated-features.wikis %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cada repositorio de {% data variables.product.product_name %} viene equipado con una sección para alojar documentación, llamada una wiki. Puedes usar la wiki de tu repositorio para compartir contenido en forma completa acerca de tu proyecto, como por ejemplo cómo usarlo, cómo lo diseñaste o sus principios básicos. Un archivo README rápidamente dice lo que puede hacer tu proyecto, mientras que puedes usar una wiki para proporcionar documentación adicional. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)". - -Con las wikis, puedes escribir contenido como en cualquier otro lado en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Iniciar con la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)". Usamos [nuestra biblioteca Markup de código abierto](https://github.com/github/markup) para convertir diferentes formatos en HTML, para que puedas elegir escribir en Markdown o en cualquier otro formato admitido. - -Las wikis están disponibles para el público en los repositorios públicos, y limitados a las personas con acceso al repositorio en los repositorios privados. Para obtener más información, consulta "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)". - -Puedes editar las wikis directamente en {% data variables.product.product_name %} o puedes editar los archivos wiki localmente. Por defecto, solo las personas con acceso de escritura a tu repositorio pueden realizar cambios en las wikis, aunque tú le puedes permitir a cualquiera en {% data variables.product.product_name %} que colabore con una wiki en un repositorio público. Para obtener más información, consulta "[Cambiar permisos de acceso para wikis](/articles/changing-access-permissions-for-wikis)". - -### Leer más - -- "[Agregar o eliminar páginas wiki](/articles/adding-or-editing-wiki-pages)" -- "[Crear un pie de página o barra lateral para tu wiki](/articles/creating-a-footer-or-sidebar-for-your-wiki)" -- "[Editar el contenido de una wiki](/articles/editing-wiki-content)" -- "[Ver el historial de cambios de una wiki](/articles/viewing-a-wiki-s-history-of-changes)" -- "[Buscar wikis](/articles/searching-wikis)" diff --git a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md deleted file mode 100644 index fe846e053f..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Agregar o eliminar páginas wiki -intro: 'Puedes agregar y editar páginas wiki directamente en {% data variables.product.product_name %} o localmente usando la línea de comando.' -redirect_from: - - /articles/adding-wiki-pages-via-the-online-interface/ - - /articles/editing-wiki-pages-via-the-online-interface/ - - /articles/adding-and-editing-wik-pages-locally/ - - /articles/adding-and-editing-wiki-pages-locally/ - - /articles/adding-or-editing-wiki-pages - - /github/building-a-strong-community/adding-or-editing-wiki-pages -product: '{% data reusables.gated-features.wikis %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Agregar páginas wiki - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-wiki %} -3. En el ángulo superior derecho de la página, haz clic en **New Page** (Página nueva) ![Botón de la nueva página wiki](/assets/images/help/wiki/wiki_new_page_button.png) -4. Opcionalmente, para escribir en otro formato diferente a Markdown, usa el menú desplegable del modo Edit (Editar) y haz clic en un formato diferente.![Selección de markup de wiki](/assets/images/help/wiki/wiki_dropdown_markup.gif) -5. Usa el editor de texto para agregar el contenido de tu página. ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png) -6. Escribe un mensaje de confirmación que describa el nuevo archivo que agregaste. ![Mensaje de confirmación de la wiki](/assets/images/help/wiki/wiki_commit_message.png) -7. Para confirmar tus cambios en la wiki, haz clic en **Guardar página**. - -### Editar páginas wiki - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-wiki %} -4. Desplázate hasta la página que deseas cambiar con la ayuda de la barra lateral wiki. En el ángulo superior derecho de la página, haz clic en **Edite** (Editar). ![Botón de la página para editar wikis](/assets/images/help/wiki/wiki_edit_page_button.png) -5. Usa el editor de texto para editar el contenido de la página. ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png) -6. Escribe un mensaje de confirmación que describa tus cambios. ![Mensaje de confirmación de la wiki](/assets/images/help/wiki/wiki_commit_message.png) -7. Para confirmar tus cambios en la wiki, haz clic en **Guardar página**. - -### Agregar o editar páginas wiki localmente - -Las wikis son parte de los repositorios Gift, de manera que puedes hacer cambios localmente y subirlos a tu repositorio mediante un flujo de trabajo de Git. - -#### Clonar wikis en tu computadora - -Cada wiki brinda una manera sencilla de clonar sus contenidos en tu computadora. Puedes clonar el repositorio a tu computadora con la URL proporcionada: - -```shell -$ git clone https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.wiki.git -# Clona la wiki localmente -``` - -Una vez que has clonado la wiki, puedes agregar archivos nuevos, editar los existentes y confirmar tus cambios. Tus colaboradores y tú pueden crear ramas cuando trabajen en wikis, pero solo los cambios que se suban a la rama predeterminada estarán productivos y disponibles para tus lectores. - -### Acerca de los nombres de archivo wiki - -El nombre de archivo determina el título de tu página wiki, y la extensión del archivo determina cómo se presenta el contenido wiki. - -Las wikis usan [nuestra biblioteca Markup de código abierto](https://github.com/github/markup) para convertir el Markup, y este determina qué convertidor usar para una extensión de archivo. Por ejemplo, si denominas un archivo *foo.md* o *foo.markdown*, wiki usará el convertidor Markdown, mientras que un archivo denominado *foo.textile* usará el convertidor Textile. - -No uses los siguientes caracteres en los títulos de tu página wiki: `\ / : * ? " < > |`. Los usuarios en determinados sistemas operativos no podrán trabajar con nombres de archivos que contienen estos caracteres. Asegúrate de escribir tu contenido mediante un idioma de Markup que coincida con la extensión, o tu contenido no se presentará de manera adecuada. diff --git a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md b/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md deleted file mode 100644 index 34df79f988..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Cambiar permisos de acceso para wikis -intro: 'Solo los colaboradores de los repositorios pueden editar el wiki del mismo predeterminadamente, pero puedes permitir a cualquiera con una cuenta de {% data variables.product.product_name %} para que lo haga.' -product: '{% data reusables.gated-features.wikis %}' -redirect_from: - - /articles/changing-access-permissions-for-wikis - - /github/building-a-strong-community/changing-access-permissions-for-wikis -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En Features (Características), quita la marca de selección de **Restrict edits to collaborators only** (Restringir ediciones a colaboradores solamente). ![Edición de restricción de wikis](/assets/images/help/wiki/wiki_restrict_editing.png) - -### Leer más - -- "[Inhabilitar wikis](/articles/disabling-wikis)" diff --git a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md b/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md deleted file mode 100644 index a32b3e6ced..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Crear un pie de página o barra lateral para tu wiki -intro: Puedes agregar una barra lateral o un pie de página personalizados a tu wiki para dar a los lectores más información contextual. -redirect_from: - - /articles/creating-a-footer/ - - /articles/creating-a-sidebar/ - - /articles/creating-a-footer-or-sidebar-for-your-wiki - - /github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki -product: '{% data reusables.gated-features.wikis %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Crear una carpeta - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-wiki %} -3. En la parte inferior de la página, haz clic en **Agregar un pie de página**. ![Sección para agregar el pie de página a la wiki](/assets/images/help/wiki/wiki_add_footer.png) -4. Usa el editor de texto para escribir el contenido que deseas que tenga tu pie de página. ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-footer.png) -5. Ingresa un mensaje de confirmación que describa el pie de página que agregaste. ![Mensaje de confirmación de la wiki](/assets/images/help/wiki/wiki_commit_message.png) -6. Para confirmar tus cambios en la wiki, haz clic en **Guardar página**. - -### Crear una barra lateral - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-wiki %} -3. Haz clic en **Agregar una barra lateral personalizada**. ![Sección para agregar la barra lateral a la wiki](/assets/images/help/wiki/wiki_add_sidebar.png) -4. Usa el editor de texto para agregar el contenido de tu página. ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png) -5. Ingresa un mensaje de confirmación que describa la barra lateral que agregaste. ![Mensaje de confirmación de la wiki](/assets/images/help/wiki/wiki_commit_message.png) -6. Para confirmar tus cambios en la wiki, haz clic en **Guardar página**. - -### Crear un pie de página o barra lateral de manera local - -Si creas un archivo con el nombre `_Footer.` or `_Sidebar.`, los usaremos para completar el pie de página y la barra lateral de tu wiki, respectivamente. Al igual que cualquier otra página wiki, la extensión que elijas para estos archivos determina cómo los representaremos. diff --git a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/disabling-wikis.md b/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/disabling-wikis.md deleted file mode 100644 index 6277eac59e..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/disabling-wikis.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Inhabilitar las wikis -intro: Puedes inhabilitar las wikis de tu repositorio. -product: '{% data reusables.gated-features.wikis %}' -redirect_from: - - /articles/disabling-wikis - - /github/building-a-strong-community/disabling-wikis -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cuando desactivas una wiki, su contenido se oculta pero no se borra. Si eliges habilitar nuevamente las wikis en el futuro, se restaurarán tus páginas anteriores. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En Características, quita la marca de selección de **Wiki**. ![Casilla de verificación para inhabilitar wikis](/assets/images/help/wiki/wiki_enable_disable.png) - -### Leer más - -- "[Cambiar los permisos de acceso para las wikis](/articles/changing-access-permissions-for-wikis)" diff --git a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/editing-wiki-content.md deleted file mode 100644 index f1af3bfff6..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/editing-wiki-content.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Editar el contenido de una wiki -intro: Puedes agregar imágenes y enlaces al contenido de tu wiki y usar algunos de los formatos que admite MediaWiki. -redirect_from: - - /articles/adding-links-to-wikis/ - - /articles/how-do-i-add-links-to-my-wiki/ - - /articles/how-do-i-add-or-upload-images-to-the-wiki/ - - /articles/needs-writing-review-how-do-i-add-or-upload-images-to-the-wiki/ - - /articles/how-do-i-add-images-to-my-wiki/ - - /articles/adding-images-to-wikis/ - - /articles/supported-mediawiki-formats/ - - /articles/editing-wiki-content - - /github/building-a-strong-community/editing-wiki-content -product: '{% data reusables.gated-features.wikis %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Agregar enlaces - -Puedes crear enlaces en wikis usando el markup estándar admitido por tu página, o usando la sintaxis MediaWiki. Por ejemplo: - -- Si tus páginas se presentan con Markdown, la sintaxis del enlace es `[Link Text](full-URL-of-wiki-page)`. -- Con la sintaxis MediaWiki, la sintaxis del enlace es `[[Link Text|nameofwikipage]]`. - -### Agregar imágenes - -Las wikis pueden presentar imágenes PNG, JPEG y GIF. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-wiki %} -3. Usando la barra lateral de la wiki, dirígete a la página que deseas cambiar y luego haz clic en **Editar**. -4. En la barra de herramientas de la wiki, haz clic en **Imagen**. ![Botón de la wiki Agregar imagen](/assets/images/help/wiki/wiki_add_image.png) -5. En el cuadro de diálogo "Insertar imagen", escribe la URL de la imagen y el texto alternativo (el que usan los motores de búsqueda y los lectores de pantalla). -6. Haz clic en **OK** (aceptar). - -#### Establecer enlaces a las imágenes en un repositorio - -Puedes establecer un enlace a una imagen en un repositorio en {% data variables.product.product_name %} copiando la URL en tu navegador y usándola como la ruta que lleva a la imagen. Por ejemplo, cuando insertas una imagen en tu wiki usando Markdown, la imagen debe verse de la siguiente manera: - - [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] - -### Formatos MediaWiki admitidos - -Independientemente del lenguaje markup en que esté escrita tu página, siempre tendrás una determinada sintaxis MediaWiki disponible. -- Enlaces ([excdepto AsciiDoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b)) -- Reglas horizontales mediante `---` -- Entidades simbólicas abreviadas (como `δ` o `€`) - -Por razones de seguridad y rendimiento, algunas sintaxis no son compatibles. -- [Transclusión](https://www.mediawiki.org/wiki/Transclusion) -- Listas de definiciones -- Sangría -- Índice diff --git a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/index.md b/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/index.md deleted file mode 100644 index 92ec32f232..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Documentar tu proyecto con wikis -intro: Puedes usar una wiki para compartir información detallada en forma completa acerca de tu proyecto. -redirect_from: - - /categories/49/articles/ - - /categories/wiki/ - - /articles/documenting-your-project-with-wikis -product: '{% data reusables.gated-features.wikis %}' -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-wikis - - /adding-or-editing-wiki-pages - - /creating-a-footer-or-sidebar-for-your-wiki - - /editing-wiki-content - - /viewing-a-wikis-history-of-changes - - /changing-access-permissions-for-wikis - - /disabling-wikis ---- - diff --git a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes.md b/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes.md deleted file mode 100644 index 028a626993..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Ver el historial de cambios de una wiki -intro: 'Debido a que las wikis son repositorios de Git, cada cambio que realices es una confirmación que puedes ver.' -product: '{% data reusables.gated-features.wikis %}' -redirect_from: - - /articles/viewing-a-wiki-s-history-of-changes - - /articles/viewing-a-wikis-history-of-changes - - /github/building-a-strong-community/viewing-a-wikis-history-of-changes -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Ver el historial de una wiki - -El historial de una wiki incluye: -- El usuario que realizó el cambio -- El mensaje de confirmación que proporcionó -- Cuándo se realizó el cambio - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-wiki %} -3. Utilizando la barra lateral de wiki, desplázate hasta la página cuyo historial deseas ver. -4. En la parte superior de la wiki, haz clic en el vínculo de revisión. ![Vínculo de revisión de wiki](/assets/images/help/wiki/wiki_revision_link.png) - -### Ver el contenido previo - -En la tabla del historial de wiki, puedes hacer clic en el [hash SHA-1](http://en.wikipedia.org/wiki/SHA-1) (la secuencia de letras y números al extremo derecho) para ver una página de wiki tal como existía en un punto determinado en el tiempo. - -![Número SHA de wiki](/assets/images/help/wiki/wiki_sha_number.png) - -### Comparar dos revisiones - -1. Selecciona dos filas que deseas comparar. -2. En la parte superior de la tabla del historial, haz clic en **Compare Revisions (Comparar revisiones)**. ![Botón de revisiones de comparación de wiki](/assets/images/help/wiki/wiki_compare_revisions.png) -3. Verás una diferencia de los cambios que muestra qué líneas se agregaron, se eliminaron y se modificaron. - -### Revertir los cambios previos - -Puedes únicamente revertir cambios si tienes permiso para editar la wiki. - -1. Selecciona una fila que deseas revertir. -2. En la parte superior de la tabla del historial, haz clic en **Compare Revisions (Comparar revisiones)**. ![Botón de revisiones de comparación de wiki](/assets/images/help/wiki/wiki_compare_revisions.png) -3. Verás una diferencia de los cambios que muestra qué líneas se agregaron, se eliminaron y se modificaron. ![Diferencia de revisión de wiki](/assets/images/help/wiki/wiki_revision_diff.png) -4. Para revertir los cambios más recientes, haz clic en **Revert Changes (Revertir cambios)**. ![Botón para revertir cambios de wiki](/assets/images/help/wiki/wiki_revert_changes.png) diff --git a/translations/es-XL/content/github/building-a-strong-community/index.md b/translations/es-XL/content/github/building-a-strong-community/index.md deleted file mode 100644 index 73e8b2aa9e..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Construir una comunidad sólida -intro: 'Más allá de que tu proyecto sea de código abierto o privado, puedes generar un entorno saludable y eficaz para la colaboración.' -redirect_from: - - /categories/building-a-strong-community -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /setting-up-your-project-for-healthy-contributions - - /using-templates-to-encourage-useful-issues-and-pull-requests - - /moderating-comments-and-conversations - - /maintaining-your-safety-on-github - - /documenting-your-project-with-wikis - - /collaborating-with-your-team ---- -### Índice - - - - - - - - - - diff --git a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md deleted file mode 100644 index fecae80366..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Bloquear a un usuario de tu organización -intro: Los propietarios de una organización pueden bloquear a un usuario para eliminar la capacidad del usuario para colaborar en los repositorios de la organización. -redirect_from: - - /articles/blocking-a-user-from-your-organization - - /github/building-a-strong-community/blocking-a-user-from-your-organization -versions: - free-pro-team: '*' ---- -Puedes bloquear a un usuario desde los parámetros de la organización o desde un comentario específico realizado por el usuario. Al bloquear a un usuario en un comentario, puedes elegir si deseas enviar una notificación al usuario explicando que fue bloqueado y por qué. De lo contrario, el usuario no será notificado directamente que ha sido bloqueado. Los usuarios bloqueados aún podrán borrar el contenido existente. - -Cuando bloqueas a un usuario, puedes elegir bloquearlo indefinidamente o durante un período determinado. Si bloqueas a alguien durante un tiempo determinado, estará desbloqueado automáticamente cuando caduque ese período. Si bloqueas a alguien indefinidamente, puedes desbloquearlo manualmente en cualquier momento. Para obtener más información, consulta "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)". - -{% tip %} - -**Sugerencia:** Si estás bloqueando a un usuario por una conversación encendida, considera [bloquear la conversación](/articles/locking-conversations) de manera que solo los colaboradores puedan comentar. - -{% endtip %} - -Al momento en que bloqueas a un usuario de tu organización: -- El usuario deja de ver los repositorios de la organización -- Las asignaciones con estrella y las propuestas del usuario se eliminarán de tus repositorios -- Se borrarán las bifurcaciones del usuario para los repositorios de tu organización -- Se borrarán los votos del usuario sobre los comentarios y debates en los repositorios de tu organización -- El usuario será eliminado como colaborador en los repositorios de tu organización -- Las contribuciones del usuario ya no contarán como tales para ellos en los repositorios de tu organización -- Cualquier repositorio o invitación de la organización pendientes para el usuario bloqueado se cancelará - -Una vez que has bloqueado a un usuario de tu organización, no podrá: -- Realizar referencias cruzadas con repositorios de la organización en comentarios -- Bifurca, observa, fija, o marca con una estrella los repositorios de tu organización - -En los repositorios de tu organización, los usuarios bloqueados tampoco podrán: -- Abrir propuestas -- Envía, cierra, o fusiona las solicitudes de extracción -- Comentar sobre las propuestas, solicitudes de extracción o confirmaciones -- Agregar o editar páginas wiki - -### Bloquear a un usuario en un comentario - -1. Desplázate hasta el comentario cuyo autor deseas bloquear. -2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} (el ícono de kebab horizontal) , después haz clic en **Block user** (Bloquear usuario). ![El ícono de kebab horizontal y el menú de moderación de comentario que muestra las opciones de bloqueo del usuario](/assets/images/help/repository/comment-menu-block-user.png) -3. Si deseas establecer un límite de tiempo para el bloqueo, usa el menú desplegable Block user (Bloquear usuario), y selecciona el período que deseas bloquear al usuario. ![Bloquear límite de tiempo en el menú desplegable para bloquear al usuario](/assets/images/help/organizations/org-block-options-menu-from-comment.png) -4. Si deseas ocultar todos los comentarios que realizó el usuario en la organización, selecciona **Hide this user's comments** (Ocultar los comentarios del usuario) y elige un motivo. ![Enviar una notificación en el menú desplegable para bloquear al usuario](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png) -5. Si te gustaría notificar al usuario sobre el motivo por el que fue bloqueado, selecciona **Send a notification to this user** (Enviar una notificación a este usuario). ![Enviar una notificación en el menú desplegable para bloquear al usuario](/assets/images/help/organizations/org-block-options-menu-send-notification.png) -6. Para bloquear al usuario, haz clic en **Block user from organization** (Bloquear usuario de la organización) o **Block user from organization and send message** (Bloquear usuario de la organización y enviar mensaje). ![Botón Block user (Bloquear usuario)](/assets/images/help/organizations/org-block-user-button-in-comment.png) - -### Bloquear a un usuario en los parámetros de la organización - -1. Para bloquear a un miembro de la organización, primero [elimina al usuario](/articles/removing-a-member-from-your-organization) desde la organización. -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.block_users %} -6. En "Block a user" (Bloquear a un usuario), escribe el nombre de usuario del usuario que deseas bloquear. ![Campo Username (Nombre de usuario)](/assets/images/help/organizations/org-block-username-field.png) -7. Si deseas establecer un límite de tiempo para el bloqueo, usa el menú desplegable Block options (Bloquear opciones), y selecciona el período que deseas bloquear al usuario. ![Menú desplegable con las opciones de bloqueo](/assets/images/help/organizations/org-block-options-menu.png) -8. Haz clic en **Block user** (Bloquear usuario). ![Botón Block (Bloquear)](/assets/images/help/organizations/org-block-user-button.png) - -### Leer más - -- "[Ver usuarios que están bloqueados en tu organización](/articles/viewing-users-who-are-blocked-from-your-organization)" -- "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" -- "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" -- "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" -- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" diff --git a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md deleted file mode 100644 index d1410567cb..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Bloquear a un usuario de tu cuenta personal -intro: Puedes bloquear a un usuario para impedirle el acceso a tu actividad y repositorios y para evitar que te envíe notificaciones. -redirect_from: - - /articles/blocking-a-user-from-your-personal-account - - /github/building-a-strong-community/blocking-a-user-from-your-personal-account -versions: - free-pro-team: '*' ---- -### Acerca de bloquear usuarios - -Puedes bloquear a un usuario en los parámetros de tu cuenta o desde el perfil del usuario. {% data variables.product.prodname_dotcom %} no notificará al usuario cuando lo bloquees. Si no deseas contribuir en el mismo proyecto que alguien que has bloqueado, puedes [exhibir una advertencia](/articles/blocking-a-user-from-your-personal-account/#blocking-a-user-in-your-account-settings) en cualquier repositorio con contribuciones previas de un usuario bloqueado. Puede que aún veas la actividad de los usuarios bloqueados en los espacios compartidos y los usuarios bloqueados pueden borrar su contenido existente. - -{% tip %} - -**Sugerencia:** Si estás bloqueando a un usuario por una conversación encendida, considera [bloquear la conversación](/articles/locking-conversations) de manera que solo los colaboradores puedan comentar. - -{% endtip %} - -Cuando bloqueas a un usuario: -- El usuario deja de seguirte -- El usuario deja de observar y deja de fijar tus repositorios -- Las asignaciones con estrella y las propuestas del usuario se eliminarán de tus repositorios -- Se borran las bifurcaciones del usuario para tus repositorios -- Borras cualquier bifuracación de los repositorios del usuario -- Se borran los votos del usuario en los comentarios o debates de tus repositorios -- El usuario será eliminado como colaborador en los repositorios de tu organización -- Las contribuciones del usuario ya no contarán como tales para ellos en tus repositorios -- Tus contribuciones para los repositorios del usuario bloqueado ya no contarán como tales para ti -- Se te elimina como colaborador en sus repositorios -- Ya no contarás con su patrocinio -- Cualquier invitación de sucesor de una cuenta o repositorio que se haga a o que provenga del usuario bloqueado se cancela - -Después de que hayas bloqueado a un usuario, no podrá: -- Enviarte notificaciones, incluso al [@mencionar](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) tu nombre de usuario -- Los comentarios o ediciones a los informes de problemas o solicitudes de extracción que has creado -- Reaccionar a tus comentarios en reportes de problemas, solicitudes de extracción y confirmaciones -- Seguir o ver tu contenido en el feed de sus actividades -- Se te asigna a los informes de problemas o solicitudes de extracción -- Invitarte para que seas colaborador en sus repositorios -- Invitarte como colaborador en una asesoría de seguridad -- Realizar referencias cruzadas con tus repositorios en comentarios -- Bifurcar, observar, fijar o marcar con estrella a tus repositorios -- Patrocinarte - -En los repositorios que te pertenecen, los usuarios bloqueados tampoco podrán: -- Abrir propuestas -- Envía, cierra, o fusiona las solicitudes de extracción -- Comentar sobre las propuestas, solicitudes de extracción o confirmaciones -- Agregar o editar páginas wiki - -### Bloquear a un usuario en tus parámetros de cuenta - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.blocked_users %} -3. En "Block a user" (Bloquear a un usuario), escribe el nombre de usuario del usuario que deseas bloquear, luego haz clic en **Block user** (Bloquear usuario). ![Campo Username (Nombre de usuario) y botón Block (Bloquear)](/assets/images/help/settings/user-settings-block-user.png) -4. Opcionalmente, para mostrar una advertencia al visitar un repositorio donde un usuario bloqueado es un colaborador, selecciona **Warn me when blocked user is a prior contributor to a repository** (Advertirme cuando un usuario bloqueado es un colaborador anterior del repositorio). ![Opción para advertir sobre usuarios bloqueados](/assets/images/help/settings/warn-block-user.png) - -### Bloquear a un usuario desde su página de perfil - -{% data reusables.profile.user_profile_page_navigation %} -{% data reusables.profile.user_profile_page_block_or_report %} -3. Haz clic en **Block user** (Bloquear usuario). ![Cuadro de modo con opciones para bloquear a un usuario o reportar abusos](/assets/images/help/profile/profile-blockuser.png) - -{% note %} - -Utiliza {% data variables.contact.report_abuse %} para contactarnos si te están acosando. {% data reusables.policies.abuse %} - -{% endnote %} - -### Leer más - -- "[Ver usuarios que has bloqueado de tu cuenta personal](/articles/viewing-users-you-ve-blocked-from-your-personal-account)" -- "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" -- "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" -- "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" -- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" -- "[Limitar las interacciones con tu repositorio](/articles/limiting-interactions-with-your-repository)" diff --git a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/index.md b/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/index.md deleted file mode 100644 index b701b96a79..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Mantener tu seguridad en GitHub -intro: 'Para construir un ambiente seguro y positivo para ti y para la comunidad de tu proyecto en {% data variables.product.prodname_dotcom %}, puedes bloquear y desbloquear a los usuarios y reportar el contenido ofensivo.' -redirect_from: - - /articles/encouraging-positive-contributions-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/encouraging-positive-contributions-in-your-organization - - /github/building-a-strong-community/encouraging-positive-contributions-to-your-project - - /articles/encouraging-positive-contributions-to-your-project -versions: - free-pro-team: '*' -children: - - /blocking-a-user-from-your-personal-account - - /viewing-users-youve-blocked-from-your-personal-account - - /unblocking-a-user-from-your-personal-account - - /blocking-a-user-from-your-organization - - /viewing-users-who-are-blocked-from-your-organization - - /unblocking-a-user-from-your-organization - - /reporting-abuse-or-spam ---- - diff --git a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/reporting-abuse-or-spam.md deleted file mode 100644 index 71b8410b96..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/reporting-abuse-or-spam.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Informar abuso o spam -intro: Puedes reportar el contenido y comportamientos que violen los lineamientos y condiciones de la comunidad. -redirect_from: - - /articles/reporting-abuse-or-spam - - /github/building-a-strong-community/reporting-abuse-or-spam -versions: - free-pro-team: '*' ---- -Los propietarios, colaboradores actuales y previos, y personas con acceso de escritura pueden reportar los comentarios que se hagan en los informes de problemas, solicitudes de extracción y confirmaciones. Cualquier persona puede informar apps en {% data variables.product.prodname_marketplace %}. - -### Acerca de reportar abusos y spam - -{% data reusables.policies.github-community-guidelines-and-terms %} - -Puedes reportar a los usuarios que hayan violado las condiciones de servicio o los lineamientos comunitarios de {% data variables.product.prodname_dotcom %} a través de {% data variables.contact.report_abuse %} o {% data variables.contact.report_content %}. También puedes reportar los comentarios en informes de problemas, solicitudes de extracción y confirmaciones. - -Si se ha habilitado la capacidad para reportar contenido en un repositorio público, también puedes reportarlo directamente a los mantenedores del mismo. - -### Informar un usuario - -{% data reusables.profile.user_profile_page_navigation %} -{% data reusables.profile.user_profile_page_block_or_report %} -3. Haz clic en **Report abuse** (Informar abuso). ![Cuadro de modo con opciones para bloquear a un usuario o reportar abusos](/assets/images/help/profile/profile-report-abuse.png) -4. Completa el formulario de contacto para informarle a {% data variables.contact.contact_support %} sobre el comportamiento del usuario, luego haz clic en **Send request** (Enviar solicitud). - -### Informar una propuesta o solicitud de extracción - -1. Navega hasta la propuesta o solicitud de extracción que quieras informar. -2. In the upper-right corner of the issue or pull request, click -{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}, then click **Report content**. - ![Botón para informar un comentario](/assets/images/help/repository/menu-report-issue-or-pr.png) -{% data reusables.community.report-content %} - -### Informar un comentario - -1. Navega hasta el comentario que quieras informar. -2. In the upper-right corner of the comment, click -{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}, then click **Report content**. -![Menú Kebab con opción para informar un comentario](/assets/images/help/repository/menu-report-comment.png) -{% data reusables.community.report-content %} - -### Informar una app en {% data variables.product.prodname_marketplace %} - -{% data reusables.marketplace.visit-marketplace %} -2. Navega hasta la app que quieras informar. -3. En la barra lateral izquierda, en la sección "Developer links" (Enlaces del programador), haz clic en {% octicon "report" aria-label="The report symbol" %} **Report abuse** (Informar abuso). ![Botón para informar una app en {% data variables.product.prodname_marketplace %}](/assets/images/help/marketplace/marketplace-report-app.png) -4. Completa el formulario de contacto para informarle a {% data variables.contact.contact_support %} sobre el comportamiento de la app, luego haz clic en **Send request** (Enviar solicitud). - -### Reportar abusos en enlaces de contacto dentro del selector de plantillas - -1. Navega al repositorio que contiene el enlace de contacto que deseas reportar. -2. Debajo del nombre del repositorio, da clic en {% octicon "issue-opened" aria-label="The issues icon" %} **Problemas**. -3. En la esquina inferior derecha del selector de plantillas, haz clic en **Report Abuse (Reportar abuso)**. ![Enlace para denunciar un abuso](/assets/images/help/repository/template-chooser-report-abuse.png) -4. Completa el formato de contacto para informar a {% data variables.contact.contact_support %} acerca del comportamiento del enlace, posteriormente, da clic en **Enviar solicitud**. - -### Leer más - -- "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" -- "[Utilizar plantillas para fomentar el informe de problemas útil y las solicitudes de extracción](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" -- [Administrar los comentarios ofensivos](/articles/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %} -- [Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" -- [Limitar las interacciones en tu repositorio](/github/building-a-strong-community/limiting-interactions-in-your-repository)"{% endif %} -- "[Rastrear cambios en un comentario](/articles/tracking-changes-in-a-comment)" diff --git a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md deleted file mode 100644 index 6de5c55eff..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Desbloquear un usuario desde tu organización -intro: Los propietarios de la organización pueden desbloquear un usuario que se haya bloqueado previamente y restaurar su acceso a los repositorios de la organización. -redirect_from: - - /articles/unblocking-a-user-from-your-organization - - /github/building-a-strong-community/unblocking-a-user-from-your-organization -versions: - free-pro-team: '*' ---- -Después de desbloquear un usuario desde tu organización, este podrá contribuir con los repositorios de tu organización. - -Si seleccionaste una cantidad de tiempo específica para bloquear al usuario, se desbloqueará de forma automática cuando termine ese período de tiempo. Para obtener más información, consulta "[Bloquear un usuario de tu organización](/articles/blocking-a-user-from-your-organization)". - -{% tip %} - -**Sugerencia**: Las configuraciones que se hayan eliminado cuando bloqueaste al usuario de tu organización, como el estado de colaborador, las estrellas y las observaciones, no se restaurarán cuando desbloquees al usuario. - -{% endtip %} - -### Desbloquear un usuario en un comentario - -1. Navega hasta el comentario cuyo autor quieres desbloquear. -2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, luego haz clic en **Unblock user** (Desbloquear usuario). ![Ícono kebab horizontal y menú de moderación de comentarios que muestra la opción de desbloquear usuario](/assets/images/help/repository/comment-menu-unblock-user.png) -3. Para confirmar que quieres desbloquear al usuario, haz clic en **Okay**. - -### Desbloquear un usuario en los parámetros de la organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.block_users %} -5. En "Blocked users" (Usuarios bloqueados), al lado del usuario que quieres desbloquear, haz clic en **Unblock** (Desbloquear). ![Botón Unblock user (Desbloquear usuario)](/assets/images/help/organizations/org-unblock-user-button.png) - -### Leer más - -- "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" -- "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" -- "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" -- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" diff --git a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md b/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md deleted file mode 100644 index 8f83e1856d..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Desbloquear un usuario desde tu cuenta personal -intro: 'Si mejoraste la relación con un {% data variables.product.prodname_dotcom %} usuario que habías bloqueado, puedes desbloquear su cuenta.' -redirect_from: - - /articles/unblocking-a-user-from-your-personal-account - - /github/building-a-strong-community/unblocking-a-user-from-your-personal-account -versions: - free-pro-team: '*' ---- -Cuando desbloqueas un usuario, podrá invitarte a ser colaborador de sus repositorios. Si te [@mention menciona](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) en cualquier parte de GitHub, recibirás notificaciones. - -En los repositorios que te pertenecen, el usuario podrá colaborar con normalidad. - -Puedes desbloquear un usuario en los parámetros de tu cuenta o desde la página de perfil del usuario. - -### Desbloquear a un usuario en tus parámetros de cuenta - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.blocked_users %} -3. En "Blocked users" (Usuarios bloqueados), al lado del usuario que quieres desbloquear, haz clic en **Unblock** (Desbloquear). ![Botón Unblock user (Desbloquear usuario)](/assets/images/help/organizations/org-unblock-user-button.png) - -### Desbloquear un usuario desde su página de perfil - -{% data reusables.profile.user_profile_page_navigation %} -2. En la barra lateral izquierda, debajo de la foto de perfil del usuario, haz clic en **Unblock or report user** (Desbloquear o informar usuario). ![Enlace Unblock or report user (Desbloquear o informar usuario)](/assets/images/help/profile/profile-unblock-or-report-user.png) -3. Haz clic en **Unblock user** (Desbloquear usuario). ![Casilla modal con la opción para desbloquear un usuario o informar abuso](/assets/images/help/profile/profile-unblockuser.png) - -{% tip %} - -**Sugerencia**: Las configuraciones que se hayan eliminado cuando bloqueaste al usuario, como el estado de colaborador, las estrellas y las cosas que sigue, no se restaurarán cuando desbloquees al usuario. - -{% endtip %} - -### Leer más - -- "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" -- "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" -- "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" -- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" diff --git a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md deleted file mode 100644 index 426f656413..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Ver usuarios que están bloqueados de tu organización -intro: 'Puedes ver una lista de todos los usuarios a quienes tú u otras personas han bloqueado de tu organización. Si un usuario fue bloqueado durante una cantidad de tiempo específica, puedes ver la cantidad de tiempo durante la cual fue bloqueado.' -redirect_from: - - /articles/viewing-users-who-are-blocked-from-your-organization - - /github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization -versions: - free-pro-team: '*' ---- -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.block_users %} -5. Dentro de "Blocked users" (Usuarios bloqueados), revisa la lista de usuarios que fueron bloqueados de tu organización. ![Lista de usuarios bloqueados](/assets/images/help/settings/list-of-blocked-users-for-org.png) - -### Leer más - -- "[Bloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" -- "[Desbloquear a un usuario de tu organización](/articles/unblocking-a-user-from-your-organization)" -- "[Ver usuarios que has bloqueado de tu cuenta personal](/articles/viewing-users-you-ve-blocked-from-your-personal-account)" diff --git a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account.md b/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account.md deleted file mode 100644 index dbae791c69..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Ver usuarios que has bloqueado de tu cuenta personal -intro: Puedes ver una lista de todos los usuarios que has bloqueado de tu cuenta personal. -redirect_from: - - /articles/viewing-users-you-ve-blocked-from-your-personal-account - - /articles/viewing-users-youve-blocked-from-your-personal-account - - /github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account -versions: - free-pro-team: '*' ---- -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.blocked_users %} -3. Dentro de "Blocked users" (Usuarios bloqueados), revisa la lista de usuarios que has bloqueado de tu cuenta. ![Lista de usuarios bloqueados](/assets/images/help/settings/list-of-blocked-users.png) - -### Leer más - -- "[Bloquear a un usuario desde tu cuenta personal](/articles/blocking-a-user-from-your-personal-account)" -- "[Desbloquear a un usuario desde tu cuenta personal](/articles/unblocking-a-user-from-your-personal-account)" -- "[Ver usuarios que están bloqueados en tu organización](/articles/viewing-users-who-are-blocked-from-your-organization)" diff --git a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/index.md b/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/index.md deleted file mode 100644 index e32e437d11..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Moderar comentarios y conversaciones -intro: 'Moderar las conversaciones crea una comunidad amigable para todos los colaboradores de tu proyecto al promover la colaboración saludable y disminuir la intensidad del conflicto. Puedes aplicar el código de conducta de tu comunidad a las discusiones viendo el contenido reportado, editando y eliminando comentarios, y fijando conversaciónes.' -redirect_from: - - /articles/moderating-comments-and-conversations -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /managing-disruptive-comments - - /locking-conversations - - /limiting-interactions-in-your-repository - - /limiting-interactions-in-your-organization - - /tracking-changes-in-a-comment - - /managing-how-contributors-report-abuse-in-your-organizations-repository - - /managing-reported-content-in-your-organizations-repository ---- - diff --git a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md deleted file mode 100644 index d84645ac4e..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Limitar las interacciones en tu organización -intro: 'Los propietarios de la organización pueden restringir de manera temporaria que determinados usuarios comenten, abran propuestas o creen solicitudes de extracción en los repositorios públicos de la organización para hacer cumplir un período de actividad limitada.' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/limiting-interactions-in-your-organization - - /articles/limiting-interactions-in-your-organization - - /github/building-a-strong-community/limiting-interactions-in-your-organization -versions: - free-pro-team: '*' ---- -Después de 24 horas, los usuarios pueden reanudar la actividad normal en los repositorios públicos de tu organización. Cuando habilitas limitaciones de actividad en toda la organización, no puedes habilitar o inhabilitar límites de interacción en los repositorios individuales. Para obtener más información sobre la limitación de actividad por repositorio, consulta "[Limitar las interacciones de tu repositorio](/articles/limiting-interactions-in-your-repository)". - -{% tip %} - -**Sugerencia:** Los propietarios de la organización también pueden bloquear usuarios durante una cantidad de tiempo específica. Después de que expira el bloqueo, el usuario se desbloquea de manera automática. Para obtener más información, consulta "[Bloquear un usuario de tu organización](/articles/blocking-a-user-from-your-organization)". - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -4. En la barra lateral Settings (Parámetros) de tu organización, haz clic en **Límites de interacción**. ![Límites de interacción en los parámetros de la organización ](/assets/images/help/organizations/org-settings-interaction-limits.png) -5. Da clic en una o más opciones debajo de "límites de interacción temporales". ![Opciones de límites de interacción temporal](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png) - - **Límites para usuarios existentes**: Limita la actividad de usuarios de la organización con cuentas que tienen menos de 24 horas y que no han realizado contribuciones anteriores ni no son colaboradores. - - **Límite para contribuyentes previos**: Limita la actividad de usuarios de la organización que no hayan contribuido anteriormente y que no sean colaboradores. - - "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)" - -### Leer más -- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" -- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" -- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)" -- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md deleted file mode 100644 index e56027679f..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Limitar las interacciones en tu repositorio -intro: 'Las personas con acceso de propietario o administrador pueden restringir de manera temporal que determinados usuarios comenten, abran propuestas o creen solicitudes de extracción en tu repositorio público para aplicar un período de actividad limitada.' -redirect_from: - - /articles/limiting-interactions-with-your-repository/ - - /articles/limiting-interactions-in-your-repository - - /github/building-a-strong-community/limiting-interactions-in-your-repository -versions: - free-pro-team: '*' ---- -Después de 24 horas, los usuarios pueden reanudar la actividad normal en tu repositorio. - -{% tip %} - -**Sugerencia:** Los propietarios de la organización pueden habilitar limitaciones de actividad en toda la organización. Si están habilitadas las limitaciones de actividad en toda la organización, no puedes limitar la actividad de los repositorios individuales. Para obtener más información, consulta "[Limitar las interacciones en tu organización](/articles/limiting-interactions-in-your-organization)". - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En la barra lateral de tus Parámetros del repositorio, haz clic en **Interaction limits** (Límites de interacción). ![Límites de interacción en los parámetros del repositorio ](/assets/images/help/repository/repo-settings-interaction-limits.png) -4. Da clic en una o más opciones debajo de "límites de interacción temporales": ![Opciones de límites de interacción temporal](/assets/images/help/repository/temporary-interaction-limits-options.png) - - **Limit to existing users** (Límites para usuarios existentes): Limita la actividad de usuarios con cuentas que tienen menos de 24 horas y que no han realizado contribuciones anteriores ni son colaboradores. - - **Limit to prior contributors** (Límite para contribuyentes anteriores): Limita la actividad de usuarios que no hayan contribuido anteriormente ni son colaboradores. - - "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)" - -### Leer más -- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" -- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" -- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)" -- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/locking-conversations.md b/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/locking-conversations.md deleted file mode 100644 index ec9b8ef6c3..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/locking-conversations.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Locking conversations -intro: 'Repository owners and collaborators, and people with write access to a repository, can lock conversations on issues, pull requests, and commits permanently or temporarily to defuse a heated interaction.' -redirect_from: - - /articles/locking-conversations - - /github/building-a-strong-community/locking-conversations -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. When you lock a conversation, you can also specify a reason, which is publicly visible. - -Locking a conversation creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who locked the conversation is only visible to people with write access to the repository. For anyone without write access, the timeline event is anonymized. - -![Anonymized timeline event for a locked conversation](/assets/images/help/issues/anonymized-timeline-entry-for-locked-conversation.png) - -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-on-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)." - -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) -3. Optionally, choose a reason for locking the conversation. -![Reason for locking a conversation menu](/assets/images/help/repository/locking-conversation-reason-menu.png) -4. Read the information about locking conversations and click **Lock conversation on this issue**, **Lock conversation on this pull request**, or **Lock conversation on this commit**. -![Confirm lock with a reason dialog box](/assets/images/help/repository/lock-conversation-confirm-with-reason.png) -5. When you're ready to unlock the conversation, click **Unlock conversation**. -![Unlock conversation link](/assets/images/help/repository/unlock-conversation.png) - -### Further reading - -- "[Setting up your project for healthy contributions](/articles/setting-up-your-project-for-healthy-contributions)" -- "[Using templates to encourage useful issues and pull requests](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" -- "[Managing disruptive comments](/articles/managing-disruptive-comments)"{% if currentVersion == "free-pro-team@latest" %} -- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/github/building-a-strong-community/maintaining-your-safety-on-github)" -- "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)" -- "[Limiting interactions in your repository](/github/building-a-strong-community/limiting-interactions-in-your-repository)" -{% endif %} diff --git a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-disruptive-comments.md deleted file mode 100644 index d76306c4cb..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-disruptive-comments.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: Managing disruptive comments -intro: 'You can {% if currentVersion == "free-pro-team@latest" %}hide, edit,{% else %}edit{% endif %} or delete comments on issues, pull requests, and commits.' -redirect_from: - - /articles/editing-a-comment/ - - /articles/deleting-a-comment/ - - /articles/managing-disruptive-comments - - /github/building-a-strong-community/managing-disruptive-comments -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Hiding a comment - -Anyone with write access to a repository can hide comments on issues, pull requests, and commits. - -If a comment is off-topic, outdated, or resolved, you may want to hide a comment to keep a discussion focused or make a pull request easier to navigate and review. Hidden comments are minimized but people with read access to the repository can expand them. - -![Minimized comment](/assets/images/help/repository/hidden-comment.png) - -1. Navigate to the comment you'd like to hide. -2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Hide**. - ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete options](/assets/images/help/repository/comment-menu.png) -3. Using the "Choose a reason" drop-down menu, click a reason to hide the comment. Then click, **Hide comment**. - {% if currentVersion == "free-pro-team@latest" %} - ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment.png) - {% else %} - ![Choose reason for hiding comment drop-down menu](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png) - {% endif %} - -### Unhiding a comment - -Anyone with write access to a repository can unhide comments on issues, pull requests, and commits. - -1. Navigate to the comment you'd like to unhide. -2. In the upper-right corner of the comment, click **{% octicon "fold" aria-label="The fold icon" %} Show comment**. - ![Show comment text](/assets/images/help/repository/hidden-comment-show.png) -3. On the right side of the expanded comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Unhide**. - ![The horizontal kebab icon and comment moderation menu showing the edit, unhide, delete options](/assets/images/help/repository/comment-menu-hidden.png) - -### Editing a comment - -Anyone with write access to a repository can edit comments on issues, pull requests, and commits. - -It's appropriate to edit a comment and remove content that doesn't contribute to the conversation and violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. - -When you edit a comment, note the location that the content was removed from and optionally, the reason for removing it. - -Anyone with read access to a repository can view a comment's edit history. The **edited** dropdown at the top of the comment contains a history of edits showing the user and timestamp for each edit. - -![Comment with added note that content was redacted](/assets/images/help/repository/content-redacted-comment.png) - -Comment authors and anyone with write access to a repository can also delete sensitive information from a comment's edit history. For more information, see "[Tracking changes in a comment](/github/building-a-strong-community/tracking-changes-in-a-comment)." - -1. Navigate to the comment you'd like to edit. -2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. - ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png) -3. In the comment window, delete the content you'd like to remove, then type `[REDACTED]` to replace it. - ![Comment window with redacted content](/assets/images/help/issues/redacted-content-comment.png) -4. At the bottom of the comment, type a note indicating that you have edited the comment, and optionally, why you edited the comment. - ![Comment window with added note that content was redacted](/assets/images/help/issues/note-content-redacted-comment.png) -5. Click **Update comment**. - -### Deleting a comment - -Anyone with write access to a repository can delete comments on issues, pull requests, and commits. Organization owners, team maintainers, and the comment author can also delete a comment on a team page. - -Deleting a comment is your last resort as a moderator. It's appropriate to delete a comment if the entire comment adds no constructive content to a conversation and violates your community's code of conduct{% if currentVersion == "free-pro-team@latest" %} or GitHub's [Community Guidelines](/articles/github-community-guidelines){% endif %}. - -Deleting a comment creates a timeline event that is visible to anyone with read access to the repository. However, the username of the person who deleted the comment is only visible to people with write access to the repository. For anyone without write access, the timeline event is anonymized. - -![Anonymized timeline event for a deleted comment](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png) - -If a comment contains some constructive content that adds to the conversation in the issue or pull request, you can edit the comment instead. - -{% note %} - -**Note:** The initial comment (or body) of an issue or pull request can't be deleted. Instead, you can edit issue and pull request bodies to remove unwanted content. - -{% endnote %} - -1. Navigate to the comment you'd like to delete. -2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. - ![The horizontal kebab icon and comment moderation menu showing the edit, hide, delete, and report options](/assets/images/help/repository/comment-menu.png) -3. Optionally, write a comment noting that you deleted a comment and why. diff --git a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository.md b/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository.md deleted file mode 100644 index 9f2460783b..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Administrar la forma en que los colaboradores reportan abusos en el repositorio de tu organización -intro: Puedes permitir que los colaboradores reporten el comportamiento ofensivo directamente a los mantenedores de los repositorios. -versions: - free-pro-team: '*' -redirect_from: - - /github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository ---- -Cualquiera con permisos de administrador en el repositorio puede administrar la forma en la que los colaboradores reportan los abusos en el mismo. - -Puedes habilitar o inhabilitar el contenido para los repositorios públicos que pertenezca a una organización. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.sidebar-moderation-reported-content %} -4. Selecciona o desselecciona **Aceptar reportes de contenido de los colaboradores recientes y anteriores** debajo de "Contenido reportado". ![Casilla para optar por ingresar o salir del contenido reportado en un repositorio](/assets/images/help/repository/reported-content-opt-in-checkbox.png) - -### Leer más - -- "[Administrar el contenido reportado en el repositorio de tu organización](/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository)" -- "[Moderar comentarios y conversaciones](/github/building-a-strong-community/moderating-comments-and-conversations)" -- "[Acerca de la administración y moderación de la comunidad](/github/building-a-strong-community/about-community-management-and-moderation)" diff --git a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository.md b/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository.md deleted file mode 100644 index e6696768e3..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Administrar el contenido reportado en el repositorio de tu organización -intro: 'Una vez que un colaborador reporta contenido ofensivo en un repositorio, los mantenedores del mismo pueden ver y administrar esta información.' -versions: - free-pro-team: '*' -redirect_from: - - /github/building-a-strong-community/managing-reported-content-in-your-organizations-repository ---- -Cualquiera con permisos de administrador para un repositorio puede ver y administrar el contenido reportado del mismo. - -### Acerca de la administración del contenido reportado - -Antes de ver o administrar el contenido reportado, debes habilitar esta opción para el repositorio. Para obtener más información, consulta "[Administrar la forma en la que los colaboradores reportan el abuso en el repositorio de tu organización](/github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository)." - -Puedes rastrear, clasificar y responder a los reportes de contenido ofensivo. Puedes ver todos los reportes y navegar directamente a cada comentario en {% data variables.product.prodname_dotcom %} dentro del listado de "Reportes de abuso". - -{% data reusables.community.tools-for-moderating %} - -Cuando termines de moderar el contenido ofensivo, puedes marcar el reporte como resuelto. Si decides que aún no has terminado de moderarlo, también puedes marcarlo como no resuelto. - -### Ver el contenido que reportó un colaborador - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.sidebar-moderation-reported-content %} -4. Da clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} al costado derecho del contenido reportado que quieres ver. Posteriormente, da clic en **Ver contenido**. !["Ver contenidot" en el menú desplegable de Editar para el contenido reportado](/assets/images/help/repository/reported-content-report-view-content.png) - -### Resolver un reporte - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.sidebar-moderation-reported-content %} -4. Da clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} a la derecha del reporte que quieres resolver. Posteriormente, da clic en **Marcar como resuelto**. !["Marcar como resuleto" en el menú desplegable de Editar para el contenido reportado](/assets/images/help/repository/reported-content-mark-report-as-resolved.png) - -### Marcar un reporte como no resuelto - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.sidebar-moderation-reported-content %} -{% data reusables.repositories.reported-content-resolved-tab %} -5. Da clic en {% octicon "kebab-horizontal" aria-label="The edit icon" %} a la derecha del reporte que quisieras marcar como no resuelto. Posteriormente, da clic en **Marcar como no resuelto**. !["Marcar como no resuelto" en el menú desplegable de Editar para el contenido reportado](/assets/images/help/repository/reported-content-mark-report-as-unresolved.png) - -### Leer más - -- "[Acerca de la administración y moderación de la comunidad](/github/building-a-strong-community/about-community-management-and-moderation)" diff --git a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/tracking-changes-in-a-comment.md b/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/tracking-changes-in-a-comment.md deleted file mode 100644 index 3e98d5b428..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/moderating-comments-and-conversations/tracking-changes-in-a-comment.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Rastrear cambios en un comentario -intro: Puedes ver el historial de edición para un comentario o eliminar información sensible del mismo. -redirect_from: - - /articles/tracking-changes-in-a-comment - - /github/building-a-strong-community/tracking-changes-in-a-comment -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Ver detalles del historial de edición de un comentario - -Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. - -1. Navega hasta el comentario del que quieres ver el historial de edición. -{% data reusables.repositories.edited-comment-list %} - -### Eliminar información confidencial del historial de un comentario - -Los autores de los comentarios y cualquiera con acceso de escritura aun repositorio pueden borrar comentarios sensibles del historial de edición de los mismos. - -Cuando eliminas información confidencial del historial de edición del comentario, la persona que hizo la edición y el momento en que la hizo siguen visibles en el historial del comentario, pero el contenido de la edición deja de estar disponible. - -1. Navega hasta el comentario del que quieres eliminar la información confidencial del historial de edición. -{% data reusables.repositories.edited-comment-list %} -3. En el margen superior derecho de la ventana del historial de edición, haz clic en **Options** (Opciones). Luego haz clic en **Delete revision from history** (Eliminar revisión del historial) para eliminar la diferencia que muestra el contenido que se agrega. ![Eliminar detalles de edición de un comentario](/assets/images/help/repository/delete-comment-edit-details.png) -4. Para confirmar la eliminación, haz clic en **OK**. - -### Leer más - -{% if currentVersion == "free-pro-team@latest" %}- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)"{% endif %} -- "[Editar un comentario](/articles/editing-a-comment)" diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md deleted file mode 100644 index 9463a98ec0..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Acerca de la gestión y moderación de la comunidad -intro: '{% data variables.product.prodname_dotcom %} ofrece herramientas para que los mantenedores de repositorios puedan establecer y dar cumplimiento a los estándares de comportamiento en sus comunidades dentro de {% data variables.product.prodname_dotcom_the_website %}.' -versions: - free-pro-team: '*' -redirect_from: - - /github/building-a-strong-community/about-community-management-and-moderation ---- -### Acerca de la gestión y moderación de la comunidad - -{% data reusables.policies.github-community-guidelines-and-terms %} - -{% data variables.product.prodname_dotcom %} también ofrece herramientas para que los mantenedores de repositorios definan y den cumplimiento a los estándares más altos de comportamiento en sus propias comunidades dentro de {% data variables.product.prodname_dotcom_the_website %}. - -Una vez definidos los estándares de comportamiento de la comunidad, puedes exhortar a que se tenga un ambiente agradable y productivo respondiendo a los comportamientos perjudiciales de manera rápida y justa. Moderar tu comunidad con efectividad generará confianza y permitirá que los colaboradores se sientan seguros y bienvenidos en ella. - -### Herramientas para moderar tu comunidad - -Las herramientas de {% data variables.product.prodname_dotcom %} optimizan la gestión y las tareas de moderación en tu comunidad sin exigir mucha experiencia previa en ello. - -Como mantenedor de repositorio, puedes crear tus propios lineamientos para contribuir con tu proyecto y compartirlos en el mismo. {% data variables.product.prodname_dotcom %} ofrece una lista de control en el perfil de la comunidad que te ayudará a crear y publicar los archivos de salud de la misma. Los colaboradores potenciales de tu proyecto pueden revisar la lista de control en el perfil de tu comunidad para conocer sus estándares y decidir si quieren contribuir. Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)." - -{% data reusables.community.tools-for-moderating %} - -Los colaboradores pueden reportar el contenido perjudicial en {% data variables.contact.github_support %} siempre que lo deseen. Si decides incluir el contenido reportado para un repositorio público en tu organización, los colaboradores también pueden reportar los comentarios que presenten comportamiento perjudicial directamente a los mantenedores del mismo. Para encontrar más información, visita la sección "[Gestionar contenido reportado en el repositorio de tu organización](/github/building-a-strong-community/managing-reported-content-in-your-organizations-repository)." - -### Leer más - -- "[Tu Código de Conducta](https://opensource.guide/code-of-conduct/)" de las Guías de Código Abierto -- "[Construyendo Comunidades de Bienvenida](https://opensource.guide/building-community/)" de las Guías de Código Abierto -- "[Liderazgo y Gobierno](https://opensource.guide/leadership-and-governance/)" de las Guías de Código Abierto -- "[Por qué es inadecuado el humillar a los demás](https://github.community/t5/Studies-in-Community/Shaming-and-why-it-is-inappropriate/ba-p/12728)" del Foro de la Comunidad de GitHub -- "[No es lo mismo la crítica constructiva que el ser tóxico](https://github.community/t5/Studies-in-Community/Being-toxic-is-not-constructive-criticism/ba-p/8029)" del Foro de la Comunidad de GitHub diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md deleted file mode 100644 index cc42a706b5..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Acerca de los perfiles de comunidad para los repositorios públicos -intro: Los mantenedores del repositorio pueden revisar el perfil de comunidad de sus repositorios públicos para saber cómo pueden ayudar a hacer crecer su comunidad y dar soporte a los colaboradores. Los colaboradores pueden ver el perfil de comunidad de un repositorio público para ver si quieren contribuir con el proyecto. -redirect_from: - - /articles/viewing-your-community-profile/ - - /articles/about-community-profiles-for-public-repositories - - /github/building-a-strong-community/about-community-profiles-for-public-repositories -versions: - free-pro-team: '*' ---- -La lista de verificación del perfil de comunidad se comprueba para ver si un proyecto incluye un archivo de salud de comunidad recomendado, como README, CODE_OF_CONDUCT, LICENSE o CONTRIBUTING, en una ubicación admitida. Para obtener más información, consulta "[ una ubicación admitida](/articles/accessing-a-project-s-community-profile)". - -### Usar la lista de verificación del perfil de comunidad como mantenedor del repositorio - -Como mantenedor del repositorio, usa la lista de verificación del perfil de comunidad para ver si tu proyecto cumple con los estándares de comunidad recomendados para ayudar a las personas a usar y contribuir con tu proyecto. Para obtener más información, consulta "[Construir una comunidad](https://opensource.guide/building-community/)" en las Guías de código abierto. - -Si un proyecto no tiene un archivo recomendado, puedes hacer clic en **Agregar** para redactar y enviar un archivo. - -{% data reusables.repositories.valid-community-issues %} Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". - -![Lista de verificación del perfil de comunidad con estándares de comunidad recomendados para mantenedores](/assets/images/help/repository/add-button-community-profile.png) - -{% data reusables.repositories.security-guidelines %} - -### Usar la lista de verificación del perfil de comunidad como colaborador o miembro de la comunidad - -Como posible colaborador, usa la lista de verificación del perfil de comunidad para ver si tu proyecto cumple con los estándares de comunidad recomendados y decidir si quieres contribuir. Para obtener más información, consulta "[¿Cómo contribuir?](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)" en las Guías de código abierto. - -Si un proyecto no tiene un archivo recomendado, puedes hacer clic en **Proponer** para redactar y enviar un archivo para que el mantenedor del repositorio lo apruebe. - -![Lista de verificación del perfil de comunidad con estándares de comunidad recomendados para colaboradores](/assets/images/help/repository/propose-button-community-profile.png) - -### Leer más - -- "[Agregar un código de conducta a tu proyecto](/articles/adding-a-code-of-conduct-to-your-project)" -- "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)" -- "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)" -- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" -- "[Guías de código abierto](https://opensource.guide/)" -- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/accessing-a-projects-community-profile.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/accessing-a-projects-community-profile.md deleted file mode 100644 index 6d151c111a..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/accessing-a-projects-community-profile.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Acceso a un perfil de comunidad del proyecto -intro: Ver un perfil de comunidad del repositorio público para verificar el estado de un proyecto y decidir si deseas contribuir. -redirect_from: - - /articles/accessing-a-project-s-community-profile - - /articles/accessing-a-projects-community-profile - - /github/building-a-strong-community/accessing-a-projects-community-profile -versions: - free-pro-team: '*' ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -3. En la barra lateral izquierda, haz clic en **Community** (Comunidad). ![Comunidad en la barra lateral izquierda](/assets/images/help/graphs/graphs-sidebar-community-tab.png) - -### Leer más - -- [Acerca de los perfiles de la comunidad para repositorios públicos](/articles/about-community-profiles-for-public-repositories)" diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md deleted file mode 100644 index 7ed3c0031b..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Agregar un código de conducta a tu proyecto -intro: 'Adoptar un código de conducta para definir los estándares de la comunidad, señalizar un proyecto cordial e inclusivo, y delinear los procedimientos para manejar los abusos.' -redirect_from: - - /articles/adding-a-code-of-conduct-to-your-project - - /github/building-a-strong-community/adding-a-code-of-conduct-to-your-project -versions: - free-pro-team: '*' ---- -Un *código de conducta* define los estándares de cómo participar en una comunidad. Señala un entorno inclusivo que respeta todas las contribuciones. También describe los procedimientos para tratar problemas de tus proyectos entre los miembros de la comunidad. Para obtener más información acerca de por qué un código de conducta define los estándares y las expectativas sobre cómo participar en una comunidad, consulta la [Guía de Código abierto](https://opensource.guide/code-of-conduct/). - -Antes de adoptar un código de conducta para tu proyecto: - -* Investiga códigos de conducta diferentes diseñados para proyectos de código abierto. Elije uno que refleje los estándares de tu comunidad. -* Considera cuidadosamente si estás dispuesto a hacerlo cumplir y puedes hacerlo. - -Puedes agregar un código de conducta a tu proyecto si utilizas una plantilla o creando manualmente un código de conducta personalizado. Tu código de conducta estará disponible de cualquier forma, pero el "Código de conducta" solo se marcará como completo en el perfil comunitario de tu repositorio si utilizas una plantilla. Si utilizas un código de conducta que escriba otra persona u organización, asegúrate de utilizar los lineamientos de adjudicación de la fuente. Para obtener más información acerca de los perfiles comunitarios, consulta la sección "[Acerca de los perfiles comunitarios para los repositorios públicos](/github/building-a-strong-community/about-community-profiles-for-public-repositories)". - -Puedes crear un código de conducta por defecto para tu organización o cuenta de usuario. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)" - -### Agregar un código de conducta mediante una plantilla - -{% data variables.product.product_name %} brinda plantillas para códigos de conducta comunes a fin de ayudarte a agregar rápidamente un código de conducta para tu proyecto. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. En el campo de nombre del archivo, escribe *CODE_OF_CONDUCT.md*. -4. Haz clic en **Choose a code of conduct template** (Elegir una plantilla de código de conducta). ![Botón para elegir una plantilla de código de conducta](/assets/images/help/repository/code-of-conduct-tool.png) -5. En el lateral izquierdo de la página, selecciona un código de conducta para previsualizar y agregar a tu proyecto. ![Selección de una plantilla de código de conducta](/assets/images/help/repository/code-of-conduct-tool-picker.png) -6. En el lateral derecho de la página, completa los campos para llenar el código de conducta seleccionado con la información adecuada. -7. Haz clic en **Review and submit** (Revisar y enviar). ![Revisar y enviar el código de conducta a un proyecto](/assets/images/help/repository/code-of-conduct-tool-review.png) -8. Revisa los contenidos del código de conducta que está en el área de texto. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -### Agregar un código de conducta manualmente - -Si el código de conducta que quieres utilizar no se encuentra disponible en las plantillas proporcionadas, puedes agregar manualmente un código de conducta. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. En el campo de nombre, teclea el nombre y la extensión del archivo. ![Nombre de archivo del código de conducta nuevo](/assets/images/help/repository/new-code-of-conduct-file-name.png) - - Para que tu código de conducta se muestre como visible en el directorio raíz del repositorio, teclea *CODE_OF_CONDUCT* en el campo de nombre de archivo. - - Para que tu código de conducta esté visible en los `docs` del repositorio, teclea *docs/CODE_OF_CONDUCT*. - - Para que tu código de conducta esté visible en el directorio `.github` del repositorio, teclea type *.github/CODE_OF_CONDUCT*. -4. En el archivo nuevo, agrega tu código de conducta personalizado. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md deleted file mode 100644 index 2f9e3eeb3f..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Agregar una licencia a un repositorio -intro: Puedes incluir una licencia de código abierto en tu repositorio para que simplifique la contribución de otras personas. -redirect_from: - - /articles/adding-a-license-to-a-repository - - /github/building-a-strong-community/adding-a-license-to-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Si incluyes una licencia detectable en tu repositorio, las personas que visiten tu repositorio la verán en la parte superior de la página del repositorio. Para leer el archivo de licencia completa, haz clic en el nombre de la licencia. - -![Un encabezado de repositorio con una licencia MIT](/assets/images/help/repository/repo-license-indicator.png) - -Las licencias de código abierto permiten que otras personas usen, cambien y distribuyan el proyecto en tu repositorio. Para más información sobre las licencias de repositorios, consulta "[Licenciar un repositorio](/articles/licensing-a-repository)". - -### Incluir una licencia de código abierto en tu repositorio - - -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. En el campo del nombre del archivo, escribe *LICENSE* o *LICENSE.md* (todo en mayúscula). -4. A la derecha del campo del nombre del archivo, haz clic en **Elegir una plantilla de licencia**. ![Elige un botón para la plantilla de licencia](/assets/images/help/repository/license-tool.png) -5. En el lateral izquierdo de la página, en "Agregar una licencia a tu proyecto", revisa las licencias disponibles, luego selecciona una licencia de la lista. ![Lista de licencias disponibles](/assets/images/help/repository/license-tool-picker.png) -6. Haz clic en **Review and submit** (Revisar y enviar). ![Botón Review and submit (Revisar y enviar)](/assets/images/help/repository/license-review-tool.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.choose-commit-email %} -10. Haz clic en **Commit new file** (Confirmar archivo nuevo). ![Confirmar licencia a la rama](/assets/images/help/repository/license-submit-tool.png) - -{% endif %} - - -{% if currentVersion != "free-pro-team@latest" %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. En el campo del nombre del archivo, escribe *LICENSE* o *LICENSE.md* (todo en mayúscula). -4. En la pestaña **Edit new file** (Editar archivo nuevo), pega el texto completo de la licencia que deseas usar. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -7. Debajo de los campos del mensaje de confirmación, decide si deseas agregar tu confirmación a la rama actual o a una rama nueva. Si tu rama actual es `main`, deberás elegir crear una nueva rama para tu confirmación y luego crear una solicitud de extracción. Para obtener más información, consulta la sección"[Crear una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request)". ![Confirmar opciones de rama](/assets/images/help/repository/choose-commit-branch.png) -8. Haz clic en **Commit new file** (Confirmar archivo nuevo). ![Confirmar licencia a la rama](/assets/images/help/repository/license-submit-tool.png) - -{% endif %} - -### Leer más - -- "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md deleted file mode 100644 index ea42285207..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Agregar recursos de soporte a tu proyecto -intro: Puedes crear un archivo de SOPORTE para permitir que las personas conozcan nueva maneras de obtener ayuda con tu proyecto. -redirect_from: - - /articles/adding-support-resources-to-your-project - - /github/building-a-strong-community/adding-support-resources-to-your-project -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Para dirigir a las personas hasta recursos de soporte específicos, puedes agregar un archivo de SOPORTE a tu raíz de repositorio, `docs` (documentos), o carpeta `.github`. Cuando alguien crea una propuesta en tu repositorio, verá un enlace en el archivo de SOPORTE de tu proyecto. - -![Lineamientos de soporte](/assets/images/help/issues/support_guidelines_in_issue.png) - -Pedes crear recursos de soporte predeterminados para tu organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o cuenta de usuario{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)" - -{% tip %} - -**Sugerencia:** Para ayudar a las personas a buscar sus lineamientos de soporte, puedes vincular tu archivo de SOPORTE desde otros lugares en tu repositorio, como tu [archivo README](/articles/about-readmes/). - -{% endtip %} - -### Agregar recursos de soporte a tu proyecto - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. En el campo de nombre del archivo, escribe *SUPPORT.md* (todo en mayúsculas. -4. En la pestaña **Edit new file** (Editar archivo nuevo), agrega la información sobre las personas que pueden obtener soporte para tu proyecto. -5. Para revisar tu archivo de SOPORTE, haz clic en **Preview** (Vista previa). -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md deleted file mode 100644 index 16cb6703af..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Creando un archivo predeterminado para la salud de la comunidad -intro: 'Puedes crear archivos predeterminados para la salud de la comunidad, como CONTRIBUTING (Contribuciones) y CODE_OF_CONDUCT (Código de conducta). Los archivos predeterminados se utilizarán para cualquier repositorio público propiedad de la cuenta que no contenga su propio archivo de ese tipo.' -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 - - /github/building-a-strong-community/creating-a-default-community-health-file -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de los archivos predeterminados del estado de la comunidad - -Puedes añadir archivos de salud predeterminados para la comunidad en la raíz del repositorio público llamada `gihub` que sea propiedad de una organización {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o cuenta de usuario{% endif %}. - -{% data variables.product.product_name %} utilizará y mostrará los archivos predeterminados para cualquier repositorio público que sea propiedad de la cuenta que no tiene su propio archivo de ese tipo en ninguno de los siguientes lugares: -- la raíz del repositorio -- la carpeta `.github` -- la carpeta `docs` - -Por ejemplo, una persona que cree una propuesta o solicitud de extracción en un repositorio público que no tenga su propio archivo CONTRIBUTING verá un enlace al archivo CONTRIBUTING predeterminado. Si un repositorio tiene cualquier archivo en su propia carpeta {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} de `.github/ISSUE_TEMPLATE`, incluyendo las plantillas de reporte de problemas o un archivo{% endif %}de *config.yml*, no se utilizará ninguno de los contenidos de la carpeta `.github/ISSUE_TEMPLATE`. - -Los archivos predeterminados no están incluidos en los clones, paquetes ni descargas de repositorios individuales porque se almacenan únicamente en el repositorio `.github`. - -### Tipos de archivos admitidos - -Puedes crear versiones predeterminadas en tu organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o cuenta de usuario{% endif %} para los siguientes archivos de salud de la comunidad: - -| Archivo de salud de la comunidad | Descripción | -| ------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% if currentVersion == "free-pro-team@latest" %} -| *CODE_OF_CONDUCT.md* | Un archivo CODE_OF_CONDUCT define las normas para participar en una comunidad. Para obtener más información, consulta "[Agregar un código de conducta a tu proyecto](/articles/adding-a-code-of-conduct-to-your-project/)".{% endif %} -| *CONTRIBUTING.md* | Un archivo CONTRIBUTING comunica cómo pueden contribuir las personas con tu proyecto. Para obtener más información, consulta "[Establecer pautas para los colaboradores del repositorio](/articles/setting-guidelines-for-repository-contributors/)".{% if currentVersion == "free-pro-team@latest" %} -| *FUNDING.yml* | Un archivo FUNDING muestra un botón de patrocinador en tu repositorio para aumentar la visibilidad de las opciones de financiación para tu proyecto de código abierto. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)".{% endif %} -| Plantillas de reporte de problemas y solicitudes de extracción{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} y *config.yml*{% endif %} | Las plantillas de propuestas y solicitudes de extracción personalizan y estandarizan la información que quieres que incluyan los colaboradores cuando abren propuestas y solicitudes de extracción en tu repositorio. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates/)".{% if currentVersion == "free-pro-team@latest" %} -| *SECURITY.md* | Un archivo SECURITY da indicaciones para informar responsablemente acerca de una vulnerabilidad de seguridad en tu proyecto. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/articles/adding-a-security-policy-to-your-repository)".{% endif %} -| *SUPPORT.md* | Un archivo SOPPORT les permite a las personas conocer las formas de obtener ayuda con tu proyecto. Para obtener más información, consulta "[Agregar recursos de soporte a tu proyecto](/articles/adding-support-resources-to-your-project/)." | - -No puedes crear un archivo de licencia predeterminado. Los archivos de licencia se deben agregar a repositorios individuales, de manera que el archivo se incluirá cuando el proyecto se clone, se coloque dentro de un paquete o se descargue. - -### Crear un repositorio para archivos predeterminados - -{% data reusables.repositories.create_new %} -2. Utiliza el menú desplegable en **Propietario**, y selecciona la organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o cuenta de usuario{% endif %} para la cual quieres crear los archivos predeterminados. ![Menú desplegable Propietario](/assets/images/help/repository/create-repository-owner.png) -3. Escribe **.github** como nombre para tu repositorio y escribe una descripción opcional. ![Crear un campo de repositorio](/assets/images/help/repository/default-file-repository-name.png) -4. Elige hacer que el repositorio sea público. ![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{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} y su archivo de configuración{% endif %} deben estar en una carpeta llamada `.github/ISSUE_TEMPLATE`. Todos los demás archivos admitidos deben estar en la raíz del repositorio. Para obtener más información, consulta "[Crear nuevos archivos](/articles/creating-new-files/)." diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md deleted file mode 100644 index 8fdbe23054..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Fomentar colaboraciones útiles a tu proyecto con etiquetas -intro: Aplica la etiqueta `good first issue` (primera buena propuesta) a las propuestas de tu repositorio para resaltar las oportunidades que las personas tienen para contribuir con tu proyecto. -redirect_from: - - /github/building-a-strong-community/helping-new-contributors-find-your-project-with-labels - - /articles/helping-new-contributors-find-your-project-with-labels - - /github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels -versions: - free-pro-team: '*' ---- -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)". - -{% 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. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issues %} -{% data reusables.repositories.select-items-in-issue-or-pr-list %} -4. En la esquina superior derecha, haz clic en **Label** (etiqueta), luego escribe `good first issue` (primera buena propuesta). Haz clic en el nombre de la etiqueta para asociarla con los elementos seleccionados. ![Desplegable de la asignación de hitos de propuestas](/assets/images/help/issues/issues_applying_labels_dropdown.png) - -### Leer más - -- "[Acerca de las etiquetas](/articles/about-labels)" -- "[Buscar repositorios](/articles/searching-for-repositories)" diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/index.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/index.md deleted file mode 100644 index bebb99be5b..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Configurar tu proyecto para contribuciones saludables -intro: Los mantenedores del repositorio pueden configurar pautas de contribuciones para ayudar a los colaboradores a hacer contribuciones significativas y útiles a tu proyecto. -redirect_from: - - /articles/helping-people-contribute-to-your-project/ - - /articles/setting-up-your-project-for-healthy-contributions -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-community-management-and-moderation - - /about-community-profiles-for-public-repositories - - /accessing-a-projects-community-profile - - /adding-a-code-of-conduct-to-your-project - - /setting-guidelines-for-repository-contributors - - /adding-a-license-to-a-repository - - /adding-support-resources-to-your-project - - /creating-a-default-community-health-file - - /encouraging-helpful-contributions-to-your-project-with-labels ---- - diff --git a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md deleted file mode 100644 index 4291bc1b03..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Configurar pautas para los colaboradores de repositorios -redirect_from: - - /articles/how-do-i-set-up-guidelines-for-contributors/ - - /articles/setting-guidelines-for-repository-contributors - - /github/building-a-strong-community/setting-guidelines-for-repository-contributors -intro: Puedes crear pautas para comunicar cómo pueden contribuir las personas a tu proyecto. -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Para ayudar a los colaboradores de tu proyecto a realizar un buen trabajo, puedes agregar un archivo con las pautas de colaboración a la raíz del repositorio de tu proyecto, carpeta `docs`, o `.github`. Cuando alguien abre una solicitud de extracción o crea una propuesta, verán un enlace a ese archivo. - -![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png) - -Para el propietario del repositorio, las pautas de contribución son una manera de comunicar cómo deben contribuir las personas. - -Para los colaboradores, las pautas los ayudan a verificar que están presentando solicitudes de extracción conformadas correctamente y abriendo propuestas útiles. - -Tanto para los propietarios como para los colaboradores, las pautas de contribución ahorran tiempo y evitan inconvenientes generados por solicitudes de extracción o propuestas creadas de manera incorrecta que deben ser rechazadas o se deben volver a presentar. - -Puedes crear lineamientos de contribución predeterminados para tu organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o cuenta de usuario{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)" - -{% tip %} - -**Sugerencia:** los mantenedores de repositorios pueden establecer pautas específicas para las propuestas al crear una plantilla de propuesta o de solicitud de extracción para el repositorio. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". - -{% endtip %} - -### Agregar un archivo *CONTRIBUTING* - -{% 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 archivos de las pautas de contribución no distinguen entre mayúsculas y minúsculas y pueden tener una extensión *.md* o *.txt*. ![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*. -4. En el nuevo archivo, agrega las pautas de contribución. Pueden incluir: - - Pasos para crear buenas propuestas o solicitudes de extracción. - - Enlaces a la documentación externa, listas de correos o un código de conducta. - - Expectativas de comportamiento y de la comunidad. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -### Ejemplos de pautas de contribución - -Si estás confundido, aquí hay algunos buenos ejemplos de pautas de contribución: - -- Pautas de contribución del Editor Atom [](https://github.com/atom/atom/blob/master/CONTRIBUTING.md). -- Pautas de contribución de Ruby on Rails [](https://github.com/rails/rails/blob/master/CONTRIBUTING.md). -- Pautas de contribución de Open Government [](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md). - -### Leer más -- La sección de la Guía de código abierto "[Iniciar un proyecto de código abierto](https://opensource.guide/starting-a-project/)"{% if currentVersion == "free-pro-team@latest" %} -- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} -- "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)" diff --git a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md deleted file mode 100644 index e249a3f585..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Acerca de las plantillas de propuestas y solicitudes de extracción -intro: 'Con las plantillas de propuestas y solicitudes de extracción, puedes personalizar y estandarizar la información que quisieras que los colaboradores incluyan cuando abren propuestas y solicitudes de extracción en tu repositorio.' -redirect_from: - - /articles/about-issue-and-pull-request-templates - - /github/building-a-strong-community/about-issue-and-pull-request-templates -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Una vez que creas las plantillas de propuestas y solicitudes de extracción en tu repositorio, los colaboradores pueden usar las plantillas para abrir propuestas o describir los cambios propuestos en sus solicitudes de extracción de acuerdo con las pautas de contribución del repositorio. Para obtener más información sobre cómo agregar pautas de contribución a un repositorio, consulta "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)". - -Puedes crear plantillas de reporte de problemas y de solicitud de extracción para tu organización {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o cuenta de usuario{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)" - -### Plantillas de propuestas - -Cuando creas plantillas de propuestas para tu repositorio usando el creador de plantillas de propuestas, estarán disponibles para que las usen los colaboradores cuando abran nuevas propuestas en el repositorio. - -![Página de la propuesta nueva que muestra las opciones de plantilla de propuesta](/assets/images/help/issues/new-issue-page-with-multiple-templates.png) - -Al usar el creador de plantillas, puedes especificar un título y una descripción para cada plantilla, agregar el contenido de la plantilla y asignar la plantilla a la rama por defecto o bien abrir una solicitud de extracción en el repositorio. El creador de plantillas automáticamente agrega el markup del texto preliminar de YAML que se requiere para que la plantilla aparezca en la página de la propuesta nueva. Para obtener más información, consulta "[Configurar plantillas de reporte de problemas para tu repositorio](/articles/configuring-issue-templates-for-your-repository)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% data reusables.repositories.issue-template-config %} Para obtener más información, consulta "[Configurar plantillas de propuestas para tu repositorio](/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)". -{% endif %} - -Las plantillas de propuestas se almacenan en la rama por defecto del repositorio, en un directorio oculto `.github/ISSUE_TEMPLATE`. Si creas una plantilla en otra rama, no estará disponible para que la usen los colaboradores. Los nombres de archivo de la plantilla de propuesta no distinguen entre mayúsculas y minúsculas y necesitan una extensión *.md*. {% data reusables.repositories.valid-community-issues %} - -Es posible crear de forma manual una única plantilla de propuesta en Markdown usando el flujo de trabajo de la plantilla de propuesta heredado. Los colaboradores del proyecto automáticamente ven el contenido de la plantilla en el cuerpo de la propuesta. Si embargo, recomendamos usar el creador de varias plantillas de propuestas actualizado para crear plantillas de propuestas. Para obtener más información acerca del flujo de trabajo heredado, consulta "[Crear de forma manual una plantilla de propuesta para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)". - -{% data reusables.repositories.security-guidelines %} - -### Plantillas de solicitudes de extracción - -Cuando agregas una plantilla de solicitud de extracción a tu repositorio, los colaboradores del proyecto verán automáticamente los contenidos de la plantilla en el cuerpo de la solicitud de extracción. - -![Plantilla de solicitud de extracción de ejemplo](/assets/images/help/pull_requests/pr-template-sample.png) - -Debes crear las plantillas en la rama por defecto del repositorio. Las plantillas creadas en otras ramas no están disponibles para que las usen los colaboradores. Puedes almacenar tu plantilla de solicitud de extracción en el directorio raíz visible del repositorio, la carpeta `docs` o el directorio oculto `.github`. Los nombres de archivo de la plantilla de solicitud de extracción no distinguen entre mayúsculas y minúsculas y pueden tener una extensión como *.md* o *.txt*. - -Para obtener más información, consulta [Crear plantillas de solicitud de extracción para tu repositorio](/articles/creating-a-pull-request-template-for-your-repository)". diff --git a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md deleted file mode 100644 index cc4270e95d..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Configurar las plantillas de reporte de problemas para tu repositorio -intro: Puedes personalizar las plantillas disponibles para los colaboradores para que las utilicen cuando abren un nuevo reporte de problema en tu repositorio. -redirect_from: - - /github/building-a-strong-community/creating-issue-templates-for-your-repository - - /articles/configuring-issue-templates-for-your-repository - - /github/building-a-strong-community/configuring-issue-templates-for-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.repositories.default-issue-templates %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -### Crear plantillas de reporte de problemas -{% endif %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En la sección "Características", en "Propuestas", haz clic en **Configurar plantillas**. ![Botón Start template setup (Comenzar la configuración de plantilla)](/assets/images/help/repository/set-up-templates.png) -4. Usa el menú desplegable Agregar plantilla y haz clic en el tipo de plantilla que deseas crear. ![Menú desplegable Agregar plantilla](/assets/images/help/repository/add-template-drop-down-menu.png) -5. Para acceder a la vista previa o editar la plantilla antes de confirmarla en el repositorio, haz clic en ** Mostrar la vista previa y editar**. ![Botón para mostrar la vista previa y editar](/assets/images/help/repository/preview-and-edit-button.png) -6. Para editar la plantilla, haz clic en {% octicon "pencil" aria-label="The edit icon" %} y escribe en los campos para editar el contenido. ![Botón Issue template edit (Editar plantilla de propuesta)](/assets/images/help/repository/issue-template-edit-button.png) -7. Para establecer automáticamente un título predeterminado para la propuesta, asigna la propuesta a personas que tengan acceso de lectura al repositorio o aplica etiquetas a tu plantilla de propuesta e ingresa estos detalles en "Información adicional opcional". También puedes agregar estos detalles en la plantilla de propuesta con `título`, `etiquetas` o `asignatario` en un formato de texto preliminar en lenguaje YAML. ![Información adicional de plantilla de propuesta](/assets/images/help/repository/additional-issue-template-info.png) -8. Cuando hayas terminado de editar y visualizar la vista previa de tu plantilla, haz clic en **Proponer cambios** en el ángulo superior derecho de la página. ![Botón para proponer cambios](/assets/images/help/repository/propose-changes-button.png) -9. Escribe un mensaje de confirmación que describa los cambios que realizaste. ![Campo para el mensaje de confirmación de la plantilla de propuesta](/assets/images/help/repository/issue-template-commit-message-field.png) -10. Debajo de los campos del mensaje de confirmación, decide si deseas confirmar tu plantilla directamente en la rama predeterminada o si deseas crear una nueva rama y abrir una solicitud de extracción. Para obtener más información acerca de las solicitudes de extracción, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)". ![Confirmar la plantilla de propuesta al repositorio principal u opción de abrir una solicitud de extracción](/assets/images/help/repository/issue-template-commit-to-master-or-open-pull-request.png) -11. Haz clic en **Commit changes** (Confirmar cambios). Una vez que estos cambios se fusionen en la rama predeterminada, la plantilla estará disponible para que la usen los colaboradores cuando abran nuevas propuestas en el repositorio. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -### Configurar el selector de plantillas - -{% data reusables.repositories.issue-template-config %} - -Puedes alentar a los colaboradores para que utilicen plantillas de informe de problemas si configuras el parámetro `blank_issues_enabled` como `false`. Si configuras `blank_issues_enabled` como `true`, las personas podrán abrir un reporte de problema en blanco. - -{% note %} - -**Nota:** Si utilizaste tu flujo de trabajo tradicional para crear manualmente un archivo de `issue_template.md` fy habilitaste el reporte de problemas en blanco en tu archivo de *config.yml* se utilizará la plantilla en `issue_template.md` cuando las personas decidan abrir un reporte de problema en blanco. Si inhabilitas los reportes de problemas en blanco, la plantilla nunca se utilizará. - -{% endnote %} - -Si prefieres recibir ciertos reportes fuera de {% data variables.product.product_name %}, puedes dirigir a las personas a sitios externos con `contact_links`. - -Aquí hay un ejemplo del archivo *config.yml*. - -```shell -blank_issues_enabled: false -contact_links: - - name: {% data variables.product.prodname_gcf %} - url: https://github.community/ - about: Please ask and answer questions here. - - name: {% data variables.product.prodname_dotcom %} Security Bug Bounty - url: https://bounty.github.com/ - about: Please report security vulnerabilities here. -``` - -Tu archivo de configuración personalizará el selector de plantilla cuando el archivo se combina en la rama predeterminada del repositorio. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. Teclea `.github/ISSUE_TEMPLATE/config.yml` en el campo de nombre de archivo. ![Nombre de archivo de configuración](/assets/images/help/repository/template-config-file-name.png) -4. Teclea el contenido de tu archivo de configuración en el cuerpo del nuevo archivo. ![Contenido de archivo de configuración](/assets/images/help/repository/template-config-file-content.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} -{% endif %} - -### Leer más - -- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" -- "[Crear de forma manual una plantilla de propuesta única para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)" diff --git a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md deleted file mode 100644 index e0d6b92a4f..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Crear una plantilla de solicitud de extracción para tu repositorio -intro: 'Cuando agregas una plantilla de solicitud de extracción a tu repositorio, los colaboradores del proyecto verán automáticamente los contenidos de la plantilla en el cuerpo de la solicitud de extracción.' -redirect_from: - - /articles/creating-a-pull-request-template-for-your-repository - - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". - -Puedes crear un subdirectorio *PULL_REQUEST_TEMPLATE/* en alguna de las carpetas admitidas para incluir múltiples plantillas de solicitudes de extracción, y utilizar el parámetro de consulta `template` para especificar la plantilla que completará el cuerpo de la solicitud de extracción. Para obtener más información, consulta "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" - -Puedes crear plantillas de solicitud de extracción predeterminadas para tu organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o cuenta de usuario{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)" - -### Agregar una plantilla de solicitud de extracción - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. En el campo del nombre del archivo: - - Para hacer que tu plantilla de solicitud de extracción se pueda ver en el directorio raíz del repositorio, nómbrala como `pull_request_template.md`. ![Nuevo nombre de plantilla de solicitud de extracción en un directorio raíz](/assets/images/help/repository/pr-template-file-name.png) - - Para hacer que tu plantilla de solicitud de extracción se pueda ver en el directorio `docs` del repositorio, nómbrala como `docs/pull_request_template.md`. ![Nueva plantilla de solicitud de extracción en un directorio de documentos](/assets/images/help/repository/pr-template-file-name-docs.png) - - Para guardar tu archivo en un directorio oculto, nombra la plantilla de solicitud de extracción `.github/pull_request_template.md`. ![Nueva plantilla de solicitud de extracción en un directorio oculto](/assets/images/help/repository/pr-template-hidden-directory.png) - - Para crear plantillas de solicitud de extracción múltiples y utilizar el parámetro de consulta `template` para especificar una plantilla para completar el cuerpo de la solicitud de extracción, escribe *.github/PULL_REQUEST_TEMPLATE/* y luego, el nombre de tu plantilla de solicitud de extracción. Por ejemplo, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. También puedes almacenar plantillas de solicitud de extracción múltiples en un subdirectorio `PULL_REQUEST_TEMPLATE` dentro de la raíz o directorios `docs/`. Para obtener más información, consulta "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" ![Nueva plantilla de solicitud de extracción múltiple en un directorio oculto](/assets/images/help/repository/pr-template-multiple-hidden-directory.png) -4. En el cuerpo del nuevo archivo, agrega tu plantilla de solicitud de extracción. Puede incluir: - - Una [ referencia a una propuesta relacionada](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) en tu repositorio. - - Una descripción de los cambios propuestos en la solicitud de extracción. - - [@menciones](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) de la persona o del equipo responsable de revisar los cambios propuestos. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} Las plantillas están a disposición de los colaboradores cuando se fusionan en la rama predeterminada del repositorio. -{% data reusables.files.propose_new_file %} - -### Leer más - -- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" -- "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" -- "[Crear una solicitud de extracción](/articles/creating-a-pull-request)" diff --git a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/index.md deleted file mode 100644 index 2be9f83df4..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Utilizar plantillas para promover informes de problemas y solicitudes de extracción útiles -intro: Los mantenedores del repositorio pueden agregar plantillas en un repositorio para ayudar a los contribuyentes a crear propuestas y solicitudes de extracción de alta calidad. -redirect_from: - - /github/building-a-strong-community/using-issue-and-pull-request-templates - - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository/ - - /articles/using-issue-and-pull-request-templates -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-issue-and-pull-request-templates - - /configuring-issue-templates-for-your-repository - - /creating-a-pull-request-template-for-your-repository - - /manually-creating-a-single-issue-template-for-your-repository ---- - diff --git a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md b/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md deleted file mode 100644 index ff82176390..0000000000 --- a/translations/es-XL/content/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Crear de forma manual una plantilla de propuesta única para tu repositorio -intro: 'Cuando agregas una plantilla de propuesta creada de forma manual a tu repositorio, los colaboradores del proyecto verán automáticamente los contenidos de la plantilla en el cuerpo de la propuesta.' -redirect_from: - - /articles/creating-an-issue-template-for-your-repository/ - - /articles/manually-creating-a-single-issue-template-for-your-repository - - /github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.repositories.legacy-issue-template-tip %} - -Puedes crear un subdirectorio de *ISSUE_TEMPLATE/* (PLANTILLA DE PROPUESTA) en alguna de las carpetas admitidas para incluir múltiples plantillas de propuestas, y utilizar el parámetro de consulta `template` para especificar la plantilla que completará el cuerpo de la propuesta. Para obtener más información, consulta "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" - -Puede añadir texto preliminar de YAML a cada plantilla de reporte de problemas para pre-llenar el título del mismo, añadir etiquetas y personal asignado automáticamente, y asignar un nombre y descripción que se mostrará en el selector de la misma, el cual verán las personas cuando se cree un nuevo reporte de problemas en su repositorio. - -Aquí hay un ejemplo de texto preliminar de YAML. - -``` ---- -nombre: Problema de rastreo -acerca de: Utilice esta plantilla para rastrear nuevas características. -título: "[DATE]: [FEATURE NAME]" -etiquetas: problema de rastreo, necesita clasificación -asignados: octocat ---- -``` -{% note %} - -**Nota:** Debes poner los -caracteres reservados de YAML tales como `:` entre comillas. Por ejemplo, `":bug: Bug"`. - -{% endnote %} - -{% if currentVersion == "free-pro-team@latest" %} - -{% data reusables.repositories.valid-community-issues %} - -{% endif %} - -{% data reusables.repositories.default-issue-templates %} - -### Agregar una plantilla de propuesta - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.files.add-file %} -3. En el campo del nombre del archivo: - - Para que tu plantilla de propuesta sea visible en el directorio raíz del repositorio, escribe el nombre de tu *issue_template* (plantilla de propuesta). Por ejemplo, `issue_template.md`. ![Nuevo nombre de la plantilla de propuesta en un directorio raíz](/assets/images/help/repository/issue-template-file-name.png) - - Para que tu plantilla de propuesta sea visible en el directorio `docs` del repositorio, escribe *docs/* seguido del nombre de tu *issue_template*. Por ejemplo, `docs/issue_template.md`, ![Nueva plantilla de propuesta en el directorio docs](/assets/images/help/repository/issue-template-file-name-docs.png) - - Para almacenar tu archivo en un directorio escondido, escribe *.github/* seguido del nombre de tu *issue_template*. Por ejemplo, `.github/issue_template.md`. ![Nueva plantilla de propuesta en un directorio oculto](/assets/images/help/repository/issue-template-hidden-directory.png) - - Para crear múltiples plantillas de propuestas y utilizar el parámetro de consulta `template` para especificar una plantilla para que complete el cuerpo de la propuesta, escribe *.github/ISSUE_TEMPLATE/*, después el nombre de tu plantilla de propuesta. Por ejemplo, `.github/ISSUE_TEMPLATE/issue_template.md`. Puedes también almacenar múltiples plantillas de propuestas en un subdirectorio `ISSUE_TEMPLATE` dentro de la raíz o directorios `docs/`. Para obtener más información, consulta "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" ![Nueva plantilla de propuesta múltiple en un directorio oculto](/assets/images/help/repository/issue-template-multiple-hidden-directory.png) -4. En el cuerpo del nuevo archivo, agrega tu plantilla de propuesta. Puede incluir: - - Texto preliminar de YAML - - Comportamiento esperado y comportamiento real - - Pasos para reproducir el problema - - Specifications like the version of the project, operating system, or hardware -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} Las plantillas están a disposición de los colaboradores cuando se fusionan en la rama predeterminada del repositorio. -{% data reusables.files.propose_new_file %} - -### Leer más - -- "[Acerca de las plantillas de propuestas y de solicitudes de extracción](/articles/about-issue-and-pull-request-templates)" -- "[Configurar las plantillas de reporte de problemas en su repositorio](/articles/configuring-issue-templates-for-your-repository)" -- "[Acerca de la automatización para las propuestas y las solicitudes de extracción con parámetros de consulta ](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" -- "[Crear una propuesta](/articles/creating-an-issue)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md deleted file mode 100644 index 09e95f7391..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Acerca de los conflictos de fusión -intro: 'Los conflictos de fusión suceden cuando fusionas ramas que tienen confirmaciones de cambios contrapuestas, y Git necesita tu ayuda para decidir qué cambios incorporar en la fusión final.' -redirect_from: - - /articles/about-merge-conflicts - - /github/collaborating-with-issues-and-pull-requests/about-merge-conflicts -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Por lo general, Git puede resolver las diferencias entre las ramas y fusionarlas automáticamente. Generalmente, los cambios están en diferentes líneas o incluso en diferentes archivos, lo que hace que sea simple para los equipos comprender la fusión. Sin embargo, a veces hay cambios contrapuestos que Git no puede resolver sin tu ayuda. Por lo general, los conflictos de fusión suceden cuando las personas realizan diferentes cambios en la misma línea en el mismo archivo o cuando una persona edita un archivo y otra persona elimina el mismo archivo. - -Debes resolver todos los conflictos de fusión antes de poder fusionar un solicitud de extracción en {% data variables.product.product_name %}. Si tienes un conflicto de fusión entre la rama de comparación y la rama base en tu solicitud de extracción, puedes ver una lista de archivos con cambios conflictivos arriba del botón **Fusionar solicitud de extracción**. El botón **Fusionar solicitud de extracción** se desactiva hasta que hayas resuelto todos los conflictos entre la rama de comparación y la rama base. - -![mensaje de error de conflicto de fusión](/assets/images/help/pull_requests/merge_conflict_error_on_github.png) - -### Resolver conflictos de fusión - -Para resolver un conflicto de fusión, debes editar de forma manual el archivo conflictivo para seleccionar los cambios que quieres mantener en la fusión final. Hay un par de maneras diferentes de resolver un conflicto de fusión: - -- Si tu conflicto de fusión es ocasionado por cambios de líneas contrapuestos, como cuando las personas realizan diferentes cambios en la misma línea del mismo archivo en diferentes ramas en tu repositorio de Git, lo puedes resolver en {% data variables.product.product_name %} usando el editor de conflictos. Para obtener más información, consulta "[Resolver un conflicto de fusión en {% data variables.product.prodname_dotcom %}](/articles/resolving-a-merge-conflict-on-github)". -- Para todos los otros tipos de conflictos de fusión, debes resolver el conflicto de fusión en un clon local del repositorio y subir el cambio a tu rama en {% data variables.product.product_name %}. Puedes usar la línea de comandos o una herramienta como [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) para subir el cambio. Para obtener más información, consulta "[Resolver un conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line)". - -Si tienes un conflicto de fusión en la línea de comandos, no puedes subir tus cambios locales a {% data variables.product.product_name %} hasta que resuelvas el conflicto de fusión localmente en tu equipo. Si intentas fusionar ramas en la línea de comandos que tiene un conflicto de fusión, recibirás un mensaje de errror. Para obtener más información, consulta "[Resolver un conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line/)". -```shell -$ git merge BRANCH-NAME -> Auto-merging styleguide.md -> CONFLICT (content): Merge conflict in styleguide.md -> Automatic merge failed; fix conflicts and then commit the result -``` - -### Leer más - -- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" -- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests/)" -- "[Resolver un conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line)" -- "[Resolver un conflicto de fusión en GitHub](/articles/resolving-a-merge-conflict-on-github)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/index.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/index.md deleted file mode 100644 index 9acf8dd2bc..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Abordar conflictos de fusión -intro: 'Si tus cambios tienen conflictos de fusión con la sucursal de base, debes ocuparte de los conflictos de fusión antes de que puedas fusionarlo con tus cambios de solicitud de extracción.' -redirect_from: - - /articles/addressing-merge-conflicts -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /about-merge-conflicts - - /resolving-a-merge-conflict-on-github - - /resolving-a-merge-conflict-using-the-command-line ---- - diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md deleted file mode 100644 index 3bb294ddfb..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Resolving a merge conflict on GitHub -intro: 'You can resolve simple merge conflicts that involve competing line changes on GitHub, using the conflict editor.' -redirect_from: - - /articles/resolving-a-merge-conflict-on-github - - /github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -You can only resolve merge conflicts on {% data variables.product.product_name %} that are caused by competing line changes, such as when people make different changes to the same line of the same file on different branches in your Git repository. For all other types of merge conflicts, you must resolve the conflict locally on the command line. For more information, see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line/)." - -{% if currentVersion != "free-pro-team@latest" %} -If a site administrator disables the merge conflict editor for pull requests between repositories, you cannot use the conflict editor on {% data variables.product.product_name %} and must resolve merge conflicts on the command line. For example, if the merge conflict editor is disabled, you cannot use it on a pull request between a fork and upstream repository. -{% endif %} - -{% warning %} - -{% if currentVersion ver_lt "enterprise-server@2.22" %} -**Warning:** When you resolve a merge conflict on {% data variables.product.product_name %}, the entire [base branch](/github/getting-started-with-github/github-glossary#base-branch) of your pull request is merged into the [head branch](/github/getting-started-with-github/github-glossary#head-branch), even if the head branch is the default branch of your repository or a protected branch. Make sure you really want to commit to this branch. -{% else %} -**Warning:** When you resolve a merge conflict on {% data variables.product.product_name %}, the entire [base branch](/github/getting-started-with-github/github-glossary#base-branch) of your pull request is merged into the [head branch](/github/getting-started-with-github/github-glossary#head-branch). Make sure you really want to commit to this branch. If the head branch is the default branch of your repository, you'll be given the option of creating a new branch to serve as the head branch for your pull request. If the head branch is protected you won't be able to merge your conflict resolution into it, so you'll be prompted to create a new head branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." -{% endif %} - -{% endwarning %} - -{% data reusables.repositories.sidebar-pr %} -1. In the "Pull Requests" list, click the pull request with a merge conflict that you'd like to resolve. -1. Near the bottom of your pull request, click **Resolve conflicts**. -![Resolve merge conflicts button](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png) - - {% tip %} - - **Tip:** If the **Resolve conflicts** button is deactivated, your pull request's merge conflict is too complex to resolve on {% data variables.product.product_name %}{% if currentVersion != "free-pro-team@latest" %} or the site administrator has disabled the conflict editor for pull requests between repositories{% endif %}. You must resolve the merge conflict using an alternative Git client, or by using Git on the command line. For more information see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line)." - - {% endtip %} -{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} - ![View merge conflict example with conflict markers](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png) -1. If you have more than one merge conflict in your file, scroll down to the next set of conflict markers and repeat steps four and five to resolve your merge conflict. -1. Once you've resolved all the conflicts in the file, click **Mark as resolved**. - ![Click mark as resolved button](/assets/images/help/pull_requests/mark-as-resolved-button.png) -1. If you have more than one file with a conflict, select the next file you want to edit on the left side of the page under "conflicting files" and repeat steps four through seven until you've resolved all of your pull request's merge conflicts. - ![Select next conflicting file if applicable](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png) -1. Once you've resolved all your merge conflicts, click **Commit merge**. This merges the entire base branch into your head branch. - ![Resolve merge conflicts button](/assets/images/help/pull_requests/merge-conflict-commit-changes.png){% if currentVersion ver_lt "enterprise-server@2.22" %} -1. If prompted, review the branch that you are committing to. If you want to commit to this branch, click **I understand, update _BRANCH_**. -![Merge conflict confirmation window](/assets/images/help/pull_requests/merge-conflict-confirmation.png){% else %} -1. If prompted, review the branch that you are committing to. - - If the head branch is the default branch of the repository, you can choose either to update this branch with the changes you made to resolve the conflict, or to create a new branch and use this as the head branch of the pull request. - ![Prompt to review the branch that will be updated](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png) - - If you choose to create a new branch, enter a name for the branch. - - If the head branch of your pull request is protected you must create a new branch. You won't get the option to update the protected branch. - - Click **Create branch and update my pull request** or **I understand, continue updating _BRANCH_**. The button text corresponds to the action you are performing. -{% endif %} -1. To merge your pull request, click **Merge pull request**. For more information about other pull request merge options, see "[Merging a pull request](/articles/merging-a-pull-request/)." - -### Further reading - -- "[About pull request merges](/articles/about-pull-request-merges)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md deleted file mode 100644 index 82121f73dc..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -title: Resolver un conflicto de fusión con la línea de comando -intro: Puedes resolver conflictos de fusión con la línea de comando y un editor de texto. -redirect_from: - - /articles/resolving-a-merge-conflict-from-the-command-line/ - - /articles/resolving-a-merge-conflict-using-the-command-line - - /github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Los conflictos de fusión ocurren cuando se hacen cambios contrapuestos en la misma línea de un archivo o cuando una persona edita un archivo y otra persona borra el mismo archivo. Para obtener más información, consulta "[Acerca de los conflictos de fusión](/articles/about-merge-conflicts/)". - -{% tip %} - -**Sugerencia:** Puedes utilizar el editor de conflictos en {% data variables.product.product_name %} para resolver conflictos de fusión de cambios de líneas contrapuestos entre ramas que son parte de una solicitud de extracción. Para obtener más información, consulta "[Resolver un conflicto de fusión en GitHub](/articles/resolving-a-merge-conflict-on-github)". - -{% endtip %} - -### Conflictos de fusión de cambios de líneas contrapuestos - -Para resolver un conflicto de fusión causado por cambios de líneas contrapuestos, debes decidir qué cambios incorporar desde las diferentes ramas de una confirmación nueva. - -Por ejemplo, si usted y otra persona editaron el archivo _styleguide.md_ en las mismas líneas de diferentes ramas del mismo repositorio de Git, recibirás un error de conflicto de fusión cuando trates de fusionar estas ramas. Debes resolver este conflicto de fusión con una confirmación nueva antes de que puedas fusionar estas ramas. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Navega en el repositorio de Git local que tiene el conflicto de fusión. - ```shell - cd REPOSITORY-NAME - ``` -3. Genera una lista de los archivos afectados por el conflicto de fusión. En este ejemplo, el archivo *styleguide.md* tiene un conflicto de fusión. - ```shell - $ git status - > # On branch branch-b - > # You have unmerged paths. - > # (fix conflicts and run "git commit") - > # - > # Unmerged paths: - > # (use "git add ..." to mark resolution) - > # - > # both modified: styleguide.md - > # - > no changes added to commit (use "git add" and/or "git commit -a") - ``` -4. Abre tu editor de texto preferido, como [Atom](https://atom.io/), y navega hasta el archivo que tiene los conflictos de fusión. -5. Para ver el origen de un conflicto de fusión en tu archivo, busca el archivo para el marcador de conflicto `<<<<<<<`. Cuando abras el archivo en tu editor de texto, verás los cambios desde la rama HEAD (encabezado) o base después de la línea `<<<<<<< HEAD`. Luego verás `=======`, que separa tus cambios de los cambios en la otra rama, seguido de `>>>>>>> BRANCH-NAME`. En este ejemplo, una persona escribió "abrir una propuesta" en la rama base o HEAD (encabezado), y otra persona escribió "haz tu pregunta en IRC" en la rama de comparación o `branch-a`. - - ``` -If you have questions, please -<<<<<<< HEAD -open an issue -======= -ask your question in IRC. ->>>>>>> branch-a - ``` -{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %}En este ejemplo, ambos cambios se incorporaron en la fusión final: - - ```shell - Si tienes preguntas, abre una propuesta o consulta en nuestro canal IRC si es más urgente. - ``` -7. Agrega o almacena tus cambios. - ```shell - $ git add . - ``` -8. Confirma tus cambios con un comentario. - ```shell - $ git commit -m "Conflicto de fusión resuelto incorporando ambas sugerencias". - ``` - -Ahora puedes fusionar las ramas en la línea de comando o [subir tus cambios a tu repositorio remoto](/articles/pushing-commits-to-a-remote-repository/) en {% data variables.product.product_name %} y [fusionar tus cambios](/articles/merging-a-pull-request/) en una solicitud de extracción. - -### Conflictos de fusión de archivos eliminados - -Para resolver un conflicto de fusión causado por cambios contrapuestos en un archivo, cuando una persona elimina un archivo en una rama y otra persona edita el mismo archivo, debes decidir si eliminar o conservar el archivo eliminado en una confirmación nueva. - -Por ejemplo, si editaste un archivo, como *README.md*, y otra persona eliminó el mismo archivo en otra rama del mismo repositorio de Git, recibirás un error de conflicto de fusión cuando trates de fusionar estas ramas. Debes resolver este conflicto de fusión con una confirmación nueva antes de que puedas fusionar estas ramas. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Navega en el repositorio de Git local que tiene el conflicto de fusión. - ```shell - cd REPOSITORY-NAME - ``` -2. Genera una lista de los archivos afectados por el conflicto de fusión. En este ejemplo, el archivo *README.md* tiene un conflicto de fusión. - ```shell - $ git status - > # On branch master - > # Your branch and 'origin/master' have diverged, - > # and have 1 and 2 different commits each, respectively. - > # (use "git pull" to merge the remote branch into yours) - > # You have unmerged paths. - > # (fix conflicts and run "git commit") - > # - > # Unmerged paths: - > # (use "git add/rm ..." as appropriate to mark resolution) - > # - > # deleted by us: README.md - > # - > # no changes added to commit (use "git add" and/or "git commit -a") - ``` -3. Abre tu editor de texto preferido, como [Atom](https://atom.io/), y navega hasta el archivo que tiene los conflictos de fusión. -6. Decide si quieres conservar el archivo eliminado. Puede que quieras ver los últimos cambios hechos en el archivo eliminado en tu editor de texto. - - Para volver a agregar el archivo eliminado a tu repositorio: - ```shell - $ git add README.md - ``` - Para eliminar este archivo de tu repositorio: - ```shell - $ git rm README.md - > README.md: needs merge - > rm 'README.md' - ``` -7. Confirma tus cambios con un comentario. - ```shell - $ git commit -m "Resolved merge conflict by keeping README.md file." - > [branch-d 6f89e49] Merge branch 'branch-c' into branch-d - ``` - -Ahora puedes fusionar las ramas en la línea de comando o [subir tus cambios a tu repositorio remoto](/articles/pushing-commits-to-a-remote-repository/) en {% data variables.product.product_name %} y [fusionar tus cambios](/articles/merging-a-pull-request/) en una solicitud de extracción. - -### Leer más - -- "[Acerca de los conflictos de fusión](/articles/about-merge-conflicts)" -- "[Revisar las solicitudes de extracción de forma local](/articles/checking-out-pull-requests-locally/)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md deleted file mode 100644 index 1a76614ca8..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Acerca de las verificaciones de estado -intro: Las verificaciones de estado te permiten saber si tus confirmaciones cumplen con las condiciones establecidas para el repositorio con el que estás colaborando. -redirect_from: - - /articles/about-statuses/ - - /articles/about-status-checks - - /github/collaborating-with-issues-and-pull-requests/about-status-checks -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Las verificaciones de estado se basan en procesos externos, como compilaciones de integración continua, que se ejecutan para cada subida que haces a un repositorio. Puedes ver el estado *pendiente*, *aprobado* o *error* de las verificaciones de estado junto a las confirmaciones individuales en tu solicitud de extracción. - -![Listado de confirmaciones y estados](/assets/images/help/pull_requests/commit-list-statuses.png) - -Cualquier persona con permisos de escritura a un repositorio puede determinar el estado de cualquier comprobación de estado en el repositorio. - -Puedes ver el estado general de la última confirmación para una rama en la página de ramas de tu repositorio o en la lista de solicitudes de extracción de tu repositorio. - -{% data reusables.pull_requests.required-checks-must-pass-to-merge %} - -### Tipos de verificaciones de estado en {% data variables.product.product_name %} - -Hay dos tipos de verificaciones de estado en {% data variables.product.product_name %}: - -- Verificaciones -- Estados - -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_app %}s. - -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](/v3/checks/)" y "[Estados](/v3/repos/statuses/)". - -### Verificaciones - -Cuando se configuran las _verificaciones_ en un repositorio, las solicitudes de extracción tienen una pestaña **Checks** (Verificaciones) en la que puedes ver los resultados detallados de la compilación desde las verificaciones de estado y volver a ejecutar las verificaciones fallidas. - -![Verificaciones de estado dentro de una solicitud de extracción](/assets/images/help/pull_requests/checks.png) - -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) - -Puedes navegar entre los resúmenes de las verificaciones para varias confirmaciones en una solicitud de extracción, usando el menú desplegable de la confirmación en la pestaña **Conversación**. - -![Resúmenes de verificación para diferentes confirmaciones en un menú desplegable](/assets/images/help/pull_requests/checks-summary-for-various-commits.png) - -#### Omitir y solicitar verificaciones para confirmaciones individuales - -Cuando un repositorio se configura para que solicite automáticamente las verificaciones para las subidas, puedes elegir omitir las verificaciones para una confirmación indvidual que subes. Cuando un repositorio _no_ se configura para que solicite automáticamente las verificaciones para las subidas, puedes solicitar verificaciones para una confirmación indvidual que subes. Para obtener más información acerca de estas configuraciones, consulta la sección "[Verificar Suites](/v3/checks/suites/#set-preferences-for-check-suites-on-a-repository)". - -Para omitir o solicitar verificaciones para tu confirmación, agrega una de las siguientes lineas de introducción al final de tu mensaje de confirmación: - -- Para _omitir verificaciones_ para una confirmación, escribe tu mensaje de confirmación y una descripción corta y significativa de tus cambios. Después de la descripción de tu confirmación, en lugar de una comilla de cierre, agrega dos líneas vacías seguidas de `skip-checks: true`: - ```shell - $ git commit -m "Update README. - > - > - skip-checks: true - ``` - - Para _solicitar_ verificaciones para una confirmación, escribe tu mensaje de confirmación y una descripción corta y significativa de tus cambios. Después de la descripción de tu confirmación, en lugar de una comilla de cierre, agrega dos líneas vacías seguidas de `request-checks: true`: - ```shell - $ git commit -m "Refactor usability tests. - > - > - request-checks: true - ``` diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md deleted file mode 100644 index 8fff4e6654..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Collaborating on repositories with code quality features -intro: 'Workflow quality features like statuses, {% if currentVersion != "free-pro-team@latest" %}pre-receive hooks, {% endif %}protected branches, and required status checks help collaborators make contributions that meet conditions set by organization and repository administrators.' -redirect_from: - - /articles/collaborating-on-repositories-with-code-quality-features-enabled/ - - /articles/collaborating-on-repositories-with-code-quality-features -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /about-status-checks - - /working-with-pre-receive-hooks ---- - diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md deleted file mode 100644 index ec8e01f6eb..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Trabajar con ganchos de pre-recepción -intro: Los *ganchos de pre-recepción* hacen cumplir las reglas para las contribuciones antes de que las confirmaciones se puedan subir a un repositorio. -redirect_from: - - /articles/working-with-pre-receive-hooks - - /github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks -versions: - enterprise-server: '*' ---- -Los ganchos de pre-recepción ejecutan pruebas en código que se suben a un repositorio para asegurar que las contribuciones cumplan con las políticas del repositorio o de la organización. Si los contenidos de la confirmación pasan las pruebas, se aceptará que se suban al repositorio. Si los contenidos de la confirmación no pasan las pruebas, no se aceptará que se suban al repositorio. - -Si no se acepta tu subida, verás un mensaje de error que corresponde al gancho de pre-recepción fallido. - -``` -$ git push -Counting objects: 3, done. -Delta compression using up to 4 threads. -Compressing objects: 100% (2/2), done. -Writing objects: 100% (3/3), 916 bytes | 0 bytes/s, done. -Total 3 (delta 0), reused 0 (delta 0) -remote: always_reject.sh: failed with exit status 1 -remote: error: rejecting all pushes -To https://54.204.174.51/hodor/nope.git - ! [remote rejected] master -> master (pre-receive hook declined) -error: failed to push some refs to 'https://54.204.174.51/hodor/nope.git' -``` - -![Mensaje de error para gancho de pre-recepción fallido](/assets/images/help/pull_requests/pre-receive-hook-failed-error.png) - -Tu {% data variables.product.product_name %} administrador del sitio puede crear y eliminar ganchos de pre-recepción para tu organización o repositorio y puede permitirle a los administradores de la organización o del repositorio habilitar o inhabilitar ganchos de pre-recepción. Para obtener más información, consulta "[Usar ganchos de pre-recepción para implementar políticas](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy)." diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md deleted file mode 100644 index 5215cbce9e..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Acerca de las fusiones de las solicitudes de extracción -intro: 'Puedes [fusionar solicitudes de extracción](/articles/merging-a-pull-request) conservando todas las confirmaciones de cambios en una rama de característica, combinando todas las confirmaiones en una única confirmación o cambiando de base confirmaciones individuales desde la rama `head` hacia la rama `base`.' -redirect_from: - - /articles/about-pull-request-merge-squashing/ - - /articles/about-pull-request-merges - - /github/collaborating-with-issues-and-pull-requests/about-pull-request-merges -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.pull_requests.default_merge_option %} - -### Combinar y fusionar las confirmaciones de cambios de tus solicitudes de extracción - -{% data reusables.pull_requests.squash_and_merge_summary %} - -#### Mensaje de fusión para una fusión de combinación - -Cuando combinas y fusionas, {% data variables.product.prodname_dotcom %} genera un mensaje de confirmación que puedes cambiar si así lo deseas. El mensaje predeterminado depende de si la solicitud de extracción contiene varias confirmaciones o solo una. - -| Cantidad de confirmaciones | Resumen | Descripción | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | -| Una confirmación | El título del mensaje de confirmación para la confirmación única, seguido de el número de la solicitud de extracción | El cuerpo de texto del mensaje de la confirmación para la confirmación única | -| Más de una confirmación | El título de la solicitud de extracción, seguido por el número de dicha solicitud | Un listado de los mensajes de confirmación para todas las confirmaciones combinadas, en orden cronológico | - -#### Combinar y fusionar una rama extensa - -Si planeas seguir trabajando en la [rama principal](/github/getting-started-with-github/github-glossary#head-branch) de una solicitud de extracción después de que ésta se fusiona, te recomendamos no combinarla y fusionarla. - -Cuando creas una solicitud de extracción, {% data variables.product.prodname_dotcom %} identifica la confirmación más reciente que se encuentre tanto en la rama principal como en la [rama base](/github/getting-started-with-github/github-glossary#base-branch): la confirmación del ancestro común. Cuando combinas y fusionas la solicitud de extracción, {% data variables.product.prodname_dotcom %} crea una confirmación en la rama base que contiene todos los cambios que realizaste en la rama principal desde la confirmación del ancestro común. - -Ya que esta confirmación se realizó únicamente en la rama base y no en la principal, el ancestro común de las dos ramas permanece sin cambios. Si sigues trabajando en la rama principal, entonces crea una solicitud de extracción nueva entre las dos ramas, la solicitud de extracción incluirá todas las confirmaciones que se hayan realizado desde el ancestro común, incluyendo aquellas que combinaste y fusionaste en la solicitud de extracción previa. Si no hay conflictos, puedes fusionar estas confirmaciones con seguridad. Sin embargo, este flujo de trabajo hace que los conflictos de fusión sean más probables. Si sigues combinando y fusionando las solicitudes de extracción para una rama principal extensa, tendrás que resolver los mismos conflictos repetidamente. - -### Cambiar de base y fusionar las confirmaciones de cambios de tus solicitudes de extracción - -{% data reusables.pull_requests.rebase_and_merge_summary %} - -No es posible cambiar de base y fusionar automáticamente en {% data variables.product.product_location %} cuando: -- La solicitud de extracción tiene conflictos de fusión. -- Cambiar de base las confirmaciones desde la rama base a la rama encabezado conlleva a tener conflictos. -- Cambiar de base las confirmaciones se considera "no seguro", como cuando un cambio de base es posible sin conflictos de fusión, pero produciría un resultado diferente del que produciría una fusión. - -Si aún quieres cambiar de base las confirmaciones, pero no puedes cambiar de base y fusionar automáticamente en {% data variables.product.product_location %}, debes hacer lo siguiente: -- Cambiar de base la rama de tema (o rama de encabezado) hacia la rama base de forma local en la línea de comandos. -- [Resolver cualquier conflicto de fusión en la línea de comandos](/articles/resolving-a-merge-conflict-using-the-command-line/). -- Realizar un empuje forzado de las confirmaciones cambiadas de base a la rama de tema de la solicitud de extracción (o rama de encabezado remota). - -Cualquiera con permisos de escritura en el repositorio, entonces puede [fusionar los cambios](/articles/merging-a-pull-request/) usando el botón Cambiar de base y fusionar en {% data variables.product.product_location %}. - -### Leer más - -- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests/)" -- "[Abordar conflictos de fusión](/articles/addressing-merge-conflicts)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md deleted file mode 100644 index 41c2d23137..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Cerrar una solicitud de extracción -intro: 'Puedes *cerrar* una solicitud de extracción sin [fusionarla en una rama ascendente] (/articles/merging-a-pull-request). Esto puede resultar útil si los cambios propuestos en la rama ya no son necesarios, o si se ha propuesto otra solución en otra rama.' -redirect_from: - - /articles/closing-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/closing-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% tip %} - -**Sugerencia**: Si abriste una solicitud de extracción con la rama base equivocada, en lugar de cerrarla y abrir una nueva, puedes cambiar la rama base. Para obtener más información, consulta "[Cambiar la rama base de una solicuitud de extracción](/articles/changing-the-base-branch-of-a-pull-request)". - -{% endtip %} - -{% data reusables.repositories.sidebar-pr %} -2. En la lista "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas cerrar. -3. En la parte inferior de la solicitud de extracción, debajo del cuadro de comentarios, haz clic en **Close pull request** (Cerrar solicitud de extracción). ![El botón para cerrar las solicitudes de extracción](/assets/images/help/pull_requests/pullrequest-closebutton.png) -4. De forma opcional, [elimina la rama](/articles/deleting-unused-branches). Esto mantiene ordenado el listado de ramas en tu repositorio. diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/index.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/index.md deleted file mode 100644 index 204af42f37..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Incorporar modificaciones desde una solicitud de extracción -intro: 'Puedes proponer modificaciones para tu trabajo en {% data variables.product.product_name %} a través de solicitudes de extracción. Aprende a crear, administrar y fusionar solicitudes de extracción.' -redirect_from: - - /articles/incorporating-changes-from-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /about-pull-request-merges - - /merging-a-pull-request - - /closing-a-pull-request - - /reverting-a-pull-request ---- - diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md deleted file mode 100644 index d1e1153abe..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Fusionar una solicitud de extracción -intro: Fusionar una solicitud de extracción dentro de una rama ascendente cuando el trabajo está completo. Cualquier persona con acceso de escritura al repositorio puede completar la fusión. -redirect_from: - - /articles/merging-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/merging-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Acerca de las fusiones de las solicitudes de extracción - -En una solicitud de extracción, propones que los cambios que hayas hecho en una rama de encabezado se fusionen en una rama base. {% data reusables.pull_requests.about-protected-branches %}Sin embargo, puede que haya restricciones sobre cuándo puedes fusionar una solicitud de extracción en una rama específica. Por ejemplo, puede que solo puedas fusionar una solicitud de extracción en la rama predeterminada si están pasando las verificaciones de estado requeridas. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)". - -Si la solicitud de extracción tiene conflictos de fusión, o si deseas probar los cambios antes de la fusión, puedes [revisar la solicitud de extracción de forma local](/articles/checking-out-pull-requests-locally) y fusionarla utilizando la línea de comando. - -You can't merge a draft pull request. Para obtener más información acerca de las solicitudes de extracción en borrador "[Acerca de las solicitudes de extracción](/articles/about-pull-requests#draft-pull-requests)". - -{% data reusables.pull_requests.automatically-delete-branches %} - -Si decides que no deseas que los cambios en una rama de tema se fusionen con la rama ascendente, puedes [cerrar la solicitud de extracción](/articles/closing-a-pull-request) sin fusionar. - -### Fusionar una solicitud de extracción en {% data variables.product.prodname_dotcom %} - -{% data reusables.repositories.sidebar-pr %} -2. En la lista "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas fusionar. -3. Según las opciones de fusión habilitadas para tu repositorio, puedes: - - [Fusionar todas las confirmaciones de cambios dentro de la rama base](/articles/about-pull-request-merges/) al hacer clic en **Merge pull request (Fusionar solicitud de extracción)**. Si no se muestra la opción **Merge pull request** (Fusionar solicitud de extracción), haz clic en el menú desplegable de fusiones y selecciona **Create a merge commit** (Crear una confirmación de fusión). ![merge-pull-request-button (botón para fusionar solicitud de extracción)](/assets/images/help/pull_requests/pullrequest-mergebutton.png) - - [Combinar las confirmaciones de cambios en una sola confirmación](/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits) haciendo clic en el menú desplegable, luego selecciona **Squash and merge** (Combinar y fusionar) y haz clic en el botón **Squash and merge** (Combinar y fusionar). ![click-squash-and-merge-button (hacer clic en el botón para combinar y fusionar)](/assets/images/help/pull_requests/select-squash-and-merge-from-drop-down-menu.png) - - [Rebasar las confirmaciones por separado sobre la rama base](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits) haciendo clic en el menú desplegable de fusión, luego selecciona **Rebase and merge** (Rebasar y fusionar) y haz clic en el botón **Rebase and merge** (Rebasar y fusionar). ![select-rebase-and-merge-from-drop-down-menu (seleccionar del menú desplegable para rebasar y fusionar)](/assets/images/help/pull_requests/select-rebase-and-merge-from-drop-down-menu.png) - - {% note %} - - **Nota:** Rebasar y fusionar siempre actualizará la información de la persona que confirma el cambio y creará una nueva SHA de confirmación de cambio. Para obtener más información, consulta "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges#rebase-and-merge-your-pull-request-commits)." - - {% endnote %} -4. Si se solicita, escribe un mensaje de confirmación de cambios, o acepta el mensaje predeterminado. - - {% data reusables.pull_requests.default-commit-message-squash-merge %} - ![Campo para mensaje de confirmación](/assets/images/help/pull_requests/merge_box/pullrequest-commitmessage.png) - -{% data reusables.files.choose-commit-email %} - -6. Haz clic en **Confirm merge** (Confirmar fusión), **Confirm squash and merge** (Confirmar combinación y fusión) o **Confirm rebase and merge** (Confirmar rebase y fusión). -6. De forma opcional, [elimina la rama](/articles/deleting-unused-branches). Esto mantiene ordenado el listado de ramas en tu repositorio. - - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}El repositorio podría configurarse para que la rama de encabezado para una solicitud de extracción se borre automáticamente cuando fusionas la solicitud de extracción. Para obtener más información, consulta la sección "[Administrar el borrado automático de ramas](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)".{% endif %} - - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - {% note %} - - **Nota:** {% data reusables.pull_requests.retargeted-on-branch-deletion %} Para obtener más información, consulta la sección "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)". - - {% endnote %} - {% endif %} - -Las solicitudes de extracción se fusionan utilizando [la opción `--no-ff`](https://git-scm.com/docs/git-merge#_fast_forward_merge), excepto [las solicitudes de extracción con confirmaciones de rebase y combinación](/articles/about-pull-request-merges), que se fusionan utilizando la opción de avance rápido. - -{% data reusables.pull_requests.close-issues-using-keywords %} - -### Leer más - -- "[Revertir una solicitud de extracción](/articles/reverting-a-pull-request)" -- "[Sincronizar tu rama](/desktop/guides/contributing-to-projects/syncing-your-branch/)" utilizando {% data variables.product.prodname_desktop %} -- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" -- "[Abordar conflictos de fusión](/articles/addressing-merge-conflicts)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md deleted file mode 100644 index fd4221cd9d..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Revertir una solicitud de extracción -intro: Puedes revertir una solicitud de extracción después de que se haya fusionado con la rama ascendente. -redirect_from: - - /articles/reverting-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Acerca de revertir una solicitud de extraccción - -Revertir una solicitud de extracción en {% data variables.product.product_name %} genera una nueva solicitud de extracción que contiene una reversión de la confirmación de fusión de la solicitud de extracción fusionada original. - -### Revertir una solicitud de extracción - -{% note %} - -**Nota:** Podrías tener que revertir las confirmaciones individuales en tu solicitud de extracción si cualquiera de los siguientes casos aplica. - -- Revertir la solicitud de extracción provoca conflictos de fusión -- La solicitud de extracción original no se fusionó originalmente en {% data variables.product.product_name %}. Por ejemplo, alguien pudo haber fusionado la solicitud de extracción utilizando una fusión adelantada en la línea de comandos. - -Para obtener más información acerca de utilizar Git para revertir las confirmaciones individuales manualmente, consulta la sección [Revertir con Git](https://git-scm.com/docs/git-revert.html) en la documentación de Git. - -{% endnote %} - -{% data reusables.repositories.sidebar-pr %} -2. En la lista de "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que quieras revertir. -3. Cerca de la parte de abajo de la solicitud de extracción, haz clic en **Revert** (Revertir). ![Enlace Revert pull request (Revertir solicitud de extracción)](/assets/images/help/pull_requests/revert-pull-request-link.png) -4. Fusionar la solicitud de extracción resultante. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)". diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/index.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/index.md deleted file mode 100644 index c6c8b4d212..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/index.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Colaborar con propuestas y solicitudes de extracción -intro: 'Usa el flujo {% data variables.product.prodname_dotcom %} para hacer el seguimiento y debatir los cambios en las propuestas, luego propone y revisa los cambios en las solicitudes de extracción.' -redirect_from: - - /categories/63/articles/ - - /categories/collaborating/ - - /categories/collaborating-on-projects-using-pull-requests/ - - /categories/collaborating-on-projects-using-issues-and-pull-requests/ - - /categories/collaborating-with-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /overview - - /working-with-forks - - /collaborating-on-repositories-with-code-quality-features - - /proposing-changes-to-your-work-with-pull-requests - - /addressing-merge-conflicts - - /reviewing-changes-in-pull-requests - - /incorporating-changes-from-a-pull-request ---- -### Índice - - - - - - - - diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/about-collaborative-development-models.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/about-collaborative-development-models.md deleted file mode 100644 index d20ff94e68..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/about-collaborative-development-models.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Acerca de los modelos de desarrollo colaborativo -intro: El modo en que usas las solicitudes de extracción depende del tipo de modelo de desarrollo que uses en tu proyecto. -redirect_from: - - /articles/types-of-collaborative-development-models/ - - /articles/about-collaborative-development-models - - /github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Hay dos tipos principales de modelos de desarrollo con los cuales usar las solicitudes de extracción. En el *modelo de bifurcación y extracción*, cualquiera puede bifurcar un repositorio existente y subir los cambios a su bifurcación personal. No necesitas permiso del repositorio fuente para subir información a una bifurcación que sea propiedad del usuario. El mantenedor del proyecto puede extraer los cambios hacia el repositorio de origen. Cuando abres una solicitud de extracción que proponga cambios desde la bifurcación que es propiedad de tu usuario para ramificar en el repositorio fuente (ascendente), puedes permitir que cualquiera con acceso de escritura en éste haga cambios en dicha solicitud. Este modelo es muy usado con los proyectos de código abierto, ya que reduce la cantidad de fricción para los colaboradores nuevos y le permite a las persona trabajar de forma independiente sin una coordinación inicial. - -{% tip %} - -**Sugerencia:** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %} - -{% endtip %} - -En el *modelo de repositorio compartido*, se le otorga a los colaboradores acceso de escritura a un único repositorio compartido y las ramas de tema son creadas cuando es necesario hacer cambios. Las solicitudes de extracción son útiles en este modelo ya que inician la revisión de código y el debate general acerca de un conjunto de cambios antes de que los mismos sean fusionados en la rama de desarrollo principal. Este modelo es más frecuente con las organizaciones y los equipos pequeños que colaboran en proyectos privados. - -### Leer más - -- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" -- "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" -- "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/about-conversations-on-github.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/about-conversations-on-github.md deleted file mode 100644 index 12d5e38984..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/about-conversations-on-github.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Acerca de las conversaciones en GitHub -intro: 'Puedes debatir cambios y proyectos específicos, así como objetivos de equipos o proyectos más amplios, usando diferentes tipos de debates en {% data variables.product.product_name %}.' -redirect_from: - - /articles/about-discussions-in-issues-and-pull-requests/ - - /articles/about-conversations-on-github - - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Debates en {% data variables.product.product_name %} - -Puedes crear y participar de propuestas, solicitudes de extracción y debates de equipos, dependiendo del tipo de conversación que quieras tener. - -Las propuestas son útiles para debatir detalles específicos de un proyecto como registros de errores y mejoras planificadas. Para obtener más información, consulta "[Acerca de las propuestas](/articles/about-issues)". Las solicitudes de extracción te permiten comentar directamente en los cambios propuestos. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" y "[Comentar en una solicitud de extracción](/articles/commenting-on-a-pull-request)". - -{% data reusables.organizations.team-discussions-purpose %} Para obtener más información, consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)". - -### Reaccionar a las ideas en los comentarios - -Puedes mostrar tu apoyo o tu desacuerdo sobre una idea en una conversación. Cuando agregas una reacción a un comentario o al cuerpo de un debate de equipo, informe de problemas o solicitud de extracción, las personas suscritas a la conversación no recibirán una notificación. Para obtener más información acerca de las suscripciones, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Suscribirse y desuscribirse de las notificaciones](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}". - -![Ejemplo de una propuesta con reacciones](/assets/images/help/repository/issue-reactions.png) - -{% if currentVersion == "free-pro-team@latest" %} - -{% tip %} - -**Sugerencia:** También puedes agregar reacciones usando tu dispositivo móvil. - -{% endtip %} - -{% endif %} -### Seguir las pautas de contribución - -Antes de abrir una propuesta o solicitud de extracción, comprueba si el repositorio tiene pautas de contribución. El archivo *CONTRIBUTING.md* incluye información acerca de cómo el mantenedor del repositorio quisiera que aportes ideas al proyecto. - -Al igual que las pautas de contribución, el mantenedor del repositorio puede haber incluido una plantilla para información para incluir en una propuesta o solicitud de extracción. Completar las indicaciones desde la plantilla puede ayudarte a obtener una mejor respuesta de los mantenedores. - -### Leer más - -- "[Configurar tu proyecto para contribuciones positivas](/articles/setting-up-your-project-for-healthy-contributions)" -- "[Utilizar plantillas para fomentar el informe de problemas útil y las solicitudes de extracción](/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests)" -- "[Moderar comentarios y conversaciones](/articles/moderating-comments-and-conversations)" -- "[Escribir en {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/github-flow.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/github-flow.md deleted file mode 100644 index e7bd70a611..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/github-flow.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Flujo de GitHub -intro: 'En GitHub, utilizamos nuestros productos todos los días y hemos desarrollado un flujo de trabajo para colaborar en proyectos. Para hacer que funcione para equipos, independientemente de su tamaño o conocimiento técnico, nos aseguramos de que cada paso de nuestro flujo de trabajo se pueda completar dentro de la interfaz con base en la web.' -redirect_from: - - /articles/creating-and-editing-files-in-your-repository/ - - /articles/github-flow-in-the-browser/ - - /articles/github-flow - - /github/collaborating-with-issues-and-pull-requests/github-flow -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Seguir el flujo de GitHub - -1. [Crea una rama](/articles/creating-and-deleting-branches-within-your-repository) de un repositorio. -2. [Crea](/articles/creating-new-files), [edita](/articles/editing-files), [renombra](/articles/renaming-a-file), [mueve](/articles/moving-a-file-to-a-new-location) o [elimina](/articles/deleting-files) archivos. -3. [Envía una solicitud de extracción](/articles/creating-a-pull-request) desde tu rama con tus modificaciones propuestas para iniciar un debate. -4. Realiza modificaciones en tu rama, según sea necesario. Tu solicitud de extracción se actualizará de manera automática. -5. [Fusiona la solicitud de extracción](/articles/merging-a-pull-request) una vez que la rama esté lista para ser fusionada. -6. [Organiza](/articles/deleting-unused-branches) tus ramas utilizando el botón de eliminación de la solicitud de extracción o en la página de ramas. - -### Leer más - -- La guía ilustrada para "[Comprender el flujo de GitHub](https://guides.github.com/introduction/flow/)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/index.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/index.md deleted file mode 100644 index 26ca43625b..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/overview/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Resumen -intro: 'Aprende sobre el flujo de {% data variables.product.prodname_dotcom %} y las formas diferentes para debatir y colaborar en tus proyectos.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /github-flow - - /about-collaborative-development-models - - /about-conversations-on-github ---- - diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md deleted file mode 100644 index 6d5c6280e7..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Acerca de las ramas -intro: Usa una rama para identificar tareas de desarrollo sin afectar otras ramas en el repositorio. Cada repositorio tiene una rama por defecto y puede tener muchas otras ramas. Puedes fusionar una rama en otra rama usando una solicitud de extracción. -redirect_from: - - /articles/working-with-protected-branches/ - - /articles/about-branches - - /github/collaborating-with-issues-and-pull-requests/about-branches -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Introducción a las ramas - -Las ramas te permiten desarrollar características, corregir errores, o experimentar con seguridad las ideas nuevas en un área contenida de tu repositorio. - -Siempre puedes crear una rama a partir de otra rama existente. Habitualmente, puedes crear una rama nueva desde la rama predeterminada de tu repositorio. Podrás entonces trabajar en esta rama nueva aislado de los cambios que otras personas hacen al repositorio. A la rama que creas para construir una característica se le conoce como rama de característica o rama de tema. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)". - -También puedes usar una rama para publicar un sitio {% data variables.product.prodname_pages %}. Para obtener más información, consulta "[¿Qué son las Páginas de {% data variables.product.prodname_dotcom %}?](/articles/what-is-github-pages)" - -Debes tener acceso de escritura para un repositorio para crear una rama, abrir una solicitud de extracción o eliminar y restablecer ramas en una solicitud de extracción. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.product_name %}](/articles/access-permissions-on-github)". - -### Acerca de la rama predeterminada - -{% data reusables.branches.new-repo-default-branch %} La rama predeterminada es la rama que {% data variables.product.prodname_dotcom %} muestra cuando alguien visita tu repositorio. La rama predeterminada es también la rama inicial que Git verifica localmente cuando alguien clona el repositorio. {% data reusables.branches.default-branch-automatically-base-branch %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - -Predeterminadamente, el nombre de dicha rama es `master`, pero puedes configurar el nombre a cualquiera que haga más sentido para tu flujo de trabajo. Para obtener más información acerca del nombre de la rama predeterminada, consulta la sección "[Administrar la rama predeterminada para tus repositorios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)". - -{% endif %} - -{% data reusables.branches.set-default-branch %} - -### Trabajando con las ramas - -Una vez que estés satisfecho con tu trabajo, puedes abrir una solicitud de extracción para fusionar los cambios en la rama actual (la rama de *encabezado*) en otra rama (la rama *base*). Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." - -Después de que se ha fusionado o cerrado la solicitud de extracción, puedes borrar la rama de encabezado, dado que ésta ya no se requerirá. Debes tener acceso de escritura en el repositorio para borrar las ramas. No puedes borrar ramas que estén directamente asociadas con solicitudes de extracción abiertas. Para obtener más información, consulta la sección "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)" - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.pull_requests.retargeted-on-branch-deletion %} -Los siguientes diagramas son un ejemplo de esto. - - Aquí alguien creó una rama llamada `feature1` desde la rama `master`, y desde entonces, has creado una rama llamada `feature2` desde `feature1`. Hay solicitudes de extracción abiertas para ambas ramas. Las flechas indican la rama base actual para cada solicitud de extracción. En este punto, `feature1` es la rama base para `feature2`. Si la solicitud de extracción para `feature2` se fusiona ahora, la rama `feature2` se fusionará en `feature1`. - - ![merge-pull-request-button (botón para fusionar solicitud de extracción)](/assets/images/help/branches/pr-retargeting-diagram1.png) - -En el siguiente diagrama, alguien fusionó la solicitud de extracción para `feature1` en la rama `master`, u borraron la rama `feature1`. Como resultado, {% data variables.product.prodname_dotcom %} ha redireccionado automáticamente la solicitud de extracción para `feature2` para que su rama base sea ahora `master`. - - ![merge-pull-request-button (botón para fusionar solicitud de extracción)](/assets/images/help/branches/pr-retargeting-diagram2.png) - -Ahora cuando fusiones la solicitud de extracción `feature2`, ésta se fusionará con la rama `master`. -{% endif %} - -### Trabajar con ramas protegidas - -Los administradores de un repositorio pueden activar las protecciones en una rama. Si estás trabajando en una rama que está protegida, no podrás eliminar ni hacer un empuje forzado a la rama. Los administradores de un repositorio además pueden activar varios parámetros de rama protegida para implementar varios flujos de trabajo antes de que se pueda fusionar una rama. - -{% note %} - -**Nota:** Si eres administrador de un repositorio, puedes fusionar las solicitudes de extracción en ramas con las protecciones de rama activadas incluso si la solicitud de extracción no cumple con los requisitos, a menos que las protecciones de rama hayan sido configuradas con "Incluir administradores". - -{% endnote %} - -Para ver si tu solicitud de extracción se puede fusionar, mira en la casilla de fusión en la parte inferior de la pestaña **Conversación** de la solicitud de extracción. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". - -Cuando una rama está protegida: - -- No podrás eliminar ni hacer un empuje forzado a la rama. -- Si las verificaciones de estado requeridas están activadas en la rama, no podrás fusionar cambios en la rama hasta que todas las pruebas de integración continua (CI) requeridas estén aprobadas. Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/articles/about-status-checks)". -- Si las revisiones de solicitud de extracción requeridas están activadas en la rama, no podrás fusionar cambios en la rama hasta que se hayan cumplido todos los requisitos en la política de revisión de solicitud de extracción. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)". -- Si la revisión requerida de un propietario del código está activada en una rama y una solicitud de extracción modifica un código que tiene un propietario, un propietario del código debe aprobar la solicitud de extracción antes de que se pueda fusionar. Para obtener más información, consulta "[Acerca de los propietarios del código](/articles/about-code-owners)." -- Si la firma de confirmación requerida está activada en una rama, no podrás subir ninguna confirmación de cambios a la rama que no esté firmada ni verificada. Para obtener más información, consulta las secciones "[Acerca de la verificación de firma en las confirmaciones](/articles/about-commit-signature-verification)" y "[Acerca de las firmas requeridas para las confirmaciones](/articles/about-required-commit-signing)".{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -- Si utilizas el editor de conflictos de {% data variables.product.prodname_dotcom %} para arreglar los conflictos en una solicitud de extracción que creaste desde una rama protegida, {% data variables.product.prodname_dotcom %} te ayuda a crear una rama alterna para esta solicitud, para que la resolución que quieras dar a los conflictos pueda fusionarse. Para obtener más información, consulta la sección "[Resolver un conflicto de fusión en {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github)".{% endif %} - -### Leer más - -- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" -- "[Rama](/articles/github-glossary/#branch)" en el glosario {% data variables.product.prodname_dotcom %} -- "[Ramas en resumen](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell)" en la documentación de Git diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md deleted file mode 100644 index be91eea595..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Acerca de comparar ramas en solicitudes de extracción -intro: Las solicitudes de extracción muestran las diferencias para comparar los cambios que haz hecho en tu rama de tema respecto a la rama en la cual quieres fusionar tus cambios. -redirect_from: - - /articles/about-comparing-branches-in-pull-requests - - /github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% note %} - -**Nota:** Cuando creas tu solicitud de extracción, puedes modificar la rama base frente a la cual estás comparando tus cambios. Para obtener más información, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)". - -{% endnote %} - -Puedes ver los cambios propuestos en una solicitud de extracción en la pestaña Archivos modificados. - -![Pestaña Archivos modificados de la solicitud de extracción](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png) - -En lugar de ver las confirmaciones de cambios, puedes ver los cambios propuestos ya que aparecerán en los archivos una vez que se fusiona la solicitud de extracción. Los archivos aparecen en orden alfabético dentro de la pestaña Archivos modificados. Las adiciones a los archivos aparecen en verde y están precedidas por un signo `+`, mientras que el contenido que ha sido eliminado aparece en rojo y está precedido por un signo `-`. - -### Opciones de diferentes vistas - -{% tip %} - -**Sugerencia:** Si te está resultando difícil comprender el contexto de un cambio, puedes hacer clic en **View** (Ver) en la pestaña Files changed (Archivos modificados) para ver el archivo completo con los cambios propuestos. - -{% endtip %} - -Tienes varias opciones para ver una diferencia: -- La vista unificada muestra el contenido actualizado y el existente en conjunto en una vista lineal. -- La vista en dos paneles muestra el contenido viejo de un lado y el contenido nuevo del otro. -- La vista diferencia rica muestra una previsualización de cómo se verán los cambios una vez que se fusione la solicitud de extracción. -- La vista de origen muestra los cambios en el origen sin el formato de la vista diferencia rica. - -También puedes elegir ignorar los cambios de espacio en blanco para obtener una vista más precisa de los cambios sustanciales en una solicitud de extracción. - -![Menú Opciones de visualización de diferencias](/assets/images/help/pull_requests/diff-settings-menu.png) - -Para simplificar los cambios de revisión en una solicitud de extracción grande, puedes filtrar las diferencias para que solo se muestren los tipos{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} de archivos seleccionados, se muestren los archivos de los que eres CODEOWNER, se oculten los archivos que ya has visto{% endif %} o se oculten los archivos eliminados. Para obtener más información, consulta "[Filtrar archivos en una solicitud de extracción por tipo de archivo](/articles/filtering-files-in-a-pull-request)". - - ![Menú desplegable Filtro de archivo](/assets/images/help/pull_requests/file-filter-menu.png) - -### Comparaciones de diferencias de Git de tres puntos y de dos puntos - -Por defecto, las solicitudes de extracción en {% data variables.product.prodname_dotcom %} muestran una diferencia de tres puntos o una comparación entre la versión más reciente de la rama de tema y la confirmación donde la rama de tema fue sincronizada por última vez con la rama base. - -Para ver dos referencias confirmables en una comparación de diferencia de dos puntos en {% data variables.product.prodname_dotcom %}, puedes editar la URL de la página "Comparar cambios" de tu repositorio. Para obtener más información, consulta el [Glosario de Git para "confirmable"](https://git-scm.com/docs/gitglossary#gitglossary-aiddefcommit-ishacommit-ishalsocommittish) del sitio del libro _Pro Git_. - -{% data reusables.repositories.two-dot-diff-comparison-example-urls %} - -Una diferenciación de dos puntos compara dos referencias confirmables de Git, como SHA u OID (ID de objeto), directamente entre sí. En {% data variables.product.prodname_dotcom %}, las referencias confirmables de Git en una comparación de diferenciación de dos puntos se deben subir al mismo repositorio o a sus bifurcaciones. - -Si quieres simular una diferenciación de dos puntos en una solicitud de extracción y ver una comparación entre las versiones más recientes de cada rama, puedes fusionar la rama base en tu rama de tema, que actualiza el último antepasado común entre tus ramas. - -Para obtener más información acerca de los comandos de Git para comparar cambios, consulta "[Opciones de diferencias de Git](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)" del sitio del libro _Pro Git_. - -### No se mostrarán las diferencias de motivos -- Has excedido el límite total de archivos o de ciertos tipos de archivos. Para obtener más información, consulta "[Límites para ver el contenido y las diferencias en un repositorio](/articles/limits-for-viewing-content-and-diffs-in-a-repository/#diff-limits)". -- Tus archivos coinciden con una regla en el archivo *.gitattributes* del repositorio para bloquear ese archivo de mostrarse por defecto. Para obtener más información, consulta "[Personalizar cómo aparecen los archivos modificados en GitHub](/articles/customizing-how-changed-files-appear-on-github)". - -### Leer más - -- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" -- "[Acerca de las bifurcaciones](/articles/about-forks)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md deleted file mode 100644 index 28ac8401d9..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Acerca de las solicitudes de extracción -intro: 'Las solicitudes de extracción te permiten comentarle a otros acerca de los cambios que has subido a una rama en un repositorio en {% data variables.product.product_name %}. Una vez que se abre una solicitud de extracción, puedes debatir y revisar los posibles cambios con los colaboradores y agregar confirmaciones de seguimientos antes de que tus cambios se fusionen en la rama base.' -redirect_from: - - /articles/using-pull-requests/ - - /articles/about-pull-requests - - /github/collaborating-with-issues-and-pull-requests/about-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Acerca de las solicitudes de extracción - -{% note %} - -**Nota:** Cuando trabajas con solicitudes de extracción, ten lo siguiente en cuenta: -* Si estás trabajando en el [modelo de repositorio compartido](/articles/about-collaborative-development-models), te recomendamos que uses una rama de tema para tu solicitud de extracción. Si bien puedes enviar solicitudes de extracción desde cualquier rama o confirmación, con una rama de tema puedes subir confirmaciones de seguimiento para actualizar tus cambios propuestos. -* Cuando subas confirmaciones a una solicitud de extracción, no realices un empuje forzado. El empuje forzado puede dañar tu solicitud de extracción. - -{% endnote %} - -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)". - -Una vez que has creado una solicitud de extracción, puedes subir confirmaciones desde tu rama de tema para agregarlas a tu solicitud de extracción existente. Estas confirmaciones aparecerán en orden cronológico dentro de tu solicitud de extracción y los cambios serán visibles en la pestaña "Archivos modificados". - -Otros colaboradores pueden revisar tus cambios propuestos, agregar comentarios de revisión, contribuir con el debate sobre la solicitud de extracción e incluso agregar confirmaciones a la solicitud de extracción. - -{% if currentVersion == "free-pro-team@latest" %} -You can see information about the branch's current deployment status and past deployment activity on the "Conversation" tab. Para obtener más información, consulta "[Ver la actividad de implementación de un repositorio](/articles/viewing-deployment-activity-for-your-repository)". -{% endif %} - -Una vez que estás conforme con los cambios propuestos, puedes fusionar la solicitud de extracción. Si estás trabajando en un modelo de repositorio compartido, creas una solicitud de extracción y tú o alguien más fusionará tus cambios desde tu rama de característica en la rama base que especificaste en tu solicitud de extracción. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)". - -{% data reusables.pull_requests.required-checks-must-pass-to-merge %} - -{% data reusables.pull_requests.close-issues-using-keywords %} - -{% tip %} - -**Sugerencias:** -- Para alternar entre expandir y contraer todos los comentarios de revisión desactualizados en una solicitud de extracción, presiona opciónAltAlty da clic en **Mostrar desactualizados** u **Ocultar desactualizados**. Para conocer más atajos del teclado, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/)". -- Puedes combinar confirmaciones cuando fusionas una solicitud de extracción para obtener una visión optimizada de los cambios. Para obtener más información, consulta "[Acerca de las fusiones de las solicitudes de extracción](/articles/about-pull-request-merges)". - -{% endtip %} - -Puedes visitar tu tablero para encontrar de forma rápida los enlaces a las solicitudes de extracción recientemente actualizadas en las que estás trabajando o estás suscripto. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". - -### Solicitudes de extracción en borrador - -{% data reusables.gated-features.draft-prs %} - -Cuando creas una solicitud de extracción, puedes elegir crear una solicitud de extracción que está lista para revisión o una solicitud de extracción en borrador. Las solicitudes de extracción en borrador no se pueden fusionar y no se les solicita automáticamentes a los propietarios del código que revisen las solicitudes de extracción en borrador. Para obtener más información acerca de la creación de una solicitud de extracción en borrador, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request)" y "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)". - -{% data reusables.pull_requests.mark-ready-review %} Puedes convertir una solicitud de extracción en borrador cuando lo desees. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/articles/changing-the-stage-of-a-pull-request)". - -### Leer más - -- "[Solicitud de extracción](/articles/github-glossary/#pull-request)" en el glosario de {% data variables.product.prodname_dotcom %} -- "[Acerca de las ramas](/articles/about-branches)" -- "[Comentar sobre una solicitud de extracción](/articles/commenting-on-a-pull-request)" -- "[Fusionar una solicitud de extracción](/articles/merging-a-pull-request)" -- "[Cerrar una solicitud de extracción](/articles/closing-a-pull-request)" -- "[Eliminar ramas no utilizadas](/articles/deleting-unused-branches)" -- "[Acerca de las fusiones de solicitudes de extracción](/articles/about-pull-request-merges/)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md deleted file mode 100644 index 3ce34b95fe..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Cambiar la rama base de una solicitud de extracción -intro: 'Una vez abierta una solicitud de extracción, puedes cambiar la rama base para comparar los cambios en la solicitud de extracción frente a una rama diferente.' -redirect_from: - - /articles/changing-the-base-branch-of-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% warning %} - -**Advertencia**: Cuando cambias la rama base de tu solicitud de extracción, algunas confirmaciones se eliminarán de la cronología. La revisión de los comentarios también puede estar desactualizada, ya que es posible que la línea del código a la que el comentario hizo referencia no sea parte de los cambios en la solicitud de extracción. - -{% endwarning %} - -{% data reusables.repositories.sidebar-pr %} -2. En la lista "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas modificar. -3. Junto al título de la solicitud de extracción, haz clic en **Edit** (Editar). ![Botón Pull request edit (Edición de solicitud de extracción)](/assets/images/help/pull_requests/pull-request-edit.png) -4. En el menú desplegable de la rama base, seleccione aquella contra la que desea [comparar cambios](/github/committing-changes-to-your-project/comparing-commits#comparing-branches). ![Menú desplegable de la rama base ](/assets/images/help/pull_requests/pull-request-edit-base-branch.png) -5. Lee la información sobre cómo cambiar la rama base y haz clic en **Change base** (Cambiar base). ![Botón de confirmación para cambiar la rama base ](/assets/images/help/pull_requests/pull-request-base-branch-confirm.png) - -### Leer más - -- "[Crear una solicitud de extracción](/articles/creating-a-pull-request)" -- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" -- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md deleted file mode 100644 index b266343639..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Cambiar la etapa de una solicitud de extracción -intro: 'Puedes marcar un borrador de solicitud de extracción como listo para revisión {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} o convertir la solicitud en borrador{% endif %}.' -permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request. -product: '{% data reusables.gated-features.draft-prs %}' -redirect_from: - - /articles/changing-the-stage-of-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Marcar una solicitud como lista para revisión - -{% data reusables.pull_requests.mark-ready-review %} - -{% data reusables.repositories.sidebar-pr %} -2. En la lista "Pull requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas marcar como disponibles para revisión. -3. En la caja de fusión, da clic en **Listo para revisión**. ![Botón Ready for review (Disponible para revisión)](/assets/images/help/pull_requests/ready-for-review-button.png) - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} - -### Convertir una solicitud de extracción en borrador - -Puedes convertir una solicitud de extracción en borrador en cualquier momento. Por ejemplo, si accidentalmente abriste una solicitud de extracción en vez de un borrador, o si recibiste retroalimentación en tu solicitud de extracción, la cual necesitas atender, puedes convertirla en borrador para indicar que requiere más cambios. Nadie puede fusionar la solicitud de extracción hasta que la marques nuevamente como lista para revisión. Las personas que ya se han suscrito a las notificaciones de la solicitud de extracción no podrán darse de baja de éstas cuando la conviertas en borrador. - -{% data reusables.repositories.sidebar-pr %} -2. En las lista de "Solicitudes de extracción", da clic en aquella que quieras convertir en borrador. -3. En la barra lateral derecha, debajo de "Revisores", da clic en **Convertir en borrador**. ![Enlace para convertir en borrador](/assets/images/help/pull_requests/convert-to-draft-link.png) -4. Da clic en **Convertir en borrador**. ![Confirmación de conversión a borrador](/assets/images/help/pull_requests/convert-to-draft-dialog.png) - -{% endif %} - -### Leer más - -- "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md deleted file mode 100644 index 33e7379f39..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Confirmar cambios a una rama de solicitud de extracción desde una bifurcación -intro: Puedes confirmar cambios en una rama de solicitud de extracción que se creó desde una bifurcación de tu repositorio con permiso del creador de la solicitud de extracción. -redirect_from: - - /articles/committing-changes-to-a-pull-request-branch-created-from-a-fork - - /github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Solo puedes realizar confirmaciones en las ramas de la solicitud de extracción que: -- están abiertas en un repositorio al que tienes acceso de escritura y que se crearon a partir de una bifurcación de ese repositorio -- se encuentren en una bifurcación propiedad del usuario -- tienes permiso otorgado por parte del creador de la solicitud de extracción -- no tengan [restricciones de rama](/articles/about-branch-restrictions) que te impidan la confirmación - -Solo el usuario que creó la solicitud de extracción puede darte permiso para subir confirmaciones de cambios en la bifurcación de la cual es dueño. Para más información, consulta "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" - -{% note %} - -**Nota:** También puedes realizar confirmaciones a una rama de solicitud de extracción desde una bifurcación de tu repositorio a través de {% data variables.product.product_location %} al crear tu propia copia (o bifurcación) de la bifurcación de tu repositorio y confirmar los cambios en la misma rama de encabezado en la que se crearon los cambios de la solicitud de extracción original. Para conocer algunos lineamientos generales, consulta "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)". - -{% endnote %} - -1. En {% data variables.product.product_name %}, desplázate hasta la página principal de la bifurcación (o copia de tu repositorio) donde se creó la rama de la solicitud de extracción. -{% data reusables.repositories.copy-clone-url %} -{% data reusables.command_line.open_the_multi_os_terminal %} - {% tip %} - - **Sugerencia:** Si prefieres clonar la bifurcación mediante {% data variables.product.prodname_desktop %}, consulta "[Clonar un repositorio en {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)". - - {% endtip %} -4. Cambia el directorio de trabajo actual a la ubicación donde deseas descargar el directorio clonado. - ```shell - $ cd open-source-projects - ``` -5. Escribe `git clone`, y luego pega la URL que copiaste en el Paso 3. - ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY - ``` -6. Presiona **Enter** (Intro). Se creará tu clon local. - ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY - > Cloning into `FORK-OF-THE-REPOSITORY`... - > remote: Counting objects: 10, done. - > remote: Compressing objects: 100% (8/8), done. - > remove: Total 10 (delta 1), reused 10 (delta 1) - > Unpacking objects: 100% (10/10), done. - ``` - {% tip %} - - **Sugerencia:** El mensaje de error "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" significa que tu directorio de trabajo actual ya contiene un repositorio con el mismo nombre. Para resolver el error, debes clonar la bifurcación en un directorio diferente. - - {% endtip %} -7. Desplázate hasta el nuevo repositorio clonado. - ```shell - $ cd FORK-OF-THE-REPOSITORY - ``` -7. Alterna las ramas para comparar la rama de la solicitud de extracción donde se realizaron los cambios originales. Si te desplazas hasta la solicitud de extracción original, verás la rama de comparación en la parte superior de la solicitud de extracción. ![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png) En este ejemplo, la rama de comparación es `test-branch`: - ```shell - $ git checkout test-branch - ``` - - {% tip %} - - **Sugerencia:** Para obtener más información acerca de las ramas de las solicitudes de extracción, con ejemplos incluidos, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request/#changing-the-branch-range-and-destination-repository)". - - {% endtip %} -8. En este punto, puedes hacer lo que desees con esta rama. Puedes subir confirmaciones nuevas a ella, ejecutar algunas pruebas locales, o fusionar otras ramas en esta rama. Realiza las modificaciones que desees. -9. Una vez que confirmas tus cambios en la rama de encabezado de la solicitud de extracción, puedes subir los cambios a la solicitud original directamente. En este ejemplo, la rama de encabezado es `test-branch`: - ```shell - $ git push origin test-branch - > Counting objects: 32, done. - > Delta compression using up to 4 threads. - > Compressing objects: 100% (26/26), done. - > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done. - > Total 29 (delta 8), reused 0 (delta 0) - > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git - > 12da2e9..250e946 test-branch -> test-branch - ``` - -Tus nuevas confirmaciones se reflejarán en la solicitud de extracción original en {% data variables.product.product_location %}. - -### Leer más - -- "[Acerca de las bifurcaciones](/articles/about-forks)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md deleted file mode 100644 index 3f81493732..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Crear una solicitud de extracción desde una bifurcación -intro: Puedes crear una solicitud de extracción para proponer cambios que has hecho a una bifurcación de un repositorio ascendente. -redirect_from: - - /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. -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -También puedes otorgar permiso a los mantenedores del repositorio ascendente para subir confirmaciones de cambios en una bifurcación propiedad del usuario. Si tu solicitud de extracción compara tu rama de tema con una rama del repositorio ascendente como la rama base, entonces tu rama de tema también se llamará rama de comparación de la solicitud de extracción. Para obtener más información acerca de las ramas de solicitud de extracción, incluyendo ejemplos, consulta la sección "[Crear una solicitud de extracción](/articles/creating-a-pull-request/#changing-the-branch-range-and-destination-repository)." - -{% data reusables.pull_requests.perms-to-open-pull-request %} - -1. Navega al repositorio original de donde creaste tu bifurcación. -{% data reusables.repositories.new-pull-request %} -3. En la página Comparar haz clic en **Comparar entre bifurcaciones**. ![Enlace para comparar entre las bifurcaciones](/assets/images/help/pull_requests/compare-across-forks-link.png) -4. En el menú desplegable de la "rama base", selecciona la rama del repositorio ascendente en donde quieras fusionar los cambios. ![Menús desplegables para elegir la bifurcación y la rama base](/assets/images/help/pull_requests/choose-base-fork-and-branch.png) -5. En el menú desplegable de la "bifurcación principal", selecciona tu bifurcación. Posteriormente, utiliza el menú desplegable de "comparar rama" para seleccionar aquella en la que realizaste los cambios. ![Menús desplegables para elegir la bifurcación del encabezado y la rama de comparación](/assets/images/help/pull_requests/choose-head-fork-compare-branch.png) -{% data reusables.repositories.pr-title-description %} -{% data reusables.repositories.allow-maintainers-user-forks %} - - ![allow-maintainers-to-make-edits-checkbox](/assets/images/help/pull_requests/allow-maintainers-to-make-edits.png) -{% data reusables.repositories.create-pull-request %} - -{% data reusables.repositories.asking-for-review %} - -### Leer más - -- "[Trabajar con bifurcaciones](/articles/working-with-forks)" -- "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md deleted file mode 100644 index 3bfab1e6ee..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Agregar una solicitud de extracción -intro: 'Crea una solicitud de extracción para proponer los cambios para un repositorio y colaborar en su realización. Estos cambios se proponen en una *rama*, lo cual garantiza que la rama predeterminada contenga únicamente trabajo finalizado y aprobado.' -redirect_from: - - /articles/creating-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -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 " -[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. - -{% data reusables.pull_requests.perms-to-open-pull-request %} - -{% data reusables.pull_requests.close-issues-using-keywords %} - - - -### Cambiar el rango de la rama y el repositorio de destino - -De manera predeterminada, las solicitudes de extracción se basan en la [rama por defecto](/articles/setting-the-default-branch) del repositorio padre. - -Si el repositorio padre predeterminado no es el correcto, puedes cambiar tanto el repositorio padre como la rama con las listas desplegables. También puedes intercambiar tus ramas base y encabezado con las listas desplegables para establecer diferencias entre los puntos de referencia. Las referencias que aparecen aquí deben ser nombres de ramas en tu repositorio GitHub. - -![Ramas para editar la solicitud de extracción](/assets/images/help/pull_requests/pull-request-review-edit-branch.png) - -Cuando pienses en las ramas, recuerda que la *rama base* es **el lugar donde** se deben aplicar los cambios y la *rama encabezado* contiene **los cambios** que deseas que se apliquen. - -Cuando cambias el repositorio base, también puedes cambiar las notificaciones de la solicitud de extracción. Cualquier usuario que pueda subir al repositorio base recibirá una notificación por correo electrónico y verá la nueva solicitud de extracción en su tablero la próxima vez que inicie sesión. - -Cuando cambies alguna información en el rango de la rama, las áreas de vista previa modificadas Confirmar y Campos se actualizarán para mostrar tu nuevo rango. - -{% tip %} - -**Tips**: - -- Usando la vista comparativa, puedes configurar comparaciones en todo el periodo. Para obtener más información, consulta la sección "[Comparar confirmaciones de cambios](/github/committing-changes-to-your-project/comparing-commits)." -- Los mantenedores de proyecto pueden agregar una plantilla de solicitud de extracción para un repositorio. Las plantillas incluyen indicaciones para la información en el cuerpo de una solicitud de extracción. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". - -{% endtip %} - - - -### Crear una solicitud de extracción - -{% tip %} - -**Tip**: También puedes utilizar {% data variables.product.prodname_desktop %} para crear una solicitud de extracción. Para obtener más información, consulta la sección “[Crear un informe de problemas o solicitud de extracción](/desktop/contributing-to-projects/creating-an-issue-or-pull-request)" en la documentación de {% data variables.product.prodname_desktop %}. - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} - -2. En el menú "Branch" (Rama), elige la rama que contiene tus confirmaciones. ![Menú desplegable de ramas](/assets/images/help/pull_requests/branch-dropdown.png) - - {% data reusables.repositories.new-pull-request %} - -4. Usa el menú desplegable de la rama _base_ para seleccionar la rama en la que deseas fusionar tus cambios y luego usa el menú desplegable de la rama de _comparación_ para elegir la rama de tema en la que hiciste los cambios. ![Menús desplegables para elegir la base y comparar ramas](/assets/images/help/pull_requests/choose-base-and-compare-branches.png) - - {% data reusables.repositories.pr-title-description %} - - - - {% data reusables.repositories.create-pull-request %} - -{% data reusables.repositories.asking-for-review %} - -Una vez que tu solicitud de extracción ha sido revisada, esta se puede [fusionar en un repositorio](/articles/merging-a-pull-request). - - - -### Leer más - -- "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" -- "[Cambiar la rama base de una solicitud de extracción](/articles/changing-the-base-branch-of-a-pull-request)" -- "[Agregar propuestas y solicitudes de extracción al tablero de proyecto desde la barra lateral](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md deleted file mode 100644 index e7113eab90..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Crear y eliminar ramas en tu repositorio -intro: 'Puedes crear o eliminar ramas directamente en {% data variables.product.product_name %}.' -redirect_from: - - /articles/deleting-branches-in-a-pull-request/ - - /articles/creating-and-deleting-branches-within-your-repository - - /github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Cómo crear una rama - -{% data reusables.repositories.navigate-to-repo %} - -1. Opcionalmente, si quieres crear tu nueva rama desde una rama diferente a la predeterminada para el repositorio, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **NUMBER branches** y luego elige otra rama: ![Vínculo de ramas en página de resumen](/assets/images/help/branches/branches-link.png) -1. Haz clic en el menú del selector de ramas. ![menú del selector de ramas](/assets/images/help/branch/branch-selection-dropdown.png) -1. Escribe un nombre único para tu nueva rama y luego selecciona **Crear rama**. ![cuadro de texto de creación de ramas](/assets/images/help/branch/branch-creation-text-box.png) - -### Cómo eliminar una rama - -{% data reusables.pull_requests.automatically-delete-branches %} - -If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. Para obtener más información, consulta la sección "[Configurar la rama predeterminada](/github/administering-a-repository/setting-the-default-branch)". - -If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request)" or "[Closing a pull request](/github/collaborating-with-issues-and-pull-requests/closing-a-pull-request)." - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.navigate-to-branches %} -1. Desplázate hasta la rama que deseas eliminar y luego haz clic en {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}. ![eliminar la rama](/assets/images/help/branches/branches-delete.png) - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -{% data reusables.pull_requests.retargeted-on-branch-deletion %} -{% endif %} -Para obtener más información, consulta "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)." - -### Leer más - -- "[Acerca de las ramas](/github/collaborating-with-issues-and-pull-requests/about-branches)" -- "[Ver las ramas en tu repositorio](/github/administering-a-repository/viewing-branches-in-your-repository)" -- "[Borrar y restaurar ramas en una solicitud de extracción](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md deleted file mode 100644 index d878aaf08e..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Proponer cambios a tu trabajo con solicitudes de extracción -intro: 'Después de agregar cambios a una rama de tema o bifurcación, puedes abrir una solicitud de extracción para pedirle a tus colaboradores o al administrador del repositorio que revisen tus cambios antes de fusionarlos con el proyecto.' -redirect_from: - - /articles/proposing-changes-to-your-work-with-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /about-branches - - /creating-and-deleting-branches-within-your-repository - - /about-pull-requests - - /about-comparing-branches-in-pull-requests - - /creating-a-pull-request - - /creating-a-pull-request-from-a-fork - - /changing-the-stage-of-a-pull-request - - /requesting-a-pull-request-review - - /changing-the-base-branch-of-a-pull-request - - /committing-changes-to-a-pull-request-branch-created-from-a-fork ---- - diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md deleted file mode 100644 index 0cea87f03f..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Solicitar una revisión de solicitud de extracción -intro: 'Después de crear una solicitud de extracción, le puedes pedir a una persona específica que revise los cambios que propusiste. Si eres miembro de la organización, también puedes solicitarle a un equipo específico que revise tus cambios.' -redirect_from: - - /articles/requesting-a-pull-request-review - - /github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Los propietarios y colaboradores de un repositorio que pertenece a una cuenta de usuario pueden asignar revisiones de solicitud de extracción. Los miembros de la organización con permisos de clasificación de un repositorio pueden asignar una revisión de solicitud de extracción. - -Los propietarios o colaboradores pueden asignar una revisión de solicitud de extracción a cualquier persona que tenga [acceso de lectura](/articles/access-permissions-on-github) explícitamente garantizado a un repositorio que es propiedad del usuario. Los miembros de la organización pueden asignar la revisión de una solicitud de extracción a una persona o equipo con acceso de lectura a un repositorio. El revisor o equipo solicitado recibirá una notificación sobre tu solicitud de revisión de la solicitud de extracción. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Si solicitas una revisión de un equipo y se ha habilitado una tarea de revisión de código, se solicitarán miembros específicos y el equipo se eliminará como revisor. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)".{% endif %} - -{% note %} - -**Nota:** Los autores de solicitudes de extracción no pueden solicitar revisiones a menos que sean propietarios del repositorio o colaboradores con acceso de escritura al repositorio. - -{% endnote %} - -Puedes solicitar una revisión de una persona sugerida o de una persona específica. Los revisores sugeridos se basan en los [datos del último responsable de git](/articles/tracking-changes-in-a-file/). Si solicitas una revisión, otras personas con acceso de escritura al repositorio pueden seguir revisando tu solicitud de extracción. Una vez que alguien haya revisado tu solicitud de código y hayas implementado los cambios necesarios, puedes volver a solicitar la revisión al mismo revisor. Si el revisor solicitado no emite una revisión y la solicitud de extracción cumple con los [requisitos para fusión](/articles/defining-the-mergeability-of-pull-requests) del repositorio, puedes fusionarla de todos modos. - -{% data reusables.repositories.sidebar-pr %} -2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que quieres que una persona específica o un equipo revise. -3. Navega hacia **Reviewers** (Revisores) en la barra lateral derecha. -4. Para solicitar la revisión de una persona sugerida en **Reviewers** (Revisores), al lado del nombre de usuario, haz clic en **Request** (Solicitar). ![Icono Reviewers request (Solicitud de revisores) en la barra lateral derecha](/assets/images/help/pull_requests/request-suggested-review.png) -5. De manera opcional, para solicitar una revisión de alguna persona que no sea una persona sugerida, haz clic en **Reviewers** (Revisores), luego haz clic en un nombre en el menú desplegable. ![Icono Reviewers gear (Parámetro de revisores) en la barra lateral derecha](/assets/images/help/pull_requests/request-a-review-not-suggested.png) -6. De manera opcional, si conoces el nombre de la persona o el equipo del que quieres una revisión, haz clic en **Reviewers** (Revisores), luego escribe el nombre de usuario de la persona o el nombre del equipo al que le solicitarás que revise tus cambios. Haz clic en su nombre de equipo o nombre de usuario para solicitar una revisión. ![Campo para ingresar el nombre de usuario de un revisor y desplegable con el nombre del revisor](/assets/images/help/pull_requests/choose-pull-request-reviewer.png) -7. Después de que la solicitud de extracción esté revisada y de que hayas hecho los cambios necesarios, le puedes pedir a un revisor que vuelva a revisar tu solicitud de extracción. Navega hasta **Reviewers** (Revisores) en la barra lateral derecha y haz clic en {% octicon "sync" aria-label="The sync icon" %} al lado del nombre del revisor del que quieres la revisión. ![Icono Re-review sync (Sincronización de volver a revisar) en la barra lateral derecha](/assets/images/help/pull_requests/request-re-review.png) - -### Leer más - -- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md deleted file mode 100644 index e573805f90..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Acerca de las revisiones de solicitudes de extracción -intro: 'Las revisiones le permiten a los colaboradores comentar los cambios propuestos en las solicitudes de extracción, aprobar los cambios o solicitar más cambios antes de que se fusione la solicitud de extracción. Los administradores de repositorio pueden solicitar que todas las solicitudes de extracción sean aprobadas antes de ser fusionadas.' -redirect_from: - - /articles/about-pull-request-reviews - - /github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Acerca de las revisiones de solicitudes de extracción - -Después de abrir una solicitud de extracción, cualquiera con acceso de *lectura* puede revisar y comentar sobre los cambios propuestos. También puedes sugerir cambios específicos a las líneas de código que el autor puede aplicar directamente desde las solicitud de extracción. 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)." - -Los colaboradores y los propietarios del repositorio pueden solicitar la revisión de una solicitud de extracción por parte de una persona específica. Los miembros de la organización también pueden solicitar la revisión de una solicitud de extracción por parte de un equipo con acceso de lectura al repositorio. Para obtener más información, consulta "[Solicitar la revisión de una solicitud de extracción](/articles/requesting-a-pull-request-review/)". {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Puedes especificar un subconjunto de miembros del equipo a quienes se les asigne automáticamente en vez de que se aplique a todo el equipo. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)".{% endif %} - -Las revisiones permiten el debate de los cambios propuestos y ayudan a asegurarse de que los cambios cumplen con las pautas de contribución del repositorio y otras normas de calidad. Puedes definir qué individuos o equipos poseen ciertos tipos o áreas de código en un archivo CODEOWNERS. Cuando una solicitud de extracción modifica un código que tiene un propietario definido, ese individuo o equipo será solicitado automáticamente como revisor. Para obtener más información, consulta "[Acerca de los propietarios del código](/articles/about-code-owners/)". - -{% if currentVersion == "free-pro-team@latest" %}Puedes programar recordatorios para las solicitudes de extracción que deben revisarse. Para obtener más información, consulta la sección "[ Administrar los recordatorios programados para solicitudes de extracción](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)".{% endif %} - -![Encabezado de revisión solicitando cambios con comentarios en la línea](/assets/images/help/pull_requests/review-header-with-line-comment.png) - -Un revisión tiene tres posibles estado: -- **Comentario**: envía opiniones en general sin aprobar explicitamente los cambios ni solicitar cambios adicionales. -- **Aprobar**: envía opiniones y aprueba la fusión de los cambios propuestos en la solicitud de extracción. -- **Solicitar cambios**: envía opiniones que deben ser abordadas antes de que se pueda fusionar la solicitud de extracción. - -![Imagen de los estados de revisión](/assets/images/help/pull_requests/pull-request-review-statuses.png) - -{% data reusables.repositories.request-changes-tips %} - -Puedes ver todas las revisiones que ha recibido una solicitud de extracción en la cronología de conversaciones y puedes ver las revisiones realizadas por los colaboradores y los propietarios del repositorio en la casilla de fusión de la solicitud de extracción. - -![Imagen de las revisiones en una casilla de fusión](/assets/images/help/pull_requests/merge_box/pr-reviews-in-merge-box.png) - -{% data reusables.search.requested_reviews_search_tip %} - -{% data reusables.pull_requests.resolving-conversations %} - -### Revisiones requeridas - -{% data reusables.pull_requests.required-reviews-for-prs-summary %} - -Para obtener más información, consulta "[Acerca de las revisiones requeridas para las solicitudes de extracción](/articles/about-required-reviews-for-pull-requests)". - -{% tip %} - -**Sugerencia**: De ser necesario, las personas con acceso de *administración* o de *escritura* a un repositorio pueden descartar una revisión de solicitud de extracción. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/articles/dismissing-a-pull-request-review)". - -{% endtip %} - -### Leer más - -- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Activar las revisiones requeridas para las solicitudes de extracción](/articles/enabling-required-reviews-for-pull-requests)" -- "[Ver la revisión de una solicitud de extracción](/articles/viewing-a-pull-request-review)" -- "[Configurar pautas para los colaboradores de repositorios](/articles/setting-guidelines-for-repository-contributors)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md deleted file mode 100644 index b95795aff7..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Aprobar una solicitud de extracción con revisiones requeridas -intro: 'Si tu repositorio requiere revisiones, las solicitud de extracción deben tener un número específico de revisiones de aprobación de personas con permisos de _escritura_ o _administración_ en el repositorio antes de que puedan ser fusionados.' -redirect_from: - - /articles/approving-a-pull-request-with-required-reviews - - /github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Para obtener más información sobre las revisiones requeridas, consulta "[Acerca de las revisiones requeridas para solicitudes de extracción](/articles/about-required-reviews-for-pull-requests)". - -Puedes comentar una solicitud de extracción, aprobar los cambios o solicitar mejoras antes de aprobarlas. Para obtener más información, consulta "[Acerca de las revisiones requeridas para solicitudes de extracción](/articles/about-required-reviews-for-pull-requests)" y "[Revisar cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)". - -{% data reusables.search.requested_reviews_search %} - -{% tip %} - -**Sugerencia**: Si una solicitud de extracción que aprobaste ha cambiado significativamente, puedes descartar tu revisión. La solicitud de extracción necesitará una nueva revisión antes de que pueda fusionarse. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/articles/dismissing-a-pull-request-review)". - -{% endtip %} - -{% data reusables.repositories.sidebar-pr %} -{% data reusables.repositories.choose-pr-review %} -{% data reusables.repositories.changed-files %} -4. Revisa los cambios en la solicitud de extracción, y opcionalmente, [comenta sobre las líneas específicas](/articles/reviewing-proposed-changes-in-a-pull-request/#starting-a-review). -{% data reusables.repositories.review-changes %} -{% data reusables.repositories.review-summary-comment %} -7. Selecciona **Approve** (Aprobar) para aprobar la fusión de los cambios propuestos en la solicitud de extracción. -{% data reusables.repositories.submit-review %} - -{% data reusables.repositories.request-changes-tips %} - -### Leer más - -- "[Acerca de las revisiones requeridas para las solicitudes de extracción](/articles/about-required-reviews-for-pull-requests)" -- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Comentar sobre una solicitud de extracción](/articles/commenting-on-a-pull-request)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md deleted file mode 100644 index c79884386c..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Revisar solicitudes de extracción localmente -intro: 'Cuando alguien te manda una solicitud de extracción desde una bifurcación o rama de tu repositorio, puedes fusionarla localmente para resolver un conflicto de fusión o para probar y verificar los cambios antes de fusionarlos en {% data variables.product.product_name %}.' -redirect_from: - - /articles/checking-out-pull-requests-locally - - /github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally -permissions: Anyone with write access to a repository can pull a remote pull request down locally. -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% note %} - - **Nota:** Los autores de solicitudes de extracción pueden otorgar permisos a los mantenedores del repositorio ascendente, o a aquellos con acceso de escritura en dicho repositorio, para realizar confirmaciones de cambios en sus solicitudes de extracción para comparar ramas en una bifurcación propiedad de un usuario. Para más información, consulta "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)" - - {% endnote %} - -### Modificar una solicitud de extracción activa localmente - -{% data reusables.repositories.sidebar-pr %} -2. En la lista de solicitudes de extracción, da clic en aquella que quieras modificar.{% if currentVersion == "free-pro-team@latest" %} -3. Para elegir dónde te gustaría abrir la solicitud de extracción, selecciona la opción **Abrir con {% octicon "triangle-down" aria-label="The down triangle icon" %}** del menú desplegable y da clic en una de las pestañas. ![Link to access command line pull request instructions](/assets/images/help/pull_requests/open-with-button.png){% else %} -3. En la caja de fusión, da clic en **instrucciones para línea de comandos**. Sigue la secuencia de pasos para disminuir la solicitud de extracción propuesta. ![Enlace para acceder a las instrucciones de la solicitud de extracción de la línea de comando](/assets/images/help/pull_requests/pull_request_show_command_line_merge.png) -4. De manera opcional, para ver los cambios propuestos en {% data variables.product.prodname_desktop %}, da clic en **abrir en {% data variables.product.prodname_desktop %}**. ![Link to open a pull request locally in Desktop](/assets/images/help/desktop/open-pr-in-desktop.png){% endif %} - -### Modificar una solicitud de extracción inactiva localmente - -Si algún autor de una solicitud de extracción no responde a las solicitudes o ha eliminado su bifurcación, dicha solicitud se fusionará de todos modos. Sin embargo, si deseas realizar cambios a una solicitud de extracción y el autor no responde, necesitarás realizar algunos pasos adicionales para actualizar la solicitud de extracción. - -Una vez que se abre una solicitud de extracción, {% data variables.product.product_name %} almacena todos los cambios remotamente. Es decir, Los repositorios cuentan con confirmaciones de cambios en una solicitud de extracción aún antes de que esta solicitud se fusione. Puedes extraer una solicitud y recrearla como tuya. - -Cualquier persona puede trabajar con una solicitud de extracción abierta anteriormente para seguir trabajando en ella, probarla o incluso abrir nuevas solicitud de extracción con cambios adicionales. Sin embargo, solo los colaboradores con acceso de escritura pueden fusionar las solicitudes de extracción. - -{% data reusables.repositories.sidebar-issue-pr %} -2. En la lista "Pull Requests" (Solicitudes de extracción), haz clic en la solicitud de extracción que deseas fusionar. -3. Busca el número de la ID de la solicitud de extracción inactiva. Esta es la secuencia de dígitos inmediatamente después del título de la solicitud de extracción. ![Número de ID de las solicitudes de extracción](/assets/images/help/pull_requests/pull_request_id_number.png) -{% data reusables.command_line.open_the_multi_os_terminal %} -5. Extrae la referencia de la solicitud de extracción en función de su número de ID, creando una nueva rama en el proceso. - ```shell - $ git fetch origin pull/ID/head:BRANCHNAME - ``` -6. Cambia a la rama nueva que está basada en esta solicitud de extracción: - ```shell - [main] $ git checkout BRANCHNAME - > Switched to a new branch 'BRANCHNAME' - ``` -7. En este punto, puedes hacer lo que desees con esta rama. Puedes ejecutar algunas pruebas locales o fusionar otras ramas en esta rama. -8. Cuando estés listo, puedes subir la rama nueva: - ```shell - [pull-inactive-pull-request] $ git push origin BRANCHNAME - > Counting objects: 32, done. - > Delta compression using up to 4 threads. - > Compressing objects: 100% (26/26), done. - > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done. - > Total 29 (delta 8), reused 0 (delta 0) - > To https://{% data variables.command_line.codeblock %}/username/repository.git - > * [new branch] BRANCHNAME -> BRANCHNAME - ``` -9. [Crea una nueva solicitud de extracción](/articles/creating-a-pull-request) con tu nueva rama. - -### Error: Error al subir algunas referencias - -El espacio de nombres remoto de `refs/pull/` es *read-only*. Si intentas subir alguna confirmación allí, verás este error: -```shell -! [remote rejected] HEAD -> refs/pull/1/head (deny updating a hidden ref) -error: failed to push some refs to 'git@github.local:USERNAME/REPOSITORY.git' -``` - -{% tip %} - -**Sugerencia:** Cuando alguien elimina o cambia el nombre de una referencia remota, tu espacio de nombre `refs/pull/origin/` local no se verá afectado por las llamadas a `git-remote`. - -{% endtip %} diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md deleted file mode 100644 index 111a4114bc..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Comentar en una solicitud de extracción -redirect_from: - - /articles/adding-commit-comments/ - - /articles/commenting-on-the-diff-of-a-pull-request/ - - /articles/commenting-on-differences-between-files/ - - /articles/commenting-on-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request -intro: 'Luego de abrir una solicitud de extracción en un repositorio, los colaboradores o miembros del equipo pueden comentar sobre la comparación de archivos entre dos ramas especificadas, o dejar comentarios generales en el proyecto en general.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Acerca de los comentarios de las solicitudes de extracción - -Puedes comentar en la pestaña **Conversation** (Conversación) de una solicitud de extracción para dejar comentarios generales, preguntas o apoyos. También puedes sugerir cambios que el autor de la solicitud de extracción puede aplicar directamente desde tu comentario. - -![Conversación de solicitud de extracción](/assets/images/help/pull_requests/conversation.png) - -También puedes comentar sobre secciones específicas de un archivo en la pestaña **Files changed** (Archivos cambiados) de una solicitud de extracción en forma de comentarios en la línea o como parte de una [revisión de solicitud de extracción](/articles/about-pull-request-reviews). Agregar comentarios en la línea es una gran manera de debatir preguntas sobre la implementación o brindar retroalimentación al autor. - -Para obtener más información sobre cómo agregar comentarios en la línea a una revisión de solicitud de extracción, consulta ["Revisar cambios propuestos en una solicitud de extracción".](/articles/reviewing-proposed-changes-in-a-pull-request) - -{% note %} - -**Nota:** Si respondes una solicitud de extracción por correo electrónico, tu comentario se agregará a la pestaña **Conversation** (Conversación) y no será parte de una revisión de solicitud de extracción. - -{% endnote %} - -Para responder un comentario en la línea que ya existe, deberás ir hasta el comentario en la pestaña **Conversation** (Conversación) o en la pestaña **Files changed** (Archivos modificados) y agregar otro comentario en la línea debajo. - -{% tip %} - -**Sugerencias:** -- Los comentarios de las solicitudes de extracción soportan el mismo [ formato](/categories/writing-on-github) que los comentarios regulares en {% data variables.product.product_name %}, como @menciones, emojis y referencias. -- Puedes [agregar reacciones](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) a los comentarios en las solicitudes de extracción en la pestaña **Files changed** (Archivos cambiados). - -{% endtip %} - -### Agregar comentarios en la línea a una solicitud de extracción - -{% data reusables.repositories.sidebar-pr %} -2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción en la que deseas dejar los comentarios en la línea. -{% data reusables.repositories.changed-files %} -{% data reusables.repositories.start-line-comment %} -{% data reusables.repositories.type-line-comment %} -{% data reusables.repositories.suggest-changes %} -5. Cuando hayas terminado, haz clic en **Add single comment** (Agregar comentario único). ![Ventana de comentario en línea](/assets/images/help/commits/inline-comment.png) - -Cualquier persona que observe la solicitud de extracción o el repositorio recibirá una notificación de tu comentario. - -{% data reusables.pull_requests.resolving-conversations %} - -### Leer más - -- [Crear un enlace permanente al fragmento de código](/articles/creating-a-permanent-link-to-a-code-snippet/)" -{% if currentVersion == "free-pro-team@latest" %}- "[Informar abuso o spam](/articles/reporting-abuse-or-spam)" -{% endif %} diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md deleted file mode 100644 index fd1c2afd68..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Descartar una revisión de una solicitud de extracción -intro: 'Si tu repositorio [requiere revisiones(/articles/about-required-reviews-for-pull-requests), puedes descartar las revisiones de solicitudes de extracción que ya no son válidas o que no pueden ser aprobadas por el revisor.' -redirect_from: - - /articles/dismissing-a-pull-request-review - - /github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.pull_requests.dismiss_review %} -Esto cambia el estado de la revisión, que pasa a ser un comentario de revisión. Cuando descartas una revisión, debes agregar un comentario que explique por qué la descartaste. Tu comentario se agregará a la conversación de la solicitud de extracción. - -{% data reusables.search.requested_reviews_search %} - -{% data reusables.repositories.sidebar-pr %} -{% data reusables.repositories.choose-pr-review %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -3. En la pestaña "Conversación", desplázate hasta la revisión que deseas descartar y haz clic en {% octicon "chevron-down" aria-label="The down button" %}. ![Icono de comillas angulares en el cuadro de fusión](/assets/images/help/pull_requests/merge_box/pull-request-open-menu.png) -4. Haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego haz clic en **Descartar revisión**. ![Icono de kebab en el cuadro de fusión](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review.png) -5. Escribe la razón por la que descartas la revisión y luego haz clic en **Descartar revisión**. ![Botón Dismiss review (Descartar revisión)](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review-button.png) -{% else %} -3. En la pestaña "Conversación", desplázate hasta la revisión que deseas ver y luego haz clic en **Descartar revisión**. ![Opción para descartar una revisión](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review.png) -4. Escribe la razón por la que descartas la revisión y luego haz clic en **Descartar revisión**. ![Botón Dismiss review (Descartar revisión)](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review-button.png) -{% endif %} - -### Leer más - -- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" -- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" -- "[Acerca de las revisiones requeridas para las solicitudes de extracción](/articles/about-required-reviews-for-pull-requests)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md deleted file mode 100644 index 55c4cbef95..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Filtrar archivos en una solicitud de extracción -intro: 'Para ayudarte a revisar rápidamente los cambios en una solicitud de extracción grande, puedes filtrar los archivos modificados.' -redirect_from: - - /articles/filtering-files-in-a-pull-request-by-file-type/ - - /articles/filtering-files-in-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Puedes filtrar archivos en una solicitud de extracción por tipo de extensión de archivo, tales como `.html` o `.js`, sin extensión, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} propietario del código, {% endif %} o archivos de configuración ("dotfiles"). - -{% tip %} - -**Sugerencia:** Para simplificar tu vista de la diferencia de la solicitud de extracción, puedes ocultar de manera temporaria los archivos eliminados{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} o los archivos que ya has visto{% endif %} en la diferencia de la solicitud de extracción desde el menú desplegable para filtrar archivos. - -{% endtip %} - -{% data reusables.repositories.sidebar-pr %} -2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que deseas filtrar. -{% data reusables.repositories.changed-files %} -4. Usa el menú desplegable para Filtrar archivos y selecciona, elimina la marca de selección o haz clic en los filtros deseados. ![Opción Filtrar archivos sobre la diferencia de la solicitud de extracción](/assets/images/help/pull_requests/file-filter-option.png) -5. Para borrar la selección de filtro en la pestaña **Archivos modificados** puedes hacer clic en **Borrar**. ![Borrar selección de filtro de archivo](/assets/images/help/pull_requests/clear-file-filter.png) - -### Leer más - -- "[Acerca de la comparación de las ramas en una solicitud de extracción](/articles/about-comparing-branches-in-pull-requests)" -- "[Encontrar métodos y funciones modificados en una solicitud de extracción](/articles/finding-changed-methods-and-functions-in-a-pull-request)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md deleted file mode 100644 index c35d6af2eb..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Encontrar funciones y métodos cambiados en una solicitud de extracción -intro: 'Puedes encontrar rápidamente los cambios propuestos en un método o función en los archivos *.go*, *.js*, *.ts*, *.py*, *.php*, and *.rb*.' -redirect_from: - - /articles/finding-changed-methods-and-functions-in-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Cualquier usuario con acceso de lectura a un repositorio puede ver una lista resumida de los cambios en las funciones y los métodos en determinados archivos o solicitud de extracción. - -La lista resumida de métodos y funciones se crea a partir de estos tipos de archivos compatibles: - - Go - - JavaScript (incluidos Typescript, Flow y otros tipos de JavaScript) - - PHP - - Python - - Ruby - -{% data reusables.repositories.sidebar-pr %} -2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción en la que deseas encontrar los métodos y funciones modificados. -{% data reusables.repositories.changed-files %} -4. Para ver una lista resumida de los métodos y funciones modificados, haz clic en **Ir a...**. ![Ir al menú desplegable](/assets/images/help/pull_requests/jump-to-menu.png) -5. Selecciona el método o la función cambiada dentro del menú desplegable. También puedes ingresar el nombre del método o la función en los resultados del filtro. ![Filtrar función y métodos](/assets/images/help/pull_requests/filter-function-and-methods.png) - - {% note %} - - **Nota:** Si no encuentras las funciones o los métodos que esperabas, confirma que tu código se compile y no contenga errores. En el menú desplegable aparecen solo las funciones y los métodos modificados en esta solicitud de extracción que se encuentran en los archivos *.go*, *.js*, *.ts*, *.py*, *.php* y *.rb*.. - - {% endnote %} - -6. Serás redireccionado a la primera línea de la función o el método seleccionado. ![ver la función o el método en los archivos modificados](/assets/images/help/pull_requests/view-selected-function-or-method.png) - -### Leer más - -- "[Acerca de la comparación de las ramas en una solicitud de extracción](/articles/about-comparing-branches-in-pull-requests)" -- "[Filtrar archivos en una solicitud de extracción por tipo de archivo](/articles/filtering-files-in-a-pull-request-by-file-type)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md deleted file mode 100644 index 9d7bf25d2e..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Incorporar comentarios en tu solicitud de extracción -intro: 'Cuando los revisores sugieran cambios en una solicitud de extracción, puedes incorporar automáticamente los cambios a la solicitud de extracción o abrir una propuesta para hacer un seguimiento de las sugerencias que están fuera de alcance.' -redirect_from: - - /articles/incorporating-feedback-in-your-pull-request - - /github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Aplicar modificaciones sugeridas - -Otras personas pueden sugerir modificaciones específicas a tu solicitud de extracción. Puedes aplicar estas modificaciones sugeridas directamente en una solicitud de extracción si tienes acceso de escritura al repositorio. Si la solicitud de extracción se creó desde una bifurcación, y el autor permitió que los mantenedores realicen ediciones, también puedes aplicar las modificaciones sugeridas si tienes acceso de escritura al repositorio ascendente. Para obtener más información, consulte las secciones"[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" y "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork)". - -Para incorporar rápidamente más de una de las modificaciones sugeridas en una confirmación simple, también puedes aplicar las modificaciones sugeridas como lote. Aplicar una modificación sugerida o un lote de modificaciones sugeridas genera una confirmación simple en la rama comparada de la solicitud de extracción. - -Cada una de las personas que sugirieron alguna de las modificaciones incluidas en la confirmación será coautora de la confirmación. La persona que aplica las modificaciones sugeridas será coautora y persona que confirma el cambio de la confirmación. Para obtener más información acerca del término "persona que confirma el cambio en Git", consulta "[Principios de Git - Ver el historial de confirmaciones](https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History)" desde el sitio del libro _Pro Git_. - -{% data reusables.repositories.sidebar-pr %} -2. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción a la que quieras aplicarle una modificación sugerida. -3. Navega hasta la primera modificación sugerida que quieras aplicar. - - Para aplicar la modificación en su propia confirmación, haz clic en **Commit suggestion** (Confirmar sugerencia). ![Botón Commit suggestion (Confirmar sugerencia)](/assets/images/help/pull_requests/commit-suggestion-button.png) - - Para agregar la sugerencia a un lote de modificaciones, haz clic en **Add suggestion to batch** (Agregar sugerencia a un lote). Continúa agregando las modificaciones sugeridas que quieras incluir en una única confirmación. Cuando hayas terminado de agregar las modificaciones sugeridas, haz clic en **Commit suggestions** (Confirmar sugerencias). ![Botón Add suggestion to batch (Agregar sugerencia al lote)](/assets/images/help/pull_requests/add-suggestion-to-batch.png) -4. En el campo de mensaje de confirmación, escribe un mensaje de confirmación corto y significativo que describa la modificación que le hiciste al archivo o los archivos. ![Campo para mensaje de confirmación](/assets/images/help/pull_requests/suggested-change-commit-message-field.png) -5. Haz clic en **Commit changes.** (Confirmar modificaciones) ![Botón Commit changes (Confirmar cambios)](/assets/images/help/pull_requests/commit-changes-button.png) - -### Abrir una propuesta para una sugerencia fuera de alcance - -Si alguna persona sugiere cambios para tu solicitud de extracción, y los cambios están fuera del alcance de la solicitud de extracción, puedes abrir una propuesta nueva para hacer el seguimiento de los comentarios. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". - -### Leer más - -- "[Acerca de las revisiones de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" -- "[Revisar los cambios propuestos en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request)" -- "[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)" -- "[Solicitar una revisión de solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review)" -- "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/index.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/index.md deleted file mode 100644 index a3cb4a02e7..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Revisar cambios en solicitudes de extracción -redirect_from: - - /articles/reviewing-and-discussing-changes-in-pull-requests/ - - /articles/reviewing-changes-in-pull-requests -intro: 'Después de haber abierto una solicitud de extracción, puedes revisar y opinar sobre el conjunto de cambios propuestos.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /about-pull-request-reviews - - /reviewing-proposed-changes-in-a-pull-request - - /filtering-files-in-a-pull-request - - /finding-changed-methods-and-functions-in-a-pull-request - - /commenting-on-a-pull-request - - /viewing-a-pull-request-review - - /incorporating-feedback-in-your-pull-request - - /approving-a-pull-request-with-required-reviews - - /dismissing-a-pull-request-review - - /checking-out-pull-requests-locally ---- - diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md deleted file mode 100644 index 37baaad8bc..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Revisar los cambios propuestos en una solicitud de extracción -intro: 'En una solicitud de extracción, puedes revisar y opinar sobre las confirmaciones, los archivos cambiados y las diferencias (o "diff") entre los archivos de las ramas de base y comparada.' -redirect_from: - - /articles/reviewing-proposed-changes-in-a-pull-request - - /github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Acerca de revisar las solicitudes de extracción - -Puedes revisar los cambios de una solicitud de extracción en un archivo por vez. Mientras revisas los archivos en una solicitud de extracción, puedes dejar comentarios individuales sobre cambios específicos.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} Después de que termines de revisar cada archivo, puedes marcar el archivo como visto. Esto colapsa el archivo, lo cual te ayuda a identificar los archivos que aún debes revisar. Una barra de progreso en el encabezado de la solicitud de extracción muestra la cantidad de archivos que ya viste.{% endif %} Después de revisar tantos archivos como quieras, puedes aprobar la solicitud de extracción o solicitar cambios adicionales enviando tu revisión con un comentario resumen. - -{% data reusables.search.requested_reviews_search_tip %} - -### Comenzar una revisión - -{% data reusables.repositories.sidebar-pr %} -{% data reusables.repositories.choose-pr-review %} -{% data reusables.repositories.changed-files %} -{% data reusables.repositories.start-line-comment %} -{% data reusables.repositories.type-line-comment %} -{% data reusables.repositories.suggest-changes %} -5. Cuando estés listo, haz clic en **Start a review** (Comenzar una revisión). Si ya comenzaste una revisión, puedes hacer clic en **Add review comment** (Agregar comentario de revisión). ![Botón Start a review (Comenzar una revisión)](/assets/images/help/pull_requests/start-a-review-button.png) - -Antes de enviar tu revisión, tus comentarios de líneas quedan _pendientes_, y solo tú los puedes ver. Puedes editar los comentarios pendientes en cualquier momento antes de enviar tu revisión. Para cancelar una revisión pendiente, incluidos todos sus comentarios pendientes, desplázate hasta el final de la cronología en la pestaña Conversation (Conversación) y haz clic en **Cancel review** (Cancelar revisión). - -![Botón Cancel review (Cancelar revisión)](/assets/images/help/pull_requests/cancel-review-button.png) - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -### Marcar un archivo como visto - -Después de que hayas terminado de revisar un archivo, puedes marcar el archivo como visto, y el archivo se colapsará. Si el archivo se modifica después de que lo hayas visto, dejará de estar marcado como visto. - -{% data reusables.repositories.changed-files %} -2. A la derecha del encabezado del archivo que terminaste de revisar, selecciona **Viewed** (Visto). ![Casilla Viewed (Visto)](/assets/images/help/pull_requests/viewed-checkbox.png) -{% endif %} - -### Enviar tu revisión - -Después de que hayas terminado de revisar todos los archivos que quieras de la solicitud de extracción, envía tu revisión. - -{% data reusables.repositories.changed-files %} -{% data reusables.repositories.review-changes %} -{% data reusables.repositories.review-summary-comment %} -4. Selecciona el tipo de revisión que te gustaría proporcionar: ![Botones de selección con opciones de revisión](/assets/images/help/pull_requests/pull-request-review-statuses.png) - - Selecciona **Comment** (Comentario) para dejar una opinión general sin aprobar de manera explícita los cambios ni solicitar cambios adicionales. - - Selecciona **Approve** (Aprobar) para enviar tus comentarios y aprobar la fusión de los cambios propuestos en la solicitud de extracción. - - Selecciona **Request changes** (Solicitar cambios) para enviar comentarios que se deban tener en cuenta antes de que se pueda fusionar la solicitud de extracción. -{% data reusables.repositories.submit-review %} - -{% data reusables.repositories.request-changes-tips %} - -### Leer más - -- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" -- "[Acerca de las revisiones requeridas para las solicitudes de extracción](/articles/about-required-reviews-for-pull-requests)" -- "[Aprobar una solicitud de extracción con revisiones requeridas](/articles/approving-a-pull-request-with-required-reviews)" -- "[Comentar sobre una solicitud de extracción](/articles/commenting-on-a-pull-request)" -- "[Filtrar solicitudes de extracción por estado de revisión](/articles/filtering-pull-requests-by-review-status)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md deleted file mode 100644 index d3e5015e11..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Ver una revisión de solicitud de extracción -intro: Puedes ver todos los comentarios realizados en una revisión de revisión de solicitud de extracción única. -redirect_from: - - /articles/viewing-a-pull-request-review - - /github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.search.requested_reviews_search %} - -Cuando ves una revisión completa, verás la misma versión de la solicitud de extracción como el revisor lo hizo al momento de la revisión. - -{% data reusables.repositories.sidebar-pr %} -{% data reusables.repositories.choose-pr-review %} -3. En la pestaña "Conversation" (Conversación), desplázate hasta la revisión que deseas ver y luego haz clic en **View changes (Ver cambios)**. ![Encabezado de revisión con el vínculo de revisión completa](/assets/images/help/pull_requests/view-full-review-view-changes.png) - -### Leer más - -- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" -- "[Revisar los cambios propuestos en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks.md deleted file mode 100644 index 0041ba8daa..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Acerca de las bifurcaciones -intro: Una bifurcación es una copia de un repositorio que administras. Las bifurcaciones te permiten realizar cambios a un proyecto sin afectar el repositorio original. Puedes recuperar actualizaciones o enviar cambios al repositorio original con solicitudes de extracción. -redirect_from: - - /articles/about-forks - - /github/collaborating-with-issues-and-pull-requests/about-forks -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Bifurcar un repositorio es similar a copiar un repositorio, con dos diferencias principales: - -* Puedes utilizar una solicitud de extracción para sugerir cambios desde las bifurcaciones de las cuales sea dueño tu usuario hacia el repositorio original, también conocido como el repositorio *ascendente*. -* Puedes llevar cambios desde tu repositorio ascendente a tu bifurcación local sincronizando tu bifurcación con el repositorio ascendente. - -{% data reusables.repositories.you-can-fork %} - -{% 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.{% if currentVersion == "free-pro-team@latest" %} 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 %} - -En proyectos de código abierto, las bifurcaciones suelen iterar en ideas o cambios antes de que se presenten al repositorio ascendente. Cuando realizas cambios en la bifurcación que es propiedad de tu usuario y abres una solicitud de extracción que compara tu trabajo con el repositorio ascendente, puedes dar permiso a cualquiera con permiso de escritura en el repositorio ascendente para subir cambios a tu rama de solicitudes de extracción. Esto agiliza la colaboración permitiendo que los mantenedores del repositorio puedan hacer confirmaciones de cambios o ejecutar pruebas locales a tu rama de solicitud de extracción desde una bifurcación propiedad de un usuario antes de fusionarlas. No puedes otorgar permisos de escritura a una bifurcación que sea propiedad de una organización. - -{% data reusables.repositories.private_forks_inherit_permissions %} - -Si quieres crear un repositorio nuevo desde los contenidos de un repositorio existente, pero no quieres fusionar tus cambios de manera ascendente en el futuro, puedes duplicar el repositorio {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %}o, si el repositorio es una plantilla, usar el repositorio como una plantilla{% endif %}. Para obtener más información, consulta "[Duplicar un repositorio](/articles/duplicating-a-repository)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} y [Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)"{% endif %}. - -### Leer más - -- "[Acerca de los modelos de desarrollo colaborativo](/articles/about-collaborative-development-models)" -- "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)" -- [Guías de código abierto](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} -- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md deleted file mode 100644 index 7f3200714c..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Permitir cambios para una rama de solicitud de extracción creada desde una bifurcación -intro: 'Para tener una mejor colaboración, puedes permitir confirmaciones de cambios en ramas que hayas creado a partir de bifurcaciones de las cuales sea dueño tu usuario.' -redirect_from: - - /articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork - - /github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork -permissions: People with push access to the upstream repository of a fork owned by a user account can commit to the forked branches. -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Solo los autores de las solicitudes de extracción pueden otorgar permisos a los mantenedores del repositorio ascendente, o a aquellos con acceso de escritura en dicho repositorio, para realizar confirmaciones de cambios en sus solicitudes de extracción para comparar ramas en una bifurcación propiedad de un usuario. Para conocer más sobre los repositorios ascendentes, consulta "[Acerca de las bifurcaciones](/articles/about-forks)". - -Los autores de las solicitudes de extracción pueden otorgar estos permisos antes o después de crear dicha solicitud inicial. desde una bifurcación propiedad de un usuario. Para obtener más información, consulta la sección "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)." - -Puedes establecer permisos de confirmación al crear por primera vez una solicitud de extracción desde una bifurcación. Para obtener más información, consulta la sección "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)." Además, puedes modificar una solicitud de extracción existente para permitir que los mantenedores de un repositorio realicen confirmaciones a tu rama. - -### Habilitar permisos del mantenedor del repositorio en solicitudes de extracción existentes - -1. En {% data variables.product.product_name %}, desplázate hasta la página principal del repositorio ascendente de tu solicitud de extracción. -2. En el nombre del repositorio ascendente, haz clic en {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull requests** (Solicitudes de extracción). ![Selección de la pestaña de propuestas y solicitudes de extracción](/assets/images/help/repository/repo-tabs-pull-requests.png) -3. En la lista de solicitudes de extracción, desplázate hasta la solicitud de extracción en la que deseas realizar las confirmaciones. -{% data reusables.repositories.allow-maintainers-user-forks %} - - ![allow-maintainers-to-make-edits-sidebar-checkbox](/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png) - -### Leer más - -- "[Confirmar cambios en una rama de la solicitud de extracción creada desde una bifurcación](/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork)" diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md deleted file mode 100644 index 71b2cbbd4a..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Configurar un remoto para una bifurcación -intro: 'Debes configurar un remoto que apunte al repositorio ascendente en Git para [sincronizar los cambios que realizas en una bifurcación](/articles/syncing-a-fork) con el repositorio original. Esto también te permite sincronizar los cambios en el repositorio original con la bifurcación.' -redirect_from: - - /articles/configuring-a-remote-for-a-fork - - /github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Enumera el repositorio remoto configurado actualmente para tu bifurcación. - ```shell - $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) - ``` -3. Especifica un nuevo repositorio *ascendente* remoto que se sincronizará con la bifurcación. - ```shell - $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git - ``` -4. Verifica el nuevo repositorio ascendente que especificaste para tu bifurcación. - ```shell - $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) - ``` diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/index.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/index.md deleted file mode 100644 index d8818065fa..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Trabajar con bifurcaciones -intro: 'Las bifurcaciones se suelen usar en desarrollo de código abierto en {% data variables.product.product_name %}.' -redirect_from: - - /articles/working-with-forks -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /about-forks - - /configuring-a-remote-for-a-fork - - /syncing-a-fork - - /merging-an-upstream-repository-into-your-fork - - /allowing-changes-to-a-pull-request-branch-created-from-a-fork - - /what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility ---- - diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md deleted file mode 100644 index e073dd985c..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Fusionar un repositorio ascendente dentro de tu bifurcación -intro: 'Si no tienes acceso de subida (escritura) en un repositorio ascendente, entonces puedes extraer confirmaciones de cambios de ese repositorio dentro tu propia bifurcación.' -redirect_from: - - /articles/merging-an-upstream-repository-into-your-fork - - /github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Cambiar el directorio de trabajo actual en tu proyecto local. -3. Revisa la rama a la que deseas fusionar. Habitualmente, fusionarás en la rama predeterminada. - ```shell - $ git checkout master - ``` -4. Extrae la rama deseada del repositorio ascendente. Este método conservará el historial de confirmación de cambios sin modificación. - ```shell - $ git pull https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git BRANCH_NAME - ``` -5. Si hay conflictos, resuélvelos. Para obtener más información, consulta "[Abordar conflictos de fusión](/articles/addressing-merge-conflicts)". -6. Confirma la fusión. -7. Revisa los cambios y asegúrate que sean correctos. -8. Sube la fusión en tu repositorio de GitHub. - ```shell - $ git push origin master - ``` diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork.md deleted file mode 100644 index a5fc10fea0..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Sincronizar una bifurcación -intro: Sincronizar una bifurcación de un repositorio para mantenerla actualizada con el repositorio ascendente. -redirect_from: - - /articles/syncing-a-fork - - /github/collaborating-with-issues-and-pull-requests/syncing-a-fork -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Antes de sincronizar una bifurcación con un repositorio ascendente, debes [configurar un remoto que apunte al repositorio ascendente ](/articles/configuring-a-remote-for-a-fork) en Git. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Cambiar el directorio de trabajo actual en tu proyecto local. -3. Extrae las ramas y sus respectivas confirmaciones desde el repositorio ascendente. Las confirmaciones de `master` (principal) se almacenarán en una rama local, `upstream/master`. - ```shell - $ git fetch upstream - > remote: Counting objects: 75, done. - > remoto: Comprimiendo objetos: 100 % (53/53), realizado. - > remote: Total 62 (delta 27), reused 44 (delta 9) - > Unpacking objects: 100% (62/62), done. - > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY - > * [new branch] master -> upstream/master - ``` -4. Revisa tus ramas `master` (principales) locales de la bifurcación. - ```shell - $ git checkout master - > Switched to branch 'master' - ``` -5. Fusiona los cambios desde `upstream/master` en tu rama `master` (principal) local. Esto trae la rama `master` (principal) de tu bifurcación en sincronización con el repositorio ascendente, sin perder tus cambios locales. - ```shell - $ git merge upstream/master - > Updating a422352..5fdff0f - > Fast-forward - > README | 9 ------- - > README.md | 7 ++++++ - > 2 files changed, 7 insertions(+), 9 deletions(-) - > delete mode 100644 README - > create mode 100644 README.md - ``` If your local branch didn't have any unique commits, Git will instead perform a "fast-forward": - ```shell - $ git merge upstream/master - > Updating 34e91da..16c56ad - > Fast-forward - > README.md | 5 +++-- - > 1 file changed, 3 insertions(+), 2 deletions(-) - ``` - -{% tip %} - -**Sugerencia:**: sincronizar tu bifurcación únicamente actualiza tu copia local del repositorio. Para actualizar tu bifurcación en {% data variables.product.product_location %}, debes [subir tus cambios](/articles/pushing-commits-to-a-remote-repository/). - -{% endtip %} diff --git a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md deleted file mode 100644 index 8f2031a3d6..0000000000 --- a/translations/es-XL/content/github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: ¿Qué le sucede a las bifurcaciones cuando se elimina un repositorio o cambia la visibilidad? -intro: Eliminar tu repositorio o cambiar su visibilidad afecta las bifurcaciones de ese repositorio. -redirect_from: - - /articles/changing-the-visibility-of-a-network/ - - /articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility - - /github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -#### Eliminar un repositorio privado - -Cuando eliminas un repositorio privado, todas sus bifurcaciones privadas también se eliminan. - -#### Eliminar un repositorio público - -Cuando eliminas un repositorio público, se elige una de sus bifurcaciones públicas para ser el nuevo repositorio padre. Todos los otros repositorios se bifurcan fuera de este nuevo repositorio y las solicitudes de extracción siguientes van a este nuevo padre. - -#### Permisos y bifurcaciones privadas - -{% data reusables.repositories.private_forks_inherit_permissions %} - -#### Convertir un repositorio público en un repositorio privado - -Si un repositorio público se convierte en privado, sus bifurcaciones públicas se separan a una nueva red. Como con la eliminación de un repositorio público, se elige una de las bifurcaciones públicas existentes para ser el nuevo repositorio padre y todos los otros repositorios se bifurcan fuera de este nuevo padre. Las solicitudes de extracción siguientes van a este nuevo padre. - -En otras palabras, las bifurcaciones de un repositorio público permanecerán en su propia red separada del repositorio incluso después de que un repositorio padre se convierte en privado. Esto permite que los propietarios de las bifurcaciones continúen trabajando y colaboren sin interrupción. Si las bifurcaciones públicas no se mueven a una red separada de esta manera, los propietarios de esas bifurcaciones podrían necesitar obtener los [permisos de acceso](/articles/access-permissions-on-github) adecuados para extraer cambios y enviar solicitudes de extracción desde el repositorio padre (ahora privado) y hacia él, incluso si no necesitaban esos permisos anteriormente. - -{% if currentVersion != "free-pro-team@latest" %} -Si un repositorio público tiene habilitado el acceso de lectura anónimo de Git, y el repositorio se vuelve privado, todas las bifurcaciones del repositorio perderán el acceso de lectura anónimo de Git y regresarán a la configuración predeterminada inhabilitada. Si un repositorio bifurcado se convierte en público, los administradores del repositorio pueden volver a habilitar el acceso de lectura anónimo de Git. Para obtener más información, consulta "[Habilitar acceso de lectura anónimo de Git para un repositorio](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)." -{% endif %} - -##### Eliminar el repositorio privado - -Si un repositorio público se convierte en privado, y después se elimina, sus bifurcaciones públicas continuarán existiendo en una red separada. - -#### Convertir un repositorio privado en un repositorio público - -Si un repositorio privado se convierte en público, cada una de sus bifurcaciones se convierte en un repositorio privado independiente y se vuelve el padre de su propia red de repositorio nueva. Las bifurcaciones privadas nunca se convierten en públicas automáticamente ya que podrían contener confirmaciones confidenciales que no deberían divulgarse públicamente. - -##### Eliminar el repositorio público - -Si un repositorio privado se convierte en público y después se elimina, sus bifurcaciones privadas continuarán existiendo como repositorios privados independientes en redes separadas. - -### Leer más - -- "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)" -- "[Acerca de las bifurcaciones](/articles/about-forks)" -- "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)" -- "[Administrar la política de bifurcación para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md deleted file mode 100644 index 87f55e8054..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Acerca de las confirmaciones -intro: Puedes guardar grupos pequeños de cambios significativos como confirmaciones. -redirect_from: - - /articles/why-are-my-commits-in-the-wrong-order - - /github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order - - /github/committing-changes-to-your-project/about-commits -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Acerca de las confirmaciones - -{% data reusables.commits.about-commits %} - -Puedes agregar un co-autor en cualquier confirmación en la que colabores. Para obtener más información, consulta "[Crear una confirmación con múltiples autores](/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors)". - -{% if currentVersion == "free-pro-team@latest" %} -También puedes crear una confirmación en nombre de una organización. Para obtener más información, consulta la sección "[Crear una confirmación en nombre de una organización](/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization)".{% endif %} - -El rebase te permite cambiar varias confirmaciones y puede modificar el órden de éstas en tu línea de tiempo. Para obtener más información, consulta la sección [Accerca del rebase de Git](/github/using-git/about-git-rebase)". - -### Leer más -- "[Confirmar y revisar los cambios a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits)" en {% data variables.product.prodname_desktop %} diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md deleted file mode 100644 index d1a45c3c46..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: Cambiar un mensaje de confirmación -redirect_from: - - /articles/can-i-delete-a-commit-message/ - - /articles/changing-a-commit-message - - /github/committing-changes-to-your-project/changing-a-commit-message -intro: 'Si un mensaje de confirmación contiene información poco clara, incorrecta o confidencial, puedes modificarlo localmente y subir una nueva confirmación con un nuevo mensaje para {% data variables.product.product_name %}. También puedes cambiar un mensaje de confirmación para agregar la información faltante.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Volver a escribir el mensaje de confirmación más reciente - -Puedes cambiar el mensaje de confirmación más reciente usando el comando `git commit --amend`. - -{% warning %} - -En Git, el texto del mensaje de confirmación es parte de la confirmación. Si cambias el mensaje de confirmación cambiará commit ID--i.e., la suma de comprobación SHA1 que designa la confirmación. Efectivamente, estás creando una nueva confirmación que reemplaza a la anterior. - -{% endwarning %} - -#### La confirmación no ha sido subida en línea - -Si la confirmación solo existe en tu repositorio local y no ha sido subida a {% data variables.product.product_location %} puedes modificar el mensaje de confirmación con el comando `git commit --amend`. - -1. En la línea de comando, desplázate hasta el repositorio que contiene la confirmación que deseas modificar. -2. Escribe `git commit --amend` y presiona **Enter** (Intro). -3. En tu editor de texto, edita el mensaje de confirmación y guarda la confirmación. - - Puedes agregar un coautor al agregar una introducción a la confirmación. Para obtener más información, consulta "[Crear una confirmación con múltiples autores](/articles/creating-a-commit-with-multiple-authors)". -{% if currentVersion == "free-pro-team@latest" %} - - Puedes crear confirmaciones en nombre de tu organización agregando una introducción al mensaje de la confirmación. Para obtener más información, consulta "[Crear una confirmación en nombre de una organización](/articles/creating-a-commit-on-behalf-of-an-organization)" -{% endif %} - -El nuevo mensaje y la confirmación aparecerán en {% data variables.product.product_location %} la próxima vez que subas un cambio. - -{% tip %} - -Puedes cambiar el editor de texto predeterminado para Git al cambiar el parámetro `core.editor`. Para más información, consulta "[Basic Client Configuration](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" en el manual de Git. - -{% endtip %} - -#### Modificar mensajes de confirmación múltiples o más antiguos - -Si ya has subido la confirmación a {% data variables.product.product_location %}, deberás realizar un empuje forzado de la confirmación con un mensaje modificado. - -{% warning %} - -Desalentamos enfáticamente el empuje forzado, dado que cambia el historial de tu repositorio. Si realizas un empuje forzado, las personas que tienen clonado tu repositorio deberán arreglar manualmente el historial local. Para obtener más información, consulta "[Recuperarse de una rebase ascendente](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" en el manual de Git. - -{% endwarning %} - -**Modificar el mensaje de la confirmación subida más recientemente** - -1. Sigue los [pasos anteriores](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) para modificar el mensaje de confirmación. -2. Usa el comando `push --force` para realizar un empuje forzado sobre la confirmación anterior. - ```shell - $ git push --force example-branch - ``` - -**Modificar el mensaje de confirmación múltiple o más antiguo** - -Si necesitas modificar el mensaje para múltiples confirmaciones o una confirmación más antigua, puedes usar la rebase interactiva y luego forzar el empuje para cambiar el historial de confirmación. - -1. En la línea de comando, desplázate hasta el repositorio que contiene la confirmación que deseas modificar. -2. Usa el comando `git rebase -i HEAD~n` para mostrar una lista de las últimas confirmaciones `n` en tu editor de texto predeterminado. - - ```shell - # Displays a list of the last 3 commits on the current branch - $ git rebase -i HEAD~3 - ``` - La lista se verá parecida a la siguiente: - - ```shell - pick e499d89 Delete CNAME - pick 0c39034 Better README - pick f7fde4a Change the commit message but push the same commit. - - # Rebase 9fdb3bd..f7fde4a sobre 9fdb3bd - # - # Comandos: - # p, escoger = usar confirmación - # r, volver a redactar = usar confirmación, pero editar el mensaje de confirmación - # e, editar = usar confirmación, pero detener la modificación - # s, machacar = usar confirmación, pero fusionarla con la confirmación anterior - # f, arreglar = como "machacar", pero descartar el mensaje de registro de confirmación - # x, exec = ejecutar comando (el resto de la línea) usando shell - # - # Estas líneas pueden reordenarse, pero se ejecutan desde arriba hacia abajo. - # - # Si eliminas una línea aquí ESA CONFIRMACIÓN SE PERDERÁ. - # Sin embargo, si eliminas todo, la rebase será interrumpida. - # - # Note that empty commits are commented out - ``` - -3. Reemplaza `pick` (escoger) por `reword` (volver a redactar) antes de cada mensaje de confirmación que desees cambiar. - ```shell - pick e499d89 Delete CNAME - reword 0c39034 Better README - reword f7fde4a Change the commit message but push the same commit. - ``` -4. Guardar y cerrar el archivo con la lista de confirmaciones. -5. En cada archivo de confirmación resultante, escribe el nuevo mensaje de confirmación, guarda el archivo, y ciérralo. -6. Realizar un empuje forzado de las confirmaciones modificadas. - ```shell - $ git push --force - ``` - -Para más información sobre la rebase interactiva, consulta [Interactive mode](https://git-scm.com/docs/git-rebase#_interactive_mode)" (Modo interactivo) en el manual de Git. - -{% tip %} - -Tal como mencionamos anteriormente, si modificas el mensaje de confirmación se producirá una confirmación nueva con una ID nueva. Sin embargo, en este caso, cada confirmación posterior a la confirmación modificada también arrojará una ID nueva porque cada confirmación también contiene la ID de su padre. - -{% endtip %} - -{% warning %} - -Si incluiste información confidencial en un mensaje de confirmación, el empuje forzado de la confirmación con una confirmación modificada no eliminará la confirmación original de {% data variables.product.product_name %}. La confirmación anterior no será parte de una clonación posterior; sin embargo, es posible que siga almacenada en la memoria caché de {% data variables.product.product_name %} y que esté accesible mediante la ID de confirmación. Debes ponerte en contacto con {% data variables.contact.contact_support %} con la ID de confirmación antigua para purgarla del repositorio remoto. - -{% endwarning %} - -### Leer más - -* "[Firmar confirmaciones](/articles/signing-commits)" diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md deleted file mode 100644 index 40cff2325e..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Crear una confirmación en nombre de una organización -intro: 'Puedes crear confirmaciones en nombre de una organización agregando una introducción al mensaje de la confirmación. Las confirmaciones atribuidas a una organización incluyen un distintivo `on-behalf-of` (en nombre de) en {% data variables.product.product_name %}.' -redirect_from: - - /articles/creating-a-commit-on-behalf-of-an-organization - - /github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization -versions: - fpt: '*' ---- -{% note %} - -**Nota:** La capacidad de crear una confirmación en nombre de una organización se encuentra actualmente en la versión beta de acceso público y está sujeta a modificaciones. - -{% endnote %} - -Para crear confirmaciones en nombre de una organización: - -- debes ser miembro de la organización indicada en la introducción -- debes firmar la confirmación -- tu correo electrónico de confirmación y el correo electrónico de la organización debe estar dentro de un dominio verificado por la organización -- tu mensaje de confirmación debe finalizar con la introducción de la confirmación `on-behalf-of: @org ` - - `org` es el inicio de sesión de la organización - - `name@organization.com` se encuentra en el dominio de la organización - -Las organizaciones pueden usar el correo electrónico `name@organization.com` como punto de contacto público para los esfuerzos de código abierto que se hagan. - -### Crear confirmaciones con un distintivo `on-behalf-of` en la línea de comando - -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} - -2. En la línea siguiente del mensaje de confirmación, escriba `on-behalf-of: @org ` y luego coloque comillas de cierre. - - ```shell - $ git commit -m "Refactor usability tests. - > - > - on-behalf-of: @org <name@organization.com>" - ``` - -El nuevo mensaje de confirmación y el distintivo aparecerán en {% data variables.product.product_location %} la próxima vez que subas un cambio. Para obtener más información, consulta "[Subir cambios a un repositorio remoto](/articles/pushing-commits-to-a-remote-repository/)." - -### Crear confirmaciones con un distintivo `on-behalf-of` en {% data variables.product.product_name %} - -Una vez que hayas realizado los cambios en un archivo usando el editor web en {% data variables.product.product_name %}, puedes crear una confirmación en nombre de tu organización agregando una introducción `on-behalf-of:` al mensaje de confirmación. - -1. Luego de hacer tus cambios, en la parte inferior de la página, escribe un mensaje de confirmación breve y significativo que describa tus cambios. ![Mensaje de confirmación de tu cambio](/assets/images/help/repository/write-commit-message-quick-pull.png) - -2. En el cuadro de texto que aparece debajo de tu mensaje de confirmación, agrega `on-behalf-of: @org `. - - ![Ejemplo de introducción de mensaje de confirmación on-behalf-of en el segundo cuadro de texto para el mensaje de confirmación](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png) -4. Haz clic en **Confirmar cambios** o **Proponer cambios**. - -La confirmación, el mensaje y el distintivo nuevos aparecerán en {% data variables.product.product_location %}. - -### Leer más - -- "[Ver las contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)" -- "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" -- "[Ver un resumen de la actividad del repositorio](/articles/viewing-a-summary-of-repository-activity)" -- "[Ver los colaboradores de un proyecto](/articles/viewing-a-projects-contributors)" -- "[Cambiar un mensaje de confirmación](/articles/changing-a-commit-message)" diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md b/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md deleted file mode 100644 index e0d30978cc..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Creating a commit with multiple authors -intro: 'You can attribute a commit to more than one author by adding one or more `Co-authored-by` trailers to the commit''s message. Co-authored commits are visible on {% data variables.product.product_name %}{% if currentVersion != "free-pro-team@latest" %} and can be included in the profile contributions graph and the repository''s statistics{% endif %}.' -redirect_from: - - /articles/creating-a-commit-with-multiple-authors - - /github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Required co-author information - -Before you can add a co-author to a commit, you must know the appropriate email to use for each co-author. For the co-author's commit to count as a contribution, you must use the email associated with their {% data variables.product.product_name %} account. - -{% if currentVersion == "free-pro-team@latest" %} - -If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy. Otherwise, the co-author's email will be available to the public in the commit message. If you want to keep your email private, you can choose to use a {% data variables.product.product_name %}-provided `no-reply` email for Git operations and ask other co-authors to list your `no-reply` email in commit trailers. - -For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." - - {% tip %} - - **Tip:** You can help a co-author find their preferred email address by sharing this information: - - To find your {% data variables.product.product_name %}-provided `no-reply` email, navigate to your email settings page under "Keep my email address private." - - To find the email you used to configure Git on your computer, run `git config user.email` on the command line. - - {% endtip %} - -{% endif %} - -### Creating co-authored commits using {% data variables.product.prodname_desktop %} - -You can use {% data variables.product.prodname_desktop %} to create a commit with a co-author. For more information, see "[Write a commit message and push your changes](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)" and [{% data variables.product.prodname_desktop %}](https://desktop.github.com). - -![Add a co-author to the commit message](/assets/images/help/desktop/co-authors-demo-hq.gif) - -### Creating co-authored commits on the command line - -{% data reusables.pull_requests.collect-co-author-commit-git-config-info %} - -{% data reusables.pull_requests.commit-message-with-trailer-beginning %} - -3. On the next line of the commit message, type `Co-authored-by: name ` with specific information for each co-author. After the co-author information, add a closing quotation mark. - - If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. - ```shell - $ git commit -m "Refactor usability tests. - > - > - Co-authored-by: name <name@example.com> - Co-authored-by: another-name <another-name@example.com>" - ``` - -The new commit and message will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/articles/pushing-commits-to-a-remote-repository/)." - -### Creating co-authored commits on {% data variables.product.product_name %} - -After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message. - -{% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -2. After making your changes together, at the bottom of the page, type a short, meaningful commit message that describes the changes you made. - ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png) -3. In the text box below your commit message, add `Co-authored-by: name ` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. - - ![Commit message co-author trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-co-author-trailer.png) -4. Click **Commit changes** or **Propose changes**. - -The new commit and message will appear on {% data variables.product.product_location %}. - -### Further reading -{% if currentVersion != "free-pro-team@latest" %} -- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)" -- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} -- "[Viewing a summary of repository activity](/articles/viewing-a-summary-of-repository-activity)" -- "[Viewing a project's contributors](/articles/viewing-a-projects-contributors)" -- "[Changing a commit message](/articles/changing-a-commit-message)" -- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#3-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/index.md b/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/index.md deleted file mode 100644 index 06da7f662a..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/creating-and-editing-commits/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Crear y editar confirmaciones de cambios -intro: '' -redirect_from: - - /articles/creating-and-editing-commits -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /about-commits - - /creating-a-commit-with-multiple-authors - - /creating-a-commit-on-behalf-of-an-organization - - /changing-a-commit-message ---- - diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/index.md b/translations/es-XL/content/github/committing-changes-to-your-project/index.md deleted file mode 100644 index 294ee55e5e..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Confirmar cambios en su proyecto -redirect_from: - - /categories/21/articles/ - - /categories/commits/ - - /categories/committing-changes-to-your-project -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /creating-and-editing-commits - - /viewing-and-comparing-commits - - /troubleshooting-commits ---- -### Índice - - diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md deleted file mode 100644 index e73dea80ab..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: La confirmación existe en GitHub pero no en mi clon local -intro: 'Algunas veces una confirmación estará visible en {% data variables.product.product_name %}, pero no existirá en tu clon local del repositorio.' -redirect_from: - - /articles/commit-exists-on-github-but-not-in-my-local-clone - - /github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -Cuando usas `git show` para ver una confirmación específica en la línea de comando, puedes obtener un error fatal. - -Por ejemplo, puedes recibir un error `bad object` localmente: - -```shell -$ git show 1095ff3d0153115e75b7bca2c09e5136845b5592 -> fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592 -``` - -Sin embargo, cuando ves la confirmación en {% data variables.product.product_location %}, podrás verla sin problemas: - -`github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592` - -Existen varias explicaciones posibles: - -* El repositorio local está desactualizado. -* La rama que contiene la contiene la confirmación fue eliminada, por lo que ya no se hace referencia a la confirmación. -* Alguien realizó un empuje forzado sobre la confirmación. - -### El repositorio local está desactualizado - -Es posible que tu repositorio local aún no esté confirmado. Para obtener información desde tu repositorio remoto hasta tu clon local, usa `git fetch`: - -```shell -$ git fetch remote -``` - -Esto copia información de manera segura desde el repositorio remoto hasta tu clon local sin hacer cambios a los archivos que has revisado. Puedes usar `git fetch upstream` para obtener información desde un repositorio que has bifurcado o `git fetch origin` para obtener información desde un repositorio que solo has clonado. - -{% tip %} - -**Sugerencia**: Para obtener información, lee sobre [cómo administrar remotos y extraer datos](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) en el libro [Pro Git](https://git-scm.com/book). - -{% endtip %} - -### La rama que contenía la confirmación fue eliminada - -Si un colaborador del repositorio ha eliminado la rama que contiene la confirmación o ha realizado un empuje forzado sobre la rama, es posible que la confirmación faltante haya quedado huérfana (es decir, no puede ser alcanzado desde cualquier referencia) y, por lo tanto, no se extraerá en tu clon local. - -Afortunadamente, si un colaborador tiene un clon local del repositorio con la confirmación faltante, puede volver a forzarla en {% data variables.product.product_name %}. Necesitan asegurarse de que la confirmación sea utilizada como referencia por parte de una rama local y que luego la suban como una rama nueva a {% data variables.product.product_name %}. - -Digamos que la persona todavía tiene una rama local (llamémosla `B`) que contiene la confirmación. Esto puede realizar el seguimiento de la rama que tuvo un empuje forzado o eliminado y que simplemente todavía no han actualizado. Para preservar la confirmación, pueden subir esa rama local a una rama nueva (llamémosla `recover-B`) en {% data variables.product.product_name %}. Para este ejemplo, supongamos que tienen un remoto denominado `ascendente` mediante el cual tienen acceso de escritura a `github.com/$account/$repository`. - -La otra persona ejecuta: - -```shell -$ git branch recover-B B -# Crea una nueva rama local que hace referencia a la confirmación -$ git push upstream B:recover-B -# Sube la B local a la nueva rama ascendente, creando una nueva referencia a la confirmación -``` - -Ahora, *tú* puedes ejecutar: - -```shell -$ git fetch upstream recover-B -# Crea la confirmación en tu repositorio local. -``` - -### Evitar empujes forzados - -Evita los empujes forzados a un repositorio a menos que sea absolutamente necesario. Esto es especialmente cierto si más de una persona puede subir al repositorio. - -### Leer más - -- ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) -- ["Recuperación de datos" sde el libro _Pro Git_](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/index.md b/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/index.md deleted file mode 100644 index 5b4ec2f351..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Confirmaciones de solución de problemas -intro: '' -redirect_from: - - /articles/troubleshooting-commits -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /commit-exists-on-github-but-not-in-my-local-clone - - /why-are-my-commits-linked-to-the-wrong-user ---- - diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md deleted file mode 100644 index a4353b4f96..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: ¿Por qué mis confirmaciones están vinculadas al usuario incorrecto? -redirect_from: - - /articles/how-do-i-get-my-commits-to-link-to-my-github-account/ - - /articles/why-are-my-commits-linked-to-the-wrong-user - - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user -intro: '{% data variables.product.product_name %} usa la dirección de correo electrónico en el encabezado de la confirmación para vincular la confirmación con un usuario de GitHub. Si tus confirmaciones se están vinculando con otro usuario, o no se están vinculando con ningún usuario, es posible que necesites cambiar tus parámetros de configuración de Git local, agregar una dirección de correo electrónico a las configuraciones de tu cuenta de correo electrónico, o ambos.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -{% tip %} - -**Nota**: Si tus confirmaciones se vinculan con otro usuario, eso no significa que el usuario puede acceder a tu repositorio. Un usuario solo puede acceder a un repositorio de tu propiedad si lo agregas como colaborador o lo agregas a un equipo que tiene acceso al repositorio. - -{% endtip %} - -### Las confirmaciones se vinculan con otro usuario - -Si tus confirmaciones se vinculan con otro usuario, eso significa que el usuario agregó la dirección de correo electrónico en tus parámetros de configuración de Git local a su cuenta {% data variables.product.product_name %}. En este caso, puedes cambiar el correo electrónico en tus parámetros de configuración de Git local y agregar la nueva dirección de correo electrónico a tu cuenta {% data variables.product.product_name %} para vincular futuras configuraciones con tu cuenta. - -1. Para cambiar la dirección de correo electrónico en tu configuración de Git local, sigue los pasos en "[Establecer tu dirección de correo electrónico de confirmación en Git](/articles/setting-your-commit-email-address)". Si trabajas en máquinas múltiples, necesitarás cambiar esta configuración en cada una de ellas. -2. Agrega la dirección de correo electrónico del paso 2 a las configuraciones de tu cuenta siguiendo los pasos en "[Agregar una dirección de correo electrónico a tu cuenta de GitHub](/articles/adding-an-email-address-to-your-github-account)". - -Las confirmaciones que haces desde este punto en adelante se vincularán con tu cuenta. - -### Las confirmaciones no se vinculan con ningún usuario - -Si tus confirmaciones de cambios no se vinculan con ningún usuario, el nombre del autor de las mismas no se mostrará como un enlace a un perfil de usuario. - -Para revisar la dirección de correo electrónico que se usó para esas confirmaciones y conectar las confirmaciones con tu cuenta, sigue los siguientes pasos: - -1. Desplázate hasta la confirmación haciendo clic en el enlace del mensaje de confirmación. ![Enlace de mensaje de confirmación](/assets/images/help/commits/commit-msg-link.png) -2. Para leer un mensaje acerca del porqué la confirmación no se vinculó, pasa el puntero sobre el {% octicon "question" aria-label="Question mark" %} azul a la derecha del nombre de usuario. ![Mensaje de confirmación con el puntero](/assets/images/help/commits/commit-hover-msg.png) - - - **Autor no reconocido (con dirección de correo electrónico)** Si ves este mensaje con una dirección de correo electrónico, significa que la dirección no se agregó a las configuraciones de tu cuenta. Para vincular tus confirmaciones, [agrega la dirección de correo electrónico a tus configuraciones de correo electrónico de GitHub](/articles/adding-an-email-address-to-your-github-account). Si tu dirección de correo electrónico se asoció a un Gravatar, este se mostrará a un costado de tu nombre de usuario en vez del Octocat gris predeterminado. - - **Autor no reconocido (sin dirección de correo electrónico)** Si ves este mensaje sin una dirección de correo electrónico, significa que usaste una dirección de correo electrónico general que no se puede agregar a tus configuraciones de correo electrónico. Deberás [establecer tu dirección de correo electrónico de confirmación en Git](/articles/setting-your-commit-email-address), luego [agregar la nueva dirección a tus configuraciones de correo electrónico de GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular tus futuras confirmaciones. Las confirmaciones antiguas no se vincularán. - - **Correo electrónico inválido** Esto significa que la dirección de correo electrónico en tus parámetros de configuración de Git local está en blanco o no está formateada como una dirección de correo electrónico. Deberás [establecer tu dirección de correo electrónico de confirmación en Git](/articles/setting-your-commit-email-address), luego [agregar la nueva dirección a tus configuraciones de correo electrónico de GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular tus futuras confirmaciones. Las confirmaciones antiguas no se vincularán. - -{% warning %} - -Si tu configuración de Git local contiene una dirección de correo electrónico general, o una dirección de correo electrónico que ya se adjuntó a la cuenta de otro usuario, entonces tus confirmaciones anteriores no se vincularán a tu cuenta. Si bien Git te permite cambiar la dirección de correo electrónico que usaste para confirmaciones anteriores, desaconsejamos esto totalmente, en especial en un repositorio compartido. - -{% endwarning %} - -### Leer más - -* "[Buscar confirmaciones](/articles/searching-commits)" diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md b/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md deleted file mode 100644 index 5533dde6e9..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Confirmar rama y etiquetas -intro: Puedes ver fácilmente qué rama es una confirmación al mirar las etiquetas debajo de la confirmación en la página de confirmación. -redirect_from: - - /articles/commit-branch-and-tag-labels - - /github/committing-changes-to-your-project/commit-branch-and-tag-labels -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -Si tu confirmación no está en la rama predeterminada, un indicador mostarará las ramas que contienen la confirmación. Si la confirmación es parte de una solicitud de extracción no fusionada, mostrará un enlace. - -![Etiqueta Commit branch (Confirmar rama)](/assets/images/help/commits/Commit-branch-label.png) - -Una vez que la confirmación está en la rama por defecto, todas las etiquetas que contienen la confirmación se mostrarán y la rama por defecto será la única rama enumerada. - -![Commit-master-label](/assets/images/help/commits/Commit-master-label.png) - -### Leer más - -* "[Firmar confirmaciones](/articles/signing-commits)" -* "[Firmar etiquetas](/articles/signing-tags)" diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md deleted file mode 100644 index 03f294af1d..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Comparar confirmaciones -redirect_from: - - /articles/comparing-commits-across-time - - /github/committing-changes-to-your-project/comparing-commits-across-time - - /github/committing-changes-to-your-project/comparing-commits -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -Puedes comparar el estado de tu repositorio a través de ramas, etiquetas, confirmaciones de cambios y fechas. Para comparar versiones diferentes de tu repositorio, añade `/compare` a la ruta del mismo. - -Demostraremos el poder de Compare (Comparar) al observar la página de comparación para [una bifurcación del repositorio Lingüista](https://github.com/octocat/linguist), que está en [https://github.com/octocat/linguist/compare/master...octocat:master](https://github.com/octocat/linguist/compare/master...octocat:master). - -Cada vista Compare (Comparar) del repositorio contiene dos menús desplegables: `base` y `compare`. - -`base` debería ser considerado como punto de partida de tu comparación, d `compare` es el punto final. Durante una comparación, siempre puedes cambiar tus puntos `base` y `compare` al hacer clic en **Edit** (Editar). - -### Comparar ramas - -El uso más común de "Compare" es comparar ramas, tal como cuando estás iniciando una solicitud de extracción nueva. Siempre se te llevará a la vista de comparación de ramas cuando inicies una [solicitud de extracción nueva](/articles/creating-a-pull-request). - -Para comparar ramas, puedes seleccionar un nombre de rama desde el menú desplegable `compare` en la parte superior de la página. - -Aquí hay un ejemplo de una [comparación entre dos ramas](https://github.com/octocat/linguist/compare/master...octocat:an-example-comparison-for-docs). - -### Comparar etiquetas - -Cuando compares etiquetas de lanzamiento se te mostrarán los cambios que se han realizado a tu repositorio desde el último lanzamiento. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}Para obtener más información, consulta la sección "[Comparar lanzamientos](/github/administering-a-repository/comparing-releases)".{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}Para comparar etiquetas, puedes seleccionar un nombre de etiqueta del menú desplegable `compare` en la parte superior de la página. {% else %}En vez de teclear un nombre de rama, teclea el nombre de tu etiqueta en el menú desplegable de `compare`.{% endif %} - -Aquí hay un ejemplo de una [comparación entre dos etiquetas](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3). - -### Comparar confirmaciones - -También puedes comparar dos confirmaciones arbitrarias en tu repositorio o sus bifurcaciones en {% data variables.product.prodname_dotcom %} en una comparación de diferencias de dos puntos. - -Para comparar rápidamente dos confirmaciones en Git Object IDs (OID por sus siglas en inglés) directamente entre sí en una comparación de diferencias de dos puntos en {% data variables.product.prodname_dotcom %}, edita la URL de la página "Comparing changes" (Comparar cambios) en tu repositorio. - -{% data reusables.repositories.two-dot-diff-comparison-example-urls %} - -Para obtener más información sobre otras opciones de comparación, consulta "[Comparaciones de diferencia de tres puntos y dos puntos](/articles/about-comparing-branches-in-pull-requests#three-dot-and-two-dot-git-diff-comparisons)". - -### Comparar entre bifurcaciones - -Puedes comparar tu repositorio base y otro repositorio bifurcado. Esta es la vista que se presenta cuando un usuario realiza una Solicitud de extracción a un proyecto. - -Para comparar ramas en repositorios diferentes, antepone los nombres de la rama con los nombres del usuario. Por ejemplo, al especificar `octocat:master` para `base` y `octo-org:master` para `compare`, puedes comparar la rama `master` de los repositorios respectivamte que pertenecen a `octocat` y `octo-org`. - -Aquí hay un ejemplo de una [comparación entre dos repositorios](https://github.com/octocat/linguist/compare/master...octo-org:master). - -### Comparaciones entre confirmaciones - -A modo de atajo, Git usa la notación `^` para referirse a "una confirmación anterior". - -Puedes usar esta notación para comparar una sola confirmación o rama con sus predecesores inmediatos. Por ejemplo, `96d29b7^^^^^` indica cinco confirmaciones anteriores a `96d29b7`, porque hay cinco marcas `^`. Si escribes `96d29b7^^^^^` en la rama `base` y `96d29b7` en la rama `compare` se compararán las cinco confirmaciones que se hicieron antes de `96d29b7` con la confirmación `96d29b7`. - -Aquí hay un ejemplo de una [comparación usando la notación `^`](https://github.com/octocat/linguist/compare/octocat:96d29b7%5E%5E%5E%5E%5E...octocat:96d29b7). - -### Leer más - -- "[Cambiar la rama base de una solicitud de extracción](/articles/changing-the-base-branch-of-a-pull-request)" diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md deleted file mode 100644 index 302329d7ce..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Diferencias entre las vistas de las confirmaciones -redirect_from: - - /articles/differences-between-commit-views - - /github/committing-changes-to-your-project/differences-between-commit-views -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -En {% data variables.product.product_name %}, puedes ver el historial de confirmaciones de un repositorio al: - -- Navegar directamente hasta [la página de confirmaciones](https://github.com/mozilla/rust/commits/master) de un repositorio -- Hacer clic en un archivo y luego hacer clic en **History** (Historial), para ir al [historial de confirmaciones para un archivo específico](https://github.com/mozilla/rust/commits/master/README.md) - -Es posible que estas dos vistas de confirmación muestren información _diferente_ ocasionalmente. El historial de un archivo único puede omitir confirmaciones que se encuentran en el historial de confirmaciones del repositorio. - -Git tiene diferentes maneras de mostrar el historial de un repositorio. Cuando Git muestra el historial de un archivo único, lo "simplifica" omitiendo las confirmaciones que no generaron cambios en el archivo. En lugar de analizar todas las confirmaciones para decidir si afectaron el archivo o no, Git omitirá la rama completa en caso de que esta, cuando se fusionó, no haya tenido impacto en el contenido final del archivo. No se muestra ninguna confirmación en la rama que haya afectado el archivo. - -Para el historial de confirmaciones de un archivo, {% data variables.product.product_name %} sigue explícitamente esta estrategia simple. Simplifica el historial al eliminar las confirmaciones que en realidad no contribuyen al resultado final. Por ejemplo, si una rama lateral ha realizado un cambio y luego lo ha revertido, esa confirmación no se mostrará en el historial de la rama. Esto permite que la revisión de las ramas sea más eficiente, dado que solo ves las confirmaciones que afectan al archivo. - -Ws posible que esta vista truncada no contenga la información que estás buscando. Si deseas ver el historial completo, {% data variables.product.product_name %} proporciona una vista con más información acerca de la página de confirmaciones de un repositorio. - -Para obtener más información acerca de cómo Git considera el historial de confirmaciones, consulta la sección [ "Simplificación del historial"](https://git-scm.com/docs/git-log#_history_simplification) del artículo de ayuda de `git log`. - -### Leer más - -- "[Firmar confirmaciones](/articles/signing-commits)" -- "[Buscar confirmaciones](/articles/searching-commits)" diff --git a/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/index.md b/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/index.md deleted file mode 100644 index ffc1f6406e..0000000000 --- a/translations/es-XL/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Ver y comparar confirmaciones de cambios -intro: '' -redirect_from: - - /articles/viewing-and-comparing-commits -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /commit-branch-and-tag-labels - - /comparing-commits - - /differences-between-commit-views ---- - diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md deleted file mode 100644 index ba24184feb..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Acerca de archivar el contenido y los datos en GitHub -intro: 'Puedes archivar contenido y datos en {% data variables.product.product_name %} para que otras personas puedan verlos y hacer referencia.' -redirect_from: - - /articles/about-archiving-content-and-data-on-github - - /github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github -versions: - free-pro-team: '*' -topics: - - Repositories ---- -### Persistencia de repositorios públicos - -{% data variables.product.product_name %} intenta mantener disponibles tus repositorios públicos, a menos que los elimines. En algunos casos, hacemos que el contenido público no esté disponible, por ejemplo si: - -- Recibimos un [aviso de retiro de DMCA](/articles/dmca-takedown-policy) para el contenido en un repositorio. -- Determinamos que el contenido de un repositorio viola nuestras [Pautas de la comunidad](/articles/github-community-guidelines) o nuestros [Términos de servicio](/articles/github-terms-of-service/). - -Académicos e investigadores pueden hacer referencia a esta información en los planes de administración de datos. - -### Acerca de {% data variables.product.prodname_archive %} - -{% data reusables.repositories.about-github-archive-program %} - -El {% data variables.product.prodname_archive %} permite que los socios terceros archiven repositorios públicos utilizando la API pública. Estos socios archivan diferentes tipos de datos en frecuencias variables y hacen que éstos estén disponibles al público. El {% data variables.product.prodname_archive %} también protege los datos constantemente al almacenar varias copias de ellos en formatos de datos y ubicaciones diversas. Por ejemplo, {% data variables.product.company_short %} almacena repositorios en el {% data variables.product.prodname_arctic_vault %}, un archivo de muy largoplazo que pretende durar por lo menos 1,000 años. Para obtener más información, consulta [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com/). - -El uso responsable de los archivos incluye respetar la privacidad de los usuarios. Para obtener más información, consulta "[Información pública sobre GitHub](/articles/github-privacy-statement/#public-information-on-github)". - -Puedes optar por que tu repositorio salga del {% data variables.product.prodname_archive %}. Para obtener más información, consulta la sección "[Optar por que tu repositorio público entre o salga del {% data variables.product.prodname_archive %}](/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository)". - -### Agregar una licencia de código abierto para aumentar la capacidad de archivado - -Bibliotecas e investigadores pueden requerir protecciones legales para crear archivos de contenido disponible públicamente. Si quieres que terceros consideren tu trabajo en {% data variables.product.product_name %} para archivado, puedes agregar una [licencia de código abierto](/articles/open-source-licensing) a tus proyectos. Una licencia de código abierto le brinda a los colaboradores permisos explícitos para copiar y distribuir el material en tu repositorio. diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/about-archiving-repositories.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/about-archiving-repositories.md deleted file mode 100644 index 9e8760ea3e..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/about-archiving-repositories.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Acerca de archivar repositorios -intro: 'Cuando archivas un repositorio, le dejas saber a las personas que un proyecto ya no se mantiene activamente.' -redirect_from: - - /articles/about-archiving-repositories - - /github/creating-cloning-and-archiving-repositories/about-archiving-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% if currentVersion == "free-pro-team@latest" %} -{% note %} - -**Nota:** Si tienes un plan de facturación por repositorio heredado, aún así se te cobrará por tu repositorio archivado. Si no quieres que se te cobre por un repositorio archivado, debes actualizar a un producto nuevo. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)". - -{% endnote %} -{% endif %} - -{% data reusables.repositories.archiving-repositories-recommendation %} - -Una vez que se archiva un repositorio, no puedes agregar ni eliminar colaboradores ni equipos. Solo los colaboradores con acceso al repositorio pueden bifurcar o iniciar tu proyecto. - -Cuando se archiva un repositorio, sus propuestas, solicitudes de extracción, códigos, etiquetas, hitos, proyectos, wiki, lanzamientos, confirmaciones de cambios, rótulos, ramas, reacciones y comentarios son 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)". - -### Leer más -- "[Archivar repositorios](/articles/archiving-repositories)" diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/archiving-repositories.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/archiving-repositories.md deleted file mode 100644 index 83d75ebcc0..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/archiving-repositories.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Archivar repositorios -intro: Puedes archivar un repositorio para que sea de solo lectura para todos los usuarios e indicar que ya no necesita mantenerse activamente. También puedes desarchivar los repositorios que han sido archivados. -redirect_from: - - /articles/archiving-repositories - - /github/creating-cloning-and-archiving-repositories/archiving-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% data reusables.repositories.archiving-repositories-recommendation %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En "Danger Zone" (Zona de peligro), haz clic en **Archive this repository** (Archivar este repositorio) o **Unarchive this repository** (Desarchivar este repositorio. este repositorio). ![Botón Archive this repository (Archivar este repositorio)](/assets/images/help/repository/archive-repository.png) -4. Lee las advertencias. -5. Escribe el nombre del repositorio que deseas archivar o desarchivar. ![Advertencias para archivar el repositorio](/assets/images/help/repository/archive-repository-warnings.png) -6. Haz clic en **I understand the consequences, archive this repository** (Comprendo las consecuencias, archivar este repositorio). - -### Leer más -- [Acerca de Archivar repositorios](/articles/about-archiving-repositories)" diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository.md deleted file mode 100644 index b2c301404f..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Backing up a repository -intro: 'You can use{% if currentVersion != "free-pro-team@latest" %} Git and{% endif %} the API {% if currentVersion == "free-pro-team@latest" %}or a third-party tool {% endif %}to back up your repository.' -redirect_from: - - /articles/backing-up-a-repository - - /github/creating-cloning-and-archiving-repositories/backing-up-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% if currentVersion == "free-pro-team@latest" %} - -To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/v3/migrations/)." -{% else %} - -You can download and back up your repositories manually: - -- To download a repository's Git data to your local machine, you'll need to clone the repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." -- You can also download your repository's wiki. For more information, see "[Adding or editing wiki pages](/articles/adding-or-editing-wiki-pages)." - -When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your {% data variables.product.product_name %} repository to your local machine: - -- [Issues](/v3/issues/#list-issues-for-a-repository) -- [Pull requests](/v3/pulls/#list-pull-requests) -- [Forks](/rest/reference/repos#list-forks) -- [Comments](/rest/reference/issues#list-issue-comments-for-a-repository) -- [Milestones](/rest/reference/issues#list-milestones) -- [Labels](/rest/reference/issues#list-labels-for-a-repository) -- [Watchers](/rest/reference/activity#list-watchers) -- [Stargazers](/rest/reference/activity#list-stargazers) -- [Projects](/v3/projects/#list-repository-projects) -{% endif %} - -Once you have {% if currentVersion != "free-pro-team@latest" %}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/). - -{% if currentVersion == "free-pro-team@latest" %} -### Third-party backup tools - -A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." - -You can back up all of a repository's Git data (such as project files and commit history), as well as much data from {% data variables.product.product_name %} (such as issues and pull requests), with [BackHub](https://github.com/marketplace/backhub), which creates daily recurring backups of your repositories with snapshots up to 30 days back in time. BackHub is available in {% data variables.product.prodname_marketplace %}. -{% endif %} diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/index.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/index.md deleted file mode 100644 index 630b02321a..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Archivar un repositorio de GitHub -intro: 'Puedes archivar, respaldar y mencionar tu trabajo mediante {% data variables.product.product_name %}, la API o herramientas y servicios de terceros.' -redirect_from: - - /articles/can-i-archive-a-repository/ - - /articles/archiving-a-github-repository - - /enterprise/admin/user-management/archiving-and-unarchiving-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /about-archiving-repositories - - /archiving-repositories - - /about-archiving-content-and-data-on-github - - /referencing-and-citing-content - - /backing-up-a-repository ---- - diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/referencing-and-citing-content.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/referencing-and-citing-content.md deleted file mode 100644 index 2982cbdc10..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/referencing-and-citing-content.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Referenciar y citar contenido -intro: Puedes utilizar herramientas de terceros para citar y referenciar contenido en GitHub. -redirect_from: - - /articles/referencing-and-citing-content - - /github/creating-cloning-and-archiving-repositories/referencing-and-citing-content -versions: - free-pro-team: '*' -topics: - - Repositories ---- -### Emitir un identificador persistente para tu repositorio con Zenodo - -Para hacer que sea más sencillo referenciar tus repositorios en la literatura académica, puedes crear identificadores persistentes, también conocidos como Identificadores de Objetos Digitales (DOI). Puedes utilizar la herramienta de archivo de datos [Zenodo](https://zenodo.org/about) para archivar un repositorio {% data variables.product.product_name %} y emitir un DOI para el archivo. - -{% tip %} - -**Sugerencias:** -- Zenodo puede acceder solo a repositorios públicos, así que asegúrate de que el repositorio que quieres archivar sea [público](/articles/making-a-private-repository-public). -- Si quieres archivar un repositorio que le pertenece a una organización, puede que el propietario de la organización deba [aprobar el acceso](/articles/approving-oauth-apps-for-your-organization) para la aplicación Zenodo. -- Asegúrate de incluir una [licencia](/articles/open-source-licensing) en tu repositorio para que los lectores sepan cómo pueden reutilizar tu trabajo. - -{% endtip %} - -1. Navega hasta [Zenodo](http://zenodo.org/). -2. En la esquina superior izquierda de la pantalla, haz clic en **Log in** (Registrarse). ![Botón Zenodo log in (Registrarse en Zenodo)](/assets/images/help/repository/zenodo_login.png) -3. Haz clic en **Log in with GitHub** (Registrarse con GitHub). ![Registrarse en Zenodo con GitHub](/assets/images/help/repository/zenodo_login_with_github.png) -4. Revisa la información acerca de los permisos de acceso, luego haz clic en **Authorize application** (Autorizar aplicación). ![Autorizar Zenodo](/assets/images/help/repository/zenodo_authorize.png) -5. Navega hasta la [Página de GitHub de Zenodo](https://zenodo.org/account/settings/github/). ![Página de GitHub de Zenodo](/assets/images/help/repository/zenodo_github_page.png) -6. A la derecha del nombre del repositorio que quieras archivar, cambia el botón de **Off** (Apagado) a **On** (Encendido) para habilitarlo para el archivo. ![Habilitar que Zenodo archive en el repositorio](/assets/images/help/repository/zenodo_toggle_on.png) - -Zenodo archiva tu repositorio y emite un DOI nuevo cada vez que creas un {% data variables.product.product_name %} [lanzamiento](/articles/about-releases/) nuevo. Sigue los pasos en "[Creating releases](/articles/creating-releases/)" (Crear lanzamientos) para crear uno nuevo. - -### Publicitar y citar material de investigación con Figshare - -Los académicos pueden utilizar el servicio de gestión de datos [Figshare](http://figshare.com) para publicitar y citar el material de investigación. Para obtener más información, consulta el [Sitio de asistencia de Figshare](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account). diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository.md deleted file mode 100644 index fcbffc6b98..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Clonar un repositorio -intro: 'When you create a repository on {% data variables.product.product_location %}, it exists as a remote repository. You can clone your repository to create a local copy on your computer and sync between the two locations.' -redirect_from: - - /articles/cloning-a-repository - - /github/creating-cloning-and-archiving-repositories/cloning-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### Acerca de clonar un repositorio - -You can clone a repository from {% data variables.product.product_location %} to your local computer to make it easier to fix merge conflicts, add or remove files, and push larger commits. When you clone a repository, you copy the repository from {% data variables.product.product_location %} to your local machine. - -Clonar un repositorio extrae una copia integral de todos los datos del mismo que {% data variables.product.product_location %} tiene en ese momento, incluyendo todas las versiones para cada archivo y carpeta para el proyecto. You can push your changes to the remote repository on {% data variables.product.product_location %}, or pull other people's changes from {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Utilizar los comandos comunes de Git](/github/using-git/using-common-git-commands)". - -You can clone your existing repository or clone another person's existing repository to contribute to a project. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also clone a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo clone`](https://cli.github.com/manual/gh_repo_clone)" in the {% data variables.product.prodname_cli %} documentation. - -{% endtip %} -{% endif %} - -### Clonar un repositorio utilizando la línea de comando - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.copy-clone-url %} -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.command_line.change-current-directory-clone %} -{% data reusables.command_line.git-clone-url %} -{% data reusables.command_line.local-clone-created %} - -### Clonar un repositorio a {% data variables.product.prodname_desktop %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.open-with-github-desktop %} -4. Sigue las indicaciones en {% data variables.product.prodname_desktop %} para completar la clonación. - -Para obtener más información, consulta "[Clonar un repositorio de {% data variables.product.prodname_dotcom %} a {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". - -### Clonar un repositorio vacío - -Un repositorio vacío no contiene archivos. Habitualmente se hace si no inicias el repositorio con un README antes de crearlo. - -{% data reusables.repositories.navigate-to-repo %} -2. Para clonar tu repositorio utilizando la línea de comandos a través de HTTPS, debajo de "Configuración rápida", da clic en {% octicon "clippy" aria-label="The clipboard icon" %}. Para clonar el repositorio utilizando una llave SSH{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, incluyendo un certificado emitido por la autoridad de certificados SSH de tu organización, {% endif %} da clic en **SSH**, y luego da clic en {% octicon "clippy" aria-label="The clipboard icon" %}. ![Botón de URL de clon de repositorio vacío](/assets/images/help/repository/empty-https-url-clone-button.png) - - Como alternativa, para clonar tu repositorio en el escritorio, da clic en {% octicon "desktop-download" aria-label="The desktop download button" %} **Configurar en el escritorio** y sigue las indicaciones para completar el clon. ![Botón de escritorio para clonar repositorio vacío](/assets/images/help/repository/empty-desktop-clone-button.png) - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.command_line.change-current-directory-clone %} -{% data reusables.command_line.git-clone-url %} -{% data reusables.command_line.local-clone-created %} - - -### Solucionar los errores de clonado - -Cuando clonas un repositorio, es posible que puedas encontrar algunos errores. - -Si no puedes clonar un repositorio, revisa que: - -- Puedas conectarte utilizando HTTPS. Para obtener más información, consulta la sección "[Errores de clonado de HTTPS](/github/creating-cloning-and-archiving-repositories/https-cloning-errors)". -- Tienes permiso para acceder al repositorio que quieres clonar. Para obtener más información, consulta la sección "[Error: Repositorio no encontrado](/github/creating-cloning-and-archiving-repositories/error-repository-not-found)". -- La rama predeterminada que quieres clonar aún existe. Para obtener más información, verifica que tienes permiso para acceder al repositorio que quieres clonar. Para obtener más información, consulta "[Error: El HEAD remoto se refiere a una ref inexistente, imposible registrar](/github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout)", - - -{% if currentVersion == "free-pro-team@latest" %} - -### Leer más - -- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)" -{% endif %} diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md deleted file mode 100644 index 66d2400276..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: 'Error: HEAD remoto remite a una referencia que no existe, imposible de controlar' -intro: 'Este error ocurre si la rama por defecto de un repositorio se ha eliminado en {% data variables.product.product_location %}.' -redirect_from: - - /articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout - - /github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Es muy fácil detectar este error; Git te dará una advertencia cuando intentes clonar el repositorio: - -```shell -$ git clone https://{% data variables.command_line.codeblock %}/user/repo.git -# Clone a repo -> Cloning into 'repo'... -> remote: Counting objects: 66179, done. -> remote: Compressing objects: 100% (15587/15587), done. -> remote: Total 66179 (delta 46985), reused 65596 (delta 46402) -> Receiving objects: 100% (66179/66179), 51.66 MiB | 667 KiB/s, done. -> Resolving deltas: 100% (46985/46985), done. -> warning: remote HEAD refers to nonexistent ref, unable to checkout. -``` - -Para resolver el error, es necesario que seas un administrador del repositorio en {% data variables.product.product_location %}. Desearás [cambiar la rama por defecto](/articles/setting-the-default-branch) del repositorio. - -Luego de hacerlo, puedes obtener una lista de todas las ramas disponibles en la línea de comando: - -```shell -$ git branch -a -# Lists ALL the branches -> remotes/origin/awesome -> remotes/origin/more-work -> remotes/origin/new-master -``` - -Luego, puedes pasar a tu nueva rama: - -```shell -$ git checkout new-master -# Create and checkout a tracking branch -> Branch new-master set up to track remote branch new-master from origin. -> Switched to a new branch 'new-master' -``` diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/error-repository-not-found.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/error-repository-not-found.md deleted file mode 100644 index 07e4c05d0c..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/error-repository-not-found.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: 'Error: Repositorio no encontrado' -intro: '{% if currentVersion == "free-pro-team@latest" %}Si ves este error cuando estás clonando un repositorio, significa que el repositorio no existe o que no tienes permiso para acceder a él. Hay pocas soluciones para este error, dependiendo de la causa.{% else %}Si ves este error cuando estás clonando un repositorio, significa que el repositorio no existe, que no tienes permiso para acceder a él, o que tu instancia de GitHub Enterprise se encuentra en modo privado. Hay pocas soluciones para este error, dependiendo de la causa.{% endif %}' -redirect_from: - - /articles/error-repository-not-found - - /github/creating-cloning-and-archiving-repositories/error-repository-not-found -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### Comprueba que no haya errores tipográficos - -Los errores tipográficos suceden, y los nombres de los repositorios distinguen mayúsculas de minúsculas. Si intentas clonar `git@{% data variables.command_line.codeblock %}:user/repo.git`, pero el repositorio se llama en realidad `User/Repo` recibirás este error. - -Para evitar este error, cuando clonas, copia y pega siempre la URL del clon desde la página del repositorio. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". - -Para actualizar el remoto en un repositorio existente, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)". - -### Comprobar tus permisos - -Si estás tratando de clonar un repositorio privado pero no tienes permiso para ver el repositorio, recibirás este error. - -Verifica si tienes acceso al repositorio de alguna de las siguientes maneras: - -* Como propietario del repositorio -* Como [colaborador](/articles/inviting-collaborators-to-a-personal-repository) del repositorio -* Como [miembro de un equipo](/articles/adding-organization-members-to-a-team) que tiene acceso al repositorio (si el repositorio pertenece a una organización) - -### Comprueba tu acceso SSH - -En muy raros casos, es posible que no tengas el acceso SSH correcto al repositorio. - -Debes asegurarte de que la clave SSH que estás usando se encuentre conectada con tu usuario de {% data variables.product.product_name %}. Para comprobarlo, escribe lo siguiente en la línea de comando: - -```shell -$ ssh -T git@{% data variables.command_line.codeblock %} -> Hi username! Has autenticado con éxito, pero GitHub no -> proporciona acceso al shell. -``` - -Si el repositorio pertenece a una organización y estás utilizando una llave SSH generada por una OAuth App, puede que algún dueño de la organización haya restringido el acceso OAuth App. Para obtener más información, consulta la sección "Acerca de las restricciones al acceso OAuth App". - -Para obtener más información, consulta "[Agregar una nueva clave SSH a tu cuenta de GitHub](/articles/adding-a-new-ssh-key-to-your-github-account)". - -{% if currentVersion != "free-pro-team@latest" %} - -### Comprueba si tu instancia se encuentra en el modo privado - -Si tu administrador del sitio ha habilitado el modo privado en tu instancia de GitHub Enterprise, los clones anónimos creados sobre `git://` se inhabilitarán. Si no puedes clonar un repositorio, comunícate con el administrador de tu sitio. - -{% endif %} - -### Comprueba que el repositorio realmente exista - -Si nada de lo anterior funciona, verifica que el repositorio realmente exista en {% data variables.product.product_location %}. Si estás intentando subir a un repositorio que no existe, se producirá este error. diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/https-cloning-errors.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/https-cloning-errors.md deleted file mode 100644 index 89324f4d68..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/https-cloning-errors.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Errores de clonación de HTTPS -intro: Existen algunos errores comunes cuando se utiliza HTTPS con Git. Estos errores suelen indicar que tienes una versión antigua de Git o que no tienes acceso al repositorio. -redirect_from: - - /articles/error-the-requested-url-returned-error-403/ - - /articles/error-the-requested-url-returned-error-401/ - - /articles/error-did-you-run-git-update-server-info-on-the-server/ - - /articles/error-the-requested-url-returned-error-403-while-accessing-https-github-com-user-repo-git-info-refs/ - - /articles/https-cloning-errors - - /github/creating-cloning-and-archiving-repositories/https-cloning-errors -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Aquí aparece un ejemplo de un error de HTTPS que puedes recibir: - -```shell -> error: La URL solicitada generó el error: 401 al intentar acceder a -> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs?service=git-receive-pack -> fatal: la solicitud de HTTP falló -``` - -```shell -> Error: La URL solicitada generó el error: 403 al intentar acceder a -> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs -> fatal: la solicitud de HTTP falló -``` - -```shell -> Error: https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs no encontrado: ¿ejecutaste git -> update-server-info en el servidor? -``` - -### Comprueba tu versión de Git - -No hay una versión mínima de Git que sea necesaria para interactuar con {% data variables.product.product_name %}, pero hemos descubierto que la versión 1.7.10 es una versión estable y cómoda que está disponible en muchas plataformas. Siempre puedes [descargar la última versión en el sitio web de Git](https://git-scm.com/downloads). - -### Asegúrate de que el remoto sea correcto - -El repositorio que estás tratando de extraer debe existir en {% data variables.product.product_location %}, y la URL distingue entre mayúsculas y minúsculas. - -Puedes encontrar la URL del repositorio local abriendo la línea de comando y escribiendo `git remote -v`: - -```shell -$ git remote -v -# Visualiza los remotos existentes -> origin https://github.com/github/reactivecocoa.git (fetch) -> origin https://github.com/github/reactivecocoa.git (push) - -$ git remote set-url origin https://github.com/github/ReactiveCocoa.git -# Cambia la URL del remoto 'origen' - -$ git remote -v -# Verifica la nueva URL remota -> origin https://github.com/github/ReactiveCocoa.git (fetch) -> origin https://github.com/github/ReactiveCocoa.git (push) -``` - -Como alternativa, puedes cambiar la URL a través de nuestra aplicación [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). - -### Proporciona un token de acceso - -Para acceder a {% data variables.product.prodname_dotcom %}, debes autenticarte con un token de acceso personal en vez de con tu contraseña. 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)". - -{% data reusables.command_line.provide-an-access-token %} - -### Comprueba tus permisos - -Cuando se te solicite un nombre de usuario y contraseña, asegúrate de usar una cuenta que tenga acceso al repositorio. - -{% tip %} - -**Tip**: Si no quieres ingresar tu nombre de usuario y contraseña cada vez que interactúes con el repositorio remoto, puedes activar el [almacenamiento en caché de las contraseñas](/github/using-git/caching-your-github-credentials-in-git). - -{% endtip %} - -### Usar SSH en su lugar - -Si ya has configurado claves SSH, puedes usar el clon SSH en lugar de HTTPS. Para obtener más información, consulta "[¿Qué URL remota debo usar?](/articles/which-remote-url-should-i-use)" diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/index.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/index.md deleted file mode 100644 index a6b67c9671..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Clonar un repositorio desde GitHub -intro: 'Puedes clonar un repositorio remoto desde tu máquina local. Si encuentras errores, existen algunas soluciones de problemas comunes.' -redirect_from: - - /articles/cloning-a-repository-from-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /cloning-a-repository - - /https-cloning-errors - - /error-repository-not-found - - /error-remote-head-refers-to-nonexistent-ref-unable-to-checkout ---- - diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners.md deleted file mode 100644 index a795678597..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Acerca de los propietarios del código -intro: Puedes usar un archivo CODEOWNERS para definir individuos o equipos que sean responsables del código en un repositorio. -redirect_from: - - /articles/about-codeowners/ - - /articles/about-code-owners - - /github/creating-cloning-and-archiving-repositories/about-code-owners -product: '{% data reusables.gated-features.code-owners %}' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -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. Cuando el propietario del código es un equipo, ese equipo debe 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 - -Cuando alguien abre una solicitud de extracción que modifica el código que pertenece a alguien, automáticamente se les solicita una revisión a los propietarios del mismo. Lo que no se solicita automáticamente a estos propietarios es la revisión de los borradores de solicitudes de extracción. Para obtener más información acerca de las solicitudes de extracción en borrador "[Acerca de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". Se notificará automáticamente a los dueños del código cuando marques un borrador de solicitud de extracción como listo para revisión. Si conviertes una solicitud de extracción en borrador, las personas que ya estén suscritas a las notificaciones no se darán de baja automáticamente. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request)". - -Cuando alguien con permisos administrativos o de propietario ha activado las revisiones requeridas, opcionalmente, también pueden solicitar aprobación de un propietario del código antes de que el autor pueda fusionar una solicitud de extracción en el repositorio. Para obtener más información, consulta la sección "[Habilitar revisiones requeridas para solicitudes de extracción](/github/administering-a-repository/enabling-required-reviews-for-pull-requests)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Si un equipo habilitó las tareas de revisión de código, las aprobaciones individuales no satisfarán el requisito de aprobación del propietario del código en una rama protegida. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)".{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -Si un archivo tiene un propietario del código, puedes ver quién es éste antes de que abras una solicitud de extracción. In the repository, you can browse to the file and hover over -{% octicon "shield-lock" aria-label="The edit icon" %}. - -![Dueño del código de un archivo en un repositorio](/assets/images/help/repository/code-owner-for-a-file.png) -{% endif %} - -### Ubicación del archivo CODEOWNERS - -Para usar un archivo CODEOWNERS, crea un archivo nuevo llamado `CODEOWNERS` en la raíz, `docs/`, o en el directorio `.github/` del repositorio, en la rama en la que quieras agregar los propietarios del código. - -Cada archivo CODEOWNERS asigna los propietarios del código para una única rama en el repositorio. Por lo tanto, puedes asignar propietarios diferentes para el código en ramas diferentes, tal como `@octo-org/codeowners-team` para una base de código en la rama predeterminada y `@octocat` para un sitio de {% data variables.product.prodname_pages %} en la rama de `gh-pages`. - -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`. - -### Sintáxis de CODEOWNERS - -Un archivo CODEOWNERS usa un patrón que sigue las mismas reglas usadas en los archivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format). 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`. 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. Las sintaxis inválidas contemplan a los comentarios dentro de las líneas y a los nombres de usuario o equipo que no existen en {% data variables.product.product_name %}. -#### Ejemplo de un archivo CODEOWNERS -``` -# Este es un comentario. -# Cada línea es el patrón de un archivo seguido por uno o más propietarios. - -# Estos propietarios serán los propietarios predeterminados para todo en # el repositorio. A menos que una coincidencia posterior tenga prioridad, se le solicitará # revisión a # @global-owner1 y @global-owner2 cuando alguien abra una solicitud de extracción. -* @global-owner1 @global-owner2 - -# El orden es importante; el último patrón en coincidir tiene la mayor -# prioridad. Cuando alguien abre una solicitud de extracción que solo -# modifica archivos JS, solo se le solicitará una revisión a @js-owner y no al/los # propietario(s) general(es). -*.js @js-owner - -# Si prefieres, también puedes usar direcciones de correo electrónico. Serán -# usadas para buscar usuarios como hacemos para los -# correos electrónicos del autor de la confirmación. -*.go docs@example.com - -# En este ejemplo, @doctocat posee cualquier archivo en el -# directorio build/logs en la raíz del repositorio y cualquiera de sus -# subdirectorios. -/build/logs/ @doctocat - -# El patrón `docs/*` coincidirá con archivos como -# `docs/getting-started.md` pero no con otros archivos anidados como -# `docs/build-app/troubleshooting.md`. -docs/* docs@example.com - -# En este ejemplo, @octocat posee cualquier archivo en el directorio de las apps -# en cualquier lugar en tu repositorio. -apps/ @octocat - -# En este ejemplo, @doctocat posee cualquier archivo en el -# directorio `/docs` en la raíz de tu repositorio. -/docs/ @doctocat -``` - -### Leer más - -- "[Crear archivos nuevos](/articles/creating-new-files)" -- "[Invitar colaboradores a un repositorio personal](/articles/inviting-collaborators-to-a-personal-repository)" -- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" -- "[Administrar el acceso del equipo al repositorio de una organización](/articles/managing-team-access-to-an-organization-repository)" -- "[Ver la revisión de una solicitud de extracción](/articles/viewing-a-pull-request-review)" diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes.md deleted file mode 100644 index 11193d0cde..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Acerca de los archivos README -intro: 'Puedes agregar un archivo README a tu repositorio para comentarle a otras personas por qué tu proyecto es útil, qué pueden hacer con tu proyecto y cómo lo pueden usar.' -redirect_from: - - /articles/section-links-on-readmes-and-blob-pages/ - - /articles/relative-links-in-readmes/ - - /articles/about-readmes - - /github/creating-cloning-and-archiving-repositories/about-readmes -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Un archivo README, junto con {% if currentVersion == "free-pro-team@latest" %}una [licencia de repositorio](/articles/licensing-a-repository), [pautas de contribución](/articles/setting-guidelines-for-repository-contributors) y un [código de conducta](/articles/adding-a-code-of-conduct-to-your-project){% else %}una [licencia de repositorio](/articles/licensing-a-repository) y [pautas de contribución](/articles/setting-guidelines-for-repository-contributors){% endif %}, te ayudan a comunicar las expectativas y a administrar las contribuciones para tu proyecto. - -Un archivo README suele ser el primer elemento que verá un visitante cuando entre a tu repositorio. Los archivos README habitualmente incluyen información sobre: -- Qué hace el proyecto. -- Por qué el proyecto es útil. -- Cómo pueden comenzar los usuarios con el proyecto. -- Dónde pueden recibir ayuda los usuarios con tu proyecto -- Quién mantiene y contribuye con el proyecto. - -Si colocas tu archivo README en la raíz de tu repositorio, `docs`, o en el directorio oculto `.github`, {% data variables.product.product_name %} lo reconocerá y automáticamente expondrá tu archivo README a los visitantes del repositorio. - -![Página principal del repositorio github/scientist y su archivo README](/assets/images/help/repository/repo-with-readme.png) - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - -{% data reusables.profile.profile-readme %} - -![El archivo de README en tu nombre de usuario/repositorio de nombre de usuario](/assets/images/help/repository/username-repo-with-readme.png) - -{% endif %} - -### Enlaces de sección en los archivos README y las páginas blob - -Muchos proyectos usan un índice al comienzo de un archivo README para dirigir a los usuarios a diferentes secciones del archivo. {% data reusables.repositories.section-links %} - -### Enlaces relativos y rutas con imágenes en los archivos README - -{% data reusables.repositories.relative-links %} - -### Leer más - -- "[Agregar un archivo a un repositorio](/articles/adding-a-file-to-a-repository)" -- 18F's "[Hacer que los archivos README sean de lectura](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)" diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories.md deleted file mode 100644 index 1acb006c33..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Acerca de los repositorios -intro: Un repositorio es como una carpeta para tu proyecto. El repositorio de tu proyecto contiene todos los archivos de tu repositorio y almacena el historial de revisión de cada archivo. También puedes debatir y administrar el trabajo de tu proyecto dentro del repositorio. -redirect_from: - - /articles/about-repositories - - /github/creating-cloning-and-archiving-repositories/about-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Puedes ser propietario de repositorios individualmente o puedes compartir la propiedad de los repositorios con otras personas en una organización. - -Puedes restringir quién tiene acceso a un repositorio seleccionando la visibilidad del mismo. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". - -Para los repositorios que son propiedad de un usuario, les puedes dar a otras personas acceso de colaborador para que puedan colaborar en tu proyecto. Si un repositorio es propiedad de una organización, les puedes dar a los miembros de la organización permisos de acceso para colaborar en tu repositorio. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/)" y "[Niveles de permiso de repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)". - -{% if currentVersion == "free-pro-team@latest" %} -Con {% data variables.product.prodname_free_team %} para cuentas de usuario y de organizaciones, puedes trabajar con colaboradores ilimitados en repositorios públicos ilimitados con un juego completo de características, o en repositorios privados ilimitados con un conjunto limitado de características. Para obtener herramientas avanzadas para repositorios privados, puedes mejorar tu plan a {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, o {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} -{% else %} -Cada persona y organización puede tener repositorios ilimitados e invitar a un número ilimitado de colaboradores a todos ellos. -{% endif %} - -Puedes colaborar en tu proyecto con otros usando los tableros de proyecto, las solicitudes de extracción y las propuestas de tu repositorio. - -![Página principal del repositorio octocat/Hello-World](/assets/images/help/repository/repo-main-page.png) - -{% data reusables.repositories.repo-size-limit %} - -### Leer más - -- "[Crear un repositorio nuevo](/articles/creating-a-new-repository)" -- "[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)" -- "[Visualizar datos del repositorio con gráficos](/categories/visualizing-repository-data-with-graphs/)" -- "[Acerca de los wikis](/articles/about-wikis)" -- "[Glosario de {% data variables.product.prodname_dotcom %}](/articles/github-glossary)" diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-languages.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-languages.md deleted file mode 100644 index 2509befaba..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-languages.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Acerca de los idiomas del repositorio -intro: Los archivos y los directorios dentro de un repositorio determinan los idiomas que componen el repositorio. Puedes ver los idiomas de un repositorio para obtener una descripción general rápida del repositorio. -redirect_from: - - /articles/my-repository-is-marked-as-the-wrong-language/ - - /articles/why-isn-t-my-favorite-language-recognized/ - - /articles/my-repo-is-marked-as-the-wrong-language/ - - /articles/why-isn-t-sql-recognized-as-a-language/ - - /articles/why-isn-t-my-favorite-language-recognized-by-github/ - - /articles/about-repository-languages - - /github/creating-cloning-and-archiving-repositories/about-repository-languages -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% data variables.product.product_name %} usa la [biblioteca lingüista](https://github.com/github/linguist) de código abierto para determinar los idiomas del archivo para el resaltado de la sintaxis y las estadísticas del repositorio. Las estadísticas de lenguaje se actualizarán después de que subas los cambios a tu rama predeterminada. - -Algunos archivos son difíciles de identificar y, a veces, los proyectos contienen más archivos de biblioteca y de proveedor que su código primario. Si estás recibiendo resultados incorrectos, consulta la [Guía de solución de problemas](https://github.com/github/linguist#troubleshooting) del Lingüista para obtener ayuda. - -### Lenguaje Markup - -Los lenguajes Markup están representados para HTML y mostrados en línea usando nuestra [Biblioteca Markup](https://github.com/github/markup) de código abierto. En este momento, no estamos aceptando nuevos lenguajes para mostrar dentro de {% data variables.product.product_name %}. Sin embargo, mantenemos activamente nuestros lengujes Markup actuales. Si encuentras un problema, [crea una propuesta](https://github.com/github/markup/issues/new). diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-visibility.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-visibility.md deleted file mode 100644 index 25b0efb65b..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-visibility.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: About repository visibility -intro: 'You can restrict who has access to a repository by choosing a repository''s visibility: {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}public, internal, or private{% else %} public or private{% endif %}.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -redirect_from: - - /github/creating-cloning-and-archiving-repositories/about-repository-visibility ---- -### About repository visibility - -When you create a repository, you can choose to make the repository public or private. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you're creating the repository in an organization{% if currentVersion == "free-pro-team@latest" %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %} - -{% if currentVersion != "free-pro-team@latest" %}If {% data variables.product.product_location_enterprise %} is not in private mode or behind a firewall, p{% else %}P{% endif %}ublic repositories are accessible to everyone on the internet.{% if currentVersion != "free-pro-team@latest" %} Otherwise, public repositories are available to everyone using {% data variables.product.product_location_enterprise %}, including outside collaborators.{% endif %} Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, [certain organization members](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization). {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}Internal repositories are accessible to {% if currentVersion == "free-pro-team@latest" %}members of your enterprise account{% else %}members of any organization on your instance{% endif %}. For more information, see "[About internal repositories](#about-internal-repositories)."{% endif %} - -Organization owners always have access to every repository created in an organization. For more information, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)." - -People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -### About internal repositories - -{% note %} - -**Note:** {% data reusables.gated-features.internal-repos %} - -{% endnote %} - -{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." - -All {% if currentVersion == "free-pro-team@latest" %}enterprise members{% else %}organization members{% endif %} have read permissions to the internal repository, but internal repositories are not visible to people {% if currentVersion == "free-pro-team@latest" %}outside of the enterprise account{% else %}who are not members of an organization{% endif %}, including outside collaborators on organization repositories. For more information, see {% if currentVersion == "free-pro-team@latest" %}"[Roles for an enterprise account](/articles/roles-for-an-enterprise-account#enterprise-members)" and {% endif %}"[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)." - -{% data reusables.repositories.internal-repo-default %} - -If a user is removed from {% if currentVersion == "free-pro-team@latest" %}an enterprise account{% else %}all organizations on the instance{% endif %}, that user's forks of internal repositories are removed automatically. -{% endif %} diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository.md deleted file mode 100644 index f675477eba..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Crear un repositorio nuevo -intro: Puedes crear un repositorio nuevo en tu cuenta personal o la cuenta de cualquier organización en la que tengas los permisos suficientes. -redirect_from: - - /creating-a-repo/ - - /articles/creating-a-repository-in-an-organization/ - - /articles/creating-a-new-organization-repository/ - - /articles/creating-a-new-repository - - /articles/creating-an-internal-repository - - /github/setting-up-and-managing-your-enterprise-account/creating-an-internal-repository - - /github/creating-cloning-and-archiving-repositories/creating-an-internal-repository - - /github/creating-cloning-and-archiving-repositories/creating-a-new-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% tip %} - -**Sugerencia:** Los propietarios pueden restringir los permisos de creación de repositorios en una organización. Para obtener más información, consulta "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)". - -{% endtip %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also create a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.product_location %} documentation. - -{% endtip %} -{% endif %} - -{% data reusables.repositories.create_new %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -2. Otra opción para crear un repositorio con la estructura del directorio y los archivos de un repositorio existente es usar el menú desplegable **Elegir una plantilla** y seleccionar un repositorio de plantillas. Verás repositorios de plantillas que te pertenecen a ti y a las organizaciones de las que eres miembro o bien repositorios de plantillas que has usado anteriormente. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -3. De manera opcional, si decides utilizar una plantilla, para incluir la estructura del directorio y los archivos de todas las ramas en la misma y no solo la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %}{% endif %} -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. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %}Si no estás usando una plantilla, {% else %}hay{% endif %} una serie de elementos opcionales con los que puedes completar tu repositorio en forma previa. 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 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.15" %}agregar o crear archivos nuevos usando la interfaz de usuario o {% endif %}elegir agregar archivos nuevos usando luego la línea de comando. Para obtener más información, consulta "[Importar un repositorio Git usando la línea de comando](/articles/importing-a-git-repository-using-the-command-line/)," "[Agregar un archivo a un repositorio usando la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)," y "[Resolver 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](/articles/ignoring-files)".{% if currentVersion == "free-pro-team@latest" %} - - Puedes elegir agregar una licencia de software a tu proyecto. Para más información, consulta "[Licenciando un repositorio](/articles/licensing-a-repository)."{% endif %} -{% data reusables.repositories.select-marketplace-apps %} -{% data reusables.repositories.create-repo %} -{% if currentVersion == "free-pro-team@latest" %} -9. En la parte inferior de la página de Configuración rápida resultante, en "Importar el código del repositorio anterior", puedes elegir importar un proyecto en tu nuevo repositorio. Para hacerlo, haz clic en **Importar código**. -{% endif %} - -### Leer más - -- [Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organization-s-repositories)" -- [Guías de código abierto](https://opensource.guide/){% if currentVersion == "free-pro-team@latest" %} -- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.16" %} -- "[Initializar un repositorio vacío con un README](/articles/initializing-an-empty-repository-with-a-readme)"{% endif %} diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-repository-from-a-template.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-repository-from-a-template.md deleted file mode 100644 index 371ceb5c9f..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-repository-from-a-template.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Crear un repositorio desde una plantilla -intro: Puedes generar un nuevo repositorio con la misma estructura de directorio y los mismos archivos que un repositorio existente. -redirect_from: - - /articles/creating-a-repository-from-a-template - - /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### About repository templates - -Cualquier usuario con permisos de lectura para un repositorio de plantillas puede crear un repositorio a partir de esa plantilla. Para obtener más información, consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.product_location %} documentation. - -{% endtip %} -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -Puedes elegir incluir la estructura de directorio y archivos únicamente desde la rama predeterminada del repositorio plantilla o incluir todas las ramas. -{% endif %} - -Crear un repositorio a partir de una plantilla es similar a bifurcar un repositorio, pero existen algunas diferencias importantes: -- Una nueva bifurcación incluye todo el historial de confirmaciones del repositorio padre, mientras que un repositorio creado a partir de una plantilla comienza con una única confirmación. -- Las confirmaciones en una bifurcación no aparecen en tu gráfico de contribuciones, mientras que las confirmaciones en un repositorio creado a partir de una plantilla sí se muestran en tu gráfico de contribuciones. -- Una bifurcación puede ser una forma temporaria de contribuir código a un proyecto existente, mientras que crear un repositorio a partir de una plantilla permite iniciar rápidamente un proyecto nuevo. - -Para obtener más información acerca de las bifurcaciones, consulta "[Acerca de las bifurcaciones](/articles/about-forks)". - -### Crear un repositorio desde una plantilla - -{% data reusables.repositories.navigate-to-repo %} -2. Sobre la lista, haz clic en **Usar esta plantilla**. ![Botón Use this template button (Usar esta plantilla)](/assets/images/help/repository/use-this-template-button.png) -{% data reusables.repositories.owner-drop-down %} -{% data reusables.repositories.repo-name %} -{% data reusables.repositories.choose-repo-visibility %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -6. De manera opcional, para incluir la estructura de directorio y los archivos de todas las ramas en la plantilla, y no únicamente aquellos de la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} -{% data reusables.repositories.select-marketplace-apps %} -8. Haz clic en **Crear un repositorio a partir de una plantilla**. diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-template-repository.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-template-repository.md deleted file mode 100644 index f4337eb6b6..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-template-repository.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Creating a template repository -intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}, branches,{% endif %} and files.' -redirect_from: - - /articles/creating-a-template-repository - - /github/creating-cloning-and-archiving-repositories/creating-a-template-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -permissions: Anyone with admin permissions to a repository can make the repository a template. -topics: - - Repositories ---- -Anyone with admin permissions to a repository can make the repository a template. - -To create a template repository, you must create a repository, then make the repository a template. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)." - -After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} They can also choose to include all the other branches in your repository.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Select **Template repository**. - ![Checkbox to make a repository a template](/assets/images/help/repository/template-repository-checkbox.png) diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository.md deleted file mode 100644 index 29c1a7f31a..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Crear un repositorio solo para propuestas -intro: '{% data variables.product.product_name %} no otorga permisos de acceso solo para propuestas, pero puedes cumplir con este requisito usando un segundo repositorio que contenga solo las propuestas.' -redirect_from: - - /articles/issues-only-access-permissions/ - - /articles/is-there-issues-only-access-to-organization-repositories/ - - /articles/creating-an-issues-only-repository - - /github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -1. Crea un repositorio **privado** para alojar el código fuente de tu proyecto. -2. Crea un segundo repositorio con los permisos que deseas alojar para el usuario a cargo del seguimiento de la propuesta. -3. Agrega un archivo README al repositorio de propuestas que explique el propósito de este repositorio y establezca un enlace con la sección de las propuestas. -4. Indica a tus colaboradores o equipos que den acceso a los repositorios que desees. - -Los usuarios con acceso de escritura a ambos pueden referenciar y cerrar las propuestas a través de los repositorios, pero los usuarios que no tengan los permisos requeridos verán referencias que contienen información mínima. - -Por ejemplo, si subiste una confirmación a la rama predeterminada del repositorio privado con un mensaje que dice `Fixes organization/public-repo#12`, la propuesta se cerrará, pero solo los usuarios con los permisos adecuados verán la referencia entre los repositorios que indica la confirmación que determinó que se cerrara la propuesta. Sin los permisos sigue apareciendo una referencia, pero se omiten los detalles. diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/duplicating-a-repository.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/duplicating-a-repository.md deleted file mode 100644 index 4b85c8a5bb..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/duplicating-a-repository.md +++ /dev/null @@ -1,84 +0,0 @@ ---- -title: Duplicar un repositorio -intro: 'Para duplicar un repositorio sin bifurcarlo, puedes ejecutar un comando de clonación especial y luego subirlo en espejo al nuevo repositorio.' -redirect_from: - - /articles/duplicating-a-repo/ - - /articles/duplicating-a-repository - - /github/creating-cloning-and-archiving-repositories/duplicating-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Para que puedas duplicar un repositorio y subirlo a tu nueva copia, o _espejo_ del repositorio, antes debes [crear el nuevo repositorio](/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 - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Crea un clon desnudo de un repositorio. - ```shell - $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git - ``` -3. Sube en espejo al nuevo repositorio. - ```shell - $ cd old-repository.git - $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git - ``` -4. Eliminar el repositorio local temporal que creaste previamente. - ```shell - $ cd .. - $ rm -rf old-repository.git - ``` - -### Replicar un repositorio que contiene objetos de {% data variables.large_files.product_name_long %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Crea un clon desnudo de un repositorio. Reemplaza el nombre de usuario del ejemplo por el nombre de la persona u organización propietaria del repositorio y reemplaza el nombre del repositorio del ejemplo por el nombre del repositorio que deseas duplicar. - ```shell - $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git - ``` -3. Dirígete al repositorio que acabas de clonar. - ```shell - $ cd old-repository.git - ``` -4. Extra los objetos {% data variables.large_files.product_name_long %} del repositorio. - ```shell - $ git lfs fetch --all - ``` -5. Sube en espejo al nuevo repositorio. - ```shell - $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git - ``` -6. Sube los objetos {% data variables.large_files.product_name_long %} del repositorio a tu espejo. - ```shell - $ git lfs push --all https://github.com/exampleuser/new-repository.git - ``` -7. Eliminar el repositorio local temporal que creaste previamente. - ```shell - $ cd .. - $ rm -rf old-repository.git - ``` - -### Replicar un repositorio en otra ubicación - -Si quieres replicar un repositorio en otra ubicación, incluido obtener actualizaciones del original, puedes clonar una réplica y subir periódicamente los cambios. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Crea un clon desnudo en espejo del repositorio. - ```shell - $ git clone --mirror https://{% data variables.command_line.codeblock %}/exampleuser/repository-to-mirror.git - ``` -3. Establece la ubicación para subir en tu espejo. - ```shell - $ cd repository-to-mirror.git - $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored - ``` - -Al igual que sucede con un clon básico, un clon replicado incluye todas las ramas y etiquetas remotas, pero todas las referencias locales se sobrescribirán cada vez que extraigas elementos, por eso siempre será igual al repositorio original. El proceso para subir elementos a tu espejo se simplifica si estableces la URL para los elementos que subes. Para actualizar tu espejo, extrae las actualizaciones y súbelas. - -```shell -$ git fetch -p origin -$ git push --mirror -``` diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/index.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/index.md deleted file mode 100644 index c650361508..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/index.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Crear un repositorio en GitHub -intro: 'Luego de crear tu repositorio en {% data variables.product.product_name %}, puedes personalizar sus parámetros y su contenido.' -redirect_from: - - /articles/creating-a-repository-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /about-repositories - - /about-repository-visibility - - /creating-a-new-repository - - /creating-a-repository-from-a-template - - /about-readmes - - /about-code-owners - - /about-repository-languages - - /licensing-a-repository - - /creating-a-template-repository - - /creating-an-issues-only-repository - - /limits-for-viewing-content-and-diffs-in-a-repository - - /duplicating-a-repository ---- - diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository.md deleted file mode 100644 index 58da48117d..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: Generar licencia para un repositorio -intro: 'Los repositorios públicos de GitHub se suelen utilizar para compartir software de código abierto. Para que tu repositorio sea verdaderamente de código abierto, tendrás que generarle una licencia. De este modo, las demás personas podrán usar, modificar y distribuir el software con libertad.' -redirect_from: - - /articles/open-source-licensing/ - - /articles/licensing-a-repository - - /github/creating-cloning-and-archiving-repositories/licensing-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Repositories ---- -### Elegir la licencia correcta - -Creamos [choosealicense.com](http://choosealicense.com), para ayudarte a entender cómo generar una licencia para tu código. Una licencia de software les informa a las demás personas lo que pueden y no pueden hacer con tu código fuente; por lo tanto, es importante tomar una decisión informada. - -No tienes la obligación de elegir una licencia. Sin embargo, sin una licencia, se aplican las leyes de derecho de autor predeterminadas, lo que implica que conservas todos los derechos de tu código fuente, y nadie puede reproducir, distribuir o crear trabajos a partir de tu trabajo. Si estás creando un proyecto de código abierto, te alentamos fuertemente a que incluyas una licencia de código abierto. La [Guía de código abierto](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) brinda más orientación para elegir la licencia correcta para tu proyecto. - -{% note %} - -**Nota:** Si publicas tu código fuente en un repositorio público de GitHub, {% if currentVersion == "free-pro-team@latest" %}de acuerdo con los [Términos de servicio](/articles/github-terms-of-service), {% endif %}otros usuarios de GitHub tienen derecho a visualizar y bifurcar tu repositorio dentro del sitio de GitHub. Si ya has creado un repositorio público y no quieres que los usuarios sigan teniendo acceso a él, puedes volver privado tu repositorio. Cuando conviertes un repositorio público en un repositorio privado, las bifurcaciones existentes o las copias locales creadas por otros usuarios seguirán existiendo. Para obtener más información, consulta "[Hacer que un repositorio público se vuelva privado](/articles/making-a-public-repository-private)". - -{% endnote %} - -### Determinar la ubicación de tu licencia - -La mayoría de las personas coloca su texto de licencia en un archivo denominado`LICENSE.txt` (o `LICENSE.md`) en la raíz del repositorio; [aquí hay un ejemplo de Hubot](https://github.com/github/hubot/blob/master/LICENSE.md). - -Algunos proyectos incluyen información acerca de sus licencias en sus README. Por ejemplo, el README de un proyecto puede incluir una nota que diga "Este proyecto cuenta con licencia conforme a los términos de la licencia MIT". - -Como buena práctica, te alentamos a que incluyas el archivo de licencia en tu proyecto. - -### Buscar en GitHub por tipo de licencia - -Puedes filtrar repositorios en función de su licencia o familia de licencia usando el calificador de `licencia` y la palabra clave exacta de la licencia: - -| Licencia | Palabra clave de la licencia | -| -------- | ------------------------------------------------------------- | -| | Academic Free License v3.0 | `afl-3.0` | -| | Apache license 2.0 | `apache-2.0` | -| | Artistic license 2.0 | `artistic-2.0` | -| | Boost Software License 1.0 | `bsl-1.0` | -| | BSD 2-clause "Simplified" license | `bsd-2-clause` | -| | BSD 3-clause "New" or "Revised" license | `bsd-3-clause` | -| | BSD 3-clause Clear license | `bsd-3-clause-clear` | -| | Creative Commons license family | `cc` | -| | Creative Commons Zero v1.0 Universal | `cc0-1.0` | -| | Creative Commons Attribution 4.0 | `cc-by-4.0` | -| | Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` | -| | Do What The F*ck You Want To Public License | `wtfpl` | -| | Educational Community License v2.0 | `ecl-2.0` | -| | Eclipse Public License 1.0 | `epl-1.0` | -| | European Union Public License 1.1 | `eupl-1.1` | -| | GNU Affero General Public License v3.0 | `agpl-3.0` | -| | GNU General Public License family | `gpl` | -| | GNU General Public License v2.0 | `gpl-2.0` | -| | GNU General Public License v3.0 | `gpl-3.0` | -| | GNU Lesser General Public License family | `lgpl` | -| | GNU Lesser General Public License v2.1 | `lgpl-2.1` | -| | GNU Lesser General Public License v3.0 | `lgpl-3.0` | -| | ISC | `isc` | -| | LaTeX Project Public License v1.3c | `lppl-1.3c` | -| | Microsoft Public License | `ms-pl` | -| | MIT | `mit` | -| | Mozilla Public License 2.0 | `mpl-2.0` | -| | Open Software License 3.0 | `osl-3.0` | -| | PostgreSQL License | `postgresql` | -| | SIL Open Font License 1.1 | `ofl-1.1` | -| | University of Illinois/NCSA Open Source License | `ncsa` | -| | 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)." - -### Detectar una licencia - -[El titular de licencia de la gema de código abierto Ruby](https://github.com/benbalter/licensee) compara el archivo *LICENSE* (LICENCIA) del repositorio con una lista corta de licencias conocidas. El titular de licencia también proporciona las [API de licencias](/v3/licenses/) y [nos da información sobre las licencias que tienen los repositorios de {% data variables.product.product_name %}](https://github.com/blog/1964-open-source-license-usage-on-github-com). Si tu repositorio utiliza una licencia que no está detallada en el [Sitio web Choose a License](http://choosealicense.com/appendix/), puedes[solicitar incluir la licencia](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). - -Si tu repositorio utiliza una licencia que está detallada en el sitio web Choose a License y no se muestra claramente en la parte superior de la página del repositorio, puede que contenga múltiples licencias u otra complejidad. Para que se detecten tus licencias, simplifica tu archivo *LICENSE* y anota la complejidad en algún otro lado, como en el archivo *README* de tu repositorio. - -### Aplicar una licencia a un repositorio con una licencia existente - -El selector de licencias solo está disponible cuando creas un proyecto nuevo en GitHub. Puedes agregar manualmente una licencia utilizando el buscador. Para obtener más información acerca de agregar una licencia a un repositorio, consulta "[Agregar una licencia a un repositorio](/articles/adding-a-license-to-a-repository)." - -![Captura de pantalla del selector de licencias en GitHub.com](/assets/images/help/repository/repository-license-picker.png) - -### Descargo - -El objetivo de los esfuerzos de generación de licencias de código abierto de GitHub es proporcionar un punto de partida para ayudarte a hacer una elección informada. GitHub muestra información de licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados y que cometemos errores como todo el mundo. Por ese motivo, GitHub proporciona la información sobre una base hipotética de "cómo es" y no da garantías al respecto de ninguna información o licencia proporcionada en función o a través de esta. Tampoco se hace responsable de los daños que surjan por el uso de la información de la licencia. Si tienes alguna pregunta al respecto de la licencia correcta para tu código o cualquier otro problema legal relacionado con esto, siempre es mejor consultar con un profesional. - -### Leer más - -- La sección de Guías de código abierto "[La parte legal del código abierto](https://opensource.guide/legal/)"{% if currentVersion == "free-pro-team@latest" %} -- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/limits-for-viewing-content-and-diffs-in-a-repository.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/limits-for-viewing-content-and-diffs-in-a-repository.md deleted file mode 100644 index 667220161f..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/limits-for-viewing-content-and-diffs-in-a-repository.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Límites para ver contenido y diferencias en un repositorio -intro: 'Determinados tipos de recursos pueden ser bastante grandes y requerir mucho procesamiento en {% data variables.product.product_name %}. Por este motivo, se establecen límites para asegurar que las solicitudes se realicen en una cantidad de tiempo razonable.' -redirect_from: - - /articles/what-are-the-limits-for-viewing-content-and-diffs-in-my-repository/ - - /articles/limits-for-viewing-content-and-diffs-in-a-repository - - /github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -La mayoría de los límites que aparecen a continuación afectan tanto {% data variables.product.product_name %} como la API. - -### Límites de texto - -Los archivos de texto de más de **1 MB** siempre se muestran como texto sin formato. 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. - -### Límites de diferencias - -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: - -- La diferencia de un archivo único no puede superar *20.000 líneas que puedes cargar* o *1 MB* 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 una diferencia única se limita a *3.000*. -- 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. - -### Límites de listas de confirmaciones - -Las páginas de vista comparada y de solicitudes de extracción muestran una lista de confirmaciones entre las revisiones de `base` y de `encabezado`. Estas listas están limitadas a **250** confirmaciones. Si superan ese límite, una nota indica que existen más confirmaciones (pero no se muestran). diff --git a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/index.md b/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/index.md deleted file mode 100644 index b5bc14589c..0000000000 --- a/translations/es-XL/content/github/creating-cloning-and-archiving-repositories/index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: 'Crear, clonar y archivar repositorios' -intro: 'Puedes elegir de entre diversas opciones de configuración cuando creas o clonas un repositorio. También puedes utilizar repositorios para archivar contenido y datos en {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /categories/repositories/ - - /categories/24/articles/ - - /categories/creating-cloning-and-archiving-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /creating-a-repository-on-github - - /cloning-a-repository-from-github - - /archiving-a-github-repository ---- -### Índice - - - - - - diff --git a/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md deleted file mode 100644 index c0a7a5dabf..0000000000 --- a/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Acerca de Mercado GitHub -intro: '{% data variables.product.prodname_marketplace %} contiene herramientas que adicionan funcionalidad y mejoran tu flujo de trabajo.' -redirect_from: - - /articles/about-github-marketplace - - /github/customizing-your-github-workflow/about-github-marketplace -versions: - fpt: '*' ---- -Puedes descubrir, explorar e instalar herramientas gratuitas y pagas, incluyendo [{% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s](/apps/differences-between-apps/) y {% data variables.product.prodname_actions %}, en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). - -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)". - -También puedes tener la opción de seleccionar una prueba gratuita de 14 días en herramientas seleccionadas. Puedes cancelar en cualquier momento durante tu prueba y no se te cobrará, pero automáticamente perderás acceso a la herramienta. Tu suscripción paga comenzará al finalizar la prueba de 14 días. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". - -{% data variables.product.prodname_github_app %}s y {% data variables.product.prodname_oauth_app %}s pueden ser verificadas o no verificadas. Las aplicaciones cumplen con requisitos específicos establecidos por {% data variables.product.prodname_dotcom %} y se someten a una revisión de seguridad antes de aparecer en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "[Requisitos para listar una app en GitHub Marketplace](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". - -### {% data variables.product.prodname_actions %} en {% data variables.product.prodname_marketplace %} - -Puedes descubrir, buscar e installar {% data variables.product.prodname_actions %} que otros hayan creado en {% data variables.product.prodname_marketplace %}, consulta la sección "[Buscar {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". - -Cualquiera puede enumerar una acción en {% data variables.product.prodname_marketplace %}. A diferencia de algunas aplicaciones, las {% data variables.product.prodname_actions %} que aparecen en {% data variables.product.prodname_marketplace %} nunca son verificadas por {% data variables.product.prodname_dotcom %}. - -### Crear y hacer aparecer una herramienta en {% data variables.product.prodname_marketplace %} - -Para obtener más información acerca de cómo crear tu propia herramienta para que se liste en {% data variables.product.prodname_marketplace %}, consulta las secciones de "[Aplicaciones](/apps)" y "[{% data variables.product.prodname_actions %}](/actions)". - -### Leer más - -- "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" -- "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" -- "[Soporte técnico de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" diff --git a/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md deleted file mode 100644 index 5f313d988d..0000000000 --- a/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Acerca de las integraciones -intro: 'Las integraciones son herramientas y servicios que se conectan con {% data variables.product.product_name %} para complementar y extender tu flujo de trabajo.' -redirect_from: - - /articles/about-integrations - - /github/customizing-your-github-workflow/about-integrations -versions: - fpt: '*' ---- -Puedes instalar integraciones en tu cuenta personal o en las organizaciones que posees. También puedes instalar {% data variables.product.prodname_github_app %}s de un tercero en un repositorio específico donde tengas permisos de administrador o que sea propiedad de tu organización. - -### Diferencias entre {% data variables.product.prodname_github_app %}s y {% data variables.product.prodname_oauth_app %}s - -Las integraciones pueden ser {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s o cualquiera que utilice API de {% data variables.product.product_name %} o webhooks. - -{% data variables.product.prodname_github_app %}s ofrece permisos granulares y solicita acceso solo a lo que necesita la aplicación. {% data variables.product.prodname_github_app %}s también ofrece permisos de nivel de usuario específicos que cada usuario debe autorizar de forma individual cuando se instala una aplicación o cuando el integrador cambia los permisos solicitados por la aplicación. - -Para obtener más información, consulta: -- "[Diferencias entre las {% data variables.product.prodname_github_app %}s y {% data variables.product.prodname_oauth_app %}s](/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 {% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps/)" -- "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations/)" - -Puedes instalar una {% data variables.product.prodname_github_app %} preconfigurada, si los integradores o los creadores de la aplicación han creado su aplicación con el flujo de manifiesto de {% data variables.product.prodname_github_app %}. Para obtener más información sobre cómo ejecutar tu {% data variables.product.prodname_github_app %} con configuración automatizada, comunícate con el integrador o el creador de la aplicación. - -Puedes crear una {% data variables.product.prodname_github_app %} con configuración simplificada si creas tu aplicación con Probot. Para obtener más información, consulta el sitio [Documentos de Probot](https://probot.github.io/docs/). - -### Descubrir integraciones en {% data variables.product.prodname_marketplace %} - -Puedes encontrar una integración para instalar o publicar tu propia integración en {% data variables.product.prodname_marketplace %}. - -[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contiene {% data variables.product.prodname_github_app %}s y {% data variables.product.prodname_oauth_app %}s. Para obtener más información sobre cómo encontrar una integración o cómo crear tu propia integración, consulta "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)". - -### Integraciones compradas directamente a los integradores - -También puedes comprar algunas integraciones directamente a los integradores. Como miembro de una organización, si encuentras una {% data variables.product.prodname_github_app %} que te gustaría usar, puedes solicitar que una organización apruebe o instale la aplicación para la organización. - -Si tienes permisos de administrador para todos los repositorios que son propiedad de una organización en la que la aplicación está instalada, puedes instalar {% data variables.product.prodname_github_app %}s 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-XL/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md deleted file mode 100644 index b44445be17..0000000000 --- a/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Extensiones e integraciones de GitHub -intro: 'Utiliza las extensiones {% data variables.product.product_name %} para trabajar sin inconvenientes en los repositorios {% data variables.product.product_name %} dentro de las aplicaciones de terceros.' -redirect_from: - - /articles/about-github-extensions-for-third-party-applications/ - - /articles/github-extensions-and-integrations - - /github/customizing-your-github-workflow/github-extensions-and-integrations -versions: - fpt: '*' ---- -### Herramientas del editor - -Para agilizar tu flujo de trabajo, te puedes conectar a los repositorios {% data variables.product.product_name %} dentro de las herramientas del editor de terceros, como Atom, Unity y Visual Studio. - -#### {% data variables.product.product_name %} para Atom - -Con el {% data variables.product.product_name %} para la extensión de Atom, puedes confirmar, subir, extraer, resolver conflictos de fusión y mucho más desde el editor de Atom. Para obtener más información, consulta el [{% data variables.product.product_name %} oficial para el sitio de Atom](https://github.atom.io/). - -#### {% data variables.product.product_name %} para Unity - -Con el {% data variables.product.product_name %} para la extensión del editor de Unity, puedes desarrollar en Unity, la plataforma de código abierto de desarrollo de juegos, y ver tu trabajo en {% data variables.product.product_name %}. Para obtener más información, consulta el [sitio](https://unity.github.com/) oficial de la extensión del editor de Unity o la [documentación](https://github.com/github-for-unity/Unity/tree/master/docs). - -#### {% data variables.product.product_name %} para Visual Studio - -Con el {% data variables.product.product_name %} para la extensión de Visual Studio, puedes trabajar en los repositorios {% data variables.product.product_name %} sin salir de Visual Studio. Para obtener más información, consulta el [sitio](https://visualstudio.github.com/) oficial de la extensión de Visual Studio o la [documentación](https://github.com/github/VisualStudio/tree/master/docs). - -#### {% data variables.product.prodname_dotcom %} para Visual Studio Code - -Con el {% data variables.product.prodname_dotcom %} para la extensión de Visual Studio Code, puedes revisar y administrar solicitudes de extracción {% data variables.product.product_name %} en Visual Studio Code. Para obtener más información, consulta el [sitio](https://vscode.github.com/) oficial de la extensión de Visual Studio Code o la [documentación](https://github.com/Microsoft/vscode-pull-request-github). - -### Herramientas de gestión de proyectos - -Para agilizar el flujo de trabajo, puedes integrar tu cuenta personal u organización {% data variables.product.product_name %} con herramientas de gestión de proyectos de terceros, como Jira. - -#### Integración de Jira Cloud y {% data variables.product.product_name %}.com - -Puedes integrar Jira Cloud con tu cuenta personal o de organización para escanear confirmaciones y solicitudes de extracción, y crear los metadatos e hipervínculos correspondientes en cualquiera de las propuestas de Jira mencionadas. diff --git a/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/index.md b/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/index.md deleted file mode 100644 index 460a3884e9..0000000000 --- a/translations/es-XL/content/github/customizing-your-github-workflow/exploring-integrations/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Explorar integraciones -intro: |- - Puedes personalizar y ampliar tu flujo de trabajo de {% data variables.product.product_name %} con herramientas y - servicios diseñados por la comunidad de {% data variables.product.product_name %}. -redirect_from: - - /articles/exploring-integrations -versions: - fpt: '*' -children: - - /about-integrations - - /about-github-marketplace - - /github-extensions-and-integrations ---- - diff --git a/translations/es-XL/content/github/customizing-your-github-workflow/index.md b/translations/es-XL/content/github/customizing-your-github-workflow/index.md deleted file mode 100644 index dfeab63a03..0000000000 --- a/translations/es-XL/content/github/customizing-your-github-workflow/index.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Personalizar tu flujo de trabajo de GitHub -redirect_from: - - /categories/customizing-your-github-workflow -versions: - fpt: '*' -children: - - /exploring-integrations - - /purchasing-and-installing-apps-in-github-marketplace ---- -### Índice diff --git a/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md b/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md deleted file mode 100644 index 8968e40029..0000000000 --- a/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Comprar e instalar aplicaciones en el Mercado GitHub -intro: '{% data variables.product.prodname_marketplace %} incluye apps con planes de precios gratuitos y pagos. Cuando encuentras una aplicación paga que desearías usar para tu cuenta personal u organización, puedes comprar e instalar la app utilizando tu información de facturación existente.' -redirect_from: - - /articles/purchasing-and-installing-apps-in-github-marketplace -versions: - fpt: '*' -children: - - /installing-an-app-in-your-personal-account - - /installing-an-app-in-your-organization ---- - diff --git a/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md b/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md deleted file mode 100644 index 10b5fbe317..0000000000 --- a/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Instalar una app en tu organización -intro: 'Puedes instalar apps desde {% data variables.product.prodname_marketplace %} para utilizar en tu organización.' -redirect_from: - - /articles/installing-an-app-in-your-organization - - /github/customizing-your-github-workflow/installing-an-app-in-your-organization -versions: - fpt: '*' ---- -{% data reusables.marketplace.marketplace-apps-only %} - -{% data reusables.marketplace.marketplace-org-perms %} - -Si eliges un plan pago, pagarás tu suscripción a la app en la fecha de facturación actual de tu organización usando el método de pago existente de tu organización. - -{% data reusables.marketplace.free-trials %} - -### Instalar una {% data variables.product.prodname_github_app %} en tu organización - -{% data reusables.marketplace.visit-marketplace %} -{% data reusables.marketplace.browse-to-app %} -{% data reusables.marketplace.choose-plan %} -{% data reusables.marketplace.install-buy %} -{% data reusables.marketplace.confirm-install-account-org %} -{% data reusables.marketplace.add-payment-method-org %} -{% data reusables.marketplace.complete-order-begin-installation %} -8. Si la aplicación requiere acceso a los repositorios, decide si le darás acceso a la aplicación a todos tus repositorios o a determinados repositorios, luego selecciona **All repositories** (Todos los repositorios) o **Only select repositories** (Solo repositorios seleccionados). ![Botones de radio con opciones para instalar una aplicación en todos tus repositorios o en determinados repositorios](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png) -{% data reusables.marketplace.select-installation-repos %} -{% data reusables.marketplace.review-app-perms-install %} - -### Instalar una {% data variables.product.prodname_oauth_app %} en tu organización - -{% data reusables.saml.saml-session-oauth %} - -{% data reusables.marketplace.visit-marketplace %} -{% data reusables.marketplace.browse-to-app %} -{% data reusables.marketplace.choose-plan %} -{% data reusables.marketplace.install-buy %} -{% data reusables.marketplace.confirm-install-account-org %} -{% data reusables.marketplace.add-payment-method-org %} -{% data reusables.marketplace.complete-order-begin-installation %} -8. Revisa la información acerca del acceso de la app a tu cuenta personal, a tus organizaciones y a los datos, luego haz clic en **Authorize application** (Autorizar aplicación). - -### Leer más - -- "[Actualizar el método de pago de tu organización](/articles/updating-your-organization-s-payment-method)" -- "[Instalar una app en tu cuenta personal](/articles/installing-an-app-in-your-personal-account)" diff --git a/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md b/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md deleted file mode 100644 index 68e5862dd0..0000000000 --- a/translations/es-XL/content/github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Instalar una app en tu cuenta personal -intro: 'Puedes instalar apps desde {% data variables.product.prodname_marketplace %} para utilizar en tu cuenta personal.' -redirect_from: - - /articles/installing-an-app-in-your-personal-account - - /github/customizing-your-github-workflow/installing-an-app-in-your-personal-account -versions: - fpt: '*' ---- -{% data reusables.marketplace.marketplace-apps-only %} - -Si eliges un plan pago, pagarás tu suscripción a la app en la fecha de facturación actual de tu cuenta personal usando tu método de pago existente. - -{% data reusables.marketplace.free-trials %} - -### Instalar una {% data variables.product.prodname_github_app %} en tu cuenta personal - -{% data reusables.marketplace.visit-marketplace %} -{% data reusables.marketplace.browse-to-app %} -{% data reusables.marketplace.choose-plan %} -{% data reusables.marketplace.install-buy %} -{% data reusables.marketplace.confirm-install-account-personal %} -{% data reusables.marketplace.add-payment-method-personal %} -{% data reusables.marketplace.complete-order-begin-installation %} -8. Decide si le darás acceso a la aplicación a todos tus repositorios o a determinados repositorios, luego selecciona **All repositories** (Todos los repositorios) o **Only select repositories** (Solo repositorios seleccionados). ![Botones de radio con opciones para instalar una aplicación en todos tus repositorios o en determinados repositorios](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png) -{% data reusables.marketplace.select-installation-repos %} -{% data reusables.marketplace.review-app-perms-install %} - -### Instalar una {% data variables.product.prodname_oauth_app %} en tu cuenta personal - -{% data reusables.saml.saml-session-oauth %} - -{% data reusables.marketplace.visit-marketplace %} -{% data reusables.marketplace.browse-to-app %} -{% data reusables.marketplace.choose-plan %} -{% data reusables.marketplace.install-buy %} -{% data reusables.marketplace.confirm-install-account-personal %} -{% data reusables.marketplace.add-payment-method-personal %} -{% data reusables.marketplace.complete-order-begin-installation %} -8. Revisa la información acerca del acceso de la app a tu cuenta personal y a tus datos, luego haz clic en **Authorize application** (Autorizar aplicación). - -### Leer más - -- "[Actualizar el método de pago de tu cuenta personal](/articles/updating-your-personal-account-s-payment-method)" -- "[Instalar una app en tu organización](/articles/installing-an-app-in-your-organization)" diff --git a/translations/es-XL/content/github/developing-online-with-codespaces/about-codespaces.md b/translations/es-XL/content/github/developing-online-with-codespaces/about-codespaces.md deleted file mode 100644 index 5ee95737bc..0000000000 --- a/translations/es-XL/content/github/developing-online-with-codespaces/about-codespaces.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Acerca de Codespaces -intro: '{% data variables.product.prodname_codespaces %} es un ambiente de desarrollo en línea, hospedado en {% data variables.product.prodname_dotcom %} e impulsado por {% data variables.product.prodname_vscode %}, que te permite desarrollar completamente en la nube.' -product: '{% data reusables.gated-features.codespaces %}' -redirect_from: - - /github/developing-online-with-github-codespaces/about-github-codespaces -versions: - free-pro-team: '*' ---- - -{% note %} - -**Nota:**{% data variables.product.prodname_codespaces %} actualmente está en un beta público limitado y está sujeto a cambios. Durante el periodo beta, {% data variables.product.prodname_dotcom %} no garantiza la disponibilidad de {% data variables.product.prodname_codespaces %}. Para obtener más información acerca de unirse al beta, consulta la sección "[Unirse al beta](/github/developing-online-with-codespaces/about-codespaces#joining-the-beta)". - -{% endnote %} - -### Acerca de {% data variables.product.prodname_codespaces %} - -{% data variables.product.prodname_codespaces %} es un ambiente de desarrollo en la nube que está disponible en tu buscador. Un codespace incluye todo lo que necesitas para hacer desarrollos para un repositorio específico, incluyendo un editor de texto con resaltamiento de sintaxis y auto-compleción, una terminal, herramientas de depuración, y comandos de Git, todo dentro de {% data variables.product.prodname_dotcom %}. También puedes instalar extensiones de {% data variables.product.prodname_vscode %} en tu codespace para agregar más funcionalidades. - -{% data variables.product.prodname_codespaces %} facilita la integración de desarrolladores a una nueva compañía, o el comenzar a contribuir en un proyecto de código abierto. Los mantenedores de proyecto pueden configurar un repositorio para que, cuando crees un codespace para el mismo, las dependencias de dicho proyecto se incluyan automáticamente. Puedes comenzar a crear código más rápido reduciendo el tiempo que gastas en configurar tu ambiente. - -{% data variables.product.prodname_codespaces %} te permite desarrollar en la nube en vez de hacerlo localmente. Los desarrolladores pueden contribuir desde donde sea, en cualquier máquina, incluyendo tablets o Chromebooks, y no es necesario mantener copias locales o propiedad intelectual. - -![Un codespace abierto](/assets/images/help/codespaces/codespace-overview.png) - -### Uso de {% data variables.product.prodname_codespaces %} - -Cada desarrollador puede crear uno o más codespaces para cualquier repositorio público, o para cualquier repositorio privado que pertenezca a su cuenta de usuario. {% data reusables.codespaces.unsupported-repos %} {% data reusables.codespaces.codespaces-are-personal %} - -{% data reusables.codespaces.codespaces-are-per-branch %}{% 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)". - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -{% data reusables.codespaces.about-configuration %} Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". - -{% data reusables.codespaces.about-personalization %}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)". - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -{% data reusables.codespaces.beta-functionality-limited %} - -### Acerca de la facturación para {% data variables.product.prodname_codespaces %} - -Durante el beta público limitado, {% data variables.product.prodname_codespaces %} es gratuito y los usuarios se limitarán a 2 codespaces. Los planes y precios se anunciarán antes de que esté disponible para el público en general. - -### Unirse al beta - -Se invitará a una cantidad limitada de personas para unirse al beta. Para unirse a la lista de espera, consulta la sección [Registrarse para el beta de Codespaces](https://github.com/features/codespaces/signup). - -### Contáctanos para conocer sobre {% data variables.product.prodname_codespaces %} - -Si encuentras problemas al utilizar {% data variables.product.prodname_codespaces %}, consulta la sección "[Solución de problemas para tu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)". - -Si aún necesitas ayuda o tienes algún tipo de retroalimentación sobre {% data variables.product.prodname_codespaces %}, utiliza el [Foro Comunitario](https://github.community/c/codespaces-beta/45). diff --git a/translations/es-XL/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md b/translations/es-XL/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md deleted file mode 100644 index 19f86a4684..0000000000 --- a/translations/es-XL/content/github/developing-online-with-codespaces/configuring-codespaces-for-your-project.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Configurar Codespaces para tu proyecto -intro: Puedes configurar ajustes predeterminados para cada codespace nuevo de tu repositorio para garantizar que los colaboradores tengan todas las herramientas y configuraciones que requieran en su ambiente de desarrollo en línea. -product: '{% data reusables.gated-features.codespaces %}' -permissions: Las personas con permisos de escritura en un repositorio pueden crear o editar la configuración predeterminada del codespace. -redirect_from: - - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project -versions: - free-pro-team: '*' ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de las configuraciones predeterminadas de los codespaces - -{% data reusables.codespaces.about-configuration %} - -Si no defines una configuración en tu repositorio, {% data variables.product.prodname_dotcom %} creará un codespace con una imagen base de Linux. La imagen base de Linux incluye herramientas para Node.js, JavaScript, TypeScript, Python, C++, Java, C#, .NET Core, PHP, y PowerShell. Para obtener más información acerca de la imagen base de Linux, consulta el repositorio [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers/codespaces-linux). - -{% data reusables.codespaces.about-personalization %}{% data reusables.codespaces.codespace-config-order %}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)". - -Puedes crear una configuración predeterminada para tus codespaces utilizando una configuración de contenedor pre-compilado para tu tipo de proyecto, o puedes crear una configuración personalizada específica para las necesidades de tu proyecto. - -{% data variables.product.prodname_codespaces %} utiliza una configuración que se contiene en un archivo llamado `devcontainer.json` en la raíz del repositorio o en una carpeta `.devcontainer`. Puedes utilizar `devcontainer.json` para configurar los ajustes predeterminados para todo el ambiente del codespace, incluyendo el editor de {% data variables.product.prodname_vscode %}, pero también puedes configurar los ajustes específicos para el editor en un archivo llamado `.vscode/settings.json`. - -Los cambios a la configuración de un codespace en un repositorio se aplican únicamente a cada codespace nuevo y no afectan a los ya existentes. - -### Utilizar una configuración de contenedor pre-compilado - -Puedes utilizar cualquier configuración de contenedor pre-compilado para {% data variables.product.prodname_vscode %} que se encuentre disponible en el repositorio [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers). Las definiciones de los contenedores pre-compilados incluyen una configuración común para un tipo de proyecto en particular, y pueden ayudarte a comenzar rápidamente con una configuración que ya tenga las opciones adecuadas para el contenedor, los ajustes de {% data variables.product.prodname_vscode %}, y las extensiones de {% data variables.product.prodname_vscode %} que deben estar instaladas. - -1. Clona o descarga el repositorio [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers). -1. En el repositorio `vscode-dev-containers`, navega a la carpeta [`containers`](https://github.com/microsoft/vscode-dev-containers/tree/master/containers), y luego escoge una configuración de contenedor de acuerdo con las necesidades de tu proyecto. Utilizaremos la configuración del contenedor de [Node.js & JavaScript](https://aka.ms/vscode-dev-containers/definitions/node) como ejemplo. -1. Desde la carpeta de [`Node.js & JavaScript`](https://aka.ms/vscode-dev-containers/definitions/node), copia la carpeta `.devcontainer` a la raíz del repositorio de tu proyecto. -1. Confirma y carga la nueva confirmación al repositorio de tu proyecto en {% data variables.product.prodname_dotcom %}. - -Cada coedspace nuevo que crées desde una rama que contenga la carpeta `.devcontainer` se configurará de acuerdo con el contenido de la misma. Para obtener más información, consulta la sección "[Crear un codespace](/github/developing-online-with-codespaces/creating-a-codespace)". - -### Crear una configuración personalizada para un codespace - -Si ninguna de las configuraciones pre-compiladas se ajusta a tus necesidades, puedes crear una configuración personalizada si agregas un archivo `devcontainer.json` a la raíz de tu repositorio o una carpeta `.devcontainer`. En el archivo, puedes utilizar claves de configuración compatibles para especificar aspectos del ambiente del codespace, como por ejemplo, qué extensiones de {% data variables.product.prodname_vscode %} deben instalarse. - -{% data reusables.codespaces.vscode-settings-order %} - -Puedes definir la configuración predeterminada del editor para {% data variables.product.prodname_vscode %} en dos lugares. - -* La configuración del editor que se definió en `.vscode/settings.json` se aplica como una configuración con alcance de _Workspace_- en este codespace. -* La configuración del editor que se definió en la clave `settings` en `devcontainer.json` se aplica como una configuración con alcance de _Remote [Codespaces]_ en este codespace. - -### Claves de configuración compatibles con los codespaces - -Puedes utilizar claves de configuración compatibles con {% data variables.product.prodname_codespaces %} en `devcontainer.json`. - -#### Ajustes generales - -- `name (nombre)` -- `parámetros` -- `extensions` -- `forwardPorts` -- `devPort` -- `postCreateCommand` - -#### Ajustes de Docker, Dockerfile o de imagen - -- `imagen` -- `dockerFile` -- `context` -- `containerEnv` -- `remoteEnv` -- `containerUser` -- `remoteUser` -- `updateRemoteUserUID` -- `mounts` -- `workspaceMount` -- `workspaceFolder` -- `runArgs` -- `overrideCommand` -- `shutdownAction` -- `dockerComposeFile` - -Para obtener más información acerca de los ajustes disponibles para `devcontainer.json`, consulta la sección [devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json) en la documentación de {% data variables.product.prodname_vscode %}. diff --git a/translations/es-XL/content/github/developing-online-with-codespaces/creating-a-codespace.md b/translations/es-XL/content/github/developing-online-with-codespaces/creating-a-codespace.md deleted file mode 100644 index b78ff2fb0a..0000000000 --- a/translations/es-XL/content/github/developing-online-with-codespaces/creating-a-codespace.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Crear un codespace -intro: Puedes crear un codespace para una rama en un repositorio para desarrollar en línea. -product: '{% data reusables.gated-features.codespaces %}' -permissions: 'Cualquiera puede crear un codespace para cualquier repositorio público, o para cualquier repositorio que pertenezca a su cuenta de usuario.' -redirect_from: - - /github/developing-online-with-github-codespaces/creating-a-codespace -versions: - free-pro-team: '*' ---- - -{% data reusables.codespaces.release-stage %} - -### Acerca de la creación de codespaces - -{% data reusables.codespaces.codespaces-are-personal %} - -{% data reusables.codespaces.codespaces-are-per-branch %}{% 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)". - -{% data reusables.codespaces.unsupported-repos %} - -No puedes crear un codespace en un repositorio vacío. Si tu repositorio está vacío, crea un archivo en él antes de crear un codespace. Para obtener más información, consulta la sección "[Agregar un archivo a un repositorio](/github/managing-files-in-a-repository/adding-a-file-to-a-repository)" y "[Agregar un archivo a un repositorio utilizando la línea de comandos](/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line)". - -El ambiente del codespace que crees se basará en la configuración del repositorio. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". - -{% data reusables.codespaces.about-personalization %}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)". - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.you-can-see-all-your-codespaces %} - -### Crear un codespace - -{% data reusables.repositories.navigate-to-repo %} -2. Debajo del nombre de repositorio, utiliza el menú desplegable de "Rama" y selecciona aquella en la que quieras crear un codespace. ![Menú desplegable de rama](/assets/images/help/codespaces/branch-drop-down.png) -3. Debajo del nombre del repositorio, utiliza el menú desplegable {% octicon "download" aria-label="The download icon" %} **Código**, y selecciona **Abrir con codespaces**. ![Botón de abrir con codespaces](/assets/images/help/codespaces/open-with-codespaces-button.png) -4. Si ya tienes un codespace para la rama, da clic en {% octicon "plus" aria-label="The plus icon" %}**Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) diff --git a/translations/es-XL/content/github/developing-online-with-codespaces/deleting-a-codespace.md b/translations/es-XL/content/github/developing-online-with-codespaces/deleting-a-codespace.md deleted file mode 100644 index d88aedb811..0000000000 --- a/translations/es-XL/content/github/developing-online-with-codespaces/deleting-a-codespace.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Borrar un codespace -intro: Puedes borrar un codespace que ya no necesites. -product: '{% data reusables.gated-features.codespaces %}' -permissions: Cualquiera puede borrar un codespace que pertenezca a su cuenta de usuario. -redirect_from: - - /github/developing-online-with-github-codespaces/deleting-a-codespace -versions: - free-pro-team: '*' ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.concurrent-codespace-limit %} - -{% data reusables.codespaces.navigate-to-codespaces %} -2. A la derecha del codespace que quieras borrar, da clic en **Borrar**. ![Botón de borrar](/assets/images/help/codespaces/delete-codespace.png) diff --git a/translations/es-XL/content/github/developing-online-with-codespaces/developing-in-a-codespace.md b/translations/es-XL/content/github/developing-online-with-codespaces/developing-in-a-codespace.md deleted file mode 100644 index 90ebc6c5bb..0000000000 --- a/translations/es-XL/content/github/developing-online-with-codespaces/developing-in-a-codespace.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Desarrollar en un codespace -intro: 'Puedes abrir un codespace en {% data variables.product.product_name %} y después desarrollar utilizando las características de {% data variables.product.prodname_vscode %}.' -product: '{% data reusables.gated-features.codespaces %}' -permissions: Cualquiera puede desarrollar en un codespace que pertenezca a su cuenta de usuario. -redirect_from: - - /github/developing-online-with-github-codespaces/developing-in-a-codespace -versions: - free-pro-team: '*' ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.use-visual-studio-features %} - -{% data reusables.codespaces.use-chrome %} Para obtener más información, consulta la sección "[Solucionar problemas de tu codespace](/github/developing-online-with-codespaces/troubleshooting-your-codespace)". - -### Conectarse a un codespace desde {% data variables.product.prodname_vscode %} -{% data reusables.codespaces.connect-to-codespace-from-vscode %} - -### Navegar a tu codespace -{% data reusables.codespaces.navigate-to-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) - -### Puertos de redireccionamiento - -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 en el puerto 3000, puedes acceder a la aplicación desde tu buscador para probarla y depurarla. - -Cuando una aplicación que se ejecuta dentro de un codespace tiene una salida en un puerto de la consola, {% data variables.product.prodname_codespaces %} detecta el patrón de la URL del localhost y redirecciona esos puertos automáticamente. Puedes dar clic en la URL dentro de la terminal para abrirla en un buscador. Por ejemplo, si una aplicación da como salida `http://127.0.0.1:3000` o `http://localhost:3000` en la consola, la bitácora convertirá la salida automáticamente en una URL para el puerto 3000 en la que se puede dar clic. - -![Reenvío Automático de Puertos](/assets/images/help/codespaces/automatic-port-forwarding.png) - -Como alternativa, también puedes utilizar cualquiera de las siguientes formas para redirigir un puerto. - -* Puedes redirigir un puerto bajo demanda si activas la paleta de comandos (`shift command P` / `shift control P`) y tecleas "Codespaces: Forward Port". Entonces puedes ingresar el número del puerto que quieras redirigir. - - ![Paleta de Comandos para la Redirección de Puertos](/assets/images/help/codespaces/command-palette-port-forwarding.png) - -* Puedes configurar automáticamente los puertos en un archivo de `.devcontainer.json` utilizando la propiedad `forwardPorts`. - -* Puedes agregar o eliminar los puertos redirigidos dentro de la extensión de Explorador Remoto. Desde el Explorador Remoto, puedes copiar y pegar las URL para los puertos redirigidos, lo cual te permite acceder a ellos a través de tu buscador. - - ![Redirección de Puertos para el Explorador Remoto](/assets/images/help/codespaces/remote-explorer-port-forwarding.png) diff --git a/translations/es-XL/content/github/developing-online-with-codespaces/index.md b/translations/es-XL/content/github/developing-online-with-codespaces/index.md deleted file mode 100644 index a11c47bb92..0000000000 --- a/translations/es-XL/content/github/developing-online-with-codespaces/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: 'Desarrollar en línea con {% data variables.product.prodname_codespaces %}' -shortTitle: Codespaces -intro: 'Puedes desarrollar íntegramente en la nube utilizando {% data variables.product.prodname_codespaces %}, un ambiente de desarrollo integrado (IDE) en {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.codespaces %}' -redirect_from: - - /github/developing-online-with-github-codespaces -versions: - free-pro-team: '*' -children: - - /about-codespaces - - /configuring-codespaces-for-your-project - - /creating-a-codespace - - /developing-in-a-codespace - - /personalizing-codespaces-for-your-account - - /deleting-a-codespace - - /troubleshooting-your-codespace - - /connecting-to-your-codespace-from-visual-studio-code ---- -{% data reusables.codespaces.release-stage %} -### Índice diff --git a/translations/es-XL/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md b/translations/es-XL/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md deleted file mode 100644 index c81d552238..0000000000 --- a/translations/es-XL/content/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Personalizar Codespaces para tu cuenta -intro: '{% data variables.product.prodname_codespaces %} utiliza tu repositorio de `dotfiles` en {% data variables.product.product_name %} para personalizar cualquier codespace nuevo que crees.' -product: '{% data reusables.gated-features.codespaces %}' -permissions: 'Cualquiera puede crear un repositorio `dotfiles` para personalizar {% data variables.product.prodname_codespaces %} para su cuenta de usuario.' -redirect_from: - - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account -versions: - free-pro-team: '*' ---- - -{% data reusables.codespaces.release-stage %} - -Los Dotfiles son archivos y carpetas de sistemas parecidos a Unix que comienzan con `.` y que controlan la configuración de aplicaciones y shells de tu sistema. Puedes alamacenar y administrar tus dotfiles en un repositorio en {% data variables.product.prodname_dotcom %}. Para encontrar consejos y tutoriales sobre qué incluir en tu repositorio de `dotfiles`, consulta la sección [GitHub maneja dotfiles](https://dotfiles.github.io/). - -Si tu cuenta de usuario en {% data variables.product.prodname_dotcom %} es propietaria de un repositorio público llamado `dotfiles`, {% data variables.product.prodname_dotcom %} utilizará este repositorio automáticamente para personalizar el ambiente de tu codespace. Actualmente, no son compatibles los repositorios `dotfiles` privados. - -Tu repositorio `dotfiles` puede incluir los alias de tu shell y tus preferencias, cualquier herramienta que quieras instalar, o cualquier otra personalización del codespace que quieras hacer. - -La personalización de codespaces utilizando el repositorio `dotfiles` aplica a cualquier codespace que crees. Los mantenendores de proyecto también pueden definir una configuración predeterminada que aplique a cada codespace para un repositorio que cree alguien más. {% data reusables.codespaces.codespace-config-order %} Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project)". - -Cuando creas un codespace nuevo, {% data variables.product.prodname_dotcom %} clona tu repositorio `dotfiles` hacia el ambiente del codespace, y busca uno de los siguientes archivos para configurar el ambiente. - -* _install.sh_ -* _install_ -* _bootstrap.sh_ -* _bootstrap_ -* _setup.sh_ -* _setup_ - -Si no encuentra alguno de estos archivos, entonces cualquier archivo o carpeta en `dotfiles` que comience con `.` se enlazará simbólicamente al directorio `~` o `$HOME` del codespace. - -Cualquier cambio a tu repositorio `dotfiles` se aplicará únicamente a cada codespace nuevo, y no afectará a ningún codespace existente. - -Para obtener más información, consulta la sección "[Personalizing](https://docs.microsoft.com/en-us/visualstudio/online/reference/personalizing) en la documentación de {% data variables.product.prodname_vscode %}. - -{% note %} - -**Nota:** Actualmente, {% data variables.product.prodname_codespaces %} no es compatible con la personalización de la configuración de _Usuario_ para el editor de {% data variables.product.prodname_vscode %} con tu repositorio de `dotfiles`. Puedes configurar ajustes predeterminados de _Workspace_ y _Remote [Codespaces]_ para un proyecto específico en el repositorio de éste. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_codespaces %} para tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-codespace-configuration)". - -{% endnote %} - - -### Leer más - -* "[Crear un repositorio nuevo](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)". diff --git a/translations/es-XL/content/github/developing-online-with-codespaces/troubleshooting-your-codespace.md b/translations/es-XL/content/github/developing-online-with-codespaces/troubleshooting-your-codespace.md deleted file mode 100644 index 6772936e6a..0000000000 --- a/translations/es-XL/content/github/developing-online-with-codespaces/troubleshooting-your-codespace.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Solucionar problemas de tu codespace -intro: Puedes solucionar los problemas de un codespace si revisas los problemas conocidos en el repositorio `microsoft/vscode`. -product: '{% data reusables.gated-features.codespaces %}' -redirect_from: - - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace -versions: - free-pro-team: '*' ---- - -{% data reusables.codespaces.release-stage %} - -{% data reusables.codespaces.beta-functionality-limited %} - -{% data reusables.codespaces.unsupported-repos %} - -Si encuentras problemas al utilizar un buscador que no se base en Chromium, intenta cambiar a uno que sí se base en él, o revisa los problemas conocidos de tu buscador en el repositorio `microsoft/vscode` buscando los problemas etiquetados con el nombre del buscador, tales 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). - -Si encuentras problemas al utilizar un buscador basado en Chromium, puedes revisar si estás experimentando otro problema conocido con {% data variables.product.prodname_vscode %} en el repositorio [`microsoft/vscode`](https://github.com/microsoft/vscode/issues). - -Si aún necesitas ayuda, puedes contactarnos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces#contacting-us-about-codespaces)". diff --git a/translations/es-XL/content/github/extending-github/about-webhooks.md b/translations/es-XL/content/github/extending-github/about-webhooks.md deleted file mode 100644 index a3f6d94600..0000000000 --- a/translations/es-XL/content/github/extending-github/about-webhooks.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Acerca de webhooks -redirect_from: - - /post-receive-hooks/ - - /articles/post-receive-hooks/ - - /articles/creating-webhooks/ - - /articles/about-webhooks -intro: Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización. -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- - -{% tip %} - -**Sugerencia:**{% data reusables.organizations.owners-and-admins-can %} administrar webhooks para una organización. {% data reusables.organizations.new-org-permissions-more-info %} - -{% endtip %} - -Los webhooks se pueden disparar siempre que se realicen una variedad de acciones en un repositorio o una organización. Por ejemplo, puedes configurar tus webhooks para ejecutarse siemrpe que: - -* Se suba a un repositorio. -* Se abra una solicitud de extracción. -* Se cree un sitio {% data variables.product.prodname_pages %}. -* Se agregue un nuevo miembro a un equipo. - -Al usar la API de {% data variables.product.product_name %}, puedes hacer que estos webhooks actualicen un seguimiento de la propuesta, disparen compilaciones de CI, actualicen un espejo de copia de seguridad o incluso se implementen en tu servidor de producción. - -Para configurar un webhook nuevo, necesitarás acceso a un servidor externo y estar familiarizado con los procedimientos técnicos involucrados. Para obtener ayuda para crear un webhook, lo cual incluye un listado completo de las acciones con las que lo puedes asociar, consulta la secicón "[Webhooks](/webhooks)". diff --git a/translations/es-XL/content/github/extending-github/getting-started-with-the-api.md b/translations/es-XL/content/github/extending-github/getting-started-with-the-api.md deleted file mode 100644 index 0bb2a26328..0000000000 --- a/translations/es-XL/content/github/extending-github/getting-started-with-the-api.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Comenzar con la API -redirect_from: - - /articles/getting-started-with-the-api -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- - -Para automatizar las tareas comunes, respaldar tus datos, o crear integraciones que se extienden {% data variables.product.product_name %}, puedes utilizar la API de {% data variables.product.product_name %}. - -Para obtener más información acerca de la API, consulta la [API de REST de GitHub](/rest) y la [API de GraphQL de GitHub](/graphql). También puedes mantenerte actualizado respecto de las novedades relacionadas con la API siguiendo el [{% data variables.product.prodname_dotcom %}Blog del programador](https://developer.github.com/changes/). - -### Leer más - -- "[Respaldar un repositorio](/articles/backing-up-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Acerca de las integraciones](/articles/about-integrations)"{% endif %} diff --git a/translations/es-XL/content/github/extending-github/git-automation-with-oauth-tokens.md b/translations/es-XL/content/github/extending-github/git-automation-with-oauth-tokens.md deleted file mode 100644 index 91fb5c4ed9..0000000000 --- a/translations/es-XL/content/github/extending-github/git-automation-with-oauth-tokens.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Automatización Git con tokens de OAuth -redirect_from: - - /articles/git-over-https-using-oauth-token/ - - /articles/git-over-http-using-oauth-token/ - - /articles/git-automation-with-oauth-tokens -intro: 'Puedes utilizar tokens de OAuth para interactuar con {% data variables.product.product_name %} a través de scripts automatizados.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- - -### Paso 1: Obtener un token de OAuth - -Crea un token de acceso personal en tu página de configuración de la aplicación. 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)". - -{% tip %} - -{% if currentVersion == "free-pro-team@latest" %} -**Sugerencias:** -- You must verify your email address before you can create a personal access token. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". -- {% data reusables.user_settings.review_oauth_tokens_tip %} -{% else %} -**Sugerencia:** {% data reusables.user_settings.review_oauth_tokens_tip %} -{% endif %} - -{% endtip %} - -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %} - -### Paso 2: Clonar un repositorio - -{% data reusables.command_line.providing-token-as-password %} - -To avoid these prompts, you can use Git password caching. Para obtener más información, consulta la sección "[Almacenar tus credenciales de GitHub en caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git)". - -{% warning %} - -**Advertencia**: Los tokens tienen acceso de escritura/lectura y deben tratarse como contraseñas. Si ingresas tu token en la URL del clon cuando clonas o agregas un remoto, Git la escribe en tu archivo _.git/config_ como texto plano, lo que representa un riesgo de seguridad. - -{% endwarning %} - -### Leer más - -- "[Autorizar las Apps de OAuth](/v3/oauth/)" diff --git a/translations/es-XL/content/github/extending-github/index.md b/translations/es-XL/content/github/extending-github/index.md deleted file mode 100644 index 28dc07ecc7..0000000000 --- a/translations/es-XL/content/github/extending-github/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Extender GitHub -redirect_from: - - /categories/86/articles/ - - /categories/automation/ - - /categories/extending-github -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /getting-started-with-the-api - - /git-automation-with-oauth-tokens - - /about-webhooks ---- -### Índice diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md deleted file mode 100644 index 3c363f8600..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: About integration with code scanning -shortTitle: About integration -intro: 'You can perform {% data variables.product.prodname_code_scanning %} externally and then display the results in {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -versions: - enterprise-server: '2.22' -topics: - - Security ---- - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} - -As an alternative to running {% data variables.product.prodname_code_scanning %} within {% data variables.product.prodname_dotcom %}, you can perform analysis elsewhere and then upload the results. Alerts for {% data variables.product.prodname_code_scanning %} that you run externally are displayed in the same way as those for {% data variables.product.prodname_code_scanning %} that you run within {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning)." - -You can use your continuous integration or continuous delivery/deployment (CI/CD) system to run {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql %} analysis and upload the results to {% data variables.product.prodname_dotcom %}. This is an alternative to using {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_codeql %} analysis. For more information, see "[Running code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)." - -If you use a third-party static analysis tool that can produce results as Static Analysis Results Interchange Format (SARIF) 2.1.0 data, you can upload this to {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Cargar un archivo SARIF a GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". - -### Leer más - -* "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)" -* "[Configuring code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system)" -* "[SARIF support for code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)" diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md deleted file mode 100644 index f221283cb5..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: About code scanning -intro: 'You can use {% data variables.product.prodname_code_scanning %} to find security vulnerabilities and errors in the code for your project on {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning -versions: - ghes: '2.22' -topics: - - Security ---- -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} - -### About {% data variables.product.prodname_code_scanning %} - -{% data reusables.code-scanning.about-code-scanning %} - -You can use {% data variables.product.prodname_code_scanning %} to find, triage, and prioritize fixes for existing problems in your code. {% data variables.product.prodname_code_scanning_capc %} also prevents developers from introducing new problems. You can schedule scans for specific days and times, or trigger scans when a specific event occurs in the repository, such as a push. - -If {% data variables.product.prodname_code_scanning %} finds a potential vulnerability or error in your code, {% data variables.product.prodname_dotcom %} displays an alert in the repository. After you fix the code that triggered the alert, {% data variables.product.prodname_dotcom %} closes the alert. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." - -To monitor results from {% data variables.product.prodname_code_scanning %} across your repositories or your organization, you can use the {% data variables.product.prodname_code_scanning %} API. -For more information about API endpoints, see "[{% data variables.product.prodname_code_scanning_capc %}](/v3/code-scanning)." - -To get started with {% data variables.product.prodname_code_scanning %}, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." - -### About {% data variables.product.prodname_codeql %} - -You can use {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}, a semantic code analysis engine. {% data variables.product.prodname_codeql %} treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. - -{% data variables.product.prodname_ql %} is the query language that powers {% data variables.product.prodname_codeql %}. {% data variables.product.prodname_ql %} is an object-oriented logic programming language. {% data variables.product.company_short %}, language experts, and security researchers create the queries used for {% data variables.product.prodname_code_scanning %}, and the queries are open source. The community maintains and updates the queries to improve analysis and reduce false positives. For more information, see [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) on the GitHub Security Lab website. - -{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages. - -{% data reusables.code-scanning.supported-languages %} - -You can view and contribute to the queries for {% data variables.product.prodname_code_scanning %} in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %} queries](https://help.semmle.com/QL/learn-ql/writing-queries/writing-queries.html) in the {% data variables.product.prodname_codeql %} documentation. - -{% if currentVersion == "free-pro-team@latest" %} - -### About billing for {% data variables.product.prodname_code_scanning %} - -{% data variables.product.prodname_code_scanning_capc %} uses {% data variables.product.prodname_actions %}, and each run of a {% data variables.product.prodname_code_scanning %} workflow consumes minutes for {% data variables.product.prodname_actions %}. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." - -{% endif %} - -### About third-party code scanning tools - -{% data reusables.code-scanning.you-can-upload-third-party-analysis %} - -{% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %} - -{% data reusables.code-scanning.get-started-uploading-third-party-data %} - -### Further reading - -{% if currentVersion == "free-pro-team@latest" %} -- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %} -- [{% data variables.product.prodname_security %}](https://securitylab.github.com/) -- [OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md deleted file mode 100644 index 2c13a90eac..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ /dev/null @@ -1,300 +0,0 @@ ---- -title: Configuring code scanning -intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.' -product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.' -miniTocMaxHeadingLevel: 3 -versions: - ghes: '2.22' -topics: - - Security -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning ---- -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} - -### About {% data variables.product.prodname_code_scanning %} configuration - -You can run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_location %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system, using the {% data variables.product.prodname_codeql_runner %}. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)." For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)." - -This article is about running {% data variables.product.prodname_code_scanning %} within {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. - -Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must enable {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." - -{% data reusables.code-scanning.edit-workflow %} - -{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% if currentVersion ver_gt "enterprise-server@2.21" %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% if currentVersion == "free-pro-team@latest" %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.product.prodname_codeql_workflow %} file. - -### Editing a {% data variables.product.prodname_code_scanning %} workflow - -{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have enabled by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_. - -1. In your repository, browse to the workflow file you want to edit. -1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}. -![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png) -1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request. -![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png) - -For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." - -### Configuring frequency - -You can configure the {% data variables.product.prodname_codeql_workflow %} to scan code on a schedule or when specific events occur in a repository. - -Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository. - -#### Scanning on push - -By default, the {% data variables.product.prodname_codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)." - -#### Scanning pull requests - -The default {% data variables.product.prodname_codeql_workflow %} uses the `pull_request` event to trigger a code scan on the `HEAD` commit of a pull request against the default branch. {% if currentVersion ver_gt "enterprise-server@2.21" %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for a repository](/github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} - -For more information about the `pull_request` event, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)." - -#### Scanning on a schedule - -If you use the default {% data variables.product.prodname_codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)." - -{% note %} - -**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch. - -{% endnote %} - -#### Example - -The following example shows a {% data variables.product.prodname_codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`. - -``` yaml -on: - push: - branches: [main, protected] - pull_request: - branches: [main] - schedule: - - cron: '0 15 * * 0' -``` - -This workflow scans: -* Every push to the default branch and the protected branch -* Every pull request to the default branch -* The default branch at 3 P.M. every Sunday - -### Specifying an operating system - -If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% if currentVersion ver_gt "enterprise-server@2.21" %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} - -If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %} - -``` yaml -jobs: - analyze: - name: Analyze - runs-on: [self-hosted, ubuntu-latest] -``` - -{% if currentVersion == "free-pro-team@latest" %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} - -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% if currentVersion ver_gt "enterprise-server@2.21" %}"[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 %}." - -{% if currentVersion ver_gt "enterprise-server@2.21" %}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 %} - -### Changing the languages that are analyzed - -{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages. - -{% data reusables.code-scanning.supported-languages %} - -The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)." - -{% data reusables.code-scanning.specify-language-to-analyze %} - -If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was enabled. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was enabled, and you later added Python code, you will need to add `python` to the matrix. - -```yaml -jobs: - analyze: - name: Analyze - ... - strategy: - fail-fast: false - matrix: - language: ['javascript', 'python'] -``` - -If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action. - -```yaml -- uses: github/codeql-action/init@v1 - with: - languages: cpp, csharp, python -``` -{% if currentVersion == "free-pro-team@latest" %} -### Analyzing Python dependencies - -For GitHub-hosted runners that use Linux only, the {% data variables.product.prodname_codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`: - -- If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies. - -- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete. - -Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract: - -{% raw %} -```yaml -jobs: - CodeQL-Build: - - runs-on: ubuntu-latest - - steps: - - name: Checkout repository - uses: actions/checkout@v2 - with: - fetch-depth: 2 - - name: Set up Python - uses: actions/setup-python@v2 - with: - python-version: '3.x' - - name: Install dependencies - run: | - python -m pip install --upgrade pip - if [ -f requirements.txt ]; - then pip install -r requirements.txt; - fi - # Set the `CODEQL-PYTHON` environment variable to the Python executable - # that includes the dependencies - echo "::set-env name=CODEQL_PYTHON::$(which python)" - - run: git checkout HEAD^2 - if: ${{ github.event_name == 'pull_request' }} - - name: Initialize CodeQL - uses: github/codeql-action/init@v1 - with: - languages: python - # Override the default behavior so that the action doesn't attempt - # to auto-install Python dependencies - setup-python-dependencies: false -``` -{% endraw %} -{% endif %} - -### Running additional queries - -{% data reusables.code-scanning.run-additional-queries %} - -To add one or more queries, add a `with: queries:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. - -``` yaml -- uses: github/codeql-action/init@v1 - with: - queries: COMMA-SEPARATED LIST OF PATHS -``` - -You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language. - -{% data reusables.code-scanning.codeql-query-suites %} - -If you are also using a configuration file for custom settings, any additional queries specified in your workflow are used instead of any specified in the configuration file. If you want to run the combined set of additional queries specified here and in the configuration file, prefix the value of `queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." - -In the following example, the `+` symbol ensures that the specified additional queries are used together with any queries specified in the referenced configuration file. - -``` yaml -- uses: github/codeql-action/init@v1 - with: - config-file: ./.github/codeql/codeql-config.yml - queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main -``` - -### Using a custom configuration file - -As an alternative to specifying which queries to run in the workflow file, you can do this in a separate configuration file. You can also use a configuration file to disable the default queries and to specify which directories to scan during analysis. - -In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_. - -``` yaml -- uses: github/codeql-action/init@v1 - with: - config-file: ./.github/codeql/codeql-config.yml -``` - -The configuration file can be located within the local repository, or in a public, remote repository. For remote repositories, you can use the _owner/repository/file.yml@branch_ syntax. The settings in the file are written in YAML format. - -#### Specifying additional queries - -You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file. - -``` yaml -queries: - - uses: ./my-basic-queries/example-query.ql - - uses: ./my-advanced-queries - - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls -``` - -Optionally, you can give each array element a name, as shown in the example configuration files below. - -For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above. - -#### Disabling the default queries - -If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`. - -#### Specifying directories to scan - -For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from scans by adding a `paths-ignore` array. - -``` yaml -paths: - - src -paths-ignore: - - node_modules - - '**/*.test.js' -``` - -{% note %} - -**Note**: - -* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on..paths` in a workflow. When they are used to modify `on.` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." -* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character. - -{% endnote %} - -For C/C++, C#, and Java, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." - -You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths) in your workflow. - -#### Example configuration files - -{% data reusables.code-scanning.example-configuration-files %} - -### Configuring {% data variables.product.prodname_code_scanning %} for compiled languages - -{% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %} - -{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages)." - -### Accessing private repositories - -If your workflow for {% data variables.product.prodname_code_scanning %} accesses a private repository, other than the repository that contains the workflow, you'll need to configure Git to authenticate with a personal access token. Define the secret in the runner environment by using `jobs..steps.env` in your workflow before any {% data variables.product.prodname_codeql %} actions. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)" and "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." - -For example, the following configuration has Git replace the full URLs to the `github/foo`, `github/bar`, and `github/baz` repositories on {% data variables.product.prodname_dotcom_the_website %} with URLs that include the personal access token that you store in the `ACCESS_TOKEN` environment variable. - -{% raw %} -```yaml -steps: -- name: Configure access to private repositories - env: - TOKEN: ${{ secrets.ACCESS_TOKEN }} - run: | - git config --global url."https://${TOKEN}@github.com/github/foo".insteadOf "https://github.com/github/foo" - git config --global url."https://${TOKEN}@github.com/github/bar".insteadOf "https://github.com/github/bar" - git config --global url."https://${TOKEN}@github.com/github/baz".insteadOf "https://github.com/github/baz" -``` -{% endraw %} - -### Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} - -{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)." diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md deleted file mode 100644 index 3128451a5d..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Escanear tu código automáticamente para encontrar vulnerabilidades y errores -shortTitle: Escanear automáticamente -intro: 'Puedes encontrar vulnerabilidades y errores en el código de tu proyecto en {% data variables.product.prodname_dotcom %}.' -versions: - ghes: '2.22' -topics: - - Security -children: - - /about-code-scanning - - /triaging-code-scanning-alerts-in-pull-requests - - /setting-up-code-scanning-for-a-repository - - /managing-code-scanning-alerts-for-your-repository - - /configuring-code-scanning - - /configuring-the-codeql-workflow-for-compiled-languages - - /troubleshooting-the-codeql-workflow - - /running-codeql-code-scanning-in-a-container ---- - diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system.md deleted file mode 100644 index 662fd8d9bc..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -title: Configuring code scanning in your CI system -shortTitle: Configuring in your CI -intro: 'You can configure how the {% data variables.product.prodname_codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -miniTocMaxHeadingLevel: 4 -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} - -### About {% data variables.product.prodname_code_scanning %} configuration in your CI system - -To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.product.prodname_codeql_runner %}. For more information, see "[Running code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system)." - -In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows. - -``` -$ /path/to-runner/codeql-runner-OS -``` - -`/path/to-runner/` depends on where you've downloaded the {% data variables.product.prodname_codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use. There are three versions of the {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively. - -To customize the way the {% data variables.product.prodname_codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file. - -### Invalidar la detección automática de lenguaje - -The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages. - -{% data reusables.code-scanning.supported-languages %} - -{% data reusables.code-scanning.specify-language-to-analyze %} - -To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. Las palabras clave para los lenguajes compatibles son `cpp`, `csharp`, `go`, `java`, `javascript`, y `python`. - -``` -$ /path/to-runner/codeql-runner-linux init --languages cpp,java -``` - -### Ejecutar consultas adicionales - -{% data reusables.code-scanning.run-additional-queries %} - -{% data reusables.code-scanning.codeql-query-suites %} - -To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file. - -If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.product.prodname_codeql_runner %} uses the additional queries specified with the     `--queries` flag instead of any in the configuration file. If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to `--queries` with the `+` symbol. 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 {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file. - -``` -$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml - --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main -``` - -### Utilizar una herramienta de escaneo de código de terceros - -Instead of passing additional information to the {% data variables.product.prodname_codeql_runner %} commands, you can specify custom settings in a separate configuration file. - -The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. Para obtener más información, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)". - -Use the `--config-file` flag of the `init` command to specify the configuration file. The value of `--config-file` is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_. - -``` -$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml -``` - -#### Ejemplos de archivos de configuración - -{% data reusables.code-scanning.example-configuration-files %} - -### Configurar {% data variables.product.prodname_code_scanning %} para los lenguajes compilados - -For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. En contraste con los otros lenguajes compilados, {% data variables.product.prodname_codeql %} analiza Go sin compilar el código. - -For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first. - -El proceso de `autobuild` solo intenta siempre compilar _un_ solo lenguaje compilado para un repositorio. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command. - -``` -$ /path/to-runner/codeql-runner-linux autobuild --language csharp -``` - -If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system#compiled-language-example)." - -### Puedes escribir un archivo de configuración para {% data variables.product.prodname_code_scanning %}. - -By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command. - -Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository. For more information, see "[Managing alerts from code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning#viewing-an-alert)." - -### {% data variables.product.prodname_codeql_runner %} command reference - -The {% data variables.product.prodname_codeql_runner %} supports the following commands and flags. - -#### `init` - -Initializes the {% data variables.product.prodname_codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed. - -| Flag | Requerido | Input value | -| -------------------------------- |:---------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repositorio` | ✓ | Name of the repository to initialize. | -| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. | -| `--github-auth` | ✓ | A {% data variables.product.prodname_github_apps %} token or personal access token. | -| `--languages` | | Comma-separated list of languages to analyze. By default, the {% data variables.product.prodname_codeql_runner %} detects and analyzes all supported languages in the repository. | -| `--queries` | | Comma-separated list of additional queries to run, in addition to the default suite of security queries. | -| `--config-file` | | Path to custom configuration file. | -| `--codeql-path` | | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.product.prodname_codeql_runner %} downloads a copy. | -| `--temp-dir` | | Directory where temporary files are stored. The default is _./codeql-runner_. | -| `--tools-dir` | | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory. | -| `--checkout-path` | | The path to the checkout of your repository. The default is the current working directory. | -| `--debug` | | None. Prints more verbose output. | -| `-h`, `--help` | | None. Displays help for the command. | - -#### `autobuild` - -Attempts to build the code for the compiled languages C/C++, C#, and Java. For those languages, {% data variables.product.prodname_codeql %} builds the code before analyzing it. Run `autobuild` between the `init` and `analyze` steps. - -| Flag | Requerido | Input value | -| --------------------------- |:---------:| --------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--language` | | The language to build. By default, the {% data variables.product.prodname_codeql_runner %} builds the compiled language with the most files. | -| `--temp-dir` | | Directory where temporary files are stored. The default is _./codeql-runner_. | -| `--debug` | | None. Prints more verbose output. | -| `-h`, `--help` | | None. Displays help for the command. | - -#### `analyze` - -Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_location %}. - -| Flag | Requerido | Input value | -| -------------------------------- |:---------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--repositorio` | ✓ | Name of the repository to analyze. | -| `--commit` | ✓ | SHA of the commit to analyze. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`. | -| `--ref` | ✓ | Name of the reference to analyze, for example `refs/heads/main`. In Git and in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. | -| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. | -| `--github-auth` | ✓ | A {% data variables.product.prodname_github_apps %} token or personal access token. | -| `--checkout-path` | | The path to the checkout of your repository. The default is the current working directory. | -| `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_location %}. | -| `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. | -| `--temp-dir` | | Directory where temporary files are stored. The default is _./codeql-runner_. | -| `--debug` | | None. Prints more verbose output. | -| `-h`, `--help` | | None. Displays help for the command. | - -#### `cargar` - -Uploads SARIF files to {% data variables.product.product_location %}. - -| Flag | Requerido | Input value | -| -------------------------------- |:---------:| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `--sarif-file` | ✓ | SARIF file to upload, or a directory containing multiple SARIF files. | -| `--repositorio` | ✓ | Name of the repository that was analyzed. | -| `--commit` | ✓ | SHA of the commit that was analyzed. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`. | -| `--ref` | ✓ | Name of the reference that was analyzed, for example `refs/heads/main`. In Git and in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. | -| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. | -| `--github-auth` | ✓ | A {% data variables.product.prodname_github_apps %} token or personal access token. | -| `--checkout-path` | | The path to the checkout of your repository. The default is the current working directory. | -| `--debug` | | None. Prints more verbose output. | -| `-h`, `--help` | | None. Displays help for the command. | diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md deleted file mode 100644 index f4cabb2462..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -title: Enabling code scanning for a repository -shortTitle: Enabling code scanning -intro: 'You can enable {% data variables.product.prodname_code_scanning %} for your project''s repository.' -product: '{% data reusables.gated-features.code-scanning %}' -permissions: 'People with write permissions to a repository can enable {% data variables.product.prodname_code_scanning %} for the repository.' -redirect_from: - - /github/managing-security-vulnerabilities/configuring-automated-code-scanning - - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} - -### Options for enabling {% data variables.product.prodname_code_scanning %} - -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 reusables.code-scanning.enabling-options %} - -### Enabling {% data variables.product.prodname_code_scanning %} using actions - -{% if currentVersion == "free-pro-team@latest" %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)."{% endif %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %}", click **Set up {% data variables.product.prodname_code_scanning %}**. - !["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) -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. - - For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." -6. Use the **Start commit** drop-down, and type a commit message. - ![Start commit](/assets/images/help/repository/start-commit-commit-new-file.png) -7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request. - ![Choose where to commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png) -8. Click **Commit new file** or **Propose new file**. - -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 or any protected branches. As a result, {% data variables.product.prodname_code_scanning %} will now commence. - -### Viewing the logging output from {% data variables.product.prodname_code_scanning %} - -After enabling {% 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. - - ![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](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository#viewing-an-alert)." - -{% 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. - - ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) - -{% endnote %} - -### Understanding the pull request checks - -Each {% data variables.product.prodname_code_scanning %} workflow you enable 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. - -The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code. - - ![{% 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. - - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) - -#### Reasons for the "missing analysis" message - -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Missing analysis for base commit SHA-HASH" 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: - -* The pull request has been raised against a branch other than the default branch or a protected branch, and this branch hasn't been analyzed. - - 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. - - ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) - - The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan. - -* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available. - - Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. - -* An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available. - - Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}. - -### Next steps - -After enabling {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can: - -- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." -- View any alerts generated for a pull request submitted after you enabled {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests)." -- Set up notifications for completed runs. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)." -- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow)." -- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md deleted file mode 100644 index fffdcb170c..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Encontrar errores y vulnerabilidades de seguridad en tu código -redirect_from: - - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code -versions: - ghes: '2.22' -topics: - - Security -children: - - /automatically-scanning-your-code-for-vulnerabilities-and-errors - - /integrating-with-code-scanning - - /using-codeql-code-scanning-with-your-existing-ci-system ---- -### Índice diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md deleted file mode 100644 index 6fdfbd02bd..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Integrating with code scanning -shortTitle: Integration -intro: 'You can integrate {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI systems or upload results from other tools.' -mapTopic: true -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning -versions: - enterprise-server: '2.22' -topics: - - Security ---- - diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system.md deleted file mode 100644 index 0869ad1a63..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system.md +++ /dev/null @@ -1,145 +0,0 @@ ---- -title: Running code scanning in your CI system -shortTitle: Running in your CI -intro: 'If you use a third-party continuous integration system, you can integrate {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} into this system using the {% data variables.product.prodname_codeql_runner %}.' -product: '{% data reusables.gated-features.code-scanning %}' -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} - -### Acerca de {% data variables.product.prodname_codeql_runner %} - -{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." - -You can use the {% data variables.product.prodname_codeql_runner %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_location %}. For information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." - -The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_location %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. - -{% data reusables.code-scanning.codeql-runner-license %} - -### Downloading the {% data variables.product.prodname_codeql_runner %} - -You can download the {% data variables.product.prodname_codeql_runner %} from https://github.com/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it. - -On Linux: - -```shell -chmod +x codeql-runner-linux -``` - -En MacOS: - -```shell -chmod +x codeql-runner-macos -sudo xattr -d com.apple.quarantine codeql-runner-macos -``` - -### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system - -Once you have downloaded the {% data variables.product.prodname_codeql_runner %} and verified that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. In addition to this, each CI server also needs: - -- A {% data variables.product.prodname_github_apps %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. For private repositories the token must have the `repo` scope. For public the token needs only the `public_repo` and `repo:security_events` scopes. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." -- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains the {% data variables.product.prodname_codeql %} CLI, queries, and libraries needed for {% data variables.product.prodname_codeql %} analysis. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)." - -The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: - -1. Allow the CI servers access to {% data variables.product.prodname_dotcom_the_website %} so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically. -1. Manually download/extract the bundle, store it with other central resources, and use the `--codeql-path` flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}. -{% if currentVersion != "free-pro-team@latest" %} -1. You can mirror the `github/codeql-action` repository on {% data variables.product.product_location %}. Unless you specify the `--codeql-path` flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} - -### Calling the {% data variables.product.prodname_codeql_runner %} - -You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are: - -1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands. -1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_location %}. - -For both commands, you must specify the URL of {% data variables.product.product_location %}, the repository *OWNER/NAME*, and the GitHub Apps or personal access token to use for authentication. You also need to specify the location of the CodeQL bundle unless the CI server has access to download it directly from the `github/codeql-action` repository on {% data variables.product.prodname_dotcom_the_website %}{% if currentVersion != "free-pro-team@latest" %} or mirrored on {% data variables.product.product_location %}{% endif %}. - -You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the `--tools-dir` flag and where it stores temporary files during analysis using `--temp-dir`. - -To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[{% data variables.product.prodname_codeql_runner %} command reference](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system#codeql-runner-command-reference)." - -#### Basic example - -This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). - -1. Check out the repository to analyze. -1. Move into the directory where the repository is checked out. -1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. - - ```shell - $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo - --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN - > Cleaning temp directory /srv/checkout/example-repo/codeql-runner - > ... - > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript. - ``` - -1. Populate the {% data variables.product.prodname_codeql_runner %} databases, analyze them, and upload the results to {% data variables.product.product_name %}. - - ```shell - $ /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo - --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN - --commit 5b6a3078b31dc346e5ce7b86837d6abbe7a18bbd --ref refs/heads/main - > Finalizing database creation - > ... - > POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms - > Successfully uploaded results - ``` - -The server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository on {% data variables.product.prodname_dotcom_the_website %}{% if currentVersion != "free-pro-team@latest" %} or mirrored on {% data variables.product.product_location %}{% endif %}, so there is no need to use the `--codeql-path` flag. When the analysis is complete, the {% data variables.product.prodname_codeql_runner %} uploads the results to the {% data variables.product.prodname_code_scanning %} view. Para obtener más información, consulta la sección "[Administrar alertas desde {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning)". - -#### Compiled language example - -This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to trace the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command. - -1. Check out the repository to analyze. -1. Move into the directory where the repository is checked out. -1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. - - ```shell - $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 - --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN - > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner - > ... - > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json" - and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". - Please export these variables to future processes so the build can be traced, for example by running " - . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". - ``` - -1. Run the script generated by the `init` action to set up the environment to trace the build. - - ```shell - $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh - ``` - -1. Build the code. -1. Populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload the results to GitHub. - - ```shell - $ /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo-2 - --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN - --commit ae7b655ef30b50fb726ae7b3daa79571a39d194d --ref refs/heads/main - > Finalizing database creation - > ... - > POST /repos/octo-org/example-repo-2/code-scanning/sarifs - 202 in 573ms - > Successfully uploaded results - ``` - -{% note %} - -**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place. - -{% endnote %} - -### Leer más - -- "[Configuring code scanning in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system)" -- "[Troubleshooting code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning)" diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md deleted file mode 100644 index 96bced0324..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -title: Running CodeQL code scanning in your CI system -shortTitle: Running in your CI -intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.' -product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system -versions: - enterprise-server: '2.22' -topics: - - Security ---- - -{% data reusables.code-scanning.beta-codeql-runner %} -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} - -### Using {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI system - -If you use a continuous integration or continuous delivery/deployment (CI/CD) system other than {% data variables.product.prodname_actions %}, you can use your existing system to run {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql %} analysis and upload the results to {% data variables.product.prodname_dotcom %}. To do this, use the {% data variables.product.prodname_codeql_runner %}. - -### About the {% data variables.product.prodname_codeql_runner %} - -{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." - -You can use the {% data variables.product.prodname_codeql_runner %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_location %}. For information, see "[Enabling {% data variables.product.prodname_code_scanning %} for a repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository)." - -The {% data variables.product.prodname_codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_location %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. - -{% data reusables.code-scanning.codeql-runner-license %} - -### Downloading the {% data variables.product.prodname_codeql_runner %} - -You can download the {% data variables.product.prodname_codeql_runner %} from https://github.com/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it. - -On Linux: - -```shell -chmod +x codeql-runner-linux -``` - -On MacOS: - -```shell -chmod +x codeql-runner-macos -sudo xattr -d com.apple.quarantine codeql-runner-macos -``` - -On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions. - -### Adding the {% data variables.product.prodname_codeql_runner %} to your CI system - -Once you have downloaded the {% data variables.product.prodname_codeql_runner %} and verified that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. It is important to notice that each CI server that you intend to use for {% data variables.product.prodname_code_scanning %} needs to have the {% data variables.product.prodname_codeql_runner %}. You might configure each server to copy the runner from a central, internal location, or you could use the REST API to get the runner direct from GitHub, for example: - -```shell -wget https://github.com/github/codeql-action/releases/download/codeql-bundle-20200826/codeql-runner-linux -chmod +x codeql-runner-linux -``` - -In addition to this, each CI server also needs: - -- A {% data variables.product.prodname_github_apps %} or personal access token for the {% data variables.product.prodname_codeql_runner %} to use. For private repositories the token must have the `repo` scope. For public the token needs only the `public_repo` and `repo:security_events` scopes. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." -- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains the {% data variables.product.prodname_codeql %} CLI, queries, and libraries needed for {% data variables.product.prodname_codeql %} analysis. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)." - -The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: - -1. Allow the CI servers access to {% data variables.product.prodname_dotcom_the_website %} so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically. -1. Manually download/extract the bundle, store it with other central resources, and use the `--codeql-path` flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}. -{% if currentVersion != "free-pro-team@latest" %} -1. You can mirror the `github/codeql-action` repository on {% data variables.product.product_location %}. Unless you specify the `--codeql-path` flag, the runner automatically checks for the bundle in this location and on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} - -### Calling the {% data variables.product.prodname_codeql_runner %} - -You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are: - -1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands. -1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_location %}. - -For both commands, you must specify the URL of {% data variables.product.product_location %}, the repository *OWNER/NAME*, and the GitHub Apps or personal access token to use for authentication. You also need to specify the location of the CodeQL bundle unless the CI server has access to download it directly from the `github/codeql-action` repository on {% data variables.product.prodname_dotcom_the_website %}{% if currentVersion != "free-pro-team@latest" %} or mirrored on {% data variables.product.product_location %}{% endif %}. - -You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the `--tools-dir` flag and where it stores temporary files during analysis using `--temp-dir`. - -To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system#codeql-runner-command-reference)." - -#### Basic example - -This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). - -1. Check out the repository to analyze. -1. Move into the directory where the repository is checked out. -1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. - - ```shell - $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo - --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN - > Cleaning temp directory /srv/checkout/example-repo/codeql-runner - > ... - > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript. - ``` - -1. Populate the {% data variables.product.prodname_codeql_runner %} databases, analyze them, and upload the results to {% data variables.product.product_name %}. - - ```shell - $ /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo - --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN - --commit 5b6a3078b31dc346e5ce7b86837d6abbe7a18bbd --ref refs/heads/main - > Finalizing database creation - > ... - > POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms - > Successfully uploaded results - ``` - -The server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository on {% data variables.product.prodname_dotcom_the_website %}{% if currentVersion != "free-pro-team@latest" %} or mirrored on {% data variables.product.product_location %}{% endif %}, so there is no need to use the `--codeql-path` flag. When the analysis is complete, the {% data variables.product.prodname_codeql_runner %} uploads the results to the {% data variables.product.prodname_code_scanning %} view. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository)." - -#### Compiled language example - -This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command. - -1. Check out the repository to analyze. -1. Move into the directory where the repository is checked out. -1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. - - ```shell - $ /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 - --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN - > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner - > ... - > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json" - and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". - Please export these variables to future processes so the build can be traced, for example by running " - . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". - ``` - -1. Run the script generated by the `init` action to set up the environment to monitor the build. - - ```shell - $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh - ``` - -1. Build the code. -1. Populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload the results to GitHub. - - ```shell - $ /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo-2 - --github-url {% data variables.command_line.git_url_example %} --github-auth TOKEN - --commit ae7b655ef30b50fb726ae7b3daa79571a39d194d --ref refs/heads/main - > Finalizing database creation - > ... - > POST /repos/octo-org/example-repo-2/code-scanning/sarifs - 202 in 573ms - > Successfully uploaded results - ``` - -{% note %} - -**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place. - -{% endnote %} - -### Further reading - -- "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system)" -- "[Troubleshooting {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system)" diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md deleted file mode 100644 index 090233d179..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning.md +++ /dev/null @@ -1,417 +0,0 @@ ---- -title: Soporte de SARIF para escaneo de código -shortTitle: Soporte de SARIF -intro: 'Para mostrar resultados de una herramienta de análisis estático de un tercero en tu repositorio de {% data variables.product.prodname_dotcom %}, necesitarás que tus resultados se almacenen en un archivo SARIF que sea compatible con un subconjunto específico del modelo SARIF 2.1.0 JSON para escaneo de código. Si utilizas el motor de análisis estático predeterminado de {% data variables.product.prodname_codeql %}, tus resultados se mostrarán automáticamente en tu repositorio de {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning -versions: - enterprise-server: '2.22' -topics: - - Security ---- - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} - -### Acerca del soporte de SARIF - -SARIF (Formato de Intercambio de Resultados de Análisis Estático, por sus siglas en inglés) es un [Estándar de OASIS](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) que define un formato de archivo de salida. El estándar SARIF se utiliza para optimizar la manera en el que las herramientas de análisis estático comparten sus resultados. {% data variables.product.prodname_code_scanning_capc %} es compatible con un subconjunto del modelo SARIF 2.1.0 JSON. - -Para cargar un archivo SARIF desde un motor de análisis estático de código desde un tercero, necesitaras asegurarte de que los archivos cargados utilicen la versión SARIF 2.1.0. {% data variables.product.prodname_dotcom %} analizará el archivo SARIF y mostrará alertas utilizando los resultados en tu repositorio como parte de la experiencia de escaneo de código. Para obtener más información, 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)". Para obtener más información acerca del modelo SARIF 2.1.0, consulta [`sari-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Schemata/sarif-schema-2.1.0.json). - -Si tu archivo SARIF no incluye `partialFingerprints`, este campo se calculará cuando cargues el archivo SARIF utilizando {% data variables.product.prodname_actions %}. Para obtener más información, 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)". - -{% data variables.product.prodname_dotcom %} utiliza propiedades en el archivo SARIF para mostrar alertas. Por ejemplo, la `shortDescription` y `fullDescription` aparecen hasta arriba de una alerta de {% data variables.product.prodname_code_scanning %}. La `location` permite a {% data variables.product.prodname_dotcom %} mostrar anotaciones en tu archivo de código. Para obtener más información, consulta la sección "[Administrar alertas desde {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning)". - -Si SARIF es nuevo para ti y quieres aprender más, consulta el repositorio [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) de Microsoft. - -### Prevenir alertas duplicadas utilizando huellas dactilares - -Cada vez que el flujo de trabajo de {% 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. - -{% 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. - -SARIF files created by the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %} include fingerprint data. If your SARIF file doesn't include `partialFingerprints`, the `partialFingerprints` field will be calculated if you upload the SARIF file using {% data variables.product.prodname_actions %}. Para obtener más información, 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)". - -### Propiedades compatibles de archivo de salida SARIF - -Si utilizas un motor de análisis de código diferente a {% data variables.product.prodname_codeql %}, puedes revisar las propiedades SARIF compatibles para optimizar cómo aparecerán los resultados de tu análisis en {% data variables.product.prodname_dotcom %}. - -Puedes cargar cualquier archivo de salida SARIF 2.1.0 válido, sin embargo, {% data variables.product.prodname_code_scanning %} utilizará únicamente las siguientes propiedades compatibles. - -#### Objeto `sarifLog` - -| Nombre | Descripción | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `$schema` | **Requerido.** la URI del modelo SARIF JSON para la versión 2.1.0. Por ejemplo, `https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json`. | -| `version` | **Requerido.**{% data variables.product.prodname_code_scanning_capc %} solo es compatible con la versión `2.1.0` de SARIF. | -| `runs[]` | **Requerido.** Un archivo SARIF contiene un arreglo de una o más ejecuciones. Cada ejecución representa una sola ejecución de una herramienta de análisis. Para obtener más información acerca de una `run`, consulta el [ objeto `run`](#run-object). | - -#### Objeto `run` - -{% data variables.product.prodname_code_scanning_capc %} utiliza el objeto `run` para filtrar los resultados por herramienta y proporcionar información acerca del origen de un resultado. El objeto `run` contienen el objeto componente de herramienta `tool.driver`, el cual contiene información acerca de la herramienta que generó el resultado. Cada `run` puede tener únicamente resultados para la herramienta de análisis. - -| Nombre | Descripción | -| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `tool.driver.name` | **Requerido.** El nombre de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre en {% data variables.product.prodname_dotcom %} para permitirte filtrar los resultados por herramienta. | -| `tool.driver.version` | **Opcional.** La versión de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} utiliza el número de versión para rastrear cuando los resultados pudieran haber cambiado debido al cambio de versión en la herramienta en vez de debido a un cambio del código que se analiza. Si el archivo SARIF incluye el campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} no utilizará `version`. | -| `tool.driver.semanticVersion` | **Opcional.** La versión de la herramienta de análisis, especificada por el formato de Semantic Versioning 2.0. {% data variables.product.prodname_code_scanning_capc %} utiliza el número de versión para rastrear cuando los resultados pudieran haber cambiado debido al cambio de versión en la herramienta en vez de debido a un cambio del código que se analiza. Si el archivo SARIF incluye el campo `semanticVersion`, {% data variables.product.prodname_code_scanning %} no utilizará `version`. Para obtener más información, consulta la sección "[Semantic Versioning 2.0.0](https://semver.org/)" en la documentación de Semantic Versioning. | -| `tool.driver.rules[]` | **Requerido.** Un arreglo de objetos `reportingDescriptor` que representen reglas. La herramienta de análisis utiliza reglas para encontrar problemas en el código que se analiza. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). | -| `results[]` | **Requerido.** Los resultados de la herramienta de análisis. {% data variables.product.prodname_code_scanning_capc %} muestra los resultados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta el [objeto `result`](#result-object). | - -#### 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. Can be one of: `very-high`, `high`, `medium`, or `low`. | - -#### `result` 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. 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). | -| `suppressions[].state` | **Opcional.** Cuando el `state` se configura como `accepted`, {% data variables.product.prodname_code_scanning %} actualizará el estado del resultado a `Closed` en {% data variables.product.prodname_dotcom %}. | - -#### Objeto `location` - -Una ubicación dentro de un artefacto de programación, tal como un archivo en el repositorio o un archivo que se generó durante una compilación. - -| Nombre | Descripción | -| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| `location.id` | **Opcional.** Un identificador único que distingue esta ubicación del resto de las ubicaciones dentro de un objeto de un único resultado. | -| `location.physicalLocation` | **requerido.** Identifica el artefacto y la región. Para obtener más información, consulta la [`physicalLocation`](#physicallocation-object). | -| `location.message.text` | **Opcional.** Un mensaje relevante para la ubicación. | - -#### Objeto `physicalLocation` - -| Nombre | Descripción | -| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `artifactLocation.uri` | **Requerido.** Un URI que indica la ubicación de un artefacto, a menudo un archivo ya sea en el repositorio o generado durante una compilación. Si el URI es relativo, deberá ser relativo a la raíz del repositorio de {% data variables.product.prodname_dotcom %} que se está analizando. Por ejemplo, main.js o src/script.js son relativos a la raíz del repositorio. Si la URI es absoluta, {% data variables.product.prodname_code_scanning %} puede utilizarla para revisar el artefacto y empatar archivos en el repositorio. Por ejemplo, `https://github.com/github/example/blob/00/src/promiseUtils.js`. | -| `region.startLine` | **Requerido.** El número del línea para el primer caracter en la región. | -| `region.startColumn` | **Requerido.** El número de columna del primer caracter en la región. | -| `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. | - -### Ejemplos de archivo de salida SARIF - -Estos ejemplos de archivos de salida SARIF muestran las propiedades compatibles y los valores de ejemplo. - -#### Ejemplo con las propiedades mínimas requeridas - -Este archivo de salida SARIF tiene valores de ejemplo para mostrar las propiedades mínimas requeridas para que los resultados de {% data variables.product.prodname_code_scanning %} funcionen como se espera. Si eliminas cualquier propiedad u omites valores, estos datos no se mostrarán correctamente ni se sincronizarán en {% data variables.product.prodname_dotcom %}. - - -```json -{ - "$schema" : "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", - "version" : "2.1.0", - "runs" : - [ - { - "tool" : { - "driver" : { - "name" : "Tool Name" - } - }, - "results" : [ { - "message" : { - "text" : "Result text. This result does not have a rule associated." - }, - "locations" : [ { - "physicalLocation" : { - "artifactLocation" : { - "uri" : "src/build.cmd" - }, - "region" : { - "startLine" : 2, - "startColumn" : 7, - "endColumn" : 10 - } - } - } ], - "partialFingerprints" : { - "primaryLocationLineHash" : "39fa2ee980eb94b0:1" - } - }] - } - ] -} -``` - -#### Ejemplo que muestra todas las propiedades compatibles con SARIF - -Este archivo de salida SARIF tiene valores ejemplo para mostrar todas las propiedades de SARIF compatibles con {% data variables.product.prodname_code_scanning %}. - -```json -{ - "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", - "version": "2.1.0", - "runs": [ - { - "tool": { - "driver": { - "name": "Tool Name", - "semanticVersion": "2.0.0", - "rules": [ - { - "id": "js/unused-local-variable", - "name": "js/unused-local-variable", - "shortDescription": { - "text": "Unused variable, import, function or class" - }, - "fullDescription": { - "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully." - }, - "defaultConfiguration": { - "level": "note" - }, - "properties": { - "tags": [ - "maintainability" - ], - "precision": "very-high" - } - }, - { - "id": "js/inconsistent-use-of-new", - "name": "js/inconsistent-use-of-new", - "shortDescription": { - "text": "Inconsistent use of 'new'" - }, - "fullDescription": { - "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'." - }, - "defaultConfiguration": null, - "properties": { - "tags": [ - "reliability", - "correctness", - "language-features" - ], - "precision": "very-high" - } - } - ] - } - }, - "results": [ - { - "ruleId": "js/unused-local-variable", - "ruleIndex": 0, - "message": { - "text": "Unused variable foo." - }, - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "main.js", - "uriBaseId": "%SRCROOT%", - "index": 0 - }, - "region": { - "startLine": 2, - "startColumn": 7, - "endColumn": 10 - } - } - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "39fa2ee980eb94b0:1", - "primaryLocationStartColumnFingerprint": "4" - } - }, - { - "ruleId": "js/inconsistent-use-of-new", - "ruleIndex": 1, - "message": { - "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))." - }, - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "https://github.com/github/example/blob/0000000000000000000000000000000000000000/src/promiseUtils.js", - "index": 1 - }, - "region": { - "startLine": 2 - } - } - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "5061c3315a741b7d:1", - "primaryLocationStartColumnFingerprint": "7" - }, - "relatedLocations": [ - { - "id": 1, - "physicalLocation": { - "artifactLocation": { - "uri": "src/ParseObject.js", - "uriBaseId": "%SRCROOT%", - "index": 3 - }, - "region": { - "startLine": 2281, - "startColumn": 33, - "endColumn": 55 - } - }, - "message": { - "text": "here" - } - }, - { - "id": 2, - "physicalLocation": { - "artifactLocation": { - "uri": "src/LiveQueryClient.js", - "uriBaseId": "%SRCROOT%", - "index": 2 - }, - "region": { - "startLine": 166 - } - }, - "message": { - "text": "here" - } - } - ] - }, - { - "message": { - "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies." - }, - "level": "error", - "locations": [ - { - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif", - "uriBaseId": "%SRCROOT%", - "index": 0 - }, - "region": { - "startLine": 54, - "startColumn": 10, - "endLine": 55, - "endColumn": 25 - } - } - } - ], - "relatedLocations": [ - { - "id": 1, - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif" - }, - "region": { - "startLine": 81, - "startColumn": 10, - "endColumn": 18 - } - }, - "message": { - "text": "here" - } - }, - { - "id": 2, - "physicalLocation": { - "artifactLocation": { - "uri": "full.sarif" - }, - "region": { - "startLine": 82, - "startColumn": 10, - "endColumn": 21 - } - }, - "message": { - "text": "here" - } - } - ], - "codeFlows": [ - { - "threadFlows": [ - { - "locations": [ - { - "location": { - "physicalLocation": { - "region": { - "startLine": 11, - "endLine": 29, - "startColumn": 10, - "endColumn": 18 - }, - "artifactLocation": { - "uriBaseId": "%SRCROOT%", - "uri": "full.sarif" - } - }, - "message": { - "text": "Rule has index 0" - } - } - }, - { - "location": { - "physicalLocation": { - "region": { - "endColumn": 47, - "startColumn": 12, - "startLine": 12 - }, - "artifactLocation": { - "uriBaseId": "%SRCROOT%", - "uri": "full.sarif" - } - } - } - } - ] - } - ] - } - ], - "partialFingerprints": { - "primaryLocationLineHash": "ABC:2" - } - } - ], - "newlineSequences": [ - "\r\n", - "\n", - "", - "
 " - ], - "columnKind": "utf16CodeUnits" - } - ] -} -``` diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md deleted file mode 100644 index 2e936ad85b..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: Troubleshooting the CodeQL workflow -shortTitle: Troubleshooting CodeQL -intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.' -product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning -versions: - enterprise-server: '2.22' -topics: - - Security ---- - -{% data reusables.code-scanning.beta %} - -### Automatic build for a compiled language fails - -If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps. - -- Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." - -- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a build matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix. - - The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step: - - ```yaml - jobs: - analyze: - ... - strategy: - fail-fast: false - matrix: - language: ['csharp', 'cpp', 'javascript'] - - ... - - - name: Initialize {% data variables.product.prodname_codeql %} - uses: github/codeql-action/init@v1 - with: - languages: {% raw %}${{ matrix.language }}{% endraw %} - ``` - - For more information about editing the workflow, see "[Configuring code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." - -### No code found during the build - -If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure: - -1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by updating the list of languages in the `language` matrix. For example, the following configuration will analyze only Go, and JavaScript. - - ```yaml - strategy: - fail-fast: false - matrix: - # Override automatic language detection by changing the list below - # Supported options are: - # ['csharp', 'cpp', 'go', 'java', 'javascript', 'python'] - language: ['go', 'javascript'] - ``` -For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. -1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually. For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." -1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis. -1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis. -1. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are certain configuration options like running your build process in a container, if you're building using a distributed build system external to {% data variables.product.prodname_actions %} using a daemon process, or if {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using. - - For C# projects using either `dotnet build` or `msbuild` which target .NET Core 2, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code. The `UseSharedCompilation` flag isn't necessary for .NET Core 3.0 and later. - - For example, the following configuration for C# will pass the flag during the first build step. - - ``` yaml - - run: | - dotnet build /p:UseSharedCompilation=false - ``` - - If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}. - -For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." - -### Portions of my repository were not analyzed using `autobuild` - -The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." - -### Error: "Server error" - -If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}. - -### Error: "Out of disk" or "Out of memory" - -On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner. -{% if currentVersion == "free-pro-team@latest" %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem. -{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %} - -### The build takes too long - -If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. - -#### Increase the memory or cores - -If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners. - -#### Use matrix builds to parallelize the analysis - -The default {% data variables.product.prodname_codeql_workflow %} uses a build matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above. - -#### Reduce the amount of code being analyzed in a single workflow - -Analysis time is typically proportional to the amount of code being analyzed. You can reduce the analysis time by reducing the amount of code being analyzed at once, for example, by excluding test code, or breaking analysis into multiple workflows that analyze only a subset of your code at a time. - -For compiled languages like Java, C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build only the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpaths)." - -For interpreted languages like Go, JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without a specific build, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#specifying-directories-to-scan)." - -If you split your analysis into multiple workflows as described above, we still recommend that you have at least one workflow which runs on a `schedule` which analyzes all of the code in your repository. Because {% data variables.product.prodname_codeql %} analyzes data flows between components, some complex security behaviors may only be detected on a complete build. - -#### Run only during a `schedule` event - -If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)." - -{% if currentVersion == "free-pro-team@latest" %} -### Results differ between analysis platforms - -If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows. - -On GitHub-hosted runners that use Linux, the {% data variables.product.prodname_codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#analyzing-python-dependencies)." - -{% endif %} diff --git a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md b/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md deleted file mode 100644 index 44cf409e23..0000000000 --- a/translations/es-XL/content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -title: Subir un archivo SARIF a GitHub -shortTitle: Cargar un archivo SARIF -intro: '{% data reusables.code-scanning.you-can-upload-third-party-analysis %}' -permissions: 'People with write permissions to a repository can upload {% data variables.product.prodname_code_scanning %} data generated outside {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.code-scanning %}' -redirect_from: - - /github/managing-security-vulnerabilities/uploading-a-code-scanning-analysis-to-github -versions: - enterprise-server: '2.22' -topics: - - Security ---- - -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} - -### Acerca de la carga de archivos SARIF para {% data variables.product.prodname_code_scanning %} - -{% data variables.product.prodname_dotcom %} creates {% data variables.product.prodname_code_scanning %} alerts in a repository using information from Static Analysis Results Interchange Format (SARIF) files. El archivo SARIF puede generarse desde una herramienta de análisis compatible con SARIF que ejecutes en el mismo flujo de trabajo de {% data variables.product.prodname_actions %} que utilizaste para cargar el archivo. Como alternativa, cuando se genere el archivo como un artefacto fuera de tu repositorio, puedes cargar el archivo SARIF directamente a algún repositorio y utilizar el flujo de trabajo para subir este archivo. Para obtener más información, consulta la sección "[Administrar alertas desde {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning)". - -You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. Para cargar resultados desde herramientas de terceros debes utilizar el Formato de Intercambio para Resultados de Análisis Estático (SARIF) 2.1.0. Para obtener más información, consulta la sección "[Acerca de la compatibilidad de SARIF con {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning)". - -You can upload the results using {% data variables.product.prodname_actions %}{% if currentVersion == "enterprise-server@2.22" %} (available if your organization is taking part in the beta program){% endif %}, the {% data variables.product.prodname_code_scanning %} API, or the {% data variables.product.prodname_codeql_runner %}. The best upload method will depend on how you generate the SARIF file, for example, if you use: - -- {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis. -- "[Administrar una ejecución de flujo de trabajo](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)" -- {% data variables.product.prodname_dotcom %} mostrará alertas de {% data variables.product.prodname_code_scanning %} desde el archivo SARIF cargado en tu repositorio. Para obtener más información, consulta la sección "[Administrar alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning)". -- A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)"). - -### Cargar un análisis de {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_actions %} - -Para cargar un archivo SARIF de terceros a {% data variables.product.prodname_dotcom %}, necesitarás un flujo de trabajo de {% data variables.product.prodname_actions %}. Para obtener más información, consulta las secciónes "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" y "[Configurar un flujo de trabajo](/actions/configuring-and-managing-workflows/configuring-a-workflow)". - -Tu flujo de trabajo necesitará utilizar la acción `upload-sarif`, que tiene parámetros de entrada que puedes utilizar para configurar la carga. It has input parameters that you can use to configure the upload. El parámetro de entrada principal que utilizarás será `sarif-file`, el cual configura el archivo o directorio de los archivos SARIF a cargar. El directorio o ruta de archivo es relativo a la raíz del repositorio. Para obtener más información, consulta la [acción `upload-sarif`](https://github.com/github/codeql-action/tree/HEAD/upload-sarif). - -La acción `upload-sarif` puede configurarse para ejecutarse cuando ocurren los eventos `push` y `scheduled`. Para obtener más información acerca de los eventos {% data variables.product.prodname_actions %}, consulta la sección [Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)". - -Si tu archivo SARIF no incluye `partialFingerprints`, la acción `upload-sarif` calculará el campo `partialFingerprints` para ti e intentará prevenir las alertas duplicadas. {% data variables.product.prodname_dotcom %} solo puede crear `partialFingerprints` cuando el repositorio contenga tanto el archivo SARIF como el código fuente utilizado en el análisis estático. Para obtener más información acerca de prevenir alertas duplicadas, consulta la sección "[Acerca de la compatibilidad de SARIF con el escaneo de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning#preventing-duplicate-alerts-using-fingerprints)". - -#### Ejemplo de flujo de trabajo para los archivos SARIF generados fuera de un repositorio - -Puedes crear un nuevo flujo de trabajo que cargue archivos SARIF después de que los confirmes en tu repositorio. Esto es útil cuando el archivo SARIF se genera como un artefacto fuera de tu repositorio. - -Este flujo de trabajo de ejemplo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción utiliza la propiedad `partialFingerprints` para determinar si ha habido cambios. Adicionalmente a ejecutarse cuando se cargan las confirmaciones, el flujo de trabajo se programa para su ejecución una vez por semana. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". - -Este flujo de trabajo carga el archivo `results.sarif` ubicado en la raíz del repositorio. Para obtener más información acerca de crear un archivo de flujo de trabajo, consulta la sección "[Configurar un flujo de trabajo](/actions/configuring-and-managing-workflows/configuring-a-workflow)". - -Como alternativa, puedes modificar este flujo de trabajo para cargar un directorio de archivos SARIF. Por ejemplo, puedes colocar todos los archivos SARIF en un directorio en la raíz de tu repositorio, el cual se llame `sarif-output` y configurar el parámetro de entrada de la acción `sarif_file` como `sarif-output`. - -```yaml -name: "Upload SARIF" - -# Run workflow each time code is pushed to your repository and on a schedule. -# The scheduled workflow runs every at 00:00 on Sunday UTC time. -on: - push: - schedule: - - cron: '0 0 * * 0' - -jobs: - build: - runs-on: ubuntu-latest - steps: - # This step checks out a copy of your repository. - - name: Checkout repository - uses: actions/checkout@v2 - - name: Upload SARIF file - uses: github/codeql-action/upload-sarif@v1 - with: - # Path to SARIF file relative to the root of the repository - sarif_file: results.sarif -``` - -#### Ejemplo de flujo de trabajo que ejecuta la herramienta de análisis ESLint - -Si generas tu archivo SARIF de terceros como parte de un flujo de trabajo de integración contínua (IC), puedes agregar la acción `upload-sarif` como un paso después de ejecutar tus pruebas de IC. Si aún no tienes un flujo de trabajo de IC, puedes crearlo utilizando una plantilla de {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Comenzar con plantillas de flujo de trabajo preconfiguradas](/actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates)." - -Este flujo de trabajo de ejemplo se ejecuta cada que las confirmaciones se cargan al repositorio. La acción utiliza la propiedad `partialFingerprints` para determinar si ha habido cambios. Adicionalmente a ejecutarse cuando se cargan las confirmaciones, el flujo de trabajo se programa para su ejecución una vez por semana. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". - -El flujo de trabajo muestra un ejemplo de ejecución de la herramienta de análisis estático ESLint como un paso en un flujo de trabajo. El paso `Run ESLint` ejecuta la herramienta ESLint y da como salida el archivo `results.sarif`. El flujo de trabajo entonces carga el archivo `results.sarif` a {% data variables.product.prodname_dotcom %} utilizando la acción `upload-sarif`. Para obtener más información acerca de crear un archivo de flujo de trabajo, consulta la sección "[Configurar un flujo de trabajo](/actions/configuring-and-managing-workflows/configuring-a-workflow)". - -```yml -name: "ESLint analysis" - -# Run workflow each time code is pushed to your repository and on a schedule. -# The scheduled workflow runs every at 00:00 on Sunday UTC time. -on: - push: - schedule: - - cron: '0 0 * * 0' - -jobs: - build: - steps: - - uses: actions/checkout@v2 - - name: Run npm install - run: npm install - # Runs the ESlint code analysis - - name: Run ESLint - # eslint exits 1 if it finds anything to report - run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true - # Uploads results.sarif to GitHub repository using the upload-sarif action - - uses: github/codeql-action/upload-sarif@v1 - with: - # Path to SARIF file relative to the root of the repository - sarif_file: results.sarif -``` - -### Leer más - -- "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" -- "[Administrar una ejecución de flujo de trabajo](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-your-workflow-history)" -- "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" -- "[Upload a SARIF file](/rest/reference/code-scanning#upload-a-sarif-file)" diff --git a/translations/es-XL/content/github/finding-talent-with-github-jobs/about-github-jobs.md b/translations/es-XL/content/github/finding-talent-with-github-jobs/about-github-jobs.md deleted file mode 100644 index 6c4e68644c..0000000000 --- a/translations/es-XL/content/github/finding-talent-with-github-jobs/about-github-jobs.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Acerca de Empleos GitHub -redirect_from: - - /articles/how-to-write-a-great-job-post/ - - /articles/about-github-jobs -intro: 'Puedes publicar un empleo en {% data variables.product.prodname_jobs %} para encontrar talentos para tu negocio.' -versions: - free-pro-team: '*' -topics: - - Jobs ---- - -Antes de poder publicar un empleo, debes crear una cuenta de {% data variables.product.prodname_dotcom %} y verificar tu dirección de correo electrónico. Para obtener más información, consulta "[Registrarse con una nueva cuenta de {% data variables.product.prodname_dotcom %} ](/articles/signing-up-for-a-new-github-account)" y "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". - -### Mejores prácticas para escribir la publicación de un empleo - -Cuando escribas la publicación de un empleo, haz que el título sea lo más descriptivo posible. Intenta mencionar el idioma o las tecnologías que requiere el empleo. - -En la descripción del empleo, incluye información acerca de la cultura de tu empresa y los beneficios que ofreces. Describe el puesto detalladamente, incluyendo información acerca de las responsabilidades del empleo y el equipo con el que el candidato trabajará. Enumera las principales habilidades requeridas para el empleo en orden de importancia. - -Para ayudar a los candidatos a encontrar tu publicación del empleo, verifica **Búsquedas de máxima actualidad** en la parte inferior de la página principal. Si alguna de estas categorías aplica para tu puesto vacante, inclúyelas en tu descripción del empleo. - -![Sección Búsquedas de máxima actualidad de {% data variables.product.prodname_dotcom %}](/assets/images/help/jobs/hot-searches.png) - -{% tip %} - -**Sugerencia:** {% data variables.product.prodname_dotcom %} no hace un seguimiento de las vistas de tu publicación del empleo ni del número de clics. Si quieres hacer un seguimiento del número de clics, puedes agregar parámetros de seguimiento a la URL que incluyes en el campo **Cómo postularse**. Para obtener más información, consulta "[Parámetros de la URL](https://support.google.com/google-ads/answer/6277564?hl=en)" de Google. - -{% endtip %} - -### Dar formato a tu publicación del empleo - -Puedes usar Markdown para dar formato a tu publicación del empleo. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)". - -### Leer más - -- [Cómo funiona {% data variables.product.prodname_jobs %} ](https://jobs.github.com/faq) en {% data variables.product.prodname_jobs %} diff --git a/translations/es-XL/content/github/finding-talent-with-github-jobs/index.md b/translations/es-XL/content/github/finding-talent-with-github-jobs/index.md deleted file mode 100644 index 3de8bd19c8..0000000000 --- a/translations/es-XL/content/github/finding-talent-with-github-jobs/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Encontrar talento con Empleos GitHub -redirect_from: - - /categories/72/articles/ - - /categories/jobs/ - - /categories/finding-talent-with-github-jobs -versions: - free-pro-team: '*' -topics: - - Jobs -children: - - /about-github-jobs ---- -### Índice diff --git a/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md deleted file mode 100644 index 6f8be08b28..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -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.' -redirect_from: - - /articles/where-can-i-find-open-source-projects-to-work-on/ - - /articles/finding-interesting-projects-on-github/ - - /articles/about-official-github-mirrors/ - - /articles/about-github-mirrors/ - - /articles/finding-open-source-projects-on-github - - /github/getting-started-with-github/finding-open-source-projects-on-github - - /github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github -versions: - free-pro-team: '*' -topics: - - Open Source ---- -### 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 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). - -Mantente al tanto de las actividades recientes de los repositorios y personas que sigues en la sección "Toda la actividad" de tu tablero personal. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". - -{% data reusables.support.ask-and-answer-forum %} - -### Encontrar informes de problemas iniciales - -Si ya sabes en qué proyecto quieres trabajar, puedes encontrar informes de problemas aptos para principiantes en ese repositorio si visitas `github.com///contribute`. Como ejemplo, puedes encontrar cómo realizar tu primera contribución a `electron/electron` en https://github.com/electron/electron/contribute. - -### Proyectos de código abierto con espejos en {% data variables.product.prodname_dotcom %} - -Algunos proyectos de código abierto presentan espejos en {% data variables.product.prodname_dotcom_the_website %} además de sus repositorios oficiales, que se alojan en otro lugar. - -Los siguientes son algunos de los repositorios más importantes que tienen sus espejos en {% data variables.product.prodname_dotcom_the_website %}: - -- [android](https://github.com/android) -- [The Apache Software Foundation](https://github.com/apache) -- [The Chromium Project](https://github.com/chromium) -- [The Eclipse Foundation](https://github.com/eclipse) -- [The FreeBSD Project](https://github.com/freebsd) -- [The Glasgow Haskell Compiler](https://github.com/ghc) -- [GNOME](https://github.com/GNOME) -- [The Linux kernel source tree](https://github.com/torvalds/linux) -- [Qt](https://github.com/qt) - -Para configurar tu propio espejo, puedes configurar [un gancho posrecepción](https://git-scm.com/book/en/Customizing-Git-Git-Hooks) en tu repositorio oficial del proyecto para subir automáticamente las confirmaciones a un repositorio espejo en {% data variables.product.product_name %}. - -Puedes buscar repositorios en función de si tienen un espejo o no. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-a-mirror)". - -### Leer más - -- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" -- "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)" diff --git a/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/following-people.md b/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/following-people.md deleted file mode 100644 index 65f70e051d..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/following-people.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Seguir a personas -intro: 'Puedes seguir a personas en {% data variables.product.product_name %} para recibir notificaciones acerca de su actividad{% if currentVersion == "free-pro-team@latest" %} y descubrir proyectos en sus comunidades{% endif %}.' -redirect_from: - - /articles/following-people - - /github/getting-started-with-github/following-people -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profile ---- -Cuando sigas a personas, verás su actividad pública en la vista de actividad de tus Noticias.{% if currentVersion == "free-pro-team@latest" %} Si alguien que tú sigues coloca una estrella en un repositorio público, {% data variables.product.product_name %} puede recomendarte el repositorio en la vista de descubrimientos de tus Noticias.{% endif %} Para seguir a una persona, visita su página de perfil y haz clic en **Seguir** debajo de su imagen de perfil. - -![Botón Follow user (Seguir usuario)](/assets/images/help/profile/follow-user-button.png) - -Para dejar de seguir a alguien, visita su página de perfil y haz clic en **Dejar de seguir** debajo de su imagen de perfil. - -{% if currentVersion == "free-pro-team@latest" %} -### Leer más - -- "[Guardar repositorios con estrellas](/articles/saving-repositories-with-stars/)" -- "[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)" -{% endif %} diff --git a/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/index.md b/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/index.md deleted file mode 100644 index 1a7537edcb..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Explorar proyectos en GitHub -intro: '' -redirect_from: - - /categories/stars/ - - /categories/87/articles/ - - /categories/exploring-projects-on-github/ - - /articles/exploring-projects-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Projects -children: - - /finding-ways-to-contribute-to-open-source-on-github - - /saving-repositories-with-stars - - /following-people ---- - diff --git a/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars.md deleted file mode 100644 index a326f54460..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Guardar repositorios con estrellas -intro: 'Puedes marcar con una estrella repositorios{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.16" %} y temas{% endif %} para hacer un rastreo de los proyectos que encuentras interesantes{% if currentVersion == "free-pro-team@latest" %} y descubrir el contenido relacionado en tus noticias{% endif %}.' -redirect_from: - - /articles/stars/ - - /articles/about-stars/ - - /articles/browsing-friends-stars/ - - /articles/managing-your-stars/ - - /articles/saving-repositories-with-stars - - /github/getting-started-with-github/saving-repositories-with-stars -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Puedes buscar, clasificar y filtrar tus repositorios y temas marcados con estrella en tu {% data variables.explore.your_stars_page %}.' - -### Acerca de las estrellas - -Marcar con estrellas tus repositorios y temas favoritos te facilitará encontrarlos posteriormente. Puedes ver todos los repositorios y temas que has marcado con estrellas visitando tu {% data variables.explore.your_stars_page %}. - -{% if currentVersion == "free-pro-team@latest" %} -Puedes marcar repositorios y temas con estrellas para descubrir proyectos similares en {% data variables.product.product_name %}. Cuando marcas repositorios o temas con estrellas, {% data variables.product.product_name %} puede recomendar contenido relacionado en la vista de tus noticias. 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)." -{% endif %} - -Marcar un repositorio con estrella también muestra reconocimiento al mantenedor del repositorio por su trabajo. Muchas de las clasificaciones de los repositorios de {% data variables.product.prodname_dotcom %} dependen de la cantidad de estrellas que tiene un repositorio. Además, [Explore](https://github.com/explore) muestra repositorios populares en base a la cantidad de estrellas que tienen. - -### Buscar estrellas - -![Buscar a través de las estrellas](/assets/images/help/stars/stars_search_bar.png) - -Puedes utilizar la barra de búsqueda para encontrar rápidamente los repositorios y temas que has marcado con estrella. La barra de búsqueda únicamente busca en los nombres de los temas y repositorios, y no en cualquier otro calificador (tal como el tamaño del repositorio o la fecha en la que se actualizó la última vez). - -### Clasificar y filtrar estrellas - -![Clasificar estrellas](/assets/images/help/stars/stars_sort_menu.png) - -En la esquina superior derecha de tu página de marcados con estrella, puedes clasificar los repositorios y temas marcados con las categorías de "recientemente marcado con estrella", "recientemente activo" y "más estrellas". - -En el lateral derecho de la página, puedes filtrar tu lista de repositorios con estrellas en base a su lenguaje. - -![Filtrar estrellas por lenguaje](/assets/images/help/stars/stars_filter_language.png) - -### Explorar las estrellas de tus amigos - - En el ángulo inferior derecho de la página, puedes explorar las estrellas de tus amigos. You can use this to find new repositories and topics to star. - -![Ver las estrellas de tus amigos](/assets/images/help/stars/stars_jump_to_a_friend.png) - -### Leer más - -- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" diff --git a/translations/es-XL/content/github/getting-started-with-github/index.md b/translations/es-XL/content/github/getting-started-with-github/index.md deleted file mode 100644 index 68450476ae..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/index.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Comenzar con GitHub -shortTitle: Empezar -intro: 'Aprende sobre los productos de {% data variables.product.prodname_dotcom %}, regístrate para obtener una cuenta y explora la comunidad {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /categories/54/articles/ - - /categories/bootcamp/ - - /categories/32/articles/ - - /categories/2/articles/ - - /categories/organizations/ - - /categories/about-github/ - - /categories/53/articles/ - - /categories/setup/ - - /categories/getting-started-with-github - - /categories/19/articles/ - - /categories/using-git - - /github/using-git -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -layout: product-landing -introLinks: - quickstart: /github/getting-started-with-github/quickstart -featuredLinks: - guides: - - /github/getting-started-with-github/githubs-products - - /github/getting-started-with-github/create-a-repo - - /github/getting-started-with-github/signing-up-for-a-new-github-account - popular: - - /github/getting-started-with-github/set-up-git - - /github/getting-started-with-github/github-glossary - - /github/getting-started-with-github/fork-a-repo - - /github/getting-started-with-github/keyboard-shortcuts - - /github/getting-started-with-github/saving-repositories-with-stars - guideCards: - - /github/getting-started-with-github/types-of-github-accounts - - /github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github - - /github/getting-started-with-github/troubleshooting-connectivity-problems -topics: - - Pull requests - - Issues - - Notifications - - Accounts -children: - - /quickstart - - /learning-about-github - - /signing-up-for-github - - /using-github - - /exploring-projects-on-github - - /getting-started-with-git - - /using-git ---- -### Índice diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/access-permissions-on-github.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/access-permissions-on-github.md deleted file mode 100644 index 9e18f22fad..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/access-permissions-on-github.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Permisos de acceso en GitHub -redirect_from: - - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do/ - - /articles/what-are-the-different-types-of-team-permissions/ - - /articles/what-are-the-different-access-permissions/ - - /articles/access-permissions-on-github - - /github/getting-started-with-github/access-permissions-on-github -intro: 'Si bien puedes otorgar acceso de lectura/escritura a los colaboradores en un repositorio personal, los miembros de una organización pueden tener más permisos de acceso granular para los repositorios de la organización.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Permissions - - Accounts ---- -### Cuentas de usuarios personales - -Un repositorio que es propiedad de una cuenta de usuario y tiene dos niveles de permiso: el *propietario del repositorio* y los *colaboradores*. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/articles/permission-levels-for-a-user-account-repository)". - -### Cuentas de organización - -Los miembros de la organización pueden tener roles de *propietario*{% if currentVersion == "free-pro-team@latest" %}, *gerente de facturación*,{% endif %} o *miembro*. Los propietarios tienen acceso administrativo completo a tu organización {% if currentVersion == "free-pro-team@latest" %}, mientras que los gerentes de facturación pueden administrar parámetros de facturación{% endif %}. El miembro tiene un rol predeterminado para todos los demás. Puedes administrar los permisos de acceso para múltiples miembros a la vez con equipos. Para obtener más información, consulta: -- [Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)" -- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" -- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" -- [Acerca de los equipos](/articles/about-teams)" - -{% if currentVersion == "free-pro-team@latest" %} - -### Cuentas de empresa - -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 "[Roles para una cuenta empresarial](/articles/roles-for-an-enterprise-account)". - -{% data reusables.gated-features.enterprise-accounts %} - -{% endif %} - -### Leer más - -- [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/exploring-early-access-releases-with-feature-preview.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/exploring-early-access-releases-with-feature-preview.md deleted file mode 100644 index d4e9646881..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/exploring-early-access-releases-with-feature-preview.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Explorar versiones de acceso anticipado con vista previa de la característica -intro: Puedes usar la vista previa de las características para ver los productos o las características que están disponibles en beta y para activar o desactivar cada característica de tu cuenta de usuario. -redirect_from: - - /articles/exploring-early-access-releases-with-feature-preview - - /github/getting-started-with-github/exploring-early-access-releases-with-feature-preview -versions: - free-pro-team: '*' -topics: - - Early access ---- -### ciclo de lanzamiento de {% data variables.product.prodname_dotcom %} - -Los productos y características de {% data variables.product.product_name %}pueden pasar por varias fases de lanzamiento. - -| Fase | Descripción | -| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Alfa | El producto o la característica está bajo un gran desarrollo y a menudo tiene requisitos y alcance cambiantes. Esta característica se encuentra disponible para propósitos de demostración y pruebas, pero puede no documentarse. Las versiones Alpha no necesariamente tienen una función completa, no se proporcionan Acuerdo de nivel de servicio (SLA) y no hay obligaciones de apoyo técnico. | -| Beta | El producto o característica está listo para una distribución más amplia. Las versiones beta pueden ser públicas o privadas, están documentadas, pero no tienen ningún SLA u obligación de soporte técnico. | -| Disponibilidad general (GA) | El producto o característica está completamente probado y abierto públicamente a todos los usuarios. Las versiones de GA están listas para su uso en producción, y se aplican el Acuerdo de nivel de servicio y las obligaciones de asistencia técnica asociados. | - -### Explorar versiones beta con vista previa de la característica - -Puedes ver una lista de características disponibles en beta y una breve descripción de cada característica. Cada característica incluye un enlace para proporcionar retroalimentación. - -1. En la esquina superior derecha de cualquier página, haz clic en tu foto de perfil, luego haz clic en **Feature preview** (Vista previa de la característica). ![Botón Feature preview (Vista previa de la característica)](/assets/images/help/settings/feature-preview-button.png) -2. Opcionalmente, a la derecha de una función, haz clic en **Enable** (Habilitar) o **Disable** (Inhabilitar). ![Activar el botón en la vista previa de la característica](/assets/images/help/settings/enable-feature-button.png) diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/faq-about-changes-to-githubs-plans.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/faq-about-changes-to-githubs-plans.md deleted file mode 100644 index a0167ca449..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/faq-about-changes-to-githubs-plans.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: Preguntas frecuentes sobre los cambios en los planes de GitHub -intro: 'Desde el 14 de abril de 2020, GitHub anunció que todas las características principales de la empresa son ahora gratuitas para todos.' -versions: - free-pro-team: '*' -topics: - - GitHub -redirect_from: - - /github/getting-started-with-github/faq-about-changes-to-githubs-plans ---- -### ¿Qué cambios en precios y planes para GitHub se anunciaron en el 14 de abril? - -GitHub anunció los siguientes cambios en sus planes y precios: - -- GitHub Free para organizaciones se encuentra inmediatamente disponible e incluye repositorios privados para usuarios ilimitados -- Todas las organizaciones que estaban utilizando Team para Código Abierto previamente tendrán ahora GitHub Free -- Github Free para desarrolladores individuales incluye ahora colaboradores ilimitados -- Las organizaciones e individuos que utilicen GitHub Free recibirán el Soporte de la Comunidad de GitHub -- GitHub Pro incluirá ahora 2GB de almacenamiento de paquetes y 10GB de transferencia de datos -- GitHub Pro ahora redujo su precio mensual a $4 -- GitHub Team tiene ahora un precio mensual reducido de $4 por usuario -- GitHub Team ya no tiene una cantidad mínima requerida de cinco plazas -- GitHub Team incluye 3,000 minutos de Acciones mensuales para los repositorios privados - -### ¿Cómo puedo mejorar mi plan? - -Para mejorar el plan de tu cuenta de usuario, consulta "[Mejorar tu suscripción de cuenta personal](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#upgrading-your-personal-accounts-subscription)". Para mejorar el plan de tu organización, consulta "[Mejorar la suscripción de tu organización](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#upgrading-your-organizations-subscription)". - -### ¿Cómo puedo bajar mi plan? - -Para bajar el plan de tu cuenta de usuario, consulta "[Bajar la suscripción de tu cuenta de usuario](/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription#downgrading-your-user-accounts-subscription)". Para bajar el plan de tu organización, consulta "[Bajar la suscripción de tu organización](/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription#downgrading-your-organizations-subscription)". - -### Si bajo de categoría desde GitHub Team o un plan tradicional hacia GitHub Free, ¿qué características perderé? -- Revisores requeridos en repositorios privados -- Ramas protegidas en repositorios privados -- Propietarios de código en repositorios privados -- GitHub Pages en repositorios privados -- Wikis en repositorios privados -- Asignados múltiples para informes de problemas y solicitudes de extracción en repositorios privados -- Revisores múltiples para solicitudes de extracción en repositorios privados -- Borradores de solicitudes de extracción en repositorios privados -- Referencias auto-vinculadas en repositorios privados -- Soporte estándar - -### ¿Cómo puedo crear una organización de GitHub Free o GitHub Team? - -Si tienes una cuenta en GitHub, crea una nueva organización en nuestra [página de plan de equipo](https://github.com/organizations/plan). Si no tienes una cuenta en GitHub, puedes [crear una en nuestra página principal](https://github.com/) y se te pedirá crear una organización durante el proceso de registro. - -### ¿Cómo puedo comparar las características de cada plan? - -Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. - -### ¿Por cuánto tiempo se permitirá un número ilimitado de colaboradores en GitHub Free? - -¡Por siempre! Este cambio es permanente. - -### Ya pagué por el plan anual de Pro o Team, ¿se me reembolsará por la diferencia de precio? - -Los clientes que están pagando anualmente por los planes de Pro o Team y se registraron antes del 14 de abril recibirán un reembolso por una cantidad prorrateada hasta finalizar su periodo de facturación anual. Por ejemplo, si llevas dos meses de suscripción y se te factura anualmente, recibirás un reembolso por la diferencia de precios de los diez meses restantes. Estos reembolsos se procesarán en 30 días, aproximadamente. Una vez que se haya procesado tu reembolso, se te enviará una notificación a la dirección de correo electrónico que hayas elegido para facturación. - -### ¿Cuál es la diferencia entre GitHub Free para desarrolladores individuales y GitHub Free para organizaciones? - -Para encontrar los detalles de las diferencias entre los productos de GitHub free, consulta la sección "[productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)". - -### ¿Cómo puedo tener más minutos de Actions si necesito más que la cantidad que se designa en el plan de GitHub Team? - -La mayoría de los equipos pequeños utiliza menos de 3,000 minutos mensuales de Actions, pero algunos equipos podrían utilizar más. Si tu equipo necesita minutos adicionales para repositorios privados, puedes incrementar tu límite de gastos para GitHub Actions. Los minutos de Actions y almacenamiento de paquetes siguen siendo gratuitos para tus repositorios públicos. Para obtener más información, consulta la sección "[Administrar tu límite de gastos para GitHub Actions](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)". - -### ¿Cómo me afectan los cambios en el límite de plazas? - -Ahora que {% data variables.product.prodname_team %} no requiere de un mínimo de plazas, si utilizas menos de cinco en tu organización, podrás eliminar las plazas pagadas para reducir tu cuenta. Para obtener más información, consulta la sección "[Bajar la categoría de tu suscripción de {% data variables.product.prodname_dotcom %}](/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription#removing-paid-seats-from-your-organization)". - -### ¿Cambiará algo para los equipos con plan de GitHub Team para código abierto? - -Si tu cuenta de organización utiliza el plan de GitHub Team para código abierto, se te migrará automáticamente a GitHub Free, lo cual incluye repositorios privados con colaboradores ilimitados, 2,000 minutos de actions para repositorios privados, y el Soporte de la Comunidad de GitHub. Los minutos de Actions y almacenamiento de paquetes siguen siendo gratuitos para tus repositorios públicos. - -### ¿Qué es el Soporte de la Comunidad de GitHub? - -El Soporte de la Comunidad de GitHub incluye soporte a través de nuestro [Foro de la Comunidad](https://github.community/), en donde puedes buscar soluciones de la comunidad de GitHub, hacer preguntas nuevas, y compartir ideas. Los Ingenieros de Soporte de GitHub Team son quienes atienden la parte de Soporte de la Comunidad de Github, y quienes moderan el Foro de la Comunidad en conjunto con nuestros miembros más activos en la misma. Si necesitas reportar spam, algún tipo de abuso, o si tienes problemas con el acceso a tu cuenta, puedes enviar un mensaje a nuestro Equipo de Soporte en https://support.github.com/.. - -### ¿Cómo afecta este cambio a los beneficios educacionales? - -Los estudiantes y maestros seguirán recibiendo todos los beneficios que reciben hoy en día. GitHub continuará ofreciendo GitHub Pro como parte de los beneficios de su [Paquete de Desarrollador para Estudiantes](https://education.github.com/pack) a todos los estudiantes. Adicionalmente, los maestros continuarán teniendo acceso a GitHub Team como parte de las [Herramientas para Maestros](https://education.github.com/toolbox). - -### ¿Cómo me afecta esto si actualmente pago por factura? - -Si actualmente eres un cliente que paga por factura, contacta por correo electrónico a tu representante de ventas para recibir más detalles. Si no sabes quién es tu representante de ventas, contacta a tu gerente de facturación o propietario de cuenta. - -### ¿Cómo va afectar esto a los usuarios y organizaciones que se encuentran en regiones donde se aplican las sanciones del gobierno de los EE.UU? government sanctions are applied? - -Due to U.S. Debido a los controles de comercio y restricciones legales, GitHub no puede proporcionar servicios para repositorios privados y servicios pagados a cuentas que se encuentren en las zonas sancionadas por los EE.UU. sanctioned regions. Sin embargo, GitHub ha preservado el acceso a los servicios gratuitos para repositorios públicos. Por favor lee sobre [GitHub y los Controles Comerciales](/github/site-policy/github-and-trade-controls) para obtener más información. - -GitHub seguirá fomentando, en conjunto con los reguladores de los EE.UU., el mejor acceso posible a los servicios colaborativos de código abierto para desarrolladores en regiones sancionadas, incluyendo repositorios privados gratuitos. Creemos que, el ofrecer estos servicios gratuitos, apoya la política externa de los EE.UU. de fomentar el flujo libre de información y libertad de expresión en estas regiones. regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/git-and-github-learning-resources.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/git-and-github-learning-resources.md deleted file mode 100644 index 645c001346..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/git-and-github-learning-resources.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Recursos de aprendizaje de Git y GitHub -redirect_from: - - /articles/good-resources-for-learning-git-and-github/ - - /articles/what-are-other-good-resources-for-learning-git-and-github/ - - /articles/git-and-github-learning-resources - - /github/getting-started-with-github/git-and-github-learning-resources -intro: 'Hay muchos recursos útiles de Git y {% data variables.product.product_name %} disponibles en la web. La siguientes es una pequeña lista de nuestros favoritos.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -authors: - - GitHub ---- -### Utilizar GitHub - -Para familiarizarte con Git, visita el [sitio oficial del proyecto Git](https://git-scm.com) y lee el [libro electrónico Progit](http://git-scm.com/book). Puedes revisar la [lista de comandos de Git](https://git-scm.com/docs) o la [referencia para buscar comandos de Git](http://gitref.org) mientras usas el simulador [Try Git](https://try.github.com). - -### Uso de {% data variables.product.product_name %} - -{% if currentVersion == "free-pro-team@latest" %} - -{% data variables.product.prodname_learning %} ofrece cursos interactivos gratuitos integrados en {% data variables.product.prodname_dotcom %} con evaluación y asistencia instantáneas y automatizadas. Aprende a abrir tu primera solicitud de extracción, hacer tu primera contribución de código abierto, crear un sitio {% data variables.product.prodname_pages %}, y mucho más. Para obtener más información acerca de los cursos ofrecidos, consulta [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). - -{% endif %} - -Adquiere más conocimientos con {% data variables.product.product_name %} a través de nuestros artículos de [seminario intensivo](/categories/bootcamp/). Consulta nuestro [ flujo de {% data variables.product.prodname_dotcom %}](https://guides.github.com/introduction/flow) para acceder a una introducción del proceso. Consulta nuestras [guías de descripción general](https://guides.github.com) para conocer nuestros conceptos básicos. - -{% data reusables.support.ask-and-answer-forum %} - -#### Ramas, bifurcaciones y solicitudes de extracción - -Conoce más sobre las [ramas de Git](http://learngitbranching.js.org/) usando una herramienta interactiva. Lee más acerca de [bifrucaciones](/articles/about-forks) y [solicitudes de extracción](/articles/using-pull-requests), además de [cómo usar las solicitudes de extracción](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) en {% data variables.product.prodname_dotcom %}. - -Accede a guías de referencia rápida acerca de la [línea de comando](https://hub.github.com) y de [guías de comprobación, hojas de referencia de {% data variables.product.prodname_dotcom %}, y mucho más](https://services.github.com/on-demand/resources). - -#### Ponte al día - -Nuestro {% data variables.product.prodname_dotcom %} [canal con guías y capacitación de YouTube](https://youtube.com/githubguides) ofrece tutoriales acerca de [solicitudes de extracción](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [ bifurcaciones](https://www.youtube.com/watch?v=5oJHRbqEofs), las funciones de [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22) y [reinicio](https://www.youtube.com/watch?v=BKPjPMVB81g). Cada tema se cubre en menos de 5 minutos. - -### Capacitación - -#### Clases gratuitas - -{% data variables.product.product_name %} ofrece una serie de cursos de capacitación interactivos a pedido [on-demand training courses](https://services.github.com/on-demand/), entre otros, {% data variables.product.prodname_dotcom %} 101: [Introducción](https://services.github.com/on-demand/intro-to-github/), {% data variables.product.prodname_dotcom %} 102: [GitHub Desktop](https://services.github.com/on-demand/github-desktop) y {% data variables.product.prodname_dotcom %} 103: [Línea de comando](https://services.github.com/on-demand/github-cli). - -#### Programas educativos basados en la web de {% data variables.product.prodname_dotcom %} - -{% data variables.product.prodname_dotcom %} ofrece [capacitaciones](https://services.github.com/#upcoming-events) en vivo con un enfoque práctico basado en proyectos tanto para los amantes de la línea de comando como para quienes no están familiarizados con esta herramienta. - -#### Capacitación para tu compañía - -{% data variables.product.prodname_dotcom %} ofrece [clases presenciales](https://services.github.com/#offerings) a cargo de nuestros capacitadores sumamente experimentados. [Contáctanos](https://services.github.com/#contact) para que podamos responder tus preguntas relacionadas con la capacitación. - -### Extras - -Un [curso de Git en línea](http://www.codeschool.com/courses/git-real) interactivo de [Code School](http://codeschool.com) con siete niveles y muchos ejercicios en un formato amigable. Adapta libremente nuestras [plantillas .gitignore](https://github.com/github/gitignore) para que resuelvan tus necesidades. - -Amplía el alcance de tu {% data variables.product.prodname_dotcom %} con[integraciones de {% if currentVersion == "free-pro-team@latest" %}](/articles/about-integrations){% else %}integraciones{% endif %}, o instala [{% data variables.product.prodname_desktop %}](https://desktop.github.com) y el poderoso editor de texto [Atom](https://atom.io). - -Descubre cómo lanzar y hacer crecer tu proyecto de código abierto con las [Guías de código abierto](https://opensource.guide/). diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/git-cheatsheet.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/git-cheatsheet.md deleted file mode 100644 index d0c25e727d..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/git-cheatsheet.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Hoja introductoria de Git -redirect_from: - - /articles/git-cheatsheet - - /github/getting-started-with-github/git-cheatsheet -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -Aprender todos los comandos de Git disponibles de una sola vez puede resultan una tarea intimidante. Mantén uno de nuestras [Hojas introductorias de Git](https://services.github.com/on-demand/resources/cheatsheets/) cerca para poder consultarla. El uso de Hojas introductorias de Git se encuentra disponible en distintos idiomas. Para obtener más información, consulta la [página de recursos en el sitio web GitHub Services](https://services.github.com/on-demand/resources/). - -Además, visita nuestra página de [recursos para el aprendizaje de Git y GitHub](/articles/git-and-github-learning-resources/), que tiene enlaces a guías, videos, y mucho más. diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-cli.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-cli.md deleted file mode 100644 index 371a32cca0..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-cli.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: CLI de GitHub -intro: 'The {% data variables.product.prodname_cli %} is a command-line tool for using {% data variables.product.product_name %} features on your computer.' -versions: - free-pro-team: '*' - enterprise-server: '>2.19' - github-ae: '*' -topics: - - CLI -redirect_from: - - /github/getting-started-with-github/github-cli ---- -### Acerca de {% data variables.product.prodname_cli %} - -{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.product_name %} from your computer's command line. When you're working from the command line, you can use the {% data variables.product.prodname_cli %} to save time and avoid switching context. - -You can use the following {% data variables.product.prodname_dotcom %} features with the {% data variables.product.prodname_cli %}. - -- View, create, clone, and fork repositories -- Create, close, and list issues and pull requests -- Review, diff, and merge pull requests -- Create, edit, list, and view gists - -Para obtener más información acerca de lo que puedes hacer con {% data variables.product.prodname_cli %}, consulta el [{% data variables.product.prodname_cli %}manual](https://cli.github.com/manual). - -### Instalar {% data variables.product.prodname_cli %} - -Ver las instrucciones de instalación de {% data variables.product.prodname_cli %} para MacOS, Windows y Linux en la [{% data variables.product.prodname_cli %}página](https://cli.github.com). - -### Compartir la retroalimentación - -Si tienes retroalimentación o solicitudes de características, puedes abrir un informe de problemas en el [repositorio `cli/cli`](https://github.com/cli/cli). diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-desktop.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-desktop.md deleted file mode 100644 index 8b3e9c02d1..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-desktop.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: GitHub Desktop -intro: '{% data variables.product.prodname_desktop %} extiende y simplifica el flujo de trabajo de tu Git y tu {% data variables.product.prodname_dotcom %} utilizando una interface visual.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Desktop -redirect_from: - - /github/getting-started-with-github/github-desktop ---- -### Acerca de {% data variables.product.prodname_desktop %} - -{% data reusables.desktop.about-github-desktop %} - -Para obtener información acerca de {% data variables.product.prodname_desktop %}, consulta la sección "[Instalar y configurar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop)" en la documentación de {% data variables.product.prodname_desktop %}. - -### Compartir la retroalimentación - -Si tienes retroalimentación o solicitudes de características, puedes abrir un informe de problema en el [repositorio `desktop/desktop`](https://github.com/desktop/desktop). diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-for-mobile.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-for-mobile.md deleted file mode 100644 index d89e32fe59..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-for-mobile.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: GitHub para móvil -intro: 'Clasifica, colabora y administra tu trabajo en {% data variables.product.company_short %} desde tu dispositivo móvil.' -versions: - free-pro-team: '*' - enterprise-server: '>=3.0' -topics: - - Mobile -redirect_from: - - /github/getting-started-with-github/github-for-mobile ---- -### Acerca de {% data variables.product.prodname_mobile %} - -{% data variables.product.prodname_mobile %} está disponible actualmente para usuarios de {% data variables.product.prodname_dotcom_the_website %} como una aplicación de iOS y Android. - -{% data variables.product.prodname_mobile %} te proporciona una manera de realizar trabajo de alto impacto en {% data variables.product.prodname_dotcom %} de forma rápida y desde cualquier lugar. {% data variables.product.prodname_mobile %} es una manera segura y estable de acceder a tus datos de {% data variables.product.prodname_dotcom %} a través de una aplicación cliente confiable de primera parte. - -Con {% data variables.product.prodname_mobile %} puedes: -- Administrar, clasificar y borrar las notificaciones -- Leer, revisar y colaborar en informes de problemas y solicitudes de extracción -- Buscar, navegar e interactuar con usuarios, repositorios y organizaciones -- Recibir notificaciones para subir información cuando alguien menciona tu nombre de usuario - -Para obtener más información sobre las notificaciones de {% data variables.product.prodname_mobile %}, consulta "[Configurando notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)." - -### Instalar {% data variables.product.prodname_mobile %} - -Para instalar {% data variables.product.prodname_mobile %} para Android o iOS, consulta la sección [{% data variables.product.prodname_mobile %}](https://github.com/mobile). - -### Administrar Enlaces Universales para {% data variables.product.prodname_mobile %} en iOS - -{% data variables.product.prodname_mobile %} habilita automáticamente los Enlaces Universales para iOS. Cuando tocas en cualquier enlace de {% data variables.product.product_name %}, la URL destino se abrirá en {% data variables.product.prodname_mobile %} en vez de en Safari. Para obtener más información, consulta la sección[Enlaces Universales](https://developer.apple.com/ios/universal-links/) en el sitio para Desarrolladores de Apple. - -Para inhabilitar los Enlaces Universales, presiona sostenidamente cualquier enlace de {% data variables.product.prodname_dotcom %} y luego toca en **Abrir**. Cada vez que toques en un enlace de {% data variables.product.prodname_dotcom %} posteriormente, la URL destino se abrirá en Safari en vez de en {% data variables.product.prodname_mobile %}. - -Para volver a habilitar los Enlaces Universales, sostén cualquier enlace de {% data variables.product.prodname_dotcom %} y luego toca en **Abrir en {% data variables.product.prodname_dotcom %}**. - -### Compartir la retroalimentación - -Si tienes retroalimentación o solicitudes de características para {% data variables.product.prodname_mobile %}, puedes enviarnos un correo electrónico a mobilefeedback@github.com. - - -### Abandonar los lanzamientos beta para iOS - -Si estás probando un lanzamiento beta de {% data variables.product.prodname_mobile %} para iOS utilizando TestFlight, puedes abandonar el beta en cualquier momento. - -1. En tu dispositivo iOS, abre la aplicación de TestFlight. -2. Debajo de "Apps", toca en **{% data variables.product.prodname_dotcom %}**. -3. En la parte inferior de la página, toca en **Dejar de Probar**. diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-glossary.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-glossary.md deleted file mode 100644 index 39ce906b49..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/github-glossary.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Glosario de GitHub -intro: 'A continuación aparece una lista de algunos términos específicos de Git y {% data variables.product.prodname_dotcom %} que usamos en nuestros sitios y en la documentación.' -redirect_from: - - /articles/github-glossary - - /github/getting-started-with-github/github-glossary -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -{% for term in site.data.glossaries.external %} - ### {{term.term}} - {{term.description}} - --- -{% endfor %} - ---- - -### Leer más - -- [El glosario oficial de Git](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html) -- [Referencia de Git](http://gitref.org/) -- [SCM de Git](https://git-scm.com/doc) diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/githubs-products.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/githubs-products.md deleted file mode 100644 index 97ebb5cbaf..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/githubs-products.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -title: Productos de GitHub -redirect_from: - - /articles/github-s-products - - /articles/githubs-products - - /github/getting-started-with-github/githubs-products -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - CLI - - Mobile - - Desktop - - Security ---- -{% data variables.product.prodname_dotcom %} ofrece productos gratuitos y pagos. Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %} - -### {% data variables.product.prodname_free_user %} for user accounts - -Con {% data variables.product.prodname_free_team %} para cuentas de usuario, puedes trabajar con colaboradores ilimitados en repositorios públicos ilimitados con un juego completo de características, y en repositorios privados ilimitados con un conjunto limitado de características. - -Con {% data variables.product.prodname_free_user %}, tu cuenta de usuario incluye: -- {% data variables.product.prodname_gcf %} -- {% data variables.product.prodname_dependabot_alerts %} -- Aplicación de la autenticación de dos factores -- 2,000 minutos de {% data variables.product.prodname_actions %} -- 500MB de almacenamiento de {% data variables.product.prodname_registry %} - -### {% data variables.product.prodname_pro %} - -Adicionalmente a las características disponibles con {% data variables.product.prodname_free_user %} para cuentas de usuario, {% data variables.product.prodname_pro %} incluye: -- {% data variables.contact.github_support %} por correo electrónico -- 3,000 minutos de {% data variables.product.prodname_actions %} -- 2GB de almacenamiento de {% data variables.product.prodname_registry %} -- Herramientas y perspectivas avanzadas en repositorios privados: - - Revisores requeridos para solicitudes de extracción - - Revisores múltiples para solicitudes de extracción - - Referencias auto-vinculadas - - {% data variables.product.prodname_pages %} - - Wikis - - Ramas protegidas - - Propietarios del código - - Gráficos de información del repositorio: pulso, contribuyentes, tráfico, confirmaciones, frecuencia de código, red y bifurcaciones - -### {% data variables.product.prodname_free_team %} para organizaciones - -Con {% data variables.product.prodname_free_team %} para organizaciones, puedes trabajar con colaboradores ilimitados en repositorios públicos ilimitados con un juego completo de características, o en repositorios privados ilimitados con un conjunto limitado de características. - -Adicionalmente a las características disponibles con {% data variables.product.prodname_free_user %} para cuentas de usuario, {% data variables.product.prodname_free_team %} para organizaciones incluye: -- {% data variables.product.prodname_gcf %} -- Debates de equipo -- Controles de acceso del equipo para administrar grupos -- 2,000 minutos de {% data variables.product.prodname_actions %} -- 500MB de almacenamiento de {% data variables.product.prodname_registry %} - -### {% data variables.product.prodname_team %} - -Adicionalmente a las características disponibles con {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %} incluye: -- {% data variables.contact.github_support %} por correo electrónico -- 3,000 minutos de {% data variables.product.prodname_actions %} -- 2GB de almacenamiento de {% data variables.product.prodname_registry %} -- Herramientas y perspectivas avanzadas en repositorios privados: - - Revisores requeridos para solicitudes de extracción - - Revisores múltiples para solicitudes de extracción - - {% data variables.product.prodname_pages %} - - Wikis - - Ramas protegidas - - Propietarios del código - - Gráficos de información del repositorio: pulso, contribuyentes, tráfico, confirmaciones, frecuencia de código, red y bifurcaciones - - Solicitudes de extracción en borrador - - Revisores de equipo para solicitudes de extracción - - Recordatorios programados - -{% data reusables.github-actions.actions-billing %} - -### {% data variables.product.prodname_enterprise %} - -{% data variables.product.prodname_enterprise %} incluye dos opciones de despliegue: hospedado en la nuba y auto-hospedado. - -Adicionalmente a las características disponibles con {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} incluye: -- {% data variables.contact.enterprise_support %} -- Controles de seguridad, cumplimiento e implementación adicionales -- Autenticación con inicio de sesión único SAML -- Provisión de acceso con SAML o SCIM -- {% data variables.product.prodname_github_connect %} - -{% data variables.product.prodname_ghe_cloud %} también incluye lo siguiente: -- {% data variables.contact.enterprise_support %}. Para obtener más información, consulta "{% data variables.product.prodname_ghe_cloud %} soporte" y "{% data variables.product.prodname_ghe_cloud %} Adenda." -- 50,000 minutos de {% data variables.product.prodname_actions %} -- 50GB de almacenamiento de {% data variables.product.prodname_registry %} -- Un acuerdo de nivel de servicio por un tiempo de actividad mensual del 99,95 % -- 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 %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)". - -Para obtener más información acerca de hospedar tu propia instancia de [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), contacta a {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %} - -### {% data variables.product.prodname_ghe_one %} - -{% data variables.product.prodname_ghe_one %} incluye [{% data variables.product.prodname_enterprise %}](#github-enterprise), mas: - -- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %} -- {% data variables.product.prodname_insights %} -- {% data variables.product.prodname_advanced_security %} -- [{% data variables.product.prodname_learning %} para organizaciones](https://lab.github.com/organizations) - -Para obtener más información acerca de registrarse para {% data variables.product.prodname_ghe_one %}, contacta al [equipo de Ventas de {% data variables.product.product_name %}](https://enterprise.github.com/contact). diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/index.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/index.md deleted file mode 100644 index ffffd001ba..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Obtener información sobre GitHub -intro: '' -redirect_from: - - /articles/learning-about-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - CLI - - Mobile - - Desktop - - Security -children: - - /githubs-products - - /github-language-support - - /about-github-advanced-security - - /types-of-github-accounts - - /access-permissions-on-github - - /faq-about-changes-to-githubs-plans ---- - diff --git a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/types-of-github-accounts.md b/translations/es-XL/content/github/getting-started-with-github/learning-about-github/types-of-github-accounts.md deleted file mode 100644 index 201ae14252..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/learning-about-github/types-of-github-accounts.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Tipos de cuentas de GitHub -intro: 'Tu cuenta de usuario es tu identidad en {% data variables.product.product_location %}. Tu cuenta de usuario puede ser miembro de cualquier cantidad de organizaciones.{% if currentVersion == "free-pro-team@latest" %} Las organizaciones pueden pertenecer a cuentas de empresa.{% endif %}' -redirect_from: - - /manage-multiple-clients/ - - /managing-clients/ - - /articles/what-s-the-difference-between-user-and-organization-accounts/ - - /articles/differences-between-user-and-organization-accounts/ - - /articles/types-of-github-accounts - - /github/getting-started-with-github/types-of-github-accounts -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - CLI - - Mobile - - Desktop - - Security ---- -{% if currentVersion == "free-pro-team@latest" %} -Para encontrar un listado completo de características para cada producto de {% data variables.product.product_name %}, consulta la sección "[Productos de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)". -{% endif %} - -### Cuentas de usuarios personales - -Toda persona que utilice {% data variables.product.product_location %} tiene su propia cuenta de usuario, la cual incluye: - -{% if currentVersion == "free-pro-team@latest" %} - -- Repositorios públicos y privados ilimitados con {% data variables.product.prodname_free_user %} -- Colaboradores ilimitados con {% data variables.product.prodname_free_user %} -- Funciones adicionales para los repositorios privados con {% data variables.product.prodname_pro %} -- Capacidad para [invitar colaboradores del repositorio](/articles/inviting-collaborators-to-a-personal-repository) - -{% else %} - -- Repositorios y [colaboradores](/articles/permission-levels-for-a-user-account-repository) ilimitados -- Capacidad para [agregar colaboradores del repositorio ilimitados](/articles/inviting-collaborators-to-a-personal-repository) - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -{% tip %} - -**Tips**: - -- Puedes utilizar una cuenta para múltiples propósitos, como uso personal y uso comercial. No recomendamos crear más de una cuenta. Para obtener más información, consulta "[Fusionar múltiples cuentas de usuario](/articles/merging-multiple-user-accounts)". -- Las cuentas de usuario están pensadas para seres humanos, pero le puedes dar una a un robot, como un bot de integración continua, si resulta necesario. - -{% endtip %} - -{% else %} - -{% tip %} - -**Sugerencia**: Las cuentas de usuario están pensadas para seres humanos, pero le puedes dar una a un robot, como un bot de integración continua, si resulta necesario. - -{% endtip %} - -{% 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. - -{% data reusables.organizations.organizations_include %} - -{% if currentVersion == "free-pro-team@latest" %} - -### Cuentas de empresa - -Con las cuentas de empresa, puedes administrar de forma centralizada la política y la facturación de múltiples {% data variables.product.prodname_dotcom_the_website %} organizaciones. {% data reusables.gated-features.enterprise-accounts %} - -{% endif %} - -### Leer más - -{% if currentVersion == "free-pro-team@latest" %}- "[Iniciar sesión en una cuenta {% data variables.product.prodname_dotcom %} nueva](/articles/signing-up-for-a-new-github-account)" -- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/githubs-products)"{% endif %} -- "[Crear una cuenta de organización nueva](/articles/creating-a-new-organization-account)" diff --git a/translations/es-XL/content/github/getting-started-with-github/quickstart/be-social.md b/translations/es-XL/content/github/getting-started-with-github/quickstart/be-social.md deleted file mode 100644 index b8a47ba276..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/quickstart/be-social.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Ser social -redirect_from: - - /be-social/ - - /articles/be-social - - /github/getting-started-with-github/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.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profile - - Pull requests - - Issues - - Notifications - - Accounts ---- -Para conocer más sobre cómo acceder a tu tablero personal, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". - -### Seguir a personas - -Cuando sigues a alguien en {% data variables.product.product_location %}, recibirás notificaciones en tu tablero personal sobre su actividad. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". - -Haz clic en **Follow** (Seguir) en la página de perfil de una persona para seguirla. - -![Botón Follow user (Seguir usuario)](/assets/images/help/profile/follow-user-button.png) - -### Ver un repositorio - -Puedes ver un repositorio para recibir notificaciones para las nuevas solicitudes de extracción y propuestas. Cuando el propietario actualiza el repositorio, verás los cambios en tu tablero personal. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Observar y dejar de observar un repositorio](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}". - -Haz clic en **Watch** (Ver) en la parte superior del repositorio que desas ver. - -![Botón Watch repository (Ver repositorio)](/assets/images/help/repository/repo-actions-watch.png) - -### Unirse a la conversación - -{% data reusables.support.ask-and-answer-forum %} - -### Hacer un poco más - -#### Crear solicitudes de extracción - - Es posible que desees contribuir al proyecto de otras personas, ya sea para agregar características o para arreglar errores. Luego de realizar cambios, permite que el autor original lo sepa al enviar una solicitud de extracción. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." - - ![Botón Pull request (Solicitud de extracción)](/assets/images/help/repository/repo-actions-pullrequest.png) - -#### Usar propuestas - -Al colaborar en un repositorio, usa las propuestas para realizar el seguimiento de ideas, mejoras, tareas o errores. Para obtener más información, consulta '[Acerca de las propuestas](/articles/about-issues/)". - -![Botón Issues (Propuestas)](/assets/images/help/repository/repo-tabs-issues.png) - -#### Participación en 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 administradores pueden establecer equipos con permisos especiales, tener un perfil de organización pública y realizar el seguimiento de la actividad dentro de la organización. Para obtener más información, consulta "[Acerca de las organizaciones](/articles/about-organizations)". - -![Desplegable de contexto para cambiar cuenta](/assets/images/help/overview/dashboard-contextswitcher.png) - -#### Explorar otros proyectos en {% data variables.product.prodname_dotcom %} - -Descubre proyectos interesantes al utilizar {% data variables.explore.explore_github %}, [Explorar repositorios](https://github.com/explore), y el {% data variables.explore.trending_page %}. Marca con una estrella los proyectos interesantes y regresa posteriormente. Visita tu {% data variables.explore.your_stars_page %} para ver todos los proyectos marcados con una estrella. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard/)". - -### Celebrar - -Ahora estás conectado con la comunidad de {% data variables.product.product_name %}. ¿Qué deseas hacer ahora? - -![Marcar un proyecto con una estrella](/assets/images/help/stars/star-a-project.png) - -- [Configurar Git](/articles/set-up-git) -- [Crear un repositorio](/articles/create-a-repo) -- [Bifurcar un repositorio](/articles/fork-a-repo) -- **Ser social** -- {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-XL/content/github/getting-started-with-github/quickstart/create-a-repo.md b/translations/es-XL/content/github/getting-started-with-github/quickstart/create-a-repo.md deleted file mode 100644 index 59d4bc9c06..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/quickstart/create-a-repo.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Crear un repositorio -redirect_from: - - /create-a-repo/ - - /articles/create-a-repo - - /github/getting-started-with-github/create-a-repo -intro: 'Para subir tu proyecto a {% data variables.product.product_location %}, deberás crear un repositorio donde alojarlo.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests - - Issues - - Notifications - - Accounts ---- -Puedes almacenar distintos proyectos en los repositorios de {% data variables.product.product_name %}, incluso proyectos de código abierto. Con [proyectos de código abierto](http://opensource.org/about), puedes compartir el código para hacer que el software funcione mejor y sea más confiable. - -{% note %} - -**Nota:** Puedes crear repositorios públicos para un proyecto de código abierto. Cuando crees un repositorio público, asegúrate de incluir un [archivo de licencia](http://choosealicense.com/) que determine cómo deseas que se comparta tu proyecto con otros usuarios. {% data reusables.open-source.open-source-guide-repositories %}{% data reusables.open-source.open-source-learning-lab %} - -{% endnote %} - -{% data reusables.repositories.create_new %} -2. Escribe un nombre corto y fácil de recordar para tu repositorio. Por ejemplo: "hola-mundo". ![Campo para ingresar un nombre para el repositorio](/assets/images/help/repository/create-repository-name.png) -3. También puedes agregar una descripción de tu repositorio. Por ejemplo, "Mi primer repositorio en {% data variables.product.product_name %}". ![Campo para ingresar una descripción para el repositorio](/assets/images/help/repository/create-repository-desc.png) -{% data reusables.repositories.choose-repo-visibility %} -{% data reusables.repositories.initialize-with-readme %} -{% data reusables.repositories.create-repo %} - -¡Felicitaciones! Has creado correctamente tu primer repositorio y lo has inicializado con un archivo *README*. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also create repositories using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. - -{% endtip %} -{% endif %} - -### Confirma tu primer cambio - -Una *[confirmación](/articles/github-glossary#commit)* es como una instantánea de todos los archivos de tu proyecto en un momento en particular. - -Cuando creaste tu nuevo repositorio, lo inicializaste con un archivo *README*. 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. - -Confirmemos un cambio en el archivo *README*. - -1. Es la lista de archivos de tu repositorio, haz clic en ***README.md***. ![Archivo Readme en la lista de archivos](/assets/images/help/repository/create-commit-open-readme.png) -2. En el contenido del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. -3. En la pestaña **Editar archivo**, escribe alguna información sobre ti. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png) -{% data reusables.files.preview_change %} -5. Revisa los cambios que realizaste en el archivo. Verás el contenido nuevo en verde. ![Vista previa del archivo](/assets/images/help/repository/create-commit-review.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} - -### Celebrar - -¡Felicitaciones! Has creado un repositorio, además de un archivo *README*, y has creado tu primera confirmación en {% data variables.product.product_location %}. ¿Qué deseas hacer ahora? - -- "[Configurar Git](/articles/set-up-git)" -- **Crear un repositorio** -- "[Bifurcar un repositorio](/articles/fork-a-repo)" -- "[Socializar](/articles/be-social)" -- {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-XL/content/github/getting-started-with-github/quickstart/fork-a-repo.md b/translations/es-XL/content/github/getting-started-with-github/quickstart/fork-a-repo.md deleted file mode 100644 index 18e9985f5d..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/quickstart/fork-a-repo.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -title: Bifurcar un repositorio -redirect_from: - - /fork-a-repo/ - - /forking/ - - /articles/fork-a-repo - - /github/getting-started-with-github/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. -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests - - Issues - - Notifications - - Accounts ---- -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. - -#### Proponer cambios para el proyecto de otra persona - -Por ejemplo, puedes utilizar ramificaciones para proponer cambios relacionados con arreglar un error. En lugar de registrar una propuesta para un error que has encontrado, puedes hacer lo siguiente: - -- Bifurcar el repositorio. -- Solucionar el problema. -- Submit a pull request to the project owner. - -#### Usar el proyecto de otra persona como inicio de tu propia idea - -El software de código abierto se basa en la idea de que, si compartimos el código, podemos crear software más confiable y mejor. Para obtener más información, consulta la sección "[Acerca de la Iniciativa de Código Abierto](http://opensource.org/about)" en la Iniciativa de Código Abierto. - -Cuando creas tu repositorio público desde una ramificación del proyecto de alguien más, asegúrate de incluir el archivo de licencia que determine cómo quieres que se comparta tu proyecto con los demás. Para obtener más información, consulta la sección "[Elegir una licencia de código abierto](http://choosealicense.com/)" en choosealicense. - -{% data reusables.open-source.open-source-guide-repositories %}{% data reusables.open-source.open-source-learning-lab %} - -{% note %} - -**Nota**: {% data reusables.repositories.desktop-fork %} - -{% endnote %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also fork a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo fork`](https://cli.github.com/manual/gh_repo_fork)" in the {% data variables.product.prodname_cli %} documentation. - -{% endtip %} -{% endif %} - -### Bifurcar un repositorio a modo de ejemplo - -Bifurcar un repositorio es un proceso muy simple que lleva dos pasos. Hemos creado un repositorio para que practiques. - -1. En {% data variables.product.product_location %}, dirígete al repositorio [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife). -2. En el ángulo superior derecho de la página, haz clic en **Bifurcar**. ![Botón Bifurcar](/assets/images/help/repository/fork_button.jpg) - -### Mantener tu bifurcación sincronizada - -Puedes ramificar un proyecto para proponer cambios en los repositorios precedentes u originales. En este caso, es una buena práctica sincronizar tu bifurcación periódicamente con el repositorio ascendente. Para hacerlo, deberás usar Git en la línea de comando. Puedes practicar cómo configurar el repositorio precedente utilizando el mismo repositorio [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) que acabas de ramificar. - -#### Paso 1: Configurar Git - -Si todavía no lo has hecho, primero debes [configurar Git](/articles/set-up-git). No olvides [configurar la autenticación a {% data variables.product.product_location %} desde Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git). - -#### Paso 2: Crear un clon local de tu bifurcación - -Ahora tienes una bifurcación del repositorio Spoon-Knife, pero no tienes los archivos de ese repositorio en tu computadora. Let's create a clone of your fork locally on your computer. - -1. En {% data variables.product.product_name %}, dirígete a **tu bifurcación** del repositorio Spoon-Knife. -{% data reusables.repositories.copy-clone-url %} -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.command_line.change-current-directory-clone %} -4. Escribe `git clone`, y luego pega la URL que copiaste antes. Se verá así, con tu nombre de usuario de {% data variables.product.product_name %} en lugar de `YOUR-USERNAME`: - ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife - ``` - -5. Presiona **Enter** (Intro). Se creará tu clon local. - ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife - > Cloning into `Spoon-Knife`... - > remote: Counting objects: 10, done. - > remote: Compressing objects: 100% (8/8), done. - > remove: Total 10 (delta 1), reused 10 (delta 1) - > Unpacking objects: 100% (10/10), done. - ``` - -Ahora tienes una copia local de tu ramificación en el repositorio Spoon-Knife. - -#### Paso 3: Configurar Git para sincronizar tu bifurcación con el repositorio original Spoon-Knife - -Cuando bifurcas un proyecto para proponer cambios en el repositorio original, puedes configurar Git para extraer cambios del original, o repositorio ascendente, en el clon local de tu bifurcación. - -1. En {% data variables.product.product_name %}, dirígete al repositorio [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife). -{% data reusables.repositories.copy-clone-url %} -{% data reusables.command_line.open_the_multi_os_terminal %} -4. Cambia los directorios a la ubicación de la bifurcación que clonaste en el [Paso 2: Crear un clon local de tu bifurcación](#step-2-create-a-local-clone-of-your-fork). - - Para ir a tu directorio de inicio, escribe solo `cd` sin ningún otro texto. - - Para generar una lista de los archivos y carpetas en tu directorio actual, escribe `ls`. - - Para ir a uno de los directorios de la lista, escribe `cd your_listed_directory`. - - Para subir un directorio, escribe `cd ..`. -5. Escribe `git remote -v` y presiona **Intro**. Verás el repositorio remoto configurado actualmente para tu bifurcación. - ```shell - $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) - ``` - -6. Escribe `git remote add upstream` y luego pega la URL que copiaste en el Paso 2 y presiona **Intro**. Se verá así: - ```shell - $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git - ``` - -7. Para verificar el nuevo repositorio ascendente que has especificado para tu bifurcación, escribe nuevamente `git remote -v`. Debes ver la URL para tu bifurcación como `origin` y la URL para el repositorio original como `upstream`. - ```shell - $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) - ``` - -Ahora, puedes mantener tu bifurcación sincronizada con el repositorio ascendente con unos pocos comandos Git. Para obtener más información, consulta "[Sincronizar una bifurcación](/articles/syncing-a-fork)". - -#### Pasos siguientes - -Puedes hacer cualquier cambio a una ramificación, incluyendo: - -- **Crear ramas:** [Las *ramas*](/articles/creating-and-deleting-branches-within-your-repository/) te permiten diseñar nuevas características o probar ideas sin poner en riesgo tu proyecto principal. -- **Abrir solicitudes de extracción:** Si deseas colaborar con el repositorio original, puedes enviar una solicitud al autor original para extraer tu bifurcación en su repositorio enviando una [solicitud de extracción](/articles/about-pull-requests). - -### Encontrar otro repositorio para bifurcar - -Bifurca un repositorio para comenzar a colaborar con un proyecto. {% data reusables.repositories.you-can-fork %} - -{% if currentVersion == "free-pro-team@latest" %}Puedes dirigirte a [Explorar](https://github.com/explore) para encontrar proyectos y comenzar a colaborar con repositorios de código abierto. 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)." - -{% endif %} - -### Celebrar - -Ahora ya has bifurcado un repositorio, has practicado la clonación de tu bifurcación y has configurado un repositorio ascendente. ¿Qué deseas hacer ahora? - -- "[Configurar Git](/articles/set-up-git)" -- "[Crear un repositorio](/articles/create-a-repo)" -- "[Socializar](/articles/be-social)" -- {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-XL/content/github/getting-started-with-github/quickstart/index.md b/translations/es-XL/content/github/getting-started-with-github/quickstart/index.md deleted file mode 100644 index e890974f4f..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/quickstart/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Inicio Rápido -intro: 'Inicia rápidamente las tareas comunes en {% data variables.product.prodname_dotcom %}.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests - - Issues - - Notifications - - Accounts -children: - - /set-up-git - - /create-a-repo - - /fork-a-repo - - /github-flow - - /be-social - - /communicating-on-github - - /github-glossary - - /git-cheatsheet - - /git-and-github-learning-resources ---- - diff --git a/translations/es-XL/content/github/getting-started-with-github/quickstart/set-up-git.md b/translations/es-XL/content/github/getting-started-with-github/quickstart/set-up-git.md deleted file mode 100644 index 0bfa3b33c2..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/quickstart/set-up-git.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Configurar Git -redirect_from: - - /git-installation-redirect/ - - /linux-git-installation/ - - /linux-set-up-git/ - - /mac-git-installation/ - - /mac-set-up-git/ - - /set-up-git-redirect/ - - /win-git-installation/ - - /win-set-up-git/ - - /articles/set-up-git - - /github/getting-started-with-github/set-up-git -intro: 'En el centro de {% data variables.product.product_name %} hay un sistema de control de versión de código abierto (VCS) llamado Git. Git es responsable de todo lo relacionado con {% data variables.product.product_name %} que suceda de forma local en tu computadora.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests - - Issues - - Notifications - - Accounts ---- -Para usar Git en la línea de comando, deberás descargar, instalar y configurar Git en tu computadora. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. For more information on {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) documentation.{% endif %} - -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/)". - -Si no deseas trabajar con archivos de forma local, {% data variables.product.product_name %} te permite realizar muchas acciones relacionadas con Git de forma directa en el navegador, lo que incluye: - -- [Crear un repositorio](/articles/create-a-repo) -- [Bifurcar un repositorio](/articles/fork-a-repo) -- [Administrar archivos](/articles/managing-files-on-github/) -- [Socializar](/articles/be-social) - -### Configurar Git - -1. [Descarga e instala la última versión de Git](https://git-scm.com/downloads). -2. [Configura tu nombre de usuario en Git](/articles/setting-your-username-in-git). -3. [Configura tu dirección de correo electrónico de confirmación en Git](/articles/setting-your-commit-email-address). - -### Pasos siguientes: Autenticación con {% data variables.product.prodname_dotcom %} desde Git - -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. - -#### Conectar por HTTPS (recomendado) - -Si [clonas con HTTPS](/articles/which-remote-url-should-i-use/#cloning-with-https-urls), puedes [almacenar tus credenciales de {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git) utilizando un asistente de credenciales. - -#### Conectar por SSH - -Si clonas [con SSH](/articles/which-remote-url-should-i-use#cloning-with-ssh-urls), debes [generar las claves de SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) en cada computadora que utilices para subir o extraer desde {% data variables.product.product_name %}. - -### Celebrar - -¡Felicitaciones, ahora tienes configurado todo Git y {% data variables.product.product_name %}! ¿Qué deseas hacer ahora? - -- **Configurar Git** -- "[Crear un repositorio](/articles/create-a-repo)" -- "[Bifurcar un repositorio](/articles/fork-a-repo)" -- "[Socializar](/articles/be-social)" -- {% data reusables.support.connect-in-the-forum-bootcamp %} diff --git a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/index.md b/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/index.md deleted file mode 100644 index 731aec6767..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Registrarse en GitHub -intro: '' -redirect_from: - - /articles/signing-up-for-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts -children: - - /signing-up-for-a-new-github-account - - /verifying-your-email-address - - /setting-up-a-trial-of-github-enterprise-cloud - - /setting-up-a-trial-of-github-enterprise-server ---- - diff --git a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md deleted file mode 100644 index bdfd0dc36b..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Configurar una prueba de la nube de GitHub Enterprise -intro: 'Puedes probar {% data variables.product.prodname_ghe_cloud %} de manera gratuita.' -redirect_from: - - /articles/setting-up-a-trial-of-github-enterprise-cloud - - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Accounts ---- -### Acerca de las pruebas de {% data variables.product.prodname_ghe_cloud %} - -Puedes configurar una prueba de 14 días para evaluar {% data variables.product.prodname_ghe_cloud %} en una cuenta nueva de organización. 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. - -También hay pruebas disponibles para {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)". - -{% data reusables.products.which-product-to-use %} - -### Configurar tu prueba de {% data variables.product.prodname_ghe_cloud %} - -Antes de poder comenzar con tu prueba de {% data variables.product.prodname_ghe_cloud %}, debes tener una cuenta de usuario existente o crear una nueva cuenta de usuario. Para obtener más información, consulta "Iniciar sesión para una nueva cuenta de {% data variables.product.prodname_dotcom %}". - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.organizations %} -{% data reusables.organizations.new-organization %} -4. En "Enterprise", haz clic en **Iniciar tu prueba de 14 días**. ![Botón para iniciar tu prueba](/assets/images/help/organizations/start-trial-button.png) -5. Escribe tu nombre de empresa. ![Campo de nombre de empresa](/assets/images/help/organizations/company-name-field.png) -{% data reusables.organizations.organization-name %} -7. En "Nombre completo", escribe tu nombre completo. ![Campo nombre completo](/assets/images/help/organizations/full-name-field.png) -8. En "Correo electrónico laboral", escribe la dirección de correo electrónico que usas para trabajar. ![Campo correo electrónico laboral](/assets/images/help/organizations/work-email-field.png) -8. Usa el menú desplegable **Industria** y selecciona la industria a la que pertenece tu empresa. ![Menú desplegable Industria](/assets/images/help/organizations/industry-drop-down.png) -9. Usa el menú desplegable **Cantidad de empleados** y selecciona la cantidad de empleados de tu empresa. ![Menú desplegable Cantidad de empleados](/assets/images/help/organizations/employees-drop-down.png) -10. Revisa el Acuerdo de licencia de evaluación, luego haz clic en **Next** (Siguiente). - -### Explorar {% data variables.product.prodname_ghe_cloud %} - -Una vez configurada tu prueba de 15 días, puedes explorar {% data variables.product.prodname_ghe_cloud %} siguiendo la [Guía de incorporación de empresas](https://resources.github.com/enterprise-onboarding/). - -{% data reusables.products.product-roadmap %} - -### Finalizar tu prueba - -Puedes comprar {% data variables.product.prodname_enterprise %} o bajar de categoría a {% data variables.product.prodname_team %} en cualquier momento durante tu prueba. - -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á a {% data variables.product.prodname_free_team %} y perderá acceso a cualquier tipo de herramienta o características que solo se incluya en los productos pagados, incluyendo a los sitios de {% data variables.product.prodname_pages %} que se publican desde esos repositorios privados. Si no planeas mejorar tu plan, para evitar perder acceso a estas características avanzadas, haz públicos los repositorios antes de que termine tu periodo de prueba. Para obtener más información, consulta "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)". - -El bajar de categoría a {% data variables.product.prodname_free_team %} en organizaciones también inhabilita cualquier configuración de SAML durante el periodo de prueba. Una vez que compras {% data variables.product.prodname_enterprise %} o {% data variables.product.prodname_team %}, tus parámetros de SAML serán activados nuevamente para que los usuarios de tu organización los autentiquen. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -5. Debajo de "{% data variables.product.prodname_ghe_cloud %} Free Trial" (Prueba gratis de {% data variables.product.prodname_ghe_cloud %}), haz clic en **Buy Enterprise** (Comprar empresa) o **Downgrade to Team** (Bajar de categoría a equipo). ![Botones Comprar Enterprise y Bajar de categoría a Team](/assets/images/help/organizations/finish-trial-buttons.png) -6. Sigue las indicaciones para ingresar tu método de pago, a continuación haz clic en **Enviar**. - -### Leer más - -- "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)" diff --git a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md deleted file mode 100644 index 7682bac6a5..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Configurar una prueba del servidor de GitHub Enterprise -intro: 'Puedes probar {% data variables.product.prodname_ghe_server %} de manera gratuita.' -redirect_from: - - /articles/requesting-a-trial-of-github-enterprise/ - - /articles/setting-up-a-trial-of-github-enterprise-server - - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Accounts ---- -### Acerca de las pruebas de {% data variables.product.prodname_ghe_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)". - -Las alertas de seguridad y {% data variables.product.prodname_github_connect %} actualmente no están disponibles en 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)". - -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)". - -{% data reusables.products.which-product-to-use %} - -### Configurar tu prueba de {% data variables.product.prodname_ghe_server %} - -{% 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. Para obtener más información, consulta "[Administrar tu licencia {% data variables.product.prodname_enterprise %}](/enterprise/admin/installation/managing-your-github-enterprise-license)". - -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)". - -### Pasos siguientes - -Para sacar el mejor provecho de tu prueba, sigue los siguientes pasos: - -1. [Crear una organización](/enterprise/admin/user-management/creating-organizations). -2. Para aprender lo básico para usar {% data variables.product.prodname_dotcom %}, consulta lo siguiente: - - [Guía de iniciación rápida a {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast - - [Comprender el {% data variables.product.prodname_dotcom %} flujo](https://guides.github.com/introduction/flow/) en {% data variables.product.prodname_dotcom %} Guías - - [Hola, mundo](https://guides.github.com/activities/hello-world/) en {% data variables.product.prodname_dotcom %} Guides -3. Para configurar tu instancia a fin de que satisfaga las necesidades de tu organización, consulta "[Configurar el {% data variables.product.prodname_ghe_server %} aparato](/enterprise/admin/installation/configuring-the-github-enterprise-server-appliance)". -4. Para integrar {% data variables.product.prodname_ghe_server %} con tu proveedor de identidad, consulta "[Utilizar SAML](/enterprise/admin/user-management/using-saml)" y "[Utilizar LDAP](/enterprise/admin/authentication/using-ldap)" -5. Invita a una cantidad ilimitada de personas a unirse a tu prueba. - - Agregar usuarios a tu instancia {% data variables.product.prodname_ghe_server %} utilizando la autenticación incorporada o tu proveedor de identidad configurado. Para obtener más información, consulta "[Utilizar la autenticación incorporada](/enterprise/admin/user-management/using-built-in-authentication)". - - Para invitar a personas a que se conviertan en administradores de cuenta, visita el [{% data variables.product.prodname_enterprise %} portal web](https://enterprise.github.com/login). - - {% note %} - - **Nota::** Las personas que invites para que sean administradores de cuenta recibirán un correo electrónico con un enlace para aceptar tu invitación. - - {% endnote %} - -{% data reusables.products.product-roadmap %} - -### Finalizar tu prueba - -Puedes subir la categoría a licencias totales en el [{% data variables.product.prodname_enterprise %} portal web](https://enterprise.github.com/login) en cualquier momento durante el período de prueba. - -Si no has subido la categoría para el último día de tu prueba, recibirás un correo electrónico notificando que tu prueba ha terminado. Si necesitas más tiempo para evaluar {% data variables.product.prodname_enterprise %}, contacta a {% data variables.contact.contact_enterprise_sales %} para solicitar una extensión. - -### Leer más - -- "[Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)" diff --git a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/signing-up-for-a-new-github-account.md b/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/signing-up-for-a-new-github-account.md deleted file mode 100644 index 7e56b05daf..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/signing-up-for-a-new-github-account.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Registrar una nueva cuenta GitHub -intro: '{% data variables.product.product_name %} ofrece cuentas de usuario para personas y organizaciones para equipos de personas que trabajan juntas.' -redirect_from: - - /articles/signing-up-for-a-new-github-account - - /github/getting-started-with-github/signing-up-for-a-new-github-account -versions: - free-pro-team: '*' -topics: - - Accounts ---- -Para obtener más información sobre tipos de cuentas y productos, consulta "[Tipos de cuentas {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" y productos de "[{% data variables.product.product_name %}](/articles/github-s-products)." - -1. Ve a la página de {% data variables.product.product_name %}[Fijación de precios]({% data variables.product.pricing_url %}). -2. Lee la información acerca de los diferentes productos y suscripciones que ofrece {% data variables.product.product_name %}, después haz clic en el botón actualizar debajo de la suscripción que deseas elegir. -3. Sigue las indicaciones para crear tu cuenta personal o de organización. - -### Pasos siguientes - -- [Verifica tus dirección de correo electrónico](/articles/verifying-your-email-address)" -- [Configura autenticación de dos factores](/articles/configuring-two-factor-authentication)" -- [Agrega una biografía a tu perfil](/articles/adding-a-bio-to-your-profile)" -- "[Crea una organización](/articles/creating-a-new-organization-from-scratch)" -- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap` diff --git a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address.md b/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address.md deleted file mode 100644 index 005095ad34..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Verificar tu dirección de correo electrónico -intro: 'Verificar tu dirección principal de correo electrónico garantiza mayor seguridad, permite que el personal {% data variables.product.prodname_dotcom %} te ayude mejor si olvidas tu contraseña y te brinda acceso a más funciones en {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /articles/troubleshooting-email-verification/ - - /articles/setting-up-email-verification/ - - /articles/verifying-your-email-address - - /github/getting-started-with-github/verifying-your-email-address -versions: - free-pro-team: '*' -topics: - - Accounts ---- -### Acerca de la verificación del correo electrónico - -Puedes verificar tu dirección de correo electrónico después de registrarte con una cuenta nueva o cuando agregas una dirección de correo electrónico nueva. Si una dirección de correo electrónico no es válida para el envío o devuelve correos, quedará como no verificada. - -Si no verificas tu dirección de correo electrónico, no podrás hacer lo siguiente: - - Crear o bifurcar repositorios - - Crear propuestas o solicitudes de extracción - - Comentar sobre las propuestas, solicitudes de extracción o confirmaciones - - Autorizar aplicaciones de {% data variables.product.prodname_oauth_app %} - - Generar tokens de acceso personal - - Recibir notificaciones por correo electrónico - - Poner estrellas en repositorios - - Crear o actualizar tableros de proyecto, incluido agregar tarjetas - - Crear o actualizar gists - - Crear o utilizar {% data variables.product.prodname_actions %} - - Patrocinar desarrolladores con {% data variables.product.prodname_sponsors %} - -{% warning %} - -**Warnings**: - -- {% data reusables.user_settings.no-verification-disposable-emails %} -- {% data reusables.user_settings.verify-org-approved-email-domain %} - -{% endwarning %} - -### Verificar tu dirección de correo electrónico - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -1. Debajo de tu dirección de correo electrónico, da clic en **Reenviar correo de verificación**. ![Reenviar enlace de verificación por correo electrónico](/assets/images/help/settings/email-verify-button.png) -4. {% data variables.product.prodname_dotcom %} te enviará un correo electrónico con un enlace. Después de hacer clic en el enlace, se te llevará a tu tablero {% data variables.product.prodname_dotcom %} y verás un mensaje emergente de confirmación. ![Mensaje emergente que confirma que se verificó tu correo electrónico](/assets/images/help/settings/email-verification-confirmation-banner.png) - -### Solución de problemas de verificación de correo electrónico - -#### No se pudo enviar el correo electrónico de verificación - -{% data reusables.user_settings.no-verification-disposable-emails %} - -#### Página de error después de hacer clic en el enlace de verificación - -El enlace de verificación vence después de 24 horas. Si no verificas tu correo electrónico dentro de las 24 horas, puedes solicitar otro enlace de verificación de correo electrónico. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". - -Si haces clic en el enlace del correo electrónico de confirmación dentro de las 24 horas, y te dirige a una página de error, debes asegurarte de haberte registrado en la cuenta {% data variables.product.prodname_dotcom %} correcta. - -1. {% data variables.product.signout_link %} de tu cuenta personal {% data variables.product.prodname_dotcom %}. -2. Sal y vuelve a iniciar tu navegador. -3. {% data variables.product.signin_link %} a tu cuenta personal {% data variables.product.prodname_dotcom %}. -4. Haz clic en el enlace de verificación del correo electrónico que te enviamos. - -### Leer más - -- "[Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address)" diff --git a/translations/es-XL/content/github/getting-started-with-github/using-github/index.md b/translations/es-XL/content/github/getting-started-with-github/using-github/index.md deleted file mode 100644 index 9d030eaaa0..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/using-github/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Utilizar GitHub -intro: '' -redirect_from: - - /articles/using-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -children: - - /exploring-early-access-releases-with-feature-preview - - /supported-browsers - - /github-cli - - /github-desktop - - /github-for-mobile - - /keyboard-shortcuts - - /troubleshooting-connectivity-problems ---- - diff --git a/translations/es-XL/content/github/getting-started-with-github/using-github/keyboard-shortcuts.md b/translations/es-XL/content/github/getting-started-with-github/using-github/keyboard-shortcuts.md deleted file mode 100644 index 7753c1d77e..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/using-github/keyboard-shortcuts.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -title: Atajos del teclado -intro: 'Prácticamente todas las páginas de {% data variables.product.product_name %} tienen atajos del teclado para realizar acciones más rápido.' -redirect_from: - - /articles/using-keyboard-shortcuts/ - - /categories/75/articles/ - - /categories/keyboard-shortcuts/ - - /articles/keyboard-shortcuts - - /github/getting-started-with-github/keyboard-shortcuts -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -### Acerca de los atajos del teclado - -Escribir ? en {% data variables.product.product_name %} genera un cuadro de diálogo que detalla los atajos del teclado disponibles para esa página. Puedes aprovechar estos atajos del teclado para realizar acciones en todo el sitio sin recurrir al mouse para navegar. - -A continuación aparece una lista de algunos de los atajos del teclado disponibles. - -### Atajos en todo el sitio - -| 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)". | -| g n | Dirige a tus notificaciones. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[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 | - -### Repositorios - -| Atajo del teclado | Descripción | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| g c | Dirige a la pestaña **Code** (Código) | -| g i | Dirige a la pestaña **Issues** (Propuestas). Para obtener más información, consulta "[Acerca de las propuestas](/articles/about-issues)". | -| g p | Dirige a la pestaña **Pull requests** (Solicitudes de extracción). Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." | -| g a | Ve a la pestaña de **Acciones**. Para obtener más información, consulta la sección "[Acerca de las Acciones](/actions/getting-started-with-github-actions/about-github-actions)". | -| g b | Dirige a la pestaña **Projects** (Proyectos). Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards)." | -| g w | Dirige a la pestaña **Wiki**. Para obtener más información, consulta "[Acerca de las wikis](/articles/about-wikis)". | - -### Edición del código fuente - -| Atajo del teclado | Descripción | -| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | -| 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) | - -Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror](https://codemirror.net/doc/manual.html#commands). - -### Exploración del código fuente - -| Atajo del teclado | Descripción | -| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| t | Activa el buscador de archivos | -| l | Salta a una línea de tu código | -| w | Cambia a una rama o etiqueta nueva | -| y | Expande una URL a su forma canónica. Para obtener más información, consulta "[Obtener enlaces permanentes a los archivos](/articles/getting-permanent-links-to-files)". | -| i | Muestra u oculta comentarios en diferencias. Para obtener más información, consulta "[Comentar en la diferencia de una solicitud de extracción](/articles/commenting-on-the-diff-of-a-pull-request)". | -| b | Abre la visualización del último responsable. Para obtener más información, consulta "[Rastrear las modificaciones de un archivo](/articles/tracing-changes-in-a-file)". | - -### Comentarios - -| Atajo del teclado | Descripción | -| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 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 | -| control shift p o comando shift p | Alterna entre las pestañas de comentarios **Write** (Escribir) y **Preview** (Vista previa) | -| 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)."{% if currentVersion == "free-pro-team@latest" %} -| 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. Para obtener más información, consulta "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-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 | -| ------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| q | Solicita un revisor. Para obtener más información, consulta "[Solicitar una revisión de solicitud de extracción](/articles/requesting-a-pull-request-review/)". | -| m | Establece un hito. Para obtener más información, consulta "[Asociar hitos a propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests/)". | -| l | Aplica una etiqueta. Para obtener más información, consulta "[Aplicar etiquetas a propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests/)". | -| a | Establece un asignatario. Para obtener más información, consulta "[Asignar propuestas y solicitudes de extracción a otros{% data variables.product.company_short %} usuarios](/articles/assigning-issues-and-pull-requests-to-other-github-users/)". | -| cmd + shift + p or control + shift + p | Alterna entre las pestañas **Write** (Escribir) y **Preview** (Vista previa) | - -### Modificaciones en las solicitudes de extracción - -| Atajo del teclado | Descripción | -| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | Abre la lista de confirmaciones de la solicitud de extracción | -| t | Abre la lista de archivos modificados de la solicitud de extracción | -| j | Mueve la selección hacia abajo en la lista | -| k | Mueve la selección hacia arriba en la lista | -| cmd + shift + enter | Agrega un comentario simple en una diferencia de solicitud de extracción | -| alt y haz clic | Alterna entre colapsar y expandir todos los comentarios de revisión desactualizados en una solicitud de extracción sosteniendo `alt` y dando clic en **Mostrar desactualizados** u **Ocultar desactualizados**.|{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -| Da clic, luego shift y clic | Comenta en líneas múltiples de una solicitud de extracción dando clic en un número de línea, sosteniendo shift, y luego dando clic en otro número de línea. Para obtener más información, consulta "[Comentar en una solicitud de extracción](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} - -### Tableros de proyecto - -#### Mover una columna - -| Atajo del teclado | Descripción | -| ----------------------------------------------------------------------------------------- | ----------------------------------------------------- | -| enter o space | Comienza a mover la columna enfocada | -| escape | Cancela el movimiento en curso | -| enter | Completa el movimiento en curso | -| ← o h | Mueve la columna hacia la izquierda | -| comando ← o comando h o control ← o control h | Mueve la columna hacia la posición más a la izquierda | -| → o l | Mueve la columna hacia la derecha | -| comando → o comando l o control → o control l | Mueve la columna hacia la posición más a la derecha | - -#### Mover una tarjeta - -| Atajo del teclado | Descripción | -| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | -| enter o space | Comienza a mover la tarjeta focalizada | -| escape | Cancela el movimiento en curso | -| enter | Completa el movimiento en curso | -| ↓ o j | Mueve la tarjeta hacia abajo | -| comando ↓ o comando j o control ↓ o control j | Mueve una tarjeta hacia la parte de abajo de la columna | -| ↑ o k | Mueve una tarjeta hacia arriba | -| comando ↑ o comando k or control ↑ o control k | Mueve una tarjeta hacia la parte de arriba de la columna | -| ← o h | Mueve una tarjeta hacia la parte de abajo de la columna de la izquierda | -| shift ← o shift h | Mueve una tarjeta hacia la parte de arriba de la columna de la izquierda | -| comando ← o comando h o control ← o control h | Mueve una tarjeta hacia la parte de abajo de la columna de más a la izquierda | -| comando shift ← o comando shift h o control shift ← o control shift h | Mueve una tarjeta hacia la parte de arriba de la columna de más a la izquierda | -| → | Mueve una tarjeta hacia la parte de abajo de la columna de la derecha | -| shift → o shift l | Mueve una tarjeta hacia la parte de arriba de la columna de la derecha | -| comando → o comando l o control → o control l | Mueve una tarjeta hacia la parte de abajo de la columna de más a la derecha | -| comando shift → o comando shift l o control shift → o control shift l | Mueve una tarjeta hacia la parte de abajo de la columna de más a la derecha | - -#### Previewing a card - -| Atajo del teclado | Descripción | -| ----------------- | --------------------------- | -| esc | Close the card preview pane | - -{% if currentVersion == "free-pro-team@latest" %} -### {% data variables.product.prodname_actions %} - -| Atajo del teclado | Descripción | -| ---------------------------------------------------- | --------------------------------------------------------------------------------------------- | -| command space o control space | En el editor del flujo de trabajo, obtén las sugerencias para tu archivo de flujo de trabajo. | - -{% endif %} - -### Notificaciones -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -| Atajo del teclado | Descripción | -| ------------------ | -------------------- | -| e | Marcar como hecho | -| shift u | Marcar como no léido | -| shift i | Marca como leído | -| shift m | Darse de baja | - -{% else %} - -| Atajo del teclado | Descripción | -| ------------------------------------------ | ---------------- | -| e o I o y | Marca como leído | -| shift m | Silencia el hilo | -{% endif %} - -### Gráfico de conexiones - -| Atajo del teclado | Descripción | -| --------------------------------------- | -------------------------------- | -| ← o h | Desplaza hacia la izquierda | -| → o l | Desplaza hacia la derecha | -| ↑ o k | Desplaza hacia arriba | -| ↓ o j | Desplaza hacia abajo | -| shift ← o shift h | Desplaza todo hacia la izquierda | -| shift → o shift l | Desplaza todo hacia la derecha | -| shift ↑ o shift k | Desplaza todo hacia arriba | -| shift ↓ o shift j | Desplaza todo hacia abajo | diff --git a/translations/es-XL/content/github/getting-started-with-github/using-github/supported-browsers.md b/translations/es-XL/content/github/getting-started-with-github/using-github/supported-browsers.md deleted file mode 100644 index dcf7e0434d..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/using-github/supported-browsers.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Navegadores compatibles -redirect_from: - - /articles/why-doesn-t-graphs-work-with-ie-8/ - - /articles/why-don-t-graphs-work-with-ie8/ - - /articles/supported-browsers - - /github/getting-started-with-github/supported-browsers -intro: 'Diseñamos {% data variables.product.product_name %} para admitir las últimas versiones de los navegadores web. Admitimos las versiones actuales de [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), {% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.16" %}Internet Explorer 11, {% endif %}y [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -### Lanzamiento de soporte extendido de Firefox - -Nos esforzamos para admitir el más reciente [Lanzamiento de soporte extendido](https://www.mozilla.org/en-US/firefox/organizations/) (ESR) de Firefox. Las versiones anteriores de Firefox pueden inhabilitar algunas funciones en {% data variables.product.product_name %} y necesitan la última versión de Firefox. - -### Construcciones de programador y beta - -Puedes encontrar errores inesperados en beta y en construcciones de programador de nuestros navegadores compatibles. Si encuentras un error en {% data variables.product.product_name %} en uno de estas construcciones no lanzadas, verifica que también exista en la versión estable del mismo navegador. Si el error solo existe en la versión inestable, considera informar el error al programador del navegador. diff --git a/translations/es-XL/content/github/getting-started-with-github/using-github/troubleshooting-connectivity-problems.md b/translations/es-XL/content/github/getting-started-with-github/using-github/troubleshooting-connectivity-problems.md deleted file mode 100644 index 05f8d41f60..0000000000 --- a/translations/es-XL/content/github/getting-started-with-github/using-github/troubleshooting-connectivity-problems.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Solucionar problemas de conectividad -intro: 'Si tienes problemas para conectarte a {% data variables.product.prodname_dotcom %}, puedes solucionar los problemas de conexión. Utiliza la herramienta {% data variables.product.prodname_debug %} para diagnosticar problemas.' -redirect_from: - - /articles/troubleshooting-connectivity-problems - - /github/getting-started-with-github/troubleshooting-connectivity-problems -versions: - free-pro-team: '*' ---- -La mayoría de las veces, los problemas de conexión ocurren porque un firewall, servidor proxy, red corporativa u otra red está configurada de una forma que bloquea {% data variables.product.prodname_dotcom %}. - -### Permitir las direcciones IP de {% data variables.product.prodname_dotcom %} - -Asegúrate de que tu red esté configurada para permitir las direcciones IP de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Acerca de las direcciones IP de {% data variables.product.prodname_dotcom %}](/articles/about-github-s-ip-addresses)". - -### Utilizar la red de una empresa u organización - -Si tienes problemas de conectividad con la red de tu empresa u organización, consulta con tu administrador de red para saber si se le aplican reglas a la red para bloquear determinados tráficos. Si ya existen reglas configuradas, consulta con tu administrador de red para permitir el tráfico hacia {% data variables.product.prodname_dotcom %}. - -### Solucionar problemas de captcha - -Si no puedes verificar con el captcha: -- Asegúrate de que javascript esté habilitado en tu navegador. -- Asegúrate de que tu navegador sea compatible. Si tu navegador no es compatible, actualízalo o instala un navegador compatible. Para obtener una lista de navegadores compatibles, consulta "[Navegadores compatibles](/articles/supported-browsers)". -- Asegúrate de que tu configuración de red no esté bloqueando https://octocaptcha.com/ o https://arkoselabs.com/. Si estás detrás de un cortafuegos corporativo, contacta a tu administrador de TI para que incluya esos dominios. Para verificar el acceso a estos dominios, visita https://octocaptcha.com/test y asegúrate de que se muestre el texto "¡La conexión se llevó a cabo exitosamente!", luego visita https://client-demo.arkoselabs.com/github y asegúrate de que puedes cargar el captcha. -- Asegúrate de que tu navegador no tenga plug-ins o extensiones que puedan estar interfiriendo con GitHub. En tal caso, inhabilita de manera temporal los plug-ins o extensiones durante la verificación del 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. Para obtener más información, consulta "[Clonar un repositorio desde {% data variables.product.prodname_dotcom %}](/articles/cloning-a-repository-from-github)". - -Si están ocurriendo interrupciones con SSH, consulta "[Error: Número de archivo erróneo](/articles/error-bad-file-number)". - -### Solucionar problemas de descargas lentas y conexiones lentas intermitentes - -{% data variables.product.prodname_dotcom %} no alterna el ancho de banda por usuario. - -Si tienes conexiones lentas en determinados momentos del día, pero no en otros, las velocidades lentas normalmente se deben a la congestión de red. Ya que {% data variables.product.prodname_dotcom %} no puede resolver congestiones de red, debes escalar el problema a tu proveedor de servicio de internet. - -### Solucionar problemas con {% data variables.product.prodname_debug %} - -Si has seguido todas las sugerencias para solucionar problemas antes detalladas y sigues teniendo problemas de conexión, puedes seguir las indicaciones del sitio {% data variables.product.prodname_debug %} para ejecutar pruebas y enviar un informe a {% data variables.product.prodname_dotcom %} Support (Asistencia). Para obtener más información, consulta [{% data variables.product.prodname_debug %}](https://github-debug.com/). diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer.md b/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer.md deleted file mode 100644 index 9ce529e383..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Acerca de Importador GitHub -intro: 'Si tienes un código fuente en Subversion, Mercurial, Team Foundation Server u otro repositorio de Git, puedes moverlo a GitHub usando el Importador GitHub.' -redirect_from: - - /articles/about-github-importer - - /github/importing-your-projects-to-github/about-github-importer -versions: - fpt: '*' ---- -Importador GitHub es una herramienta que importa de forma rápida repositorios de código fuente, incluido el historial de revisiones y confirmaciones de cambios, a GitHub para tí. - -![Importar un gif de repositorio](/assets/images/help/importer/github-importer.gif) - -Durante una importación, dependiendo del sistema de control de la versión del que estás importando, puedes autenticar con tu repositorio remoto, actualizar la atribución del autor de la confirmación e importar repositorios con archivos grandes (o eliminar archivos grandes si no quieres usar Large File Storage de Git). - -| Acción de importación | Subversion | Mercurial | Team Foundation Server | Git | -|:-------------------------------------------------------------------------------------------------------------------------- |:----------:|:---------:|:----------------------:|:-----:| -| Autenticar con repositorio remoto | **X** | **X** | **X** | **X** | -| [Actualizar la atribución del autor de la confirmación](/articles/updating-commit-author-attribution-with-github-importer) | **X** | **X** | **X** | | -| Mover archivos grandes a [Large File Storage de Git](/articles/about-git-large-file-storage) | **X** | **X** | **X** | | -| Eliminar archivos grandes de tu repositorio | **X** | **X** | **X** | | - -### Leer más - -- "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" -- "[Actualizar la atribución del autor de la confirmación con Importador GitHub ](/articles/updating-commit-author-attribution-with-github-importer)" -- "[Importar un repositorio de Git usando la línea de comando](/articles/importing-a-git-repository-using-the-command-line)" -- "[Herramientas de migración de código fuente](/articles/source-code-migration-tools)" diff --git a/translations/es-XL/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-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md deleted file mode 100644 index cfc476b9c0..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Agregar un proyecto existente a GitHub utilizando la línea de comando -intro: 'Poner tu trabajo existente en {% data variables.product.product_name %} puede permitirte compartir y colaborar de muchas maneras increíbles.' -redirect_from: - - /articles/add-an-existing-project-to-github/ - - /articles/adding-an-existing-project-to-github-using-the-command-line - - /github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -{% data reusables.repositories.migrating-from-codeplex %} - -{% tip %} - -**Sugerencia:** Si estás más a gusto con una interfaz de usuario de tipo "apuntar y hacer clic", trata de agregar tu proyecto con {% data variables.product.prodname_desktop %}. Para más información, consulta "[Agregar un repositorio de tu computadora local a GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" en *{% data variables.product.prodname_desktop %} Ayuda*. - -{% endtip %} - -{% data reusables.repositories.sensitive-info-warning %} - -{% mac %} - -1. [Crear un repositorio nuevo](/articles/creating-a-new-repository) en {% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png) -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Cambiar el directorio de trabajo actual en tu proyecto local. -4. Inicializar el directorio local como un repositorio de Git. - ```shell - $ git init - ``` -5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación. - ```shell - $ git add . - # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %} - ``` -6. Confirmar los archivos que has preparado en tu repositorio local. - ```shell - $ git commit -m "First commit" - # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} - ``` -7. En la parte superior de la página de Configuración rápida del repositorio de {% 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) -8. En Terminal, [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. - ```shell - $ git remote add origin remote repository URL - # Sets the new remote - $ git remote -v - # Verifies the new remote URL - ``` -9. [Sube los cambios](/articles/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}. - ```shell - $ git push -u origin master - # Pushes the changes in your local repository up to the remote repository you specified as the origin - ``` - -{% endmac %} - -{% windows %} - -1. [Crear un repositorio nuevo](/articles/creating-a-new-repository) en {% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png) -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Cambiar el directorio de trabajo actual en tu proyecto local. -4. Inicializar el directorio local como un repositorio de Git. - ```shell - $ git init - ``` -5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación. - ```shell - $ git add . - # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %} - ``` -6. Confirmar los archivos que has preparado en tu repositorio local. - ```shell - $ git commit -m "First commit" - # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} - ``` -7. En la parte superior de la página de Configuración rápida del repositorio de {% 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) -8. En la indicación Command (Comando), [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. - ```shell - $ git remote add origin remote repository URL - # Sets the new remote - $ git remote -v - # Verifies the new remote URL - ``` -9. [Sube los cambios](/articles/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}. - ```shell - $ git push origin master - # Pushes the changes in your local repository up to the remote repository you specified as the origin - ``` - -{% endwindows %} - -{% linux %} - -1. [Crear un repositorio nuevo](/articles/creating-a-new-repository) en {% data variables.product.product_location %}. Para evitar errores, no inicialices el nuevo repositorio con archivos *README* licencia o `gitingnore`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. ![Desplegable Create New Repository (Crear nuevo repositorio)](/assets/images/help/repository/repo-create.png) -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Cambiar el directorio de trabajo actual en tu proyecto local. -4. Inicializar el directorio local como un repositorio de Git. - ```shell - $ git init - ``` -5. Agregar los archivos a tu nuevo repositorio local. Esto representa la primera confirmación. - ```shell - $ git add . - # Agrega el archivo en el repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %} - ``` -6. Confirmar los archivos que has preparado en tu repositorio local. - ```shell - $ git commit -m "First commit" - # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} - ``` -7. En la parte superior de la página de Configuración rápida del repositorio de {% 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) -8. En Terminal, [agrega la URL para el repositorio remoto](/articles/adding-a-remote) donde se subirá tu repositorio local. - ```shell - $ git remote add origin remote repository URL - # Sets the new remote - $ git remote -v - # Verifies the new remote URL - ``` -9. [Sube los cambios](/articles/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}. - ```shell - $ git push origin master - # Pushes the changes in your local repository up to the remote repository you specified as the origin - ``` - -{% endlinux %} - -### Leer más - -- [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md b/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md deleted file mode 100644 index 440e6bb38c..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Importar un repositorio de Git usando la línea de comando -intro: '{% if currentVersion == "free-pro-team@latest" %}Si [Importador GitHub](/articles/importing-a-repository-with-github-importer) no es adecuado para tus propósitos, como cuando tu código existente está alojado en una red privada, recomendamos importar usando la línea de comando.{% else %}Importar proyectos de Git usando la línea de comando es adecuado cuando tu código existente está alojado en una red privada.{% endif %}' -redirect_from: - - /articles/importing-a-git-repository-using-the-command-line - - /github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -Antes de comenzar, asegúrate de saber lo siguiente: - -- Tu nombre de usuario {% data variables.product.product_name %} -- La URL del clon del repositorio externo, como `https://external-host.com/user/repo.git` o `git://external-host.com/user/repo.git` (quizás con un `user@` adelante del nombre de dominio `external-host.com`) - -{% tip %} - -A los fines de demostración, usaremos lo siguiente: - -- Una cuenta externa llamada **extuser** -- Un host de Git externo llamado `https://external-host.com` -- Una cuenta de usuario personal {% data variables.product.product_name %} llamada **ghuser** -- Un repositorio {% data variables.product.product_name %} llamado **repo.git** - -{% endtip %} - -1. [Crear un repositorio nuevo en {% data variables.product.product_name %}](/articles/creating-a-new-repository). Importarás tu repositorio de Git externo a este repositorio nuevo. -2. En la línea de comando, haz un clon "en blanco" del repositorio usando la URL del clon externo. Esto crea una copia completa de los datos, pero sin un directorio de trabajo para editar archivos, y asegura una exportación limpia y nueva de todos los datos antiguos. - ```shell - $ git clone --bare https://external-host.com/extuser/repo.git - # Makes a bare clone of the external repository in a local directory - ``` -3. Sube el repositorio clonado de forma local a {% data variables.product.product_name %} usando la opción "espejo", que asegura que todas las referencias, como ramas y etiquetas, se copien en el repositorio importado. - ```shell - $ cd repo.git - $ git push --mirror https://{% data variables.command_line.codeblock %}/ghuser/repo.git - # Pushes the mirror to the new {% data variables.product.product_name %} repository - ``` -4. Elimina el repositorio local temporal. - ```shell - $ cd .. - $ rm -rf repo.git - ``` diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md b/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md deleted file mode 100644 index 29654cb9ff..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Importar un repositorio con el Importador GitHub -intro: 'Si tienes un proyecto alojado en otro sistema de control de versión, puedes importarlo automáticamente a GitHub usando la herramienta Importador GitHub.' -redirect_from: - - /articles/importing-from-other-version-control-systems-to-github/ - - /articles/importing-a-repository-with-github-importer - - /github/importing-your-projects-to-github/importing-a-repository-with-github-importer -versions: - fpt: '*' ---- -{% tip %} - -**Sugerencia:** El Importador GitHub no útil para todas las importaciones. Por ejemplo, si tu código existente está alojado en una red privada, nuestra herramienta no podrá acceder a él. En estos casos, recomendamos [importar usando la línea de comando](/articles/importing-a-git-repository-using-the-command-line) para los repositorios de Git o una [herramienta de migración de código fuente](/articles/source-code-migration-tools) externa para los proyectos importados desde otros sistemas de control de versión. - -{% endtip %} - -Si quieres hacer coincidir las confirmaciones de tu repositorio con las cuentas de usuario de GitHub de los autores durante la importación, asegúrate de que cada contribuyente de tu repositorio tenga una cuenta de GitHub antes de comenzar la importación. - -{% data reusables.repositories.migrating-from-codeplex %} - -{% data reusables.repositories.repo-size-limit %} - -1. En la esquina superior derecha de cada página, haz clic en {% octicon "plus" aria-label="Plus symbol" %} y luego haz clic en **Import repository** (Importar repositorio). ![Opción de Importar repositorio en el menú del nuevo repositorio](/assets/images/help/importer/import-repository.png) -2. En "La URL del clon de tu repositorio antiguo", escribe la URL del proyecto que quieres importar. ![Campo de texto para la URL del repositorio importado](/assets/images/help/importer/import-url.png) -3. Elige tu cuenta de usuario o una organización como propietaria del repositorio, luego escribe un nombre para el repositorio en GitHub. ![Menú del propietario del repositorio y campo del nombre del repositorio](/assets/images/help/importer/import-repo-owner-name.png) -4. Especifica si el repositorio nuevo debe ser *público* o *privado*. Para obtener más información, consulta "[Configurar la visibilidad de un repositorio](/articles/setting-repository-visibility)". ![Botones Radio para el repositorio público o privado](/assets/images/help/importer/import-public-or-private.png) -5. Revisa la información que ingresaste, luego haz clic en **Begin import** (Comenzar importación). ![Botón Begin import (Comenzar importación)](/assets/images/help/importer/begin-import-button.png) -6. Si tus proyectos antiguos estaban protegidos con contraseña, escribe tu información de inicio de sesión para ese proyecto, luego haz clic en **Submit** (Enviar). ![Formulario de contraseña y botón Submit (Enviar) para proyecto protegido con contraseña](/assets/images/help/importer/submit-old-credentials-importer.png) -7. Si hay múltiples proyectos alojados en la URL del clon de tu proyecto antiguo, elige el proyecto que quieras importar, luego haz clic en **Submit** (Enviar). ![Lista de proyectos para importar y botón Submit (Enviar)](/assets/images/help/importer/choose-project-importer.png) -8. Si tu proyecto contiene archivos mayores a 100 MB, elige si importarás los archivos grandes usando [Git Large File Storage](/articles/versioning-large-files), luego haz clic en **Continue** (Continuar). ![Menú de Git Large File Storage y botón Continue (Continuar)](/assets/images/help/importer/select-gitlfs-importer.png) - -Recibirás un correo electrónico cuando se haya importado todo el repositorio. - -### Leer más - -- "[Actualizar la atribución del autor de la confirmación con Importador GitHub ](/articles/updating-commit-author-attribution-with-github-importer)" diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md b/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md deleted file mode 100644 index 759f6be302..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Importar código fuente a GitHub -intro: 'Puedes importar repositorios a GitHub usando el {% if currentVersion == "free-pro-team@latest" %}Importador GitHub, la línea de comando,{% else %}la línea de comando{% endif %} o herramientas de migración externas.' -redirect_from: - - /articles/importing-an-external-git-repository/ - - /articles/importing-from-bitbucket/ - - /articles/importing-an-external-git-repo/ - - /articles/importing-your-project-to-github/ - - /articles/importing-source-code-to-github -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /about-github-importer - - /importing-a-repository-with-github-importer - - /updating-commit-author-attribution-with-github-importer - - /importing-a-git-repository-using-the-command-line - - /adding-an-existing-project-to-github-using-the-command-line - - /source-code-migration-tools ---- - diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md deleted file mode 100644 index 73581351ff..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Herramientas de migración de código fuente -intro: Puedes utilizar herramientas externas para mover tus proyectos a GitHub. -redirect_from: - - /articles/importing-from-subversion/ - - /articles/source-code-migration-tools - - /github/importing-your-projects-to-github/source-code-migration-tools -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -{% if currentVersion == "free-pro-team@latest" %} - -Recomendamos utilizar [GitHub Importer](/articles/about-github-importer) para importar proyectos desde Subversion, Mercurial, Team Foundation Server u otro repositorio de Git. También puedes utilizar estas herramientas externas para convertir tus proyectos a Git. - -{% endif %} - -### Importar desde Subversion - -En un entorno normal de Subversion, se almacenan varios proyectos en un único repositorio raíz. En GitHub, cada uno de estos proyectos generalmente se mapeará a un repositorio de Git separado para una cuenta de usuario o de organización. Sugerimos importar cada parte de tu repositorio de Subversion a un repositorio de GitHub separado si: - -* Los colaboradores necesitan revisar o confirmar esa parte del proyecto de forma separada desde las otras partes -* Deseas que distintas partes tengan sus propios permisos de acceso - -Recomendamos estas herramientas para convertir repositorio de Subversion a Git: - -- [`git-svn`](https://git-scm.com/docs/git-svn) -- [svn2git](https://github.com/nirvdrum/svn2git) - -### Importar desde Mercurial - -Recomendamos [hg-fast-export](https://github.com/frej/fast-export) para convertir repositorios de Mercurial a Git. - -### Importar desde Team Foundation Server - -Recomendamos estas herramientas para mover cambios entre Team Foundation Server y Git: - -- [git-tfs](https://github.com/git-tfs/git-tfs) -- [Git-TF](https://gittf.codeplex.com/) - -{% tip %} - -**Sugerencia:** después de haber convertido con éxito tu proyecto a Git, puedes [subirlo a {% data variables.product.prodname_dotcom %}](/articles/pushing-commits-to-a-remote-repository/). - -{% endtip %} - -{% if currentVersion == "free-pro-team@latest" %} - -### Leer más - -- "[Acerca del Importador GitHub](/articles/about-github-importer)" -- "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" -- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) - -{% endif %} diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer.md b/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer.md deleted file mode 100644 index 33953917bd..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Actualizar la atribución del autor de la confirmación con Importador GitHub -intro: 'Durante una importación, puedes hacer coincidir las confirmaciones de tu repositorio con la cuenta de GitHub del autor de la confirmación.' -redirect_from: - - /articles/updating-commit-author-attribution-with-github-importer - - /github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer -versions: - fpt: '*' ---- -El Importador GitHub busca los usuarios de GitHub cuyas direcciones de correo electrónico coincidan con los autores de las confirmaciones del repositorio que estás importando. Luego puedes conectar una confirmación con su autor utilizando su dirección de correo electrónico o el nombre de usuario de GitHub del autor. - -### Actualizar autores de la confirmación - -1. Después de que hayas importado tu repositorio, en la página de estado de importación, haz clic en **Match authors** (Hacer coincidir autores). ![Botón Match authors (Hacer coincidir autores)](/assets/images/help/importer/match-authors-button.png) -2. Al lado del autor cuya información quieres actualizar, haz clic en **Connect** (Conectar). ![Lista de autores de la confirmación](/assets/images/help/importer/connect-commit-author.png) -3. Escribe la dirección de correo electrónico o el nombre de usuario de GitHub del autor, luego presiona **Enter**. - -### Atribuir confirmaciones a un usuario de GitHub con una dirección de correo electrónico pública - -Si el autor de una confirmación en tu repositorio importado tiene una cuenta de GitHub asociada con la dirección de correo electrónico que utilizó para figurar como autor de la confirmación y no estableció [su dirección de correo electrónico de confirmaciones como privada](/articles/setting-your-commit-email-address), el Importador GitHub hará coincidir la dirección de correo electrónico asociada a la confirmación con la dirección de correo electrónico pública asociada a su cuenta de GitHub, y atribuirá la confirmación a su cuenta de GitHub. - -### Atribuir confirmaciones a un usuario de GitHub sin una dirección de correo electrónico pública - -Si el autor de una confirmación en tu repositorio importado no estableció una dirección de correo electrónico pública en su perfil de GitHub ni [estableció su dirección de correo electrónico de confirmaciones como privada](/articles/setting-your-commit-email-address), el Importador GitHub no podrá hacer coincidir la dirección de correo electrónico asociada a la confirmación con su cuenta de GitHub. - -El autor de la confirmación puede resolver esto estableciendo su dirección de correo electrónico como privada. Sus confirmaciones luego se le atribuirán a `@users.noreply.github.com`, y las confirmaciones importadas se asociarán a su cuenta de GitHub. - -### Atribuir confirmaciones utilizando una dirección de correo electrónico - -Si la dirección de correo electrónico del autor no está asociada a su cuenta de GitHub, puede [agregar la dirección a su cuenta](/articles/adding-an-email-address-to-your-github-account) después de la importación, y las confirmaciones se atribuirán de manera correcta. - -Si el autor no tiene una cuenta de GitHub, el Importador GitHub atribuirá sus confirmaciones a la dirección de correo electrónico asociada a las confirmaciones. - -### Leer más - -- "[Acerca del Importador GitHub](/articles/about-github-importer)" -- "[Importar un repositorio con Importador GitHub](/articles/importing-a-repository-with-github-importer)" -- "[Agregar una dirección de correo electrónico a tu cuenta](/articles/adding-an-email-address-to-your-github-account/)" -- "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address)" diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/index.md b/translations/es-XL/content/github/importing-your-projects-to-github/index.md deleted file mode 100644 index 16a0573e3c..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Importar tus proyectos a GitHub -shortTitle: Importar tus proyectos -redirect_from: - - /categories/67/articles/ - - /categories/importing/ - - /categories/importing-your-projects-to-github -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /importing-source-code-to-github - - /working-with-subversion-on-github ---- -### Índice - - diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/index.md b/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/index.md deleted file mode 100644 index 55341c331c..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Trabajar con Subversion en GitHub -intro: Puedes usar clientes de Subversion y algunos flujos de trabajo y propiedades de Subversion con GitHub. -redirect_from: - - /articles/working-with-subversion-on-github -versions: - fpt: '*' - ghes: '*' -children: - - /what-are-the-differences-between-subversion-and-git - - /support-for-subversion-clients - - /subversion-properties-supported-by-github ---- - diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md b/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md deleted file mode 100644 index 548eda397e..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Propiedades de Subversion admitidas por GitHub -intro: 'Existen varios flujos de trabajo y propiedades de Subversion que son similares a la funcionalidad existente en {% data variables.product.product_name %}.' -redirect_from: - - /articles/subversion-properties-supported-by-github - - /github/importing-your-projects-to-github/subversion-properties-supported-by-github -versions: - fpt: '*' - ghes: '*' ---- -### Archivos ejecutables (svn:executable) - -Convertimos propiedades `svn:executable` al actualizar el modo archivo directamente antes de agregarlo al repositorio de Git. - -### Tipos MIME (svn:mime-type) - -{% data variables.product.product_name %} internalmente rastrea las propiedades mime-type de los archivos y las confirmaciones que los agregaron. - -### Ignorar elementos sin versión (svn:ignore) - -Si has configurado que los archivos y los directorios se ignoren en Subversion, {% data variables.product.product_name %} los rastrearemos de manera interna. Los archivos ignorados por los clientes de Subversion son completamente distintos a las entradas en un archivo *.gitignore*. - -### Propiedades admitidas actualmente - -{% data variables.product.product_name %} no admite actualmente `svn:externals`, `svn:global-ignores`, o culaquier propiedad no enumerada anteriormente, incluidas las propiedades personalizadas. diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md b/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md deleted file mode 100644 index a3f5f99a0f..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Soporte para clientes de Subversion -intro: Los repositorios de GitHub pueden accederse desde los clientes de Git y de Subversion (SVN). En este artículo se aborda el uso de un cliente de Subversion en GitHub y algunos problemas comunes que puedes llegar a encontrar. -redirect_from: - - /articles/support-for-subversion-clients - - /github/importing-your-projects-to-github/support-for-subversion-clients -versions: - fpt: '*' - ghes: '*' ---- -GitHub admite clientes de Subversion por medio del protocolo HTTPS. Utilizamos el puente de Subversion para comunicar los comandos svn a GitHub. - -### Funciones de Subversion admitidas en GitHub - -#### Control - -La primera cosa que desearás realizar es un control de Subversion. Ya que los clones de Git mantienen un directorio de trabajo (donde editas los archivos) separado de los datos del repositorio, solo hay una rama en el directorio de trabajo a la vez. - -Los controles de Subversion son diferentes: combinan los datos del repositorio en los directorios de trabajo, por lo que hay un directorio de trabajo para cada rama y etiqueta que has revisado. Para los repositorios con muchas ramas y etiquetas, revisar cada cosa puede ser una sobrecarga del ancho de banda, por lo que deberías comenzar con un control parcial. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.copy-clone-url %} - -3. Realiza un control vacío del repositorio: - ```shell - $ svn co --depth empty https://github.com/user/repo - > Checked out revision 1. - $ cd repo - ``` - -4. Llega hasta la rama `trunk` (tronco). El puente de Subversion mapea a trunk en la rama HEAD de Git. - ```shell - $ svn up trunk - > A trunk - > A trunk/README.md - > A trunk/gizmo.rb - > Updated to revision 1. - ``` - -5. Consigue un control vacío del directorio de `branches` (ramas). Aquí es donde están todas las ramas non-`HEAD` (no encabezado), y donde harás las ramas de características. - ```shell - $ svn up --depth empty branches - Updated to revision 1. - ``` - -#### Crear ramas - -También puedes crear ramas usando el puente de Subversion a GitHub. - -Desde tu cliente svn, asegúrate de que la rama "principal" esté vigente actualizando la rama `trunk` (tronco): -```shell -$ svn up trunk -> At revision 1. -``` - -A continuación, puedes utilizar `svn copy` para crear una nueva rama: -```shell -$ svn copy trunk branches/more_awesome -> A branches/more_awesome -$ svn commit -m 'Added more_awesome topic branch' -> Adding branches/more_awesome - -> Revisión confirmada 2. -``` - -Puedes confirmar que la nueva rama existe en el menú desplegable de la rama del repositorio: - -![branch-snapshot](/assets/images/help/branch/svnflow-branch-snapshot.png) - -También puedes confirmar la nueva rama por medio de la línea de comando: - -```shell -$ git fetch -> From https://github.com/user/repo/ -> * [new branch] more_awesome -> origin/more_awesome -``` - -#### Realizar confirmaciones de cambios en Subversion - -Después de haber agregado algunas características y haber arreglado algunos errores, desearás confirmar estos cambios en GitHub. Esto funciona de la misma forma en la que estás acostumbrado en Subversion. Edita tus archivos y utiliza `svn commit` para registrar tus cambios: - -```shell -$ svn status -> M gizmo.rb -$ svn commit -m 'Guard against known problems' -> Sending more_awesome/gizmo.rb -> Transmitiendo los datos del archivo. -> Revisión confirmada 3. -$ svn status -> ? test -$ svn add test -> A test -> A test/gizmo_test.rb -$ svn commit -m 'Test coverage for problems' -> Adding more_awesome/test -> Adding more_awesome/test/gizmo_test.rb -> Transmitiendo los datos del archivo. -> Revisión confirmada 4. -``` - -#### Alternar entre ramas - -Para alternar entre ramas, probablemente desearás comenzar con un control del `trunk` (tronco): - -```shell -$ svn co --depth empty https://github.com/user/repo/trunk -``` - -Luego, puedes alternar a otra rama: - -```shell -$ svn switch https://github.com/user/repo/branches/more_awesome -``` - -### Encontrar el SHA de confirmación de Git para una confirmación de Subversion - -El servidor de Subversion de GitHub muestra el sha de confirmación de Git para cada confirmación de Subversion. - -Para ver el SHA de confirmación, deberías solicitar la propiedad remota sin versión de `git-commit`. - -```shell -$ svn propget git-commit --revprop -r HEAD https://github.com/user/repo -05fcc584ed53d7b0c92e116cb7e64d198b13c4e3 -``` - -Con este SHA de confirmación, puedes, por ejemplo, consultar la correspondiente confirmación Git en GitHub. - -### Leer más - -* "[Propiedades de Subversion admitidas por GitHub](/articles/subversion-properties-supported-by-github)" diff --git a/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md b/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md deleted file mode 100644 index 41b44119ed..0000000000 --- a/translations/es-XL/content/github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: ¿Cuáles son las diferencias entre Subversion y Git? -intro: 'Los repositorios de Subversion (SVN) son similares a los repositorios de Git, pero hay diferencias cuando se refiere a la arquitectura de tus proyectos.' -redirect_from: - - /articles/what-are-the-differences-between-svn-and-git/ - - /articles/what-are-the-differences-between-subversion-and-git - - /github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git -versions: - fpt: '*' - ghes: '*' ---- -### Estructura del directorio - -Cada *referencia*, o instantánea etiquetada de una confirmación, en un proyecto se organiza dentro de subdirectorios específicos, como `tronco`, `ramas` y `etiquetas`. Por ejemplo, un proyecto SVN con dos características bajo desarrollo debería parecerse a esto: - - sample_project/trunk/README.md - sample_project/trunk/lib/widget.rb - sample_project/branches/new_feature/README.md - sample_project/branches/new_feature/lib/widget.rb - sample_project/branches/another_new_feature/README.md - sample_project/branches/another_new_feature/lib/widget.rb - -Un flujo de trabajo SVN se parece a esto: - -* El directorio `tronco` representa el último lanzamiento estable de un proyecto. -* El trabajo de característica activa se desarrolla dentro de subdirectorios dentro de `ramas`. -* Cuando una característica se termina, el directorio de la característica se fusiona dentro del `tronco` y se elimina. - -Los proyectos de Git también se almacenan dentro de un directorio único. Sin embargo, Git oculta los detalles de sus referencias al almacenarlos en un directorio *.git* especial. Por ejemplo, un proyecto Git con dos características bajo desarrollo debería parecerse a esto: - - sample_project/.git - sample_project/README.md - sample_project/lib/widget.rb - -Un flujo de trabajo Git se parece a esto: - -* Un repositorio Git almacena el historial completo de todas sus ramas y etiquetas dentro del directorio de *.git*. -* El último lanzamiento estable es contenido dentro de la rama `master o principal`. -* El trabajo de característica activa se desarrolla en ramas separadas. -* Cuando una característica se termina, la rama de la característica se fusiona dentro de la rama `master o principal` y se elimina. - -A diferencia de SVN, con Git la estructura del directorio permanece igual, pero los contenidos de los archivos cambia en base a tu rama. - -### Incluir los subproyectos - -Un *subproyecto* es un proyecto que se ha desarrollado y administrado en algún lugar fuera del proyecto principal. Normalmente importas un subproyecto para agregar alguna funcionalidad a tu proyecto sin necesidad de mantener el código. Cada vez que el proyecto se actualiza, puedes sincronizarlo con tu proyecto para garantizar que todo esté actualizado. - -En SVN, un subproyecto se llama un *SVN externo*. En Git, se llama un *submódulo Git*. A pesar de que conceptualmente son similares, los submódulos Git no se mantienen actualizados de forma automática; debes solicitar explícitamente que se traiga una nueva versión a tu proyecto. - -Para obtener más información, consulta la sección "[Submódulos de las Git Tools](https://git-scm.com/book/en/Git-Tools-Submodules)" en la documentación de Git. - -### Mantener el historial - -SVN está configurado para suponer que el historial de un proyecto nunca cambia. Git te permite modificar cambios y confirmaciones previas utilizando herramientas como [`git rebase`](/articles/about-git-rebase). - -{% tip %} - -[GitHub admite clientes de Subversion](/articles/support-for-subversion-clients), lo que puede generar algunos resultados inesperados si estás utilizando tanto Git como SVN en el mismo proyecto. Si has manipulado el historial de confirmación de Git, esas mismas confirmaciones siempre permanecerán dentro del historial de SVN. Si accidentalmente confirmaste algunos datos confidenciales, hay un [artículo que te ayudará a eliminarlo del historial de Git](/articles/removing-sensitive-data-from-a-repository). - -{% endtip %} - -### Leer más - -- "[Propiedades de Subversion admitidas por GitHub](/articles/subversion-properties-supported-by-github)" -- ["Branching and Merging" del libro _Git SCM_](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging) -- "[Importar código fuente a GitHub](/articles/importing-source-code-to-github)" -- "[Herramientas de migración de código fuente](/articles/source-code-migration-tools)" diff --git a/translations/es-XL/content/github/index.md b/translations/es-XL/content/github/index.md deleted file mode 100644 index 04d183038b..0000000000 --- a/translations/es-XL/content/github/index.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: GitHub.com -redirect_from: - - /articles/ - - /common-issues-and-questions/ - - /troubleshooting-common-issues/ -intro: 'Documentación, guías y temas de ayuda para programadores de software, diseñadores y gerentes de proyectos. Cubre el uso de Git, solicitudes de extracción, propuestas, wikis, gists y todo lo necesario para sacar el máximo provecho de GitHub para programación.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /copilot - - /setting-up-and-managing-your-enterprise - - /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 - - /customizing-your-github-workflow - - /extending-github - - /working-with-github-support - - /understanding-how-github-uses-and-protects-your-data - - /site-policy - - /site-policy-deprecated ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/index.md b/translations/es-XL/content/github/managing-files-in-a-repository/index.md deleted file mode 100644 index 2856493135..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Administrar archivos en un repositorio -redirect_from: - - /categories/81/articles/ - - /categories/manipulating-files/ - - /categories/managing-files-in-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /managing-files-on-github - - /managing-files-using-the-command-line - - /working-with-non-code-files ---- -### Índice - - diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/adding-a-file-to-a-repository.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/adding-a-file-to-a-repository.md deleted file mode 100644 index b683177f7f..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/adding-a-file-to-a-repository.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Agregar un archivo a un repositorio -intro: 'Puedes cargar y confirmar un archivo existente a un repositorio {% data variables.product.product_name %}. Arrastra y suelta un archivo en cualquier directorio en el árbol de archivos desde la página principal del repositorio.' -redirect_from: - - /articles/adding-a-file-to-a-repository - - /github/managing-files-in-a-repository/adding-a-file-to-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -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](/articles/adding-a-file-to-a-repository-using-the-command-line)". - -{% tip %} - -**Sugerencias:** -- Puedes cargar múltiples archivos en {% data variables.product.product_name %} a la vez. -- {% data reusables.repositories.protected-branches-block-web-edits-uploads %} - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -2. Debajo del nombre del repositorio, haz clic en **Upload files** (Cargar archivos). ![Botón Upload files (Cargar archivos)](/assets/images/help/repository/upload-files-button.png) -{% else %} -2. Sobre la lista de archivos, da clic en **Cargar archivos** utilizando el menú desplegable de **Agregar archivo**. !["Archivos cargados" en el menú desplegable de "Agregar archivo"](/assets/images/help/repository/upload-files-button.png) -{% endif %} -3. Arrastra y suelta el archivo o la carpeta que te gustaría cargar en tu repositorio en el árbol del archivo. ![Área para arrastrar y soltar](/assets/images/help/repository/upload-files-drag-and-drop.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -6. Haz clic en **Commit changes** (Confirmar cambios). ![Botón Commit changes (Confirmar cambios)](/assets/images/help/repository/commit-changes-button.png) diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/creating-new-files.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/creating-new-files.md deleted file mode 100644 index f5b4649e0b..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/creating-new-files.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Crear nuevos archivos -intro: 'Puedes crear nuevos archivos directamente en {% data variables.product.product_name %} en cualquier repositorio al que tengas acceso de escritura.' -redirect_from: - - /articles/creating-new-files - - /github/managing-files-in-a-repository/creating-new-files -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Cuando crees un archivo en {% data variables.product.product_name %}, ten en cuenta lo siguiente: - -- Si intentas crear un nuevo archivo en un repositorio al que no tienes acceso, bifurcaremos el proyecto para tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original una vez que confirmes tu cambio. -- Los nombres de los archivos creados a través de la interfaz web solo pueden contener caracteres alfanuméricos y guiones (`-`). Para usar otros caracteres, [crea y confirma los archivos de manera local, y luego súbelos al repositorio en {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository-using-the-command-line). - -{% data reusables.repositories.sensitive-info-warning %} - -{% data reusables.repositories.navigate-to-repo %} -2. En tu repositorio, dirígete a la carpeta en la que deseas crear un archivo. -{% data reusables.files.add-file %} -4. En el campo para el nombre del archivo, escribe el nombre y la extensión del archivo. Para crear subdirectorios, escribe el separador de directorio `/`. ![Nombre del nuevo archivo](/assets/images/help/repository/new-file-name.png) -5. En la pestaña **Editar nuevo archivo**, agrega contenido al archivo. ![Contenido del nuevo archivo](/assets/images/help/repository/new-file-content.png) -6. Para revisar el nuevo contenido, haz clic en **Vista previa**. ![Botón New file preview (Vista previa del archivo nuevo)](/assets/images/help/repository/new-file-preview.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -### Leer más - -- "[Agregar un archivo a un repositorio](/articles/adding-a-file-to-a-repository)" -- [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/deleting-files.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/deleting-files.md deleted file mode 100644 index 9f69b608fc..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/deleting-files.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Eliminar archivos -intro: 'Puedes eliminar cualquier archivo dentro de tus repositorios en {% data variables.product.product_name %}.' -redirect_from: - - /articles/deleting-files - - /github/managing-files-in-a-repository/deleting-files -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% tip %} - -**Sugerencia**: Si tratas de eliminar un archivo en un repositorio al cual no tienes acceso, bifurcaremos el proyecto a tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original después de confirmar tu cambio. - -{% endtip %} - -1. Dirígete al archivo que deseas eliminar de tu repositorio. -2. At the top of the file, click -{% octicon "trashcan" aria-label="The trashcan icon" %}. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} - -{% danger %} - -**Atención**: Dado que Git es un sistema de control de versiones, siempre guarda tu copia de seguridad en caso de que luego necesites recuperar el archivo. Si *realmente* necesitas eliminar **por completo** un archivo de un repositorio por algún motivo, por ejemplo, en caso de que se trate de un archivo confidencial que se confirmó por error, debes seguir los pasos en [nuestro artículo acerca de la eliminación de datos sensibles](/articles/removing-sensitive-data-from-a-repository). - -{% enddanger %} diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/editing-files-in-another-users-repository.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/editing-files-in-another-users-repository.md deleted file mode 100644 index 2b49712183..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/editing-files-in-another-users-repository.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Editar archivos en el repositorio de otro usuario -intro: 'Cuando edites un archivo en el repositorio de otro usuario, automáticamente [bifurcaremos el repositorio](/articles/fork-a-repo) y [abriremos una solicitud de extracción](/articles/creating-a-pull-request) por ti.' -redirect_from: - - /articles/editing-files-in-another-users-repository/ - - /articles/editing-files-in-another-user-s-repository - - /articles/editing-files-in-another-users-repository - - /github/managing-files-in-a-repository/editing-files-in-another-users-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -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. -3. Realiza todos los cambios que necesites en el archivo. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png) -{% data reusables.files.preview_change %} -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -6. Haz clic en **Proponer cambio en el archivo**. ![Botón Confirmar cambios](/assets/images/help/repository/propose_file_change_button.png) -7. Escribe un título y una descripción para tu solicitud de extracción. ![Página de descripción de la solicitud de extracción](/assets/images/help/pull_requests/pullrequest-description.png) -8. Haz clic en **Create Pull Request** (Crear solicitud de extracción). ![Botón Solicitud de extracción](/assets/images/help/pull_requests/pullrequest-send.png) - -### Leer más - -* "[Editar archivos en un repositorio](/articles/editing-files-in-your-repository)" diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/editing-files-in-your-repository.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/editing-files-in-your-repository.md deleted file mode 100644 index 8c72b2f211..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/editing-files-in-your-repository.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Editar archivos en tu repositorio -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/ - - /articles/editing-files-in-your-repository - - /github/managing-files-in-a-repository/editing-files-in-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% tip %} - -**Sugerencia**:{% data reusables.repositories.protected-branches-block-web-edits-uploads %} - -{% endtip %} - -{% note %} - -**Nota:** El editor de archivos de {% data variables.product.product_name %} usa [CodeMirror](https://codemirror.net/). - -{% endnote %} - -1. En tu repositorio, dirígete al archivo que deseas editar. -{% data reusables.repositories.edit-file %} -3. En la pestaña **Editar archivo**, realiza todos los cambios que sean necesarios. ![Nuevo contenido en el archivo](/assets/images/help/repository/edit-readme-light.png) -{% data reusables.files.preview_change %} -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} - -### Leer más - -* "[Editar archivos en el repositorio de otro usuario](/articles/editing-files-in-another-user-s-repository)" diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/getting-permanent-links-to-files.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/getting-permanent-links-to-files.md deleted file mode 100644 index 5ccb1bf3bc..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/getting-permanent-links-to-files.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: Obtener enlaces permanentes a archivos -intro: 'Cuando ves un archivo en {% data variables.product.product_location %}, puedes presionar la tecla "y" para actualizar la URL y obtener un enlace permanente para la versión exacta del archivo que estás viendo.' -redirect_from: - - /articles/getting-a-permanent-link-to-a-file/ - - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url/ - - /articles/getting-permanent-links-to-files - - /github/managing-files-in-a-repository/getting-permanent-links-to-files -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% tip %} - -**Sugerencia**: Presiona "?" en cualquier página en {% data variables.product.product_name %} para ver todos los atajos del teclado disponibles. - -{% endtip %} - -### Vistas del archivo que muestran la versión más reciente en una rama - -Cuando ves un archivo en {% data variables.product.product_location %}, por lo general, accedes a la versión en el encabezado actual de una rama. Por ejemplo: - -* [https://github.com/github/hubot/blob/**master**/README.md](https://github.com/github/hubot/blob/master/README.md) - -se refiere al repositorio `hubot` de GitHub y muestra la versión actual de la rama `master` del archivo `README.md`. - -La versión de un archivo en el encabezado de una rama puede cambiar cuando se realizan nuevas confirmaciones, por eso si copias la URL normal, el contenido del archivo puede no ser el mismo cuando alguien lo vea más tarde. - -### Presiona y para obtener un enlace permanente en archivo en una confirmación específica - -Para obtener un enlace permanente a la versión específica de un archivo que ves, en lugar de usar el nombre de una rama en la URL (es decir, la parte `master` en el ejemplo anterior) coloca un ID de confirmación. Esto generará un enlace permanente a la versión exacta del archivo en esa confirmación. Por ejemplo: - -* [https://github.com/github/hubot/blob/**ed25584f5ac2520a6c28547ffd0961c7abd7ea49**/README.md](https://github.com/github/hubot/blob/ed25584f5ac2520a6c28547ffd0961c7abd7ea49/README.md) - -remplaza `master` por un ID de confirmación específico y el contenido del archivo no cambiará. - -Buscar de manera manual el SHA de confirmación es muy poco práctico. No obstante, a modo de atajo, puedes escribir y para actualizar automáticamente la URL para la versión del enlace permanente. Luego puedes copiar la URL sabiendo que todas las personas con quienes la compartas verán exactamente lo mismo que tú viste. - -{% tip %} - -**Sugerencia**: Puedes colocar un identificador que se puede resolver para una confirmación en la URL, incluidos los nombres de las ramas, los SHA de confirmación específicos o las etiquetas. - -{% endtip %} - -### Crear un enlace permanente a un fragmento de código - -Puedes crear un enlace permanente a una línea específica o a un rango de líneas de código en una versión específica de un archivo o de una solicitud de extracción. Para obtener más información, consulta "[Crear un enlace permanente al fragmento de código](/articles/creating-a-permanent-link-to-a-code-snippet/)". - -### Leer más - -- "[Archivar un repositorio de GitHub](/articles/archiving-a-github-repository)" diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/index.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/index.md deleted file mode 100644 index a6e992e640..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Administrar archivos en GitHub -intro: 'En {% data variables.product.product_name %}, puedes crear, editar, mover y eliminar archivos en un repositorio.' -redirect_from: - - /articles/managing-files-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /navigating-code-on-github - - /creating-new-files - - /adding-a-file-to-a-repository - - /moving-a-file-to-a-new-location - - /editing-files-in-your-repository - - /editing-files-in-another-users-repository - - /tracking-changes-in-a-file - - /deleting-files-in-a-repository - - /renaming-a-file - - /getting-permanent-links-to-files ---- - diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/moving-a-file-to-a-new-location.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/moving-a-file-to-a-new-location.md deleted file mode 100644 index 9b3503c4c8..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/moving-a-file-to-a-new-location.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Mover un archivo a una nueva ubicación -intro: 'Cuando editas un archivo, puedes elegir moverlo a cualquier lugar dentro de tu repositorio, incluso si el directorio no existe.' -redirect_from: - - /articles/moving-a-file-to-a-new-location - - /github/managing-files-in-a-repository/moving-a-file-to-a-new-location -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -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. - -{% tip %} - -**Tips**: - -- Si tratas de mover un archivo en un repositorio al cual no tienes acceso, bifurcaremos el proyecto a tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original después de confirmar tu cambio. -- Algunos archivos, como imágenes, necesitan que los muevas desde la línea de comando. Para obtener más información, consulta "[Mover un archivo a una nueva ubicación utilizando la línea de comando](/articles/moving-a-file-to-a-new-location-using-the-command-line)". -- {% data reusables.repositories.protected-branches-block-web-edits-uploads %} - -{% endtip %} - -1. En tu repositorio, navega hasta el archivo que deseas mover. -2. En la esquina superior derecha de la vista del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %} para abrir el editor de archivos. ![Icono Edit file (Editar archivo)](/assets/images/help/repository/move-file-edit-file-icon.png) -3. En el campo de nombre de archivo, cambia el nombre del archivo utilizando estos lineamientos: ![Editar el nombre del archivo](/assets/images/help/repository/moving_files.gif) - - Para mover el archivo **dentro de una subcarpeta**, escribe el nombre de la carpeta que deseas, seguido de `/`. El nombre de tu nueva carpeta se convierte en el nuevo elemento en la ruta de navegación. - - Para mover el archivo dentro de un directorio **encima de la ubicación actual del archivo**, coloca tu cursor al comienzo del campo de nombre de archivo, después escribe `../` para subir un nivel completo de directorio, o presiona la tecla de `retroceso` para editar el nombre de la carpeta padre. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/navigating-code-on-github.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/navigating-code-on-github.md deleted file mode 100644 index f299f55343..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/navigating-code-on-github.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Código de navegación en GitHub -intro: 'Puedes comprender las relaciones dentro y a través de los repositorios al navegar directamente por código en {% data variables.product.product_name %}.' -redirect_from: - - /articles/navigating-code-on-github - - /github/managing-files-in-a-repository/navigating-code-on-github -versions: - free-pro-team: '*' -topics: - - Repositories ---- -### Acerca de la navegación de código en {% data variables.product.prodname_dotcom %} - -Las funciones del código de navegación usan la biblioteca de código abierto [semántica](https://github.com/github/semantic). Los siguientes idiomas son compatibles: -- CodeQL -- Go -- Java -- JavaScript -- PHP -- Python -- Ruby -- TypeScript - -{% note %} - -**Nota**: La navegación de código funciona para las ramas activas. Si tienes la función habilitada pero no ves los enlaces a las definiciones de las funciones y los métodos, sube a la rama y trata nuevamente. - -{% endnote %} - -### Saltar a la definición de una función o método - -Puedes saltar a una definición de función o de método dentro del mismo repositorio si das clic en la llamada a dicha función o método dentro de un archivo. - -![Pestaña Jump-to-definition](/assets/images/help/repository/jump-to-definition-tab.png) - -### Buscar todas las referencias de una función o método - -Puedes encontrar todas las referencias para una función o método dentro del mismo repositorio si das clic en el llamado a dicha función o método en un archivo y posteriormente das clic en la pestaña de **Referencias**. - -![Pestaña Find all references (Buscar todas las referencias)](/assets/images/help/repository/find-all-references-tab.png) - -### Leer más -- "[Buscar código](/github/searching-for-information-on-github/searching-code)" diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/renaming-a-file.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/renaming-a-file.md deleted file mode 100644 index 4441899255..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/renaming-a-file.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Renombrar un archivo -intro: 'Puedes renombrar cualquier archivo de tus repositorios directamente en {% data variables.product.product_name %}. Renombrar un archivo también te da la posibilidad de [mover el archivo a una ubicación nueva](/articles/moving-a-file-to-a-new-location).' -redirect_from: - - /articles/renaming-a-file - - /github/managing-files-in-a-repository/renaming-a-file -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% tip %} - -**Tips**: - -- Si intentas renombrar un archivo de un repositorio al que no tienes acceso, bifurcaremos el proyecto para tu cuenta de usuario y te ayudaremos a enviar [una solicitud de extracción](/articles/about-pull-requests) al repositorio original después de que confirmes tu cambio. -- Los nombres de los archivos creados a través de la interfaz web solo pueden contener caracteres alfanuméricos y guiones (`-`). Para utilizar otros caracteres, crea y confirma los archivos de forma local y luego súbelos al repositorio. -- Algunos archivos, como las imágenes, requieren que los renombres desde la línea de comando. Para obtener más información, consulta "[Renombrar un archivo usando la línea de comando](/articles/renaming-a-file-using-the-command-line)". - -{% endtip %} - -1. En tu repositorio, busca el archivo que quieres renombrar. -2. En la esquina superior derecha de la vista del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %} para abrir el editor de archivos. ![Icono Edit file (Editar archivo)](/assets/images/help/repository/edit-file-icon.png) -3. En el campo de nombre del archivo, cambia el nombre del archivo con el nombre de archivo nuevo que quieras. También puedes actualizar los contenidos de tu archivo en el mismo momento. ![Editar el nombre del archivo](/assets/images/help/repository/changing-file-name.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file.md deleted file mode 100644 index 12c7e6173d..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Rastrear cambios en un archivo -intro: Puedes rastrear cambios de líneas en un archivo y descubrir la manera en que las partes del archivo fueron evolucionando. -redirect_from: - - /articles/using-git-blame-to-trace-changes-in-a-file/ - - /articles/tracing-changes-in-a-file/ - - /articles/tracking-changes-in-a-file - - /github/managing-files-in-a-repository/tracking-changes-in-a-file -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Con la vista de último responsable, puedes ver el historial de revisión línea por línea para todo un archivo o ver el historial de revisión de una única línea dentro de un archivo haciendo clic en {% octicon "versions" aria-label="The prior blame icon" %}. Cada vez que hagas clic en {% octicon "versions" aria-label="The prior blame icon" %}, verás la información de revisión anterior para esa línea, incluido quién y cuándo confirmó el cambio. - -![Vista de último responsable de Git](/assets/images/help/repository/git_blame.png) - -En un archivo o solicitud de extracción, también puedes utilizar el menú {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} para ver el último responsable de Git para una línea o rango de líneas seleccionado. - -![Menú Kebab con opciones para ver el último responsable de Git para una línea seleccionada](/assets/images/help/repository/view-git-blame-specific-line.png) - -{% tip %} - -**Sugerencia:** En la línea de comando, también puedes utilizar `git blame` para ver el historial de revisión de líneas dentro de un archivo. Para obtener más información, consulta la documentación de [ `git blame`](https://git-scm.com/docs/git-blame) de Git. - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -2. Haz clic para abrir el archivo cuyo historial de líneas quieres ver. -3. En la esquina superior derecha de la vista del archivo, haz clic en **Blame** (Último responsable) para abrir la vista del último responsable. ![Botón Blame (Último responsable)](/assets/images/help/repository/blame-button.png) -4. Para ver versiones anteriores de una línea específica, o el siguiente último responsable, haz clic en {% octicon "versions" aria-label="The prior blame icon" %} hasta que hayas encontrado los cambios que quieres ver. ![Botón Prior blame (Último responsable anterior)](/assets/images/help/repository/prior-blame-button.png) diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/adding-a-file-to-a-repository-using-the-command-line.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/adding-a-file-to-a-repository-using-the-command-line.md deleted file mode 100644 index 27364f6cad..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/adding-a-file-to-a-repository-using-the-command-line.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Agregar un archivo a un repositorio utilizando la línea de comando -intro: 'Puedes cargar un archivo existente a un repositorio {% data variables.product.product_name %} utilizando la línea de comando.' -redirect_from: - - /articles/adding-a-file-to-a-repository-from-the-command-line/ - - /articles/adding-a-file-to-a-repository-using-the-command-line - - /github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% tip %} - -**Sugerencia:** También puedes [agregar un archivo existente a un repositorio desde el sitio web de {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository). - -{% endtip %} - -{% data reusables.command_line.manipulating_file_prereqs %} - -{% data reusables.repositories.sensitive-info-warning %} - -1. En tu computadora, mueve el archivo que deseas cargar a {% data variables.product.product_name %} en el directorio local que se creó cuando clonaste el repositorio. -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.command_line.switching_directories_procedural %} -{% data reusables.git.stage_for_commit %} - ```shell - $ git add . - # Agrega el archivo a tu repositorio local y lo presenta para la confirmación. {% data reusables.git.unstage-codeblock %} - ``` -{% data reusables.git.commit-file %} - ```shell - $ git commit -m "Add existing file" - # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} - ``` -{% data reusables.git.git-push %} - -### Leer más - -- "[Crear archivos nuevos](/articles/creating-new-files)" -- [Agregar un proyecto existente a GitHub mediante la línea de comando](/articles/adding-an-existing-project-to-github-using-the-command-line)" diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/index.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/index.md deleted file mode 100644 index 08911d395e..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Administrar archivos utilizando la línea de comando -intro: 'Utilizando la línea de comando, puedes agregar, renombrar y mover archivos en un repositorio.' -redirect_from: - - /articles/managing-files-using-the-command-line -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /adding-a-file-to-a-repository-using-the-command-line - - /renaming-a-file-using-the-command-line - - /moving-a-file-to-a-new-location-using-the-command-line ---- - diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/moving-a-file-to-a-new-location-using-the-command-line.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/moving-a-file-to-a-new-location-using-the-command-line.md deleted file mode 100644 index 13386ae29a..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/moving-a-file-to-a-new-location-using-the-command-line.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Mover un archivo a una nueva ubicación utilizando la línea de comando -intro: Puedes utilizar la línea de comando para mover archivos dentro de un repositorio al eliminar el archivo de la ubicación anterior y después agregarlo en la nueva ubicación. -redirect_from: - - /articles/moving-a-file-to-a-new-location-using-the-command-line - - /github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Muchos archivos pueden [moverse directamente en {% data variables.product.product_name %}](/articles/moving-a-file-to-a-new-location), pero algunos archivos, como imágenes, necesitan que los muevas desde la línea de comando. - -{% data reusables.command_line.manipulating_file_prereqs %} - -1. En la computadora, mueve el archivo a una nueva ubicación dentro del directorio que fue creado localmente en tu computadora cuando clonaste el repositorio. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Utiliza `git status` para verificar la nueva ubicación y la ubicación anterior del archivo. - ```shell - $ git status - > # On branch your-branch - > # Changes not staged for commit: - > # (use "git add/rm ..." to update what will be committed) - > # (use "git checkout -- ..." to discard changes in working directory) - > # - > # deleted: /old-folder/image.png - > # - > # Untracked files: - > # (use "git add ..." to include in what will be committed) - > # - > # /new-folder/image.png - > # - > # no changes added to commit (use "git add" and/or "git commit -a") - ``` -{% data reusables.git.stage_for_commit %} Esto eliminará, o `git rm`, el archivo de la ubicación antigua y agregará, o `git add`, el archivo en la nueva ubicación. - ```shell - $ git add . - # Agrega el archivo a tu repositorio local y lo presenta para la confirmación. - # {% data reusables.git.unstage-codeblock %} - ``` -5. Utiliza `git status` para verificar los cambios preparados para confirmar. - ```shell - $ git status - > # On branch your-branch - > # Changes to be committed: - > # (use "git reset HEAD ..." to unstage) - > # - > # renamed: /old-folder/image.png -> /new-folder/image.png - # Displays the changes staged for commit - ``` -{% data reusables.git.commit-file %} - ```shell - $ git commit -m "Move file to new directory" - # Commits the tracked changes and prepares them to be pushed to a remote repository. - # {% data reusables.git.reset-head-to-previous-commit-codeblock %} - ``` -{% data reusables.git.git-push %} - -### Leer más - -- "[Renombrar un archivo utilizando la línea de comando](/articles/renaming-a-file-using-the-command-line)" -- [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/renaming-a-file-using-the-command-line.md b/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/renaming-a-file-using-the-command-line.md deleted file mode 100644 index 212eb71fec..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/managing-files-using-the-command-line/renaming-a-file-using-the-command-line.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Renombrar un archivo usando la línea de comando -intro: Puedes usar la línea de comando para renombrar cualquier archivo de tu repositorio. -redirect_from: - - /articles/renaming-a-file-using-the-command-line - - /github/managing-files-in-a-repository/renaming-a-file-using-the-command-line -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Muchos archivos se pueden [renombrar directamente en {% data variables.product.product_name %}](/articles/renaming-a-file), pero algunos, como las imágenes, requieren que los renombres desde la línea de comando. - -{% data reusables.command_line.manipulating_file_prereqs %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.command_line.switching_directories_procedural %} -3. Renombra el archivo, especificando el nombre de archivo antiguo y el nombre de archivo nuevo que le quieres asignar. Esto preparará tu cambio para la confirmación. - ```shell - $ git mv old_filename new_filename - ``` -4. Utiliza `git status` para comprobar los nombres de archivo antiguo y nuevo. - ```shell - $ git status - > # On branch your-branch - > # Changes to be committed: - > # (use "git reset HEAD ..." to unstage) - > # - > # renamed: old_filename -> new_filename - > # - ``` -{% data reusables.git.commit-file %} - ```shell - $ git commit -m "Rename file" - # Commits the tracked changes and prepares them to be pushed to a remote repository. - # {% data reusables.git.reset-head-to-previous-commit-codeblock %} - ``` -{% data reusables.git.git-push %} - -### Leer más -- "[Mover un archivo a una ubicación nueva mediante la línea de comando](/articles/moving-a-file-to-a-new-location-using-the-command-line)" -- [Agregar un archivo a un repositorio mediante la línea de comando](/articles/adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/3d-file-viewer.md b/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/3d-file-viewer.md deleted file mode 100644 index c3a2865bb3..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/3d-file-viewer.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Visualizador de archivos 3D -redirect_from: - - /articles/stl-file-viewer/ - - /articles/3d-file-viewer - - /github/managing-files-in-a-repository/3d-file-viewer -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% data variables.product.product_name %} puede alojar y representar archivos 3D con la extensión *.stl*. - -Al buscar directamente en un archivo STL en {% data variables.product.product_name %} puedes: - -* Hacer clic y arrastrar para girar el modelo. -* Hacer clic con el botón derecho y arrastrar para traducir la vista. -* Desplazarse para acercar y alejar. -* Hacer clic en los diferentes modos para cambiar la vista. - -### Diferencias - -Cuando miras una confirmación de cambios o un conjunto de cambios que incluyen un archivo STL, podrás ver una diferencia de antes y después del archivo. - -Por defecto, obtendrás una vista donde todo lo que no ha cambiado está en el esquema de página. Las adiciones aparecen en verde y las partes eliminadas aparecen en rojo. - -![esquema de página](/assets/images/help/repository/stl_wireframe.png) - -También puedes seleccionar la opción **Control deslizante de la revisión**, que te permite usar un control deslizante en la parte superior del archivo para cambiar entre las revisiones actuales y las anteriores. - -### Solucionar un rendimiento reducido - -Si ves este ícono en la esquina del visualizador, entonces la tecnología WebGL no está disponible en tu navegador: - -![error emergente de WebGL](/assets/images/help/repository/render_webgl_error.png) - -WebGL es necesario para aprovechar el hardware de tu equipo al máximo. Te recomendamos que intentes con navegadores como [Chrome](https://www.google.com/intl/en/chrome/browser/) o [Firefox](https://www.mozilla.org/en-US/firefox/new/), que vienen con WebGL activado. - -### Error: "No se puede mostrar" - -Si tu modelo no es válido, es posible que GitHub no pueda mostrar el archivo. Además, los archivos de más de 10 MB son demasiado grandes para que GitHub los muestre. - -### Insertar tu modelo en otro lugar - -Para mostrar tu archivo 3D en algún otro lugar de Internet, modifica esta plantilla y colócala en cualquier página HTML que sea compatible con JavaScript: - -```html - -``` - -Por ejemplo, si la URL de tu modelo es [github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl](https://github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl), tu código para insertar sería: - -```html - -``` - -Por defecto, la representación insertada es de 420 píxeles de ancho por 620 de alto, pero puedes personalizar la salida, pasando las variables de altura y ancho como parámetros al final de la URL, como `?height=300&width=500`. - -{% tip %} - -**Nota**: `ref` puede ser una rama del hash para una confirmación individual (como `2391ae`). - -{% endtip %} diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/index.md b/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/index.md deleted file mode 100644 index e3ff453701..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Trabajar con archivos sin código -intro: '' -redirect_from: - - /categories/89/articles/ - - /articles/working-with-non-code-files -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /rendering-and-diffing-images - - /3d-file-viewer - - /rendering-csv-and-tsv-data - - /rendering-pdf-documents - - /rendering-differences-in-prose-documents - - /mapping-geojson-files-on-github - - /working-with-jupyter-notebook-files-on-github ---- - diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/mapping-geojson-files-on-github.md b/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/mapping-geojson-files-on-github.md deleted file mode 100644 index e7446c5431..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/mapping-geojson-files-on-github.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Mapear archivos geoJSON en GitHub -redirect_from: - - /articles/mapping-geojson-files-on-github - - /github/managing-files-in-a-repository/mapping-geojson-files-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% 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. - -Cuando haces clic en el ícono de papel a la derecha, también verás los cambios realizados a ese archivo como parte de una confirmación de cambios. - -![Captura de pantalla de conmutación de representación de fuente](/assets/images/help/repository/source-render-toggle-geojson.png) - -### Tipos de Geometry - -Los mapas en {% data variables.product.product_name %} utilizan [Leaflet.js](http://leafletjs.com) y admiten todos los tipos de Geometry indicados en [las especificaciones de geoJSON](http://www.geojson.org/geojson-spec.html) (Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon y GeometryCollection). Los archivos TopoJSON deberían ser del tipo "Topology" y adherir a las especificaciones [topoJSON](https://github.com/mbostock/topojson/wiki/Specification). - -### Características de estilo - -Puedes personalizar la manera en que se muestran las características, como especificar un color particular o agregar un ícono descriptivo, al pasar metadatos adicionales dentro de las propiedades del objeto geoJSON. Las opciones son: - -* `marker-size` - `small`, `medium`, o `large` -* `marker-color` - color RGB hex válido -* `marker-symbol` - un ID del ícono del [proyecto Maki ](http://mapbox.com/maki/) o un carácter único alfanumérico (a-z o 0-9). -* `stroke` - color de una línea o borde de un polígono (RGB) -* `stroke-opacity` - opacidad de una línea o borde de un polígono (0.0 - 1.0) -* `stroke-width` - ancho de una línea o borde de un polígono -* `fill` - el color del interior de un polígono (GRB) -* `fill-opacity` - la opacidad del interior de un polígono (0.0-1.0) - -Consulta la versión [1.1.0 de las especificaciones de estilo simple abierto](https://github.com/mapbox/simplestyle-spec/tree/master/1.1.0) para obtener más información. - -### Incrustrar tu mapa en otro lugar - -Deseas hacer disponible tu mapa geoJSON en un lugar distinto a {% data variables.product.product_name %}? Simplemente modifica esta plantilla, y colócala en alguna página HTML que admita javascript (p. ej., [{% data variables.product.prodname_pages %}](http://pages.github.com)): - -```html - -``` - -Por ejemplo, si la URL de tu mapa es [github.com/benbalter/dc-wifi-social/blob/master/bars.geojson](https://github.com/benbalter/dc-wifi-social/blob/master/bars.geojson), tu código de incrustación sería: - -```html - -``` - -Por defecto, el mapa incrustado es 420px x 620px, pero puedes personalizar el resultado al pasar variables de alto y ancho como parámetros al final, como `?height=300&width=500`. - -{% tip %} - -**Nota**: `ref` puede ser una rama del hash para una confirmación individual (como `2391ae`). - -{% endtip %} - -### Agrupación - -Si tu mapa contiende una gran cantidad de marcadores (aproximadamente más de 750), GitHub automáticamente agrupará marcadores cercanos en niveles superiores de zoom. Simplemente haz clic la agrupación o el zoom de acercamiento para ver los marcadores individuales. - -### Algo sucede con el mapa subyacente - -Los datos del mapa subyacente (nombres de calles, caminos, etc.) están controlados por [OpenStreetMap](http://www.openstreetmap.org/), un proyecto colaborativo para crear un mapa editable gratuito del mundo. Si notas que algo no está del todo bien, ya que es código abierto, simplemente [sign up](https://www.openstreetmap.org/user/new) y envía un arreglo. - -### Solución de problemas - -Si estás teniendo problemas al representar archivos geoJSON, asegúrate que tienes un archivo geoJSON válido al ejecutarlo en un [limpiador de geoJSON](http://geojsonlint.com/). Si tus puntos no aparecen donde lo esperas (p. ej., aparecen en la mitad del océano), es probable que los datos estén en una proyección que actualmente no se admite. Actualmente, {% data variables.product.product_name %} admite únicamente la proyección `urn:ogc:def:crs:OGC:1.3:CRS84`. - -Por otra parte, si tu archivo `.geojson` es particularmente grande (superior a 10 MB), no es posible representarlo dentro del navegador. Si ese es el caso, por lo general verás un mensaje similar a este: - -![Archivo de gran tamaño](/assets/images/help/repository/view_raw.png) - -Todavía se podrían representar los datos al convertir el archivo `.geojson` a [TopoJSON](https://github.com/mbostock/topojson), un formato de compresión que, en algunos casos, puede reducir el tamaño del archivo hasta un 80 %. Por supuesto, siempre puedes partir el archivo en fragmentos más pequeños (como por estado o por año), y almacenar los datos como archivos múltiples dentro del repositorio. - -### Recursos adicionales - -* [Documentación Leaflet.js geojson](http://leafletjs.com/examples/geojson.html) -* [Documentación de estilización de marcador MapBox](http://www.mapbox.com/developers/simplestyle/) -* [TopoJSON Wiki](https://github.com/mbostock/topojson/wiki) diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-and-diffing-images.md b/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-and-diffing-images.md deleted file mode 100644 index 23e5fd703b..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-and-diffing-images.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Representar y comparar imágenes -intro: '{% data variables.product.product_name %} puede mostrar varios formatos de imagen comunes, incluidos PNG, JPG, GIF, PSD y SVG. Asimismo, para simplificar mostrarlas, existen diversas formas de comparar las diferencias entre las versiones de esos formatos de imagen.' -redirect_from: - - /articles/rendering-and-diffing-images - - /github/managing-files-in-a-repository/rendering-and-diffing-images -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% note %} - -**Nota:** Si estás utilizando el navegador Firefox, puede que los SVG en {% data variables.product.prodname_dotcom %} no se representen. - -{% endnote %} - -### Ver imágenes - -Puedes navegar y ver imágenes directamente en tu {% data variables.product.product_name %} repositorio: - -![imagen alineada](/assets/images/help/images/view.png) - -Los SVG actualmente no admiten scripting alineado o animación. - -### Ver diferencias - -Puedes comparar visualmente las imágenes de tres modos diferentes: [2-up](#2-up), [deslizar](#swipe) y [papel cebolla](#onion-skin). - -#### 2-up - -**2-up** es el modo predeterminado; te muestra una descripción rápida de ambas imágenes. Asimismo, si la imagen cambió de tamaño entre las versiones, se muestra el cambio de dimensión real. Esto debería ser muy evidente cuando las cosas cambian de tamaño, como cuando los activos se suben de categoría a resoluciones más altas. - -![2-up](/assets/images/help/repository/images-2up-view.png) - -#### Deslizar - -**Deslizar**te deja ver partes de tus imágenes. ¿No estás seguro de si cambiaron los colores en las diferentes versiones? Arrastra el control deslizante de deslizamiento sobre el área en cuestión y compara los píxeles tú mismo. - -![Deslizar](/assets/images/help/repository/images-swipe-view.png) - -#### Papel cebolla - -**Papel cebolla** realmente ayuda cuando los elementos apenas se desplazan y cuesta percibir el cambio. ¿Un icono se corrió dos píxeles a la izquierda? Arrastra el control deslizante de opacidad hacia atrás un poco y comprueba si las cosas se desplazaron. - -![Papel cebolla](/assets/images/help/repository/images-onion-view.gif) diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-csv-and-tsv-data.md b/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-csv-and-tsv-data.md deleted file mode 100644 index 415d8fefbb..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-csv-and-tsv-data.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Representar datos CSV y TSV -redirect_from: - - /articles/rendering-csv-and-tsv-data - - /github/managing-files-in-a-repository/rendering-csv-and-tsv-data -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -GitHub admite la representación de datos tabulares en la forma de archivos *.csv* (separados por coma) y .*tsv* (separados por pestaña). - -![Muestra de CSV representado](/assets/images/help/repository/rendered_csv.png) - -Cuando se visualiza, cualquier archivo _.csv_ o _.tsv_ confirmado en un repositorio de {% data variables.product.product_name %} se representa automáticamente como una tabla interactiva, completa con encabezados y numeración de filas. Por defecto, siempre asumimos que la primera fila es tu fila de encabezados. - -Puedes generar un enlace a una fila particular haciendo clic en el número de fila o seleccionar varias filas manteniendo presionada la tecla shift. Tan solo copia la URL y envíasela a un amigo. - -### Buscar datos - -Si quieres encontrar un valor determinado en tu conjunto de datos, puedes comenzar escribiendo en la barra de búsqueda directamente arriba del archivo. Las filas se filtrarán automáticamente: - -![Buscar valores](/assets/images/help/repository/searching_csvs.gif) - -### Manejar errores - -De manera ocasional, puede que descubras que tu archivo CSV o TSV no se representa. En esas instancias, aparece un cuadro de error al pie del texto original que sugiere cuál puede ser el error. - -![Mensaje de error de representación de CSV](/assets/images/help/repository/csv_render_error.png) - -Los errores comunes incluyen los siguientes: - -* Conteos de columnas que no coinciden. Debes tener la misma cantidad de separadores en cada fila, incluso si la celda está en blanco -* Superar el tamaño de archivo. Nuestra representación solo funciona para archivos de hasta 512KB. Cualquier cosa más grande hace que el navegador se vuelva más lento. diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-differences-in-prose-documents.md b/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-differences-in-prose-documents.md deleted file mode 100644 index 7586511bce..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-differences-in-prose-documents.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Representar diferencias en documentos en prosa -redirect_from: - - /articles/rendering-differences-in-prose-documents - - /github/managing-files-in-a-repository/rendering-differences-in-prose-documents -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Las confirmaciones y solicitudes de extracción que incluyen documentos en prosa tienen la capacidad de representar esos documentos con vistas *de origen* y *representadas*. - -La vista de origen muestra el texto en bruto que se escribió, mientras que la vista representada muestra la manera en que ese texto se vería una vez que se represente en {% data variables.product.product_name %}. Por ejemplo, esto puede ser la diferencia entre mostrar `**negrita**` en Markdown y **negrita** en la vista representada. - -Se admite la representación en prosa para documentos representados compatibles con [github/markup](https://github.com/github/markup): - -* Markdown -* AsciiDoc -* Textile -* ReStructuredText -* Rdoc -* Org -* Creole -* MediaWiki -* Pod - -![Icono Paper (Papel) para ver el documento en prosa representado](/assets/images/help/repository/rendered_prose_diff.png) - -Puedes hacer clic en {% octicon "file" aria-label="The paper icon" %} para ver los cambios hechos al documento como parte de una confirmación. - -![Cambios en prosa representados](/assets/images/help/repository/rendered_prose_changes.png) - -### 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: - -![Cambios en atributos de la prosa representados](/assets/images/help/repository/prose_diff_attributes.png) - -### Comentar cambios - -Solo se pueden agregar [comentarios de la confirmación](/articles/commenting-on-differences-between-files) en los archivos dentro de la vista *de origen*, línea por línea. - -### Vincular a encabezados - -Como con [otros documentos en prosa representados](/articles/about-readmes), deslizarse sobre un encabezado de tu documento crea un icono de enlace. Puedes vincular a los lectores de tu diferencia de prosa representada a secciones específicas. - -### Ver diferencias complejas - -Algunas solicitudes de extracción incluyen una gran cantidad de cambios con documentos grandes y complejos. When the changes take too long to analyze, {% data variables.product.product_name %} can't always produce a rendered view of the changes. If this happens, you'll see an error message when you click the rendered button. - -![Message when view can't be rendered](/assets/images/help/repository/prose_diff_rendering.png) - -Aún puedes utilizar la vista de origen para analizar y comentar cambios. - -### Ver elementos HTML - -No admitimos directamente vistas representadas de confirmaciones en documentos HTML. Algunos formatos, como Markdown, te permiten insertar HTML arbitrarios en un documento. Cuando estos documentos se muestran en {% data variables.product.product_name %}, algunos de esos HTML insertados pueden aparecer en una vista previa, mientras que con otros no es posible hacerlo (como un video de YouTube insertado). - -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. diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-pdf-documents.md b/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-pdf-documents.md deleted file mode 100644 index 7e421680c6..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/rendering-pdf-documents.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Representar documentos PDF -redirect_from: - - /articles/rendering-pdf-documents - - /github/managing-files-in-a-repository/rendering-pdf-documents -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -GitHub admite la representación de documentos PDF. - -![Documento PDF representado](/assets/images/help/repository/rendered-pdf.png) - -Actualmente, se ignoran los enlaces dentro de los PDF. diff --git a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/working-with-jupyter-notebook-files-on-github.md b/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/working-with-jupyter-notebook-files-on-github.md deleted file mode 100644 index 32c1e6ff46..0000000000 --- a/translations/es-XL/content/github/managing-files-in-a-repository/working-with-non-code-files/working-with-jupyter-notebook-files-on-github.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Trabajar con archivos notebook Jupyter en GitHub -intro: 'Cuando agregas archivos notebook Jupyter o notebook iPython con una extensión *.ipynb* en {% data variables.product.product_location %}, se representarán como archivos HTML estáticos en tu repositorio.' -redirect_from: - - /articles/working-with-jupyter-notebook-files-on-github - - /github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -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/master/tutorial/06%20-%20Linking%20and%20Interactions.ipynb). - -Para ver tu notebook Jupyter con el contenido representado de JavaScript o para compartir tus archivos notebook con otros, puedes usar [nbviewer](https://nbviewer.jupyter.org/). Para obtener un ejemplo, consulta [*Enlaces e interacciones.ipynb*](https://nbviewer.jupyter.org/github/bokeh/bokeh-notebooks/blob/master/tutorial/06%20-%20Linking%20and%20Interactions.ipynb) representados en nbviewer. - -Para ver una versión completamente interactiva de tu notebook Jupyter, puedes configurar un servidor notebook de manera local. Para obtener más información, consulta [Documentación oficial de Jupyter](http://jupyter.readthedocs.io/en/latest/index.html). - -### Solución de problemas - -Si tienes problemas para representar los archivos notebook Jupyter en HTML estático, puedes convertir el archivo de forma local en la línea de comando usando el comando [`nbconvert`](https://github.com/jupyter/nbconvert): - -```shell -$ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb -``` - -### Leer más - -- [Repositorio GitHub de notebook Jupyter](https://github.com/jupyter/jupyter_notebook) -- [Galería de notebooks Jupyter](https://github.com/jupyter/jupyter/wiki/A-gallery-of-interesting-Jupyter-Notebooks) diff --git a/translations/es-XL/content/github/managing-large-files/index.md b/translations/es-XL/content/github/managing-large-files/index.md deleted file mode 100644 index 3680cf2328..0000000000 --- a/translations/es-XL/content/github/managing-large-files/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Administrar archivos grandes -redirect_from: - - /categories/managing-large-files -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -children: - - /working-with-large-files - - /versioning-large-files ---- -### Índice - - - - diff --git a/translations/es-XL/content/github/managing-large-files/versioning-large-files/about-git-large-file-storage.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/about-git-large-file-storage.md deleted file mode 100644 index 25ec393a49..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/about-git-large-file-storage.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Acerca de Large File Storage de Git -intro: '{% data variables.large_files.product_name_short %}te permite subir los archivos que sean más grandes que el límite de subida en Git a {% data variables.product.product_name %}.' -redirect_from: - - /articles/about-large-file-storage/ - - /articles/about-git-large-file-storage - - /github/managing-large-files/about-git-large-file-storage -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -{% data variables.large_files.product_name_short %} maneja archivos grandes almacenando referencias del archivo en el repositorio, pero no el archivo real. Para trabajar en la arquitectura de Git, {% data variables.large_files.product_name_short %} crea un archivo puntero que actúa como una referencia del archivo real (que se almacena en otro lugar). {% data variables.product.product_name %} administra este archivo puntero en tu repositorio. Cuando clonas el repositorio, {% data variables.product.product_name %} usa el archivo puntero como un mapa para ir y buscar el archivo grande por ti. - -{% if currentVersion == "free-pro-team@latest" %} -Con {% data variables.large_files.product_name_short %} puedes subier archivos de hasta: - -| Producto | Tamaño máximo de archivo | -| ------------------------------------------------------ | ------------------------ | -| {% data variables.product.prodname_free_user %} | 2 GB | -| {% data variables.product.prodname_pro %} | 2 GB | -| {% data variables.product.prodname_team %} | 4 GB | -| {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %} - Con {% data variables.large_files.product_name_short %} puedes almacenar archivos de hasta -{% if currentVersion ver_lt "enterprise-server@2.21" %}{% data variables.large_files.max_lfs_size %}{% else %}5 GB{% endif %} en tu repositorio. -{% endif %} - -Tambié puedes usar {% data variables.large_files.product_name_short %} con {% data variables.product.prodname_desktop %}. Para obtener más información acerca de cómo clonar repositorios LFS de Git en {% data variables.product.prodname_desktop %}, consulta "[Cómo clonar un repositorio desde GitHub hasta GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". - -{% data reusables.large_files.can-include-lfs-objects-archives %} - -#### Formato de archivo puntero - -El archivo puntero de {% data variables.large_files.product_name_short %} se ve así: - -``` -version {% data variables.large_files.version_name %} -oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5 -size 84977953 -``` - -Hace un seguimiento de la `version` de {% data variables.large_files.product_name_short %} que estás usando, seguido de un identificador único para el archivo (`oid`). También almacena el `size` del archivo final. - -{% tip %} - -**Sugerencia**: {% data variables.large_files.product_name_short %} no se puede usar con los sitios {% data variables.product.prodname_pages %}. - -{% endtip %} - -### Leer más - -- "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" diff --git a/translations/es-XL/content/github/managing-large-files/versioning-large-files/about-storage-and-bandwidth-usage.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/about-storage-and-bandwidth-usage.md deleted file mode 100644 index d9a12e0ed3..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/about-storage-and-bandwidth-usage.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Acerca del uso de ancho de banda y del almacenamiento -intro: '{% data reusables.large_files.free-storage-bandwidth-amount %}' -redirect_from: - - /articles/billing-plans-for-large-file-storage/ - - /articles/billing-plans-for-git-large-file-storage/ - - /articles/about-storage-and-bandwidth-usage - - /github/managing-large-files/about-storage-and-bandwidth-usage -versions: - free-pro-team: '*' ---- -{% data variables.large_files.product_name_short %} está disponible para cada repositorio en {% data variables.product.product_name %}, ya sea que tu cuenta u organización tenga o no una suscripción paga. - -### Hacer un seguimiento del uso de ancho de banda y del almacenamiento - -Cuando confirmas y subes un cambio a un archivo seguido con {% data variables.large_files.product_name_short %}, se sube una nueva versión del archivo completo y el tamaño total del archivo cuenta para el límite de almacenamiento del propietario del repositorio. Cuando descargas un archivo seguido con {% data variables.large_files.product_name_short %}, el tamaño total del archivo cuenta para el límite de ancho de banda del propietario del repositorio. Las cargas de {% data variables.large_files.product_name_short %} no cuentan para el lpimite de ancho de banda. - -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 currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -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)". -{% endif %} - -{% tip %} - -**Tips**: -- {% data reusables.large_files.owner_quota_only %} -- {% data reusables.large_files.does_not_carry %} - -{% endtip %} - -### Cuota de almacenamiento - -Si utilizas más de {% data variables.large_files.initial_storage_quota %} de almacenamiento sin comprar un paquete de datos, aún puedes clonar repositorios con elementos grandes, pero solo podrás descargar los archivos puntero, y no podrás subir archivos nuevos otra vez. Para obtener más información acerca de los archivos puntero, consulta la sección "[Acerca de{% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)". - -### Cuota de ancho de banda - -Si usas más de {% data variables.large_files.initial_bandwidth_quota %} de ancho de banda por mes sin comprar un paquete de datos, el soporte de {% data variables.large_files.product_name_short %} se desactiva en tu cuenta hasta el próximo mes. - -### Leer más - -- "[Ver tu uso de {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)" -- "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" diff --git a/translations/es-XL/content/github/managing-large-files/versioning-large-files/collaboration-with-git-large-file-storage.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/collaboration-with-git-large-file-storage.md deleted file mode 100644 index ce356bb477..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/collaboration-with-git-large-file-storage.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Colaboración con el almacenamiento de archivos de gran tamaño de Git -intro: 'Con {% data variables.large_files.product_name_short %} habilitado, podrás extraer, modificar y subir archivos de gran tamaño del mismo modo que lo harías con cualquier archivo que administre Git. Sin embargo, un usuario que no tiene {% data variables.large_files.product_name_short %} experimentará un flujo de trabajo diferente.' -redirect_from: - - /articles/collaboration-with-large-file-storage/ - - /articles/collaboration-with-git-large-file-storage - - /github/managing-large-files/collaboration-with-git-large-file-storage -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -Si los colaboradores en tu repositorio no tienen {% data variables.large_files.product_name_short %} instalado, no tendrán acceso al archivo de gran tamaño original. Si intentan clonar tu repositorio, solo extraerán los archivos punteros, y no tendrán acceso a los datos trues. - -{% tip %} - -**Tip:** Te recomendamos configurar lineamientos para los contribuyentes del repositorio, los cuales describan la forma de trabajar con archivos grandes, para todo usuario que no tenga {% data variables.large_files.product_name_short %} habilitado. Por ejemplo, puedes pedirles a los colaboradores que no modifiquen archivos de gran tamaño o que carguen los cambios a un servicio de intercambio de archivos como [Dropbox](http://www.dropbox.com/) o Google Drive. Para obtener más información, consulta "[Establecer pautas para los colaboradores del repositorio](/github/building-a-strong-community/setting-guidelines-for-repository-contributors)". - -{% endtip %} - -### Ver archivos de gran tamaño en solicitudes de extracción - -{% data variables.product.product_name %} no representa {% data variables.large_files.product_name_short %} objectos en solicitudes de extracción. Only the pointer file is shown: - -![Ejemplo de PR para archivos de gran tamaño](/assets/images/help/large_files/large_files_pr.png) - -Para obtener más información acerca de los archivos puntero, consulta la sección "[Acerca de{% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format)". - -Para ver los cambios que se realizaron en los archivos grandes, verifica localmente la solicitud de extracción para revisar la diferencia. Para obtener más información, consulta la sección "[Revisar las solicitudes de extracción localmente](/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally)". - -{% if currentVersion == "free-pro-team@latest" %} - -### Subir archivos de gran tamaño a bifurcaciones - -La subida de archivos de gran tamaño cuenta para el ancho de banda de un repositorio padre y las cuotas de almacenamiento, en lugar de hacerlo para las cuotas del propietario de la bifurcación. - -Puedes subir {% data variables.large_files.product_name_short %} objetos a las bifurcaciones públicas si la red del repositorio ya tiene {% data variables.large_files.product_name_short %} objetos o si tienes acceso de escritura a la raíz de la red del repositorio. - -{% endif %} - -### Leer más - -- "[Duplicar un repositorio con objetos de almacenamiento de gran tamaño de Git](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)" diff --git a/translations/es-XL/content/github/managing-large-files/versioning-large-files/configuring-git-large-file-storage.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/configuring-git-large-file-storage.md deleted file mode 100644 index f45931fca4..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/configuring-git-large-file-storage.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Configurar el almacenamiento de archivos Git de gran tamaño -intro: 'Una vez que {[{% data variables.large_files.product_name_short %} está instalado], (/articles/installing-git-large-file-storage/), deberás asociarlo con un archivo de gran tamaño en tu repositorio.' -redirect_from: - - /articles/configuring-large-file-storage/ - - /articles/configuring-git-large-file-storage - - /github/managing-large-files/configuring-git-large-file-storage -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -Si hay archivos existentes en tu repositorio con los que te gustaría usar {% data variables.product.product_name %}, primero debes eliminarlos del repositorio y luego agregarlas a {% data variables.large_files.product_name_short %} localmente. Para obtener más información, consulta "[Mover un archivo en tu repositorio a {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage)". - -{% data reusables.large_files.resolving-upload-failures %} - -{% if currentVersion != "free-pro-team@latest" %} - -{% tip %} - -**Nota:** Antes de intentar subir un archivo de gran tamaño {% data variables.product.product_name %}, asegúrate de haber habilitado {% data variables.large_files.product_name_short %} en tu aparato. Para obtener más información, consulta "[Configurar almacenamiento de archivos Git de gran tamaño en GitHub Enterprise Server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/)". - -{% endtip %} - -{% endif %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Cambia tu directorio de trabajo actual a un repositorio existente que desees usar con {% data variables.large_files.product_name_short %}. -3. Para asociar un tipo de archivo en tu repositorio con {% data variables.large_files.product_name_short %}, escribe `git {% data variables.large_files.command_name %} track` seguido por el nombre de la extensión de archivo a la que deseas cargar automáticamente {% data variables.large_files.product_name_short %}. - - Por ejemplo, para asociar un archivo _.psd_, escribe el siguiente comando: - ```shell - $ git {% data variables.large_files.command_name %} track "*.psd" - > Adding path *.psd - ``` - Cada tipo de archivo que desees asociar con {% data variables.large_files.product_name_short %} deberá agregarse con `got{% data variables.large_files.command_name %} track`. Este comando enmienda tu archivo *.gitattributes* del repositorio y asocia archivos de gran tamaño {% data variables.large_files.product_name_short %}. - - {% tip %} - - **Sugerencia:** Sugerimos enfáticamente que confirmes el archivo *.gitattributes* local en tu repositorio. Basándose en un archivo global *.gitattributes* asociado con {% data variables.large_files.product_name_short %} puede causar conflictos al contribuir con otros proyectos Git. - - {% endtip %} - -4. Agrega un archivo al repositorio que coincide con la extensión que has asociado: - ```shell - $ git add path/to/file.psd - ``` -5. Confirma el archivo y súbelo a {% data variables.product.product_name %}: - ```shell - $ git commit -m "add file.psd" - $ git push origin master - ``` - Deberías ver información de diagnóstico sobre la carga del archivo: - ```shell - > Sending file.psd - > 44.74 MB / 81.04 MB 55.21 % 14s - > 64.74 MB / 81.04 MB 79.21 % 3s - ``` - -### Leer más - -- "[Colaboración con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -- "[Administrar 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-XL/content/github/managing-large-files/versioning-large-files/index.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/index.md deleted file mode 100644 index 17121dc080..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Control de versiones de archivos grandes -intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' -redirect_from: - - /articles/versioning-large-files -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -children: - - /about-git-large-file-storage - - /installing-git-large-file-storage - - /configuring-git-large-file-storage - - /about-storage-and-bandwidth-usage - - /collaboration-with-git-large-file-storage - - /moving-a-file-in-your-repository-to-git-large-file-storage - - /removing-files-from-git-large-file-storage - - /resolving-git-large-file-storage-upload-failures ---- - diff --git a/translations/es-XL/content/github/managing-large-files/versioning-large-files/installing-git-large-file-storage.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/installing-git-large-file-storage.md deleted file mode 100644 index a7aca828c6..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/installing-git-large-file-storage.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -title: Instalar Git Large File Storage -intro: 'Para utilizar {% data variables.large_files.product_name_short %}, tendrás que descargar e instalar un programa nuevo, además de Git.' -redirect_from: - - /articles/installing-large-file-storage/ - - /articles/installing-git-large-file-storage - - /github/managing-large-files/installing-git-large-file-storage -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -{% mac %} - -1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar). También puedes instalar {% data variables.large_files.product_name_short %} utilizando un administrador de paquete: - - Para utilizar [Homebrew](http://brew.sh/), ejecuta `brew install git-lfs`. - - Para utilizar [MacPorts](https://www.macports.org/), ejecuta `port install git-lfs`. - - Si instalas {% data variables.large_files.product_name_short %} con Homebrew o MacPorts, dirígete al paso seis. - -2. En tu computadora, ubica y descomprime el archivo descargado. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Cambia el directorio de trabajo actual por la carpeta en la que descargaste y descomprimiste el archivo. - ```shell - $ cd ~/Downloads/git-lfs-1.X.X - ``` - {% note %} - - **Nota:** La ruta de archivo que utilices después de `cd` depende de tu sistema operativo, de la versión de Git LFS que descargaste y de dónde guardaste la descarga {% data variables.large_files.product_name_short %}. - - {% endnote %} -4. Para instalar el archivo, ejecuta este comando: - ```shell - $ ./install.sh - > {% data variables.large_files.product_name_short %} initialized. - ``` - {% note %} - - **Nota:** Puede que tengas que usar `sudo ./install.sh` para instalar el archivo. - - {% endnote %} -5. Verifica que la instalación haya sido exitosa: - ```shell - $ git {% data variables.large_files.command_name %} install - > {% data variables.large_files.product_name_short %} initialized. - ``` -6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo. - -{% endmac %} - -{% windows %} - -1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar). - - {% tip %} - - **Sugerencia:** Para obtener más información acerca de otras formas de instalar {% data variables.large_files.product_name_short %} para Windows, consulta esta [Guía de introducción](https://github.com/github/git-lfs#getting-started). - - {% endtip %} -2. En tu computadora, ubica el archivo descargado. -3. Haz doble clic en el archivo llamado *git-lfs-windows-1.X.X.exe*, donde 1.X.X se reemplazará con la versión LFS de Git que descargaste. Cuando abras este archivo, Windows ejecutará un asistente de configuración para instalar {% data variables.large_files.product_name_short %}. -{% data reusables.command_line.open_the_multi_os_terminal %} -5. Verifica que la instalación haya sido exitosa: - ```shell - $ git {% data variables.large_files.command_name %} install - > {% data variables.large_files.product_name_short %} initialized. - ``` -6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo. - -{% endwindows %} - -{% linux %} - -1. Navega hasta [git-lfs.github.com](https://git-lfs.github.com) y haz clic en **Download** (Descargar). - - {% tip %} - - **Sugerencia:** Para obtener más información acerca de otras formas de instalar {% data variables.large_files.product_name_short %} para Linux, consulta esta [Guía de introducción](https://github.com/github/git-lfs#getting-started). - - {% endtip %} -2. En tu computadora, ubica y descomprime el archivo descargado. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Cambia el directorio de trabajo actual por la carpeta en la que descargaste y descomprimiste el archivo. - ```shell - $ cd ~/Downloads/git-lfs-1.X.X - ``` - {% note %} - - **Nota:** La ruta de archivo que utilices después de `cd` depende de tu sistema operativo, de la versión de Git LFS que descargaste y de dónde guardaste la descarga {% data variables.large_files.product_name_short %}. - - {% endnote %} -4. Para instalar el archivo, ejecuta este comando: - ```shell - $ ./install.sh - > {% data variables.large_files.product_name_short %} initialized. - ``` - {% note %} - - **Nota:** Puede que tengas que usar `sudo ./install.sh` para instalar el archivo. - - {% endnote %} -5. Verifica que la instalación haya sido exitosa: - ```shell - $ git {% data variables.large_files.command_name %} install - > {% data variables.large_files.product_name_short %} initialized. - ``` -6. Si no ves un mensaje que indique que `git {% data variables.large_files.command_name %} install` fue exitoso, contáctate con {% data variables.contact.contact_support %}. Asegúrate de incluir el nombre de tu sistema operativo. - -{% endlinux %} - -### Leer más - -- "[Configurar {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)" diff --git a/translations/es-XL/content/github/managing-large-files/versioning-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md deleted file mode 100644 index 54f833713b..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Mover un archivo en tu repositorio a Git Large File Storage -intro: 'Si has configurado {% data variables.large_files.product_name_short %}, y tienes un archivo existente en tu repositorio que debe ser rastreado en {% data variables.large_files.product_name_short %}, debes primero eliminarlo de tu repositorio.' -redirect_from: - - /articles/moving-a-file-in-your-repository-to-git-large-file-storage - - /github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -Después de instalar {% data variables.large_files.product_name_short %} y configurar el rastreo de {% data variables.large_files.product_name_short %}, puedes mover archivos del rastreo habitual de Git hacia {% data variables.large_files.product_name_short %}. Para obtener más información, consulta la sección "[Instalar {% data variables.large_files.product_name_long %}](/github/managing-large-files/installing-git-large-file-storage)" y "[Configurar {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage)". - -{% data reusables.large_files.resolving-upload-failures %} - -{% tip %} - -**Sugerencia:** si te aparece un error "esto excede el límite de tamaño de archivo {% data variables.large_files.product_name_short %} de {% data variables.large_files.max_github_size %}" cuando tratas de subir archivos a Git, puedes utilizar `git lfs migrate` en lugar de `filter branch` o del BFG Repo Cleaner, para mover un archivo grande a {% data variables.large_files.product_name_long %}. Para obtener más información acerca del comando `git lfs migrate`, consulta el anuncio de lanzamiento de [Git LFS 2.2.0](https://github.com/blog/2384-git-lfs-2-2-0-released). - -{% endtip %} - -1. Elimina el archivo del historial del repositorio de Git utilizando el comando `filter-branch` o BFG Repo-Cleaner. Para obtener información detallada sobre sus usos, consulta "[Eliminar datos confidenciales de un repositorio](/articles/removing-sensitive-data-from-a-repository)". -2. Configura el rastreo para tu archivo y súbelo a {% data variables.large_files.product_name_short %}. Para obtener más información sobre este procedimiento, consulta "[Configurar {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)." - -### Leer más - -- "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" -- "[Colaborar con {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" -- "[Instalar {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" diff --git a/translations/es-XL/content/github/managing-large-files/versioning-large-files/removing-files-from-git-large-file-storage.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/removing-files-from-git-large-file-storage.md deleted file mode 100644 index 5f6b77d256..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/removing-files-from-git-large-file-storage.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Removing files from Git Large File Storage -intro: 'If you''ve set up {% data variables.large_files.product_name_short %} for your repository, you can remove all files or a subset of files from {% data variables.large_files.product_name_short %}.' -redirect_from: - - /articles/removing-files-from-git-large-file-storage - - /github/managing-large-files/removing-files-from-git-large-file-storage -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -### Removing a single file - -1. Remove the file from the repository's Git history using either the `filter-branch` command or BFG Repo-Cleaner. For detailed information on using these, see "[Removing sensitive data from a repository](/articles/removing-sensitive-data-from-a-repository)." -2. Navigate to your *.gitattributes* file. - - {% note %} - - **Note:** Your *.gitattributes* file is generally saved within your local repository. In some cases, you may have created a global *.gitattributes* file that contains all of your {% data variables.large_files.product_name_short %} associations. - - {% endnote %} -3. Find and remove the associated {% data variables.large_files.product_name_short %} tracking rule within the *.gitattributes* file. -4. Save and exit the *.gitattributes* file. - -### Removing all files within a {% data variables.large_files.product_name_short %} repository - -1. Remove the files from the repository's Git history using either the `filter-branch` command or BFG Repo-Cleaner. For detailed information on using these, see "[Removing sensitive data from a repository](/articles/removing-sensitive-data-from-a-repository)." -2. Optionally, to uninstall {% data variables.large_files.product_name_short %} in the repository, run: - ```shell - $ git lfs uninstall - ``` - For {% data variables.large_files.product_name_short %} versions below 1.1.0, run: - ```shell - $ git lfs uninit - ``` - -### {% data variables.large_files.product_name_short %} objects in your repository - -After you remove files from {% data variables.large_files.product_name_short %}, the {% data variables.large_files.product_name_short %} objects still exist on the remote storage{% if currentVersion == "free-pro-team@latest" %} and will continue to count toward your {% data variables.large_files.product_name_short %} storage quota{% endif %}. - -To remove {% data variables.large_files.product_name_short %} objects from a repository, {% if currentVersion == "free-pro-team@latest" %}delete and recreate the repository. When you delete a repository, any associated issues, stars, and forks are also deleted. For more information, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)."{% else %}contact your {% data variables.product.prodname_enterprise %} administrator to archive the objects. Archived objects are purged after three months.{% endif %} - -{% note %} - -**Note:** If you removed a single file and have other {% data variables.large_files.product_name_short %} objects that you'd like to keep in your repository, after deleting and recreating your repository, reconfigure your {% data variables.large_files.product_name_short %}-associated files. For more information, see "[Removing a single file](#removing-a-single-file)" and "[Configuring {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage)." - -{% endnote %} - -### Further reading - -- "[About {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" -- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)" -- "[Installing {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" diff --git a/translations/es-XL/content/github/managing-large-files/versioning-large-files/resolving-git-large-file-storage-upload-failures.md b/translations/es-XL/content/github/managing-large-files/versioning-large-files/resolving-git-large-file-storage-upload-failures.md deleted file mode 100644 index a4c5b0f69a..0000000000 --- a/translations/es-XL/content/github/managing-large-files/versioning-large-files/resolving-git-large-file-storage-upload-failures.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Resolver fallas de carga de Git Large File Storage -intro: 'Si tus archivos {% data variables.large_files.product_name_short %} no se cargaron bien, puedes tomar varias medidas para solucionar los problemas de error de carga.' -redirect_from: - - /articles/resolving-git-large-file-storage-upload-failures - - /github/managing-large-files/resolving-git-large-file-storage-upload-failures -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -La {% data variables.large_files.product_name_short %} comprobación de integridad asegura que todos los archivos {% data variables.large_files.product_name_short %} referenciados en una subida se hayan cargado bien. Si la comprobación detecta archivos referenciados que no se cargaron, recibirás un mensaje de error y se bloqueará la subida. - -Para resolver el mensaje de error, debes reinstalar tu cliente local de {% data variables.large_files.product_name_short %} para garantizar que los archivos referenciados de {% data variables.large_files.product_name_short %} pueden subirse adecuadamente en ocasiones posteriores. - -1. Abre Terminal. -2. Reinstala {% data variables.large_files.product_name_short %}. - ```shell - $ git lfs install - ``` -3. Sube todos los archivos referenciados {% data variables.large_files.product_name_short %}. - ```shell - $ git lfs push --all origin - ``` diff --git a/translations/es-XL/content/github/managing-large-files/working-with-large-files/conditions-for-large-files.md b/translations/es-XL/content/github/managing-large-files/working-with-large-files/conditions-for-large-files.md deleted file mode 100644 index f88e386e01..0000000000 --- a/translations/es-XL/content/github/managing-large-files/working-with-large-files/conditions-for-large-files.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Condiciones para archivos de gran tamaño -intro: '{% data variables.product.product_name %} limita el tamaño permitido para los archivos de los repositorios y bloqueará una subida de información si estos superan el tamaño máximo.' -redirect_from: - - /articles/conditions-for-large-files - - /github/managing-large-files/conditions-for-large-files -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -{% data reusables.large_files.use_lfs_tip %} - -### Advertencia para archivos mayores a {% data variables.large_files.warning_size %} - -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 más información, consulta la sección "[Eliminar archivos del historial de un repositorio](/github/managing-large-files/removing-files-from-a-repositorys-history)". - -### Subidas bloquadas para archivos grandes - -{% if currentVersion != "free-pro-team@latest" %}Predeterminadamente, {% endif %}{% data variables.product.product_name %} bloquea las subidas que excedan {% data variables.large_files.max_github_size %}. {% if currentVersion != "free-pro-team@latest" %}Sin embargo, los administradores de sitio pueden configurar un límite diferente para tu instancia de {% data variables.product.prodname_ghe_server %}. 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 %} diff --git a/translations/es-XL/content/github/managing-large-files/working-with-large-files/distributing-large-binaries.md b/translations/es-XL/content/github/managing-large-files/working-with-large-files/distributing-large-binaries.md deleted file mode 100644 index fabf8633d3..0000000000 --- a/translations/es-XL/content/github/managing-large-files/working-with-large-files/distributing-large-binaries.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Distribuir binarios grandes -intro: 'Algunos proyectos requieren la distribución de archivos grandes, como los binarios o instaladores, además de la distribución del código fuente.' -redirect_from: - - /articles/distributing-large-binaries - - /github/managing-large-files/distributing-large-binaries -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -Si necesitas distribuir archivos grandes dentro de tu repositorio, puedes crear lanzamientos en {% data variables.product.product_location %}. Los lanzamientos te permiten empaquetar el software, notas de lanzamiento y enlaces a los archivos binarios para que otras personas puedan utilizarlos. Para obtener más información, consulta la sección "[Acerca de los lanzamientos](/github/administering-a-repository/about-releases)". - -{% if currentVersion == "free-pro-team@latest" %} - -No limitamos el tamaño total de los archivos binarios en los lanzamientos o anchos de banda que se utilizan para entregarlos. Sin embargo, cada archivo individual debe ser menor a {% data variables.large_files.max_lfs_size %}. - -{% endif %} - -{% data reusables.large_files.use_lfs_tip %} diff --git a/translations/es-XL/content/github/managing-large-files/working-with-large-files/index.md b/translations/es-XL/content/github/managing-large-files/working-with-large-files/index.md deleted file mode 100644 index 1523ef101d..0000000000 --- a/translations/es-XL/content/github/managing-large-files/working-with-large-files/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Trabajar con archivos de gran tamaño -intro: 'Un repositorio Git contiene cada versión de cada archivo. Pero para algunos tipos de archivos, esto no es práctico. Las revisiones múltiples de archivos de gran tamaño incrementan los tiempos de clonación y extracción para otros usuarios de un repositorio.' -redirect_from: - - /articles/working-with-large-files -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -children: - - /conditions-for-large-files - - /removing-files-from-a-repositorys-history - - /distributing-large-binaries - - /what-is-my-disk-quota ---- - diff --git a/translations/es-XL/content/github/managing-large-files/working-with-large-files/removing-files-from-a-repositorys-history.md b/translations/es-XL/content/github/managing-large-files/working-with-large-files/removing-files-from-a-repositorys-history.md deleted file mode 100644 index f11f105d92..0000000000 --- a/translations/es-XL/content/github/managing-large-files/working-with-large-files/removing-files-from-a-repositorys-history.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Eliminar archivos del historial de un repositorio -intro: 'Para eliminar un archivo grande de tu repositorio, debes eliminarlo por completo de tu repositorio local y de {% data variables.product.product_location %}.' -redirect_from: - - /articles/removing-files-from-a-repository-s-history - - /articles/removing-files-from-a-repositorys-history - - /github/managing-large-files/removing-files-from-a-repositorys-history -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' ---- -{% warning %} - -**Advertencia**: Estos procedimientos eliminarán archivos de manera permanente del repositorio de tu computadora y de {% data variables.product.product_location %}. Si el archivo es importante, haz una copia de seguridad local en un directorio por fuera del repositorio. - -{% endwarning %} - -### Eliminar un archivo que se añadió en una confirmación de cambios previa - -Si añadiste un archivo en una confirmación previa, necesitas eliminarlo del historial del repositorio. Para eliminar archivos de la historia del repositorio, puedes utilizar BFG Repo-Cleaner o el comando `git filter-branch`. Para obtener más información, consulta la sección "[Eliminar datos sensibles de un repositorio](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)". - -### Eliminar un archivo agregado en la confirmación más reciente no subida - -Si el archivo se agregó con tu confirmación más reciente, y no lo subiste a {% data variables.product.product_location %}, puedes eliminar el archivo y modificar la confirmación: - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.command_line.switching_directories_procedural %} -3. Para eliminar el archivo, ingresa a `git rm --cached`: - ```shell - $ git rm --cached giant_file - # Stage our giant file for removal, but leave it on disk - ``` -4. Confirma este cambio usando `--amend -CHEAD`: - ```shell - $ git commit --amend -CHEAD - # Amend the previous commit with your change - # Simply making a new commit won't work, as you need - # to remove the file from the unpushed history as well - ``` -5. Sube tus confirmaciones a {% data variables.product.product_location %}: - ```shell - $ git push - # Push our rewritten, smaller commit - ``` diff --git a/translations/es-XL/content/github/managing-large-files/working-with-large-files/what-is-my-disk-quota.md b/translations/es-XL/content/github/managing-large-files/working-with-large-files/what-is-my-disk-quota.md deleted file mode 100644 index 69a6eb5664..0000000000 --- a/translations/es-XL/content/github/managing-large-files/working-with-large-files/what-is-my-disk-quota.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: ¿Cuál es mi cuota de disco? -redirect_from: - - /articles/what-is-the-size-limit-for-a-repository/ - - /articles/what-is-my-disk-quota - - /github/managing-large-files/what-is-my-disk-quota -intro: '{% 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.' -versions: - free-pro-team: '*' ---- -{% data reusables.large_files.use_lfs_tip %} - -### Límites de tamaños para 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. - -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. Los archivos individuales en un repositorio se limitan estrictamente a un límite de tamaño máximo de {% data variables.large_files.max_github_size %}. Para obtener más información, consulta "[Trabajar con archivos grandes](/github/managing-large-files/working-with-large-files)." - -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). - -{% note %} - -**Nota:** si agregas un archivo a un repositorio por medio de un navegador, el archivo no puede ser mayor de {% data variables.large_files.max_github_browser_size %}. Para obtener más información, consulta la sección "[Agregar un archivo a un repositorio](/github/managing-files-in-a-repository/adding-a-file-to-a-repository)." - -{% endnote %} - -### Copias de seguridad - -Git no está diseñado para fungir como una herramienta de respaldo. Sin embargo, existen muchas soluciones diseñadas específicamente para realizar respaldos, tales como [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), y [CrashPlan](https://www.crashplan.com/en-us/). - -### Vertederos de base de datos - -Los sistemas de control de versiones, tales como Git, no se diseñan para manejar archivos grandes de SQL. Para compartir bases de datos grandes con otros desarrolladores, te recomendamos utilizar [Dropbox](https://www.dropbox.com/). - -Git no debe utilizarse como respaldo para tus servidores productivos. Para obtener más información, consulta la sección "Respaldos". - -### Dependencias externas - -Las dependencias externas pueden causar que los repositorios de Git se hagan muy grandes. Para evitar llenar un repositorio con dependencias externas, te recomendamos utilizar un administrador de paquetes. Los administradores de paquetes populares para lenguajes (de programación) comunes incluyen a [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), y [Maven](http://maven.apache.org/). Estos administradores de paquetes soportan la utilización directa de repositorios de Git para que no dependas de fuentes pre-empacadas. - -### Versiones de lanzamiento empaquetado - -No recomendamos distribuir código compilado y lanzamientos empaquetados previamente dentro de tu repositorio. Para obtener más información, consulta la sección "[Distribuir archivos binarios grandes](/github/managing-large-files/distributing-large-binaries)". - -### Cambiar el historial de un repositorio existente - -Si ya tienes un repositorio considerablemente grande, puedes reducir su tamaño si eliminas archivos grandes de su historial. Para obtener más información, consulta la sección "[Eliminar archivos del historial de un repositorio](/github/managing-large-files/removing-files-from-a-repositorys-history)". diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/index.md b/translations/es-XL/content/github/managing-security-vulnerabilities/index.md deleted file mode 100644 index dbe4f49f08..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Administrar vulnerabilidades de seguridad -redirect_from: - - /categories/managing-security-vulnerabilities -versions: - ghes: <=2.22 -topics: - - Security -children: - - /managing-vulnerabilities-in-your-projects-dependencies ---- -### Índice - - - - - - diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/about-github-security-advisories.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/about-github-security-advisories.md deleted file mode 100644 index 5cb416d25b..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/about-github-security-advisories.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Acerca de GitHub Security Advisories -intro: 'Puedes usar {% data variables.product.prodname_security_advisories %} para discutir, corregir y publicar información sobre vulnerabilidades de seguridad en tu repositorio.' -redirect_from: - - /articles/about-maintainer-security-advisories - - /github/managing-security-vulnerabilities/about-maintainer-security-advisories - - /github/managing-security-vulnerabilities/about-github-security-advisories -versions: - free-pro-team: '*' ---- -{% data reusables.repositories.security-advisory-admin-permissions %} - -{% data reusables.security-advisory.security-researcher-cannot-create-advisory %} - -### Acerca de {% data variables.product.prodname_security_advisories %} - -{% data variables.product.prodname_security_advisories %} permite a los mantenedores del repositorio discutir en privado y corregir una vulnerabilidad de seguridad en un proyecto. Después de colaborar en una corrección, los mantenedores del repositorio pueden publicar el aviso de seguridad para revelar públicamente la vulnerabilidad de seguridad a la comunidad del proyecto. Al publicar avisos de seguridad, los mantenedores de repositorios facilitan que su comunidad actualice las dependencias de los paquetes e investigue el impacto de las vulnerabilidades de seguridad. - -Con {% data variables.product.prodname_security_advisories %}, puedes: - -1. Crear un borrador de asesoría de seguridad y utilizarlo para debatir de manera privada sobre el impacto de la vulnerabilidad en tu proyecto. -2. Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria. -3. Publicar la asesoría de seguridad para enviar una alerta sobre la vulnerabilidad a tu comunidad. - -{% data reusables.repositories.security-advisories-republishing %} - -Para empezar, ve "[Creando un aviso de seguridad](/github/managing-security-vulnerabilities/creating-a-security-advisory)." - -Puedes dar crédito a los individuos que contribuyeron con una asesoría de seguridad. Para obtener más información, consulta la sección " - -Editar una asesoría de seguridad".

    - -{% data reusables.repositories.security-guidelines %} - -{% data reusables.repositories.github-security-lab %} - - - -### Números de identificación CVE - -Las {% data variables.product.prodname_security_advisories %} se construyen sobre las bases de la lista de Vulnerabilidades y Exposiciones Comunes (CVE, por sus siglas en inglés). {% data variables.product.prodname_dotcom %} es una Autoridad de Numeración de CVE (CNA, por sus siglas en inglés) y está autorizado para asignar números de identificación de CVE. Para obtener más información, consulta las secciones "[Acerca de CVE](https://cve.mitre.org/about/index.html)" y "[Autoridades de Numeración de CVE](https://cve.mitre.org/cve/cna.html)" en el sitio de CVE. - -Cuando creas una asesoría de seguridad para un repositorio público en {% data variables.product.prodname_dotcom %}, tienes la opción de proporcionar un número de identificación de CVE para la vulnerabilidad de seguridad. {% data reusables.repositories.request-security-advisory-cve-id %} - -Una vez que hayas publicado la asesoría de seguridad y que {% data variables.product.prodname_dotcom %} haya asignado un número de identificación CVE a la vulnerabilidad, {% data variables.product.prodname_dotcom %} publicará el CVE a la base de datos de MITRE. Para obtener más información, consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory#requesting-a-cve-identification-number)". - - - -### {% data variables.product.prodname_dependabot_alerts %} para las asesorías de seguridad publicadas - -{% data reusables.repositories.github-reviews-security-advisories %} diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/adding-a-collaborator-to-a-security-advisory.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/adding-a-collaborator-to-a-security-advisory.md deleted file mode 100644 index 18cca92f1d..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/adding-a-collaborator-to-a-security-advisory.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Añadir un colaborador a una asesoría de seguridad -intro: Puedes agregar otros usuarios o equipos para que colaboren contigo en un aviso de seguridad. -redirect_from: - - /articles/adding-a-collaborator-to-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory -versions: - free-pro-team: '*' ---- -Las personas con permisos de administrador en una asesoría de seguridad pueden añadir colaboradores a la misma. - -### Añadir un colaborador a una asesoría de seguridad - -Los colaboradores tienen permisos de escritura para el aviso de seguridad. Para obtener más información, consulte la sección "[Niveles de permiso para las asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)". - -{% note %} - -{% data reusables.repositories.security-advisory-collaborators-public-repositories %}Para encontrar más información acerca de eliminar a un colaborador de una asesoría de seguridad, consulta la sección "[Eliminar a un colaborador de una asesoría de seguridad](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)". - -{% endnote %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. En la lista de "Asesorías de Seguridad", da clic en la asesoría a la cual quieras añadir un colaborador. -5. En la parte derecha de la página, debajo de "Colaboradores", teclea el nombre de usuario o equipo que quieras añadir a la asesoría de seguridad.![Campo para escribir el nombre del equipo o el usuario](/assets/images/help/security/add-collaborator-field.png) -6. Da clic en **Agregar**. ![Botón Add (Agregar)](/assets/images/help/security/security-advisory-add-collaborator-button.png) - -### Leer más - -- "[Niveles de permiso para asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" -- "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)" -- "[Eliminar a un colaborador de una asesoría de seguridad](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)" diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/adding-a-security-policy-to-your-repository.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/adding-a-security-policy-to-your-repository.md deleted file mode 100644 index 8ed92fbbfd..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/adding-a-security-policy-to-your-repository.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Agregar una política de seguridad a tu repositorio -intro: Puedes brindar instrucciones sobre cómo informar responsablemente una vulnerabilidad de seguridad en tu proyecto al agregar una política de seguridad a tu repositorio. -redirect_from: - - /articles/adding-a-security-policy-to-your-repository - - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository -versions: - free-pro-team: '*' ---- -### Acerca de las políticas de seguridad - -Para brindar instrucciones sobre cómo informar responsablemente las vulnerabilidades de seguridad en tu proyecto, puedes agregar un archivo _SECURITY.md_ a la raíz de tu repositorio, `docs`, o carpeta `.github`. Cuando alguien crea una propuesta en tu repositorio, verán un enlace en la política de seguridad de tu proyecto. - -Puedes crear una política de seguridad predeterminada para tu cuenta de usuario o de organización. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)" - -{% tip %} - -**Sugerencia:** Para que las demás personas puedan encontrar tu política de seguridad, puedes vincular tu archivo _SECURITY.md_ desde otros lugares en tu repositorio, como un archivo README. Para obtener más información, consulta "[Acerca de los archivos README](/articles/about-readmes/)". - -{% endtip %} - -Después de que alguien reporte una vulnerabilidad de seguridad en tu proyecto, puedes utilizar {% data variables.product.prodname_security_advisories %} para divulgar, arreglar y publicar información acerca de la misma. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". - -{% data reusables.repositories.github-security-lab %} - -### Agregar una política de seguridad a tu repositorio - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -3. En la barra lateral izquierda, haz clic en **Policy** (Política). ![Pestaña Policy (Política)](/assets/images/help/security/policy-tab.png) -4. Haz clic en **Start setup** (Iniciar configuración). ![Botón Start setup (Iniciar configuración)](/assets/images/help/security/start-setup-policy-button.png) -5. En el archivo _SECURITY.md_ nuevo, agrega información sobre las versiones compatibles de tu proyecto y cómo informar una vulnerabilidad. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} - -### Leer más - -- [Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" -- "[Configurar tu proyecto para contribuciones positivas](/github/building-a-strong-community/setting-up-your-project-for-healthy-contributions)" -- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}) diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md deleted file mode 100644 index 7400c368d6..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad -intro: Puedes crear una bifurcación privada temporal para colaborar de manera privada en la resolución de una vulnerabilidad de seguridad en tu repositorio. -redirect_from: - - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability -versions: - free-pro-team: '*' ---- -### Prerrequisitos - -Antes de que puedas colaborar en una bifurcación privada temporal, debes crear un borrador de asesoría de seguridad. Para obtener más información, consulta la sección "[Crear una asesoría de seguridad](/github/managing-security-vulnerabilities/creating-a-security-advisory)". - -### Crear una bifurcación privada temporal - -Cualquier persona con permisos de administración para un aviso de seguridad puede crear una bifurcación privada temporal. - -Para garantizar la seguridad de la información sobre vulnerabilidades, las integraciones, entre las que se incluye CI, no pueden acceder a las bifurcaciones privadas temporales. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. En la lista de "Asesorías de Seguridad", da clic en aquella en la cual desees crear una bifurcación privada temporal. ![Asesoría de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png) -5. Haz clic en **New temporary private fork** (Nueva bifurcación privada temporal). ![Nuevo botón de bifurcación privada temporal](/assets/images/help/security/new-temporary-private-fork-button.png) - -### Añadir colaboradores a una bifurcación privada temporal - -Cualquiera con permisos de administrador en una asesoría de seguridad puede añadir colaboradores adicionales a la misma, y estos pueden acceder a la bifurcación privada temporal. Para obtener más información, consulta la sección "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)". - -### Agregar cambios a una bifurcación privada temporal - -Cualquier persona con permisos de escritura para un aviso de seguridad puede agregar cambios a una bifurcación privada temporal. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% 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 la lista](/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. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository)" y "[Editar archivos en tu repositorio](/articles/editing-files-in-your-repository)". - - 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 - -Cualquier persona con permisos de escritura para un aviso de seguridad puede crear una solicitud de extracción desde una bifurcación privada temporal. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. En la lista de "Asesorías de Seguridad", da clic sobre aquella en la que desees crear una solicitud de extracción. ![Asesoría de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png) -5. A la derecha del nombre de tu rama, haz clic en **Compare & pull request** (Comparar solicitudes de extracción). ![Botón Compare & pull request (Comparar y solicitud de extracción)](/assets/images/help/security/security-advisory-compare-and-pr.png) -{% data reusables.repositories.pr-title-description %} -{% data reusables.repositories.create-pull-request %} - -{% data reusables.repositories.merge-all-pulls-together %}Para obtener más información, consulta la sección [Fusionar cambios en una asesoría de seguridad](#merging-changes-in-a-security-advisory)". - -### Fusionar cambios en una asesoría de seguridad - -Cualquiera con permisos de administrador en una asesoría de seguridad puede fusionar los cambios en la misma. - -{% data reusables.repositories.merge-all-pulls-together %} - -Antes de que puedas fusionar cambios en una asesoría de seguridad, cada solicitud de extracción abierta en la bifurcación privada temporal debe ser fusionable. No puede haber conflictos de fusión, y se deben cumplir los requisitos de protección de la rama. Para garantizar la seguridad de la información sobre las vulnerabilidades, las verificaciones de estado no ejecutan solicitudes de extracción en bifurcaciones privadas temporales. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". - -{% 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 sobre aquella que tiene los cambios que quieras fusionar. ![Asesoría de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png) -5. Para fusionar todas las solicitudes de extracción abiertas en la bifurcación privada temporal, haz clic en **Merge pull requests** (Fusionar solicitudes de extracción). ![Botón para fusionar solicitud de extracción](/assets/images/help/security/merge-pull-requests-button.png) - -Después de que fusiones cambios en una asesoría de seguridad, puedes publicarla para alertar a tu comunidad sobre las vulnerabilidades de seguridad en versiones previas de tu proyecto. Para obtener más información, consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)". - -### Leer más - -- "[Niveles de permiso para asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" -- "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)" diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/creating-a-security-advisory.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/creating-a-security-advisory.md deleted file mode 100644 index 11747b77ee..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/creating-a-security-advisory.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Crear una asesoría de seguridad -intro: Puedes crear un borrador de asesoría de seguridad para debatir en privado y arreglar una vulnerabilidad de seguridad en tu proyecto de código abierto. -redirect_from: - - /articles/creating-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/creating-a-security-advisory -versions: - free-pro-team: '*' ---- -Cualquier usuario con permisos de administrador puede crear un aviso de seguridad. - -{% data reusables.security-advisory.security-researcher-cannot-create-advisory %} - -### Crear una asesoría de seguridad - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. Da clic en **Nuevo borrador de asesoría de seguridad**. ![Botón Abrir aviso en borrador](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png) -5. Escribe un título para tu aviso de seguridad. ![Campo de título](/assets/images/help/security/security-advisory-title.png) -{% data reusables.repositories.security-advisory-edit-details %} -{% data reusables.repositories.security-advisory-edit-description %} -8. Da clic en **Crear asesoría de seguridad**". ![Botón para crear asesoría de seguridad](/assets/images/help/security/security-advisory-create-security-advisory-button.png) - -### Pasos siguientes - -- Comentar en el borrador de asesoría de seguridad para debatir sobre la vulnerabilidad con tu equipo. -- Añadir colaboradores a la asesoría de seguridad. Para obtener más información, consulta la sección "[Añadir un colaborador a la asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory)". -- Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria. Para obtener más información, consulta "[Colaborar en una bifurcación privada temporaria para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)". -- Agregar individuos que deberían recibir crédito por contribuir con la asesoría de seguridad. Para obtener más información, consulta la sección " -Editar una asesoría de seguridad". - - - Publicar la asesoría de seguridad para notificar a tu comunidad sobre la vulnerabilidad de seguridad en cuestión. Para obtener más información, consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)". diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/editing-a-security-advisory.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/editing-a-security-advisory.md deleted file mode 100644 index 01cae21f73..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/editing-a-security-advisory.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Editar una asesoría de seguridad -intro: Puedes editar los metadatos y la descripción de una asesoría de seguridad si necesitas actualizar los detalles o corregir los errores en la misma. -versions: - free-pro-team: '*' -redirect_from: - - /github/managing-security-vulnerabilities/editing-a-security-advisory ---- -Las personas con permisos de administrador en una asesoría de seguridad pueden editarla. - -### Acerca de los créditos para las asesorías de seguridad - -Puedes dar crédito a las personas que ayudaron a descubrir, reportar, o arreglar una vulnerabilidad de seguridad. Si le das crédito a alguien, ellos pueden elegir aceptarlo o declinarlo. - -Si alguien acepta el crédito, el nombre de usuario de la persona aparecerá en la sección "Créditos" de la asesoría de seguridad. Cualquiera con acceso de lectura al repositorio puede ver la asesoría y las personas que aceptaron el crédito por ella. - -### Editar una asesoría de seguridad - -{% 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 que quieras editar. -5. In the upper-right corner of the details for the security advisory, click -{% octicon "pencil" aria-label="The edit icon" %}. - ![Botón de editar para una asesoría de seguridad](/assets/images/help/security/security-advisory-edit-button.png) -{% data reusables.repositories.security-advisory-edit-details %} -{% data reusables.repositories.security-advisory-edit-description %} -8. 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) -9. Da clic en **Actualizar asesoría de seguridad**". ![Botón Add (Agregar)](/assets/images/help/security/update-advisory-button.png) -10. 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 - -- "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/index.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/index.md deleted file mode 100644 index eb8f26f074..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Administrar las vulnerabilidades de seguridad en tu proyecto -intro: 'Puedes descubrir, discutir, reparar y divulgar vulnerabilidades de seguridad en tus repositorios.' -redirect_from: - - /articles/managing-security-vulnerabilities-in-your-project -versions: - free-pro-team: '*' -children: - - /adding-a-security-policy-to-your-repository - - /about-github-security-advisories - - /permission-levels-for-security-advisories - - /creating-a-security-advisory - - /adding-a-collaborator-to-a-security-advisory - - /removing-a-collaborator-from-a-security-advisory - - /collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /publishing-a-security-advisory - - /editing-a-security-advisory - - /withdrawing-a-security-advisory ---- - diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/permission-levels-for-security-advisories.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/permission-levels-for-security-advisories.md deleted file mode 100644 index f7b05ec683..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/permission-levels-for-security-advisories.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Niveles de permiso para las asesorías de seguridad -intro: Las acciones que puedes tomar en una asesoría de seguridad dependen de si tienes permisos de administrador o de escritura en la misma. -redirect_from: - - /articles/permission-levels-for-maintainer-security-advisories - - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories - - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories -versions: - free-pro-team: '*' ---- -### Resumen de permisos - -{% data reusables.repositories.security-advisory-admin-permissions %} Para obtener más información sobre cómo añadir un colaborador a una asesoría de seguridad, consulta la sección "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)". - -| Acción | Permisos de escritura | Permisos de administrador | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ------------------------- | -| Ver un borrador de asesoría de seguridad | X | X | -| Añadir colaboradores a la asesoría de seguridad (consulta la sección "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)") | | X | -| Editar y borrar cualquier comentario en la asesoría de seguridad | X | X | -| Crear una bifurcación privada temporal en la asesoría de seguridad (consulta la sección "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)) | | X | -| Añadir cambios a una bifurcación privada temporal en la asesoría de seguridad (consulta la sección "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)") | X | X | -| Crear solicitudes de extracción en una bifurcación privada temporaria (consulta "[Colaborar en una bifurcación privada temporaria para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)") | X | X | -| Fusionar cambios en la asesoría de seguridad (consulta la sección "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)") | | X | -| Añadir y editar los metadatos de la asesoría de seguridad (consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)") | X | X | -| Agrega y elimina los créditos para una asesoría de seguridad (consulta "[Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)") | X | X | -| Cerrar el borrador de la asesoría de seguridad | | X | -| Publicar la asesoría de seguridad (consulta la sección "[Publicar una asesoría de seguridad](/github/managing-security-vulnerabilities/publishing-a-security-advisory)") | | X | - -### Leer más - -- "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)" -- "[Colaborar en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)" -- "[Eliminar a un colaborador de una asesoría de seguridad](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)" -- "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/publishing-a-security-advisory.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/publishing-a-security-advisory.md deleted file mode 100644 index 03e5f549d3..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/publishing-a-security-advisory.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Publicar una asesoría de seguridad -intro: Puedes publicar una asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad de seguridad en tu proyecto. -redirect_from: - - /articles/publishing-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory - - /github/managing-security-vulnerabilities/publishing-a-security-advisory -versions: - free-pro-team: '*' ---- -Cualquiera con permisos de administrador en una asesoría de seguridad puede publicarla. - -### Prerrequisitos - -Before you can publish a security advisory or request a CVE identification number, you must create a draft security advisory and provide information about the versions of your project affected by the security vulnerability. Para obtener más información, consulta la sección "[Crear una asesoría de seguridad](/github/managing-security-vulnerabilities/creating-a-security-advisory)". - -Si creaste una asesoría de seguridad pero no has proporcionado detalles sobre las versiones de tu proyecto que afectó la vulnerabilidad, 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)". - -### Acerca de publicar una asesoría de seguridad - -When you publish a security advisory, you notify your community about the security vulnerability that the security advisory addresses. Publishing a security advisory makes it easier for your community to update package dependencies and research the impact of the security vulnerability. - -{% data reusables.repositories.security-advisories-republishing %} - -Before you publish a security advisory, you can privately collaborate to fix the vulnerability in a temporary private fork. Para obtener más información, consulta "[Colaborar en una bifurcación privada temporaria para resolver una vulnerabilidad de seguridad](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)". - -Cuando publicas un borrador de asesoría desde un repositorio público, todos pueden ver: - -- La versión actual de los datos de la asesoría. -- Cualquier asesoría atribuye que los usuarios acreditados han aceptado. - -{% note %} - -**Nota**: El público en general jamás tendrá acceso al historial de ediciones de la asesoría y solo verá la versión publicada. - -{% endnote %} - -Después de que publicas una asesoría de seguridad, la URL de la misa permanecerá tal como antes de publicarla. Cualquiera con acceso de lectura al repositorio puede verla. Los colaboradores de la asesoría de seguridad pueden seguir viendo las conversaciones pasadas, incluyendo el flujo completo de comentarios, en la asesoría de seguridad a menos de que alguien con permisos administrativos elimine al colaborador de la asesoría de seguridad. - -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 - -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. 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 la lista](/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 - -Publishing a security advisory deletes the temporary private fork for the security advisory. - -{% 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 sobre la que quieras publicar. ![Asesoría de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png) -5. En la parte inferior de la página, da clic sobre **Publicar asesoría**. ![Botón para publicar aviso](/assets/images/help/security/publish-advisory-button.png) - -### {% data variables.product.prodname_dependabot_alerts %} para las asesorías de seguridad publicadas - -{% data reusables.repositories.github-reviews-security-advisories %} - -### Leer más - -- "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/removing-a-collaborator-from-a-security-advisory.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/removing-a-collaborator-from-a-security-advisory.md deleted file mode 100644 index 7892bfe70b..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/removing-a-collaborator-from-a-security-advisory.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Eliminar a un colaborador de una asesoría de seguridad -intro: 'Cuando eliminas a un colaborador de una asesoría de seguridad, este pierde el acceso de lectura y escritura en el debate y metadatos de la misma.' -versions: - free-pro-team: '*' -redirect_from: - - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory ---- -Las personas con permisos administrativos en una asesoría de seguridad pueden eliminar a los colaboradores de la misma. - -### Eliminar a un colaborador de una asesoría de seguridad - -{% data reusables.repositories.security-advisory-collaborators-public-repositories %} - -{% 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 sobre aquella en la que quieras eliminar a algún colaborador. ![Asesoría de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png) -5. En el lado derecho de la página, debajo de "Colaboradores", encuentra el nombre del usuario o equipo al que quieres eliminar de la asesoría de seguridad. ![Colaborador de la asesoría de seguridad](/assets/images/help/security/security-advisory-collaborator.png) -6. Al lado del colaborador que deseas eliminar, haz clic en el icono **X**. ![Icono X para eliminar al colaborador de la asesoría de seguridad](/assets/images/help/security/security-advisory-remove-collaborator-x.png) - -### Leer más - -- "[Niveles de permiso para asesorías de seguridad](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" -- "[Añadir un colaborador a una asesoría de seguridad](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)" diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/withdrawing-a-security-advisory.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/withdrawing-a-security-advisory.md deleted file mode 100644 index 271e4f4082..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project/withdrawing-a-security-advisory.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Retirar una asesoría de seguridad -intro: Puedes retirar una asesoría de seguridad que hayas publicado. -versions: - free-pro-team: '*' -redirect_from: - - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory ---- -Si publicas una asesoría de seguridad por error, puedes retirarla contactando a {% data variables.contact.contact_support %}. - -### Leer más - -- [Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory) diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md deleted file mode 100644 index 1e82b4a7c2..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -title: About alerts for vulnerable dependencies -intro: '{% data variables.product.product_name %} sends {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} when we detect vulnerabilities affecting your repository.' -redirect_from: - - /github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies -versions: - ghes: <=2.22 -topics: - - Security ---- -### About vulnerable dependencies - -{% data reusables.repositories.a-vulnerability-is %} - -When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it. - -### Detection of vulnerable dependencies - - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_short %} alerts{% else %}{% data variables.product.product_name %} detects vulnerable dependencies and sends security alerts{% endif %} when: - -{% if currentVersion == "free-pro-team@latest" %} -- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)." -- New vulnerability data from [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database) is processed.{% else %} -- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}."{% endif %} -- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." - -For a list of the ecosystems that {% data variables.product.product_name %} can detect vulnerabilities and dependencies for, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." - -{% note %} - -**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use. - -{% endnote %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" % %} -### {% data variables.product.prodname_dependabot %} alerts for vulnerable dependencies -{% else %} -### Security alerts for vulnerable dependencies -{% endif %} - -{% data reusables.repositories.enable-security-alerts %} - -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects and alerts users to vulnerable dependencies in _public_ repositories by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. - -You can also enable or disable {% data variables.product.prodname_dependabot %} alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)." - -{% data variables.product.product_name %} starts generating the dependency graph immediately and sends alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)." -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a {% data variables.product.prodname_dependabot_short %} alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. {% if currentVersion == "free-pro-team@latest" %}For repositories that have enabled {% data variables.product.prodname_dependabot_security_updates %}, the alert also contains a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)."{% endif %} -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -When {% data variables.product.product_name %} identifies a vulnerable dependency, we send a security alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. -{% endif %} - -{% warning %} - -**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and alert you with our most up-to-date information, we will not be able to catch everything or alert you to known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary. - -{% endwarning %} - -### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} alerts - -You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -We send {% data variables.product.prodname_dependabot_short %} alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository.{% if currentVersion == "free-pro-team@latest" %} You can also enable {% data variables.product.prodname_dependabot_short %} alerts for additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-github-dependabot-alerts)."{% endif %} -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -We send security alerts to people with admin permissions in the affected repositories by default. {% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. -{% endif %} - -### Configuring notifications for {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -By default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability. You can also choose to receive {% data variables.product.prodname_dependabot_alerts %} in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the {% data variables.product.product_name %} user interface. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-dependabot-alerts-notification-options)." -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %} -By default, if your site administrator has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %} by email. You can also choose to receive {% data variables.product.prodname_dependabot_alerts %} in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the {% data variables.product.product_name %} user interface. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-dependabot-alerts-notification-options)." -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion == "enterprise-server@2.21" %} -By default, if your site administrator has configured email for notifications on your instance, you will receive security alerts by email. You can also choose to receive security alerts in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the {% data variables.product.product_name %} user interface. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#security-alert-notification-options)." -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %} -By default, if your site administrator has configured email for notifications on your instance, you will receive security alerts by email. You can also choose to receive security alerts in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the {% data variables.product.product_name %} user interface. For more information, see "[Choosing the delivery method for your notifications -](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)." -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.20" % %} - -{% if currentVersion ver_gt "enterprise-server@2.21" %}Site administrators can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot_short %} alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} - -{% if currentVersion ver_lt "enterprise-server@2.22" %}Site administrators can also enable security alerts without notifications. For more information, see "[Enabling security alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %}{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -### Further reading - -- "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)" -- "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Understanding how {% data variables.product.product_name %} uses and protects your data](/categories/understanding-how-github-uses-and-protects-your-data)"{% endif %} diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md deleted file mode 100644 index b2c6af39f6..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Buscar vulnerabilidades de seguridad en la Base de Datos de Asesorías de GitHub -intro: 'La {% data variables.product.prodname_advisory_database %} te permite buscar vulnerabilidades que afecten proyectos de código abierto, ya sea manualmente o por coincidencia exacta, en {% data variables.product.company_short %}.' -versions: - free-pro-team: '*' -redirect_from: - - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database ---- -### Acerca de las vulnerabilidades de seguridad - -{% data reusables.repositories.a-vulnerability-is %} - -{% data variables.product.product_name %} will send you {% data variables.product.prodname_dependabot_alerts %} if we detect that any of the vulnerabilities from the {% data variables.product.prodname_advisory_database %} affect the packages that your repository depends on. 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)". - -### Acerca de {% data variables.product.prodname_advisory_database %} - -La {% data variables.product.prodname_advisory_database %} contiene una lista selecta de vulnerabilidades de seguridad que se han mapeado para los paquetes que rastrea la gráfica de dependencias de {% data variables.product.company_short %}. {% data reusables.repositories.tracks-vulnerabilities %} - -Cada asesoría de seguridad contiene información acerca de la vulnerabilidad, incluyendo la descripción, severidad, paquete afectado, paquete de ecosistema, versiones afectadas y versiones parchadas, impacto, e información opcional tal como referencias, soluciones alternas, y créditos. Adicionalmente, las asesorías de la Base de Datos Nacional de Vulnerabilidades contiene un enlace al registro de CVE, en donde puedes leer más sobre los detalles de la vulnerabilidad, su puntuación de CVSS y su nivel de severidad cualitativo. Para obtener más información, consulta la "[National Vulnerability Database](https://nvd.nist.gov/)" del Instituto Nacional de Estándares y Tecnología. - -El nivel de gravedad es uno de cuatro niveles posibles definidos en el [Sistema de clasificación de vulnerabilidades comunes (CVSS), Sección 2.12](https://www.first.org/cvss/specification-document): -- Bajo -- Moderado -- Alto -- Crítico - -La {% data variables.product.prodname_advisory_database %} utiliza estándares de CVSS versión 3.0 y los niveles de CVSS descritos anteriormente. {% data variables.product.product_name %} no publica los puntajes de CVSS. - -{% data reusables.repositories.github-security-lab %} - -### Acceder a una asesoría en la {% data variables.product.prodname_advisory_database %} - -1. Navega hasta https://github.com/advisories. -2. Opcionalmente, para filtrar la lista, utiliza cualquiera de los menúes desplegables. ![Filtros desplegables](/assets/images/help/security/advisory-database-dropdown-filters.png) -3. Da clic en cualquier asesoría para ver los detalles. - -{% note %} - -También se puede acceder a la base de datos utilizando la API de GraphQL. Para obtener más información, consulta la sección "[evento de webhook de `security_advisory`](/webhooks/event-payloads/#security_advisory)". - -{% endnote %} - -### Buscar en la {% data variables.product.prodname_advisory_database %} por coincidencia exacta -Puedes buscar coincidencias exactas en la base de datos y utilizar calificadores para reducir tu búsqueda y encontrar asesorías que se crearon en cierta fecha, en un ecosistema específico o en una biblioteca en particular. - -{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} - -{% data reusables.search.date_gt_lt %} - -| Qualifier | Ejemplo | -| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará únicamente asesorías que afecten paquetes NPM. | -| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará únicamente asesorías con nivel de gravedad alto. | -| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará únicamente asesorías que afecten la biblioteca lodash. | -| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) organizará los resultados para mostrar las asesorías más viejas primero. | -| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) organizará los resultados para mostrar las asesorías más nuevas primero. | -| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) organizará los resultados para mostrar aquellos actualizados menos recientemente. | -| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) organizará los resultados para mostrar los aquellos actualizados más recientemente. | -| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará únicamente las asesorías que se han retirado. | -| `created:YYYY-MM-DD` | [**created:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2019-10-31) mostrará únicamente las asesorías creadas en esta fecha. | -| `updated:YYYY-MM-DD` | [**updated:2019-10-31**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2019-10-31) mostrará únicamente asesorías actualizadas en esta fecha. | - -### Leer más - -- [Definición de MITRE de "vulnerabilidad"](https://cve.mitre.org/about/terminology.html#vulnerability) diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/configuring-github-dependabot-security-updates.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/configuring-github-dependabot-security-updates.md deleted file mode 100644 index 221bd0b3fb..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/configuring-github-dependabot-security-updates.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Condigurar las actualizaciones de seguridad del Dependabot de GitHub -intro: 'Puedes utilizar las {% data variables.product.prodname_dependabot_security_updates %} o las solicitudes de extracción manuales para actualizar fácilmente las dependencias vulnerables.' -redirect_from: - - /articles/configuring-automated-security-fixes - - /github/managing-security-vulnerabilities/configuring-automated-security-fixes - - /github/managing-security-vulnerabilities/configuring-automated-security-updates - - /github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates -versions: - free-pro-team: '*' ---- -### Acerca de {% data variables.product.prodname_dependabot_security_updates %} - -El {% data variables.product.prodname_dependabot_short %} monitorea las asesorías de seguridad tales como la {% data variables.product.prodname_advisory_database %} y [WhiteSource](https://www.whitesourcesoftware.com/vulnerability-database), y activa automáticamente una solicitud de extracción cuando detecta que hay una dependencia vulnerable nueva en el gráfico de dependencias de los repositorios. Para obtener más información acerca de la {% data variables.product.prodname_advisory_database %}, consulta la sección "[Acerca de la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#about-the-github-advisory-database)". - -{% data reusables.dependabot.upgrade-dependency-to-minimum-secure-version %} - -El {% data variables.product.prodname_dependabot_short %} incluye un enlace a la solicitud de extracción para la dependencia vulnerable en la alerta. Para obtener más información, consulta las secciones "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" y "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". - -Cada actualización de seguridad contiene todo lo que tienes que revisar y fusionar de manera rápida y segura para una propuesta de corrección en tu proyecto. Esto incluye la información acerca de la vulnerabilidad, como las notas de lanzamiento, las entradas de bitácora de cambios, y los detalles de confirmación. Los detalles sobre qué vulnerabilidad resuelve una solicitud de extracción se encuentran escondidos de todo aquél que no tenga acceso a las alertas de {% data variables.product.prodname_dependabot_short %} para el repositorio. - -Cuando fusionas una solicitud de extracción que contiene una actualización de seguridad, la alerta correspondiente se marca como resuelta para tu repositorio. - -{% note %} - -**Nota:** Las {% data variables.product.prodname_dependabot_security_updates %} solo resuelven vulnerabilidades de seguridad en las dependencias que rastrea tu gráfica de dependencias. Las actualizaciones de seguridad no se crean para resolver vulnerabilidades en registros privados o en paquetes hospedados en repositorios privados. Sin embargo, las dependencias indirectas o transitorias se incluyen si se definen explícitamente en un archivo bloqueado, o en alguno similar. 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)". Adicionalmente, es importante resaltar que las {% data variables.product.prodname_dependabot_security_updates %}crean solicitudes de extracción automáticamente con las correcciones propuestas para los archivos bloqueados para las dependencias que detectan como vulnerables. - -{% endnote %} - -Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice las alertas del {% data variables.product.prodname_dependabot_short %} y la gráfica de dependencias. Puedes inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual o para todos los repositorios que pertenezcan a tu organización o cuenta de usuario. Para obtener más información, consulta la sección "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios](#managing-github-dependabot-security-updates-for-your-repositories)" acontinuación. - -{% data reusables.dependabot.dependabot-tos %} - -### Repositorios compatibles - -{% data variables.product.prodname_dotcom %} habilita las {% data variables.product.prodname_dependabot_security_updates %} automáticamente para cada repositorio que cumpla con estos pre-requisitos. - -{% note %} - -**Note**: You can manually enable {% data variables.product.prodname_dependabot_security_updates %}, even if the repository doesn't meet some of the prerequisites below. For example, you can enable {% data variables.product.prodname_dependabot_security_updates %} on a fork, or for a package manager that isn't directly supported by following the instructions in "[Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories](#managing-github-dependabot-security-updates-for-your-repositories)." - -{% endnote %} - -| Pre-requisito de habilitación automática | Más información | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Que el repositorio no sea una bifrucación | "[Acerca de las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)" | -| Que el repositorio no esté archivado | "[Archivar repositorios](/github/creating-cloning-and-archiving-repositories/archiving-repositories)" | -| Que el repositorio sea público, o que sea privado y hayas habilitado un análisis de solo lectura por {% data variables.product.prodname_dotcom %}, gráfica de dependencias y alertas de vulnerabilidades en la configuración del mismo | "[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)". | -| Que el repositorio contenga un archivo de manifiesto de dependencias de un ecosistema de paquete que sea compatible con {% data variables.product.prodname_dotcom %} | "[Ecosistemas de paquete compatibles](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" | -| Las {% data variables.product.prodname_dependabot_security_updates %} no se han inhabilitado para el repositorio | "[Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tu repositorio](#managing-github-dependabot-security-updates-for-your-repositories)" | -| Que el repositorio no esté utilizando ya una integración para administración de dependencias | "[Acerca de las integraciones](/github/customizing-your-github-workflow/about-integrations)" | - -Si no se habilitan las actualizaciones de seguridad para tu repositorio y no sabes por qué, intenta primero habilitarles de acuerdo con las instrucciones que se encuentran en los procedimientos siguientes. Si las actualizaciones aún no funcionan, puedes [contactar a soporte](https://support.github.com/contact). - -### Acerca de las puntuaciones de compatibilidad - -Las {% data variables.product.prodname_dependabot_security_updates %} también incluyen puntuaciones de compatibilidad para que sepas si el actualizar una vulnerabilidad podría causar cambios sustanciales en tu proyecto. Revisamos las pruebas de IC que pasaron previamente en repositorios públicos en donde generamos alguna actualización de seguridad para aprender si la actualización puede causar que las pruebas fallen. Una puntuación de compatibilidad de la actualización es el porcentaje de ejecuciones de CI que se aprobaron al actualizar entre las versiones relevantes de la dependencia. - -### Administrar las {% data variables.product.prodname_dependabot_security_updates %} para tus repositorios - -Puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual. - -También puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para todos los repositorios que pertenezcan atu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario" o la sección](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)"[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". - -Las {% data variables.product.prodname_dependabot_security_updates %} requieren de configuraciones de repositorio específicas. Para obtener más información, consulta la sección "[Repositorios compatibles](#supported-repositories)". - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. Arriba de la lista de alertas, utiliza el menú desplegable y selecciona o deselecciona **alertas de seguridad del {% data variables.product.prodname_dependabot_short %}**. ![Menú desplegable con la opción de habilitar las {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-drop-down.png) - -### Leer más - -- "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" -- "[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)". -- "[Ecosistemas de paquete compatibles](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/index.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/index.md deleted file mode 100644 index 0a883ebb57..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Administrar vulnerabilidades en las dependencias de tus proyectos -intro: 'Puedes rastrear las dependencias de tus repositorios y recibir alertas de seguridad de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}{% endif %} cuando {% data variables.product.product_name %} detecta dependencias vulnerables.' -redirect_from: - - /articles/updating-your-project-s-dependencies/ - - /articles/updating-your-projects-dependencies/ - - /articles/managing-security-vulnerabilities-in-your-projects-dependencies/ - - /articles/managing-vulnerabilities-in-your-projects-dependencies -versions: - ghes: <=2.22 -topics: - - Security -children: - - /about-alerts-for-vulnerable-dependencies - - /configuring-notifications-for-vulnerable-dependencies ---- - diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md deleted file mode 100644 index d00513f9a8..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: Solucionar problemas en la detección de dependencias vulnerables -intro: 'Si la información de la dependencia que reportó {% data variables.product.product_name %} no es lo que esperabas, hay varios puntos a considerar y varias cosas que puedes revisar.' -versions: - free-pro-team: '*' -redirect_from: - - /github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies ---- -Los resultados de la detección de dependencias que reporta {% data variables.product.product_name %} pueden ser diferentes a aquellos que devuelven otras herramientas. Esto está justificado y es útil el entender cómo {% data variables.product.prodname_dotcom %} determina las dependencias para tu proyecto. - -### ¿Por qué parece que faltan algunas dependencias? - -{% data variables.product.prodname_dotcom %} genera y muestra los datos de las dependencias de forma diferente a otras herramientas. En consecuencia, si has estado utilizando otra herramienta para identificar dependencias, muy probablemente encuentres resultados diferentes. Considera lo sigueinte: - -* {% data variables.product.prodname_advisory_database %} es una de las fuentes de datos que utiliza {% data variables.product.prodname_dotcom %} para identificar las dependencias vulnerables. Es una base de datos de información de vulnerabilidades orgtanizada y gratuita para los ecosistemas de paquetes comunes en {% data variables.product.prodname_dotcom %}. Esta incluye tanto los datos reportados directamente a {% data variables.product.prodname_dotcom %} desde {% data variables.product.prodname_security_advisories %}, así como las fuentes oficiales y las comunitarias. {% data variables.product.prodname_dotcom %} revisa y organiza estos datos para garantizar que la información falsa o inprocesable no se comparta con la comunidad de desarrollo. Para obtener más información, consulta las secciones "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" y [Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". -* La gráfica de dependencias analiza todos los archivos de manifiesto de paquetes conocidos en un repositorio de usuario. Por ejemplo, para npm analizará el archivo _package-lock.json_. Construye una gráfica de todas las dependencias del repositorio y de los dependientes públicos. Esto sucede cuando habilitas la gráfica de dependencias y cuando alguien hace cargas a la rama predeterminada, y esto incluye a las confirmaciones que hacen cambios a un formato de manifiesto compatible. 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)". -* {% data variables.product.prodname_dependabot_short %} escanea cualquier subida a la rama predeterminada que contenga un archivo de manifiesto. Cuando se agrega un registro de vulnerabilidad nuevo, este escanea todos los repositorios existentes y genera una alerta para cada repositorio vulnerable. Las alertas de {% data variables.product.prodname_dependabot_short %} se agregan a nivel del repositorio en vez de crear una alerta por cada vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". -* Las {% data variables.product.prodname_dependabot_security_updates %} se activan cuando recibes una alerta de seguridad sobre una dependencia vulnerable en tu repositorio. {% data variables.product.prodname_dotcom %} crea una solicitud de extracción automáticamente en tu repositorio para mejorar la dependencia vulnerable a la versión segura mínima posible para evitar la vulnerabilidad. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)". - - {% data variables.product.prodname_dependabot_short %} no escanea repositorios con una programación, sino más bien cuando algo cambia. Por ejemplo, se activa un escaneo cuando se agrega una dependencia ({% data variables.product.prodname_dotcom %} verifica esto en cada subida), o cuando se descubre una vulnerabilidad nueva y ésta se agrega en la base de datos de asesorías. - -### ¿Por qué no me llegan alertas de vulnerabilidades de algunos ecosistemas? - -{% data variables.product.prodname_dotcom %} limita su soporte para alertas de vulnerabilidades a un conjunto de ecosistemas donde podemos proporcionar datos procesables de alta calidad. Las vulnerabilidades que se organizan en la {% data variables.product.prodname_advisory_database %}, la gráfica de dependencias, las alertas de {% data variables.product.prodname_dependabot_short %}, y las actualizaciones de seguridad del {% data variables.product.prodname_dependabot_short %} se proporcionan para varios ecosistemas, incluyendo Maven de Java, npm y Yarn de JavaScript, NuGet de .NET, pip de Python, RubyGems de Ruby y Composer de PHP. Seguiremos agregando soporte para más ecosistemas a la larga. Para obtener una vista general de los ecosistemas de paquete que soportamos, consulta la sección "[Acerca del gráfico de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". - -Vale la pena señalar que podrían existir [Asesorías de Seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories) para otros ecosistemas. La información en una asesoría de seguridad la porporcionan los mantenedores de un repositorio específico. Estos datos no se organizan de la misma forma que la información para los ecosistemas compatibles. - -**Verifica**: ¿Acaso la vulnerabilidad que no se detectó aplica a algún ecosistema no compatible? - -### ¿Acaso la gráfica de dependencias solo encuentra depedencias en los manifiestos y lockfiles? - -La gráfica de dependencias incluye información sobre las dependencias, la cual se declara explícitamente en tu ambiente. Esto es, dependencias que se especifican en un manifiesto o en un lockfile. La gráfica de dependencias también incluye dependencias transitivas generalmente, aún cuando no se especifican en un lockfile, mediante la revisión de las dependencias de las dependencias en un archivo de manifiesto. - -Las alertas del {% data variables.product.prodname_dependabot_short %} te asesoran sobre las dependencias que debes actualizar, incluyendo aquellas transitivas en donde la versión se puede determinar desde un manifiesto o lockfile. Las alertas de seguridad de {% data variables.product.prodname_dependabot_short %} solo sugieren un cambio en donde puedan "arreglar" directamente la dependencia, esto es cuando estas son: -* Dependencias directas declaradas explícitamente en un manifiesto o lockfile -* Dependencias transitivas declaradas en un lockfile - -La gráfica de dependencias no incluye las dependencias "sueltas". Las dependencias "sueltas" son archivos individuales que se copian de otra fuernte y se revisan directamente en el repositorio o dentro de un archivo (tal como un archivo ZIP o JAR) en ves de que se referencien en un manifiesto de paquete de administrador o en un lockfile. - -**Verifica**; ¿Acaso no se especifica la vulnerabilidad no detectada para un componente en el manifiesto o lockfile del repositorio? - -### ¿Acaso la gráfica de dependencias detecta dependencias que se especifican utilizando variables? - -La gráfica de dependencias analiza los manifiestos mientras se suben a {% data variables.product.prodname_dotcom %}. Por lo tanto, la gráfica de dependencias no tiene acceso al ambiente de compilación del proyecto, así que no puede resolver variables que se utilizan dentro de los manifiestos. Si utilizas variables dentro de un manifiesto para especificar el nombre, o más comunmente la versión de una dependencia, entonces dicha dependencia no se incluirá en la gráfica de dependencias. - -**Verifica**: ¿Acaso la dependencia faltante se declara en el manifiesto utilizando una variable para su nombre o versión? - -### ¿Existen límites que afecten los datos de la gráfica de dependencias? - -Sí, la gráfica de dependencias tiene dos categorías de límites: - -1. **Límites de procesamiento** - - Estos afectan la gráfica de dependencias que se muestra dentro de {% data variables.product.prodname_dotcom %} y también previenen la creación de alertas del {% data variables.product.prodname_dependabot_short %}. - - 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 alertas de {% data variables.product.prodname_dependabot_short %}. - - Predeterminadamente, {% data variables.product.prodname_dotcom %} no procesará más de 20 manifiestos por repositorio. Las alertas de {% data variables.product.prodname_dependabot_short %} no deben crearse para los manifiestos mas allá de éste límite. Si necesitas incrementar el límite, contacta a {% data variables.contact.contact_support %}. - -2. **Límites de visualización** - - Estos afectan a lo que se muestra en la gráfica de dependencias dentro de {% data variables.product.prodname_dotcom %}. Sin embargo, estos no afectan las alertas del {% data variables.product.prodname_dependabot_short %} que se crean. - - La vista de dependencias de la gráfica de dependencias para un repositorio solo muestra 1000 manifiestos. Habitualmente, esto es tan adecuado como es significativamente más alto que el límite de procesamiento descrito anteriormente. En situaciones en donde le límite de procesamiento es mayor a 100, las alertas del {% data variables.product.prodname_dependabot_short %} se crearán aún para cualquier manifiesto que no se muestre dentro de {% data variables.product.prodname_dotcom %}. - -**Verifica**: ¿La dependencia faltante está en un archivo de manifiesto que tiene más de 0.5 MB, o en un repositorio con una gran cantidad de manifiesto? - -### ¿Acaso el {% data variables.product.prodname_dependabot_short %} genera alertas para vulnerabilidades que se han conocido por muchos años? - -La {% data variables.product.prodname_advisory_database %} se lanzó en noviembre de 2019 e incialmente rellenó la inclusión de vulnerabilidades informáticas para los ecosistemas compatibles, comenzando en 2017. Cuando agregas CVE a la base de datos, priorizamos la organización de CVE nuevos y los CVE que afecten las versiones nuevas del software. - -Alguna información sobre las vulnerabilidades antiguas se encuentra disponible, especialmente en donde estos CVE se diseminan específicamente, sin embargo, algunas vulnerabilidades no se incluyen en la {% data variables.product.prodname_advisory_database %}. Si hay una vulnerabilidad antigua específica la cual necesites incluir en la base de datos, contacta a {% data variables.contact.contact_support %}. - -**Verifica**: ¿Acaso la vulnerabilidad no detectada tiene una fecha depublicación más antigua de 2017 en la Base de Datos de Vulnerabilidades Nacional? - -### Por qué la {% data variables.product.prodname_advisory_database %} utiliza un subconjunto de datos de vulnerabilidades publicados? - -Algunas herramientas de terceros utilizan datos de CVE sin organizar y no las verificó ni filtró un humano. Esto significa que los CVE con errores de etiquetado o de severidad, o con cualquier problema de calidad, causarán alertas más frecuentes, ruidosas y menos útiles. - -Ya que {% data variables.product.prodname_dependabot_short %} utiliza datos organizado en la {% data variables.product.prodname_advisory_database %}, la cantidad de alertas podría ser menor, pero las alertas que sí recibas serán exactas y relevantes. - -### ¿Acaso cada vulnerabilidad de la dependencia genera una alerta separada? - -Cuadno una dependencia tiene vulnerabilidades múltiples, solo se genera una alerta agregada para esta dependencia en vez de una por cada vulnerabilidad. - -Las alertas del {% data variables.product.prodname_dependabot_short %} cuentan en {% data variables.product.prodname_dotcom %} y muestran un total para la cantidad de alertas, es decir, la cantidad de dependencias con vulnerabilidades y no la cantidad de vulnerabilidades. - -![Vista de alertas de {% data variables.product.prodname_dependabot_short %}](/assets/images/help/repository/dependabot-alerts-view.png) - -Cuando das clic para mostrar los detalles de la alerta puedes ver cuántas vulnerabilidades se incluyen en la misma. - -![Vulnerabilidades múltiples para una alerta de {% data variables.product.prodname_dependabot_short %}](/assets/images/help/repository/dependabot-vulnerabilities-number.png) - -**Verifica**: Si hay una discrepancia en la cantidad total que ves, verifica si no estás comparando la cantidad de alertas con la cantidad de vulnerabilidades. - -### Leer más - -- "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" -- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" diff --git a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md b/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md deleted file mode 100644 index fe2b95c0f3..0000000000 --- a/translations/es-XL/content/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Ver y actualizar dependencias vulnerables en tu repositorio -intro: 'Si {% data variables.product.product_name %} descubre una dependencia vulnerable en tu proyecto, podrás verla en la pestaña de alertas del Dependabot de tu repositorio. Posteriormente, podrás actualizar tu proyecto para resolver o descartar la vulnerabilidad.' -redirect_from: - - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository - - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository -permissions: Los administradores de repositorio y propietarios de la organización pueden ver y actualizar las dependencias. -versions: - free-pro-team: '*' ---- -La pestaña de alertas del {% data variables.product.prodname_dependabot %} de tu repositorio lista todas las {% data variables.product.prodname_dependabot_alerts %} abiertas y cerradas, y las {% data variables.product.prodname_dependabot_security_updates %} correspondientes. Puedes clasificar la lista de alertas utilizando el menú desplegable y hacer clic en alertas específicas para obtener más detalles. 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)". - -Puedes habilitar automáticamente las alertas de seguridad para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)". - -### Acerca de las actualizaciones para las dependencias vulnerables en tu repositorio - -{% data variables.product.product_name %} envía {% data variables.product.prodname_dependabot_alerts %} cuando detectamos vulnerabilidades que afectan tu repositorio. Para los repositorios en donde se habilitaron las {% data variables.product.prodname_dependabot_security_updates %}, cuando {% data variables.product.product_name %} detecta una dependencia vulnerable, el {% data variables.product.prodname_dependabot_short %} crea una solicitud de extracción para arreglarla. {% data reusables.dependabot.upgrade-dependency-to-minimum-secure-version %} - -### Ver y actualizar las dependencias vulnerables - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-dependabot-alerts %} -1. Haz clic en la alerta que quieres ver. ![Alerta seleccionada en la lista de alertas](/assets/images/help/graphs/click-alert-in-alerts-list.png) -1. Revisa los detalles de la vulnerabilidad y, en caso de que esté disponible, la solicitud de extracción que contienen la actualización de seguridad automatizada. -1. Opcionalmente, si no existe ya una actualización de {% data variables.product.prodname_dependabot_security_updates %} para la alerta, para crear una solicitud de extracción o para resolver la vulnerabilidad, da clic en **Crear una actualización de eguridad del {% data variables.product.prodname_dependabot_short %}**. ![Crea un botón de actualización de seguridad del {% data variables.product.prodname_dependabot_short %}](/assets/images/help/repository/create-dependabot-security-update-button.png) -1. Cuando estés listo para actualizar tu dependencia y resolver la vulnerabilidad, fusiona la solicitud de extracción. Cada solicitud de extracción que levante el {% data variables.product.prodname_dependabot_short %} incluye información sobre los comandos que puedes utilizar para controlar el {% data variables.product.prodname_dependabot_short %}. Para obtener más información, consulta la sección "[Adminsitrar las solicitudes de extracción para las actualizaciones de las dependencias](/github/administering-a-repository/managing-pull-requests-for-dependency-updates#managing-github-dependabot-pull-requests-with-comment-commands)". -1. Opcionalmente, si se está arreglando la alerta, si es incorrecta o si se ubica en una sección de código sin utilizar, utiliza el menú desplegable de "Descartar" y da clic en una razón para descartar la alerta.![Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"](/assets/images/help/repository/dependabot-alert-dismiss-drop-down.png) - -### Leer más - -- "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" -- "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)" -- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" -- "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/index.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/index.md deleted file mode 100644 index 99c1068946..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Administrar suscripciones y notificaciones en GitHub -redirect_from: - - /categories/76/articles/ - - /categories/notifications/ - - /categories/receiving-notifications-about-activity-on-github -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications -children: - - /setting-up-notifications - - /viewing-and-triaging-notifications - - /managing-subscriptions-for-activity-on-github ---- -### Índice diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/index.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/index.md deleted file mode 100644 index e8a6f09878..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Administrar suscripciones de actividades en GitHub -intro: 'Para mantener notificaciones de flujo de trabajo sostenibles, entender y revisar frecuentemente tus suscripciones.' -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications -children: - - /viewing-your-subscriptions - - /managing-your-subscriptions ---- - diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md deleted file mode 100644 index 52b8aa3ca8..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Administrar tus suscripciones -intro: Hay varias maneras de darte de baja para ayudarte a administrar tus notificaciones de manera eficiente. -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications -redirect_from: - - /github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions ---- -Para ayudarte a entender tus suscripciones y decidir si quieres desuscribirte, consulta la sección "[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)". - -{% note %} - -**Nota:** En vez de desuscribirte, tienes la opción de ignorar un repositorio. Si ignoras un repositorio, no recibirás ninguna notificación. No recomendamos ignorar repositorios ya que no se te notificará si eres mencionado. {% if currentVersion == "free-pro-team@latest" %}Si te encuentras con comportamientos abusivos y deseas ignorar un repositorio, por favor [contacta a Soporte](/contact) para que podamos ayudarte. {% data reusables.policies.abuse %}{% endif %} - -{% endnote %} - -### Elegir cómo darte de baja - -Para dejar de observar (o para desuscribirte de) un repositorio rápidamente, ve a la página de "Repositorios en observación", donde puedes ver todos los repositorios que estás observando. Para obtener más información, consulta la sección "[Dejar de observar un repositorio](#unwatch-a-repository)". - -Para desuscribirte de varias notificaciones al mismo tiempo, puedes hacerlo utilizando tu bandeja de entrada o en la página de suscripciones. Ambas de estas opciones ofrecen más contexto acerca de tus suscripciones que la página de "Repositorios en observación". - -#### Beneficios de darte de baja desde tu bandeja de entrada - -Cuando te desuscribes de las notificaciones en tu bandeja de entrada, tienes varias otras opciones de clasificación y puedes filtrar tus notificaciones con filtros personalizados y tipos de discusión. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". - -#### Beneficios de darte de baja desde la página de suscripciones - -Cuando te desuscribes de las notificaciones en la página de suscripciones, puedes ver más notificaciones a las que estés suscrito y clasificarlas por "Suscrito más recientemente" o "Suscrito más antiguamente". - -La página de suscripciones te muestra todas las notificaciones a las que estás actualmente suscrito, incluyendo aquellas que hayas marcado como **Listas** en tu bandeja de entrada. - -Solo puedes filtrar tus suscripciones por repositorio y por la razón que estás recibiendo la notificación. - -### Darte de baja de las notificaciones en tu bandeja de entrada - -Cuando te desuscribes de las notificaciones en tu bandeja de entrada, desaparecerán automáticamente de ésta. - -{% 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 **seleccionados**{% octicon "triangle-down" aria-label="The down triangle icon" %} para dar clic en **Darse de baja** ![Opción para darse de baja desde la bandeja de entrada principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) - -### Darse de baja de las notificaciones en la página de suscripciones - -{% 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 **Suscripciones**. ![Opciones del menú desplegable "Administrar notificaciones"](/assets/images/help/notifications-v2/manage-notifications-options.png) - -2. Selecciona las notificaciones de las cuales quieres darte de baja. En la esquina superior derecha, da clic en **Darse de baja** ![Página de suscripciones](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png) - -### Dejar de seguir un repositorio - -Cuando dejas de observar un repositorio, de desuscribes de notificaciones futuras del mismo, a menos de que participes en una conversación o te @mencionen. - -{% 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 "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: - - dejar de seguir un repositorio - - únicamente seguir los lanzamientos de un repositorio - - ignorar todas las notificaciones de un repositorio diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md deleted file mode 100644 index f8dd0318d2..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Visualizar tus suscripciones -intro: 'Para entender de dónde están llegando las notificaciones y la cantidad de las mismas, te recomendamos revisarlas frecuentemente, así como los repositorios que sigues de cerca.' -redirect_from: - - /articles/subscribing-to-conversations/ - - /articles/unsubscribing-from-conversations/ - - /articles/subscribing-to-and-unsubscribing-from-notifications - - /articles/listing-the-issues-and-pull-requests-youre-subscribed-to - - /articles/watching-repositories/ - - /articles/unwatching-repositories/ - - /articles/watching-and-unwatching-repositories - - /articles/watching-and-unwatching-releases-for-a-repository - - /articles/watching-and-unwatching-team-discussions - - /articles/listing-watched-repositories/ - - /articles/listing-the-repositories-you-re-watching - - /articles/listing-the-repositories-youre-watching - - /github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications ---- -Recibes notificaciones para tus suscripciones de la actividad reciente en {% data variables.product.product_name %}. Hay muchas razones por las cuales puedes estar suscrito a una conversación. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)". - -Te recomendamos auditar tus suscripciones y desuscribirte de las que no sean necesarias como parte de un flujo de trabajo de notificaciones saludable. Para obtener más información acerca de tus opciones para desuscribirte, consulta la sección "[Administrar suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". - -### Diagnosticar el por qué recibes tantas notificaciones - -Cuando tu bandeja de entrada tiene demasiadas notificaciones como para administrarlas, considera si estás suscrito a más de las que puedas manejar, o cómo puedes cambiar tu configuración de notificaciones para reducir aquellas que ya tienes y ver los tipos de notificaciones que estás recibiendo. Por ejemplo, puedes considerar inhabilitar la configuración para que observes automáticamente todos los repositorios y discusiones de equipo cada que te unas a un equipo o repositorio. - -![Seguimiento automático](/assets/images/help/notifications-v2/automatic-watching-example.png) - -Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)". - -Para ver un resumen de tus suscripciones a repositorios, consulta la sección "[Revisar los repositorios que estás observando](#reviewing-repositories-that-youre-watching)". Muchas personas se olvidan de los repositorios que han marcado para observar. Desde la página de "Repositorios observados" puedes dejar de observar los repositorios rápidamente. Para obtener más información acerca de las formas de desuscribirse, consulta la sección "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". - -### Revisar todas tus suscripciones - -{% data reusables.notifications.access_notifications %} -1. En la barra lateral izquierda, debajo de la lista de repositorios de los cuales recibes notificaciones, utiliza el menú desplegable "Administrar notificaciones" para dar clic en **Suscripciones**. ![Opciones del menú desplegable "Administrar notificaciones"](/assets/images/help/notifications-v2/manage-notifications-options.png) - -2. Utiliza los filtros y organiza para reducir la lista de suscripciones y comenzar a darte de baja de las conversaciones de las cuales ya no quieres recibir notificaciones. - - ![Página de suscripciones](/assets/images/help/notifications-v2/all-subscriptions.png) - -{% tip %} - -**Sugerencias:** -- Para revisar las suscripciones que pudiste haber olvidado, organiza por "suscripciones menos recientes" - -- Para revisar una lista de repositorios de los cuales aún puedes recibir notificaciones, despliega el menú "filtrar por repositorio" para ver el listado. - -{% endtip %} - -### Revisar los repositorios que estás siguiendo de cerca - -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 "Administrar notificaciones"](/assets/images/help/notifications-v2/manage-notifications-options.png) - -3. 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. - - ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications.png) - - {% tip %} - - **Tip:**En vez de seguir un repositorio, considera si deseas seguir únicamente los lanzamientos el mismo, o dejar de seguirlo definitivamente. Cuando dejas de seguir un repositorio, aún se te puede notificar cuando te @mencionan o cuando participas en un hilo. Cuando únicamente sigues de cerca los lanzamientos de un repositorio, solo se te notificará cuando existe un lanzamiento nuevo, cuando participas en un hilo, o cuando se @menciona a tu usuario o alguno de los equipos a los que pertenezcas. - - {% endtip %} - -### Configurar los ajustes de observación para un repositorio individual - -Puedes elegir si quieres observar o dejar de observar un repositorio individual. También puedes elegir que se te notifique únicamente sobre los lanzamientos nuevos o ignorar 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. ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications-v2/watch-repository-options.png) diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md deleted file mode 100644 index 7b3f38f605..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -title: Acerca de las notificaciones -intro: 'Las notificaciones proporcionan actualizaciones sobre las actividades de {% data variables.product.product_name %} a las que te hayas suscrito. Puedes utilizar la bandeja de notificaciones para personalizar, clasificar y administrar tus actualizaciones.' -redirect_from: - - /articles/notifications/ - - /articles/about-notifications - - /github/managing-subscriptions-and-notifications-on-github/about-notifications-beta - - /github/managing-subscriptions-and-notifications-on-github/about-notifications -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications ---- -### Notificaciones y suscripciones - -Puedes elegir recibir actualizaciones continuas sobre actividades específicas en {% data variables.product.product_name %} mediante una suscripción. Las notificaciones son actualizaciones que recibes por alguna actividad específica a la que te hayas suscrito. - -#### Opciones de suscripción - -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 %}. -- Lanzamientos en un repositorio. - -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**. - -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. Por ejemplo, si ya no quieres recibir notificaciones de algún repositorio en particular, puedes dar clic en **Darse de baja**. Para obtener más información, consulta la opción "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". - -#### Suscripciones predeterminadas - -Generalmente, estarás suscrito automática y predeterminadamente a las conversaciones cuando: -- No has inhabilitado el seguimiento automático a través de tu configuración de notificaciones para los repositorios o equipos a los cuales te has unido. Esta configuración está predeterminadamente habilitada. -- Te han asignado a un informe de problemas o solicitud de extracción. -- Has abierto una solicitud de extracción, informe de problemas, o has creado una publicación para que un equipo la debata. -- Has comentado en un hilo. -- Te has suscrito a un hilo manualmente dando clic en **Seguir** o **Suscribirse**. -- Han @mencionado tu nombre de usuario. -- Has cambiado el estado de un hilo, como cuando cierras un informe de problemas o fusionas una solicitud de extracción. -- Se ha @mencionado a algún equipo al que pertenezcas. - -También está predeterminado que sigas automáticamente a todos los repositorios que has creado y sean propiedad de tu cuenta de usuario. - -Para darte de baja de las conversaciones a las cuales estás suscrito automáticamente, puedes cambiar tu configuración de notificaciones o darte de baja directamente o dejar de seguir la actividad de {% data variables.product.product_name %}. Para obtener más información, consulta la opción "[Administrar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". - -### Personalizar notificaciones y suscripciones - -Puedes elegir ver tus notificaciones a través de la bandeja de entrada de notificaciones en [https://github.com/notifications](https://github.com/notifications){% if currentVersion == "free-pro-team@latest" %} y en la app de {% data variables.product.prodname_mobile %}{% endif %}, a través de tu correo electrónico, o en alguna combinación de estas opciones. - -Para personalizar los tipos de actualizaciones que deseas recibir y el lugar a donde quieras que se envíen, modifica tu configuración de notificaciones. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". - -Para poder seguir administrando tus suscripciones, revisa los repositorios que sigues y las suscripciones que tienes y date de baja de aquellos que ya no quieras seguir. Para obtener más información, consulta la sección "[Administrar suscripciones de actividad en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". - -Para personalizar la manera en la que deseas recibir actualizaciones para solicitudes de extracción o informes de problemas específicos, puedes configurar tus preferencias dentro de las mismas. Para obtener más información, consulta la sección "[Categorizar una notificación](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)". - -{% if currentVersion == "free-pro-team@latest" %} -Puedes habilitar las notificaciones de subida de información en la app de {% data variables.product.prodname_mobile %}. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)". -{% endif %} - -### Razones para que recibas notificaciones - -Tu bandeja de entrada se configura con filtros predeterminados que representan las razones más comunes para que la gente necesite dar seguimiento a sus notificaciones. Para obtener más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)". - -Tu bandeja de entrada muestra las `reasons` (razones) para que recibas notificaciones a modo de etiqueta. - -![Etiquetas de razones en la bandeja de entrada](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png) - -Puedes filtrar tu bandeja de entrada por razón por la cual estás suscrito a notificaciones. Por ejemplo, para ver únicamente solicitudes de extracción en donde alguien solicitó tu revisión, puedes utilizar el filtro de búsqueda `review-requested` (revisión solicitada). - -![Filtrar notificaciones por revisión de la razón solicitada](/assets/images/help/notifications-v2/review-requested-reason.png) - -Si configuraste las notificaciones para que se enviaran por correo electrónico y crees que estás recibiendo notificaciones que no te pertenecen, considera dar solución a los problemas especificando el tema en los encabezados de correo electrónico que muestren el receptor al que se pretende llegar. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)". - -### Clasificar las notificaciones de tu bandeja de entrada - -Para administrar tus notificaciones de manera efectiva, puedes clasificar tu bandeja de entrada con opciones para: -- Eliminar una notificación de la bandeja de entrada marcada como **Completada**. Puedes revisar las notificaciones **Completadas** en un mismo lugar dando clic en **Completada** en la barra lateral o utilizando el query `is:done`. -- Marcar la notificación como leída o no leída. -- **Guardar** una notificación para su revisión posterior. Las notificaciones **Guardadas** se resaltan en tu bandeja de entrada. Puedes revisar las notificaciones **Guardadas** en un mismo lugar en la barra lateral si das clic en **Guardadas**" o utilizando el query `is:saved`. -- Darte de baja automáticamente de esta notificación y de las actualizaciones futuras a esta conversación. Darte de baja también elimina la notificación de tu bandeja de entrada. Si te das de baja de una conversación y alguien menciona tu nombre de usuario o el equipo al que perteneces, del cual recibes notificaciones, entonces comenzarás a recibirlas de nuevo para dicha conversación. - -También puedes clasificar varias notificaciones al mismo tiempo desde tu bandeja de entrada. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)". - -### Personalizar tu bandeja de entrada de notificaciones - -Para enfocarte en un grupo de notificaciones en tu bandeja de entrada en {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} o en {% data variables.product.prodname_mobile %}{% endif %}, puedes crear filtros personalizados. Por ejemplo, puedes crear un filtro personalizado para un proyecto de código abierto en el que contribuyes y únicamente ver notificaciones para el repositorio en el que se te mencione. Para recibir más información, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para ver más ejemplos de cómo personalizar tu flujo de trabajo de clasificaciones, consulta la sección "[Personalizar un flujo de trabajo para clasificar tus notificaciones](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)". - -### Política de retención de notificaciones - -Las notificaciones que no se marquen como **Guardadas** se mantendrán por 5 meses. Aquellas marcadas como **Guardadas** se mantendrán por tiempo indefinido. Si tu notificación guardada tiene más de 5 meses y la dejas de guardad, ésta desaparecerá de tu bandeja de entrada en un día. - -### Retroalimentación y soporte - -Si tienes retroalimentación o alguna solicitud de características, utiliza el [formato de retroalimentación para notificaciones](https://support.github.com/contact/feedback?contact%5Bcategory%5D=notifications&contact%5Bsubject%5D=Product+feedback). diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md deleted file mode 100644 index c56356fa3e..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ /dev/null @@ -1,215 +0,0 @@ ---- -title: Configuring notifications -intro: 'Choose the type of activity on {% data variables.product.product_name %} that you want to receive notifications for and how you want these updates delivered.' -redirect_from: - - /articles/about-web-notifications - - /format-of-notification-emails/ - - /articles/configuring-notification-emails/ - - /articles/about-notification-emails/ - - /articles/about-email-notifications - - /articles/accessing-your-notifications - - /articles/configuring-notification-delivery-methods/ - - /articles/managing-notification-delivery-methods/ - - /articles/managing-notification-emails-for-organizations/ - - /articles/choosing-the-delivery-method-for-your-notifications - - /articles/choosing-the-types-of-notifications-you-receive/ - - /github/managing-subscriptions-and-notifications-on-github/configuring-notifications -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications ---- -### Notification delivery options - -You have three basic options for notification delivery: - - the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} - - the notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_name %}{% endif %} - - an email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)." -{% endif %} - -{% data reusables.notifications-v2.tip-for-syncing-email-and-your-inbox-on-github %} - -#### Benefits of the notifications inbox - -The notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.product_name %} notifications flow, including options to: - - Triage multiple notifications at once. - - Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query. - - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query. - - Unsubscribe and remove a notification from your inbox. - - Preview the issue, pull request, or team discussion where the notification originates on {% data variables.product.product_name %} from within the notifications inbox. - - See one of the latest reasons you're receiving a notification from your inbox with a `reasons` label. - - Create custom filters to focus on different notifications when you want. - - Group notifications in your inbox by repository or date to get a quick overview with less context switching - -{% if currentVersion == "free-pro-team@latest" %} -In addition, the notifications inbox on {% data variables.product.prodname_mobile %} allows you to triage notifications in dark mode and receive push notifications for direct mentions. For more information, see "[Enabling push notifications with GitHub for mobile](#enabling-push-notifications-with-github-for-mobile)" or "[GitHub for mobile](/github/getting-started-with-github/github-for-mobile)." -{% endif %} - -#### Benefits of using an email client for notifications - -One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)." - -Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels. - -Email notifications also allow flexibility with the types of notifications you receive and allow you to choose different email addresses for updates. For example, you can send certain notifications for a repository to a verified personal email address. For more information, about your email customization options, see "[Customizing your email notifications](#customizing-your-email-notifications)." - -### About participating and watching notifications - -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. To see repositories that you're watching, see [https://github.com/watching](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)." - -Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox. - -For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %} and {% data variables.product.prodname_mobile %}{% endif %}. - -![Participating and watching notifications options](/assets/images/help/notifications-v2/participating-and-watching-options.png) - -For example: - - If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications. - - If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating". - -If you do not enable watching or participating notifications for web{% if currentVersion == "free-pro-team@latest" %} and mobile{% endif %}, then your notifications inbox will not have any updates. - -### Customizing your email notifications - -After enabling email notifications, {% data variables.product.product_name %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.product.product_name %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only. - -{% data reusables.notifications.outbound_email_tip %} - -{% data reusables.notifications.shared_state %} - -{% if currentVersion == "free-pro-team@latest" %} - -If you're using Gmail, you can click a button beside the notification email to visit the original issue or pull request that generated the notification. - -![Buttons in Gmail](/assets/images/help/notifications/gmail-buttons.png) - -{% endif %} - -Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.product.product_name %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from: - - Comments on issues and pull requests. - - Pull request reviews. - - Pull request pushes. - - Your own updates, such as when you open, comment on, or close an issue or pull request. - -Depending on the organization that owns the repository, you can also send notifications to different email addresses for specific repositories. For example, you can send notifications for a specific public repository to a verified personal email address. Your organization may require the email address to be verified for a specific domain. For more information, see “[Choosing where your organization’s email notifications are sent](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)." - -{% data reusables.notifications-v2.email-notification-caveats %} - -### Filtering email notifications - -Each email notification that {% data variables.product.product_name %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.product_name %} notifications, or certain types of {% data variables.product.product_name %} notifications. - -If you believe you're receiving notifications that don't belong to you, examine the `X-GitHub-Recipient` and `X-GitHub-Recipient-Address` headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user. - -Email notifications from {% data variables.product.product_name %} contain the following header information: - -| Header | Information | -| --- | --- | -| `From` address | This address will always be {% if currentVersion == "free-pro-team@latest" %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | -| `To` field | This field connects directly to the thread. If you reply to the email, you'll add a new comment to the conversation. | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
    • `assign`: You were assigned to an issue or pull request.
    • `author`: You created an issue or pull request.
    • `comment`: You commented on an issue or pull request.
    • `manual`: There was an update to an issue or pull request you manually subscribed to.
    • `mention`: You were mentioned on an issue or pull request.
    • `push`: Someone committed to a pull request you're subscribed to.
    • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
    • `subscribed`: There was an update in a repository you're watching.
    • `team_mention`: A team you belong to was mentioned on an issue or pull request.
    • `your_activity`: You opened, commented on, or closed an issue or pull request.
    | -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" % %} -| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} - -### Choosing your notification settings - -{% data reusables.notifications.access_notifications %} -{% data reusables.notifications-v2.manage-notifications %} -3. On the notifications settings page, choose how you receive notifications when: - - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} options](#github-dependabot-alerts-options)." {% endif %}{% if currentVersion == "enterprise-server@2.21" %} - - There are new security alerts in your repository. For more information, see "[Security alert options](#security-alert-options)." {% endif %} {% if currentVersion == "free-pro-team@latest" %} - - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %} - -### Automatic watching - -By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options. - - ![Automatic watching options](/assets/images/help/notifications-v2/automatic-watching-options.png) - -If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option. - -### Choosing where your organization’s email notifications are sent - -If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address. - -{% data reusables.notifications-v2.email-notification-caveats %} - -{% data reusables.notifications.access_notifications %} -{% data reusables.notifications-v2.manage-notifications %} -3. Under "Default notification email", select the email address you'd like notifications sent to. -![Default notification email address drop-down](/assets/images/help/notifications/notifications_primary_email_for_orgs.png) -4. Click **Save**. - -#### Customizing email routes per organization - -If you are a member of more than one organization, you can configure each one to send notifications to any of{% if currentVersion == "free-pro-team@latest" %} your verified email addresses{% else %} the email addressed you've added to your {% data variables.product.product_name %} account{% endif %}. {% if currentVersion == "free-pro-team@latest" %} For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} - -{% data reusables.notifications.access_notifications %} -{% data reusables.notifications-v2.manage-notifications %} -3. Under "Custom routing," find your organization's name in the list. -![List of organizations and email addresses](/assets/images/help/notifications/notifications_org_emails.png) -4. Click **Edit** next to the email address you want to change. -![Editing an organization's email addresses](/assets/images/help/notifications/notifications_edit_org_emails.png) -5. Select one of your verified email addresses, then click **Save**. -![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -### {% data variables.product.prodname_dependabot_alerts %} options -{% else %} -### Security alert options -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}Choose how you want to receive {% data variables.product.prodname_dependabot_alerts %} for repositories that you are watching. You can receive {% data variables.product.prodname_dependabot_alerts %} in your inbox, as a banner on {% data variables.product.product_name %}, on the command line, through email, or some combination of these options. - -If you want to receive {% data variables.product.prodname_dependabot_alerts %} by email, choose whether you want a weekly email summary of vulnerabilities for up 10 repositories or a new email each time a vulnerability is detected. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% endif %} - -{% if currentVersion == "enterprise-server@2.21" %}Choose how you want to receive security alerts for repositories that you are watching. You can receive security alerts in your inbox, as a banner on {% data variables.product.product_name %}, on the command line, through email, or some combination of these options. - -If you want to receive security alerts by email, choose whether you want a weekly email summary of vulnerabilities for up 10 repositories or a new email each time a vulnerability is detected. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - ![{% data variables.product.prodname_dependabot_short %} alerts options](/assets/images/help/notifications-v2/dependabot-alerts-options.png) -{% else %} - ![Security alerts options](/assets/images/help/notifications-v2/security-alerts-options.png) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - -### {% data variables.product.prodname_actions %} notification options - -Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs. - - ![Notification options for {% data variables.product.prodname_actions %}](/assets/images/help/notifications-v2/github-actions-notification-options.png) - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -### Enabling push notifications with {% data variables.product.prodname_mobile %} - -When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. You can then enable push notifications for direct mentions within the app. - -You can only receive notifications for pushes to repositories on {% data variables.product.prodname_mobile %} at this time. - -#### Enabling push notifications with {% data variables.product.prodname_ios %} - -1. Above "Home", tap your profile photo. -2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}. - ![Settings icon for GitHub for iOS](/assets/images/help/mobile/ios-settings-icon.png) -3. To update your notification settings, tap **Push notifications**. -4. To turn on push notifications for direct mentions, use the **Direct Mentions** toggle. - -#### Enabling push notifications with {% data variables.product.prodname_android %} - -1. Above "Home", tap your profile photo. -2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}. - ![Settings icon for GitHub for Android](/assets/images/help/mobile/android-settings-icon.png) -3. To turn on push notifications for direct mentions, use the **Direct mentions** toggle. -{% endif %} diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/index.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/index.md deleted file mode 100644 index 0b654a1ec5..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Configurar las notificaciones -intro: 'Para mejorar la relevancia de tus notificaciones y simplificar tu flujo de trabajo de clasificación, configura tus notificaciones para que empaten con tus prioridades.' -redirect_from: - - /articles/getting-started-with-notifications -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications -children: - - /about-notifications - - /configuring-notifications ---- - diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md deleted file mode 100644 index ec08cb3ea6..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Personalizar un flujo de trabajo para clasificar tus notificaciones -intro: 'Para crear un flujo de trabajo ideal para clasificar tus notificaciones, puedes adaptar y personalizar estos flujos de trabajo de ejemplo.' -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications -redirect_from: - - /github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications ---- -### Comenzar la clasificación en tu bandeja de entrada - -Antes de que comiences a clasificar tu bandeja de entrada, considera si prefieres encontrar y responder primero a las actualizaciones más importantes o si quieres vaciar tu bandeja de entrada de las actualizaciones que te distraen y que son fáciles de clasificar o de eliminar. - -Puedes decidir utilizar una combinación de ambos acercamientos en varios momentos, dependiendo del volumen de notificaciones que tengas. - -Para encontrar un flujo de trabajo de ejemplo que trata sobre encontrar y responder a las notificaciones más importantes, consulta la sección "[Revisar tus notificaciones con prioridad más alta](#checking-your-highest-notification-priorities)". - -Para encontrar un ejemplo de flujo de trabajo que muestra cómo eliminar las notificaciones que se pueden clasificar o eliminar fácilmente, consulta la sección "[Borrar tus notificaciones menos importantes](#clearing-your-least-important-notifications)". - -### Revisar las notificaciones con prioridades más altas - -Elige qué tipo de notificaciones son más urgentes de revisar y escoge un la hora en la que te sea más conveniente revisarlas. Deberás considerar la pregunta "¿A quién estoy bloqueando?" - -Por ejemplo, puedes elegir revisar tus notificaciones en este orden en la mañana mientras haces la planeación de tu día en general: - - Solicitudes de extracción en donde se solicita tu revisión. (filtra por `reason:review-requested`) - - Eventos en donde se @menciona tu nombre de usuario, también llamadas menciones directas. (filtra por `reason:mention`) - - Eventos en donde se @menciona un equipo del cual eres miembro, también llamadas menciones de equipo. (filtra por `reason:team-mention`) - - Fallos de flujo de trabajo de IC para un repositorio en específico. (filtra por by `reason:ci-activity` y `repo:owner/repo-name` y asegúrate de que habilitaste las notificaciones de IC para fallas en el flujo de trabajo en tu configuración de notificaciones) - - {% tip %} - - **Tip:** Para revisar rápidamente tus prioridades más altas, configura los filtros personalizados de acuerdo con su prioridad de revisión. Para obtener más información, consulta la sección "[Administrar notificación desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#customizing-your-inbox-with-custom-filters)". - - {% endtip %} - -### Dar seguimiento a las actualizaciones de las notificaciones en curso - -Para dar seguimiento a las notificaciones, podrías considerar la pregunta "¿En qué estaba bloqueado y ya no lo estoy?" Elige tus prioridades de notificaciones para seguimiento. Choose your follow-up notification priorities. - -Por ejemplo, puedes decidir dar seguimiento en este orden: - - Los informes de problemas y solicitudes de extracción a los que estás asignado. Inmediatamente cierra cualquier informe de problemas o solicitudes de extracción que puedas y añade actualizaciones. Guarda las notificaciones que desees revisar después conforme lo necesites. - - Revisa las notificaciones en la bandeja de guardados, especialmente las que no leídas. Si el hilo ya no es relevante, desmarca {% octicon "bookmark" aria-label="The bookmark icon" %} para eliminar la notificación de la bandeja de guardados, y márcala como no guardada. - -### Administrar notificaciones de prioridad más baja - -Después de clasificar las notificaciones de prioridad alta, revisa las notificaciones restantes, tales como las de participación. Considera las siguientes preguntas: - - ¿Puedes darte de baja de esta notificación? ¿Se ha completado la notificación y se encuentra lista para marcarse como **Completada**? - {% tip %} - - **Tip:**Cuando te das de baja de una notificación, ya no recibirás nuevas actualizaciones a menos de que comiences a participar en el hilo o que @mencionen a tu usuario o a algún equipo al que pertenezcas. Cuando marcas alguna notificación como **Completada**, esta se elimina de la vista de tu bandeja principal y se puede visualizar con el query `is:read`. Para obtener más información, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)". - - {% endtip %} - - ¿Te gustaría recibir actualizaciones en el futuro cuando este informe de problemas o solicitud de extracción se cierre o se reabra, o cuando se fusione una solicitud de extracción? Para obtener más información sobre estas opciones, consulta la sección [Clasificar solo una notificación](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)". - - ¿Te gustaría evitar el seguir recibiendo notificaciones como esta posteriormente? En ese caso, considera darte de baja. Para obtener más información, consulta la sección "[Administrar suscripciones de actividad en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". - -### Limpiar tus notificaciones menos importantes - -Elige qué tipo de notificaciones son las que puedes clasificar y eliminar de tu bandeja de entrada mas rápida y fácilmente, idealmente, clasificar varias notificaciones al mismo tiempo. - -Por ejemplo, puedes decidir eliminar las notificaciones en este orden: - - Notificaciones de participación en las que te puedes dar de baja. - - Actualizaciones de repositorios que no son relevantes como para continuar con su seguimiento. - -Para obtener más información sobre la administración de notificaciones múltiples en tu bandeja de entrada al mismo tiempo, consulta la sección "[Administrar las notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)". - -También podrías considerar cambiar tus ajustes de notificaciones o desuscribirte de estas actualizaciones si es posible. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" o "[Administrar tus suscripciones para la actividad en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md deleted file mode 100644 index d7d59b5d47..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Ver y clasificar las notificaciones -intro: 'Para optimizar el flujo de trabajo de tus notificaciones, puedes personalizar como las visualizas y clasificas.' -redirect_from: - - /articles/managing-notifications/ - - /articles/managing-your-notifications -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications -children: - - /managing-notifications-from-your-inbox - - /triaging-a-single-notification - - /customizing-a-workflow-for-triaging-your-notifications ---- - diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md deleted file mode 100644 index 3af78d973d..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -title: Administrar las notificaciones en tu bandeja de entrada -intro: 'Utiliza tu bandeja de entrada para clasificar y sincronizar rápidamente tus notificaciones a través de tu correo electrónico {% if currentVersion == "free-pro-team@latest" %} y dispositivos móviles{% endif %}.' -redirect_from: - - /articles/marking-notifications-as-read - - /articles/saving-notifications-for-later - - /github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications ---- -### Acerca de tu bandeja de entrada - -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.notifications-v2.notifications-inbox-required-setting %}Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". -{% endif %} - -Para acceder a tu bandeja de notificaciones, en la esquina superior derecha de cualquier página, da clic en {% octicon "bell" aria-label="The notifications bell" %}. - - ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) - - -Tu bandeja de entrada muestra todas las notificaciones de las cuales aún no te has desuscrito o que no has marcado como **Hecho**. Puedes personalizar tu bandeja de entrada como mejor se acople con tu flujo de trabajo utilizando filtros, visualizando todas las notificaciones o únicamente las que no se han leído, y agrupando tus notificaciones para obtener un resumen rápido. - - ![vista de bandeja de entrada](/assets/images/help/notifications-v2/inbox-view.png) - -Predeterminadamente, tu bandeja de entrada mostrará las notificaciones leídas y no leídas. Para solo ver las no leídas, da clic en **No leídas** o utiliza la consulta `is:unread`. - - ![vista de no leídos en bandeja de entrada](/assets/images/help/notifications-v2/unread-inbox-view.png) - -### Opciones de clasificación - -Tienes varias opciones para clasificar las notificaciones de tu bandeja de entrada. - -| Opción de clasificación | Descripción | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Guardar | Guarda tu notificación para revisarla posteriormente. Para guardar una notificación, da clic en {% octicon "bookmark" aria-label="The bookmark icon" %} al lado derecho de la misma.

    Las notificaciones guardadas se mantienen por tiempo indefinido y puedes verlas si das clic en **Guardadas** en la barra lateral o con el query `is:saved`. Si guardas las notificaciones por más de 5 meses y luego las dejas de guardar, estas desaparecerán de tu bandeja de entrada en un día. | -| Done | Marca una notificación como completada y elimina la notificación de tu bandeja de entrada. Puedes ver todas las notificaciones completadas dando clic en **Completado** dentro de la barra lateral o con el query `is:done`. Las notificaciones marcadas como **Completado** se guardan por 5 meses. | -| Darse de baja | Elimina automáticamente la notificación de tu bandeja de entrada y te da de baja de la conversación hasta que se @mencione a tu usuario o a algún equipo al que pertenezcas, o cuando se te solicite una revisión. | -| Lectura | Marca la notificación como leída. Para ver únicamente las notificaciones leídas en tu bandeja de entrada, utiliza el query `is:read`. Este query no incluirá a las notificaciones marcadas como **Completado**. | -| Sin leer | Mara la notificación como no leída. Para ver únicamente las notificaciones sin leer en tu bandeja de entrada, utiliza el query `is:unread`. | - -Para ver los atajos de teclado disponibles, consulta la sección "[Atajos de Teclado](/github/getting-started-with-github/keyboard-shortcuts#notifications)". - -Antes de escoger una opción de clasificación, puedes prever los detalles de la notificación e investigar. Para obtener más información, consulta la sección "[Clasificar una sola notificación](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)". - -### Clasificar varias notificaciones al mismo tiempo - -Para clasificar varias notificaciones de una sola vez, selecciona las notificaciones relevantes y utiliza el menú desplegable de {% octicon "kebab-horizontal" aria-label="The edit icon" %} para elegir una opción de clasificación. - -![Menú desplegable con opciones de clasificación y notificaciones seleccionadas](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) - -### Filtros de notificación predeterminados - -Predeterminadamente, tu bandeja de entrada tiene filtros para cuando se te asigna, participas en un hilo, se te solicita revisar una solicitud de extracción, o cuando se @menciona a tu usuario directamente o a un equipo del cual eres miembro. - - ![Filtros personalizados predeterminados](/assets/images/help/notifications-v2/default-filters.png) - -### Personalizar tu bandeja de entrada con filtros personalizados - -Puedes agregar hasta 15 de tus filtros personalizados. - -{% data reusables.notifications.access_notifications %} -2. Para abrir la configuración de filtros, en la barra lateral izquierda, a lado de "Filtros", da clic en {% octicon "gear" aria-label="The Gear icon" %}. - - {% tip %} - - **Tip:** Puedes prever rápidamente los resultados del filtro en la bandeja de entrada si creas un query en ella y das clic en **Guardar**, lo cual abrirá la configuración del filtro personalizado. - - {% endtip %} - -3. Añade un nombre para tu filtro y query del mismo. Por ejemplo, para ver únicamente las notificaciones de un repositorio específico, puedes crear un filtro utilizando el query `repo:octocat/open-source-project-name reason:participating`. También puedes añadir emojis con un teclado que los tenga como nativos. Para ver una lista de queries de búsqueda compatibles, consulta la sección "[Queries compatibles para filtros personalizados](#supported-queries-for-custom-filters)". - - ![Ejemplo de filtro personalizado](/assets/images/help/notifications-v2/custom-filter-example.png) - -4. Haz clic en **Create** (crear). - -### Limitaciones de los filtros personalizados - -Los filtros personalizados no son compatibles actualmente con: - - Búsquedas de texto completo en tu bandeja de entrada, incluyendo búsquedas de los títulos de los informes de problemas o solicitudes de extracción. - - Distinción entre los queries de filtro `is:issue`, `is:pr`, y `is:pull-request`. Estos queries darán como resultado tanto informes de verificación como solicitudes de extracción. - - Crear más de 15 filtros personalizados. - - Cambiar los filtros predeterminados o su orden. - -### Queries compatibles para filtros personalizados - -Existen tres tipos de filtros que puedes utilizar: - - Filtrar por repositorio con `repo:` - - Filtrar por tipo de debate con `is:` - - Filtrar por la razón de la notificación con `reason:` - -Para gregar un filtro de `repo:`, debes incluir al dueño del repositorio en la consulta. Por ejemplo, `repo:atom/atom` representa el repositorio de Atom que pertenece a la organización Atom. - -#### Queries de tipo `reason:` compatibles - -Para filtrar las notificaciones de acuerdo con la razón por la cual recibiste una actualización, puedes utilizar la consulta `reason:`. Por ejemplo, para ver las notificaciones cuando se solicita (a ti o a un equipo al que pertenezcas) revisar una solicitud de extracción, utiliza `reason:review-requested`. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)". - -| Consulta | Descripción | -| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `reason:assign` | Cuando hay una actualización en un informe de problemas o solicitud de extracción en los que estés asignado. | -| `reason:author` | Cuando abres una solicitud de extracción o informe de problemas y ésta ha tenido una actualización o comentario nuevo. | -| `reason:comment` | Cuando comentas en un informe de problemas, solicitud de extracción o debate de equipo. | -| `reason:participating` | Cuando comentas en un informe de problemas, solicitud de extracción o debate de equipo en el que te @mencionaron. | -| `reason:invitation` | Cuando se te invita a un equipo, organización o repositorio. | -| `reason:manual` | Cuando das clic en **Suscribirse** en un informe de problemas o solicitud de extracción al que no estuvieras suscrito. | -| `reason:mention` | Cuando te @mencionan directamente. | -| `reason:review-requested` | Cuando se solicita a tu usuario o a algún equipo al que pertenezcas revisar una solicitud de extracción. | -| `reason:security-alert` | Cuando se emite una alerta de seguridad para un repositorio. | -| `reason:state-change` | Cuando el estado de un informe de problemas o solicitud de extracción cambia. Por ejemplo, se cierra un informe de problemas o se fusiona una solicitud de extracción. | -| `reason:team-mention` | Cuando se @menciona a algún equipo al que pertenezcas. | -| `reason:ci-activity` | Cuando un repositorio tiene una actualización de IC, tal como un nuevo estado de ejecución en un flujo de trabajo. | - -#### Queries de tipo `is:` compatibles - -Para filtrar las notificaciones para una actividad específica en {% data variables.product.product_name %}, puedes utililzar la consulta `is`. Por ejemplo, para ver únicamente las actualizaciones de invitación a un repositorio, utiliza `is:repository-invitation`. - -- `is:check-suite` -- `is:commit` -- `is:gist` -- `is:issue-or-pull-request` -- `is:release` -- `is:repository-invitation` -- `is:repository-vulnerability-alert` -- `is:repository-advisory` -- `is:team-discussion` - -También puedes utilizar la consulta `is:` para describir cómo se clasificó la notificación. - -- `is:saved` -- `is:done` -- `is:unread` -- `is:read` diff --git a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification.md b/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification.md deleted file mode 100644 index 3f0b8ba8a9..0000000000 --- a/translations/es-XL/content/github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Clasificar solo una notificación -intro: 'Cuando revisas e investigas solo una notificación, tienes varias opciones de clasificación que se optimizan para la vista detallada de la misma.' -versions: - free-pro-team: '*' - enterprise-server: '>=2.21' - github-ae: '*' -topics: - - Notifications -redirect_from: - - /github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification ---- -### Guardar solo una notificación - -Para guardar una notificación y revisarla más tarde, a la derecha de la misma, da clic en {% octicon "bookmark" aria-label="The bookmark icon" %}. Solo puedes guardar una notificación a la vez. - -Las notificaciones guardadas se mantienen indefinidamente y se pueden ver si das clic en **Guardado** en la barra lateral o con la consulta `is:saved`. Si guardas las notificaciones por más de 5 meses y luego las dejas de guardar, estas desaparecerán de tu bandeja de entrada en un día. - - ![Opción de clasificación en guardados](/assets/images/help/notifications-v2/save-triaging-option.png) - -### Investigar una notificación - -Cuando das clic en una notificación individual de tu bandeja de entrada, se te dirige a la conversación que la provocó. Desde la parte superior de la página, puedes: -- Marcar la notificación individual como completada -- Darte de baja de las notificaciones posteriores -- Marcar la notificación como leída -- Guardar la notificación para después -- Regresar a tu bandeja de notificaciones - -Para obtener más información acerca de tus opciones de clasificación, consulta la sección "[Administrar notificaciones desde tu bandeja de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options)". - -### Personalizar cuándo recibir actualizaciones posteriores para un informe de problemas o solicitud de extracción - -Puedes elegir como quieres recibir las notificaciones posteriores para una solicitud de extracción o informe de problemas. - -1. En la columna derecha del informe de problemas o solicitud de extracción, a un costado de "Notificaciones", da clic en **Personalizar**". - - ![Personalizar opción debajo de "Notificaciones"](/assets/images/help/notifications-v2/customize-notifications-for-specific-thread.png) - -2. Selecciona **Personalizado** y elige cuando quieres recibir una actualización de notificación para este hilo. Por ejemplo, puedes elegir recibir una actualización cuando se fusiona, cierra o reabre la solicitud de extracción. Te suscribirás nuevamente si participas en el hilo, si se @menciona a tu nombre de usuario, o si se @menciona a algún equipo del cual formes parte. - - ![Opciones para personalizar las notificaciones](/assets/images/help/notifications-v2/custom-options-for-customizing-notification-thread-updates.png) - -3. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md deleted file mode 100644 index 126665838e..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/filtering-issues-and-pull-requests.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Filtrar propuestas y solicitudes de extracción -intro: Las propuestas y las solicitudes de extracción vienen con un conjunto de filtros predeterminados que puedes aplicar para organizar tus listas. -redirect_from: - - /articles/filtering-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- - -{% data reusables.search.requested_reviews_search %} - -Puedes filtrar propuestas y solicitudes de extracción para buscar: -- Todas las propuestas y solicitudes de extracción abiertas -- Las propuestas y solicitudes de extracción creadas por ti -- Las propuestas y solicitudes de extracción que se te han asignado -- Las propuestas y solicitudes de extracción en las que eres [**@mencionado**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) - -{% data reusables.cli.filter-issues-and-pull-requests-tip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -3. Haz clic en **Filtros** para elegir el tipo de filtro que te interesa. ![Usar el menú desplegable Filtros](/assets/images/help/issues/issues_filter_dropdown.png) - -### Leer más - -- "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)" -- "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" -- [Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)" -- "[Filtrar solicitudes de extracción por estado de revisión](/articles/filtering-pull-requests-by-review-status)" -- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" -- "[Compartir filtros](/articles/sharing-filters)" -- "[Ver todas tus propuestas y solicitudes de extracción](/articles/viewing-all-of-your-issues-and-pull-requests)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees.md b/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees.md deleted file mode 100644 index 500e8bc1b8..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Filtrar propuestas y solicitudes de extracción por asignatarios -intro: 'Una vez que has [asignado una propuesta o solicitud de extracción a alguien] (/articles/assigning-issues-and-pull-requests-to-other-github-users), puedes buscar elementos que se basan en la persona que se encuentra trabajando en estas.' -redirect_from: - - /articles/filtering-issues-and-pull-requests-by-assignees - - /github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.cli.filter-issues-and-pull-requests-tip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -3. En el ángulo superior derecho, selecciona el menú desplegable Asignatario. -4. El menú desplegable Asignatario menciona a todos los usuarios que tienen acceso de escritura a tu repositorio. Haz clic en el nombre de la persona cuyos elementos asignados deseas ver, o haz clic en **No asignado a nadie** para ver qué propuestas no están asignadas. ![Utilizar la pestaña desplegable Asignatarios](/assets/images/help/issues/issues_assignee_dropdown.png) - -{% tip %} - -Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda, filtros y clasificaciones actuales**. - -{% endtip %} - -### Leer más - -- [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" -- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" -- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" -- "[Compartir filtros](/articles/sharing-filters)" -- "[Ver todas tus propuestas y solicitudes de extracción](/articles/viewing-all-of-your-issues-and-pull-requests)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-labels.md b/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-labels.md deleted file mode 100644 index 5fb920b28c..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-labels.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Filtrar propuestas y solicitudes de extracción por etiquetas -intro: 'Una vez que has [aplicado etiquetas a una propuesta o solicitud de extracción] (/articles/applying-labels-to-issues-and-pull-requests), puedes encontrar elementos basados en sus etiquetas.' -redirect_from: - - /articles/filtering-issues-and-pull-requests-by-labels - - /github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.cli.filter-issues-and-pull-requests-tip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -{% data reusables.project-management.labels %} -4. En la lista de etiquetas, haz clic en una etiqueta para ver las propuestas y solicitudes de extracción a las que se ha aplicado. ![Lista de etiquetas de repositorio](/assets/images/help/issues/labels-page.png) - -{% tip %} - -**Sugerencia:** Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda, filtros y clasificaciones actuales**. - -{% endtip %} - -### Leer más - -- [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" -- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" -- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" -- "[Compartir filtros](/articles/sharing-filters)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-pull-requests-by-review-status.md b/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-pull-requests-by-review-status.md deleted file mode 100644 index 7336864d0b..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/filtering-pull-requests-by-review-status.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Filtrar solicitudes de extracción por estado de revisión -intro: Puedes usar filtros para ver en una lista las solicitudes de extracción por estado de revisión y buscar las solicitudes de extracción que has revisado o que otras personas te han pedido que revises. -redirect_from: - - /articles/filtering-pull-requests-by-review-status - - /github/managing-your-work-on-github/filtering-pull-requests-by-review-status -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Puedes filtrar la lista de solicitudes de extracción de un repositorio para buscar: -- Solicitudes de extracción que no han sido [revisadas](/articles/about-pull-request-reviews) todavía -- Solicitudes de extracción que [requieren una revisión](/articles/about-required-reviews-for-pull-requests) 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 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 %} -{% data reusables.repositories.sidebar-pr %} -3. En el ángulo superior derecho, selecciona el menú desplegable Revisiones. ![Menú desplegable Revisiones en el menú de filtros sobre la lista de solicitudes de extracción](/assets/images/help/pull_requests/reviews-filter-dropdown.png) -4. Elige un filtro para buscar todas las solicitudes de extracción con ese estado de filtro. ![Lista de filtros en el menú desplegable Revisiones](/assets/images/help/pull_requests/pr-review-filters.png) - -### Leer más - -- "[Acerca de las revisiones de solicitudes de extracción](/articles/about-pull-request-reviews)" -- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" -- "[Ver todas tus propuestas y solicitudes de extracción](/articles/viewing-all-of-your-issues-and-pull-requests)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/index.md b/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/index.md deleted file mode 100644 index 0709974eeb..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Buscar información en un repositorio -intro: 'Para buscar información detallada acerca de un repositorio en GitHub, puedes filtrar, clasificar y buscar propuestas y solicitudes de extracción que son relevantes para el repositorio.' -redirect_from: - - /articles/finding-information-in-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /filtering-issues-and-pull-requests-by-assignees - - /filtering-issues-and-pull-requests-by-labels - - /filtering-pull-requests-by-review-status - - /sorting-issues-and-pull-requests - - /using-search-to-filter-issues-and-pull-requests - - /sharing-filters ---- - diff --git a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/sharing-filters.md b/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/sharing-filters.md deleted file mode 100644 index cb8b894e35..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/sharing-filters.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Compartir filtros -intro: 'Cuando filtras o clasificas propuestas y solicitudes de extracción, la URL de tu navegador se actualiza automáticamente para coincidir con la nueva vista.' -redirect_from: - - /articles/sharing-filters - - /github/managing-your-work-on-github/sharing-filters -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Puedes enviar la URL que genera esa propuesta a cualquier usuario, que podrá ver el mismo filtro que tú ves. - -Por ejemplo, si filtras propuestas asignadas a Hubot, y clasificas las propuestas abiertas más antiguas, tu URL se actualizaría a algo similar a esto: - -``` -/issues?q=state:open+type:issue+assignee:hubot+sort:created-asc -``` - -### Leer más - -* [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" -* [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" -* "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/sorting-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/sorting-issues-and-pull-requests.md deleted file mode 100644 index 98e4906bd0..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/sorting-issues-and-pull-requests.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Clasificar propuestas y solicitudes de extracción -intro: Los filtros pueden ser clasificados para ofrecer mejor información durante un período de tiempo específico. -redirect_from: - - /articles/sorting-issues-and-pull-requests - - /github/managing-your-work-on-github/sorting-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Puedes clasificar cualquier vista filtrada por: - -* Las propuestas y solicitudes de extracción creadas más recientemente -* Las propuestas y solicitudes de extracción creadas con mayor antigüedad -* Las propuestas y solicitudes de extracción más comentadas -* Las propuestas y solicitudes de extracción menos comentadas -* Las propuestas y solicitudes de extracción actualizadas más recientemente -* Las propuestas y solicitudes de extracción actualizadas con mayor antigüedad -* La [reacción](/articles/about-conversations-on-github#reacting-to-ideas-in-comments) más agregada en propuestas o solicitudes de extracción - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -3. En el ángulo superior derecho, selecciona el menú desplegable de Clasificación. ![Utilizar la pestaña desplegable de Clasificación](/assets/images/help/issues/issues_sort_dropdown.png) - -Para borrar tu selección de clasificación, haz clic en **Sort** > (Clasificar); **Newest** (Más reciente). - -### Leer más - -* [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" -* "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" -* "[Compartir filtros](/articles/sharing-filters)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md deleted file mode 100644 index 59dd51f37c..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Utilizar búsqueda para filtrar propuestas y solicitudes de extracción -intro: Cada vista de propuestas y solicitudes de extracción viene con una barra de búsqueda para la administración de filtros avanzada. -redirect_from: - - /articles/using-search-to-filter-issues-and-pull-requests - - /github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -La barra de búsqueda de propuestas y solicitudes de extracción te permite definir tus propios filtros personalizados y clasificar por una amplia variedad de criterios. Puedes encontrar la barra de búsqueda en las pestañas **Issues** (Propuestas) y **Pull requests** (Solicitudes de extracción) de cada repositorio y en tus [tableros de Issues (Propuestas) y Pull requests (Solicitudes de extracción)](/articles/viewing-all-of-your-issues-and-pull-requests). - -![La barra de búsqueda de propuestas y solicitudes de extracción](/assets/images/help/issues/issues_search_bar.png) - -{% tip %} - -**Sugerencia:** {% data reusables.search.search_issues_and_pull_requests_shortcut %} - -{% endtip %} - -Con los términos de búsqueda de propuestas y solicitudes de extracción, puedes hacer lo siguiente: - -- Filtrar propuestas y solicitudes de extracción por autor: `state:open type:issue author:octocat` -- Filtrar propuestas y solicitudes de extracción que involucren, aunque no necesariamente [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) (mencionen), determinadas personas: `state:open type:issue involves:octocat` -- Filtrar propuestas y solicitudes de extracción por asignatario: `state:open type:issue assignee:octocat` -- Filtrar propuestas y solicitudes de extracción por etiqueta: `state:open type:issue label:"bug"` - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -Para el caso de informes de problemas, también puedes utilizar la búsqueda para: - -- Filtrar los informes de problemas enlazados a una solicitud de extracción mediante una referencia de cierre: `linked:pr` -{% endif %} - -For pull requests, you can also use search to: -- Filtrar solicitudes de extracción [en borrador](/articles/about-pull-requests#draft-pull-requests): `is:draft` -- Filtrar solicitudes de extracción que aún no hayan sido [revisadas](/articles/about-pull-request-reviews): `state:open type:pr review:none` -- Filtrar solicitudes de extracción que [requieran una revisión](/articles/about-required-reviews-for-pull-requests) antes de que se puedan fusionar: `state:open type:pr review:required` -- 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 extracción por el equipo que se solicita para revisión: `state:open type:pr team-review-requested:github/atom`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- Filtrar por las solicitudes de extracción enlazadas con un informe de problemas que se pudiera cerrar con dicha solicitud: `linked:issue`{% endif %} - -### Leer más - -- "[Buscar propuestas](/articles/searching-issues)" -- [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" -- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" -- "[Compartir filtros](/articles/sharing-filters)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/index.md b/translations/es-XL/content/github/managing-your-work-on-github/index.md deleted file mode 100644 index 852285f878..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/index.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Administrar tu trabajo en GitHub -redirect_from: - - /categories/100/articles/ - - /categories/managing-projects/ - - /categories/managing-projects-on-github/ - - /categories/managing-your-work-on-github -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /managing-your-work-with-issues - - /labeling-issues-and-pull-requests - - /managing-project-boards - - /tracking-the-progress-of-your-work-with-project-boards - - /tracking-the-progress-of-your-work-with-milestones - - /finding-information-in-a-repository - - /finding-information-in-a-repository ---- -### Índice - - - - - - diff --git a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/about-labels.md b/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/about-labels.md deleted file mode 100644 index ae5302cdd6..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/about-labels.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Acerca de las etiquetas -intro: 'Las etiquetas en {% data variables.product.product_name %} te ayudan a organizar y priorizar tu trabajo. Puedes aplicar etiquetas a propuestas y solicitudes de extracción para indicar prioridad, categoría o cualquier otra información que encuentres útil.' -redirect_from: - - /articles/about-labels - - /github/managing-your-work-on-github/about-labels -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Las etiqueta están asociadas al repositorio en el que están creadas. Una vez que existe una etiqueta, puedes usarla en cualquier propuesta o solicitud de extracción dentro de ese repositorio. Para obtener más información, consulta "[Crear una etiqueta](/articles/creating-a-label/)". - -Cualquiera con acceso de lectura a un repositorio puede ver y buscar las etiquetas del repositorio. Para crear, editar, aplicar o eliminar una etiqueta, debes tener acceso de escritura al repositorio. - -### Usar 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: - -| Etiqueta | Descripción | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `error` | Indica un problema inesperado o un comportamiento no intencionado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -| `documentación` | Indica una necesidad de mejoras o adiciones a la documentación{% endif %} -| `duplicado` | Indica propuestas o solicitudes de extracción similares | -| `mejora` | Indica solicitudes de nueva función | -| `primera buena propuesta` | Indica una buena propuesta para los colaboradores por primera vez | -| `se busca ayuda` | Indica que un mantenedor necesita ayuda en una propuesta o solicitud de extracción | -| `no válida` | Indica que una propuesta o solicitud de extracción ya no es relevante | -| `pregunta` | Indica que una propuesta o solicitud de extracción necesita más información | -| `wontfix` | Indica que no continuará el trabajo en una propuesta o solicitud de extracción | - -Las etiquetas predeterminadas se incluyen en todos los repositorios nuevos cuando se crea el repositorio, pero luego puedes editarlas o eliminarlas. Para obtener más información, consulta "[Eliminar una etiqueta](/articles/deleting-a-label/)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -Los propietarios de la organización pueden personalizar las etiquetas predeterminadas para los repositorios de la organización. Para obtener más información, consulta "[Administrar etiquetas predeterminadas para los repositorios en tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)". -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -### Leer más - -- "[Fomentar las contribuciones útiles a tu proyecto con etiquetas](/github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels)" -{% endif %} diff --git a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/applying-labels-to-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/applying-labels-to-issues-and-pull-requests.md deleted file mode 100644 index f8aa0ed4e7..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/applying-labels-to-issues-and-pull-requests.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Aplicar etiquetas para propuestas y solicitudes de extracción -intro: 'En los repositorios en los que tienes acceso de escritura, puedes asignar etiquetas a las propuestas y solicitudes de extracción a modo de ayuda para organizar tus proyectos.' -redirect_from: - - /articles/customizing-issue-labels/ - - /articles/applying-labels-to-issues-and-pull-requests - - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% tip %} - -**Sugerencia:** También puedes aplicar una etiqueta en el menú desplegable Etiquetas dentro de una propuesta o solicitud de extracción. - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -{% data reusables.repositories.select-items-in-issue-or-pr-list %} -4. En el ángulo superior derecho, haz clic en **Label** (Etiqueta), luego comienza a escribir el nombre de una etiqueta existente. Haz clic en el nombre de la etiqueta para asociarla con los elementos seleccionados. ![Desplegable de la asignación de hitos de propuestas](/assets/images/help/issues/issues_applying_labels_dropdown.png) - -### Leer más - -- "[Acerca de las etiquetas](/articles/about-labels)" -- [Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/creating-a-label.md b/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/creating-a-label.md deleted file mode 100644 index ae79c35326..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/creating-a-label.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Crear una etiqueta -intro: 'En los repositorios a los que tienes acceso de escritura, puedes crear etiquetas para organizar las propuestas y solicitudes de extracción.' -redirect_from: - - /articles/creating-and-editing-labels-for-issues-and-pull-requests/ - - /articles/creating-a-label - - /github/managing-your-work-on-github/creating-a-label -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% tip %} - -**Sugerencia:** También puedes crear una etiqueta en el menú desplegable Etiquetas dentro de una propuesta o solicitud de extracción. - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -{% data reusables.project-management.labels %} -4. A la derecha del campo de búsqueda, haz clic en **Nueva etiqueta**. -{% data reusables.project-management.name-label %} -{% data reusables.project-management.label-description %} -{% data reusables.project-management.label-color-randomizer %} -{% data reusables.project-management.create-label %} - -### Leer más - -- "[Acerca de las etiquetas](/articles/about-labels)" -- "[Aplicar etiquetas a las propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests)" -- "[Editar una etiqueta](/articles/editing-a-label)" -- "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -- "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)" -{% endif %} diff --git a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/deleting-a-label.md b/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/deleting-a-label.md deleted file mode 100644 index 860a7be3c3..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/deleting-a-label.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Eliminar una etiqueta -intro: 'En los repositorios en los que tienes acceso de escritura, puedes eliminar una etiqueta si ya no la necesitas para clasificar las propuestas o las solicitudes de extracción.' -redirect_from: - - /articles/deleting-a-label - - /github/managing-your-work-on-github/deleting-a-label -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Al eliminar una etiqueta, esta se quitará de todas las propuestas o solicitudes de extracción en las que se la ha aplicado. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -{% data reusables.project-management.labels %} -{% data reusables.project-management.delete-label %} - -### Leer más - -- "[Aplicar etiquetas a las propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests)" -- "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -- "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)" -{% endif %} diff --git a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/editing-a-label.md b/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/editing-a-label.md deleted file mode 100644 index 469a450a18..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/editing-a-label.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Editar una etiqueta -intro: 'En los repositorios a los que tienes acceso de escritura, puedes editar el nombre, color y descripción de una etiqueta existente.' -redirect_from: - - /articles/editing-a-label - - /github/managing-your-work-on-github/editing-a-label -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -{% data reusables.project-management.labels %} -{% data reusables.project-management.edit-label %} -{% data reusables.project-management.name-label %} -{% data reusables.project-management.label-description %} -{% data reusables.project-management.label-color-randomizer %} -{% data reusables.project-management.save-label %} - -### Leer más - -- "[Acerca de las etiquetas](/articles/about-labels)" -- "[Crear una etiqueta](/articles/creating-a-label)" -- "[Eliminar una etiqueta](/articles/deleting-a-label)" -- "[Aplicar etiquetas a las propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests)" -- "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)"{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -- "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)" -{% endif %} diff --git a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/index.md b/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/index.md deleted file mode 100644 index 09bde48ec2..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/labeling-issues-and-pull-requests/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Etiquetar propuestas y solicitudes de extracción -intro: 'Puedes administrar tu trabajo en {% data variables.product.product_name %} creando etiquetas para clasificar las propuestas y las solicitudes de extracción.' -redirect_from: - - /articles/labeling-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-labels - - /creating-a-label - - /applying-labels-to-issues-and-pull-requests - - /editing-a-label - - /deleting-a-label ---- - diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards.md deleted file mode 100644 index e6327cafeb..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Acerca de automatización de tableros de proyecto -intro: Puedes configurar flujos de trabajo automáticos para mantener el estado de las tarjetas del tablero de proyecto en sincronización con las propuestas y las solicitudes de extracción asociadas. -redirect_from: - - /articles/about-automation-for-project-boards - - /github/managing-your-work-on-github/about-automation-for-project-boards -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.project-management.automate-project-board-permissions %} Para obtener más información, consulta "[Permisos del tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". - -Puedes automatizar acciones en función de los eventos desencadenantes para las columnas del tablero de proyecto. Esto elimina algunas tareas manuales en la administración de un tablero de proyecto. Por ejemplo, puedes configurar una columna "Tareas pendientes", donde cualquier propuesta o solicitud de extracción que agregues a un tablero de proyecto se mueva automáticamente a la columna configurada. Para obtener más información, consulta "[Configurar automatización para tableros de proyecto](/articles/configuring-automation-for-project-boards)". - -{% data reusables.project-management.use-automated-template %} - -{% data reusables.project-management.copy-project-boards %} - -La automatización del tablero de proyecto también puede ayudar a los equipos a desarrollar un entendimiento común del propósito de un tablero de proyecto y del proceso de desarrollo del equipo creando un flujo de trabajo estándar para ciertas acciones. - -{% data reusables.project-management.resync-automation %} - -### Opciones de automatización - -| Columna preestablecida | Opciones de configuración | -| ---------------------- | ------------------------- | -| Tarea pendientes |
    • Mover todas las propuestas agregadas recientemente aquí.
    • Mover todas las solicitudes de extracción agregadas recientemente aquí.
    • Mover todas las propuestas que se volvieron a abrir aquí.
    • Mover todas las solicitudes de extracción que se volvieron a abrir aquí.
    | -| In progress |
    • Mover todas las solicitudes de extracción que se volvieron a abrir recientemente aquí.
    • Mover todas las propuestas que se volvieron a abrir aquí.
    • Mover todas las solicitudes de extracción que se volvieron a abrir aquí.
    • Mover todas las solicitudes de extracción que cumplen con la cantidad mínima de revisiones requeridas de la rama base aquí.
    • Mover todas las solicitudes de extracción que ya no cumplen con la cantidad mínima de revisiones requeridas de la rama base aquí.
    | -| Done |
    • Mover todas las propuestas cerradas aquí.
    • Mover todas las solicitudes de extracción fusionadas aquí.
    • Mover todas las solicitudes de extracción cerradas, sin fusionar aquí.
    | - -### Seguimiento de progreso del proyecto -La automatización del tablero de proyecto permite un seguimiento de progreso por defecto. Las tarjetas en las columnas con "Tareas pendientes", "En progreso", "Hecho" preestablecen el conteo hacia el progreso general del proyecto. {% data reusables.project-management.project-progress-locations %} - -### Leer más -- "[Configurar automatización para tableros de proyecto](/articles/configuring-automation-for-project-boards)"{% if currentVersion == "free-pro-team@latest" %} -- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/about-project-boards.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/about-project-boards.md deleted file mode 100644 index c094c95d13..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/about-project-boards.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Acerca de los tableros de proyecto -intro: 'Los tableros de proyecto en {% data variables.product.product_name %} te ayudan a organizar y priorizar tu trabajo. Puedes crear tableros de proyecto para un trabajo con características específicas, hojas de ruta completas y hasta listas de verificación de lanzamientos. Con los tableros de proyecto, tienes la flexibilidad de crear flujos de trabajo personalizados que se adapten a tus necesidades.' -redirect_from: - - /articles/about-projects/ - - /articles/about-project-boards - - /github/managing-your-work-on-github/about-project-boards -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Los tableros de proyecto están compuestos por propuestas, solicitudes de extracción y notas que se categorizan como tarjetas en columnas a tu elección. Puedes arrastrar y soltar o usar los atajos del teclado para reordenar las tarjetas dentro de una columna, mover tarjetas de columna a columna y cambiar el orden de las columnas. - -Las tarjetas del tablero de proyecto contienen metadatos relevantes para las propuestas y las solicitudes de extracción, como etiquetas, asignatarios, el estado y quién la abrió. {% data reusables.project-management.edit-in-project %} - -También puedes crear notas dentro de las columnas para servir como recordatorios de tarea, referencias a propuestas y solicitudes de extracción desde cualquier repositorio en {% data variables.product.product_name %}, o agregar información relacionada con tu tablero de proyecto. Puedes crear una tarjeta de referencia para otro tablero de proyecto agregando un enlace a una nota. Si la nota no es suficiente para tus necesidades, puedes convertirla en una propuesta. Para obtener más información sobre cómo convertir las notas del tablero de proyecto en propuestas, consulta "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)". - -Tipos de tableros de proyecto: - -- Los **tableros de proyecto propiedad del usuario** pueden contener propuestas y solicitudes de extracción de cualquier repositorio personal. -- Los **tableros de proyecto para toda la organización** pueden contener propuestas y solicitudes de extracción de cualquier repositorio que pertenezca a una organización. {% data reusables.project-management.link-repos-to-project-board %} Para obtener más información, consulta "[Enlazar un repositorio a un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". -- Los **tableros de proyecto para un repositorio** están limitados a las propuestas y las solicitudes de extracción dentro de un único repositorio. También pueden incluir notas que hacen referencia a las propuestas y las solicitudes de extracción en otros repositorios. - -### Crear y ver tableros de proyecto - -Para crear un tablero de proyecto para tu organización, debes ser un miembro de la organización. Los propietarios de la organización y las personas con permisos de administrador para el tablero de proyecto pueden personalizar el acceso al tablero de proyecto. - -Si un tablero de proyecto propiedad de la organización incluye propuestas o solicitudes de extracción de un repositorio del que no tienes permiso para ver, la tarjeta será censurada. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". - -La vista actividad muestra el historial reciente del tablero de proyecto, como las tarjetas que alguien creó o movió entre las columnas. Para acceder a la vista actividad, haz clic en **Menú** y desplázate hacia abajo. - -Para encontrar tarjetas específicas en un tablero de proyecto o para ver un subconjunto de tarjetas, puedes filtrar las tarjetas del tablero de proyecto. Para obtener más información, consulta "[Filtrar tarjetas en un tablero de proyecto](/articles/filtering-cards-on-a-project-board)". - -Para simplificar tu flujo de trabajo y para mantener las tareas completadas al margen de tu tablero de proyecto, puedes archivar tarjetas. Para obtener más información, consulta "[Archivar tarjetas en un tablero de proyecto](/articles/archiving-cards-on-a-project-board)". - -Si has completado todas las tareas de tu tablero de proyecto o ya no necesitas usar tu tablero de proyecto, puedes cerrar el tablero de proyecto. Para obtener más información, consulta "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)". - -También puedes [desactivar tableros de proyecto en un repositorio](/articles/disabling-project-boards-in-a-repository) o [desactivar tableros de proyecto en tu organización](/articles/disabling-project-boards-in-your-organization), si prefieres hacer un seguimiento de tu trabajo de manera diferente. - -{% data reusables.project-management.project-board-import-with-api %} - -### Plantillas para tableros de proyecto - -Puedes usar plantillas para configurar de forma rápida un nuevo tablero de proyecto. Cuando usas una plantilla para crear un tablero de proyecto, tu nuevo tablero incluirá columnas, así como tarjetas con sugerencias para usar los tableros de proyecto. También puedes elegir una plantilla con la automatización ya configurada. - -| Plantilla | Descripción | -| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Kanban básico | Hace un seguimiento de tus tareas con las columnas Tareas pendientes, En progreso y Hecho | -| Kanban automatizado | Las tarjetas se mueven automáticamente entre las columnas Tareas pendientes, En progreso y Hecho | -| Kanba automatizado con revisión | Las tarjetas se mueven automáticamente entre las columnas Tareas pendientes, En progreso y Hecho, con disparos adicionales para el estado de la revisión de solicitud de extracción | -| Evaluación de error | Evalúa y prioriza errores con las columnas Tareas pendientes, Prioridad alta, Prioridad baja y Cerrado | - -Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards)". - -![Tablero de proyecto con plantilla de kanban básico](/assets/images/help/projects/project-board-basic-kanban-template.png) - -{% data reusables.project-management.copy-project-boards %} - -### Leer más - -- "[Crear un tablero de proyecto](/articles/creating-a-project-board)" -- "[Editar un tablero de proyecto](/articles/editing-a-project-board)"{% if currentVersion == "free-pro-team@latest" %} -- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} -- "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" -- "[Atajos del teclado](/articles/keyboard-shortcuts/#project-boards)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility.md deleted file mode 100644 index da05693521..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Cambiar la visibilidad del tablero de proyecto -intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes hacer que un tablero de proyecto sea público o privado.' -redirect_from: - - /articles/changing-project-board-visibility - - /github/managing-your-work-on-github/changing-project-board-visibility -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.project-management.project-board-visibility %} - -{% tip %} - -**Sugerencia:** Al hacer público tu tablero de proyecto, los miembros de la organización cuentan con acceso de lectura de manera predeterminada. Puedes brindar a los miembros de la organización permisos de escritura o administración específicos al brindar acceso al tablero de proyecto a los equipos en los que están y al agregarlos en un tablero de proyecto como colaboradores. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". - -{% endtip %} - -1. Dirígete al tablero de proyecto que deseas jacer público o privado. -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -4. En "Visibility" (Visibilidad), selecciona **Public** (Público) o **Private** (Privado). Luego, haz clic en **Save** (Guardar). ![Botones de opción público y privado](/assets/images/help/projects/project-board-visibility-options.png) diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/closing-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/closing-a-project-board.md deleted file mode 100644 index 1af49525d5..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/closing-a-project-board.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Cerrar un tablero de proyecto -intro: 'Si has completado todas las tareas de tu tablero de proyecto o ya no necesitas usar un tablero de proyecto, puedes cerrarlo.' -redirect_from: - - /articles/closing-a-project/ - - /articles/closing-a-project-board - - /github/managing-your-work-on-github/closing-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Cuando cierras un tablero de proyecto, todas las automatizaciones del flujo de trabajo configuradas se pausarán por defecto. - -Si vuelves a abrir un tablero de proyecto, tienes la opción de *sincronizar* la automatización, lo que actualiza la posición de las tarjetas en el tablero de acuerdo con los parámetros de automatización configurados para el tablero. Para obtener más información, consulta "[Volver a abrir un tablero de proyecto cerrado](/articles/reopening-a-closed-project-board)" o "[Acerca de la automatización de los tableros de proyectos](/articles/about-automation-for-project-boards)". - -1. Navega hasta la lista de tableros de proyectos en tu repositorio u organización o los que le pertenezcan a tu cuenta de usuario. -2. En la lista de proyectos, junto al tablero de proyectos que deseas cerrar, haz clic en {% octicon "chevron-down" aria-label="The chevron icon" %}. ![Icono de comillas angulares a la derecha del nombre del tablero de proyecto](/assets/images/help/projects/project-list-action-chevron.png) -3. Click **Close**. ![Menú desplegable para cerrar elementos en el tablero de proyecto](/assets/images/help/projects/close-project.png) - -### Leer más - -- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" -- "[Eliminar un tablero de proyecto](/articles/deleting-a-project-board)" -- "[Inhabilitar tableros de proyectos en un repositorio](/articles/disabling-project-boards-in-a-repository)" -- "[Inhabilitar tableros de proyectos en tu organización](/articles/disabling-project-boards-in-a-repository)" -- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards.md deleted file mode 100644 index 78498e4937..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Configurar la automatización para tableros de proyecto -intro: Puedes establecer flujos de trabajo automáticos para mover propuestas y solicitudes de extracción a una columna de tablero de proyecto cuando se produce un evento especificado. -redirect_from: - - /articles/configuring-automation-for-project-boards - - /github/managing-your-work-on-github/configuring-automation-for-project-boards -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.project-management.automate-project-board-permissions %} Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards)". - -{% data reusables.project-management.use-automated-template %} - -{% data reusables.project-management.resync-automation %} - -{% tip %} - -**Sugerencia** Para editar columnas que ya tienen configurada la automatización, haz clic en **Manage** (Administrar) en la parte inferior de la columna. - -{% endtip %} - -1. Dirígete al tablero de proyecto que deseas automatizar. -2. En la columna que deseas automatizar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Icono Editar](/assets/images/help/projects/edit-column-button.png) -3. Haz clic en **Manage automation** (Administrar automatización). ![Botón Manage automation (Administrar automatización)](/assets/images/help/projects/manage-automation-button.png) -4. En el menú desplegable Preset (Preestablecer), selecciona el preestablecimiento de la automatización. ![Selecciona preestablecer la automatización desde el menú](/assets/images/help/projects/select-automation.png) -5. Selecciona las automatizaciones del flujo de trabajo que deseas configurar para la columna. ![Lista de opciones para automatizar la columna](/assets/images/help/projects/select-automation-options-existing-column.png) -6. Haz clic en **Update automation** (Actualizar automatización). - -### Leer más -- "[Acerca de la automatización de los tableros de proyecto](/articles/about-automation-for-project-boards)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/copying-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/copying-a-project-board.md deleted file mode 100644 index 30d72a50c2..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/copying-a-project-board.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Copiar un tablero de proyecto -intro: Puedes copiar un tablero de proyecto para crear rápidamente un proyecto nuevo. Si copias los tableros de proyecto altamente personalizados o que se usan con frecuencia te ayudará a estandarizar tu flujo de trabajo. -redirect_from: - - /articles/copying-a-project-board - - /github/managing-your-work-on-github/copying-a-project-board -versions: - free-pro-team: '*' -topics: - - Pull requests ---- -Copiar un tablero de proyecto te permite volver a usar el título, la descripción y la configuración automática de un tablero de proyecto. Puedes copiar los tableros de proyecto para eliminar el proceso manual de creación de nuevos tableros de proyecto para flujos de trabajo similares. - -Debes tener acceso de lectura de un tablero de proyecto para copiarlo en un repositorio u organización donde tengas acceso de lectura. - -Cuando copias un tablero de proyecto a una organización, la visibilidad del tablero de proyecto se predeterminará en privada, con la opción de cambiar la visibilidad. Para obtener más información, consulta "[Cambiar la visibilidad del tablero de proyecto](/articles/changing-project-board-visibility/)". - -La automatización del tablero de proyecto también está habilitada por defecto. Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards/)". - -1. Navega hasta el tablero de proyecto que quieres copiar. -{% data reusables.project-management.click-menu %} -3. Haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, luego haz clic en **Copy** (Copiar). ![Opción para copiar en el menú desplegable desde la barra lateral del tablero de proyecto](/assets/images/help/projects/project-board-copy-setting.png) -4. Debajo de "Owner" (Propietario), usa el menú desplegable y haz clic en el repositorio o la organización donde deseas copiar el tablero de proyecto. ![Selecciona el propietario del tablero de proyecto copiado desde el menú desplegable](/assets/images/help/projects/copied-project-board-owner.png) -5. Opcionalmente, debajo de "Project board name" (Nombre del tablero de proyecto), haz clic en el nombre del tablero de proyecto copiado. ![Campo para escribir un nombre para el tablero de proyecto copiado](/assets/images/help/projects/copied-project-board-name.png) -6. Opcionalmente, debajo de "Description" (Descripción), escribe una descripción del tablero de proyecto copiado que verán otras personas. ![Campo para escribir una descripción para el tablero de proyecto copiado](/assets/images/help/projects/copied-project-board-description.png) -7. Opcionalmente, debajo de "Automation settings " (Parámetros de automatización), selecciona si deseas copiar los flujos de trabajo automáticos configurados. Esta opción está habilitada por defecto. Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards/)". ![Selecciona los parámetros de automatización para el tablero de proyecto copiado](/assets/images/help/projects/copied-project-board-automation-settings.png) -8. Si estás copiando un tablero de proyecto que es propiedad de la organización, en "Visibility" (Visibilidad), selecciona si deseas que tu tablero de proyecto copiado sea privado o público. ![Selecciona los parámetros de visibilidad para el tablero de proyecto copiado](/assets/images/help/projects/copied-project-board-visibility-settings.png) -9. Haz clic en **Copy project** (Copiar proyecto). ![Botón para confirmar copia](/assets/images/help/projects/confirm-copy-project-board.png) diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/creating-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/creating-a-project-board.md deleted file mode 100644 index 3a25ec9dc3..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/creating-a-project-board.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Crear un tablero de proyecto -intro: 'Los tableros de proyecto se pueden usar para crear flujos de trabajo personalizados de acuerdo con tus necesidades, como hacer un seguimiento y priorizar trabajos con características específicas, hojas de ruta completas y hasta listas de verificación de lanzamientos.' -redirect_from: - - /articles/creating-a-project/ - - /articles/creating-a-project-board - - /github/managing-your-work-on-github/creating-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.project-management.use-automated-template %} - -{% data reusables.project-management.copy-project-boards %} - -{% data reusables.project-management.link-repos-to-project-board %} Para obtener más información, consulta "[Enlazar un repositorio a un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". - -Una vez que has creado tu tablero de proyecto, puedes agregarle propuestas, solicitudes de extracción y notas. Para obtener más información, consulta "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" y "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)". - -También puedes configurar automatizaciones de flujo de trabajo para mantener tu tablero de proyecto sincronizado con el estado de las propuestas y solicitudes de extracción. Para obtener más información, consulta "[Acerca de la automatización para tableros de proyecto](/articles/about-automation-for-project-boards)". - -{% data reusables.project-management.project-board-import-with-api %} - -### Crear un tablero de proyecto propiedad de un usuario - -{% data reusables.profile.access_profile %} -2. On the top of your profile page, in the main navigation, click -{% octicon "project" aria-label="The project board icon" %} **Projects**. -![Pestaña Project (Proyecto)](/assets/images/help/projects/user-projects-tab.png) -{% data reusables.project-management.click-new-project %} -{% data reusables.project-management.create-project-name-description %} -{% data reusables.project-management.choose-template %} -{% data reusables.project-management.linked-repositories %} -{% data reusables.project-management.create-project-button %} -{% data reusables.project-management.add-column-new-project %} -{% data reusables.project-management.name-project-board-column %} -{% data reusables.project-management.select-column-preset %} -{% data reusables.project-management.select-automation-options-new-column %} -{% data reusables.project-management.click-create-column %} -{% data reusables.project-management.add-more-columns %} - -{% data reusables.project-management.edit-project-columns %} - -### Crear un tablero de proyecto para toda la organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.organization-wide-project %} -{% data reusables.project-management.click-new-project %} -{% data reusables.project-management.create-project-name-description %} -{% data reusables.project-management.choose-template %} -{% data reusables.project-management.linked-repositories %} -{% data reusables.project-management.create-project-button %} -{% data reusables.project-management.add-column-new-project %} -{% data reusables.project-management.name-project-board-column %} -{% data reusables.project-management.select-column-preset %} -{% data reusables.project-management.select-automation-options-new-column %} -{% data reusables.project-management.click-create-column %} -{% data reusables.project-management.add-more-columns %} - -{% data reusables.project-management.edit-project-columns %} - -### Crear un tablero de proyecto para un repositorio - -{% data reusables.repositories.navigate-to-repo %} -2. Debajo del nombre de tu repositorio, da clic -{% octicon "project" aria-label="The project board icon" %} **Projects**. -![Pestaña Project (Proyecto)](/assets/images/help/projects/repo-tabs-projects.png) -{% data reusables.project-management.click-new-project %} -{% data reusables.project-management.create-project-name-description %} -{% data reusables.project-management.choose-template %} -{% data reusables.project-management.create-project-button %} -{% data reusables.project-management.add-column-new-project %} -{% data reusables.project-management.name-project-board-column %} -{% data reusables.project-management.select-column-preset %} -{% data reusables.project-management.select-automation-options-new-column %} -{% data reusables.project-management.click-create-column %} -{% data reusables.project-management.add-more-columns %} - -{% data reusables.project-management.edit-project-columns %} - -### Leer más - -- "[Acerca de los tableros de proyectos](/articles/about-project-boards)" -- "[Editar un tablero de proyecto](/articles/editing-a-project-board)"{% if currentVersion == "free-pro-team@latest" %} -- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} -- "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)" -- "[Acerca de la automatización de los tableros de proyecto](/articles/about-automation-for-project-boards)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board.md deleted file mode 100644 index e73a73d80e..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Eliminar un tablero de proyecto -intro: Puedes eliminar un tablero de proyecto existente si ya no necesitas acceder a su contenido. -redirect_from: - - /articles/deleting-a-project/ - - /articles/deleting-a-project-board - - /github/managing-your-work-on-github/deleting-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% tip %} - -**Sugerencia**: Si deseas conservar el acceso a un tablero de proyecto que ya no necesitas o que ya está completo sin perder acceso a su contenido, puedes [cerrar el tablero de proyecto](/articles/closing-a-project-board) en lugar de eliminarlo. - -{% endtip %} - -1. Dirígete al tablero de proyecto que deseas eliminar. -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.click-edit-sidebar-menu-project-board %} -4. Haz clic en **Eliminar proyecto**. ![Botón Eliminar proyecto](/assets/images/help/projects/delete-project-button.png) -5. Para confirmar que deseas eliminar el tablero de proyecto, haz clic en **Aceptar**. - -### Leer más - -- "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)" -- "[Inhabilitar tableros de proyectos en un repositorio](/articles/disabling-project-boards-in-a-repository)" -- "[Inhabilitar tableros de proyectos en tu organización](/articles/disabling-project-boards-in-a-repository)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository.md deleted file mode 100644 index e41578234d..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Inhabilitar los tableros de proyecto en un repositorio -intro: Los administradores de los repositorios pueden desactivar los tableros de proyecto para un repositorio si tanto tu equipo como tú administran el trabajo de forma diferente. -redirect_from: - - /articles/disabling-project-boards-in-a-repository - - /github/managing-your-work-on-github/disabling-project-boards-in-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Cuando inhabilitas los tableros de proyecto, ya no ves la información de los tableros de proyecto de manera cronológica o de acuerdo con los [registros de auditoría](/articles/reviewing-your-security-log/). - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En "Características", quita la marca de selección de la casilla de verificación **Proyectos**. ![Casilla de verificación Eliminar proyectos](/assets/images/help/projects/disable-projects-checkbox.png) - -Una vez que se inhabilitan los tableros de proyecto, ya no se puede acceder a ellos en sus URL anteriores. {% data reusables.organizations.disable_project_board_results %} diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-your-organization.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-your-organization.md deleted file mode 100644 index 59227841f2..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Inhabilitar los tableros de proyecto en tu organización -intro: Los propietarios de la organización pueden desactivar tableros de proyecto que se usan en toda la organización y tableros de proyecto de repositorios en una organización. -redirect_from: - - /articles/disabling-project-boards-in-your-organization - - /github/managing-your-work-on-github/disabling-project-boards-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Una vez que inhabilites tableros de proyecto que se usan en toda la organización, ya no se podrán crear nuevos tableros de proyecto a nivel de la organización, y ya no se podrá acceder a ningún tablero de proyecto existente a nivel de la organización en su URL anterior. Los tableros de proyecto en los repositorios de la organización no se ven afectados. - -Una vez que inhabilites tableros de proyecto de repositorios en una organización, ya no se podrán crear nuevos tableros de proyecto en ningún repositorio de la organización, y ya no se podrá acceder a ningún tablero de proyecto de los repositorios existentes en la organización en sus URL anteriores. Los tableros de proyecto a nivel de la organización no se ven afectados. - -Cuando inhabilitas tableros de proyecto, ya no ves su información de manera cronológica o de acuerdo con los [registros de auditoría](/articles/reviewing-your-security-log/). - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -4. Decide si deseas inhabilitar los tableros de proyecto que se usan en toda la organización, los tableros de proyecto de los repositorios de la organización, o ambos. Luego, en "Proyectos": - - Para inhabilitar los tableros de proyecto que se usan en toda la organización, quita la marca de selección de **Habilitar proyectos para la organización**. - - Para inhabilitar los tableros de proyecto de los repositorios en la organización, quita la marca de selección de **Habilitar proyectos para todos los repositorios**. ![Casillas de verificación para inhabilitar proyectos para una organización o para todos los repositorios de una organización](/assets/images/help/projects/disable-org-projects-checkbox.png) -5. Haz clic en **Save (Guardar)**. - -{% data reusables.organizations.disable_project_board_results %} - -### Leer más - -- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" -- "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)" -- "[Eliminar un tablero de proyecto](/articles/deleting-a-project-board)" -- "[Inhabilitar tableros de proyectos en un repositorio](/articles/disabling-project-boards-in-a-repository)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/editing-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/editing-a-project-board.md deleted file mode 100644 index 2396bb0dc8..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/editing-a-project-board.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Editar un tablero de proyecto -intro: Puedes editar el título y la descripción de un tablero de proyecto existente. -redirect_from: - - /articles/editing-a-project/ - - /articles/editing-and-deleting-a-project/ - - /articles/editing-a-project-board - - /github/managing-your-work-on-github/editing-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% tip %} - -**Sugerencia:** Para conocer detalles sobre cómo agregar, eliminar o editar columnas en tu tablero de proyecto, consulta "[Crear un tablero de proyecto](/articles/creating-a-project-board)". - -{% endtip %} - -1. Dirígete al tablero de proyecto que deseas editar. -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.click-edit-sidebar-menu-project-board %} -4. Modifica el nombre y la descripción del tablero de proyecto según sea necesario y luego haz clic en **Guardar proyecto**. ![Campos con el nombre y la descripción del tablero de proyecto y botón Guardar proyecto](/assets/images/help/projects/edit-project-board-save-button.png) - -### Leer más - -- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" -- "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[Eliminar un tablero de proyecto](/articles/deleting-a-project-board)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/index.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/index.md deleted file mode 100644 index 5b08fc9df4..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Administrar tableros de proyecto -intro: Puedes usar tableros de proyecto para organizar propuestas y solicitudes de extracción y administrar tu flujo de trabajo a través de un repositorio u organización. -redirect_from: - - /articles/managing-project-boards -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /about-project-boards - - /creating-a-project-board - - /editing-a-project-board - - /linking-a-repository-to-a-project-board - - /about-automation-for-project-boards - - /configuring-automation-for-project-boards - - /copying-a-project-board - - /closing-a-project-board - - /reopening-a-closed-project-board - - /deleting-a-project-board - - /disabling-project-boards-in-a-repository - - /disabling-project-boards-in-your-organization - - /changing-project-board-visibility ---- - diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/linking-a-repository-to-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/linking-a-repository-to-a-project-board.md deleted file mode 100644 index f3b44c4d46..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/linking-a-repository-to-a-project-board.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Vincular un repositorio a un tablero de proyecto -intro: Puedes vincular un repositorio a tu tablero de proyecto de la organización o de la cuenta de usuario. -redirect_from: - - /articles/linking-a-repository-to-a-project-board - - /github/managing-your-work-on-github/linking-a-repository-to-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Cualquiera con permisos de escritura en un tablero de proyecto puede enlazar repositorios que sean propiedad de la cuenta de usuario u organización al mismo. Para obtener más información, consulta la sección "[Permisos para una organización sobre el tablero de proyecto](/articles/project-board-permissions-for-an-organization/)" o "[Niveles de permiso para tableros de proyecto propiedad de un usuario](/articles/permission-levels-for-user-owned-project-boards/)". - -{% data reusables.project-management.link-repos-to-project-board %} Puedes agregar propuestas y solicitudes de extracción desde cualquier repositorio no vinculado escribiendo la URL de la propuesta o de la solicitud de extracción en una tarjeta. Para obtener más información, consulta "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)". - -1. Navega hasta el tablero de proyecto al que quieras vincular un repositorio. -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -4. En la barra lateral izquierda, haz clic en **Linked repositories** (Repositorios vinculados). ![Opción del menú Linked repositories (Repositorios vinculados) en la barra lateral izquierda](/assets/images/help/projects/project-board-linked-repositories-setting.png) -5. Haz clic en **Link a repository** (Vincular un repositorio). ![Botón Link a repository (Vincular un repositorio) en la pestaña Linked repositories (Repositorios vinculados)](/assets/images/help/projects/link-repository-button.png) -6. Busca el repositorio que quieras vincular. ![Campo de búsqueda en la ventana Link a repository (Vincular un repositorio)](/assets/images/help/projects/search-to-link-repository.png) -7. Click **Link**. Para desvincular, haz clic en **Unlink** (Desvincular). ![Botón Link (Vincular)](/assets/images/help/projects/link-button.png) - -### Leer más - -- "[Acerca de los tableros de proyectos](/articles/about-project-boards)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board.md deleted file mode 100644 index 69729e9fd2..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Reabrir un tablero de proyecto cerrado -intro: Puedes reabrir un tablero de proyecto cerrado y reiniciar cualquier automatización de flujo de trabajo que se haya configurado para el tablero de proyecto. -redirect_from: - - /articles/reopening-a-closed-project-board - - /github/managing-your-work-on-github/reopening-a-closed-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Cuando cierras un tablero de proyecto, por defecto, se detiene cualquier automatización de flujo de trabajo que se haya configurado para el tablero de proyecto. Para obtener más información, consulta "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)". - -Cuando reabres un tablero de proyecto, tienes la opción de *sync* (sincronizar) automatización, lo cual actualiza la posición de las tarjetas en el tablero de acuerdo con los parámetros de automatización establecidos para el tablero. - -1. Navega hasta el tablero de proyecto que quieres reabrir. -{% data reusables.project-management.click-menu %} -3. Elige la sincronización de la automatización para tu tablero de proyecto o reabre tu tablero de proyecto sin sincronizar. - - Para reabrir tu tablero de proyecto y sincronizar la automatización, haz clic en **Reopen and sync project** (Reabrir y sincronizar proyecto). ![Selecciona el botón "Reopen and resync project" (Reabrir y resincronizar proyecto)](/assets/images/help/projects/reopen-and-sync-project.png) - - Para reabrir tu tablero de proyecto sin sincronizar la automatización, utilizando el menú desplegable, haz clic en **Reopen only** (Solo reabrir). Luego, haz clic en **Reopen only** (Solo reabrir). ![Menú desplegable para reabrir tablero de proyecto cerrado](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png) - -### Leer más - -- "[Configurar la automatización para los tableros de proyecto](/articles/configuring-automation-for-project-boards)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-automation-for-issues-and-pull-requests-with-query-parameters.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-automation-for-issues-and-pull-requests-with-query-parameters.md deleted file mode 100644 index 852bec9b1c..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-automation-for-issues-and-pull-requests-with-query-parameters.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Acerca de la automatización para propuestas y solicitudes de extracción con parámetros de consulta -intro: Puedes usar los parámetros de consulta para compartir URLs con información personalizada. -redirect_from: - - /articles/about-automation-for-issues-and-pull-requests-with-query-parameters - - /github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Los parámetros de consulta son partes opcionales de una URL que puedes personalizar para compartir una vista de página web específica, como los resultados de filtro de búsqueda o una plantilla de propuestas en {% data variables.product.prodname_dotcom %}. Para crear tus propios parámetros de consulta, debes hacer coincidir el par de clave y valor. - -{% tip %} - -**Sugerencia:** También puedes crear plantillas de propuestas que se abran con etiquetas, asignatarios y un título de propuesta predeterminados. Para obtener más información, consulta "[Configurar plantillas de propuestas para tu repositorio](/articles/configuring-issue-templates-for-your-repository)" o "[Crear de forma manual una plantilla de propuesta para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)". - -{% endtip %} - -Debes tener los permisos adecuados para cualquier acción para usar el parámetro de consulta equivalente. Por ejemplo, debes tener permiso para agregar una etiqueta a una propuesta para usar el parámetro de consulta `labels`. - -Si creas una URL no válida usando los parámetros de consulta o si no tienen los permisos adecuados, la URL devolverá una página de error 404. - -### Parámetros de consulta admitidos - -| Parámetro de consulta | Ejemplo | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `cuerpo` | `https://github.com/octo-org/octo-repo/compare/master...pull-request-test?quick_pull=1&body=Fixes+the+problem.` crea una solicitud de extracción, comparando ramas `master` y `pull-request-test`, con el comentario "Soluciona el problema" en el cuerpo de la solicitud de extracción. | -| `título` | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` crea una propuesta en la etiqueta "error" y el título "Nuevo informe de error". | -| `etiquetas` | `https://github.com/octo-org/octo-repo/compare/master...pull-request-test?quick_pull=1&labels=bug` crea una solicitud de extracción, comparando las ramas `master` y `pull-request-test`, con la etiqueta "error". | -| `plantilla` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` crea una propuesta con una plantilla en el cuerpo de la propuesta. | -| `hito` | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` crea una propuesta con el hito "probando hitos". | -| `asignatarios` | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` crea una propuesta y la asigna a @octocat. | -| `proyectos` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` crea una propuesta con el título "Solución del problema" y la agrega al tablero de proyecto 1 de la organización. | - -### Completar propuestas y solicitudes de extracción con plantillas personalizadas - -{% data reusables.repositories.legacy-issue-template-tip %} - -Puedes usar el parámetro de consulta `template` para especificar una plantilla para completar de forma automática la propuesta o el cuerpo de la solicitud de extracción. El parámetro de consulta `template` funciona con las plantillas almacenadas en el subdirectorio `ISSUE_TEMPLATE` o `PULL_REQUEST_TEMPLATE` dentro de la raíz, del directorio `docs/` o `.github/` en un repositorio. - -Si un repositorio contiene solo la solicitud de extracción o la plantilla de propuesta predeterminada, cualquier propuesta o solicitud de extracción nueva tendrá la plantilla predeterminada en el cuerpo. - -Para obtener más información, consulta "[Crear una plantilla de solicitud de extracción para tu repositorio](/articles/creating-a-pull-request-template-for-your-repository)" o "[Crear de forma manual una plantilla de propuesta para tu repositorio](/articles/manually-creating-a-single-issue-template-for-your-repository)". - -### Leer más - -- "[Automatización para formularios de lanzamiento con parámetros de consulta](/articles/automation-for-release-forms-with-query-parameters)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-duplicate-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-duplicate-issues-and-pull-requests.md deleted file mode 100644 index 25c46be59c..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-duplicate-issues-and-pull-requests.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Acerca de duplicar propuestas y solicitudes de extracción -intro: 'Marca una propuesta o solicitud de extracción como un duplicado para hacer un seguimiento de propuestas o solicitudes de extracción similares en conjunto y eliminar una responsabilidad innecesaria, tanto para los mantenedores como para los colaboradores.' -redirect_from: - - /articles/about-duplicate-issues-and-pull-requests - - /github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Para que aparezca un evento cronológico "marcado como duplicado", el usuario que crea el comentario de referencia duplicado debe tener acceso de escritura al repositorio donde crea el comentario. - -### Marcar duplicados - -Para marcar una propuesta o solicitud de extracción como un duplicado, escribe "Duplicado de" seguido del número de propuesta o solicitud de extracción que se duplica en el cuerpo de un comentario nuevo. También puedes usar las respuestas guardadas "Duplicar propuesta" o "Duplicar solicitud de extracción" provistas por GitHub para marcar una propuesta o solicitud de extracción como un duplicado. Para obtener más información, consulta "[Acerca de las respuestas guardadas](/articles/about-saved-replies)". - -![Duplicar la sintaxis de la propuesta](/assets/images/help/issues/duplicate-issue-syntax.png) - -### Desmarcar duplicados - -Puedes desmarcar propuestas o solicitudes de extracción duplicadas haciendo clic en la cronología **Deshacer**. Esto agregará un evento cronológico nuevo, indicando que la propuesta o la solicitud de extracción fue desmarcada. - -![Botón Desmarcar propuesta duplicada](/assets/images/help/issues/unmark-duplicate-issue-button.png) diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-issues.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-issues.md deleted file mode 100644 index 183638c57e..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-issues.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Acerca de las propuestas -intro: 'Usa las propuestas para rastrear ideas, mejoras, tareas o errores para tu trabajo en {% data variables.product.product_name %}.' -redirect_from: - - /articles/creating-issues/ - - /articles/about-issues/ - - /github/managing-your-work-on-github/about-issues -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Puedes recopilar opiniones del usuario, informar errores de software y organizar tareas que quieras realizar con las propuestas en un repositorio. Las propuestas pueden actuar como más que un simple lugar para informar errores de software. - -{% data reusables.pull_requests.close-issues-using-keywords %} - -Para estar actualizado sobre los comentarios más recientes en una propuesta, puedes ver una propuesta para recibir notificaciones acerca de los últimos comentarios. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[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 %}". - -Para encontrar rápidamente los enlaces a los informes de problemas recientemente actualizados a los cuales te has suscrito, visita tu tablero. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". - -### Trabajar con propuesta - -Con las propuestas, puedes hacer lo siguiente: -- Rastrear y priorizar tu trabajo usando tableros de proyecto. Para obtener más información, consulta "[Cómo usar tableros de proyecto](/articles/about-project-boards)". -- Crear nuevos informes de problemas para rastrear la retroalimentación fuera de ámbito desde un comentario en una revisión de informe de problemas o de solicitud de extracción. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". -- Crear plantillas de propuestas para ayudar a los colaboradores a abrir propuestas significativas. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)".{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -- Transferir propuestas abiertas a otros repositorios. Para obtener más información, consulta "[Transferir una propuesta a otro repositorio](/articles/transferring-an-issue-to-another-repository)."{% endif %} -- Anclar propuestas importantes para hacer que sea más fácil encontrarlas, evitando las propuestas duplicadas y reduciendo el ruido. Para obtener más información, consulta "[Anclar una propuesta a tu repositorio](/articles/pinning-an-issue-to-your-repository)". -- Rastrear propuestas duplicadas usando las respuestas guardadas. Para obtener más información, consulta "[Acerca de las respuestas guardadas](/articles/about-saved-replies)."{% if currentVersion == "free-pro-team@latest" %} -- Informar comentarios que violan las [Pautas de la comunidad](/articles/github-community-guidelines) de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Informar abuso o spam](/articles/reporting-abuse-or-spam)".{% endif %} - -Las propuestas también se pueden [asignar a otros usuarios](/articles/assigning-issues-and-pull-requests-to-other-github-users), [marcar con etiquetas](/articles/applying-labels-to-issues-and-pull-requests) para una búsqueda más rápida y [agrupar con hitos](/articles/creating-and-editing-milestones-for-issues-and-pull-requests). diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-task-lists.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-task-lists.md deleted file mode 100644 index 25c1dcf634..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/about-task-lists.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Acerca de las listas de tareas -intro: Puedes usar listas de tareas para crear una lista de elementos con casillas de verificación dentro de los comentarios de una solicitud de extracción y de una propuesta o archivos Markdown en tu repositorio. -redirect_from: - - /articles/about-task-lists - - /github/managing-your-work-on-github/about-task-lists -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Las listas de tareas están representadas con casillas de verificación interactivas en los comentarios. Puedes seleccionar o quitar la marca de selección de las casillas de verificación para marcarlas como completas o incompletas. - -Las listas de tareas están representadas como casillas de verificación de solo lectura en los archivos Markdown. Las personas con permisos de escritura en el repositorio pueden editar el archivo para seleccionar o quitar la marca de selección de las casillas de verificación. - -Puedes ver la información del resúmen de la lista de tareas en las listas de una propuesta y una solicitud de extracción, cuando la lista de tareas está en el comentario inicial. - -![Resúmen de lista de tareas](/assets/images/help/issues/task-list-summary.png) - -### Crear listas de tareas - -{% data reusables.repositories.task-list-markdown %} - -### Volver a ordenar tareas - -Puedes volver a ordenar las listas de tareas dentro de un comentario único haciendo clic a la izquierda de la casilla de verificación de una tarea, arrastrándola a una nueva ubicación y colocándola ahí. Si tienes varias listas dentro de un comentario, puedes volver a ordenar tareas en el comentario único. Puedes agregar o volver a ordenar tareas en diferentes comentarios. - -![Volver a ordenar lista de tareas](/assets/images/help/writing/task-list-reordered.gif) - -### Leer más - -* [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md deleted file mode 100644 index 1dfe6b6e0d..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -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. -redirect_from: - - /articles/assigning-issues-and-pull-requests-to-other-github-users - - /github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Cualquier persona con permisos de escritura en un repositorio puede asignar propuestas y solicitudes de extracción. - -Puedes asignar hasta 10 personas a cada propuesta o solicitudes de extracción, incluido tú mismo, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} a cualquier persona que haya comentado sobre la propuesta o la solicitud de extracción,{% endif %} o cualquier persona con permisos de escritura en el repositorio, y 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)". - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -3. Selecciona la casilla de verificación junto a los elementos que deseas asignar a alguien. ![Casilla de verificación de metadatos de propuestas](/assets/images/help/issues/issues_assign_checkbox.png) -4. En el margen superior derecho, haz clic en **Assignee** (Asignatario). -5. Para asignar los elementos a un usuario, comienza escribiendo su nombre de usuario, luego haz clic en su nombre cuando aparezca. Puedes seleccionar y asignar hasta 10 asignatarios a una propuesta o solicitud de extracción. ![Desplegable de la asignación de propuestas](/assets/images/help/issues/issues_assigning_dropdown.png) - -### Leer más - -* "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/creating-a-permanent-link-to-a-code-snippet.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/creating-a-permanent-link-to-a-code-snippet.md deleted file mode 100644 index de924af8e0..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/creating-a-permanent-link-to-a-code-snippet.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Crear un enlace permanente a un fragmento de código -intro: Puedes crear un enlace permanente a una línea específica o a un rango de líneas de código en una versión específica de un archivo o de una solicitud de extracción. -redirect_from: - - /articles/creating-a-permanent-link-to-a-code-snippet - - /github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Este tipo de enlace permanente se presentará como un fragmento de código únicamente en el repositorio en el que se originó. En los demás repositorios, el fragmento de código de enlace permanente se presentará como una URL. - -![Fragmento de código que se presenta en un comentario](/assets/images/help/repository/rendered-code-snippet.png) - -{% tip %} - -**Sugerencia:** Para crear un enlace permanente para un archivo completo, consulta "[Obtener enlaces permanentes a los archivos](/articles/getting-permanent-links-to-files)". - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -2. Busca el código con el que deseas establecer el enlace: - - Para enlazar el código desde un archivo, dirígete hacia ese archivo. - - Para enlazar el código desde una solicitud de extracción, dirígete a la solicitud de extracción y haz clic en {% octicon "diff" aria-label="The file diff icon" %}**Archivos con cambios**. Luego, desplázate hasta el archivo que contiene el código que deseas incluir en tu comentario y haz clic en **Ver**. -{% data reusables.repositories.choose-line-or-range %} -4. A la izquierda de la línea o del rango de líneas, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. En el menú desplegable, haz clic en **Copiar enlace permanente**. ![Menú kebab con la opción de copiar un enlace permanente desde una línea seleccionada](/assets/images/help/repository/copy-permalink-specific-line.png) -5. Dirígete a la conversación en la que deseas enlazar el fragmento de código. -6. Pega tu enlace permanente en un comentario y haz clic en **Comentar**. ![Enlace permanente pegado en un comentario en el mismo repositorio](/assets/images/help/repository/code-snippet-permalink-in-comment.png) - -### Leer más - -- [Crear una propuesta](/articles/creating-an-issue/)" -- "[Abrir una propuesta desde el código](/articles/opening-an-issue-from-code/)" -- "[Revisar los cambios en las solicitudes de extracción](/articles/reviewing-changes-in-pull-requests/)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/creating-an-issue.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/creating-an-issue.md deleted file mode 100644 index be2df55bec..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/creating-an-issue.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Crear una propuesta -intro: 'Las propuestas se pueden usar para hacer un seguimiento de los errores, mejoras u otras solicitudes.' -redirect_from: - - /articles/creating-an-issue - - /github/managing-your-work-on-github/creating-an-issue -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -permissions: People with read permissions can create an issue in a repository where issues are enabled. -topics: - - Pull requests ---- -{% data reusables.repositories.create-issue-in-public-repository %} - -Puedes abrir una nueva propuesta basada en el código a partir de una solicitud de extracción existente. Para obtener más información, consulta la sección "[Abrir un informe de problemas desde el código](/github/managing-your-work-on-github/opening-an-issue-from-code)". - -Puedes abrir un nuevo informe de problemas directamente desde un comentario en algún otro informe o en una solicitud de extracción. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also create an issue using the {% data variables.product.prodname_cli %}. For more information, see "[`gh issue create`](https://cli.github.com/manual/gh_issue_create)" in the {% data variables.product.prodname_cli %} documentation. - -{% endtip %} -{% endif %} - -Si utilizas un tablero de proyecto para rastrear y priorizar tu trabajo, puedes convertir las notas del mismo en informes de problemas. Para obtener más información, consulta la sección "[Acerca de los tableros de proyecto](/github/managing-your-work-on-github/about-project-boards)" y "[Agregar notas a un tablero de proyecto](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue)". - -{% tip %} - -**Sugerencias**: Los mantenedores del proyecto pueden elegir hacer lo siguiente: - - Crear una plantilla de propuesta para un repositorio. Las plantillas incluyen indicaciones para brindar información en el cuerpo de una propuesta. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/github/building-a-strong-community/about-issue-and-pull-request-templates)". - - Inhabilitar las propuestas para un repositorio. Para obtener más información, consulta la sección "[Inhabilitar informes de problemas](/github/managing-your-work-on-github/disabling-issues)". Pull requests can't be turned off and are always available. - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issues %} -3. Haz clic en **Nueva propuesta**. ![Botón Nuevas propuestas](/assets/images/help/issues/new_issues_button.png) -4. Si hay distintos tipos de propuestas, haz clic en **Empezar** junto al tipo de propuesta que deseas abrir. ![Selecciona el tipo de informe de problemas que quieres crear](/assets/images/help/issues/issue_template_get_started_button.png) -{% if currentVersion == "free-pro-team@latest" or currentVersion >= "enterprise-server@2.21" %} -5. Opcionalmente, da clic en **Abrir un informe de problemas en blanco** si el tipo de informe de problemas que quieres abrir no se incluye en las opciones disponibles. ![Enlace para abrir un informe de problemas en blanco](/assets/images/help/issues/blank_issue_link.png) -{% else %} -5. Opcionalmente, da clic en **Abrir un informe de problemas normal** si el tipo de informe de problemas que quieres abrir no se incluye en las opciones disponibles. ![Enlace para abrir un informe de problemas normal](/assets/images/help/issues/regular_issue_link.png) -{% endif %} -{% data reusables.repositories.type-issue-title-and-description %} -{% data reusables.repositories.assign-an-issue-as-project-maintainer %} -{% data reusables.repositories.submit-new-issue %} -### Leer más - -- "[Crear un enlace permanente a un fragmento de código](/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet)". diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/deleting-an-issue.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/deleting-an-issue.md deleted file mode 100644 index 8883ba4766..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/deleting-an-issue.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Eliminar una propuesta -intro: Los usuarios con permisos de administración en un repositorio determinado pueden eliminar una propuesta de manera permanente de ese repositorio. -redirect_from: - - /articles/deleting-an-issue - - /github/managing-your-work-on-github/deleting-an-issue -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Solo puedes eliminar una propuesta en un repositorio que sea propiedad de tu cuenta de usuario. No puedes eliminar una propuesta en un repositorio que sea propiedad de otra cuenta de usuario, aun si eres una colaborador de esa cuenta. - -Para eliminar una propuesta en un repositorio que sea propiedad de una organización, un propietario de la organización debe habilitar la eliminación de una propuesta para los repositorios de la organización, y tú debes tener permisos de propietario o de administración en ese repositorio. Para obtener más información, consulta "[Permitir que se eliminen propuestas en tu organización](/articles/allowing-people-to-delete-issues-in-your-organization)" y "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)". - -Los colaboradores no reciben una notificación cuando eliminas una propuesta. Cuando visiten la URL de una propuesta que ha sido eliminada, los colaboradores verán un mensaje que dice que la propuesta se ha eliminado. Los usuarios con permisos de propietario o de administración en el repositorio verán también el nombre de usuario de la persona que eliminó la propuesta y la fecha en que se la eliminó. - -1. Dirígete a la propuesta que deseas eliminar. -3. En la barra lateral derecha, debajo de "Notificaciones", da clic en **Borrar informe de problemas**. ![Texto de "Borrar informe de problemas" resaltado al final de la barra lateral derecha de la página del informe de problemas](/assets/images/help/issues/delete-issue.png) -4. Para confirmar la eliminación, haz clic en **Eliminar esta propuesta**. - -### Leer más - -- "[Enlazar una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/disabling-issues.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/disabling-issues.md deleted file mode 100644 index 72391ea46c..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/disabling-issues.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Inhabilitar propuestas -intro: Es posible que desees desactivar las propuestas de tu repositorio en caso de que no aceptes contribuciones o informes de errores. -redirect_from: - - /articles/disabling-issues - - /github/managing-your-work-on-github/disabling-issues -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. En Características, quita la marca de selección de la casilla de verificación **Propuestas**. ![Casilla de verificación Eliminar propuestas](/assets/images/help/issues/issues_settings_remove_from_repo.png) - -Si decides habilitar las propuestas nuevamente en el futuro, todas las propuestas que se hayan agregado previamente estarán disponibles. - -{% if currentVersion == "free-pro-team@latest" %} - -{% tip %} - -Comunícate con {% data variables.contact.contact_support %} si deseas desactivar las propuestas para evitar el abuso de extraños. -{% data reusables.policies.abuse %} - -{% endtip %} - -{% endif %} diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/file-attachments-on-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/file-attachments-on-issues-and-pull-requests.md deleted file mode 100644 index 9ebb62d6b4..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/file-attachments-on-issues-and-pull-requests.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: File attachments on issues and pull requests -intro: 'When you open issue or update a pull request, you can use issue attachments to upload images of proposed features or screenshots of bugs.' -redirect_from: - - /articles/issue-attachments/ - - /articles/file-attachments-on-issues-and-pull-requests - - /github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% warning %} - -**Warning:** If you add an image to a pull request or issue comment, anyone can view the anonymized image URL without authentication, even if the pull request is in a private repository{% if currentVersion != "free-pro-team@latest" %}, or if private mode is enabled{% endif %}. To keep sensitive images private, serve them from a private network or server that requires authentication. {% if currentVersion == "free-pro-team@latest" %}For more information on anonymized URLs see "[About anonymized image URLs](/articles/about-anonymized-image-urls)".{% endif %} - -{% endwarning %} - -To attach a file to an issue or pull request conversation, drag and drop it into the comment box. Alternatively, you can click the bar at the bottom of the comment box to browse, select, and add a file from your computer. - -![Select attachments from computer](/assets/images/help/pull_requests/select-bar.png) - -{% tip %} - -**Tip:** If you're using Chrome, you can also copy-and-paste images directly into the box. - -{% endtip %} - -The maximum size for files is 25MB and the maximum size for images is 10MB. - -We support these files: - -* PNG (*.png*) -* GIF (*.gif*) -* JPEG (*.jpg*) -* Log files (*.log*) -* Microsoft Word (*.docx*), Powerpoint (*.pptx*), and Excel (*.xlsx*) documents -* Text files (*.txt*) -* PDFs (*.pdf*) -* ZIP (*.zip*, *.gz*) - -![Attachments animated GIF](/assets/images/help/pull_requests/dragging_images.gif) diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/index.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/index.md deleted file mode 100644 index 516b517fe1..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Administrar tu trabajo con propuestas -intro: 'Puedes administrar tu trabajo en {% data variables.product.product_name %} al crear propuestas para rastrear ideas, mejoras, tareas o errores.' -redirect_from: - - /articles/managing-your-work-with-issues -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-issues - - /creating-an-issue - - /deleting-an-issue - - /opening-an-issue-from-a-comment - - /opening-an-issue-from-code - - /transferring-an-issue-to-another-repository - - /pinning-an-issue-to-your-repository - - /creating-a-permanent-link-to-a-code-snippet - - /about-task-lists - - /about-automation-for-issues-and-pull-requests-with-query-parameters - - /file-attachments-on-issues-and-pull-requests - - /assigning-issues-and-pull-requests-to-other-github-users - - /viewing-all-of-your-issues-and-pull-requests - - /disabling-issues - - /linking-a-pull-request-to-an-issue - - /about-duplicate-issues-and-pull-requests ---- - diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/linking-a-pull-request-to-an-issue.md deleted file mode 100644 index 0a47a6d435..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Enlazar una solicitud de extracción a un informe de problemas -intro: 'Puedes enlazar una solicitud de extracción a un informe de problemas para que {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} muestre si existe un arreglo en curso y para {% endif %} cerrar dicho informe automáticamente cuando se fusione la solicitud de extracción.' -redirect_from: - - /articles/closing-issues-via-commit-message/ - - /articles/closing-issues-via-commit-messages/ - - /articles/closing-issues-using-keywords - - /github/managing-your-work-on-github/closing-issues-using-keywords - - /github/managing-your-work-on-github/linking-a-pull-request-to-an-issue -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -### Acerca de enlazar informes de problemas y solicitudes de extracción - -Puedes enlazar un informe de problemas a una solicitud de extracción {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} manualmente o {% endif %}utilizando una palabra clave compatible en la descripción de esta solicitud. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -Cuando enlazas una solicitud de extracción al informe de problemas al que ésta hace referencia, los colaboradores pueden ver si alguien está trabajando en dicho informe. -{% if currentVersion ver_lt "enterprise-server@2.21" %}Si la solicitud de extracción y el informe de problemas se encuentran en repositorios diferentes, {% data variables.product.product_name %} mostrará el enlace después de que se fusione esta solicitud, si en caso de que la persona que fusiona la solicitud también tiene permiso de cerrar el informe de problemas.{% endif %}{% endif %} - -Cuando fusionas una solicitud de extracción que se ha enlazado y se encuentra en la rama predeterminada de un repositorio, su informe de problemas enlazado se cierra automáticamente. Para obtener más información acerca de la rama predeterminada, consulta la sección "[Configurar la rama predeterminada](/github/administering-a-repository/setting-the-default-branch)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -### Enlazar una solicitud de extracción a un informe de problemas manualmente - -Cualquiera con permisos de escritura en un repositorio puede enlazar una solicitud de extracción a un problema manualmente. - -Puedes enlazar hasta diez informes de problemas a cada solicitud de extracción manualmente. El informe de problemas y la solicitud de extracción deberán encontrarse en el mismo repositorio. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-pr %} -3. En la lista de solicitudes de extracción, da clic en aquella que quieras enlazar a un informe de problemas. -4. En la barra lateral derecha, da clic en **Informes de problemas relacionados**. ![Informes de problemas enlazados en la barra lateral derecha](/assets/images/help/pull_requests/linked-issues.png) -5. Da clic en el informe de problemas que quieras enlazar a la solicitud de extracción. ![Menú desplegable para enlazar un informe de problemas](/assets/images/help/pull_requests/link-issue-drop-down.png) -{% endif %} - -### Enlazar una solicitud de extracción a un informe de problemas utilizando una palabra clave - -Puedes enlazar una solicitud de extracción a un informe de problemas si utilizas una palabra clave compatible en la descripción de la solicitud. - -* close -* closes -* closed -* fix -* fixes -* fixed -* resolver -* resolves -* resolved - -La sintaxis para palabras clave de cierre dependerá de si el informe de problemas se encuentra en el mismo repositorio que la solicitud de extracción. - -| Informe enlazado | Sintaxis | Ejemplo | -| ------------------------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------- | -| Propuesta en el mismo repositorio | Closes #10 | `Closes #10` | -| Propuesta en un repositorio diferente | *PALABRA CLAVE* *PROPIETARIO*/*Repositorio*#*NÚMERO DE PROPUESTA* | `Fixes octo-org/octo-repo#100` | -| Múltiples propuestas | Utilizar la sintaxis completa para cada informe | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}Solo las solicitudes de extracción enlazadas manualmente se podrán desenlazar de la misma forma. Para desenlazar un informe de problemas que hayas enlazado previamente utilizando una palabra clave, deberás editar la descripción de la solicitud de extracción y así poder eliminar la palabra clave.{% endif %} - -También puedes utilizar palabras clave de cierre en un mensaje de confirmación. El informe de problemas se cerrará cuando fusiones la confirmación de cambios en la rama predeterminada {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, pero la solicitud de extracción que contenga dicha confirmación no se listará como una solicitud de extracción enlazada{% endif %}. - -### Leer más - -- "[URL y referencias auto-enlazadas](/articles/autolinked-references-and-urls/#issues-and-pull-requests)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/opening-an-issue-from-a-comment.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/opening-an-issue-from-a-comment.md deleted file mode 100644 index 11eee334a2..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/opening-an-issue-from-a-comment.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Abrir un informe de problemas desde un comentario -intro: Puedes abrir un nuevo informe de problemas desde un comentario específico en un informe de problemas o solicitud de extracción. -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -permissions: People with read permissions can create an issue in a repository where issues are enabled. -topics: - - Pull requests -redirect_from: - - /github/managing-your-work-on-github/opening-an-issue-from-a-comment ---- -Cuando abres un informe de problemas desde un comentario, este informe contiene un fragmento de código que muestra en dónde se hizo el comentario originalmente. - -1. Navega al comentario desde el cual quieras abrir un informe de problemas. - -2. Dentro del comentario, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Botón Kebab en el comentario de la revisión de solicitud de extracción](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png) -3. Haz clic en **Reference in new issue** (Referencia en la propuesta nueva). ![Referencia en el elemento del menú de propuestas nuevas](/assets/images/help/pull_requests/reference-in-new-issue.png) -4. Usa el menú desplegable "Repository" (Repositorio) y selecciona el repositorio donde desees abrir la propuesta. ![Repositorio desplegable para nueva propuesta](/assets/images/help/pull_requests/new-issue-repository.png) -5. Escribe un título descriptivo y un cuerpo para la propuesta. ![Título y cuerpo para la nueva propuesta](/assets/images/help/pull_requests/new-issue-title-and-body.png) -6. Haz clic en **Create issue** (Crear propuesta). ![Botón para crear la nueva propuesta](/assets/images/help/pull_requests/create-issue.png) -{% data reusables.repositories.assign-an-issue-as-project-maintainer %} - -### Leer más - -- [Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/opening-an-issue-from-code.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/opening-an-issue-from-code.md deleted file mode 100644 index 8ca291ec4a..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/opening-an-issue-from-code.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Abrir una propuesta desde el código -intro: Puedes abrir una nueva propuesta desde una línea específica o líneas de código en un archivo o solicitud de extracción. -redirect_from: - - /articles/opening-an-issue-from-code - - /github/managing-your-work-on-github/opening-an-issue-from-code -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -permissions: People with read permissions can create an issue in a repository where issues are enabled. -topics: - - Pull requests ---- -Cuando abres una propuesta desde el código, la propuesta contiene un fragmento de código que muestra la línea o rango de código que elegiste. Solo puedes abrir una propuesta en el mismo repositorio donde se almacena el código. - -![Fragmento de código representado en una propuesta abierta desde el código](/assets/images/help/repository/issue-opened-from-code.png) - -{% data reusables.repositories.create-issue-in-public-repository %} - -{% data reusables.repositories.navigate-to-repo %} -2. Ubica el código que deseas hacer referencia en una propuesta: - - Para abrir una propuesta acerca de un código en un archivo, navega hasta el archivo. - - Para abrir una propuesta acerca de un código en una solicitud de extracción, navega hasta la solicitud de extracción y haz clic en {% octicon "diff" aria-label="The file diff icon" %} **Files changed (Archivos modificados)**. Luego, desplázate hasta el archivo que contiene el código que deseas incluir en tu comentario y haz clic en **Ver**. -{% data reusables.repositories.choose-line-or-range %} -4. To the left of the code range, click -{% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. En el menú desplegable, da clic en **Referenciar en nuevo informe de problemas**. - ![Menú Kebab con opción para abrir una propuesta nueva desde una línea seleccionada](/assets/images/help/repository/open-new-issue-specific-line.png) -{% data reusables.repositories.type-issue-title-and-description %} -{% data reusables.repositories.assign-an-issue-as-project-maintainer %} -{% data reusables.repositories.submit-new-issue %} - -### Leer más - -- [Crear una propuesta](/github/managing-your-work-on-github/creating-an-issue)" -- "[Obtener enlaces permanentes a los archivos](/github/managing-files-in-a-repository/getting-permanent-links-to-files)" -- "[Crear un enlace permanente a un fragmento de código](/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet)". diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/pinning-an-issue-to-your-repository.md deleted file mode 100644 index 46dd0fa315..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/pinning-an-issue-to-your-repository.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Anclar una propuesta a tu repositorio -intro: Puedes anclar hasta tres propuestas importantes encima de las propuestas enumeradas en tu repositorio. -redirect_from: - - /articles/pinning-an-issue-to-your-repository - - /github/managing-your-work-on-github/pinning-an-issue-to-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -![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 %} -3. En la lista de propuestas, haz clic en la propuesta que deseas anclar. -4. En la barra lateral derecha, haz clic **Pin issue (Anclar una propuesta)**. ![Botón para anclar una propuesta](/assets/images/help/repository/pin-issue.png) diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/transferring-an-issue-to-another-repository.md deleted file mode 100644 index 51a2a22040..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/transferring-an-issue-to-another-repository.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Transferir una propuesta a otro repositorio -intro: 'Para mover una propuesta a un repositorio al que mejor se ajuste, puedes transferir propuestas abiertas a otros repositorios.' -redirect_from: - - /articles/transferring-an-issue-to-another-repository - - /github/managing-your-work-on-github/transferring-an-issue-to-another-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Para transferir una propuesta abierta a otro repositorio, debes tener permisos de escritura sobre el repositorio en el que está la propuesta y sobre el repositorio al que le estás transfiriendo la propuesta. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". - -Solo puedes transferir propuestas entre repositorios que son propiedad del mismo usuario o de la misma cuenta de la organización. No puedes transferir una propuesta desde un repositorio privado a un repositorio público. - -Cuando transfieres un informe de problemas, se retendrá tanto los comentarios como las personas asignadas. No se retendrán las etiquetas del informe{% if currentVersion ver_lt "enterprise-server@2.19" %}, proyectos, {% endif %}ni los hitos.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} Este informe de problemas se quedará en cualquiera de los tableros de proyecto que pertenezca a las organizaciones o los usuarios y se eliminará de cualquier tablero de proyecto de repositorio. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards)".{% endif %} - -Las personas o equipos que se mencionan en la propuesta recibirán una notificación que les haga saber que la propuesta se transfirió a un repositorio nuevo. La URL original se redirige a la URL nueva de la propuesta. Las personas que no tengan permisos de lectura en el repositorio nuevo verán un anuncio que les hará saber que la propuesta se transfirió a un repositorio nuevo al que no pueden acceder. - -### Transferir una propuesta abierta a otro repositorio - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issues %} -3. En la lista de propuestas, haz clic en la propuesta que quieres transferir. -4. En la barra lateral derecha, haz clic en **Transfer issue** (Transferir propuesta). ![Botón para transferir propuesta](/assets/images/help/repository/transfer-issue.png) -5. Utiliza el menú desplegable **Choose a repository** (Elegir un repositorio) y selecciona el repositorio al que quieres transferir la propuesta. ![Elige una selección de repositorio](/assets/images/help/repository/choose-a-repository.png) -6. Haz clic en **Transfer issue** (Transferir propuesta). ![Botón Transfer issue (Transferir propuesta)](/assets/images/help/repository/transfer-issue-button.png) - -### Leer más - -- "[Acerca de las propuestas](/articles/about-issues)" -- "[Revisar tu registro de seguridad](/articles/reviewing-your-security-log)" -- "[Revisar el registro de auditoría para tu organización](/articles/reviewing-the-audit-log-for-your-organization)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md deleted file mode 100644 index dec9a626a8..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/managing-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Ver todas tus propuestas y solicitudes de extracción -intro: 'Los tableros de propuestas y solicitudes de extracción enumeran las propuestas y solicitudes de extracción abiertas que has creado. Puedes utilizarlos para actualizar los elementos que se han puesto en espera, que has cerrado o que mantienes un registro de dónde has sido mencionado a lo largo de todos los repositorios (incluidos aquellos en los que no estás suscrito).' -redirect_from: - - /articles/viewing-all-of-your-issues-and-pull-requests - - /github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Tus tableros de propuestas y solicitudes de extracción están disponibles en la parte superior de cualquier página. En cada tablero, puedes filtrar la lista para encontrar propuestas y solicitudes de extracción que creaste, que están asignadas a ti o en las cuales estás mencionado. También puedes encontrar solicitudes de extracción que te han pedido que revises. - -1. En la partes superior de cualquier página, haz clic en **Pull requests (Solicitudes de extracción)** o **Issues (Propuestas)**. ![Tableros de solicitudes de extracción o propuestas globales](/assets/images/help/overview/issues_and_pr_dashboard.png) -2. Como alternativa, elige un filtro o [utiliza la barra de búsqueda para filtrar resultados más específicos](/articles/using-search-to-filter-issues-and-pull-requests). ![Lista de solicitudes de extracción con el filtro "Created" (Creado) seleccionado](/assets/images/help/overview/pr_dashboard_created.png) - -### Leer más - -- {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listar los repositorios que estás observando](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/about-milestones.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/about-milestones.md deleted file mode 100644 index febcd57d86..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/about-milestones.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Acerca de los hitos -intro: Puedes usar hitos para hacer un seguimiento del progreso en grupos de propuestas o solicitudes de extracción en un repositorio. -redirect_from: - - /articles/about-milestones - - /github/managing-your-work-on-github/about-milestones -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Cuando [creas un hito](/articles/creating-and-editing-milestones-for-issues-and-pull-requests), puedes [asociarlo con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests). - -Para administrar mejor tu proyecto, puedes [ver detalles acerca de tu hito](/articles/viewing-your-milestone-s-progress). Desde la página del hito, puedes ver lo siguiente: - -- Una descripción del hito proporcionada por el usuario, que puede incluir información como la descripción general del proyecto, los equipos relevantes y las fechas de vencimiento previstas. -- La fecha de vencimiento del hito. -- El porcentaje de finalización del hito. -- La cantidad de propuestas y solicitudes de extracción abiertas y cerradas asociadas con el hito. -- Una lista de las propuestas y las solicitudes de extracción abiertas y cerradas asociadas con el hito. - -Además, puedes editar el hito desde la página del hito y crear nuevas propuesta que estén, de forma predeterminada, asociadas con el hito. - -![Página del hito](/assets/images/help/issues/milestone-info-page.png) - -### Priorizar propuestas y solicitudes de extracción en hitos - -Puedes priorizar propuestas y solicitudes de extracción abiertas en un hito haciendo clic a la izquierda de la casilla de verificación de una propuesta o solicitud de extracción, arrastrándola a una nueva ubicación y colocándola ahí. - -{% note %} - -**Nota:** Si hay más de 500 propuestas abiertas en un hito, no podrás priorizar propuestas. - -{% endnote %} - -![Hito reordenado](/assets/images/help/issues/milestone-reordered.gif) - -### Leer más - -- "[Crear y editar hitos para propuestas y solicitudes de extracción](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)" -- "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" -- "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" -- "[Ver el progreso de tus hitos](/articles/viewing-your-milestone-s-progress)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/associating-milestones-with-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/associating-milestones-with-issues-and-pull-requests.md deleted file mode 100644 index 72865d59be..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/associating-milestones-with-issues-and-pull-requests.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Asociar hitos con propuestas y solicitudes de extracción -intro: Puedes asociar propuestas y solicitudes de extracción similares con un hito para realizar un mejor seguimiento de su progreso. -redirect_from: - - /articles/associating-milestones-with-issues-and-pull-requests - - /github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -3. Selecciona la casilla de verificación junto a los elementos que deseas asociar a un hito. ![Casilla de verificación de metadatos de propuestas](/assets/images/help/issues/issues_assign_checkbox.png) -4. En el margen superior derecho, haz clic en **Milestone** (Hito), luego comienza a escribir el nombre de un [hito existente](/articles/creating-and-editing-milestones-for-issues-and-pull-requests). Haz clic en el nombre del hito para asociarlo con el elemento. ![Desplegable de la asignación de hitos de propuestas](/assets/images/help/issues/issues_assigning_milestone_dropdown.png) - -{% tip %} - -A medida que trabajas en las propuestas y las solicitudes de extracción, puedes [realizar el seguimiento del progreso de tu hito](/articles/viewing-your-milestone-s-progress). - -{% endtip %} - -### Leer más - -- "[Acerca de los hitos](/articles/about-milestones)" -- "[Crear y editar hitos para propuestas y solicitudes de extracción](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)" -- "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests.md deleted file mode 100644 index b286a9a811..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Crear y editar hitos para propuestas y solicitudes de extracción -intro: Puedes crear un hito para hacer un seguimiento del progreso en grupos de propuestas o solicitudes de extracción en un repositorio. -redirect_from: - - /articles/creating-milestones-for-issues-and-pull-requests/ - - /articles/creating-and-editing-milestones-for-issues-and-pull-requests - - /github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -{% data reusables.project-management.milestones %} -4. Elige una de las siguientes opciones: - - Para crear un nuevo hito, haz clic en **Nuevo hito**. ![Botón Nuevo hito](/assets/images/help/repository/new-milestone.png) - - Para editar un hito, haz clic en **Editar** junto al hito que deseas editar. ![Opción Editar hito](/assets/images/help/repository/edit-milestone.png) -5. Escribe el título, la descripción y los demás cambios del hito, y luego haz clic en **Create milestone** (Crear hito) o **Save changes** (Guardar cambios). - -### Eliminar hitos - -Cuando eliminas hitos, las propuestas y las solicitudes de extracción no se ven afectadas. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -{% data reusables.project-management.milestones %} -4. Junto al hito que deseas eliminar, haz clic en **Eliminar**. ![Opción Eliminar hito](/assets/images/help/repository/delete-milestone.png) - -### Leer más - -- "[Acerca de los hitos](/articles/about-milestones)" -- "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" -- "[Ver el progreso de tus hitos](/articles/viewing-your-milestone-s-progress)" -- "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/filtering-issues-and-pull-requests-by-milestone.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/filtering-issues-and-pull-requests-by-milestone.md deleted file mode 100644 index de719dc9d0..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/filtering-issues-and-pull-requests-by-milestone.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Filtrar propuestas y solicitudes de extracción por hito -intro: 'Las propuestas y solicitudes de extracción se pueden filtrar según el hito con el que están asociadas. Una vez que has [asociado una propuesta o solicitud de extracción con un hito](/articles/associating-milestones-with-issues-and-pull-requests), puedes buscar elementos basados en sus hitos. Dentro de un hito, puedes priorizar las propuestas y solicitudes de extracción.' -redirect_from: - - /articles/filtering-issues-and-pull-requests-by-milestone - - /github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% tip %} - -**Sugerencias:** - -- Si prefieres filtrar propuestas y solicitudes de extracción usando la barra de búsqueda, puedes usar la sintaxis de búsqueda de hitos. Para un hito llamado My milestone, la sintaxis de búsqueda sería: `milestone:"My Milestone"`. -- Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda, filtros y clasificaciones actuales**. -- You can also filter issues or pull requests using the {% data variables.product.prodname_cli %}. For more information, see "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" or "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)" in the {% data variables.product.prodname_cli %} documentation. - -{% endtip %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -3. Selecciona **Hitos** para ver una lista de todos los hitos disponibles para el repositorio. ![Botón Hitos](/assets/images/help/issues/issues_milestone_button.png) -4. Selecciona el hito que te interesa en la lista. En la página del hito puedes ver información relevante sobre el hito, incluidas todas las propuestas y solicitudes de extracción asociadas con él. Para obtener más información, consulta "[Acerca de los hitos](/articles/about-milestones)". - -### Leer más - -- [Filtrar propuestas y solicitudes de extracción](/articles/filtering-issues-and-pull-requests)" -- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests)" -- "[Usar la búsqueda para filtrar propuestas y solicitudes de extracción](/articles/using-search-to-filter-issues-and-pull-requests)" -- "[Compartir filtros](/articles/sharing-filters)" -- "[Filtrar tarjetas en un tablero de proyecto](/articles/filtering-cards-on-a-project-board)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/index.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/index.md deleted file mode 100644 index 86d48215bc..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Rastrear el progreso de tu trabajo con hitos -intro: 'Puedes hacer el seguimiento de tu trabajo en {% data variables.product.product_name %} creando hitos con propuestas y solicitudes de extracción asociadas.' -redirect_from: - - /articles/tracking-the-progress-of-your-work-with-milestones -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /about-milestones - - /creating-and-editing-milestones-for-issues-and-pull-requests - - /associating-milestones-with-issues-and-pull-requests - - /filtering-issues-and-pull-requests-by-milestone - - /viewing-your-milestones-progress ---- - diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/viewing-your-milestones-progress.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/viewing-your-milestones-progress.md deleted file mode 100644 index f14edf146f..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/viewing-your-milestones-progress.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Ver el avance de tu hito -intro: 'Con el fin de rastrear tus hitos, querrás obtener una mejor comprensión de cuántas propuestas y solicitudes de extracción abiertas están pendientes.' -redirect_from: - - /articles/viewing-your-milestone-s-progress - - /articles/viewing-your-milestones-progress - - /github/managing-your-work-on-github/viewing-your-milestones-progress -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -3. En el ángulo superior izquierdo, haz clic en **Milestones (Hitos)**. ![Botón de propuestas del hito](/assets/images/help/issues/issues_milestone_button.png) -4. Selecciona el hito sobre el que deseas ver más información. - -![Resumen de propuestas del hito](/assets/images/help/issues/issues_milestone_overview.png) - -Para administrar mejor tu proyecto, puedes priorizar propuestas o solicitudes de extracción dentro de un hito. Para obtener más información, consulta "[Acerca de los hitos](/articles/about-milestones#prioritizing-issues-and-pull-requests-in-milestones)." - -### Leer más - -* "[Asociar hitos con propuestas y solicitudes de extracción](/articles/associating-milestones-with-issues-and-pull-requests)" -* "[Filtrar propuestas y solicitudes de extracción por hitos](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md deleted file mode 100644 index 8345b0a5c5..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Agregar propuestas y solicitudes de extracción a un tablero de proyecto -intro: Puedes agregar propuestas y solicitudes de extracción a un tablero de proyecto en la forma de tarjetas y jerarquizarlas en columnas. -redirect_from: - - /articles/adding-issues-and-pull-requests-to-a-project/ - - /articles/adding-issues-and-pull-requests-to-a-project-board - - /github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -Puedes agregar propuestas o tarjetas de solicitudes de extracción a un tablero de proyecto al: -- Arrastrar tarjetas desde la sección **Triage** (Jerarquizar) en la barra lateral. -- Escribir la propuesta o URL de solicitud de extracción en una tarjeta. -- Buscar las propuestas o solicitudes de extracción en la barra lateral de búsqueda del tablero de proyecto. - -Puedes poner un máximo de 2500 tarjetas en cada columna del proyecto. Si una columna ha alcanzado un número máximo de tarjetas, ninguna tarjeta puede moverse a esa columna. - -![El cursor mueve la tarjeta de propuestas desde la barra lateral de clasificación hasta la columna del tablero](/assets/images/help/projects/add-card-from-sidebar.gif) - -{% note %} - -**Nota:** También puedes agregar notas a tu tablero de proyecto para servir como recordatorios de tarea, referencias a propuestas y solicitudes de extracción desde un repositorio en {% data variables.product.product_name %}, o agregar información relacionada con tu tablero de proyecto. Para obtener más información, consulta "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)". - -{% endnote %} - -{% data reusables.project-management.edit-in-project %} - -{% data reusables.project-management.link-repos-to-project-board %} Cuando buscas propuestas y solicitudes de extracción para agregar a tu tablero de proyecto, la búsqueda automáticamente llega a tus repositorios relacionados. Puedes eliminar estos calificadores para buscar dentro de todos los repositorios de la organización. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". - -### Agregar propuestas y solicitudes de extracción a un tablero de proyecto - -1. Navegue hasta el tablero de proyecto donde deseas agregar propuestas y solicitudes de extracción. -2. En tu tablero de proyecto, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Add cards** (Agregar tarjetas). ![Agregar botón de tarjetas](/assets/images/help/projects/add-cards-button.png) -3. Buscar propuestas y solicitudes de extracción para agregar a tu tablero de proyecto mediante calificadores de búsqueda. Para más información sobre la búsqueda de calificadores que puedes usar, consulta "[Buscar propuestas](/articles/searching-issues)". ![Buscar propuestas y solicitudes de extracción](/assets/images/help/issues/issues_search_bar.png) - - {% tip %} - - **Sugerencias:** - - También puedes agregar una propuesta o solicitud de extracción al escribir la URL en una tarjeta. - - Si estás trabajando en una característica específica, puedes aplicar una etiqueta a cada propuesta relacionada o solicitud de extracción para esa característica, y luego agregar tarjetas fácilmente a tu tablero de proyecto al buscar por el nombre de la etiqueta. Para obtener más información, consulta "[Aplicar etiquetas a propuestas y solicitudes de extracción](/articles/applying-labels-to-issues-and-pull-requests)". - - {% endtip %} -4. En la lista filtrada de propuestas y solicitudes de extracción, arrastra la tarjeta que te gustaría agregar a tu tablero de proyecto y colócala en la columna correcta. Como alternativa, puedes mover las tarjetas usando los atajos del teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} - - {% tip %} - - **Sugerencia:** Puedes arrastrar y soltar o usar los atajos del teclado para reordenar las tarjetas y moverlas entre las columnas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} - - {% endtip %} - -### Agregar propuestas y solicitudes de extracción a un tablero de proyecto de la barra lateral - -1. En el lateral derecho de una propuesta o solicitud de extracción, haz clic en **Projects{% octicon "gear" aria-label="The Gear icon" %} (Proyectos**. ![Botón del tablero de proyecto en la barra lateral](/assets/images/help/projects/sidebar-project.png) -2. Da clic en la pestaña **Reciente**,**Repositorio**,**Usuario**, u **Organización** del tablero de proyecto que te gustaría agregar. ![Pestañas Recent (Reciente), Repository (Repositorio) y Organization (Organización)](/assets/images/help/projects/sidebar-project-tabs.png) -3. Escribe el nombre del proyecto en el campo **Filter projects** (Filtrar proyectos). ![Cuadro de búsqueda del tablero de proyecto](/assets/images/help/projects/sidebar-search-project.png) -4. Selecciona uno o más tableros de proyectos en los que quieras agregar la propuesta o solicitud de extracción. ![Selected project board](/assets/images/help/projects/sidebar-select-project.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -5. Click -{% octicon "triangle-down" aria-label="The down triangle icon" %}, then click the column where you want your issue or pull request. La tarjeta se moverá al final de la columna del tablero de proyecto que selecciones. - ![Menú Move card to column (Mover tarjeta a la columna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png) -{% else %} -5. En el lateral derecho de una propuesta o solicitud de extracción, escribe **PROJECT-BOARD-NAME (a la espera de prioridades)**. ![Enlace al tablero de proyecto](/assets/images/help/projects/sidebar-project-board-link.png) -6. En tu tablero de proyecto, haz clic en **{% octicon "plus" aria-label="The Plus icon" %} Add cards (1 new)** (Agregar tarjetas [1 nueva]). ![Agregar botón de tarjetas](/assets/images/help/projects/add-cards-pending-button.png) -7. Arrastra la tarjeta para tu propuesta o solicitud de extracción desde la sección **Triage** (Jerarquía) en la columna que desees en el tablero de proyecto. Como alternativa, puedes mover las tarjetas usando los atajos del teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} -{% endif %} - -### Leer más - -- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" -- "[Editar un tablero de proyecto](/articles/editing-a-project-board)" -- "[Filtrar tarjetas en un tablero de proyecto](/articles/filtering-cards-on-a-project-board)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board.md deleted file mode 100644 index cb72b334c7..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Agregar notas a tu tablero de proyecto -intro: Puedes agregar notas a tu tablero de proyecto para que funcionen como recordatorios de tareas o para agregar información relacionada con el tablero de proyecto. -redirect_from: - - /articles/adding-notes-to-a-project/ - - /articles/adding-notes-to-a-project-board - - /github/managing-your-work-on-github/adding-notes-to-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% tip %} - -**Sugerencias:** -- Puedes dar formato a tu nota usando la sintaxis de Markdown. Por ejemplo, puedes usar encabezados, enlaces, listas de tareas o emojis. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)". -- Puedes arrastrar y soltar o usar los atajos del teclado para reordenar las tarjetas y moverlas entre las columnas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} -- Tu tablero de proyecto debe tener al menos una columna antes de que puedas agregar notas. Para obtener más información, consulta "[Crear un tablero de proyecto](/articles/creating-a-project-board)". - -{% endtip %} - -Cuando agregas una URL para una propuesta, solicitud de extracción u otro tablero de proyecto para una nota, verás la vista previa en una tarjeta de resumen debajo de tu texto. - -![Tarjetas de tableros de proyecto mostrando una vista previa de una propuesta y otro tablero de proyecto](/assets/images/help/projects/note-with-summary-card.png) - -### Agregar notas a tu tablero de proyecto - -1. Desplázate hasta el tablero de proyecto donde quieres agregar notas. -2. En la columna en la que deseas agregar una nota, haz clic en {% octicon "plus" aria-label="The plus icon" %}. ![Icono de adición en el encabezado de la columna](/assets/images/help/projects/add-note-button.png) -3. Escribe tu nota, luego haz clic en **Add** (Agregar). ![Campo para escribir una nota y botón Add card (Agregar tarjeta)](/assets/images/help/projects/create-and-add-note-button.png) - - {% tip %} - - **Sugerencia:** Puedes hacer referencia a una propuesta o solicitud de extracción en tu nota al escribir su URL en la tarjeta. - - {% endtip %} - -### Convertir una nota en una propuesta - -Si has creado una nota y consideras que no es suficiente para tus necesidades, puedes convertirla en una propuesta. - -Cuando conviertes una nota en una propuesta, la propuesta se crea automáticamente usando el contenido de la nota. La primera línea de la nota será el título de la propuesta y cualquier información adicional de la nota se agregará a la descripción de la propuesta. - -{% tip %} - -**Sugerencia:** Puedes agregar el contenido en el cuerpo de tu nota para @mencionar a alguien, vincular otra propuesta o solicitud de extracción, y agregar un emoji. Estas características de formato Markdown de {% data variables.product.prodname_dotcom %} no son compatibles con las notas del tablero de proyecto, pero una vez que tu nota se convierte en una propuesta, aparecerán correctamente. Para obtener más información sobre cómo usar estas características, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)". - -{% endtip %} - -1. Desplázate hasta la nota que deseas convertir en propuesta. -{% data reusables.project-management.project-note-more-options %} -3. Haz clic en **Convert to issue** (Convertir en propuesta). ![Botón para convertir en propuesta](/assets/images/help/projects/convert-to-issue.png) -4. Si la tarjeta está en un tablero de proyecto en toda la organización, en el menú desplegable, elige el repositorio en el que deseas agregar la propuesta. ![Menú desplegable enumerando los repositorios donde puedes crear la propuesta](/assets/images/help/projects/convert-note-choose-repository.png) -5. Opcionalmente, edita el título de la propuesta completada previamente, y escribe el cuerpo de la propuesta. ![Campos para título y cuerpo de la propuesta](/assets/images/help/projects/convert-note-issue-title-body.png) -6. Haz clic en **Convert to issue** (Convertir en propuesta). -7. La nota se convertirá automáticamente en una propuesta. En el tablero de proyecto, la nueva tarjeta de propuesta estará en la misma ubicación que la nota anterior. - -### Editar o eliminar una nota - -1. Desplázate hasta la nota que deseas editar o eliminar. -{% data reusables.project-management.project-note-more-options %} -3. Para editar los contenidos de la nota, haz clic en **Edit note** (Editar nota). ![Botón para editar notas](/assets/images/help/projects/edit-note.png) -4. Para eliminar los contenidos de las notas, haz clic en **Delete note** (Eliminar nota). ![Botón para eliminar notas](/assets/images/help/projects/delete-note.png) - -### Leer más - -- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" -- "[Crear un tablero de proyecto](/articles/creating-a-project-board)" -- "[Editar un tablero de proyecto](/articles/editing-a-project-board)" -- "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board.md deleted file mode 100644 index 94dd9591ed..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Archivar tarjetas en un tablero de proyecto -intro: Puedes archivar tarjetas en un tablero de proyecto para organizar tu flujo de trabajo sin perder el contexto histórico de un proyecto. -redirect_from: - - /articles/archiving-cards-on-a-project-board - - /github/managing-your-work-on-github/archiving-cards-on-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -La automatización en tu tablero de proyecto no se aplica a las tarjetas del tablero de proyecto archivado. Por ejemplo, si cierras una propuesta en un archivo del tablero de proyecto, la tarjeta archivada no se mueve automáticamente a la columna "Done" (Listo). Cuando restauras una tarjeta del archivo del tablero de proyecto, la tarjeta volverá a la columna donde fue archivada. - -### Archivar tarjetas en un tablero de proyecto - -1. En un tablero de proyecto, busca la tarjeta que quieres archivar y luego haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Lista de opciones para editar una tarjeta del tablero de proyecto](/assets/images/help/projects/select-archiving-options-project-board-card.png) -2. Click **Archive**. ![Opción para seleccionar archivos desde el menú.](/assets/images/help/projects/archive-project-board-card.png) - -### Restaurar tarjetas en un tablero de proyecto desde la barra lateral - -{% data reusables.project-management.click-menu %} -2. Haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, luego haz clic en **View archive** (Ver archivo). ![Seleccionar la opción para ver el archivo desde el menú](/assets/images/help/projects/select-view-archive-option-project-board-card.png) -3. Encima de la tarjeta del tablero de proyecto que deseas desarchivar, haz clic en **Restore** (Restaurar). ![Seleccionar la restauración de la tarjeta del tablero de proyecto](/assets/images/help/projects/restore-card.png) diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/filtering-cards-on-a-project-board.md deleted file mode 100644 index 2fa60ea90f..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/filtering-cards-on-a-project-board.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Filtrar tarjetas en un tablero de proyecto -intro: Puedes filtrar las tarjetas en un tablero de proyecto para buscar tarjetas específicas o ver un subconjunto de tarjetas. -redirect_from: - - /articles/filtering-cards-on-a-project-board - - /github/managing-your-work-on-github/filtering-cards-on-a-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -En una tarjeta, puedes hacer clic en cualquier asignatario {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %}, hito,{% endif %} o etiqueta para filtrar el tablero de proyecto en función de ese calificador. Para borrar la búsqueda, puedes hacer clic otra vez en el mismo asignatario {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %}, hito,{% endif %} o etiqueta. - -También puedes usar la barra de búsqueda "Filtrar tarjetas" en la parte superior de cada tablero de proyecto para buscar tarjetas. Puedes filtrar tarjetas usando los siguientes calificadores de búsqueda en cualquier combinación, o simplemente escribir el texto que deseas buscar. - -- Filtrar tarjetas por autor usando `author:USERNAME` -- Filtrar tarjetas por asignatario usando `assignee:USERNAME` o `no:assignee` -- Filtrar tarjetas por etiqueta usando `label:LABEL`, `label:"MULTI-WORD LABEL NAME"` o `no:label`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -- Filtrar por hito usando `milestone:MY-MILESTONE`{% endif %} -- Filtrar tarjetas por estado usando `state:open`, `state:closed` o `state:merged` -- Filtrar por estado de revisión usando `review:none`, `review:required`, `review:approved`, o `review:changes_requested` -- Filtrar por comprobación de estado usando `status:pending`, `status:success` o `status:failure` -- Filtrar tarjetas por tipo usando `type:issue`, `type:pr` o `type:note` -- Filtrar tarjetas por estado y tipo usando `is:open`, `is:closed` o `is:merged` y `is:issue`, `is:pr` o `is:note` -- Filtrar tarjetas por informes de problemas que se enlazan con alguna solicitud de extracción mediante una referencia de cierre utilizando `linked:pr`{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- Filtrar tarjetas por repositorio en un tablero de proyecto de toda la organización utilizando `repo:ORGANIZATION/REPOSITORY`{% endif %} - -1. Dirígete al tablero de proyecto que contenga las tarjetas que desees filtrar. -2. Sobre las columnas de las tarjetas del proyecto, haz clic en la barra de búsqueda "Filtrar tarjetas" y escribe la consulta de búsqueda para filtrar las tarjetas. ![Barra de búsqueda Filtrar tarjetas](/assets/images/help/projects/filter-card-search-bar.png) - -{% tip %} - -**Sugerencia:** Puedes arrastrar y soltar las tarjetas filtradas o usar los atajos del teclado para moverlas entre las columnas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} - -{% endtip %} - -### Leer más - -- "[Acerca de los tablero de proyecto](/articles/about-project-boards)" -- "[Agregar propuestas y solicitudes de extracción a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[Agregar notas a un tablero de proyecto](/articles/adding-notes-to-a-project-board)" diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/index.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/index.md deleted file mode 100644 index 2dcdbb05b5..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Rastrear el progreso de tu trabajo con tableros de proyecto -intro: 'Puedes hacer el seguimiento y priorizar tu trabajo en {% data variables.product.product_name %} creando un tablero de proyecto con propuestas, solicitudes de extracción y notas asociadas.' -redirect_from: - - /articles/tracking-the-progress-of-your-work-with-projects/ - - /articles/tracking-the-progress-of-your-work-with-project-boards -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests -children: - - /adding-issues-and-pull-requests-to-a-project-board - - /adding-notes-to-a-project-board - - /tracking-progress-on-your-project-board - - /filtering-cards-on-a-project-board - - /archiving-cards-on-a-project-board ---- - diff --git a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/tracking-progress-on-your-project-board.md b/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/tracking-progress-on-your-project-board.md deleted file mode 100644 index ea24e65d70..0000000000 --- a/translations/es-XL/content/github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/tracking-progress-on-your-project-board.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Rastrear el progreso en tu tablero de proyecto -intro: 'Por defecto, cuando habilitas la automatización en un tablero de proyecto, se hace el seguimiento del progreso general del proyecto en una barra de progreso.' -redirect_from: - - /articles/tracking-progress-on-your-project-board - - /github/managing-your-work-on-github/tracking-progress-on-your-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Pull requests ---- -{% data reusables.project-management.project-progress-locations %} - -1. Navega hasta el tablero de proyecto en el que quieres inhabilitar el seguimiento del progreso del proyecto. -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -4. Anula la selección de **Track project progress** (Rastrear progreso del proyecto). diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-email-notifications.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-email-notifications.md deleted file mode 100644 index cdff7615a6..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-email-notifications.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Acerca de las notificaciones por correo electrónico -intro: 'Cuando activas las notificaciones por correo electrónico, recibirás notificaciones de participación y de observación en tu cliente de correo electrónico y puedes filtrarlas usando la información del encabezado del correo electrónico.' -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/about-email-notifications ---- -Para obtener más información acerca de las diferencias entre las notificaciones de *participar* y *observar*, consulta la sección [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)". - -Después de activar las notificaciones por correo electrónico, {% data variables.product.product_name %} te enviará notificaciones como correos electrónicos con varias partes que contienen copias del contenido tanto en HTML como en texto simple. El contenido de las notificaciones por correo electrónico incluye cualquier Markdown, @menciones, emojis, vínculos hash, etc., que aparecen en el contenido original en {% data variables.product.product_name %}. Si solo quieres ver el texto en el correo electrónico, puedes configurar tu cliente de correo electrónico para que muestre solo la copia de texto simple. Para obtener más información acerca de habilitar las notificaciones por correo electrónico, consulta la sección "[Elegir el método de entrega de tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". - -{% data reusables.notifications.outbound_email_tip %} - -{% data reusables.notifications.shared_state %} - -### Filtrar las notificaciones por correo electrónico - -Cada notificación por correo electrónico que envía {% data variables.product.product_name %} contiene información de encabezado. La información del encabezado en cada correo electrónico es consistente, para que puedas usarla en tu cliente de correo electrónico para filtrar o enviar todas las notificaciones de {% data variables.product.product_name %} o ciertos tipos de notificaciones de {% data variables.product.product_name %}. - -Las notificaciones por correo electrónico de {% data variables.product.product_name %} contienen la siguiente información de encabezado: - -| Encabezado | Información | -| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| dirección `De` | Esta dirección siempre será la dirección de correo electrónico de tipo "no-reply" que configure tu administrador de sitio. | -| campo `Para` | Este campo se conecta directamente con el hilo de correo. Si respondes al correo electrónico, agregarás un nuevo comentario a la conversación. | -| dirección `Cc` | {% data variables.product.product_name %} te enviará `Cc` si estás suscripto a una conversación. La segunda dirección de correo electrónico `Cc` coincide con el motivo de la notificación. El sufijo para estos motivos de notificación es {% data variables.notifications.cc_address %}. Los posibles motivos de notificación son:
    • `assign`: Te asignaron a una propuesta o solicitud de extracción.
    • `author`: Creaste una propuesta o solicitud de extracción.
    • `comment`: Comentaste una propuesta o solicitud de extracción.
    • `manual`: Hubo una actualización de una propuesta o solicitud de extracción a la que te suscribiste de forma manual.
    • `mention`: Te mencionaron en una propuesta o solicitud de extracción.
    • `push`: Alguien confirmó una solicitud de extracción a la que estás suscripto.
    • `review_requested`: Te solicitaron a tí o a un equipo del que eres miembro revisar una solicitud de extracción.
    • `security_alert`: {% data variables.product.prodname_dotcom %} detectó una vulnerabilidad en un repositorio para el que recibes alertas de seguridad.
    • `state_change`: Se cerró o se abrió una propuesta o solicitud de extracción a la que estás suscripto.
    • `subscribed`: Hubo una actualización en un repositorio que estás mirando.
    • `team_mention`: Un equipo al que perteneces fue mencionado en una propuesta o solicitud de extracción.
    • `your_activity`: Abriste, comentaste en o cerraste una propuesta o solicitud de extracción.
    | -| Campo `mailing list` (lista de correos) | Este campo identifica el nombre del repositorio y su propietario. El formato de esta dirección siempre es `..{% data variables.command_line.backticks %}`. |{% if currentVersion ver_gt "enterprise-server@2.19" % %} -| Campo `X-GitHub-Severity` | {% data reusables.repositories.security-alerts-x-github-severity %} Los posibles niveles de gravedad son:
    • `low`
    • `moderate`
    • `high`
    • `critical`
    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)". |{% endif %} - -### Leer más - -- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" -- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" -- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)"{% if currentVersion ver_gt "enterprise-server@2.17" %} -- "[Crear gists](/articles/creating-gists)"{% endif %} diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-notifications.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-notifications.md deleted file mode 100644 index 2206a1c742..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-notifications.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Acerca de las notificaciones -intro: 'Las notificaciones ofrecen actualizaciones acerca de las actividades y las conversaciones en las que estás interesado. Puedes recibir notificaciones en {% data variables.product.product_name %} o mediante tu cliente de correo electrónico.' -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/about-notifications ---- -### Tipos de notificaciones - -Las notificaciones que recibes serán notificaciones de *participación* o notificaciones de *observación*. Ambos tipos de notificaciones se pueden recibir como notificaciones web o notificaciones por correo electrónico. Para obtener más información, consulta: - -- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" -- "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" -- "[Escoger el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" - -{% data reusables.notifications.outbound_email_tip %} - -{% data reusables.notifications.shared_state %} - -#### Notificaciones de participación - -{% data variables.product.product_name %} envía notificaciones de *participación* cuando estás directamente involucrado en las actividades o las conversaciones dentro de un repositorio o equipo del que eres miembro. Recibirás una notificación si: - - Te mencionan a tí o a un equipo del que eres miembro. Para obtener más información, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)". - - Se menciona al equipo padre de un equipo hijo del que eres miembro. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". - - Eres asignado a una propuesta o solicitud de extracción. - - Se agrega un comentario en una conversación a la cual estás suscripto. - - Se realiza una confirmación de una solicitud de extracción a la que estás suscripto. - - Abres, comentas o cierras una propuesta o una solicitud de extracción. - - Se envía una revisión que aprueba o solicita cambios en una solicitud de extracción a la que estás suscripto. - - Se te solicita a tí o a un equipo del que eres miembro revisar una solicitud de extracción. - - Se te designa a tí o a un equipo del que eres miembro como propietario de un archivo y alguien abre una solicitud de extracción que modifica ese archivo. Para obtener más información, consulta "[Acerca de los propietarios del código](/articles/about-code-owners)." - - Creas o respondes a un debate de equipo. - -#### Notificaciones de observación - -{% data variables.product.product_name %} envía notificaciones de *observación* para actualizaciones en repositorios o debates de equipos que estés mirando. {% if currentVersion ver_gt "enterprise-server@2.17" %}{% data reusables.notifications.auto-watch %}Para obtener más información, consulta la sección "[Observar y dejar de observar los repositorios](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)". - -{% endif %}Recibirás una notificación si: - - Se abre una propuesta. - - Se agrega un comentario a una propuesta abierta. - - Se abre una solicitud de extracción. - - Se agrega un comentario a una solicitud de extracción abierta. - - Se agrega un comentario a una confirmación de cambios. - - Se publica un lanzamiento. Para obtener más información, consulta "[Acerca de los lanzamientos](/articles/about-releases)." También puedes ver solo los lanzamientos publicados en un repositorio, en lugar de todas las actualizaciones de un repositorio. Para obtener más información, consulta la sección "[Observar y dejar de observar los lanzamientos para un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository)". - - Se envía una revisión que aprueba o solicita cambios en una solicitud de extracción. - - Se crea o se responde a una publicación de un debate de equipo para un equipo que estás mirando. - - Se abre, se edita o se responde a una publicación de un debate de equipo para un equipo padre o un equipo del que eres miembro y estás mirando. Para obtener más información, consulta "[Equipos anidados](/articles/about-teams/#nested-teams)". - -También puedes explorar las actividades de las personas que sigues, los repositorios que miras y las organizaciones de las que eres miembro en tu tablero. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". - -### Leer más - -- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" -- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" -- "[Observar y dejar de observar los debates de equipo](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions)" -- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-web-notifications.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-web-notifications.md deleted file mode 100644 index ddef3bf3d0..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/about-web-notifications.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Acerca de las notificaciones web -intro: 'Si estás recibiendo notificaciones web, puedes ver tus notificaciones de participación y de observación en la página de notificaciones en {% data variables.product.product_name %}.' -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/about-web-notifications ---- -Para obtener más información acerca de las diferencias entre las notificaciones de *participar* y *observar*, consulta la sección [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)". - -Cuando las notificaciones web están activadas para tu cuenta, puedes hacer clic en un elemento en tu página de notificaciones y serás redirigido a la conversación a la que hace referencia la notificación. Cuando las notificaciones web están activadas para tu cuenta, puedes hacer clic en un elemento en tu página de notificaciones y serás redirigido a la conversación a la que hace referencia la notificación. Para obtener más información sobre habilitar las notificaciones web, consulta la sección "[Elegir el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". - -{% data reusables.notifications.shared_state %} - -Desde la página de notificaciones, también puedes marcar las notificaciones como leídas, guardar las notificaciones para más adelante y cancelar la suscripción a los hilos. Para obtener más información, consulta: - -- "[Marcar las notificaciones como leídas](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read)" -- "[Guardar las notificaciones para después](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/saving-notifications-for-later)" -- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" - -### Leer más - -- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" -- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" -- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/accessing-your-notifications.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/accessing-your-notifications.md deleted file mode 100644 index 01d168fea0..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/accessing-your-notifications.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Acceder a tus notificaciones -intro: 'Según el modo en que se configuró tu entrega de notificaciones, puedes acceder a tus notificaciones en {% data variables.product.product_name %} o a través de tu cliente de correo electrónico.' -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/accessing-your-notifications ---- -### Acceder a tus notificaciones web - -Para acceder a las notificaciones web en {% data variables.product.product_name %}, debes tener las notificaciones web habilitadas. Para obtener más información, consulta la sección "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" y "[Elegir el método de entrega de tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". - -{% data reusables.notifications.access_notifications %} -2. En la barra lateral izquierda, para ver todas las notificaciones de las actividades en las que estás participando, haz clic en **Participating** (Participación). ![Enumerar las notificaciones de participación](/assets/images/help/notifications/notifications_sidebar_participating.png) -3. En la barra lateral izquierda, haz clic en el nombre de un repositorio para ver las notificaciones de un repositorio específico. ![Enumerar las notificaciones de repositorio individual](/assets/images/help/notifications/notifications_sidebar_specific_repos.png) - -### Acceder a tus notificaciones por correo electrónico - -Si tienes configuradas las notificaciones por correo electrónico, puedes acceder a tus notificaciones a través de tu cliente de correo electrónico. Para obtener más información sobre habilitar las notificaciones por correo electrónico, consulta la sección "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" y "[Elegir el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". - -### Leer más - -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/choosing-the-delivery-method-for-your-notifications.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/choosing-the-delivery-method-for-your-notifications.md deleted file mode 100644 index f61ae0a850..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/choosing-the-delivery-method-for-your-notifications.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Elegir el método de entrega para tus notificaciones -intro: 'Puedes recibir tus notificaciones en {% data variables.product.product_location %} o recibirlas mediante tu cliente de correo electrónico.' -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications ---- -Para las cuentas personales, los correos electrónicos de notificación se envían automáticamente a tu correo electrónico de notificación predeterminado. - -{% data reusables.notifications.outbound_email_tip %} - -### Elegir el método de entrega para notificaciones sobre la actividad del repositorio - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.notifications %} -3. Configura cómo deseas recibir las notificaciones en las que participas u observas al seleccionar las casillas de verificación: - - Si seleccionas **Email** (Correo electrónico) se envía un correo electrónico a tu correo electrónico predeterminado. - - Si seleccionas **Web** podrás acceder a las notificaciones en {% data variables.product.product_location %}. ![Configurar ajustes de notificaciones](/assets/images/help/settings/ent-notifications-settings.png) -4. Si seleccionaste **Email** (Correo electrónico) para conversaciones en las que participas u observas, elige qué actualizaciones recibirás al seleccionar las casillas de verificación en la sección "Notification email" (Correo electrónico de notificación): - - Selecciona **Comments on Issues and Pull Requests** (Comentarios sobre propuestas y solicitudes de extracción) para recibir un correo electrónico cuando alguien realiza un comentario en una propuesta en la pestaña "Conversation" (Conversación) de una solicitud de extracción. - - Selecciona **Pull request reviews** (Revisiones de solicitudes de extracción) para recibir un correo electrónico cuando alguien realiza un comentario de revisión en la pestaña "Files changed" (Archivos cambiados) de una solicitud de extracción. - - Selecciona **Pull request pushes** (Impulsos de solicitud de extracción) para recibir un correo electrónico cuando alguien agrega confirmaciones a una solicitud de extracción a la que te suscribiste. - - Selecciona **Include your own updates** (Incluir tus propias actualizaciones) para recibir un correo electrónico cuando abras, comentes o cierres una propuesta o solicitud de extracción. ![Configurar opciones de notificación por correo electrónico](/assets/images/help/settings/email_notification_settings.png) - -### Elegir el método de entrega para alertas de seguridad para dependencias vulnerables - -{% data reusables.repositories.security-alert-delivery-options %} - -{% data reusables.repositories.enable-security-alerts %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.notifications %} -3. Debajo de "Alertas de seguridad", configura cómo te gustaría recibir las notificaciones cuando {% data variables.product.product_name %} detecte una dependencia vulnerable en tu repositorio: ![Opciones para configurar notificaciones para alertas de seguridad](/assets/images/help/settings/vulnerability-alerts-options.png) - - Si seleccionas **UI alerts** (Alertas de UI) muestra un mensaje emergente en la interfaz de {% data variables.product.product_name %}. - - Si seleccionas **Command Line** (Línea de comando) muestra advertencias como una devolución cuando subes a un repositorio con vulnerabilidades. - - Si seleccionas **Web** podrás acceder a las notificaciones en {% data variables.product.product_location %}. - - Si seleccionas **Email each time a vulnerabilidad is found** (Enviar un correo electrónico cada vez que se encuentra una vulnerabilidad) se envía un correo electrónico a tu correo electrónico predeterminado. - - Si seleccionas **Email a digest summary of vulnerabilities** (Enviar un correo electrónico con un resumen de vulnerabilidades) envía un correo electrónico condensado con un resumen de hasta 10 alertas de seguridad de los repositorios. Usa el menú desplegable para recibir correos electrónicos condensados diariamente o semanalmente. - -### Leer más - -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" -- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" -- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" -- "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/index.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/index.md deleted file mode 100644 index 61ec1d51d0..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/getting-started-with-notifications/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Comenzar con las notificaciones -intro: 'Las notificaciones te ayudan a hacer un seguimiento de las conversaciones y las actualizaciones que te interesan. Puedes recibir notificaciones en {% data variables.product.product_name %} o a través de tu cliente de correo electrónico sobre conversaciones en las que estás participando o actualizaciones que estás observando.' -versions: - enterprise-server: <2.21 -children: - - /about-notifications - - /about-web-notifications - - /about-email-notifications - - /accessing-your-notifications - - /choosing-the-delivery-method-for-your-notifications ---- - diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/index.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/index.md deleted file mode 100644 index a202a086b2..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Recibir notificaciones acerca de la actividad en GitHub -versions: - enterprise-server: <2.21 -children: - - /getting-started-with-notifications - - /managing-your-notifications ---- -### Índice - - - - - - diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/index.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/index.md deleted file mode 100644 index 82cea3f6f4..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Administrar tus notificaciones -intro: 'Para que sea más sencillo recibir las notificaciones que te interesan, puedes marcar notificaciones como leer, suscribir y cancelar la suscripción de notificaciones y ver y dejar de ver repositorios.' -versions: - enterprise-server: <2.21 -children: - - /marking-notifications-as-read - - /saving-notifications-for-later - - /subscribing-to-and-unsubscribing-from-notifications - - /listing-the-issues-and-pull-requests-youre-subscribed-to - - /watching-and-unwatching-repositories - - /watching-and-unwatching-releases-for-a-repository - - /watching-and-unwatching-team-discussions - - /listing-the-repositories-youre-watching ---- - diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/listing-the-issues-and-pull-requests-youre-subscribed-to.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/listing-the-issues-and-pull-requests-youre-subscribed-to.md deleted file mode 100644 index a60b1afcaf..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/listing-the-issues-and-pull-requests-youre-subscribed-to.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Detallar las propuestas y las solicitudes de extracción a las que estás suscrito -intro: 'Puedes ver un resumen de todas las propuestas y solicitudes de extracción a las que estás suscrito. Esto simplifica la navegación hacia las conversaciones que te interesan, pero sobre las que no has recibido notificaciones recientes.' -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to ---- -La lista de suscripciones no incluye todas las propuestas y solicitudes de extracción de los repositorios que estás observando. Puedes suscribirte de forma manual a una propuesta o solicitud de extracción específica para incluirla en tu lista de suscripciones. Para obtener más información consulta la sección "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" y "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)". - -### Ver una lista de tus suscripciones - -1. En la esquina superior derecha de cualquier página, haz clic en {% octicon "bell" aria-label="The notifications bell" %}. Si inhabilitaste las notificaciones web y no ves el icono de la campana, puedes navegar hasta . Para obtener más información, consulta la sección "[Escoger el método de entrega para las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)". ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) -2. Da clic en **Suscripciones** ![Pestaña Subscriptions (Suscripciones)](/assets/images/help/notifications/subscriptions-tab.png) - -### Cancelar la suscripción desde propuestas y solicitudes de extracción - -Puedes cancelar la suscripción desde propuestas y solicitudes de extracción directamente desde tu lista de suscripciones. - -1. A la izquierda de cada propuesta o solicitud de extracción de la que quieras cancelar la suscripción, selecciona la casilla. ![Casilla para cancelar la suscripción](/assets/images/help/notifications/unsubscribe-checkbox.png) -2. En la esquina superior derecha de la página, haz clic en **Unsubscribe** (Cancelar suscripción). ![Botón Unsubscribe (Cancelar suscripción)](/assets/images/help/notifications/unsubscribe-button.png) diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/listing-the-repositories-youre-watching.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/listing-the-repositories-youre-watching.md deleted file mode 100644 index aaf613336c..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/listing-the-repositories-youre-watching.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Detallar los repositorios que estás observando -intro: Puedes obtener un resumen de todos los repositorios que estés observando para poder eliminar fácilmente cualquiera del que ya no te interese recibir notificaciones. -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching ---- -{% data reusables.notifications.access_watching %} -2. Haz clic en **Watching** (Ver) para ver la lista de repositorios que estás observando. ![Lista de repositorios observados](/assets/images/help/notifications/notifications-watching-tab.png) -3. Da clic en **Dejar de Seguir** o en **Dejar de seguir los lanzamientos** junto al repositorio del que ya no quieras recibir notificaciones. - -### Leer más - -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" - -- "[Ver todas tus propuestas y solicitudes de extracción](/articles/viewing-all-of-your-issues-and-pull-requests)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/marking-notifications-as-read.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/marking-notifications-as-read.md deleted file mode 100644 index 22ac8dab20..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/marking-notifications-as-read.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Marcar notificaciones como leídas -intro: 'Puedes marcar notificaciones web como leídas sin revisarlas. Si se realiza una actualización a la conversación, recibirás una nueva notificación. También puedes marcar las notificaciones leídas como no leídas, para que las puedas encontrar fácilmente despues.' -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/marking-notifications-as-read ---- -Para obtener más información acerca de cómo acceder a tus notificaciones web, consulta "[Acceder a tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications)". - -### Marcar una notificación como leída - -{% data reusables.notifications.access_notifications %} -1. En la lista de notificaciones no leídas, encuentra la notificación que desearías marcar como leída. -1. En el lateral derecho de la notificación, haz clic en {% octicon "check" aria-label="The check symbol" %}. ![Botón para marcar una notificación única como leída](/assets/images/help/notifications/notifications_mark_individual_as_read.png) - -### Marcar una notificación como no leída - -{% data reusables.notifications.access_notifications %} -1. En la barra lateral izquierda, haz clic en **Read (Leída)**. ![Botón de todas las notificaciones](/assets/images/help/notifications/sidebar_read_notifications.png) -1. En la lista de notificaciones leídas, encuentra la notificación que desearías marcar como no leída. -1. En el lateral derecho de la notificación, haz clic en {% octicon "dot-fill" aria-label="The dot symbol" %}. ![Botón para marcar una notificación como leída](/assets/images/help/notifications/notifications_mark_individual_as_unread.png) - -### Marcar todas las notificaciones como leídas - -{% data reusables.notifications.access_notifications %} -1. En la esquina superior derecha de la página, haz clic en **Mark all as read (Marcar todas como leídas)**. ![Botón para marcar todas las notificaciones como leídas](/assets/images/help/notifications/notifications_mark_all_as_read.png) - -### Marcar todas las notificaciones de un repositorio como leídas - -{% data reusables.notifications.access_notifications %} -1. En la barra lateral izquierda, haz clic en el nombre del repositorio para el cual desearías marcar todas las notificaciones como leídas. -1. En la lista de notificaciones, en el lateral derecho del nombre del repositorio, haz clic en {% octicon "check" aria-label="The check symbol" %}. ![Botón para marcar todas las notificaciones de un repositorio como leídas](/assets/images/help/notifications/notifications_repositories_mark_all_as_read.png) - -### Leer más - -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/saving-notifications-for-later.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/saving-notifications-for-later.md deleted file mode 100644 index d4d8d1f92c..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/saving-notifications-for-later.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Guardar notificaciones para más tarde -intro: Puedes guardar notificaciones web para hacerles un seguimiento posterior. -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/saving-notifications-for-later ---- -Cuando guardas una notificación, se mueve a la pestaña Saved for later (Guardado para más tarde) en tu página de notificaciones. Para obtener más información, consulta la sección "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)". - -### Guardar una notificación para más tarde - -{% data reusables.notifications.access_notifications %} -1. En la lista de notificaciones, encuentra la notificación que deseas guardar para más tarde. -1. On the right side of the notification, click -{% octicon "bookmark" aria-label="The bookmark button" %}. -![Botón para guardar una notificación](/assets/images/help/notifications/save_notification.png) -{% data reusables.notifications.saved_for_late_sidebar %} - -### Eliminar una notificación guardada - -{% data reusables.notifications.access_notifications %} -{% data reusables.notifications.saved_for_late_sidebar %} -1. En tu lista de notificaciones guardadas, encuentra la notificación guardada que desearías eliminar. -1. En el lateral derecho de la notificación guardada, haz clic en {% octicon "bookmark" aria-label="The bookmark button" %}. ![Botón para eliminar una notificación guardada](/assets/images/help/notifications/remove-saved-notification.png) - -### Leer más - -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Acceder a tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/accessing-your-notifications)" -- "[Marcar las notificaciones como leídas](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/marking-notifications-as-read)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/subscribing-to-and-unsubscribing-from-notifications.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/subscribing-to-and-unsubscribing-from-notifications.md deleted file mode 100644 index 53d771a80d..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/subscribing-to-and-unsubscribing-from-notifications.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Suscribirse y cancelar las suscripciones de las notificaciones -intro: 'Puedes suscribirte a conversaciones individuales en propuestas, solicitudes de extracción y debates de equipo, incluso si no estás observando el repositorio o un miembro del equipo donde se está dando el debate. Si ya no estás interesado en una conversación, puedes cancelar la suscripción o personalizar los tipos de notificaciones que recibes.' -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications ---- -### Administrar tus configuraciones de notificación para una propuesta o solicitud de extracción - -{% if currentVersion ver_lt "enterprise-server@2.18" %}Cuando te subscribes a una conversación en una propuesta o solicitud de extracción, recibirás notificaciones de cada actualización de la conversación incluso si no estás participando en ella. - -Cuando cancelas la suscripción de una conversación en una propuesta o solicitud de extracción, ya no recibes notificaciones sobre ella. Si tú o un equipo del que eres miembro son mencionados en la conversación, comenzarán nuevamente a recibir notificaciones. Para obtener más información acerca de menciones, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)".{% endif %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -3. Elige una propuesta o solicitud de extracción a la que suscribirte. -{% if currentVersion ver_gt "enterprise-server@2.17" %} -4. En el barra lateral derecha, haz clic en **Subscribe (Suscribirse)** o **Unsubscribe (Cancelar la suscripción)**. ![Botón para suscribirte a una conversación](/assets/images/help/notifications/subscribe_button_with_gear.png) -5. Para personalizar tus notificaciones, haz clic en {% octicon "gear" aria-label="The gear icon" %}. ![Botón de ajustes al lado de Suscribirse a una conversación](/assets/images/help/notifications/subscribe_button_with_gear_chosen.png) -6. Selecciona el tipo de notificaciones que deseas recibir de esta conversación, después haz clic en **Save (Guardar)**. ![Lista de opciones para suscribirse a una conversación](/assets/images/help/notifications/subscribe_options.png) -{% else %} -4. Para suscribirse o cancelar la suscripción a una conversación, en la barra lateral derecha, haz clic en **Subscribe** (Suscribirse) o **Unsubscribe** (Cancelar la suscripción). ![Botón para suscribirte a una conversación](/assets/images/help/notifications/subscribe_button.png) -{% endif %} -Puedes ver una lista de todas las propuestas y solicitudes de extracción a las que estás suscrito. Para obtener más información, consulta la sección "[ Listar los informes de problemas y solicitudes de extracción a los que estás suscrito](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-issues-and-pull-requests-youre-subscribed-to)". - -### Suscribirte a debates de equipo - -{% data reusables.organizations.team-discussions-are-for-orgs %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -5. En la página del equipo, encuentra el debate al que deseas suscribirte. -6. En el ángulo superior derecho del debate, haz clic en {% octicon "unmute" aria-label="The subscribe symbol" %} para suscribirte al debate. ![Botón para suscribirse a un debate de equipo](/assets/images/help/notifications/team-discussion-subscribe-button.png) - -### Cancelar la suscripción a debates de equipo - -{% data reusables.organizations.team-discussions-are-for-orgs %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -5. En la página del equipo, encuentra el debate del que deseas cancelar la suscripción. -6. En el ángulo superior derecho del debate, haz clic en {% octicon "mute" aria-label="The unsubscribe symbol" %} para cancelar la suscripción al debate. ![Botón para suscribirse a un debate de equipo](/assets/images/help/notifications/team-discussion-unsubscribe-button.png) - -### Leer más - -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Acerca de los debates en {% data variables.product.product_name %}](/articles/about-conversations-on-github)" -- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" - -- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-releases-for-a-repository.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-releases-for-a-repository.md deleted file mode 100644 index 1f970782d2..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-releases-for-a-repository.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Ver y dejar de ver los lanzamientos de un repositorio -intro: Puedes ver lanzamientos en un repositorio para recibir notificaciones cuando un nuevo lanzamiento se publica sin recibir notificaciones sobre otras actualizaciones en el repositorio. También puedes dejar de ver lanzamientos si ya no deseas recibir notificaciones de nuevos lanzamientos en un repositorio. -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository ---- -### Ver lanzamientos en un repositorio - -{% data reusables.repositories.navigate-to-repo %} -2. En el ángulo superior derecho, haz clic en **Releases only (Solo lanzamientos)** desde el menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para lanzamientos](/assets/images/help/notifications/watch-releases.png) - -### Dejar de ver lanzamientos en un repositorio - -{% data reusables.repositories.navigate-to-repo %} -2. En el ángulo superior derecho, haz clic en **Not watching (Dejar de ver)** desde el menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para lanzamientos](/assets/images/help/notifications/unwatch-repository.png) - -### Leer más - -- "[Acerca de los lanzamientos](/articles/about-releases)" -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Observar y dejar de observar un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-repositories.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-repositories.md deleted file mode 100644 index c22a951099..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-repositories.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Ver y dejar de ver repositorios -intro: Puedes ver un repositorio para recibir notificaciones por las nuevas solicitudes de extracción y propuestas que se crearon. También puedes dejar de ver un repositorio si ya no deseas recibir notificaciones de ese repositorio específico. -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories ---- -{% if currentVersion ver_gt "enterprise-server@2.17" %} -{% data reusables.notifications.auto-watch %} Para obtener más información, consulta la sección "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)". -{% endif %} - -You can also watch and unwatch releases in a repository. Para obtener más información, consulta la sección "[Observar y dejar de observar los lanzamientos para un repositorio](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository)". - -### Ver todos los repositorios a los que tienes acceso de escritura - -{% data reusables.notifications.access_watching %} -2. Click **Watching**. ![Lista de repositorios observados](/assets/images/help/notifications/notifications-watching-tab.png) -3. En el lateral derecho de la página, selecciona **Automatically watch (Ver automáticamente)**. ![Una casilla de verificación para configurar ver automáticamente repositorios](/assets/images/help/notifications/ent-automatically-watch-repos.png) - -### Ver un repositorio único - -{% data reusables.repositories.navigate-to-repo %} -2. En el ángulo superior derecho, haz clic en **Watching (Ver)** del menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications/watch-repository.png) - -### Dejar de ver todos los repositorios a los que tienes acceso de escritura - -{% data reusables.notifications.access_watching %} -2. Click **Watching**. ![Lista de repositorios observados](/assets/images/help/notifications/notifications-watching-tab.png) -3. En el lateral derecho de la página, deselecciona **Automatically watch (Ver automáticamente)**. ![Una casilla de verificación para configurar ver automáticamente repositorios](/assets/images/help/notifications/ent-automatically-watch-repos.png) - -### Dejar de ver un repositorio único - -{% data reusables.repositories.navigate-to-repo %} -2. En el ángulo superior derecho, haz clic en **Unwatch (Dejar de ver)** desde el menú desplegable "Watch" (Ver). ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications/unwatch-repository.png) - -{% note %} - -**Nota:** también puedes elegir ignorar un repositorio. Si ignoras un repositorio, no recibirás ninguna notificación. No recomendamos ignorar repositorios ya que no se te notificará si eres mencionado. {% if currentVersion == "free-pro-team@latest" %}Si sufres abuso y deseas ignorar un repositorio, [contacta a Soporte](/contact) así podemos ayudarte. {% data reusables.policies.abuse %}{% endif %} - -{% endnote %} - -### Leer más - -- "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)" -- "[Listar los repositorios que estás observando](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching)" diff --git a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-team-discussions.md b/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-team-discussions.md deleted file mode 100644 index 8b07cc7897..0000000000 --- a/translations/es-XL/content/github/receiving-notifications-about-activity-on-github/managing-your-notifications/watching-and-unwatching-team-discussions.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Ver y dejar de ver debates de equipo -intro: Puedes ver un equipo para recibir notificaciones de los debates del equipo. Puedes dejar de ver un equipo si ya no quieres recibir notificaciones de los debates de ese equipo. -versions: - enterprise-server: <2.21 -redirect_from: - - /github/receiving-notifications-about-activity-on-github/watching-and-unwatching-team-discussions ---- -Por defecto, recibirás automáticamente notificaciones de los debates del equipo del que eres miembros. Si no quieres recibir determinadas notificaciones para un debate de equipo existente, debes dejar de ver ese equipo. También puedes cancelar la suscripción o suscribirte a publicaciones de debates de equipo específicas. Para obtener más información, consulta la sección "[Acerca de los debates de equipo](/articles/about-team-discussions)" y "[Suscribirse y desuscribirse de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications)." - -Si no deseas ver automáticamente debates de equipo cuando te conviertes en miembro de equipos nuevos, puedes actualizar tus configuraciones automáticas de observación. - -### Ver los debates de todos los equipos nuevos a los que te unes - -Para ver automáticamente todos los debates de los equipos nuevos a los que te unes, configura tus parámetros de notificaciones automáticas de observación. - -{% note %} - -**Nota:** por defecto, esta configuración se realiza para **Automatically watching teams (Ver automáticamente equipos)**. - -{% endnote %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.notifications %} -{% data reusables.user_settings.automatic_watching_box %} selecciona **Automatically watch teams** (Ver equipos automáticamente). ![Casilla de verificación para ver automáticamente equipos](/assets/images/help/notifications/automatic-team-discussions-watching.png) - -### Ver debates de un equipo único - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.watch-team-options %} haz clic en **Watch** (Ver) para abrir tus opciones de notificaciones. Después haz clic en **Watching (Ver)**. ![Ver opciones en un menú desplegable para un equipo específico](/assets/images/help/notifications/specific-team-watch-options.png) - -### Dejar de ver los debates de todos los equipos nuevos a los que te unes - -Si no deseas recibir de forma automática las notificaciones de debates de equipo cuando te unes a un equipo, puedes cambiar tus configuraciones de notificación para dejar de ver todos los nuevos equipos a los que te unes. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.notifications %} -{% data reusables.user_settings.automatic_watching_box %} anula la selección de **Automatically watch teams** (Ver equipos automáticamente). ![Configuración para ver automáticamente equipos seleccionada por defecto](/assets/images/help/notifications/automatic-team-discussions-watching.png) - -### Dejar de ver debates de un equipo único - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.watch-team-options %} haz clic en **Unwatch** (Dejar de ver) para abrir tus opciones de notificaciones. Después haz clic en **Not watching (No ver)**. ![Ver opciones en un menú desplegable para un equipo específico](/assets/images/help/notifications/specific-team-unwatch.png) - -{% note %} - -**Nota:** también puedes elegir ignorar las notificaciones de un equipo. Si ignoras un equipo, no recibirás ninguna notificación. No recomendamos ignorar equipos ya que no se te notificará si eres mencionado. - -{% endnote %} - -### Leer más - -- [Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Acerca de los debates de equipo](/articles/about-team-discussions)" -- [Acerca de los equipos](/articles/about-teams)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github.md deleted file mode 100644 index 1266e02c5d..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Acerca de la búsqueda en GitHub -intro: 'Usa nuestras eficaces herramientas de búsqueda para encontrar lo que estás buscando entre los muchos 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 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search ---- -Puedes buscar globalmente en todo {% data variables.product.product_name %} o limitar tu búsqueda a un repositorio o a una organización en particular - -- 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:** - -- {% data reusables.search.required_login %} -- 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](/articles/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/)" - -{% 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](/articles/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 los siguientes tipos de información en todos los repositorios de {% data variables.product.product_name %} públicos y en todos los repositorios de {% data variables.product.product_name %} privados a los que tienes acceso: - -- [Repositorios](/articles/searching-for-repositories) -- [Temas](/articles/searching-topics) -- [Propuestas y solicitudes de extracción](/articles/searching-issues-and-pull-requests) -- [Código](/articles/searching-code) -- [Confirmaciones](/articles/searching-commits) -- [Usuarios](/articles/searching-users){% if currentVersion == "free-pro-team@latest" %} -- [Paquetes](/github/searching-for-information-on-github/searching-for-packages){% endif %} -- [Wikis](/articles/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) - -### Buscar en todo {% data variables.product.prodname_enterprise %} y {% data variables.product.prodname_dotcom_the_website %} simultáneamente - -Si usas {% data variables.product.prodname_enterprise %} y eres miembro de una organización de {% data variables.product.prodname_dotcom_the_website %} que usa {% data variables.product.prodname_ghe_cloud %}, tu administrador del sitio {% data variables.product.prodname_enterprise %} puede activar {% data variables.product.prodname_github_connect %} para que puedas buscar en ambos entornos al mismo tiempo. Para obtener más información, consulta "[Activar {% data variables.product.prodname_unified_search %} entre {% data variables.product.prodname_enterprise %} y {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com)". - -También solo puedes buscar en ambos entornos desde {% data variables.product.prodname_enterprise %}. 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.prodname_enterprise %}, 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`. - -El administrador de tu sitio {% data variables.product.prodname_enterprise %} puede activar {% data variables.product.prodname_unified_search %} para todos los repositorios públicos, todos los repositorios privados o solo ciertos repositorios privados en la organización de {% data variables.product.prodname_ghe_cloud %} conectada. - -Si el administrador de tu sitio activa {% data variables.product.prodname_unified_search %} en los repositorios privados, solo puedes buscar en los repositorios privados para los que el administrador activó {% data variables.product.prodname_unified_search %} y para los que tienes acceso en la organización de {% data variables.product.prodname_dotcom_the_website %} conectada. Los administradores de {% data variables.product.prodname_enterprise %} y los propietarios de la organización en {% data variables.product.prodname_dotcom_the_website %} no pueden buscar en repositorios privados que son propiedad de tu cuenta. Para buscar los repositorios privados aplicables, debes activar la búsqueda de repositorio privado para tus cuentas personales en {% data variables.product.prodname_dotcom_the_website %} y {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta "[Activar la búsqueda de repositorio privado de {% data variables.product.prodname_dotcom_the_website %} en tu cuenta de {% data variables.product.prodname_enterprise %} account](/articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account)". - -### Leer más - -- "[Comprender la sintaxis de búsqueda](/articles/understanding-the-search-syntax)" -- "[Búsqueda en GitHub](/articles/searching-on-github)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md b/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md deleted file mode 100644 index 0727fb78c4..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-in-github-enterprise-server.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Habilitar la búsqueda de repositorios de GitHub.com en tu cuenta de servidor de GitHub Enterprise -intro: 'Puedes conectar tus cuentas personales para {% data variables.product.prodname_dotcom_the_website %} y {% data variables.product.prodname_ghe_server %} a fin de buscar contenido en determinados repositorios privados de {% data variables.product.prodname_dotcom_the_website %} de {% data variables.product.prodname_ghe_server %}.' -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 -versions: - fpt: '*' - ghes: '*' -topics: - - GitHub search ---- -Si usas {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %} tu administrador del sitio {% data variables.product.prodname_ghe_server %} ha habilitado {% data variables.product.prodname_github_connect %} y {% data variables.product.prodname_unified_search %} para repositorios privados, podrás buscar repositorios privados designados en la organización conectada. - -Para ver los repositorios privados en tus resultados de búsqueda, ya debes tener acceso a esos repositorios y debes conectar tus cuentas {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información acerca de los repositorios en los que puedes buscar, consulta "[Buscar en {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %} simultáneamente](/articles/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)". - -{% data reusables.github-connect.access-dotcom-and-enterprise %} -{% data reusables.github-connect.access-profile-settings %} -{% data reusables.github-connect.github-connect-tab-user-settings %} -{% data reusables.github-connect.connect-dotcom-and-enterprise %} -{% data reusables.github-connect.authorize-connection %} diff --git a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/index.md b/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/index.md deleted file mode 100644 index 3d4f8fef77..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Comenzar con la búsqueda en GitHub -redirect_from: - - /articles/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-in-github-enterprise-server ---- - diff --git a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results.md deleted file mode 100644 index 6aa2ed00fb..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -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 -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 la búsqueda en GitHub](/articles/about-searching-on-github) -- [Clasificar propuestas y solicitudes de extracción](/articles/sorting-issues-and-pull-requests/) diff --git a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md deleted file mode 100644 index fd6524efbb..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -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 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search ---- -### 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](/articles/about-searching-on-github)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md deleted file mode 100644 index 030b4d8779..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -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 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search ---- -### 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-04-30](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. with a UTC offset of `07:00` and March 1, 2017 at 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. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -### 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-XL/content/github/searching-for-information-on-github/index.md b/translations/es-XL/content/github/searching-for-information-on-github/index.md deleted file mode 100644 index dffe35fd31..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Buscar información en GitHub -redirect_from: - - /categories/78/articles/ - - /categories/search/ - - /categories/searching-for-information-on-github -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search -children: - - /getting-started-with-searching-on-github - - /searching-on-github ---- -### Índice - {% if currentVersion == "free-pro-team@latest" %} - {% endif %} diff --git a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/finding-files-on-github.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/finding-files-on-github.md deleted file mode 100644 index db96206025..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/finding-files-on-github.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Buscar archivos en GitHub -intro: 'Puedes buscar un archivo en un repositorio utilizando el buscador de archivos. Para buscar un archivo en distintos repositorios en {% data variables.product.product_name %}, usa el [calificados de búsqueda de código`filename`](/articles/searching-code#search-by-filename).' -redirect_from: - - /articles/finding-files-on-github - - /github/searching-for-information-on-github/finding-files-on-github -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search ---- -{% tip %} - -**Sugerencias:** - -- 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`](/articles/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 %} -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -2. Debajo del nombre del repositorio, haz clic en **Buscar archivo**. ![Botón Buscar archivo](/assets/images/help/search/find-file-button.png) -{% else %} -2. Sobre la lista de archivos, da clic en **Ir al archivo**. ![Botón Buscar archivo](/assets/images/help/search/find-file-button.png) -{% endif %} -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](/articles/about-searching-on-github)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/index.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/index.md deleted file mode 100644 index 8c9b349664..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Buscar en GitHub -redirect_from: - - /articles/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-XL/content/github/searching-for-information-on-github/searching-on-github/searching-code.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-code.md deleted file mode 100644 index ae1ac7fc4e..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-code.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -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 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search ---- -Puedes buscar código globalmente a lo largo de todos los {% data variables.product.product_name %}, o buscar código dentro de un repositorio u organización particular. Para buscar código a través de todos los repositorios públicos, debes estar registrado en una cuenta {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de la búsqueda en GitHub](/articles/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: - -- {% data reusables.search.required_login %} -- 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](/articles/searching-in-forks)". -- Solo la _rama predeterminada_ se indiza para la búsqueda de código.{% if currentVersion == "free-pro-team@latest" %} -- 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 los repositorios con menos de 500.000 archivos son indexados. -- Los usuarios que están registrados pueden buscar en todos los repositorios públicos. -- 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) encuentra los archivos Perl con la palabra "form" en un directorio cgi-bin o en cualquiera de sus subdirectorios. | -| 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) encuentra los archivos JavaScript con la palabra "console" en un directorio app/public o en cualquiera de sus subdirectorios (incluso si se encuentran en app/public/js/form-validators). | - -### Buscar por lenguaje - -Puedes buscar el código basado en el lenguaje en que está escrito. - -| 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](/articles/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](/articles/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](/articles/sorting-search-results/)" -- "[Buscar en ramificaciones](/articles/searching-in-forks)"{% if currentVersion == "free-pro-team@latest" %} -- "[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-XL/content/github/searching-for-information-on-github/searching-on-github/searching-commits.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-commits.md deleted file mode 100644 index da1ef9caba..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-commits.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -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 -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 %}](/articles/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 confirmaciones creadas 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 repositorios públicos o privados - -El calificador `is` encuentra confirmaciones públicas o privadas. - -| Qualifier | Ejemplo | -| ------------ | ---------------------------------------------------------------------------------------------------------- | -| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) encuentra confirmaciones públicas. | -| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) encuentra confirmaciones privadas. | - -### Leer más - -- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-for-packages.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-for-packages.md deleted file mode 100644 index c364d352f0..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-for-packages.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -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 ---- -{% 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 %}](/articles/about-searching-on-github)". - -{% if currentVersion != "free-pro-team@latest" %} -Para encontrar paquetes que sean propiedad de cierto usuario u organización, utiliza el calificador `user` u `org`. -{% 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-XL/content/github/searching-for-information-on-github/searching-on-github/searching-for-repositories.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-for-repositories.md deleted file mode 100644 index 36f23a2908..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-for-repositories.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -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 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search ---- -Puedes buscar repositorios globalmente a través de todos los {% data variables.product.product_name %}, 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 %}](/articles/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](/articles/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) encuentra repositorios con "jquery" en su nombre. | -| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) encuentra repositorios con "jquery" en su nombre o en su descripción. | -| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) encuentra repositorios que mencionan "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 al buscar por el contenido en el archivo README, utilizando el calificador `in:readme`. - -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 %}](/articles/finding-files-on-github)" y "[Buscar código](/articles/searching-code)." - -| Qualifier | Ejemplo | -| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) encuentra repositorios que mencionan "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` (tamaño) encuentra repositorios que coinciden con un determinado tamaño (en kilobytes), utilizando los calificadores [mayor que, menor que y rango](/articles/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 repositorios en base a la cantidad de seguidores que tienen, utilizando el calificador `followers` (seguidores) con los calificadores [mayor que, menor que y rango](/articles/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` (bifurcaciones) especifica la cantidad de bifurcaciones que debería tener un repositorio, utilizando los calificadores [mayor que, menor que y rango](/articles/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 en base a la cantidad de [estrellas](/articles/saving-repositories-with-stars) que tiene un repositorio, utilizando los calificadores [mayor que, menor que y rango](/articles/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 en base al lenguaje principal en que están escritos. - -| 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 están clasificados con un [tema](/articles/classifying-your-repository-with-topics) particular. - -| 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 en base a la cantidad de [temas](/articles/classifying-your-repository-with-topics) que se les ha aplicado, utilizando los calificadores `topics` (temas) junto con los calificadores [mayor que, menor que y rango](/articles/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. | - -### Buscar por licencia - -Puedes buscar repositorios por su [licencia](/articles/licensing-a-repository). Debes utilizar la [palabra clave licencia](/articles/licensing-a-repository/#searching-github-by-license-type) para filtrar repositorios por una licencia o familia de licencias particular. - -| 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. | - -### Buscar por repositorio privado o público - -Puedes filtrar tu búsqueda en base a si un repositorio es público o privado. - -| Qualifier | Ejemplo | -| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories&utf8=%E2%9C%93) encuentra repositorios que son propiedad de GitHub que son públicos. | -| `is:private` | [**is:private pages**](https://github.com/search?utf8=%E2%9C%93&q=pages+is%3Aprivate&type=Repositories) encuentra repositorios privados a los que has accedido y que contienen la palabra "pages." | - -{% if currentVersion == "free-pro-team@latest" %} - -### Buscar en base a si un repositorio es un espejo - -Puedes buscar los repositorios basándote en el criterio de si son un espejo y están hospedados en algún 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=) encuentra repositorios que son espejos y contienen la palabra "GNOME." | -| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) encuentra repositorios que no son espejo y contienen la palabra "GNOME." | - -{% endif %} - -### Buscar en base a si un repositorio está archivado - -Puedes buscar repositorios en base a si están o no [archivados](/articles/about-archiving-repositories). - -| Qualifier | Ejemplo | -| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) encuentra repositorios que están archivados y contienen la palabra "GNOME." | -| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) encuentra repositorios que no están archivados y contienen la palabra "GNOME." | - -{% if currentVersion == "free-pro-team@latest" %} -### 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](/github/building-a-strong-community/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." | -{% endif %} - -### Leer más - -- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" -- "[Búsqueda en bifurcaciones](/articles/searching-in-forks)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-github-marketplace.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-github-marketplace.md deleted file mode 100644 index be8f801e00..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-github-marketplace.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -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 ---- -### 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-XL/content/github/searching-for-information-on-github/searching-on-github/searching-in-forks.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-in-forks.md deleted file mode 100644 index 6fd173a139..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-in-forks.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -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 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search ---- -Para mostrar bifurcaciones en los resultados de la [búsqueda de repositorios](/articles/searching-for-repositories), agrega `fork:true` o `fork:only` en tu consulta. - -Las fiburcaciones solo se indexan por [búsqueda de código](/articles/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](/articles/about-searching-on-github)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md deleted file mode 100644 index 345e1262cd..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests.md +++ /dev/null @@ -1,335 +0,0 @@ ---- -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 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - GitHub search ---- -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 %}](/articles/about-searching-on-github)". - -{% tip %} - -**Sugerencia:**{% if currentVersion != "free-pro-team@latest" %} - - 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_enterprise %}.{% 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](/articles/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`. - -| 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." | - -### Buscar por repositorio privado o público - -Si estás buscando [a través de todos los {% data variables.product.product_name %}](https://github.com/search), puede ser útil filtrar tus resultados en base a si el repositorio es público o privado. Puedes hacer con `is:public` y `is:private`. - -| Qualifier | Ejemplo | -| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) encuentra propuestas y solicitudes de extracción en todos los repositorios públicos. | -| `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate&type=Issues) encuentra propuestas y solicitudes de extracción que contienen la palabra "cupcake" en repositorios privados a los que tienes acceso. | - -### 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) encuentra propuestas y solicitudes de extracción con la palabra "cool" que fueron creados por @gjtorikian. | -| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) encuentra propuestas escritas por @mdo que contienen la palabra "bootstrap" en el cuerpo. | -| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) encuentra propuestas creadas por la cuenta de integración con el nombre "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 de extracción que tengan _cualquier_ asignatario, sin embargo, puedes buscar [propuestas y solicitudes de extracción que no tengan un asignatario](#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) encuentra propuestas y solicitudes de extracción en el proyecto de libgit2 libgit2 que están asignados 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) encuentra propuestas con la palabra "resque" 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** encuentra propuestas en donde se mencione al equipo `@jekyll/owners`. | -| | **team:myorg/ops is:open is:pr** encuentra solicitudes de extracción abiertas en donde se mencione 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) encuentra propuestas en repositorios que son propiedad de GitHub, que contienen la palabra "github," y tienen 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)** encuentra propuestas en las que están involucrados @defunkt o @jlord. | -| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) encuentra propuestas en las que participa @mdo que no contienen la palabra "bootstrap" en el cuerpo. | - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -### 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" (error) y "resolved" (solucionado). | - -### 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 específicamente útil si estás utilizando [la API de Estados](/v3/repos/statuses/) o un servicio de IC. - -| 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 ](/articles/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%3C100&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](/articles/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](/articles/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 | ------------- | -------------{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) coincidirá con las solicitudes de extracción en estado de borrador. | `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 solicitada es sobre un equipo al que se lo solicita la revisión, entonces las solicitudes de revisión de ese equipo también aparecerán en los resultados de búsqueda. | -| 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) 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. | - -### 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) 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. | - -### 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) 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. | - -### 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](/articles/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](/articles/sorting-search-results/)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-topics.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-topics.md deleted file mode 100644 index 086438e742..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-topics.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -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 -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)**. -{% if currentVersion == "free-pro-team@latest" %} - ![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 el repositorio explore en 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 [](/articles/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](/articles/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-XL/content/github/searching-for-information-on-github/searching-on-github/searching-users.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-users.md deleted file mode 100644 index be672549c1..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-users.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -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 -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 %}](/articles/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](/articles/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](/articles/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. | - -### Leer más - -- "[Clasificar los resultados de la búsqueda](/articles/sorting-search-results/)" diff --git a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-wikis.md b/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-wikis.md deleted file mode 100644 index 59a75db422..0000000000 --- a/translations/es-XL/content/github/searching-for-information-on-github/searching-on-github/searching-wikis.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -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 -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 %}](/articles/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](/articles/sorting-search-results/)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/index.md deleted file mode 100644 index b79211c785..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Configurar y administrar la facturación y los pagos en GitHub -shortTitle: Facturación y pagos -redirect_from: - - /categories/setting-up-and-managing-billing-and-payments-on-github -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /managing-your-github-billing-settings - - /managing-billing-for-your-github-account - - /managing-billing-for-github-marketplace-apps - - /managing-billing-for-github-actions - - /managing-billing-for-git-large-file-storage - - /managing-billing-for-github-sponsors - - /managing-billing-for-github-packages - - /setting-up-paid-organizations-for-procurement-companies ---- -### Índice diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md deleted file mode 100644 index 162a45dbb7..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Acerca de la facturación para Large File Storage de Git -intro: 'Si compras ancho de banda y almacenamiento adicional para {% data variables.large_files.product_name_long %}, tu compra comparte la fecha de facturación, el método de pago y el recibo existentes de tu cuenta.' -redirect_from: - - /articles/about-billing-for-git-large-file-storage - - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Acerca de la facturación para {% data variables.large_files.product_name_long %} - -{% data reusables.large_files.free-storage-bandwidth-amount %} {% data reusables.large_files.does_not_carry %} - -{% data reusables.large_files.owner_quota_only %} - -### Comprar ancho de banda y almacenamiento adicional - -Se ofrece ancho de banda y almacenamiento adicional en un paquete de datos simple. Un paquete de datos cuesta {% data variables.large_files.pack_monthly_price %} y ofrece una cuota mensual de {% data variables.large_files.pack_monthly_bandwidth %} para ancho de banda y {% data variables.large_files.pack_monthly_storage %} para almacenamiento. Puedes comprar tantos paquetes de datos como necesites. Por ejemplo, si necesitas 150 GB de almacenamiento, comprarías tres paquetes de datos. - -La compra de paquetes de datos para {% data variables.large_files.product_name_short %} es independiente de cualquier otra característica paga o producto en {% data variables.product.product_name %}. - -### Bajar de categoría el almacenamiento y el ancho de banda - -Si bajas de categoría tu cantidad de paquetes de datos adicionales, tus cambios entrarán en vigencia en tu próxima fecha de facturación. - -### Leer más - -- "[Acerca de {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)" -- "[Instalar {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)" -- "[Acerca del uso de banda ancha y del almacenamiento](/articles/about-storage-and-bandwidth-usage)" -- "[Ver tu uso de {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)" -- "[Actualizar {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)" -- "[Bajar de categoría {% data variables.large_files.product_name_long %}](/articles/downgrading-git-large-file-storage)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md deleted file mode 100644 index 2fba3017cc..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Bajar de categoría Large File Storage de Git -intro: 'Puedes bajar de categoría y modificar el ancho de banda para {% data variables.large_files.product_name_short %} aplicando incrementos de 50 GB por mes.' -redirect_from: - - /articles/downgrading-storage-and-bandwidth-for-a-personal-account/ - - /articles/downgrading-storage-and-bandwidth-for-an-organization/ - - /articles/downgrading-git-large-file-storage - - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage -versions: - free-pro-team: '*' -topics: - - Billing ---- -Si bajas de categoría tu cantidad de paquetes de datos, tu cambio entrará en vigencia en tu próxima fecha de facturación. Para obtener más información, consulta " -[Acerca de la facturación para {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)".

    - - - -### Bajar de categoría y reducir el ancho de banda para una cuenta personal - -{% data reusables.user_settings.access_settings %} - - - -{% data reusables.user_settings.billing %} - - - -{% data reusables.user_settings.subscriptions-tab %} - - - -{% data reusables.dotcom_billing.lfs-remove-data %} - - - -{% data reusables.large_files.downgrade_data_packs %} - - - -### Bajar de categoría y reducir el ancho de banda para una organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.profile.access_profile %} - - - -{% data reusables.profile.access_org %} - - - -{% data reusables.organizations.org_settings %} - - - -{% data reusables.organizations.billing %} - - - -{% data reusables.user_settings.subscriptions-tab %} - - - -{% data reusables.dotcom_billing.lfs-remove-data %} - - - -{% data reusables.large_files.downgrade_data_packs %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/index.md deleted file mode 100644 index dd17532ff4..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Administrar la facturación para Large File Storage de Git -intro: 'Puedes ver el uso, la actualización y el cambio a una versión anterior{% data variables.large_files.product_name_long %}.' -redirect_from: - - /articles/managing-large-file-storage-and-bandwidth-for-your-personal-account/ - - /articles/managing-large-file-storage-and-bandwidth-for-your-organization/ - - /articles/managing-storage-and-bandwidth-usage/ - - /articles/managing-billing-for-git-large-file-storage -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /about-billing-for-git-large-file-storage - - /viewing-your-git-large-file-storage-usage - - /upgrading-git-large-file-storage - - /downgrading-git-large-file-storage ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md deleted file mode 100644 index 5cb6b25789..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Subir de categoría Git Large File Storage -intro: 'Puedes comprar más paquetes de datos para aumentar tu cuota de banda ancha mensual y la capacidad de almacenamiento total para {% data variables.large_files.product_name_short %}.' -redirect_from: - - /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account/ - - /articles/purchasing-additional-storage-and-bandwidth-for-an-organization/ - - /articles/upgrading-git-large-file-storage - - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Comprar más almacenamiento y ancho de banda para una cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.lfs-add-data %} -{% data reusables.large_files.pack_selection %} -{% data reusables.large_files.pack_confirm %} - -### Comprar más almacenamiento y ancho de banda para una organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.lfs-add-data %} -{% data reusables.large_files.pack_selection %} -{% data reusables.large_files.pack_confirm %} - -### Leer más - -- "[Acerca de la facturación para {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)" -- "[Acerca del uso de banda ancha y del almacenamiento](/articles/about-storage-and-bandwidth-usage)" -- "[Ver tu uso de {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)" -- "[Control de versiones de archivos grandes](/articles/versioning-large-files)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md deleted file mode 100644 index 29e2698d9c..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Ver tu uso de Git Large File Storage -intro: 'Puedes auditar la cuota de ancho de banda mensual de cuenta y el almacenamiento restante para {% data variables.large_files.product_name_short %}.' -redirect_from: - - /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account/ - - /articles/viewing-storage-and-bandwidth-usage-for-an-organization/ - - /articles/viewing-your-git-large-file-storage-usage - - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage -versions: - free-pro-team: '*' -topics: - - Billing ---- -{% data reusables.large_files.owner_quota_only %} {% data reusables.large_files.does_not_carry %} - -### Ver el uso del almacenamiento y del ancho de banda para una cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.lfs-data %} - -### Ver el uso del almacenamiento y del ancho de banda para una organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.lfs-data %} - -### Leer más - -- "[Acerca del uso de banda ancha y del almacenamiento](/articles/about-storage-and-bandwidth-usage)" -- "[Actualizar {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/about-billing-for-github-actions.md deleted file mode 100644 index 0883fc117d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: Acerca de la facturación para GitHub Actions -intro: 'Si quieres utilizar {% data variables.product.prodname_actions %} con más almacenamiento o minutos de los que se incluyen en tu cuenta, se te cobrará por estos recursos adicionales.' -product: '{% data reusables.gated-features.actions %}' -versions: - free-pro-team: '*' -topics: - - Billing -redirect_from: - - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions ---- -### Acerca de la facturación para {% data variables.product.prodname_actions %} - -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} - -Los minutos se restablecen cada mes, pero no es el caso para el uso de almacenamiento. - -| Producto | Almacenamiento | Minutos (por mes) | -| -------------------------------------------------------------------------- | -------------- | ----------------- | -| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 | -| {% data variables.product.prodname_pro %} | 1 GB | 3,000 | -| {% data variables.product.prodname_free_team %} para organizaciones | 500 MB | 2,000 | -| {% data variables.product.prodname_team %} | 2 GB | 3,000 | -| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 | - -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. - -| Sistema operativo | Multiplicador de minutos | -| ----------------- | ------------------------ | -| Linux | 1 | -| macOS | 10 | -| Windows | 2 | - -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 %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". - - Si tu uso de cuenta sobrepasa estos límites y habías configurado un límite de gastos mayor a $0, 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 %} - -**Nota:**Los multiplicadores de minutos no se aplican a las tasas por minuto que se muestran a continuación. - -{% endnote %} - -| Sistema operativo | Tasa por minuto | -| ----------------- | --------------- | -| Linux | $0.008 | -| macOS | $0.08 | -| Windows | $0.016 | - -La cantidad de jobs que puedes ejecutar simultáneamente a través de todos los repositorios que pertenezcan a tu cuenta de usuario u organización dependerá de tu plan de GitHub. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/about-github-actions/#usage-limits)". - -### Calcular los gastos por minuto y por almacenamiento - -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. 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 minutos (3,000 de Linux y 2,000 de Windows) = $56 ($24 + $32) (USD). - - 3,000 minutos de Linux a $0.008 por minuto = $24 (USD). - - 2,000 minutos de Windows a $0.016 por minuto = $32 (USD). - -Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu transferencia de datos al número de GB más cercano. - -{% data variables.product.prodname_dotcom %} calcula tu uso de almacenamiento para cada mes basándose en el uso por hora durante el mismo mes. 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: - -- 3 GB x 10 días x (24 horas por día) = 720 GB-Horas -- 12 GB x 21 días x (24 horas por día) = 6,048 GB-Horas -- 720 GB-Horas + 6,048 GB-Horas = 6,768 GB-Horas -- 6,768 GB-Horas/ (744 horas por mes) = 9.0967 GB-Meses - -Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. Por lo tanto, tu uso de almacenamiento para marzo sería de 9.097 GB. - -Tu uso de {% data variables.product.prodname_actions %} comparte la fecha de facturación, método de pago y recibo existente en tu cuenta. {% data reusables.dotcom_billing.view-all-subscriptions %} - -### Acerca de los límites de gasto - -Predeterminadamente, tu cuenta tendrá un límite de gastos de $0 para el uso de {% data variables.product.prodname_actions %}. Para habilitar el uso extendido de minutos y almacenamiento para repositorios privados por encima de lo incluido en tu cuenta, puedes incrementar el límite de gastos o permitir gastos ilimitados. Para obtener más información, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions)". - -{% data reusables.github-actions.spending-limit-enterprise-account %} - -{% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/index.md deleted file mode 100644 index bc96fb0282..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Administrar la facturación para GitHub Actions -intro: 'Puedes ver el uso y configurar un límite de gastos para {% data variables.product.prodname_actions %}.' -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /about-billing-for-github-actions - - /viewing-your-github-actions-usage - - /managing-your-spending-limit-for-github-actions ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md deleted file mode 100644 index df279e381b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Administrar tu límite de gastos para GitHub Actions -intro: 'Puedes configurar un límite de gastos para el uso de {% data variables.product.prodname_actions %}.' -product: '{% data reusables.gated-features.actions %}' -versions: - free-pro-team: '*' -topics: - - Billing -redirect_from: - - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions ---- -### Acerca de los límites de gastos para {% data variables.product.prodname_actions %} - -{% data reusables.github-actions.actions-billing %} {% data reusables.github-actions.actions-spending-limit %} - -Puedes configurar un límite de gastos mayor o, en algunas cuentas, permitir gastos ilimitados. Si pagas mediante factura los gastos de tu cuenta empresarial u organizacional, puedes prepagar los excedentes para configurar un límite de gastos superior. The spending limit applies to your combined overages for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}. For more information about pricing for {% data variables.product.prodname_actions %} usage, see "[About billing for {% data variables.product.prodname_actions %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)." - -Tan pronto como configures un límite de gastos mayor a $0, serás responsable de cualquier excedente que haya ocurrido anteriormente. Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, no permite excedentes, y crea artefactos de flujo de trabajo que incrementan tu uso de almacenamiento para el mes en curso de 1.9GB a 2.1GB, utilizarás un poco más de almacenamiento que los 2Gb incluidos en tu producto. - -Ya que no has habilitado los excedentes, tu siguiente intento de publicar una versión del paquete no será exitosa. No recibirás una cuenta por esos 0.1GB extras en ese mes. Sin embargo, si habilitas los excedentes en algún mes posterior, tu primera factura incluirá ese 0.1GB de excedente que ya utilizaste adicional a cualquier otro excedente del ciclo de facturación en curso. - -### Administrar el límite de gastos de {% data variables.product.prodname_actions %} para tu cuenta de usuario - -Cualquiera puede administrar el límite de gastos de {% data variables.product.prodname_actions %} para su propia cuenta de usuario. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.cost-management-tab %} -{% data reusables.dotcom_billing.monthly-spending-limit %} -{% data reusables.dotcom_billing.update-spending-limit %} - -### Administrar el límite de gastos de {% data variables.product.prodname_actions %} para tu organización - -Los propietarios de las organizaciones pueden administrar el límite de gastos de {% data variables.product.prodname_actions %} para una organización. - -Si pagas mediante factura por tu cuenta organizacional, no podrás administrar el límite de gastos para tu cuenta empresarial en {% data variables.product.product_name %}. Si quieres permitir que los repositorios que pertenecen a tu organización utilicen {% data variables.product.prodname_actions %} con mayor almacenamiento o transferencia de datos de los que se incluye predeterminadamente por repositorio, puedes hacer prepagos por los excedentes. Ya que los excedentes deben prepagarse, no puedes habilitar los gastos ilimitados en cuentas que se paguen mediante factura. Tu límite de gastos será de 150% de la cantidad que hayas prepagado. Si tienes cualquier duda, [contacta a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact). - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.cost-management-tab %} -{% data reusables.dotcom_billing.monthly-spending-limit %} -{% data reusables.dotcom_billing.update-spending-limit %} - -### Administrar el límite de gastos de {% data variables.product.prodname_actions %} para tu cuenta empresarial - -Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an enterprise account. - -{% data reusables.github-actions.spending-limit-enterprise-account %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.billing-tab %} -1. Debajo de "uso mensual de {% data variables.product.prodname_actions %} y de paquetes", da clic en **Administración de costos**. ![Pestaña de administración de costos](/assets/images/help/settings/cost-management-tab-enterprise.png) -{% data reusables.dotcom_billing.monthly-spending-limit %} -{% data reusables.dotcom_billing.update-spending-limit %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/viewing-your-github-actions-usage.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/viewing-your-github-actions-usage.md deleted file mode 100644 index 23ef8e173c..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/viewing-your-github-actions-usage.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Visualizar el uso de tu GitHub Actions -intro: 'Puedes ver los detalles de tu uso de minutos y almacenamiento para {% data variables.product.prodname_actions %}.' -product: '{% data reusables.gated-features.actions %}' -versions: - free-pro-team: '*' -topics: - - Billing -redirect_from: - - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage ---- -También puedes ver los minutos de ejecución facturables para los jobs en una ejecución de flujo de trabajo individual. Para obtener más información, consulta la sección "[Administrar la ejecución de un flujo de trabajo](/actions/configuring-and-managing-workflows/managing-a-workflow-run#viewing-billable-job-execution-minutes)". - -### Visualizar el uso de {% data variables.product.prodname_actions %} para tu cuenta de usuario - -Cualquiera puede ver el uso de {% data variables.product.prodname_actions %} para su cuenta de usuario personal. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.dotcom_billing.actions-minutes %} -{% data reusables.dotcom_billing.actions-packages-storage %} -{% data reusables.dotcom_billing.actions-packages-report-download %} - -### Visualizar el uso de {% data variables.product.prodname_actions %} para tu organización - -Organization owners and billing managers can view {% data variables.product.prodname_actions %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_actions %} usage in the organization billing page. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.actions-minutes %} -{% data reusables.dotcom_billing.actions-packages-storage %} -{% data reusables.dotcom_billing.actions-packages-report-download %} - -### Visualizar el uso de {% data variables.product.prodname_actions %} para tu cuenta empresarial - -Los propietarios de empresa y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_actions %} para una cuenta empresarial. - -{% note %} - -**Nota:** Los detalles de facturación para las cuentas empresariales no resumen el uso de los minutos para cada sistema operativo. {% data reusables.github-actions.enterprise-billing-details %} - -{% endnote %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.billing-tab %} -1. Debajo de "{% data variables.product.prodname_actions %}", visualiza los detalles de uso para transferencia de datos de cada organización en tu cuenta empresarial. ![Detalles del uso de minutos](/assets/images/help/billing/actions-minutes-enterprise.png) -{% data reusables.dotcom_billing.actions-packages-storage-enterprise-account %} -{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md deleted file mode 100644 index ab08ed58a7..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Acerca de la facturación para el Mercado GitHub -intro: 'Si instalas una app paga en {% data variables.product.prodname_marketplace %}, tu suscripción comparte la fecha de facturación, el método de pago y el recibo existentes de tu cuenta.' -redirect_from: - - /articles/about-billing-for-github-marketplace - - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace -versions: - free-pro-team: '*' -topics: - - Billing ---- -{% data variables.product.prodname_marketplace %} incluye apps con planes de precios gratuitos y pagos. Después de comprar e instalar una app, puedes actualizar, bajar de categoría o cancerla en cualquier momento. - -{% data reusables.marketplace.marketplace-apps-only %} - -{% data reusables.marketplace.marketplace-org-perms %} - -### Métodos de pago y ciclos de facturación para las compras de {% data variables.product.prodname_marketplace %} - -Tendrás el mismo método de pago para todas las suscripciones y los planes pagos en todo {% data variables.product.prodname_dotcom %}. - -Si tu cuenta personal u organización no tienen un método de pago en el archivo, cuando eliges un plan pago para una app: -- Tu fecha de facturación es hoy. -- Debes agregar un método de pago a tu cuenta personal o a la organización en la que quieres instalar la app. -- Tu método de pago será cargado con el monto total de tu suscripción. -- Tu recibo se envía a la dirección de correo electrónico de facturación o a la principal en el archivo para tu cuenta personal u organización. - -Si tu cuenta personal u organización tienen un método de pago existente, cuando eliges un plan pago para una app: -- Al método de pago en el archivo se le cobrará de inmediato un monto prorrateado por el tiempo restante hasta tu próxima fecha de facturación. -- La fecha de facturación mensual o anual para la suscripción de tu app es la misma que la fecha de facturación regular de tu cuenta u organización. -- En tu próxima fecha de facturación, tu recibo detalla los cargos por tu plan {% data variables.product.prodname_dotcom %} pago y tu suscripción a la app. - -Cuando eliges un plan pago con una prueba gratuita: -- Debes tener un método de pago existente o agregar un método de pago nuevo para tu cuenta personal o para la organización en la que quieres instalar la app. -- Si no tienes ninguna otra suscripción ni plan pago, se te cobrará el monto total de tu suscripción al finalizar la prueba gratuita de 14 días. -- Si tienes otras suscripciones o planes pagos, una vez que finaliza tu prueba de 14 días, al método de pago en el archivo se le cobrará de inmediato un monto prorrateado por el tiempo restante hasta tu próxima fecha de facturación. -- Si tienes otras suscripciones o planes pagos, en tu próxima fecha de facturación, tu recibo detalla los cargos por tu plan {% data variables.product.prodname_dotcom %} pago y tu suscripción a la app. - -### Limites de plan unitario - -Si eliges un plan unitario (por ejemplo, un plan que cobra por usuario) y excedes las unidades por las que estás pagando, el integrador puede desactivar tu acceso hasta que actualices la app. Para obtener más información, consulta [Actualizar el plan de facturación para una app del {% data variables.product.prodname_marketplace %}](/articles/upgrading-the-billing-plan-for-a-github-marketplace-app)". - -### Bajar de categoría una app {% data variables.product.prodname_marketplace %} - -Si bajas de categoría la suscripción de tu app a un plan más económico o si cancelas la suscripción de una app paga, tus cambios entrarán en vigencia al finalizar tu ciclo de facturación actual. Tu suscripción se moverá a tu nuevo plan en tu próxima fecha de facturación. - -Si cancelas una app en un plan gratuito, tu suscripción terminará de inmediato y perderás el acceso a la app. - -{% data reusables.marketplace.downgrade-marketplace-only %} - -Si cancelas un prueba gratuita en un plan pago, tu suscripción se cancela de inmediato y perderás el acceso a la app. Para obtener más información, consulta [Cancelar una app de {% data variables.product.prodname_marketplace %}](/articles/canceling-a-github-marketplace-app)". - -### Leer más - -- "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)" -- "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" -- "[Soporte técnico de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md deleted file mode 100644 index 55c223bcda..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Cancelar una app Mercado GitHub -intro: 'Puedes cancelar y eliminar una app {% data variables.product.prodname_marketplace %} desde tu cuenta en cualquier momento.' -redirect_from: - - /articles/canceling-an-app-for-your-personal-account/ - - /articles/canceling-an-app-for-your-organization/ - - /articles/canceling-a-github-marketplace-app - - /github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app -versions: - free-pro-team: '*' -topics: - - Billing ---- -Al cancelar una app, tu suscripción se mantiene activa hasta el final de tu ciclo de facturación actual. La cancelación entra en vigencia en tu siguiente fecha de facturación. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". - -Cuando cancelas una prueba gratis de un plan pago, tu suscripción se cancela inmediatamente y perderás acceso a la app. Si no cancelas tu prueba gratis dentro del período de pago, el método de pago en el registro de tu cuenta se cargará para el plan que elegiste al final del período de prueba. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". - -{% data reusables.marketplace.downgrade-marketplace-only %} - -### Cancelar una app en tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.marketplace.cancel-app-billing-settings %} -{% data reusables.marketplace.cancel-app %} - -### Cancelar una prueba gratis para una app en tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.marketplace.cancel-free-trial-billing-settings %} -{% data reusables.marketplace.cancel-app %} - -### Cancelar una app para tu organización - -{% data reusables.marketplace.marketplace-org-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.marketplace.cancel-app-billing-settings %} -{% data reusables.marketplace.cancel-app %} - -### Cancelar una prueba gratis para una app en tu organización - -{% data reusables.marketplace.marketplace-org-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.marketplace.cancel-free-trial-billing-settings %} -{% data reusables.marketplace.cancel-app %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md deleted file mode 100644 index 3fa4849bf1..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Bajar de categoría el plan de facturación para la app Mercado GitHub -intro: 'Si deseas usar un plan de facturación diferente, puedes bajar de categoría tu app {% data variables.product.prodname_marketplace %} en cualquier momento.' -redirect_from: - - /articles/downgrading-an-app-for-your-personal-account/ - - /articles/downgrading-an-app-for-your-organization/ - - /articles/downgrading-the-billing-plan-for-a-github-marketplace-app - - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app -versions: - free-pro-team: '*' -topics: - - Billing ---- -Cuando bajas de categoría una app, tu suscripción permanece activa hasta el final de tu ciclo de facturación actual. El cambio entra en vigencia en tu próxima fecha de facturación. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". - -{% data reusables.marketplace.downgrade-marketplace-only %} - -### Bajar de categoría una app para tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.marketplace.downgrade-app-billing-settings %} -{% data reusables.marketplace.choose-new-plan %} -{% data reusables.marketplace.choose-new-quantity %} -{% data reusables.marketplace.issue-plan-changes %} - -### Bajar de categoría una app para tu organización - -{% data reusables.marketplace.marketplace-org-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.marketplace.downgrade-app-billing-settings %} -{% data reusables.marketplace.choose-new-plan %} -{% data reusables.marketplace.choose-new-quantity %} -{% data reusables.marketplace.issue-plan-changes %} - -### Leer más - -- "[Cancelar una app {% data variables.product.prodname_marketplace %}](/articles/canceling-a-github-marketplace-app/)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/index.md deleted file mode 100644 index 7443f77f3c..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Administrar la facturación por las aplicaciones de Mercado GitHub -intro: 'Puedes actualizar, bajar de categoría, o cancelar aplicaciones {% data variables.product.prodname_marketplace %} en cualquier momento.' -redirect_from: - - /articles/managing-your-personal-account-s-apps/ - - /articles/managing-your-organization-s-apps/ - - /articles/managing-billing-for-github-marketplace-apps -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /about-billing-for-github-marketplace - - /upgrading-the-billing-plan-for-a-github-marketplace-app - - /downgrading-the-billing-plan-for-a-github-marketplace-app - - /canceling-a-github-marketplace-app ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md deleted file mode 100644 index 19da220adb..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Subir de categoría el plan de facturación de una app del Mercado GitHub -intro: 'Puedes subir de categoría tu {% data variables.product.prodname_marketplace %} app a un plan diferente en cualquier momento.' -redirect_from: - - /articles/upgrading-an-app-for-your-personal-account/ - - /articles/upgrading-an-app-for-your-organization/ - - /articles/upgrading-the-billing-plan-for-a-github-marketplace-app - - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app -versions: - free-pro-team: '*' -topics: - - Billing ---- -Cuando subes de categoría una app, a tu método de pago se le cobra un monto prorrateado en función del tiempo restante hasta tu próxima fecha de facturación. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". - -### Subir de categoría una app para tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.marketplace.upgrade-app-billing-settings %} -{% data reusables.marketplace.choose-new-plan %} -{% data reusables.marketplace.choose-new-quantity %} -{% data reusables.marketplace.issue-plan-changes %} - -### Subir de categoría una app para tu organización - -{% data reusables.marketplace.marketplace-org-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.marketplace.upgrade-app-billing-settings %} -{% data reusables.marketplace.choose-new-plan %} -{% data reusables.marketplace.choose-new-quantity %} -{% data reusables.marketplace.issue-plan-changes %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/about-billing-for-github-packages.md deleted file mode 100644 index c141172b44..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Acerca de la facturación para GitHub Packages -intro: 'Si quieres utilizar {% data variables.product.prodname_registry %} con más almacenamiento o transferencia de datos de los que se incluyen en tu cuenta, se te cobrará por este uso adicional.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' -topics: - - Billing -redirect_from: - - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages ---- -### Acerca de la facturación para {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.packages-billing %} - -{% data reusables.package_registry.container-registry-beta-billing-note %} - -La transferencia de datos se restablece cada mes, pero no así el uso de almacenamiento. - -| Producto | Almacenamiento | Transferencia de datos (por mes) | -| -------------------------------------------------------------------------- | -------------- | -------------------------------- | -| {% data variables.product.prodname_free_user %} | 500MB | 1GB | -| {% data variables.product.prodname_pro %} | 2GB | 10GB | -| {% data variables.product.prodname_free_team %} para organizaciones | 500MB | 1GB | -| {% data variables.product.prodname_team %} | 2GB | 10GB | -| {% data variables.product.prodname_ghe_cloud %} | 50GB | 100GB | - -Todos los datos de transferencia saliente, cuando se desencadenan mediante {% data variables.product.prodname_actions %}, y aquellos de transferencia entrante desde cualquier origen, son gratuitos. Determinamos que estás descargando paquetes mediante el uso de {% data variables.product.prodname_actions %} cuando ingresas en {% data variables.product.prodname_registry %} utilizando un `GITHUB_TOKEN`. - -| | Hospedado | Auto-Hospedado | -| --------------------------------------------- | --------- | -------------- | -| Acceso utilizando un `GITHUB_TOKEN` | Gratis | Gratis | -| Acceso utilizando un token de acceso personal | Gratis | $ | - -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 %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions)". - -{% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenece el repositorio en donde se publica el paquete. Si tu uso de cuenta sobrepasa estos límites y has configurado un límite de gastos mayor a $0, 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. El excedente de almacenamiento costaría $0.25 por GB, o $37. El excedente para transferencia de datos costaría $0.50 por GB, o $20. - -Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu transferencia de datos al número de GB más cercano. - -{% data variables.product.prodname_dotcom %} calcula tu uso de almacenamiento para cada mes basándose en el uso por hora durante el mismo mes. 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: - -- 3 GB x 10 días x (24 horas por día) = 720 GB-Horas -- 12 GB x 21 días x (24 horas por día) = 6,048 GB-Horas -- 720 GB-Horas + 6,048 GB-Horas = 6,768 GB-Horas -- 6,768 GB-Horas/ (744 horas por mes) = 9.0967 GB-Meses - -Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. Por lo tanto, tu uso de almacenamiento para marzo sería de 9.097 GB. - -Tu uso de {% data variables.product.prodname_registry %} comparte la fecha de facturación, método de pago y recibo existente en tu cuenta. {% data reusables.dotcom_billing.view-all-subscriptions %} - -### Acerca de los límites de gasto - -Predeterminadamente, tu cuenta tendrá un límite de gastos de $0 para el uso de {% data variables.product.prodname_registry %}. Para habilitar el uso extendido de almacenamiento y transferencia de datos para paquetes privados por encima de lo incluido en tu cuenta, puedes incrementar el límite de gastos o permitir gastos ilimitados. Para obtener más información, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages)". - -{% data reusables.package_registry.spending-limit-enterprise-account %} - -{% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/index.md deleted file mode 100644 index 46a0895680..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Administrar la facturación para GitHub Packages -intro: 'Puedes ver tu uso de {% data variables.product.prodname_registry %} y configurar un límite de gastos para {% data variables.product.prodname_registry %}.' -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /about-billing-for-github-packages - - /viewing-your-github-packages-usage - - /managing-your-spending-limit-for-github-packages ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md deleted file mode 100644 index ac3cf059cc..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Administrar tu límite de gastos para GitHub Packages -intro: 'Puedes configurar un límite de gastos para el uso de {% data variables.product.prodname_registry %}.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' -topics: - - Billing -redirect_from: - - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages ---- -### Acerca de los límites de gastos para {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.packages-billing %} - -Puedes configurar un límite de gastos mayor o, en algunas cuentas, permitir gastos ilimitados. Si pagas mediante factura los gastos de tu cuenta empresarial u organizacional, puedes prepagar los excedentes para configurar un límite de gastos superior. The spending limit applies to your combined overages for {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}. For more information about pricing for {% data variables.product.prodname_registry %} usage, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." - -Tan pronto como configures un límite de gastos mayor a $0, serás responsable de cualquier excedente que haya ocurrido anteriormente. Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, no permite excedentes, y publica una nueva versión de un paquete privado que incrementa tu uso de almacenamiento para el mes en curso de 1.9GB a 2.1GB, la publicación de esta versión usará un poco más de los 2GB que se incluyen en tu paquete. - -Ya que no has habilitado los excedentes, tu siguiente intento de publicar una versión del paquete no será exitosa. No recibirás una cuenta por esos 0.1GB extras en ese mes. Sin embargo, si habilitas los excedentes en algún mes posterior, tu primera factura incluirá ese 0.1GB de excedente que ya utilizaste adicional a cualquier otro excedente del ciclo de facturación en curso. - -### Administrar el límite de gastos de {% data variables.product.prodname_registry %} para tu cuenta de usuario - -Cualquiera puede administrar el límite de gastos de {% data variables.product.prodname_registry %} para su propia cuenta de usuario. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.cost-management-tab %} -{% data reusables.dotcom_billing.monthly-spending-limit %} -{% data reusables.dotcom_billing.update-spending-limit %} - -### Administrar el límite de gastos de {% data variables.product.prodname_registry %} para tu organización - -Los propietarios de las organizaciones pueden administrar el límite de gastos de {% data variables.product.prodname_registry %} para una organización. - -Si pagas mediante factura por tu cuenta organizacional, no podrás administrar el límite de gastos para tu cuenta empresarial en {% data variables.product.product_name %}. Si quieres permitir que los repositorios que pertenecen a tu organización utilicen {% data variables.product.prodname_registry %} con mayor almacenamiento o transferencia de datos de los que se incluye predeterminadamente por repositorio, puedes hacer prepagos por los excedentes. Ya que los excedentes deben prepagarse, no puedes habilitar los gastos ilimitados en cuentas que se paguen mediante factura. Tu límite de gastos será de 150% de la cantidad que hayas prepagado. Si tienes cualquier duda, [contacta a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact). - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.cost-management-tab %} -{% data reusables.dotcom_billing.monthly-spending-limit %} -{% data reusables.dotcom_billing.update-spending-limit %} - -### Administrar el límite de gastos de {% data variables.product.prodname_registry %} para tu cuenta empresarial - -Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an enterprise account. - -{% data reusables.package_registry.spending-limit-enterprise-account %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.billing-tab %} -1. Debajo de "uso mensual de {% data variables.product.prodname_actions %} y de paquetes", da clic en **Administración de costos**. ![Pestaña de administración de costos](/assets/images/help/settings/cost-management-tab-enterprise.png) -{% data reusables.dotcom_billing.monthly-spending-limit %} -{% data reusables.dotcom_billing.update-spending-limit %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/viewing-your-github-packages-usage.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/viewing-your-github-packages-usage.md deleted file mode 100644 index 00e3ffacf4..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/viewing-your-github-packages-usage.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Visualizar el uso de tu GitHub Packages -intro: 'Puedes ver los detalles de uso de almacenamiento y transferencia de datos para {% data variables.product.prodname_registry %}.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' -topics: - - Billing -redirect_from: - - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage ---- -### Visualizar el uso de {% data variables.product.prodname_registry %} para tu cuenta de usuario - -Cualquiera puede ver el uso de {% data variables.product.prodname_registry %} para su cuenta de usuario personal. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.dotcom_billing.packages-data %} -{% data reusables.dotcom_billing.actions-packages-storage %} -{% data reusables.dotcom_billing.actions-packages-report-download %} - -### Visualizar el uso de {% data variables.product.prodname_registry %} para tu organización - -Organization owners and billing managers can view {% data variables.product.prodname_registry %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_registry %} usage in the organization billing page. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.packages-data %} -{% data reusables.dotcom_billing.actions-packages-storage %} -{% data reusables.dotcom_billing.actions-packages-report-download %} - -### Visualizar el uso de {% data variables.product.prodname_registry %} para tu cuenta empresarial - -Los propietarios de empresa y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_registry %} para una cuenta empresarial. - -{% note %} - -**Nota:** Los detalles de facturación para cuentas empresariales únicamente resumen el uso de almacenamiento de datos por organización. {% data reusables.github-actions.enterprise-billing-details %} - -{% endnote %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.billing-tab %} -1. Debajo de "{% data variables.product.prodname_registry %}", visualiza los detalles de uso de transferencia de datos para cada organización en tu cuenta empresarial. ![Detalles de uso de transferencia de datos](/assets/images/help/billing/packages-data-enterprise.png) -{% data reusables.dotcom_billing.actions-packages-storage-enterprise-account %} -{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md deleted file mode 100644 index 0c6a590dbd..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Acerca de la facturación de los Patrocinadores de GitHub -intro: Recibirás la factura por tus patrocinios con el resto de tus características y productos pagos. -redirect_from: - - /articles/about-billing-for-github-sponsors - - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors -versions: - free-pro-team: '*' -topics: - - Billing ---- -{% data reusables.sponsors.sponsorship-details %} - -{% data reusables.dotcom_billing.view-all-subscriptions %} - -### Leer más - -- "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" -- "[Patrocinar a contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md deleted file mode 100644 index e0055121a0..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Bajar de categoría un patrocinio -intro: 'Puedes bajar de categoría un patrocinio y llevarlo a un nivel inferior, o bien cancelar tu patrocinio.' -redirect_from: - - /articles/downgrading-a-sponsorship - - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Bajar de categoría un patrocinio - -Cuando bajas de categoría un patrocinio, el cambio entra en vigencia en tu próxima fecha de facturación. {% data reusables.sponsors.no-refunds %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. Del lado derecho de la página, al lado del nivel seleccionado, haz clic en **Edit** (Editar). ![Botón Edit tier (Editar nivel)](/assets/images/help/billing/edit-tier-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.update-sponsorship %} - -### Cancelar un patrocinio - -Cuando cancelas un patrocinio, el cambio entra en vigencia en tu próxima fecha de facturación. {% data reusables.sponsors.no-refunds %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -3. Debajo de "{% data variables.product.prodname_sponsors %}", a la derecha del contribuyente de código abierto, da clic en {% octicon "triangle-down" aria-label="The down triangle octicon" %} a un costado de tu cantidad patrocinada. Posteriormente, da clic en **Cancelar patrocinio**. ![Botón Cancelar patrocinio](/assets/images/help/billing/edit-sponsor-billing.png) -4. Revisa la información acerca de la cancelación de tu patrocinio y luego haz clic en **Aceptar**. ![Casilla de confirmación de cancelación](/assets/images/help/billing/confirm-sponsorship-cancellation.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/index.md deleted file mode 100644 index a104d52862..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Administrar la facturación de Patrocinadores de GitHub -intro: Puedes actualizar o bajar de categoría el nivel de cada uno de tus patrocinadores. -redirect_from: - - /articles/managing-billing-for-github-sponsors -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /about-billing-for-github-sponsors - - /upgrading-a-sponsorship - - /downgrading-a-sponsorship ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md deleted file mode 100644 index 355e4a1e8d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Subir de categoría un patrocinio -intro: Puedes subir de categoría tu patrocinio a un nivel superior. -redirect_from: - - /articles/upgrading-a-sponsorship - - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship -versions: - free-pro-team: '*' -topics: - - Billing ---- -Cuando subes de categoría tu nivel de patrocinio, el cambio entrará en vigor de inmediato. {% data reusables.sponsors.prorated-sponsorship %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.sponsors.change-tier %} -4. Del lado derecho de la página, al lado del nivel seleccionado, haz clic en **Edit** (Editar). ![Botón Edit tier (Editar nivel)](/assets/images/help/billing/edit-tier-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.update-sponsorship %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-billing-for-github-accounts.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-billing-for-github-accounts.md deleted file mode 100644 index 079446db57..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-billing-for-github-accounts.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Acerca de la facturación para las cuentas de GitHub -intro: '{% data variables.product.product_name %} ofrece productos gratuitos y pagos para cada programador o equipo.' -redirect_from: - - /articles/what-is-the-total-cost-of-using-an-organization-account/ - - /articles/what-are-the-costs-of-using-an-organization-account/ - - /articles/what-plan-should-i-choose/ - - /articles/do-you-have-custom-plans/ - - /articles/user-account-billing-plans/ - - /articles/organization-billing-plans/ - - /articles/github-s-billing-plans - - /articles/about-billing-for-github-accounts - - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts -versions: - free-pro-team: '*' -topics: - - Billing ---- -Para obtener más información sobre los productos disponibles para tu cuenta, consulta los productos de"[{% data variables.product.product_name %}](/articles/github-s-products)". Puedes ver los precios y una lista completa de las funciones de cada producto en <{% data variables.product.pricing_url %}>. {% data variables.product.product_name %} no ofrece productos personalizados ni suscripciones. - -Puedes elegir una facturación mensual o anual y puedes actualizar o bajar de categoría tu suscripción en cualquier momento. Para obtener más información, consulta "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)". - -Puedes comprar otras características o productos con tu información de pago de {% data variables.product.product_name %} existente. Para obtener más información, consulta "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)". - -{% tip %} - -**Sugerencia:** {% data variables.product.prodname_dotcom %} tiene programas para estudiantes validados y académicos, que incluyen descuentos académicos. Para obtener más información, visita [{% data variables.product.prodname_education %}](https://education.github.com/). - -{% endtip %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-per-user-pricing.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-per-user-pricing.md deleted file mode 100644 index afdb690210..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-per-user-pricing.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Acerca del precio por usuario -intro: 'Con el precio por usuario, las organizaciones pagan en función del tamaño del equipo para acceder a la colaboración de avanzada y a las herramientas de administración para equipos, y opcionalmente, controles de seguridad, cumplimiento e implementación.' -redirect_from: - - /articles/about-per-user-pricing - - /github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing -versions: - free-pro-team: '*' -topics: - - Billing ---- -Las organizaciones nuevas pueden crear proyectos de código abierto y públicos con {% data variables.product.prodname_free_team %} o [actualizarse]({% data variables.product.pricing_url %}) a un producto pago con el precio por usuario. - -Las organizaciones que usan una suscripción paga antes del 11 de mayo de 2016 pueden elegir permanecer en su plan existente por repositorio o cambiar al precio por usuario. Te notificaremos doce meses antes de cualquier cambio impuesto en tu suscripción. Para obtener más información sobre cómo cambiar tu suscripción, consulta "[Actualizar tu {% data variables.product.prodname_dotcom %} suscripción](/articles/upgrading-your-github-subscription)". - -Para obtener más información sobre los productos con precio por usuario, consulta "[Productos de {% data variables.product.prodname_dotcom %}](/articles/githubs-products)". - -### ¿Cuántas licencias necesito para mi organización? - -Los propietarios y miembros de las organizaciones deberán contar con una licencia individual por persona. Si has enviado una invitación pendiente para un miembro prospecto de una organización, ésta tomará una licencia. {% data reusables.organizations.org-invite-expiration %} - -Los colaboradores externos y cuentas bot contarán en el total de las licencias pagadas de tu organización si se les da acceso a un repositorio privado. - -### ¿Cómo puedo añadir o bajar de categoría a las licencias pagadas de mi organización? - -Puedes añadir licencias pagadas a tu organización en cualquier momento. Si pagas por más licencias de las que utilizas, también puedes eliminar las licencias pagadas de tu organización. Para obtener más información, consulta "[Actualizar tu suscripción de {% data variables.product.prodname_dotcom %}](/articles/upgrading-your-github-subscription)" y "[Bajar de categoría tu suscripción de {% data variables.product.prodname_dotcom %}](/articles/downgrading-your-github-subscription)". - -Si tienes consultas acerca de la suscripción de tu organización, comunícate con {% data variables.contact.contact_support %}. - -### Si mantengo mi organización en un plan por repositorio, ¿puedo actualizar o bajar de categoría a un plan de repositorio diferente? - -Puedes actualizar o bajar de categoría entre planes pagos heredados en los parámetros de facturación de tu organización. Cuando te actualizas a un plan con más repositorios privados, inmediatamente moveremos tu cuenta a tu nuevo plan y te facturaremos la diferencia en el precio, prorrateado por la cantidad de días que quedan en tu ciclo de facturación. - -Cuando bajas de categoría a un plan pago heredado con menos repositorios privados, tu nuevo plan entrará en vigencia en tu próxima fecha de facturación. Si tienes más repositorios privados de los que permite tu nuevo plan, tus repositorios privados se bloquearán cuando tu nuevo plan entre en vigencia. Para reducir la cantidad de repositorios privados, puedes hacer que algunos de tus repositorios privados sean públicos o puedes clonar tus repositorios privados localmente y eliminar las copias en {% data variables.product.prodname_dotcom %}. - -### Leer más - -- "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md deleted file mode 100644 index f88c072c59..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Suscripciones con descuentos para cuentas GitHub -intro: '{% data variables.product.product_name %} ofrece descuentos a estudiantes, educadores, instituciones educativas, bibliotecas y organizaciones sin fines de lucro.' -redirect_from: - - /articles/discounted-personal-accounts/ - - /articles/discounted-organization-accounts/ - - /articles/discounted-billing-plans/ - - /articles/discounted-subscriptions-for-github-accounts - - /github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts -versions: - free-pro-team: '*' -topics: - - Billing ---- -{% tip %} - -**Sugerencia**: Los descuentos para {% data variables.product.prodname_dotcom %} no se tienen vigencia para las suscripciones de otros productos y características pagos. - -{% endtip %} - -### Descuentos para cuentas personales - -Además del número ilimitado de repositorios públicos y privados para estudiantes y miembros del cuerpo docente con {% data variables.product.prodname_free_user %}, los estudiantes validados pueden solicitar el {% data variables.product.prodname_student_pack %} para recibir beneficios adicionales ofrecidos por los socios de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Solicitar el paquete de desarrollo para estudiantes](/articles/applying-for-a-student-developer-pack)". - -### Descuentos para escuelas y universidades - -Los miembros del cuerpo docente validados pueden solicitar {% data variables.product.prodname_team %} para la enseñanza y la investigación académica. Los miembros del cuerpo docente validados pueden solicitar {% data variables.product.prodname_team %} para la enseñanza y la investigación académica. Para obtener más información, consulta "[Usar {% data variables.product.prodname_dotcom %} en tu clase y en tu investigación](/articles/using-github-in-your-classroom-and-research)". Para obtener más información, visita [{% data variables.product.prodname_education %}](https://education.github.com/). - -### Descuentos para bibliotecas y organizaciones sin fines de lucro - -{% data variables.product.product_name %}proporciona {% data variables.product.prodname_team %} gratuito para organizaciones y cuenta con repositorios privados ilimitados, colaboradores ilimitados, y un juego completo de características a organizaciones y bibliotecas que califiquen como 501(c)3 (o equivalentes). Puedes solicitar un descuento para tu organización en [nuestra página de organizaciones sin fines de lucro](https://github.com/nonprofit). - -Si tu organización ya tiene una suscripción paga, la última transacción de tu organización se reembolsará una vez que se haya aplicado tu descuento para organizaciones sin fines de lucro. - -### Leer más - -- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/downgrading-your-github-subscription.md deleted file mode 100644 index 4d4ced3bf2..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/downgrading-your-github-subscription.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -title: Bajar de categoría tu suscripción de GitHub -intro: 'Puedes bajar tu suscripción de nivel para cualquier tipo de cuenta de {% data variables.product.product_name %} en cualquier momento.' -redirect_from: - - /articles/downgrading-your-personal-account-s-billing-plan/ - - /articles/how-do-i-cancel-my-account/ - - /articles/downgrading-a-user-account-to-free/ - - /articles/removing-paid-seats-from-your-organization/ - - /articles/downgrading-your-organization-s-paid-seats/ - - /articles/downgrading-your-organization-s-billing-plan/ - - /articles/downgrading-an-organization-with-per-seat-pricing-to-free/ - - /articles/downgrading-an-organization-with-per-repository-pricing-to-free/ - - /articles/downgrading-your-organization-to-free/ - - /articles/downgrading-your-organization-from-the-business-plan-to-the-team-plan/ - - /articles/downgrading-your-organization-from-github-business-cloud-to-the-team-plan/ - - /articles/downgrading-your-github-billing-plan/ - - /articles/downgrading-your-github-subscription - - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Bajar de nivel tu suscripción de {% data variables.product.product_name %} - -Cuando bajas de nivel tu suscricpión de cuenta de usuario o de organización, los precios y características cambian y toman efecto en tu siguiente fecha de facturación. Los cambios a tu suscripción de cuenta de usuario u organización no afectan aquellas suscripciones o pagos para otras características pagadas de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[¿Cómo afecta subir o bajar de categoría el proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)." - -### Bajar de nivel tu suscripción de cuenta de usuario - -Si bajas tu cuenta de usuario de nivel desde {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, esta perderá acceso a las herramientas avanzadas de revisión de código en los repositorios privados. {% data reusables.gated-features.more-info %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -4. Utiliza el menú desplegable **Edit** (Editar) y haz clic en **Downgrade to Free** (Bajar de categoría a Gratis). ![Botón Downgrade to free (Bajar de categoría a gratis)](/assets/images/help/billing/downgrade-to-free.png) -5. Lee la información sobre de las características a las cuales perderá acceso tu cuenta de usuario en tu siguiente fecha de facturación, y luego da clic en **Entiendo. Bajar de nivel**. ![Botón de proceder con la baja de categoría](/assets/images/help/billing/continue-with-downgrade.png) - -Si publicaste un sitio de {% data variables.product.prodname_pages %} en un repositorio privado y añadiste un dominio personalizado, retira o actualiza tus registros de DNS antes de bajarlo de nivel desde {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, para evitar el riesgo de que te ganen el dominio. 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)". - -### Bajar de nivel tu suscripción de orgnización - -{% data reusables.dotcom_billing.org-billing-perms %} - -Si bajas tu organización de nivel desde {% data variables.product.prodname_team %} a {% data variables.product.prodname_free_team %} para organizaciones, la cuenta perderá acceso a las herramientas de administración y colaboración para equipos. - -Si bajas a tu organización de nivel desde {% data variables.product.prodname_ghe_cloud %} a {% data variables.product.prodname_team %} o {% data variables.product.prodname_free_team %}, la cuenta perderá acceso a los controles avanzados de seguridad, cumplimiento y despliegue. {% data reusables.gated-features.more-info %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -6. Utiliza el menú desplegable de **Editar** y da clic en la opción a la cual desees bajar. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-option-button.png) -{% data reusables.dotcom_billing.confirm_cancel_org_plan %} - -### Bajar de nivel la suscripción de una organización con precios tradicionales por repositorio - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.dotcom_billing.switch-legacy-billing %}Para obtener más información, consulta la sección "[Cambiar a tu organización de precios por repositorio a precios por usuario](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -5. Debajo de "Suscripciones", selecciona el menú desplegable de "Editar" y da clic en **Editar plan**. ![Menú desplegable de Editar Plan](/assets/images/help/billing/edit-plan-dropdown.png) -1. Debajo de "Facturación/Planes", a un costado del plan que quieras cambiar, da clic en **Bajar categoría**. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-plan-option-button.png) -1. Ingresa la razón por la cual estás degradando tu cuenta y luego haz clic en **Degradar plan**. ![Caja de texto para la razón de degradar la versión y botón de degradar](/assets/images/help/billing/downgrade-plan-button.png) - -### Eliminar asientos pagos de tu organización - -Para reducir el número de asientos pagos que usa tu organización, puedes eliminar miembros de tu organización o convertirlos en colaboradores externos y darles acceso únicamente a los repositorios públicos. Para obtener más información, consulta: -- "[Eliminar un miembro de tu organización](/articles/removing-a-member-from-your-organization)" -- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" -- "[Administrar el acceso de un individuo al repositorio de una organización](/articles/managing-an-individual-s-access-to-an-organization-repository)" - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -6. Utiliza el menú desplegable **Edit** (Editar) y haz clic en **Remove seats** (Eliminar asientos). ![menú desplegable para eliminar plazas](/assets/images/help/billing/remove-seats-dropdown.png) -1. En "Eliminar asientos" selecciona el número de asientos pagos de la categoría a la que deseas bajar. ![opción de eliminar plazas](/assets/images/help/billing/remove-seats-amount.png) -1. Revisa la información sobre tu nuevo pago en tu siguiente fecha de facturación, posteriormente, da clic en **Eliminar plazas**. ![botón de eliminar plazas](/assets/images/help/billing/remove-seats-button.png) - -### Leer más - -- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" -- "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" -- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)". -- "[Eliminar un método de pago](/articles/removing-a-payment-method)" -- "[Acerca del precio por usuario](/articles/about-per-user-pricing)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md deleted file mode 100644 index 88ab74c057..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: ¿Cómo impacta subir o bajar de categoría en el proceso de facturación? -intro: 'Cuando subes de categoría la suscripción de tu cuenta personal u organización, las modificaciones se aplican de inmediato. Cuando bajas de categoría tu suscripción, las modificaciones se aplican al final de tu ciclo de facturación actual.' -redirect_from: - - /articles/how-does-upgrading-or-downgrading-affect-the-billing-process - - /github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process -versions: - free-pro-team: '*' -topics: - - Billing ---- -Los cambios en tu suscripción pagada de cuenta de usuario u organización no afectan las suscripciones o pagos de otras características pagadas de {% data variables.product.prodname_dotcom %}, tales como {% data variables.large_files.product_name_long %} o aplicaciones pagadas que compraste en {% data variables.product.prodname_marketplace %}. - -Para obtener más información, consulta los productos de "[{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" y "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)." - -#### Ejemplo de cancelación de una suscripción paga de una cuenta personal u organización - -Kumiko paga una suscripción mensual el día 5 de cada mes. Si Kimiko se baja de categoría de la suscripción pagada a {% data variables.product.prodname_free_user %} en el 10 de octubre, su suscripción se mantendrá efectiva hasta el final de su ciclo actual de facturación en el 4 de noviembre. En el 5 de noviembre, su cuenta se migrará a {% data variables.product.prodname_free_user %}. - -#### Ejemplo de cambiar de una suscripción anual a una mensual para una cuenta personal u organización - -Ravi paga una suscripción anual el 5 de octubre de cada año. Si el 10 de diciembre Ravi cambia de una facturación anual a una mensual, su cuenta sigue en la suscripción anual hasta el final de su ciclo de facturación actual, el 4 de octubre del siguiente año. El 5 de octubre del siguiente año, a Ravi se le cobrará por un servicio mensual. Su próxima fecha de facturación será el 5 de noviembre. - -#### Ejemplo de agregar asientos pagos a tu organización - -La organización de Mada paga por 25 asientos el día 15 de cada mes. Si el 4 de junio Mada agrega diez asientos pagos, de inmediato se le cobrará a su organización un monto prorrateado por los diez asientos adicionales por el tiempo que transcurre entre el 4 y el 14 de junio, y los asientos estarán disponibles de inmediato para el uso. El 15 de junio, la organización de Mada pagará por 35 asientos. - -#### Ejemplo de eliminar asientos pagos de tu organización - -La organización de Stefan paga por 50 asientos el 20 de mayo de cada año. Si Stefan elimina 20 asientos y baja de categoría a un nuevo total de 30 asientos pagos el 30 de septiembre, su organización puede seguir accediendo a sus 50 asientos pagos hasta el final de su ciclo de facturación actual, el 19 de mayo. El 20 de mayo, entrará en vigor la categoría más baja, la organización de Stefan pagará por 30 asientos y tendrá acceso a 30 asientos pagos. - -### Leer más - -- "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)" -- "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" -- "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" -- "[Acerca del precio por usuario](/articles/about-per-user-pricing)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/index.md deleted file mode 100644 index c0360eaaf8..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Administrar la facturación para tu cuenta de GitHub -intro: '{% data variables.product.product_name %} ofrece productos gratuitos y pagos para cada cuenta. Puedes actualizar, bajar de categoría y visualizar los cambios pendientes de la suscripción de tu cuenta en cualquier momento.' -redirect_from: - - /categories/97/articles/ - - /categories/paying-for-user-accounts/ - - /articles/paying-for-your-github-user-account/ - - /articles/managing-billing-on-github/ - - /articles/changing-your-personal-account-s-billing-plan/ - - /categories/billing/ - - /categories/3/articles/ - - /articles/managing-your-organization-s-paid-seats/ - - /articles/managing-billing-for-your-github-account -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /about-billing-for-github-accounts - - /about-per-user-pricing - - /how-does-upgrading-or-downgrading-affect-the-billing-process - - /upgrading-your-github-subscription - - /viewing-and-managing-pending-changes-to-your-subscription - - /downgrading-your-github-subscription - - /discounted-subscriptions-for-github-accounts ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/upgrading-your-github-subscription.md deleted file mode 100644 index 559075cc16..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/upgrading-your-github-subscription.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: Subir de categoría tu suscripción de GitHub -intro: 'Puedes subir de categoría la suscripción para cualquier tipo de {% data variables.product.product_name %} cuenta en cualquier momento.' -redirect_from: - - /articles/upgrading-your-personal-account-s-billing-plan/ - - /articles/upgrading-your-personal-account/ - - /articles/upgrading-your-personal-account-from-free-to-a-paid-account/ - - /articles/upgrading-your-personal-account-from-free-to-paid-with-a-credit-card/ - - /articles/upgrading-your-personal-account-from-free-to-paid-with-paypal/ - - /articles/500-error-while-upgrading/ - - /articles/upgrading-your-organization-s-billing-plan/ - - /articles/changing-your-organization-billing-plan/ - - /articles/upgrading-your-organization-account-from-free-to-paid-with-a-credit-card/ - - /articles/upgrading-your-organization-account-from-free-to-paid-with-paypal/ - - /articles/upgrading-your-organization-account/ - - /articles/switching-from-per-repository-to-per-user-pricing/ - - /articles/adding-seats-to-your-organization/ - - /articles/upgrading-your-github-billing-plan/ - - /articles/upgrading-your-github-subscription - - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Subir de categoría la suscripción de tu cuenta personal - -Puedes mejorar tu cuenta personal desde {% data variables.product.prodname_free_user %} a {% data variables.product.prodname_pro %} para obtener herramientas avanzadas de revisión de código en repositorios privados. {% data reusables.gated-features.more-info %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -4. Junto a "{% data variables.product.prodname_free_user %}", haz clic en **Upgrade** (Subir de categoría). ![Botón Upgrade (Bajar de categoría)](/assets/images/help/billing/settings_billing_user_upgrade.png) -{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} -{% data reusables.dotcom_billing.show-plan-details %} -{% data reusables.dotcom_billing.enter-payment-info %} -{% data reusables.dotcom_billing.finish_upgrade %} - -### Subir de categoría la suscripción de tu organización - -Puedes mejorar a tu organización desde {% data variables.product.prodname_free_team %} para organizaciones a {% data variables.product.prodname_team %} para acceder a herramientas de administración y colaboración avanzadas para equipos, o mejorarla a {% data variables.product.prodname_ghe_cloud %} para tener controles adicionales de seguridad, cumplimiento y despliegue. {% data reusables.gated-features.more-info-org-products %} - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.upgrade_org %} -{% data reusables.dotcom_billing.choose_org_plan %} -{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} -{% data reusables.dotcom_billing.show-plan-details %} -{% data reusables.dotcom_billing.enter-payment-info %} -{% data reusables.dotcom_billing.owned_by_business %} -{% data reusables.dotcom_billing.finish_upgrade %} - -#### Próximos pasos para las organizaciones que usan {% data variables.product.prodname_ghe_cloud %} - -Si mejoras a tu organización a {% data variables.product.prodname_ghe_cloud %}, puedes configurar la administración de accesos e identidad para la misma. Para obtener más información, consulta "[Administrar el inicio de sesión único de SAML para tu organización](/articles/managing-saml-single-sign-on-for-your-organization)". - -Si quisieras utilizar una cuenta empresarial con {% data variables.product.prodname_ghe_cloud %}, contacta a {% data variables.contact.contact_enterprise_sales %}. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/articles/about-enterprise-accounts)". - -### Agregar asientos a tu organización - -Si quisieras que usuarios adicionales tengan acceso a los repositorios privados de {% data variables.product.prodname_team %} en tu organización, puedes comprar más plazas en cualquier momento. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.add-seats %} -{% data reusables.dotcom_billing.number-of-seats %} -{% data reusables.dotcom_billing.confirm-add-seats %} - -### Cambiar tu organización de precio por repositorio a precio por usuario - -{% data reusables.dotcom_billing.switch-legacy-billing %}Para obtener más información, consulta "[Acerca de los precios por usuario](/articles/about-per-user-pricing)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -5. A la derecha de tu nombre de plan, utiliza el menú desplegable de **Editar** y selecciona **Editar plan**. ![Menú desplegable de editar](/assets/images/help/billing/per-user-upgrade-button.png) -6. A la derecha de "Herramientas avanzadas para equipos", da clic en **Mejorar ahora**. ![Botón de mejorar ahora](/assets/images/help/billing/per-user-upgrade-now-button.png) -{% data reusables.dotcom_billing.choose_org_plan %} -{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} -{% data reusables.dotcom_billing.owned_by_business %} -{% data reusables.dotcom_billing.finish_upgrade %} - -### Solucionar problemas de un error 500 al subir de categoría - -{% data reusables.dotcom_billing.500-error %} - -### Leer más - -- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" -- "[¿Cómo afecta subir o bajar de categoría al proceso de facturación?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" -- "[Acerca de la facturación en {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)". diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md deleted file mode 100644 index 1f88b6abc7..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Ver y administrar cambios pendientes en tu suscripción -intro: Puedes ver y cancelar cambios pendientes en tus suscripciones antes de que se hagan efectivas en la próxima fecha de facturación. -redirect_from: - - /articles/viewing-and-managing-pending-changes-to-your-personal-account-s-billing-plan/ - - /articles/viewing-and-managing-pending-changes-to-your-organization-s-billing-plan/ - - /articles/viewing-and-managing-pending-changes-to-your-billing-plan/ - - /articles/viewing-and-managing-pending-changes-to-your-subscription - - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription -versions: - free-pro-team: '*' -topics: - - Billing ---- -Puedes cancelar cambios pendientes en la suscripción de tu cuenta y cambios pendientes en tus suscripciones a otras funciones y productos pagos. - -Cuando cancelas un cambio pendiente, tu suscripción no cambiará en tu próxima fecha de facturación (a menos que hagas un cambio posterior en tu suscripción antes de la próxima fecha de facturación). - -### Ver y administrar cambios pendientes en tu suscripción de cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.review-pending-changes %} -{% data reusables.dotcom_billing.cancel-pending-changes %} -{% data reusables.dotcom_billing.confirm-cancel-pending-changes %} - -### Ver y administrar cambios pendientes en tu suscripción de organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.review-pending-changes %} -{% data reusables.dotcom_billing.cancel-pending-changes %} -{% data reusables.dotcom_billing.confirm-cancel-pending-changes %} - -### Leer más - -- "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/about-billing-on-github.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/about-billing-on-github.md deleted file mode 100644 index eec2be103f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/about-billing-on-github.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Acerca de la facturación en GitHub -intro: 'Todo lo que compras en {% data variables.product.prodname_dotcom %} comparte la fecha de facturación, el método de pago y el recibo de tu cuenta.' -redirect_from: - - /articles/about-billing-on-github - - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Productos y características pagos - -Puedes actualizar tu cuenta personal u organización a una suscripción paga en cualquier momento. También puedes elegir comprar apps desde {% data variables.product.prodname_marketplace %} o actualizar el almacenamiento y el ancho de banda para {% data variables.large_files.product_name_long %}. Para obtener más información, consulta: -- "[Acerca de la facturación para las cuentas de {% data variables.product.product_name %}](/articles/about-billing-for-github-accounts)" -- "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)" -- "[Acerca de la facturación para {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)" -- "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)" - -### Administrar parámetros de facturación - -Debes administrar los parámetros de facturación, el método de pago y las características y los productos pagos para cada una de tus cuentas por separado. Puedes elegir pagar mensual o anualmente las características y los productos pagos de cada cuenta. Cada característica o producto pago asociado con una cuenta comparten una fecha de facturación, el método de pago y el recibo. - -{% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %} - -Para obtener más información, consulta "[Administrar tus parámetros de facturación {% data variables.product.prodname_dotcom %}](/articles/managing-your-github-billing-settings)". - -### Leer más - -- "[Administrar la facturación para tu cuenta de {% data variables.product.prodname_dotcom %}](/articles/managing-billing-for-your-github-account)" -- "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" -- "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)" -- "[Administrar la facturación para {% data variables.product.prodname_sponsors %}](/articles/managing-billing-for-github-sponsors)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-information-to-your-receipts.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-information-to-your-receipts.md deleted file mode 100644 index 80e2c7c6dc..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-information-to-your-receipts.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Agregar información a tus recibos -intro: 'Puedes agregar información adicional a tus recibos de {% data variables.product.product_name %}, como información fiscal o contable solicitada por tu empresa o país.' -redirect_from: - - /articles/can-i-add-my-credit-card-number-to-my-receipts/ - - /articles/can-i-add-extra-information-to-my-receipts--2/ - - /articles/how-can-i-add-extra-information-to-my-receipts/ - - /articles/could-you-add-my-card-number-to-my-receipts/ - - /articles/how-can-i-add-extra-information-to-my-personal-account-s-receipts/ - - /articles/adding-information-to-your-personal-account-s-receipts/ - - /articles/how-can-i-add-extra-information-to-my-organization-s-receipts/ - - /articles/adding-information-to-your-organization-s-receipts/ - - /articles/adding-information-to-your-receipts - - /github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts -versions: - free-pro-team: '*' -topics: - - Billing ---- -Tus recibos incluyen tu suscripción de {% data variables.product.prodname_dotcom %} así como otras suscripciones para [otras funciones y productos remunerados](/articles/about-billing-on-github). - -{% warning %} - -**Advertencia**: Por motivos de seguridad, recomendamos enfáticamente no incluir información confidencial o financiera (como número de tarjeta de crédito) en tus recibos. - -{% endwarning %} - -### Agregar información a tus recibos de cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.payment-info-tab %} -{% data reusables.dotcom_billing.extra_info_receipt %} - -### Agregar información a los recibos de tu organización - -{% note %} - -**Nota**: {% data reusables.dotcom_billing.org-billing-perms %} - -{% endnote %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.payment-info-tab %} -{% data reusables.dotcom_billing.extra_info_receipt %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md deleted file mode 100644 index 9f0a320e44..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Agregar o eliminar un método de pago -intro: Puedes agregar un método de pago a tu cuenta o actualizar el método de pago existente de tu cuenta en cualquier momento. -redirect_from: - - /articles/updating-your-personal-account-s-payment-method/ - - /articles/how-do-i-update-my-credit-card/ - - /articles/updating-your-account-s-credit-card/ - - /articles/updating-your-personal-account-s-credit-card/ - - /articles/updating-your-personal-account-s-paypal-information/ - - /articles/does-github-provide-invoicing/ - - /articles/switching-payment-methods-for-your-personal-account/ - - /articles/paying-for-your-github-organization-account/ - - /articles/updating-your-organization-s-credit-card/ - - /articles/updating-your-organization-s-paypal-information/ - - /articles/updating-your-organization-s-payment-method/ - - /articles/switching-payment-methods-for-your-organization/ - - /articles/adding-or-editing-a-payment-method - - /github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method -versions: - free-pro-team: '*' -topics: - - Billing ---- -{% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %} - -No entregamos facturas u órdenes de compra de respaldo a cuentas personales. Enviamos recibos por correo electrónico mensual o anualmente a la fecha de facturación de tu cuenta. Si tu empresa, país o contador necesita que tus recibos sean más detallados, también puedes [agregar información adicional](/articles/adding-information-to-your-personal-account-s-receipts) a tus recibos. - -### Actualizar el método de pago de tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.dotcom_billing.update_payment_method %} -{% data reusables.dotcom_billing.enter-payment-info %} - -### Actualizar el método de pago de tu organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -Si tu organización está fuera de los EE. UU. o si estás usando una cuenta corriente corporativa para pagar {% data variables.product.product_name %}, PayPal puede ser un método de pago útil. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.update_payment_method %} -{% data reusables.dotcom_billing.enter-payment-info %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md deleted file mode 100644 index 1f9d0dd6f4..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Cambiar la duración de tu ciclo de facturación -intro: Puedes pagar la suscripción de tu cuenta y otras características y productos remunerados en un ciclo de facturación mensual o anual. -redirect_from: - - /articles/monthly-and-yearly-billing/ - - /articles/switching-between-monthly-and-yearly-billing-for-your-personal-account/ - - /articles/switching-between-monthly-and-yearly-billing-for-your-organization/ - - /articles/changing-the-duration-of-your-billing-cycle - - /github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle -versions: - free-pro-team: '*' -topics: - - Billing ---- -Al cambiar la duración de tu ciclo de facturación, tu suscripción a {% data variables.product.prodname_dotcom %}, junto con otras características y productos remunerados, se moverán al nuevo ciclo de facturación en tu próxima fecha de facturación. - -### Cambiar la duración del ciclo de facturación de tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.dotcom_billing.change_plan_duration %} -{% data reusables.dotcom_billing.confirm_duration_change %} - -### Cambiar la duración del ciclo de facturación de tu organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -#### Cambiar la duración de una suscripción por usuario - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.change_plan_duration %} -{% data reusables.dotcom_billing.confirm_duration_change %} - -#### Cambiar la duración de un plan heredado por repositorio - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.billing %} -4. En "Billing overview" (Resumen de facturación), haz clic en **Change plan** (Cambiar plan). ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/billing/billing_overview_change_plan.png) -5. En el ángulo superior derecho, haz clic en **Switch to monthly billing** (Cambiar a facturación mensual) o **Switch to yearly billing** (Cambiar a facturación mensual). ![Sección de información de facturación](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/index.md deleted file mode 100644 index 647501adc6..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/index.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Administrar tus configuraciones de facturación de GitHub -intro: 'Las configuraciones de facturación de tu cuenta se aplican a cada característica paga o producto que agregas a la cuenta. Puedes administrar configuraciones como tu método de pago, el ciclo de facturación y el correo electrónico de facturación. También puedes visualizar la información de facturación como tu suscripción, la fecha de facturación, el historial de pagos y los recibos pasados.' -redirect_from: - - /articles/viewing-and-managing-your-personal-account-s-billing-information/ - - /articles/paying-for-user-accounts/ - - /articles/viewing-and-managing-your-organization-s-billing-information/ - - /articles/paying-for-organization-accounts/ - - /categories/paying-for-organization-accounts/articles/ - - /categories/99/articles/ - - /articles/managing-your-github-billing-settings -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /about-billing-on-github - - /viewing-your-subscriptions-and-billing-date - - /adding-or-editing-a-payment-method - - /viewing-your-payment-history-and-receipts - - /adding-information-to-your-receipts - - /setting-your-billing-email - - /changing-the-duration-of-your-billing-cycle - - /redeeming-a-coupon - - /troubleshooting-a-declined-credit-card-charge - - /unlocking-a-locked-account - - /removing-a-payment-method ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/redeeming-a-coupon.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/redeeming-a-coupon.md deleted file mode 100644 index cf1fc5eca5..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/redeeming-a-coupon.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Canjear un cupón -intro: 'Si tienes un cupón, puedes canjearlo por una suscripción {% data variables.product.prodname_dotcom %} paga.' -redirect_from: - - /articles/where-do-i-add-a-coupon-code/ - - /articles/redeeming-a-coupon-for-your-personal-account/ - - /articles/redeeming-a-coupon-for-organizations/ - - /articles/redeeming-a-coupon - - /github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon -versions: - free-pro-team: '*' -topics: - - Billing ---- -{% data variables.product.product_name %} no puede emitir un reembolso si pagas una cuenta antes de aplicar un cupón. Tampoco podemos transferir un cupón canjeado o entregarte un cupón nuevo si lo aplicas a la cuenta equivocada. Confirma que estás aplicando el cupón a la cuenta correcta antes de canjear un cupón. - -No puedes aplicar cupones a planes pagos de {% data variables.product.prodname_marketplace %} apps. - -### Canjear un cupón para tu cuenta personal - -{% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %} -4. En "Redeem your coupon" (Canjear tu cupón), haz clic en **Choose** (Elegir) al lado del nombre de usuario de tu cuenta *personal*. ![Botón Choose (Elegir)](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png) -{% data reusables.dotcom_billing.redeem_coupon %} - -### Canjear un cupón para tu organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %} -4. En "Redeem your coupon" (Canjear tu cupón), haz clic en **Choose** (Elegir) al lado de la *organización* a la que quieras aplicarle el cupón. Si le quieres aplicar el cupón a una organización nueva que aún no existe, haz clic en **Create a new organization** (Crear una organización nueva). ![Botón Choose (Elegir)](/assets/images/help/settings/redeem-coupon-choose-button.png) -{% data reusables.dotcom_billing.redeem_coupon %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method.md deleted file mode 100644 index dc3483c5ee..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/removing-a-payment-method.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Eliminar un método de pago -intro: 'Si no estás usando tu método de pago para ninguna suscripción paga en {% data variables.product.prodname_dotcom %}, puedes eliminar el método de pago para que no siga almacenado en tu cuenta.' -redirect_from: - - /articles/removing-a-credit-card-associated-with-your-user-account/ - - /articles/removing-a-payment-method-associated-with-your-user-account/ - - /articles/removing-a-credit-card-associated-with-your-organization/ - - /articles/removing-a-payment-method-associated-with-your-organization/ - - /articles/removing-a-payment-method - - /github/setting-up-and-managing-billing-and-payments-on-github/removing-a-payment-method -versions: - free-pro-team: '*' -topics: - - Billing ---- -Si vas a pagar tu {% data variables.product.product_name %} suscripción con un cupón y no vas a usar tu método de pago para ninguna [otra función o producto pago](/articles/about-billing-on-github) en {% data variables.product.product_name %}, puedes eliminar tu información de tarjeta de crédito o de PayPal. - -{% tip %} - -**Sugerencia:** Si [bajas la categoría de tu cuenta a producto gratuito](/articles/downgrading-your-github-subscription) y no tienes suscripciones a ninguna otra función o producto pago, eliminaremos automáticamente tu información de pago. - -{% endtip %} - -### Eliminar el método de pago de tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.user_settings.payment-info-tab %} -{% data reusables.dotcom_billing.remove-payment-method %} -{% data reusables.dotcom_billing.remove_payment_info %} - -### Eliminar el método de pago de tu organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.payment-info-tab %} -{% data reusables.dotcom_billing.remove-payment-method %} -{% data reusables.dotcom_billing.remove_payment_info %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/setting-your-billing-email.md deleted file mode 100644 index d7353022ec..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/setting-your-billing-email.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Configurar tu correo electrónico de facturación -intro: 'El correo electrónico de facturación de tu cuenta es donde {% data variables.product.product_name %} envía los recibos y otras comunicaciones relacionadas con la facturación.' -redirect_from: - - /articles/setting-your-personal-account-s-billing-email/ - - /articles/can-i-change-what-email-address-received-my-github-receipt/ - - '/articles/how-do-i-change-the-billing-email,setting-your-billing-email/' - - /articles/setting-your-organization-s-billing-email/ - - /articles/setting-your-billing-email - - /github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Configurar el correo electrónico de facturación de tu cuenta personal - -El correo electrónico principal de tu cuenta personal es donde {% data variables.product.product_name %} envía los recibos y otras comunicaciones relacionadas con la facturación. - -Tu dirección principal de correo electrónico es el primer correo electrónico enumerado en las configuraciones de correo electrónico de tu cuenta. También utilizamos tu dirección principal de correo electrónico como nuestra dirección de correo electrónico de facturación. - -Si deseas cambiar tu correo electrónico de facturación, consulta "[Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address)." - -### Configurar el correo electrónico de facturación de tu organización - -El correo electrónico de facturación de tu organización es donde {% data variables.product.product_name %} envía los recibos y otras comunicaciones relacionadas con la facturación. - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -4. Dentro de **Billing email (Correo electrónico de facturación)**, escribe una dirección de correo electrónico válida. El correo electrónico no necesariamente debe ser único para la cuenta de la organización. ![Casilla de texto para el correo electrónico de facturación](/assets/images/help/settings/org-billing-email.png) -5. Para confirmar tus cambios, haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/settings/update-profile-button.png) - -### Managing additional recipients for your organization's billing email - -If you have users that want to receive billing reports, you can add their email addresses as billing email recipients. This feature is only available to organizations that are not managed by an enterprise. - -#### Adding a recipient for billing notifications - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -1. Under "Billing management", to the right of "Email recipients", click **Add**. ![Add recipient](/assets/images/help/billing/billing-add-email-recipient.png) -1. Type the email address of the recipient, then click **Add**. ![Add recipient modal](/assets/images/help/billing/billing-add-email-recipient-modal.png) - -#### Changing the primary recipient for billing notifications - -One address must always be designated as the primary recipient. The address with this designation can't be removed until a new primary recipient is selected. - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -1. Under "Billing management", find the email address you want to set as the primary recipient. -1. To the right of the email address, use the "Edit" drop-down menu, and click **Mark as primary**. ![Mark primary recipient](/assets/images/help/billing/billing-change-primary-email-recipient.png) - -#### Removing a recipient from billing notifications - -{% data reusables.organizations.navigate-to-org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -1. Under "Email recipients", find the email address you want to remove. -1. For the user's entry in the list, click **Edit**. ![Edit recipient](/assets/images/help/billing/billing-edit-email-recipient.png) -1. To the right of the email address, use the "Edit" drop-down menu, and click *Remove**. ![Remove recipient](/assets/images/help/billing/billing-remove-email-recipient.png) -1. Review the confirmation prompt, then click **Remove**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md deleted file mode 100644 index a0a3ee18da..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Solucionar problemas de un pago de tarjeta de crédito rechazado -intro: 'Si se rechaza la tarjeta de crédito que utilizas para pagar {% data variables.product.product_name %}, puedes tomar varias medidas para asegurarte de que tus pagos se concreten y de no estar bloqueado de tu cuenta.' -redirect_from: - - /articles/what-do-i-do-if-my-card-is-declined/ - - /articles/troubleshooting-a-declined-credit-card-charge - - /github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge -versions: - free-pro-team: '*' -topics: - - Billing ---- -Si se rechaza tu tarjeta, te enviaremos un correo electrónico acerca del motivo por el que se rechazó el pago. Tendrás algunos días para resolver el problema antes de que tratemos de volver a cobrarte. - -### Verifica la fecha de vencimiento de tu tarjeta - -Si tu tarjeta está vencida, tendrás que actualizar la información de pago de tu cuenta. Para obtener más información, consulta "[Agregar o editar un método de pago](/articles/adding-or-editing-a-payment-method)". - -### Revisa la política de tu banco sobre restricciones de tarjetas - -Algunos bancos internacionales colocan restricciones en las transacciones internacionales, de comercio electrónico o automáticamente recurrentes. Si tienes problemas para hacer un pago con tu tarjeta de crédito internacional, llama a tu banco para ver si hay alguna restricción sobre tu tarjeta. - -También admitimos pagos por PayPal. Para obtener más información, consulta "[Agregar o editar un método de pago](/articles/adding-or-editing-a-payment-method)". - -### Contáctate con tu banco para obtener detalles acerca de la transacción - -Tu banco puede proporcionar más información acerca de los pagos rechazados si, específicamente, preguntas por la transacción que se intentó realizar. Si existen restricciones sobre tu tarjeta, y debes llamar al banco, proporciona la siguiente información: - -- **El monto que se te cobra.** El monto de tu suscripción aparece en tus recibos de cuenta. Para obtener más información, consulta "[Ver tu historial de pagos y tus recibos](/articles/viewing-your-payment-history-and-receipts)". -- **La fecha en que {% data variables.product.product_name %} te factura.** La fecha de facturación de tu cuenta aparece en tus recibos. -- **El número de Id. de tu transacción.** El Id. de transacción de tu cuenta aparece en tus recibos. -- **El nombre del vendedor.** El nombre del vendedor es {% data variables.product.prodname_dotcom %}. -- **El mensaje de error que te envió el banco con el pago rechazado.** Puedes encontrar el mensaje de error del banco en el correo electrónico que te enviamos cuando se rechaza un pago. diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/unlocking-a-locked-account.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/unlocking-a-locked-account.md deleted file mode 100644 index fd3f5b3c41..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/unlocking-a-locked-account.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Desbloquear una cuenta bloqueada -intro: Las características pagadas de tu organización se bloquearán si tu pago no se recibe a tiempo debido a problemas de facturación. -redirect_from: - - /articles/what-happens-if-my-account-is-locked/ - - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-owe-anything-for-previous-time/ - - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-pay-backcharges/ - - /articles/what-happens-if-my-repository-is-locked/ - - /articles/unlocking-a-locked-personal-account/ - - /articles/unlocking-a-locked-organization-account/ - - /articles/unlocking-a-locked-account - - /github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account -versions: - free-pro-team: '*' -topics: - - Billing ---- -Puedes desbloquear y acceder a tu cuenta si actualizas el método de pago de tu organización y el estado final del pago. No te pediremos que pagues el tiempo transcurrido en modo bloqueado. - -Puedes bajar a tu organización de nivel a {% data variables.product.prodname_free_team %} para continuar con las mismas características avanzadas en los repositorios públicos. Para obtener más información, consulta la sección "[Bajar de nivel tu suscripción de {% data variables.product.product_name %}](/github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription)". - -### Desbloquear las características de una organización debido a un pago rechazado - -Si las características avanzadas de tu organización se bloquearon debido a un pago rechazado, necesitarás actualizar tu información de facturación para activar un cargo recién autorizado. Para obtener más información, consulta "[Agregar o editar un método de pago](/articles/adding-or-editing-a-payment-method)". - -Si se aprueba la información de facturación nueva, te cobraremos de inmediato el producto pago que elegiste. La organización se desbloqueará automáticamente cuando se haya realizado un pago exitoso. diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md deleted file mode 100644 index 19c60cf065..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Ver tu historial de pagos y recibos -intro: Puedes ver el historial de pagos de tu cuenta y descargar los últimos recibos en cualquier momento. -redirect_from: - - /articles/downloading-receipts/ - - /articles/downloading-receipts-for-personal-accounts/ - - /articles/downloading-receipts-for-organizations/ - - /articles/viewing-your-payment-history-and-receipts - - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Ver los recibos de tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.dotcom_billing.view-payment-history %} -{% data reusables.dotcom_billing.download_receipt %} - -### Ver los recibos de tu organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.view-payment-history %} -{% data reusables.dotcom_billing.download_receipt %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md deleted file mode 100644 index fa701e643b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Ver tus suscripción y fecha de facturación -intro: 'Puedes ver la suscripción de tu cuenta, tu otras características y productos de pago y tu próxima fecha de facturación en las configuraciones de facturación de tu cuenta.' -redirect_from: - - /articles/finding-your-next-billing-date/ - - /articles/finding-your-personal-account-s-next-billing-date/ - - /articles/finding-your-organization-s-next-billing-date/ - - /articles/viewing-your-plans-and-billing-date/ - - /articles/viewing-your-subscriptions-and-billing-date - - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Encontrar la próxima fecha de facturación de tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.billing %} -{% data reusables.dotcom_billing.next_billing_date %} - -### Encontrar la próxima fecha de facturación de tu organización - -{% data reusables.dotcom_billing.org-billing-perms %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.next_billing_date %} - -### Leer más - -- "[Acerca de la facturación para las cuentas de {% data variables.product.product_name %}](/articles/about-billing-for-github-accounts)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md deleted file mode 100644 index 2ed9892a1f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Acerca de las organizaciones para empresas de contratación -intro: 'Las empresas usan las organizaciones para colaborar en proyectos compartidos con varios propietarios y administradores. Puedes crear una organización para tu cliente, realizar un pago en su nombre, y entonces transferir la propiedad de la organización a tu cliente.' -redirect_from: - - /articles/about-organizations-for-resellers/ - - /articles/about-organizations-for-procurement-companies - - /github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies -versions: - free-pro-team: '*' -topics: - - Billing ---- -Para acceder a una organización, cada miembro debe iniciar sesión en su cuenta de usuario personal. - -Los miembros de la organización pueden tener diferentes roles, como *propietario* o *gerente de facturación*: - -- Los **Propietarios** tienen acceso administrativo completo a una organización y sus contenidos. -- Los **Gerentes de facturación** pueden administrar los parámetros de facturación y no pueden acceder a los contenidos de la organización. Los gerentes de facturación no se muestran en la lista de miembros de la organización. - -### Pagos y precios para las organizaciones - -No proporcionamos cotizaciones para los precios de las organizaciones. Puedes ver nuestros precios publicados para [organizaciones](https://github.com/pricing) y [Large File Storage de Git](/articles/about-storage-and-bandwidth-usage/). No ofrecemos descuentos para empresas de contratación ni para pedidos de renovación. - -Aceptamos pagos en dólares estadounidenses, aunque los usuarios finales pueden estar en cualquier parte del mundo. - -Aceptamos pagos mediante tarjeta de crédito y PayPal. No aceptamos pagos mediante factura ni orden de compra. - -Para una compra más fácil y más eficaz, recomendamos que las empresas de contratación configuren una facturación anual para las organizaciones de sus clientes. - -### Leer más - -- "[Crear una organización y pagar por ella en nombre de un cliente](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)" -- "[Actualizar o bajar de categoría la organización paga de tu cliente](/articles/upgrading-or-downgrading-your-client-s-paid-organization)" -- "[Renovar la organización paga de tu cliente](/articles/renewing-your-client-s-paid-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md deleted file mode 100644 index 8e200e599b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Crear una organización y pagar por ella en nombre de un cliente -intro: 'Puedes crear una organización {% data variables.product.prodname_dotcom %} y pagar por ella en nombre de un cliente.' -redirect_from: - - /articles/creating-and-paying-for-an-organization-on-behalf-of-a-client - - /github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client -versions: - free-pro-team: '*' -topics: - - Billing ---- -### Requisitos - -Antes de comenzar, asegúrate de saber lo siguiente: -- El nombre de usuario {% data variables.product.prodname_dotcom %} del cliente que se convertirá en el propietario de la organización que creaste -- El nombre que tu cliente deseará usar para la organización -- La dirección de correo electrónico a la que deseas que se envíen los recibos -- El [producto](/articles/github-s-products) que tu cliente desea comprar -- El número de [asientos pagos](/articles/about-per-user-pricing/) que tu cliente desea comprar para la organización - -### Paso 1: Crea tu cuenta personal de {% data variables.product.prodname_dotcom %}. - -Usarás tu cuenta personal para configurar la organización. También necesitarás iniciar sesión en esta cuenta para renovar la suscripción de tu cliente o hacer cambios en ella en el futuro. - -Si ya posees una cuenta de usuario de {% data variables.product.prodname_dotcom %}, omite el [paso 2](#step-2-create-the-organization). - -1. Dirígete a la página [Unirse a GitHub](https://github.com/join). -2. En "Crear tu cuenta personal", escribe tu nombre de usuario, dirección de correo electrónico y contraseña, y luego haz clic en **Crear una cuenta**. ![Crear el formulario de ingreso a una cuenta personal](/assets/images/help/billing/billing_create_your_personal_account_form.png) -3. Selecciona {% data variables.product.prodname_free_user %} para tu cuenta personal. -4. Haz clic en **Finalizar registración**. - -### Paso 2: Crea la organización. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.organizations %} -{% data reusables.organizations.new-organization %} -3. Dentro de "Choose a plan" (Elegir un plan), haz clic en **Choose (Elegir) {% data variables.product.prodname_free_team %}**. Actualizarás la organización en el próximo paso. -{% data reusables.organizations.organization-name %} -5. Debajo de "Contact email" (Correo electrónico de contacto), escribe una dirección de correo electrónico de contacto para tu cliente. ![Campo para el correo electrónico de contacto](/assets/images/help/organizations/contact-email-field.png) -{% data reusables.dotcom_billing.owned_by_business %} -8. Click **Next**. - -### Paso 3: Actualiza la organización para que tenga una suscripción anual paga. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.upgrade_org %} -{% data reusables.dotcom_billing.choose_org_plan %} (Puedes agregar más asientos a la organización en el siguiente paso). -6. En "Actualizar resumen", selecciona **Pago anual** para pagar por la organización de forma anual. ![Botón de selección para la facturación anual](/assets/images/help/billing/choose-annual-billing-org-resellers.png) -{% data reusables.dotcom_billing.show-plan-details %} -{% data reusables.dotcom_billing.add-payment-method %} -1. En "Pagar con" escribe los datos de tu tarjeta de crédito.![Formulario para ingresar datos de tarjeta de crédito](/assets/images/help/billing/settings_billing_upgrade_with_credit_card.png) -1. Haz clic en **Actualizar tarjeta de crédito**. -{% data reusables.dotcom_billing.finish_upgrade %} - -### Paso 4: Actualiza el número de asientos pagos de la organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.add-seats %} -{% data reusables.dotcom_billing.number-of-seats %} -{% data reusables.dotcom_billing.confirm-add-seats %} - -### Paso 5: Invita a tu cliente a unirse a la organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.invite_member_from_people_tab %} -5. Escribe el nombre de usuario de {% data variables.product.prodname_dotcom %} de tu cliente y presiona **Enter**. ![Campo para escribir el nombre de usuario de tu cliente](/assets/images/help/organizations/org-invite-modal.png) -6. Elige el rol de *propietario* para tu cliente y luego haz clic en **Enviar invitación**. ![Botón de selección para el propietario y botón para enviar invitación](/assets/images/help/organizations/add-owner-send-invite-reseller.png) -7. Tu cliente recibirá un correo electrónico en el que se lo invitará a unirse a la organización. Será necesario que acepte la invitación para que puedas continuar con el paso siguiente. - -### Paso 6: Transfiere la propiedad de la organización a tu cliente. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Verifica que tu cliente se encuentre en la lista de miembros de la organización y tenga el rol de *propietario* asignado. -5. A la derecha de tu nombre de usuario, usa el menú desplegable {% octicon "gear" aria-label="The Settings gear" %} y haz clic en **Administrar**. ![Enlace de acceso al gerente](/assets/images/help/organizations/member-manage-access.png) -6. A la izquierda, haz clic en **Eliminar de la organización**. ![Botón para eliminar de la organización ](/assets/images/help/organizations/remove-from-org-button.png) -7. Confirma tu opción y haz clic en **Eliminar miembros**. ![Botón para confirmar la eliminación de miembros](/assets/images/help/organizations/confirm-remove-from-org.png) - -### Pasos siguientes - -1. Ponte en contacto con tu cliente y pídele que [te agregue a la organización como gerente de facturación](/articles/adding-a-billing-manager-to-your-organization). Será necesario que seas un gerente de facturación de la organización para que puedas renovar la suscripción de tu cliente o hacer cambios en esta en el futuro. -2. Si deseas que la tarjeta de crédito de tu organización se elimine de la organización para que no vuelvan a hacerse cargos en ella, ponte en contacto con {% data variables.contact.contact_support %}. -3. Cuando sea el momento de renovar la suscripción paga de tu cliente, consulta "[Renovar la organización paga de tu cliente](/articles/renewing-your-client-s-paid-organization)". - -### Leer más - -- "[Acerca de las organizaciones para empresas de contratación](/articles/about-organizations-for-procurement-companies)" -- "[Actualizar o bajar de categoría la organización paga de tu cliente](/articles/upgrading-or-downgrading-your-client-s-paid-organization)" -- "[Renovar la organización paga de tu cliente](/articles/renewing-your-client-s-paid-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/index.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/index.md deleted file mode 100644 index b26da6f219..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Configurar organizaciones remuneradas para empresas de contratación -intro: 'Si pagas por {% data variables.product.product_name %} en nombre de un cliente, puedes configurar sus parámetros de organización y pago para optimizar la conveniencia y la seguridad.' -redirect_from: - - /articles/setting-up-and-paying-for-organizations-for-resellers/ - - /articles/setting-up-and-paying-for-organizations-for-procurement-companies/ - - /articles/setting-up-paid-organizations-for-procurement-companies -versions: - free-pro-team: '*' -topics: - - Billing -children: - - /about-organizations-for-procurement-companies - - /creating-and-paying-for-an-organization-on-behalf-of-a-client - - /upgrading-or-downgrading-your-clients-paid-organization - - /renewing-your-clients-paid-organization ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md deleted file mode 100644 index 69a6037baf..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Renovar la organización paga de tu cliente -intro: 'Si la organización de tu cliente tiene un método de pago válido archivado, su suscripción anual se renovará automáticamente. Los gerentes de facturación pueden ver y actualizar el método de pago y la suscripción de la organización.' -redirect_from: - - /articles/renewing-your-client-s-paid-organization - - /articles/renewing-your-clients-paid-organization - - /github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization -versions: - free-pro-team: '*' -topics: - - Billing ---- -{% data reusables.organizations.reseller-ask-to-become-billing-manager %} - -{% tip %} - -**Sugerencia**: Los gerentes de facturación también pueden [cambiar la cantidad de asientos pagos de la organización](/articles/upgrading-or-downgrading-your-client-s-paid-organization) en cualquier momento. - -{% endtip %} - -### Actualizar la tarjeta de crédito de tu organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.dotcom_billing.update_payment_method %} -1. Escribe la información nueva de tu tarjeta de crédito en el formulario seguro. ![Formulario de información de tarjeta de crédito](/assets/images/help/settings/creditcard-billing-form.png) -1. Haz clic en **Update credit card** (Actualizar tarjeta de crédito) o **Save credit card** (Guardar tarjeta de crédito). diff --git a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md deleted file mode 100644 index e02e6e16ab..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Subir o bajar de categoría la organización paga de tu cliente -intro: Los gerentes de facturación pueden subir o bajar de categoría la organización paga de un cliente en cualquier momento. -redirect_from: - - /articles/upgrading-or-downgrading-your-client-s-paid-organization - - /articles/upgrading-or-downgrading-your-clients-paid-organization - - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization -versions: - free-pro-team: '*' -topics: - - Billing ---- -{% data reusables.organizations.reseller-ask-to-become-billing-manager %} - -{% tip %} - -**Tips**: -- Antes de subir de categoría la organización de tu cliente, puedes [ver o actualizar el método de pago archivado para la organización](/articles/adding-or-editing-a-payment-method). -- Estas indicaciones son para subir o bajar de categoría organizaciones en la *suscripción por asiento*. Si tu cliente paga {% data variables.product.product_name %} utilizando un plan *por repositorio heredado*, puedes subir o [bajar de categoría](/articles/downgrading-your-github-subscription) su plan heredado o [cambiar su organización a un precio por asiento](/articles/upgrading-your-github-subscription). - -{% endtip %} - -### Subir de categoría la cantidad de asientos pagos de una organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.add-seats %} -{% data reusables.dotcom_billing.number-of-seats %} -{% data reusables.dotcom_billing.confirm-add-seats %} - -Después de agregar asientos, al método de pago archivado para la organización se le cobrará un monto prorrateado en función de la cantidad de asientos que agregues y la cantidad de tiempo que quede en tu ciclo de facturación. - -### Bajar la categoría de la cantidad de asientos pagos de una organización a gratuita - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -{% data reusables.user_settings.subscriptions-tab %} -{% data reusables.dotcom_billing.downgrade-org-to-free %} -{% data reusables.dotcom_billing.confirm_cancel_org_plan %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-organizations.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-organizations.md deleted file mode 100644 index d0c7319f8e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-organizations.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Acerca de las organizaciones -intro: 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. -redirect_from: - - /articles/about-organizations - - /github/setting-up-and-managing-organizations-and-teams/about-organizations -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.organizations.organizations_include %} - -{% if currentVersion == "free-pro-team@latest" %} -### Organizaciones y cuentas de empresa - -Las cuentas de empresa le permiten a los propietarios administrar en forma centralizada las políticas y la facturación de varias organizaciones de {% data variables.product.prodname_dotcom_the_website %}. - -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.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](/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization)". - -### Términos de servicio y protección de datos para organizaciones - -Una entidad, como una empresa, una organización sin fines de lucro o un grupo, puede aceptar los Términos de servicio estándar o los Términos de servicio corporativos para su organización. Para obtener más información, consulta "[Actualizarse a los Términos de servicio corporativos](/articles/upgrading-to-the-corporate-terms-of-service)". - -{% data reusables.organizations.enter-data-protection-agreement %} Para obtener más información, consulta "[Ingresar el contrato de protección de datos con {% data variables.product.prodname_dotcom %} para el cumplimiento con el RGPD](/articles/entering-a-data-protection-agreement-with-github-for-gdpr-compliance)". -{% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md deleted file mode 100644 index c8c93add09..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Acerca del tablero de tu organización -intro: 'Como miembro de una organización, puedes visitar el tablero de tu organización durante todo el día para estar actualizado sobre la actualidad reciente y hacer un seguimiento de las propuestas y las solicitudes de extracción en las que estás trabajando o siguiendo en la organización.' -redirect_from: - - /articles/about-your-organization-dashboard - - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acceder al tablero de tu organización - -{% data reusables.dashboard.access-org-dashboard %} - -### Encontrar tu actividad reciente - -En la sección "Recent activity" (Actividad reciente) de tus noticias, rápidamente puedes buscar las propuestas y solicitud de extracción de tu organización recientemente actualizadas y hacerles el seguimiento. - -{% data reusables.dashboard.recent-activity-qualifying-events %} - -### Encontrar repositorios en tu organización - -En la barra lateral izquierda de tu tablero, puedes acceder a los principales repositorios de tu organización en los que estás activo. - -![Listado delos repositorios en los que eres más activo de tu organización](/assets/images/help/dashboard/repositories-from-organization-dashboard.png) - -### Estar actualizado con la actividad desde tu organización - -En la sección "All activity" (Toda la actividad) de tus noticias, puedes ver actualizaciones de otros equipos y repositorios en tu organización. - -La sección "All activity" (Toda la actividad) muestra toda la actividad reciente en la organización, incluida la actividad en los repositorios a los que no estás suscrito y de las personas que no sigues. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"Acerca de las notificaciones] (/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Observar y dejar de observar los repositorios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" y "[Seguir a alguien](/articles/following-people)". - -Por ejemplo, las noticias de la organización muestran actualizaciones cuando alguien en la organización: - - Crea una rama nueva. - - Comenta en una propuesta o una solicitud de extracción. - - Envía un comentario de revisión de solicitud de extracción. - - Bifurca un repositorio. - - Crea una página wiki. - - Sube confirmaciones. - - Crea un repositorio público. - -### Información adicional - -- "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md deleted file mode 100644 index 71ff1fb08f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Acerca de las noticias de tu organización -intro: Puedes usar las noticias de tu organización para mantenerte al corriente de las actividades recientes en los repositorios que posee esa organización. -redirect_from: - - /articles/news-feed/ - - /articles/about-your-organization-s-news-feed - - /articles/about-your-organizations-news-feed - - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Las noticias de una organización muestran las actividades de otras personas en los repositorios que posee esa organización. Puedes usar las noticias de tu organización para ver cuando alguien abre, cierra o fusiona una propuesta o solicitud de extracción, crea o elimina una rama, crea una etiqueta o un lanzamiento, comenta en una propuesta, una solicitud de extracción o una confirmación de cambios o sube confirmaciones nuevas a {% data variables.product.product_name %}. - -### Acceder a las noticias de tu organización - -1. {% data variables.product.signin_link %} a tu cuenta de {% data variables.product.product_name %}. -2. Abre tu {% data reusables.user_settings.personal_dashboard %}. -3. Haz clic en el cambiador de contexto de la cuenta en la esquina superior izquierda de la página. ![Botón cambiador de contexto en Enterprise](/assets/images/help/organizations/account_context_switcher.png) -4. Selecciona una organización del menú desplegable.{% if currentVersion == "free-pro-team@latest" %} ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %} -![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md deleted file mode 100644 index afc02c220b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Acceder a los parámetros de tu organización -redirect_from: - - /articles/who-can-access-organization-billing-information-and-account-settings/ - - /articles/managing-the-organization-s-settings/ - - /articles/who-can-see-billing-information-account-settings/ - - /articles/who-can-see-billing-information-and-access-account-settings/ - - /articles/managing-an-organization-s-settings/ - - /articles/accessing-your-organization-s-settings - - /articles/accessing-your-organizations-settings - - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings -intro: 'La página de los parámetros de la cuenta de la organización brinda varias maneras de administrar la cuenta, como parámetros de facturación, miembros del equipo y repositorio.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% if currentVersion == "free-pro-team@latest" %} - -{% tip %} - -**Sugerencia:** Solo los propietarios de la organización y los gerentes de facturación pueden ver y cambiar la información de facturación y la configuración de la cuenta para una organización. {% data reusables.organizations.new-org-permissions-more-info %} - -{% endtip %} - -{% endif %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md deleted file mode 100644 index e11372490a..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Crear una organización nueva desde cero -intro: Crea una organización para aplicar permisos de acceso refinados a los repositorios. -redirect_from: - - /articles/creating-a-new-organization-from-scratch - - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cuando creas una organización nueva desde cero, esta no tiene ningún repositorio asociado. Para obtener más información acerca de cómo agregar repositorios a tu organización, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)" y "[Transferir un repositorio](/articles/transferring-a-repository)". - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.organizations %} -{% data reusables.organizations.new-organization %} -4. Sigue las propuestas para crear tu organización. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información sobre los planes disponibles para tu equipo, consulta los productos de "[{% data variables.product.prodname_dotcom %}](/articles/githubs-products)."{% endif %} - -### Leer más - -{% if currentVersion == "free-pro-team@latest" %} -- "[Establecer tu correo electrónico de facturación](/articles/setting-your-billing-email)"{% endif %} -- "[Acerca de las organizaciones](/articles/about-organizations)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/index.md deleted file mode 100644 index 0607668234..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Colaborar con grupos en organizaciones -intro: Los grupos de personas pueden colaborar en muchos proyectos a la vez en cuentas d ela organización. -redirect_from: - - /articles/creating-a-new-organization-account/ - - /articles/collaborating-with-groups-in-organizations -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-organizations - - /about-your-organization-dashboard - - /creating-a-new-organization-from-scratch - - /accessing-your-organizations-settings - - /about-your-organizations-news-feed - - /viewing-insights-for-your-organization ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md deleted file mode 100644 index d4c9a2aee0..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Ver información de tu organización -intro: 'La información de tu organización brinda datos acerca de la actividad, las contribuciones y las dependencias de tu organización.' -product: '{% data reusables.gated-features.org-insights %}' -redirect_from: - - /articles/viewing-insights-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization -versions: - free-pro-team: '*' ---- -Todos los miembros de una organización pueden ver información de la organización. Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". - -Puedes utilizar la información sobre la actividad de la organización para ayudarte a comprender mejor cómo los miembros de tu organización están utilizando {% data variables.product.product_name %} para colaborar y trabajar con el código. La información sobre las dependencias puede ayudarte a rastrear, informar y actuar en relación al uso del código abierto de tu organización. - -### Ver la información de la actividad de la organización - -{% note %} - -**Nota:**las perspectivas de actividad en las organizaciones se encuentran actualmente en un beta público y están sujetos a cambio. - -{% endnote %} - -Con la información sobre la actividad de la organización puedes ver semanal, mensual y anualmente las visualizaciones de datos de toda tu organización o de repositorios específicos, incluida la actividad de las propuestas y las solicitudes de extracción, los principales lenguajes utilizados e información acumulada sobre dónde los miembros de tu organización pasan su tiempo. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -3. Dentro del nombre de tu organización, haz clic en {% octicon "graph" aria-label="The bar graph icon" %} **Insights (Información)**. ![Haz clic en la pestaña de información de la organización](/assets/images/help/organizations/org-nav-insights-tab.png) -4. Como alternativa, en el ángulo superior derecho de la página, elige ver los datos del/de la último/a **semana**, **mes** o **año**. ![Elige un período de tiempo para ver la información de la organización](/assets/images/help/organizations/org-insights-time-period.png) -5. Alternativamente, en el ángulo superior derecho de la página, elige ver hasta tres repositorios y haz clic en **Apply (Aplicar)**. ![Elige repositorios para ver la información de la organización](/assets/images/help/organizations/org-insights-repos.png) - -### Ver la información de las dependencias de la organización -Con la información sobre las dependencias puedes ver vulnerabilidades, licencias y otra información importante de los proyectos de código abierto de los que depende tu organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -3. Dentro del nombre de tu organización, haz clic en {% octicon "graph" aria-label="The bar graph icon" %} **Insights (Información)**. ![Pestaña de información en la barra de navegación principal de la organización](/assets/images/help/organizations/org-nav-insights-tab.png) -4. Para ver las dependencias de esta organización, haz clic en **Dependencies (Dependencias)**. ![Pestaña de dependencias debajo de la barra de navegación principal de la organización](/assets/images/help/organizations/org-insights-dependencies-tab.png) -5. Para ver la información de las dependencias de todas tus organizaciones {% data variables.product.prodname_ghe_cloud %}, haz clic en **My organizations (Mis organizaciones)**. ![Botón Mi organización dentro de la pestaña de dependencias](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png) -6. Puedes hacer clic en los resultados de los gráficos **Open security advisories** (Avisos de seguridad abiertos) y **Licenses** (Licencias) para filtrar por estado de vulnerabilidad, por licencia o por una combinación de ambos. ![Gráficos de licencias y vulnerabilidades de mis organizaciones](/assets/images/help/organizations/org-insights-dependencies-graphs.png) -7. Puedes hacer clic en {% octicon "package" aria-label="The package icon" %} **dependents (dependientes)** al lado de cada vulnerabilidad para ver qué dependiente en tu organización está usando cada biblioteca. ![Dependientes vulnerables de mis organizaciones](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png) - - - ### Leer más - - - "[Acerca de las organizaciones](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" - - "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)" - - "[Cambiar la visibilidad de la información de dependencias de tu organización](/github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights)" - - "[Hacer cumplir una política sobre las percepciones de la dependencia en tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md deleted file mode 100644 index 433a8e80ba..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Acerca de la autenticación de dos factores y el inicio de sesión único de SAML -intro: Los administradores de las organizaciones pueden activar tanto el inicio de sesión único de SAML como la autenticación de dos factores para agregar medidas de autenticación adicionales para sus miembros de la organización. -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/about-two-factor-authentication-and-saml-single-sign-on - - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on -versions: - free-pro-team: '*' ---- -La autenticación de dos factores (2FA) ofrece una autenticación básica para los miembros de la organización. Al activar la 2FA, los administradores de la organización limitan la probabilidad de que la cuenta de {% data variables.product.product_name %} de un miembro se vea comprometida. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/articles/about-two-factor-authentication)". - -Para agregar medidas de autenticación adicionales, los administradores de la organización también pueden [activar el inicio de sesión único (SSO) de SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para que los miembros de la organización deban usar el inicio de sesión único para acceder a una organización. Para obtener más información sobre SAML SSO, consulta "[Acerca de la administración de identidad y acceso con inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)". - -Si tanto la 2FA como SAML SSO están activados, los miembros de la organización deben hacer lo siguiente: -- Usar la 2FA para iniciar sesión en su cuenta de {% data variables.product.product_name %}. -- Usar el inicio de sesión único para acceder a la organización. -- Usar un token autorizado para el acceso a Git o a la API y usar el inicio de sesión único para autorizar el token. - -### Leer más - -- "[Implementar el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/index.md deleted file mode 100644 index 95fa46fc23..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Conceder acceso a tu organización con el inicio de sesión único SAML -intro: 'Los administradores de la organización pueden conceder acceso con el inicio de sesión único SAML. Este acceso se les puede conceder a los miembros de la organización, a los bots y a las cuentas de servicio.' -redirect_from: - - /articles/granting-access-to-your-organization-with-saml-single-sign-on -versions: - free-pro-team: '*' -children: - - /managing-bots-and-service-accounts-with-saml-single-sign-on - - /viewing-and-managing-a-members-saml-access-to-your-organization - - /about-two-factor-authentication-and-saml-single-sign-on ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md deleted file mode 100644 index 5e39225a9f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Administrar bot y cuentas de servicio con inicio de sesión único de SAML -intro: Las organizaciones que han habilitado el inicio de sesión único de SAML pueden conservar el acceso para los bot y las cuentas de servicio. -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on - - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on -versions: - free-pro-team: '*' ---- -Para conservar el acceso a los bot y a las cuentas de servicio, los administradores de la organización pueden [habilitar](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), pero **no** [implementar](/articles/enforcing-saml-single-sign-on-for-your-organization) el inicio de sesión único de SAML para sus organizaciones. Si debes implementar el inicio de sesión único de SAML para tu organización, puedes crear una identidad externa para el bot o la cuenta de servicio con tu proveedor de identidad (IdP). - -{% warning %} - -**Nota:** Si implementas el inicio de sesión único de SAML para tu organización y **no** tienes identidades externas configuradas para bots y cuentas de servicio con tu IdP, estas se eliminarán de tu organización. - -{% endwarning %} - -### Leer más - -- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md deleted file mode 100644 index b7abbf4f74..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Visualizar y administrar el acceso de SAML de un miembro a tu organización -intro: 'Puedes ver y revocar la identidad vinculada de un miembro de la organización, sesiones activas y credenciales autorizadas.' -permissions: Los dueños de organización pueden ver y administrar el acceso de SAML de un miembro a la misma. -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/viewing-and-revoking-organization-members-authorized-access-tokens - - /github/setting-up-and-managing-organizations-and-teams/viewing-and-revoking-organization-members-authorized-access-tokens - - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization -versions: - free-pro-team: '*' ---- -### Acerca del acceso de SAML a tu organización - -Cuando habilitas el inicio de sesión único de SAML para tu organización, cada miembro de ella puede vincular su identidad externa con tu proveedor de identidad (IdP) a su cuenta existente de {% data variables.product.product_name %}. Para acceder a los recursos de tu organización en {% data variables.product.product_name %}, el miembro debe tener una sesión activa de SAML en su buscador. Para acceder a los recursos de tu organización utilizando Git o la API, el miembro debe utilizar un token de acceso personal o llave SSH que se le haya autorizado para su uso con tu organización. - -Puedes ver y revocar la identidad vinculada de cada miembro, sesiones activas y credenciales auotrizadas en la misma página. - -### Visualizar y revocar una identidad vinculada - -{% data reusables.saml.about-linked-identities %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.saml.click-person-revoke-identity %} -{% data reusables.saml.saml-identity-linked %} -{% data reusables.saml.view-sso-identity %} -{% data reusables.saml.revoke-sso-identity %} -{% data reusables.saml.confirm-revoke-identity %} - -### Ver y revocar una sesión activa de SAML - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.saml.click-person-revoke-session %} -{% data reusables.saml.saml-identity-linked %} -{% data reusables.saml.view-saml-sessions %} -{% data reusables.saml.revoke-saml-session %} - -### Visualizar y revocar credenciales autorizadas - -{% data reusables.saml.about-authorized-credentials %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.saml.click-person-revoke-credentials %} -{% data reusables.saml.saml-identity-linked %} -{% data reusables.saml.view-authorized-credentials %} -{% data reusables.saml.revoke-authorized-credentials %} -{% data reusables.saml.confirm-revoke-credentials %} - -### Leer más - -- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" -- "[Visualizar y administrar el acceso de SAML de un usuario a tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/index.md deleted file mode 100644 index 775bdda0bc..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/index.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Configurar y administrar organizaciones y equipos -shortTitle: Organizaciones y equipos -intro: 'Colaborar en muchos proyectos mientras se administra el acceso a proyectos y datos, y se personalizan las configuraciones para tu organización.' -redirect_from: - - /articles/about-improved-organization-permissions/ - - /categories/setting-up-and-managing-organizations-and-teams -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /collaborating-with-groups-in-organizations - - /managing-membership-in-your-organization - - /managing-peoples-access-to-your-organization-with-roles - - /organizing-members-into-teams - - /managing-access-to-your-organizations-repositories - - /managing-access-to-your-organizations-project-boards - - /managing-access-to-your-organizations-apps - - /managing-organization-settings - - /migrating-to-improved-organization-permissions - - /restricting-access-to-your-organizations-data - - /keeping-your-organization-secure - - /managing-saml-single-sign-on-for-your-organization - - /granting-access-to-your-organization-with-saml-single-sign-on - - /managing-git-access-to-your-organizations-repositories ---- -### Índice - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/index.md deleted file mode 100644 index 7649b38a8d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Mantener segura tu organización -redirect_from: - - /articles/preventing-unauthorized-access-to-organization-information/ - - /articles/keeping-your-organization-secure -intro: 'Los propietarios de la organización tienen varias funciones que los ayudan a mantener seguros los proyectos y los datos. Si eres propietario de una organización, debes revisar de manera constante el registro de auditoría, el estado de 2FA del miembro y las configuraciones de aplicación de tu organización para asegurarte de que no haya ocurrido ninguna actividad no autorizada o maliciosa.' -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /viewing-whether-users-in-your-organization-have-2fa-enabled - - /preparing-to-require-two-factor-authentication-in-your-organization - - /requiring-two-factor-authentication-in-your-organization - - /managing-security-and-analysis-settings-for-your-organization - - /managing-secret-scanning-for-your-organization - - /managing-allowed-ip-addresses-for-your-organization - - /restricting-email-notifications-to-an-approved-domain - - /reviewing-the-audit-log-for-your-organization - - /reviewing-your-organizations-installed-integrations ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md deleted file mode 100644 index f77c05693c..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Administrar las direcciones IP permitidas en tu organización -intro: Puedes restringir el acceso a los activos de tu organización si configuras una lista de direcciones IP que se pueden conectar a ella. -product: '{% data reusables.gated-features.allowed-ip-addresses %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization ---- -Los propietarios de las organizaciones pueden administrar las direcciones IP permitidas en las mismas. - -### Acerca de las direcciones IP permitidas - -Puedes restringir el acceso a los activos de la organización configurando un listado de direcciones IP específicas permitidas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %} - -{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %} - -{% data reusables.identity-and-permissions.ip-allow-lists-enable %} - -También puedes configurar las direcciones IP permitidas para las organizaciones en una cuenta empresarial. Para obtener más información, consulta la sección "[Requerir los parámetros de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)". - -### Agregar una dirección IP permitida - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} -{% data reusables.identity-and-permissions.ip-allow-lists-add-description %} -{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} - -### Habilitar direcciones IP permitidas - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -3. En "IP allow list" (Lista de permisos de IP), seleccione **Enable IP allow list** (Habilitar lista de permisos de IP). ![Realizar una marca de verificación para permitir direcciones IP](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png) -4. Haz clic en **Save (Guardar)**. - -### Editar una dirección IP permitida - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} -{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} -{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %} -8. Da clic en **Actualizar**. - -### Eliminar una dirección IP permitida - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} -{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %} - -### Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas - -{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-secret-scanning-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-secret-scanning-for-your-organization.md deleted file mode 100644 index f9e6f46e9d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-secret-scanning-for-your-organization.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Administrar el escaneo de secretos para tu organización -intro: 'Puedes controlar qué repositorios en tu organización escaneará {% data variables.product.product_name %} en busca de secretos.' -permissions: 'Los propietarios de la organización pueden administrar el {% data variables.product.prodname_secret_scanning %} para los repositorios que le pertenecen a ésta.' -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization ---- -{% data reusables.secret-scanning.beta %} - -### Acerca de la administración del {% data variables.product.prodname_secret_scanning %} - -{% data variables.product.prodname_secret_scanning_caps %} te puede ayudar a mitigar el impacto de los secretos que se filtran en los repositorios de tu organización. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)". - -Puedes administrar cómo {% data variables.product.prodname_dotcom %} escanea los secretos en los repositorios existentes dentro de tu organización. También puedes habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %} predeterminado para cualquier repositorio nuevo que creen los miembros dentro de tu organización. - -{% data reusables.security.security-and-analysis-features-enable-read-only %} - -{% note %} - -**Nota**: El {% data variables.product.prodname_secret_scanning_caps %} se habilita predeterminadamente para los repositorios públicos en tu organización y no puede inhabilitarse. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos para los repositorios públicos](/github/administering-a-repository/about-secret-scanning#about-secret-scanning-for-public-repositories)". - -{% endnote %} - -### Habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios privados existentes - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. A la derecha de "Escaneo de secretos", da clic en **Inhabilitar todos** o **Habilitar todos**. ![Botón de "Habilitar todos" o "Inhabilitar todos" para el escaneo de secretos](/assets/images/help/organizations/security-and-analysis-disable-or-enable-secret-scanning.png) -6. Opcionalmente, habilita el {% data variables.product.prodname_secret_scanning %} predeterminado para los repositorios en tu organización. ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-secret-scanning-enable-by-default.png) -7. Da clic en **Inhabilitar el escaneo de secretos** o en **Habilitar el escaneo de secretos** para inhabilitar o habilitar esta característica en todos los repositorios de tu organización. ![Botón para inhabilitar o habilitar el {% data variables.product.prodname_secret_scanning %} ](/assets/images/help/organizations/security-and-analysis-enable-secret-scanning.png) - -### Habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %} para los repositorios privados - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. A la derecha de "Escaneo de secretos", habilita o inhabilita la característica predeterminada para los repositorios privados nuevos en tu organización. ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md deleted file mode 100644 index 762670be29..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Administrar los parámetros de seguridad y análisis para tu organización -intro: 'Puedes controlar las características que aseguran y analizan el código en los proyectos de tu organización en {% data variables.product.prodname_dotcom %}.' -permissions: Los propietarios de la organización pueden administrar los parámetros de seguridad y de análisis para los repositorios en la organización. -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization ---- -### Acerca de la administración de los parámetros de seguridad y análisis - -{% data variables.product.prodname_dotcom %} puede ayudarte a asegurar los repositorios en tu organización. Puedes administrar las características de seguridad y de análisis para todos los repositorios existentes que los miembros creen en tu organización. - -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} - -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.security.security-and-analysis-features-enable-read-only %} -{% endif %} - -### Habilitar o inhabilitar las características para los repositorios existentes - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all.png) -6. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización. ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png) -7. Da clic en **Inhabilitar CARACTERÍSTICA** o en **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios en tu organización. ![Botón para inhabilitar o habilitar la característica](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png) - -### Habilitar o inhabilitar las características para los repositorios nuevos - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security-and-analysis %} -5. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, habilítala o inhabilítala para los repositorios nuevos en tu organización. ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png) - -### Leer más - -{% if currentVersion == "free-pro-team@latest" %}- "[Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)" -- "[Acerca del escaneo de secretos](/github/administering-a-repository/about-secret-scanning)" -- "[Mantener tus dependencias actualizadas automáticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)" -{% endif %} -- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Administrar las vulnerabilidades en las dependencias de tu proyecto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md deleted file mode 100644 index 99602d0419..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Prepararse para requerir autenticación de dos factores en tu organización -intro: 'Antes de requerir la autenticación de dos factores (2FA), puedes notificar a los usuarios acerca del futuro cambio y verificar quien ya utiliza 2FA.' -redirect_from: - - /articles/preparing-to-require-two-factor-authentication-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Recomendamos que notifiques a {% if currentVersion == "free-pro-team@latest" %}los miembros de la organización, a los colaboradores externos y a los gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} por lo menos una semana antes de requerir 2FA en tu organización. - -Cuando solicitas que se use la autenticación de dos factores para tu organización, los miembros, los colaboradores externos y los gerentes de facturación (incluidas las cuentas bot) que no utilizan 2FA se eliminarán de tu organización y perderán acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización. - -Antes de solicitar 2FA en tu organización, recomendamos que: - - [Habilites 2FA](/articles/securing-your-account-with-two-factor-authentication-2fa/) en tu cuenta personal - - Le solicites a las personas en tu organización que configuren 2FA en sus cuentas - - Consultes si [los usuarios en tu organizacipon tienen habilitado el 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/) - - Le adviertas a los usuarios que una vez que el 2FA esté habilitado, aquellos sin 2FA se eliminarán automáticamente de la organización diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md deleted file mode 100644 index 8dc56687bd..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Solicitar autenticación de dos factores en tu organización -intro: 'Los propietarios de la organización pueden requerir que los {% if currentVersion == "free-pro-team@latest" %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} habiliten la autenticación de dos factores para sus cuentas personales, lo que hace que sea más complicado para los actores maliciosos acceder a los repositorios y parámetros de una organización.' -redirect_from: - - /articles/requiring-two-factor-authentication-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.two_fa.auth_methods_2fa %} - -### Requisitos para aplicar la autenticación de dos factores - -Antes de que puedas requerir que los {% if currentVersion == "free-pro-team@latest" %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} utilicen la 2FA, debes [habilitar la autenticación de dos factores](/articles/securing-your-account-with-two-factor-authentication-2fa/) para tu propia cuenta personal. - -{% warning %} - -**Advertencias:** - -- Cuando requieres el uso de autenticación de dos factores para tu organización, los {% if currentVersion == "free-pro-team@latest" %}miembros, colaboradores externos y gerentes de facturación{% else %}miembros y colaboradores externos{% endif %} (incluidas las cuentas de bot) que no utilicen la 2FA se eliminarán de la organización y perderán el acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización. Puedes [reinstalar sus privilegios y parámetros de acceso](/articles/reinstating-a-former-member-of-your-organization) si habilitan la autenticación de dos factores para su cuenta personal en el transcurso de los tres meses posteriores a la eliminación desde tu organización. -- Si un propietario de la organización, miembro,{% if currentVersion == "free-pro-team@latest" %} gerente de facturación{% endif %} o colaborador externo inhabilita la 2FA para su cuenta personal después de que hayas habilitado la autenticación de dos factores requerida, se lo eliminará automáticamente de la organización. -- Si eres el único propietario de una organización que requiere autenticación de dos factores, no podrás inhabilitar la 2FA de tu cuenta personal sin inhabilitar la autenticación de dos factores para la organización. - -{% endwarning %} - -Antes de que requieras el uso de autenticación de dos factores, recomendamos que se lo notifiques a los {% if currentVersion == "free-pro-team@latest" %}miembros de la organización, colaboradores externos y gerentes de facturación{% else %}miembros de la organización y colaboradores externos{% endif %} y les solicites que configuren la 2FA para sus cuentas. Puedes [ver si los miembros y colaboradores externos ya utilizan la 2FA](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) en la página de Personas de tu organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.organizations.require_two_factor_authentication %} -{% data reusables.organizations.removed_outside_collaborators %} -{% if currentVersion == "free-pro-team@latest" %} -8. Si algún miembro o colaborador externo se elimina de tu organización, te recomendamos enviarle una invitación para reinstalar sus privilegios antiguos y el acceso a tu organización. Deben habilitar la autenticación de dos factores para poder aceptar la invitación. -{% endif %} - -### Ver las personas que se eliminaron de tu organización - -Para ver las personas que se eliminaron automáticamente de tu organización por no cumplir cuando les requeriste la autenticación de dos factores, puedes [buscar el registro de auditoría de tu organización](/articles/reviewing-the-audit-log-for-your-organization/#accessing-the-audit-log) para las personas eliminadas de tu organización. El evento de registro de auditoría mostrará si se eliminó a una persona por no cumplir con la 2FA. - -![Evento de registro de auditoría que muestra un usuario eliminado por no cumplir con la 2FA](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png) - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.audit_log.audit_log_sidebar_for_org_admins %} -4. Ingresa tu consulta de búsqueda. Para buscar por: - - Miembros de la organización eliminados, utiliza `action:org.remove_member` en tu consulta de búsqueda - - Colaboradores externos eliminados, utiliza `action:org.remove_outside_collaborator` en tu consulta de búsqueda{% if currentVersion == "free-pro-team@latest" %} - - Gerentes de facturación eliminados, utiliza `action:org.remove_billing_manager`en tu consulta de búsqueda{% endif %} - - También puedes ver las personas que se eliminaron de tu organización utilizando un [período de tiempo](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) en tu búsqueda. - -### Ayudar a que los miembros y colaboradores externos eliminados se vuelvan a unir a tu organización - -Si algún miembro o colaborador externo se eliminó de la organización cuando habilitaste el uso requerido de autenticación de dos factores, recibirá un correo electrónico que le notifique que ha sido eliminado. Debe entonces habilitar la 2FA para su cuenta personal y contactarse con un propietario de la organización para solicitar acceso a tu organización. - -### Leer más - -- "[Ver si los usuarios de tu organización tienen la 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" -- "[Proteger tu cuenta con autenticación de dos factores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)" -- "[Reinstalar un miembro antiguo de tu organización](/articles/reinstating-a-former-member-of-your-organization)" -- "[Reinstalar el acceso a tu organización de un colaborador externo antiguo](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md deleted file mode 100644 index 3a566cc802..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Restringir las notificaciones por correo electrónico para un dominio aprobado -intro: 'Para evitar que se fugue información de la organización a las cuentas personales, los propietarios de la organización pueden restringir las notificaciones por correo electrónico sobre la actividad de una organización para un dominio verificado.' -product: '{% data reusables.gated-features.restrict-email-domain %}' -redirect_from: - - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain/ - - /articles/restricting-email-notifications-to-an-approved-domain - - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain -versions: - free-pro-team: '*' ---- -Cuando se habilitan las notificaciones por correo electrónico restringidas en una organización, los miembros solo pueden recibir notificaciones por correo electrónico acerca de la actividad de la organización en una dirección de correo electrónico asociada con el dominio verificado de la organización. Para obtener más información, consulta "[Verificar el dominio de tu organización](/articles/verifying-your-organization-s-domain)". - -Los colabores externos no están sujetos a las restricciones en las notificaciones por correo electrónico para los dominios verificados. Para obtener más información sobre los colaboradores externos, consulta la sección "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.verified-domains %} -5. En "Enforcement preferences" (Preferencias de aplicación), selecciona **Restrict email notifications to domain email** (Restringir las notificaciones por correo electrónico para el correo electrónico del dominio). ![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) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md deleted file mode 100644 index 221e054c70..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ /dev/null @@ -1,425 +0,0 @@ ---- -title: Reviewing the audit log for your organization -intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.' -redirect_from: - - /articles/reviewing-the-audit-log-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Accessing the audit log - -The audit log lists actions performed within the last 90 days. Only owners can access an organization's audit log. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.audit_log.audit_log_sidebar_for_org_admins %} - -### Searching the audit log - -{% data reusables.audit_log.audit-log-search %} - -#### Search based on the action performed - -To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories: - -| Category Name | Description -|------------------|-------------------{% if currentVersion == "free-pro-team@latest" %} -| `account` | Contains all activities related to your organization account.{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| `billing` | Contains all activities related to your organization's billing.{% endif %} -| `discussion_post` | Contains all activities related to discussions posted to a team page. -| `discussion_post_reply` | Contains all activities related to replies to discussions posted to a team page. -| `hook` | Contains all activities related to webhooks. -| `integration_installation_request` | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% if currentVersion == "free-pro-team@latest" %} -| `marketplace_agreement_signature` | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. -| `marketplace_listing` | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| `members_can_create_pages` | Contains all activities related to disabling the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." | {% endif %} -| `org` | Contains all activities related to organization membership{% if currentVersion == "free-pro-team@latest" %} -| `org_credential_authorization` | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| `organization_label` | Contains all activities related to default labels for repositories in your organization.{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| `payment_method` | Contains all activities related to how your organization pays for GitHub.{% endif %} -| `profile_picture` | Contains all activities related to your organization's profile picture. -| `project` | Contains all activities related to project boards. -| `protected_branch` | Contains all activities related to protected branches. -| `repo` | Contains all activities related to the repositories owned by your organization.{% if currentVersion == "free-pro-team@latest" %} -| `repository_content_analysis` | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data). -| `repository_dependency_graph` | Contains all activities related to [enabling or disabling the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository).{% endif %} -| `repository_vulnerability_alert` | Contains all activities related to [{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% if currentVersion == "free-pro-team@latest" %} -| `sponsors` | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% if currentVersion != "free-pro-team@latest" %} -| `team` | Contains all activities related to teams in your organization.{% endif %} -| `team_discussions` | Contains activities related to managing team discussions for an organization. - -You can search for specific sets of actions using these terms. For example: - - * `action:team` finds all events grouped within the team category. - * `-action:hook` excludes all events in the webhook category. - -Each category has a set of associated events that you can filter on. For example: - - * `action:team.create` finds all events where a team was created. - * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered. - -This list describes the available categories and associated events: - -{% if currentVersion == "free-pro-team@latest" %}- [The `account` category](#the-account-category) -- [The `billing` category](#the-billing-category){% endif %} -- [The `discussion_post` category](#the-discussion_post-category) -- [The `discussion_post_reply` category](#the-discussion_post_reply-category) -- [The `hook` category](#the-hook-category) -- [The `integration_installation_request` category](#the-integration_installation_request-category) -- [The `issue` category](#the-issue-category){% if currentVersion == "free-pro-team@latest" %} -- [The `marketplace_agreement_signature` category](#the-marketplace_agreement_signature-category) -- [The `marketplace_listing` category](#the-marketplace_listing-category){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -- [The `members_can_create_pages` category](#the-members_can_create_pages-category){% endif %} -- [The `org` category](#the-org-category){% if currentVersion == "free-pro-team@latest" %} -- [The `org_credential_authorization` category](#the-org_credential_authorization-category){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -- [The `organization_label` category](#the-organization_label-category){% endif %} -- [The `oauth_application` category](#the-oauth_application-category){% if currentVersion == "free-pro-team@latest" %} -- [The `payment_method` category](#the-payment_method-category){% endif %} -- [The `profile_picture` category](#the-profile_picture-category) -- [The `project` category](#the-project-category) -- [The `protected_branch` category](#the-protected_branch-category) -- [The `repo` category](#the-repo-category){% if currentVersion == "free-pro-team@latest" %} -- [The `repository_content_analysis` category](#the-repository_content_analysis-category) -- [The `repository_dependency_graph` category](#the-repository_dependency_graph-category){% endif %} -- [The `repository_vulnerability_alert` category](#the-repository_vulnerability_alert-category){% if currentVersion == "free-pro-team@latest" %} -- [The `sponsors` category](#the-sponsors-category){% endif %}{% if currentVersion != "free-pro-team@latest" %} -- [The `team` category](#the-team-category){% endif %} -- [The `team_discussions` category](#the-team_discussions-category) - -{% if currentVersion == "free-pro-team@latest" %} - -##### The `account` category - -| Action | Description -|------------------|------------------- -| `billing_plan_change` | Triggered when an organization's [billing cycle](/articles/changing-the-duration-of-your-billing-cycle) changes. -| `plan_change` | Triggered when an organization's [subscription](/articles/about-billing-for-github-accounts) changes. -| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). -| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/). - -##### The `billing` category - -| Action | Description -|------------------|------------------- -| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). -| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes. - -{% endif %} - -##### The `discussion_post` category - -| Action | Description -|------------------|------------------- -| `update` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). -| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). - -##### The `discussion_post_reply` category - -| Action | Description -|------------------|------------------- -| `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). -| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). - -##### The `hook` category - -| Action | Description -|------------------|------------------- -| `create` | Triggered when [a new hook was added](/articles/creating-webhooks) to a repository owned by your organization. -| `config_changed` | Triggered when an existing hook has its configuration altered. -| `destroy` | Triggered when an existing hook was removed from a repository. -| `events_changed` | Triggered when the events on a hook have been altered. - -##### The `integration_installation_request` category - -| Action | Description -|------------------|------------------- -| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. -| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. - -##### The `issue` category - -| Action | Description -|------------------|------------------- -| `destroy` | Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository. - -{% if currentVersion == "free-pro-team@latest" %} - -##### The `marketplace_agreement_signature` category - -| Action | Description -|------------------|------------------- -| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. - -##### The `marketplace_listing` category - -| Action | Description -|------------------|------------------- -| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. -| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. -| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. -| `redraft` | Triggered when your listing is sent back to draft state. -| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - -##### The `members_can_create_pages` category - -For more information, see "[Restricting publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." - -| Action | Description | -| :- | :- | -| `enable` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | -| `disable` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | - -{% endif %} - -##### The `org` category - -| Action | Description -|------------------|-------------------{% if currentVersion == "free-pro-team@latest"%} -| `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. -| `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/articles/blocking-a-user-from-your-organization). -| `cancel_invitation` | Triggered when an organization invitation has been revoked. -| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization. -| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %} -| `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." | -| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators in an organization.{% if currentVersion == "free-pro-team@latest" %} -| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization. -| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %} -| `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." | -| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% if currentVersion == "free-pro-team@latest" %}, billing managers,{% endif %} and outside collaborators in an organization. -| `invite_member` | Triggered when [a new user was invited to join your organization](/articles/adding-organization-members-to-a-team).{% if currentVersion == "free-pro-team@latest" %} -| `oauth_app_access_approved` | Triggered when an owner [grants organization access to an {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). -| `oauth_app_access_denied` | Triggered when an owner [disables a previously approved {% data variables.product.prodname_oauth_app %}'s access](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to your organization. -| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %}{% if currentVersion == "free-pro-team@latest" %} -| `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. |{% endif %} -| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization.| -| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA. |{% if currentVersion == "free-pro-team@latest" %} -| `revoke_external_identity` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." -| `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." -| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/articles/unblocking-a-user-from-your-organization).{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -| `update_new_repository_default_branch_setting` | Triggered when an owner changes the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization)."{% endif %} -| `update_default_repository_permission` | Triggered when an owner changes the default repository permission level for organization members. -| `update_member` | Triggered when an owner changes a person's role from owner to member or member to owner. -| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% if currentVersion == "free-pro-team@latest" %} -| `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated. -| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -##### The `org_credential_authorization` category - -| Action | Description -|------------------|------------------- -| `grant` | Triggered when a member [authorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). -| `deauthorized` | Triggered when a member [deauthorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). -| `revoke` | Triggered when an owner [revokes authorized credentials](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization). - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -##### The `organization_label` category - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a default label is created. -| `update` | Triggered when a default label is edited. -| `destroy` | Triggered when a default label is deleted. - -{% endif %} - -##### The `oauth_application` category - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. -| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. -| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. -| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. -| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. - -{% if currentVersion == "free-pro-team@latest" %} - -##### The `payment_method` category - -| Action | Description -|------------------|------------------- -| `clear` | Triggered when a payment method on file is [removed](/articles/removing-a-payment-method). -| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account. -| `update` | Triggered when an existing payment method is updated. - -{% endif %} - -##### The `profile_picture` category -| Action | Description -|------------------|------------------- -| update | Triggered when you set or update your organization's profile picture. - -##### The `project` category - -| Action | Description -|--------------------|--------------------- -| `create` | Triggered when a project board is created. -| `link` | Triggered when a repository is linked to a project board. -| `rename` | Triggered when a project board is renamed. -| `update` | Triggered when a project board is updated. -| `delete` | Triggered when a project board is deleted. -| `unlink` | Triggered when a repository is unlinked from a project board. -| `update_org_permission` | Triggered when the base-level permission for all organization members is changed or removed. | -| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. | -| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.| - -##### The `protected_branch` category - -| Action | Description -|--------------------|--------------------- -| `create ` | Triggered when branch protection is enabled on a branch. -| `destroy` | Triggered when branch protection is disabled on a branch. -| `update_admin_enforced ` | Triggered when branch protection is enforced for repository administrators. -| `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch. -| `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch. -| `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch. -| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. -| `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. -| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. -| `rejected_ref_update ` | Triggered when a branch update attempt is rejected. -| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -| `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. -| `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. -| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. -{% endif %} - -##### The `repo` category - -| Action | Description -|------------------|------------------- -| `access` | Triggered when a repository owned by an organization is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa). -| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). -| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository. -| `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% if currentVersion != "free-pro-team@latest" %} -| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. -| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). -| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} -| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository). -| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% if currentVersion == "free-pro-team@latest" %} -| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %} -| `enable` | Triggered when a repository is reenabled. -| `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository). -| `remove_topic` | Triggered when a repository admin removes a topic from a repository. -| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository). -| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). -| `transfer_start` | Triggered when a repository transfer is about to occur. -| `unarchived` | Triggered when a repository admin unarchives a repository. - -{% if currentVersion == "free-pro-team@latest" %} - -##### The `repository_content_analysis` category - -| Action | Description -|------------------|------------------- -| `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). -| `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository). - -##### The `repository_dependency_graph` category - -| Action | Description -|------------------|------------------- -| `enable` | Triggered when a repository owner or person with admin access to the repository [enables the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository). -| `disable` | Triggered when a repository owner or person with admin access to the repository [disables the dependency graph for a private repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository). - -{% endif %} -##### The `repository_vulnerability_alert` category - -| Action | Description -|------------------|------------------- -| `create` | Triggered when {% data variables.product.product_name %} creates a [{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} alert for a vulnerable dependency](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a particular repository. -| `resolve` | Triggered when someone with write access to a repository [pushes changes to update and resolve a vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a project dependency. -| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_short %}{% else %}security{% endif %} alert about a vulnerable dependency.{% if currentVersion == "free-pro-team@latest" %} -| `authorized_users_teams` | Triggered when an organization owner or a member with admin permissions to the repository [updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_short %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-github-dependabot-alerts) for vulnerable dependencies in the repository.{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -##### The `sponsors` category - -| Action | Description -|------------------|------------------- -| repo_funding_link_button_toggle | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -| repo_funding_links_file_action | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") -{% endif %} - -{% if currentVersion != "free-pro-team@latest" %} -##### The `team` category - -| Action | Description -|------------------|------------------- -| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team). -| `add_repository` | Triggered when a team is given control of a repository. -| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). -| `change_privacy` | Triggered when a team's privacy level is changed. -| `create` | Triggered when a new team is created. -| `destroy` | Triggered when a team is deleted from the organization. -| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). -| `remove_repository` | Triggered when a repository is no longer under a team's control. -{% endif %} - -##### The `team_discussions` category - -| Action | Description -|---|---| -| `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." -| `enable` | Triggered when an organization owner enables team discussions for an organization. - -#### Search based on time of action - -Use the `created` qualifier to filter actions in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} - -{% data reusables.search.date_gt_lt %} For example: - - * `created:2014-07-08` finds all events that occurred on July 8th, 2014. - * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. - * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014. - * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. - -The audit log contains data for the past 90 days, but you can use the `created` qualifier to search for events earlier than that. - -#### Search based on location - -Using the qualifier `country`, you can filter actions in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example: - - * `country:de` finds all events that occurred in Germany. - * `country:Mexico` finds all events that occurred in Mexico. - * `country:"United States"` all finds events that occurred in the United States. - -{% if currentVersion == "free-pro-team@latest" %} -### Exporting the audit log - -{% data reusables.audit_log.export-log %} -{% data reusables.audit_log.exported-log-keys-and-values %} -{% endif %} - -### Using the Audit log API - -{% note %} - -**Note**: The Audit log API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} - -{% endnote %} - -To ensure a secure IP and maintain compliance for your organization, you can use the Audit log API to keep copies of your audit log data and monitor: -* Access to your organization or repository settings. -* Changes in permissions. -* Added or removed users in an organization, repository, or team. -* Users being promoted to admin. -* Changes to permissions of a GitHub App. - -The GraphQL response can include data for up to 90 to 120 days. - -For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log](/graphql/reference/interfaces#auditentry/)." - -### Further reading - -- "[Keeping your organization secure](/articles/keeping-your-organization-secure)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md deleted file mode 100644 index 844bd26ec9..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Reviewing your organization's installed integrations -intro: You can review the permission levels for your organization's installed integrations and configure each integration's access to organization repositories. -redirect_from: - - /articles/reviewing-your-organization-s-installed-integrations - - /articles/reviewing-your-organizations-installed-integrations - - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -4. In the left sidebar, click **Installed {% data variables.product.prodname_github_app %}s**. - ![Installed {% data variables.product.prodname_github_app %}s tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png) -5. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**. - ![Configure button](/assets/images/help/organizations/configure-installed-integration-button.png) -6. Review the {% data variables.product.prodname_github_app %}'s permissions and repository access. - ![Option to give the {% data variables.product.prodname_github_app %} access to all repositories or specific repositories](/assets/images/help/organizations/toggle-integration-repo-access.png) - - To give the {% data variables.product.prodname_github_app %} access to all of your organization's repositories, select **All repositories**. - - To choose specific repositories to give the application access to, select **Only select repositories**, then type a repository name. -7. Click **Save**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md deleted file mode 100644 index e8f86b341e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Ver si los usuarios en tu organización han habilitado 2FA -intro: 'Puedes ver los propietarios de la organización, miembros y colaboradores externos que han habilitado la autenticación de dos factores.' -redirect_from: - - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled - - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% note %} - -**Nota:** puedes solicitar que todos los miembros {% if currentVersion == "free-pro-team@latest" %}, incluidos, los propietarios, gerentes de facturación y{% else %} y{% endif %} colaboradores externos en tu organización tengan habilitada la autenticación de dos factores. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/articles/requiring-two-factor-authentication-in-your-organization)". - -{% endnote %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Para ver los miembros de la organización, incluidos los propietarios de la organización, que han habilitado o inhabilitado la autenticación de dos factores, a la derecha, haz clic en **2FA** y selecciona **Enabled** (Habilitado) o **Disabled** (Inhabilitado). ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png) -5. Para ver los colaboradores externos en tu organización, dentro de la pestaña "People" (Personas), haz clic en **Outside collaborators (Colaboradores externos)**. ![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png) -6. Para ver qué colaboradores externos han habilitado o inhabilitado la autenticación de dos factores, a la derecha, haz clic en **2FA** y selecciona **Enabled** (Habilitado) o **Disabled** (Inhabilitado). ![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png) - -### Leer más - -- "[Ver los roles de las personas en un organización](/articles/viewing-people-s-roles-in-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md deleted file mode 100644 index 268024b49e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Agregar administradores de App GitHub a tu organización -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_app %}s 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 -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Para más información sobre los permisos de 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)". - -### Brindar a alguien la posibilidad de administrar todos los {% data variables.product.prodname_github_app %} que son propiedad de la organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.github-apps-settings-sidebar %} -1. En "Management" (Administración), escribe el nombre de usuario de la persona a quien deseas designar como gerente de {% data variables.product.prodname_github_app %} en la organización, y haz clic en **Grant** (Conceder). ![Agregar un administrador de {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/add-github-app-manager.png) - -### Brindar a alguien la posibilidad de administrar un {% data variables.product.prodname_github_app %} individual - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.github-apps-settings-sidebar %} -1. Debajo de "{% data variables.product.prodname_github_app %}s", haz clic en el avatar de la app a la que quieres agregarle 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) - -{% if currentVersion == "free-pro-team@latest" %} -### Leer más - -- "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)" -{% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/index.md deleted file mode 100644 index a2001fce03..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Administrar el acceso a las aplicaciones de tu organización -intro: 'Como propietario de la organización, puedes permitir a los miembros individuales de la organización a administrar las aplicaciones {% data variables.product.prodname_github_app %} en tu organización.' -redirect_from: - - /articles/managing-access-to-your-organization-s-apps - - /articles/managing-access-to-your-organizations-apps -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /adding-github-app-managers-in-your-organization - - /removing-github-app-managers-from-your-organization ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md deleted file mode 100644 index 41b8c16c89..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Eliminar administradores de App GitHub de tu organización -intro: 'Los propietarios de la organización pueden revocar los permisos de administrador {% data variables.product.prodname_github_app %} que se le hayan concedido a un miembro de la organización.' -redirect_from: - - /articles/removing-github-app-managers-from-your-organization - - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Para más información sobre los permisos de 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)". - -### Eliminar los {% data variables.product.prodname_github_app %} permisos de un administrador para toda la organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.github-apps-settings-sidebar %} -1. En "Management" (Administración), 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.png) - -### Eliminar los {% data variables.product.prodname_github_app %} permisos de administrador para una persona {% data variables.product.prodname_github_app %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.github-apps-settings-sidebar %} -1. Debajo de "{% data variables.product.prodname_github_app %}s", haz clic en el avatar de la app de la que quieres eliminar un administrador {% 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) - -{% if currentVersion == "free-pro-team@latest" %} -### Leer más - -- "[Acerca de {% data variables.product.prodname_dotcom %} Mercado](/articles/about-github-marketplace/)" -{% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md deleted file mode 100644 index 34600b4f9e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Agregar un colaborador externo al tablero de proyecto de tu organización -intro: 'Como propietario de una organización o administrador de un tablero de proyecto, puedes agregar un colaborador externo y personalizar sus permisos para un tablero de proyecto.' -redirect_from: - - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Un colaborador externo es una persona que no es explícitamente un miembro de tu organización, pero tiene permisos para un tablero de proyecto en tu organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.organization-wide-project %} -{% data reusables.project-management.select-project %} -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -{% data reusables.project-management.collaborator-option %} -9. Debajo de "Search by username, full name or email address" (Buscar por nombre de usuario, nombre completo o dirección de correo electrónico), escribe el nombre, nombre de usuario o correo electrónico del colaborador externo {% data variables.product.prodname_dotcom %}. ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/projects/org-project-collaborators-find-name.png) -{% data reusables.project-management.add-collaborator %} -{% data reusables.project-management.collaborator-permissions %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/index.md deleted file mode 100644 index 719ae2a69d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Administrar el acceso a los tableros de proyecto de tu organización -intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes darles a los miembros de la organización, a los equipos o a colaboradores externos diferentes niveles de acceso a tableros de proyecto que son propiedad de tu organización.' -redirect_from: - - /articles/managing-access-to-your-organization-s-project-boards - - /articles/managing-access-to-your-organizations-project-boards -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /project-board-permissions-for-an-organization - - /managing-access-to-a-project-board-for-organization-members - - /managing-team-access-to-an-organization-project-board - - /managing-an-individuals-access-to-an-organization-project-board - - /adding-an-outside-collaborator-to-a-project-board-in-your-organization - - /removing-an-outside-collaborator-from-an-organization-project-board ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md deleted file mode 100644 index f8f2b01b53..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Administrar el acceso a un tablero de proyecto para los miembros de una organización -intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes configurar un nivel de permiso predeterminado para un tablero de proyecto para todos los miembros de la organización.' -redirect_from: - - /articles/managing-access-to-a-project-board-for-organization-members - - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Por defecto, los miembros de una organización tienen acceso de escritura a sus tableros de proyecto de la organización excepto que los propietarios de la organización o los administradores de un tablero de proyecto configuren permisos diferentes para tableros de proyecto específicos. - -### Configurar un nivel de permiso base para todos los miembros de la organización - -{% tip %} - -**Sugerencia:** Puedes darle a un miembro de la organización mayores permisos a un tablero de proyecto. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.organization-wide-project %} -{% data reusables.project-management.select-project %} -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -8. Debajo de "Organization member permission" (Permiso para miembro de la organización), elige un nivel base de permiso para todos los miembros de la organización: **Read** (Lectura), **Write** (Escritura), **Administrar** o **None** (Ninguno). ![Opciones de permiso base a un tablero de proyecto para todos los miembros de una organización](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png) -9. Haz clic en **Save (Guardar)**. - -### Leer más - -- "[Administrar el acceso de una persona a un tablero de proyecto de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)" -- "[Administrar el acceso de equipo a un tablero de proyecto de una organización](/articles/managing-team-access-to-an-organization-project-board)" -- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md deleted file mode 100644 index b891435ff6..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Administrar un acceso individual a un tablero de proyecto de una organización -intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes administrar al acceso de un miembro individual a un tablero de proyecto propiedad de tu organización.' -redirect_from: - - /articles/managing-an-individual-s-access-to-an-organization-project-board - - /articles/managing-an-individuals-access-to-an-organization-project-board - - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% note %} - -**Nota:** {% data reusables.project-management.cascading-permissions %} Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)." - -{% endnote %} - -### Otorgarle acceso a un miembro de la organización a un tablero de proyecto - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.organization-wide-project %} -{% data reusables.project-management.select-project %} -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -{% data reusables.project-management.collaborator-option %} -9. Debajo de "Search by username, full name or email address" (Buscar por nombre de usuario, nombre completo o dirección de correo electrónico), escribe el nombre, el nombre de usuario o el correo electrónico del colaborador {% data variables.product.prodname_dotcom %}. ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/projects/org-project-collaborators-find-name.png) -{% data reusables.project-management.add-collaborator %} -{% data reusables.project-management.collaborator-permissions %} - -### Cambiar el acceso de un miembro de la organización a un tablero de proyecto - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.organization-wide-project %} -{% data reusables.project-management.select-project %} -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -{% data reusables.project-management.collaborator-option %} -{% data reusables.project-management.collaborator-permissions %} - -### Eliminar el acceso de un miembro de la organización a un tablero de proyecto - -Cuando eliminas a un colaborador de un tablero de proyecto, es posible que conserve acceso a un tablero en base a los permisos que tiene por otros roles. Para eliminar de forma completa el acceso a un tablero de proyecto, debes eliminar el acceso para cada rol que tenga esa persona. Por ejemplo, una persona puede tener acceso al tablero de proyecto como miembro de la organización o miembro del equipo. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.organization-wide-project %} -{% data reusables.project-management.select-project %} -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -{% data reusables.project-management.collaborator-option %} -{% data reusables.project-management.remove-collaborator %} - -### Leer más - -- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md deleted file mode 100644 index e0bb5489a7..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Administrar acceso de equipo a un tablero de proyecto de una organización -intro: 'Como propietario de la organización o administrador de un tablero de proyecto, puedes darle acceso de equipo a un tablero de proyecto propiedad de tu organización.' -redirect_from: - - /articles/managing-team-access-to-an-organization-project-board - - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% warning %} - -**Advertencias:** -- Puedes cambiar el nivel de permiso de un equipo si el equipo tiene acceso directo a un tablero de proyecto. Si el acceso del equipo a un tablero de proyecto se hereda de un equipo padre, debes cambiar el acceso del equipo padre al tablero de proyecto. -- Si agregas o eliminas acceso a un tablero de proyecto para un equipo padre, cada uno de esos equipos hijos también recibirá o perderá acceso al tablero de proyecto. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". - -{% endwarning %} - -### Otorgarle a un equipo acceso a un tablero de proyecto - -Puedes otorgarle a un equipo completo el mismo nivel de permiso a un tablero de proyecto. - -{% note %} - -**Nota:** {% data reusables.project-management.cascading-permissions %} Por ejemplo, si un propietario de la organización le ha otorgado a un equipo permisos de lectura a un tablero de proyecto y un administrador de tablero de proyecto le otorga a uno de los miembros del equipo permisos de administrador a ese tablero como colaborador individual, esa persona tendría permisos de administrador al tablero de proyecto. Para obtener más información, consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)." - -{% endnote %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.organization-wide-project %} -{% data reusables.project-management.select-project %} -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -8. En la barra lateral izquierda, haz clic en **Teams (Equipos)**. -9. Para agregar un equipo, haz clic en **Add a team: Select team (Agregar un equipo: seleccionar equipo)**. Después, elige un equipo del menú desplegable o busca el equipo que deseas agregar. ![Agregar un menú desplegable de equipo con una lista de equipos en la organización](/assets/images/help/projects/add-a-team.png) -10. Junto al nombre del equipo, utiliza el menú desplegable para seleccionar el nivel de permiso deseado: **Read** (Lectura), **Write** (Escritura) o **Admin** (Administración). ![Menú desplegable de permisos de equipo con opciones de lectura, escritura o administrador](/assets/images/help/projects/org-project-team-choose-permissions.png) - -### Configurar el acceso de un equipo a un tablero de proyecto - -Si un equipo hereda el acceso a un tablero de proyecto desde un equipo padre, deberás cambiar el acceso de dicho equipo padre a este tablero para actualizar el acceso de los equipos hijos. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -4. Encima de la conversación del equipo, haz clic en {% octicon "project" aria-label="The Projects icon" %} **Projects (Proyectos)**. ![La pestaña de repositorios del equipo](/assets/images/help/organizations/team-project-board-button.png) -5. Para cambiar los niveles de permiso, utiliza el menú desplegable que se encuentra al costado derecho del tablero de proyecto que quieres actualizar. Para elminar un tablero de proyecto, da clic en **{% octicon "trashcan" aria-label="The trashcan icon" %}**. ![Botón para eliminar un tablero de proyecto de la papelera del equipo](/assets/images/help/organizations/trash-button.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md deleted file mode 100644 index 0dc15fc1e4..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Permisos de tablero de proyecto para una organización -intro: 'Los propietarios de la organización y las personas con permisos de administradores de los tableros de proyecto pueden personalizar quién tiene permisos de lectura, escritura y de administrador en los tableros de proyecto de tu organización.' -redirect_from: - - /articles/project-board-permissions-for-an-organization - - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Resumen de permisos - -Hay tres niveles de permisos para las personas y para los equipos a un tablero de proyecto: - -{% data reusables.project-management.project-board-permissions %} - -Los propietarios de la organización y las personas con permisos de administrador pueden otorgarle acceso a una persona a un tablero de proyecto de una organización de manera individual, como un colaborador externo o como miembro de la organización, o a través de su membresía en un equipo o una organización. Un colaborador externo es alguien que no es miembro de la organización pero a quien le han otorgado permisos para colaborar en tu organización. - -Los propietarios de la organización y las personas con permisos de administrador a un tablero de proyecto también pueden: -- Configurar permisos predeterminados a un tablero de proyecto para todos los miembros de la organización. -- Administrar el acceso al tablero de proyecto para los miembros de la organización, los equipos y los colaboradores externos. Para obtener más información, consulta "[Administrar el acceso de equipo a un tablero de proyecto de una organización](/articles/managing-team-access-to-an-organization-project-board)", "[Administrar el acceso de una persona a un tablero de proyecto de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)", o "[Administrar el acceso a un tablero de proyecto para los miembros de una organización](/articles/managing-access-to-a-project-board-for-organization-members)." -- Administrar la visibilidad del tablero de proyecto. Para obtener más información, consulta "[Administrar el acceso a un tablero de proyecto para los miembros de una organización](/articles/managing-access-to-a-project-board-for-organization-members)." - -### Permisos en cascada para tableros de proyecto - -{% data reusables.project-management.cascading-permissions %} - -Por ejemplo, si el propietario de la organización ha otorgado a todos los miembros de la organización permisos de lectura a un tablero de proyecto y un administrador de tablero de proyecto le otorga a un miembro de la organización permisos de escritura a ese tablero como colaborador individual, esa persona tendría permisos de escritura al tablero de proyecto. - -### Visibilidad del tablero de proyecto - -{% data reusables.project-management.project-board-visibility %} Puedes cambiar la visibilidad del tablero de proyecto de privada a pública y viceversa. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". - -### Leer más - -- "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)." -- "[Administrar el acceso de una persona a un tablero de proyecto de una organización](/articles/managing-an-individual-s-access-to-an-organization-project-board)" -- "[Administrar el acceso de equipo a un tablero de proyecto de una organización](/articles/managing-team-access-to-an-organization-project-board)" -- "[Administrar el acceso a un tablero de proyecto para los miembros de una organización](/articles/managing-access-to-a-project-board-for-organization-members)." diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md deleted file mode 100644 index ee90db63d9..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Eliminar un colaborador externo de un tablero de proyecto de la organización -intro: 'Como propietario de la organización o administrador del tablero de proyecto, puedes eliminar el acceso de un colaborador externo a un tablero de proyecto.' -redirect_from: - - /articles/removing-an-outside-collaborator-from-an-organization-project-board - - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.organization-wide-project %} -{% data reusables.project-management.select-project %} -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -{% data reusables.project-management.collaborator-option %} -{% data reusables.project-management.remove-collaborator %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md deleted file mode 100644 index d486d16568..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Agregar colaboradores externos a los repositorios en tu organización -intro: Un *colaborador externo* es una persona que no es explícitamente un miembro en tu organización pero tiene premisos de lectura. -redirect_from: - - /articles/adding-outside-collaborators-to-repositories-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% 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)". - -{% data reusables.organizations.outside-collaborators-use-seats %} - -Si tu organización [requiere miembros y colaboradores externos para usar la autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization), deben habilitar la autenticación de dos factores antes de que puedan aceptar tu invitación para colaborar en el repositorio de una organización. - -{% data reusables.organizations.outside_collaborator_forks %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.repositories.navigate-to-manage-access %} -{% data reusables.organizations.invite-teams-or-people %} -5. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. ![Campo de búsqueda para teclear el nombre de una persona e invitarla al repositorio](/assets/images/help/repository/manage-access-invite-search-field.png) -6. Debajo de "Selecciona un rol", selecciona los permisos que quieres otorgar a la persona, luego da clic en **"Añadir NOMBRE a REPOSITORIO**. ![Seleccionar los permisos para la persona](/assets/images/help/repository/manage-access-invite-choose-role-add.png) -{% else %} -5. En la barra lateral izquierda, haz clic en **Collaborators & teams** (Colaboradores y equipos). ![Barra lateral de configuraciones del repositorio con Colaboradores y equipos resaltados](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) -6. En "Collaborators" (Colaboradores), escribe el nombre de la persona a la que te gustaría brindar acceso al repositorio, luego haz clic en **Add collaborator** (Agregar colaborador). ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/repository/org-repo-collaborators-find-name.png) -7. Junto al nombre del colaborador, escribe el nivel de permiso correspondiente: *Write* (Escritura) *Read* (Lectura) o *Admin* (Administración). ![El recolector de permisos del repositorio](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) -{% endif %} - -### Leer más - -- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" -- "[Eliminar a un colaborador externo de un repositorio de la organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md deleted file mode 100644 index 84a523344a..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Cancelar una invitación para convertirse en un colaborador externo en tu organización -intro: Puedes cancelar todas las invitaciones para que las personas se conviertan en un colaborador externo en los repositorios que pertenecen a tu organización. -permissions: Los propietarios de la organización pueden cancelar una invitación para convertirse en un colaborador externo en la misma. -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization ---- -Puedes ver una lista de todas las personas con invitaciones pendientes para convertirse en colaboradores externos en cualquier repositorio que pertenezca a tu organización. - -Para cada colaborador pendiente, puedes cancelar al mismo tiempo todas las invitaciones para unirse a los repositorios de la organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.people_tab_outside_collaborators %} -5. Da clic en **colaboradores pendientes**. ![Botón de "Colaboradores pendientes"](/assets/images/help/organizations/pending-collaborator-list.png) -6. A la derecha de la persona para la cual quieres cancelar las invitaciones, da clic en **Cancelar invitaciones**. ![Botón de "Cancelar invitación"](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. Da clic en **Cancelar invitaciones para los colaboradores pendientes**. ![Botón para confirmar cancelación](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md deleted file mode 100644 index c4af23e3dc..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Convertir a un miembro de la organización en un colaborador externo -intro: 'Si un miembro actual de tu organización solo necesita acceso a determinados repositorios, como consultores o empleados temporales, puedes convertirlo en un *colaborador externo".' -redirect_from: - - /articles/converting-an-organization-member-to-an-outside-collaborator - - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.organizations.owners-and-admins-can %} convertir a los miembros de la organización en colaboradores externos. - -{% data reusables.organizations.outside-collaborators-use-seats %}{% data reusables.organizations.outside_collaborator_forks %} - -Luego de convertir a un miembro de la organización en un colaborador externo, solo tendrá acceso a los repositorios que permite su membresía de equipo actual. La persona ya no será un miembro explícito de la organización, y ya no podrá: - -- Crear equipos -- Ver todos los miembros y equipos de la organización -- @mencionar cualquier equipo visible -- Ser un mantenedor del equipo - -Para obtener más información, consulta ´la sección "[Niveles de permisos para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)". - -Recomendamos revisar el acceso del miembro de la organización a los repositorios para garantizar que su acceso sea el que esperas. Para obtener más información, consulta la sección "[Administrar el acceso de un individuo a un repositorio de la organización](/articles/managing-an-individual-s-access-to-an-organization-repository)". - -Cuando conviertes a un miembro de la organización en un colaborador externo, sus privilegios como miembro de la organización se guardan durante tres meses para que puedas restaurar sus privilegios de membresía si lo{% if currentVersion == "free-pro-team@latest" %}invitas a unirse nuevamente{% else %} lo vuelves a agregar{% endif %} a tu organización dentro de ese período. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Selecciona la persona o las personas a quienes deseas convertir en colaboradores externos. ![Lista de miembros con dos miembros seleccionados](/assets/images/help/teams/list-of-members-selected-bulk.png) -5. Arriba de la lista de miembros, utiliza el menú desplegable y haz clic en **Convert to outside collaborator** (Convertir en colaborador externo). ![Menú desplegable con la opción para convertir miembros en colaboradores externos](/assets/images/help/teams/user-bulk-management-options.png) -6. Lee la información sobre cómo convertir miembros en colaboradores externos, luego haz clic en **Convert to outside collaborator** (Convertir en colaborador externo). ![Información sobre permisos de colaboradores externos y botón Convert to outside collaborators (Convertir en colaboradores externos)](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) - -### Leer más - -- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- "[Eliminar a un colaborador externo de un repositorio de la organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" -- "[Convertir a un colaborador externoe en un miembro de la organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md deleted file mode 100644 index 5989f3460f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Converting an outside collaborator to an organization member -intro: 'If you would like to give an outside collaborator on your organization''s repositories broader permissions within your organization, you can {% if currentVersion == "free-pro-team@latest" %}invite them to become a member of{% else %}make them a member of{% endif %} the organization.' -redirect_from: - - /articles/converting-an-outside-collaborator-to-an-organization-member - - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% tip %} - -**Tips**: -- Only organization owners can {% if currentVersion == "free-pro-team@latest" %}invite users to join{% else %}add users to{% endif %} an organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)."{% if currentVersion == "free-pro-team@latest" %} -- If your organization is on a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-expiration %}{% endif %} -- If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users {% if currentVersion == "free-pro-team@latest" %}you invite must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before they can accept the invitation.{% else %}must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before you can add them to the organization.{% endif %} - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.people_tab_outside_collaborators %} -{% if currentVersion == "free-pro-team@latest" %} -5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) -{% else %} -5. To the right of the name of the outside collaborator you want to become a member, click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png) -{% endif %} -{% data reusables.organizations.choose-to-restore-privileges %} -{% data reusables.organizations.choose-user-role-send-invitation %} -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} -{% endif %} - -### Further reading - -- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/index.md deleted file mode 100644 index a37f7cb4e2..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Administrar el acceso a los repositorios de tu organización -intro: Los propietarios de la organización pueden administrar el acceso individual y de equipo a los repositorios de una organización. Los mantenedores del equipo también pueden administrar el acceso a un repositorio de equipo. -redirect_from: - - /articles/permission-levels-for-an-organization-repository/ - - /articles/managing-access-to-your-organization-s-repositories - - /articles/managing-access-to-your-organizations-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /repository-permission-levels-for-an-organization - - /setting-base-permissions-for-an-organization - - /viewing-people-with-access-to-your-repository - - /managing-an-individuals-access-to-an-organization-repository - - /managing-team-access-to-an-organization-repository - - /adding-outside-collaborators-to-repositories-in-your-organization - - /canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization - - /removing-an-outside-collaborator-from-an-organization-repository - - /converting-an-organization-member-to-an-outside-collaborator - - /converting-an-outside-collaborator-to-an-organization-member - - /reinstating-a-former-outside-collaborators-access-to-your-organization ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md deleted file mode 100644 index 05dba3167f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Administrar el acceso de una persona a un repositorio de una organización -intro: Puedes administrar el acceso de una persona a un repositorio propiedad de tu organización. -redirect_from: - - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program/ - - /articles/managing-an-individual-s-access-to-an-organization-repository - - /articles/managing-an-individuals-access-to-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Las personas con permisos de administrador pueden administrar el acceso de los miembros de la organización y de los colaboradores externos a un repositorio de la organización. - -### Eliminar el acceso a los repositorios - -Cuando eliminas a un colaborador de un repositorio en tu organización, el colaborador pierde el acceso de lectura y escritura al repositorio. Si el repositorio es privado y el colaborador ha bifurcado el repositorio, entonces su bifurcación también se elimina, pero el colaborador conservará cualquier clon local de tu repositorio. - -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -### Administrar el acceso de una persona a un repositorio de una organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Haz clic en **Members (Miembros)** o **Outside collaborators (Colaboradores externos)** para administrar las personas con diferentes tipos de acceso. ![Botón para invitar a miembros o colaboradores externos a una organización](/assets/images/help/organizations/select-outside-collaborators.png) -5. A la derecha del nombre de la persona que desearías administrar, utiliza el menú desplegable {% octicon "gear" aria-label="The Settings gear" %}, y haz clic en **Manage (Administrar)**. ![Enlace de acceso al gerente](/assets/images/help/organizations/member-manage-access.png) -6. En la página "Manage access" (Administrar el acceso), al lado del repositorio, haz clic en **Manage access (Administrar el acceso)**. ![Botón de administración de acceso a un repositorio](/assets/images/help/organizations/repository-manage-access.png) -7. Revisa el acceso de la persona a un repositorio determinado, como si fuera un colaborador o si tuviera acceso a un repositorio por medio de una membresía de equipo. ![Matriz de acceso a repositorio para el usuario](/assets/images/help/organizations/repository-access-matrix-for-user.png) - -### Leer más - -{% if currentVersion == "free-pro-team@latest" %}- "[Limitar las interacciones con tu repositorio](/articles/limiting-interactions-with-your-repository)"{% endif %} -- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md deleted file mode 100644 index 25f8cc2a3a..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Administrar el acceso de equipo a un repositorio de la organización -intro: 'Puedes darle acceso de equipo a un repositorio, eliminar el acceso del equipo sobre un repositorio, o cambiar el nivel de permiso del equipo sobre un repositorio.' -redirect_from: - - /articles/managing-team-access-to-an-organization-repository-early-access-program/ - - /articles/managing-team-access-to-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Las personas con acceso de administrador a un repositorio pueden administrar el acceso del equipo a un repositorio. Los mantenedores del equipo pueden eliminar el acceso de un equipo a un repositorio. - -{% warning %} - -**Advertencias:** -- Puedes cambiar el nivel de permiso de un equipo si el equipo tiene acceso directo a un repositorio. Si el acceso del equipo a un repositorio se hereda de un equipo padre, debes cambiar el acceso del equipo padre al repositorio. -- Si agregas o eliminas el acceso al repositorio de un equipo padre, cada uno de sus equipos hijos también recibirá o perderá el acceso al repositorio. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". - -{% endwarning %} - -### Otorgarle a un equipo acceso a un repositorio - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-repositories-tab %} -5. Encima de la lista de repositorios, haz clic en **Add repository (Agregar repositorio)**. ![Botón Agregar repositorio](/assets/images/help/organizations/add-repositories-button.png) -6. Escribe el nombre de un repositorio, después haz clic en **Add repository to team (Agregar repositorio al equipo)**. ![Campo Buscar repositorio](/assets/images/help/organizations/team-repositories-add.png) -7. De forma opcional, a la derecha del nombre del repositorio, utiliza el menú desplegable y elige un nivel de permiso diferente para el equipo. ![Menú desplegable de nivel de acceso a un repositorio](/assets/images/help/organizations/team-repositories-change-permission-level.png) - -### Eliminar el acceso de un equipo a un repositorio - -Puedes eliminar el acceso de un equipo a un repositorio si el equipo tiene acceso directo a un repositorio. Si el acceso de un equipo al repositorio se hereda de un equipo padre, debes eliminar el repositorio del equipo padre para poder eliminar el repositorio de los equipos hijos. - -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-repositories-tab %} -5. Selecciona el repositorio o los repositorios que deseas eliminar del equipo. ![Lista de repositorios de equipo con casillas de verificación para algunos repositorios seleccionados](/assets/images/help/teams/select-team-repositories-bulk.png) -6. Encima de la lista de repositorios, utiliza el menú desplegable, y haz clic en **Remove from team (Eliminar del equipo)**. ![Menú desplegable con la opción de eliminar un repositorio de un equipo](/assets/images/help/teams/remove-team-repo-dropdown.png) -7. Revisa el o los repositorios que serán eliminados del equipo, después haz clic en **Remove repositories (Eliminar repositorios)**. ![Casilla modal con una lista de repositorios a los que el equipo ya no tiene acceso](/assets/images/help/teams/confirm-remove-team-repos.png) - -### Leer más - -- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md deleted file mode 100644 index 2a3502ebe1..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Reinstating a former outside collaborator's access to your organization -intro: 'If you required two-factor authentication in your organization and an outside collaborator was removed from the organization for not having 2FA enabled, you can reinstate a former outside collaborator''s access permissions for organization repositories, forks, and settings.' -redirect_from: - - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization - - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization - - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -If an outside collaborator's access to your organization's private repositories is removed because you've [required members and outside collaborators to enable two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), the user's access privileges and settings are saved for three months. You can restore the user's privileges if you {% if currentVersion == "free-pro-team@latest" %}invite{% else %}add{% endif %} them back to the organization within that time frame. - -{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} - -When you reinstate a former outside collaborator, you can restore: - - The user's former access to organization repositories - - Any private forks of repositories owned by the organization - - Membership in the organization's teams - - Previous access and permissions for the organization's repositories - - Stars for organization repositories - - Issue assignments in the organization - - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity) - -{% tip %} - -**Tips**: - - Only organization owners can reinstate outside collaborators' access to an organization. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." - - The reinstating a member flow on {% data variables.product.product_location %} may use the term "member" to describe reinstating an outside collaborator but if you reinstate this person and keep their previous privileges, they will only have their previous [outside collaborator permissions](/articles/permission-levels-for-an-organization/#outside-collaborators).{% if currentVersion == "free-pro-team@latest" %} - - If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."{% endif %} - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.invite_member_from_people_tab %} -{% data reusables.organizations.reinstate-user-type-username %} -{% if currentVersion == "free-pro-team@latest" %} -6. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Invite and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Invite and start fresh**. - - {% warning %} - - **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Invite and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Invite and reinstate** instead. Once this person accepts the invitation, you can convert them to an organization member by [inviting them to join the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member). - - {% endwarning %} - - ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) -{% else %} -6. Choose to restore the outside collaborator's previous privileges in the organization by clicking **Add and reinstate** or choose to clear their previous privileges and set new access permissions by clicking **Add and start fresh**. - - {% warning %} - - **Warning:** If you want to upgrade the outside collaborator to a member of your organization, then choose **Add and start fresh** and choose a new role for this person. Note, however, that this person's private forks of your organization's repositories will be lost if you choose to start fresh. To make the former outside collaborator a member of your organization *and* keep their private forks, choose **Add and reinstate** instead. Then, you can convert them to an organization member by [adding them to the organization as a member](/articles/converting-an-outside-collaborator-to-an-organization-member). - - {% endwarning %} - - ![Choose to restore settings or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Send invitation**. - ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png) -{% else %} -7. If you cleared the previous privileges for a former outside collaborator, choose a role for the user and optionally add them to some teams, then click **Add member**. - ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -8. The invited person will receive an email inviting them to the organization. They will need to accept the invitation before becoming an outside collaborator in the organization. {% data reusables.organizations.cancel_org_invite %} -{% endif %} - -### Further Reading - -- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md deleted file mode 100644 index 360ec3da64..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Eliminar un colaborador externo de un repositorio de la organización -intro: Los propietarios y los administradores del repositorio pueden eliminar el acceso a un repositorio de un colaborador externo. -redirect_from: - - /articles/removing-an-outside-collaborator-from-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% if currentVersion == "free-pro-team@latest" %} - -{% warning %} - -**Advertencia:** -- Cuando se elimina un colaborador externo de un repositorio privado, el conteo 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)". - -- Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. - -{% endwarning %} - -{% endif %} - -Aunque se borren las bifurcaciones de los repositorios privados cuando se elimina un colaborador, la persona seguirá teniendo todos los clones locales de tu repositorio. - -### Eliminar colaboradores externos de todos los repositorios de una organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.people_tab_outside_collaborators %} -5. Selecciona el colaborador externo o los colaboradores externos que quieres eliminar de la organización. ![Lista de colaboradores externos con dos colaboradores externos seleccionados](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) -6. Arriba de la lista de colaboradores externos, usa el menú desplegable y haz clic en **Remove from all repositories** (Eliminar de todos los repositorios). ![Menú desplegable con la opción para eliminar colaboradores externos ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) -7. Revisa el colaborador externo o los colaboradores externos que se eliminarán de la organización, luego haz clic en **Remove outside collaborators** (Eliminar colaboradores externos). ![Lista de colaboradores externos que se eliminarán y botón Remove outside collaborators (Eliminar colaboradores externos)](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) - -### Eliminar un colaborador externo de un repositorio particular de una organización - -Si solo quieres eliminar un colaborador externo de determinados repositorios de tu organización, puedes eliminar el acceso de esa persona a un repositorio específico por vez. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.people_tab_outside_collaborators %} -5. A la derecha del nombre de usuario de la persona que quieres eliminar, utiliza el menú desplegable {% octicon "gear" aria-label="The Settings gear" %} y haz clic en **Manage** (Administrar). ![Botón Manage access (Administrar acceso)](/assets/images/help/organizations/member-manage-access.png) -6. A la derecha del repositorio del que quieres eliminar al colaborador externo, haz clic en **Manage access** (Administrar acceso). ![Selecciona el botón Manage access (Administrar acceso) al lado del repositorio al que tiene acceso el colaborador externo](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) -7. Para eliminar por completo el acceso del colaborador externo al repositorio, en la esquina superior derecha, haz clic en **Remove access to this repository** (Eliminar acceso a este repositorio). ![Botón Remove access to this repository (Eliminar acceso a este repositorio)](/assets/images/help/organizations/remove-access-to-this-repository.png) -8. Para confirmar, haz clic en **Remove access** (Eliminar acceso). ![Confirmar el colaborador externo que se eliminará del repositorio](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) - -### Leer más - -- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md deleted file mode 100644 index 98bc875515..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ /dev/null @@ -1,178 +0,0 @@ ---- -title: Niveles de permiso del repositorio para una organización -intro: 'Puedes personalizar el acceso a cada repositorio de tu organización con niveles de permiso granulares, dándoles a las personas acceso a las funciones y tareas que necesitan.' -redirect_from: - - /articles/repository-permission-levels-for-an-organization-early-access-program/ - - /articles/repository-permission-levels-for-an-organization - - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Las personas con permisos de administrador pueden administrar el acceso individual o del equipo al repositorio que le pertenece a la organización. - -### Niveles de permiso para los repositorios que le pertenecen a una organización - -Puedes otorgar diferentes niveles de acceso a los miembros de la organización, los colaboradores externos y los equipos de personas para los repositorios que le pertenecen a una organización. Cada nivel de permiso aumenta de manera progresiva el acceso al contenido y los parámetros de un repositorio. Elige el nivel que mejor se adecue a cada rol de persona o equipo de tu proyecto, evitando otorgar a las personas más acceso al proyecto del que necesitan. - -Del menor acceso al mayor acceso, los niveles de permiso para el repositorio de una organización son los siguientes: -- **Lectura**: Recomendado para los contribuyentes sin código que quieren ver tu proyecto u opinar sobre él {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -- **Prueba**: Recomendado para los contribuyentes que necesiten administrar propuestas y solicitudes de extracción de manera proactiva sin acceso de escritura{% endif %} -- **Escritura**: Recomendado para los contribuyentes que suben contenido a tu proyecto de manera activa{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -- **Mantenimiento (beta)**: Recomendado para los gerentes del proyecto que necesiten administrar el repositorio sin acceder a las acciones confidenciales o destructivas{% endif %} -- **Administrador**: Recomendado para las personas que necesitan acceso total al proyecto, incluidas las acciones conflictivas y destructivas, como gestionar la seguridad o eliminar un repositorio - -{% if currentVersion == "free-pro-team@latest" %} - -{% endif %} - -Para obtener más información acerca de otorgar acceso a los repositorios a las personas y los equipos, consulta "[Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organizations-repositories)". - -Los dueños de las organizaciones pueden configurar permisos base que apliquen a todos los miembros de la misma cuando accedan a cualquiera de los repositorios que le pertenezcan a dicha organización. Para obtener más información, consulta la sección "[Configurar los permisos base para una organización](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization#setting-base-permissions)". - -Los propietarios de la organización también pueden decidir limitar más el acceso a determinados parámetros y acciones de la organización. Para obtener más información sobre las opciones de parámetros específicos, consulta "[Administrar los parámetros de la organización](/articles/managing-organization-settings)". - -Además de administrar los parámetros al nivel de la organización, los propietarios de la organización tienen permisos de administradores para cada repositorio que le pertenece a la organización. Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". - -{% warning %} - -**Advertencia:** Cuando una persona agrega una llave de implementación a un repositorio, cualquier usuario que tenga la llave privada puede leer o escribir en el repositorio (según los parámetros de la llave), incluso si luego es eliminada de la organización. - -{% endwarning %} - -### Acceso al repositorio para cada nivel de permiso -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -| Acción del repositorio | Lectura | 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** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [Informar contenido abusivo o de spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Aplicar etiquetas | | **X** | **X** | **X** | **X** | -| Elegir, reabrir y asignar todas las propuestas y solicitudes de extracción | | **X** | **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** | -| 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](/articles/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Bloquear conversaciones](/articles/locking-conversations) | | | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -| Transferir propuestas (consulta "[Transferir una propuesta a otro repositorio](/articles/transferring-an-issue-to-another-repository)" para obtener detalles) | | | **X** | **X** | **X** |{% endif %} -| [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** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -| [Convertir una solicitud de extracción en borrador](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** |{% endif %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| 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** |{% if currentVersion == "free-pro-team@latest" %} -| [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** | -| [Borrar paquetes](/packages/publishing-and-managing-packages/deleting-a-package) | | | | | **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** |{% if currentVersion == "free-pro-team@latest" %} -| Limitar las [interacciones en un repositorio](/github/building-a-strong-community/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](/github/setting-up-and-managing-organizations-and-teams/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** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -| Volver plantilla un repositorio (consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)") | | | | | **X** |{% endif %} -| 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** | -| Administrar webhooks y desplegar llaves | | | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Habilitar el gráfico de dependencias](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) de un repositorio privado | | | | | **X** | -| Recibir [{% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerabiles](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en un repositorio | | | | | **X** | -| [Ignorar las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** | -| [Designar personas o equipos adicionales para que reciban las {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) para las dependencias vulnerables | | | | | **X** | -| [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 %}{% if currentVersion == "free-pro-team@latest" %}| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories) | | | | | **X** |{% endif %} -| [Administrar la política de bifurcación para 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** |{% if currentVersion == "free-pro-team@latest" %} -| 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 %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -| 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** |{% endif %} - -{% else %} - -| Acción del repositorio | Permisos de lectura | Permisos de escritura | Permisos de administrador | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------------------:|:---------------------:|:----------------------------------------------------------------------:| -| Extraer desde (leer) los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | -| Bifurcar (copiar) los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | -| Editar y eliminar sus propios comentarios sobre confirmaciones, solicitudes de extracción y propuestas | **X** | **X** | **X** | -| Abrir propuestas | **X** | **X** | **X** | -| Cerrar propuestas que ellos mismos abrieron | **X** | **X** | **X** | -| Reabrir propuestas que ellos mismos cerraron | **X** | **X** | **X** | -| Recibir la asignación de una propuesta | **X** | **X** | **X** | -| Enviar solicitudes de extracción desde las bifurcaciones de los repositorios asignados del equipo | **X** | **X** | **X** | -| Enviar revisiones sobre solicitudes de extracción | **X** | **X** | **X** | -| Ver los lanzamientos publicados | **X** | **X** | **X** | -| Editar wikis | **X** | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Informar contenido abusivo o de spam](/articles/reporting-abuse-or-spam) | **X** | **X** | **X** |{% endif %} -| Subir a (escribir en) los repositorios asignados de la persona o el equipo | | **X** | **X** | -| Editar y eliminar comentarios o confirmaciones, solicitudes de extracción y propuestas de cualquier persona | | **X** | **X** | -| [Ocultar los comentarios de cualquier persona](/articles/managing-disruptive-comments) | | **X** | **X** | -| [Bloquear conversaciones](/articles/locking-conversations) | | **X** | **X** | -| Aplicar etiquetas e hitos | | **X** | **X** | -| Cerrar, reabrir y asignar todas las propuestas | | **X** | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Marcar [duplicar propuestas y solicitudes de extracción](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** |{% endif %} -| [Actuar como propietario del código designado para un repositorio](/articles/about-code-owners) | | **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** | -| Solicitar [revisiones de solicitudes de extracción](/articles/requesting-a-pull-request-review) | | **X** | **X** | -| Enviar revisiones que afecten la capacidad de fusión de una solicitud de extracción | | **X** | **X** | -| Aplicar cambios sugeridos a las solicitudes de extracción (consulta "[Incorporar opiniones en tu solicitud de extracción](/articles/incorporating-feedback-in-your-pull-request)" para obtener más detalles) | | **X** | **X** | -| Crear [comprobaciones de estado](/articles/about-status-checks) | | **X** | **X** | -| Crear y editar lanzamientos | | **X** | **X** | -| Ver lanzamientos en borrador | | **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** | -| Editar la descripción de un repositorio | | | **X** | -| Administrar [temas](/articles/classifying-your-repository-with-topics) | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -| Crear y editar las tarjetas sociales del repositorio (consulta "[Personalizar la vista preliminar de las redes sociales del repositorio](/articles/customizing-your-repositorys-social-media-preview)) | | | **X** |{% endif %} -| Añadir un repositorio a un equipo (consulta la sección "[Administrar el acceso de un equipo a un repositorio de la organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obtener más detalles) | | | **X** | -| Administrar el acceso de un colaborador externo a un repositorio (consulta "[Agregar colaboradores externos a los repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" para obtener más detalles) | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| Limitar las [interacciones en un repositorio](/github/building-a-strong-community/limiting-interactions-in-your-repository) | | | **X** |{% endif %} -| Cambiar la visibilidad de un repositorio (consulta "[Restringir cambios en la visibilidad del repositorio de tu organización](/articles/restricting-repository-visibility-changes-in-your-organization)" para obtener más detalles) | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} -| Volver plantilla un repositorio (consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)") | | | | | **X** |{% endif %} -| 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** | -| Administrar webhooks y desplegar llaves | | | **X** |{% if currentVersion == "free-pro-team@latest" %} -| [Habilitar el gráfico de dependencias](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) de un repositorio privado | | | **X** | -| Recibir [{% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerabiles](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en un repositorio | | | **X** | -| [Ignorar las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | **X** | -| [Designar personas o equipos adicionales para que reciban las {% data variables.product.prodname_dependabot_alerts %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-github-dependabot-alerts) para las dependencias vulnerables | | | **X** | -| [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 %}{% if currentVersion == "free-pro-team@latest" %} -| Crear [asesorías de seguridad](/github/managing-security-vulnerabilities/about-github-security-advisories)") | | | **X** |{% endif %} -| [Administrar la política de bifurcación para un repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | **X** | -| Transferir repositorios a la cuenta de la organización (consulta "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)" para obtener más detalles) | | | **X** | -| Eliminar o transferir repositorios (consulta "[Establecer permisos para eliminar o transferir repositorios en tu organización](/articles/setting-permissions-for-deleting-or-transferring-repositories)" para obtener más detalles) | | | **X** | -| [Archivar repositorios](/articles/about-archiving-repositories) | | | **X** |{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -| 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** |{% endif %} - -{% endif %} - -### Leer más - -- [Administrar el acceso a los repositorios de tu organización](/articles/managing-access-to-your-organization-s-repositories)" -- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md deleted file mode 100644 index 2ccfdf0006..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Configurar los permisos base para una organización -intro: Puedes configurar permisos base para los repositorios que pertenezcan a una organización. -permissions: Los dueños de la organización pueden configurar permisos base para la misma. -versions: - free-pro-team: '*' - enterprise-server: '*' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization ---- -### Acerca de los permisos base para una organización - -Puedes configurar permisos base que apliquen a todos los miembros de una organización cuando accedan a cualquiera de los repositorios de la misma. Los permisos base no aplican para los colaboradores externos. - -{% if currentVersion == "free-pro-team@latest" %}Predeterminadamente, los miembros de una organización tendrán permisos de **Lectura** para los repositorios de la misma{% endif %} - -Si alguien con permisos administrativos en un repositorio de la organización otorga un nivel superior de permisos en el mismo a algún miembro, este nivel de permiso superior anulará el permiso base. - -### Configurar los permisos base - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. Debajo de "Permisos Base", utiliza el menú desplegable para seleccionar los nuevos permisos base. ![Selección de nuevo nivel de permiso desde el menú desplegable de "permisos base"](/assets/images/help/organizations/base-permissions-drop-down.png) -6. Revisa los cambios. Da clic en **Cambiar el permiso predeterminado por PERMISO** para confirmar. ![Revisar y confirmar el cambio de permisos base](/assets/images/help/organizations/base-permissions-confirm.png) - -### Leer más - -- "[Niveles de permisopara una organización en un repositorio](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization)" -- "[Añadir colaboradores externos a los repositorios de tu organización](/github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md deleted file mode 100644 index 36e55f05d5..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Ver personas con acceso a tu repositorio -intro: 'Los propietarios de la organización pueden ver el acceso de las personas a un repositorio dentro de una organización. Los propietario de organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} o {% data variables.product.prodname_ghe_server %} también pueden exportar una lista CSV de personas que tienen acceso a un repositorio.' -redirect_from: - - /articles/viewing-people-with-access-to-your-repository - - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Los administradores pueden utilizar esta información para ayudar a personas externas, reunir datos de cumplimiento y otras verificaciones generales de seguridad. - -![Lista de permisos de personas a un repositorio](/assets/images/help/repository/repository-permissions-list.png) - -### Ver personas con acceso a tu repositorio - -{% if currentVersion == "free-pro-team@latest" %} -{% note %} - -**Nota**: También puedes tener una vista general combinada de los equipos y personas con acceso a tu repositorio. Para obtener más información, consulta la sección "[Administrar los equipos y personas con acceso a tu repositorio](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)". - -{% endnote %} -{% endif %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.accessing-repository-people %} - -### Exportar una lista de personas con acceso a tu repositorio - -Los propietario de organizaciones en {% data variables.product.prodname_ghe_cloud %} o {% data variables.product.prodname_ghe_server %} pueden exportar una lista CSV de personas que tienen acceso a un repositorio. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.accessing-repository-people %} -4. Haz clic en **Export CSV (Exportar CSV)**. ![Pestaña de personas en la barra lateral del repositorio](/assets/images/help/repository/export-repository-permissions.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md deleted file mode 100644 index 31ee4c9a74..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Acerca de las autoridades de certificación de SSH -intro: 'Con una autoridad de certificación de SSH, tu cuenta de empresa u organización puede ofrecer certificados SSH que los miembros pueden usar para aceder a tus recursos con Git.' -product: '{% data reusables.gated-features.ssh-certificate-authorities %}' -redirect_from: - - /articles/about-ssh-certificate-authorities - - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities -versions: - free-pro-team: '*' - enterprise-server: '>=2.19' ---- -Un certificado SSH es un mecanismo para que una clave SSH firme otra clave SSH. Si usas una autoridad de certificación de SSH (CA) para ofrecerle a los miembros de tu organización certificados SSH firmados, puedes agregar la CA a tu cuenta de empresa u organización para permitirle a los miembros de la organización usar sus certificados para acceder a los recursos de la organización. Para obtener más información, consulta [Administrar las autoridades de certificación de SSH de tu organización ](/articles/managing-your-organizations-ssh-certificate-authorities)". - -Una vez que agregas una CA de SSH a tu cuenta de empresa u organización, puedes usar la CA para firmar certificados de SSH de clientes para los miembros de la organización. Los miembros de la organización pueden usar los certificados firmados para acceder a los repositorios de tu organización (y solo los repositorios de tu organización) con Git. Puedes solicitar a los miembros que usen certificados SSH para acceder a los recursos de la organización.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta "[Hacer cumplir los parámetros en tu cuenta de empresa](/articles/enforcing-security-settings-in-your-enterprise-account#managing-your-enterprise-accounts-ssh-certificate-authorities)".{% endif %} - -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 %}: - -```shell -$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME ./user-key.pub -``` - -Para emitir un certificado para alguien que tiene diferentes nombres de usuario para {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}, puedes incluir dos extensiones de inicio de sesión. - -```shell -$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=CLOUD-USERNAME extension:login@HOSTNAME=SERVER-USERNAME ./user-key.pub -``` - -Puedes restringir las direcciones IP desde las que un miembro de la organización puede acceder a los recursos de tu organización usando una extensión `source-address`. La extensión acepta una dirección IP específica o una gama de direcciones IP con la notación CIDR. Puedes especificar múltiples direcciones o rangos separando los valores con comas. Para obtener más información, consulta "[Enrutamiento entre dominios sin clases](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" en Wikipedia. - -```shell -$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@github.com=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub -``` - -Los miembros de la organización pueden usar sus certificados firmados para la autenticación, incluso si has aplicado el inicio de sesión único de SAML. A menos que hagas que los certificados SSH sean un requisito, los miembros de la organización pueden seguir usando otros medios para la autenticación para acceder a los recursos de tu organización con Git, incluyendo sus nombre de usuario y contraseña, tokens de acceso personales y sus propias claves SSH. - -Para evitar errores de autenticación, los miembros de la organización deben usar una URL especial que incluya el ID de la organización para clonar los repositorios mediante certificados firmados. Cualquier persona con acceso de lectura al repositorio puede buscar esta URL en la página del repositorio. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/index.md deleted file mode 100644 index d02561acd4..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Administrar el acceso de Git a los repositorios de tu organización -intro: Puedes agregar una autoridad de certificados (CA) SSH a tu organización y permitir que los miembros accedan a los repositorios de la organización sobre Git mediante claves firmadas por la CA SSH. -product: '{% data reusables.gated-features.ssh-certificate-authorities %}' -redirect_from: - - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities/ - - /articles/managing-git-access-to-your-organizations-repositories -versions: - free-pro-team: '*' - enterprise-server: '>=2.19' -children: - - /about-ssh-certificate-authorities - - /managing-your-organizations-ssh-certificate-authorities ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md deleted file mode 100644 index 9311846c34..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Administrar las autoridades de certificación SSH de tu organización -intro: Puedes agregar o eliminar autoridades de certificación SSH desde tu organización. -product: '{% data reusables.gated-features.ssh-certificate-authorities %}' -redirect_from: - - /articles/managing-your-organizations-ssh-certificate-authorities - - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities -versions: - free-pro-team: '*' - enterprise-server: '>=2.19' ---- -Los propietarios de la organización pueden administrar autoridades de certificado (CA) SSH de la organización - -Puedes permitir que los miembros accedan a los repositorios d ela organización mediante certificados SSH que brindas al agregar un CA SSH a tu organización. {% data reusables.organizations.can-require-ssh-cert %}Para obtener más información, consulta "[Acerca de las autoridades de certificados de SSH](/articles/about-ssh-certificate-authorities)". - -### Agregar una autoridad de certificado de SSH - -{% data reusables.organizations.add-extension-to-cert %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.organizations.new-ssh-ca %} -{% data reusables.organizations.require-ssh-cert %} - -### Eliminar una autoridad de certificado de SSH - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.organizations.delete-ssh-ca %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/adding-people-to-your-organization.md deleted file mode 100644 index 766bd6d3d1..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/adding-people-to-your-organization.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Agregar personas a tu organización -intro: 'Puedes hacer que cualquier persona se convierta en miembro de tu organización usando el nombre de usuario de {% data variables.product.product_name %} o la dirección de correo electrónico.' -redirect_from: - - /articles/adding-people-to-your-organization - - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization -versions: - enterprise-server: '*' ---- -{% tip %} - -**Tips**: -- Solo los propietarios de la organización pueden agregar usuarios a una organización. Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". -- Si tu organización[requiere que los miembros usen autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization), los usuarios deben [habilitar la autenticación de dos factores](/articles/securing-your-account-with-two-factor-authentication-2fa) antes de que puedas agregarlos a la organización. - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.invite_member_from_people_tab %} -{% data reusables.organizations.invite_to_org %} -{% data reusables.organizations.choose-to-restore-privileges %} -{% data reusables.organizations.choose-user-role %} -{% data reusables.organizations.choose-user-license %} -{% data reusables.organizations.add-user-to-teams %} -{% data reusables.organizations.send-invitation %} - -### Leer más -- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md deleted file mode 100644 index 7007f04891..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: ¿Puedo crear cuentas para personas en mi organización? -redirect_from: - - /articles/can-i-create-accounts-for-those-in-my-organization/ - - /articles/can-i-create-accounts-for-people-in-my-organization - - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization -intro: 'Si bien puedes agregar usuarios a una organización que has creado, no puedes crear cuentas de usuario personales en nombre de otra persona.' -versions: - free-pro-team: '*' ---- -Dado que accedes a una organización iniciando sesión mediante tu cuenta personal, cada uno de los miembros del equipo necesita una cuenta personal. Una vez que tienes los nombres de usuario de cada persona que deseas agregar a tu organización, puedes agregarlos a los equipos. - -### Agregar usuarios a tu organización - -1. Brinda a cada persona las instrucciones para [crear una cuenta personal](/articles/signing-up-for-a-new-github-account). -2. Preguntar el nombre de usuario a cada persona a la que deseas dar membresía a la organización. -3. [Invitar a las nuevas cuentas personales para que se unan](/articles/inviting-users-to-join-your-organization) a tu organización. Usar [roles de la organización](/articles/permission-levels-for-an-organization) y [permisos de repositorio](/articles/repository-permission-levels-for-an-organization) para limitar el acceso a cada cuenta. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md deleted file mode 100644 index ebe4867520..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Cancelar o editar una invitación a unirse a tu organización -intro: Los propietarios de la organización pueden editar o cancelar una invitación para convertirte en miembro de tu organización en cualquier momento antes de que el usuario acepte. -redirect_from: - - /articles/canceling-or-editing-an-invitation-to-join-your-organization - - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization -versions: - free-pro-team: '*' ---- -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. En la pestaña (People) Personas, haz clic en **Pending invitation** (Invitación pendiente). ![Enlace a invitación pendiente](/assets/images/help/organizations/pending-invitation-link.png) -5. Junto al nombre de usuario o la dirección de correo electrónico de la persona cuya invitación deseas editar o cancelar, haz clic en **Edit invitation** (Editar invitación). ![Botón Edit invitation (Editar invitación)](/assets/images/help/organizations/edit-invitation-button.png) - - Es posible que necesites hacer clic en **View all invitations** (Ver todas las invitaciones) en la parte inferior de la ventana para encontrar a la persona que estás buscando. -6. Decide si deseas edita o cancelar la invitación del usuario para unirse a tu organización. ![Botones Update invitation (Actualizar invitación) y Cancel invitation (Cancelar invitación)](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png) - - Para editar la invitación del usuario, selecciona un rol o equipo diferente, luego haz clic en **Update invitation** (Actualizar invitación). - - Para cancelar la invitación del usuario para unirte a tu organización, haz clic en **Cancel invitation** (Cancelar invitación). - -### Leer más - -{% if currentVersion == "free-pro-team@latest" %} -- "[Invitar a usuarios para que se unan a nuestra organización](/articles/inviting-users-to-join-your-organization)" -{% endif %} -- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/index.md deleted file mode 100644 index f7ae94fea1..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Administrar la membresía en tu organización -intro: 'Después de crear tu organización, puedes {% if currentVersion == "free-pro-team@latest" %}invitar a personas para que se conviertan en {% else %}agregar personas como{% endif %} miembros de la organización. También puedes eliminar a miembros de la organización y reinstalar a miembros antiguos.' -redirect_from: - - /articles/removing-a-user-from-your-organization/ - - /articles/managing-membership-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /inviting-users-to-join-your-organization - - /canceling-or-editing-an-invitation-to-join-your-organization - - /adding-people-to-your-organization - - /removing-a-member-from-your-organization - - /reinstating-a-former-member-of-your-organization - - /can-i-create-accounts-for-people-in-my-organization ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md deleted file mode 100644 index affa9e9424..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Invitar a usuarios a unirse a tu organización -intro: 'Puedes invitar a cualquier persona a que se convierta en miembro de tu organización usando su nombre de usuario o dirección de correo electrónico {% data variables.product.product_name %}.' -redirect_from: - - /articles/adding-or-inviting-members-to-a-team-in-an-organization/ - - /articles/inviting-users-to-join-your-organization - - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization -versions: - free-pro-team: '*' ---- -{% tip %} - -**Tips**: -- Solo los propietarios de la organización pueden invitar a usuarios a unirse a una organización. Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". -- Si tu organización tiene una suscripción de pago por usuario, debe de existir una licencia sin utilizarse antes de que puedas invitar a un nuevo miembro para que se una a la organización o antes de reinstalar a algún mimbro previo de la misma. Para obtener más información, consulta "[About per-user pricing](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %} -- Si tu organización [requiere que los miembros usen la autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization), los usuarios que invites deben[habilitar la autenticación de dos factores](/articles/securing-your-account-with-two-factor-authentication-2fa) para poder aceptar la invitación. - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.invite_member_from_people_tab %} -{% data reusables.organizations.invite_to_org %} -{% data reusables.organizations.choose-to-restore-privileges %} -{% data reusables.organizations.choose-user-role %} -{% data reusables.organizations.add-user-to-teams %} -{% data reusables.organizations.send-invitation %} -{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} - -### Leer más -- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md deleted file mode 100644 index bf5658ab22..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Reinstalar un miembro antiguo de tu organización -intro: 'Los dueños de las organizaciones pueden {% if currentVersion == "free-pro-team@latest" %} invitar a un miembro previo de la organización para que se vuelva a unir{% else %}añadir miembros previos a{% endif%}sus organizaciónes, y escoger si se restablecen los roles previos, permisos de acceso, bifurcaciones y configuraciones de estas personas.' -redirect_from: - - /articles/reinstating-a-former-member-of-your-organization - - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Si [eliminas un usuario de tu organización](/articles/removing-a-member-from-your-organization), [conviertes un miembro de la organización en un colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator) o si se elimina un usuario de tu organización porque [solicitaste a los miembros y colaboradores externos que habilitaran la autenticación de dos factores (2FA)](/articles/requiring-two-factor-authentication-in-your-organization), los privilegios y parámetros de acceso del usuario se guardarán durante tres meses. Puedes restaurar los privilegios del usuario si lo vuelves a {% if currentVersion =="free-pro-team@latest" %}invitar{% else %}agregar{% endif %} a la organización en el transcurso de ese tiempo. - -{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} - -Cuando reinstales un miembro antiguo de la organización, puedes restaurar lo siguiente: - - El rol del usuario en la organización - - Cualquier bifurcación privada de los repositorios que son propiedad de la organización - - La membresía a los equipos de la organización - - El acceso y los permisos previos para los repositorios de la organización - - Las estrellas para los repositorios de la organización - - Las asignaciones de propuestas en la organización - - Las suscripciones a repositorios (los parámetros de notificaciones para observar, no observar o ignorar la actividad de un repositorio) - - {% tip %} - - {% if currentVersion == "free-pro-team@latest" %} - **Tips**: - - Si se eliminó de la organización a un miembro de la organización porque no utilizó la autenticación de dos factores, y tu organización aún requiere que los miembros utilicen la 2FA, el miembro antiguo debe habilitar la autenticación de dos factores antes de que puedas reinstalar su membresía. - - Solo los propietarios de la organización pueden invitar a usuarios a unirse a una organización. Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". - - Si tu organización tiene una suscripción de pago por usuario, debes de contar con una licencia disponible antes de que puedas reinstaurar a algún miembro previo de la organización. Para obtener más información, consulta "[About per-user pricing](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %} - - {% else %} - **Tips**: - - Si se eliminó de la organización a un miembro de la organización porque no utilizó la autenticación de dos factores, y tu organización aún requiere que los miembros utilicen la 2FA, el miembro antiguo debe habilitar la autenticación de dos factores antes de que puedas reinstalar su membresía. - - Solo los propietarios de la organización pueden agregar usuarios a una organización. Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". - {% endif %} - - {% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.invite_member_from_people_tab %} -{% data reusables.organizations.reinstate-user-type-username %} -{% if currentVersion == "free-pro-team@latest" %} -6. Decide si quieres restaurar los privilegios antiguos de esa persona en la organización o eliminar sus privilegios antiguos y establecer nuevos permisos de acceso, luego haz clic en **Invite and reinstate** (Invitar y reinstalar) o **Invite and start fresh** (Invitar e iniciar de nuevo). ![Decide si quieres restaurar la información o no](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) -{% else %} -6. Decide si quieres restaurar los privilegios antiguos de esa persona en la organización o eliminar sus privilegios antiguos y establecer nuevos permisos de acceso, luego haz clic en **Add and reinstate** (Agregar y reinstalar) o **Add and start fresh** (Agregar e iniciar de nuevo). ![Decide si quieres restaurar los privilegios](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -7. Si eliminaste los privilegios anteriores de un miembro antiguo de la organización, elige un rol para el usuario, y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Send invitation** (Enviar invitación). ![Opciones de rol y equipo y botón para enviar invitación](/assets/images/help/organizations/add-role-send-invitation.png) -{% else %} -7. Si eliminaste los privilegios anteriores de un miembro antiguo de la organización, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Add member** (Agregar miembro). ![Opciones de rol y equipo y botón para agregar miembros](/assets/images/help/organizations/add-role-add-member.png) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} -{% endif %} - -### Leer más - -- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/removing-a-member-from-your-organization.md deleted file mode 100644 index db4b4739d8..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Eliminar a un miembro de tu organización -intro: 'Si miembros de tu organización ya no necesitan acceso a ningún repositorio que le pertenece a la organización, puedes eliminarlos de la organización.' -redirect_from: - - /articles/removing-a-member-from-your-organization - - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Solo los propietarios de la organización pueden eliminar usuarios de una organización. - -{% if currentVersion == "free-pro-team@latest" %} - -{% warning %} - -**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. -- 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 %} - -{% else %} - -{% warning %} - -**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. - - 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 %} - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -Para ayudar con la transición de la persona que estás eliminando de tu organización y ayudar a asegurar que elimine la información confidencial o propiedad intelectual, recomendamos compartir una lista de verificación para salir de tu organización. Para ver un ejemplo, consulta "[Buenas prácticas para salir de tu empresa](/articles/best-practices-for-leaving-your-company/)". - -{% endif %} - -{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %} - -### Revocar la membresía del usuario - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Selecciona el miembro o los miembros que quieres eliminar de la organización. ![Lista de miembros con dos miembros seleccionados](/assets/images/help/teams/list-of-members-selected-bulk.png) -5. Arriba de la lista de miembros, utiliza el menú desplegable y haz clic en **Remove from organization** (Eliminar de la organización). ![Menú desplegable con la opción para eliminar miembros](/assets/images/help/teams/user-bulk-management-options.png) -6. Revisa el miembro o los miembros que se eliminarán de la organización, luego haz clic en **Remove members** (Eliminar miembros). ![Lista de miembros que se eliminarán y botón Remove members (Eliminar miembros)](/assets/images/help/teams/confirm-remove-members-bulk.png) - -### Leer más - -- "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md deleted file mode 100644 index a692bf0635..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Permitir que personas eliminen propuestas en tu organización -intro: Los propietarios de la organización pueden permitir que determinadas personas eliminen propuestas en repositorios que pertenecen a tu organización. -redirect_from: - - /articles/allowing-people-to-delete-issues-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Por defecto, las propuestas no pueden eliminarse en los repositorios de una organización. El propietario de la organización debe habilitar esta característica para todos los repositorios de la organización en primer lugar. - -Una vez habilitados, los propietarios de la organización y las personas con permisos de administración en un repositorio que es propiedad de la empresa pueden eliminar propuestas. Entre las personas con permisos de administración en un repositorio se incluyen los miembros de la organización y los colaboradores externos con privilegios de administración. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)" y "[Eliminar una propuesta"](/articles/deleting-an-issue)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. En "Issue deletion" (Eliminación de la propuesta), selecciona **Permitir que los miembros eliminen propuestas para esta organización**. ![Casilla de verificación para permitir que las personas eliminen propuestas](/assets/images/help/settings/issue-deletion.png) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md deleted file mode 100644 index e001d7a1b7..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Cambiar la visibilidad de la información de dependencias de la organización -intro: Puedes permitir que todos los miembros de la organización vean información de dependencias para tu organización o limiten la visualización de los propietarios de la organización. -product: '{% data reusables.gated-features.org-insights %}' -redirect_from: - - /articles/changing-the-visibility-of-your-organizations-dependency-insights - - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights -versions: - free-pro-team: '*' ---- -Los propietarios de la organización pueden establecer limitaciones para ver la información de dependencias de la organización. De manera predeterminada, todos los miembros de una organización pueden ver información de la dependencia de la organización. - -Los propietarios de la empresa pueden establecer limitaciones para ver la información de las dependencias de la organización en todas las organizaciones de tu cuenta de empresa. Para obtener más información, consulta "[Hacer cumplir una política sobre las percepciones de la dependencia en tu cuenta de empresa](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)" - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. En "Member organization permissions" (Permisos para miembros de la organización), selecciona o quita la marca de selección de **Allow members to view dependency insights** (Permitir que los miembros vean información de dependencias). ![Casilla de verificación para permitir que los miembros vean información](/assets/images/help/organizations/allow-members-to-view-insights.png) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/converting-an-organization-into-a-user.md deleted file mode 100644 index 0f5ed235fb..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/converting-an-organization-into-a-user.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Convertir una organización en un usuario -intro: 'No es posible convertir una organización en una cuenta de usuario personal, pero puedes crear una nueva cuenta de usuario y transferirle los repositorios de la organización.' -redirect_from: - - /articles/converting-an-organization-into-a-user - - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% if currentVersion == "free-pro-team@latest" %} - -1. [Regístrate](/articles/signing-up-for-a-new-github-account) para una nueva cuenta de usuario de GitHub. -2. [Cambia el rol de usuario a un propietario](/articles/changing-a-person-s-role-to-owner). -3. {% data variables.product.signin_link %} para la nueva cuenta de usuario. -4. [Transfiere cada repositorio de la organización](/articles/how-to-transfer-a-repository) a la nueva cuenta de usuario. -5. [Elimina la organización](/articles/deleting-an-organization-account). -6. [Cambia el nombre del usuario](/articles/changing-your-github-username) por el nombre de la organización. - -{% else %} - -1. Inicia sesión para una nueva cuenta de usuario de GitHub Enterprise. -2. [Cambia el rol de usuario a un propietario](/articles/changing-a-person-s-role-to-owner). -3. {% data variables.product.signin_link %} para la nueva cuenta de usuario. -4. [Transfiere cada repositorio de la organización](/articles/how-to-transfer-a-repository) a la nueva cuenta de usuario. -5. [Elimina la organización](/articles/deleting-an-organization-account). -6. [Cambia el nombre del usuario](/articles/changing-your-github-username) por el nombre de la organización. - -{% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/deleting-an-organization-account.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/deleting-an-organization-account.md deleted file mode 100644 index f8fddf562c..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/deleting-an-organization-account.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Eliminar una cuenta de una organización -intro: 'Cuando eliminas una organización, se eliminan también todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas del proyecto y de la organización. {% if currentVersion == "free-pro-team@latest" %}Tu facturación finalizará y el nombre de la organización pasará a estar disponible para su uso por parte de una nueva cuenta de usuario o de organización.{% endif %}' -redirect_from: - - /articles/deleting-an-organization-account - - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% if currentVersion == "free-pro-team@latest" %} -{% tip %} - -**Sugerencia**: Si deseas cancelar tu suscripción paga, puedes [bajar la categoría de tu organización a {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) en lugar de eliminar la organización y su contenido. - -{% endtip %} - -{% endif %} - -### 1. Haz una copia de respaldo del contenido de tu organización - -Una vez que eliminas una organización, GitHub **no puede restaurar su contenido**. Por consiguiente, antes de eliminar tu organización, asegúrate de tener una copia de todos los repositorios, wikis y propuestas de la cuenta. - -### 2. Elimina la organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -4. Junto a la parte inferior de la página de configuración de la organización, haz clic en **Eliminar esta organización**. ![Botón Eliminar esta organización](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md deleted file mode 100644 index 817e9e0e89..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Inhabilitar o limitar GitHub Actions para tu organización -intro: 'Los propietarios de organización pueden inhabilitar, habilitar y limitar GitHub Actions para la misma.' -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization ---- -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -### Acerca de los permisos de {% data variables.product.prodname_actions %} para tu organización - -{% data reusables.github-actions.disabling-github-actions %}Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". - -Puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.github-actions.enabled-actions-description %}Puedes inhabilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización. {% data reusables.github-actions.disabled-actions-description %} - -De manera alterna, puedes habilitar {% data variables.product.prodname_actions %} para todos los repositorios en tu organización, pero limitando las acciones que un flujo de trabajo puede ejecutar. {% data reusables.github-actions.enabled-local-github-actions %} - -### Administrar los permisos de {% data variables.product.prodname_actions %} para tu organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.settings-sidebar-actions %} -1. Debajo de **Acciones locales y de terceros**, selecciona una opción. ![Habilitar, inhabilitar o limitar acciones para esta organización](/assets/images/help/repository/enable-org-actions.png) -1. Haz clic en **Save (Guardar)**. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -### Habilitar flujos de trabajo para las bifurcaciones de repositorios privados - -{% data reusables.github-actions.private-repository-forks-overview %} - -#### Configurar la política de bifurcaciones privadas para una organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.settings-sidebar-actions %} -{% data reusables.github-actions.private-repository-forks-configure %} -{% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/disabling-publication-of-github-pages-sites-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/disabling-publication-of-github-pages-sites-for-your-organization.md deleted file mode 100644 index 98fd09482e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/disabling-publication-of-github-pages-sites-for-your-organization.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Disabling publication of GitHub Pages sites for your organization -intro: 'You can prevent members of your organization from publishing {% data variables.product.prodname_pages %} sites from repositories in the organization.' -permissions: 'Organization owners can disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '>2.22' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization ---- -### About restrictions on publication of {% data variables.product.prodname_pages %} sites - -You can control whether members of your organization can publish websites from repositories in your organization using {% data variables.product.prodname_pages %}. For more information about {% data variables.product.prodname_pages %}, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." - -{% if currentVersion != "free-pro-team@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or internal{% endif %}. For more information, see{% if currentVersion != "free-pro-team@latest" %} "[Configuring {% data variables.product.prodname_pages %} on your appliance](/enterprise/admin/installation/configuring-github-pages-on-your-appliance#making-github-pages-publicly-accessible)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." - -### Disabling publication of {% data variables.product.prodname_pages %} sites - -After you disable publication of {% data variables.product.prodname_pages %} sites, any published site will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/github/working-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 %} -1. Under "Pages creation", unselect **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) -1. Click **Save**. - !["Save" button for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-save-button.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/index.md deleted file mode 100644 index 5a8f94b475..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/index.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Administrar configuraciones de la organización -intro: 'Los administradores de la organización pueden cambiar diversas configuraciones, incluidos los nombres de los repositorios que pertenecen a la organización y la membresía de equipo de los propietarios. Además, los administradores de la organización pueden eliminar a la organización y a todos sus repositorios.' -redirect_from: - - /articles/managing-organization-settings -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /verifying-your-organizations-domain - - /renaming-an-organization - - /transferring-organization-ownership - - /restricting-repository-creation-in-your-organization - - /setting-permissions-for-deleting-or-transferring-repositories - - /restricting-repository-visibility-changes-in-your-organization - - /managing-the-forking-policy-for-your-organization - - /disabling-or-limiting-github-actions-for-your-organization - - /setting-permissions-for-adding-outside-collaborators - - /allowing-people-to-delete-issues-in-your-organization - - /setting-team-creation-permissions-in-your-organization - - /managing-scheduled-reminders-for-your-organization - - /managing-the-default-branch-name-for-repositories-in-your-organization - - /managing-default-labels-for-repositories-in-your-organization - - /changing-the-visibility-of-your-organizations-dependency-insights - - /managing-the-display-of-member-names-in-your-organization - - /disabling-publication-of-github-pages-sites-for-your-organization - - /deleting-an-organization-account - - /converting-an-organization-into-a-user - - /integrating-jira-with-your-organization-project-board - - /upgrading-to-the-corporate-terms-of-service - - /entering-a-data-protection-agreement-with-github-for-gdpr-compliance ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/integrating-jira-with-your-organization-project-board.md deleted file mode 100644 index dea4d5d03d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/integrating-jira-with-your-organization-project-board.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Integrar Jira al tablero de proyecto de tu organización -intro: 'Puedes integrar Jira Cloud a la cuenta de tu organización para escanear confirmaciones y solicitudes de extracción, creando los metadatos e hipervínculos correspondientes en cualquier propuesta de Jira mencionada.' -redirect_from: - - /articles/integrating-jira-with-your-organization-project-board - - /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board -versions: - enterprise-server: '*' ---- -{% data reusables.user_settings.access_settings %} -2. En la barra lateral izquierda en **Organization settings** (Configuraciones de la organización), haz clic en el nombre de tu organización. ![Barra lateral Organization name (Nombre de la organización)](/assets/images/help/settings/organization-settings-from-sidebar.png) -3. En la barra lateral de **Developer settings** (Configuraciones del programador), haz clic en **OAuth applications** (Aplicaciones OAuth). ![Pestaña de aplicaciones OAuth de la barra lateral izquierda](/assets/images/help/organizations/org-oauth-applications-ghe.png) -4. Haz clic en **Register a new application** (Registrar una aplicación nueva). -5. En **Application name** (Nombre de la aplicación), escribe "Jira". -6. En **Homepage URL** (URL de la página de inicio), escribe la URL completa de tu instancia de Jira. -7. En **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa para tu instancia de Jira. -8. Haz clic en **Register application** (Registrar aplicación). ![Botón Register application (Registrar aplicación)](/assets/images/help/oauth/register-application-button.png) -9. En **Organization owned applications** (Aplicaciones propiedad de la organización), presta atención a los valores de "Client ID" (Id. del cliente) y "Client Secret" (Secreto del cliente). ![Id. del cliente y secreto del cliente](/assets/images/help/oauth/client-id-and-secret.png) -{% data reusables.user_settings.jira_help_docs %} - -### Leer más - -- ["Integrar Jira a tus proyectos personales"](/articles/integrating-jira-with-your-personal-projects) -- Conectar Jira Cloud a GitHub (Documentación de Atlassian) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md deleted file mode 100644 index ae48863ab1..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Administrar etiquetas predeterminadas para los repositorios de tu organización -intro: Puedes personalizar las etiquetas que se incluirán en todos los repositorios nuevos de tu organización. -redirect_from: - - /articles/managing-default-labels-for-repositories-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '>=2.20' ---- -Los propietarios de la organización pueden administrar las etiquetas predeterminadas para los repositorios de la organización. - -Las etiquetas predeterminadas se incluirán en todos los repositorios nuevos de tu organización, pero luego cualquier usuario con acceso de escritura al repositorio puede editar o eliminar las etiquetas de ese repositorio. Agregar, editar o eliminar una etiqueta predeterminada no agrega, edita o elimina la etiqueta de los repositorios existentes. - -### Crear una etiqueta predeterminada - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -{% data reusables.organizations.repository-defaults %} -{% else %} -{% data reusables.organizations.repository-labels %} -{% endif %} -5. Debajo de "Repository labels" (Etiquetas del repositorio), haz clic en **New label** (Etiqueta nueva). ![Botón New update (Actualización nueva)](/assets/images/help/organizations/new-label-button.png) -{% data reusables.project-management.name-label %} -{% data reusables.project-management.label-description %} -{% data reusables.project-management.label-color-randomizer %} -{% data reusables.project-management.create-label %} - -### Editar una etiqueta predeterminada - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -{% data reusables.organizations.repository-defaults %} -{% else %} -{% data reusables.organizations.repository-labels %} -{% endif %} -{% data reusables.project-management.edit-label %} -{% data reusables.project-management.name-label %} -{% data reusables.project-management.label-description %} -{% data reusables.project-management.label-color-randomizer %} -{% data reusables.project-management.save-label %} - -### Eliminar una etiqueta predeterminada - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -{% data reusables.organizations.repository-defaults %} -{% else %} -{% data reusables.organizations.repository-labels %} -{% endif %} -{% data reusables.project-management.delete-label %} -{% data reusables.project-management.confirm-label-deletion %} - -### Leer más - -- "[Acerca de las etiquetas](/articles/about-labels)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md deleted file mode 100644 index 2ea8a64a41..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Administrar los recordatorios programados para tu organización -intro: Puedes obtener recordatorios en Slack para todas las solicitudes de extracción de las cuales se haya solicitado revisión por parte de los equipos en tu organización. -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization ---- -### Acerca de los recordatorios programados para las solicitudes de extracción - -{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} - -Los propietarios de la organización pueden programar un recordatorio para uno mas equipos en ella que contemple todas las solicitudes de extracción que han solicitado la revisión de uno o más equipos de ésta. - -### Crear un recordatorio programado para una organización -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png) -{% data reusables.reminders.add-reminder %} -{% data reusables.reminders.authorize-slack %} -{% data reusables.reminders.slack-channel %} -{% data reusables.reminders.days-dropdown %} -{% data reusables.reminders.times-dropdowns %} -{% data reusables.reminders.tracked-repos %} -11. Da clic en el menú desplegable de **Añadir equipo** debajo de "Filtrar por equipo asignado para revisar el código", y elige uno o más equipos. Puedes agregar hasta 100 equipos. Si el equipo que seleccionas carece de acceso a los "Repositorios rastreados" seleccionados anteriormente, no podrás crear el recordatorio programado. ![Menú desplegable de añadir un equipo](/assets/images/help/organizations/scheduled-reminders-add-teams.png) -{% data reusables.reminders.ignore-drafts %} -{% data reusables.reminders.no-review-requests %} -{% data reusables.reminders.author-reviews %} -{% data reusables.reminders.approved-prs %} -{% data reusables.reminders.min-age %} -{% data reusables.reminders.min-staleness %} -{% data reusables.reminders.ignored-terms %} -{% data reusables.reminders.ignored-labels %} -{% data reusables.reminders.required-labels %} -{% data reusables.reminders.create-reminder %} - -### Administrar un recordatorio programado para una organización -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png) -{% data reusables.reminders.edit-existing %} -{% data reusables.reminders.edit-page %} -{% data reusables.reminders.update-buttons %} - -### Borrar un recordatorio programado para una organización -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/organizations/scheduled-reminders-org.png) -{% data reusables.reminders.delete %} - -### Leer más - -- "[Administrar tus recordatorios programados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" -- "[Administrar los recordatorios programados para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md deleted file mode 100644 index d53fbb64bd..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Administrar el nombre de la rama predeterminada para los repositorios en tu organización -intro: Puedes configurar el nombre de la rama predeterminada de los repositorios que crean los miembros de tu organizción. -versions: - free-pro-team: '*' - enterprise-server: '>=2.23' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization ---- -### Acerca del nombre de la rama predeterminada - -Cuando un miembro de tu organización crea un repositorio nuevo, {% data variables.product.prodname_dotcom %} creará una sola rama y la configurará como la rama predeterminada del repositorio. Actualmente, {% data variables.product.prodname_dotcom %} nombra a la rama predeterminada como `master`, pero puedes configurarla para que se llame como quieras de acuerdo con tu ambiente de desarrollo. - -{% data reusables.branches.set-default-branch %} - -{% data reusables.branches.rename-existing-branch %} - -### Configurar el nombre de la rama predeterminada - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.repository-defaults %} -3. Debajo de "Rama predeterminada del repositorio", da clic en **Cambiar el nombre de la rama predeterminada ahora**. ![Botón de ignorar](/assets/images/help/organizations/repo-default-name-button.png) - {% note %} - - **Nota:**Si el dueño de tu empresa requiere una política para el nombre predeterminado, no podrás cambiarlo aquí. Podrás configurar la rama predeterminada en repositorios individuales. Para obtener más información, consulta las secciones "[Requerir una política para el nombre de la rama predeterminada](/github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-the-default-branch-name)" y "[Configurar la rama predeterminada](/github/administering-a-repository/setting-the-default-branch)". - - {% endnote %} -4. Teclea el nombre predeterminado que quisieras utilizar para las ramas nuevas. ![Caja de texto para ingresar el nombre predeterminado](/assets/images/help/organizations/repo-default-name-text.png) -5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/organizations/repo-default-name-update.png) - -### Leer más - -- [Administrar el nombre de la rama predeterminada para tus repositorios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md deleted file mode 100644 index babc66a7e6..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Administrar la visualización de los nombres de los miembros en tu organización -intro: Puedes permitir que los miembros de tu organización vean un nombre de perfil del autor de un comentarios en los repositorios privados en la organización. -product: '{% data reusables.gated-features.display-names %}' -redirect_from: - - /articles/managing-the-display-of-member-names-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '>=2.18' ---- -Los propietarios de la organización pueden administrar la visualización de los nombres de los miembros en una organización. - -![Nombre del perfil del autor del comentario que se muestra en un comentario](/assets/images/help/issues/commenter-full-name.png) - -Cada miembro de la organización elige su propio nombre de perfil en sus configuraciones. Para obtener más información, consulta la sección "[Personalizar tu perfil](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)." - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. Dentro de "Admin repository permissions" (Permisos del administrador del repositorio), selecciona o quita la marca de selección **Allow members to see comment author's profile name in private repositories (Permitir que los miembros vean el nombre de perfil del autor del comentario en los repositorios privados)**. ![Casilla de verificación para permitir que los miembros vean el nombre completo del autor del comentario en los repositorios privados](/assets/images/help/organizations/allow-members-to-view-full-names.png) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-forking-policy-for-your-organization.md deleted file mode 100644 index d2a912d58b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/managing-the-forking-policy-for-your-organization.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Administrar la política de bifurcación para tu organización -intro: 'Puedes permitir o prevenir la bifurcación de cualquier repositorio privado {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} e interno{% endif %}que pertenezca a tu organización.' -redirect_from: - - /articles/allowing-people-to-fork-private-repositories-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization -permissions: Los propietarios de la organización pueden administrar la política de bifurcación para la misma. -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Predeterminadamente, las organizaciones nuevas se configuran para impedir la bifurcación de repositorios privados{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} e internos{% endif %}. - -Si permites la bifurcación de repositorios privados {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} e internos{% endif %} a nivel organizacional, también puedes configurar la capacidad para bifurcar repositorios privados {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o internos{% endif %} específicos. Para obtener más información, consulta la sección "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". - -{% data reusables.organizations.internal-repos-enterprise %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. Debajo de "Bifurcación de repositorios", selecciona **Permitir la bifurcación de repositorios privados** o **Permitir la bifurcación de repositorios privados e internos**. ![Casilla de verificación para permitir o prohibir la bifurcación en la organización](/assets/images/help/repository/allow-disable-forking-organization.png) -6. Haz clic en **Save (Guardar)**. - -### Leer más - -- "[Acerca de las bifurcaciones](/articles/about-forks)" -- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/renaming-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/renaming-an-organization.md deleted file mode 100644 index a5fb463874..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/renaming-an-organization.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Renombrar una organización -intro: 'Si tu proyecto o empresa cambió de nombre, puedes actualizar el nombre de tu organización para que coincida.' -redirect_from: - - /articles/what-happens-when-i-change-my-organization-s-name/ - - /articles/renaming-an-organization - - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% tip %} - -**Sugerencia:** Solo los propietarios de la organización pueden renombrar una organización. {% data reusables.organizations.new-org-permissions-more-info %} - -{% endtip %} - -### ¿Qué sucede cuando cambio el nombre de mi organización? - -Después de cambiar el nombre de tu organización, el nombre antiguo de tu organización se pone a disposición para quien lo quiera utilizar. Cuando cambias el nombre de tu organización, la mayoría de las referencias a los repositorios bajo el nombre antiguo de tu organización se cambiarán automáticamente al nombre nuevo. Sin embargo, algunos enlaces a tu perfil no se redirigirán automáticamente. - -#### Cambios que ocurren automáticamente - -- {% data variables.product.prodname_dotcom %} redirige automáticamente las referencias a tus repositorios. Los enlaces web a los **repositorios** existentes de tu organización seguirán funcionando. Puede tomar algunos minutos para que se complete luego de que inicies el cambio. -- Puedes continuar subiendo tus repositorios locales a la URL de seguimiento del remoto antiguo sin actualizarla. Sin embargo, recomendamos que actualices todas las URL de repositorios remotos existentes después de cambiar el nombre de tu organización. Como el nombre antiguo de tu organización queda disponible para que lo utilice cualquier otra persona después de que lo cambies, el propietario de la organización nuevo puede crear repositorios que remplacen las entradas redirigidas a tu repositorio. Para obtener más información, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url). -- Las confirmaciones de Git anteriores también se atribuirán según corresponda a los usuarios de tu organización. - -#### Cambios que no son automáticos - -Después de cambiar el nombre de tu organización: -- Los enlaces a la página de perfil de tu organización anterior, como `https://{% data variables.command_line.backticks %}/previousorgname`, generarán un error 404. Recomendamos que actualices los enlaces a tu organización desde otros sitios{% if currentVersion == "free-pro-team@latest" %}, como tus perfiles de LinkedIn o Twitter{% endif %}. -- Las solicitudes API que utilizan el nombre de la organización antiguo generarán un error 404. Recomendamos que actualices el nombre de la organización antiguo en tus solicitudes API. -- No existen redireccionamientos automáticos [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) para los equipos que utilizan el nombre de la organización antiguo. - -### Cambiar el nombre de tu organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -4. Cerca de la parte de abajo de la página de parámetros, en "Rename organization" (Renombrar organización), haz clic en **Rename Organization** (Renombrar organización). ![Botón Rename organization (Renombrar organización)](/assets/images/help/settings/settings-rename-organization.png) - -### Leer más - -* "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)" -* "[¿Por qué mis confirmaciones están vinculadas al usuario incorrecto?](/articles/why-are-my-commits-linked-to-the-wrong-user)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/restricting-repository-creation-in-your-organization.md deleted file mode 100644 index 2fbfaf247f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Restringir la creación de repositorios en tu organización -intro: 'Para proteger los datos de tu organización, puedes configurar permisos para crear repositorios en tu organización.' -redirect_from: - - /articles/restricting-repository-creation-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -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. {% if currentVersion == "free-pro-team@latest" %}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 la visibilidad de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". - -Organization owners can always create any type of repository. - -{% if currentVersion == "free-pro-team@latest" %}Los propietarios de empresas{% else %}administradores de sitio{% endif %} pueden restringir las opciones que tienes disponibles para la política de creación de repositorios de tu organización. Para obtener más información, consulta la sección {% if currentVersion == "free-pro-team@latest" %}"[Requerir políticas de administración de repositorios en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account)".{% else %}"[Restringir la creación de repositorios en tu instancia"](/enterprise/admin/user-management/restricting-repository-creation-in-your-instance).{% endif %} - -{% warning %} - -**Advertencia**: Este ajuste solo restringe las opciones de visibilidad disponibles cuando los repositorios se crean y no restringe la capacidad de cambiar la visibilidad del repositorio posteriormente. Para obtener más información acerca de cómo restringir los cambios a las visibilidades existentes de los repositorios, consulta la sección "[Restringir la visibilidad de los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)". - -{% endwarning %} - -{% data reusables.organizations.internal-repos-enterprise %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. Debajo de "Repository creation" (Creación de repositorios), selecciona {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}una o más opciones{% else %}un ajuste{% endif %}. ![Opciones de creación de repositorio](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md deleted file mode 100644 index b290e219f9..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Restringir cambios en la visibilidad de los repositorios en tu organización -intro: 'Para proteger los datos de tu organización, puedes configurar permisos para cambiar la visibilidad de los repositorios en tu organización.' -redirect_from: - - /articles/restricting-repository-visibility-changes-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Puedes restringir la capacidad de cambiar la visibilidad de los repositorios para los propietarios de la organización únicamente o permitir que los miembros con privilegios de administrador para un repositorio también cambien la visibilidad de privado a público o de público a privado. - -{% warning %} - -**Advertencia**: En caso de habilitarse, este ajuste permite a las personas con permisos administrativos cambiar un repositorio existente a cualquier visibilidad, aún si no permites que se cree este tipo de repositorio. Para obtener más información acerca de cómo restringir la visibilidad de los repositorios durante su creación, consulta la sección "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)". - -{% endwarning %} - - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. En "Repository visibility change" (Cambio en la visibilidad de los repositorios), anula la selección de **Allow members to change repository visibilities for this organization** (Permitir que los miembros cambien las visibilidades de los repositorios para esta organización). ![Casilla para permitir que los miembros cambien la visibilidad de los repositorios](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md deleted file mode 100644 index 7e7c5f9182..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Setting permissions for adding outside collaborators -intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can allow only owners to invite outside collaborators to organization repositories.' -product: '{% data reusables.gated-features.restict-add-collaborator %}' -redirect_from: - - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories/ - - /articles/setting-permissions-for-adding-outside-collaborators - - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Organization owners, and members with admin privileges for a repository, can invite outside collaborators to work on the repository. You can also restrict outside collaborator invite permissions to only organization owners. - -{% data reusables.organizations.outside-collaborators-use-seats %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% else %} - ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox.png){% endif %} -6. Click **Save**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md deleted file mode 100644 index 1faafcd987..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Configurar permisos para eliminar o transferir repositorios en tu organización -intro: 'Puedes permitir que los miembros de una organización con permisos de administrador accedan a un repositorio para eliminar o transferir el repositorio, o limitar la capacidad para borrar o transferir repositorios únicamente a los propietarios de la organización.' -redirect_from: - - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization/ - - /articles/setting-permissions-for-deleting-or-transferring-repositories - - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Los propietarios pueden configurar permisos para eliminar o transferir repositorios en una organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. Dentro de "Repository deletion and transfer" (Eliminación o transferencia de repositorios), selecciona o deselecciona **Allow members to delete or transfer repositories for this organization (Permitir que los miembros puedan eliminar o transferir repositorios para esta organización)**. ![Casilla de verificación para permitir que los miembros eliminen repositorios](/assets/images/help/organizations/disallow-members-to-delete-repositories.png) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md deleted file mode 100644 index cc4b3e4ce9..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Configurar permisos de creación de equipos en tu organización -intro: Puedes permitirle a todos los miembros de la organización crear equipos o limitar la creación de equipos a los propietarios de la organización. -redirect_from: - - /articles/setting-team-creation-permissions-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Los propietarios de la organización pueden establecer permisos de creación de equipos. - -Si no configuras permisos de creación de equipos, todos los miembros de la organización podrán crear equipos por defecto. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. Dentro de "Team creation rules" (Reglas de creación de equipos), selecciona o deselecciona **Allow members to create teams (Permitirle a los miembros crear equipos)**. ![Casilla de verificación para permitir que los miembros creen equipos](/assets/images/help/organizations/allow-members-to-create-teams.png) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/transferring-organization-ownership.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/transferring-organization-ownership.md deleted file mode 100644 index c2d08a8c29..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/transferring-organization-ownership.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Transferir la propiedad de la organización -redirect_from: - - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else/ - - /articles/transferring-organization-ownership - - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership -intro: 'Para hacer que alguna otra persona sea propietaria de una cuenta de organización, puedes agregar un propietario nuevo{% if currentVersion == "free-pro-team@latest" %}, asegurar que la información de facturación esté actualizada{% endif %} y luego eliminarte de la cuenta.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -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](/github/setting-up-and-managing-organizations-and-teams/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). -{% if currentVersion == "free-pro-team@latest" %} -3. Si actualmente eres responsable de pagarle a GitHub en tu organización, también tendrás que hacer que el propietario nuevo o un [gerente de facturación](/articles/adding-a-billing-manager-to-your-organization/) actualice la información de pago de la organización. Para obtener más información, consulta "[Agregar o editar un método de pago](/articles/adding-or-editing-a-payment-method)". - - {% warning %} - - **Advertencia**: Eliminarte de la organización **no** actualiza la información de facturación archivada para la cuenta de la organización. El propietario nuevo o un gerente de facturación debe actualizar la información de facturación archivada para eliminar tu información de tarjeta de crédito o de PayPal. - - {% endwarning %} - -{% endif %} -4. [Eliminarte](/articles/removing-yourself-from-an-organization) de la organización. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md deleted file mode 100644 index a6e8670a13..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Subir de categoría a los Términos de servicio corporativos -intro: Las organizaciones pueden subir de categoría desde los Términos de servicio estándar a los Términos de servicio corporativos. -redirect_from: - - /articles/upgrading-to-the-corporate-terms-of-service - - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service -versions: - free-pro-team: '*' ---- -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. Contáctate con {% data variables.contact.contact_support %} para solicitar un aumento de categoría a los Términos de servicio corporativos. Habilitarán un anuncio en el tablero de tu organización que te permitirá aceptar los Términos de servicio corporativos. -{% data reusables.dashboard.access-org-dashboard %} -3. En la parte de arriba de la página, a la derecha del anuncio de los Términos de servicio, haz clic en **Sign now** (Firmar ahora). ![Botón Sign now (Firmar ahora)](/assets/images/help/organizations/sign-now-button.png) -4. Lee la información acerca de los Términos de servicio corporativos, luego selecciona **Yes, I want to sign these terms on behalf of my business.** (Sí, quiero firmar estos términos en nombre de mi empresa.). ![Casilla para firmar e nombre de tu empresa](/assets/images/help/organizations/sign-on-behalf-business.png) -5. 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) -6. 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) - -### Leer más -- "[Términos de servicio corporativos de GitHub](/articles/github-corporate-terms-of-service/)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/verifying-your-organizations-domain.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/verifying-your-organizations-domain.md deleted file mode 100644 index f10fbac095..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-organization-settings/verifying-your-organizations-domain.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Verificar el dominio de tu organización -intro: 'Puedes verificar los dominios controlados por tu organización para confirmar la identidad de tu organización en {% data variables.product.product_name %}.' -redirect_from: - - /articles/verifying-your-organization-s-domain - - /articles/verifying-your-organizations-domain - - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain -versions: - free-pro-team: '*' ---- -Para verificar dominios en {% data variables.product.product_name %}, debes tener permisos de propietario en la organización. Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". También necesitarás acceso para modificar los registros de dominio con tu servicio de alojamiento de dominio. - -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. Si tu organización está en {% data variables.product.prodname_ghe_cloud %} y ha aceptado los Términos de servicio corporativos, los propietarios de la organización podrán verificar la identidad de los miembros de la organización al ver la dirección de correo electrónico de cada miembro dentro del dominio verificado. Para obtener más información, consulta "[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](/articles/upgrading-to-the-corporate-terms-of-service)." - -Para mostrar una insignia de "Verificado", el sitio web y la información de correo electrónico que se muestran en el perfil de tu organización deben coincidir con el o los dominios verificados. Si el sitio web y la dirección de correo electrónico que se muestran en el perfil de tu organización se alojan en un dominio diferente, debes verificar ambos dominios. - -{% note %} - -**Nota:** si la dirección de correo electrónico y el sitio web que se muestran en el perfil de tu organización utilizan variantes del mismo dominio, debes verificar ambas variantes. Por ejemplo, si el perfil de tu organización muestra el sitio web `www.example.com` y la dirección de correo electrónico `info@example.com`, deberías verificar tanto `www.example.com` como `example.com`. - -{% endnote %} - -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 a ese dominio. Para obtener más información, consulta "[Restringir las notificaciones por correo electrónico a un dominio aprobado](/articles/restricting-email-notifications-to-an-approved-domain)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.verified-domains %} -5. Haz clic en **Add a domain (Agregar un dominio)**. ![Botón para agregar un dominio](/assets/images/help/organizations/add-a-domain-button.png) -6. En el campo dominio, escribe el dominio que deseas verificar, después haz clic en **Add domain (Agregar dominio)**. ![Campo para agregar un dominio](/assets/images/help/organizations/add-domain-field.png) -7. Sigue las instrucciones dentro de **Add a DNS TXT record (Agregar un registro TXT de DNS)** para crear un registro TXT de DNS con tu servicio de alojamiento de dominio. Puede demorar hasta 72 horas para que tu configuración de DNS cambie. Una vez que la configuración de DNS ha cambiado, continúa al paso siguiente. ![Instrucciones para crear un registro txt de DNS](/assets/images/help/organizations/create-dns-txt-record-instructions.png) - - {% tip %} - - **Sugerencia:** puedes confirmar que tu configuración de DNS ha cambiado al ejecutar el comando `dig` en la línea de comando. En el comando de ejemplo, reemplaza `ORGANIZATION` por el nombre de tu organización y `example.com` por el dominio que deseas verificar. Deberías ver tu nuevo registro TXT enumerado en el resultado del comando. - - ```shell - $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT - ``` - - {% endtip %} - -8. Después de confirmar que tu registro de TXT se agregó en tu DNS, desplázate hasta la pestaña Verified domains (Dominios verificados) en las configuraciones de tu organización. Puedes seguir los pasos anteriores uno a cuatro para ubicar la pestaña Dominios verificados. ![Página de configuraciones de dominios verificados con dominio pendiente](/assets/images/help/organizations/pending-domain-verification.png) -9. Al lado del dominio que está pendiente de verificación, haz clic en el {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, después haz clic en **Continue verifying (Continuar verificando)**. ![Botón para continuar verificando](/assets/images/help/organizations/continue-verifying-domain.png) -10. Haz clic en **Verify domain (Verificar dominio)**. ![Botón para verificar dominio](/assets/images/help/organizations/verify-domain-final-button.png) -11. Como alternativa, una vez que la insignia "Verified" (Verificado) es visible en la página de perfil de tu organización, puedes eliminar la entrada de TXT desde el registro de DNS en tu servicio de alojamiento de dominio. ![Insignia Verificado](/assets/images/help/organizations/verified-badge.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md deleted file mode 100644 index 4230a26d97..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Agregar un gerente de facturación a tu organización -intro: 'Un *gerente de facturación* es un usuario que administra los parámetros de facturación de tu organización, como la actualización de la información de pago. Esta es una gran opción si los miembros regulares de tu organización habitualmente no tienen acceso a los recursos de facturación.' -redirect_from: - - /articles/adding-a-billing-manager-to-your-organization - - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization -versions: - free-pro-team: '*' ---- -Los miembros del equipo Propietarios de tu organización pueden permitir que los *gerentes de facturación* proporcionen permisos a las personas. Una vez que una persona acepta la invitación para convertirse en gerente de facturación para tu organización, puede invitar a otras personas para convertirse en gerentes de facturación. - -{% note %} - -**Nota:**Los gerentes de facturación no utilizan licencias pagadas en la suscripción de tu organización. - -{% endnote %} - -### Permisos para los gerentes de facturación - -Los gerentes de facturación pueden: - -- Actualizar o bajar la categoría de la cuenta -- Agregar, actualizar o eliminar métodos de pago -- Ver historial de pagos -- Descargar recibos -- Ver, invitar y eliminar gerentes de facturación - -Además, todos los gerentes de facturación recibirán recibos de facturación por correo electrónico en la fecha de facturación de la organización. - -Los gerentes de facturación**no** pueden: - -- Crear o acceder repositorios en tus organizaciones -- Ver miembros privados de tu organización -- Ser visto en la lista de los miembros de la organización -- Comprar, editar o cancelar suscripciones para aplicaciones de {% data variables.product.prodname_marketplace %} - -{% tip %} - -**Sugerencia:** Si tu organización [requiere que los miembros, gerentes de facturación y colaboradores externos usen autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization), el usuario debe habilitar la autenticación de dos factores antes de que puedan aceptar tu invitación para convertirse en gerentes de facturación para la organización. - -{% endtip %} - -### Invitar a un gerente de facturación - -La persona invitada recibirá una invitación por correo electrónico solicitándole que se convierta en gerente de facturación para tu organización. Una vez que la persona invitada hace clic en el enlace de aceptación en el correo electrónico de la invitación, se agregarán automáticamente a la organización como gerentes de facturación. Si todavía no tienen una cuenta GitHub, deberán iniciar sesión para una cuenta, y se agregarán automáticamente a la organización como gerentes de facturación luego de crear una cuenta. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -5. Junto a Billing managers (Gerentes de facturación), haz clic en **Add a billing manager** (Agregar un gerente de facturación). ![Invitar gerente de facturación](/assets/images/help/billing/settings_billing_managers_list.png) -6. Escribe el nombre de usuario o la dirección de correo electrónico de la persona a la que deseas agregar y haz clic en **Send invitation** (Enviar invitación). ![Página Invitar gerente de facturación](/assets/images/help/billing/billing_manager_invite.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md deleted file mode 100644 index c628cebf08..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Otorgar permisos de "mantenedor del equipo" a un miembro de la organización -intro: 'Un propietario de la organización puede promover a cualquier miembro de la organización a *mantenedor del equipo* de un equipo, otorgándole un subconjunto de privilegios disponibles para los propietarios de la organización.' -redirect_from: - - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/ - - /articles/giving-team-maintainer-permissions-to-an-organization-member - - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.organizations.team_maintainers_can %} - -### Promover un miembro de la organización a mantenedor del equipo - -Antes de promover un miembro de la organización a mantenedor del equipo, la persona ya debe ser miembro del equipo. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_members_tab %} -4. Selecciona la persona o las personas que desees promover a mantenedor del equipo. ![Casilla junto al miembro de la organización](/assets/images/help/teams/team-member-check-box.png) -5. Por encima de la lista de miembros del equipo, utiliza el menú desplegable y haz clic en **Change role...** (Cambiar rol). ![Menú desplegable con opción para cambiar el rol](/assets/images/help/teams/bulk-edit-drop-down.png) -6. Selecciona un rol nuevo y haz clic en **Change role** (Cambiar rol). ![Botones Radio para los roles de Mantenedor o Miembro](/assets/images/help/teams/team-role-modal.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/index.md deleted file mode 100644 index cb00314748..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Administrar el acceso de las personas a tu organización con roles -intro: 'El rol de una persona en tu organización define su nivel de acceso a tu organización, sus configuraciones y tus datos. Puedes convertir a personas en propietarios, miembros o gerentes de facturación para tu organización, o puedes darles permisos de mantenedor del equipo.' -redirect_from: - - /articles/managing-people-s-access-to-your-organization-with-roles - - /articles/managing-peoples-access-to-your-organization-with-roles -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /permission-levels-for-an-organization - - /maintaining-ownership-continuity-for-your-organization - - /giving-team-maintainer-permissions-to-an-organization-member - - /adding-a-billing-manager-to-your-organization - - /removing-a-billing-manager-from-your-organization ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md deleted file mode 100644 index 29980fd4a8..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Mantener la continuidad de propiedad para tu organización -intro: Las organizaciones pueden tener más de un propietario para evitar las intermitencias de propiedad. -redirect_from: - - /articles/changing-a-person-s-role-to-owner - - /articles/changing-a-persons-role-to-owner - - /github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner - - /github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization -permissions: Los propietarios de organizaciones pueden promover a cualquier miembro de una organización a propietario de la misma. -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de mantener la continuidad de propiedad para tu organización - -{% data reusables.organizations.org-ownership-recommendation %} - -Los propietarios de una organización tienen acceso administrativo completo a la misma. {% data reusables.organizations.new-org-permissions-more-info %} - -### Designar un propietario de organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Selecciona la persona o las personas que quisieras promover a propietario. ![Lista de miembros con dos miembros seleccionados](/assets/images/help/teams/list-of-members-selected-bulk.png) -5. Arriba de la lista de miembros, usa el menú desplegable y haz clic en **Change role...** (Cambiar rol). ![Menú desplegable con la opción para eliminar miembros](/assets/images/help/teams/user-bulk-management-options.png) -6. Selecciona un nuevo rol para la persona o las personas, luego haz clic en **Change role** (Cambiar rol). ![Botones de opción con roles de propietario y miembros y botón Change role (Cambiar rol)](/assets/images/help/teams/select-and-confirm-new-role-bulk.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md deleted file mode 100644 index e96b45a5d7..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -title: Niveles de permiso para una organización -intro: 'Después de seleccionar [create an organization (crear una organización)](/articles/creating-a-new-organization-account), deberías dar permisos de propietario a un pequeño grupo de personas que administrarán la cuenta de la organización.' -redirect_from: - - /articles/permission-levels-for-an-organization-early-access-program/ - - /articles/permission-levels-for-an-organization - - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Niveles de permiso para una organización - -Los miembros de la organización pueden tener roles de *propietario*{% if currentVersion == "free-pro-team@latest" %}, *gerente de facturación*,{% endif %} o *miembro*: - -- Los **Propietarios** tienen acceso administrativo completo a tu organización. Este rol debe limitarse a dos personas, por lo mucho, en tu organización. Para obtener más información, consulta la sección "[Mantener la continuidad de la propiedad para tu organización](/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization)". -{% if currentVersion == "free-pro-team@latest" %} -- El acceso como **Gerente de facturación** le permite a una persona administrar las configuraciones de facturación. Para obtener más información, consulta "[Agregar un gerente de facturación a tu organización](/articles/adding-a-billing-manager-to-your-organization)". -{% endif %} -- El acceso como **Miembros** es el rol por defecto para todo el resto. - -{% if currentVersion == "free-pro-team@latest" %} - - -| Acción de organización | Propietarios | Miembros | Gerentes de facturación | -|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------:|:--------:|:----------------------------------:| -| Crear repositorios (consulta "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)" para obtener más detalles) | **X** | **X** | | -| Ver y editar la información de facturación | **X** | | **X** | -| Invitar personas para que se unan a la organización | **X** | | | -| Editar y cancelar invitaciones para unirse a la organización | **X** | | | -| Eliminar miembros de tu organización | **X** | | | -| Reinstalar antiguos miembros a la organización | **X** | | | -| Agregar o eliminar personas de **todos los equipos** | **X** | | | -| Ascender a miembros de la organización a *mantenedores del equipo* | **X** | | | -| Configurar las tareas de revisión de código (consulta la sección "[Administrar una tarea de revisión de código asignada a tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | | | -| Configurar los recordatorios programados (consulta la sección "[Administrar los recordatorios programados para solicitudes de extracción](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)") | **X** | | | -| Agregar colaboradores a **todos los repositorios** | **X** | | | -| Acceder al registro de auditoría de la organización | **X** | | | -| Editar la página de perfil de la organización (consulta "[Acerca del perfil de tu organización](/articles/about-your-organization-s-profile)" para obtener más detalles) | **X** | | | -| Verificar los dominios de la organización (consulta "[Verificar el dominio de tu organización](/articles/verifying-your-organization-s-domain)" para obtener más detalles) | **X** | | | -| Eliminar **todos los equipos** | **X** | | | -| Eliminar la cuenta de la organización, incluidos todos los repositorios | **X** | | | -| Crear equipos (consulta "[Configurar los permisos de creación de equipos en tu organización](/articles/setting-team-creation-permissions-in-your-organization)" para obtener más detalles) | **X** | **X** | | -| [Mover equipos en la jerarquía de una organización](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Crear tableros de la organización (consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" para obtener más detalles) | **X** | **X** | | -| Ver todos los miembros y equipos de la organización | **X** | **X** | | -| @mencionar cualquier equipo visible | **X** | **X** | | -| Poder convertirse en *mantenedor del equipo* | **X** | **X** | | -| Ver información de la organización (consulta "[Ver información de tu organización](/articles/viewing-insights-for-your-organization)" para obtener más detalles) | **X** | **X** | | -| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)" para obtener más detalles) | **X** | **X** | | -| Ver y publicar debates de equipo privados para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)" para obtener más detalles) | **X** | | | -| Editar y eliminar debates de equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)" para obtener más detalles) | **X** | | | -| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **X** | **X** | | -| Inhabilitar debates de equipo para una organización (consulta "[Inhabilitar debates de equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)" para obtener más detalles) | **X** | | |{% if currentVersion == "free-pro-team@latest" %} -| Administrar vistas de la información de las dependencias de la organización (consulta "[Cambiar la visibilidad de la información de las dependencias de tu organización](/articles/changing-the-visibility-of-your-organizations-dependency-insights)" para obtener más detalles) | **X** | | |{% endif %} -| Configurar una imagen de perfil de equipo en **todos los equipos** (consulta "[Configurar la imagen de perfil de tu equipo](/articles/setting-your-team-s-profile-picture)" para obtener más detalles) | **X** | | | -| Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | | -| Administra la configuración de seguridad y de análisis (consulta la sección "[Administrar la configuración de seguridad y de análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" para encontrar más detalles) | **X** | | | -| Habilitar y aplicar el [inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** | | | -| [Administrar el acceso de SAML de un usuario a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** | | | -| Administrar las autoridades de certificado de SSH de una organización (consulta "[Administrar las autoridades de certificado de SSH de tu organización](/articles/managing-your-organizations-ssh-certificate-authorities)" para obtener más detalles) | **X** | | | -| Transferir repositorios | **X** | | | -| Comprar, instalar, administrar la facturación y cancelar aplicaciones {% data variables.product.prodname_marketplace %} | **X** | | | -| Enumerar aplicaciones en {% data variables.product.prodname_marketplace %} | **X** | | | -| Recibe [{% data variables.product.prodname_dependabot_alerts %} sobre las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) para todos los repositorios de una organización | **X** | | | -| Administrar las {% data variables.product.prodname_dependabot_security_updates %} (consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates)") | **X** | | | -| [Administrar la política de bifurcación](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization) | **X** | | | -| [Limitar la actividad en repositorios públicos en una organización](/articles/limiting-interactions-in-your-organization) | **X** | | | -| Extraer (leer), subir (escribir) y clonar (copiar) *todos los repositorios* en la organización | **X** | | | -| Convertir a los miembros de la organización en [colaboradores externos](#outside-collaborators) | **X** | | | -| [Ver las personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository) | **X** | | | -| [Exportar una lista de personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | -| Habilitar la sincronización de equipos (consulta la sección "[Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" para obtener más detalles) | **X** | | | - -{% else %} - - -| Acción de organización | Propietarios | Miembros | -|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------:|:---------------------------------------:| -| Invitar personas para que se unan a la organización | **X** | | -| Editar y cancelar invitaciones para unirse a la organización | **X** | | -| Eliminar miembros de tu organización | **X** | | | -| Reinstalar antiguos miembros a la organización | **X** | | | -| Agregar o eliminar personas de **todos los equipos** | **X** | | -| Ascender a miembros de la organización a *mantenedores del equipo* | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" %} -| Configurar las tareas de revisión de código (consulta la sección "[Administrar una tarea de revisión de código asignada a tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)") | **X** | |{% endif %} -| Agregar colaboradores a **todos los repositorios** | **X** | | -| Acceder al registro de auditoría de la organización | **X** | | -| Editar la página de perfil de la organización (consulta "[Acerca del perfil de tu organización](/articles/about-your-organization-s-profile)" para obtener más detalles) | **X** | | | -| Eliminar **todos los equipos** | **X** | | -| Eliminar la cuenta de la organización, incluidos todos los repositorios | **X** | | -| Crear equipos (consulta "[Configurar los permisos de creación de equipos en tu organización](/articles/setting-team-creation-permissions-in-your-organization)" para obtener más detalles) | **X** | **X** | -| Ver todos los miembros y equipos de la organización | **X** | **X** | -| @mencionar cualquier equipo visible | **X** | **X** | -| Poder convertirse en *mantenedor del equipo* | **X** | **X** | -| Transferir repositorios | **X** | |{% if currentVersion ver_gt "enterprise-server@2.18" %} -| Administrar las autoridades de certificado de SSH de una organización (consulta "[Administrar las autoridades de certificado de SSH de tu organización](/articles/managing-your-organizations-ssh-certificate-authorities)" para obtener más detalles) | **X** | |{% endif %} -| Crear tableros de la organización (consulta "[Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" para obtener más detalles) | **X** | **X** | | -| Ver y publicar debates de equipo públicos para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)" para obtener más detalles) | **X** | **X** | | -| Ver y publicar debates de equipo privados para **todos los equipos** (consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)" para obtener más detalles) | **X** | | | -| Editar y eliminar debates del equipo en **todos los equipos** (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments)" para obtener más detalles) | **X** | | | -| Ocultar comentarios en confirmaciones, solicitudes de extracción y propuestas (consulta "[Administrar comentarios ofensivos](/articles/managing-disruptive-comments/#hiding-a-comment)" para obtener más detalles) | **X** | **X** | **X** | -| Inhabilitar debates de equipo para una organización (consulta "[Inhabilitar debates de equipo para tu organización](/articles/disabling-team-discussions-for-your-organization)" para obtener más detalles) | **X** | | | -| Configurar una imagen de perfil de equipo en **todos los equipos** (consulta "[Configurar la imagen de perfil de tu equipo](/articles/setting-your-team-s-profile-picture)" para obtener más detalles) | **X** | | |{% if currentVersion ver_gt "enterprise-server@2.22" %} -| Disable publication of {% data variables.product.prodname_pages %} sites from repositories in the organization (see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)" for details) | **X** | | |{% endif %} -| [Mover equipos en la jerarquía de una organización](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | | -| Extraer (leer), subir (escribir) y clonar (copiar) *todos los repositorios* en la organización | **X** | | -| Convertir a los miembros de la organización en [colaboradores externos](#outside-collaborators) | **X** | | -| [Ver las personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository) | **X** | | -| [Exportar una lista de personas con acceso a un repositorio de una organización](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |{% if currentVersion ver_gt "enterprise-server@2.19" %} -| Administrar etiquetas predeterminadas (consulta "[Administrar etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | |{% endif %} - -{% endif %} - -### {% data variables.product.prodname_github_app %} administadores - -Por defecto, únicamente los propietarios de la organización pueden administrar las configuraciones de las {% data variables.product.prodname_github_app %}s que le pertenecen a una organización. Para permitir que más usuarios administren las {% data variables.product.prodname_github_app %}s que le pertenecen a una organización, un propietario puede otorgarles permisos de administrador de {% data variables.product.prodname_github_app %}. - -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_app %}s 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)" - -### Colaboradores externos - -Para mantener seguros los datos de tu organización mientras que permites el acceso a los repositorios, puedes agregar *colaboradores externos*. {% data reusables.organizations.outside_collaborators_description %} - -### Leer más - -- "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization)" -- [Acerca de los equipos](/articles/about-teams)" -- [Permisos de tablero de proyecto para una organización](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md deleted file mode 100644 index 97bbe3b22f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Eliminar un gerente de facturación de tu organización -intro: 'Si una persona con el rol de *gerente de facturación* no necesita seguir viendo o modificando la información de facturación de tu organización, puedes eliminar su acceso a la organización.' -redirect_from: - - /articles/removing-a-billing-manager-from-your-organization - - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization -versions: - free-pro-team: '*' ---- -{% warning %} - -**Nota:** {% data reusables.dotcom_billing.org-billing-perms %} - -{% endwarning %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.billing %} -5. En la lista de Gerentes de facturación, al lado del nombre de la persona que quieres eliminar, haz clic en {% octicon "x" aria-label="X symbol" %}. ![Eliminar gerente de facturación](/assets/images/help/billing/settings_billing_managers_remove_manager.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md deleted file mode 100644 index 5a97420812..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML -intro: 'Si administras centralmente las identidades y aplicaciones de tus usuarios con un provedor de identidad (IdP), puedes configurar el inicio de sesión único (SSO) del Lenguaje de Marcado para Confirmaciones de Seguridad (SAML) para proteger los recursos de tu organización en {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/about-identity-and-access-management-with-saml-single-sign-on - - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on -versions: - free-pro-team: '*' ---- -### Acerca de SAML SSO - -{% data reusables.saml.dotcom-saml-explanation %} - -Después de configurar 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. - -Los propietarios de la empresa también pueden requerir SSO de SAML para todas las organizaciones en una 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-account/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". - -{% data reusables.saml.outside-collaborators-exemption %} - -Antes de habilitar el SSO de SAML para tu organización, necesitarás conectar tu IdP a la misma. Para obtener más información, consulta "[Conectar tu proveedor de identidad a tu organización](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)." - -En una organización, el SSO de SAML puede inhabilitarse, habilitarse pero no requerirse, o habilitarse y requerirse. Después de habilitar exitosamente el SSO de SAML para tu organización y que sus miembros se autentiquen exitosamente con tu IdP, puedes requerir la configuración del SSO de SAML. Para obtener más información acerca de requerir el SSO de SAML para tu organización en {% data variables.product.prodname_dotcom %}, consulta la sección "[Requerir el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". - -Los miembros deben autenticarse regularmente con tu IdP y obtener acceso a los recursos de tu organización. Tu IdP especifica la duración de este período de inicio de sesión y, generalmente, es de 24 horas. Este requisito de inicio de sesión periódico limita la duración del acceso y requiere que los usuarios se vuelvan a identificar para continuar. - -Para acceder a los recursos protegidos de tu organización tulizando la API y Git en la línea de comando, los miembros deberán autorizar y autentificarse con un token de acceso personal o llave SSH. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para su uso 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)". - -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](/github/setting-up-and-managing-organizations-and-teams/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-account/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. Para obtener más información sobre los tipos de visibilidad para los repositorios, visita "[Acerca de la visibilidad de los repositorios](/github/creating-cloning-and-archiving-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. - -### Servicios SAML admitidos - -{% data reusables.saml.saml-supported-idps %} - -Algunos IdP admiten acceso de suministro a una organización de {% data variables.product.prodname_dotcom %} a través de SCIM. Para obtener más información, consulta la sección "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". - -### Agregar miembros a una organización usando SAML SSO - -Una vez que activas SAML SSO, hay varias maneras de poder agregar nuevos miembros a tu organización. Los propietarios de la organización pueden invitar a los miembros de forma manual en {% data variables.product.product_name %} o usando la API. Para obtener más información, consulta las secciones "[Invitar usuarios a unirse a tu organización](/articles/inviting-users-to-join-your-organization)" y "[Miembros](/v3/orgs/members/#add-or-update-organization-membership)". - -{% data reusables.organizations.team-synchronization %} - -Para aprovisionar nuevos usuarios sin una invitación de un propietario de la organización, puedes usar la URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, reemplazando _ORGANIZATION_ con el nombre de tu organización. Por ejemplo, puedes configurar tu IdP para que cualquiera con acceso al IdP pueda hacer clic en el tablero del IdP para unirse a tu organización de {% data variables.product.prodname_dotcom %}. - -Si tu IdP admite SCIM, {% data variables.product.prodname_dotcom %} puede invitar automáticamente a los miembros para que se unan a tu organización cuando les otorgas acceso en tu IdP. Si eliminas el acceso de un miembro a tu organización de {% data variables.product.prodname_dotcom %} en tu IdP de SAML, éste se eliminará automáticamente de la organización de{% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". - -{% data reusables.saml.saml-single-logout-not-supported %} - -### Leer más - -- "[Acerca de la autenticación de dos factores y el inicio de sesión único de SAML ](/articles/about-two-factor-authentication-and-saml-single-sign-on)" -- "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/about-scim.md deleted file mode 100644 index 8e449e0e36..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Acerca de SCIM -intro: 'Con Sistema para la administración de identidades entre dominios (SCIM), los administradores pueden automatizar el intercambio de información de identidad del usuario entre los sistemas.' -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/about-scim - - /github/setting-up-and-managing-organizations-and-teams/about-scim -versions: - free-pro-team: '*' ---- -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. - -Estos proveedores de identidad son compatibles con la API de SCIM de {% data variables.product.product_name %} para organizaciones. Para obtener más información, consulta [SCIM](/v3/scim/) en la documentación de {% data variables.product.product_name %} API. -- Azure AD -- Okta -- OneLogin - -{% data reusables.scim.enterprise-account-scim %} Para obtener más información, consulta la sección "[Requerir la configuración de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)". - -### Leer más - -- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" -- "[Conectar tu proveedor de identidad a tu organización](/articles/connecting-your-identity-provider-to-your-organization)" -- "[Activar y probar el inicio de sesión único de SAML para tu organización](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)" -- "[Visualizar y administrar un acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md deleted file mode 100644 index 0fb66f3f48..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Acceder a tu organización si tu proveedor de identidad no está disponible -intro: 'Los administradores de la organización pueden iniciar sesión en {% data variables.product.product_name %} incluso si su proveedor de identidad no está disponible al saltear el inicio de sesión único y usar sus códigos de recuperación.' -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable - - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable -versions: - free-pro-team: '*' ---- -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. Es posible que los hayas guardado en un administrador de contraseñas, como [LastPass](https://lastpass.com/), [1Password](https://1password.com/), o [Keeper](https://keepersecurity.com/). - -{% note %} - -**Nota:** Solo puedes usar los códigos de recuperación una vez y debes usarlos en un orden consecutivo. Los códigos de recuperación garantizan el acceso durante 24 horas. - -{% endnote %} - -1. En la parte inferior del diálogo de inicio de sesión único, haz clic en **Use a recovery code** (Usar un código de recuperación) para saltear el inicio de sesión único. ![Enlace para ingresar tu código de recuperación](/assets/images/help/saml/saml_use_recovery_code.png) -2. En el campo "Recovery Code" (Código de recuperación), escribe tu código de recuperación. ![Código para ingresar tu código de recuperación](/assets/images/help/saml/saml_recovery_code_entry.png) -3. Click **Verify**. ![Botón para verificar tu código de recuperación](/assets/images/help/saml/saml_verify_recovery_codes.png) - -Una vez que has usado un código de verificación, asegúrate de anotar que ya no es válido. No podrás volver a usar el código de recuperación. - -### Leer más - -- [Acerca de la administración de acceso e identidad con SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md deleted file mode 100644 index a85d0e05da..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Cofnigurar SCIM y el inicio de sesión único de SAML con Okta -intro: 'Puedes utilizar el inicio de sesión único (SSO) del Lenguaje de Marcado para Confirmaciones de Seguridad (SAML) y un Sistema para la Administración de Identidad a través de los Dominios (SCIM) con Okta para administrar automáticamente el acceso a tu organización en {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.saml-sso %}' -permissions: Los propietarios de las organizaciones pueden configurar el SSO de SAML y SCIM utilizando Okta para su organización. -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta ---- -### Acerca de SAML y SCIM con Okta - -Puedes controlar el acceso a tu organización de {% data variables.product.prodname_dotcom %} y a otras aplicaciones web desde una interface central si configuras la organización para que utilice el SSO de SAML con Okta, un Proveedor de Identidad (IdP). - -El SSO de SAML controla y asegura el acceso a los recursos organizacionales como los repositorios, informes de problemas y solicitudes de extracción. SCIM agrega automáticamente, administra y elimina el acceso de los miembros a tu organización de {% data variables.product.prodname_dotcom %} cuando haces cambios en Okta. Para obtener más información, consulta la sección "[Acerca de la administración de accesos e identidad con el inicio de sesión único de SAML](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)" y "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". - -Después de que habilites SCIM, las siguientes características de aprovisionamiento estarán disponibles para cualquier usuario al que asignes tu aplicación de {% data variables.product.prodname_ghe_cloud %} en Okta. - -| Característica | Descripción | -| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Subir Usuarios Nuevos | Cuando creas un usuario nuevo en Okta, éste recibirá un correo electrónico para unirse a tu organización de {% data variables.product.prodname_dotcom %}. | -| Subir Desactivaciones de Usuarios | Cuando desactivas un usuario en Okta, Okta lo eliminará de tu organización de {% data variables.product.prodname_dotcom %}. | -| Subir Actualizaciones de Perfil | Cuando actualizas el perfil de un usuario en Okta, Okta actualizará los metadatos de su membrecía en tu organización de {% data variables.product.prodname_dotcom %}. | -| Reactivar Usuarios | Cuando reactivas un usuario en Okta, Okta le enviará una invitación por correo electrónico para que vuelva a unirse a tu organización de {% data variables.product.prodname_dotcom %}. | - -### Prerrequisitos - -{% data reusables.saml.use-classic-ui %} - -### Agregar la aplicación {% data variables.product.prodname_ghe_cloud %} en Okta - -{% data reusables.saml.okta-dashboard-click-applications %} -{% data reusables.saml.add-okta-application %} -{% data reusables.saml.search-ghec-okta %} -4. Da clic en **Agregar** a la derecha de "Github Enterprise Cloud - Organization". ![Dar clic en "Agregar" para la aplicación de {% data variables.product.prodname_ghe_cloud %}](/assets/images/help/saml/okta-add-ghec-application.png) - -5. En el campo **Organizaciòn de GitHub**, teclea el nombre de tu organizaciòn de {% data variables.product.prodname_dotcom %}. Por ejemplo, si la URL de de tu organizaciòn es https://github.com/octo-org, el nombre de organizaciòn serìa `octo-org`. ![Teclear el nombre de organización de GitHub](/assets/images/help/saml/okta-github-organization-name.png) - -6. Haz clic en **Done** (listo). - -### Habilitar y probar el SSO de SAML - -{% data reusables.saml.okta-dashboard-click-applications %} -{% data reusables.saml.okta-applications-click-ghec-application-label %} -{% data reusables.saml.assign-yourself-to-okta %} -{% data reusables.saml.okta-sign-on-tab %} -{% data reusables.saml.okta-view-setup-instructions %} -6. Habilita y prueba el SSO de SAML en {% data variables.product.prodname_dotcom %} utilizando la URL de registro, URL del emisor, y certificados pùblicos de la guìa "Còmo configurar SAML 2.0". Para obtener mas información, consulta la sección "[Habilitar y probar el inicio de sesión único de SAML para tu organización](/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization)". - -### Configurar el aprovisionamiento de acceso con SCIM en Okta - -{% data reusables.saml.okta-dashboard-click-applications %} -{% data reusables.saml.okta-applications-click-ghec-application-label %} -{% data reusables.saml.okta-provisioning-tab %} -{% data reusables.saml.okta-configure-api-integration %} -{% data reusables.saml.okta-enable-api-integration %} - - -6. Da clic en **Autenticar con Github Enterprise Cloud - Ortanizaction**. ![Botón "Autenticar con GitHub Enterprise Cloud - Organization" para la aplicación de Okta](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png) - -7. A la derecha del nombre de tu organizaciòn, da clic en **Otorgar**. ![Botón "Otorgar" para autorizar la integración de SCIM de Okta para acceder a la organización](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) - - {% note %} - - **Nota**: si no ves tu organización en la lista, dirígete a `https://github.com/orgs/ORGANIZATION-NAME/sso` en tu buscador y autentícate con ella a través del SSO de SAML utilizando tu cuenta de administrador en el IdP. Por ejemplo, si tu nombre de organización es `octo-org`, La URL sería `https://github.com/orgs/octo-org/sso`. 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/about-authentication-with-saml-single-sign-on)". - - {% endnote %} -1. Da clic en **Autorizar OktaOAN**. ![Botón "Autorizar a OktaOAN" para autorizar la integración de SCIM de Okta para acceder a la organización](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png) -{% data reusables.saml.okta-save-provisioning %} -{% data reusables.saml.okta-edit-provisioning %} - -### Leer más - -- "[Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta](/github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)" -- "[Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)" -- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) en la documentación de Okta -- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) en la documentación de Okta diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md deleted file mode 100644 index 6602cff7c1..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Conectar tu proveedor de identidad con tu organización -intro: 'Para usar el inicio de sesión único de SAML y SCIM, debes conectar tu proveedor de identidad con tu organización {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/connecting-your-identity-provider-to-your-organization - - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization -versions: - free-pro-team: '*' ---- -Antes de [habilitar SAML SSO](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) en tu organización {% data variables.product.product_name %}, deberás conectar tu proveedor de identidad (IdP) con tu organización. - -Puedes buscar los detalles de la implementación de SAML y SCIM para tu IdP en su documentación: -- 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/) -- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) y [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e) -- PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector) -- Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home) - -{% note %} - -**Nota:** Los proveedores de identidad que soportan {% data variables.product.product_name %} SCIM son Azure AD, Okta y OneLogin. Para obtener más información acerca de SCIM, consulta "[Acerca de SCIM](/articles/about-scim)". - -{% endnote %} - -### Leer más - -- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" -- "[Implementar el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md deleted file mode 100644 index 5002e3255f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Descargar los códigos de recuperación de inicio de sesión único SAML de tu organización -intro: 'Los administradores de la organización deben descargar los códigos de recuperación de inicio de sesión único SAML de la organización para asegurarse de poder acceder a {% data variables.product.product_name %} aun cuando el proveedor de identidad no se encuentre disponible para la organización.' -redirect_from: - - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes - - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes - - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes -product: '{% data reusables.gated-features.saml-sso %}' -versions: - free-pro-team: '*' ---- -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/), [1Password](https://1password.com/), o [Keeper](https://keepersecurity.com/). - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -5. En "Inicio de sesión único SAML", en la nota acerca de los códigos de recuperación, haz clic en **Guardar tus códigos de recuperación**. ![Enlace para ver y guardar tus códigos de recuperación](/assets/images/help/saml/saml_recovery_codes.png) -6. Guarda tus códigos de recuperación haciendo clic en **Download** (Descargar), **Print** (Imprimir) o **Copy** (Copiar). ![Botones para descargar, imprimir o copiar tus códigos de recuperación](/assets/images/help/saml/saml_recovery_code_options.png) - - {% note %} - - **Nota:** Tus códigos de recuperación te ayudarán a acceder nuevamente a {% data variables.product.product_name %} si tu IdP no está disponible. Si generas nuevos códigos de recuperación, los códigos de recuperación que se muestran en la página "Códigos de recuperación de inicio de sesión único" se actualizarán automáticamente. - - {% endnote %} - -7. Una vez que usas un código de recuperación para obtener acceso nuevamente a {% data variables.product.product_name %}, no puedes volver a usarlo. El acceso a {% data variables.product.product_name %} solo estará disponible durante 24 horas antes de que se te solicite que inicies sesión usando inicio de sesión único. - -### Leer más - -- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" -- "[Acceder a tu organización cuando tu proveedor de identidad no está disponible](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md deleted file mode 100644 index 7e2d4f6302..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Habilitar y probar el inicio de sesión único SAML para tu organización -intro: Los administradores y los propietarios de la organización pueden habilitar el inicio de sesión único SAML para agregar una capa más de seguridad a su organización. -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization -versions: - free-pro-team: '*' ---- -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. - -Si habilitas pero no exiges SAML SSO, los miembros de la organización que elijan no usar SAML SSO pueden seguir siendo miembros de esta. Para obtener más información acerca de la exigencia de SAML SSO, consulta "[Exigir inicio de sesión único SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". - -{% data reusables.saml.outside-collaborators-exemption %} - -Antes de exigir SAML SSO en tu organización, verifica que ya tengas configurado tu proveedor de identidad (IP). 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)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -5. En "inicio de sesión único SAML", selecciona **Habilitar autenticación SAML**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/saml/saml_enable.png) - - {% note %} - - **Nota:** Luego de habilitar SAML SSO, puedes descargar tus códigos de recuperación de inicio de sesión único para poder acceder a tu organización aun cuando tu IdP no se encuentre disponible. Para obtener más información, consulta "[Descargar los códigos de recuperación de inicio de sesión único SAML de tu organización](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)". - - {% endnote %} - -6. En el campo "URL de inicio de sesión único", escribe el extremo del 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.png) -7. También puedes escribir tu nombre de emisor SAML en el campo "Emisor". Esto verifica 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", copia un certificado para verificar las respuestas SAML. ![Campo para el certificado público de tu proveedor de identidad](/assets/images/help/saml/saml_public_certificate.png) -9. Haz clic en {% octicon "pencil" aria-label="The edit icon" %} y luego en los menús desplegables de Método de firma y Método de resumen y elige el algoritmo de hash que usa tu emisor SAML para verificar la integridad de las solicitudes. ![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) -10. Antes de habilitar SAML SSO para tu organización, haz clic en **Probar la configuración de SAML** para asegurarte de que la información que has ingresado sea correcta. ![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) - - {% tip %} - - **Sugerencia:**{% data reusables.saml.testing-saml-sso %} - - {% endtip %} -11. Para implementar SAML SSO y eliminar a todos los miembros de la organización que no se hayan autenticado mediante tu IdP, selecciona **Require SAML SSO authentication for all members of the _organization name_ organization**.** (Requerir autenticación SAML SSO a todos los miembros de la organización [nombre de la organización]). Para obtener más información acerca de la exigencia de SAML SSO, consulta "[Exigir inicio de sesión único SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". ![Casilla de verificación para requerir SAML SSO para tu organización ](/assets/images/help/saml/saml_require_saml_sso.png)

    -12 -Haz clic en **Save (Guardar)**. ![Botón para guardar la configuración de SAML SSO](/assets/images/help/saml/saml_save.png) - -### Leer más - -- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md deleted file mode 100644 index ba3bad86f5..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Hacer cumplir el inicio de sesión único de SAML para tu organización -intro: Los propietarios y los administradores de la organización pueden hacer cumplir 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. -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/enforcing-saml-single-sign-on-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization -versions: - free-pro-team: '*' ---- -Si haces cumplir el inicio de sesión único de SAML en tu organización, todo miembro que no se haya autenticado mediante tu proveedor de identidad de SAML (IdP), incluidos los administradores, será eliminado de la organización y recibirá un correo electrónico en el que se le notificará la eliminación. También se eliminarán los bots y las cuentas de servicio que no tengan identidades externas configuradas en el IdP de tu organización. Para obtener más información acerca de los bots y las cuentas de servicio, consulta "[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)". Puedes restaurar los miembros de la organización una vez que realizas el inicio de sesión único sin problemas. - -Si tu organización le pertenece a una cuenta de empresa, al habilitar SAML para la cuenta de empresa, se reemplazará la configuración SAML al nivel de organización. Para obtener más información, consulta "[Requerir configuraciónes de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account)". - -{% tip %} - -**Sugerencia:**{% data reusables.saml.testing-saml-sso %} - -{% endtip %} - -1. Habilita y prueba el inicio de sesión único de SAML para tu organización. Para obtener más información acerca de este proceso, 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)". -2. Luego de seleccionar **Requerir autenticación del inicio de sesión único de SAML para todos los miembros de la organización SAML SSO Org**, se mostrarán los miembros de la organización que no se hayan autenticado mediante tu IdP. Si haces cumplir el inicio de sesión único de SAML, estos miembros se eliminarán de la organización. -3. Haz clic en **Hacer cumplir el inicio de sesión único de SAML** para hacer cumplir el inicio de sesión único de SAML y eliminar a los miembros de la organización que figuren en la lista. - -### Leer más - -- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/index.md deleted file mode 100644 index 2a1fae910b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Administrar el inicio de sesión único de SAML para tu organización -intro: Los administradores de la organización pueden administrar las identidades y el acceso a la organización de los miembros con el inicio de sesión único (SSO) de SAML. -redirect_from: - - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on/ - - /articles/managing-saml-single-sign-on-for-your-organization -versions: - free-pro-team: '*' -children: - - /about-identity-and-access-management-with-saml-single-sign-on - - /about-scim - - /connecting-your-identity-provider-to-your-organization - - /configuring-saml-single-sign-on-and-scim-using-okta - - /enabling-and-testing-saml-single-sign-on-for-your-organization - - /preparing-to-enforce-saml-single-sign-on-in-your-organization - - /enforcing-saml-single-sign-on-for-your-organization - - /downloading-your-organizations-saml-single-sign-on-recovery-codes - - /managing-team-synchronization-for-your-organization - - /accessing-your-organization-if-your-identity-provider-is-unavailable ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md deleted file mode 100644 index d410bc6761..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Administrar la sincronización de equipos para tu organización -intro: 'Puedes habilitar e inhabilitar la sincronización entre tu Proveedor de Identidad (IdP) y tu organización en {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.team-synchronization %}' -redirect_from: - - /articles/synchronizing-teams-between-your-identity-provider-and-github - - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github - - /github/articles/synchronizing-teams-between-okta-and-github - - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization -permissions: Los propietarios de las organizaciones pueden administrar la sincronización de equipos a una organización. -miniTocMaxHeadingLevel: 4 -versions: - free-pro-team: '*' ---- -{% data reusables.gated-features.okta-team-sync %} - -### Acerca de la sincronización de equipo - -Puedes habilitar la sincronización de equipos entre tu IdP y {% data variables.product.product_name %} para permitir a los propietarios de la organización y a los mantenedores de equipo conectar equipos en tu organización con grupos de IdP. - -{% data reusables.identity-and-permissions.about-team-sync %} - -{% data reusables.identity-and-permissions.supported-idps-team-sync %} - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -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 "[Requerir configuraciónes de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account)". - -### Habilitar la sincronización de equipo - -Los pasos para habilitar la sincronización de equipos dependen del IdP que quieras utilizar. Existen prerrequisitos aplicables a cada IdP para habilitar la sincronización de equipos. Cada IdP individual tiene prerrequisitos adicionales. - -#### Prerrequisitos - -{% data reusables.identity-and-permissions.team-sync-required-permissions %} - -Debes habilitar el inicio de sesión único de SAML para tu organización y tu IdP compatible. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". - -Debes autenticarte con tu organización 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)". - -#### Habilitar la sincronización de equipos para Azure AD - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -6. Revisa la información de locatario del proveedor de identidad que deseas conectar a tu organización, después haz clic en **Approve (Aprobar)**. ![Solicitud pendiente para habilitar la sincronización de equipo a un locatario IdP específico con la opción de aprobar o cancelar la solicitud](/assets/images/help/teams/approve-team-synchronization.png) - -#### Habilitar la sincronización de equipos para Okta - -{% data reusables.identity-and-permissions.team-sync-okta-requirements %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-okta %} -7. Debajo del nombre de tu organización, teclea un token SSWS válido y la URL de tu instancia de Okta. ![Formulario organizacional de Okta para habilitar la sincronización de equipos](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png) -6. Revisa la información de locatario del proveedor de identidad que deseas conectar a tu organización, después da clic en **Crear**. ![Botón de crear en habilitar la sincronización de equipos](/assets/images/help/teams/confirm-team-synchronization-okta.png) - -### Inhabilitar la sincronización de equipo - -{% data reusables.identity-and-permissions.team-sync-disable %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.security %} -5. Dentro de "Team synchronization" (Sincronización de equipo), haz clic en **Disable team synchronization (Inhabilitar la sincronización de equipo)**. ![Inhabilita la sincronización de equipo](/assets/images/help/teams/disable-team-synchronization.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md deleted file mode 100644 index 0812a82b0c..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Prepararse para aplicar el inicio de sesión único SAML en tu organización -intro: 'Antes de aplicar el inicio de sesión único de SAML en tu organización, deberías verificar la membresía de tu organización y configurar las configuraciones de conexión para tu proveedor de identidad.' -product: '{% data reusables.gated-features.saml-sso %}' -redirect_from: - - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization -versions: - free-pro-team: '*' ---- -Cuando [aplicas el inicio de sesión único de SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) en tu organización, los miembros que no se han autenticado por medio de tu proveedor de identidad (IdP) serán eliminados de la organización y recibirán un correo electrónico informándoles acerca de la eliminación. - -Antes de aplicar un SSO de SAML en tu organización, deberías: - -- [Agregar](/articles/inviting-users-to-join-your-organization) o [eliminar](/articles/removing-a-member-from-your-organization) miembros de tu organización si es necesario. -- Si no lo has hecho, conectar tu IdP a tu organización. Para obtener más información, consulta "[Conectar tu proveedor de identidad a tu organización](/articles/connecting-your-identity-provider-to-your-organization)." -- Asegurar que los miembros de tu organización se hayan registrado y hayan vinculado sus cuentas con tu IdP. - -{% data reusables.saml.outside-collaborators-exemption %} - -### Leer más - -- "[Acerca de la administración de acceso e identidad con el inicio de sesión único de SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md deleted file mode 100644 index 1298acb7e9..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Convertir un equipo de administradores a los permisos de organización mejorados -intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. Los miembros de los equipos de administradores heredados conservan de forma automática la capacidad para crear repositorios hasta que esos equipos sean migrados al modelo mejorado de permisos de la organización.' -redirect_from: - - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/ - - /articles/converting-an-admin-team-to-improved-organization-permissions - - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Puedes eliminar la capacidad de los miembros del equipo de administración heredado para crear repositorios al crear un nuevo equipo para esos miembros, asegurándote de que el equipo tenga el acceso necesario a los repositorios de la organización, y eliminando el equipo de administración heredado. - -Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)". - -{% warning %} - -**Advertencias:** -- Si hay miembros de su equipo de administración heredados que no son miembros de otros equipos, la eliminación del equipo eliminará a esos miembros de la organización. Antes de eliminar el equipo, asegúrate de que los miembros ya sean miembros directos de la organización, o que tengan acceso de colaborador a los repositorios necesarios. -- Para evitar la pérdida de bifurcaciones privadas realizadas por los miembros del equipo de administradores heredado, debes seguir los pasos 1-3 a continuación antes de eliminar el equipo de administradores heredado. -- Dado que "admin" es un término para los miembros de la organización con [acceso específico a determinados repositorios](/articles/repository-permission-levels-for-an-organization) en la organización, te recomendamos evitar ese término en cualquier nombre de equipo sobre el que puedas decidir. - -{% endwarning %} - -1. [Crear un equipo nuevo](/articles/creating-a-team). -2. [Agregar cada uno de los miembros](/articles/adding-organization-members-to-a-team) de tu equipo de administradores heredado al nuevo equipo. -3. [Brindar al equipo nuevo el acceso equivalente](/articles/managing-team-access-to-an-organization-repository) a cada uno de los repositorios a los que podía acceder el equipo heredado. -4. [Eliminar el equipo de administradores heredado](/articles/deleting-a-team). diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md deleted file mode 100644 index 031f0a6b2a..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Convertir un equipo de Propietarios a los permisos de organización mejorados -intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. El "Propietario" ahora tiene un rol administrativo otorgado a los miembros individuales de tu organización. Los miembros de tu equipo de Propietarios heredado automáticamente reciben los privilegios del propietario.' -redirect_from: - - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program/ - - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions/ - - /articles/converting-an-owners-team-to-improved-organization-permissions - - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Tienes algunas opciones para convertir tu equipo de Propietarios heredado: - -- Coloca un nuevo nombre al equipo que denote que los miembros tienen un estado especial en la organización. -- Elimina el equipo luego de asegurarte de que todos los miembros han sido agregados a los equipos que garantizan las acciones necesarias a los repositorios de la organización. - -### Proporcionar al equipo de Propietarios un nuevo nombre - -{% tip %} - - **Nota:** Dado que "admin" es un término para los miembros de la organización con [acceso específico a determinados repositorios](/articles/repository-permission-levels-for-an-organization) en la organización, te recomendamos evitar ese término en cualquier nombre de equipo sobre el que puedas decidir. - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.owners-team %} -{% data reusables.organizations.convert-owners-team-confirm %} -5. En el campo de nombre del equipo, escoge un nuevo nombre para el equipo Propietarios. Por ejemplo: - - Si muy pocos miembros de tu organización fuesen miembros del equipo Propietarios, puedes designarlo como equipo "Central". - - Si todos los miembros de tu organización fuesen miembros del equipo Propietarios de manera que puedan [@mencionar equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), puedes designar al equipo como "Empleados". ![El campo de nombre del equipo, con el equipo Propietarios con el nuevo nombre Central](/assets/images/help/teams/owners-team-new-name.png) -6. Debajo de la descripción del equipo, haz clic en **Save and continue** (Guardar y continuar). ![El botón para guardar y continuar](/assets/images/help/teams/owners-team-save-and-continue.png) -7. Opcionalmente, [puedes hacer que el equipo sea *público*](/articles/changing-team-visibility). - -### Eliminar el equipo de Propietarios heredado - -{% warning %} - -**Advertencia**: Si hay miembros del equipo de Propietarios heredado que no son miembros de otros equipos, la eliminación del equipo eliminará a esos miembros de la organización. Antes de eliminar el equipo, asegúrate de que los miembros ya sean miembros directos de la organización, o que tengan acceso de colaborador a los repositorios necesarios. - -{% endwarning %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.owners-team %} -{% data reusables.organizations.convert-owners-team-confirm %} -5. En la parte inferior de la página, revisa la advertencia y haz clic en **Delete the Owners team** (Eliminar el equipo de Propietarios). ![Enlace para eliminar el equipo de Propietarios](/assets/images/help/teams/owners-team-delete.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/index.md deleted file mode 100644 index c7896e0286..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Migrar a permisos de organización mejorados -intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización incluye los permisos de la organización mejorados por defecto. Es posible que las organizaciones creadas antes de septiembre de 2015 necesiten migrar a los antiguos equipos de administradores para el modelo mejorado de permisos de la organización.' -redirect_from: - - /articles/improved-organization-permissions/ - - /articles/github-direct-organization-membership-pre-release-guide/ - - /articles/migrating-your-organization-to-improved-organization-permissions/ - - /articles/migrating-to-improved-organization-permissions -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /converting-an-owners-team-to-improved-organization-permissions - - /converting-an-admin-team-to-improved-organization-permissions - - /migrating-admin-teams-to-improved-organization-permissions ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md deleted file mode 100644 index c5c939e13f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Migrar los equipos de administradores a permisos de organización mejorados -intro: 'Si tu organización fue creada después de septiembre de 2015, tu organización ha mejorado los permisos de la organización por defecto. Las organizaciones creadas antes de septiembre de 2015 pueden necesitar migrar a los antiguos equipos de propietarios y administradores al modelo mejorado de permisos. Los miembros de los equipos de administradores heredados conservan de forma automática la capacidad para crear repositorios hasta que esos equipos sean migrados al modelo mejorado de permisos de la organización.' -redirect_from: - - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions/ - - /articles/migrating-admin-teams-to-improved-organization-permissions - - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Por defecto, todos los miembros de la organización pueden crear repositorios. Si restringes los [permisos de creación de repositorios](/articles/restricting-repository-creation-in-your-organization) a los propietarios de la organización y tu organización fue creada dentro de la estructura heredada de permisos de organización, los miembros de los equipos de administración heredados seguirán teniendo la capacidad de crear repositorios. - -Los equipos de administración heredados son equipos que fueron creados con el nivel de permiso de administración dentro de la estructura heredada de permisos de organización. Los miembros de estos equipos pudieron crear repositorios para la organización, y hemos conservado esta capacidad en la estructura mejorada de permisos de la organización. - -Puedes eliminar esta capacidad al migrar tus equipos de administradores heredados a los permisos mejorados de la organización. - -Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". - -{% warning %} - -**Advertencia:** si tu organización ha inhabilitado [los permisos de creación de repositorio](/articles/restricting-repository-creation-in-your-organization) para todos los miembros, algunos miembros de los equipos de administradores heredados pueden perder los permisos de creación de repositorio. Si tu organización ha habilitado la creación de repositorio de miembro, migrar los equipos de administradores heredados a los permisos mejorados de la organización no afectará la capacidad de los miembros del equipo de crear repositorios. - -{% endwarning %} - -### Migrar todos tus equipos de administradores heredados de tu organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.teams_sidebar %} -1. Revisa tus equipos de administradores heredados de la organización, después haz clic en **Migrate all teams (Migrar todos los equipos)**. ![Botón Migrar todos los equipos](/assets/images/help/teams/migrate-all-legacy-admin-teams.png) -1. Lee la información sobre los posibles cambios en permisos para los miembros de estos equipos, después haz clic en **Migrate all teams (Migrar todos los equipos).** ![Botón Confirmar migración](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png) - -### Migrar un equipo de administradores único - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -1. En la casilla de descripción de equipo, haz clic en **Migrate team (Migrar equipo)**. ![Botón Migrar equipo](/assets/images/help/teams/migrate-a-legacy-admin-team.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/about-teams.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/about-teams.md deleted file mode 100644 index 7c57795cd1..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/about-teams.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Acerca de los equipos -intro: Los equipos son grupos de miembros de una organización que reflejan la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. -redirect_from: - - /articles/about-teams - - /github/setting-up-and-managing-organizations-and-teams/about-teams -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -![Listado de equipos en una organización](/assets/images/help/teams/org-list-of-teams.png) - -Los propietarios de la organización y los mantenedores del equipo le pueden otorgar a los equipos acceso de escritura, de lectura o de administrador a los repositorios de la organización. Los miembros de la organización pueden enviar una notificación a todo un equipo al mencionar el nombre del equipo. Los miembros de la organización también pueden enviar una notificación a todo un equipo al solicitar una revisión de ese equipo. Los miembros de la organización pueden solicitar revisiones de equipos específicos con acceso de lectura al repositorio donde la solicitud de extracción esté abierta. Los equipos pueden ser designados como propietarios de ciertos tipos o áreas de código en un archivo CODEOWNERS. - -Para obtener más información, consulta: -- "[Administrar el acceso del equipo al repositorio de una organización](/articles/managing-team-access-to-an-organization-repository)" -- "[Mencionar personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" -- "[Acerca de los propietarios del código](/articles/about-code-owners/)" - -![Imagen de la mención a un equipo](/assets/images/help/teams/team-mention.png) - -{% if currentVersion != "free-pro-team@latest" %} - -También puedes usar la sincronización LDAP para sincronizar los roles del equipo y los miembros del equipo de {% data variables.product.product_location_enterprise %} con tus grupos de LDAP establecidos. Esto te permite establecer un control de acceso para usuarios basado en roles desde tu servidor LDAP, en lugar de hacerlo de forma manual dentro de {% data variables.product.product_location_enterprise %}. Para obtener más información, consulta "[Activar sincronización LDAP](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap#enabling-ldap-sync)". - -{% endif %} - -{% data reusables.organizations.team-synchronization %} - -### Visibilidad del equipo - -{% data reusables.organizations.types-of-team-visibility %} - -### Paginas del equipo - -Cada equipo tiene su propia página dentro de una organización. En la página de un equipo, puedes ver los miembros del equipo, los equipos hijo y los repositorios del equipo. Los propietarios de la organización y los mantenedores del equipo pueden acceder a los parámetros del equipo y actualizar la foto de perfil y la descripción del equipo desde la página del equipo. - -Los miembros de la organización pueden crear y participar en debates con el equipo. Para obtener más información, consulta [Acerca de los debates del equipo](/articles/about-team-discussions)". - -![Página del equipo que enumera los miembros del equipo y los debates](/assets/images/help/organizations/team-page-discussions-tab.png) - -### Equipos anidados - -Puedes reflejar la jerarquía de tu grupo o empresa dentro de tu organización de {% data variables.product.product_name %} con varios niveles de equipos anidados. Un equipo padre puede tener varios equipos hijo, mientras que cada equipo hijo solo tiene un equipo padre. No puedes anidar equipos secretos. - -Los equipos hijo heredan los permisos de acceso del padre, lo que simplifica la administración de permisos para los grupos grandes. Los miembros de los equipos hijo también reciben notificaciones cuando se hace una @mención al equipo padre, simplificando la comunicación con varios grupos de personas. - -Por ejemplo, si la estructura de tu equipo es Empleados > Ingeniería > Ingeniería de aplicación> Identidad, otorgar acceso de escritura a Ingeniería en un repositorio implicará que también se podrá acceder a Ingeniería de aplicación e Identidad. Si haces una @mención al equipo de Identidad o a cualquier equipo de la parte inferior de la jerarquía de la organización, son los únicos que recibirán una notificación. - -![Página de los equipos con un equipo padre y equipos hijo](/assets/images/help/teams/nested-teams-eng-example.png) - -Para comprender fácilmente quién comparte las menciones y los permisos de un equipo padre, puedes ver todos los miembros de los equipos hijo de un equipo padre en la pestaña Miembros de la página del equipo padre. Los miembros de un equipo hijo no son miembros directos del equipo padre. - -![Página del equipo padre con todos los miembros de los equipos hijo](/assets/images/help/teams/team-and-subteam-members.png) - -Puedes elegir un padre cuando creas el equipo o puedes mover un equipo más tarde en la jerarquía de tu organización. Para obtener más información, consulta [Mover un equipo dentro de la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)". - -{% if currentVersion != "free-pro-team@latest" %} - -{% data reusables.enterprise_user_management.ldap-sync-nested-teams %} - -{% endif %} - -### Prepararse para anidar equipos en tu organización - -Si tu organización ya tiene equipos existentes, deberías auditar los permisos de acceso a los repositorios de cada equipo antes de anidar equipos por arriba o por debajo del mismo. También deberías considerar la nueva estructura que te gustaría implementar para tu organización. - -En la parte superior de la jerarquía del equipo, deberías otorgar permisos de acceso a los repositorios de los equipos padre que son seguros para cada miembro del equipo padre y sus equipos hijo. A medida que te mueves hacia la parte inferior de la jerarquía, puedes otorgar a los equipos hijo un acceso adicional, más pormenorizado para los repositorios más confidenciales. - -1. Eliminar todos los miembros de los equipos existentes. -2. Auditar y ajustar los permisos de acceso a los repositorios de cada equipo y darle a cada equipo un padre. -3. Crear todos los equipos nuevos que quieras, elegir un padre para cada equipo nuevo y otorgarles acceso a los repositorios. -4. Agregar las personas directamente a los equipos. - -### Leer más - -- "[Crear un equipo](/articles/creating-a-team)" -- "[Agregar miembros de la organización a un equipo](/articles/adding-organization-members-to-a-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/adding-organization-members-to-a-team.md deleted file mode 100644 index c5ca76ceea..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/adding-organization-members-to-a-team.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Adding organization members to a team -intro: 'People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also {% if currentVersion == "free-pro-team@latest" %}invite non-members to join{% else %}add non-members to{% endif %} a team and the organization.' -redirect_from: - - /articles/adding-organization-members-to-a-team-early-access-program/ - - /articles/adding-organization-members-to-a-team - - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.organizations.team-synchronization %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_members_tab %} -6. Above the list of team members, click **Add a member**. -![Add member button](/assets/images/help/teams/add-member-button.png) -{% data reusables.organizations.invite_to_team %} -{% data reusables.organizations.review-team-repository-access %} - -{% if currentVersion == "free-pro-team@latest" %}{% data reusables.organizations.cancel_org_invite %}{% endif %} - -### Further reading - -- "[About teams](/articles/about-teams)" -- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/changing-team-visibility.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/changing-team-visibility.md deleted file mode 100644 index 366df3a84f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/changing-team-visibility.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Cambiar la visibilidad del equipo -intro: Los mantenedores del equipo y los propietarios de la organización pueden determinar si un equipo es *visible* o *secreto*. -redirect_from: - - /articles/changing-team-visibility - - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.organizations.types-of-team-visibility %} - -{% tip %} - -**Sugerencia:** Si un equipo tiene [equipos padres o hijos](/articles/about-teams), no puedes convertirlo en un equipo secreto. - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.teams %} -3. Selecciona el equipo o los equipos cuya visibilidad deseas cambiar. ![Lista de equipos con dos equipos seleccionados](/assets/images/help/teams/list-of-teams-selected.png) -4. Arriba de la lista de equipos, usa el menú desplegable y haz clic en **Change visibilidad** (Cambiar visibilidad). ![Menú desplegable con opción para cambiar la visibilidad del equipo](/assets/images/help/teams/team-bulk-management-options.png) -5. Elige si deseas hacer que el equipo o los equipos sean visibles o secretos, luego haz clic en **Change visibilidad** (Cambiar visibilidad). ![Botones de opción para hacer que un equipo sea visible o secreto y botón Change visibility (Cambiar visibilidad)](/assets/images/help/teams/select-and-confirm-new-visibility.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/creating-a-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/creating-a-team.md deleted file mode 100644 index a84e077000..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/creating-a-team.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Crear un equipo -intro: Puedes crear equipos independientes o anidados para administrar los permisos del repositorio y las menciones de grupos de personas. -redirect_from: - - /articles/creating-a-team-early-access-program/ - - /articles/creating-a-team - - /github/setting-up-and-managing-organizations-and-teams/creating-a-team -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Solo los propietarios y mantenedores de la organización en un equipo padre pueden crear un nuevo equipo hijo debajo del padre. Los propietarios también pueden restringir los permisos de creación para todos los equipos en una organización. 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)." - -{% data reusables.organizations.team-synchronization %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.new_team %} -{% data reusables.organizations.team_name %} -{% data reusables.organizations.team_description %} -{% data reusables.organizations.create-team-choose-parent %} -{% if currentVersion == "free-pro-team@latest" %} -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](/github/setting-up-and-managing-organizations-and-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). - -### Leer más - -- [Acerca de los equipos](/articles/about-teams)" -- "[Cambiar la visibilidad del equipo](/articles/changing-team-visibility)" -- [Mover un equipo dentro de la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/deleting-a-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/deleting-a-team.md deleted file mode 100644 index 18cf2744ed..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/deleting-a-team.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Eliminar un equipo -intro: Los propietarios de la organización pueden eliminar equipos en cualquier momento desde la página de configuración del equipo. -redirect_from: - - /articles/deleting-a-team - - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% tip %} - -**Sugerencia:** Solo los propietarios de la organización pueden eliminar equipos padres. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.teams %} -4. Selecciona los equipos que deseas eliminar. ![Lista de equipos con dos equipos seleccionados](/assets/images/help/teams/list-of-teams-selected.png) -5. Sobre la lista de equipos, usa el menú desplegable y haz clic en **Eliminar**. ![Menú desplegable con opción para cambiar la visibilidad del equipo](/assets/images/help/teams/team-bulk-management-options.png) -6. Revisa los equipos que se eliminarán y luego haz clic en **Comprendo. Eliminar estos equipos**. ![Lista de equipos que se eliminarán y botón Eliminar equipos](/assets/images/help/teams/confirm-delete-teams-bulk.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md deleted file mode 100644 index f88425af29..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Inhabilitar los debates de equipo para tu organización -intro: Los propietarios de la organización pueden optar por habilitar o inhabilitar los debates de equipo en toda la organización. -redirect_from: - - /articles/disabling-team-discussions-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.organizations.team-discussions-default %}Para obtener más información acerca de los debates de equipo, consulta "[Acerca de los debates de equipo](/articles/about-team-discussions)". - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.teams_sidebar %} -5. En "Debates de equipo", quita la marca de selección de **Habilitar debates de equipo para esta organización**. ![Casilla de verificación para inhabilitar debates de equipo para una organización](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png) -6. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/index.md deleted file mode 100644 index 9fc5b4c342..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/index.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Organizar miembros en un equipo -intro: Puedes agrupar miembros de la organización en equipos que reflejen la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. -redirect_from: - - /articles/setting-up-teams-improved-organization-permissions/ - - /articles/setting-up-teams-for-accessing-organization-repositories/ - - /articles/creating-teams/ - - /articles/adding-people-to-teams-in-an-organization/ - - /articles/removing-a-member-from-a-team-in-your-organization/ - - /articles/setting-up-teams/ - - /articles/maintaining-teams-improved-organization-permissions/ - - /articles/maintaining-teams/ - - /articles/organizing-members-into-teams -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-teams - - /creating-a-team - - /setting-your-teams-profile-picture - - /adding-organization-members-to-a-team - - /managing-code-review-assignment-for-your-team - - /renaming-a-team - - /changing-team-visibility - - /synchronizing-a-team-with-an-identity-provider-group - - /moving-a-team-in-your-organizations-hierarchy - - /requesting-to-add-a-child-team - - /requesting-to-add-or-change-a-parent-team - - /removing-organization-members-from-a-team - - /disabling-team-discussions-for-your-organization - - /managing-scheduled-reminders-for-your-team - - /deleting-a-team ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md deleted file mode 100644 index 00c3c537b8..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Administrar una tarea de revisión de código para tu equipo -intro: Las tareas de revisión de código indican claramente qué miembros de un equipo se espera emitan una revisión para una solicitud de extracción. -product: '{% data reusables.gated-features.code-review-assignment %}' -versions: - free-pro-team: '*' - enterprise-server: '>=2.20' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team ---- -Los mantenedores de equipo y propietarios de organización pueden configurar tareas de revisión de código. - -### Acerca de las tareas de revisión de código - -Al utilizar tareas de revisión de código, cada que se pida a tu equipo revisar una solicitud de extracción, éste se eliminará como revisor y se asignará un subconjunto de miembros específicos del mismo en sustitución. Las tareas de revisión de código te permiten decidir si se notificará a todo el equipo o solo a un subconjunto de miembros del mismo cuando se solicite que éste realice una revisión. - -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)." - -### Rutear algoritmos - -Las tareas de revisión de código escogen y asignan revisores automáticamente basándose en uno de dos posibles algoritmos. - -El algoritmo de round robin (turno rotativo) escoge revisores basándose en quién recibe la solicitud de revisión menos reciente, y se enfoca en alternar entre todos los miembros del equipo sin importar el número de revisiones pendientes que tengan en el momento. - -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. - -### Configurar una tarea de revisión de código -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -5. En la barra lateral izquierda, da clic en **Tarea de revisión de código** ![Botón de tarea de revisión de código](/assets/images/help/teams/review-assignment-button.png) -6. Selecciona **Habilitar auto asignación**. ![Botón de tarea de revisión de código](/assets/images/help/teams/review-assignment-enable.png) -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**. - -### Inhabilitar una tarea de revisión de código -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -5. Selecciona **Habilitar auto asignación** para eliminar la marca. ![Botón de tarea de revisión de código](/assets/images/help/teams/review-assignment-enable.png) -6. Haz clic en **Guardar cambios**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md deleted file mode 100644 index 02a2366b9e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Administrar recordatorios programados para tu equipo -intro: Puedes obtener recordatorios en Slack cuando existan solicitudes de extracción pendientes de revisión por parte de tu equipo. -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests - - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team -versions: - free-pro-team: '*' ---- -### Acerca de los recordatorios programados para equipos - -{% data reusables.reminders.about-scheduled-reminders-teams-orgs %} - -Los mantenedores de equipo y propietarios de organización pueden configurar recordatorios programados para cualquier solicitud de extracción que tenga una solicitud de revisión por parte de sus equipos. Antes de que puedas crear un recordatorio programado para tu equipo, un propietario de la organización debe autorizar tu espacio de trabajo de Slack. Para obtener más información, consulta la sección "[Administrar recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)". - -### Crear un recordatorio programado para un equipo -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/teams/scheduled-reminders-teams.png) -{% data reusables.reminders.add-reminder %} -{% data reusables.reminders.authorize-slack %} -{% data reusables.reminders.slack-channel %} -{% data reusables.reminders.days-dropdown %} -{% data reusables.reminders.times-dropdowns %} -{% data reusables.reminders.tracked-repos %} -{% data reusables.reminders.ignore-drafts %} -{% data reusables.reminders.no-review-requests %} -{% data reusables.reminders.author-reviews %} -{% data reusables.reminders.approved-prs %} -{% data reusables.reminders.min-age %} -{% data reusables.reminders.min-staleness %} -{% data reusables.reminders.ignored-terms %} -{% data reusables.reminders.ignored-labels %} -{% data reusables.reminders.required-labels %} -{% data reusables.reminders.create-reminder %} - -### Administrar un recordatorio programado para un equipo -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/teams/scheduled-reminders-teams.png) -{% data reusables.reminders.edit-existing %} -{% data reusables.reminders.edit-page %} -{% data reusables.reminders.update-buttons %} - -### Borrar un recordatorio programado para un equipo -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/teams/scheduled-reminders-teams.png) -{% data reusables.reminders.delete %} - -### Leer más - -- "[Administrar los recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" -- "[Administrar tus recordatorios programados](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md deleted file mode 100644 index f89d59572d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Mover un equipo en la jerarquía de tu organización -intro: 'Los mantenedores del equipo y los propietarios de la organización pueden anidar un equipo bajo un equipo padre, o cambiar o eliminar un equipo padre de un equipo anidado.' -redirect_from: - - /articles/changing-a-team-s-parent/ - - /articles/moving-a-team-in-your-organization-s-hierarchy - - /articles/moving-a-team-in-your-organizations-hierarchy - - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Los propietarios de la organización pueden cambiar el padre de cualquier equipo. Los mantenedores del equipo pueden cambiar el equipo padre de un equipo si son mantenedores tanto en el equipo hijo como en el equipo padre. Los mantenedores del equipo sin permisos de mantenedor en el equipo hijo puede solicitar agregar un equipo padre o hijo. Para obtener más información, consulta "[Solicitar agregar o cambiar un equipo padre](/articles/requesting-to-add-or-change-a-parent-team)" y "[Solicitar agregar un equipo hijo](/articles/requesting-to-add-a-child-team)." - -{% data reusables.organizations.child-team-inherits-permissions %} - -{% tip %} - -**Sugerencias:** -- No puedes cambiar el equipo padre de un equipo a un equipo secreto. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". -- No puedes anidar un equipo padre debajo de uno de sus equipos hijos. - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.teams %} -4. En la lista de equipos, haz clic en el nombre del equipo cuyo padre deseas cambiar. ![Lista de los equipos de la organización](/assets/images/help/teams/click-team-name.png) -{% data reusables.organizations.team_settings %} -6. Utiliza el menú desplegable para elegir un equipo padre, o para eliminar un equipo padre existente, selecciona **Clear selected value (Borrar el valor seleccionado)**. ![Menú desplegable que detalla los equipos de la organización](/assets/images/help/teams/choose-parent-team.png) -7. Da clic en **Actualizar**. -{% data reusables.repositories.changed-repository-access-permissions %} -9. Haz clic en **Confirm new parent team (Confirmar nuevo equipo padre)**. ![Casilla modal con información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) - -### Leer más - -- [Acerca de los equipos](/articles/about-teams)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/removing-organization-members-from-a-team.md deleted file mode 100644 index 841d3871c0..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/removing-organization-members-from-a-team.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Eliminar de un equipo a miembros de la organización -intro: 'Las personas con permisos de *propietario* o *mantenedor del equipo* pueden eliminar de un equipo a miembros del equipo. Puede que se deba hacer esto si una persona no necesita más el acceso a un repositorio que otorga el equipo, o si una persona no se dedica más a los proyectos de un equipo.' -redirect_from: - - /articles/removing-organization-members-from-a-team-early-access-program/ - - /articles/removing-organization-members-from-a-team - - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -4. Selecciona la persona o las personas que quieres eliminar. ![Casilla junto al miembro de la organización](/assets/images/help/teams/team-member-check-box.png) -5. Arriba de la lista de miembros del equipo, utiliza el menú desplegable y haz clic en **Eliminar del equipo**. ![Menú desplegable con opción para cambiar el rol](/assets/images/help/teams/bulk-edit-drop-down.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/renaming-a-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/renaming-a-team.md deleted file mode 100644 index 12c1f2766c..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/renaming-a-team.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Renombrar un equipo -intro: Los mantenedores del equipo y los propietarios de la organización pueden editar el nombre y la descripción de un equipo. -redirect_from: - - /articles/renaming-a-team - - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -5. Escribe un nombre o descripción nuevos para el equipo. ![Campos para el nombre y la descripción del equipo](/assets/images/help/teams/team-name-description.png) -6. Da clic en **Actualizar**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/requesting-to-add-a-child-team.md deleted file mode 100644 index f2340eaca0..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/requesting-to-add-a-child-team.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Solicitar agregar un equipo hijo -intro: 'Si tienes permisos de mantenedor en un equipo, puedes solicitar anidar un equipo existente en tu equipo en la jerarquía de tu organización.' -redirect_from: - - /articles/requesting-to-add-a-child-team - - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cuando solicitas agregar un equipo como hijo, se envía una solicitud a los mantenedores del equipo hijo. Una vez que un mantenedor del equipo hijo aprueba tu solicitud, el equipo hijo se anida en el equipo padre de la jerarquía de tu organización. - -Si eres propietario de una organización o tienes permisos de mantenedor del equipo tanto en el equipo hijo como en el equipo padre, puedes agregar el equipo hijo sin solicitar aprobación o modificar el padre del equipo hijo desde la página de configuraciones del equipo hijo. Para obtener más información, consulta "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)". - -{% data reusables.organizations.child-team-inherits-permissions %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.teams %} -4. En la lista de equipos, haz clic en el nombre del equipo al que quieres agregar el equipo hijo. ![Lista de los equipos de la organización](/assets/images/help/teams/click-team-name.png) -5. En la parte superior de la página del equipo, haz clic en {% octicon "people" aria-label="The people icon" %} **Teams** (Equipos). ![Pestaña de equipos en la página de un equipo](/assets/images/help/teams/team-teams-tab.png) -6. Haz clic en **Add a team** (Agregar un equipo). ![Botón Add a team (Agregar un equipo) en una página de equipo](/assets/images/help/teams/add-a-team.png) -7. Escribe el nombre del equipo que quieres agregar como equipo hijo y selecciónalo desde la lista desplegable. ![Recuadro para escribir y menú desplegable para seleccionar el nombre del equipo hijo](/assets/images/help/teams/type-child-team-name.png) -{% data reusables.repositories.changed-repository-access-permissions %} -9. Haz clic en **Confirm changes** (Confirmar cambios) para enviar una solicitud para agregar al equipo hijo. ![Casilla modal con información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) - -### Leer más - -- [Acerca de los equipos](/articles/about-teams)" -- "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)" -- "[Solicitar agregar o modificar un equipo padre](/articles/requesting-to-add-or-change-a-parent-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md deleted file mode 100644 index 80981b24b3..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Solicitar agregar o modificar un equipo padre -intro: 'Si tienes permisos de mantenedor en un equipo, puedes solicitar anidar tu equipo bajo un equipo padre en la jerarquía de tu organización.' -redirect_from: - - /articles/requesting-to-add-or-change-a-parent-team - - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cuando solicitas agregar o modificar el padre de tu equipo, se envía una solicitud a los mantenedores del equipo padre. Cuando un mantenedor del nuevo equipo padre aprueba tu solicitud, tu equipo se anida como equipo hijo en bajo el equipo padre en la jerarquía de tu organización. - -Si eres propietario de la organización o tienes permisos de mantenedor del equipo en el equipo hijo y el equipo padre, puedes agregar el equipo padre sin solicitar aprobación ni modificar el padre de tu equipo desde la página de parámetros del equipo. Para obtener más información, consulta "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)". - -{% data reusables.organizations.child-team-inherits-permissions %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.teams %} -4. En la lista de equipos, haz clic en el nombre del equipo que quieres anidar bajo un padre. ![Lista de los equipos de la organización](/assets/images/help/teams/click-team-name.png) -{% data reusables.organizations.team_settings %} -6. En "Parent team" (Equipo padre), utiliza el menú desplegable "Select parent team" (Seleccionar equipo padre) y haz clic en el nombre del nuevo equipo padre. ![Menú desplegable que detalla los equipos de la organización](/assets/images/help/teams/choose-parent-team.png) -7. Haz clic en **Guardar cambios**. -{% data reusables.repositories.changed-repository-access-permissions %} -9. Haz clic en **Confirm changes** (Confirmar cambios) para enviar una solicitud para agregar o modificar el padre de tu equipo. ![Casilla modal con información acerca de los cambios en los permisos de acceso del repositorio](/assets/images/help/teams/confirm-new-parent-team.png) - -### Leer más - -- [Acerca de los equipos](/articles/about-teams)" -- "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organization-s-hierarchy)" -- "[Solicitar agregar un equipo hijo](/articles/requesting-to-add-a-child-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/setting-your-teams-profile-picture.md deleted file mode 100644 index 5633f34e4e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/setting-your-teams-profile-picture.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Configurar la imagen de perfil de tu equipo -intro: 'Los mantenedores del equipo y los propietarios de la organización pueden establecer una imagen de perfil para un equipo, que se muestra en la página del equipo.' -redirect_from: - - /articles/setting-your-team-s-profile-picture - - /articles/setting-your-teams-profile-picture - - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Excepto que configures una imagen de perfil para un equipo, la imagen de perfil del equipo coincidirá con la imagen de perfil de la organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -5. Haz clic en **Upload new picture (Cargar una imagen)** o selecciona la imagen de perfil que deseas. ![Cargar nueva imagen](/assets/images/help/teams/org-team-profile-picture-upload.png) -6. Haz clic y arrastra el recorte de la imagen según se necesite, después haz clic en **Set new team avatar (Establecer nuevo avatar del equipo)**. ![Establecer nuevo avatar del equipo](/assets/images/help/teams/org-team-set-new-team-avatar.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md deleted file mode 100644 index 1fe66276e1..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Sincronizar un equipo con un grupo de proveedor de identidad -intro: 'Puedes sincronizar un equipo de {% data variables.product.prodname_dotcom %} con un grupo de proveedor de identidad (IdP) para agregar y eliminar miembros del grupo automáticamente.' -product: '{% data reusables.gated-features.team-synchronization %}' -permissions: 'Los propietarios de la organización y mantenedores de equipo pueden sincronizar un equipo de {% data variables.product.prodname_dotcom %} con un grupo de IdP.' -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group ---- -{% data reusables.gated-features.okta-team-sync %} - -### Acerca de la sincronización de equipo - -{% data reusables.identity-and-permissions.about-team-sync %} - -Puedes conectar hasta cinco grupos de IdP a un equipo de {% data variables.product.prodname_dotcom %}. Un grupo de IdP puede asignarse a varios equipos de {% data variables.product.prodname_dotcom %} sin restricción. - -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 la membrecía del equipo en {% data variables.product.product_name %} ni utilizando la API. - -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)." - -Los equipos padre no pueden sincronizarse con los grupos de IdP. Si el equipo que quieres conectar a un grupo de IdP es un equipo padre, te recomendamos crear un equipo nuevo o eliminar las relaciones anidadas que hacen de tu equipo un equipo padre. Para obtener más información, consulta las secciónes "[Acerca de los equipos](/articles/about-teams#nested-teams)", "[Crear un equipo](/github/setting-up-and-managing-organizations-and-teams/creating-a-team)", y "[Mover un equipo en la jerarquía de tu organización](/articles/moving-a-team-in-your-organizations-hierarchy)". - -Para administrar el acceso de un repositorio para cualquier equipo de {% data variables.product.prodname_dotcom %}, incluyendo los equipos conectados a un grupo de IdP debes hacer cambios con {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de equipos](/articles/about-teams)" y "[Administrar el acceso de equipo a un repositorio de la organización](/articles/managing-team-access-to-an-organization-repository)." - -También puedes administrar la sincronización de equipos con la API. Para obtener más información, consulta la sección "[Sincronización de equipos](/v3/teams/team_sync/)". - -### Requisitos para los miembros de los equipos sincronizados - -Después de conectar a un equipo al grupo de IdP, los datos de mebrecía para cada miembro del equipo se sincronizarán si la persona sigue autenticándose utilizando el SSO de SAML con la misma identidad de SSO en {% data variables.product.prodname_dotcom %}, y si la persona sigue siendo miembro del grupo de IdP conectado. - -Los equipos o miembros de grupo existentes pueden eliminarse automáticamente del equipo en {% data variables.product.prodname_dotcom %}. Todo equipo o miembro de grupo existente que no se autentique en la organización o cuenta empresarial utilizando SSO podría perder acceso a los repositorios. Todo equipo o miembro de grupo existente que no se encuentre en el grupo de IdP conectado podría perder acceso a los repositorios potencialmente. - -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. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)". - -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 "[Requerir la configuración de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)". - -### Prerrequisitos - -Antes de poder conectar a un equipo con un grupo de proveedor de identidad, un propietario de organización o de empresa debe habilitar la sincronización de equipos para tu organización o cuenta empresarial. Para obtener más información, consulta las secciones "[Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)" y "[Requerir la configuración de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-team-synchronization-for-organizations-in-your-enterprise-account)". - -Para evitar el eliminar miembros del equipo accidentalmente, visita el protal administrativo para tu IdP y confirma que cada miembro actual del equipo también se encuentre en los grupos de IdP que quieras conectar a este equipo. Si no tienes este acceso a tu proveedor de identidad, puedes comunicarte con tu administrador de IdP. - -Debes autenticarte utilizando el SSO de SAML. 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)". - -### Conectar un grupo de IdP a tu equipo - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -5. Debajo de "Grupos del Proveedor de Identidad", utiliza el menú desplegable y selecciona hasta 5 grupos del proveedor de identidad. ![Menú desplegable para elegir los grupos de proveedor de identidad](/assets/images/help/teams/choose-an-idp-group.png) -6. Haz clic en **Guardar cambios**. - -### Desconectar un grupo de IdP de un equipo - -Si desconectas un grupo de IdP de un equipo de {% data variables.product.prodname_dotcom %}, los miembros de este equipo que fueran asignados al equipo {% data variables.product.prodname_dotcom %} a través del grupo de IdP se eliminarán de dicho equipo. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -6. Debajo de "Grupos del Proveedor de Identidad", a la derecha del grupo de IdP que quieras desconectar, da clic en {% octicon "x" aria-label="X symbol" %}. ![Deselecciona un grupo IdP conectado desde el equipo de GitHub](/assets/images/help/teams/unselect-idp-group.png) -7. Haz clic en **Guardar cambios**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md deleted file mode 100644 index d469c05114..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Acerca de las restricciones de acceso a App OAuth -intro: 'Las organizaciones pueden elegir qué {% data variables.product.prodname_oauth_app %}s 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 - - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions -versions: - free-pro-team: '*' ---- -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_app %}s que quieran usar y los propietarios de la organización reciben una notificación de solicitudes pendientes. - -{% data reusables.organizations.oauth_app_restrictions_default %} - -{% tip %} - -**Sugerencia**: Cuando una organización no ha configurado las restricciones de acceso a {% data variables.product.prodname_oauth_app %}, cualquier {% data variables.product.prodname_oauth_app %} autorizada por un miembro de la organización también puede acceder a los recursos privados de la organización. - -{% endtip %} - -### 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. -- Las **{% data variables.product.prodname_oauth_app %}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). -- Las **claves SSH creadas por {% data variables.product.prodname_oauth_app %}s durante o después de febrero de 2014** inmediatamente pierden acceso a los recursos de la organización. -- Las **entregas de enlace de los repositorios privados de una organización** ya no serán enviadas a {% data variables.product.prodname_oauth_app %}s no aprobadas. -- El **acceso de API** a los recursos privados de la organización no está disponible para las {% data variables.product.prodname_oauth_app %}s 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. - -### Resolver las fallas de acceso a SSH - -Cuando una clave SSH creada antes de febrero de 2014 pierde acceso a una organización con las restricciones de acceso a {% data variables.product.prodname_oauth_app %} activadas, los subsiguientes intentos de acceso a SSH fallarán. Los usuarios se encontrarán con un mensaje de error que los redirecciona a una URL donde pueden aprobar la clave o cargar una clave de confianza en su lugar. - -### Webhooks - -Cuando se le otorga acceso a la organización a una {% data variables.product.prodname_oauth_app %} una vez que las restricciones están activadas, cualquier webhook preexistente creado por esa {% data variables.product.prodname_oauth_app %} retomará el despacho. - -Cuando una organización elimina el acceso de una {% data variables.product.prodname_oauth_app %} previamente aprobada, cualquier webhook preexistente creado por esa aplicación ya no será despachado (estos enlaces de desactivarán, pero no se eliminarán). - -### Volver a activar las restricciones de acceso - -Si una organización desactiva las restricciones de aplicación de acceso de {% data variables.product.prodname_oauth_app %}, y más tarde las vuelve a activar, automáticamente se le otorga acceso a los recursos de la organización a la {% data variables.product.prodname_oauth_app %} previamente aprobada . - -### 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)" -- "[Aprobar {% data variables.product.prodname_oauth_app %}s 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)" -- "[Solicitar aprobación de la organización para las {% data variables.product.prodname_oauth_app %}s](/articles/requesting-organization-approval-for-oauth-apps)" -- "[Autorizar las{% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md deleted file mode 100644 index 6f4ef8a7c7..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Aprobar aplicaciones OAuth para tu organización -intro: 'Cuando un miembro de la organización solicita a {% data variables.product.prodname_oauth_app %} que acceda a los recursos de la organización, los propietarios de la organización pueden aprobar o rechazar la solicitud.' -redirect_from: - - /articles/approving-third-party-applications-for-your-organization/ - - /articles/approving-oauth-apps-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization -versions: - free-pro-team: '*' ---- -Cuando las restricciones de acceso a {% data variables.product.prodname_oauth_app %} están habilitadas, los miembros de la organización deben [solicitar la aprobación](/articles/requesting-organization-approval-for-oauth-apps) de un propietario de la organización antes de que puedan autorizar una {% data variables.product.prodname_oauth_app %} que tiene acceso a los recursos de la organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.oauth_app_access %} -5. Junto a la aplicación que quieres aprobar, haz clic en **Review** (Revisar). ![Enlace de revisión de solicitud](/assets/images/help/settings/settings-third-party-approve-review.png) -6. Una vez que revises la información sobre la aplicación solicitada, haz clic en **Grant access** (Otorgar acceso). ![Botón para otorgar acceso](/assets/images/help/settings/settings-third-party-approve-grant.png) - -### Leer más - -- "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md deleted file mode 100644 index 6574b5f4e4..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Denegar el acceso a una App OAuth anteriormente aprobada para tu organización -intro: 'Si una organización ya no requiere una {% data variables.product.prodname_oauth_app %} previamente autorizada, los propietarios pueden eliminar el acceso de la aplicación a los recursos de la organización.' -redirect_from: - - /articles/denying-access-to-a-previously-approved-application-for-your-organization/ - - /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization -versions: - free-pro-team: '*' ---- -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.oauth_app_access %} -5. Junto a la aplicación que deseas inhabilitar, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. ![Icono Editar](/assets/images/help/settings/settings-third-party-deny-edit.png) -6. Haz clic en **Denegar acceso**. ![Botón Denegar confirmación](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md deleted file mode 100644 index c27c141043..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Inhabilitar las restricciones de acceso de las App OAuth para tu organización -intro: 'Los propietarios de la organización pueden inhabilitar las restricciones de las {% data variables.product.prodname_oauth_app %} 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 - - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization -versions: - free-pro-team: '*' ---- -{% danger %} - -**Advertencia**: Cuando inhabilitas las restricciones de acceso de {% data variables.product.prodname_oauth_app %} para tu organización, cualquier miembro de la organización autorizará automáticamente el acceso de {% data variables.product.prodname_oauth_app %} a los recursos privados de la organización cuando aprueben una aplicación para el uso en los parámetros de su cuenta personal. - -{% enddanger %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.oauth_app_access %} -5. Haz clic en **Eliminar restricciones**. ![Botón Eliminar restricciones](/assets/images/help/settings/settings-third-party-remove-restrictions.png) -6. Revisa la información acerca de la inhabilitación de las restricciones de las aplicaciones de terceros y luego haz clic en **Sí, eliminar las restricciones de las aplicaciones**. ![Botón para confirmar la eliminación](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md deleted file mode 100644 index 54d6acffa6..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Habilitar las restricciones de acceso de las App OAuth para tu organización -intro: 'Los propietarios de la organización pueden habilitar restricciones de acceso de las {% data variables.product.prodname_oauth_app %} para evitar que las aplicaciones que no sean confiables accedan a los recursos de la organización y para permitir que los miembros de la organización usen las {% data variables.product.prodname_oauth_app %} para sus cuentas personales.' -redirect_from: - - /articles/enabling-third-party-application-restrictions-for-your-organization/ - - /articles/enabling-oauth-app-access-restrictions-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization -versions: - free-pro-team: '*' ---- -{% data reusables.organizations.oauth_app_restrictions_default %} - -{% warning %} - -**Warnings**: -- Habilitar las restricciones de acceso de las {% data variables.product.prodname_oauth_app %} revocará los acesos de la organización a todas las {% data variables.product.prodname_oauth_app %} 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 %}. - -{% endwarning %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.oauth_app_access %} -5. En "Política de acceso de aplicaciones de terceros", haz clic en **Configurar restricciones de acceso de aplicaciones**. ![Botón Configurar restricciones](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) -6. Luego de revisar la información acerca de las restricciones de acceso de las aplicaciones de terceros, haz clic en **Restringir el acceso de aplicaciones de terceros**. ![Botón Confirmar restricciones](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/index.md b/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/index.md deleted file mode 100644 index e57f7c2f64..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -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. Luego los miembros de la organización pueden utilizar {% data variables.product.prodname_oauth_app %}s para sus cuentas de usuario personales mientras mantienen seguros los datos de la organización.' -redirect_from: - - /articles/restricting-access-to-your-organization-s-data - - /articles/restricting-access-to-your-organizations-data -versions: - free-pro-team: '*' -children: - - /about-oauth-app-access-restrictions - - /enabling-oauth-app-access-restrictions-for-your-organization - - /disabling-oauth-app-access-restrictions-for-your-organization - - /approving-oauth-apps-for-your-organization - - /denying-access-to-a-previously-approved-oauth-app-for-your-organization ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/index.md deleted file mode 100644 index 22d08a0424..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Configurar y administrar tu cuenta de empresa -shortTitle: Tu cuenta de empresa -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /categories/setting-up-and-managing-your-enterprise-account -versions: - free-pro-team: '*' -children: - - /managing-your-enterprise-account - - /managing-users-in-your-enterprise-account - - /managing-organizations-in-your-enterprise-account - - /setting-policies-for-organizations-in-your-enterprise-account ---- -### Índice diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md deleted file mode 100644 index ea89a35395..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Agregar organizaciones en tu cuenta de empresa -intro: Puedes crear nuevas organizaciones para administrar dentro de tu cuenta de empresa. -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/adding-organizations-to-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/adding-organizations-to-your-enterprise-account -versions: - free-pro-team: '*' ---- -Los propietarios de la empresa pueden crear nuevas organizaciones dentro de los parámetros de la cuenta de 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. No puedes transferir las organizaciones existentes a una cuenta de empresa. - -### Crear una organización en tu cuenta de empresa - -Las organizaciones nuevas que crees dentro de los parámetros de la cuenta de empresa se incluyen en la suscripción de la cuenta de empresa de {% data variables.product.prodname_ghe_cloud %}. Para más información sobre la colaboración en organizaciones, consulta "[Configurar y administrar organizaciones y equipo](/categories/setting-up-and-managing-organizations-and-teams)". - -Los propietarios de empresas que creen una organización que es propiedad de una cuenta de empresa se convierten automáticamente en los propietarios de la organización. Para obtener más información sobre los propietarios de organizaciones, consulta "[Niveles de permiso de una organización](/articles/permission-levels-for-an-organization)." - -{% data reusables.enterprise-accounts.access-enterprise %} -2. En la pestaña **Organizations** (Organizaciones), encima de la lista d elas organizaciones, haz clic en **New organization** (Organización nueva). ![Botón de la nueva organización](/assets/images/help/business-accounts/enterprise-account-add-org.png) -3. En "Organization name" (Nombre de la organización) escribe un nombre para tu organización. ![Campo para escribir el nombre de una organización nueva](/assets/images/help/business-accounts/new-organization-name-field.png) -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. Click **Finish**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account.md deleted file mode 100644 index 95884baed4..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Configurar webhooks para eventos de la organización en tu cuenta de empresa -intro: Los propietarios de empresas pueden configurar webhooks para eventos en organizaciones que son propiedad de una cuenta de empresa. -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/configuring-webhooks-for-organization-events-in-your-business-account/ - - /articles/configuring-webhooks-for-organization-events-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account -versions: - free-pro-team: '*' ---- -Puedes configurar webhooks para recibir eventos de organizaciones que son propiedad de tu cuenta de empresa. Para obtener más información acerca de los webhooks, consulta la sección "[Webhooks](/webhooks/)". - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.hooks-tab %} -4. Al lado de "Webhooks", haz clic en **Add webhook** (Agregar webhook). ![Botón para agregar webhook en la barra lateral Webhooks](/assets/images/help/business-accounts/add-webhook-button.png) -5. Escribe una URL de carga, luego opcionalmente personaliza la configuración. Para obtener más información, consulta "[Crear webhooks](/webhooks/creating/#creating-webhooks)". ![Campos para la URL de carga y otras opciones de personalización](/assets/images/help/business-accounts/webhook-payload-url-and-customization-options.png) -6. En "Which events would you like to trigger this webhook?" (¿Qué eventos desaría desencadenar este webhook?), selecciona **Let me select individual events** (Dejarme seleccionar eventos individuales). ![Seleccionar eventos individuales](/assets/images/help/business-accounts/webhook-let-me-select-individual-events.png) -7. Selecciona uno o más eventos de la cuenta de empresa para que reciba tu webhook. Para obtener más información, consulta la sección "[Tipos de eventos y cargas útiles](/webhooks/event-payloads/)". ![Seleccionar eventos individuales](/assets/images/help/business-accounts/webhook-selected-events.png) -8. Para recibir los eventos seleccionados para los webhooks desencadenados, selecciona **Active** (Activar). ![Seleccionar eventos individuales](/assets/images/help/business-accounts/webhook-active.png) -9. Haz clic en **Add webhook** (Agregar webhook). diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/index.md deleted file mode 100644 index 2aa5d77064..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Administrar organizaciones en tu cuenta de empresa -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/managing-organizations-in-your-enterprise-account -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /adding-organizations-to-your-enterprise-account - - /managing-unowned-organizations-in-your-enterprise-account - - /viewing-the-audit-logs-for-organizations-in-your-enterprise-account - - /configuring-webhooks-for-organization-events-in-your-enterprise-account ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account.md deleted file mode 100644 index 875f522be9..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Administrar las organizaciones que no te pertenecen en tu cuenta empresarial -intro: Puedes convertirte en propietario de una organización en tu cuenta empresarial si ésta no tiene propietarios actualmente. -product: '{% data reusables.gated-features.enterprise-accounts %}' -permissions: Los propietarios de las empresas pueden adminsitrar organizaciones sin propietario en una cuenta empresarial. -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account ---- -Si habilitas el desaprovisionamiento de usuarios para administrar las membrecías organizacionales en tu cuenta empresarial, podrías terminar teniendo una organización que no tiene propietarios. 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-account/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)". - -{% data reusables.enterprise-accounts.access-enterprise %} -2. A la derecha del campo de búsqueda, da clic en **X sin propietario**. ![Botón para ver las organizaciones sin propietario](/assets/images/help/business-accounts/unowned-organizations-button.png) -3. A la derecha de la organización sobre la cual quieres asumirte como propietario, da clic en **Convertirte en propietario**. ![Botón de convertirte en propietario](/assets/images/help/business-accounts/become-an-owner-button.png) -4. Lee la advertencia y luego da clic en **Convertirte en propietario**. ![Botón de convertirte en propietario](/assets/images/help/business-accounts/become-an-owner-confirmation.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account.md deleted file mode 100644 index 986820d530..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Ver los registros de auditoría para organizaciones en tu cuenta de empresa -intro: Los propietarios de la empresa pueden ver accciones acumuladas de todas las organizaciones propiedad de una cuenta de empresa en su registro de auditoría. -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account/ - - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account -versions: - free-pro-team: '*' ---- -Cada entrada del registro de auditoría muestra información vigente acerca de un evento, como: - -- 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 - -Puedes buscar el registro de auditoría para eventos específicos y exportar los datos del registro de auditoría. Para obtener más información acerca de buscar el registro de auditoría y eventos en una organización específica, consulta "[Revisar el registro de auditoría para tu organización](/articles/reviewing-the-audit-log-for-your-organization)." - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.audit-log-tab %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/index.md deleted file mode 100644 index ffb0c223ed..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Administrar a los usuarios en tu cuenta de empresa -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/managing-users-in-your-enterprise-account -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /roles-for-an-enterprise-account - - /inviting-people-to-manage-your-enterprise-account - - /viewing-people-in-your-enterprise-account - - /viewing-and-managing-a-users-saml-access-to-your-enterprise-account ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/inviting-people-to-manage-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/inviting-people-to-manage-your-enterprise-account.md deleted file mode 100644 index a2e7f90330..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/inviting-people-to-manage-your-enterprise-account.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Invitar a personas a administrar tu cuenta de empresa -intro: Puedes invitar a personas a que se vuelvan propietarios de empresa o administradores de facturación en tu cuenta de empresa. También puedes eliminar propietarios de empresa o administradores de facturación que no necesiten seguir teniendo acceso a la cuenta de empresa. -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/inviting-people-to-collaborate-in-your-business-account/ - - /articles/inviting-people-to-manage-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de invitar a personas a administrar tu cuenta de empresa - -{% data reusables.enterprise-accounts.enterprise-administrators %} Para obtener más información, consulta "[Roles de una cuenta de empresa](/articles/roles-for-an-enterprise-account)". - -{% tip %} - -**Sugerencia:**Para obtener más información acerca de administrar usuarios dentro de una organización que le pertenece a tu cuenta de empresa, consulta "[Administrar membresías de tu organización](/articles/managing-membership-in-your-organization)" y "[Administrar el acceso de personas a tu organización con roles](/articles/managing-peoples-access-to-your-organization-with-roles)." - -{% endtip %} - -### Invitar a un administrador de empresa a tu cuenta de empresa - -Solo los propietarios de empresa pueden invitar a otras personas a que se conviertan en administradores de empresa. - -Después de que invites a alguna persona a que se una a la cuenta de empresa, esta debe aceptar la invitación enviada por correo electrónico antes de poder acceder a la cuenta de empresa. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -3. 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) -4. Arriba de la lista de administradores, haz clic en **Invite admin** (Invitar administrador). ![Botón Invite admin (Invitar administrador) arriba de la lista de propietarios de empresa](/assets/images/help/business-accounts/invite-admin-button.png) -5. 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. ![Casilla modal con campo para escribir el nombre de usuario, el nombre completo o la dirección de correo electrónico de una persona y botón Invite (Invitar)](/assets/images/help/business-accounts/invite-admins-modal-button.png) -6. 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) -7. Haz clic en **Send Invitation** (Enviar invitación). ![Botón Send invitation (Enviar invitación)](/assets/images/help/business-accounts/invite-admins-send-invitation.png) - -### Eliminar un administrador de empresa de tu cuenta de empresa - -Solo los propietarios de empresa pueden eliminar a otros administradores de empresa de la cuenta de empresa. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -3. Junto al nombre de usuario de la persona que quieres eliminar, haz clic en {% octicon "gear" aria-label="The Settings gear" %}, luego haz clic en **Remove owner** (Eliminar propietario) o **Remove billing manager** (Eliminar gerente de facturación). ![Parámetros con opción del menú para eliminar un administrador de empresa](/assets/images/help/business-accounts/remove-admin.png) - -### Leer más - -- "[Roles de una cuenta de empresa](/articles/roles-for-an-enterprise-account)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/roles-for-an-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/roles-for-an-enterprise-account.md deleted file mode 100644 index 59e11e1ebb..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/roles-for-an-enterprise-account.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Roles para una cuenta de empresa -intro: 'Para controlar el acceso a los parámetros y los datos de tu cuenta de empresa, les puedes otorgar diferentes roles a las personas de la cuenta de empresa.' -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/permission-levels-for-a-business-account/ - - /articles/roles-for-an-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Para obtener más información acerca de agregar personas a tu cuenta de empresa, consulta "[Invitar personas a administrar tu cuenta de empresa](/articles/inviting-people-to-manage-your-enterprise-account)". - -### Acerca de los roles para una cuenta de empresa - -Las cuentas de empresa vienen con un conjunto de roles de administrador que puedes asignarles a los usuarios de tu empresa. Cada rol de administrador se mapea con las funciones comerciales y proporciona permisos para hacer tareas específicas dentro de la cuenta de empresa. - -{% data reusables.enterprise-accounts.enterprise-administrators %} - -### Propietario de empresa - -Los propietarios de empresa tienen control total sobre la cuenta de empresa y pueden hacer todas las acciones, incluidas las siguientes: -- Gestionar administradores -- Agregar organizaciones a la empresa y eliminarlas -- Administrar parámetros de la empresa -- Aplicar políticas en las organizaciones -- Administrar parámetros de facturación - -Los propietarios de empresa no pueden acceder a los parámetros o el contenido de la organización, a menos que se conviertan en propietarios de la organización o que se les otorgue acceso directo al repositorio que le pertenece a una organización. Del mismo modo, los propietarios de organizaciones en tu cuenta de empresa no tienen acceso a la cuenta de empresa en sí misma, a menos que los conviertas en propietarios de la empresa. - -Puedes agregar a tantos propietarios de empresa como desees para tu cuenta de empresa. Los propietarios de empresa deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}. Como buena práctica, recomendamos que conviertas solo a algunas personas de tu empresa en propietarios de empresa para reducir el riesgo al que se expone tu negocio. - -### Miembros de empresa - -Los miembros de las organizaciones que le pertenecen a tu cuenta de empresa, automáticamente, se vuelven miembros de la cuenta de empresa. Los miembros pueden colaborar en las organizaciones y pueden ser propietarios de la organización, pero no pueden acceder a los parámetros de la cuenta de empresa ni configurarlos, incluidos los parámetros de facturación. - -Las personas de tu cuenta de empresa pueden tener diferentes niveles de acceso a las varias organizaciones que le pertenecen a tu cuenta de empresa y a los repositorios dentro de esas organizaciones. Puedes ver los recursos a los que tiene acceso cada persona. Para obtener más información, consulta "[Ver personas en tu cuenta de empresa](/articles/viewing-people-in-your-enterprise-account)." - -Para obtener más información acerca de los permisos al nivel de la organización, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". - -Las personas con acceso de colaborador externo a los repositorios que le pertenecen a tu organización también se detallan en la pestaña People (Personas) de tu cuenta de empresa, pero no son miembros de la empresa y no tienen ningún acceso a la cuenta de empresa. Para obtener más información sobre los colaboradores externos, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". - -### Gerente de facturación - -Los gerentes de facturación solo tienen acceso a los parámetros de facturación de tu cuenta de empresa. Los gerentes de facturación de tu cuenta de empresa pueden hacer lo siguiente: -- Ver y administrar las licencias de usuario, {% data variables.large_files.product_name_short %} los paquetes y otros parámetros de facturación -- Ver una lista de gerentes de facturación -- Agregar o eliminar otros gerentes de facturación - -Los gerentes de facturación no tienen acceso a las organizaciones o repositorios de tu cuenta de empresa y no pueden agregar o eliminar propietarios de empresa. Los gerentes de facturación deben tener una cuenta personal en {% data variables.product.prodname_dotcom %}. - -### Leer más - -- "[Acerca de las cuentas de empresa](/articles/about-enterprise-accounts)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account.md deleted file mode 100644 index 74e051a257..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Visualizar y administrar el acceso de SAML de un usuario a tu cuenta empresarial -intro: 'Puedes ver y revocar la identidad vinculada de un miembro de la empresa, sesiones activas y credenciales autorizadas.' -permissions: Los propietarios de empresa pueden ver y administrar el acceso de SAML para los miembros en las organizaciones. -product: '{% data reusables.gated-features.enterprise-accounts %}' -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account ---- -### Acerca del acceso de SAML a tu cuenta empresarial - -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 %} - -### Visualizar y revocar una identidad vinculada - -{% data reusables.saml.about-linked-identities %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -{% data reusables.saml.click-person-revoke-identity %} -{% data reusables.saml.saml-identity-linked %} -{% data reusables.saml.view-sso-identity %} -{% data reusables.saml.revoke-sso-identity %} -{% data reusables.saml.confirm-revoke-identity %} - -### Ver y revocar una sesión activa de SAML - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -{% data reusables.saml.click-person-revoke-session %} -{% data reusables.saml.saml-identity-linked %} -{% data reusables.saml.view-saml-sessions %} -{% data reusables.saml.revoke-saml-session %} - -### Visualizar y revocar credenciales autorizadas - -{% data reusables.saml.about-authorized-credentials %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -{% data reusables.saml.click-person-revoke-credentials %} -{% data reusables.saml.saml-identity-linked %} -{% data reusables.saml.view-authorized-credentials %} -{% data reusables.saml.revoke-authorized-credentials %} -{% data reusables.saml.confirm-revoke-credentials %} - -### Leer más - -- "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/viewing-people-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/viewing-people-in-your-enterprise-account.md deleted file mode 100644 index c6135b129b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account/viewing-people-in-your-enterprise-account.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Ver personas en tu cuenta de empresa -intro: 'Para auditar el acceso a los recursos que son propiedad de la empresa o el uso de la licencia de usuario, los propietarios de la empresa pueden ver cada administrador o miembro de la cuenta de empresa.' -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/viewing-people-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Ver propietarios de empresa y gerentes de facturación - -Puedes ver los propietarios de empresa y los gerentes de facturación, y una lista de invitaciones pendientes para convertirse en propietarios y gerentes de facturación. Puedes filtrar la lista de administradores de empresa por rol. Puedes encontrar una persona específica al buscar por su nombre de usuario o nombre completo. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -{% data reusables.enterprise-accounts.administrators-tab %} - -### Ver miembros y colaboradores externos - -Puedes ver la cantidad de miembros y colaboradores externos pendientes. Puedes filtrar la lista de miembros por implementación ({% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}), rol y organización. Puedes filtrar la lista de colaboradores externos por la visibilidad de los repositorios a los que el colaborador tiene acceso. Puedes encontrar una persona específica al buscar por su nombre de usuario o nombre que se muestra. - -Al hacer clic en el nombre de la persona, puedes ver todas las organizaciones de {% data variables.product.prodname_ghe_cloud %} e instancias de {% data variables.product.prodname_ghe_server %} a las que un miembro pertenece, y a qué repositorios tiene acceso un colaborador externo. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.people-tab %} -3. De manera opcional, para ver una lista de colaboradores externos en lugar de una lista de miembros, haz clic en **Outside collaborators (Colaboradores externos)**. ![Pestaña de colaboradores externos en la página de miembros de la organización](/assets/images/help/business-accounts/outside-collaborators-tab.png) - -### Leer más - -- "[Roles de una cuenta de empresa](/articles/roles-for-an-enterprise-account)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/about-enterprise-accounts.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/about-enterprise-accounts.md deleted file mode 100644 index a7bfa2e81a..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/about-enterprise-accounts.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Acerca de las cuentas de empresa -intro: 'Con {% data variables.product.prodname_ghe_cloud %}, puedes crear una cuenta de empresa para activar la colaboración entre tus organizaciones, al mismo tiempo que le das 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/ - - /articles/about-enterprise-accounts - - /github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de las cuentas de empresa - -Una cuenta empresarial te permite administrar diversas organizaciones de {% data variables.product.prodname_dotcom %} e instancias de {% data variables.product.prodname_ghe_server %}. Tu cuenta de empresa debe tener un controlador, como una organización o cuenta personal en {% data variables.product.prodname_dotcom %}. Los administradores de empresas pueden administrar los parámetros y las referencias, como: - -- El acceso de los miembros y la administración (miembros de la organización, colaboradores externos). -- Facturación y uso (instancias de {% data variables.product.prodname_ghe_server %}, licencias de usuario, paquetes de {% data variables.large_files.product_name_short %}) -- Seguridad (inicio de sesión único, autenticación de dos factores). -- Solicitudes y paquetes de soporte compartidos con {% data variables.contact.enterprise_support %} - -{% data reusables.enterprise-accounts.enterprise-accounts-billing %} - -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 %}](/articles/githubs-products)". Para mejorar tu cuenta a {% data variables.product.prodname_enterprise %} o para comenzar con una cuenta empresarial, contacta a {% data variables.contact.contact_enterprise_sales %}. - -Para obtener más información acerca del acceso de los miembros y la administración, consulta "[Administrar usuarios en tu cuenta de empresa](/articles/managing-users-in-your-enterprise-account)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -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](/v4/guides/managing-enterprise-accounts)". -{% endif %} - -### Administrar las organizaciones vinculadas con tu cuenta de empresa - -Las organizaciones son cuentas compartidas donde grupos de personas pueden colaborar en muchos proyectos a la vez. Los propietarios 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, consulta "[Acerca de las organizaciones](/articles/about-organizations)". - -Los propietarios de la empresa pueden crear organizaciones y vincularlas a la empresa. Después de añadir organizaciones a tu cuenta empresarial, podrás administrar y hacer cumplir las políticas organizacionales. 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 "[Administrar las organizaciones de tu cuenta de empresa](/articles/managing-organizations-in-your-enterprise-account)" y "[Configurar políticas para las organizaciones de tu cuenta de empresa](/articles/setting-policies-for-organizations-in-your-enterprise-account)". - -### Administrar las licencias de {% data variables.product.prodname_ghe_server %} enlazadas con tu cuenta empresarial - -{% data reusables.enterprise-accounts.admin-managing-licenses %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/index.md deleted file mode 100644 index 0a5902a141..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Administrar tu cuenta de empresa -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/managing-your-enterprise-account -versions: - free-pro-team: '*' -children: - - /about-enterprise-accounts - - /viewing-the-subscription-and-usage-for-your-enterprise-account ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md deleted file mode 100644 index fcd4349714..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Ver la suscripción y el uso de tu cuenta de empresa -intro: 'Puedes ver la suscripción actual, el uso de la licencia, las facturas, el historial de pagos y otra información de facturación de tu cuenta de empresa.' -product: '{% data reusables.gated-features.enterprise-accounts %}' -permissions: 'Los propietarios de la empresa y los gerente de facturación pueden acceder y administrar todas las configuraciones de facturación para las cuentas de empresa. Para obtener más información acerca de los gerentes de facturación responsables, consulta la sección "[invitar personas para administrar tu cuenta empresarial](/articles/inviting-people-to-manage-your-enterprise-account)".' -redirect_from: - - /articles/viewing-the-subscription-and-usage-for-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de la facturación para las cuentas de empresa - -Las cuentas empresariales actualmente están disponibles para los clientes de {% data variables.product.prodname_enterprise %} que pagan por factura. La facturación para todas las organizaciones e instancias de {% data variables.product.prodname_ghe_server %} conectadas con tu cuenta empresarial se conjunta en un solo cargo por factura para todos tus servicios pagados de {% data variables.product.prodname_dotcom_the_website %} (incluyendo las licencias pagadas en organizaciones, paquetes de datos de {% data variables.large_files.product_name_long %}, y suscripciones a las apps de {% data variables.product.prodname_marketplace %}). - -### Ver la suscripción y el uso de tu cuenta de empresa - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.enterprise-licensing-tab %} -4. Dentro de "User licenses" (Licencias de usuario), visualiza tus licencias totales, la cantidad de licencias consumidas y la fecha de vencimiento de tu suscripción. ![Información de licencia y suscripción en las configuraciones de facturación de la empresa](/assets/images/help/business-accounts/billing-license-info.png) -5. Para ver los detalles de las licencias de usuario que se utilizan actualmente, da clic en **Ver detalles**. diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md deleted file mode 100644 index 6e4d73760d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta -intro: 'Puedes utilizar el inicio de sesión único (SSO, por sus siglas en inglés) del Lenguaje de Marcado para Confirmaciones (SAML, por sus siglas en inglés) y la Adminsitración de Identidad a Través de Dominios (SCIM, por sus siglas en inglés) con Okta para adminsitrar automáticamente el acceso a tu cuenta empresarial en {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account/configuring-single-sign-on-and-scim-for-your-enterprise-account-using-okta - - /github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta -versions: - free-pro-team: '*' ---- -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -### Acerca de SAML y SCIM 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 y SCIM 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. El SCIM agrega, administra y elimina automáticamente el acceso de los miembros a las organizaciones que pertenezcan a tu cuenta empresarial cuando haces cambios en Okta. Para obtener más información, consulta "[Requerir configuraciónes de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account)". - -Después de que habilites SCIM, las siguientes características de aprovisionamiento estarán disponibles para cualquier usuario al que asignes tu aplicación de {% data variables.product.prodname_ghe_cloud %} en Okta. - -| Característica | Descripción | -| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Subir Usuarios Nuevos | Los usuarios nuevos que se crean en Okta obtendrán acceso a los recursos de la cuenta empresarial y, opcionalmente, se pueden invitar a cualquiera de las organizaciones que pertenezcan a esta cuenta | -| Subir Desactivaciones de Usuarios | Desactivar un usuario en Okta revocará el acceso del mismo a los recursos de la cuenta empresarial y eliminará al usuario de todas las organizaciones que pertenezcan a esta cuenta | -| Subir Actualizaciones de Perfil | Las actualizaciones que se hagan al perfil de usuario en Okta se subirán a los metadatos de la cuenta empresarial del usuario | -| Reactivar Usuarios | Reactivar al usuario en Okta rehabilitará el acceso del mismo a la cuenta empresarial y, opcionalmente, enviará invitaciones por correo electrónico al usuario para volverse a unir a cualquiera de las organizaciones que pertenezcan a la cuenta empresarial de la cual era miembro este usuario previamente | - -### Prerrequisitos - -{% data reusables.saml.use-classic-ui %} - -### Agregar la aplicación {% data variables.product.prodname_ghe_cloud %} en Okta - -{% data reusables.saml.okta-admin-button %} -{% data reusables.saml.okta-dashboard-click-applications %} -{% data reusables.saml.add-okta-application %} -{% data reusables.saml.search-ghec-okta %} -1. Da clic en "{% data variables.product.prodname_ghe_cloud %} - Cuentas Empresariales". -1. Da clic en **Agregar**. -1. Opcionalmente, a la derecha de la "Etiqueta de aplicación", teclea un nombre descriptivo para la aplicación. ![Campo de etiqueta de la aplicación](/assets/images/help/saml/okta-application-label.png) -1. A la derecha de "Empresas de {% data variables.product.prodname_dotcom %}", teclea el nombre de tu cuenta empresarial. Por ejemplo, si la URL de tu cuenta empresarial es `https://github.com/enterprises/octo-corp`, teclea `octo-corp`. ![Campo de Github Enterprises](/assets/images/help/saml/okta-github-enterprises.png) -1. Haz clic en **Done** (listo). - -### Habilitar y probar el SSO de SAML - -{% data reusables.saml.okta-admin-button %} -{% data reusables.saml.okta-dashboard-click-applications %} -{% data reusables.saml.click-enterprise-account-application %} -{% data reusables.saml.assign-yourself-to-okta %} -{% data reusables.saml.okta-sign-on-tab %} -1. A la derecha de los Ajustes, da clic en **Editar**. -1. Debajo de "Atributos de SAML Configurados", a la derecha de "grupos"; utiliza el menú desplegable y selecciona **Coincidencias de regex**. -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. 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-account/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)". - -### Crear grupos en Okta - -1. En Okta, crea un grupo para que empate con la organización que pertenezca a tu cuenta empresarial. El nombre de cada grupo debe coincidir con el nombre de cuenta de la organización (no así, con el nombre mostrado de la misma). Por ejemplo, si la URL de la organización es `https://github.com/octo-org`, nombra `octo-org` al grupo. -1. Asigna la aplicación que creaste para tu cuenta empresarial a cada grupo. {% data variables.product.prodname_dotcom %} recibirá todos los datos de los `groups` para cada usuario. -1. Agrega usuarios a los grupos basándote en las organizaciones a las cuales quisieras que pertenezcan dichos usuarios. - -### Configurar el aprovisionamiento de usuarios con SCIM en Okta - -{% data reusables.scim.enterprise-account-scim %} - -Para configurar el aprovisionamiento de usuarios con SCIM en Okta, debes autorizar una aplicación de OAuth para que cree un token que Okta pueda utilizar para autenticarse en {% data variables.product.product_name %} a tu nombre. Okta creó la aplicación okta-oauth en asociación con {% data variables.product.prodname_dotcom %}. - -{% data reusables.saml.okta-admin-button %} -{% data reusables.saml.okta-dashboard-click-applications %} -{% data reusables.saml.click-enterprise-account-application %} -{% data reusables.saml.okta-provisioning-tab %} -{% data reusables.saml.okta-configure-api-integration %} -{% data reusables.saml.okta-enable-api-integration %} -1. Da clic en **Autenticarse con GitHub Enterprise Cloud - Cuentas Empresariales**. ![Botón para autenticarse con {% data variables.product.prodname_dotcom %}](/assets/images/help/business-accounts/authenticate-with-github-button.png) -1. A la derecha del nombre de tu cuenta empresarial, da clic en **Otorgar**. -1. Da clic en **Autorizar a okta-oauth**. -{% data reusables.saml.okta-save-provisioning %} -{% data reusables.saml.okta-edit-provisioning %} -1. Debajo del nombre de la aplicación, da clic en **Grupos de Subida**. ![Pestaña de Grupos de Subida](/assets/images/help/business-accounts/okta-push-groups-tab.png) -1. Utiliza el menú desplegable de **Grupos de Subida** y selecciona **Encontrar grupos por nombre**. ![Menú desplegable de Grupos de Subida](/assets/images/help/business-accounts/okta-push-groups-drop-down.png) -1. Agrega un grupo de subida para cada organización en tu cuenta empresarial en la cual quieras habilitar el aprovisionamiento de usuarios. - - Debajo de "GRUPOS DE SUBIDA POR NOMBRE", busca el grupo que corresponda a una organización que pertenezca a tu cuenta empresarial, luego da clic en el grupo dentro de los resultados de la búsqueda. - - A la derecha del nombre de grupo, en el menú desplegable de "Empatar resultados & acción de subida", verifica que se encuentre seleccionada la opción **Crear Grupo**. ![Menú desplegable con resultados coincidentes para la opción Crear Grupo seleccionada](/assets/images/help/saml/create-group-okta.png) - - Haz clic en **Save (Guardar)**. - - Repite esto para cada organización. -1. Debajo del nombre de tu aplicación, da clic en **Tareas**. ![Pestaña de tareas](/assets/images/help/business-accounts/okta-assignments-tab.png) -1. Si ves la opción **Aprovisionar usuarios**, los usuarios que fuesen miembros de un grupo de Okta antes de que agregaras un grupo de subida para este grupo no se han aprovisionado. Para enviar datos de SCIM de estos usuarios a {% data variables.product.product_name %}, da clic en **Aprovisionar usuarios**. - -### Habilitar SAML utilizando el aprovisionamiento - -Después de que habilitas el aprovisionamiento y desaprovisionamiento de SCIM, puedes habilitar opcionalmente el aprovisionamiento y desaprovisionamiento de usuarios de SAML. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -1. Debajo de "Aprovisionamiento de Usuarios de SAML", selecciona **Habilitar el aprovisionamiento de usuarios de SAML**. ![Casilla para habilitar el aprovisionamiento de usuarios con SAML](/assets/images/help/business-accounts/user-provisioning.png) -1. Haz clic en **Save (Guardar)**. -1. Opcionalmente, habilita el desaprovisionamiento de usuarios de SAML. - - Selecciona **Habilitar el resaprovisionamiento de usuarios de SAML**, y luego da clic en **Guardar**. ![Casilla para habilitar el desaprovisionamiento de usuarios con SAML](/assets/images/help/business-accounts/saml-deprovisioning.png) - - Lee la advertencia y da clic en **Habilitar el desaprovisionamiento de SAML**. ![Botón para habilitar el desaprovisionamiento de usuarios de SAML](/assets/images/help/business-accounts/saml-deprovisioning-confirm.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account.md deleted file mode 100644 index 6054bbfb41..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Hacer cumplir una política sobre las percepciones de la dependencia en tu cuenta de empresa -intro: 'En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir o no permitir que los miembros vean la información de dependencias o puedes permitir que los propietarios administren este parámetro a nivel de la organización.' -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/enforcing-a-policy-on-dependency-insights/ - - /articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account -versions: - free-pro-team: '*' ---- -En las organizaciones que son propiedad de una cuenta de empresa, los propietarios de la organización pueden establecer limitaciones para la visualización de la información de dependencias de la organización. Para obtener más información, consulta "[Cambiar la visibilidad de la información de dependencias de la organización](/articles/changing-the-visibility-of-your-organizations-dependency-insights)". - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -3. En la barra lateral de la cuenta de empresa, haz clic en **Organizaciones**. ![Pestaña Organizaciones en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/settings-policies-org-tab.png) -4. En "Políticas de la organización", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. En "Políticas de la organización", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de la organización](/assets/images/help/business-accounts/organization-policy-drop-down.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md deleted file mode 100644 index ab58280d85..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Requerir las políticas de Github Actions en tu cuenta empresarial -intro: 'Los propietarios de las empresas pueden habilitar, inhabilitar y limitar las {% data variables.product.prodname_actions %} para una cuenta empresarial.' -product: '{% data reusables.gated-features.enterprise-accounts %}' -miniTocMaxHeadingLevel: 4 -versions: - free-pro-team: '*' -redirect_from: - - /github/setting-up-and-managing-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account ---- -### Acerca de los permisos de las {% data variables.product.prodname_actions %} para tu cuenta empresarial - -Predeterminadamente, {% data variables.product.prodname_actions %} se habilita en todas las organizaciones que pertenezcan a una cuenta empresarial. Puedes elegir inhabilitar {% data variables.product.prodname_actions %} para todas las organizaciones que pertenezcan a una cuenta empresarial, o permitirlas únicamente para una organización epecífica. También puedes limitar el uso de acciones públicas, para que las personas solo puedan utilizar acciones locales que existen en tu organización. - -Para obtener más información acerca de {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)". - - -### Adminsitrar los permisos de {% data variables.product.prodname_actions %} para tu cuenta empresarial - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.actions-tab %} -{% data reusables.actions.enterprise-actions-permissions %} - -### Habilitar flujos de trabajo para las bifurcaciones de repositorios privados - -{% data reusables.github-actions.private-repository-forks-overview %} - -#### Configurar la política de bifurcaciones privadas para tu cuenta empresarial - -{% 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 %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account.md deleted file mode 100644 index dd7635f9c5..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Hacer cumplir políticas de tableros de proyecto en tu cuenta de empresa -intro: Los propietarios de empresas pueden hacer cumplir determinadas políticas de tableros de proyecto para todas las organizaciones que son propiedad de una cuenta de empresa o pueden permitir que las políticas se establezcan en cada organización. -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account/ - - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account/ - - /articles/enforcing-project-board-policies-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account -versions: - free-pro-team: '*' ---- -Para obtener más información acerca de los tipos de tableros de proyecto, consulta "[Acerca de los tableros de proyecto](/articles/about-project-boards)." - -### Hacer cumplir una política para tableros de proyecto en toda la organización - -En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes habilitar o inhabilitar tableros de proyecto en toda la organización o permitir que los propietarios administren este parámetro a nivel de la organización. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.projects-tab %} -4. En "Proyectos de la organización", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. En "Proyectos de la organización", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de tableros de proyecto de la organización](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png) - -### Hacer cumplir una política para tableros de proyecto de repositorios - -En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes habilitar o inhabilitar tableros de proyecto a nivel de los repositorios o permitir que los propietarios administren este parámetro a nivel de la organización. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -{% data reusables.enterprise-accounts.projects-tab %} -4. En "Proyectos de repositorios", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. En "Proyectos de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de tableros de proyecto de repositorios](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md deleted file mode 100644 index 3ec3dd052b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Hacer cumplir políticas de administración de repositorios para las organizaciones en tu cuenta de empresa -intro: Los propietarios de empresas pueden hacer cumplir determinadas políticas de administración de repositorios para todas las organizaciones que son propiedad de una cuenta de empresa o pueden permitir que las políticas se establezcan en cada organización. -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/enforcing-repository-management-settings-for-organizations-in-your-business-account/ - - /articles/enforcing-repository-management-policies-for-organizations-in-your-enterprise-account/ - - /articles/enforcing-repository-management-policies-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account -versions: - free-pro-team: '*' ---- -Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". - -### Hacer cumplir una política sobre los permisos de repositorios predeterminados - -En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes establecer un nivel de permiso predeterminado para los repositorios (ninguno, de lectura, de escritura o de 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. En la pestaña **Políticas de repositorios**, en "Permisos predeterminados", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. En "Permisos predeterminados", 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 - -En todas las organizaciones que le pertenecen a tu cuenta de empresa, puedes permitir que los miembros creen repositorios, restringir la creación de repositorios para los propietarios de la organización o permitir que los propietarios administren los ajustes en el nivel de la organización. Si permites que los miembros creen repositorios, puedes decidir si pueden crear cualquier combinación de repositorios públicos, privados e internos. {% data reusables.repositories.internal-repo-default %} Para obtener más información acerca de los repositorios internos, consulta "[Crear un repositorio interno](/articles/creating-an-internal-repository)". - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -3. En la pestaña **Políticas de repositorios**, en "Creación de repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -{% data reusables.enterprise-accounts.repo-creation-policy %} -{% data reusables.enterprise-accounts.repo-creation-types %} -6. Haz clic en **Save (Guardar)**. - -### Requerir una política para bifurcar repositorios privados o internos - -En todas las organizaciones que pertenezcan a tu cuenta empresarial, puedes permitir o prohibir la bifurcación de un repositorio privado o interno o permitir a los propietarios administrar la configuración a nivel organizacional para todos los que tengan acceso a éstos. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -3. En la pestaña **Políticas de repositorios**, en "Bifurcación de repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -4. En "Bifurcación de repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de bifurcación de repositorios](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png) - -### Hacer cumplir una política sobre la invitación de colaboradores externos a los repositorios - -En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir que los miembros inviten colaboradores externos a los repositorios, restringir las invitaciones de colaboradores externos a los propietarios 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 %} -3. En la pestaña **Políticas de repositorios**, en "Invitaciones a los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -4. En "Invitaciones a los repositorios", usa el menú desplegable y elige una política. - ![Menú desplegable con opciones de políticas de invitación de colaboradores externos](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png) - -### Hacer cumplir una política sobre cambios en la visibilidad de los repositorios - -En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir que los miembros con permisos de administrador modifiquen la visibilidad de un repositorio, puedes restringir los cambios en la visibilidad del repositorio a los propietarios 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 %} -3. En la pestaña **Políticas de repositorios**, en "Cambio en la visibilidad de los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -{% data reusables.enterprise-accounts.repository-visibility-policy %} - -### Hacer cumplir una política sobre la eliminación o la transferencia de repositorios - -En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir que los miembros con permisos de administrador eliminen o transfieran un repositorio, puedes restringir la eliminación o la transferencia de repositorios a los propietarios 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 %} -3. En la pestaña **Políticas de repositorios**, en "Eliminación y transferencia de los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -{% data reusables.enterprise-accounts.repository-deletion-policy %} - -### Hacer cumplir una política sobre la eliminación de propuestas - -En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes permitir que los miembros con permisos de administrador eliminen propuestas en un repositorio, puedes restringir la eliminación de propuestas a los propietarios 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 %} -3. En la pestaña **Políticas de repositorios**, en "Eliminación de propuestas en los repositorios", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -4. En "Eliminación de propuestas en los repositorios", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de eliminación de propuestas](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png) - -### Requerir una política para el nombre de la rama predeterminada - -Puedes configurar el nombre de la rama predeterminada para cualquier repositorio nuevo que creen los miembros s lo largo de todas las organizaciones que pertenezcan a tu cuenta empresarial. Puedes elegir el requerir un nombre de rama predeterminado a través de todas las organizaciones o permitir a algunas configurar un nombre diferente. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -3. En la pestaña de **Políticas de los repositorios**, debajo de "Nombre de la rama predeterminada", ingresa el nombre de rama predeterminada que deberán utilizar los repositorios nuevos. ![Caja de texto para ingresar un nombre de rama predeterminado](/assets/images/help/business-accounts/default-branch-name-text.png) -4. Opcionalmente, para requerir el nombre de rama predeterminado para todas las organizaciones en la empresa, selecciona **Requerir en toda la empresa**. ![Casilla de requerir](/assets/images/help/business-accounts/default-branch-name-enforce.png) -5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/business-accounts/default-branch-name-update.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account.md deleted file mode 100644 index 638b6210de..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account.md +++ /dev/null @@ -1,204 +0,0 @@ ---- -title: Hacer cumplir los parámetros de seguridad en tu cuenta de empresa -intro: Los propietarios de empresa pueden hacer cumplir determinadas políticas de seguridad para todas las organizaciones que son propiedad de una cuenta de empresa. -product: '{% data reusables.gated-features.enterprise-accounts %}' -miniTocMaxHeadingLevel: 4 -redirect_from: - - /articles/enforcing-security-settings-for-organizations-in-your-business-account/ - - /articles/enforcing-security-settings-for-organizations-in-your-enterprise-account/ - - /articles/enforcing-security-settings-in-your-enterprise-account - - /github/articles/managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account -versions: - free-pro-team: '*' ---- -### Requerir autenticación de dos factores para las organizaciones en tu cuenta de empresa - -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. - -Para requerir la autenticación de dos factores para todas las organizaciones que sean propiedad de tu cuenta de empresa, primero debes habilitar la autenticación de dos factores para tu propia cuenta. Para obtener más información, consulta "[Proteger tu cuenta con la autenticación de dos factores (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa/)". - -{% warning %} - -**Advertencias:** - -- Cuando requieras que se use la autenticación de dos factores para tu cuenta de empresa, los miembros, los colaboradores externos y los gerentes de facturación (incluidas las cuentas bot) en todas las organizaciones que sean propiedad de tu cuenta de empresa que no utilicen 2FA se eliminarán de tu organización y perderán acceso a sus repositorios. También perderán acceso a las bifurcaciones de sus repositorios privados de la organización. Puedes reinstalar sus privilegios de acceso y sus parámetros de configuración si habilitan la autenticación de dos factores para sus cuentas personales dentro de un plazo de tres meses a partir de su eliminación de tu organización. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization)". -- Todo propietario de la organización, miembro, gerente de facturación o colaborador externo en cualquiera de las organizaciones que sean propiedad de tu cuenta de empresa será automáticamente eliminado de tu organización si inhabilita la autenticación de dos factores de su cuenta personal una vez que hayas habilitado la autenticación de dos factores requerida. -- Si eres el único propietario de una cuenta de empresa que requiere autenticación de dos factores, no podrás inhabilitar la 2FA para tu cuenta personal sin inhabilitar la autenticación de dos factores requerida para la cuenta de empresa. - -{% endwarning %} - -Antes de solicitar el uso de la autenticación de dos factores, te recomendamos notificar a los miembros de la organización, a los colaboradores externos y a los gerentes de facturación y pedirles que configuren la 2FA para sus cuentas. Los propietarios de la organización pueden ver si los miembros y los colaboradores externos ya usan 2FA en la página Personas de cada organización. Para obtener más información, consulta "[Ver si los usuarios en tu organización tienen la 2FA habilitada](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)". - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. En "Autenticación de dos factores", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Debajo de "Two-factor authentication" ¨(Autenticación de dos factores), selecciona **Require two-factor authentication for all organizations in your business** (Requerir autenticación de dos factores para todas las organizaciones en tu empresa) y luego haz clic en **Save** (Guardar). ![Casilla de verificación para requerir autenticación de dos factores](/assets/images/help/business-accounts/require-2fa-checkbox.png) -6. Si se lo solicita, lee la información acerca de los miembros y colaboradores externos que serán eliminados de las organizaciones que son propiedad de tu cuenta de empresa. Para confirmar el cambio, escribe el nombre de tu cuenta de empresa y luego haz clic en **Eliminar miembros y requerir autenticación de dos factores**. ![Cuadro Confirmar aplicación obligatoria de dos factores](/assets/images/help/business-accounts/confirm-require-2fa.png) -7. Si algún miembro o colaborador externo es eliminado de las organizaciones que son propiedad de tu cuenta de empresa, también te recomendamos enviarle una invitación para reinstalar sus privilegios anteriores y su acceso a tu organización. Cada persona debe habilitar la autenticación de dos factores para poder aceptar tu invitación. - -### Administrar direcciones IP permitidas para organizaciones en su cuenta de empresa - -Los propietarios de empresa pueden restringir el acceso a los activos que pertenezcan a las organizaciones dentro de la cuenta empresarial mediante la configuración de una lista de direcciones IP permitidas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %} - -{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %} - -{% data reusables.identity-and-permissions.ip-allow-lists-enable %} - -También puedes configurar las direcciones IP permitidas para una organización individual. Para obtener más información, consulta "[Administrar las direcciones IP permitidas en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization)". - -#### Agregar una dirección IP permitida - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} -{% data reusables.identity-and-permissions.ip-allow-lists-add-description %} -{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} - -#### Habilitar direcciones IP permitidas - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -3. En "IP allow list" (Lista de permisos de IP), seleccione **Enable IP allow list** (Habilitar lista de permisos de IP). ![Realizar una marca de verificación para permitir direcciones IP](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png) -4. Haz clic en **Save (Guardar)**. - -#### Editar una dirección IP permitida - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} -{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} -{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %} -8. Da clic en **Actualizar**. - -#### Eliminar una dirección IP permitida - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} -{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %} - -#### Utilizar {% data variables.product.prodname_actions %} con un listado de direcciones IP permitidas - -{% data reusables.github-actions.ip-allow-list-self-hosted-runners %} - -### Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta de empresa - -{% 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](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)". - -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. Una vez que habilitas SAML SSO para tu cuenta de empresa, SAML SSO se habilita de manera predeterminada para todas las organizaciones que sean propiedad de tu cuenta de empresa. 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. - -{% data reusables.saml.about-saml-access-enterprise-account %}Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un usuario a tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". - -{% data reusables.saml.saml-supported-idps %} - -{% data reusables.scim.enterprise-account-scim %}Si no estás participando en el beta privado, SCIM no será compatible para las cuentas empresariales. Para obtener más información, consulta la sección "[Administrar el aprovisionamiento de usuarios para las organizaciones en tu cuenta empresarial](#managing-user-provisioning-for-organizations-in-your-enterprise-account)". - -{% note %} - -**Nota:** Habilitar la autenticación con inicio de sesión único de SAML para tu cuenta de empresa reemplazará cualquier configuración de SAML existente al nivel de la organización. - -{% endnote %} - -Para obtener información más detallada sobre cómo habilitar el SAML utilizando Okta, consulta la sección "[Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta](/github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta). - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. En "inicio de sesión único SAML", selecciona **Habilitar 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. También puedes escribir tu nombre de emisor de SAML en el campo **Emisor**. Esto verifica 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) -9. Para verificar la integridad de las solicitudes de tu emisor de SAML, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. Luego, en los menús desplegables Método de firma y Método de resumen, elige el algoritmo de hash que usa 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) -10. Antes de habilitar SAML SSO para tu empresa, haz clic en **Probar la configuración de SAML** para asegurarte de que la información que has ingresado sea correcta. ![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) -11. Haz clic en **Save (Guardar)**. - -### Administrar el aprovisionamiento de usuarios para las organizaciones en tu cuenta empresarial - -Los propietarios de las empresas pueden administrar las membrecías de la organización en una cuenta empresarial directamente desde un proveedor de identidad (IdP). - -{% data reusables.enterprise-accounts.user-provisioning-release-stage %} - -{% data reusables.saml.about-user-provisioning-enterprise-account %} - -{% data reusables.scim.enterprise-account-scim %} Opcionalmente, puedes habilitar el aprovisionamiento de SAML y, por separado, el desaprovisionamiento. - -Si configuras SCIM en tu IdP, cada que hagas cambios a una membrecía grupal en tu IdP, éste hará una llamada de SCIM a {% data variables.product.prodname_dotcom %} para actualizar la membrecía correspondiente de la organización. Si habilitas el aprovisionamiento de SAML, cada que un miembro de la empresa acceda a un recurso que protege tu configuración de SAML en la cuenta de la empresa, esa aserción de SAML activará el aprovisionamiento. - -Para cada llamada de SCIM o aserción de SAML, {% data variables.product.product_name %} verificará los grupos de IdP a los cuales pertenece el usuario y realizará las siguientes operaciones: - -- Si el usuario es un miembro de un grupo de IdP que corresponda a una organización que pertenezca a tu cuenta empresarial, y el usuario no es actualmente miembro de dicha organización, agrégalo a la organización (aserción de SAML) o envía una invitación por correo electrónico al usuario para que se una a una organización (llamado de SCIM). -- Cancela cualquier invitación que exista para que el usuario se una a la organización que pertenece a tu cuenta empresarial. - -Para cada llamada de SCIM y, en caso de que habilites el desaprovisionamiento de SAML, en cada aserción de SAML, {% data variables.product.product_name %} también realizará la siguiente operación: - -- Si el usuario no es un miembro de un grupo de IdP que corresponde a una organización que pertenezca a tu cuenta empresarial y éste es un miembro actual de dicha organización, elimina al usuario de la organización. - -Si el desaprovisionamiento eleimina al último propietario que queda en una organización, ésta quedará sin propietario. Los propietarios de las empresas pueden asumir la propiedad de las organizaciones sin propietario. Para obtener más información, consulta la sección "[Administrar las organizaciones sin dueño en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account)". - -Para habilitar el aprovisionamiento de usuarios en tu cuenta empresarial utilizandoOkta, consulta la sección "[Configurar el inicio de sesión único de SAML y SCIM para tu cuenta empresarial utilizando Okta](/github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)". - -### Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial - -Los propietarios de las empresas pueden habilitar la sincronización de equipos entre un IdP y {% data variables.product.product_name %} para permitir a los propietarios de las organizaciones y a los mantenedores de equipo conectar a los equipos en las organizaciones que pertenezcan a tu cuenta empresarial con los grupos de IdP. - -{% data reusables.identity-and-permissions.about-team-sync %} - -Puedes utilizar la sincronización de equipos con tu cuenta empresarial con Azure AD. - -{% data reusables.identity-and-permissions.sync-team-with-idp-group %} - -{% data reusables.identity-and-permissions.team-sync-disable %} - -También puedes configurar y administrar la sincronización de equipos para una organización individual. Para obtener más información, consulta la sección [Administrar la sincronización de equipos para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization)". - -#### Prerrequisitos - -Antes de que puedas habilitar la sincronización de equipos para tu cuenta empresarial: - - Tú o tu administrador de Azure AD debe ser un administrador global o un administrador de Rol Privilegiado en Azure AD. - - Debes habilitar 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 "[Habilitar el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial](#enabling-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)". - -#### Administrar la sincronización de equipos para Azure AD - -{% data reusables.identity-and-permissions.team-sync-azure-permissions %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.identity-and-permissions.team-sync-confirm-saml %} -{% data reusables.identity-and-permissions.enable-team-sync-azure %} -{% data reusables.identity-and-permissions.team-sync-confirm %} -7. Revisa la información del organismo proveedor de identidad al cual quieres conectar tu cuenta empresarial, posteriormente, da clic en **Aprovar**. ![Solicitud pendiente para habilitar la sincronización de equipo a un locatario IdP específico con la opción de aprobar o cancelar la solicitud](/assets/images/help/teams/approve-team-synchronization.png) -8. Para inhabilitar la sincronización de equipos, da clic en **Inhabilitar la sincronización de equipos**. ![Inhabilita la sincronización de equipo](/assets/images/help/teams/disable-team-synchronization.png) - -### Administrar las autoridades de los certificados de SSH de tu cuenta de empresa - -Los propietarios de empresa pueden agregar y eliminar las autoridades de los certificados de SSH de una cuenta de empresa (CA). - -Al agregar una CA de SSH a tu cuenta de empresa, puedes permitir que los miembros de cualquier organización que sea propiedad de tu cuenta de empresa acceda a los repositorios de esa organización usando los certificados de SSH proporcionados por ti. {% data reusables.organizations.can-require-ssh-cert %}Para obtener más información, consulta "[Acerca de las autoridades de certificados de SSH](/articles/about-ssh-certificate-authorities)". - -#### Agregar una autoridad de certificado de SSH - -{% data reusables.organizations.add-extension-to-cert %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.organizations.new-ssh-ca %} -{% data reusables.organizations.require-ssh-cert %} - -#### Eliminar una autoridad de certificado de SSH - -La eliminación de un CA no se puede deshacer. Si deseas usar la misma CA en el futuro, deberás cargarla nuevamente. - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.settings-tab %} -{% data reusables.enterprise-accounts.security-tab %} -{% data reusables.organizations.delete-ssh-ca %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-team-policies-in-your-enterprise-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-team-policies-in-your-enterprise-account.md deleted file mode 100644 index ee2b90c9f5..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/enforcing-team-policies-in-your-enterprise-account.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Hacer cumplir políticas de equipo en tu cuenta de empresa -intro: Los propietarios de empresa pueden hacer cumplir determinadas políticas de equipo para todas las organizaciones que son propiedad de una cuenta de empresa o pueden permitir que estas políticas se establezcan en cada organización. -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/enforcing-team-settings-for-organizations-in-your-business-account/ - - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account/ - - /articles/enforcing-team-policies-in-your-enterprise-account - - /github/setting-up-and-managing-your-enterprise-account/enforcing-team-policies-in-your-enterprise-account -versions: - free-pro-team: '*' ---- -### Hacer cumplir una política para los debates de equipo - -En todas las organizaciones que son propiedad de tu cuenta de empresa, puedes habilitar o inhabilitar los debates de equipo o permitir que los propietarios administren este parámetro a nivel de la organización. Para obtener más información, consulta [Acerca de los debates de equipo](/articles/about-team-discussions)". - -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.policies-tab %} -3. En la barra lateral de la cuenta de empresa, haz clic en **Equipos**. ![Pestaña Equipos en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/settings-teams-tab.png) -4. En "Debates de equipo", revisa la información sobre cómo modificar los parámetros. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. En "Debates de equipo", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de debate de equipo](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/index.md deleted file mode 100644 index 7de11472b2..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Establecer políticas para organizaciones en tu cuenta de empresa -product: '{% data reusables.gated-features.enterprise-accounts %}' -redirect_from: - - /articles/setting-policies-for-organizations-in-your-enterprise-account -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /enforcing-repository-management-policies-in-your-enterprise-account - - /enforcing-project-board-policies-in-your-enterprise-account - - /enforcing-team-policies-in-your-enterprise-account - - /enforcing-security-settings-in-your-enterprise-account - - /configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta - - /enforcing-a-policy-on-dependency-insights-in-your-enterprise-account - - /enforcing-github-actions-policies-in-your-enterprise-account ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md deleted file mode 100644 index f21965c786..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Acerca del perfil de tu organización -intro: La página del perfil de tu organización muestra la información básica acerca de tu organización. -redirect_from: - - /articles/about-your-organization-s-profile - - /articles/about-your-organizations-profile - - /github/setting-up-and-managing-your-github-profile/about-your-organizations-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles ---- -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 en la parte superior de la página. - -{% if currentVersion == "free-pro-team@latest" %}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 "[Verificar el dominio de tu organización](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain)." - -![Muestra de página de perfil de una organización verificada](/assets/images/help/profile/org_profile_verified.png) -{% else %} -![Muestra de la página de perfil de una organización](/assets/images/help/profile/org_profile.png) -{% endif %} - -### Leer más - -- "[Acerca de las organizaciones](/github/setting-up-and-managing-organizations-and-teams/about-organizations)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md deleted file mode 100644 index 32f1f71aa9..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Acerca de tu perfil -intro: 'La página de tu perfil le cuenta a las personas la historia de tu trabajo a través de los repositorios en los que te interesas, las colaboraciones que has realizado y las conversaciones que has tenido.' -redirect_from: - - /articles/viewing-your-feeds/ - - /articles/profile-pages/ - - /articles/about-your-profile - - /github/setting-up-and-managing-your-github-profile/about-your-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles ---- -Puedes agregar información personal acerca de ti mismo en tu biobiografía, como lugares en los que has trabajado previamente, proyectos con los que has colaborado o intereses que tengas que a otras personas les pueda interesar conocer sobre tí. Para obtener más información, consulta "[Agregar una biografía en tu perfil](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - -{% data reusables.profile.profile-readme %} - -![Archivo de README del perfil que se muestra en éste](/assets/images/help/repository/profile-with-readme.png) - -{% endif %} - -Las personas que visitan tu perfil ven una cronología de tu actividad de colaboración, como las propuestas y las solicitudes de extracción que has abierto, las confirmaciones que has realizado y las solicitudes de extracción que has revisado. Puedes elegir mostrar solo las contribuciones públicas o también incluir las contribuciones privadas, anonimizadas. Para obtener más información, consulta "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" o "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". - -También pueden ver: - -- Repositorios y gists que te pertenezcan o en los que contribuyas. Puedes exhibir tus mejores obras si fijas los repositorios y los gists a tu perfil. Para obtener más información, consulta "[A nclar elementos a tu perfil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)". -- Repositorios que has destacado. Para obtener más información, consulta "[Guardar repositorios con estrellas](/articles/saving-repositories-with-stars/)". -- Una descripción general de tu actividad en organizaciones, repositorios y equipos en los que eres más activo. Para obtener más información, consulta la sección "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)".{% if currentVersion == "free-pro-team@latest" %} -- Las insignias que anuncian tu particiapción en los programas como {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, oen el Programa de Desarrollador de {% data variables.product.company_short %}. -- Si estás usando {% data variables.product.prodname_pro %}. Para obtener más información, consulta la sección "[Personalizar tu perfil](/articles/personalizing-your-profile)".{% endif %} - -También puedes establecer un estado en tu perfil para brindar información sobre tu disponibilidad. Para obtener más información, consulta "[Configurar un estado](/articles/personalizing-your-profile/#setting-a-status)". - -### Leer más - -- "[¿Cómo configuro mi foto de perfil?](/articles/how-do-i-set-up-my-profile-picture)" -- "[Anclar repositorios a tu perfil](/articles/pinning-repositories-to-your-profile)" -- "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Ver las contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md deleted file mode 100644 index 074be54d84..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Personalizar tu perfil -intro: Puedes personalizar tu perfil para que los demás usuarios puedan comprender mejor quién eres y qué trabajo realizas. -redirect_from: - - /articles/customizing-your-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles -children: - - /about-your-profile - - /about-your-organizations-profile - - /personalizing-your-profile - - /managing-your-profile-readme - - /pinning-items-to-your-profile ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md deleted file mode 100644 index 08468d6d1f..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Administrar el README de tu perfil -intro: 'Puedes agregar un README a tu perfil de {% data variables.product.prodname_dotcom %} para que otras personas sepan sobre ti.' -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' -topics: - - Profiles -redirect_from: - - /github/setting-up-and-managing-your-github-profile/managing-your-profile-readme ---- -### Acerca del README de tu perfil - -Puedes compartir información acerca de ti mismo con la comunidad en {% data variables.product.prodname_dotcom %} si creas un README para tu perfil. {% data variables.product.prodname_dotcom %} muestra el README de tu perfil al inicio de tu página de perfil. - -Tú decides qué información incluir en el README de tu perfil, así que tienes todo el contro sobre cómo te presentas con los demás en {% data variables.product.prodname_dotcom %}. Aquí tienes algunos ejemplos de información que puede ser interesante, divertida o útil para los visitantes que lean el README en tu perfil. - -- Una sección de "sobre mí" que describa tu trabajo y tus intereses -- Las contribuciones de las cuales estás orgulloso y el contexto de las mismas -- Orientación para obtener ayuda en las comunidades en las que estás involucrado - -![Archivo de README del perfil que se muestra en éste](/assets/images/help/repository/profile-with-readme.png) - -Puedes formatear el texto e incluir emojis, imágenes y GIFs en el README de tu perfil 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)". - -### Prerrequisitos - -GitHub mostrará el README de tu perfil en tu página de perfil si cuentas con todo lo siguiente. - -- Has creado un repositorio con un nombre que empate con tu nombre de usuario de {% data variables.product.prodname_dotcom %}. -- Este repositorio es público. -- Este repositorio contiene un archivo de nombre README.md en su raíz. -- El archivo README.md contiene cualquier tipo de contenido. - -{% note %} - -**Nota**: Si creaste un repositorio público con el mismo nombre de tu nombre de usuario antes de julio del 2020, {% data variables.product.prodname_dotcom %} no mostrará automáticamente el README de tu repositorio en tu perfil. Puedes compartir manualmente el README de tu repositorio en tu perfil si te diriges al repositorio en {% data variables.product.prodname_dotcom_the_website %} y das clic en **Compartir en mi perfil**. - -![Botón para compartir el README en el perfil](/assets/images/help/repository/share-to-profile.png) - -{% endnote %} - -### Agregar un README de perfil - -{% data reusables.repositories.create_new %} -2. Debajo de "Nombre de repositorio", teclea un nombre de repositorio que empate con tu nombre de usuario de {% data variables.product.prodname_dotcom %}. Por ejemplo, si tu nombre de usuario es "octocat", el nombre de repositorio debe ser "octocat". ![Campo de nombre de repositorio que empata con el nombre de usuario](/assets/images/help/repository/repo-username-match.png) -3. También puedes agregar una descripción de tu repositorio. Por ejemplo, "Mi repositorio personal". ![Campo para ingresar una descripción para el repositorio](/assets/images/help/repository/create-personal-repository-desc.png) -4. Selecciona **Público**. ![Botón radial para seleccionar la visibilidad con la opción de público seleccionada](/assets/images/help/repository/create-personal-repository-visibility.png) -{% data reusables.repositories.initialize-with-readme %} -{% data reusables.repositories.create-repo %} -7. Sobre la barra lateral derecha, da clic en **Editar README**. ![Botón para editar el archivo README](/assets/images/help/repository/personal-repository-edit-readme.png) - - El archivo de README que se ha generado está pre-llenado con una plantilla para que te inspires en completarlo. ![Archivo README con la plantilla pre-llenada](/assets/images/help/repository/personal-repository-readme-template.png) - -### Eliminar un README de perfil - -El README de tu perfil se eliminará de tu perfil de {% data variables.product.prodname_dotcom %} si sucede cualquiera de los siguientes escenarios: - -- El archivo README está vacío o no existe. -- El repositorio es privado. -- El nombre del repositorio no empata con tu nombre de usuario. - -The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. Para encontrar los pasos de cómo hacer tu repositorio privado, consulta la sección ["Cambiar la visibilidad de un repositorio".](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility) - -### Leer más - -- [Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md deleted file mode 100644 index 60ac06157b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: Personalizar tu perfil -intro: 'Puedes compartir información sobre tI con otros usuarios de {% data variables.product.product_name %} al configurar una imagen de perfil y agregar una biografía a tu perfil.' -redirect_from: - - /articles/adding-a-bio-to-your-profile/ - - /articles/setting-your-profile-picture/ - - /articles/how-do-i-set-up-my-profile-picture/ - - /articles/gravatar-problems/ - - /articles/how-do-i-set-up-my-avatar/ - - /articles/personalizing-your-profile - - /github/setting-up-and-managing-your-github-profile/personalizing-your-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles ---- -### Cambiar tu imagen de perfil - -Tu imagen de perfil ayuda a identificarte dentro de {% data variables.product.product_name %} en solicitudes de extracción, comentarios, páginas de contribuciones y gráficos. - -Cuando te registras en una cuenta, {% data variables.product.product_name %} te proporciona un "identicon" generado al azar. [Tu identicon](https://github.com/blog/1586-identicons) se genera a partir de un hash de tu ID de usuario, por lo que no hay manera de controlar su color o patrón. Puedes reemplazar tu identicon con una imagen que te represente. - -{% tip %} - -**Sugerencia**: la imagen de tu perfil debería ser un archivo PNG, JPG, o GIF menor de 1 MB de tamaño. Para mostrar la mejor calidad, recomendamos mantener la imagen en alrededor de 500 por 500 píxeles. - -{% endtip %} - -#### Configurar una imagen de perfil - -{% data reusables.user_settings.access_settings %} -2. Dentro de **Profile Picture (Imagen de perfil)**, haz clic en {% octicon "pencil" aria-label="The edit icon" %} **Edit (Editar)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-photo.png) -3. Haz clic en **Upload a photo... (Cargar una foto...)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-picture-options.png) -3. Recorta tu imagen. Cuando hayas terminado, haz clic en **Set new profile picture (Configurar nueva imagen de perfil)**. ![Recortar foto cargada](/assets/images/help/profile/avatar_crop_and_save.png) - -#### Restablecer tu imagen de perfil al identicon - -{% data reusables.user_settings.access_settings %} -2. Dentro de **Profile Picture (Imagen de perfil)**, haz clic en {% octicon "pencil" aria-label="The edit icon" %} **Edit (Editar)**. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-photo.png) -3. Para regresar a tu identicon, haz clic en **Remove photo (Eliminar foto)**. Si tu dirección de correo electrónico está asociada con [Gravatar](https://en.gravatar.com/), no puedes regresar a tu identicon. Haz clic en **Revert to Gravatar (Revertir a Gravatar)** en su lugar. ![Editar imagen de perfil](/assets/images/help/profile/edit-profile-picture-options.png) - -### Cambiar tu nombre de perfil - -Puedes cambiar el nombre que se muestra en tu perfil. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %}Este nombre también se puede mostrar al lado de los comentarios que haces en los repositorios privados propiedad de 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)."{% 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) - -### Agregar una biografía en tu perfil - -Agrega una biografía a tu perfil para compartir información sobre ti con otros usuarios de {% data variables.product.product_name %}. Con la ayuda de [@mentions](/articles/basic-writing-and-formatting-syntax) y emoji, puedes incluir información sobre dónde estás trabajando actualmente o dónde trabajaste anteriormente, qué tipo de trabajo realizas, o incluso qué tipo de café tomas. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} - -Para encontrar un formato más largo y una forma más prominente de mostrar la información acerca de ti mismo, también puedes utilizar un README de perfil. Para obtener más información sobre el README de perfil, consulta la sección "[Administrar el README de tu perfil](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)". - -{% endif %} - -{% note %} - -**Nota:** Si tienes habilitada la sección de resumen de la actividad para tu perfil y @mencionas a una organización a la que pertenezcas en tu biografía de perfil, esta organización se presentará primero en tu resumen de actividad. Para obtener más información, consulta "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)." - -{% endnote %} - -{% data reusables.user_settings.access_settings %} -2. Dentro de **Bio (Biografía)**, agrega el contenido que deseas mostrar en tu perfil. El campo biografía tiene un límite de 160 caracteres. ![Actualizar biografía en el perfil](/assets/images/help/profile/bio-field.png) - - {% tip %} - - **Sugerencia:** cuando mencionas una organización, únicamente aquellas de las que eres miembro se completarán automáticamente. Incluso puedes mencionar organizaciones de las que no eres miembro, como un antiguo empleador, pero el nombre de la organización no se completará automáticamente. - - {% endtip %} - -3. Haz clic en **Update profile (Actualizar perfil)**. ![Botón Actualizar perfil](/assets/images/help/profile/update-profile-button.png) - -### Configurar un estado - -Puedes configurar un estado para mostrar información acerca de tu disponibilidad actual en {% data variables.product.product_name %}. Tu estado se mostrará: -- en tu página de perfil {% data variables.product.product_name %}. -- cuando las personas se desplacen sobre tu nombre de usuario o avatar en {% data variables.product.product_name %}. -- en una página de equipo en un equipo del cual eres un miembro. Para obtener más información, consulta "[Acerca de equipos](/articles/about-teams/#team-pages)." -- en el tablero de la organización en una organización de la cual eres miembro. Para obtener más información, consulta "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard/)." - -Cuando configuras tu estado, también puedes permitir que las personas sepan que tienes disponibilidad limitada en {% data variables.product.product_name %}. - -![El nombre de usuario mencionado muestra una nota de "busy" (ocupado) al lado del nombre de usuario](/assets/images/help/profile/username-with-limited-availibilty-text.png) - -![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. - -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) -3. De manera opcional, para configurar un estado de emoji, haz clic en el ícono sonriente y selecciona un emoji de la lista. ![Botón para seleccionar un estado de emoji](/assets/images/help/profile/select-emoji-status.png) -4. Como alternativa, si te gustaría compartir que tienes disponibilidad limitada, selecciona "Busy" (Ocupado). ![Opción ocupado seleccionada en las opciones de Editar estado](/assets/images/help/profile/limited-availability-status.png) -5. Utiliza el menú desplegable **Clear status (Borrar estado)** y selecciona cuándo deseas que venza tu estado. Si no deseas seleccionar un vencimiento de estado, mantendrás tu estado hasta que lo borres o edites. ![Menú desplegable para elegir cuando vence tu estado](/assets/images/help/profile/status-expiration.png) -6. Utiliza el menú desplegable y haz clic en la organización para la que deseas que tu estado sea visible. Si no seleccionas una organización, tu estado será público. ![Menú desplegable para elegir para quién es visible tu estado](/assets/images/help/profile/status-visibility.png) -7. Haz clic en **Set status (Configurar estado)**. ![Botón para establecer el estado](/assets/images/help/profile/set-status-button.png) - -{% if currentVersion == "free-pro-team@latest" %} -### Mostrar las insignias en tu perfil - -Cuando participas en algunos programas, {% data variables.product.prodname_dotcom %} muestra automáticamente una insignia en tu perfil. - -| Insignia | Programa | Descripción | -| --------------------------------------------------------------- | ------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% octicon "north-star" aria-label="The North Star icon" %} | **{% data variables.product.prodname_arctic_vault %} Colaborador** | Si eres el autor de cualquier confirmación en la rama predeterminada de un repositorio que se archivó en el programa del 2020 del Vaúl del Ártico, obtendrás una insignia de colaborador de {% data variables.product.prodname_arctic_vault %} en tu perfil. Para obtener más información sobre el programa, consulta la sección [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). | -| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Miembro del Programa de Desarrolladores** | Si eres un miembro registrado del Programa de Desarrolladores de GitHub, crear una app con la API de GitHub te otorgará una insignia de Miembro del Programa de Desarrolladores en tu perfil. Para obtener más información sobre el Programa de Desarrolladores de Github, consulta la sección [Desarrolladores de GitHub](/program/). | -| {% octicon "heart-fill" aria-label="The GitHub Sponsor icon" %} | **Patrocinador de GitHub** | Si patrocinaste a un colaborador de código abierto a través de {% data variables.product.prodname_sponsors %} obtendrás una insignia de Patrocinador de GitHub en tu perfil. Para obtener más información, consulta la sección "[Patrocinar colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)". | -| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | Si utilizas {% data variables.product.prodname_pro %} obtendrás una insignia de PRO en tu perfil. Para obtener más información acerca de {% data variables.product.prodname_pro %}, consulta los productos de "[{% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products#github-pro)." | - -### Inhabilitar las insignias en tu perfil - -Puedes inhabilitar algunas de las insignias de los programas de {% data variables.product.prodname_dotcom %} en los cuales participas, incluyendo las insignias de PRO y de {% data variables.product.prodname_arctic_vault %}. - -{% data reusables.user_settings.access_settings %} -2. Debajo de "Configuración del perfil", deselecciona la insignia que quieres inhabilitar. ![Casilla para dejar de mostrar una insignia en tu perfil](/assets/images/help/profile/display-pro-badge-checkbox.png) -3. Haz clic en **Update preferences (Actualizar preferencias)**. - -{% endif %} - -### Leer más - -- "[Acerca de tu perfil](/articles/about-your-profile)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md deleted file mode 100644 index 3da95013cc..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Anclar elementos a tu perfil -intro: 'Puedes anclar {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.16" %}gist y {% endif %}repositorios a tu perfil para que otras personas puedan rápidamente ver tu mejor trabajo.' -redirect_from: - - /articles/pinning-repositories-to-your-profile/ - - /articles/pinning-items-to-your-profile - - /github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Profiles ---- -Puedes anclar un repositorio público si eres propietario del repositorio o has realizado contribuciones al repositorio. Las confirmaciones de las bifurcaciones no cuentan como contribuciones, por ello no puedes anclar una bifurcación de la que no eres propietario. Para obtener más información, consulta "[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" - -You can pin any public gist you own. - -Los elementos fijados incluyen información importante sobre ellos, como el número de estrellas que ha recibido el repositorio, o algunas de las primeras líneas de un gist. Una vez que hayas anclado elementos a tu perfil, la sección "Pinned" (Anclados) reemplaza a la sección "Popular repositories" (Repositorios populares) en tu perfil. - -Puedes reordenar los elementos en la sección "Anclados". En el ángulo superior derecho de un elemento anclado, haz clic en {% octicon "grabber" aria-label="The grabber symbol" %} y arrastra el anclado a una nueva ubicación. - -{% data reusables.profile.access_profile %} -2. En la sección "Repositorios populares" o "Anclados", haz clic en **Customize your pins (Personalizar tus anclados)**. ![Botón para personalizar tus elementos anclados](/assets/images/help/profile/customize-pinned-repositories.png) -3. Para mostrar una lista de búsqueda de elementos por anclar, selecciona "Repositories" (Repositorios), "Gists" o ambos. ![Casillas de verificación para seleccionar los tipos de elementos a mostrar](/assets/images/help/profile/pinned-repo-picker.png) -4. Como opción, para que sea más sencillo encontrar un elemento específico, en el campo de filtro, escribe el nombre de un usuario, una organización, un repositorio o un gist. ![Filtrar elementos](/assets/images/help/profile/pinned-repo-search.png) -5. Selecciona una combinación de hasta seis repositorios o gists para mostrar. ![Seleccionar elementos](/assets/images/help/profile/select-items-to-pin.png) -6. Haz clic en **Save pins (Guardar anclados)**. ![Botón guardar elementos anclados](/assets/images/help/profile/save-pinned-repositories.png) - -### Leer más - -- "[Acerca de tu perfil](/articles/about-your-profile)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/index.md deleted file mode 100644 index d265d6ae00..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Configurar y administrar tu perfil de GitHub -shortTitle: Perfiles -redirect_from: - - /categories/setting-up-and-managing-your-github-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles -children: - - /customizing-your-profile - - /managing-contribution-graphs-on-your-profile ---- -### Índice diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md deleted file mode 100644 index 4756d1f807..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Administrar los gráficos de contribución en tu perfil -intro: 'Tus contribuciones, incluidas las confirmaciones de cambios, las solicitudes de extracción propuestas y las propuestas abiertas, se muestran en tu perfil para que las personas puedan ver fácilmente el trabajo que has realizado.' -redirect_from: - - /articles/managing-contribution-graphs-on-your-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles -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 - - /why-are-my-contributions-not-showing-up-on-my-profile - - /troubleshooting-commits-on-your-timeline ---- - diff --git a/translations/es-XL/content/github/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-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md deleted file mode 100644 index adaf5a9767..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Divulgar u ocultar tus contribuciones privadas en tu perfil -intro: 'Tu perfil {% data variables.product.product_name %} muestra un gráfico de las contribuciones a tu repositorio durante el último año. Puedes elegir mostrar actividad de forma anónima de los repositorios privados además de la actividad que se muestra de los repositorios públicos.' -redirect_from: - - /articles/publicizing-or-hiding-your-private-contributions-on-your-profile - - /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles ---- -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)". - -### 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: - - 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) - -### 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)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile.md deleted file mode 100644 index 69a114abbd..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Enviar tus contribuciones de GitHub Enterprise Server a tu perfil de GitHub.com -intro: 'Puedes resaltar tu trabajo en {% data variables.product.prodname_ghe_server %} 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 -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Profiles ---- -{% 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 {% data variables.product.prodname_ghe_server %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}, un administrador de sitio debe habilitar {% data variables.product.prodname_github_connect %} y permitir que se compartan contribuciones entre los entornos. Para obtener más información, contacta a tu administrador del sitio {% data variables.product.prodname_ghe_server %}. - -{% endnote %} - -Tu perfil de {% data variables.product.prodname_dotcom_the_website %} muestra los recuentos de contribuciones de {% data variables.product.prodname_ghe_server %} durante los últimos 90 días. Los recuentos de contribuciones de {% data reusables.github-connect.sync-frequency %} de {% data variables.product.prodname_ghe_server %} se consideran contribuciones privadas. Los detalles de confirmación mostrarán únicamente los recuentos de contribuciones y que estas contribuciones se realizaron en {% data variables.product.prodname_ghe_server %}. - -Si los usuarios finales de {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %} desean que sus recuentos de contribuciones privadas sean públicas, pueden divulgar sus recuentos de contribuciones privadas. 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/)." - -{% data reusables.github-connect.access-dotcom-and-enterprise %} -{% data reusables.github-connect.access-profile-settings %} -{% data reusables.github-connect.github-connect-tab-user-settings %} -{% data reusables.github-connect.connect-dotcom-and-enterprise %} -{% data reusables.github-connect.authorize-connection %} -6. 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-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md deleted file mode 100644 index 1e8c769c60..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Mostrar un resumen de tu actividad en tu perfil -intro: Puedes habilitar la sección de resumen de actividad en tu perfil para darle a los observadores más contexto acerca de los tipos de contribuciones que realizas. -redirect_from: - - /articles/showing-an-overview-of-your-activity-on-your-profile - - /github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles ---- -{% data reusables.profile.activity-overview-summary %} Para obtener más información, consulta "[Ver contribuciones en tu perfil](/articles/viewing-contributions-on-your-profile)." - -![Sección de resumen de actividad en el perfil](/assets/images/help/profile/activity-overview-section.png) - -{% data reusables.profile.access_profile %} -2. Arriba de tu gráfica de contribuyentes, utiliza el menú desplegable de **configuración de contribuciones** y selecciona o deselecciona **Resumen de la actividad**. ![Habilita el resumen de actividad desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/activity-overview.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline.md deleted file mode 100644 index a923d9f8a8..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Confirmaciones de solución de problemas en tu cronología -intro: 'Puedes ver los detalles de las confirmaciones desde tu cronología del perfil. Si no ves las confirmaciones que esperas en tu perfil o no puedes encontrar los detalles de confirmaciones desde la página de tu perfil, puede que sean diferentes la fecha de la confirmación y el autor de la confirmación.' -redirect_from: - - /articles/troubleshooting-commits-on-your-timeline - - /github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles ---- -### Comportamiento esperado para ver detalles de confirmaciones - -En la cronología de la página de tu perfil, puedes hacer clic en el número de confirmaciones al lado de un repositorio específico para ver más detalles acerca de tus confirmaciones desde ese período de tiempo, incluida una diferencia de cambios específicos hechos en un repositorio. - -![Enlace de confirmación en la cronología del perfil](/assets/images/help/profile/commit-link-on-profile-timeline.png) - -![Detalles de confirmaciones](/assets/images/help/commits/commit-details.png) - -### Detalles de confirmaciones faltantes de las confirmaciones de tu cronología - -Si haces clic en un enlace de confirmación desde tu página de perfil y no ves todas las confirmaciones esperadas en la página de confirmaciones del repositorio, es posible que el historial de confirmaciones de Git se haya rescrito y que el autor de la confirmación y la fecha de la confirmación sean diferentes. - -![Página del repositorio con el mensaje que dice "no commits found for octocat" (no se encontraron confirmaciones para octocat)](/assets/images/help/repository/no-commits-found.png) - -### Cómo utiliza GitHub la fecha de autor y la fecha de confirmación de Git - -En Git, la fecha de autor es cuando alguna persona crea por primera vez una confirmación con `git commit`. La fecha de la confirmación es idéntica a la fecha de autor, a menos que alguna persona cambie la fecha de confirmación utilizando `git commit --amend`, un empuje forzado, una rebase u otro comando de Git. - -En tu página de perfil, la fecha de autor se utiliza para calcular cuándo se realizó una confirmación. Por otro lado, en un repositorio, la fecha de confirmación se utiliza para calcular cuándo se hizo una confirmación en el repositorio. - -La mayoría de las veces, la fecha de autor y la fecha de confirmación son las mismas, pero puedes notar que tu secuencia de confirmaciones no funciona si se modifica el historial de confirmaciones. Para obtener más información, consulta "[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" - -### Ver detalles de confirmaciones faltantes de las confirmaciones de tu cronología - -Puedes utilizar el comando `git show` con la marca `--pretty=fuller` para comprobar si la fecha de autor de la confirmación y la fecha de confirmación son diferentes. - -```shell -$ git show Your commit SHA number --pretty=fuller -commit Your commit SHA number -Author: octocat user email -AuthorDate: Wed Jul 13 02:02:30 2016 +0900 -Commit: Sally Johnson user email -CommitDate: Wed Jul 20 06:25:08 2016 +0900 -``` - -Si la fecha de autor y de confirmación son diferentes, puedes cambiar de forma manual la fecha de confirmación en la URL para ver los detalles de la confirmación. - -Por ejemplo: -- Esta URL utiliza la fecha de autor del `2016-07-13`: - - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-13T00:00:00Z&until=2016-07-13T23:59:59Z` -- Esta URL utiliza la fecha de confirmación del `2016-07-19`: - - `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2016-07-19T00:00:00Z&until=2016-07-19T23:59:59Z` - -Cuando abres la URL con la fecha de confirmación modificada, puedes ver los detalles de la confirmación. - -![Detalles de confirmaciones](/assets/images/help/commits/commit-details.png) - -### Confirmaciones esperadas faltantes en tu cronología - -Si no estás viendo las confirmaciones esperadas en tu cronología, es posible que el historial de confirmaciones de Git se haya rescrito y que la fecha de autor de la confirmación y la fecha de confirmación sean diferentes. Para conocer otras posibilidades, consulta "[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md deleted file mode 100644 index c5a0570a71..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: Ver contribuciones en tu perfil -intro: 'Tu perfil {% data variables.product.product_name %} muestra tus repositorios anclados y el gráfico de las contribuciones de tu repositorio durante el último año.' -redirect_from: - - /articles/viewing-contributions/ - - /articles/viewing-contributions-on-your-profile-page/ - - /articles/viewing-contributions-on-your-profile - - /github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles ---- -Tu gráfico de contribución muestra la actividad de los repositorios públicos. Puedes elegir mostrar la actividad desde los repositorios públicos y privados, con detalles específicos de tu actividad en los repositorios privados de forma anónima. Para obtener más información, consulte "[Publicar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)." - -{% note %} - -**Nota:** las confirmaciones únicamente aparecerán en tu gráfico de contribución si has agregado [ la dirección de correo electrónico que utilizaste en tu configuración local de Git para configurar el correo electrónico de {% data variables.product.product_name %}](/articles/adding-an-email-address-to-your-github-account). Para obtener más información, consulta"[¿Por qué mis contribuciones no se muestran en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#you-havent-added-your-local-git-commit-email-to-your-profile)" - -{% endnote %} - -### Qué cuenta como una contribución - -En tu página de perfil, determinadas acciones cuentan como contribuciones: - -- Confirmar cambios en una rama por defecto de un repositorio o en la rama `gh-pages` -- Abrir una propuesta -- Proponer una solicitud de extracción -- Enviar una revisión de solicitud de extracción{% if currentVersion != "free-pro-team@latest" %} -- Confirmar como coautor en la rama por defecto de un repositorio o en la rama `gh-pages`{% endif %} - -{% data reusables.pull_requests.pull_request_merges_and_contributions %} - -### Repositorios populares - -Esta sección muestra tus repositorios con la mayor cantidad de observadores. Una vez que anclas repositorios [en tu perfil](/articles/pinning-repositories-to-your-profile), esta sección cambiará a "Pinned repositories" (Repositorios anclados). - -![Repositorios populares](/assets/images/help/profile/profile_popular_repositories.png) - -### Repositorios anclados - -Esta sección muestra hasta seis repositorios públicos y puede incluir tus repositorios y los repositorios a los que has contribuidos. Para ver fácilmente detalles importantes sobre los repositorios que has seleccionado para mostrar, cada repositorio en esta sección incluye un resumen del trabajo que se está realizando, la cantidad de [estrellas](/articles/saving-repositories-with-stars/) que el repositorio ha recibido y el lenguaje de programación principal utilizado en el repositorio. Para obtener más información, consulta "[Anclar repositorios en tu perfil](/articles/pinning-repositories-to-your-profile)." - -![Repositorios anclados](/assets/images/help/profile/profile_pinned_repositories.png) - -### Calendario de contribuciones - -Tu calendario de contribuciones muestra tu actividad de contribuciones. - -#### Ver contribuciones de momentos específicos - -- Haz clic en el cuadrado de un día para mostrar las contribuciones realizadas durante ese período de 24 horas. -- Presiona *Shift* y haz clic en el cuadrado de otro día para mostrar las contribuciones realizadas durante ese período de tiempo. - -{% note %} - -**Nota:** puedes seleccionar hasta un rango de un mes en tu calendario de contribuciones. Si seleccionas un período de tiempo más extenso, únicamente se mostrarán las contribuciones de un mes. - -{% endnote %} - -![Tu gráfico de contribuciones](/assets/images/help/profile/contributions_graph.png) - -#### Cómo se calculan los momentos de los eventos de las contribuciones - -Las marcas horarias se calculan de forma diferente para las confirmaciones y las solicitudes de extracción: -- **Confirmaciones** utilizan la información de la zona horaria en la marca de tiempo de la confirmación. Para obtener más información, consulta "[Solución de problemas con confirmaciones en tu cronología](/articles/troubleshooting-commits-on-your-timeline)." -- **Las solicitudes de extracción** y **las propuestas** abiertas en {% data variables.product.product_name %} utilizan la zona horaria de tu navegador. Aquellas abiertas a través de API utilizan la marca horaria o la zona horaria [especificada en la llamada de API](https://developer.github.com/changes/2014-03-04-timezone-handling-changes). - -### Resumen de la actividad - -{% data reusables.profile.activity-overview-summary %} Para obtener más información, consulta "[Mostrar un resumen de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)." - -![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/)." - -### Actividad de contribución - -La sección de actividad de contribuciones incluye una cronología detallada de tu trabajo, incluyendo confirmaciones que has realizado o de las que eres coautor, solicitudes de extracción que propusiste y propuestas que abriste. Puedes ver tus contribuciones en el tiempo al hacer clic en **Show more activity (Mostrar más actividad)** en la parte inferior de tu actividad de contribuciones o al hacer clic en el año que te interesa ver hacia la derecha de la página. Momentos importantes, como la fecha en que te uniste a una organización, propusiste tu primera solicitud de extracción o abriste una propuesta de alto perfil, se resaltan en tu actividad de contribuciones. Si no puedes ver determinados eventos en tu cronología, asegúrate de que todavía tengas acceso a la organización o al repositorio donde ocurrió el evento. - -![Filtro de tiempo de actividad de contribuciones](/assets/images/help/profile/contributions_activity_time_filter.png) - -### Ver contribuciones de {% data variables.product.product_location_enterprise %} en {% data variables.product.prodname_dotcom_the_website %} - -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)." - -### 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-XL/content/github/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-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md deleted file mode 100644 index f789f7afe5..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -title: ¿Por qué mis contribuciones no aparecen en mi perfil? -intro: '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.' -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 -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Profiles ---- -### Contribuciones que se cuentan - -#### Propuestas y solicitudes de extracción - -Las propuestas y las solicitudes de extracción aparecerán en tu gráfico de contribución si se abrieron en un repositorio independiente, no en una bifurcación. - -#### Confirmaciones -Las confirmaciones aparecerán en tu gráfico de contribución si cumplen **todas** las condiciones a continuación: -- La dirección de correo electrónico que se usa para las confirmaciones se asocia con tu cuenta {% data variables.product.product_name %}. -- Las confirmaciones se hicieron en un repositorio independiente, no en una bifurcación. -- Las confirmaciones se hicieron: - - En la rama predeterminada del repositorio - - En la rama `gh-pages` (para los repositorios con sitios de proyecto) - -Para obtener más información sobre los sitios del proyecto, consulta "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)" - -Asimismo, **al menos una** de las siguientes afirmaciones debe ser verdadera: -- Eres un colaborador en el repositorio o eres miembro de la organización a la que pertenece el repositorio. -- Has bifurcado el repositorio. -- Has abierto una solicitud de extracción o una propuesta en el repositorio. -- Has destacado el repositorio. -{% if currentVersion != "free-pro-team@latest" %} -### Razones comunes por las que las contribuciones no se cuentan - -{% data reusables.pull_requests.pull_request_merges_and_contributions %}{% endif %} - -#### La confirmación se hizo hace menos de 24 horas - -Después de hacer una confirmación que cumpla con los requisitos para contar como una contribución, es posible que debas esperar hasta 24 horas para que aparezca la contribución en tu gráfico de contribución. - -#### No has agregado tu correo electrónico de confirmación de Git a tu perfil - -Las confirmaciones deben realizarse con una dirección de correo electrónico que se haya agregado a tu cuenta de {% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}, o con la dirección de correo electrónico de `noreply` que te proporcionó {% data variables.product.product_name %} en la configuración de tu correo electrónico,{% endif %} para que aparezca en tu gráfica de contribuciones.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información acerca de las direcciones de correo electrónico de tipo `noreply`, consulta la sección "[Configurar tus direcciones de correo para las confirmaciones](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)".{% endif %} - -You can check the email address used for a commit by adding `.patch` to the end of a commit URL, e.g. https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: - -``` -From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001 -From: The Octocat -Date: Sun, 27 Apr 2014 15:36:39 +0530 -Subject: [PATCH] índice actualizado para un mejor mensaje de bienvenida -``` - -La dirección de correo electrónico en el campo `From: (Desde:)` es la dirección que se estableció en los [parámetros de configuración de Git local](/articles/set-up-git). En este ejemplo, la dirección de correo electrónico que se usó para la confirmación es `octocat@nowhere.com`. - -Si la dirección de correo electrónico que se usó para la confirmación no se agregó a tu perfil {% data variables.product.product_name %}, debes [agregar la dirección de correo electrónico](/articles/adding-an-email-address-to-your-github-account) a tu cuenta {% data variables.product.product_name %}. Tu gráfico de contribución será reconstruido automáticamente cuando agregues la nueva dirección. - -{% warning %} - -Las direcciones de correo electrónico generales, tales como `jane@computer.local`, no se pueden agregar a las cuentas {% data variables.product.product_name %}. Si usas un correo electrónico de ese estilo para tus confirmaciones, las confirmaciones no se vincularán a tu perfil {% data variables.product.product_name %} y no aparecerán en tu gráfico de contribución. - -{% endwarning %} - -#### La confirmación no se hizo en la rama predeterminada o en la rama `gh-pages` - -Las confirmaciones solo se cuentan si se realizan en la rama predeterminada o en la rama `gh-pages` (para los repositorios con sitios de proyecto). Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)". - -Si tus confirmaciones están en una rama que no es una rama predeterminada ni es la rama `gh-pages` y te gustaría que contaran para tus contribuciones, necesitarás realizar las siguientes acciones: -- [Abre una solicitud de extracción](/articles/creating-a-pull-request) para obtener la fusión de tus cambios en la rama predeterminada o la rama `gh-pages`. -- [Cambiar la rama por defecto](/articles/setting-the-default-branch) del repositorio. - -{% warning %} - -Cambiar la rama por defecto del repositorio la cambiará para todos los colaboradores del repositorio. Realiza esta acción solamente si quieres que la nueva rama se convierta en la base respecto de todas las confirmaciones y las solicitudes de extracción que se harán en el futuro. - -{% endwarning %} - -#### La confirmación se hizo en una bifurcación - -Las confirmaciones que se hicieron en una bifurcación no contarán para tus contribuciones. Para hacer que cuenten, debes realizar una de las siguientes acciones: -- [Abre una solicitud de extracción](/articles/creating-a-pull-request) para que se fusionen tus cambios en el repositorio padre. -- Para desconectar la bifurcación y convertirla en un repositorio independiente en {% data variables.product.product_name %}, contacta {% data variables.contact.contact_support %}. Si la bifurcación tiene a su vez más bifurcaciones, indica a {% data variables.contact.github_support %} si éstas deberán moverse junto con tu repositorio a una nueva red o permanecer en la actual. Para obtener más información, consulta "[Acerca de las bifurcaciones](/articles/about-forks/)." - -### Leer más - -- "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/index.md deleted file mode 100644 index 0290ecccae..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/index.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Configurar y administrar tu cuenta de usuario de GitHub -shortTitle: Cuentas de usuario -redirect_from: - - /categories/setting-up-and-managing-your-github-user-account -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts -children: - - /managing-user-account-settings - - /managing-email-preferences - - /managing-access-to-your-personal-repositories - - /managing-your-membership-in-organizations ---- -### Índice - - - - - - - - - - - - - - - - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md deleted file mode 100644 index adbf2c52e9..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Administrar el acceso a tus repositorios personales -intro: Puedes otorgarle a las personas acceso de colaborador a los repositorios que sean propiedad de tu cuenta personal. -redirect_from: - - /categories/101/articles/ - - /categories/managing-repository-collaborators/ - - /articles/managing-access-to-your-personal-repositories -product: '{% data reusables.gated-features.user-repo-collaborators %}' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - Repositories -children: - - /inviting-collaborators-to-a-personal-repository - - /removing-a-collaborator-from-a-personal-repository - - /removing-yourself-from-a-collaborators-repository - - /maintaining-ownership-continuity-of-your-user-accounts-repositories ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md deleted file mode 100644 index 019689eac2..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Invitar colaboradores a un repositorio personal -intro: 'Puedes {% if currentVersion == "free-pro-team@latest" %}invitar usuarios para convertir{% else %}agregar usuarios como{% endif %} colaboradores de tu repositorio personal.' -redirect_from: - - /articles/how-do-i-add-a-collaborator/ - - /articles/adding-collaborators-to-a-personal-repository/ - - /articles/inviting-collaborators-to-a-personal-repository - - /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository -product: '{% data reusables.gated-features.user-repo-collaborators %}' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - Repositories ---- -Los repositorios que son propiedad de una organización pueden conceder acceso más pormenorizado. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.product_name %}](/articles/access-permissions-on-github)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -{% data reusables.organizations.org-invite-expiration %} -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -{% 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. - -{% endnote %} - -{% endif %} - -1. Solicita el nombre de usuario de la persona que estás invitando como colaboradora. - -{% if currentVersion == "free-pro-team@latest" %} Si todavía no tiene un nombre de usuario, puede registrarse en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Registrar una nueva cuenta de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)".{% endif %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.repositories.navigate-to-manage-access %} -1. Da clic en **Invitar un colaborador**. ![botón de "invitar un colaborador"](/assets/images/help/repository/invite-a-collaborator-button.png) -2. En el campo de búsqueda, comienza a teclear el nombre de la persona que quieres invitar, luego da clic en un nombre de la lista de resultados. ![Campo de búsqueda para teclear el nombre de una persona e invitarla al repositorio](/assets/images/help/repository/manage-access-invite-search-field-user.png) -3. Da clic en **Añadir NOMBRE a REPOSITORIO**. ![Botón para añadir un colaborador](/assets/images/help/repository/add-collaborator-user-repo.png) -{% else %} -5. En la barra lateral izquierda, haz clic en **Collaborators** (Colaboradores). ![Barra lateral de configuraciones del repositorio con Colaboradores resaltados](/assets/images/help/repository/user-account-repo-settings-collaborators.png) -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). ![Botón Add (Agregar)](/assets/images/help/repository/repo-settings-collab-add.png) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -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. -{% endif %} - -### Leer más - -- "[Niveles de permiso para el repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-on-a-repository-owned-by-a-user-account)" -- "[Eliminar un colaborador de un repositorio personal](/articles/removing-a-collaborator-from-a-personal-repository)" -- "[Eliminarte a ti mismo del repositorio de un colaborador](/articles/removing-yourself-from-a-collaborator-s-repository)" -- "[Organizar los miembros en equipos](/articles/organizing-members-into-teams)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md deleted file mode 100644 index 0f44ded95c..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Mantener la continuidad de la propiedad para los repositorios de tu cuenta de usuario -intro: Puedes invitar a alguien para administrar los repositorios que pertenezcan a tu usuario si no puedes hacerlo tú mismo. -versions: - free-pro-team: '*' -topics: - - Accounts - - Repositories -redirect_from: - - /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories ---- -### Acerca de los sucesores - -Te recomendamos invitar a otro usuario de {% data variables.product.company_short %} para que sea tu sucesor y que así administre los repositorios que te pertenezcan si tú no puedes hacerlo. Como sucesores, tendrán permisos para: - -- Archivar tus repositorios públicos. -- Transferir tus repositorios públicos a su propia cuenta de usuario. -- Transferir tus repositorios públicos a una organización donde puedan crear repositorios. - -Los sucesores no pueden iniciar sesión en tu cuenta. - -Un sucesor designado puede administrar tus repositorios públicos después de presentar un certificado de defunción y esperar por 7 días o presentar un obituario y esperar por 21 días. Para obtener más información, consulta la sección "[Política de Usuario Finado de {% data variables.product.company_short %}](/github/site-policy/github-deceased-user-policy)". - -Para solicitar acceso para administrar los repositorios como sucesor, contacta a[Soporte de GitHub](https://support.github.com/contact). - -### Invitar un sucesor -La persona que invites para ser tu sucesor deberá tener una cuenta de {% data variables.product.company_short %}. - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.account_settings %} -3. Debajo de "Ajustes de sucesor", para invitar a un sucesor, comienza a escribir el nombre de usuario, nombre completo, o dirección de correo electrónico. Posteriormente, da clic en su nombre cuando éste aparezca. ![Campo de bísqueda para invitación de sucesor](/assets/images/help/settings/settings-invite-successor-search-field.png) -4. Da clic en **Agregar sucesor**. -{% data reusables.user_settings.sudo-mode-popup %} -5. El usuario que has invitado se listará como "Pendiente" hasta que acepte convertirse en tu sucesor. ![Invitación de sucesor pendiente](/assets/images/help/settings/settings-pending-successor.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md deleted file mode 100644 index 91c1655e71..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Eliminar un colaborador de un repositorio personal -intro: 'Cuando eliminas un colaborador de tu proyecto, pierde el acceso de lectura o escritura a tu repositorio. Si el repositorio es privado, y la persona creó una bifurcación, esa bifurcación también se elimina.' -redirect_from: - - /articles/how-do-i-remove-a-collaborator/ - - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository/ - - /articles/removing-a-collaborator-from-a-private-repository/ - - /articles/deleting-a-private-fork-of-a-private-user-repository/ - - /articles/how-do-i-delete-a-fork-of-my-private-repository/ - - /articles/removing-a-collaborator-from-a-personal-repository - - /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository -product: '{% data reusables.gated-features.user-repo-collaborators %}' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - Repositories ---- -### Eliminar bifurcaciones de repositorios privados - -Aunque se borren las bifurcaciones de los repositorios privados cuando se elimina un colaborador, la persona seguirá teniendo todos los clones locales de tu repositorio. - -### Eliminar los permisos de colaborador de una persona que contribuye con un repositorio - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.repositories.navigate-to-manage-access %} -4. To the right of the collaborator you want to remove, click -{% octicon "trashcan" aria-label="The trashcan icon" %}. - ![Botón para eliminar un colaborador](/assets/images/help/repository/collaborator-remove.png) -{% else %} -3. En la barra lateral izquierda, haz clic en **Collaborators & teams** (Colaboradores y equipos). ![Pestaña Collaborators (Colaboradores)](/assets/images/help/repository/repo-settings-collaborators.png) -4. Al lado del colaborador que deseas eliminar, haz clic en el icono **X**. ![Enlace Remove (Eliminar)](/assets/images/help/organizations/Collaborator-Remove.png) -{% endif %} - -### Leer más - -- "[Eliminar de un equipo a miembros de la organización](/articles/removing-organization-members-from-a-team)" -- "[Eliminar a un colaborador externo de un repositorio de la organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md deleted file mode 100644 index e6f734f4b5..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Eliminarte del repositorio de un colaborador -intro: 'Si no quieres seguir siendo colaborador del repositorio de otra persona, te puedes eliminar.' -redirect_from: - - /leave-a-collaborative-repo/ - - /leave-a-repo/ - - /articles/removing-yourself-from-a-collaborator-s-repo/ - - /articles/removing-yourself-from-a-collaborator-s-repository - - /articles/removing-yourself-from-a-collaborators-repository - - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository -product: '{% data reusables.gated-features.user-repo-collaborators %}' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - Repositories ---- -{% data reusables.user_settings.access_settings %} -2. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/settings-sidebar-repositories.png) -3. Junto al repositorio que quieres abandonar, haz clic en **Leave** (Abandonar). ![Botón Leave (Abandonar)](/assets/images/help/repository/repo-leave.png) -4. Lee la advertencia con atención, luego haz clic en "I understand, leave this repository" (Comprendo, abandonar este repositorio). ![Cuadro de diálogo con advertencia sobre el abandono](/assets/images/help/repository/repo-leave-confirmation.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md deleted file mode 100644 index 91a5c2582a..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Agregar una dirección de correo electrónico a tu cuenta de GitHub -intro: '{% data variables.product.product_name %} permite que agregues a tu cuenta tantas direcciones de correo electrónico como desees. Si estableces una dirección de correo electrónico en tu configuración de Git local, necesitarás agregarla a los parámetros de tu cuenta a fin de conectar tus confirmaciones con tu cuenta. Para más información sobre las direcciones de correo electrónico y las confirmaciones, consulta "[Setting your commit email address](/articles/setting-your-commit-email-address/)".' -redirect_from: - - /articles/adding-an-email-address-to-your-github-account - - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Accounts - - Notifications ---- -{% if currentVersion == "free-pro-team@latest" %} - -{% note %} - -**Nota**: {% data reusables.user_settings.no-verification-disposable-emails %} - -{% endnote %} - -{% endif %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -{% data reusables.user_settings.add_and_verify_email %} -{% data reusables.user_settings.select_primary_email %} - -### Leer más - -- "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences/)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md deleted file mode 100644 index d24017e68e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Bloquear las inserciones de la línea de comando que muestran tu dirección de correo electrónico personal -intro: 'Si decidiste mantener tu dirección de correo electrónico privada al realizar operaciones basadas en la web, también puedes optar por bloquear las inserciones de la línea de comando que pueden exponer tu dirección de correo electrónico personal.' -redirect_from: - - /articles/blocking-command-line-pushes-that-expose-your-personal-email-address - - /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address -versions: - free-pro-team: '*' -topics: - - Accounts - - Notifications ---- -Cuando subes las confirmaciones de la línea de comando, la dirección de correo electrónico que has [establecido en Git](/articles/setting-your-commit-email-address) están asociadas con tus confirmaciones. Este parámetro impide que subas confirmaciones a la línea de comando que usa tu dirección de correo electrónico personal. - -{% data reusables.user_settings.about-commit-email-addresses %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -{% data reusables.user_settings.keeping_your_email_address_private %} -4. Para que tu dirección de correo electrónico siga siendo privada en las confirmaciones desde la línea de comando, selecciona **Block command line pusses that expose my email** (Bloquear inserciones de la línea de comando que expone mi correo electrónico). ![Opción para bloquear las inserciones de la línea de comando que expone tus correos electrónicos](/assets/images/help/settings/email_privacy_block_command_line_pushes.png) - -### Leer más - -- "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md deleted file mode 100644 index 4fb5644eb6..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Cambiar tu dirección principal de correo electrónico -intro: Puedes cambiar la dirección de correo electrónico asociada con tu cuenta de usuario en cualquier momento. -redirect_from: - - /articles/changing-your-primary-email-address - - /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Accounts - - Notifications ---- -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -3. Si deseas agregar una nueva dirección de correo electrónico para que sea tu dirección principal de correo electrónico, en "Add email address" (Agregar dirección de correo electrónico), escribe una nueva dirección de correo electrónico y haz clic en **Add** (Agregar). ![Botón Add another email address (Agregar otra dirección de correo electrónico)](/assets/images/help/settings/add_another_email_address.png) -4. En "Primary email address" (dirección principal de correo electrónico), usa el menú desplegable para hacer clic en la dirección de correo electrónico que deseas establecer como tu dirección principal de correo electrónico, y haz clic en **Save** (Guardar). ![Botón Set as primary (Establecer como principal)](/assets/images/help/settings/set_as_primary_email.png) -5. To remove the old email address from your account, next to the old email, click -{% octicon "trashcan" aria-label="The trashcan symbol" %}. -{% if currentVersion == "free-pro-team@latest" %} -6. Verifica tu nueva dirección principal de correo electrónico. Sin una dirección de correo electrónico verificada, no podrás usar todas las características de {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)". -{% endif %} - -### Leer más - -- "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences/)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md deleted file mode 100644 index 9d1c70cb0b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Administrar preferencias de correo electrónico -intro: 'Puedes agregar o cambiar las direcciones de correo electrónico asociadas con tu cuenta {% data variables.product.product_name %}. También puedes administrar correos electrónicos que recibes de {% data variables.product.product_name %}.' -redirect_from: - - /categories/managing-email-preferences/ - - /articles/managing-email-preferences -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - Notifications -children: - - /adding-an-email-address-to-your-github-account - - /changing-your-primary-email-address - - /setting-a-backup-email-address - - /setting-your-commit-email-address - - /blocking-command-line-pushes-that-expose-your-personal-email-address - - /remembering-your-github-username-or-email - - /types-of-emails-github-sends - - /managing-marketing-emails-from-github ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md deleted file mode 100644 index 9126eff906..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Administrar correos electrónicos de marketing de GitHub -intro: 'Además de las notificaciones y de los correos electrónicos de la cuenta, {% data variables.product.prodname_dotcom %} ocasionalmente envía correos electrónicos de marketing con novedades e información sobre nuestros productos. Si cancelas la suscripción de los correos electrónicos de marketing existentes, no se te incluirá en las futuras campañas excepto que cambies tus configuraciones de correo electrónico {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /articles/managing-marketing-emails-from-github - - /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github -versions: - free-pro-team: '*' -topics: - - Accounts - - Notifications ---- -### Cancelar la suscripción de los correos electrónicos de marketing de {% data variables.product.prodname_dotcom %} - -{% tip %} - -**Sugerencia:** si cancelas la suscripción de todos los correos electrónicos de marketing y después te suscribes en el boletín informativo de Explore, solo recibirás el boletín informativo de Explore y no recibirás otros correos electrónicos de marketing. - -{% endtip %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -3. Dentro de *Email preferences (Preferencias de correo electrónico)*, selecciona **Only receive account related emails, and those I subscribe to (Recibir únicamente correos electrónicos relacionados con la cuenta y aquellos a los cuales me suscribo)**. ![Captura de pantalla de la cancelación de la suscripción de un correo electrónico de marketing](/assets/images/help/notifications/email_preferences.png) -4. Haz clic en **Save email preferences (Guardar preferencias de correo electrónico)**. ![Botón para guardar las preferencias de correo electrónico](/assets/images/help/notifications/save_email_preferences.png) - -### Leer más - -- "[Tipos de correos electrónicos que envía GitHub](/articles/types-of-emails-github-sends)" -- "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md deleted file mode 100644 index a6bc304f6d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Recordar tu nombre de usuario o correo electrónico de GitHub -intro: '¿Vas a iniciar sesión en {% data variables.product.product_location %} por primera vez después de un tiempo? Si es así, ¡bienvenido de nuevo! Si no puedes recordar tu {% data variables.product.product_name %} nombre de la cuenta de usuario, puedes intentar estos métodos para hacerlo.' -redirect_from: - - /articles/oh-noes-i-ve-forgotten-my-username-email/ - - /articles/oh-noes-i-ve-forgotten-my-username-or-email/ - - /articles/remembering-your-github-username-or-email - - /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Accounts - - Notifications ---- -{% mac %} - -### Usuarios {% data variables.product.prodname_desktop %} - -1. En el menú de **GitHub Desktop** (GitHub Desktop), haz clic en **Preferences** (Preferencias). -2. En la ventana Preferences (Preferencias), comprueba lo siguiente: - - Para ver tu {% data variables.product.product_name %} nombre de usuario, haz clic en **Accounts** (Cuentas). - - Para ver tu correo electrónico de Git, haz clic en **Git**. Ten en cuenta que no está garantizado que este correo electrónico sea [tu correo electrónico {% data variables.product.product_name %} principal](/articles/changing-your-primary-email-address). - -{% endmac %} - -{% windows %} - -### Usuarios {% data variables.product.prodname_desktop %} - -1. In the **File** menu, click **Options**. -2. En la ventana Options (Opciones), comprueba lo siguiente: - - Para ver tu {% data variables.product.product_name %} nombre de usuario, haz clic en **Accounts** (Cuentas). - - Para ver tu correo electrónico de Git, haz clic en **Git**. Ten en cuenta que no está garantizado que este correo electrónico sea [tu correo electrónico {% data variables.product.product_name %} principal](/articles/changing-your-primary-email-address). - -{% endwindows %} - -### Encontrar tu nombre de usuario en tu configuración `user.name` - -Durante la configuración, puede que debas [establecer tu nombre de usuario en Git](/articles/setting-your-username-in-git). En tal caso, puedes revisar el valor de este parámetro de configuración: - -```shell -$ git config user.name -# Ver el parámetro -YOUR_USERNAME -``` - -### Encontrar tu nombre de usuario en la URL de repositorios remotos - -Si tienes alguna copia local de los repositorios personales que has creado o bifurcado, puedes verificar la URL del repositorio remoto. - -{% tip %} - -**Sugerencia**: Este método solo funciona si tienes un repositorio original o tu propia bifurcación del repositorio de alguna otra persona. Si clonas el repositorio de alguna otra persona, se mostrará su nombre de usuario en lugar del tuyo. Del mismo modo, los repositorios de la organización mostrarán el nombre de la organización en lugar del de un usuario particular en la URL remota. - -{% endtip %} - -```shell -$ cd YOUR_REPOSITORY -# Cambia los directorios para el repositorio de Git inicializado -$ git remote -v -origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch) -origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push) -``` - -Tu nombre de usuario es lo que le sigue inmediatamente a `https://{% data variables.command_line.backticks %}/`. - -{% if currentVersion == "free-pro-team@latest" %} -### Leer más - -- "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)" -{% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md deleted file mode 100644 index 873b21f434..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Configurar una dirección de correo electrónico de respaldo -intro: Utiliza una dirección de correo electrónico de respaldo para reiniciar de forma segura tu contraseña si ya no puedes acceder a tu dirección principal de correo electrónico. -redirect_from: - - /articles/setting-a-backup-email-address - - /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - Notifications ---- -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -3. Dentro de "Backup email address" (Dirección de correo electrónico de respaldo), selecciona la dirección que deseas configurar como tu dirección de correo electrónico de respaldo utilizando el menú desplegable. ![Dirección de correo electrónico de respaldo](/assets/images/help/settings/backup-email-address.png) -4. Haz clic en **Save (Guardar)**. - -### Leer más - -- "[Administrar preferencias de correo electrónico](/articles/managing-email-preferences/)" -- "[Actualizar tus credenciales de acceso de GitHub](/articles/updating-your-github-access-credentials/)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md deleted file mode 100644 index c09e8a87c7..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: Configurar tu dirección de correo electrónico de confirmación -intro: 'Puedes configurar una dirección principal de correo electrónico en {% data variables.product.product_name %} que esté asociada con las operaciones de Git que realizas con base en la web como ediciones y fusiones.' -redirect_from: - - /articles/keeping-your-email-address-private/ - - /articles/setting-your-commit-email-address-on-github/ - - /article/about-commit-email-addresses/ - - /articles/git-email-settings/ - - /articles/setting-your-email-in-git/ - - /articles/set-your-user-name-email-and-github-token/ - - /articles/setting-your-commit-email-address-in-git/ - - /articles/setting-your-commit-email-address - - /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts - - Notifications ---- -### Acerca de las dirección de correo electrónico de confirmación - -{% data variables.product.product_name %} utiliza tu dirección de correo electrónico de confirmación para asociar las confirmaciones con tu cuenta {% data variables.product.product_name %}. Puedes elegir la dirección de correo electrónico que se asociará con las confirmaciones que subes desde la línea de comando y las operaciones de Git con base en la web que realizas. - -Para las operaciones de Git con base en la web, puedes configurar tu dirección de correo electrónico de confirmación en {% data variables.product.product_name %}. Para las confirmaciones que subes desde la línea de comando, puedes configurar tu dirección de correo electrónico de confirmaciones en Git. - -{% if currentVersion == "free-pro-team@latest" %}Cualquier confirmación que hayas realizado antes de cambiar tu dirección de correo electrónico de confirmaciones estará todavía asociada a tu dirección de correo electrónico previa.{% else %}Después de cambiar tu dirección de correo electrónico de confirmaciones en {% data variables.product.product_name %}, la nueva dirección de correo electrónico será visible por defecto en todas tus operaciones futuras de Git con base en la web. Cualquier confirmación que realices antes de cambiar tu dirección de correo electrónico de confirmaciones estarán todavía asociada a tu dirección de correo electrónico anterior.{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -{% note %} - -**Nota**: {% data reusables.user_settings.no-verification-disposable-emails %} - -{% endnote %} - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %}Si deseas mantener de forma privada tu dirección personal de correo electrónico, puedes utilizar una dirección de correo electrónico `no-reply` provista por {% data variables.product.product_name %} como tu dirección de correo electrónico de confirmaciones. Para utilizar tu dirección de correo electrónico `noreply` para confirmaciones que subes desde la línea de comando, utiliza esa dirección de correo electrónico cuando configuras tu dirección de correo electrónico de confirmaciones en Git. Para utilizar tu dirección `noreply` para las operaciones de Git con base en la web, configura tu dirección de correo electrónico de confirmaciones en GitHub y elige **Keep my email address private (Mantener mi dirección de correo electrónico privada)**. - -También puedes elegir bloquear las confirmaciones que subes desde la línea de comando que muestra tu dirección de correo electrónico personal. Para obtener más información, consulta "[Bloquear las subidas de línea de comando que muestran tu correo electrónico personal](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %} - -Para garantizar que las confirmaciones se te asignen y aparezcan en tu gráfico de contribuciones, utiliza una dirección de correo electrónico que hayas [agregado en tu cuenta de GitHub](/articles/adding-an-email-address-to-your-github-account/){% if currentVersion == "free-pro-team@latest" %}, o la dirección de correo electrónico `noreply` que provee {% data variables.product.product_name %} que figura en tus configuraciones de correo electrónico{% endif %}. - -{% if currentVersion == "free-pro-team@latest" %} - -{% note %} - -**Nota:** Si creaste tu cuenta de {% data variables.product.product_name %} _después_ del 18 de julio de 2017, tu dirección de correo electrónico `no-reply` provista por {% data variables.product.product_name %} es un número de Id. de siete dígitos, y tu nombre de usuario tiene la forma de ID+username@users.noreply.github.com. Si creaste tu cuenta de {% data variables.product.product_name %} _antes del_ 18 de julio de 2017, tu dirección de correo electrónico `no-reply` provista por {% data variables.product.product_name %} es tu nombre de usuario con la forma de username@users.noreply.github.com. Puedes obtener una dirección de correo electrónico `no-reply` provista por {% data variables.product.product_name %} con base en el ID al seleccionar (o deseleccionar y volver a seleccionar) **Keep my email address private (Mantener mi dirección de correo electrónico privada)** en tus configuraciones. - -{% endnote %} - -Si utilizas tu dirección de correo electrónico `noreply` provista por {% data variables.product.product_name %} para realizar confirmaciones y después [cambias tu nombre de usuario](/articles/changing-your-github-username), esas confirmaciones no estarán asociadas a tu cuenta {% data variables.product.product_name %}. Esto no se aplica si estás usando una dirección `noreply` basada en el ID provista por {% data variables.product.product_name %}. Para obtener más información, consulta [Cambiar tu {% data variables.product.prodname_dotcom %} nombre de usuario](/articles/changing-your-github-username)"{% endif %} - -### Configurar tu dirección de correo electrónico de confirmación en {% data variables.product.prodname_dotcom %} - -{% data reusables.files.commit-author-email-options %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.emails %} -{% data reusables.user_settings.add_and_verify_email %} -{% data reusables.user_settings.select_primary_email %}{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.user_settings.keeping_your_email_address_private %}{% endif %} - -### Configurar tu dirección de correo electrónico de confirmación en Git - -Puedes utilizar el comando `git config` para cambiar la dirección de correo electrónico que asocias a tus confirmaciones de Git. La nueva dirección de correo electrónico que configures será visible en cualquier confirmación futura que subas a {% data variables.product.product_name %} desde la línea de comando. Cualquier confirmación que realices antes de cambiar tu dirección de correo electrónico de confirmaciones estarán todavía asociadas a tu dirección de correo electrónico anterior. - -#### Configurar tu dirección de correo electrónico para cada repositorio en tu computadora - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. {% data reusables.user_settings.set_your_email_address_in_git %} - ```shell - $ git config --global user.email "email@example.com" - ``` -3. {% data reusables.user_settings.confirm_git_email_address_correct %} - ```shell - $ git config --global user.email - email@example.com - ``` -4. {% data reusables.user_settings.link_email_with_your_account %} - -#### Configurar tu dirección de correo electrónico para un repositorio único - -{% data variables.product.product_name %} utiliza la dirección de correo electrónico configurada en tu configuración local de Git para asociar las confirmaciones subidas desde la línea de comando con tu cuenta {% data variables.product.product_name %}. - -Puedes cambiar la dirección de correo electrónico asociada a las confirmaciones que realizas en un repositorio único. Esto sustituirá tus configuraciones globales de Git en este único repositorio, pero no afectará otros repositorios. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Cambia el directorio de trabajo actual al repositorio local donde deseas configurar la dirección de correo electrónico que asocias con tus confirmaciones de Git. -3. {% data reusables.user_settings.set_your_email_address_in_git %} - ```shell - $ git config user.email "email@example.com" - ``` -4. {% data reusables.user_settings.confirm_git_email_address_correct %} - ```shell - $ git config user.email - email@example.com - ``` -5. {% data reusables.user_settings.link_email_with_your_account %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md deleted file mode 100644 index f6b429e029..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Tipos de correos electrónicos que envía GitHub -intro: 'Existen varios tipos de correos electrónicos que puedes recibir de {% data variables.product.product_name %}, incluidas notificaciones, información de cuenta y comunicaciones de marketing.' -redirect_from: - - /articles/types-of-emails-github-sends - - /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends -versions: - free-pro-team: '*' -topics: - - Accounts - - Notifications ---- -### Correos electrónicos de notificación - -Puedes decidir si quieres recibir algunas o todas las notificaciones de tu actividad por correo electrónico. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)". Los correos electrónicos de notificación pueden incluir: - -- Actividad relacionada con la seguridad de los repositorios a los que tienes acceso de administrador -- Actividad de los repositorios que estás observando -- Conversaciones en las que estás participando -- Conversaciones en las que te han mencionado @mentioned -- Subidas a solicitudes de extracción en las que estás participando -- Invitaciones a colaborar en una organización o repositorio -- Tu propia actividad, como abrir, comentar o cerrar propuestas y solicitudes de extracción - -También puedes elegir qué tipo de actualizaciones de correo electrónico quieres recibir sobre las conversaciones en las que estás participando o que estás observando. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". - -### Correos electrónico de la cuenta - -Si subiste de categoría a productos o funciones pagas, recibirás los recibos de facturación en la dirección principal de correo electrónico de la cuenta. Para obtener más información, consulta "[Establecer tu correo electrónico de facturación](/articles/setting-your-billing-email)". - -### Correos electrónicos de marketing - -{% data variables.product.product_name %}, en algunas ocasiones, envía estos tipos de correos electrónicos de marketing: - -- Trucos y sugerencias para comenzar con tu cuenta -- Información personalizada acerca de participar en proyectos o funciones nuevas -- Boletines a los que te suscribiste, tales como {% data variables.explore.explore_github %} - -Para obtener más información, consulta "[Administrar los correos electrónicos de marketing desde GitHub](/articles/managing-marketing-emails-from-github)". diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md deleted file mode 100644 index 2c39a146b8..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Acerca de tu tablero personal -redirect_from: - - /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github/ - - /articles/opting-into-the-public-beta-for-a-new-dashboard/ - - /articles/about-your-personal-dashboard - - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard -intro: 'Puedes visitar tu tablero personal para hacer un seguimiento de las propuestas y las solicitudes de extracción que estás siguiendo o en las que estás trabajando, navegar hacia las páginas de equipo y tus repositorios principales, estar actualizado sobres las actividadess recientes en las organizaciones y los repositorios en los que estás suscripto y explorar los repositorios recomendados.' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -### Acceder a tu tablero personal - -Tu tablero personal es la primera página que verás cuando inicias sesión en {% data variables.product.product_name %}. - -Para acceder a tu tablero personal una vez que has iniciado sesión, haz clic en el {% octicon "mark-github" aria-label="The github octocat logo" %} en la esquina superior izquierda de cualquier página en {% data variables.product.product_url %}. - -### Encontrar tu actividad reciente - -En la sección "Recent activity" (Actividad reciente) de tus noticias, rápidamente puedes encontrar las propuestas y solicitudes de extracción recién actualizadas en las que estás trabajando y hacerles el seguimiento. En "Recent activity" (Actividad reciente), puedes previsualizar hasta 12 actualizaciones recientes, realizadas durante las últimas dos semanas. - -{% data reusables.dashboard.recent-activity-qualifying-events %} - -### Encontrar tus equipos y repositorios principales - -En la barra lateral izquierda de tu tablero, puedes acceder a los equipos y los repositorios principales que usas. - -![listado de repositorios y equipos de diferentes organizaciones](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png) - -También puedes encontrar un listado de los repositorios, los equipos y los tableros de proyecto recientemente visitados al hacer clic en la barra de búsqueda en la parte principal de cualquier página en {% data variables.product.product_name %}. - -### Estar actualizado con la actividad desde tu organización - -En la sección "All activity" (Todas las actividades) de tus noticias, puedes ver las actualizaciones de los repositorios a los que estás suscrito y de las personas que sigues. La sección "All activity" (Todas las actividades) muestra las actualizaciones de los repositorios que observas o has marcado con una estrella, y de los usuarios a quienes sigues. - -Verás actualizaciones en tus noticias cuando un usuario que sigues: -- Destaca un repositorio. -- Sigue a otro usuario. -- Crea un repositorio público. -- 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 confirmaciones a un repositorio que miras. -- Bifurca un repositorio público. - -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)". - -### Explorar los repositorios recomendados - -Puedes explorar los repositorios recomendados en tus comunidades en la sección "Explorar repositorios" en el costado derecho de tu tablero. Las recomendaciones se basan en repositorios que has visitado o a los que has marcado con una estrella, las personas que sigues, y la actividad dentro de los repositorios a los cuales tienes acceso. {% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta "[Encontrar maneras 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)".{% endif %} - -### Leer más - -- "[Acerca del tablero de tu organización](/articles/about-your-organization-dashboard)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md deleted file mode 100644 index 384b0082a3..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Mejores prácticas para abandonar la empresa -intro: 'Cambiar de trabajo es una realidad. Si usas tu cuenta de usuario de GitHub para tus objetivos personales *y* laborales, hay algunas cosas que debes tener en cuenta al dejar la empresa u organización.' -redirect_from: - - /articles/best-practices-for-leaving-your-company - - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company -versions: - free-pro-team: '*' -topics: - - Accounts ---- -Antes de abandonar tu empresa, asegúrate de actualizar la siguiente información en tu cuenta de usuario: - -- Quitar la marca de verificación de la dirección de correo electrónico de la empresa al [eliminarla de los parámetros de Correo electrónico](/articles/changing-your-primary-email-address). Puedes volver a agregarla sin verificar para conservar todas las confirmaciones asociadas vinculadas con tu cuenta. -- [Cambiar tu dirección principal de correo electrónico](/articles/changing-your-primary-email-address) del correo electrónico de tu empresa a tu correo electrónico personal. -{% if currentVersion == "free-pro-team@latest" %} -- [Verificar tu nueva dirección principal de correo electrónico](/articles/verifying-your-email-address). -{% endif %} -- [Cambiar tu nombre de usuario de GitHub](/articles/changing-your-github-username) para eliminar cualquier referencia a tu empresa u organización, si es necesario. - -## Abandonar las organizaciones - -Si has estado trabajando con repositorios que pertenecen a una organización, deberás [eliminarte como miembro de la organización](/articles/removing-yourself-from-an-organization). Ten en cuenta que si eres el propietario de la organización, primero deberías [transferir tu pertenencia a la organización](/articles/transferring-organization-ownership) a otra persona. - -## Eliminar asociaciones profesionales con repositorios personales. - -Si has estado colaborando profesionalmente con otra persona en repositorios que pertenecen a su cuenta de usuario personal, deberás [eliminarte como colaborador](/articles/removing-yourself-from-a-collaborator-s-repository) desde otros repositorios. - -- [Deja de mirar repositorios](https://github.com/watching) relacionados con tu trabajo. No desearás volver a ver esas notificaciones. -- [Transfiere los repositorios que posees](/articles/how-to-transfer-a-repository) a otros que deben seguir trabajando con ellos una vez que te marches. -- [Elimina bifurcaciones que te pertenecen](/articles/deleting-a-repository) y que están relacionadas con el trabajo que estabas haciendo. No te preocupes, si eliminas una bifurcación no eliminarás el repositorio ascendente. -- Elimina copias locales de las bifurcaciones que pueden existir en tu computadora. - -```shell -$ rm -rf work_directory -``` diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md deleted file mode 100644 index 760bb3fe7e..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Changing your GitHub username -intro: 'You can change your {% data variables.product.product_name %} username at any time.' -redirect_from: - - /articles/how-to-change-your-username/ - - /articles/changing-your-github-user-name/ - - /articles/renaming-a-user/ - - /articles/what-happens-when-i-change-my-username/ - - /articles/changing-your-github-username - - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Accounts ---- -### About username changes - -You can change your username to another username that is not currently in use.{% if currentVersion == "free-pro-team@latest" %} If the username you want is not available, you'll see information about whether you can request the username to be released when you type in the desired username. - -If the username is not eligible for release and you don't hold a trademark for the username, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %} - -After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect. - -{% data variables.product.product_name %} cannot set up redirects for: -- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username -- Links to [gists](/articles/creating-gists) that include your old username - -### Repository references - -After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories. -- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change. -- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work. - -If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Changing a remote's URL](/articles/changing-a-remote-s-url)." - -### Links to your previous profile page - -After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your {% data variables.product.product_name %} account from elsewhere{% if currentVersion == "free-pro-team@latest" %}, such as your LinkedIn or Twitter profile{% endif %}. - -### Your Git commits - -{% if currentVersion == "free-pro-team@latest"%}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% if currentVersion == "free-pro-team@latest"%}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." - -### Changing your username - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.account_settings %} -3. In the "Change username" section, click **Change username**. - ![Change Username button](/assets/images/help/settings/settings-change-username.png){% if currentVersion == "free-pro-team@latest" %} -4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**. - ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png) -5. Type a new username. - ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png) -6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see. - ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png) -{% endif %} - -### Further reading - -- "[Changing a remote's URL](/articles/changing-a-remote-s-url)" -- "[Why are my commits linked to the wrong user?](/articles/why-are-my-commits-linked-to-the-wrong-user)"{% if currentVersion == "free-pro-team@latest" %} -- "[{% data variables.product.prodname_dotcom %} Username Policy](/articles/github-username-policy)"{% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md deleted file mode 100644 index af97ad9b88..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Convertir un usuario en una organización -redirect_from: - - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization/ - - /articles/explaining-the-account-transformation-warning/ - - /articles/converting-a-user-into-an-organization - - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization -intro: Puedes convertir tu cuenta de usuario en una organización. Esto permite que haya más permisos granulares para repositorios que pertenecen a la organización. -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Accounts ---- -{% warning %} - -**Advertencia**: Antes de convertir un usuario en una organización, ten en cuenta estos puntos: - - - **Ya no** podrás iniciar sesión con la cuenta de usuario convertida. - - **Ya no** podrás crear o modificar gists que pertenecen a la cuenta de usuario convertida. - - Una organización **no puede** volver a convertirse en un usuario. - - Las claves SSH, los tokens de OAuth, las reacciones de {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %},{% endif %} y la información del usuario asociado **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. - -{% endwarning %} - -### Conservar la cuenta de usuario personal y crear una nueva organización manualmente - -Si deseas que tu organización tenga el mismo nombre que estás usando actualmente para tu cuenta personal, o si deseas que la información de la cuenta del usuario personal permanezca intacta, debes crear una organización nueva y trasnferirla a tus repositorios en lugar de convertir tu cuenta de usuario en una organización. - -1. Para conservar el nombre de la cuenta de usuario para uso personal, [cambia el nombre de tu cuenta de usuario personal](/articles/changing-your-github-username) por uno nuevo y maravilloso. -2. [Crea una nueva organización](/articles/creating-a-new-organization-from-scratch) con el nombre original de tu cuenta de usuario personal. -3. [Transfiere tus repositorios](/articles/transferring-a-repository) a tu nueva cuenta de la organización. - -### Convertir tu cuenta personal en una organización automáticamente - -Puedes convertir tu cuenta de usuario personal directamente en una organización. Convertir tu cuenta: - - Preserva los repositorios ya que no tienen la necesidad de ser transferidos a otra cuenta manualmente - - Invita automáticamente a que los colaboradores se unan a los equipos con permisos equivalentes a los que tenían antes - {% if currentVersion == "free-pro-team@latest" %}- Para las cuentas de usuario en {% data variables.product.prodname_pro %}, automáticamente traslada la facturación [al {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) pago sin la necesidad de volver a ingresar la información de pago, ajustar tu ciclo de facturación o duplicar el pago en ningún momento{% endif %} - -1. Crea una nueva cuenta personal, que usarás para iniciar sesión en GitHub y acceder a la organización y a tus repositorios después de la conversión. -2. [Sal de todas las organizaciones](/articles/removing-yourself-from-an-organization) a las que se ha unido la cuenta de usuario que estás convirtiendo. -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.organizations %} -5. En "Transform account" (Transformar cuenta), haz clic en **Turn into an organization** (Convertir en una organización). ![Botón para convertir la organización](/assets/images/help/settings/convert-to-organization.png) -6. En el cuadro de diálogo Account Transformation Warning (Advertencia de transformación de la cuenta), revisa y confirma la confirmación. Ten en cuenta que la información en este cuadro es la misma que la advertencia en la parte superior de este artículo. ![Advertencia de conversión](/assets/images/help/organizations/organization-account-transformation-warning.png) -7. En la página "Transform your user into an organization" (Transformar tu usuario en una organización), debajo de "Choose an organization owner" (Elegir un propietario de la organización), elige la cuenta personal secundaria que creaste en la sección anterior u otro usuario en quien confías para administrar la organización. ![Página Add organization owner (Agregar propietario de la organización)](/assets/images/help/organizations/organization-add-owner.png) -8. Escoge la nueva suscripción de la organización y escribe tu información de facturación si se te solicita. -9. Haz clic en **Create Organization** (Crear organización). -10. Inicia sesión en la nueva cuenta de usuario que creaste en el paso uno, luego usa el cambiador de contexto para acceder a la organización nueva. - -{% tip %} - -**Sugerencia**: Cuando conviertas una cuenta de usuario en una organización, agregaremos los colaboradores a los repositorios que le pertenecen a la cuenta de la nueva organización como *colaboradores externos*. Luego puedes invitar a los *colaboradores externos* para que se conviertan en miembros de la organización nueva, si así lo deseas. Para obtener más información, consulta "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)." - -{% endtip %} - -### Leer más -- "[Configurar equipos](/articles/setting-up-teams)" -{% if currentVersion == "free-pro-team@latest" %}- "[Invitar usuarios a unirse a tu organización](/articles/inviting-users-to-join-your-organization)"{% endif %} -- "[Acceder a una organización](/articles/accessing-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md deleted file mode 100644 index 84fc1e0c99..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Eliminar tu cuenta de usuario -intro: 'Puedes eliminar tu cuenta de usuario de {% data variables.product.product_name %} en cualquier momento.' -redirect_from: - - /articles/deleting-a-user-account/ - - /articles/deleting-your-user-account - - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account -versions: - free-pro-team: '*' - enterprise-server: '*' -topics: - - Accounts ---- -Al eliminar tu cuenta de usuario se eliminan todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta. {% if currentVersion == "free-pro-team@latest" %}No se eliminarán las propuestas ni las solicitudes de extracción que hayas creado ni los comentarios que hayas hecho en repositorios que sean propiedad de otros usuarios. En lugar de eliminarlos, se los asociará con nuestro [Usuario fantasma](https://github.com/ghost).{% else %}No se eliminarán las propuestas ni las solicitudes de extracción que hayas creado ni los comentarios que hayas hecho en repositorios que sean propiedad de otros usuarios.{% endif %} - -{% if currentVersion == "free-pro-team@latest" %}El nombre de la cuenta también pasará a estar disponible para que cualquier otra persona pueda usarlo en una cuenta nueva, y daremos por terminada tu facturación. La dirección de correo electrónico asociada con la cuenta pasará a estar disponible para el uso por parte de otra cuenta de {% data variables.product.product_name %}. {% endif %} - -Si eres el único propietario de una organización, debes transferir la propiedad a otra persona o eliminar la organización primero para que puedas eliminar tu cuenta de usuario. Si hay otros propietarios de la organización, debes eliminarte de la organización primero para que puedas eliminar tu cuenta de usuario. - -Para obtener más información, consulta: -- "[Transferir la propiedad de la organización](/articles/transferring-organization-ownership)" -- "[Eliminar una cuenta de la organización](/articles/deleting-an-organization-account)" -- "[Eliminarte de una organización](/articles/removing-yourself-from-an-organization/)" - -### Copias de seguridad de los datos de tu cuenta - -Antes de eliminar tu cuenta de usuario, haz una copia de todos los repositorios, bifurcaciones privadas, wikis, propuestas y solicitudes de extracción que sean propiedad de tu cuenta. - -{% warning %} - -**Advertencia:** Una vez que tu cuenta de usuario se ha eliminado, GitHub no puede restaurar su contenido. - -{% endwarning %} - -### Eliminar tu cuenta de usuario - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.account_settings %} -3. En la parte inferior de la página de configuración de la cuenta, en "Eliminar cuenta", haz clic en **Eliminar tu cuenta**. Para que puedas eliminar tu cuenta de usuario, antes debes tener en cuenta lo siguiente: - - Si eres el único propietario de la organización, debes transferir la propiedad a otra persona o eliminar tu organización. - - Si hay otros propietarios de la organización dentro de la organización, debes eliminarte de la organización. ![Botón Eliminación de cuenta](/assets/images/help/settings/settings-account-delete.png) -4. En el cuadro de diálogo "Make sure you want to do this" (Asegúrate de que quieres hacer esto), realiza los siguientes pasos para confirmar que comprendes lo que sucede cuando se elimina tu cuenta: ![Diálogo de confirmación para eliminar cuenta](/assets/images/help/settings/settings-account-deleteconfirm.png) - {% if currentVersion == "free-pro-team@latest" %}-Recuerda que se eliminarán todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta, tu facturación finalizará y tu nombre de usuario pasará a estar disponible para que cualquier otra persona lo use en {% data variables.product.product_name %}. - {% else %}-Recuerda que se eliminarán todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta, y tu nombre de usuario pasará a estar disponible para que cualquier otra persona lo use en {% data variables.product.product_name %}. - {% endif %}- En el primer campo, escribe tu nombre de usuario de {% data variables.product.product_name %} o tu correo electrónico. - - En el segundo campo, escribe la frase que se indica. diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md deleted file mode 100644 index 46ee0e7787..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Administrar las configuraciones del usuario de la cuenta -intro: 'Puedes cambiar varias configuraciones de tu cuenta personal, lo que incluye cambiar tu nombre de usuario y eliminar tu cuenta.' -redirect_from: - - /categories/29/articles/ - - /categories/user-accounts/ - - /articles/managing-user-account-settings -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts -children: - - /about-your-personal-dashboard - - /managing-your-theme-settings - - /changing-your-github-username - - /merging-multiple-user-accounts - - /converting-a-user-into-an-organization - - /deleting-your-user-account - - /permission-levels-for-a-user-account-repository - - /permission-levels-for-user-owned-project-boards - - /managing-the-default-branch-name-for-your-repositories - - /managing-security-and-analysis-settings-for-your-user-account - - /managing-access-to-your-user-accounts-project-boards - - /integrating-jira-with-your-personal-projects - - /best-practices-for-leaving-your-company - - /what-does-the-available-for-hire-checkbox-do ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md deleted file mode 100644 index 65c5413e17..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Integrar Jira con tus proyectos personales -intro: 'Puedes integrar Jira Cloud a tu cuenta de usuario para escanear confirmaciones y solicitudes de extracción, creando los metadatos e hipervínculos correspondientes en cualquier propuesta de Jira mencionada.' -redirect_from: - - /articles/integrating-jira-with-your-personal-projects - - /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects -versions: - enterprise-server: '*' - github-ae: '*' ---- -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.developer_settings %} -3. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_oauth_app %}s**. ![Pestaña de { site.data.variables.product.prodname_oauth_app }} en la barra lateral izquierda](/assets/images/help/settings/developer-settings-oauth-apps.png) -3. Haz clic en **Register a new application** (Registrar una aplicación nueva). -4. En **Application name** (Nombre de la aplicación), escribe "Jira". -5. En **Homepage URL** (URL de la página de inicio), escribe la URL completa de tu instancia de Jira. -6. En **Authorization callback URL** (URL de devolución de llamada de autorización), escribe la URL completa para tu instancia de Jira. -7. Haz clic en **Register application** (Registrar aplicación). ![Botón Register application (Registrar aplicación)](/assets/images/help/oauth/register-application-button.png) -8. En **Developer applications** (Aplicaciones del programador), presta atención a los valores de "Client ID" (Id. del cliente) y "Client Secret" (Secreto del cliente). ![Id. del cliente y secreto del cliente](/assets/images/help/oauth/client-id-and-secret.png) -{% data reusables.user_settings.jira_help_docs %} - -### Leer más - -- ["Integrar Jira al tablero de proyecto de tu organización"](/articles/integrating-jira-with-your-organization-project-board) -- Conectar Jira Cloud a GitHub (Documentación de Atlassian) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md deleted file mode 100644 index 048375f794..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Administrar el acceso a los tableros de proyecto de tu cuenta de usuario -intro: 'Como propietario de un tablero de proyecto, puedes agregar o eliminar a un colaborador y personalizar sus permisos a un tablero de proyecto.' -redirect_from: - - /articles/managing-project-boards-in-your-repository-or-organization/ - - /articles/managing-access-to-your-user-account-s-project-boards - - /articles/managing-access-to-your-user-accounts-project-boards - - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -Un colaborador es una persona que tiene permisos a tablero de proyecto de tu propiedad. Un colaborador tendrá como predeterminado permisos de acceso de lectura. Para obtener más información, consulta "[Niveles de permiso para tableros de proyecto propiedad del usuario](/articles/permission-levels-for-user-owned-project-boards)." - -### Invitar a colaboradores a un tablero de proyecto propiedad del usuario - -1. Navegua hasta el tablero de proyecto donde deseas agregar a un colaborador. -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -{% data reusables.project-management.collaborator-option %} -5. Debajo de "Search by username, full name or email address" (Buscar por nombre de usuario, nombre completo o dirección de correo electrónico), escribe el nombre, el nombre de usuario o el correo electrónico del colaborador {% data variables.product.prodname_dotcom %}. ![La sección Collaborators (Colaboradores) con el nombre de usuario de Octocat ingresado en el campo de búsqueda](/assets/images/help/projects/org-project-collaborators-find-name.png) -{% data reusables.project-management.add-collaborator %} -7. Por defecto, el nuevo colaborador tiene permisos de lectura. De forma opcional, al lado del nombre del nuevo colaborador, utiliza el menú desplegable y elige un nivel de permiso diferente. ![Sección Colaboradores con el menú desplegable de permisos seleccionado](/assets/images/help/projects/user-project-collaborators-edit-permissions.png) - -### Eliminar a un colaborador de un tablero de proyecto propiedad del usuario - -{% data reusables.project-management.click-menu %} -{% data reusables.project-management.access-collaboration-settings %} -{% data reusables.project-management.collaborator-option %} -{% data reusables.project-management.remove-collaborator %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md deleted file mode 100644 index d1102827f4..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Administrar la configuración de seguridad y análisis para tu cuenta de usuario -intro: 'Puedes controlar las características que dan seguridad y analizan tu código en tus proyectos dentro de {% data variables.product.prodname_dotcom %}.' -versions: - free-pro-team: '*' -topics: - - Accounts -redirect_from: - - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account ---- -### Acerca de la administración de los parámetros de seguridad y análisis - -{% data variables.product.prodname_dotcom %} puede ayudarte a asegurar tus repositorios. Este tema te muestra cómo puedes administrar las características de seguridad y análisis para todos tus repositorios existentes o nuevos. - -Aún puedes administrar las características de seguridad y análisis para los repositorios individuales. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". - -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} - -{% data reusables.security.security-and-analysis-features-enable-read-only %} - -Para encontrar un resumen de la seguridad a nivel de repositorio, consulta la sección "[Acerca de asegurar tu repositorio](/github/administering-a-repository/about-securing-your-repository)". - -### Habilitar o inhabilitar las características para los repositorios existentes - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security-analysis %} -3. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, da clic en **Inhabilitar todo** o **Habilitar todo**. ![Botón de "Habilitar todo" o "Inhabilitar todo" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png) -6. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos en tu organización. ![Opción de "Habilitar predeterminadamente" para los repositorios nuevos](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png) -7. Da clic en **Inhabilitar CARACTERÍSTICA** o **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios que te pertenezcan. ![Botón para inhabilitar o habilitar la característica](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png) - -### Habilitar o inhabilitar las características para los repositorios nuevos - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security-analysis %} -3. Debajo de "Configurar las características de seguridad y análisis", a la derecha de la característica, habilítala o inhabilítala para los repositorios nuevos en tu organización. ![Casilla para habilitar o inhabilitar una característica para los repositorios nuevos](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png) - -### Leer más - -- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Administrar las vulnerabilidades en las dependencias de tu proyecto](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)" -{% if currentVersion == "free-pro-team@latest" %}- "![Mantener tus dependencias actualizadas automáticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% endif %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md deleted file mode 100644 index 715a6c793b..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Administrar el nombre de la rama predeterminada para tus repositorios -intro: Puedes configurar el nombre de la rama predeterminada para todos los repositorios nuevos que crees. -versions: - free-pro-team: '*' - enterprise-server: '>=2.23' - github-ae: '*' -topics: - - Accounts -redirect_from: - - /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories ---- -### Acerca del nombre de la rama predeterminada - -{% data reusables.branches.new-repo-default-branch %} Esta rama se llama `master` actualmente, pero puedes configurar el nombre de la rama predeterminada como mejor se ajuste a tu ambiente de desarrollo. - -{% data reusables.branches.set-default-branch %} - -{% data reusables.branches.rename-existing-branch %} - -### Configurar el nombre de la rama predeterminada - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.repo-tab %} -3. Debajo de "Rama predeterminada del repositorio", da clic en **Cambiar el nombre de la rama predeterminada ahora**. ![Botón de ignorar](/assets/images/help/settings/repo-default-name-button.png) -4. Teclea el nombre predeterminado que quisieras utilizar para las ramas nuevas. ![Caja de texto para ingresar el nombre predeterminado](/assets/images/help/settings/repo-default-name-text.png) -5. Da clic en **Actualizar**. ![Botón de actualizar](/assets/images/help/settings/repo-default-name-update.png) - -### Leer más - -- [Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md deleted file mode 100644 index ad14ad77b6..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Fusionar cuentas de usuarios múltiples -intro: 'Si tienes cuentas separadas para uso laboral y personal, puedes fusionar las cuentas.' -redirect_from: - - /articles/can-i-merge-two-accounts/ - - /articles/keeping-work-and-personal-repositories-separate/ - - /articles/merging-multiple-user-accounts - - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts -versions: - free-pro-team: '*' -topics: - - Accounts ---- -{% tip %} - -**Sugerencia:** recomendamos utilizar únicamente una cuenta de usuario para administrar los repositorios personales y laborales. - -{% endtip %} - -1. [Transfiere cualquier repositorio](/articles/how-to-transfer-a-repository) desde la cuenta que deseas eliminar a la cuenta que deseas mantener. También se transfieren propuestas, solicitudes de extracción y wikis. Verifica que los repositorios existan en la cuenta que deseas mantener. -2. [Actualiza las URL remotas](/articles/changing-a-remote-s-url) en cualquier clon local de los repositorios que se movieron. -3. [Elimina la cuenta](/articles/deleting-your-user-account) que ya no deseas utilizar. - -### Leer más - -- [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md deleted file mode 100644 index 57c497c0a6..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Permission levels for a user account repository -intro: 'A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*.' -redirect_from: - - /articles/permission-levels-for-a-user-account-repository - - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -{% tip %} - -**Tip:** If you require more granular read/write access to a repository owned by your user account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/articles/transferring-a-repository)." - -{% endtip %} - -#### Owner access on a repository owned by a user account - -The repository owner has full control of the repository. In addition to all the permissions allowed by repository collaborators, the repository owner can: - -- {% if currentVersion == "free-pro-team@latest" %}[Invite collaborators](/articles/inviting-collaborators-to-a-personal-repository){% else %}[Add collaborators](/articles/inviting-collaborators-to-a-personal-repository){% endif %} -- Change the visibility of the repository (from [public to private](/articles/making-a-public-repository-private), or from [private to public](/articles/making-a-private-repository-public)){% if currentVersion == "free-pro-team@latest" %} -- [Limit interactions with a repository](/articles/limiting-interactions-with-your-repository){% endif %} -- Merge a pull request on a protected branch, even if there are no approving reviews -- [Delete the repository](/articles/deleting-a-repository) -- [Manage a repository's topics](/articles/classifying-your-repository-with-topics){% if currentVersion == "free-pro-team@latest" %} -- Manage security and analysis settings. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)."{% endif %}{% if currentVersion == "free-pro-team@latest" %} -- [Enable the dependency graph](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository) for a private repository{% endif %}{% if currentVersion == "free-pro-team@latest" %} -- Delete packages. For more information, see "[Deleting a package](/github/managing-packages-with-github-packages/deleting-a-package)."{% endif %} -- Create and edit repository social cards. For more information, see "[Customizing your repository's social media preview](/articles/customizing-your-repositorys-social-media-preview)." -- Make the repository a template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)." -- Receive [{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}security alerts{% endif %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in a repository.{% if currentVersion == "free-pro-team@latest" %} -- Dismiss {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)." -- [Manage data usage for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository){% endif %} -- [Define code owners for the repository](/articles/about-code-owners) -- [Archive repositories](/articles/about-archiving-repositories){% if currentVersion == "free-pro-team@latest" %} -- Create security advisories. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)." -- Display a sponsor button. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %} - -There is only **one owner** of a repository owned by a user account; this permission cannot be shared with another user account. To transfer ownership of a repository to another user, see "[How to transfer a repository](/articles/how-to-transfer-a-repository)." - -#### Collaborator access on a repository owned by a user account - -{% note %} - -**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a user account. - -{% endnote %} - -Collaborators on a personal repository can: - -- Push to (write), pull from (read), and fork (copy) the repository -- Create, apply, and delete labels and milestones -- Open, close, re-open, and assign issues -- Edit and delete comments on commits, pull requests, and issues -- Mark an issue or pull request as a duplicate. For more information, see "[About duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)." -- Open, merge and close pull requests -- Apply suggested changes to pull requests. For more information, see "[Incorporating feedback in your pull request](/articles/incorporating-feedback-in-your-pull-request)." -- Send pull requests from forks of the repository{% if currentVersion == "free-pro-team@latest" %} -- Publish, view, and install packages. For more information, see "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)."{% endif %} -- Create and edit Wikis -- Create and edit releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository). -- Remove themselves as collaborators on the repository -- Submit a review on a pull request that will affect its mergeability -- Act as a designated code owner for the repository. For more information, see "[About code owners](/articles/about-code-owners)." -- Lock a conversation. For more information, see "[Locking conversations](/articles/locking-conversations)."{% if currentVersion == "free-pro-team@latest" %} -- Report abusive content to {% data variables.contact.contact_support %}. For more information, see "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)."{% endif %} -- Transfer an issue to a different repository. For more information, see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)." - -### Further reading - -- "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)" -- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md deleted file mode 100644 index ec0017a806..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Niveles de permiso para tableros de proyecto propiedad del usuario -intro: 'Un tablero de proyecto propiedad de una cuenta de usuario tiene dos niveles de permiso: el del propietario del tablero de proyecto y el de los colaboradores.' -redirect_from: - - /articles/permission-levels-for-user-owned-project-boards - - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -### Resumen de permisos - -Solamente hay un único propietario de un tablero de proyecto propiedad de un usuario; este permiso no puede compartirse con otra cuenta de usuario. Además del propietario, otras personas pueden colaborar en tableros de proyecto. - -Hay tres niveles de permisos para los colaboradores de un tablero de proyecto: - -{% data reusables.project-management.project-board-permissions %} - -### Permisos de propietario y de administrador para un tablero de proyecto propiedad del usuario - -El propietario del tablero de proyecto y los colaboradores con acceso de administrador tienen control completo del tablero de proyecto. Además de todos los permisos admitidos por los colaboradores del tablero de proyecto, un propietario y un colaborador de un tablero de proyecto con acceso de administrador pueden: - -- [Administrar, ver y agregar colaboradores](/articles/managing-access-to-your-user-account-s-project-boards) -- [Configurar un tablero de proyecto como público o privado](/articles/changing-project-board-visibility) -- [Eliminar un tablero de proyecto](/articles/deleting-a-project-board/) -- [Cerrar un tablero de proyecto](/articles/closing-a-project-board/) -- [Volver a abrir un tablero de proyecto cerrado](/articles/reopening-a-closed-project-board) - -### Permisos de lectura y escritura para un tablero de proyecto propiedad del usuario - -Los colaboradores con acceso de lectura a un tablero de proyecto propiedad del usuario pueden: - -- Ver un tablero de proyecto -- Copiar un tablero de proyecto -- Filtrar tarjetas en un tablero de proyecto - -Los colaboradores con acceso de escritura a un tablero de proyecto propiedad del usuario pueden: - -- Ver un tablero de proyecto -- Copiar un tablero de proyecto -- Filtrar tarjetas en un tablero de proyecto -- Editar un tablero de proyecto -- Vincular un repositorio a un tablero de proyecto -- Configurar la automatización de tableros de proyecto -- Copiar un tablero de proyecto -- Agregar propuestas y solicitudes de extracción a un tablero de proyecto -- Agregar notas a un tablero de proyecto -- Rastrear el avance de un tablero de proyecto -- Archivar tarjetas en un tablero de proyecto - -### Visibilidad del tablero de proyecto - -Puedes cambiar la visibilidad de un tablero de proyecto de privado a público y viceversa. Por defecto, los tableros de proyecto propiedad del usuario son privados. Para obtener más información, consulta "[Cambiar la visibilidad de un tablero de proyecto](/articles/changing-project-board-visibility)". - -### Leer más - - - "[Administrar el acceso a los tableros de proyectos de tu cuenta de usuario](/articles/managing-access-to-your-user-account-s-project-boards)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md deleted file mode 100644 index ad0db78653..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: ¿Qué función cumple la casilla de verificación 'Available for hire' (Disponible para contratación)? -intro: Utiliza la casilla de verificación **Available for hire** (Disponible para contratación) para ver las publicaciones de Empleos de GitHub dentro de GitHub. -redirect_from: - - /articles/what-does-the-available-for-hire-checkbox-do - - /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do -versions: - free-pro-team: '*' -topics: - - Accounts ---- -El tablero [Empleos de GitHub](https://jobs.github.com/) es una buena manera de encontrar trabajo en el sector de tecnología. Puedes elegir para ver los trabajos publicados allí en tu tablero de GitHub. - -![Anuncios de Empleos GitHub en el tablero](/assets/images/help/settings/jobs-ads-on-dashboard.png) - -{% data reusables.user_settings.access_settings %} -2. Dentro de Jobs Profile (Perfil de trabajos), selecciona **Available for hire (Disponible para contratación)**, después haz clic en **Save jobs profile (Guardar perfil de trabajos)**. ![Configuraciones de perfil de trabajos](/assets/images/help/settings/jobs-profile-settings.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md deleted file mode 100644 index 08d98dd8ec..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Acerca de la membresía de una organización -intro: Puedes convertirte en miembro de una organización para colaborar con los compañeros de trabajo o los colaboradores de código abierto en muchos repositorios a la vez. -redirect_from: - - /articles/about-organization-membership - - /github/setting-up-and-managing-your-github-user-account/about-organization-membership -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -Un propietario de la organización puede invitarte a unirte a su organización como miembro, gerente de facturación o propietario. Un miembro o propietario de la organización con privilegios de administrador para un repositorio puede invitarte a colaborar en uno o más repositorios como un colaborador externo. Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". - -Puedes acceder a las organizaciones de las que eres miembro en tu página de perfil. Para obtener más información, consulta "[Acceder a una organización](/articles/accessing-an-organization)". - -Cuando aceptas una invitación para unirte a una organización, el propietario de la organización puede ver lo siguiente: - -- La información de tu perfil público. -- Tu dirección de correo electrónico. -- Si tienes la autorización de dos factores activada. -- Los repositorios a los que tienes acceso dentro de la organización y tu nivel de acceso. -- Ciertas actividades dentro de la organización. -- País del origen de la solicitud. -- Tu dirección IP. - -Para obtener más información, consulta la {% data variables.product.prodname_dotcom %} Declaración de privacidad. - - {% note %} - - **Nota:** Los propietarios no pueden ver las direcciones IP del miembro en el registro de auditoría de la organización. En el caso de un incidente de seguridad, como una cuenta comprometida o la divulgación involuntaria de datos confidenciales, los propietarios de la organización pueden solicitar los detalles de acceso a los repositorios privados. La información que devolvemos puede incluir tu dirección IP. - - {% endnote %} - -Por defecto, la visibilidad de los miembros de tu organización se establece como privada. Puede elegir publicar miembros individuales de la organización en tu perfil. Para obtener más información, consulta "[Publicar u ocultar los miembros de la organización](/articles/publicizing-or-hiding-organization-membership)". - -{% if currentVersion == "free-pro-team@latest" %} - -Si tu organización pertenece a una cuenta de empresa, automáticamente eres un miembro de la cuenta de empresa y visible para los propietarios de la cuenta de empresa. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/articles/about-enterprise-accounts)". - -{% endif %} - -Puedes dejar una organización en cualquier momento. Para obtener más información, consulta "[Cómo eliminarte de una organización](/articles/removing-yourself-from-an-organization)". - -### Leer más - -- "[Acerca de las organizaciones](/articles/about-organizations)" -- "[Administrar tu membresía en organizaciones](/articles/managing-your-membership-in-organizations)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md deleted file mode 100644 index 327e386867..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Acceder a una organización -intro: 'Para acceder a una organización de la que eres miembro, debes iniciar sesión en tu cuenta de usuario personal.' -redirect_from: - - /articles/error-cannot-log-in-that-account-is-an-organization/ - - /articles/cannot-log-in-that-account-is-an-organization/ - - /articles/how-do-i-access-my-organization-account/ - - /articles/accessing-an-organization - - /github/setting-up-and-managing-your-github-user-account/accessing-an-organization -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -{% tip %} - -**Sugerencia:** Solo los propietarios de la organización pueden ver y cambiar los parámetros de la cuenta para una organización. - -{% endtip %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md deleted file mode 100644 index f009e1c1bc..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Administrar tu membresía en organizaciones -intro: 'Si eres un miembro de una organización, puedes publicar u ocultar tu membresía, ver los roles de otras personas y eliminarte de una organización.' -redirect_from: - - /articles/managing-your-membership-in-organizations -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts -children: - - /about-organization-membership - - /accessing-an-organization - - /viewing-peoples-roles-in-an-organization - - /requesting-organization-approval-for-oauth-apps - - /publicizing-or-hiding-organization-membership - - /managing-your-scheduled-reminders - - /removing-yourself-from-an-organization ---- - diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md deleted file mode 100644 index 3018cddc80..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Administrar tus recordatorios programados -intro: Obtén recordatorios en Slack cuando tú o tu equipo tenga solicitudes de extracción pendientes de revisión. -versions: - free-pro-team: '*' -topics: - - Accounts -redirect_from: - - /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders ---- -### Acerca de los recordatorios programados para usuarios - -Los recordatorios programados se utilizan para garantizar que los usuarios se enfoquen en las solicitudes de revisión más importantes que requieren de su atención. Los recordatorios programados para solicitudes de extracción te enviarán un mensaje en Slack con las solicitudes de extracción que estén abiertas y necesiten de tu revisión en un periodo específico. Por ejemplo, puedes configurar tus recordatorios programados para que te envíen un mensaje en Slack cada mañana a las 10 AM con las solicitudes de extracción que requieren de tu revisión o de la de alguno de tus equipos. - -Para ciertos eventos, también puedes habilitar las alertas en tiempo real para los recordatorios programados. Las alertas en tiempo real se envían a tu canal de Slack tan pronto se suscita un evento importante, tal como cuando se te asigna una revisión. - -Puedes configurar recordatorios programados para solicitudes de revisión a nivel personal o a nivel de equipo para las solicitudes de extracción en las organizaciones de las cuales eres miembro. Antes de que puedas crear un recordatorio programado para ti mismo, un propietario de la organización debe autorizar tu espacio de trabajo en Slack. Para obtener más información, consulta la sección "[Administrar recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)". - -### Crear recordatorios programados para tu cuenta de usuario - -{% data reusables.user_settings.access_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/profile/scheduled-reminders-profile.png) -3. Da clic en **Editar** a un costado de la organización para la cual quieres programar un recordatorio. ![Botón de editar recordatorios programados](/assets/images/help/settings/scheduled-reminders-org-choice.png) -{% data reusables.reminders.add-reminder %} -{% data reusables.reminders.authorize-slack %} -{% data reusables.reminders.days-dropdown %} -{% data reusables.reminders.times-dropdowns %} -8. Opcionalmente, para recibir recordatorios programados para las revisiones a las cuales se te ha asignado, selecciona **Revisar las solicitudes que se te han asignado**. ![Casilla de revisar las solicitudes que se te han asignado](/assets/images/help/profile/scheduled-reminders-your-requests.png) -9. Opcionalmente, para recibir los recordatorios programados para las revisiones que se han asignado a algún equipo del cual seas miembro, selecciona **Revisar solicitudes asignadas a tu equipo**. ![Casilla de revisar las solicitudes que se han asignado a tu equipo](/assets/images/help/profile/scheduled-reminders-your-team-requests.png) -{% data reusables.reminders.real-time-alerts %} -![Casilla para habilitar las alertas en tiempo real](/assets/images/help/settings/scheduled-reminders-real-time-alerts-personal.png) -{% data reusables.reminders.create-reminder %} - -### Administrar recordatorios programados para tu cuenta de usuario -{% data reusables.user_settings.access_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/profile/scheduled-reminders-profile.png) -3. Da clic en **Editar** a un costado de la organización para la cual quieres editar los recordatorios programados. ![Botón de editar recordatorios programados](/assets/images/help/settings/scheduled-reminders-org-choice.png) -{% data reusables.reminders.edit-page %} -{% data reusables.reminders.update-buttons %} - -### Borrar recordatorios programados para tu cuenta de usuario -{% data reusables.user_settings.access_settings %} -{% data reusables.reminders.scheduled-reminders %} -![Botón de recordatorios programados](/assets/images/help/profile/scheduled-reminders-profile.png) -3. Da clic en **Editar** a un costado de la organización para la cual quieres borrar un recordatorio. ![Botón de editar recordatorios programados](/assets/images/help/settings/scheduled-reminders-org-choice.png) -{% data reusables.reminders.delete %} - -### Leer más - -- "[Administrar los recordatorios programados para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization)" -- "[Administrar los recordatorios programados para tu equipo](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md deleted file mode 100644 index fb4b326acc..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Divulgar u ocultar membresía de la organización -intro: 'Si te gustaría decirle al mundo a qué organizaciones perteneces, puedes mostrar los avatares de las organizaciones en tu perfil.' -redirect_from: - - /articles/publicizing-or-concealing-organization-membership/ - - /articles/publicizing-or-hiding-organization-membership - - /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -![Casilla de perfil de organizaciones](/assets/images/help/profile/profile_orgs_box.png) - -### Cambiar la visibilidad de la membresía de tu organización - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Ubica tu nombre de usuario en la lista de miembros. Si la lista es grande, puedes buscar tu nombre de usuario en la casilla de búsqueda. ![Casilla de búsqueda de miembro de la organización](/assets/images/help/organizations/member-search-box.png) -5. En el menú a la derecha de tu nombre de usuario, elige una nueva opción de visibilidad: - - Para divulgar tu membresía, elige **Public (Pública)**. - - Para esconder tu membresía, elige **Private (Privada)**. ![Enlace de visibilidad de un miembro de la organización](/assets/images/help/organizations/member-visibility-link.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md deleted file mode 100644 index 374c6dcea8..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Eliminarte de una organización -intro: 'Si eres colaborador externo o miembro de una organización, puedes abandonar la organización en cualquier momento.' -redirect_from: - - /articles/how-do-i-remove-myself-from-an-organization/ - - /articles/removing-yourself-from-an-organization - - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -{% if currentVersion == "free-pro-team@latest" %} - -{% warning %} - -**Advertencia:** Si actualmente eres responsable de pagar {% data variables.product.product_name %} en tu organización, eliminarte de la organización **no** actualiza la información de facturación archivada de la organización. Si actualmente eres responsable de la facturación, **debes** hacer que otro propietario o gerente de facturación de la organización [actualice el método de pago de la organización](/articles/adding-or-editing-a-payment-method). - -Para obtener más información, consulta "[Transferir la propiedad de la organización](/articles/transferring-organization-ownership)". - -{% endwarning %} - -{% endif %} - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.organizations %} -3. En "Organizations" (Organizaciones), busca la organización de la que quieres eliminarte, luego haz clic en **Leave** (Abandonar). ![Botón Leave organization (Abandonar organización) con roles exhibidos](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png) diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md deleted file mode 100644 index ca03864e37..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Solicitar aprobación de la organización para OAuth Apps -intro: 'Los miembros de la organización pueden solicitar que un propietario apruebe el acceso a los recursos de la organización para {% data variables.product.prodname_oauth_app %}.' -redirect_from: - - /articles/requesting-organization-approval-for-third-party-applications/ - - /articles/requesting-organization-approval-for-your-authorized-applications/ - - /articles/requesting-organization-approval-for-oauth-apps - - /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps -versions: - free-pro-team: '*' -topics: - - Accounts ---- -### Solicitar aprobación de la organización para una {% data variables.product.prodname_oauth_app %} que ya has autorizado para tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.access_applications %} -{% data reusables.user_settings.access_authorized_oauth_apps %} -3. En la lista de aplicaciones, haz clic en el nombre de la {% data variables.product.prodname_oauth_app %} para la que quieres solicitar acceso. ![Botón View application (Ver aplicación)](/assets/images/help/settings/settings-third-party-view-app.png) -4. Al lado de la organización a la que quieres que {% data variables.product.prodname_oauth_app %} acceda, haz clic en **Request access** (Solicitar acceso). ![Botón Request access (Solicitar acceso)](/assets/images/help/settings/settings-third-party-request-access.png) -5. Después de revisar la información acerca de solicitarle a {% data variables.product.prodname_oauth_app %} acceso, haz clic en **Request approval from owners** (Solicitar aprobación de los propietarios). ![Botón Request approval (Solicitar aprobación)](/assets/images/help/settings/oauth-access-request-approval.png) - -### Leer más - -- "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md deleted file mode 100644 index 4b74a94f0d..0000000000 --- a/translations/es-XL/content/github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Ver los roles de las personas en una organización -intro: 'Puedes ver una lista de personas en tu organización y filtrar por su rol. Para obtener más información sobre roles en la organización, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)."' -redirect_from: - - /articles/viewing-people-s-roles-in-an-organization - - /articles/viewing-peoples-roles-in-an-organization - - /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Accounts ---- -{% note %} - -**Nota:** debes ser miembro de una organización para ver los roles de las personas en tu organización. - -{% endnote %} - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.people %} -4. Verás una lista de personas en tu organización. Para filtrar esta lista por rol, haz clic en **Role (Rol)** y seleccionar el rol que estás buscando. ![click-role](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png) diff --git a/translations/es-XL/content/github/site-policy/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md b/translations/es-XL/content/github/site-policy/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md deleted file mode 100644 index 5fd10cdcca..0000000000 --- a/translations/es-XL/content/github/site-policy/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Anexo a los Términos de servicio de GitHub aplicables a los usuarios del Gobierno federal de los EE. UU. Federal Government Users -redirect_from: - - /articles/amendment-to-github-terms-of-service-applicable-to-government-users/ - - /articles/proposed-amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/ - - /articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users - - /articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users -versions: - free-pro-team: '*' ---- - -{% tip %} - -Esta modificación a los [Términos de Servicio](/articles/github-terms-of-service) de GitHub solo se aplica a los usuarios que están usando GitHub en nombre del gobierno federal de Estados Unidos. If you are not using GitHub on behalf of the U.S. Si no estás usando GitHub en nombre del gobierno federal estadounidense, los [Términos de Servicio de GitHub](/articles/github-terms-of-service) estándar aplicarán para ti. - -{% endtip %} - -Esta enmienda es un contrato entre GitHub, Inc. ("GitHub" o "La Compañía") y los usuarios del del sitio web de GitHub (el "Servicio") en el gobierno federal de los EE.UU. Y se aplica únicamente a cualquier agencia de gobierno federal de los EE.UU. y a sus usuarios que utilicen o accedan al Servicio por parte del gobierno federal de los EE.UU. (el "Gobierno"). - -Se requiere que, cuando tú, como entidad del gobierno de los Estados Unidos, aceptes los términos de contrato con otras partes, sigas las leyes y regulaciones aplicables, incluyendo aquellas que se relacionan con ética; privacidad y seguridad; accesibilidad; registros de retención; limitaciones de compensación; limitaciones de ley fiscal, publicidad y respaldo; libertad de la información; derecho aplicable y foro de disputa para resoluciones. - -GitHub y tú (juntos, como las "Partes") acuerdan que las modificaciones a las [Condiciones de Servicio](/articles/github-terms-of-service) (las "ToS") son adecuadas para adaptarse a tu estado legal, tu misión pública (en contraste con la privada), y otras circunstancias específicas. Por consiguiente, los ToS se modifican por la presente con esta enmienda ya que conciernen al uso gubernamental del sitio y servicios de la compañía: - -### A. Propósito público - -1. *Entidad gubernamental* - "Tú" dentro de los ToS deberás representar al gobierno mismo y no deberás comprometer, en su capacidad individual, a la(s) persona(s) que utilicen el sitio o los servicios de la Compañía en nombre del Gobierno. La Compañía verá únicamente por el Gobierno para reforzar cualquier fuga o violación de los ToS que realicen dichos individuos sujetos a la ley federal. - -2. *Publicidad* - La presente Compañía acuerda no servir o mostrar ningún tipo de publicidad o solicitud de terceros en ninguna página dentro del sitio de la Compañía que muestre contenido creado por o bajo el control del Gobierno. Esta exclusión no se extenderá a los anuncios caseros, los cuales podrá emitir la Compañía en páginas de forma no intrusiva. Las obligaciones antes citadas son contingentes sobre las direcciones de correo electrónico designadas en tu página de detalles que termina en `.gov`, `.mil`, o `.fed.us`. - -### B. Tu contenido en GitHub - -1. *Acceso y uso* - La Compañía reconoce que el uso del Servicio por parte del Gobierno puede energizar una interacción ciudadana significativa. El lenguaje en los ToS que permite a la Compañía terminar el servicio, el rehusarse a eliminar cualquier Contenido, o cerrar una cuenta gubernamental, en cualquier momento, por cualquier razón, se modifica para reflejar el acuerdo de las partes en el que la Compañía puede modificar o descontinuar un servicio de manera unilateral, temporalmente o permanentemente, rehusar o eliminar cualquier Contenido, y/o finalizar la cuenta del Gobierno únicamente por incumplimiento de las obligaciones del mismo explicadas en los ToS o por su fallo material para cumplir con las instrucciones y lineamientos publicados en el Servicio, o si la Compañía deja de operar el Servicio en general. La Compañía proporcionará al Gobierno oportunidad razonable para resarcir cualquier incumplimiento o fallo por parte de éste. - -2. *Sin respaldo* - La Compañía acuerda que tus sellos, marcas registradas, logos, marcas de servicio, nombres comerciales, y el hecho de que tienes presencia en el sitio de la Compañía y utilizas sus servicios, no deberá utilizarse por parte de la Compañía de forma tal que declare o implique que respaldas, patrocinas o recomidas los productos o servicios de la Compañía, o que estas entidades los consideran superiores a cualquier otro producto o servicio. Con excepción de las páginas cuyo diseño y contenido está bajo control del Gobierno, o para los enlaces a o promoción de dichas páginas, la Compañía acuerda no mostrar sellos o logos gubernamentales en su página principal o en cualquier otra parte de su Sitio, a menos de que el Gobierno u otra autoridad gubernamental federal competente otorgue dicho permiso. La Compañía puede listar el nombre del Gobierno en una lista de clientes disponible al público mientras que este nombre no se muestre en una forma más prominente que cualquier otro nombre de terceros. - -3. *Disposición de datos* - En caso de rescisión del servicio, dentro de 30 días de dicha rescisión, bajo solicitud, la Compañía te proporcionara todo el contenido generado por el usuario que esté visible al público en general a través de los Sitios que creaste en la Compañía. Los datos se proporcionarán en un formato de archivo o de base de datos común de acuerdo a lo que la Compañía considere adecuado. La compañía no proporcionara datos si el hacerlo viola su política de privacidad, la cual está disponible en [https://docs.github.com/privacy](/privacy). - -### C. Planes pagados y no pagados - -1. *Acuerdo para no generar costos* - Nada en esta enmienda o ToS te obliga a gastar créditos o incurrir en obligaciones financieras. Las Partes reconocen y acuerdan que ninguna de las obligaciones que derivan de esta Enmienda o ToS son contingentes sobre el pago de cuotas de ninguna de las partes. GitHub puede ofrecer, a discreción de La Compañía, una cuenta gratuita con un plan de uso gratuito, tal como el Plan Gratuito para Código Abierto, y en dicho caso, esta Enmienda aplicará al uso del Gobierno bajo el plan/cuenta gratuito(a). Esta Enmienda también es aplicable cuando el Gobierno utilice alguno de los planes de uso pagados de GitHub. - -2. *Responsabilidades del Gobierno bajo los planes de uso pagados* - Reconoces que, si bien la Compañía te proporcionara servicios bajo un plan gratuito, ésta se reserva el derecho para comenzar a cobrar por dicho servicio en algún momento en el futuro. La Compañía te notificará con por lo menos 30 días de antelación sobre cualquier cambio que involucre el cobro de cuotas para un servicio gratuito. También entiendes que la Compañía ofrece planes pagados con el cobro de una cuota. Las Partes entienden que los servicios que involucran el pago de una cuota son categóricamente diferentes a aquellos gratuitos, y están sujetos a los procesos y reglas federales de contratación. Antes de que el Gobierno decida ingresar en una suscripción de negocios o de empresa, o en cualquier otro servicio que implique elpago de cuotas que esta Compañía o cualquier proveedor alternativo pueda ofrecer ahora o en el futuro, tu acuerdas: determinar que el Gobierno necesita estos servicios adicionales que implican el pago de una cuota; considerar el valor de las suscripciones en comparación con los servicios similares disponibles en cualquier otra parte; determinar que los fondos del Gobierno están disponibles para dichos pagos; utilizar adecuadamente la Tarjeta de Pagos Gubernamental, si ésta se utiliza como método de pago; revisar cualquier ToS aplicable de conformidad con la ley de contratación federal; y todos los demás aspectos para seguir las leyes de adquisición federal aplicables, regulaciones y lineamientos de agencia (incluyendo aquellos relacionados con pagos) cuando se inicie dicha acción por separado. - -3. *No se crea relación de negocioso alguna* - Las Partes son entidades independientes y ninguna parte de esta Enmienda o ToS crea una agencia, sociedad, empresa conjunta, o relación de empleador/empleado. - -### D. Regulaciones Federales - -1. *Seguridad* - La compañía ejercerá, de buena fue, debida diligencia utilizando prácticas comerciales de negocios generalmente aceptadas para la seguridad de TI, para garantizar que los sistemas se operen y mantengan de forma segura, y que se utilicen controles administrativos, técnicos y operacionales para garantizar la seguridad de los datos y sistemas. Reconociendo la naturaleza cambiante de la Web, la Compañía trabajará continuamente con los usuarios para garantizar que sus productos y servicios se operen y mantengan de forma segura. La compañía acuerda discutir e implementar controles de seguridad adicionales de acuerdo el Gobierno lo considere necesario para adecuarse a la Ley Federal de Administración de Seguridad Informática (FISMA, por sus siglas en inglés), 44 U. S.C. 3541 y posteriores. - -2. *Registros Federales* - El Gobierno reconoce que el uso del sitio y servicios de la Compañía requerirá de la administración de registros federales. El contenido generado por el Gobierno y por el usuario deberá cumplir con la definición de registros Federales según lo determinado por la agencia. *Registros Federales* - El Gobierno reconoce que el uso del sitio y servicios de la Compañía requerirá de la administración de registros federales. El contenido generado por el Gobierno y por el usuario deberá cumplir con la definición de registros Federales según lo determinado por la agencia. 21, 29, 31, 33), y con las regulaciones de la Administración Nacional para Archivos y Registros (NARA, por sus siglas en inglés) en el 36 CFR Capítulo XII Subcapítulo B). Administrar los registros incluye, mas no se limita a, almacenamiento seguro, capacidad de recuperación, y eliminación adecuada de todos los registros Federales, incluyendo la transferencia de registros permanentemente valiosos para NARA en un formato y forma aceptable para NARA al momento de la transferencia. El Gobierno se responsabiliza de garantizar que la Compañía cumpla con las leyes y regulaciones aplicables para administración de registros a través de la vida y terminación del Acuerdo. - -### E. Condiciones Generales - -1. *Indemnización* - Cualquier aprovisionamiento de las ToS relacionado con indemnización, daños, cuotas de abogados, y liquidaciones quedan exentas. La responsabilidad del gobierno por cualquier incumplimiento de las ToS o de este Acuerdo, o por cualquier reclamación, demanda, juicio o procedimiento que se derive de las ToS o de este acuerdo, deberá determinarse de acuerdo con la Ley Federal de Reclamos al Estado, o por otra autoridad regente. La responsabilidad de la Compañía para cualquier incumplimiento de las ToS o de este Acuerdo, bajo cualquier reclamación, demanda, juicio o procedimiento que se derive de los mismos, deberá determinarse de acuerdo con la ley federal o estatal aplicable. - -2. *Limitación de la responsabilidad* - Las partes acuerdan que nada dentro de la cláusula de Limitación de Responsabilidades o en cualquier otra parte de las ToS otorga de alguna manera a la Compañía una exención, renuncia o limitación de las responsabilidades que atañen a cualquier violación futura, reciente o pasada de la ley federal. - -3. *Foro y derecho aplicable* - El aprovisionamiento de resolución de disputas en las ToS se encuentra eliminado por la presente. Las ToS y esta Enmienda deberán regirse, interpretarse y hacerse cumplir de acuerdo con las leyes federales aplicables de los Estados Unidos de América y la jurisdicción exclusiva estará en las cortes federales adecuadas de los EE.UU. federal courts. Hasta donde lo permita la ley federal, las leyes del Estado de California aplicarán en ausencia de la ley federal. - -4. *Cesión* - Ninguna de las partes podrá asignar sus obligaciones en esta Enmienda o en las ToS a ningún tercero sin primero obtener consentimiento por escrito de la otra, sin embargo, GitHub podrá, sin el consentimiento del Gobierno, asignar sus obligaciones al Gobierno que esté utilizando el servicio bajo un plan gratuito de acuerdo con esta Enmienda o con las ToS a un afiliado, sucesor o adquiriente, según sea el caso, en conexión con una empresa fusionada, adquisición, reorganización o consolidación corporativa, o con la venta de todos o substancialmente todos los bienes de GitHub. - -### F. Cambios a este acuerdo - -1. *Precedencia; Enmiendas Subsecuentes; Terminación* - Esta Enmienda constituye una enmienda a las ToS. Quedan exentas las secciones de las ToS en donde se indica que éstas no pueden ser modificadas o que por sí solas constituyen todo el acuerdo entre las partes. Si existe algún conflicto entre esta Enmienda y las ToS, o entre esta Enmienda y otras reglas o políticas del sitio o servicios de la compañía, esta Enmienda prevalecerá. Esta Enmienda podrá tener enmiendas subsecuentes únicamente bajo un acuerdo por escrito que ejecuten ambas partes. El Gobierno podrá cerrar su cuenta y rescindir este acuerdo en cualquier momento. La Compañía podrá cerrar la cuenta del Gobierno y rescindir este acuerdo después de 30 días a partir de la notificación por rescrito, pero el Gobierno no no tendrá acceso al reembolso de cualquier cuota pagada. - -2. *Publicación y disponibilidad de esta Enmienda* - Las partes acuerdan que esta Enmienda no contiene información confidencial o propietaria, y ninguna de las partes podrá lanzarla al público en general. diff --git a/translations/es-XL/content/github/site-policy/dmca-takedown-policy.md b/translations/es-XL/content/github/site-policy/dmca-takedown-policy.md deleted file mode 100644 index f2093fe570..0000000000 --- a/translations/es-XL/content/github/site-policy/dmca-takedown-policy.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: Política de retiro de DMCA -redirect_from: - - /dmca/ - - /dmca-takedown/ - - /dmca-takedown-policy/ - - /articles/dmca-takedown/ - - /articles/dmca-takedown-policy -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Bienvenido a la Guía sobre la Ley de Derechos de Autor del Milenio Digital de GitHub, comúnmente conocida como la "DMCA". Esta página no está pensada como un manual extenso del estatuto. Sin embargo, si has recibido un aviso de retiro de la DMCA orientado al contenido que has publicado en GitHub o si eres un titular de derechos que busca proponer dicho aviso, esperamos que esta página ayude a desmitificar la ley un poco, así como nuestras políticas para cumplirla. - -(Si solo deseas enviar un aviso, puedes [ir al final del documento](#f-submitting-notices).) - -Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal. - -### ¿Qué es la DMCA? - -Para entender la DMCA y algunas de las orientaciones de la política, tal vez sea útil considerar la duración antes de que se promulgara. - -La DMCA proporciona un puerto seguro para los proveedores de servicios que albergan contenido generado por los usuarios. Dado que incluso una sola reclamación de infracción de derechos de autor puede conllevar daños estatutarios por hasta $150,000, la posibilidad de responsabilizarse de los contenidos generados por los usuarios podría ser muy perjudicial para los proveedores de servicios. Con daños potenciales multiplicados a través de millones de usuarios, la computación en la nube y los sitios de contenido generados por usuarios como YouTube, Facebook, o GitHub probablemente [nunca habrían existido](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/) sin la DMCA (o al menos sin pasar parte de ese costo a sus usuarios). - -La DMCA aborda este problema mediante la creación de un [puerto seguro de responsabilidad de derechos de autor](https://www.copyright.gov/title17/92chap5.html#512) para los proveedores de servicios de Internet que presuntamente infrinjan el contenido generado por los usuarios. Esencialmente, mientras un proveedor de servicios siga las reglas de notificación y retiro de la DMCA, no será responsable de la infracción de derechos de autor con base en el contenido generado por los usuarios. Debido a esto, es importante que GitHub mantenga su estado de puerto seguro de la DMCA. - -### Avisos de la DMCA en Nutshell - -La DMCA proporciona dos procedimientos claros y sencillos sobre los que todos los usuarios de GitHub deberían tener conocimiento: (i) un procedimiento [de notificación de retiro](/articles/guide-to-submitting-a-dmca-takedown-notice) para que los titulares de los derechos de autor soliciten que se elimine el contenido; y (ii) una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice) para que se reactive el contenido, cuando se elimina por error o identificación incorrecta. - -Los propietarios de derechos de autor utilizan [notificaciones de retiro de la DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice) para solicitar a GitHub que retire el contenido que consideran infractor. Si eres diseñador de software o desarrollador, creas contenido con derechos de autor todos los días. Si alguien más está utilizando tu contenido con derechos de autor sin autorización dentro de GitHub, puedes enviarnos una notificación de retiro de la DMCA para solicitar que se cambie o elimine el contenido que comete dicha violación. - -Por otro lado, se pueden utilizar [contra notificaciones](/articles/guide-to-submitting-a-dmca-counter-notice) para corregir errores. Quizá la persona que envía la notificación de retiro no tiene los derechos de autor o no se percató que tienes una licencia o cometió algún otro error en su notificación de retiro. Ya que GitHub normalmente no puede saber si ha ocurrido un error, la contra notificación de la DMCA te permite hacernos saber y solicitar que le volvamos a poner el contenido nuevamente. - -El proceso de eliminación notificación y retiro de la DMCA debe utilizarse únicamente para reclamaciones sobre violaciones de derechos de autor. Las notificaciones enviadas a través de nuestro proceso DMCA deben identificar obras o trabajos protegidos por derechos de autor que supuestamente están siendo infringidos. El proceso no puede utilizarse para otras reclamaciones, tales como quejas sobre presuntas [infracciones de marcas](/articles/github-trademark-policy/) o [datos sensibles](/articles/github-sensitive-data-removal-policy/); ofrecemos procesos separados para esas situaciones. - -### A. ¿Cómo funciona realmente? - -El marco de la DMCA es un poco como pasar notas en clase. El propietario de los derechos de autor entrega a GitHub una reclamación sobre un usuario. Si está redactado correctamente, pasamos la queja al usuario. Si el usuario cuestiona la reclamación, puede regresar una nota afirmando. GitHub ejerce poca discreción en el proceso aparte de determinar si los avisos cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que las notificaciones deben realizarse bajo pena de perjurio. - -Aquí están los pasos básicos en el proceso. - -1. **El Propietario de Derechos de Autor investiga.** Un propietario de los derechos de autor siempre debe realizar una investigación inicial para confirmar (a) que son propietarios de los derechos de autor de una obra original y (b) que el contenido de GitHub no está autorizado y es infractor. Esto incluye confirmar que el uso no está protegido como [uso razonable](https://www.lumendatabase.org/topics/22). Un uso particular puede ser justo si solamente utiliza una pequeña cantidad de contenido protegido por derechos de autor, utiliza ese contenido de forma transformativa, lo utiliza para fines educativos, o alguna combinación de lo anterior. Dado que el código naturalmente se presta a dichos usos, cada caso de uso es diferente y debe considerarse por separado. -> **Ejemplo:** Un empleado de Acme Web Company encuentra parte del código de la empresa en un repositorio de GitHub. Acme Web Company otorga licencias de su código fuente a diversos socios de confianza. Antes de enviar una notificación de retiro, Acme debe revisar dichas licencias y sus acuerdos para confirmar que el código en GitHub no esté autorizado bajo ninguna de ellas. - -2. **El propietario de los derechos de autor envía una notificación.** Después de realizar una investigación, un propietario de los derechos de autor prepara y envía una [notificación de retiro](/articles/guide-to-submitting-a-dmca-takedown-notice) a GitHub. Suponiendo que la notificación de retiro esté suficientemente detallada de acuerdo con los requisitos legales (como se explica en la [guía práctica](/articles/guide-to-submitting-a-dmca-takedown-notice)), [publicaremos la notificación](#d-transparency) en nuestro [repositorio público](https://github.com/github/dmca) y pasaremos el enlace al usuario afectado. - -3. **GitHub solicita a sus usuarios hacer cambios.** Si la notificación declara que todo el contenido de un repositorio o un paquete están cometiendo una violación, saltaremos al Paso 6 e inhabilitaremos todo el repositorio o paquete expeditamente. De lo contrario, debido a que GitHub no puede inhabilitar el acceso a archivos específicos dentro de un repositorio, nos contactaremos con el usuario que creó el repositorio y les daremos aproximadamente 1 día hábil para eliminar o modificar el contenido especificado en el aviso. Notificaremos al propietario de los derechos de autor si y cuando demos al usuario la oportunidad de hacer cambios. Ya que los paquetes son inmutables, si solo una parte de un paquete incurre en una violación, GitHub necesitará inhabilitar todo el paquete, pero permitiremos su restablecimiento una vez que se elimine la parte que comete la violación. - -4. **El usuario notifica a GitHub acerca de los cambios.** Si el usuario opta por realizar los cambios especificados, *Debe* avísanos dentro de la ventana de aproximadamente 1 día hábil. Si no lo hacen, deshabilitaremos el repositorio (como se describe en el paso 6). Si el usuario nos notifica que realizó cambios, verificaremos que los cambios se hayan realizado y posteriormente notificaremos al propietario de los derechos de autor. - -5. **El titular de los derechos de autor revisa o retrae la notificación.** Si el usuario realiza cambios, el propietario de los derechos de autor debe revisarlos y renovar o revisar su aviso de eliminación si los cambios son insuficientes. GitHub no tomará ninguna acción adicional a menos que el propietario de los derechos de autor se ponga en contacto con nosotros para renovar la notificación de retiro original o presentar uno revisado. Si el propietario de los derechos de autor está satisfecho con los cambios, puede presentar una retracción formal o no hacer nada. GitHub interpretará el silencio durante más de dos semanas como una retracción implícita del aviso de retiro. - -6. **GitHub puede inhabilitar el acceso al contenido.** GitHub inhabilitará el contenido de un usuario si: (i) el propietario de los derechos de autor reclama dichos derechos sobre un paquete o todo el repositorio del usuario (como se explica en el Paso 3); (ii) el usuario no ha realizado cambios después de habérsele proporcionado una oportunidad para hacerlo (de acuerdo con el Paso 4); o (iii) el propietario de los derechos de autor renovó su notificación de retiro después de que el usuario tuvo una oportunidad de realizar los cambios. Si el propietario de los derechos de autor elige *revisar* la notificación, volveremos al paso 2 y repetiremos el proceso como si la notificación revisada fuera un nuevo aviso. - -7. **El usuario puede enviar una contra notificación.** Alentamos a los usuarios que han deshabilitado contenido a consultar con un abogado sobre sus opciones. Si un usuario considera que su contenido fue deshabilitado como resultado de un error o identificación incorrecta, pueden enviarnos una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice). Como en la notificación original, nos aseguraremos de que la contra notificación esté lo suficientemente detallada (como se explica en la [guía práctica](/articles/guide-to-submitting-a-dmca-counter-notice)). Si es así, [lo publicaremos](#d-transparency) en nuestro [repositorio público](https://github.com/github/dmca) y pasaremos el aviso al propietario de los derechos de autor enviándole el enlace. - -8. **El propietario de los derechos de autor puede presentar una acción legal.** Si un propietario de derechos de autor desea mantener el contenido deshabilitado después de recibir una contra notificación, tendrán que iniciar una acción legal que busque una orden judicial para impedir que el usuario se implique en actividades relacionadas con el contenido de GitHub. En otras palabras, podrías ser demandado. Si el propietario de los derechos de autor no da aviso a GitHub en un plazo de 10-14 días, enviando una copia de una queja legal válida presentada en un tribunal de jurisdicción competente, GitHub rehabilitará el contenido inhabilitado. - -### B. ¿Qué hay de las bifurcaciones? (o ¿Qué es una bifurcación?) - -Una de las mejores características de GitHub es la capacidad de los usuarios de "bifurcar" los repositorios de otros. ¿Qué significa esto? En esencia, significa que los usuarios pueden hacer una copia de un proyecto en GitHub en sus propios repositorios. Como la licencia o la ley permite, los usuarios pueden hacer cambios en esa bifurcación para volver al proyecto principal o simplemente mantener como su propia variación de un proyecto. Cada una de estas copias es una "[bifurcación](/articles/github-glossary#fork)" del repositorio original, que a su vez también se puede llamar la "matriz" de la bifurcación. - -GitHub *no deshabilitará automáticamente* las bifurcaciones cuando se deshabilite un repositorio matriz. Esto se debe a que las bifurcaciones pertenecen a diferentes usuarios, pueden haber sido alteradas de manera significativa y pueden ser licenciadas o utilizada de una manera diferente que estén protegidas por la doctrina de uso leal. GitHub no lleva a cabo ninguna investigación independiente sobre las bifucaciones. Esperamos que los propietarios de los derechos de autor lleven a cabo esa investigación y, si creen que las bifurcaciones también están infringiendo, incluyan expresamente bifurcaciones en su notificación de retiro. - -### C. ¿Qué pasa si perdí inadvertidamente el período para hacer cambios? - -Reconocemos que existen muchas razones válidas para que no puedas hacer cambios dentro de la ventana de aproximadamente 1 día laborable que proporcionamos antes de que tu repositorio se inhabilite. Quizá nuestro mensaje fue marcado como spam, tal vez estabas de vacaciones, posiblemente no revisas esa cuenta de correo electrónico regularmente, o probablemente solo estabas ocupado. Lo entendemos. Si respondes para hacernos saber que te hubiera gustado hacer los cambios, pero de alguna manera faltaste a la primera oportunidad, rehabilitaremos el repositorio un tiempo adicional durante aproximadamente 1 día hábil para permitir que realices los cambios. Nuevamente, debes notificarnos que has realizado los cambios con el fin de mantener el repositorio habilitado después de esa ventana de aproximadamente 1 día hávil, como se mencionó anteriormente en el [Paso A. 4](#a-how-does-this-actually-work). Ten en cuenta que sólo te daremos una oportunidad adicional. - -### D. Transparencia - -Creemos que la transparencia es una virtud. El público debería saber qué contenido se está eliminando de GitHub y por qué. Un público informado puede notar y descubrir posibles problemas superficiales que de otro modo pasarían desapercibidos en un sistema poco claro. Publicamos copias redactadas de cualquier aviso legal que recibamos (incluyendo notificaciones originales, contra notificaciones o retracciones) en . No haremos pública tu información de contacto personal; eliminaremos la información personal (excepto los nombres de usuario en las URLs) antes de publicar notificaciones. Sin embargo, no redactaremos ninguna otra información de tu notificación a menos que nos lo solicites específicamente. Estos son algunos ejemplos de una [notificación ](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) publicada y [una contra notificación](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md) para que veas cómo son. Cuando eliminemos el contenido, publicaremos un enlace al aviso relacionado en su lugar. - -Ten también en cuenta que, aunque no publicaremos avisos no modificados, podemos proporcionar una copia completa y no editada de cualquier notificación que recibamos directamente a cualquier parte cuyos derechos se verían afectados por ella. - -### E. Retición de una infracción - -Es la política de GitHub, en circunstancias apropiadas y a su entera discreción, desactivar y terminar las cuentas de los usuarios que puedan infringir los derechos de autor u otros derechos de propiedad intelectual de GitHub u otros. - -### F. Cómo enviar notificaciones - -Si estás listo para enviar una notificación o una contra notificación: -- [Cómo enviar una notificación de la DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice) -- [Cómo enviar una contra notificación de la DMCA](/articles/guide-to-submitting-a-dmca-counter-notice) - -### Conoce más y comunícate - -Si exploras Internet, no es demasiado difícil encontrar comentarios y críticas sobre el sistema de derechos de autor en general y la DMCA en particular. Mientras que GitHub reconoce y aprecia el importante papel que ha desempeñado la DMCA en la promoción de la innovación en línea creemos que las leyes de derechos de autor probablemente podrían usar un patch o dos, o bien una versión completamente nueva. En software, estamos constantemente mejorando y actualizando nuestro código. Piensa en cuánto ha cambiado la tecnología desde 1998, cuando se redactó la DMCA. ¿No tiene sentido actualizar estas leyes que se aplican al software? - -No presumimos de tener todas las respuestas. Pero si eres curioso, aquí tienes algunos enlaces a artículos informativos y entradas de blog que hemos encontrado con opiniones y propuestas para la reforma: - -- [Consecuencias no deseadas: Doce años bajo la DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Constitución de la Frontera Electrónica) -- [Daños y Perjuicios Reglamentarios en la Ley de Derechos de Autor: Un recordatorio en la necesidad de la reforma](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Revisión de la ley María) -- [¿El plazo de protección de los derechos de autor es demasiado largo?](https://the1709blog.blogspot.com/2012/11/is-term-of-protection-of-copyright-too.html) (el 1709 blog) -- [Si vamos a cambiar 'Notificación y Retiro', de la DMCA, centrémonos en su amplio abuso](https://www.techdirt.com/articles/20140314/11350426579/if-were-going-to-change-dmcas-notice-takedown-lets-focus-how-widely-its-abused.shtml) (TechDirt) -- [Oportunidades para la reforma de los derechos de autor](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato sin asociar) -- [Uso Justo de la Doctrina y la Ley de Derechos de Autor del Milenio Digital: ¿Existe un uso justo en Internet bajo la DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Revisión de la Ley de Santa Clara) - -GitHub no necesariamente respalda ninguno de los puntos de vista en esos artículos. Proporcionamos los enlaces para invitarte a conocer más, formar tus propias opiniones y posteriormente llegar a tu(s) representante(s) electos (por ejemplo, en el [Congreso de los Estados Unidos](https://www.govtrack.us/congress/members) o [Parlamento de los EE. UU.](https://www.europarl.europa.eu/meps/en/home)) para buscar los cambios que consideras que deberían llevarse a cabo. Congress or [E.U. Parliament](https://www.europarl.europa.eu/meps/en/home)) to seek whatever changes you think should be made. diff --git a/translations/es-XL/content/github/site-policy/github-acceptable-use-policies.md b/translations/es-XL/content/github/site-policy/github-acceptable-use-policies.md deleted file mode 100644 index 7867345523..0000000000 --- a/translations/es-XL/content/github/site-policy/github-acceptable-use-policies.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: Políticas de uso aceptable de GitHub -redirect_from: - - /articles/github-acceptable-use-policies -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -**Versión simplificada:** _Presentamos una amplia variedad de proyectos en equipo en todo el mundo y dicha cooperación solamente funciona cuando nuestros usuarios pueden trabajar juntos con buenas intenciones. Mientras usas el Servicio, debes cumplir con nuestras políticas de uso aceptable, que incluyen algunas restricciones sobre el contenido que puedes publicar o gestionar en el servicio y otras limitaciones. En síntesis, la idea es que sean geniales entre sí._ - -Los términos en mayúsculas que se utilizan, pero no se definen en estas Políticas de uso aceptable tienen significados asignados en nuestros [Términos de servicio](/articles/github-terms-of-service), [Términos de servicio corporativos](/articles/github-corporate-terms-of-service) y [Declaración de privacidad](/articles/github-privacy-statement). Para los clientes sujetos a los [Términos de servicio corporativos](/articles/github-corporate-terms-of-service), "tú" y "tu/tus" se refieren al "Cliente" o los "Usuarios". "Nosotros", "nuestro", "nuestros" se refieren a "GitHub". - -### 1. Cumplimiento con las leyes y regulaciones -Eres responsable de usar el Servicio de conformidad con todas las leyes, regulaciones y con todas nuestras Políticas de uso aceptable que correspondan. Estas políticas se pueden actualizar cada cierto tiempo y se presentan a continuación. También se puede acceder a ellas en nuestros [Términos de servicio](/articles/github-terms-of-service) y [Términos de servicio corporativos](/articles/github-corporate-terms-of-service). - -### 2. Restricciones de contenido -Bajo ninguna circunstancia los usuarios cargarán, publicarán, presentarán, realizarán o transmitirán ningún contenido en ninguno de los repositorios: - -- que sea ilícito o promueva actividades ilícitas; - -- que constituya o contenga contenido sexualmente explícito u obsceno; - -- que sea calumnioso, difamatorio o fraudulento; - -- que sea discriminatorio u ofensivo hacia cualquier persona o grupo; - -- que represente violencia o la glorifique injustificadamente, incluidas imágenes violentas; - -- que sea o contenga información falsa, inexacta o intencionalmente engañosa que pueda afectar negativamente el interés público (incluyendo la salud, seguridad, integridad de la elección y participación cívica); - -- que contenga o instale cualquier malware o vulnerabilidad de seguridad, o use nuestra plataforma para el envío de vulnerabilidades de seguridad (como parte de un comando y un sistema de control); - -- que infrinja algún derecho de propiedad de cualquiera de las partes, incluidos la patente, el nombre comercial, el secreto comercial, la propiedad intelectual, el derecho a publicidad o cualquier otro derecho. - -### 3. Restricciones de conducta -Mientras usas el Servicio, en ninguna circunstancia puedes hacer lo siguiente: - -- acosar, abusar o amenazar a cualquier persona o grupo, incluidos nuestros empleados, funcionarios y agentes, o cualquier otro usuario, ni incitar violencia hacia ellos; - -- usar nuestros servidores para llevar a cabo cualquier forma de actividad masiva automática excesiva (por ejemplo, correo no deseado o masivo) o colocar una carga indebida en nuestros servidores a través de medios automatizados o retransmitir alguna otra forma de publicidad o solicitudes no requeridas a través de nuestros servidores, como esquemas del tipo "hazte rico rápidamente"; - -- usar nuestros servidores para interrumpir o intentar interrumpir, obtener o intentar obtener acceso no autorizado a cualquier servicio, dispositivo, datos, cuenta o red (a menos que lo autorice el [programa Bug Bounty GitHub](https://bounty.github.com)); - -- hacerte pasar por cualquier persona o entidad, incluidos cualquiera de nuestros empleados o representantes, incluso a través de asociación falsa con GitHub, o falsear de manera fraudulenta tu identidad o el propósito del sitio; - -- violar la privacidad de cualquier tercero, como publicar información personal de otra persona sin su consentimiento. - -### 4. Límites de uso de los servicios -No reproducirás, duplicarás, copiarás, venderás, revenderás o aprovecharás ninguna parte del Servicio, el uso del Servicio o el acceso al Servicio sin autorización expresa por escrito. - -### 5. Restricciones de extracción y uso de la API -La extracción se refiere a extraer datos de nuestro Servicio a través de un proceso automático, como un bot o agente de búsqueda. No se refiere a la recopilación de información a través de nuestra API. Por favor, consulta la sección H de nuestras [Condiciones de Servicio](/articles/github-terms-of-service#h-api-terms) para nuestras Condiciones de la API. Puedes realizar extracciones de nuestro sitio web por los siguientes motivos: - -- Los investigadores pueden extraer del Servicio información pública que no sea personal para los fines de investigación, solo si ninguna publicación de esa investigación será de acceso abierto. -- Los archivistas pueden realizar extracciones del Servicio de datos públicos para los fines de archivo. - -No debes realizar extracciones del sitio para enviar correos masivos, incluidos aquellos con fines de venta de Información personal del Usuario (como se define en la [Declaración de privacidad de GitHub](/articles/github-privacy-statement)), como los destinados a encargados de contratación, cazatalentos y bolsas de trabajo. - -Todo el uso de los datos reunidos a través de la extracción debe cumplir con la [Declaración de privacidad de GitHub](/articles/github-privacy-statement). - -### 6. Privacidad -Está prohibido el uso indebido de la Información personal del Usuario. - -Cualquier persona, entidad o servicio que recopile datos del Servicio debe cumplir con la [Declaración de privacidad de GitHub](/articles/github-privacy-statement), en particular, al respecto de la recopilación de Información personal del Usuario. Si recopilas cualquier Información personal del Usuario desde el Servicio, debes aceptar que solo usarás esa Información personal del Usuario para los fines que ese Usuario autorizó. Aceptas que asegurarás de manera razonable cualquier Información personal del Usuario que hayas reunido desde el Servicio y responderás de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" que hagamos nosotros u otros usuarios. - -### 7. Uso del ancho de banda excesivo -Las limitaciones de ancho de banda del servicio varían en función de las características que utilices. Si determinamos que tu uso del ancho de banda es significativamente excesivo en relación con el de otros usuarios, nos reservamos el derecho a suspender tu Cuenta o limitar el alojamiento de tu archivo o, de otra forma, limitar tu actividad hasta que puedas reducir tu consumo de ancho de banda. Tambien nos reservamos los derechos—después de proporcionar una notificación por adelantado—de borrar repositorios que creamos están colocando una tensión indebida en nuestra infraestructura. Para obtener orientación sobre el uso aceptado de almacenamiento de objetos en los repositorios, refiérete a la sección "[¿Cuál es mi cuota de disco?](/github/managing-large-files/what-is-my-disk-quota)". Para obtener más detalles sobre las limitaciones de ancho de banda de características especiales, consulta la sección [Condiciones Adicionales de Producto de GitHub](/github/site-policy/github-additional-product-terms). - -### 8. Advertising on GitHub -**Versión simplificada:** *Generalmente no prohibimos el uso de GitHub para publicidad. Sin embargo, esperamos que nuestros usuarios sigan ciertas limitaciones, por lo que GitHub no se convierta en un espacio lleno de spam. Nadie desea eso.* - -Aunque entendemos que tal vez deseas promover tu Contenido publicando los nombres o logos de los seguidores de tu Cuenta, el enfoque principal del Contenido publicado en o a través de tu Cuenta al Servicio no debe ser publicidad o marketing promocional. Esto incluye Contenido publicado en o a través de Páginas, Paquetes, repositorios y todas las demás partes del Servicio. Puedes incluir imágenes estáticas, enlaces y textos promocionales en los documentos README o secciones de descripción del proyecto asociadas con tu Cuenta, pero deben estar relacionados con el proyecto que estás alojando en GitHub. No puedes publicitar en las Cuentas de otros Usuarios, por ejemplo, mediante la publicación de contenido monetizado o excesivo en masa. - -No puedes promover o distribuir contenido o actividad ilegal o prohibida por nuestros [Términos de servicio](/github/site-policy/github-terms-of-service/), [Directrices de la comunidad](/github/site-policy/github-community-guidelines/), o [Política de Uso Aceptable](/github/site-policy/github-acceptable-use-policies/), incluyendo una actividad masiva automatizada excesiva (por ejemplo, spamming), esquemas "hazte rico rápidamente" y distorsión o engaño relacionados con tu promoción. - -Si decides alojar cualquier material publicitario o promocional en tu Cuenta, eres el único responsable de cumplir con todas las leyes y regulaciones correspondientes, incluyendo, entre otras, las Directrices sobre Endosos y Testimonios de la Comisión Federal de Comercio de los EE. UU. Federal Trade Commission's Guidelines on Endorsements and Testimonials. Nos reservamos el derecho de eliminar cualquier material promocional o publicidad que, a nuestra entera discreción, viole cualquier término o política de GitHub. - -### 9. Spam y actividad falsa en GitHub -En GitHub se prohíbe la actividad excesiva automatizada y la actividad coordinada falsa, como el spamming. Las actividades prohibidas incluyen: -* distribución masiva de promociones y publicidad prohibida por los términos y políticas de GitHub -* interacciones falsas, tales como cuentas falsas y la actividad automatizada falsa -* abuso de rango, por ejemplo, protagonización automática o la -* creación o participación posterior en los mercados secundarios con la intención de la proliferación de actividades falsas -* usar a GitHub como una plataforma para propagar abusos en otras plataformas -* phishing o intento de phishing - -GitHub se reserva el derecho de eliminar cualquier Contenido que viole esta política. - -### 10. Protección del Usuario -No debes participar de actividades que dañen de manera significativa a otros usuarios. Resolveremos las disputas en favor de la protección de los usuarios como totalidad. diff --git a/translations/es-XL/content/github/site-policy/github-additional-product-terms.md b/translations/es-XL/content/github/site-policy/github-additional-product-terms.md deleted file mode 100644 index 16e94e49a7..0000000000 --- a/translations/es-XL/content/github/site-policy/github-additional-product-terms.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -title: Términos adicionales de los productos de GitHub -versions: - free-pro-team: '*' -topics: - - Policy - - Legal ---- - -Al crear una Cuenta, se le da acceso a muchas características y productos diferentes que forman parte del Servicio. Debido a que muchas de estas características y productos ofrecen una funcionalidad diferente, pueden requerir términos y condiciones adicionales específicas de esa característica o producto. A continuación, hemos enumerado esas características y productos, junto con las correspondientes reglas adicionales que se aplican a esas partes del Servicio. - -Tu uso de GitHub está sujeto a los términos aplicables (el "Contrato") así como a los siguientes términos del producto adicional de GitHub (los "Términos Adicionales"). Al aceptar el Contrato y utilizar los productos y características adicionales, también estás aceptando estos Términos Adicionales. Cualquier violación de las Condiciones Adicionales es una violación del Contrato. Los términos en mayúsculas no definidos en las Condiciones Adicionales tendrán el significado establecido en el Contrato. - -### 1. Marketplace - -Si registras un Producto de Desarrollador a través de GitHub Marketplace, entonces debes aceptar el [Acuerdo de Desarrollador de GitHub Marketplace](/github/site-policy/github-marketplace-developer-agreement), antes de enviar el proyecto a registrar. - -Si compras Productos de Desarollador a través de GitHub Marketplace, los [Términos de servicio de GitHub Marketplace](/github/site-policy/github-marketplace-terms-of-service) controlarán tu compra. El Acuerdo, así como los [Términos de Servicio de GitHub Marketplace](/github/site-policy/github-marketplace-terms-of-service), regirán tu uso de GitHub Marketplace. - -### 2. Integraciones de terceros - -#### a. Creating Applications -Si creas una aplicación de terceros u otro producto de desarrollador que recopile Información Personal de Usuario o Contenido Generado por el Usuario e que se integre con el Servicio a través de la API de GitHub, el Mecanismo OAuth, o de otro modo ("Producto de Desarrollador") y está a disposición de otros usuarios, entonces debe cumplir con los siguientes requisitos: -- Debes cumplir con este Acuerdo y la Declaración de privacidad de GitHub. -- Excepto que se permita de otra manera, por ley o por una licencia, debes limitar tu uso de la Información Personal del Usuario o el Contenido Generado por el Usuario que recopiles para ese propósito para el cual el Usuario ha autorizado su recopilación. -- Debes tomar todas las medidas de seguridad razonables apropiadas para los riesgos, por ejemplo, contra la destrucción accidental o ilegal, o pérdidas accidentales, alteración, divulgación o acceso no autorizado, presentado mediante el procesamiento de la Información Personal del Usuario o Contenido Generado por el Usuario. -- No debes recopilar información personal o contenido generado por el usuario en nombre de GitHub y proporcionar un aviso necesario de tus prácticas de privacidad al Usuario, como por ejemplo, mediante la publicación de una política de privacidad. -- Debes ofrecerle a los Usuarios un método para borrar cualquier Información personal del Usuario o Contenido generado por el Usuario que hayas recopilado por medio de GitHub cuando deje de ser necesario para los fines limitados y especificados para los cuales el Usuario autorizó su recopilación, excepto cuando se requiera su retención por ley o se permita lo contrario, por ejemplo, a través de una licencia. - -#### b. Solicitudes de uso de terceros -Puedes conceder una autorización de Producto de Desarrollador para usar, ingresar y divulgar el contenido de sus repositorios, incluyendo sus repositorios privados. Algunos Productos de Desarrollador están disponibles a través de [GitHub Marketplace](https://github.com/marketplace). Algunos Productos de Desarrollador pueden usarse para realizar tareas automatizadas y a menudo diversos usuarios pueden dirigir las acciones de un Producto de Desarrollador. Sin embargo, si compras y/o configuras un Producto de Desarrollador en tu Cuenta o eres propietario de una Cuenta con un Producto de Desarrollador integrado, entonces serás responsable de las acciones del Producto del Desarrollador que se llevan a cabo en o a través de tu Cuenta. Consulta nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement#third-party-applications) para obtener más información sobre cómo compartimos datos con los Productos del Desarrollador. - -**GitHub no ofrece ninguna garantía de ningún tipo en relación con los Productos de Desarrollador y no se hace responsable de las revelaciones a terceros que autorice a acceder a Tu Contenido. El uso que hagas de cualquier solicitud de terceros corre por tu cuenta y riesgo.** - -### 3. Soporte de Git LFS - -Si activas Git Large File Storage ("Git LFS") en tu Cuenta, podrás obtener, modificar y extraer archivos grandes como esperarías con cualquier archivo que Git gestione. Tu Cuenta viene con cierta cantidad de ancho de banda y almacenamiento para usar con Git LFS, que se puede encontrar en la [documentación de Git LFS](/github/managing-large-files/about-storage-and-bandwidth-usage). El ancho de banda y el uso de almacenamiento de Git LFS se muestran en la [configuración de Tu cuenta](https://github.com/settings/billing). Si deseas utilizar Git LFS más allá del ancho de banda y almacenamiento asignados, puedes [comprar paquetes de datos adicionales](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage). - -### 4. Pages - -Cada cuenta de GitHub viene con acceso al [servicio de alojamiento estático de las páginas de GitHub](/github/working-with-github-pages/about-github-pages). Este servicio de alojamiento está destinado a albergar páginas web estáticas para todos los usuarios, pero principalmente como escaparate para proyectos personales y organizativos. Se permiten algunas iniciativas de monetización en las Páginas, tales como botones de donación y enlaces de financiación colectiva. - -Las páginas de GitHub están sujetas a algunos límites específicos de ancho de banda y uso y podrían no ser adecuadas para algunos usos de alto ancho de banda u otros usos prohibidos. Consulte nuestras [directrices de páginas de GitHub](/github/working-with-github-pages/about-github-pages) para obtener más información. GitHub se reserva el derecho en todo momento de reclamar cualquier subdominio de GitHub sin responsabilidad. - -### 5. Acciones y paquetes - -#### a. Uso de 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. Cada Cuenta viene con cantidades incluidas de cálculo y almacenamiento para usar con las Acciones, dependiendo del plan de tu cuenta, que pueden encontrarse en la [documentación de acciones](/github/automating-your-workflow-with-github-actions/about-github-actions#about-github-actions). Tu uso de acciones se muestra en [la configuración de tu cuenta](https://github.com/settings/billing) y se te notificará por correo electrónico antes de alcanzar el límite de las cantidades incluidas. Si deseas usar Acciones más allá de las cantidades incluidas, puedes [habilitar sobrecargas](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions). - -El uso de las cantidades incluidas y pagadas se calcula en minutos en función del tipo de Acciones que ejecutes (por ejemplo, Linux, Windows, macOS). Los minutos utilizados para el trabajo o tarea de cada acción se redondearán hasta el minuto más cercano. Para cantidades incluidas y dependiendo del tipo de Acción, se puede aplicar un multiplicador a la cantidad de tiempo usado para ejecutar cada trabajo o tarea, antes de ser redondeado hasta el minuto más cercano. Los minutos promedio se cobran al [precio por minuto](https://github.com/features/actions) con base en el tipo de Acciones que ejecutes. Las Acciones y los Paquetes comparten almacenamiento y tu uso de almacenamiento se muestra en la configuración de tu cuenta[](https://github.com/settings/billing). Para obtener más detalles sobre los cálculos de uso de la cantidad incluida, consulta la [documentación de Acciones](/github/automating-your-workflow-with-github-actions/about-github-actions#about-github-actions). - -Las acciones y cualquier elemento del servicio de las Acciones puede utilizarse en violación del Acuerdo, la [Política de Uso Aceptable](/github/site-policy/github-acceptable-use-policies)o las limitaciones de servicio [de las Acciones de GitHub](/github/automating-your-workflow-with-github-actions/about-github-actions#usage-limits). Además, las acciones no deben utilizarse para: -- criptominería; -- usar nuestros servidores para interrumpir,o para ganar o intentar obtener acceso no autorizado a, cualquier servicio, dispositivo, datos, cuenta o red (además de los autorizados por el [programa de recompensas de error de GitHub](https://bounty.github.com)) -- el aproviosionamiento de las aplicaciones autónomas o integradas o del servicio que ofrece acciones o cualquier elemento de ellas 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 -- cualquier otra actividad no relacionada con la producción, prueba, despliegue o publicación del proyecto de software asociado con el repositorio donde se utilizan las Acciones de GitHub. - -Para evitar violaciones de estas limitaciones y abuso de las Acciones de GitHub, GitHub puede controlar tu uso de Acciones de GitHub. El uso indebido de Acciones de GitHub puede resultar en la terminación de trabajos o restricciones en tu capacidad de usar Acciones de GitHub. - -#### b. Uso de paquetes -Los paquetes de GitHub se pueden usar para descargar, publicar y administrar los paquetes de Contenido. Cada plan de Cuenta viene con ancho de banda incluido y cantidades de almacenamiento para tu uso con Paquetes, que se pueden encontrar en la [documentación de Paquetes](/github/managing-packages-with-github-package-registry/about-github-package-registry). Las Acciones y Paquetes comparten almacenamiento entre las dos características de Servicio. El uso de almacenamiento y ancho de banda se muestran en la configuración de tu cuenta [](https://github.com/settings/billing) y se te notificará por correo electrónico antes de alcanzar el límite de las cantidades incluidas. Si deseas utilizar Paquetes más allá de las cantidades de ancho de banda y almacenamiento incluidos, puedes [habilitar sobrecargas](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages). - -El uso de ancho de banda se calcula basándose en la cantidad de datos transferidos fuera de tus repositorios mediante Paquetes, pero las transferencias de paquetes a través de Acciones no contarán para las cantidades incluidas o pagadas. El uso de ancho de banda de los paquetes está limitado por la [Política de Uso Aceptable](/github/site-policy/github-acceptable-use-policies#7-excessive-bandwidth-use) y las cantidades de ancho de banda incluidas se determinan por su plan de [Cuenta](https://github.com/pricing). - -Las Acciones y el uso de almacenamiento de Paquetes se comparte entre las dos características de Servicio. El uso del almacenamiento se calcula como una media ponderada en el transcurso del mes y no se reinicia cada mes. Los repositorios públicos y privados tienen diferentes cantidades de almacenamiento incluidas, y las cantidades incluidas para los repositorios privados dependen de su [plan de Cuenta](https://github.com/pricing). - -#### c. Pago y facturación de las Acciones y los Paquetes -La facturación para las Acciones y los Paquetes se basa en el uso. Las cantidades adicionales de Acciones o Paquetes no se pueden comprar por separado. Para clientes facturados mensualmente, debes tener un método de pago en el archivo para elegir pagar por cantidades adicionales de estas características del Servicio. Se te cobrará mensualmente, recurriendo a la base de tu uso en el mes anterior, a menos que se te cobre por factura. Para clientes facturados, debes pagar las tarifas dentro de los treinta (30) días siguientes a la fecha de la factura de GitHub. Para los clientes que pagan con antelación los excedentes en la característica del servicio, los minutos prepagados no utilizados no se transferirán al próximo período de facturación y no se reembolsarán. - -Puedes establecer un límite de gasto mensual en tu [configuración de cuenta](https://github.com/settings/billing/cost_management). Se te notificará por correo electrónico antes de alcanzar el límite de las cantidades incluidas y el límite de gasto designado de tus cantidades adicionales pagadas. - -### 6. Laboratorio de aprendizaje - -**Inscripción.** Para completar la inscripción en Learning Lab for Organizations, aceptas crear una organización diferente para los fines de laboratorio de aprendizaje y nos autorizas a agregar materiales del curso Learning Lab a esa organización en tu nombre. - -**Materiales del curso Learning Lab.** Todos los materiales del curso que ofrece GitHub son propiedad únicamente de GitHub; sin embargo, siempre que GitHub te conceda una licencia a nivel mundia, no exclusiva, a plazo limitado, no transferible y exenta de regalías para copiar, mantener, usar y ejecutar dicho material del curso para tus fines comerciales internos asociados con el uso de Learning Lab. Esta concesión de licencia está sujeta a cualquier acuerdo de licencia de código abierto adicional que se pueda proporcionar junto con el código fuente. Los materiales del curso que origines son propiedad únicamente tuya, considerando que concedes a GitHub una licencia mundial, no exclusiva, perpetua, no transferible y exenta de regalías para copiar, mantener, usar, alojar y ejecutar (según corresponda) en el servicio, dichos materiales del curso. Tu uso de los materiales del curso de GitHub y tu creación y almacenamiento de tus propios materiales del curso no constituye una propiedad conjunta en la propiedad intelectual respectiva de cualquiera de las partes por parte de la otra. - -**Privacidad.** Learning Lab puede recopilar información personal. Controlas qué Information Learning Lab recopila en tu panel de ajustes del perfil de GitHub.com. Si Learning Lab recopila información personal en nombre de GitHub, GitHub procesará esa información de acuerdo con la [Declaración de privacidad de GitHub](/github/site-policy/github-privacy-statement). Si te inscribes o estás completando un curso privado a través de Learning Lab, GitHub puede compartir tu información de inscripción y el progreso del curso mediante la finalización con los administradores de la organización. Esto puede incluir datos individuales como el nombre de usuario de GitHub, la fecha de inicio del curso y la fecha de finalización del curso. Los datos de finalización del curso también se pueden presentar en forma agregada para ayudar a orientar las mejoras en el contenido del curso. - -### 7. Conexión - -Para acceder a Conexión con GitHub, el Cliente debe tener al menos una (1) cuenta en GitHub.com y una (1) instancia con licencia del Software. La Conexión con GitHub se puede usar para ejecutar tareas automatizadas. Además, múltiples Usuarios pueden dirigir determinadas acciones con Conexión con GitHub. El Cliente es responsable de las acciones que se realizan en sus cuentas o a través de ellas. GitHub puede recopilar información sobre la manera en que el Cliente usa la Conexión con GitHub para proporcionar y mejorar la función. Al usar la Conexión con GitHub, el Cliente autoriza a GitHub a recopilar datos protegidos, que incluyen datos del Repositorio privado e Información personal del Usuario (como se define en la Declaración de privacidad de GitHub), de la cuenta del servidor de GitHub Enterprise del Cliente. El Cliente también autoriza la transferencia de información de la instancia de identificación a GitHub por medio de la Conexión con GitHub. Esta información se rige por la Declaración de privacidad de GitHub. - -### 8. Programa de patrocinadores - -Para convertirse en un Desarrollador Patrocinado, debes aceptar los [Términos Adicionales del Programa de Patrocinadores de GitHub](/github/site-policy/github-sponsors-additional-terms). - -### 9. GitHub Advanced Security - -GitHub Advanced Security te permite identificar vulnerabilidades de seguridad a través del análisis semántico automatizado de código. GitHub Advanced Security maneja las licencias por usuario. Si utilizas la GitHub Advanced Security como parte de GitHub Enterprise Cloud, muchas de las características de la primera, incluyendo el escaneo automatizado de código para repositorios privados, también requerirán que utilices GitHub Actions. La facturación para el uso de GitHub Actions se basa en su uso, y está sujeta a las [Condiciones de GitHub Actions](/github/site-policy/github-additional-product-terms#c-payment-and-billing-for-actions-and-packages). - -### 10. Vista previa de Dependabot - -Tu uso de la vista previa de Dependabot se rige por los [Términos de Servicio](https://dependabot.com/terms) y la [Política de Privacidad](https://dependabot.com/privacy) por separado. - -### 11. Spectrum - -Tu uso de Spectrum se rige por las [Condiciones de Servicio](/github/site-policy/github-terms-of-service) de GitHub y por la [Declaración de Privacidad](/github/site-policy/github-privacy-statement). - -### 12. Base de datos consultiva - -#### a. Licencia otorgada - -Necesitamos el derecho legal de enviar tus contribuciones a la base de datos consultiva de GitHub a los conjuntos de datos de dominio público como la [Base de datos nacional de vulnerabilidad](https://nvd.nist.gov/) y para licenciar la base de datos consultiva de GitHub bajo condiciones abiertas para su uso por investigadores de seguridad, la comunidad de código abierto, la industria y el público. Aceptas publicar tus contribuciones a la base de datos consultiva de GitHub bajo la [licencia Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). - -#### b. 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 . - diff --git a/translations/es-XL/content/github/site-policy/github-and-trade-controls.md b/translations/es-XL/content/github/site-policy/github-and-trade-controls.md deleted file mode 100644 index 254879aa10..0000000000 --- a/translations/es-XL/content/github/site-policy/github-and-trade-controls.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: GitHub y controles comerciales -redirect_from: - - /articles/github-and-export-controls - - /articles/github-and-trade-control - - /articles/github-and-trade-controls - - /github/site-policy/github-and-export-controls -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -GitHub.com, GitHub Enterprise Server y la información que subas a cualquiera de los productos puede estar sujeta a las regulaciones de control de comercio, incluso bajo las Regulaciones sobre Exportación de la Administracción de los Estados Unidos (EAR). Export Administration Regulations (the EAR). - -La visión de GitHub deber ser la plataforma global para la colaboración de desarrolladores, sin importar dónde residan. Nos tomamos en serio nuestra responsabilidad de examinar a fondo los mandatos del gobierno para estar seguros de que los usuarios y clientes no se van afectados más allá de lo que exige la ley. Esto incluye mantener los servicios de repositorios públicos, incluyendo los de proyectos de código abierto, disponibles y accesibles para apoyar las comunicaciones personales que implican a los desarrolladores de regiones sancionadas. - -To comply with U.S. Para cumplir con las leyes de control comercial de los Ee. Uu. GitHub realizó algunos cambios necesarios a la forma en la que llevamos a cabo nuestros servicios. As U.S. trade controls laws evolve, we will continue to work with U.S. A medida que evolucionen las leyes de controles comerciales de los Estados Unidos, continuaremos trabajando con reguladores de EE.UU. con respecto hasta qué punto podemos ofrecer servicios gratuitos de colaboración en código a los desarrolladores en mercados sancionados. We believe that offering those free services supports U.S. Creemos que ofrecer dichos servicios gratuitos apoya la política exterior estadounidense de fomentar el libre flujo de información y la libertad de expresión en esos mercados. Para obtener más información sobre nuestro enfoque y cómo las sanciones afectan la colaboración de software global, lee nuestro [blog sobre las sanciones](https://github.blog/2019-09-12-global-software-collaboration-in-the-face-of-sanctions/). - -Aunque hemos proporcionado la siguiente información para tu comodidad, es tu responsabilidad asegurar que el uso de los productos y servicios de GitHub cumple con todas las leyes y regulaciones aplicables, incluyendo las leyes de control de exportaciones de EE. UU. export control laws. - -### Información general sobre exportaciones - -#### GitHub.com - -Bajo nuestras [Condiciones del servicio](/articles/github-terms-of-service), los usuarios solo pueden acceder y usar GitHub.com en cumplimiento con la ley aplicable, incluyendo las leyes de control de exportación y sanciones de EE. UU. export control and sanctions laws. - -Los usuarios son responsables de garantizar que el contenido que desarrollen y compartan en GitHub.com cumplA con los requisitos de las leyes de control de exportaciones, incluyendo las EAR y el Reglamento sobre Tráfico Internacional de Armas (ITAR) de los Estados Unidos. export control laws, including the EAR and the U.S. International Traffic in Arms Regulations (ITAR). La oferta de servicio alojado en la nube disponible en [GitHub.com](https://github.com) no ha sido diseñado para alojar datos sujetos al ITAR y actualmente no ofrece la posibilidad de restringir el acceso al repositorio por país. Si deseas colaborar en los datos controlados por exportación o el ITAR, te recomendamos que consideres [GitHub Enterprise Server](https://enterprise.github.com), la oferta local de GitHub. - -U.S. Las leyes de control comercial de los Estados Unidos restringen lo que los servicios de GitHub.com pueden poner a disposición de los usuarios en ciertos países y territorios. GitHub may allow users in or ordinarily resident in countries and territories subject to U.S. GitHub puede permitir a los usuarios que residan en países y territorios sujetos a las sanciones de Estados Unidos acceder a ciertos servicios gratuitos de GitHub.com para comunicaciones personales de acuerdo con las autorizaciones emitidas por la Oficina de Control de Activos Extranjeros (OFAC) del Departamento del Tesoro de los EE. UU. Treasury Department’s Office of Foreign Assets Controls (OFAC). Se prohíbe el uso de proxies de propiedad intelectual a las personas en o que residan comúnmente en estos países y territorios, VPN u otros métodos para disfrazar su ubicación al acceder a GitHub y que solo pueden utilizar GitHub.com para comunicaciones no comerciales y personales. - -Specially Designated Nationals (SDNs) and other denied or blocked parties under U.S. Los nacionales especialmente designados (SDN) y otras partes denegadas o bloqueadas bajo la ley de EE. UU y otras leyes aplicables tienen prohibido acceder o usar GitHub.com. Además, los usuarios no pueden utilizar GitHub.com para o en nombre de dichos partes, incluyendo los Gobiernos de los países sancionados. Además, GitHub.com no puede utilizarse para propósitos prohibidos bajo las leyes de control de exportaciones aplicables, incluyendo usos finales prohibidos descritos en [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5). - -#### Servidor de GitHub Enterprise - -GitHub Enterprise Server es una aplicación virtual autoalojada que se puede ejecutar dentro de su propio centro de datos o nube privada virtual. Como tal, GitHub Enterprise Server se puede utilizar para almacenar información controlada por ITAR u otra exportación, sin embargo, los usuarios finales son responsables de garantizar el cumplimiento del ITAR y de otros controles de exportación aplicables. - -GitHub Enterprise Server es un producto comercial de mercado masivo y se le ha asignado el Número de Clasificación de Control de Exportación (ECCN) de `5D992.` y puede exportarse a la mayoría de destinos sin necesidad de licencia (NLR). - -GitHub Enterprise Server no puede venderse, exportarse o reexportarse a ningún país listado en el Grupo de Países E:1 que se encuentran en el Suplemento No. 1 a la parte 740 del EAR o a la región de Crimea de Ucrania. Esta lista contiene actualmente a Cuba, Irán, Corea del Norte y Syria, pero está sujeta a cambios. - -### Preguntas frecuentes - -#### ¿En qué países y territorios se aplican las sanciones del gobierno estadounidense? government sanctions applied? - -Crimea, Cuba, Irán, Corea del Norte y Syria. - -#### ¿Cómo garantiza GitHub que las personas que no viven o que tienen vínculos profesionales con los países y territorios sancionados continúan teniendo acceso o capacidad de solicitud? - -En el raro caso de que una cuenta se vea afectada involuntariamente o por error, tenemos un proceso de apelación para atender dichos casos. - -Si un usuario individual o administrador de la organización considera que ha sido marcado por error, entonces ese usuario tiene la oportunidad de apelar la marca proporcionando información de verificación a GitHub. Si GitHub recibe suficiente información para verificar que el usuario u organización no está afiliado con una jurisdicción sancionada por EE.UU o restringida por las sanciones económicas estadounidenses, entonces la marca se eliminará. economic sanctions, then the flag will be removed. Consulte el [formulario de solicitud de apelación de cuenta individual](https://airtable.com/shrGBcceazKIoz6pY) y [el formulario de solicitud de apelación de cuenta organizacional](https://airtable.com/shrB2je5RBkqLEt5D). - -#### ¿Se verán afectados los viajes por estas regiones? - -Los viajes en estas regiones podrían impactar el estado de tu cuenta, pero la disponibilidad se podría reincorporar una vez que estés fuera de la región sancionada y al momento de emitir una [solicitud de petición de cuenta individual](https://airtable.com/shrGBcceazKIoz6pY) o una [solicitud de petición de cuenta organizacional](https://airtable.com/shrB2je5RBkqLEt5D) con éxito. - -#### ¿Qué está disponible y qué no está disponible? - -GitHub está comprometido a continuar con la oferta de servicios de repositorios públicos gratuitos para desarrolladores con cuentas individuales y organizacionales en las regiones sancionadas por los EE.UU. Esto incluye el acceso limitado a los servicios gratuitos, tales como los repositorios públicos para proyectos de código abierto (y las páginas públicas asociadas), gists públicos, y los minutos gratuitos asignados de acciones, únicamente para las comunicaciones personales, y no así para propósitos comerciales. - -However, due to U.S. Debido a los controles de comercio y restricciones legales, GitHub no puede proporcionar servicios para repositorios privados y servicios pagados a cuentas que se encuentren en las zonas sancionadas por los EE.UU. sanctioned regions like North Korea, Iran, Syria, and Crimea. Esta restricción suspende el acceso a servicios de repositorios privados y servicios pagados, tal como la disponibilidad de repositorios privados gratuitos o pagados, gists secretos, minutos de acciones pagados, patrocinadores y servicios de GitHub Marketplace. - -Para las cuentas organizacionales pagadas en regiones sancionadas, los usuarios podrían tener acceso limitado a otros repositorios públicos que se han degradado a repositorios archivados de solo lectura. Para el caso de las cuentas organizacionales gratuitas en las regiones sancionadas, sin embargo, los usuarios seguirán teniendo acceso completo a los repositorios públicos para proyectos de código abierto (y para las páginas públicas asociadas), gists públicos, y minutos de acciones gratuitos asignados. - -GitHub seguirá fomentando, en conjunto con los reguladores de los EE.UU., el mejor acceso posible a los servicios colaborativos de código abierto para desarrolladores en regiones sancionadas, incluyendo repositorios privados gratuitos. Creemos que, el ofrecer estos servicios gratuitos, apoya la política externa de los EE.UU. de fomentar el flujo libre de información y libertad de expresión en estas regiones. regulators for the greatest possible access to free code collaboration services to developers in sanctioned regions, including free private repositories. We believe that offering those free services supports U.S. foreign policy of encouraging the free flow of information and free speech in those regions. - -#### ¿Cómo defines estos usuarios específicos? - -Si GitHub determina que un usuario o cliente se encuentra en una región que está sujeta a las restricciones de control de comercio de EE.UU o un usuario está restringido bajo las sanciones económicas de EE. UU., entonces, la cuenta afiliada se restringió al cumplimiento de dichos requisitos legales. Sin embargo, debido a las restricciones legales sobre los controles comerciales de los EE.UU. economic sanctions, then the affiliated account has been restricted to comply with those legal requirements. La determinación de la ubicación del usuario y del cliente para implementar estas restricciones legales se deriva de una serie de fuentes, incluyendo direcciones IP e historial de pagos. La nacionalidad y la etnicidad no se utilizan para marcar a los usuarios para las restricciones de sanciones. - -#### ¿Cómo se ven afectadas las cuentas de la organización? - -Si una organización está basada en el exterior, o los individuos clave o la membresía de una organización muestra suficientes vínculos con un territorio o país sancionado, o si la organización parece estar sujeta a las sanciones económicas de EE.UU., entonces la cuenta de la organización y la cuenta del propietario afiliado se restringirán. economic sanctions, then the organization account and the affiliated owner account will be restricted. - -Esta restricción suspende el acceso a servicios de repositorios privados y servicios pagados, tal como la disponibilidad de repositorios privados gratuitos o pagados, gists secretos, minutos de acciones pagados, patrocinadores y servicios de GitHub Marketplace. Para las cuentas organizacionales pagadas asociadas con las regiones sancionadas, los usuarios podrían tener acceso limitado a sus repositorios públicos, los cuales se habrán degradado a repositorios archivados de solo lectura. Para las cuentas organizacionales gratuitas asociadas con las regiones sancionadas, los usuarios seguirán teneniendo acceso completo a los repositorios públicos gratuitos para proyectos de código abierto (y a las páginas públicas asociadas), gists públicos, y minutos de acciones gratuitos asociados. - -#### ¿Se pueden hacer públicos los repositorios privados de usuarios restringidos al intercambio? - -Los usuarios de cuentas individuales gratuitas pueden hacer públicos los repositorios privados restringidos, solo para comunicaciones personales, y no para propósitos comerciales. Los usuarios pueden hacer esto navegando a la pestaña de configuración del repositorio y haciendo clic en el botón "hacer público". Una vez que el repositorio sea público, los usuarios tendrán acceso a los servicios de repositorios públicos. This action cannot be undone. - -#### ¿Los usuarios restringidos al intercambio pueden acceder a datos del repositorio privado (por ejemplo, descargar o eliminar datos del repositorio)? - -Desafortunadamente, nuestra comprensión de la ley no nos da la opción de permitir descargas o eliminación de contenido de repositorio privado hasta que lo autorice de otra forma el gobierno de EE. UU. government. We will strongly advocate, with U.S. Defenderemos firmemente, junto con los reguladores estadounidenses, el derecho de los usuarios restringidos al intercambio a asegurar el contenido de sus repositorios privados. También abogaremos por una mayor disponibilidad de servicios de GitHub para desarrolladores en mercados sancionados y subrayaremos la importancia de la colaboración en código para apoyar las comunicaciones personales para los desarrolladores en todo el mundo. - diff --git a/translations/es-XL/content/github/site-policy/github-anti-bribery-statement.md b/translations/es-XL/content/github/site-policy/github-anti-bribery-statement.md deleted file mode 100644 index 630606a981..0000000000 --- a/translations/es-XL/content/github/site-policy/github-anti-bribery-statement.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Declaración antisoborno de GitHub -redirect_from: - - /articles/github-anti-bribery-statement -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -GitHub defiende nuestro compromiso con prácticas comerciales éticas, que incluyen prohibir el soborno y la corrupción. Como la [Transparencia Internacional](https://www.transparency.org/what-is-corruption#costs-of-corruption) lo explica, los costos de la corrupción son: -- **políticos**, que plantean un gran obstáculo para la democracia y el estado de derecho -- **económicos**, agotando la riqueza nacional -- **sociales**, al socavar la confianza de las personas en la sociedad, las instituciones y los líderes políticos -- **ambientales**, al facilitar la no aplicación de las leyes y regulaciones ambientales. - -Según el [Banco Mundial](https://www.worldbank.org/en/topic/governance/brief/anti-corruption) en 2017, las empresas y personas pagan un estimado de $1.5 billones en sobornos cada año. - -### Políticas de GitHub que prohíben el soborno - -GitHub hace que nuestro compromiso con el anti-soborno sea claro en una cantidad de políticas de la empresa. Como parte de la familia de Microsoft, GitHub también se compromete con la política anticorrupción de Microsoft, que se aplica a todos los empleados y contratistas de GitHub, además de las políticas aquí descritas. - -El **código de ética** de GitHub prohíbe que los empleados y los contratistas participen o contribuyan con el soborno o la corrupción y establece requisitos de mantenimiento de registros: -> Nunca debes pagar, ofrecer pagar, prometer pagar, inducir, aceptar o autorizar el pago de ninguna otra cosa de valor, a ninguna persona, incluyendo a ninguna persona en una posición de poder o autoridad, por ejemplo, funcionarios del gobierno o en transacciones comerciales, con el fin de obtener o mantener negocios, o asegurar cualquier otra ventaja inapropiada para GitHub o Microsoft. Tampoco debes solicitar o aceptar sobornos, ni ningún otro pago indebido en efectivo. ... [Los empleados de GitHub] están obligados a mantener registros precisos y razonables de todas las transacciones que implican cualquier gasto hecho en nombre de GitHub, por ejemplo, al mantener los recibos y proporcionar descripciones precisas de tus gastos, o cualquier otra transacción que implique la eliminación o la transferencia de los activos de GitHub. Such actions are required by the U.S. Foreign Corrupt Practices Act, the U.K. Estas acciones se exigen por la ley de prácticas corruptas extranjeras de los EE. UU., la ley de soborno del Reino Unido de 2010 y las leyes antisoborno de otras jurisdicciones en las que GitHub hace negocios y que también son simplemente la manera correcta de proceder. - -El código ético de GitHub detalla ciertas situaciones, incluyendo sobre regalos, viajes y entretenimiento; facilitación de pagos; donaciones caritativas; puestos laborales y trabajar con representantes, así como la descripción de quién se considera un funcionario del gobierno. - -Las normas de conducta de GitHub prohíben: -> Sobornar a funcionarios del gobierno u otras personas para obtener una ventaja injusta y tomar sobornos de cualquier persona. - -La **política de regalos y entretenimiento** de GitHub explica que el soborno no está permitido en relación con los viajes o el entretenimiento y proporciona ejemplos para ilustrar conductas inadecuadas. La política describe los regalos adecuados e inadecuados, los gastos de viajes y entretenimiento; los procesos de la empresa para que los directores de GitHub, funcionarios, empleados y agentes hagan regalos y los requisitos para el mantenimiento de registros, sanciones; y la denuncia de violaciones. Incluye umbrales monetarios claros para los regalos junto con las limitaciones anuales, con excepciones limitadas para los regalos aprobados por la administración adecuada. La política es clara y de fácil acceso para los empleados y los contratistas de GitHub. - -### Formación para nuestros empleados - -Los empleados de GitHub están obligados a participar en la capacitación sobre corrupción, incluyendo sobornos. También proporcionamos capacitación adicional para personas y equipos particularmente relevantes, como nuestro equipo de ventas. The training explains relevant elements of the U.S. La capacitación explica los elementos pertinentes de la ley de prácticas corruptas extranjeras de los EE. UU. y la ley de soborno del Reino Unido de 2010. Bribery Act of 2010. Por ejemplo, -- definición y efectos estructurales de la corrupción -- que está cubierto, incluyendo - - funcionarios públicos u otros en una posición de poder - - terceros -- qué tipo de actividad está cubierta, incluyendo - - efectivo, regalos, viajes y entretenimiento - - pagos de facilitación - - contribuciones caritativas y patrocinio -- para qué propósito, incluyendo - - intento - - ventaja o influencia incorrecta -- diligencia debida y señales de alerta -- requisitos de mantenimiento de registros - -Además, la capacitación cubre las políticas internas de GitHub relacionadas con la lucha contra la corrupción y el soborno, incluyendo nuestra política de no represalias (denuncia de irregularidades). - -While the U.S. FCPA is focused on interactions with government officials, the U.K. Bribery Act is broader and extends to bribing anyone, regardless of whether they are a government official. Ambas leyes pueden extenderse a las acciones de GitHub en otro lugar del mundo. Las políticas de GitHub prohíben sobornar a cualquier persona, en cualquier parte del mundo. - -### Involucrar a nuestros socios -- Los acuerdos de reventa de GitHub ** con socios de canal** incluyen cláusulas de anti-corrupción obligatorias. En adelante, GitHub requirá que nuestros socios de canal se comprometan a cumplir con esta declaración anticorrupción. -- En adelante, los **contratos de vendedores** de GitHub requerirán un compromiso para cumplir con el código de conducta del proveedor de Microsoft o con esta declaración anticorrupción. diff --git a/translations/es-XL/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md b/translations/es-XL/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md deleted file mode 100644 index dfe3600756..0000000000 --- a/translations/es-XL/content/github/site-policy/github-bug-bounty-program-legal-safe-harbor.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Disposición de seguridad legal del programa de recompensas de errores de GitHub -redirect_from: - - /articles/github-bug-bounty-program-legal-safe-harbor -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -### Resumen -1. Deseamos que divulgues responsablemente a través de nuestro programa de recompensa de errores y no queremos que los investigadores se atemoricen por las consecuencias legales debido a sus intentos de buena fe para cumplir con nuestra política de recompensas por errores. No podemos vincular a ningún tercero, por lo que no presuponemos que esta protección se extiende a ningún tercero. Si tienes dudas, pregúntanos antes de participar en cualquier acción específica que consideres que _Podría_ vaya fuera de los límites de nuestra política. -2. Dado que tanto la información de identificación como la no identificativa pueden poner a un investigador en riesgo, limitamos lo que compartimos con terceros. Es posible que proporcionemos información sustantiva no identificativa de tu informe a un tercero afectado, pero solo después de notificarte a ti y de recibir un compromiso de que el tercero no perseguirá acciones legales en tu contra. Solo compartiremos la información de identificación (nombre, dirección de correo electrónico, número de teléfono, etc.) con un tercero si le proporcionas tu permiso por escrito. -3. Si tu investigación de seguridad como parte del programa de recompensas por errores viola ciertas restricciones en nuestras políticas del sitio, los términos del puerto seguro permiten una exención limitada. - -### 1. Condiciones de la disposición de seguridad - -Para alentar la investigación y la divulgación responsable de las vulnerabilidades de seguridad, no perseguiremos acciones civiles o penales, o enviaremos un aviso a la aplicación de la ley por violaciones fortuitas o de buena fe de esta política. Consideramos que las investigaciones de seguridad y las actividades de divulgación de vulnerabilidades llevadas a cabo de acuerdo con esta política son conductas "autorizadas" conforme a la ley de fraude y abuso informático, la DMCA y otras leyes aplicables de uso informático, como Código Penal de Cal. 502(c). Renunciamos a cualquier demanda potencial de DMCA en tu contra por eludir las medidas tecnológicas que hemos utilizado para proteger las aplicaciones en este alcance del programa de recompensas de errores. - -Por favor, entiende que si tu investigación de seguridad involucra las redes, sistemas, información, aplicaciones, productos o servicios de un tercero (que no seamos nosotros), no podemos vincular a ese tercero y pueden perseguir acciones legales o aviso de cumplimiento de la ley. No podemos y no autorizamos la investigación de seguridad en el nombre de otras entidades, y de ninguna manera podemos ofrecer defenderte, indemnizarte o protegerte de ninguna manera de cualquier acción de terceros en base a sus acciones. - -Se espera, como siempre, cumplir con todas las leyes aplicables a ti, y no interrumpir o comprometer ningún dato más allá de lo que este programa de recompensas de errores permite. - -Ponte en contacto con nosotros antes de participar en una conducta que puede ser incompatible con esta política o no ser tratada por esta. Nos reservamos el derecho exclusivo de hacer la determinación de si una violación de esta política es accidental o de buena fe y el contacto proactivo con nosotros antes de participar en cualquier acción es un factor significativo en esa decisión. Si tienes dudas, ¡Pregúntanos primero! - -### 2. Disposición de seguridad de terceros - -Si envías un informe a través de nuestro programa de recompensas de errores que afecta a un servicio de terceros, limitaremos lo que compartamos con cualquier tercero afectado. Es posible que compartamos contenido no identificable de tu informe con un tercero afectado, pero solo después de notificarte que tenemos la intención de hacerlo y de obtener el compromiso por escrito del tercero de que no perseguirán acciones legales en tu contra o de iniciar contacto con las fuerzas del orden de las leyes en base a tu informe. No compartiremos tu información de identificación con ningún tercero afectado sin obtener primero tu permiso por escrito para hacerlo. - -Ten en cuenta que no podemos autorizar pruebas fuera de alcance en nombre de terceros y dichas pruebas están fuera del alcance de nuestra política. Consulta la política de recompensas de errores de ese tercer, si tiene una, o comunícate directamente con el tercero o a través de un representante legal antes de iniciar cualquier prueba en ese tercero o en sus servicios. Esto no es, y no debe entenderse como, cualquier acuerdo de nuestra parte para defender, indemnizar o de cualquier otra manera protegerte de cualquier acción de terceros con base a tus acciones. - -Dicho esto, si un tercero inicia una acción legal, incluyendo las fuerzas del orden, en tu contra por tu participación en este programa de recompensa de errores y has cumplido suficientemente con nuestra política de recompensas por errores (es decir, no has hecho violaciones intencionales o de mala fe), tomaremos las medidas para hacer que se conozca que tus acciones se realizaron de conformidad con esta política. Si bien consideramos que los informes presentados son documentos confidenciales y potencialmente privilegiados y protegidos frente a la divulgación forzada en la mayoría de las circunstancias, ten en cuenta que un tribunal puede, a pesar de nuestras objeciones, ordenarnos que compartamos información con un tercero. - -### 3. Exención limitada de otras políticas del sitio - -En la medida en que tus actividades de investigación de seguridad no sean coherentes con ciertas restricciones en nuestras [políticas del sitio relevantes](/categories/site-policy/) pero son consistentes con los términos de nuestro programa de recompensas de errores, renunciamos a esas restricciones con el único y limitado propósito de permitir tu investigación de seguridad bajo este programa de recompensas de errores. De la misma forma que se menciona anteriormente, si tienes dudas, ¡Pregúntanos primero! diff --git a/translations/es-XL/content/github/site-policy/github-community-forum-code-of-conduct.md b/translations/es-XL/content/github/site-policy/github-community-forum-code-of-conduct.md deleted file mode 100644 index 6371080a78..0000000000 --- a/translations/es-XL/content/github/site-policy/github-community-forum-code-of-conduct.md +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: Código de conducta del foro de la comunidad GitHub -redirect_from: - - /articles/github-community-forum-code-of-conduct -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -### Descripción y propósito - -Millones de programadores albergan millones de proyectos en GitHub — tanto de código abierto como de código cerrado — y tenemos el honor de participar en permitir la colaboración de toda la comunidad de programadores todos los días. Juntos tenemos una emocionante oportunidad y responsabilidad de hacer de esta una comunidad de la que podemos estar orgullosos. - -El Foro de la Comunidad de GitHub está previsto para ser un lugar para más colaboración, apoyo y reunión de reflexión. Este es un lugar civilizado para conectarse con otros usuarios, aprender nuevas habilidades, compartir comentarios e ideas y encontrar todo el apoyo que necesitas para tus proyectos de GitHub. Al participar en esta Comunidad, aceptas los mismos [Términos de Servicio](/articles/github-terms-of-service/) que se aplican a GitHub.com, así como este Código de Conducta específico para la Comunidad. - -Con este Código de Conducta esperamos ayudarte a entender cómo colaborar mejor en el Foro de la Comunidad de GitHub, lo que puedes esperar de los moderadores y qué tipo de acciones o contenidos pueden resultar en una suspensión temporal o permanente de la participación en la Comunidad. Investigaremos cualquier reporte de abuso y podremos moderar el contenido público dentro de la Comunidad que determinemos que viola los Términos de Servicio de GitHub o de este Código de Conducta. - -Los usuarios de GitHub en todo el mundo ofrecen perspectivas, ideas y experiencias diferentes y van desde personas que crearon su primer proyecto "Hola Mundo" la semana pasada hasta los desarrolladores de software más conocidos del mundo. Estamos comprometidos a hacer de GitHub y el Foro de la Comunidad de GitHub un entorno acogedor para todas las diferentes voces y perspectivas aquí, manteniendo un espacio donde la gente es libre de expresarse. - -### Compromiso - -En interés de fomentar un entorno abierto y acogedor, como colaboradores y mantenedores nos comprometemos a hacer de la participación en el Foro de la Comunidad de GitHub una experiencia sin acoso para todos, sin importar la edad, complexión, capacidad, etnicidad, identidad y expresión de género, nivel de experiencia, nacionalidad, apariencia personal, raza, religión o identidad y orientación sexual. - -### Estándares - -Trata el Foro de la Comunidad de GitHub con respeto. Somos un recurso compartido — un lugar para compartir habilidades, conocimientos e intereses a través de una conversación continua. - -Lo siguiente no son normas duras y rápidas, sino ayudas al juicio humano de nuestra Comunidad. Utiliza estas pautas para mantener este lugar limpio y bien iluminado para el discurso público civilizado. - -#### *Mejores prácticas para construir una comunidad sólida* - -- Se respetuoso y considerado. - - **Se bienvenido y abierto.** Es posible que otros miembros de la comunidad no tengan el mismo nivel de experiencia o antecedentes que tú, pero eso no significa que no tengan buenas ideas para contribuir. Te invitamos a dar la bienvenida a los nuevos miembros y a los que están empezando a trabajar. - - **Respeto unos a otros.** Nada sabotea una conversación saludable como la rudeza. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones. - - Es probable que desees responder a algo discrepándolo. Está bien. Pero recuerda criticar las ideas, no a las personas. Evita ataques usando el nombre, ad hominem, respondiendo al tono de un post en lugar de su contenido real y contradicción reactiva. En lugar de ello, proporciona contra-argumentos razonados que mejoran la conversación. - - **Comunícate con empatía.** Los desacuerdos o diferencias de opinión son un hecho de la vida. Formar parte de una comunidad significa interactuar con personas de diferentes orígenes y perspectivas, muchas de las cuales pueden no ser propias. Si no estás de acuerdo con alguien, trata de entender y compartir sus sentimientos antes de abordarlos. Esto promoverá un ambiente respetuoso y amistoso donde la gente se sienta cómoda haciendo preguntas, participando en discusiones y haciendo contribuciones. -- Contribuye de forma positiva y constructiva. - - **Mejorar el debate.** Ayúdanos a hacer de esto un gran lugar para el debate trabajando siempre para mejorar la discusión de alguna manera, sin embargo siempre breve. Si no estás seguro de que tu publicación sume a la conversación, piensa en lo que quieres decir e inténtalo de nuevo más tarde. - - Los temas debatidos aquí nos importan y esperamos que actúes como si también te importasen. Se respetuoso con los temas y con las personas que los debaten, aunque no estés de acuerdo con algo de los que se dice. - - **Se claro y enfócate en el tema.** Comunicarse con extraños en Internet puede ser incómodo. Es difícil transmitir o leer el tono y el sarcasmo es frecuentemente mal entendido. Intenta usar un lenguaje claro y piensa cómo será recibido por la otra persona. - - Esto también se aplica al intercambio de vínculos. Cualquier enlace compartido en el Foro de la Comunidad debe compartirse con la intención de proporcionar información relevante y apropiada. Los enlaces no deben publicarse para simplemente conducir el tráfico o la atención a un sitio. Los enlaces siempre deberán ir acompañados de una explicación completa del contenido y propósito de los mismos. Publicar enlaces, especialmente los no solicitados, sin un contexto relevante y valioso puede parecer publicidad o con fines aún más maliciosos. - - Además, el Foro de la Comunidad de GitHub tiene el objetivo de colaborar, compartir ideas y ayudarse mutuamente a hacer cosas. Los comentarios fuera del tema son una distracción (en ocasiones bien recibido, pero generalmente no) sobre realizar el trabajo y ser productivo. Mantener el tema ayuda a producir discusiones positivas y productivas. - - **Comparte con precaución.** Al pedir a otros que te den comentarios o colaboren en un proyecto, solo comparte recursos valiosos y relevantes para proporcionar un contexto. No publiques enlaces que no añadan valor al tema y no publiques enlaces no solicitados a tus propios proyectos o sitios en los temas de otros usuarios. - - Además, no compartas información confidencial. Esto incluye tu propia dirección de correo electrónico. No permitimos compartir dicha información en este Foro de la Comunidad, ya que puede crear riesgos de seguridad y privacidad para la persona que publica, así como para otros usuarios. Si quieres invitar a otros miembros del Foro a colaborar en un proyecto o trabajar contigo, comparte un enlace al repositorio en el que existe el proyecto en el que estás trabajando. Al compartir el enlace al repositorio de tu proyecto - con alguna información sobre lo que es tu proyecto y qué tipo de ayuda o retroalimentación estás buscando, puedes invitar a otros a colaborar contigo a través de temas o solicitudes de extracción sin tener que compartir tu información privada. También puedes añadir a otros como colaboradores externos en el repositorio de tu proyecto para darles permisos especiales que te ayuden a desarrollar tu proyecto. - - **Mantén el orden.** Haz el esfuerzo de colocar las cosas en el lugar correcto, para que podamos pasar más tiempo debatiendo y menos tiempo resolviendo problemas. Así que: - - No inicies un tema en la categoría equivocada. - - No publiques lo mismo en múltiples temas. - - No publiques respuestas sin contenido. - - No "infles" publicaciones, a menos que tengas información nueva y relevante que compartir. - - No desvíes un tema cambiándolo a midstream. - - En lugar de publicar “+1” o “De acuerdo”, utiliza el botón Kudos. En lugar de tomar un tema existente en una dirección radicalmente diferente, abre un nuevo tema. - -- Se digno de confianza. - - **Siempre se honesto.** No compartas conscientemente información incorrecta o confundas intencionalmente a otros miembros del foro de la comunidad de GitHub. Si no conoces la respuesta a la pregunta de alguien pero deseas ayudarle, puedes intentar ayudarle a investigar o encontrar recursos en su lugar. El personal de GitHub también estará activo en la Comunidad, así que si no estás seguro de una respuesta, es probable que un moderador pueda ayudar. - -#### *Lo que no está permitido* - -- **Amenazas de violencia.** No puede amenazar la violencia hacia otros ni utilizar el sitio para organizar, promover o incitar a actos de violencia o terrorismo en el mundo real. Piensa detenidamente en las palabras que usas, las imágenes que publicas e incluso el software que escribas y cómo lo pueden interpretar otros. Incluso si dices algo como una broma, es posible que no se reciba de esa forma. If you think that someone else might interpret the content you post as a threat, or as promoting violence or terrorism, stop. No lo publiques. En casos extraordinarios podemos denunciar amenazas de violencia a la aplicación de la ley si creemos que puede haber un verdadero riesgo de daños físicos o una amenaza para la seguridad pública. - -- **Discurso de odio y discriminación.** Aunque no está prohibido abordar temas como edad, complexión, capacidad, etnia, identidad de género y expresión, nivel de experiencia, nacionalidad, apariencia personal, raza, religión u identidad y orientación sexual, no toleramos el discurso que ataque a una persona o grupo de personas en función de quiénes son. Sólo date cuenta de que hablar de estos u otros temas delicados puede hacer que otros se sientan insólitos, o quizás incluso inseguros si se enfoca de forma agresiva o aislante. Esperamos que nuestros miembros de la Comunidad sean respetuosos a la hora de debatir temas delicados. - -- **Intimidación y acoso** No toleramos acoso ni intimidación. Esto significa cualquier acoso o intimidación habitual dirigida a una persona o grupo específico de personas. En general, si tus acciones son indeseables y continúas participando en ellas, hay una buena posibilidad de que te dirijas a territorio de intimidación o acoso. - -- **Suplantación.** No puedes suplantar a otra persona copiando su avatar, publicando contenido bajo su dirección de correo electrónico, utilizar intencionalmente un nombre de usuario engañosamente similar o de otro modo hacer publicaciones como alguien más. La suplantación es una forma de acoso. - -- **Doxing e invasión de privacidad** - No publiques información personal de otras personas, como números de teléfono, direcciones de correo electrónico privadas, direcciones físicas, números de tarjetas de crédito, números de seguridad social o de identificación nacional o contraseñas. Dependiendo del contexto, como en el caso de intimidación o acoso, podemos considerar otra información, tales como fotos o vídeos que fueron tomados o distribuidos sin el consentimiento de la persona, una invasión de la privacidad, especialmente cuando dicho material representa un riesgo para la seguridad del sujeto. - -- **Contenido impúdico/sexualmente explícito.** Básicamente, no publique pornografía. Esto no significa que toda la desnudez o contenido sexual esté prohibido. Reconocemos que la sexualidad es parte de la vida y que el contenido sexual no pornográfico puede ser parte de su proyecto o puede presentarse con fines educativos o artísticos. Si tienes alguna pregunta o inquietud sobre algo que quieras publicar, [no dudes en contactar y preguntar](https://support.github.com/contact) de antemano. - -- **Spam.** Respeta el Foro de la Comunidad de GitHub. No publiques anuncios, enlaces a sitios web con spam ni vandalices de otro modo a la Comunidad. Esta comunidad está diseñada para que los usuarios de GitHub debatan sobre proyectos, aprendan y compartan ideas entre sí - no para publicidad u otro contenido como spam. Los contenidos que consideremos spam serán eliminados. - -- **Contenido con derechos de autor o ilegal.** Publica solo tus propias cosas. Eres responsable de lo que publicas. Si publicas algo que no te creaste, debes tener derecho a publicarlo. Ni puedes publicar contenido ilegal, incluyendo contenido ilegal bajo las leyes de copyright y marca registrada, enlaces a contenido ilegal, o métodos para eludir la ley. - -- **Malware activo o explotación de vulnerabilidad** - Ser parte de una comunidad incluye no aprovecharse de otros miembros de la comunidad. No permitimos que nadie utilice nuestra plataforma para la entrega de explotación (p. ej. Utilizar la Comunidad como medio para entregar ejecutables maliciosos) o como infraestructura de ataque (p. ej. Organizar ataques de denegación de servicio o administrar servidores de comandos y control). Sin embargo, ten en cuenta, que no prohibimos la publicación de código fuente que podría utilizarse para desarrollar malware o explotación de vulnerabilidad, ya que la publicación y distribución de dicho código fuente tiene un valor educativo y proporciona un beneficio neto a la comunidad de seguridad. - -- **Cualquier persona menor de 13 años.** Si eres menor de 13 años, no puedes tener una cuenta en el Foro de la Comunidad de GitHub (o en el propio GitHub). GitHub no recopila intencionalmente información de niños menores de 13 años ni dirige ninguno de nuestros contenidos de manera específica a ellos. Si aprendemos o tenemos motivos para sospechar que eres un usuario menor de 13 años, desafortunadamente tendremos que cerrar tanto tu Foro de la Comunidad de GitHub como tus cuentas en GitHub.com. No queremos desalentarte de que aprendas nuestro código, pero esas son las reglas. Consulta nuestras [Términos de servicio](/articles/github-terms-of-service/) para obtener información sobre la cancelación de la cuenta. - -- **Otras conductas que podrían considerarse razonablemente inadecuadas en un entorno profesional.** El Foro de la Comunidad de GitHub es un espacio profesional y debe ser tratado como tal. - -### Cumplimiento - -#### *Qué actividades pueden realizar los miembros de los foros de la comunidad de GitHub* - -- **Si ves un problema, repórtalo.** Los moderadores tienen autoridad especial; son responsables de esta comunidad. Pero tú también. Con tu ayuda, los moderadores pueden ser facilitadores de la comunidad, no sólo personal de limpieza o policía. - - Cuando observes un mal comportamiento, no respondas. Fomenta el mal comportamiento al reconocerlo, consume tu energía y pierde el tiempo de todos. Simplemente repórtalo a través de "Reporte de contenido inapropiado" en el Menú Opción. Si se acumulan suficientes informes, se tomarán medidas, ya sea automáticamente o mediante la intervención del moderador. - -#### Nuestras responsabilidades - -Existe una variedad de acciones que podemos tomar en respuesta al comportamiento o contenido inadecuado. Por lo general, depende de las circunstancias exactas de un caso en particular. Reconocemos que en ocasiones la gente puede decir o hacer cosas inadecuadas por diversas razones. Tal vez no se dieron cuenta de cómo se percibirían sus palabras. O tal vez sólo dejan que sus emociones saquen lo mejor de ellos. Por supuesto, en ocasiones, hay gente que sólo quiere hacer spam o causar problemas. - -Cada caso requiere un enfoque diferente, e intentamos adaptar nuestra respuesta para satisfacer las necesidades de la situación. Revisaremos cada situación caso por caso. En cada caso, tendremos un equipo diverso que investigue el contenido y los hechos relacionados y responda según corresponda, usando este Código de Conducta para guiar nuestra decisión. - -Las acciones que podemos llevar a cabo en respuesta a un reporte de abuso incluyen, pero no se limitan a: - - Eliminación de contenido - - Bloqueo de contenido - - Suspensión de la cuenta del Foro de la Comunidad - - Terminación de la cuenta del Foro de la Comunidad - -Los moderadores del Foro de la Comunidad que no sigan o no hagan cumplir el Código de Conducta de buena fe pueden enfrentarse a repercusiones temporales o permanentes según lo determine el liderazgo de otros miembros del Foro de la Comunidad. - -### Contacto con el personal de GitHub - -Si por cualquier razón quieres contactar en privado al personal de GitHub, los Gerentes Comunitarios, Administradores o Moderadores de este foro, puedes utilizar nuestro [Formulario de contacto para soporte](https://support.github.com/contact?tags=community-support). Se recomienda fuertemente que no contactes a ningún miembro del personal de GitHub a través de cualquier canal diferente al foro mismo o del formato de contacto para soporte y, el hacerlo, podria considerarse como una violación a nuestra prohibición contra el acoso. - -Trabajemos juntos para mantener el foro un lugar donde las personas se sientan seguras de participar por ser respetuosas con ellos y su tiempo. - -### Avisos legales - -Sí, los términos legales son aburridos, pero debemos protegernos –y por extensión, tú y tus datos– de las personas poco amistosas. Tenemos [Términos de Servicio](/articles/github-terms-of-service/) y la [Declaración de Privacidad](/articles/github-privacy-statement/) que describe tu comportamiento (y nuestro) y los derechos relacionados con el contenido, privacidad y leyes. Para utilizar este servicio, debes aceptar cumplir nuestros [Términos de Servicio](/articles/github-terms-of-service/) y la [Declaración de Privacidad](/articles/github-privacy-statement/). - -Este Código de Conducta no modifica nuestros [Términos de Servicio](/articles/github-terms-of-service/) y no pretende ser una lista completa. GitHub conserva toda la discreción bajo los [Términos de Servicio](/articles/github-terms-of-service/) para eliminar cualquier contenido o cancelar cualquier cuenta de actividad que sea "ilegal, ofensivo, amenazante, calumnioso, difamatorio, pornográfico, obsceno o de otro modo censurable o que viole la propiedad intelectual de cualquier parte o estos Términos de Servicio. Este Código de Conducta describe cuándo ejerceremos esa discreción. diff --git a/translations/es-XL/content/github/site-policy/github-community-guidelines.md b/translations/es-XL/content/github/site-policy/github-community-guidelines.md deleted file mode 100644 index 40e3820c52..0000000000 --- a/translations/es-XL/content/github/site-policy/github-community-guidelines.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Pautas de la comunidad GitHub -redirect_from: - - /community-guidelines/ - - /articles/github-community-guidelines -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Millones de desarrolladores albergan millones de proyectos en GitHub — tanto de código abierto como de código cerrado — y tenemos el honor de participar en la colaboración de toda la comunidad todos los días. Juntos tenemos una emocionante oportunidad y responsabilidad de hacer de esta una comunidad de la que podemos estar orgullosos. - -Los usuarios de GitHub en todo el mundo ofrecen perspectivas, ideas y experiencias diferentes y van desde personas que crearon su primer proyecto "Hola Mundo" la semana pasada hasta los desarrolladores de software más conocidos del mundo. Estamos comprometidos a hacer de GitHub un ambiente acogedor para todas las diferentes voces y perspectivas de nuestra comunidad, manteniendo un espacio donde la gente sea libre de expresarse. - -Dependemos de nuestros miembros de la comunidad para que comuniquen las expectativas, [moderen](#what-if-something-or-someone-offends-you) sus proyectos, y {% data variables.contact.report_abuse %} o {% data variables.contact.report_content %}. No buscamos activamente contenido para moderar. Al describir lo que esperamos ver dentro de nuestra comunidad, esperamos ayudarte a entender cómo colaborar de mejor forma en GitHub y qué tipo de acciones o contenido pueden violar nuestros [Términos de Servicio](#legal-notices). Investigaremos cualquier reporte de abuso y podremos moderar el contenido público en nuestro sitio que determinemos que infringe nuestros Términos de Servicio. - -### Construir una comunidad sólida - -El propósito principal de la comunidad de GitHub es colaborar en proyectos de software. Deseamos que la gente trabaje mejor juntos. Aunque mantenemos el sitio, esta es una comunidad que construimos *juntos* y necesitamos tu ayuda para que sea lo mejor. - -* **Se cordial y de mentalidad abierta** - Otros colaboradores pueden no tener el mismo nivel de experiencia o antecedentes que tú, pero eso no significa que no tengan buenas ideas para aportar. Te invitamos a dar la bienvenida a los nuevos miembros y a los que están empezando a trabajar. - -* **Respeto unos a otros.** Nada sabotea una conversación saludable como la rudeza. Se cortés y profesional y no publiques nada que una persona razonable consideraría ofensivo, abusivo o un discurso de odio. No acoses ni molestes a nadie. Trato mutuo con dignidad y consideración en todas las interacciones. - - Es probable que desees responder a algo discrepándolo. Está bien. Pero recuerda criticar las ideas, no a las personas. Evita ataques usando el nombre, ad hominem, respondiendo al tono de un post en lugar de su contenido real y contradicción reactiva. En lugar de ello, proporciona contra-argumentos razonados que mejoran la conversación. - -* **Comunícate con empatía.** Los desacuerdos o diferencias de opinión son un hecho de la vida. Formar parte de una comunidad significa interactuar con personas de diferentes orígenes y perspectivas, muchas de las cuales pueden no ser propias. Si no estás de acuerdo con alguien, trata de entender y compartir sus sentimientos antes de abordarlos. Esto promoverá un ambiente respetuoso y amistoso donde la gente se sienta cómoda haciendo preguntas, participando en discusiones y haciendo contribuciones. - -* **Se claro y permanece en el tema** -Las personas usan GitHub para hacer el trabajo y ser más productivos. Los comentarios fuera del tema son una distracción (en ocasiones bien recibido, pero generalmente no) sobre realizar el trabajo y ser productivo. Mantener el tema ayuda a producir discusiones positivas y productivas. - - Además, comunicarse con extraños en Internet puede ser incómodo. Es difícil transmitir o leer el tono y el sarcasmo es frecuentemente mal entendido. Intenta usar un lenguaje claro y piensa cómo será recibido por la otra persona. - -### ¿Qué pasa si algo o alguien te ofende? - -Confiamos en que la comunidad nos comunique cuándo sea necesario abordar una cuestión. No monitoreamos activamente el sitio por contenido ofensivo. Si encuentras algo o alguien en el sitio que sea censurable, aquí hay algunas herramientas que proporciona GitHub para ayudarte a tomar acción inmediatamente: - -* **Comunica las expectativas** - Si participas en una comunidad que no haya establecido sus propias pautas específicas de la comunidad, invítalos a realizarlo en el archivo README o [CONTRIBUTING](/articles/setting-guidelines-for-repository-contributors/), o en [un código de conducta dedicado](/articles/adding-a-code-of-conduct-to-your-project/), enviando una solicitud de extracción. - -* **Modera comentarios** - Si tienes [privilegios de acceso de escritura](/articles/repository-permission-levels-for-an-organization/) para un repositorio, puedes editar, eliminar u ocultar los comentarios de cualquier persona sobre confirmaciones, solicitudes de extracción y propuestas. Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. Los autores del comentario y las personas con acceso de escritura a un repositorio pueden eliminar información confidencial del historial de edición de un comentario. Para obtener más información, consulta "[Seguimiento de cambios en un comentario](/articles/tracking-changes-in-a-comment)" y "[Gestión de comentarios perturbadores](/articles/managing-disruptive-comments)." - -* **Bloquea Conversaciones**- Si una discusión en una propuesta o solicitud de extracción sale de control, puedes [bloquear la conversación](/articles/locking-conversations/). - -* **Bloquea usuarios** - Si encuentras a un usuario que continúa presentando un mal comportamiento, puedes [bloquear al usuario desde su cuenta personal](/articles/blocking-a-user-from-your-personal-account/) o [bloquear al usuario desde su organización](/articles/blocking-a-user-from-your-organization/). - -Claro que siempre podrás contactarnos en {% data variables.contact.report_abuse %} si necesitas más ayuda con alguna situación. - -### ¿Qué no está permitido? - -Estamos comprometidos a mantener una comunidad donde los usuarios sean libres de expresarse y desafiar las ideas de los demás, tanto técnicas como de otro tipo. Sin embargo, es poco probable que dichos debates fomenten un diálogo fructífero cuando se silencian las ideas porque los miembros de la comunidad están siendo bloqueados o tienen miedo de hablar. Esto significa que deberías ser respetuoso y civil en todo momento y que deberías esforzarse por no atacar a los demás considerando quiénes son. No toleramos un comportamiento que cruce la línea de lo siguiente: - -* **Amenaza de violencia** - No puedes amenazar con violencia a otros ni usar el sitio para organizar, promover o incitar a actos de violencia o terrorismo en el mundo real. Piensa detenidamente en las palabras que usas, las imágenes que publicas e incluso el software que escribas y cómo lo pueden interpretar otros. Incluso si dices algo como una broma, es posible que no se reciba de esa forma. Si crees que alguien más *podría* interpretar el contenido que publicas como una amenaza o como una promoción de la violencia o el terrorismo, detente. No lo publiques en GitHub. En casos extraordinarios podemos denunciar amenazas de violencia a la aplicación de la ley si creemos que puede haber un verdadero riesgo de daños físicos o una amenaza para la seguridad pública. - -* **Discurso de odio y discriminación** - Aunque no está prohibido abordar temas como la edad, complexión corporal, discapacidad, etnicidad, identidad de género y expresión, nivel de experiencia, nacionalidad, apariencia personal, raza, religión e identidad y orientación sexual, no toleramos el discurso que ataque a una persona o grupo de personas en función de quiénes son. Sólo date cuenta de que cuando se trata de una forma agresiva o insultante, estos (y otros) temas delicados pueden hacer que otros se sientan no deseados o incluso inseguros. Aunque siempre existe la posibilidad de malentendidos, esperamos que los miembros de nuestra comunidad continúen siendo respetuosos y corteses cuando discutan temas delicados. - -* **Intimidación y acoso** - No toleramos acoso ni intimidación. Esto significa cualquier acoso o intimidación habitual dirigida a una persona o grupo específico de personas. En general, si tus acciones son indeseables y continúas participando en ellas, hay una buena posibilidad de que te dirijas a territorio de intimidación o acoso. - -* **Suplantación** - No puedes intentar confundir a otros en cuanto a tu identidad copiando el avatar de otra persona, publicando contenido bajo su dirección de correo electrónico, usando un nombre de usuario similar o presentándote de otra manera como alguien más. La suplantación es una forma de acoso. - -* **Doxing e invasión de privacidad** - No publique información personal de otras personas, como números de teléfono, direcciones de correo electrónico privadas, direcciones físicas, números de tarjetas de crédito, números de seguridad social o de identificación nacional o contraseñas. Dependiendo del contexto, como en el caso de intimidación o acoso, podemos considerar otra información, tales como fotos o vídeos que fueron tomados o distribuidos sin el consentimiento de la persona, una invasión de la privacidad, especialmente cuando dicho material representa un riesgo para la seguridad del sujeto. - -* **Contenido sexualmente obsceno** - No publiques contenido pornográfico. Esto no significa que toda la desnudez o todo el código y contenido relacionados con la sexualidad, esté prohibido. Reconocemos que la sexualidad es parte de la vida y que el contenido sexual no pornográfico puede ser parte de su proyecto o puede presentarse con fines educativos o artísticos. No permitimos contenidos sexuales obscenos que puedan implicar la explotación o la sexualización de menores. - -* **Contenido violento injustificadamente** - No publique imágenes, texto u otro contenido sin un contexto o advertencias razonables. Aunque a menudo es correcto incluir contenido violento en videojuegos, reportes de noticias y descripciones de acontecimientos históricos, no permitimos contenido violento que se publique de forma indiscriminada o que se publique de una manera que dificulte a otros usuarios evitarlo (por ejemplo, un avatar de perfil o un comentario sobre una propuesta). Una clara advertencia o renuncia de responsabilidad en otros contextos ayuda a los usuarios a tomar una decisión educada sobre si quieren participar en dichos contenidos o no. - -* **Información errónea y desinformación** - No puedes publicar contenido que presente una visión distorsionada de la realidad, es probable que sea inexacta o falsa (información errónea) o que sea intencionalmente engañosa (desinformación) porque dicho contenido probablemente resultará en daño al público o para interferir con oportunidades justas y equitativas para que todos participen en la vida pública. Por ejemplo, no permitimos contenido que pueda poner el bienestar de grupos de personas en riesgo o limitar su capacidad de participar en una sociedad libre y abierta. Fomentamos la participación activa en la expresión de ideas, perspectivas y experiencias y podríamos no estar en posición de disputar cuentas personales u observaciones. Por lo general, permitimos la parodia y la sátira que está en línea con nuestras políticas de uso aceptable y consideramos que el contexto es importante en la manera en que se recibe y se entiende la información; por lo tanto, puede ser adecuado aclarar tus intenciones mediante renuncias u otros medios, así como la fuente(s) de tu información. - -* **Malware activo o explotación de vulnerabilidad** - Ser parte de una comunidad incluye no aprovecharse de otros miembros de la comunidad. No permitimos que nadie utilice nuestra plataforma para la entrega de explotación de vulnerabilidad, por ejemplo usar GitHub como un medio para entregar ejecutables maliciosos, o como infraestructura de ataques, por ejemplo organizando ataques de denegación de servicio o gestionando servidores de comando y control. Sin embargo, ten en cuenta, que no prohibimos la publicación de código fuente que podría utilizarse para desarrollar malware o explotación de vulnerabilidad, ya que la publicación y distribución de dicho código fuente tiene un valor educativo y proporciona un beneficio neto a la comunidad de seguridad. - - -### ¿Qué sucede si alguien no comple con las reglas? - -Hay una serie de acciones que podemos tomar cuando un usuario reporta un comportamiento o contenido inadecuado. Por lo general, depende de las circunstancias exactas de un caso en particular. Reconocemos que en ocasiones la gente puede decir o hacer cosas inadecuadas por diversas razones. Tal vez no se dieron cuenta de cómo se percibirían sus palabras. O tal vez sólo dejan que sus emociones saquen lo mejor de ellos. Por supuesto, en ocasiones, hay gente que sólo quiere hacer spam o causar problemas. - -Cada caso requiere un enfoque diferente e intentamos adaptar nuestra respuesta para satisfacer las necesidades de la situación que se ha informado. Revisaremos cada informe de abuso caso por caso. En cada caso, tendremos un equipo diverso que investigue el contenido y los hechos relacionados y responda según corresponda, utilizando estas directrices para guiar nuestra decisión. - -Las acciones que podemos emprender en respuesta a un informe de abuso incluyen, pero no se limitan a: - -* Eliminación de contenido -* Bloqueo de contenido -* Suspensión de la cuenta -* Terminación de la cuenta - -### Avisos legales - -Dedicamos estas Pautas de la Comunidad al dominio público para que cualquiera pueda usar, reutilizar, adaptar o lo que sea, bajo los términos de [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/). - -Estas son solo directrices; no modifican nuestros [Términos de Servicio](/articles/github-terms-of-service/) y no pretenden ser una lista completa. GitHub mantiene total discreción bajo los [Términos de Servicio](/articles/github-terms-of-service/#c-acceptable-use) para eliminar cualquier contenido o cancelar cualquier cuenta por actividad que infrinja nuestros Términos del Uso Aceptable. Estas directrices describen en qué situaciones ejerceremos dicha discreción. diff --git a/translations/es-XL/content/github/site-policy/github-connect-addendum-to-the-github-enterprise-license-agreement.md b/translations/es-XL/content/github/site-policy/github-connect-addendum-to-the-github-enterprise-license-agreement.md deleted file mode 100644 index 070327ceef..0000000000 --- a/translations/es-XL/content/github/site-policy/github-connect-addendum-to-the-github-enterprise-license-agreement.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Anexo de GitHub Connect al Acuerdo de licencia de GitHub Enterprise -redirect_from: - - /articles/github-com-connection-addendum-to-the-github-enterprise-license-agreement/ - - /articles/github-connect-addendum-to-the-github-enterprise-license-agreement -versions: - free-pro-team: '*' ---- - -POR FAVOR LEE ESTA ADENDA CUIDADOSAMENTE, YA QUE ES UN ANEXO A LAS CONDICIONES DE TU ACUERDO DE LICENCIA EMPRESARIAL CON NOSOTROS Y RIGE ESPECÍFICAMENTE TU USO DE GITHUB CONNECT (COMO SE DEFINE A CONTINUACIÓN), A MENOS DE QUE GITHUB ("NOSOTROS") HAYA EJECUTADO UNA ADENDA SEPARADA Y POR ESCRITO CONTIGO PARA ESTE PROPÓSITO. - -CUANDO A CCEDES A GITHUB CONNECT, ACEPTAS TODOS LOS TÉRMINOS Y CONDICIONES DE ESTA ADENDA. SI ESTÁS INGRESANDO A ESTA ADENDA REPRESENTANDO A UNA COMPAÑÍA O A CUALQUIER OTRA ENTIDAD LEGAL ("CLIENTE"), ACEPTAS QUE TIENES LA AUTORIDAD LEGAL PARA VINCULAR AL CLIENTE CON ESTE CONTRATO. - -#### 1. Se aplicarán las condiciones de servicio de GitHub y el contrato de licencia de software empresarial de GitHub; Precios - -El cliente podrá habilitar integraciones unificadas, lo cual le permite a los usuarios de la empresa del mismo conectarse con GitHub.com ("GitHub Connect"). Para acceder a GitHub Connect, el cliente deberá contar con por lo menos una (1) cuenta en GitHub.com y una (1) instancia con licencia de GitHub Enterprise. El acceso de los clientes a GitHub Connect también se regirá por las Condiciones de Servicio de GitHub.com aplicables y a los contratos que se incorporen por referencia en la presente, (las "Condiciones Generalmente Aplicables"), para que las Condiciones Generalmente Aplicables se ejerzan simultáneamente. En caso de suscitarse un conflicto directo entre esta adenda y los Términos Generalmente Aplicables, los últimos se favorecerán, con excepción de los casos que involucren el uso de GitHub Connect, en cuyo caso, se favorecerá a la adenda. - -El cliente no deberá usar GitHub Connect para violar sus Términos Generalmente Aplicables. Cualquier uso de GitHub Connect que viole los Términos Generalmente Aplicables también constituirá una violación de esta adenda. La Conexión con GitHub se puede usar para ejecutar tareas automatizadas. Además, múltiples Usuarios pueden dirigir determinadas acciones con Conexión con GitHub. El cliente es responsable por las acciones que se realicen en o a través de sus cuentas. - -La participación de GitHub Connect se proporciona sin cargo adicional a través del plazo de la adenda (como se define a continuación). - -#### 2. Confidentiality - -Mientras no entren en conflicto con las obligaciones de confidencialidad proporcionadas en el Contrato de Licencia de Software Empresarial de GitHub, GitHub Connect, incluyendo cualquier información confidencial, se regirá mediante las obligaciones de confidencialidad aquí citadas. - -Para propósito de esta adenda, la "información confidencial" se referirá a cualquier información de negocio o técnica que se comparta con la otra parte (específicamente excluyendo cualquier contenido o información creado o compartido en el Servicio o Sitio Web, cuyo contenido o información se rige mediante otros aprovisionamientos en esta adenda y en los Términos Generalmente Aplicables) que cualquiera de nosotros divulgue al otro, ya sea por escrito, oralmente o por cualquier otro medio, incluyendo programas de cómputo, código, algoritmos, datos, conocimiento de manejo, fórmulas, procesos, ideas, invenciones (ya sean patentables o no), modelados y otros planes técnicos, de negocios, financieros y de desarrollo, nombres y experiencia de los empleados y consultores, y listas de clientes. Cada parte acuerda mantener la información confidencial de la otra parte como confidencial, utilizando por lo menos el mismo grado de cuidado que utiliza en el salvaguardo de su propia información confidencial, sujeta a un estándar mínimo de diligencia y protección razonables. - -#### 3. Plazo y terminación - -Esta adenda comienza en la Fecha de Entrada en Vigor de la misma y continúa durante el Periodo de Licencia de acuerdo con lo definido en los Términos Generalmente Aplicables ("Periodo de la Adenda"). Esta adenda puede terminarse de acuerdo con los Términos Generalmente Aplicables. Esta adenda terminará inmediatamente, sin requerir notificación alguna sobre ello, si el cliente infringe cualquier condición de la misma o de los Términos Generalmente Aplicables. - -Los derechos y obligaciones declarados en las secciones 1, 2, 4 hasta la 12, o los que debieran sobrevivir naturalmente a la terminación o caducidad de un acuerdo, también sobrevivirán al término o caducidad de esta adenda o de los Términos Generalmente Aplicables. Una vez que termine o caduque la presente adenda, todos los derechos y licencias otorgados al cliente en ella cesarán inmediatamente, el cliente deberá destruir (o, a petición de GitHub, regresar) toda la información confidencial y cualquier copia (incluyendo las electrónicas) que estén en posesión o control del cliente, y certificar por escrito el cumplimiento con estos requisitos. - -#### 4. Garantías y limitaciones de responsabilidades - -El cliente autoriza que: (1) tiene la utoridad para ejecutar esta adenda y realizar sus obligaciones; (ii) no hará declaraciones o representaciones falsas o engañosas con respecto a GitHub o los productos y servicios de GitHub; y (iii) no asumirá ninguna obligación o responsabilidad, o hará ninguna representación, autorización, garantía o respaldo a nadie en nombre de GitHub (incluyendo, sin limitación, a cualquiera de sus productos o servicios). - -EL CLIENTE ENTIENDE Y CONVIENE QUE CUALQUIER MATERIAL O INFORMACIÓN QUE SE LE PROPORCIONA O A LA CUAL TIENE ACCESO BAJO ESTA ADENDA (INCLUYENDO, SIN LIMITACIÓN, CUALQUIER INFORMACIÓN CONFIDENCIAL O MATERIAL DE PRE-LANZAMIENTO) SE PROPORCIONA "TAL Y COMO ESTÁ", Y SIN AUTORIZACIÓN DE NINGUNA MANERA, EXPRESA O IMPLÍCITA. GITHUB RENUNCIA ESPECÍFICAMENTE A TODAS Y CADA UNA DE LAS GARANTÍAS IMPLÍCITAS O CONDICIONES DE COMERCIABILIDAD, ADAPTABILIDAD PARA UN FIN ESPECÍFICO Y NO INCUMPLIMIENTO. - -#### 5. Indemnización - -El cliente acuerda indemnizar, defender y exonerar de toda responsabilidad a GitHub de y con respecto a cualquier reclamación que pudiera generarse debido a la participación del cliente en GitHub Connect; la negligencia o mal comportamiento del cliente; cualquier mala interpretación que el cliente haga con respecto a GitHub o los productos y servicios de GitHub; o la violación del cliente a cualquier parte de esta Adenda. - -#### 6. Limitación de responsabilidad - -NINGUNA DE LAS PARTES SERÁ RESPONSABLE, EN NINGÚN CASO, DE LA OTRA O DE CUALQUIER TERCERO POR NINGÚN DAÑO INDIRECTO, ESPECIAL, INCIDENTAL, CONSECUENCIAL, EJEMPLAR O PUNITIVO, INCLUYENDO MAS NO LIMITÁNDOSE A AQUELLOS POR PÉRDIDA DE DATOS, PÉRDIDA DE GANANCIAS O COSTOS DE CONTRATACIÓN DE BIENES O SERVICIOS SUSTITUTOS CAUSADOS DE CUALQUIER MANERA Y BAJO CUALQUIER TEORÍA DE RESPONSABILIDAD; YA SEA CONTRACTUAL, POR AGRAVIO (INCLUYENDO RESPONSABILIDAD POR PRODUCTOS ILIMITADOS, RESPONSABILIDAD ESTRICTA Y NEGLIGENCIA), O EN CUALQUIER OTRA TEORÍA, Y YA SEA QUE LA PARTE SEPA O NO, O DEBIESE HABER SABIDO SOBRE LA POSIBILIDAD DE DICHO DAÑO. DE NINGUNA MANERA, LA RESPONSABILIDAD GLOBAL DE GITHUB HACIA LOS CLIENTES, LA CUAL SURJA DE O POR CAUSAS RELACIONADAS CON ESTA ADENDA POR CUALQUIER MOTIVO, Y SIN IMPORTAR LA FORMA DE ACCIÓN, YA SEA EN CONTRATO O AGRAVIO, EXCEDERÁ LA MÁXIMA (I) CANTIDAD PAGADA BAJO ESTA ADENDA; O (II) QUINIENTOS DÓLARES ($500). LAS LIMITACIONES PRECEDENTES APLICARÁN NO OBSTANTE EL FRACASO DEL PROPÓSITO ESENCIAL DE CUALQUIER SOLUCIÓN LIMITADA QUE SE DECLARE EN ESTA ADENDA. - -#### 7. Derechos de propiedad - -El cliente acuerda que GitHub y sus licenciantes son propietarios de todos los derechos, títulos e intereses en y a través de todos los productos y servicios de GitHub; toda información y datos relacionados con las configuraciones y combinaciones; y todas las modificaciones y trabajo derivado de cualquiera de los anteriores. El cliente no debe eliminar, alterar, cubrir u ofuscar ningún derecho de autor u otros avisos de derechos de proviedad que GitHub coloque o inserte en GitHub Connect, o en cualquier otro producto o servicio de GitHub. - -#### 8. Desarrollo independiente - -Ninguna parte de la presente adenda impedirá el derecho de GitHub para desarrollar, adquirir, licenciar, comercializar, promocionar o distribuir productos, software o tecnologías que pudiesen competir con aquellas del cliente. - -#### 9. Privacidad - -GitHub puede recolectar información acerca de cómo el Cliente utiliza GitHub Connect y cómo GitHub puede mejorarlo. El cliente puede habilitar a GitHub Connect para autorizar a GitHub la recolección de datos protegidos, lo cual incluye aquellos datos de repositorios privados y la Información Personal de Cliente (como se define en la Declaración de Privacidad de GitHub), desde la cuenta empresarial del cliente. Si el cliente conecta su instancia empresarial con su cuenta de GitHub.com, éste envía información de identificación de la instancia a GitHub.com, la cual se rige mediante la [Declaración de Privacidad de GitHub](/articles/github-privacy-statement/). Al habilitar esta configuración, el cliente acuerda que es responsable por las acciones que se realicen en o a través de su cienta, sujetas a las condiciones de los Términos Generalmente Aplicables. - -GitHub puede recolectar cierta información personal adicional del Cliente en GitHub Connect. Por ejemplo, GitHub puede invitar al cliente a que envíe retroalimentación (como se explica en la sección 10). GitHub puede hacer preguntas acerca de las experiencias de los usuarios del cliente, la familiaridad con el producto, o información demográfica. GitHub utilizará esta información para mejorar sus productos y servicios, y no la venderá a terceros o anunciantes. Los clientes pueden negarse a proporcionar retroalimentación o a responder preguntas específicas, o pueden contactar a GitHub para borrar o cambiar la información que han proporcionado. - -GitHub's servers are located in the United States. GitHub procesa y controla los datos del cliente en los Estados Unidos. Sin embargo, el cliente es el único responsable de determinar qué datos personales emite a GitHub. Por favor, consulta nuestra [Declaración de privacidad](/articles/github-privacy-statement/) para obtener más información. - -#### 10. Comentarios - -El cliente podrá, opcionalmente, proporcionar ideas, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de ampliación, recomendaciones, o cualquier otro tipo de retroalimentación para GitHub Connect o cualquier otro producto o servicio de GitHub (conjuntamente, "Retroalimentación"). Si el cliente proporciona retroalimentación, reconoce y acuerda que GitHub tendrá licencia exenta de regalías, totalmente pagada, internacional, transferible, sub-licenciable, irrevocable y perpetua para implementarla, utilizarla, modificarla, aprovecharla comercialmente o incorporarla en sus productos, servicios y documentación. - -#### 11. Entire Agreement - -Esta adenda y los Términos Generalmente Aplicables contienen el acuerdo completo de las partes con respecto a su tema y sustituye a cualquier comunicación, representación, entendimiento y acuerdo previo, ya sea en forma oral o escrita. Los términos y condiciones de cualquier orden de compra, reconocimiento u otro tipo de documento del cliente que se envíe en conexión con la presente adenda se considerarán nulos y vetados, y no tendrán efecto. - -#### 12. Sin otras modificaciones; orden de precedencia - -A menos que se indique expresamente en la presente, nada en esta adenda se deberá considerar como una renuncia o modificación a ninguna de las disposiciones del acuerdo, que de otra forma permanece en pleno vigor y efecto. En caso de que se suscite cualquier conflicto entre el acuerdo y esta adenda con respecto al tema aquí expuesto, esta adenda deberá prevalecer. diff --git a/translations/es-XL/content/github/site-policy/github-corporate-terms-of-service.md b/translations/es-XL/content/github/site-policy/github-corporate-terms-of-service.md deleted file mode 100644 index 6b645b7c0a..0000000000 --- a/translations/es-XL/content/github/site-policy/github-corporate-terms-of-service.md +++ /dev/null @@ -1,313 +0,0 @@ ---- -title: Términos de servicio corporativos de GitHub -redirect_from: - - /articles/github-corporate-terms-of-service -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -GRACIAS POR ELEGIR GITHUB PARA CUBRIR LAS NECESIDADES COMERCIALES DE SU EMPRESA. LEE ESTE ACUERDO CUIDADOSAMENTE YA QUE RIGE EL USO DE LOS PRODUCTOS (COMO SE DEFINEN A CONTINUACIÓN), A MENOS QUE GITHUB HAYA CELEBRADO UN ACUERDO POR ESCRITO POR SEPARADO CON EL CLIENTE PARA DICHO PROPÓSITO. AL HACER CLIC EN EL BOTÓN "ACEPTO" O EN UN BOTÓN SIMILAR O AL UTILIZAR CUALQUIERA DE LOS PRODUCTOS, EL CLIENTE ACEPTA TODOS LOS TÉRMINOS Y CONDICIONES DEL PRESENTE ACUERDO. SI EL CLIENTE ESTÁ CELEBRANDO ESTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA PERSONA MORAL, EL CLIENTE REPRESENTA QUE TIENE LA AUTORIDAD LÉGAL DE VINCULAR A LA EMPRESA U OTRAS PERSONAS MORALES AL PRESENTE ACUERDO. - -### Términos de servicio corporativos de GitHub -Fecha de entrada en vigor de la versión: 20 de julio de 2020 - -El presente Acuerdo se aplica a las siguientes ofertas de GitHub, como se define a continuación (colectivamente, los **“Productos”**): -- El servicio; -- Cualquier Vista previa Beta; -- Cualquier Soporte relacionado; y -- Cualquier Servicio profesional relacionado. - -### A. Definiciones - -**"Filial"** significa cualquier entidad que controle directa o indirectamente, esté controlada por, o esté bajo control común con una parte donde el "control" signifique tener más del cincuenta por ciento (50%) de la propiedad o el derecho a dirigir la gestión de la entidad. - -**"Acuerdo"** significa, colectivamente, todos los términos, condiciones, avisos contenidos o referenciados en este documento y todas las demás reglas operativas. políticas y procedimientos que GitHub puede publicar periódicamente en el Servicio. Las políticas de sitio de GitHub están disponibles en [https://docs.github.com/categories/site-policy](/categories/site-policy). - -**“Todos los usuarios”** se refiere, en conjunto, a los Usuarios del Cliente y los Usuarios externos que usan el Servicio. - -**“Américas”** se refiere a los Estados Unidos, Canadá, México o un país de América Central o América del Sur o el Caribe. - -**"Vistas previas beta"** se refiere al software, los servicios o las funciones identificadas como alfa, beta, vista previa, acceso temprano o evaluación, o a las palabras o frases con significados similares. - -**"Información confidencial"** se refiere a toda la información no pública divulgada por cualquiera de las Partes a otros, ya sea por escrito, en forma oral o por otros medios, designada como confidencial o que la Parte receptora sabe o razonablemente debe saber, conforme a las circunstancias en torno a la divulgación y la naturaleza de la información, que es confidencial para la Parte reveladora. Para evitar dudas, ningún Contenido publicado en el Servicio se considerará Información confidencial excepto el Contenido del Cliente almacenado únicamente en los Repositorios privados del Cliente. La Información confidencial no incluye ninguna información que (i) era de conocimiento público o se dio a conocer públicamente por motivos ajenos a la parte receptora; (ii) era legítimamente conocida o se dio a conocer en forma legítima a la Parte receptora sin restricciones de propiedad o confidencialidad por parte de una fuente que no es la parte reveladora y que tiene derecho a divulgarla; (iii) es aprobada por la Parte reveladora para su divulgación sin restricciones en un documento escrito firmado por un funcionario debidamente autorizado de dicha Parte reveladora; (iv) la Parte receptora desarrolla independientemente sin el acceso a la Información confidencial de la otra Parte ni el uso de esta; o (v) está o estuvo almacenada o publicada en el Servicio y fuera de los Repositorios privados del Cliente. - -**"Contenido"** significa, sin limitaciones, código, texto, datos, artículos, imágenes, paquetes, fotografías, gráficos, software, aplicaciones, diseños, características y otros materiales que se destacan, muestran o se ponen a disposición a través del Servicio. - -**"Cuenta corporativa"** se refiere a una cuenta creada por el Usuario en nombre de una entidad. - -**"Cliente"** se refiere a la empresa u organización que ha celebrado el presente Acuerdo con GitHub haciendo clic en el botón "AGREE" o similar o ingresando a los Productos. - -**"Contenido del Cliente"** se refiere al Contenido que el Cliente crea, posee o sobre el cual el Cliente tiene los derechos. - -**"Documentación"** hace referencia a cualquier manual, documentación y otros materiales de soporte relacionados con los productos que GitHub proporciona o pone a disposición del cliente. - -**"Fecha efectiva"** es la fecha anterior sobre la cual el cliente (i) hace clic en "Acepto" los términos y condiciones de este acuerdo, o (ii) hace primero un pedido de los Productos. - -**"Usuario externo"** se refiere a un individuo, que no incluye a los Usuarios del Cliente, que visita o usa el Servicio. - -**"Comentarios"** se refiere a cualquier idea, conocimiento, algoritmo, contribución de código, sugerencia, solicitud de mejora, recomendación o cualquier otro comentario sobre los productos o servicios de GitHub. - -**"Cuotas"** hace referencia las tarifas que el Cliente debe pagar a GitHub para (i) usar los Productos durante el término aplicable o (ii) recibir Servicios Profesionales, ya que dichas tarifas se reflejan en un Formulario de Pedido o SOW. - -**“Bifurcación”** se refiere a copiar el Contenido de un repositorio en otro repositorio. - -**"GitHub"** significa GitHub, Inc., sus filiales y sus representantes. - -**"Contenido de GitHub"** se refiere al Contenido que GitHub crea, posee o el contenido sobre el cual tiene los derechos. - -**“Cuenta de máquina”** se refiere a una cuenta registrada por una persona que acepta los términos aplicables del servicio en nombre de la Cuenta de máquina, proporciona una dirección de correo electrónico válida y es responsable de sus acciones. Una Cuenta de máquina se usa exclusivamente para ejecutar tareas automatizadas. Múltiples usuarios pueden dirigir las acciones de una Cuenta de máquina, pero el propietario de la cuenta es responsable en última instancia de las acciones de la máquina. - -**"Formulario de pedidos"** significa documentación escrita o electrónica (incluyendo una cotización), que las Partes pueden utilizar para ordenar los Productos. - -**“Organización”** se refiere a un espacio de trabajo compartido que se puede asociar con una única entidad o con uno o más Usuarios donde múltiples Usuarios pueden colaborar en muchos proyectos a la vez. Un Usuario puede ser miembro de más de una Organización. - -**“Repositorio privado”** se refiere a un repositorio que permite que un Usuario controle el acceso al Contenido. - -**"Servicios Profesionales"** se refiere a la capacitación, consulta o servicios de implementación que GitHub proporciona al Cliente de acuerdo con una SOW ejecutada recíprocamente. Los Servicios profesionales no incluyen el Soporte. - -**"Créditos de servicios profesionales"** se refiere al método de pago inicial para comprar Servicios profesionales (sin incluir los viajes y gastos de alojamiento) que el Cliente puede usar en un período de doce (12) meses (a menos que se indique lo contrario en un Formulario de pedidos) para los Servicios profesionales. Cualquier Crédito de servicios profesionales que quede sin uso luego de los doce (12) meses posteriores a la fecha de compra (o como se indique en un Formulario de pedidos) quedará automáticamente cancelado y no será reembolsable. - -**“Repositorio público”** se refiere a un repositorio cuyo Contenido es visible para todos los Usuarios. - -**"Representantes"** hace referencia a los empleados, oficiales, agentes, contratistas independientes, consultores y asesores jurídicos y financieros. - -**“Extracción”** se refiere a extraer datos del Servicio a través de un proceso automatizado, como un bot o agente de búsqueda, y que no incluye la recopilación de información a través de la API de GitHub. - -**"Servicio"** significa el servicio alojado de GitHub y cualquier Documentación aplicable. - -**"SOW"** significa una declaración de trabajo ejecutada recíprocamente que detalla los Servicios Profesionales que GitHub realizará, cualquier tarifa relacionada y las obligaciones relacionadas con cada parte. - -**"Licencia de suscripción"** hace referencia a la licencia asignada a cada Usuario para instalar, operar, ingresar y utilizar el Servicio en nombre del Cliente. El cliente sólo puede asignar una Licencia de Suscripción por Usuario a través de sus Organizaciones. Para mayor claridad, una vez que el Cliente asigna una Licencia de Suscripción a un Usuario, el Cliente no estará autorizado a bifurcar la Licencia de Suscripción de modo que un Usuario podrá usar una Licencia de Suscripción en una Organización mientras que otro Usuario utiliza la misma Licencia de Suscripción en otra Organización. - -**“Soporte”** se refiere al soporte técnico para el Servicio que GitHub puede proporcionar. - -**"Usuario"** significa una cuenta individual o de máquina que (a) ingresa o utiliza el Servicio, (b) ingresa o utilizar cualquier parte de la cuenta del cliente; o (c) dirige el uso de la cuenta del Cliente en el desempeño de las funciones, en cada caso en nombre del Cliente. La cantidad de Usuarios no debe exceder el número de Licencias de suscripción que el Cliente compró. - -**“Contenido generado por el Usuario”** se refiere al Contenido que un tercero o un Usuario externo crea o posee. - -### B. Términos de la cuenta - -#### 1. Controles de la cuenta. - * _Usuarios._ El cliente reconoce que los Usuarios conservan el control administrativo definitivo sobre sus cuentas individuales y el Contenido dentro de ellas. [Las condiciones de servicio estándar de GitHub](/articles/github-terms-of-service) rigen el uso del servicio por parte de los usuarios, excepto con respecto a las actividades de los usuarios en esta Sección B. - - * _Organizaciones._ El cliente conserva el control administrativo definitivo sobre cualquier organización creada en nombre del cliente y el contenido generado por el usuario publicado en los repositorios dentro de la(s) organización(es), sujeto a esta Sección B. Esta Sección B regirá el uso de la Organización(es) del Cliente. - -#### 2. Requisitos de la cuenta -Para crear una cuenta, el Cliente debe adherirse a los siguientes puntos: - -* El cliente no debe crear una cuenta para el uso de ninguna persona menor de 13 años. Si GitHub se entera de que existe algún Usuario menor de 13 años, cancelará esa cuenta de Usuario de inmediato. Si el Cliente o su(s) Usuario(s) están ubicados en un país fuera de los Estados Unidos, la edad mínima de ese país puede ser mayor; en ese caso, el Cliente es responsable de cumplir con las leyes de ese país. - -* El inicio de sesión de un usuario no puede compartirse por varias personas. - -- Customer must not use the Products (a) in violation of export control or sanctions laws of the United States or any other applicable jurisdiction; (b) if it is located in or ordinarily resident in a country or territory subject to comprehensive to comprehensive sanctions administered by the U.S. Office of Foreign Assets Control (OFAC); or (c) if it is or is working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions. Para obtener más información, consulta nuestra[Política de Controles de Exportación](/articles/github-and-export-controls). - -#### 3. Account Security -El Cliente es responsable de: (i) todo el Contenido publicado y la actividad que se produce bajo su Cuenta Corporativa; (ii) mantener la seguridad de las credenciales de inicio de sesión de su cuenta; y (iii) [notificar rápidamente a GitHub](https://github.com/contact) al darse cuenta de cualquier uso no autorizado de, o ingreso al Servicio a través de su cuenta. GitHub no será responsable de ninguna pérdida o daño por el incumplimiento por parte del Cliente de esta Sección B. - -#### 4. Términos de terceros -En algunas situaciones, pueden aplicarse términos de terceros al uso del Cliente de GitHub. Por ejemplo, el Cliente puede ser miembro de una Organización con sus propios términos o acuerdos de licencia; el Cliente puede descargar una aplicación que se integre con el Servicio; o el Cliente puede usar el Servicio para autenticarse a otro servicio. Aunque este Acuerdo es el acuerdo completo de GitHub con el Cliente, los términos de otras partes rigen sus relaciones con el Cliente. - -#### 5. U.S. Términos del Gobierno federal de los EE.⁰UU -If Customer is a U.S. government entity or otherwise accessing or using the Service in a government capacity, the [U.S. Federal Government Amendment](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) applies, and Customer agrees to its provisions. - -#### 6. Enterprise Cloud Service Level Agreement -GitHub’s quarterly uptime commitment for GitHub Enterprise Cloud is provided in the [Enterprise Service Level Agreement](/github/site-policy/github-enterprise-service-level-agreement). If Customer signed up for GitHub Enterprise Cloud, then Customer will be entitled to a service credit if GitHub does not meet its service level. - -### C. Compliance with Laws; Acceptable Use; Privacy - -#### 1. Cumplimiento con las leyes y regulaciones -El uso del cliente de los Productos no debe violar ninguna ley aplicable, incluyendo leyes de derechos de autor o marcas comerciales, leyes de control de exportación o regulaciones en su jurisdicción. - -#### 2. Uso aceptable -El uso que el Cliente dé al servicio deberá cumplir con las [Políticas de Uso Aceptado de GitHub](/articles/github-acceptable-use-policies) y los [Lineamientos de la Comunidad de GitHub](/articles/github-community-guidelines). El Cliente no debe usar el Servicio en ninguna jurisdicción si contiene Contenidos o actividades ilegales, obscenos, ofensivos o fraudulentos, tales como promover o causar daño, vulnerar la integridad o la seguridad de una red o sistema o interferir en ellos, evadir filtros, enviar mensajes no solicitados, abusivos o engañosos, virus o códigos perjudiciales, o socavar los derechos de terceros. - -#### 3. Privacidad -La [Declaración de Privacidad de GitHub](/articles/github-privacy-statement) y la [Adenda de Protección de Datos de Github](/github/site-policy/github-data-protection-addendum) proporcionan una notificación detallada de las prácticas de privacidad y para el uso de datos de GitHub así como el procesamiento de GitHub y las obligaciones de seguridad con respecto a los Datos Personales del Cliente. Cualquier persona, entidad o servicio que recolecte datos del Servicio debe cumplir con la Declaración de Privacidad de GitHub, en particular en lo que se refiere a la recopilación de datos personales de los usuarios (como se define en la Declaración de Privacidad de GitHub). Si el Cliente recopila cualquier Información personal del usuario proveniente de GitHub, el Cliente solamente la usará para el propósito por el cual el Usuario externo lo autorizó. El Cliente asegurará razonablemente dicha Información personal y el Cliente responderá de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" de GitHub o de Usuarios externos. - -### D. Content Responsibility; Ownership; License Rights - -#### 1. Responsabilidad para el Contenido generado por el usuario -El Cliente puede crear o cargar Contenido generado por el Usuario mientras usa el Servicio. El cliente es el único responsable de cualquier Contenido Generado por el Usuario que publique, suba, enlace o ponga a disposición a través del Servicio, independientemente de la forma de ese Contenido Generado por el Usuario. GitHub no es responsable de ninguna visualización pública o uso indebido del Contenido generado por el Usuario. - -#### 2. Propiedad del Contenido, Derecho a publicar y Otorgamientos de licencia -El cliente mantiene la propiedad del Contenido del Cliente que este crea o posee. El Cliente reconoce lo siguiente: (a) que es responsable del Contenido del Cliente, (b) que solo enviará el Contenido del Cliente que el Cliente tenga derecho a publicar (incluido el Contenido generado por el Usuario o por terceros) y (c) que el Cliente cumplirá plenamente con cualquier licencia de terceros relacionada con el Contenido del Cliente que el Cliente publica. El Cliente otorga los derechos establecidos en las Secciones D.3 a D.6, de forma gratuita y para los propósitos identificados en dichas secciones hasta que el Cliente retire el Contenido del Cliente de los servidores de GitHub, excepto por el contenido que el cliente ha anunciado públicamente y que los usuarios externos han bifurcado, en cuyo caso la licencia es perpetua hasta que todos los Forks del Contenido del Cliente se hayan eliminado de los servidores de GitHub. Si el Cliente carga Contenido del Cliente que ya viene con una licencia y le otorga a GitHub los permisos que necesita para ejecutar el Servicio, no se requiere ninguna licencia adicional. - -#### 3. Licencia otorgada -El Cliente le otorga a GitHub el derecho a almacenar, analizar y mostrar el Contenido del Cliente y de hacer copias incidentales solo como sea necesario para proporcionar el Servicio. Esto incluye el derecho a copiar el Contenido del Cliente en la base de datos de GitHub y a hacer copias de seguridad; mostrarle el Contenido del Cliente al Cliente y a quienes el Cliente decida; analizar el Contenido del Cliente en un índice de búsqueda o, de lo contrario, analizarlo en los servidores de GitHub; compartir el Contenido del Cliente con Usuarios externos con los cuales el Cliente elige compartirlo; y reproducir el Contenido del Cliente, en el caso de que se trate de música o vídeo. Estos derechos se aplican tanto a los Repositorios privados como a los públicos. Esta licencia no le otorga a GitHub el derecho a vender el Contenido del Cliente o a distribuirlo o utilizarlo por fuera del Servicio. El Cliente le otorga a GitHub los derechos que necesita para usar el Contenido del Cliente sin atribución y para hacer las adaptaciones razonables del Contenido del Cliente como sea necesario para proporcionar el Servicio. - -#### 4. License Grant to External Users -Cualquier Contenido que el Cliente anuncie públicamente, incluyendo temas, comentarios y contribuciones a los repositorios de usuarios externos, puede ser visto por otros. El Cliente acepta permitir que Usuarios externos vean y bifurquen los repositorios del Cliente cuando configura sus repositorios para que se vean públicamente. Si el Cliente coloca sus páginas y repositorios para ser vistos públicamente, el Cliente concede a los usuarios externos una licencia no exclusiva a nivel mundial para usar, mostrar, y realizar Contenido del Cliente a través del Servicio y reproducir Contenido del Cliente únicamente en el Servicio según lo permitido a través de la funcionalidad proporcionada por GitHub (por ejemplo, a través de Forking). El Cliente puede conceder más derechos al Contenido del Cliente si adopta una licencia. Si el Cliente está cargando Contenido del Cliente que no creó ni posee, el Cliente es responsable de asegurar que el Contenido del Cliente que carga cuente con licencia conforme a los términos que otorgan estos permisos a los Usuarios externos - -#### 5. Contribuciones conforme a la Licencia del repositorio -Cada vez que el cliente hace una contribución a un repositorio que contiene una notificación de una licencia, otorga licencias a dichas contribuciones en los mismos términos y acepta que tiene derecho a autorizar dichas contribuciones en virtud de dichos términos. Si el Cliente tiene otro acuerdo para licenciar sus contribuciones conforme a términos diferentes, tal como un acuerdo de licencia de colaborador, ese acuerdo prevalecerá. - -#### 6. Derechos morales -El Cliente conserva todos los derechos morales sobre el Contenido del Cliente que carga, publica o envía a cualquier parte del Servicio, incluidos los derechos de integridad y atribución. Sin embargo, el cliente renuncia a estos derechos y acuerda no establecerlos contra GitHub, únicamente para permitir a GitHub ejercer razonablemente los derechos otorgados en la Sección D, pero no de otro modo. - -### E. Repositorios privados - -#### 1. Control -El cliente es responsable de administrar el acceso a sus Repositorios Privados, incluyendo invitaciones, control administrativo de Organizaciones y equipos y de acceso. - -#### 2. Confidentiality -GitHub considera que el Contenido del Cliente en los Repositorios privados del Cliente constituye Información confidencial del Cliente. GitHub protegerá y mantendrá estrictamente confidencial el Contenido del Cliente de los Repositorios Privados de acuerdo con la Sección P. - -#### 3. Acceso -El personal de GitHub sólo puede acceder a los Repositorios Privados del Cliente (i) con el consentimiento y conocimiento del Cliente, por razones de soporte o (ii) cuando se requiera acceso por razones de seguridad. El Cliente puede decidir habilitar más acceso a sus Repositorios privados. Por ejemplo, el Cliente puede habilitar varios servicios o funciones de GitHub que requieren derechos adicionales sobre el Contenido del Cliente en los Repositorios privados. Estos derechos pueden variar según el servicio o la función, pero GitHub continuará considerando el Contenido del Cliente en los Repositorios privados del Cliente como Información confidencial. GitHub proporcionará una explicación sobre esos derechos si esos servicios o funciones requieren más derechos de los que necesita para proporcionar el Servicio. - -#### 4. Exclusiones -Si GitHub tiene razones para creer que el Contenido de un Repositorio privado incumple la ley o este Acuerdo, GitHub tiene derecho a acceder, revisar y eliminar ese Contenido. Además, GitHub puede estar [obligado por la ley](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar el contenido de los repositorios privados del cliente. A menos que los requisitos previstos por la ley indiquen lo contrario o que sea en respuesta a una amenaza de seguridad u otro riesgo para la seguridad, GitHub dará aviso de tales acciones. - -### F. Notificación de propiedad intelectual - -#### 1. Derechos de GitHub sobre el Contenido -La apariencia del Servicio es propiedad intelectual de © GitHub, Inc. Todos los derechos reservados. El Cliente no puede duplicar, copiar o volver a usar ninguna parte de los elementos o conceptos de HTML/CSS, Javascript o de diseño visual sin autorización expresa por escrito de GitHub. - -#### 2. Nombres comerciales y logos de GitHub -Si el Cliente desea usar los nombres comerciales de GitHub, debe seguir todas las pautas de nombres comerciales de GitHub, incluyendo las que se encuentran en la [página de logos de GitHub](https://github.com/logos). - -#### 3. Licencia a políticas de GitHub -Este Acuerdo está licenciado bajo la [licencia Creative Commons Cero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). - -#### 4. Violación de la propiedad intelectual y la política de DMCA -Si el cliente es un propietario de derechos de autor y considera que el Contenido del servicio viola los derechos de autor del Cliente, el cliente puede notificar a GitHub de acuerdo con la[Ley de Derechos de Autor del Milenio Digital](/articles/dmca-takedown-policy/) de GiHub a través del [formulario DMCA](https://github.com/contact/dmca) o enviando un correo electrónico a copyright@github.com. - -#### 5. Derechos de propiedad intelectual reservados -Como fue acordado entre las Partes, GitHub posee todos los derechos, títulos e intereses, incluidos todos los derechos de propiedad intelectual, sobre los Productos y para ellos. GitHub se reserva todos los derechos sobre los Productos y para ellos no otorgados expresamente al Cliente conforme a lo dispuesto en el presente Acuerdo. - -### G. Términos adicionales de los productos de GitHub -Algunas características de servicio pueden estar sujetas a términos adicionales como se establece en los [términos de producto adicionales de GitHub](/github/site-policy/github-additional-product-terms). Al acceder o utilizar estas características, el cliente acepta las condiciones de producto adicionales de GitHub. - -### H. Subscription Licenses -Las Licencias de suscripción se otorgan por Usuario y la misma Licencia de suscripción no puede ser utilizada por múltiples Usuarios. El Cliente puede reasignar una Licencia de suscripción a un nuevo Usuario solo después de noventa (90) días desde la última reasignación de esa misma Licencia de suscripción, excepto que la reasignación se deba a (i) la pérdida o la falla permanente del hardware, (ii) la terminación del empleo o el contrato del Usuario, o (iii) la readjudicación temporal de las Licencias de Suscripción para cubrir una ausencia del Usuario. Cuando el Cliente reasigna una Licencia de suscripción de un Usuario a otro, el Cliente debe bloquear el acceso del Usuario anterior a la Licencia de suscripción y a las Organizaciones del Cliente. - -### I. Affiliates -Los afiliados del cliente están autorizados a utilizar los Productos de conformidad con este Acuerdo, siempre y cuando el Cliente sea plenamente responsable de su acceso y uso de los Productos. - -### J. Pago - -#### 1. Precios; Tarifas - -**Términos de pago** Nuestro precio está disponible en [github.com/pricing](https://github.com/pricing) (a menos que las partes lo negocien de otra forma y lo indiquen en un Formulario de Pedido). El Cliente acepta pagar las Tarifas por completo, desde el inicio sin deducciones ni compensaciones de ningún tipo, en Dólares estadounidenses. estadounidenses. El cliente debe pagar las Tarifas dentro de los treinta (30) días de la fecha de la factura de GitHub. Los importes pagaderos en virtud de este Acuerdo no son reembolsables, excepto que se estipule de otro modo en este Acuerdo. Si el cliente no paga las Tarifas a tiempo, GitHub se reserva el derecho, además de tomar cualquier otra acción en la ley o equidad, para (i) cobrar intereses sobre importes vencidos en 1.0% al mes o el tipo de interés más alto permitido por la ley, el que sea menor y cobrar todos los gastos de recuperación, y (ii) cancelar el Formulario de Pedido o SOW aplicable. El Cliente es el único responsable de todos los impuestos, tarifas, obligaciones y valoraciones gubernamentales (a excepción de los impuestos basados en los ingresos netos de GitHub) que se imponen o vencen en conexión con el presente Acuerdo. - -**Facturación basada en el uso** Algunas características del servicio se facturan según su uso. Una cantidad limitada de estas características del Servicio puede incluirse en su plan por un período limitado sin cargo adicional. Si decides comprar características de Servicio pagadas más allá de la cantidad incluida en tu plan, pagarás por estas funciones del Servicio con base en tu uso real en el mes anterior. El pago mensual de estas compras se cobrará de forma periódica en arreares, siempre y cuando para los clientes facturados, las funciones de Servicio de pago se facturan por adelantado. Consulte [Términos de producto adicionales de GitHub para obtener más detalles](/github/site-policy/github-additional-product-terms). - -#### 2. Purchasing Additional Subscription Licenses -El cliente puede obtener Licencias de Suscripción adicionales bajo este Contrato enviando una solicitud a través del Servicio o a través de su equipo de ventas. Si el Cliente compra las Licencias de suscripción adicionales, el Cliente debe pagar por ellas las Tarifas correspondientes vigentes en ese momento, prorrateadas por el saldo de la Vigencia de suscripción aplicable. Al momento de la renovación de las Licencias de suscripción del Cliente por otro Plazo de suscripción, GitHub facturará todas las Licencias de suscripción una sola vez al año excepto que se especifique lo contrario en un Formulario de pedidos. - -#### 3. Professional Services Credits. -Si el Cliente usa Créditos de servicios profesionales para pagar por Servicios profesionales, una vez que el Cliente reciba una SOW, los Créditos de servicios profesionales aplicables se deducirán del saldo de los Créditos de servicios profesionales del Cliente. El Cliente es responsable de asegurar que su orden de compra emitida a GitHub por los Servicios profesionales refleje los precios establecidos en la SOW. Si existiera una diferencia en los precios que figuran en la SOW y los precios que figuran en la orden de compra del Cliente, prevalecerán los precios de la SOW. Las Partes acuerdan que las SOW pagaderas a través de Créditos de servicios profesionales no necesitan firmarse por ninguna de las Partes para ser válidas y ejecutables. Todos los Créditos de servicios profesionales deben utilizarse durante el tiempo establecido en el Formulario de pedidos o se cancelarán automáticamente y serán no reembolsables. El Cliente no puede aplicar los Créditos de servicios profesionales en viajes y gastos de alojamiento, los cuales se deben facturar por separado. - -#### 4. Autorización -El cliente autoriza a GitHub a hacer un cargo en la tarjeta de crédito en el archivo, a la cuenta PayPal, u otros métodos de pago aprobados para Tarifas. - -### K. Término; Terminación; Suspensión - -#### 1. Terminación -Este Contrato comienza en la Fecha de entrada en Vigencia y continuará en vigor hasta que una Parte lo rescinda de acuerdo con esta sección K. - -#### 2. Terminación por Conveniencia; Cancelación de Cuenta -Cualquiera de las Partes puede cancelar un Formulario de Pedido (si aplica) o este Contrato, sin causa, al menos treinta (30) días antes de la notificación por escrito. Si el Cliente elige poner fin a un Formulario de pedidos o a un Acuerdo, es responsabilidad del Cliente cancelar debidamente su cuenta con GitHub ingresando en Configuraciones en la barra de navegación global en la parte superior de la pantalla. GitHub no puede cancelar cuentas en respuesta a un correo electrónico o a una solicitud telefónica. - -#### 3. Termination for Material Breach -Cualquiera de las Partes puede terminar el presente Acuerdo en forma inmediata previa notificación si la otra Parte incumple una obligación esencial conforme a lo dispuesto en el presente Acuerdo y no puede subsanar el incumplimiento dentro de los treinta (30) días desde la fecha en que recibe la notificación. GitHub puede rescindir este Contrato si la Cuenta del Cliente se suspendió por más de 90 días. - -#### 4. Plazo y terminación -- _Formularios de Pedido._ Una vez rescindido el presente Contrato, el Cliente no podrá ejecutar Formularios de Pedido adicionales (si aplica); sin embargo, este Acuerdo permanecerá en vigor para el resto de los Formularios de Pedido activos. Cuando un Formulario de Pedido termina o expira, en cuanto a ese Formulario de Pedido: (i) el Plazo terminará inmediatamente; (ii) cualquier Licencia de Suscripción en el Formulario de Pedido cancelará automáticamente y el Cliente ya no tendrá derecho a usar el Servicio; (iii) si se adeuda alguna Tarifa antes de la terminación, el Cliente debe abonar dichas tasas inmediatamente; (iv) cada Parte devolverá rápidamente (o, si la otra parte lo solicita, destruirá) toda la Información Confidencial perteneciente al otro en la medida permitida por el Servicio. No obstante lo anterior, GitHub hará un esfuerzo razonable para proporcionar al Cliente una copia de sus Contenidos de cuenta legítimos y no infractores cuando lo solicite; siempre que el Cliente haga esta solicitud dentro de los 90 días siguientes a la terminación, suspensión o descenso de categoría. - -- GitHub conservará y utilizará la información del Cliente según sea necesario para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir los acuerdos de GitHub, pero abandonando los requisitos legales, GitHub eliminará el perfil completo del Cliente y el Contenido de sus repositorios dentro de los 90 días posteriores a la terminación o caducidad (aunque cierta información puede permanecer en copias de seguridad cifradas). Esta información no se puede recuperar una vez que la cuenta del Clientse se cancele. - -- GitHub no eliminará el Contenido que el Cliente ha contribuido a los repositorios de Usuarios Externos o que los Usuarios Externos han bifurcado. - -#### 5. Suspensión -GitHub tiene el derecho de suspender el acceso a todo o cualquier parte del Servicio, incluyendo la eliminación de Contenido, en cualquier momento por violación de este Contrato o para proteger la integridad, operabilidad y seguridad del Servicio, efectiva inmediatamente, con o sin previo aviso. A menos que esté prohibido por ley o proceso legal o para prevenir daños inminentes al Servicio o a cualquier tercero, GitHub normalmente proporciona un aviso en forma de banner o correo electrónico en o antes de dicha suspensión. GitHub personalizará, a su criterio y de buena fe, cualquier suspensión que sea necesaria para preservar la integridad, operatividad y seguridad del Servicio. - -#### 6. Continuidad -Todas las disposiciones de este Acuerdo que por su naturaleza deberían sobrevivir a la terminación sobrevivirán a la terminación, incluyendo, sin limitación, las provisiones de propiedad, las exenciones de garantía, indemnización y limitaciones de responsabilidad. - -### L. Comunicaciones con GitHub - -#### 1. Comunicación electrónica requerida -Con fines contractuales, el Cliente (1) consiente recibir comunicaciones en un formulario electrónico a través de la dirección de correo electrónico que se envío o a través del Servicio; y (2) acepta que todos los Términos de Servicio, acuerdos, avisos, revelaciones y otras comunicaciones que GitHub proporciona electrónicamente cumple con cualquier requerimiento legal que estas comunicaciones satisfagan si estuvieran en papel. Esta sección no afecta los derechos no renunciables del Cliente. - -#### 2. El aviso legal para GitHub debe ser por escrito -Las comunicaciones realizadas a través del correo electrónico o el sistema de mensajería del soporte de GitHub no constituirán un aviso legal a GitHub en ninguna situación en la que el contrato o cualquier ley o regulación requieran aviso a GitHub. El aviso legal a GitHub debe ser por escrito y [presentado al agente legal de GitHub](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests). - -### M. Garantía limitada; descargo de responsabilidad - -_Garantía General_. Cada una de las Partes manifiesta y garantiza a la otra Parte que tiene el poder legal y la autoridad para celebrar el presente Acuerdo, y que este Acuerdo y todos los Formularios de pedidos y SOW son concertados por un empleado o agente de dicha Parte con toda la autoridad necesaria para vincular a la Parte mencionada con los términos y condiciones del presente Acuerdo. - -_Garantía de Servicios Profesionales._ A menos que se exponga lo contrario en una SOW, GitHub garantiza que todos los Servicios Profesionales realizados bajo este Contrato se realizarán de forma profesional y con mano de obra por personal debidamente cualificada. La única obligación de GitHub, y el único remedio del cliente, por un incumplimiento de esta garantía serán, a opción y coste de GitHub: (i) realizar nueva y rápidamente los Servicios Profesionales que no cumplan con esta garantía o (ii) si la infracción no se puede remediar, rescindir la SOW y reembolsar las tarifas prepagadas no utilizadas. - -_Descargo de responsabilidad del Servicio._ GitHub proporciona el Servicio **"TAL CUAL"** y **"SEGÚN ESTÉ DISPONIBLE"** sin garantía de ningún tipo. Sin perjuicio de esto, GitHub renuncia expresamente a todas las garantías, ya sean explícitas, implícitas o reglamentarias, respecto del Servicio incluidas entre otras cualquier garantía implícita de comercialización, idoneidad para un propósito en particular, título, seguridad, precisión y de no incumplimiento. GitHub no garantiza que los Servicios cumplan con los requisitos del Cliente; que los Servicios no se interrumpan y sean oportunos, seguros o sin errores; que la información que se provee a través de los Servicios sea precisa, confiable o correcta; que cualquier defecto o error será corregido; que el Servicio estará disponible en cualquier momento o ubicación en particular; o que el Servicio se encuentra libre de virus u otros componentes dañinos. GitHub no será responsable por cualquier riesgo de pérdida que resulte de la descarga del Cliente y/o el uso de archivos, información, Contenido u otro material obtenido del Servicio. - -_(iii) Descargo de Responsabilidad de Vista previa Beta._ El Cliente puede elegir utilizar la Vista previa Beta a su exclusivo criterio. Las Vistas previas Beta pueden no ser compatibles y pueden cambiarse en cualquier momento sin previo aviso. Las Vistas previas Beta pueden no ser tan confiables o no estar disponibles como el Servicio. Las Vistas previas Beta no están sujetas a las mismas medidas de seguridad y de auditoría a las que el Servicio se encuentra sujeto. GitHub no tendrá ninguna responsabilidad que surja de las Vistas previas Beta o que esté relacionado con ellas. **Usos de las Vistas previas Beta por parte del Cliente a su propio riesgo.** - -### N. Limitations of Liability -**_Daños indirectos_ En la medida máxima permitida por la ley aplicable, en ningún caso será responsable ante la otra parte o ante terceros por ningún daño indirecto, especial, incidental, punitivo o consecuente (incluyendo pérdidas de ganancias, ingresos, o datos) o por el coste de obtener productos sustitutos que surjan de o en conexión con este Acuerdo, sea cual fuere la causa, si dicha responsabilidad surge de cualquier reclamación basada en el contrato, garantía, agravio (incluyendo negligencia), responsabilidad estricta o de otra forma y si una parte ha sido advertida o no de la posibilidad de dichos daños.** - -**_Restricción de la responsabilidad total._ En la medida máxima permitida por la ley aplicable, en ningún caso la responsabilidad acumulada total de ninguna de las partes en virtud de este Acuerdo por todas las causas de acción y todas las teorías de responsabilidad excederán las Tarifas que el Cliente ha pagado a GitHub durante los 12 meses anteriores a la reclamación que da lugar a dicha responsabilidad. Para los productos y los servicios (incluido el uso de los Productos) que se brindan gratis, la responsabilidad de GitHub se limita a los daños directos por hasta USD⁰5000,00. Para las Vistas previas Beta, la responsabilidad de GitHub se limita a los daños directos por hasta USD⁰500,00.** - -**_Exclusiones._ Las exclusiones y limitaciones expuestas en esta Sección N no se aplicarán a la responsabilidad derivada de (1) la violación por parte de una Parte de sus obligaciones de confidencialidad en la Sección P (excepto toda responsabilidad relacionada con el Contenido (excluyendo el contenido de GitHub), que permanecerán sujetas a las limitaciones y exclusiones anteriores) o (2) las obligaciones de defensa de una Parte en la Sección O.** - -### O. Defensa de demandas; Liberación - -Las Partes se defenderán mutuamente contra las demandas de terceros, hasta el punto que se establece en la presente Sección O y pagarán la cantidad correspondiente de cualquier sentencia firme adversa resultante o convenio aprobado, solamente si se notifica de inmediato a la Parte demandada por escrito sobre la reclamación y tiene el derecho de controlar la defensa y cualquiera de sus convenios. La Parte defendida debe proveer a la Parte demandada toda la asistencia, la información y la autoridad que se solicita. La Parte demandada reembolsará a la otra Parte por los gastos de bolsillo razonables en que incurra al proveer asistencia y no resolverá ni hará ninguna admisión con respecto a un reclamo de terceros sin previo consentimiento escrito de la otra Parte, sin que sea indebidamente demorado o retenido. La presente Sección O describe los únicos recursos de las Partes y la responsabilidad total para dichas demandas. - -#### 1. Por GitHub -GitHub defenderá al Cliente contra cualquier demanda presentada por un tercero sin afiliación en la medida en que alegue que el uso autorizado del Servicio o el Software por parte del Cliente infringe un derecho de propiedad, una patente o un nombre comercial, o que malversa un secreto comercial de un tercero sin afiliación. Si GitHub no puede resolver alguna de dichas demandas en términos comercialmente razonables, puede, según su criterio: (a) modificar, reparar o reemplazar el Servicio (si corresponde); o (b) poner fin a la suscripción del Cliente y reembolsar cualquier tarifa de suscripción pagada anticipadamente sin usar. GitHub no tendrá ninguna obligación conforme a lo dispuesto en la presente Sección O.1 por cualquier reclamación que surja de las siguientes situaciones: i) la modificación del Servicio; o la combinación, la operación o el uso del Servicio con equipos, dispositivos, software, sistemas o datos que no sean los expresamente autorizados por este Acuerdo (incluyendo la Documentación); (ii) el incumplimiento por parte del Cliente de dejar de usar el Servicio después de recibir la correspondiente notificación; (iii) las obligaciones del Cliente según lo dispuesto por la Sección O.2; (iv) los productos o servicios (incluyendo el uso del Servicio) que GitHub proporciona en forma gratuita; o (v) el acceso o uso de las Vistas previas Beta. Para los fines de la obligación de GitHub conforme a lo dispuesto en la presente Sección O.1,. el Servicio incluye componentes de código abierto que GitHub ha incorporado al mismo. - -#### 2. Por el Cliente -El cliente defenderá a GitHub contra cualquier demanda presentada por un tercero no afiliado que surja de: (i) el Contenido del Cliente que carga al Servicio; (ii) la violación por parte del Cliente de este Contrato, incluyendo la violación de la confidencialidad o violación de la Sección C; o (ii) cualquier equipo de marca de terceros, dispositivos, software, sistemas o datos que el Cliente combine, opere o utilice con el Servicio. - -#### 3. Disputas con otros usuarios -Si el Cliente tiene una disputa con uno o más Usuarios, el Cliente libera a GitHub de todos los reclamos, demandas y dañoss (reales y consecuentes) de todo tipo y naturaleza, conocidos y desconocidos, que surjan de o que estén relacionados de alguna forma con dichas disputas. - -### P. Confidentiality -Ninguna de las Partes utilizará la Información confidencial de la otra Parte, excepto de acuerdo con lo permitido en el presente Acuerdo. Cada una de las Partes acepta mantener de forma confidencial y proteger la Información confidencial de la otra Parte utilizando al menos el mismo grado de cuidado con el que protege la información propia de la misma naturaleza, pero en cualquier caso al menos a niveles razonables de cuidado. Cada una de las Partes acepta tomar todas las precauciones razonables para evitar cualquier divulgación no autorizada de la Información confidencial de la otra Parte, incluyendo, entre otras, las divulgaciones de dicha Información confidencial solamente a sus Representantes, quienes (i) necesiten conocer dicha información, (ii) sean partes de acuerdos lo suficientemente adecuados como para cumplir con la presente Sección P y (iii) se encuentran informados sobre las restricciones del uso y la divulgación establecidas en la presente Sección P. Cada una de las Partes es responsable de todos los actos y omisiones de sus Representantes. Las obligaciones mencionadas no restringirán que ninguna de las Partes divulgue la Información Confidencial de la otra Parte en cumplimiento con una solicitud o exigencia de un juzgado, de una agencia administrativa o de otro organismo gubernamental, _siempre y cuando_ la Parte obligada a hacer dicha divulgación dé una notificación razonable a la otra Parte para habilitar a dicha Parte a objetar la orden o exigencia, excepto que la notificación esté prohibida por ley. Las restricciones establecidas en la presente Sección P continuarán en vigencia después de la terminación o caducidad del presente Acuerdo. - -### Q. Servicios profesionales -Al momento de la solicitud de Servicios profesionales por parte del Cliente, GitHub proporcionará una SOW detallando tales Servicios profesionales. GitHub realizará los Servicios profesionales que se describen en cada SOW. GitHub controlará la forma y los medios utilizados para llevar a cabo los Servicios profesionales y se reserva el derecho de determinar el personal asignado. GitHub puede utilizar a terceros para realizar los Servicios profesionales, siempre y cuando GitHub siga teniendo responsabilidad por sus actos y omisiones. El Cliente reconoce y acepta que GitHub conserva todos los derechos, títulos e intereses sobre cualquier cosa que se usa o se desarrolla en conexión con los Servicios profesionales, incluido el software, las herramientas, las especificaciones, las ideas, los conceptos, las invenciones, los procesos, las técnicas y las habilidades. En la medida en que GitHub entregue cualquier cosa al Cliente mientras realiza los Servicios Profesionales, GitHub otorga al Cliente una licencia no exclusiva, intransferible en todo el mundo, exenta de regalías, de plazo limitado para usar dichos entregables durante el término de este Contrato, únicamente en conjunción con el uso del Servicio por parte del Cliente. - -### R. Cambios al servicio o a los términos -GitHub se reserva el derecho, a su exclusivo criterio, de modificar el presente Acuerdo en cualquier momento y actualizará este Acuerdo en el caso en que ocurran dichas modificaciones. GitHub notificará al Cliente sobre los cambios sustanciales al presente Acuerdo, tales como cambios en los precios, al menos 30 días antes de que el cambio entre en vigencia publicando un aviso en el Servicio. Para modificaciones no sustanciales, el uso continuo del Servicio por parte del Cliente representa la aceptación de nuestras revisiones sobre el presente Acuerdo. El Cliente puede visualizar todas las modificaciones al presente Acuerdo en nuestro repositorio [Site Policy](https://github.com/github/site-policy). - -GitHub cambia el Servicio mediante Actualizaciones y adición de nuevas características. Sin perjuicio de lo anterior, GitHub se reserva el derecho de modificar o interrumpir en cualquier momento temporal o permanentemente el Servicio (o cualquier parte del mismo) con o sin previo aviso. - -### S. Asistencia -GitHub proporcionará Soporte técnico estándar para el Servicios sin ningún cargo adicional veinticuatro (24) horas al día, cinco (5) días a la semana, excluyendo los fines de semana y los días feriados nacionales de los Estados Unidos. holidays. El Soporte estándar solo se ofrece por medio de tickets basados en la web a través del Soporte de GitHub y las solicitudes de Soporte deben ser iniciadas por un Usuario con el que el equipo de Soporte de GitHub pueda interactuar. GitHub puede proporcionar Soporte premium (sujeto a los términos [de GitHub Premium para Enterprise Cloud](/articles/about-github-premium-support)) o Soporte técnico dedicado para el Servicio en el nivel de Soporte, Tarifas y Términos de Suscripción especificados en un Formulario de Pedido o SOW. - -### T. Varios - -#### 1. Legislación aplicable -Si la sede principal del cliente se encuentra en el Continente Americano, el presente Acuerdo se regirá por las leyes del estado de California y se interpretará de acuerdo a ellas sin dar efecto a los principios de conflicto de leyes, cualquier procedimiento o acción legal que surja del presente Acuerdo se presentará exclusivamente ante las cortes federales o estatales ubicadas en el Distrito Norte de California, y por el presente las Partes convienen competencia y jurisdicción personal de dichos tribunales. Si la sede principal del Cliente se encuentra fuera de América, el presente Acuerdo se regirá por las leyes de Irlanda, cualquier procedimiento o acción legal que surja del presente Acuerdo se presentará exclusivamente ante las cortes ubicadas en Dublín, y por el presente las Partes convienen competencia y jurisdicción personal de dichos tribunales. Las partes acuerdan expresamente que no se aplicarán a este Acuerdo la Convención de las Naciones Unidas sobre Contratos de Compraventa Internacional de Bienes y la Ley Uniforme de Transacciones Electrónicas. Sin perjuicio de cualquier disposición contraria anterior, GitHub puede presentar una reclamación para obtener una compensación equitativa en cualquier corte de jurisdicción competente. - -#### 2. Comentarios -El Cliente puede proporcionar Retroalimentación a GitHub con respecto a los Productos. La retroalimentación es voluntaria y no es Información Confidencial del Cliente, incluso si se designa como tal. GitHub puede ejercer y explotar plenamente dicha Retroalimentación con el propósito de (i) mejorar la operación, funcionalidad y uso de las ofertas de productos existentes y futuras de GitHub; y (ii) publicación de estadísticas agregadas sobre la calidad de los Productos, siempre que no se utilicen datos en ninguna de estas publicaciones para identificar específicamente al Cliente, sus empleados o el código de software propietario del Cliente. - -#### 3. Intransferible -Ninguna de las Partes puede asignar o de otro modo transferir el presente Acuerdo, ni total ni parcialmente, sin previo consentimiento escrito de la otra Parte, dicho consentimiento no será retenido injustificadamente y cualquier intento de hacerlo será nulo y sin efecto, salvo que GitHub pueda asignar el presente Acuerdo en su totalidad, previa notificación a la otra parte pero sin el consentimiento de la otra Parte, en conexión con una fusión, adquisición, reorganización corporativa o venta de todos o casi todos los negocios o activos de la parte que asigna. - -#### 4. Waiver -Se puede renunciar a las obligaciones de una de las Partes según lo dispuesto en el presente Acuerdo solamente por escrito con la firma de un representante autorizado de la otra Parte. Ninguna demora o falta de una de las Partes en relación a este Acuerdo en el ejercicio de algún derecho según este documento obrará como renuncia a dicho derecho, y el ejercicio único o parcial de estos derechos no imposibilitará otro ejercicio al respecto o el ejercicio de cualquier derecho según este documento por ley o normas de equidad. - -#### 5. Severability -Si una corte de jurisdicción competente considera que alguna disposición del presente Acuerdo es ilegal, nula o inaplicable, las Partes modificarán o reformarán el presente Acuerdo para darle el mayor efecto posible a esa disposición. Cualquier disposición que no se pueda modificar o reformar de esta forma se considerará eliminada y las provisiones restantes del presente Acuerdo continuarán en pleno vigor y efecto. - -#### 6. Enmiendas; Contrato Completo; Orden de Precedencia -Este Acuerdo solo se puede modificar por una enmienda por escrito firmada por un representante autorizado de GitHub, o por GitHub publicando una versión revisada de acuerdo con la Sección T. Este Acuerdo representa el acuerdo completo y exclusivo entre las Partes. Este Acuerdo sustituye cualquier propuesta o acuerdo previo oral o escrito y cualquier otra comunicación entre las Partes relacionadas con el tema de estos términos, incluyendo cualquier acuerdo de confidencialidad o no divulgación. En el caso en que exista algún conflicto entre los términos del presente Acuerdo y cualquier Formulario de pedidos o SOW, los términos del Formulario de pedidos o SOW prevalecerán solamente con respecto a ese Formulario de pedidos o SOW. - -#### 7. Publicidad -Si el cliente muestra públicamente el nombre de su empresa u organización en su cuenta o si de otro modo muestra públicamente sus marcas o logotipos en su página de perfil, el Cliente permite a GitHub utilizar el nombre de su empresa u organización para identificar al Cliente como un cliente de GitHub en materiales promocionales. El cliente puede revocar este permiso ocultando el nombre de su empresa u organización de la exhibición pública y notificando a GitHub por escrito para dejar de usar el nombre de su organización en materiales promocionales. Sin embargo, GitHub no tendrá ninguna obligación de eliminar o recuperar ningún uso o distribución previa de los materiales promocionales. - -#### 8. Force Majeure -GitHub será excusado de la responsabilidad hasta el punto en que sea incapaz de ejecutar cualquier obligación conforme a lo dispuesto en el presente Acuerdo debido a causas extraordinarias más allá de su control razonable, incluidos los hechos fortuitos, los desastres naturales, las huelgas, los disturbios, los bloqueos, los actos de guerra, las epidemias, o las fallas eléctricas, en las telecomunicaciones o en las redes. - -#### 9. Contratistas independientes -Cada una de las Partes es un contratista independiente con respecto al objeto del presente Acuerdo. Nada de lo dispuesto en el presente Acuerdo será considerado o interpretado de forma tal que dé lugar a la creación de una asociación legal, sociedad, empresa mixta, empleo, agencia, fiduciaria u otra relación similar entre las Partes, y ninguna de las Partes puede vincular a la otra por contrato. - -#### 10. Preguntas -¿Preguntas sobre los Términos de Servicio? [Contáctanos](https://github.com/contact/). diff --git a/translations/es-XL/content/github/site-policy/github-data-protection-addendum.md b/translations/es-XL/content/github/site-policy/github-data-protection-addendum.md deleted file mode 100644 index babcb157db..0000000000 --- a/translations/es-XL/content/github/site-policy/github-data-protection-addendum.md +++ /dev/null @@ -1,420 +0,0 @@ ---- -title: Adenda de protección de datos de GitHub -versions: - free-pro-team: '*' ---- - -Fecha de entrada en vigencia de la versión: 20 de julio de 2020 - -## INTRODUCCIÓN - -Las partes acuerdan que la Protección de Datos de GitHub y la Evidencia de Seguridad (en conjunto, la **Adenda de Protección de Datos"** o **"DPA"**) enuncia sus obligaciones con respecto al procesamiento y seguridad de los Datos Personales del Cliente en conexión con el servicio hospedado de GitHub Enterprise Cloud (el **"Servicio"**). En esta DPA, GitHub se compromete con todos los clientes que utilicen el Servicio. Las condiciones separadas, incluyendo aquellas condiciones diferentes de privacidad y seguridad, rigen el uso de los clientes para los productos diferentes a los de GitHub. - -En caso de que exista cualquier conflicto o inconsistencia entre la DPA y cualquier otra condición en el acuerdo del cliente con Github, la DPA deberá prevalecer. Las disposiciones de la DPA sustituyen cualquier disposición que entre en conflicto con la Declaración de Privacidad de GitHub que pudiera aplicarse de otra forma al procesamiento de los Datos Personales del Cliente como se define en el presente documento. Para mayor claridad, en apego a la Cláusula 10 de las Cláusulas Contractuales Estándar en el Adjunto 1, las Cláusulas Contractuales Estándar prevalecerán sobre cualquier otra condición en la DPA. - - -## PROTECCIÓN DE DATOS DE GITHUB - -### 1. Definiciones. - -1.1 Las "**Leyes de Protección de Datos Aplicables**" se refiere a ciertas leyes, regulaciones, marcos de trabajo regulatorios, u otras legislaciones que se relacionen con el procesamiento y el uso de los Datos Personales del Cliente, de acuerdo a lo aplicable con el uso de GitHub por parte del cliente y del Servicio de GitHub, incluyendo: - - a. El reglamento general de protección de datos 2016/679 de la UE (**RGPD**), junto con cualquier legislación o reglamentación nacional equivalente que sea de aplicación o correspondiente, una vez que se aplique o sea aplicable; y - - b. La Ley de Privacidad de los Consumidores de California de 2018, Cal. Civ. Code §§1798.100 et seq. (**"CCPA"**); y - - c. La Ley de Protección de Datos del Reino Unido de 2018 y la implementación de RGDP que se contiene en la misma. - -1,2 Las palabras "**Controlador**", "**Titular de los datos**", "**Estado miembro**", "**Datos Personales**", "**Violación a los Datos Personales**, "**Procesamiento**", "**Procesador**", y "**Autoridad de Supervisión**" tienen los significados que se les otorguen en las Leyes de Protección de Datos Aplicables. En el caso de un conflicto, prevalecerán los significados que se les atribuyen en el RGPD. - -1.3 "**Datos personales del Cliente**" se refiere a cualquier Dato personal del cual el Cliente sea Controlador, ya sea suministrado por el Cliente para el procesamiento de GitHub o generado por GitHub durante la realización de sus obligaciones conforme al Acuerdo. Incluye datos como información de la facturación, direcciones IP, direcciones de correo electrónico corporativas y cualquier otro Dato personal del cual el Cliente sea Controlador. - -1.4 "**Datos del Repositorio del Cliente**" se refiere a cualquier dato o información que el Cliente carga o crea en cualquiera de sus Repositorios privados. - -1.5 A "**Violación de datos**" se refiere a una violación de datos personales o cualquier otro incumplimiento confirmado o razonablemente sospechado de los datos protegidos del cliente. - -1.6 "**Usuario final**" se refiere a un Sujeto de datos individual que controla una cuenta de GitHub y aceptó los Términos de servicio de GitHub, y cuyos datos personales están siendo transferidos, almacenados o procesados por GitHub. Por ejemplo, cada empleado o contratista del Cliente que tiene una cuenta de GitHub también es un Usuario final de GitHub. - -1.7 "**Fines permitidos**" para el procesamiento de datos son aquellos fines limitados y específicos de prestación del Servicio según se establece en el Acuerdo, en la Declaración de privacidad de GitHub y en el presente Apéndice A, o los fines para los cuales un Sujeto de datos autorizó el uso de los Datos personales del Cliente. - -1.8 "**Datos protegidos**" incluye cualquier Dato personal del Cliente y cualquier Dato del Repositorio del Cliente procesado por GitHub en nombre del Cliente, según lo dispuesto en el Acuerdo. - -1.9 "**Datos Sensibles**" Significa cualquier tipo de dato personal que revele el origen racial o étnico; las opiniones políticas, las creencias religiosas o filosóficas o afiliaciones a sindicatos; procesamiento de datos genéticos o biométricos para propósitos únicos de identificación de una persona natural; datos pertinentes a la salud, la vida sexual de una persona natural o la orientación sexual de la misma; y los datos pertinentes a las ofensas, convicciones criminales o medidas de seguridad. - -### 2. Estado y cumplimiento. - -#### 2.1 Procesamiento de Datos. -GitHub actúa como un Procesador con respecto a los Datos Personales de los clientes que recibe en conexión con el Acuerdo, y GitHub procesará los Datos Personales del Cliente únicamente para los propósitos permitidos de acuerdo con las instrucciones del Cliente de acuerdo a como se representa en el Acuerdo y en otros comunicados por escrito. En el caso de que GitHub no pueda cumplir con las indicaciones del Cliente, por ejemplo, debido a conflictos con las Leyes aplicables de Protección de datos, o cuando las Leyes aplicables de Protección de datos u otros requisitos legales requieren el procesamiento, GitHub notificará al Cliente en la medida de lo permitido. GitHub procesa todos los Datos personales del Cliente en los Estados Unidos o en la Unión Europea; sin embargo, los subprocesadores de GitHub pueden procesar datos fuera de los Estados Unidos o la Unión Europea. Además, GitHub actúa como Procesador para cualquier Dato del Repositorio del Cliente. - -#### 2.2 Controladores de Datos. -GitHub recibe Datos Personales de los Clientes tanto del Cliente como directamente de los Titulares de los Datos que crean cuentas de Usuario Final. El Cliente es Controlador únicamente de los Datos personales del Cliente que transfiere directamente a GitHub. - -#### 2.3 Cumplimiento de GitHub; Transferencias de Datos. -GitHub cumplirá con las Leyes Aplicables de Protección de Datosen relación con el procesamiento de los Datos Personales del Cliente. - -Todas las transferencias de Datos Personales del Cliente fuera de la Unión Europea, el Área Económica Europea, el Reino Unido y Suiza par aproporcionar el Servicio se regirán por las Cláusulas Contractuales Estándar en el Adjunto 1 (Cláusulas Contractuales Estándar). GitHub cumplirá con los requerimientos del Área Económica Europea y la ley de protección de datos suiza de acuerdo con la recolección, uso, transferencia, retención y otros tipos de procesamiento de Datos Personales de los Clientes desde el Área Económica Europea, el Reino Unido y Suiza. Todas las transferencias de Datos Personales del Cliente a un país tercero o a una organización internacional estarán sujetos a la salvaguarda adecuada de acuerdo a lo descrito en el artículo 46 del RGPD y dichas transferencias y salvaguardas se documentarán de acuerdo con el artículo 30(2) del RGPD. - -Adicionalmente, GitHub está certificado en el Marco del Escudo de Privacidad de U.E. - E.U.A. y de Suiza - E.U.A. 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 acuerda notificar al cliente si hace una determinación de que ya no puede cumplir con su obligación de proporcional el mismo nivel de protección de acuerdo a como se requiere con los principios del Escudo de Privacidad. - - -### 3. Protección de datos. - -#### 3.1 Limitación de propósitos. -GitHub procesará y comunicará los Datos Protegidos únicmente para los Propósitos Permitidos, a menos de que las partes convengan por escrito un propósito ampliado. - -#### 3.2 Calidad y Proporcionalidad de los Datos. -GitHub mantendrá los Datos Personales del Cliente actualizados y exactos, o habilitará al cliente para que lo haga. GitHub seguirá los pasos comercialmente razonables para asegurar que cualquier Dato protegido que recopile en nombre del Cliente sea adecuado, relevante y no excesivo en relación con los fines para los cuales se transfiere y se procesa. En ningún caso GitHub recopilará intencionalmente Datos confidenciales en nombre del Cliente. El Cliente acepta que el Servicio de GitHub no está destinado al almacenamiento de Datos confidenciales. Si el Cliente decide cargar Datos confidenciales en el Servicio, el Cliente debe cumplir con el Artículo 9 del GDPR, o las disposiciones equivalentes de las Leyes aplicables de Protección de datos. - -#### 3.3 Retención y Eliminación de Datos. -Bajo la solicitud razonable del cliente, a menos de que se prohiba por ley, GitHub devolverá, destruirá o desidentificará todos los Datos Personales del Cliente y los datos relacionados en todas las ubicaciones donde se almacenen después de que dejen de requerirse para los Propósitos Permitidos dentro de treinta días de la solicitud. GitHub puede conservar los Datos personales del Cliente y los datos relacionados en la medida que lo exijan las Leyes aplicables de Protección de datos y solo en la medida y por el período que estas lo requieran, siempre que GitHub asegure que los Datos personales del Cliente se procesarán solo si se necesitan para el fin especificado en las Leyes aplicables de Protección de datos y sin ningún otro fin, y los Datos personales del Cliente segruirán protegidos por las Leyes aplicables de Protección de datos. - -#### 3.4 Procesamiento de Datos. -GitHub proporciona la siguiente información, requerida por el Artículo 28(3) del RGPD, con respecto a su procesamiento de los Datos protegidos del Cliente: - -a. *El motivo y la duración del procesamiento* de los Datos personales del Cliente están establecidos en el Acuerdo y en el presente Anexo. - -b. *La naturaleza y el fin del procesamiento* de los Datos personales del Cliente se describen en la Sección 3.1 del presente Anexo. - -c. *Los tipos de Datos personales del Cliente que se procesarán* se describen en la Declaración de privacidad de GitHub e incluyen Datos personales del Cliente, tales como nombres de usuario, contraseñas, direcciones de correo electrónico y direcciones IP. GitHub también procesa la información necesaria para la facturación de la cuenta del Cliente, pero no procesa ni almacena información sobre tarjetas de crédito. El Cliente puede elegir suministrarle a GitHub Datos personales del Cliente, por ejemplo, en los parámetros del perfil del Cliente o al cargar Datos personales del Cliente en sus repositorios de GitHub. - -d. *Las categorías del Sujeto de datos con quien se relacionan los Datos personales del Cliente* son el propio Cliente y sus Usuarios finales. - -e. *Las obligaciones y los derechos del Cliente* están establecidos en el Acuerdo y en el presente Anexo. - -### 4. Seguridad y obligaciones de auditoría. - -#### 4.1 Medidas de Seguridad Técnicas y Organizacionales. -Tomando en cuenta las tecnologías más actuales, los costos de implementación, y la naturaleza, alcance, contexto y propósito de procesamiento, así como el riesgo de variar la probabilidad y severidad de los derechos y libertades de las personas naturales, GitHub implementará medidas técnicas y organizacionales adecuadas para garantizar un nivel de seguridad adecuado para los riesgos, tales como aquellas contra la destrucción accidental o ilegal, o contra la pérdida, alteración, o contra el acceso o divulgación no autorizados que se presenten debido al Procesamiento de los Datos. GitHub supervisará regularmente el cumplimiento de estas medidas y continuará tomando las debidas salvaguardias durante la vigencia del Acuerdo. Consulte la Sección 1.1 del Apéndice de Seguridad de GitHub respecto de las responsabilidades de GitHub en relación con las salvaguardias de seguridad. - -#### 4.2 Respuesta a Incidentes y Notificación de Filtración. -GitHub cumplirá con las obligaciones de Seguridad de la Información que se encuentran en las Pruebas de Seguridad de GitHub y en las Leyes de Protección de Datos, incluyendo las obligaciones de notificación para la Filtración de Datos. Consulte la Sección 1.2 del Apéndice de Seguridad de GitHub sobre las responsabilidades de GitHub en relación con la respuesta y notificación del Incumplimiento de datos. - -#### 4.3 Personal de GitHub. -GitHub representa y garantiza que tomará los pasos razonables para asegurarse de que todo su personal que maneje Datos Protegidos haya acordado mantener dichos datos como confidenciales y haya recibido capacitación adecuada para cumplir con esta Adenda y con las Leyes de Protección de Datos Aplicables. - -#### 4.4 Registros. -GitHub mantendrá los registros por escrito completos, precisos y actualizados para todas las categorías de las actividades de procesamiento que se lleven a cabo en nombre de un Cliente, las cuales contengan la información que se requiere por las Leyes de Protección de Datos Aplicables. En la medida que la asistencia no ponga en riesgo la seguridad de GitHub o los derechos de privacidad de Sujetos de datos individuales, GitHub pondrá a disposición del Cliente estos registros a su solicitud cuando se requieran de manera razonable, por ejemplo, para ayudar al Cliente a demostrar su cumplimiento según lo dispuesto en las Leyes aplicables de Protección de datos. Para conocer más sobre los requisitos de GitHub para proporcionar asistencia en caso de un incidente de seguridad, consulta la Sección 1.2 del Apéndice de Seguridad de GitHub. - -#### 4.5 Reporte de Cumplimiento. -GitHub proporcionará reportes de cumplimiento en seguridad de acuerdo con la sección 2.3 de la Prueba de Seguridad de Github y también los reportes de cumplimiento de privacidad de acuerdo con la misma sección. El Cliente acepta que cualquier información y derechos de auditoría concedidos por las Leyes aplicables de Protección de datos (incluido, cuando corresponda, el Artículo 28(3)(h) del GDPR) se cubrirán con estos informes de cumplimiento y solo se presentarán en la medida que la generación de un informe de cumplimiento por parte de GitHub no brinde suficiente información o en la medida que el Cliente deba responder a una auditoría de la Autoridad de supervisión o reglamentaria. La Sección 3.1 del Apéndice de Seguridad de GitHub describe las responsabilidades de las Partes en relación con una auditoría de la Autoridad de supervisión o reglamentaria. - -#### 4.6 Asistencia. -GitHub proporcionará asistencia considerable a los Clientes con preocupaciones tales como la valoración de impacto de la privacidad de los datos, solicitudes de derechos de los Titulares de los Datos, consultas con las Autoridades Supervisantes, y otros asuntes similares, en cada caso, únicamente para el procesamiento de los Datos Personales del cliente y tomando en cuenta la naturaleza del procesamiento. - -### 5. Uso y divulgación de Datos protegidos. - -#### 5.1 Si Uso para Marketing. -GitHub no utilizará los Datos Protegidos para propósitos de anunciar el contenido de terceros, y no venderá los Datos Protegidos a ningún tercero, excepto como parte de una adquisición o fusión. - -#### 5.2 Declaración de Privacidad de GitHub. -La Declaración de Privacidad de GitHub, la cual está disponible al público en [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), proporciona notificaciones detalladas de las prácticas de uso de datos y de privacidad de GitHub, incluyendo su uso de cookies, su proceso de resolución de disputas, y más detalles sobre el cumplimiento con el RGPD. - -### 6. Subprocesamiento y transferencia ulterior. - -#### 6.1 Protección de los Datos. -GitHub es responsable de las transferencias subsecuentes de los Datos Protegidos a sus subprocesadores, tales como su procesador de pagos tercero. En caso de que GitHub sí transfiera los Datos Protegidos a un subprocesador tercero, o que GitHub instale, use o habilite a un tercero o a un servicio de un tercero para procesar los Datos Protegidos en nombre de GitHub, github garantizará que dicho subprocesador tercero esté vinculado por un contrato escrito que le requiera proporcionar por lo menos el mismo nivel de confidencialidad, seguridad y protección de privacidad de acuerdo a como lo requiere GitHub en esta DPA y conforme a las Leyes de Protección de Datos Aplicables. - -#### 6.2 Aceptación de los Subprocesadores de GitHub. -El cliente autoriza a GitHub para designar (y permitir a cada subprocesador designado de acuerdo con la sección 6 el designar) subprocesadores de acuerdo con la sección 6 y con cualquier otra restricción en el Acuerdo. GitHub puede seguir usando los subprocesadores a los que actualmente recurre a partir de la Fecha de entrada en vigor del presente Anexo. - -#### 6.3 Consentimiento General para el Subprocesamiento Posterior. -El cliente proporciona un consentimiento general para que GitHub incluya subprocesadores posteriores, condicionalmente con el cumplimiento de GitHub con los siguientes requisitos: - -a. Cualquier suprocesador posterior deberá acordar por escrito solo procesar los datos en un país en el que la Comisión Europea haya declarado tener un nivel de protección "adecuado"; o el procesar solo datos en condiciones equivalentes a las Cláusulas Contractuales Estándar, o conforme a una aprobación de Reglas Corporativas de Vinculación que otorgue una autoridad de protección de datos europea competente, o conforme a las certificaciones de Escudo de Privacidad de UE-EUA y Suiza-E.U.A válids. ; y - -b. GitHub restringirá el acceso de los subprocesadores ulteriores a los Datos personales del Cliente solo a lo que resulte estrictamente necesario para prestar sus servicios, y GitHub le prohibirá al subprocesador procesar los Datos personales del Cliente para cualquier otro fin. - -#### 6.4 Divulgación de los Acuerdos de los Subprocesadores. -GitHub mantiene una lista de subprocesadores posteriores que ha contactado para procesar los Datos Personales de los Clientes en [https://docs.github.com/articles/github-subprocessors-and-cookies](/articles/github-subprocessors-and-cookies), incluyendo las categorías de Datos Personales de Clientes que se han procesado, una descripción del tipo de procesamiento que realiza el subprocesador, y la ubicación de su procesamiento. GitHub proporcionará al Cliente, previa solicitud escrita, la lista de subprocesadores y los términos según los cuales procesan los Datos personales del Cliente. Conforme a las restricciones de confidencialidad del subprocesador, GitHub puede eliminar cualquier información confidencial o comercialmente sensible antes de proporcionarle la lista y los términos al Cliente. En el caso de que GitHub no le pueda divulgar información confidencial o sensible al Cliente, las Partes acuerdan que GitHub proporcionará toda la información que razonablemente pueda en conexión con sus acuerdos de subprocesamiento. - -#### 6.5 Objeción a los Subprocesadores. -GitHub proporcionará treinta (30) días de notificación previa por escrito sobre la adición o eliminación de cualquier subprocesador, incluyendo a los de las categorías listadas en la sección 6.4, mediante el anuncio de los cambios en su sitio de . Si el Cliente tiene una objeción razonable sobre la incorporación de un nuevo subprocesador por parte de GitHub, el Cliente se lo debe notificar de inmediato por escrito a GitHub. En lo posible, GitHub hará los esfuerzos comercialmente razonables para proporcionar una solución alternativa al Servicio afectado para evitar el procesamiento de los datos por parte del subprocesador objetable. En el caso de que GitHub no pueda proporcionar una solución alternativa, y las Partes no puedan resolver el conflicto dentro de los noventa días, el Cliente puede poner fin al Acuerdo. - -### 7. Terminación. - -#### 7.1 Suspensión. -En caso de que GitHub se encuentre en una violación de sus obligaciones para mantener un niel adecuado de seguridad o protección de la privacidad, el cliente deberá suspender temporalmente la transferencia de todos los Datos Personales del mismo o prohibir la recolección y procesamiento de estos en nombre del cliente hasta que la violación se repare o hasta que finalice el contrato. - -#### 7.2 Terminación con Causa. -Adicionalmente a cualquier derecho de terminación que tenga el clinte bajo el contrato, dicho cliente puede terminar el contrato sin afectación a ningún otro reclamo en derecho o equidad en caso de que: - -a. GitHub notifica al Cliente que ya no puede cumplir con sus obligaciones de privacidad; - -b. la transferencia, recopilación o procesamiento de todos los Datos personales del Cliente ha sido suspendida de forma temporal por más de un mes en virtud de la Sección 7.1; - -c. GitHub se encuentra en incumplimiento sustancial o persistente de cualquiera de las garantías o manifestaciones según lo dispuesto en el presente Anexo; - -d. GitHub no continúa con su actividad, se disuelve, entra en quiebra o se hace una orden de liquidación a nombre de GitHub; - -e. El Cliente objeta al subprocesador conforme a la Sección 6.5, y GitHub no ha podido proporcionar una solución alternativa dentro de los noventa días. - -#### 7.3 Violación. -El incumplimiento con los aprovisionamientos materiales de esta adenda se considera una violación material bajo el acuerdo. - -#### 7.4 Incapacidad de realización. -En caso de que los cambios a la ley o a las regulaciones se traduzcan en la imposibilidad de hacer valer esta adenda o que el hacerlo sea comercialmente irracional, las partes podrán volver a negociar la adenda de buena fe. Si la renegociación no soluciona la imposibilidad, o si las Partes no pueden llegar a un acuerdo, las Partes pueden terminar el Acuerdo luego de treinta días. - -#### 7.5 Notificación. -En caso de que GitHub determine que ya no puede cumplir con sus obligaciones de privacidad conforme a esta adenda, Github notificará al cliente inmediatamente por escrito. - -#### 7.6 Modificaciones. -GitHub podrá modificar esta adenda de vez en cuando de acuerdo a los requisitos de las Leyes de Protección de Datos Aplicables emitiendo una notificación al Cliente treinta días antes de hacerlo. - -#### 7.7 Requisitos de la Terminación. -Al momento de la Terminación, GitHub Deberá: - -a. tomar las medidas razonables y adecuadas para detener el procesamiento de los Datos personales del Cliente; - -b. dentro de los noventa días posteriores a la terminación, eliminar o anonimizar cualquier Dato personal del Cliente que GitHub almacena en nombre del Cliente en virtud de la Sección 3.3; - -c. proporcionar al Cliente la certeza razonable de que GitHub ha cumplido con sus obligaciones de la Sección 7.7. - -### 8. Responsabilidad por el procesamiento de datos. - -#### 8.1 Limitaciones. -Salvo a las limitaciones que proporcionan las Leyes de Protección de Datos Aplicables, cualquier reclamo que se suscite bajo esta adenda estará sujeto a las condiciones del acuerdo con respecto a las Limitaciiones de Responsabilidades. - -## Adjunto 1 – Las Cláusulas Contractuales Estándar (Procesadores) -La ejecución del presente acuerdo a manes del cliente incluye la ejecución de este Adjunto 1 a la Adenda de Protección de Datos de Github, la cual refrenda 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. - -Para propósitos del artículo 46(2) de la Regulación General de Protección de Datos (EU 2016/679) para la transferencia de datos personales a los procesadores establecidos en países terceros que no garantizan un nivel adecuado de protección de datos, el Cliente (como exportador de datos) y GitHub (como importador de datos, cuya firma aparece debajo), siendo cada uno de ellos una "parte", y en conjunto "las partes", acuerdan cumplir con las siguientes Cláusulas Contractuales (las "Cláusulas" o las "Cláusulas Contractuales Estándar") para citar los salvaguardos adecuados con respecto a la protección de la privacidad y de los derechos y libertades fundamentales de los individuos para la transferencia por parte del exportador de datos al importador de datos que manejará los datos personales especificados en el Apéndice 1. - -#### Cláusula 1: Definiciones -(a) los términos 'datos personales', 'categorías especiales de datos, 'proceso/procesamiento', 'controlador', 'procesador', 'titular de los datos' y 'autoridad supervisora' tendrán el mismo significado que en la Regulación General de Protección de Datos (EU 2016/679) sobre la protección de los individuos con respecto al procesamiento de los datos personales y sobre el movimiento libre de dichos datos; - -(b) 'el exportador de datos' se refiere al controlador que transifere los datos personales; - -(c) 'el importador de datos' se refiere al procesador que acuerda recibir datos personales del exportador, los cuales se pretenden procesar en su nombre después de la transferencia, de acuerdo con sus instrucciones y los términos de las Cláusulas y quien no está sujeto a un sistema de país tercero que garantice la protección adecuada dentro de las disposiciones del artículo 45(2) de la Regulación General para la Protección de Datos (EU 2016/679); - -(d) 'el subprocesador' significa cualquier procesador contactado mediante el importador de datos o mediante cualquier otro subprocesador del importador de datos quien acuerde recibir del importador de datos o de cualquier otro subprocesador de dicho importador los datos personales exclusivos que se pretenden utilizar en actividades de procesamiento que se llevarán acabo en nombre del exportador de datos después de la transferencia de acuerdo con sus instrucciones, las condiciones de las Cláusulas y las de el subcontrato por escrito; - -(e) 'la ley de protección de datos aplicable' se refiere a la legislación que protege los derechos fundamentales y las libertades de los individuos y, particularmente, su derecho a la privacidad con respecto al procesamiento de los datos personales aplicables al controlador de datos en el Estado Miembro en el cual se establece el exportador de datos; - -(f) 'medidas de seguridad técnicas y organizacionales' se refiere a aquellas medidas que se enfocan en proteger los datos contra una pérdida accidental o una destrucción ilegal, alteraciones, diseminación no autorizada o acceso, particularmente donde el procesamiento involucre la transmisión de datos a través de una red, y contra todo el resto de formas ilegales de procesamiento. - -#### 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. 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. 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. 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. - -#### Cláusula 4: Las obligaciones del exportador de los datos -El exportador de los datos acuerda y garantiza: - -(a) que el procesamiento, incluyendo la transferencia misma de los datos personales, se ha estado llevando a cabo y se seguirá haciendo de acuerdo con las disposiciones generales de la ley de protección de datos aplicable (y, cuando sea aplicable, se ha notificado a las autoridades relevantes del Estado Miembro en donde se establece el exportador de los datos) y no viola las disposiciones generales relevantes de dicho estado; - -(b) que se ha instruido y, a través de la duración de los servicios de procesamiento de datos personales, se instuirá al importador de los datos para procesar los datos personales transferidos únicamente en nombre del exportador de los datos de acuerdo con la ley de protección de datos personales y con las Cláusulas; - -(c) Que el importador de los datos proporcionará garantía suficiente con respecto a las medidas de seguridad técnicas y organizacionales especificadas en el Apéndice 2 descrito posteriormente; - -(d) que después de la valoración de los requisitos para la ley de protección de datos aplicable, las medidas de seguridad son adecuadas para proteger los datos personales contra la destrucción accidental o ilegal o contra la pérdida, alteración, divulgación no autorizada o acceso accidentales, particularmente en donde el procesamiento involucre la transmisión de datos a través de una red, y contra cualquier otra forma ilegal de procesamiento, y que estas medidas garantizan un nivel de seguridad adecuado para los riesgos que se presentan mediante el procesamiento y por la naturaleza de los datos que se protegerán con respecto a las tecnologías más recientes y el costo de su implementación; - -(e) que garantizará el cumplimiento con las medidas de seguridad; - -(f) que, si la transferencia involucra categorías especiales de datos, se ha informado o se informará previamente al titular de los datos, o se hará tan pronto como sea posible posteriormente, sobre que la transferencia de sus datos puede realizarse a un país tercero que no proporciona protección adecuada dentro de las estipulaciones de la Regulación General para la Protección de los Datos (EU 2016/679); - -(g) reenviar cualquier notificación que se recibe de un importador de datos o de cualquier subprocesador de acuerdo con la Cláusula 5(b) y la Cláusula 8(3) a la autoridad supervisora de protección de datos si el exportador de los datos decide continuar con la transferencia o levantar la suspeción; - -(h) poner a disposición una copia de las Cláusulas para los titulares de los datos por solicitud, con la exepción del Apéndice 2, y un resúmen descriptivo de las medidas de seguridad, así como una copia de cualquier contrato para los servicios de subprocesamiento que se tiene que hacer de acuerdo con las Cláusulas, a menos de que las Cláusulas o el contrato contengan información comercial, en cuyo caso se podrá eliminar dicha información comercial; - -(i) que, en caso de subprocesamiento, la actividad de procesamiento se llevará a cabo de acuerdo con la Cláusula 11 mediante un subprocesador que proporcione por lo menos el mismo nivel de protección para los datos personales y para los derechos del titual de los datos como importador de los mismos bajo las Cláusulas; y - -(j) que garantizará el cumplimiento con la Cláusula 4(a) a la (j). - -#### Cláusula 5: Obligaciones del importador de los datos -El importador de los datos acuerda y garantiza: - -(a) procesar los datos personales únicamente en nombre del exportador de los datos y en cumplimiento con sus instrucciones y con las Cláusulas; si no puede proporcionar dicho cumplimiento por cualquier razón, acuerda informar de manera oportuna al exportador de los datos de dicha incapacidad, en cuyo caso, el exportador de los datos tendrá derecho a suspender al trasnferencia de los mismos o de terminar el contrato; - -(b) que no hay razón para creer que la legislación aplicable a ello les previene de completar las instrucciones recibidas del exportador de datos y sus obligaciones contractuales y que en caso de un cambio a dicha legislación, el cual probablemente tenga un efecto adverso sobre las garantías y obligaciones que proporcionan las Cláusulas, se notificará oportunamente sobre el cambio al exportador de los datos tan pronto sea de su conocimiento, en cuyo caso, el exportador de los datos tendrá derecho para suspender la transferencia de los mismos y/o de terminar el contrato; - -(c) que ha implementado las medidas de seguridad técnicas y organizacionales especificadas en el Apéndice 2 antes de procesar los datos personales transferidos; - -(d) que notificará oportunamente al exportador de los datos sobre: - -(i) cualquier solicitud legalmente vinculante para la divulgación de los datos personales mediante una autoridad legal a menos de que se prohiba de otro modo, tal como una prohibición bajo leyes judiciales para preservar la confidencialidad de una investigación legal, - -(ii) cualquier acceso accidental o no autorizado, y - -(iii) cualquier solicitud recibida directamente de los titulares de los datos sin responder a dicha solicitud, a menos de que se haya autorizado de otra forma; - -(e) lidiar oportuna y adecuadamente con todas las investigaciones de exportador de datos que se relacionen con su procesamiento de los datos personales sujetos a transferencia y cumplir con los consejos de la autoridad supervisante con respecto al procesamiento de los datos transferidos; - -(f) bajo solicitud del exportador de los datos, emitir sus medios de procesamiento de datos para su auditoría de actividades de procesamiento que se cubren en las cláusulas, lo cual se deberá llevar a cabo por medio del exportador de los datos o mediante un cuerpo de inspección compuesto de miembros independientes y en posesión de las certificaciones profesionales requeridas y ligadas por deber o confidencialidad, seleccionadas por el exportador de los datos, cuando sea aplicable, de acuerdo con la autoridad supervisora; - -(g) poner a disposición para el titular de los datos bajo solicitud una copia de las Cláusulas, o de cualquier contrato existente para el subprocesamiento, a menos de que dichas Cláusulas o contrato contengan información compercial, en cuyo caso pudiera eliminar dicha información comercial, con excepción del Apéndice 2, el cual se deberá reemplazar con un resumen descriptivo de las medidas de seguridad en esos casos donde el titular de los datos no puede obtener una copia del exportador de los datos; - -(h) que, en caso de subprocesamiento, se ha informado previamente al exportador de los datos y se ha obtenido una aprobación previa por escrito; - -(i) que los servicios de procesamiento del subprocesador se llevarán acabo de acuerdo con la Cláusula 11; y - -(j) enviar al exportador de los datos oportunamente una copia de cualquier contrato de subprocesamiento que se concluya bajo las Cláusulas. - -#### 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. Si algún titular de los datos no puede presentr un reclamo de indemnización en contra del exportador de los datos de acuerdo con el párrafo 1, la cual se derive de una violación por parte del importador de los datos o de su subprocesador o de cualquiera de sus obligaciones que se describen en la Cláusula 3 o en la Cláusula 11, debido a que el exportador de los datos ha desaparecido realmente o dejado de existir ante la ley, o se ha declarado insolvente, el importador de los datos acuerda que el titular de los datos puede emitir un reclamo contra el importador de los datos como si fuera el exportador de los mismos, a menos de que alguna entidad sucesora haya asumido las obligaciones legales íntegras del exportador de los datos contractualmente o mediante la aplicación de la ley, en cuyo caso, el sujeto de los datos puede hacer valer sus derechos contra dicha entidad. El importador de los datos podría no depender de que exista una violación por parte de un subprocesador de sus obligaciones para evitar las suyas propias. - -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. - -#### 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: - -(a) para referir la disputa de mediación, mediante una persona independiente o, cuando sea aplicable, mediante la autoridad supervisora; - -(b) referir la disputa en las cortes del Estado Miembro en el cual se establece el exportador de los datos. - -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. 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. 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 dado caso, el exportador de los datos tenga derecho a tomar las medidas previstas en la Cláusula 5(b). - -#### 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. 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. 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. 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. - -#### 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. 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. - -### Apéndice 1 para las Cláusulas Contractuales Estándar -Exportador de los datos: El cliente es el exportador de los datos. - -**Importador de los datos:** El importador de los datos es GitHub, Inc., un productor global de software y servicios. - -**Titulares de los datos:** Los titulares de los datos incluyen a los representantes de los exportadores de datos y a los usuarios finales, incluyendo a los empleados, consultores, colaboradores, y clientes del exportador de los datos. Los titulares de los datos también podrían incluir a aquellos individuos que intentan comunicarse o transferir información personal a los usuarios de los servicios proporcionados por el importador de los datos. GitHub reconoce que, dependiendo de el uso del Servicio que tenga el Cliente, éste puede elegir el incluir los datos personales de cualquiera de los siguientes tipos de titulares de datos en los Datos Personales del Cliente: - -- Empleados, consultores y trabajadores temporales (actuales, previos o futuros) del exportador de los datos; -- Dependientes de los antes listados; -- 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); -- Usuarios (por ejemplo, clientes, pacientes, visitantes, etc.) y otros titulares de los datos que sean usuarios de los servicios del exportador de los datos; -- Socios, interesados o individuos que colaboren, se comuniquen o interactuen activamente de otra forma con los empleados del exportador de los datos y/o que utilicen herramientas de comunicación tales como apps y sitios web que proporcione el exportador de los datos; -- Los interesados o los individuos que interactuen pasivamente con el exportador de los datos (por ejemplo, porque son el titular de una inspección, investigación o que se mencionan en documentos o en correspondencia dirigida a o proviniente del exportador de los datos); o -- Profesionales con privilegios de profesionista (por ejemplo, doctores, abogados, notarios, trabajadores religiosos, etc.). - -**Categorías de los datos:** Los datos personales transferidos que se incluyen en los correos electrónicos, documentos y en otros tipos de datos en forma electrónica o en el contexto del Servicio. GitHub reconoce que, dependiendo del uso que el Cliente de al Servicio, éste puede elegir incluir datos personales de cualquiera de las siguientes categorías dentro de los Datos Personales del Cliente: -- Datos de autenticación (por ejemplo, nombre de usuario, correo electrónico, contraseña); -- Información de contacto (por ejemplo, correo electrónico); -- Números de identificación única y firmas (direcciones IP, identificadores únicos en cookies de rastreo o tecnologías similares). -- Otra información de identificación única. Los titulares de los datos podrían incluir más datos tales como nombres reales, imágenes de avatar, y otra información personal; - -**Categorías especiales de los datos (si corresponde):** El importador de los datos no recolecta procesa intencionalmente ninguna categoría especial de datos para llevar a cabo sus servicios para el exportador de los mismos. - -Sin embargo, ya que el importador de los dtos proporciona servicios de almacenamiento y no controla las categorías de los datos que almacena, el exportador de los datos podría elegir transferir las categorías especiales de los datos. Por consiguiente, el exportador de los datos es el único responsable de garantizar que cumple con todas las obligaciones impuestas por las leyes y regulaciones aplicables relacionadas con la recolección y procesamiento de cualquier categoría de datos, incluyendo el obtener el consentimiento explícito del titular de los datos antes de procesar datos personales sensibles. - -**Operaciones de procesamiento:** Los datos personales transferidos estarán sujetos a las actividades de procesamiento básico siguientes: GitHub utiliza los datos pesonales para los propósitos limitados que se establecen en la Declaración de Privacidad de GitHub, disponible en [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), y en la sección de "Procesamiento de Datos" de la DPA. Subcontratistas: De acuerdo con la DPA, el importador de los datos podrá contratar a otras compañías para proporcionar servicios limitados en nombre del importador de los datos, tales como proporcionar soporte al cliente. Cualquier subcontratista de este tipo tendrá permiso de obtener los Datos Personales del Cliente únicamente para entregar los servicios para los cuales lo contrató el importador de los mismos, y se les prohibe utilizar los Datos Personales del Cliente para cualquier otro propósito. - -### Apéndice 2 para las Cláusulas Contractuales Estándar -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. Personal.** El personal del importador de los datos no procesará los Datos Personales del Cliente sin autorización. El personal está obligado a mantener la confidencialidad de cualquier Dato Personal del Cliente y esta obligación continúa aún después de que la relación termine. - -**2. Contacto de Privacidad de los Datos.** El director de privacidad para el importador de los datos puede contactarse en la siguiente dirección: GitHub, Inc. Atención: Privacidad 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA - -**3. Medidas Técnicas y Organizacionales.** El importador de los datos ha implementado y mantendrá las medidas técnicas y organizacionales adecuadas, controles internos y rutinas de seguridad informática que pretenden proteger los Datos Personales del Cliente de acuerdo como se definen en las Pruebas de Seguridad de GitHub, contra la pérdida accidental, destrucción o alteración; divulgación no autorizada o acceso; o destrucción ilegal de acuerdo a lo siguiente: Las medidas organizacionales y técnicas, controles internos, y rutinas de seguridad informática establecidas en las Pruebas de Seguridad de Github se incorporan en la presente a este Apéndice 2 mediante esta referencia y se vinculan con el importador de los datos como si se establecieran en este Apéndice 2 íntegramente. La Firma de GitHub, Inc. se muestra a continuación. - -Se firman las Cláusulas Contractuales Estándar, Apéndice 1 y Apéndice 2 en nombre del importador de los datos - -![Impresión de pantalla 2020-07-20 a las 2 20 29 PM](/assets/images/help/site-policy/docusign-signature.png) - -Lynn Hashimoto, Jefe de Producto & Regulación Legal - -GitHub, Inc. - - -## PRUEBA DE SEGURIDAD - -### 1. Programa de seguridad de la información. - -#### 1.1 Administración de la seguridad. - -Durante la vigencia del Acuerdo, GitHub mantendrá y hará valer un programa de seguridad informática por escrito (**"Programa de Seguridad"**) que se alínea con los marcos de trabajo reconocidos por la industria; incluye salvaguardas de seguridad razonables diseñadas para proteger la confidencialidad, integridad, disponibilidad y resiliencia de los Datos Protegidos del Cliente; es adecuada para la naturaleza, tamaño y complegidad de las operaciones de negocio de GitHub; y cumple con las Leyes de Protección de Datos Aplicables y otras leyes y regulaciones de seguridad informática específicas que aplican en las regiones geográficas en donde GitHub conduce sus negocios. - -a. Oficial de seguridad. GitHub ha designado a un empleado de rango superior para que sea responsable de supervisar y llevar a cabo su Programa de seguridad y para la gobernanza y las comunicaciones internas sobre los temas de seguridad de la información. - -b. Cambios en el Programa de seguridad. GitHub no hará cambios en su Programa de seguridad que afecten negativamente la seguridad de cualquier Dato protegido del Cliente sobre los que se exija notificación según lo dispuesto en las reglamentaciones y leyes aplicables. - -c. GitHub mantendrá las prácticas de seguridad estándar del sector que incluyen, entre otras, las siguientes: - -- Programa de Administración de vulnerabilidades -- Capacitación para el Desarrollo seguro, Prácticas de revisión y codificación -- Controles de acceso lógicos y físicos a los Sistemas de producción -- Evaluaciones y auditorías técnicas externas -- Políticas de seguridad, estándares y procedimientos de operaciones estándar -- Capacitación para la concientización sobre la seguridad y la privacidad - - -#### 1.2 Administración de Incidentes de Seguridad. -Durante la vigencia del Acuerdo y donde sea aplicable, GitHub proporcionará un programa de administración de incidentes de acuerdo a lo siguiente: - -a. Disponibilidad de seguridad e intensificación. GitHub mantendrá el contacto de seguridad adecuado y los procesos de intensificación las 24 horas del día, los 7 días de la semana, para asegurar que los clientes y los empleados puedan enviar propuestas al equipo de Seguridad de GitHub. - -b. Respuesta ante incidentes. Si GitHub supiese de cualquier violación de seguridad que conlleve a la destrucción ilegal o accidental, pérdida, alteración, divulgación o acceso no autorizado a los Datos Personales del Cliente (cada uno de éstos considerado un **"Incidente de Seguridad"**), GitHub, oportunamente y sin retraso alguno (1) notificará al cliente del Incidente de Seguridad; (2) investigará el Incidente de Seguridad y proporcionará al cliente con la información detallada sobre dicho Incidente de Seguridad; (3) tomará los pasos razonables para mitigar los efectos y para minimizar cualquier daño que resulte del Incidente de Seguridad. - -c. Notificación. La(s) Notificación(es) de los Incidentes de seguridad se entregarán a uno o más administradores del Cliente por el medio que GitHub seleccione. Es responsabilidad únicamente del Cliente asegurar que los administradores del Cliente supervisen y respondan cualquier notificación. 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. - -d. Asistencia razonable. GitHub hará los esfuerzos comercialmente razonables para ayudar al Cliente a cumplir con su obligación del Cliente, según las regulaciones o leyes aplicables, de notificar a la autoridad correspondiente y a los sujetos de datos sobre dicho Incidente de seguridad. - -#### 1.3 Cuidado Adecuado sobre los Subcontratistas y Proveedores. -GitHub mantendrá un cuidado adecuado cuando utilice subcontratistas y proveedores. GitHub conservará los informes de evaluación del proveedor y cualquier trabajo de evaluación por un mínimo de tres años. - -#### 1.4 Salvaguardas Físicas en el Centro de Datos. -En medida que GitHub utilice proveedores terceros para hospedar ambientes productivos, GitHub seleccionará aquellos que cumplan con los controles de seguridad física descritos en los estándares de la industria y que emitan un reporte de auditoría externa anual tal como una certificación de SOC 2 o de ISO 27001. Todos los accesos a las áreas, gabinetes o estantes que alojan telecomunicaciones, dispositivos de red y otras "líneas de transmisión de datos" o equipos se controlarán como se indica a continuación: - -a. el acceso se controlará con lectores de insignia en uno o más puntos de entrada; - -b. las puertas que solo se usan como puntos de salida tendrán picaportes de un solo lado o dispositivos con barra antipánico en la salida; - -c. todas las puertas se equiparán con contactos de alarmas; - -d. todas las puertas de salida tendrán capacidad de videovigilancia; - -e. todos los accesos con tarjeta y sistemas de vídeo estarán vinculados a un generador o a un sistema de respaldo UPS. - -### 2. Solicitudes de información e informes del cumplimiento. - -#### 2.1 Solicitudes de Información. -En caso de que exista una solicitud por escrito y no más de una vez por año, GitHub responderá a las solicitudes de información para valorar la información del cumplimiento y seguridad reñacionada con los riesgos. La respuesta se entregará por escrito dentro de los treinta días de recibida la solicitud, a la espera de aclaraciones necesarias de cualquier solicitud. - -#### 2.2 Contenidos de la Respuesta. -GitHub incluirá en su respuesta anual los reportes de auditoría relevantes para los centros de datos productivos, IaaS, Paas, o proveedores de hospedaje privado, así como GitHub determine relevante, bajo su criterio exclusivo, y basándose en los servicios y datos proporcionados. - -#### 2.3 Reporte de Auditoría de Seguridad de GitHub. -GitHub ejecutará auditorías externas para producir un reporte de auditoría de SOC1, tipo 2, y de SOC2, tipo2. GitHub continuará ejecutando auditorías y emitiendo los informes correspondientes durante la vigencia del Acuerdo al menos anualmente. - -### 3. Cooperación con las auditorías reglamentarias. -En caso de que el cliente lleve a cabo una auditoría regulatoria o una auditoría en respuesta a una Autoridad Supervisora la cual requiera la participación de GitHub, GitHub cooperará íntegramente con las solicitudes relacionadas al proporcionar acceso al personal experto, documentación y software de aplicación relevantes. El Cliente tiene las siguientes responsabilidades sobre cualquiera de dichas auditorías de Autoridad de supervisión o reglamentarias: - -a. El Cliente debe asegurar el uso de un tercero independiente (es decir, el regulador o el delegado del regulador) y que los resultados y los datos no relevantes para el Cliente quedarán restringidos para el acceso del Cliente. - -b. La notificación de dicha auditoría deber ser por escrito y se debe entregar a GitHub en su debido momento, a la espera de la notificación del regulador, y de una forma que permita que el personal adecuado esté disponible para ayudar. Cuando los reguladores no proporcionen notificación por anticipado al Cliente acerca de la auditoría o la investigación, GitHub responderá en su debido momento según lo exijan los reguladores. - -c. Cualquier auditor externo debe divulgarle a GitHub los resultados y las acciones recomendadas cuando el regulador lo permita. - -d. En el caso de que haya una auditoría reglamentaria, se permitirá el acceso solo durante las horas de trabajo habituales, hora del Pacífico. - -e. En la medida que lo permita la ley, el Cliente debe mantener confidencial cualquier información reunida mediante este tipo de auditorías de GitHubb que, por su naturaleza, debe ser confidencial. diff --git a/translations/es-XL/content/github/site-policy/github-deceased-user-policy.md b/translations/es-XL/content/github/site-policy/github-deceased-user-policy.md deleted file mode 100644 index dd7ebdeae9..0000000000 --- a/translations/es-XL/content/github/site-policy/github-deceased-user-policy.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Política de Usuario Finado de Github -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -En caso de que fallezca un usuario de GitHub, podemos trabajar con un individuo autorizado para determinar qué sucederá con el contenido de la cuenta. - -Si eres un familiar cercano, un [sucesor pre-designado](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories), u otro individuo autorizado (que podría incluir a colaboradores o socios de negocios) de un usuario que a fallecido y te gustaría hacer una solicitud con respecto a la cuenta, puedes contactarnos en https://support.github.com/contact. Por favor, porporciona a siguiente información en tu mensaje: - -- Nombre -- Información de Contacto -- Nombre del cuentahabiente finado -- Nombre de usuario de GitHub del cuentahabiente finado -- Tu parentezco con el cuentahabiente finado (por favor incluye si se te ha designado como el sucesor de la cuenta en GitHub.com) -- Si se te designó como sucesor de cuenta, proporciona el nombre de usuario de tu cuenta de GitHub -- La acción que buscas (por ejemplo, transferir repositorios públicos, cancelar la facturación en una cuenta) - -Una vez que hayamos recibido tu solicitud, podremos dar seguimiento con otra solicitud de información adicional, tal como la copia de tu identificación con fotografía, copia del certificado de defunción, y la documentación que confirme que estás autorizado para actuar con relación a la cuenta del usuario finado, para verificar que estamos autorizados adecuadamente para procesar tu solicitud. - -Por favor, nota que la información que proporciones en tu solicitud se recabará de acuerdo con nuestra [Declaración de privacidad](/github/site-policy/github-privacy-statement), y retendremos la información únicamente de acuerdo con lo necesario para cumplir con nuestras obligaciones legales y resolver disputas. diff --git a/translations/es-XL/content/github/site-policy/github-enterprise-cloud-evaluation-agreement.md b/translations/es-XL/content/github/site-policy/github-enterprise-cloud-evaluation-agreement.md deleted file mode 100644 index 9afe00a785..0000000000 --- a/translations/es-XL/content/github/site-policy/github-enterprise-cloud-evaluation-agreement.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Acuerdo de evaluación de GitHub Enterprise Cloud -redirect_from: - - /articles/github-enterprise-cloud-evaluation-agreement -versions: - free-pro-team: '*' ---- - -GRACIAS POR ELEGIR GITHUB PARA LAS NECESIDADES COMERCIALES DE SU EMPRESA. LEA ESTOS TÉRMINOS DETENIDAMENTE YA QUE RIGEN SU EVALUACIÓN DEL USO DEL SERVICIO, A MENOS QUE GITHUB HAYA EJECUTADO UN ACUERDO ESCRITO POR SEPARADO CON USTED PARA ESE FIN. AL HACER CLIC EN EL BOTÓN "ACEPTO" O UN BOTÓN SIMILAR O AL ACCEDER AL SERVICIO A MODO DE PRUEBA, ACEPTA TODOS LOS TÉRMINOS Y CONDICIONES DE ESTE ACUERDO DE EVALUACIÓN. SI ESTÁ INGRESANDO A ESTE ACUERDO DE EVALUACIÓN EN NOMBRE DE UNA EMPRESA U OTRA ENTIDAD GLOBAL (EN ADELANTE DENOMINADO "**CLIENTE**), EL CLIENTE EXPRESA QUE TIENE LA AUTORIDAD LEGAL PARA VINCULAR A LA EMPRESA U OTRA ENTIDAD LEGAL CON ESTE ACUERDO DE EVALUACIÓN. ADEMÁS AL ACEPTAR ESTOS TÉRMINOS, EL CLIENTE ACEPTA QUE HA LEÍDO LA DECLARACIÓN DE PRIVACIDAD DE GITHUB. - -### 1. Términos de servicio corporativos - -El cliente debe tener una cuenta corporativa en GitHub.com para poder acceder a la evaluación. La evaluación del Cliente sobre Enterprise Cloud se regirá mediante estas condiciones y las Condiciones Corporativas del Servicio (las cuales se pueden encontrar en [https://docs.github.com/articles/github-corporate-terms-of-service](/articles/github-corporate-terms-of-service)) (en conjunto conocidas como el "**Acuerdo de Evaluación**"). Sin embargo, los términos adicionales asociados con el [Anexo de Enterprise Cloud](https://docs.github.com/articles/github-enterprise-cloud-addendum) **no** se aplicarán hasta que el Cliente actualice su compra a una suscripción remunerada de Enterprise Cloud.Todos los términos en mayúscula que no están definidos en este Acuerdo de evaluación están definidos en los Términos de servicio corporativos. - -### 2. Plazo y terminación - -*2.1 Plazo.*"Fecha de vigencia del acuerdo de evaluación" es la fecha en la que el Cliente acepta los términos y condiciones de este Acuerdo de evaluación. Este Acuerdo comienza con la Fecha de vigencia del Acuerdo de evaluación y continúa vigente durante catorce (14) días ("**Plazo de evaluación**"). - -*2.2. Terminación.* Cualquiera de las partes puede terminar este Acuerdo de evaluación por cualquier motivo y sin causa alguna. La Sección 2.3 se aplicará a la elección de cualquiera de las partes de terminar este Acuerdo de evaluación. Este Acuerdo de evaluación terminará inmediatamente, sin previo aviso, si el Cliente incumple alguno de los términos de este Acuerdo de evaluación. - -*2.3 Efecto de terminación.* Al finalizar el Plazo de evaluación, cualquier Licencia de suscripción finalizará automáticamente; el Cliente ya no tendrá derecho a usar Enterprise Cloud, y el Cliente puede perder acceso al Contenido, las características o la capacidad de esta cuenta. Consulte la sección "Efecto de terminación" de los Términos de servicio corporativos para obtener información sobre cómo obtener una copia de ese Contenido. - -### 3. Garantías y limitaciones de responsabilidades - -EL CLIENTE COMPRENDE Y ACEPTA QUE CUALQUIER MATERIAL O INFORMACIÓN QUE GITHUB PROPORCIONE O A LA QUE EL CLIENTE TENGA ACCESO CONFORME A ESTE ACUERDO DE EVALUACIÓN (QUE INCLUYE, PERO QUE NO SE LIMITA A, CUALQUIER INFORMACIÓN CONFIDENCIAL O MATERIALES DE LA CUENTA DE EVALUACIÓN) SE SUMINISTRAN "**TAL COMO ESTÁN**" Y SIN GARANTÍA DE NINGÚN TIPO, EXPRESA O IMPLÍCITA. GITHUB RENUNCIA ESPECÍFICAMENTE A TODAS Y CADA UNA DE LAS GARANTÍAS IMPLÍCITAS O CONDICIONES DE COMERCIABILIDAD, ADAPTABILIDAD PARA UN FIN ESPECÍFICO Y NO INCUMPLIMIENTO. - -### 4. Limitación de responsabilidad - -EN NINGÚN CASO GITHUB SERÁ RESPONSABLE POR UN CLIENTE O TERCERO POR CUALQUIER DAÑO INDIRECTO, ESPECIAL, INCIDENTAL, RESULTANTE, EJEMPLAR O PUNITIVO, QUE INCLUYA PERO NO EXCLUSIVAMENTE DAÑOS POR DATOS PERDIDOS, GANANCIAS PERDIDAS O COSTOS DE PROCURACIÓN DE BIENES O SERVICIOS SUSTITUTOS, QUE SE HAYA CAUSADO Y CONFORME A CUALQUIER TEORÍA DE RESPONSABILIDAD, YA SEA POR CONTRATO, AGRAVIO (QUE INCLUYE SIN LIMITACIÓN RESPONSABILIDAD POR PRODUCTOS, ESTRICTA RESPONSABILIDAD Y NEGLIGENCIA) O CUALQUIER OTRA TEORÍA, Y SI LA OTRA PARTE SABÍA O DEBERÍA SABER SOBRE LA POSIBILIDAD DE ESE DAÑO. EN NINGÚN CASO LA RESPONSABILIDAD TOTAL DE GITHUB QUE SURGE DE O ESTÁ RELACIONADA CON ESTE ACUERDO DE EVALUACIÓN POR CUALQUIER CAUSA EN ABSOLUTO, E INDEPENDIENTEMENTE DE LA FORMA DE LA ACCIÓN, YA SEA CONTRACTUAL O EXTRACONTRACTUAL, SUPERARÁ LOS QUINIENTOS DÓLARES ($500.00). LAS LIMITACIONES ANTERIORES SE APLICARÁN A PESAR DEL OBJETIVO ESENCIAL DE CUALQUIER SOLUCIÓN LIMITADA ESTABLECIDA EN ESTE ACUERDO DE EVALUACIÓN. - -### 5. Privacidad - -5.1 Como parte del desarrollo y la evaluación de nuestros programas de evaluación, GitHub necesita recopilar información sobre cómo los Clientes usan los servicios y los programas y cómo GitHub puede mejorarlos. Es posible que GitHub recopile determinada información personal adicional del Cliente. Por ejemplo, GitHub puede invitar al Cliente para brindar retroalimentación (tal como se explica en la Sección 6 a continuación). GitHub puede realizar preguntas sobre experiencias de los clientes, familiaridad con el producto, o información demográfica. GitHub usa esta información para mejorar sus productos y servicios y no vende la retroalimentación a terceros o anunciantes. El cliente puede negarse a facilitar retroalimentación, negarse a responder preguntas específicas o comunicarse con GitHub para eliminar o alterar la información que ha recopilado sobre el Cliente. - -5.2 Los servidores de GitHub están situados en los Estados Unidos. GitHub procesa los datos del cliente en los Estados Unidos. Sin embargo, el Cliente es responsable de determinar qué tipo de datos personales emite a GitHub. Por favor, consulta la [Declaración de Privacidad](/articles/github-privacy-statement) para obtener más información. - -### 6. Comentarios - -GitHub siempre está tratando de mejorar sus productos y servicios, y las opiniones de los clientes sobre su cuenta de evaluación serán de gran ayuda. Si el cliente decide proporcionar algún comentario a GitHub, el cliente reconoce y acepta que GitHub tendrá una licencia exenta de regalías, totalmente paga, en todo el mundo, transferible, sublicenciable, irrevocable y perpetua para implementar, usar, modificar, explotar comercialmente y/o incorporar los comentarios en productos, servicios y documentación de GitHub. - -### 7. Modificaciones; renuncias; inexistencia de terceros beneficiarios - -Es posible que este Acuerdo de evaluación no se cambie, excepto mediante un escrito firmado por ambas partes o mediante una actualización de los Términos generalmente aplicables. Si algún plazo, condición o cláusula de este Acuerdo de evaluación o es válido o inexigible, los términos restantes seguirán siendo válidos y exigibles en la mayor medida permitida por la ley. Las partes acuerdan expresamente que no hay terceros beneficiarios de este Acuerdo de evaluación. - -### 8. Acuerdo completo; Orden de prevalencia - -Los términos generalmente aplicables conjuntamente con este Acuerdo de evaluación contienen el acuerdo completo de las partes con respecto a su asunto y reemplazan a todas las comunicaciones representaciones, comprensiones y acuerdos anteriores, ya sean escritos u orales. Los términos o condiciones de cualquiera de las órdenes de compra del Cliente, reconocimientos u otros documentos enviados a GitHub en relación con este Acuerdo de evaluación serán nulos y sin efecto. En caso de un conflicto entre este Acuerdo de evaluación y los Términos generalmente aplicables, este Acuerdo de evaluación regirá con respecto a las cláusulas relevantes para el Plazo de evaluación del acuerdo de evaluación. diff --git a/translations/es-XL/content/github/site-policy/github-enterprise-server-license-agreement.md b/translations/es-XL/content/github/site-policy/github-enterprise-server-license-agreement.md deleted file mode 100644 index 6e25cf27c8..0000000000 --- a/translations/es-XL/content/github/site-policy/github-enterprise-server-license-agreement.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -title: Acuerdo de licencia del servidor de GitHub Enterprise -redirect_from: - - /articles/github-enterprise-server-license-agreement -versions: - free-pro-team: '*' ---- - -Fecha de entrada en vigor: 1 de abril de 2020 - -POR FAVOR LEE ESTE ACUERDO CUIDADOSAMENTE, YA QUE RIGE TU USO DE LOS PRODUCTOS (COMO SE DEFINE A CONTINUACIÓN), A MENOS DE QUE HAYAMOS CELEBRADO UN CONTRATO SEPARADO POR ESCRITO CONTIGO PARA ESTE PROPÓSITO. - -AL DAR CLIC EN EL BOTÓN "ESTOY DE ACUERDO" O SIMILAR, O AL ACCEDER A LOS PRODUCTOS, ACEPTAS TODOS LOS TÉRMINOS Y CONDICIONES DE ESTE ACUERDO. SI ESTÁS INGRESANDO A ESTE ACUERDO EN NOMBRE DE ALGUNA COMPAÑÍA U OTRA ENTIDAD LEGAL (EN LO SUBSECUENTE EL "**Cliente**"), EL CLIENTE REPRESENTA QUE TIENE LA AUTORIDAD LEGAL PARA VINCULAR A LA COMPAÑÍA U OTRA ENTIDAD LEGAL A ESTE ACUERDO. GITHUB PODRÁ MODIFICAR ESTE ACUERDO OCASIONALMENTE, SUJETO A LA SECCIÓN 18.2. - -El presente Acuerdo se aplica a las siguientes ofertas de GitHub, como se define a continuación (colectivamente, los **“Productos”**): - -- El Software (que podrá incluir Software complementario, tal como Advanced Security, Insights y Learning Lab para Enterprise Server); - -- Cualquier Soporte relacionado; y - -- Cualquier Servicio profesional relacionado. - -Si el cliente compró los productos de un socio de GitHub, se reemplazarán las siguientes disposiciones de este acuerdo por las condiciones entre el cliente y el socio de GitHub: Sección 8, Pago; Sección 9, Entrega; Sección 10, Verificación; y Sección 17, Plazo y Terminación. - -**1. Definiciones.** Las letras en mayúscula que no se listen aquí se definirán dentro del acuerdo. - -"**Software Complementario**" Significa Advanced Security, Insights, Learning Lab para Enterprise Server y otro tipo de productos de software complementario adicionales que GitHub puede ofrecer ocasionalmente. - -"**Advanced Security**" significa la característica de Software que permite al cliente identificar las vulnerabilidades de seguridad a través del análisis semántico automatizado de código. - -"**Fecha de Entrada en Vigor del Acuerdo**" es la primera fecha en la que el cliente da clic en "Estoy de Acuerdo" para los términos y condiciones de este acuerdo, o en la primera fecha en la que hace una solicitud de los productos. - -"**Afiliado**" significa cualquier entidad que controla directa o indirectamente, es controlada por, o está bajo control común con una parte en donde "control" significa tener más del cincuenta porciento (50%) de propiedad o el derecho para dirigir la administración de la entidad. - -"**Vista Previa Beta** significa software, servicios, o características identificadas como alfa, beta, vista previa, acceso temprano, o evaluación, o palabras y frases con significados similares. - -"**Modificaciones del Cliente**" significa modificaciones de software que el cliente puede hacer únicamente con el propósito de de desarrollar correcciones de errores, personalizaciones, o características adicionales para cualquier biblioteca que esté bajo la licencia de código abierto que pueda incluirse con o ligarse al Software. - -"**Documentación**" significa cualquier manual, documentos y otros materiales de apoyo relacionados con el Software que GitHub proporciona o pone a disposición del cliente. La documentación se considera parte del Software. - -"**Retroalimentación**" significa cualquier idea, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de ampliación, recomendaciones o cualquier otra observación sobre los productos y servicios de GitHub. - -"**Cuotas**" significa los pagos que el cliente debe hacer a GitHub para utilizar los productos durante el Periodo de Suscripción aplicable o Servicios Profesionales, ya que éstas se reflejan en un Formato de Compra o SOW. - -"**GitHub Insights**" o "**Insights**" significa la característica de software que proporciona al cliente métricas, herramientas de análisis y recomendaciones que se relacionan con el uso del Software. GitHub Insights no incluye características tradicionales de GitHub incluyendo perspectivas de organización y de repositorio. - -"**Socio de GitHub**" significa una compañía autorizada para revender productos de GitHub bajo los términos y condiciones del Contrato de Socios para los Canales de GitHub. - -"**Learning Lab para Enterprise Server**" significa la característica de Software que permite a los usuarios aprender acerca de las funcionalidades de GitHub, incluyendo la documentación asociada. - -"**Feca de Entrada en Vigor de la Licencia**" significa la fecha de entrada en vigor de cada Formato de Compra como se declare en el mismo. - -"**Llave de Licencia**" Significa el archivo de datos que utiliza el mecanismo de control de acceso del Software, el cual te permite instalarlo, operarlo y utilizarlo, y que se entrega por medio de un sitio web seguro protegido por contraseña. - -"**Formato de Compra**" significa la documentación escrita o electrónica (incluyendo una cotización) que las partes utilizan para solicitar los productos. - -"**Partes**" significa las referencias a GitHub y el Cliente colectivamente. Podrá referirse a cada una como una "**Parte**". - -"**Servicios Profesionales**" significa servicios de capacitación, consultoría o implementación que GitHub proporciona al Cliente de acuerdo con una SOW ejecutada recíprocamente. Los Servicios profesionales no incluyen el Soporte. - -"**Lanzamiento**" significa un lanzamiento de Software que GitHub generalmente pone a disposición de sus clientes, junto con cualquier cambio correspondiente a la documentación, que contiene ampliaciones, nuevas características o nuevas funcionalidades, generalmente indicado por un cambio en el dígito de la derecha del primer punto decimal (por ejemplo, de x.x.x a x.y.x) o a la izquierda del primer punto decimal (por ejemplo, de x.x.x a y.x.x). - -"**Software**" se refiere al software propietario de Enterprise Server de GitHub. El Software incluye cualquier Documentación aplicable, cualquier actualización al Software que GitHub proporciona al cliente o al cual puede acceder dicho cliente bajo este acuerdo y, si se incluye en la suscripción de un cliente, cualquier Software complementario. - -**"SOW"** se refiere a una declaración de trabajo ejecutada recíprocamente que detalla los Servicios profesionales que GitHub realizará, cualquier Tarifa relacionada y las obligaciones relacionadas de cada una de las Partes. - -**"Licencia de Suscripción"** significa la licencia asignada a cada usuario para instalar, operar, acceder y utilizar el Software por parte del Clilente. El cliente solo podrá asignar una Licencia de Suscripción por Usuario a través de sus instancias de GitHub Enterprise Server. Cada usuario tendrá acceso a tantas instancias de cliente de Enterprise Server como lo permita dicho cliente. Para obtener mayor claridad, sin embargo, una vez que un Cliente asigne una Licencia de Suscripción a un Usuario, dicho Cliente no recibirá autorización de bifurcar esta licencia para que un Usuario pueda utilizarla en Enterprise Server mientras otro utiliza la misma licencia en otra instancia de GitHub Enterprise Server. - -"**Plazo de Suscripción**" significa el periodo de un (1) año a partir de la fecha de entrada en vigor, a menos de que se especifique algún periodo alterno en un Formato de Compra. GitHub proporcionará al cliente una notificación de renovación por lo menos (60) días antes de la fecha de caducidad del Plazo de Suscripción y generará un Formato de Compra nuevo para la renovación. GitHub proporcionará al cliente una nueva llave de licencia descargable que permitirá el uso continuo del Software de acuerdo con el formato de compra. - -"**Soporte**" significa el soporte técnico para el Software que pudiera proporcionar GitHub. - -"**Actualización**" significa un lanzamiento de Software que GitHub pone generalmente a disposición de los clientes junto con cualquier cambio correspondiente a la documentación, el cual contiene correcciones o soluciones de errores y que se indica generalmente por el cambio del dígito a la derecha del segundo punto decimal (por ejemplo, de x.x.x a x.x.y). - -"**Usuario**" significa una sola persona o cuenta de máquina que inicia la ejecución del Software o que interactúa o con o dirige el Software en el desempeño de sus funciones. - -**2. Subsidio de Licencia de Software.** GitHub proporciona al cliente una licencia no exclusiva, no transferible, global, sin cargo de regalías, de tiempo limitado para instalar y utilizar el Software para los propósitos comerciales internos del cliente durante el Plazo de Suscripción aplicable, de acuerdo con la documentación, y únicamente por la cantidad de licencias de suscripción declaradas en el Formato de Compra del Cliente. El Software incluye componentes autorizados por terceros a GitHub, incluido el software cuya licencia exige que GitHub facilite el código fuente para que esos componentes estén disponibles. El código fuente para dichos componentes se facilitará previa solicitud. Sin limitar lo anterior, esta licencia permite que el cliente descargue y ejecute la imagen del contenedor de la edición estándar de Microsoft SQL Server para los archivos de Linux ("**Imágenes de SQL Server**"), que solo se puede utilizar con el software como se documenta. El derecho del cliente a usar las imágenes de SQL Server finaliza cuando el cliente ya no tiene derechos para usar el software y el cliente debe desinstalar las imágenes de SQL Server cuando su derecho a usarlos finalice. Microsoft Corporation puede inhabilitar las imágenes de SQL Server en cualquier momento. - -**3. Restricciones de Licencia.** Exceptuando a lo expresamente permitido por la ley, o por una licencia de terceros aplicable, el Cliente y sus Afiliados no deben realizar ni permitir a terceros: (i) sublicenciar, vender, rentar, arrendar, transferir, asignar o dedistribuir el Software; (ii) hospedar el Software para beneficio de terceros; (iii) divulgar o permitir a cualquier tercero para acceder al Software, exceptuando lo expresamente permitido en la sección 2; (iv) hackear o modificar la Llave de licencia, o evitar o cambiar cualquier proceso de registro de licencia; (v) exceptuando a las Modificaciones del Cliente, modificar o crear trabajos derivados del Software, o fusionar dicho Software con otro tipo de software; (vi) desensamblar, descompilar, derivar cualquier ofuscación de código, o de otra manera, hacer ingeniería inversa del Software o pretender derivar cualquier parte de su código fuente, en su totalidad o en parte; (vii) modificar, obscurecer, o borrar cualquier notificación de derechos de autor incluidas en el Software o en su documentación; o (viii) utilizar o copiar de otro modo el Software o la Documentación en alguna forma que no sea expresamente permitida en este acuerdo. - -**4. Derechos de Propiedad Intelectual.** Como se acuerda entre las Partes, GitHub es propietario de todos los derechos, títulos e intereses, incluyendo aquél de derechos de propiedad intelectual, en y para con los Productos. GitHub se reserva todos los derechos sobre los Productos y para ellos no otorgados expresamente al Cliente conforme a lo dispuesto en el presente Acuerdo. - -**5. Retroalimentación.** El ciente podrá proporcionar Retroalimentación a GitHub sobre los Productos. La retroalimentación es voluntaria y no es Información Confidencial del Cliente, incluso si se designa como tal. GitHub puede ejercer y explotar plenamente dicha Retroalimentación con el propósito de (i) mejorar la operación, funcionalidad y uso de las ofertas de productos existentes y futuras de GitHub; y (ii) publicación de estadísticas agregadas sobre la calidad de los Productos, siempre que no se utilicen datos en ninguna de estas publicaciones para identificar específicamente al Cliente, sus empleados o el código de software propietario del Cliente. - -**6. Licencias de Suscripción.** Las Licencias de Suscripción se otorgan por Usuario y varios usuarios no pueden utilizar la misma Licencia de Suscripción. El Cliente puede reasignar una Licencia de suscripción a un nuevo Usuario solo después de noventa (90) días desde la última reasignación de esa misma Licencia de suscripción, excepto que la reasignación se deba a (i) la pérdida o la falla permanente del hardware, (ii) la terminación del empleo o el contrato del Usuario, o (iii) la readjudicación temporal de las Licencias de Suscripción para cubrir una ausencia del Usuario. Cuando un Cliente reasigna una Licencia de Suscripción de un Usuario a otro, dicho Cliente deberá bloquear el acceso del usuario anterior a dicha licencia. - -**7. Afiliados.** Se autoriza a los Afiliados de los Clientes utilizar el Software de conformidad con este acuerdo, siempre que el Cliente sea plenamente responsable de su acceso y del uso del Software. - -**8. Pago** - -**8.1** *Cuotas.* El cliente acuerda pagar las cuotas en su totalidad, por anticipado sin deducción o compensación de cualquier tipo, en dólares estadounidenses. estadounidenses. El cliente debe pagar las Tarifas dentro de los treinta (30) días de la fecha de la factura de GitHub. Las cantidades a pagar bajo este acuerdo no son reembolsables, exceptuando a lo descrito en las secciones 13 y 14.1. Si el cliente no cumple con el pago de las Cuotas a tiempo, GitHub se reserva el derecho, adicionalmente a tomar cualquier otra acción legal o equitativa, de (i) cobrar intereses sobre cantidades atrasadas con valor de 1.0% mensual o la tasa de interés más alta permitida por la ley, la que fuese menor, y cargar todos los gastos de recuperación, y (ii) terminar el Formato de Compra o SOW aplicable. El Cliente es el único responsable de todos los impuestos, tarifas, obligaciones y valoraciones gubernamentales (a excepción de los impuestos basados en los ingresos netos de GitHub) que se imponen o vencen en conexión con el presente Acuerdo. - -**8.2** *Comprar Licencias de Suscripción Adicionales.* El cliente podrá obtener Licencias de Suscripción adicionales bajo este Acuerdo si emite una solicitud a través del sitio web de GitHub o del personal de ventas. Se generará entonces un nuevo Formato de Compra y, si el Cliente compra las Licencias de Suscripción adicionales, éste deberá pagar las cuotas entonces aplicables para ellas, prorrateadas por el saldo del Plazo de Suscripción aplicable. Al momento de la renovación de las Licencias de suscripción del Cliente por otro Plazo de suscripción, GitHub facturará todas las Licencias de suscripción una sola vez al año excepto que se especifique lo contrario en un Formulario de pedidos. - -**8.3** *Software Complementario.* El Software Complementario se licencia por Usuario. Para evitar dudas y a menos que se estipule lo contrario en un formulario de pedidos, la cantidad de licencias de suscripción que el cliente tiene en un momento dado para el software del complemento debe ser igual a la cantidad de licencias de suscripción que el cliente tiene para los productos conforme a lo dispuesto en el presente acuerdo. Por ejemplo, si el Cliente quiere comprar una suscripción de Advanced Security y ya tiene Licencias de Suscripción para 100 Usuarios para los Productos, éste deberá comprar las Licencias de Suscripción para Advanced Security para 100 Usuarios. - -**9. Entrega.** GitHub pondrá la Llave de Licencia a disposición del Cliente para que la pueda descargar en un sitio web seguro y protegido por contraseña. All deliveries under this Section 9 will be electronic. Para evitar dudas, el Cliente es responsable de la instalación de cualquier Software y reconoce que GitHub no tiene ninguna obligación de entrega adicional con respecto al Software después de la entrega de la Clave de la licencia. Cuando las actualizaciones estén disponibles, GitHub las facilitará para la descarga en el mismo sitio web. El Cliente debe Actualizar el Software sobre una base comercialmente razonable pero no menos de una (1) vez al año. El Cliente es responsable de mantener la confidencialidad de sus nombres de usuario y sus contraseñas. - -**10. Verificación.** Bajo solicitud de GitHub, el Cliente proporcionará inmediatamente a GitHub el reporte generado por Software que verifique que el cliente está utilizando el Software en cumplimiento con este Acuerdo. GitHub facturará al Cliente por cualquier uso adicional, con vigencia a partir de la fecha en que su uso excedió los términos del presente Acuerdo. - -**11. Support.** - -**11.1** *Soporte Estándar.* GitHub proporcionará Soporte técnico estándar para el Software sin cargo adicional veinticuatro (24) horas al día, cinco (5) días a la semana, excluyendo fines de semana y días festivos oficiales en los EE.UU. holidays. El Soporte estándar solo se ofrece por medio de tickets basados en la web a través del Soporte de GitHub y las solicitudes de Soporte deben ser iniciadas por un Usuario con el que el equipo de Soporte de GitHub pueda interactuar. GitHub podrá proporcionar Soporte remium (sujeto a las [Condiciones de Soporte Premium para Enterprise Server](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server)) o soporte técnico dedicado para el software a nivel de cuotas, soporte y plazo de suscripción especificadas en un Formato de Compra o SOW. - -**11.2** *Ofertas de Soporte Ampliado.* GitHub podrá proporcionar ofertas de soporte ampliado para el Software (incluyendo aquellas para Soporte Premium, Premium Plus, y Soporte Directo de Ingeniería) de acuerdo con las [Condiciones de soporte](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise), y en el nivel de soporte, cuotas y término de la suscripción que se especifica en un Formato de Compra o SOW. - -**11.3** *Exclusiones.* GitHub hará esfuerzos razonables para corregir cualquier material, errores replicables en el Software del cual reciba notificación por parte del Cliente. Sin embargo, GitHub no será responsable de proporcionar el Soporte cuando (i) alguien (que no sea GitHub) modifica el Software; (ii) el Cliente cambia su sistema operativo o su entorno de una forma que afecta negativamente al Software o a su rendimiento; (iii) el Cliente usa el Software de una forma diferente a la autorizada conforme a lo dispuesto en el presente Acuerdo o a la Documentación; o (iv) existe una negligencia o un uso indebido del Software por parte del Cliente. - -**11.4** *Actualizaciones; Lanzamientos.* GitHub brindará soporte para un lanzamiento determinado únicamente por un (1) año desde la fecha de lanzamiento original, o seis (6) meses a partir de la última actualización del Lanzamiento, lo que sea más prolongado. Si el Cliente requiere Soporte para Lanzamientos anteriores del Software, en ese caso el Cliente debe pagar por ese Soporte de acuerdo con los términos de un Formulario de pedidos o SOW convenidos mutuamente. - -**12. Servicios Profesionales. ** Cuando el Cliente solicite Servicios Profesionales, GitHub proporcionará una SOW que los detalle. GitHub realizará los Servicios profesionales que se describen en cada SOW. GitHub controlará la forma y los medios utilizados para llevar a cabo los Servicios profesionales y se reserva el derecho de determinar el personal asignado. GitHub puede utilizar a terceros para realizar los Servicios profesionales, siempre y cuando GitHub siga teniendo responsabilidad por sus actos y omisiones. El Cliente reconoce y acepta que GitHub conserva todos los derechos, títulos e intereses sobre cualquier cosa que se usa o se desarrolla en conexión con los Servicios profesionales, incluido el software, las herramientas, las especificaciones, las ideas, los conceptos, las invenciones, los procesos, las técnicas y las habilidades. En medida que GitHub haga cualquier entrega al Cliente mientras desempeña los Servicios Profesionales, GitHub garantiza al Cliente una licencia no exclusiva, intransferible, global, exenta de regalías, de plazo limitado para utilizar con los entregables durante el plazo de este acuerdo, únicamente en conjunto con el uso que el Cliente de al Software. - -**13. Limited Warranties.** - -**13.1** *Garantías Extendidas de Software*. GitHub garantiza que: (i) el Software sin modificaciones, en el momento que se pone a disposición del Cliente para su descarga, no contendrá o transmitirá ningún malware, virus, o gusanos informáticos (conocidos también como código informático u otra tecnología específicamente diseñada para alterar, inhabilitar o dañar el software, hardware, sistema computacional o red del cliente) y (ii) por noventa (90) días a partir de la fecha en la que se pone a disposición para su descarga inicial, el Software sin modificaciones se apegará sustancialmente a su documentación. GitHub no garantiza que el uso que el cliente dé al Software será ininterrumpido, o que la operación de dicho software estará libre de errores. La garantía en la presente sección 13.1 no se aplicará si el Cliente modifica o utiliza el Software de alguna manera que no esté expresamente permitida en este acuerdo y en la documentación. La única obligación de GitHub y la única compensación del Cliente, por cualquier incumplimiento de esta garantía será, a discreción y expensas de GitHub, (a) reparar el Software; (b) reemplazar el Software; o (c) terminar el presente Acuerdo con respecto al Software defectuoso y reembolsar las Tarifas pagadas anticipadamente sin uso por el Software defectuoso durante el Plazo de suscripción vigente en ese momento. - -**13.2** *Garantía de Servicios Profesionales.* GitHub garantiza al Cliente que cualquier clase de Servicios Profesionales llevados a cabo bajo el presente acuerdo se realizará de forma eficiente y profesional con el personal calificado adecuado. La única obligación de GitHub, y la única compensación del Cliente, en caso de incumplimiento con esta garantía será, a discreción y expensas de Github, ya sea: (i) volver a realizar inmediatamente cualquier Servicio Profesional que no haya podido cumplir en garantía o, (ii) si no puede resarcirse el incumplimiento, terminar la SOW y reembolsar las cuotas pre-pagadas sin utilizar. - -**13.3** *Garantía General.* Cada parte representa y garantiza que tiene el poder legal y la autoridad de ingresar en este acuerdo, y que se ingresa al presente acuerdo y a cada Formato de Compra mediante un empleado o agente de la Parte que cuenta con toda la autoridad necesaria para vincular a la Parte con los términos y condiciones de este acuerdo. - -**13.4** *Vistas Previas Beta..* El cliente podrá elegir utilizar las Vistas Previas beta a su absoluta discreción. Las Vistas previas Beta pueden no ser compatibles y pueden cambiarse en cualquier momento sin previo aviso. Las Vistas Previas Beta pudieran no ser tan confiables o estar tan disponibles como el Software. Las Vistas Previas Beta no están sujetas a las mismas medidas de seguridad a las cuales sí lo ha estado y sigue estando el Software. GitHub no tendrá ninguna responsabilidad que surja de las Vistas previas Beta o que esté relacionado con ellas. **LOS CLIENTES UTILIZAN LAS VISTAS PREVIAS BETA BAJO SU PROPIO RIESGO..** - -**13.5** *Aviso de Garantía.* LAS GARANTÍAS LIMITADAS ANTES DESCRITAS SON LAS ÚNICAS QUE GITHUB HACE CON RESPECTO AL SOFTWARE, SERVICIOS PROFESIONALES, Y EL SOPORTE. GIHUB NO OTORGA NINGUNA OTRA GARANTÍA NI REPRESENTACIONES DE CUALQUIER TIPO, Y EN LA PRESENTE SE DESLINDA ESPECÍFICAMENTE DE CUALQUIER OTRA GARANTÍA, YA SEA EXPRESA, IMPLICADA, O ESTATUTORIA, INCLUYENDO MAS SIN LIMITARSE A LAS GARANTÍAS DE COMERCIABILIDAD, ADECUACIÓN PARA UN PROPÓSITO EN PARTICULAR, NO INCUMPLIMIENTO, O CUALQUIER GARANTÍA O CONDICIONES QUE SURJAN A PARTIR DEL CURSO DE LOS ACUERDOS O USO MERCANTIL. NINGUNA INFORMACIÓN O AVISO, YA SEA ORAL O ESCRITO, PROPORCIONADO POR GITHUB O EN CUALQUIER OTRO LUGAR CREARÁ GARANTÍA O CONDICIÓN ALGUNA QUE NO ESTÉ EXPRESAMENTE DECLARADA EN ESTE ACUERDO. - -**14. Defensa de demandas; Liberación.** - -Las Partes de defenderán mutuamente contra las reclamaciones de terceros, hasta el punto que se establece en la presente Sección 14 y pagarán la cantidad correspondiente de cualquier sentencia firme adversa resultante o convenio aprobado, pero solamente si se notifica de inmediato a la Parte demandada por escrito sobre la reclamación y tiene el derecho de controlar la defensa y cualquiera de sus convenios. La Parte defendida debe proveer a la Parte demandada toda la asistencia, la información y la autoridad que se solicita. La Parte demandada reembolsará a la otra Parte por los gastos de bolsillo razonables en que incurra al proveer asistencia y no resolverá ni hará ninguna admisión con respecto a un reclamo de terceros sin previo consentimiento escrito de la otra Parte, sin que sea indebidamente demorado o retenido. La presente Sección 14 describe las únicas compensaciones de las Partes y la responsabilidad total para dichas reclamaciones. - -**14.1** *GitHub*. GitHub defenderá al Cliente contra cualquier reclamación que presente un tercero sin afiliación en medida que alegue que el uso del Software autorizado del cliente infringe derechos de autor, patentes, o nombres comerciales, o que malversa secretos comerciales de un tercero no afiliado. Si GitHub es incapaz de resolver dicha reclamación bajo términos comerciales razonables, podrá optar por ya sea: (a) modificar, reparar o reemplazar el Software (según sea aplicable); o (b) terminar la suscripción del Cliente y reembolsar cualquier cuota de suscripción pre-pagada sin utilizar. GitHub no tendrá obligación alguna bajo esta Sección 14.1 para ninguna reclamación que se derive de: (i) la modificación del Software, o la combinación, operación o uso del Software con el equipo, dispositivos, software, sistemas o datos, diferentes a los autorizados expresamente por el presente acuerdo (incluyendo la Documentación); (ii) La incapacidad del Cliente para dejar de utilizar el Software después de recibir la notificación para hacerlo; (iii) las obligaciones del Cliente bajo la sección 14.2; (iv) los productos o servicios (incluyendo el uso del Software) que proporciona GitHub gratuitamente; o (v) el acceso o utilización de las Vistas Previas Beta. Para fines de las obligaciones de GitHub bajo esta Sección 14.1, El Software incluye componentes de código abierto que GitHub incorpora en ella. - -**14.2** *Cliente*. El cliente defenderá a GitHub contra cualquier reclamación que presente un tercero no afiliado, la cual se derive de: (i) el contenido que el Cliente cargue al Software; (ii) la violación del cliente al presente Acuerdo, incluyendo las violaciones a la confidencialidad por parte del Cliente; (iii) las modificaciones que el Cliente realice al Software; o (iv) cualquier equipo, dispositivo, software, sistemas o datos con la marca del tercero que el Cliente combine, opere, o utilice con el Software. - -**15. LIMITACIÓN DE LA RESPONSABILIDAD.** - -**15.1** *Sin Daños Indirectos*. EN LA MÁXIMA MEDIDA QUE SE PERMITA Y SEA LEGALMENTE APLICABLE, EN NINGUNA SITUACIÓN SERÁ RESPONSABLE NINGUNA DE LAS PARTES POR LA OTRA PARTE O POR NINGÚN TERCERO POR CUALQUIER DAÑO INDIRECTO, ESPECIAL, INCIDENTAL, PUNITIVO, O CONSECUENCIAL (INCLUYENDO AQUELLOS POR PÉRDIDA DE GANANCIAS, INGRESOS, O DATOS) O POR EL COSTO DE OBTENER PRODUCTOS SUSTITUTOS QUE SE DERIVEN DE O ESTÉN EN CONEXIÓN CON EL PRESENTE ACUERDO, CUALQUIERA QUE FUESE SU CAUSA, YA SEA QUE LA RESPONSABILIDAD SE GENERE DE CUALQUIER RECLAMACIÓN BASADA EN CONTRATOS; GARANTÍAS, AGRAVIOS (INCLUYENDO NEGLIGENCIA), RESPONSABILIDAD ESTRICTA O DE CUALQUIER OTRO TIPO; Y YA SEA QUE SE HAYA AVISADO A LA PARTE O NO DE LA POSIBILIDAD DE QUE OCURRAN DICHOS DAÑOS. - -**15.2** *Limitación de la Responsabilidad Total*. HASTA EL GRADO MÁXIMO QUE PERMITA LA LEY APLICABLE, EN NINGÚN CASO LA RESPONSABILIDAD ACUMULATIVA TOTAL DE CADA PARTE BAJO ESTE ACUERDO DESDE TODA CAUSO DE ACCIÓN Y TODAS LAS TEORÍAS DE RESPONSABILIDAD PODRÁ EXCEDER LAS CUOTAS QUE EL CLIENTE YA HAYA PAGADO AL GITHUB DURANTE LOS DOCE (12) MESES PRECEDENTES A QUE LA RECLAMACIÓN HAYA DADO LUGAR A DICHA RESPONSABILIDAD. PARA LOS PRODUCTOS Y SERVICIOS QUE SE PROPORCIONAN GRATUITAMENTE, LA RESPONSABILIDAD DE GITHUB SE LIMITA A LOS DAÑOS DIRECTOS CON VALOR DE HASTA $5,000 DÓLARES ESTADOUNIDENSES. PARA LAS VISTAS PREVIAS BETA, LA RESPONSABILIDAD DE GITHUB SE LIMITA A LOS DAÑOS DIRECTOS DE HASTA $5,000.00 DÓLARES ESTADOUNIDENSES. - -**15.3** *Excepciones*. Las exclusiones y limitaciones expuestas en esta Sección 15 no aplicarán a la responsabilidad que se derive de (1) la falta de cumplimiento del cliente con la garantía o restricciones de la licencia citadas en las Secciones 2 y 3; (2) las obligaciones de defensa de la Parte citadas en la Sección 14; o (c) la violación de una parte a sus obligaciones de confidencialidad citadas en la Sección 16. - -**16. Confidentiality.** - -**16.1** *Definición de Información Confidencial*. Para el propósito de este acuerdo, "Información Confidencial" significa cualquier información técnica o de negocio que cualquiera de las Partes divulga al otro, por escrito, oralmente, o por cualquier otro medio, incluyendo la divulgación de programas, código, algoritmos, datos, conocimiento, fórmulas, procesos, ideas, invenciones (ya sean patentables o no), modelados y cualquier otro tipo de planes técnicos, de negocios, y de desarrollo de productos, nombres y pericia de los empleados y consultores, y listas de clientes. Para efectos del presente Acuerdo, exceptuando lo expresamente establecido en la sección 2.1, el código fuente del Software se considerará ser Información Confidencial de GitHub, sin importar si está marcado como tal. - -**16.2** *Restricciones sobre el Uso y Divulgación.* Ninguna de las Partes podrá utilizar la Información Confidencial de la otra, exceptuando aquella permitida en este Acuerdo. Cada Parte acuerda mantener la confidencialidad y proteger la Información Confidencial de la otra Parte utilizando por lo menos el mismo grado de cuidado que utiliza para su propia información de una naturaleza similar, pero en todos los casos, por lo menos un grado razonable de cuidado. Cada Parte acuerda tomar todas las precauciones razonables para prevenir cualquier divulgación no autorizada de la Información Confidencial de la otra Parte, incluyendo, sin limitación, el divulgar Información Confidencial únicamente a sus empleados, proveedores independientes, consultores y asesores financieros y legales (colectivamente conocidos como "Representantes") (i) con la necesidad de conocer esta información, (ii) quienes son partes de acuerdos adecuados y suficientes para cumplir con la presente sección 16, y (iii) a quienes se les informa de las obligaciones de no divulgación impuestas por la presente sección 16. Cada parte es responsable de todo acto y omisión de sus Representantes. Las obligaciones mencionadas no restringen a ninguna de las partes para divulgar Información Confidencial de la otra parte para cumplir con la orden o requerimiento de una corte, agencia administrativa, o cualquier otro cuerpo gubernamental, considerando que la Parte requerida para hacer dicha divulgación haya dado una notificación razonable a la otra Parte para habilitarlos para disputar dicha orden o requerimiento. The restrictions set forth in this Section 16 will survive the termination or expiration of this Agreement. - -**16.3** *Exclusiones*. Las restricciones expuestas en la sección 16.2 no aplicarán con respecto a cualquier Información Confidencial que: (i) fuese o se hiciera de conocimiento público sin que fuese culpa de la parte receptora; (ii) fuese bien conocida o se hiciera bien conocida para la parte receptora sin restricciones confidenciales o propietarias desde una fuente diferente a la parte divulgante quien tiene derecho a divulgarla: (iii) se apruebe por la parte divulgante para la divulgación sin restricciones a través de un documento escrito que firme un dirigente debidamente autorizado de dicha parte divulgante; o (iv) la Parte receptora desarrolle independientemente sin acceso a o uso de la Información Confidencial de la otra Parte. - -**17. Plazo y terminación.** - -**17.1** *Plazo del* *Acuerdo*. El presente acuerdo comienza en la Fecha de Entrada en Vigor del mismo y continuará en efecto hasta que alguna de las Partes lo termine de acuerdo con la presente sección 17. Si el presente acuerdo se termina antes de la caducidad o terminación de un Plazo de Susctipción, entonces cualquier Formato de Compra permanecerá en vigor de acuerdo con las condiciones de este Acuerdo. - -**17.2** *Terminación por Conveniencia*. Cada Parte podrá terminar un Formato de Compra con o sin causa, posterior a haber otorgado una noticia por escrito de por lo menos treinta (30) días previa al final del Plazo de Suscripción entonces actual. - -**17.3** *Terminación por Incumplimiento Sustancial*. Cualquiera de las Partes puede terminar el presente Acuerdo en forma inmediata previa notificación si la otra Parte incumple una obligación esencial conforme a lo dispuesto en el presente Acuerdo y no puede subsanar el incumplimiento dentro de los treinta (30) días desde la fecha en que recibe la notificación. Cada parte se reserva el derecho de terminar el presente Acuerdo inmediatamente al momento de recibir notificación escrita, pero sin dar a la otra Parte un periodo de tiempo para subsanamiento, si el Cliente viola cualquiera de las condiciones de este acuerdo que se relacionen con la propiedad intelectual de GitHub (incluyendo el cumplimiento de Cliente con el subsidio de la licencia y con cualquier restricción de la misma) o con la Información Confidencial de Cualquiera de las Partes. - -**17.4** *Efecto de Terminación; Supervivencia.* Cuando el presente Acuerdo caduque o termine, el Ciente podrá no ejecutar Formatos de Compra adicionales; sin embargo, el Acuerdo permanecerá en plena vigencia para el resto de los Formatos de Compra activos. Cuando un Formato de Compra caduca o termina, con respecto a este: (i) el Plazo de Suscripción para cualquier Software terminará inmediatamente; (ii) el Cliente ya no tendrá el derecho de utilizar el Software y cualquier Licencia de Suscripción otorgada en el Formato de Compra dejará de existir automáticamente desde la fecha de caducidad o terminación; (iii) si se debiera cualquier cuota antes de la terminación, el Cliente deberá pagarla inmediatamente; (iv) el cliente deberá destruir todas las copias del Software que estén en su posesión o control, así como certificar por escrito a GitHub de que ésto se ha hecho, y (v) cada Parte regresará inmediatamente (o, si la otra parte así lo solicita, destruirá) toda Información Confidencial que pertenezca al otro. Sin perjuicio de lo anterior, el Cliente podrá continuar accediendo al Software para migrar sus datos por noventa (90) días después de la terminación o caducidad del presente Acuerdo o de un Formato de Compra; sin embargo, el Cliente no deberá utilizar el Software como productivo durante este tiempo. Cualquier término o sección que por su naturaliza deba sobrevivir razonablemente, sobrevivirá a la caducidad o terminación del presente Acuerdo o de un Formato de Compra. - -**18. General Provisions.** - -**18.1** *Cumplimiento con las Leyes y Regulaciones.* El cliente cumplirá con todas las leyes y regulaciones aplicables, incluyendo, mas no limitándose a aquellas de empleo y protección de datos en su uso de los Productos. - -**18.2** *Consideraciones de Protección de Datos para el uso de GitHub Insights y Learning Lab para Enterprise Server.* Si el uso que pretende dar el Cliente a GitHub Insights o Learning Lab para Enterprise Server involucra el procesamiento de datos personales, será solo el Cliente que determine si se debe completar una evaluación de impacto para la protección de datos o no, o de otra manera, cómo asegurar el análisis legal formal del uso que el Cliente planea tener. A criterio exclusivo del cliente, ya sea usar GitHub Insights o Learning Lab for Enterprise Server para procesar los datos de los empleados y/o usuarios del cliente, y si el cliente lo hace, el cliente es el único responsable de llevar a cabo dicho procesamiento de conformidad con la legislación aplicable. - -**18.3** *Legislación Aplicable; Sede* Para los clientes domiciliados en los Estados Unidos, Canadá, México, o cualquier país en América Central o del Sur, o el Caribe (el "Continente Americano"), el presente Acuerdo se regirá e interpretará de acuerdo con las leyes del Estado de California, como si se ejecutaran íntegramente dentro de dicho estado y sin dar efecto a los principios de conflicto de leyes. Para dichos Clientes, cualquier acción o procedimiento legal que se derive del presente Acuerdo se llevará acabo exclusivamente en las cortes federales o estatales del Distrito del Norte de California y de las partes que aquí consienten la jurisdicción personal y la sede en ésta. Si la sede principal del Cliente se encuentra fuera de América, el presente Acuerdo se regirá por las leyes de Irlanda, cualquier procedimiento o acción legal que surja del presente Acuerdo se presentará exclusivamente ante las cortes ubicadas en Dublín, y por el presente las Partes convienen competencia y jurisdicción personal de dichos tribunales. Las partes acuerdan expresamente que no se aplicarán a este Acuerdo la Convención de las Naciones Unidas sobre Contratos de Compraventa Internacional de Bienes y la Ley Uniforme de Transacciones Electrónicas. Sin perjuicio de lo anterior, GitHub podrá presentar una reclamación para obtener una compensación equitativa en cualquier corte con la jurisdicción adecuada. - -**18.4** *Usuarios del Gobierno.* Los Productos y Documentación se desarrollaron íntegramente con fondos privados y se consideran "Software Computacional Comercial" y "Documentación de Software Computacional Comercial" de acuerdo a lo descrito en las Regulaciones de Adquisición Federal 12.212 y 27.405-3, y en el Suplemento de Regulación Para Adquisición Federal de Defensa 227.7202-3. Los productos se licencian al usuario final del Gobierno de los Estados Unidos como software computacional restringido y datos de derechos limitados. Ningún dato técnico ni software informático se desarrolla conforme a lo dispuesto en el presente Acuerdo. Cualquier uso, divulgación, modificación, distribución o reproducción de los Productos o la Documentación por parte del Gobierno de los Estados Unidos o sus contratistas se encuentra sujeto a las restricciones descritas en el presente Acuerdo. Cualquier otro uso está prohibido. - -**18.5** *Exportar.* Los productos están sujetos a exportación y a restricciones de sanciones administradas por el Gobierno de los EE.UU. y restricciones de importaciones por tarte de ciertos gobiernos extranjeros, y el Cliente deberá cumplir con las leyes y regulaciones aplicables para importaciones y exportaciones cuando éste utilice los Prodcutos. y las restricciones de importación de ciertos gobiernos extranjeros, y el Cliente cumplirá con todas las leyes y reglamentaciones de exportación e importación aplicables para el uso de los Productos por parte del Cliente. El cliente no deberá realizar ni permitir a cualquier parte la eliminación o exportación desde los Estados Unidos o permitir la exportación o re-exportación de cualquier parte de los Productos o cualquier producto directo de estos: (i) en (o a cualquier persona nacional o residente de) cualquier país o territorio prohibido o que apoye el terrorismo; (ii) a cualquiera en la Lista o Tabla de Pedidos Denegados de Entidades del Departamento de Comercio de los EE.UU. a cualquiera bloqueado de acuerdo con las reglas administradas por la Oficina de Control de Bienes Extranjeros de los EE.UU., Incluyendo a cualquiera en la lista de Nacionales Especialmente Designados o entidades de "Gobierno" sancionadas, o a cualquiera sujeto a otras listas aplicables de personas prohibidas o sancionadas; (iii) a cualquier país o territorio en el cual estas exportaciones o re-exportaciones estén prohibidas, o en las cuales el gobierno de los EE.UU. o cualquier agencia del mismo requiera licencia o aprobación; o (iv) de otra forma, se encuentre en violación de cualquier exportación, sanciones, o restricciones de importación, leyes o regulaciones de cualquier autoridad o agencia externa o de los EE.UU. Commerce Department’s Entity List or Table of Denial Orders, anyone blocked pursuant to rules administered by the U.S. Office of Foreign Assets Control, including anyone on the List of Specially Designated Nationals or sanctioned country “Government” entities, or anyone subject to other applicable prohibited or sanctioned persons lists; (iii) to any country or territory to which such export or re-export is restricted or prohibited, or as to which the U.S. government or any agency thereof requires an export license or other governmental approval at the time of export or re-export without first obtaining such license or approval; or (iv) otherwise in violation of any export, sanctions, or import restrictions, laws or regulations of any United States or foreign agency or authority. El cliente representa y garantiza que no está ubicado en o bajo el control de, o es un residente nacional de cualquier país o territorio prohibido o de cualquier entidad en la lista de partes prohibidas. GitHub Enterprise Server es un aplicativo virtual auto-hospedado que puede ejecutarse dentro del centro de datos propio del Cliente o en una nube privada virtual. Como tal, GitHub Enterprise Server puede utilizarse para almacenar ITAR u otro tipo de información controlada por exportación. Sin embargo, el Cliente es responsable de garantizar tal cumplimiento. El cliente reconoce y acuerda que los Productos se restringen de su uso para el diseño o desarrollo de armamento nuclear, químico o biológico o tecnología de misiles sin los permisos previos requeridos por el gobierno de los EE.UU. government. - -**18.6** *No Habrá Publicidad sin Permiso.* GitHub Podrá identificar al Cliente como un cliente subsecuente de otros clientes o prospectos de clientes. Sin embargo, GitHub no puede usar el nombre o el logo del Cliente en ninguna publicidad o material de marketing sin el permiso del Cliente. - -**18.7** *Asignación*. Ninguna de las Partes puede asignar o de otro modo transferir el presente Acuerdo, ni total ni parcialmente, sin previo consentimiento escrito de la otra Parte, dicho consentimiento no será retenido injustificadamente y cualquier intento de hacerlo será nulo y sin efecto, salvo que GitHub pueda asignar el presente Acuerdo en su totalidad, previa notificación a la otra parte pero sin el consentimiento de la otra Parte, en conexión con una fusión, adquisición, reorganización corporativa o venta de todos o casi todos los negocios o activos de la parte que asigna. - -**18.8** *Notificaciones*. A menos que se indique lo contrario en el presente, cualquier notificación, solicitud, demanda u otra comunicación conforme a lo dispuesto en el presente Acuerdo se debe realizar por escrito (se acepta el correo electrónico), debe mencionar el presente Acuerdo y se considerará otorgada adecuadamente: (i) ante su recepción, si se entrega personalmente; (ii) un (1) día hábil tras la recepción de la confirmación por parte del destinatario, si es por correo electrónico; (iii) cinco (5) días hábiles luego de enviarse por correo registrado o certificado, con confirmación escrita de recepción y correo electrónico; o (iv) tres (3) días hábiles tras el depósito con un correo expreso reconocido internacionalmente y correo electrónico, con confirmación escrita de recepción. Las Notificaciones se pueden enviar a la(s) dirección(es) establecidas en el presente Acuerdo, a menos que una de las Partes notifique a la otra que esas direcciones cambiaron. - -**18.9** *Fuerza Mayor*. GitHub será excusado de la responsabilidad hasta el punto en que sea incapaz de ejecutar cualquier obligación conforme a lo dispuesto en el presente Acuerdo debido a causas extraordinarias más allá de su control razonable, incluidos los hechos fortuitos, los desastres naturales, las huelgas, los disturbios, los bloqueos, los actos de guerra, las epidemias, o las fallas eléctricas, en las telecomunicaciones o en las redes. - -**18.10** *Proveedores Independientes*. Las Partes son proveedores independientes del otro con respecto al objeto del presente Acuerdo. Nada de lo dispuesto en el presente Acuerdo será considerado o interpretado de forma tal que dé lugar a la creación de una asociación legal, sociedad, empresa mixta, empleo, agencia, fiduciaria u otra relación similar entre las Partes, y ninguna de las Partes puede vincular a la otra por contrato. - -**18.11** *Renuncia*. Solo podrá renunciarse a las obligaciones de las partes bajo este acuerdo de manera escrita y firmada por un representante autorizado de la otra Parte, y dicha renuncia tomará efecto únicamente con respecto a la obligación específica descrita. Ninguna demora o falta de una de las Partes en relación a este Acuerdo en el ejercicio de algún derecho según este documento obrará como renuncia a dicho derecho, y el ejercicio único o parcial de estos derechos no imposibilitará otro ejercicio al respecto o el ejercicio de cualquier derecho según este documento por ley o normas de equidad. - -**18.12** *Acuerdo Íntegro*. El presente acuerdo, incluyendo cada Formato de Compra y SOW, constituye todo el acerudo y entendimiento de las Partes con respecto a su objeto, y sustituye todos los entendimientos y acuerdos contemporáneos previos, ya sean orales o por escrito, entre las Partes con respecto a su objeto. Las condiciones de cualquier orden de compra, términos o condiciones escritos, o cualquier otro documento que el Cliente emita a GitHub el cual contenga condiciones diferentes, adicionales o que entran en conflicto con aquellas de este Acuerdo, SOW o de cualquier Formato de Compra se vetarán y dejarán sin efecto. - -**18.13** *Enmiendas; Orden de Precedencia*. GitHub se reserva el derecho de enmendar el presente Acuerdo en cualquier momento y actualizará los términos y condiciones del mismo en caso de que estas enmiendas se presenten. Los cambios al presente acuerdo entrarán en vigor en el aniversario del Plazo de Suscripción entonces actual del Cliente. En caso de que exista un conflicto entre el presente acuerdo y algun Formato de Compra, el último prevalecerá con respecto a esa compra únicamente. El presente Acuerdo y cualquier adenda, incluyendo los Formatos de Compra, deberán prevalecer y ninguna modificación, cambio o enmienda al presente vinculará a las Partes o sustituirá las condiciones de este Acuerdo a menos de que sea por escrito y esté debidamente firmado por el representante autorizado de cada Parte. - -**18.14** *Divisibilidad*. Si cualquier disposición del presente acuerdo se considera como ilegal, inválida o incumplible por parte de una jurisdicción de corte competente, dicha corte modificará o reformará el presente para dar tanto efecto como sea posible a dicha disposición. Cualquier disposición que no se pueda modificar o reformar de esta forma se considerará eliminada y las provisiones restantes del presente Acuerdo continuarán en pleno vigor y efecto. diff --git a/translations/es-XL/content/github/site-policy/github-enterprise-service-level-agreement.md b/translations/es-XL/content/github/site-policy/github-enterprise-service-level-agreement.md deleted file mode 100644 index fe1d9f9497..0000000000 --- a/translations/es-XL/content/github/site-policy/github-enterprise-service-level-agreement.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: GitHub Enterprise Service Level Agreement -redirect_from: - - /github-enterprise-cloud-addendum/ - - /github-business-cloud-addendum/ - - /articles/github-enterprise-cloud-addendum -versions: - free-pro-team: '*' ---- - -# GitHub Enterprise Service Level Agreement - -**Short version:** GitHub guarantees a 99.9% quarterly uptime commitment for the GitHub Enterprise Cloud service (the “**Service Level**” or “**SLA**”). If GitHub does not meet the SLA, then Customer will be entitled to a service credit to Customer’s account (“**Service Credits**”). - -For definitions of each Service feature (“**Service Feature**”) and to review historical and current Uptime, visit the [GitHub Status Page](https://www.githubstatus.com/). Capitalized terms used but not defined in this SLA have the meaning assigned in Customer’s applicable agreement. - -## Uptime Guarantee - -“**Uptime**” is the percentage of total possible minutes the Service was available in a given calendar quarter. GitHub commits to maintain at least 99.9% Uptime for the Service. The Uptime calculation for each Service Feature is described below (“**Uptime Calculation**”). If GitHub does not meet the SLA, Customer will be entitled to Service Credits based on the calculation below (“**Service Credits Calculation**”). Note, Downtime does not affect every customer at the same time or in the same way. - -| **Service Feature** | **Uptime Calculation** | **Definiciones** | **Service Credits Calculation** | -| --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | -| The **Service** includes the following Service Features:
    • Problemas
    • Pull Requests
    • Git Operations
    • API Requests
    • Webhooks
    • Pages
    • Acciones
    • Packages
    | (total minutes in a calendar quarter - Downtime) / total minutes in a calendar quarter | “**Downtime**” is a period of time where either (a) the error rate exceeds five percent (5%) in a given minute for any Service Feature or (b) the Service was unavailable as determined by a combination of GitHub's internal and external monitoring systems. | A Service Credits claim may be based on either (not both) of the following calculations:
    • 10% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime for that Service Feature was less than 99.9%, but greater than 99.0%.

      OR

    • 25% of the amount Customer paid for a Service Feature in a calendar quarter where the Uptime of that Service Feature was less than 99.0%.
    | | -| **Acciones** | (Total Triggered Executions – Unavailable Executions) / (Total Triggered Executions) x 100 | “**Total Triggered Executions**” is the total number of all Actions executions triggered by Customer in a calendar quarter.

    “**Unavailable Executions**” is the total number of executions within Total Triggered Executions which failed to run in a calendar quarter. An execution failed to run when the Actions history log did not capture any output five (5) minutes after the trigger was successfully fired. | Same as above | -| **Packages** | Transfers Uptime = same as Actions

    Storage Uptime = 100% - Average Error Rate*

    *The Uptime Calculation excludes public usage and storage transactions that do not count toward either Total Storage Transactions or Failed Storage Transactions (including pre-authentication failures; authentication failures; attempted transactions for storage accounts over their prescribed quotas). | “**Error Rate**” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). If the Total Storage Transactions in a given one-hour interval is zero, the error rate for that interval is 0%.

    “**Average Error Rate**” is the sum of Error Rates for each hour in a calendar quarter divided by the total number of hours in a calendar quarter. | Same as above | - -## Exclusiones -Excluded from the Uptime Calculation are Service Feature failures resulting from (i) Customer’s acts, omissions, or misuse of the Service including violations of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) factors outside GitHub's reasonable control, including force majeure events; or (iv) Customer’s equipment, services, or other technology. - -## Service Credits Redemption -If GitHub does not meet this SLA, Customer may redeem Service Credits only upon written request to GitHub within thirty (30) days of the end of the calendar quarter. Written requests for Service Credits redemption should be sent to [GitHub Support](https://support.github.com/contact). - -Service Credits may take the form of a refund or credit to Customer’s account, cannot be exchanged into a cash amount, are limited to a maximum of ninety (90) days of paid service per calendar quarter, require Customer to have paid any outstanding invoices, and expire upon termination of Customer’s agreement with GitHub. Service Credits are the sole and exclusive remedy for any failure by GitHub to meet any obligations in this SLA. diff --git a/translations/es-XL/content/github/site-policy/github-enterprise-subscription-agreement.md b/translations/es-XL/content/github/site-policy/github-enterprise-subscription-agreement.md deleted file mode 100644 index 1172659d9d..0000000000 --- a/translations/es-XL/content/github/site-policy/github-enterprise-subscription-agreement.md +++ /dev/null @@ -1,449 +0,0 @@ ---- -title: Acuerdo de suscripción de GitHub Enterprise -redirect_from: - - /articles/github-enterprise-agreement/ - - /articles/github-enterprise-subscription-agreement -versions: - free-pro-team: '*' ---- - -Fecha de entrada en vigor de la versión: 20 de julio de 2020 - -AL HACER CLIC EN EL BOTÓN "ACEPTO" O EN UN BOTÓN SIMILAR O AL UTILIZAR CUALQUIERA DE LOS PRODUCTOS (DEFINIDOS A CONTINUACIÓN), EL CLIENTE ACEPTA LOS TÉRMINOS Y CONDICIONES DEL PRESENTE ACUERDO. SI EL CLIENTE ACEPTA EL PRESENTE ACUERDO EN NOMBRE DE UNA PERSONA JURÍDICA, EL CLIENTE MANIFIESTA QUE TIENE LA CAPACIDAD LEGAL PARA VINCULAR A LA PERSONA JURÍDICA CON ESTE ACUERDO. - -Este Acuerdo aplica a las siguientes ofertas de GitHub, tal como se define a continuación (collectivamente, los **"Productos"**): - -- GitHub Enterprised (que contiene a GitHub Enterprise Server, el cual podrá incluir Software Complementario, y GitHub Enterprise Cloud) y GitHub One; - -- Cualquier Vista previa Beta; - -- Cualquier Soporte relacionado; y - -- Cualquier Servicio profesional relacionado. - -El presente Acuerdo incluye las siguientes Secciones y Apéndices, cada uno de las cuales se incorpora por referencia en este documento: - -* SECCIÓN 1: Términos y Condiciones generales; - -* SECCIÓN 2: Términos de la licencia del servidor de GitHub Enterprise; - -* SECCIÓN 3: Términos de servicio de GitHub Enterprise Cloud; - -* PRUEBA A: Definiciones. - -Si el Cliente compró cualquier Producto de un revendedor de GitHub autorizado, las siguientes Secciones de este Acuerdo se reemplazan por los términos que el Cliente acordó con el revendedor de GitHub: Sección 1.1 (Vigencia y Terminación); 1.2 (Pago); Sección 2.3 (Entrega); y Sección 2.4 (Verificación). - -## SECCIÓN 1: TÉRMINOS Y CONDICIONES GENERALES - -La presente Sección 1 establece los términos y condiciones aplicables a la compra y el uso de cualquiera de los Productos por parte del Cliente. Los términos en mayúscula que se utilizan pero no se definen en el cuerpo de este Acuerdo se definen en la Prueba A. - -### 1.1 Vigencia y Terminación. - -#### 1.1.1 Vigencia. - -El presente Acuerdo comienza en la Fecha de entrada en vigencia y continúa en efecto hasta ser rescindido por una de las Partes de acuerdo con la presente Sección 1.1. - -#### 1.1.2 Terminación por Conveniencia. Cancelación de la cuenta. - -Cualquiera de las Partes puede poner fin a un Formulario de pedidos del presente Acuerdo, sin causa alguna, con una notificación escrita al menos treinta (30) días antes del Término de suscripción vigente en ese momento. Si el Cliente elige poner fin a un Formulario de pedidos o a un Acuerdo, es responsabilidad del Cliente cancelar debidamente su cuenta con GitHub ingresando en Configuraciones en la barra de navegación global en la parte superior de la pantalla. GitHub no puede cancelar cuentas en respuesta a un correo electrónico o a una solicitud telefónica. - -#### 1.1.3 Terminación por Incumplimiento sustancial. - -Cualquiera de las Partes puede terminar el presente Acuerdo en forma inmediata previa notificación si la otra Parte incumple una obligación esencial conforme a lo dispuesto en el presente Acuerdo y no puede subsanar el incumplimiento dentro de los treinta (30) días desde la fecha en que recibe la notificación. Cada una de las Partes también se reserva el derecho de terminar este Acuerdo en forma inmediata previa notificación por escrito, sin darle a la otra Parte un período para subsanar el incumplimiento, como se indica a continuación: por GitHub, si el Cliente incumple cualquiera de los términos del presente Acuerdo en relación a la propiedad intelectual de GitHub (incluido el incumplimiento por parte del Cliente del otorgamiento de licencia o cualquier restricción de la licencia), o si la cuenta del Cliente ha sido suspendida por más de noventa (90) días; o por cualquiera de las Partes, si la otra Parte incumple sus obligaciones de confidencialidad dispuestas en la Sección 1.4. - -#### 1.1.4 Vigencia de la Terminación; Continuidad. - -Al momento de la terminación del presente Acuerdo, el Cliente no puede ejecutar Formularios de pedidos adicionales; sin embargo, el presente Acuerdo permanecerá en vigencia por el período restante de cualquier Formulario de pedidos activo. Cuando un Formato de Compra termina o caduca, con respecto a éste: (i) el Plazo de Suscripción para el Software y/o el Servicio finalizará inmediatamente; (ii) cualquier Licencia de Suscripción en el Formato de Compra finalizará automáticamente, y el Cliente ya no tendrá derecho de utilizar los Productos; (iii) si se debía cualquier Cuota antes de la terminación, el Cliente deberá pagarla inmediatamente; (iv) El Cliente deberá destruir todas las copias del Software en su posesión o control y certificar por escrito a GitHub que lo ha hecho; y (v) cada Parte regresará inmediatamente (o, si la contraparte lo solicita, destruirá) toda Información Confidencial que pertenezca al otro hasta donde el Servicio lo permita. Sin perjuicio de lo anterior, el Cliente puede continuar accediendo al Software para migrar sus datos y puede solicitar la migración de los datos en sus repositorios por hasta noventa (90) días después de la terminación o la caducidad del presente Acuerdo o de un Formulario de pedidos; sin embargo, el Cliente no puede usar el Software o el Servicio sobre una base de producción durante ese período de tiempo. Cualquier disposición que por su naturaleza debiera mantenerse razonablemente en vigencia continuará luego de la terminación o la caducidad del presente Acuerdo o de un Formulario de pedidos. - -### 1.2 Pago. - -#### 1.2.1 Tarifas. - -El Cliente acepta pagar las Tarifas por completo, desde el inicio sin deducciones ni compensaciones de ningún tipo, en Dólares estadounidenses. estadounidenses. El cliente debe pagar las Tarifas dentro de los treinta (30) días de la fecha de la factura de GitHub. Los importes a pagar conforme a lo dispuesto en el presente Acuerdo no son reembolsables, excepto como se describe en las Secciones 1.5.1 y 1.6.2. Si el cliente no cumple con el pago de las Cuotas a tiempo, GitHub se reserva el derecho, adicionalmente a tomar cualquier otra acción legal o equitativa, de (i) cobrar intereses sobre cantidades atrasadas con valor de 1.0% mensual o la tasa de interés más alta permitida por la ley, la que fuese menor, y cargar todos los gastos de recuperación, y (ii) terminar el Formato de Compra o SOW aplicable. El Cliente es el único responsable de todos los impuestos, tarifas, obligaciones y valoraciones gubernamentales (a excepción de los impuestos basados en los ingresos netos de GitHub) que se imponen o vencen en conexión con el presente Acuerdo. - -#### 1.2.2 Comprar Licencias de suscripción adicionales. - -El Cliente puede obtener Licencias de suscripción adicionales conforme a lo dispuesto en el presente Acuerdo enviando una solicitud a través del sitio web de GitHub o mediante su equipo de ventas. Si el Cliente compra las Licencias de suscripción adicionales, el Cliente debe pagar por ellas las Tarifas correspondientes vigentes en ese momento, prorrateadas por el saldo de la Vigencia de suscripción aplicable. Al momento de la renovación de las Licencias de suscripción del Cliente por otro Plazo de suscripción, GitHub facturará todas las Licencias de suscripción una sola vez al año excepto que se especifique lo contrario en un Formulario de pedidos. - -#### 1.2.3 Software Complementario. - -El software agregado está licenciado por usuario. Para evitar dudas y a menos que se estipule lo contrario en un formulario de pedidos, la cantidad de licencias de suscripción que el cliente tiene en un momento dado para el software del complemento debe ser igual a la cantidad de licencias de suscripción que el cliente tiene para los productos conforme a lo dispuesto en el presente acuerdo. Por ejemplo, si el Cliente quiere comprar una suscripción de Advanced Security y ya tiene Licencias de Suscripción para 100 Usuarios para los Productos, éste deberá comprar las Licencias de Suscripción para Advanced Security para 100 Usuarios. - -### 1.3 Servicios Profesionales. - -Al momento de la solicitud de Servicios profesionales por parte del Cliente, GitHub proporcionará una SOW detallando tales Servicios profesionales. GitHub realizará los Servicios profesionales que se describen en cada SOW. GitHub controlará la forma y los medios utilizados para llevar a cabo los Servicios profesionales y se reserva el derecho de determinar el personal asignado. GitHub puede utilizar a terceros para realizar los Servicios profesionales, siempre y cuando GitHub siga teniendo responsabilidad por sus actos y omisiones. El Cliente reconoce y acepta que GitHub conserva todos los derechos, títulos e intereses sobre cualquier cosa que se usa o se desarrolla en conexión con los Servicios profesionales, incluido el software, las herramientas, las especificaciones, las ideas, los conceptos, las invenciones, los procesos, las técnicas y las habilidades. En la medida en que GitHub entrega algo al Cliente mientras realiza los Servicios profesionales, GitHub garantiza al Cliente una licencia de plazo limitado no exclusiva, intransferible, multinacional y exenta de regalías para usar esos productos a entregar durante la vigencia de este Acuerdo, únicamente en conjunto con el uso del Servicio o el Software por parte del Cliente. - -### 1.4 Confidencialidad. - -Ninguna de las Partes utilizará la Información confidencial de la otra Parte, excepto de acuerdo con lo permitido en el presente Acuerdo. Cada una de las Partes acepta mantener de forma confidencial y proteger la Información confidencial de la otra Parte utilizando al menos el mismo grado de cuidado con el que protege la información propia de la misma naturaleza, pero en cualquier caso al menos a niveles razonables de cuidado. Ninguna de las Partes utilizará la Información confidencial de la otra Parte, excepto de acuerdo con lo permitido en el presente Acuerdo. Cada parte es responsable de todo acto y omisión de sus Representantes. Las obligaciones mencionadas no restringirán que una de las Partes divulgue la Información confidencial de la otra Parte en cumplimiento con un pedido o exigencia de la corte, de una agencia administrativa o de otro organismo gubernamental, siempre y cuando la Parte obligada a hacer dicha divulgación dé una notificación razonable a la otra Parte para habilitar a dicha Parte a objetar la orden o exigencia, excepto que la notificación esté prohibida por ley. Las restricciones establecidas en la presente Sección 1.4 continuarán en vigencia luego de la terminación o caducidad del presente Acuerdo. - -### 1.5 Defensa de Reclamaciones. - -Las Partes de defenderán mutuamente contra las reclamaciones de terceros, hasta el punto que se establece en la presente Sección 1.5 y pagarán la cantidad correspondiente de cualquier sentencia firme adversa resultante o convenio aprobado, pero solamente si se notifica de inmediato a la Parte demandada por escrito sobre la reclamación y tiene el derecho de controlar la defensa y cualquiera de sus convenios. La Parte defendida debe proveer a la Parte demandada toda la asistencia, la información y la autoridad que se solicita. La Parte demandada reembolsará a la otra Parte por los gastos de bolsillo razonables en que incurra al proveer asistencia y no resolverá ni hará ninguna admisión con respecto a un reclamo de terceros sin previo consentimiento escrito de la otra Parte, sin que sea indebidamente demorado o retenido. La presente Sección 1.5 describe las únicas compensaciones de las Partes y la responsabilidad total para dichas reclamaciones. - -#### 1.5.1 GitHub. - -GitHub defenderá al Cliente contra cualquier reclamación presentada por un tercero sin afiliación en la medida en que alegue que el uso autorizado del Servicio o el Software por parte del Cliente infringe un derecho de propiedad, una patente o un nombre comercial, o que malversa un secreto comercial de un tercero sin afiliación. Si GitHub es incapaz de resolver cualquiera de dichas reclamaciones bajo términos comercialmente razonables, podrá, como opción, ya sea: (i) modificar, reparar o reemplazar el Software o Servicio (como sea aplicable); o (ii) terminar la suscripción del Cliente y reembolsar cualquier cuota de suscripción pre-pagada sin utilizarse. GitHub no tendrá obligación alguna bajo la presente sección 1.5.1 sobre cualquier reclamación que surja por: (a) la modificación del Software o Servicio, o la combinación, operación, o uso del Software o Servicio con equipo, dispositivos, software, sistemas, o datos, diferentes a los expresamente autorizados en el presente Acuerdo (incluyendo la Documentación); (b) La incapacidad del cliente para dejar de utilizar el Software o Servicio después de haber recibido la notificación para hacerlo; (c) las obligaciones del Cliente descritas en la Sección 1.5.2; (d) los productos o servicios (incluyendo el uso del Software o Servicio) gratuitos que porporcione GitHub; o (e) el acceso o uso de las Vistas Previas Beta. A los fines de la obligación de GitHub conforme a lo dispuesto en la presente Sección 1.5.1, el Software y el Servicio incluyen componentes de código abierto que GitHub ha incorporado en ellos. - -#### 1.5.2 El Cliente. - -El Cliente defenderá a GitHub contra cualquier reclamación que presente un tercero sin afiliación que surja de las siguientes situaciones: (i) el Contenido del Cliente que carga al Software o al Servicio; (ii) el incumplimiento de este Acuerdo por parte del Cliente, incluida la vulneración de la confidencialidad por parte del Cliente o el incumplimiento de los términos de uso aceptable de GitHub; (iii) las Modificaciones del Cliente al Software; o (iv) cualquier equipo, dispositivo, software, sistemas o datos de marcas de terceros que el Cliente combina, opera o utiliza con el Software o el Servicio. - -### 1.6 Representaciones y Garantías; Exención; Limitaciones de Responsabilidad. - -#### 1.6.1 Garantía general. - -Cada una de las Partes manifiesta y garantiza a la otra Parte que tiene el poder legal y la autoridad para celebrar el presente Acuerdo, y que este Acuerdo y todos los Formularios de pedidos y SOW son concertados por un empleado o agente de dicha Parte con toda la autoridad necesaria para vincular a la Parte mencionada con los términos y condiciones del presente Acuerdo. - -#### 1.6.2 Garantías limitadas. - -**(i) Software.** GitHub garantiza que: (1) el software sin modificar, en el momento en que se pone a disposición del Cliente para su descarga, no contendrá o transmitirá ningún malware, virus, o gusanos informáticos (también conocidos como código informático o cualquier otra tecnología diseñada específicamente para alterar, inhabilitar o dañar el software, hardware, sistemas computacionales o red del Cliente); y que (2) por noventa (90) días a partir de que éste se puso a disposición para su descarga inicial, el Software sin modificaciones se apegará substancialmente a su Documentación. GitHub no garantiza que el uso que el cliente dé al Software será ininterrumpido, o que la operación de dicho software estará libre de errores. La garantía en la presente Sección 1.6.2(i) no se aplicará si el Cliente modifica o usa el Software de alguna forma que no está expresamente permitida por la Sección 2 y la Documentación. La única obligación de GitHub y la única compensación del Cliente, por cualquier incumplimiento de esta garantía será, a discreción y expensas de GitHub, (a) reparar el Software; (b) reemplazar el Software; o (c) terminar el presente Acuerdo con respecto al Software defectuoso y reembolsar las Tarifas pagadas anticipadamente sin uso por el Software defectuoso durante el Plazo de suscripción vigente en ese momento. - -**(ii) Servicios profesionales.** GitHub garantiza al Cliente que cualquier Servicio profesional que se desarrolla conforme a lo dispuesto en el presente Acuerdo se llevará a cabo de una forma profesional y eficiente por medio de personal adecuado y calificado. La única obligación de GitHub, y la única compensación del Cliente por el incumplimiento de esta garantía será, a elección y expensas de GitHub: (1) volver a realizar inmediatamente cualquier Servicio Profesional que no cumpla con esta garantía; o (2) si no se puede subsanar el incumplimiento, terminar la SOW y reembolsar las Cuotas pre-pagadas sin utilizar. - -#### 1.6.3 Descargo de responsabilidad. - -**(i) Términos generales.** Salvo que se estipule lo contrario en el presente Acuerdo, GitHub no ofrece ninguna otra garantía ni realiza manifestación de ningún tipo, y por el presente renuncia específicamente a cualquier otra garantía, ya sea explícita, implícita o reglamentaria, incluidas entre otras las garantías implícitas de comercialización, idoneidad para un propósito particular, de no incumplimiento, o cualquier otra garantía o condiciones que surjan durante las transacciones o costumbres del comercio. Ningún consejo o información, ya sea de forma oral o escrita que proporcione GitHub o que provenga de cualquier otro lugar generará ninguna garantía o condición que no esté expresamente estipulada en este Acuerdo. - -**(ii) Servicio.** GitHub proprociona el Servicio **"TAL CUAL"** y **"SEGÚN SU DISPONIBILIDAD"** sin garantías de cualquier tipo. Sin limitar esto, GitHub renuncia expresamente cualquier garantía, explícita, implícita o estatutaria, sobre el Servicio, incluyendo, sin limitarse a, cualquier garantía de comercialización, adecuación para un propósito en particular, título, seguridad, exactitud y de no incumplimiento. GitHub no garantiza que los Servicios cumplan con los requisitos del Cliente; que los Servicios no se interrumpan y sean oportunos, seguros o sin errores; que la información que se provee a través de los Servicios sea precisa, confiable o correcta; que cualquier defecto o error será corregido; que el Servicio estará disponible en cualquier momento o ubicación en particular; o que el Servicio se encuentra libre de virus u otros componentes dañinos. GitHub no será responsable por cualquier riesgo de pérdida que resulte de la descarga del Cliente y/o el uso de archivos, información, Contenido u otro material obtenido del Servicio. - -**(iii) Vista previa Beta.** El Cliente puede elegir utilizar la Vista previa Beta a su exclusivo criterio. Las Vistas previas Beta pueden no ser compatibles y pueden cambiarse en cualquier momento sin previo aviso. Las Vistas previas Beta pueden no ser tan confiables o no estar disponibles como el Servicio. Las Vistas previas Beta no están sujetas a las mismas medidas de seguridad y de auditoría a las que el Servicio se encuentra sujeto. GitHub no tendrá ninguna responsabilidad que surja de las Vistas previas Beta o que esté relacionado con ellas. **Usos de las Vistas previas Beta por parte del Cliente a su propio riesgo.** - -#### 1.6.4 Limitaciones de responsabilidad. - -**(i) Daños indirectos. Hasta el grado máximo que permita la ley, en ningún caso una de las partes será responsable ante la otra parte o ante terceros por daños indirectos, especiales, incidentales, punitivos o emergentes (incluida la pérdida de ganancias, ingresos o datos) o por el costo de obtener productos sustitutos que surjan de este Acuerdo o tengan relación con este Acuerdo, cualquiera sea su causa, ya sea que dicha responsabilidad surja de un reclamo conforme a un contrato, una garantía, un agravio (incluida la negligencia), una responsabilidad objetiva o de cualquier otro modo, y haya sido o no informada una parte de la posibilidad de dichos daños.** - -**(ii) Limitación de la Responsabilidad total. Hasta el grado máximo que permita la ley, en ningún caso la responsabilidad acumulada total de una de las partes conforme a lo dispuesto en el presente Acuerdo de todas las causales de acción legal y todas las teorías de responsabilidad excederá las Tarifas que el Cliente pagó realmente a GitHub durante los 12 meses anteriores a la reclamación que dio origen a dicha responsabilidad. Para los productos y los servicios (incluido el uso de los Productos) que se brindan gratis, la responsabilidad de GitHub se limita a los daños directos por hasta USD⁰5000,00. Para las Vistas previas Beta, la responsabilidad de GitHub se limita a los daños directos por hasta USD⁰500,00.** - -**(iii) Excepciones. Las exclusiones y limitaciones que se establecen en la presente sección 1.6.4 no se aplicarán a la responsabilidad que se genere por (1) la violación de una Parte a las obligaciones de confidencialidad descritas en la Sección 1.4 (con excepción de todas aquellas relacionadas con el Contenido (excluyendo el Contenido de GitHub), que permanecerán sujetas a las limitaciones de exclusión anteriormente citadas); (2) las obligaciones de defensa de una Parte descritas en la Sección 1.5; o (3) la falta de cumplimiento del Cliente con el subsidio de licencia o con las restricciones de la licencia descritas en las Secciones 2.1 y 2.2.** - -### 1.7 Licencias de suscripción. - -Las Licencias de suscripción se otorgan por Usuario y la misma Licencia de suscripción no puede ser utilizada por múltiples Usuarios. El Cliente puede reasignar una Licencia de suscripción a un nuevo Usuario solo después de noventa (90) días desde la última reasignación de esa misma Licencia de suscripción, excepto que la reasignación se deba a (i) la pérdida o la falla permanente del hardware, (ii) la terminación del empleo o el contrato del Usuario, o (iii) la readjudicación temporal de las Licencias de Suscripción para cubrir una ausencia del Usuario. Cuando el Cliente reasigna una Licencia de suscripción de un Usuario a otro, el Cliente debe bloquear el acceso del Usuario anterior a la Licencia de suscripción y a las Organizaciones del Cliente. - -### 1.8 Afiliados. - -Los Afiliados del Cliente están autorizados a usar el Software y el Servicio de acuerdo con el presente Acuerdo, siempre que el Cliente siga teniendo completa responsabilidad por su acceso y por el uso del Software y del Servicio. - -### 1.9 Soporte. - -GitHub proporcionará Soporte para el Software y el Servicio como se indica a continuación: - -#### 1.9.1 Soporte Estándar. - -GitHub proporcionará Soporte técnico estándar para el Software y el Servicio sin ningún cargo adicional veinticuatro (24) horas al día, cinco (5) días a la semana, excluidos los fines de semana y los feriados nacionales de los Estados Unidos. holidays. El Soporte estándar solo se ofrece por medio de tickets basados en la web a través del Soporte de GitHub y las solicitudes de Soporte deben ser iniciadas por un Usuario con el que el equipo de Soporte de GitHub pueda interactuar. - -#### 1.9.2 Ofertas de Soporte Optimizado. - -GitHub podrá proporcionar ofertas de soporte ampliado para el Software y los servicios (incluyendo aquellas para Soporte Premium, Premium Plus, y Soporte Directo de Ingeniería) de acuerdo con las [Condiciones de soporte](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise), y en el nivel de soporte, cuotas y término de la suscripción que se especifica en un Formato de Compra o SOW. - -#### 1.9.3 Exclusiones. - -GitHub hará los esfuerzos razonables para corregir cualquier error material y reproducible en el Software sobre el cual el Cliente notifica a GitHub. Sin embargo, GitHub no será responsable de proporcionar el Soporte cuando (i) alguien (que no sea GitHub) modifica el Software; (ii) el Cliente cambia su sistema operativo o su entorno de una forma que afecta negativamente al Software o a su rendimiento; (iii) el Cliente usa el Software de una forma diferente a la autorizada conforme a lo dispuesto en el presente Acuerdo o a la Documentación; o (iv) existe una negligencia o un uso indebido del Software por parte del Cliente. - -### 1.10 Derechos de propiedad intelectual. - -Como fue acordado entre las Partes, GitHub posee todos los derechos, títulos e intereses, incluidos todos los derechos de propiedad intelectual, sobre los Productos y para ellos. GitHub se reserva todos los derechos sobre los Productos y para ellos no otorgados expresamente al Cliente conforme a lo dispuesto en el presente Acuerdo. GitHub puede usar, modificar e incorporar a sus Productos, cualquier opinión, comentario o sugerencia que el Cliente pueda hacer o publicar en foros sin ninguna obligación hacia el Cliente. - -### 1.11 Retroalimentación. - -El Cliente puede proporcionar Retroalimentación a GitHub con respecto a los Productos. La retroalimentación es voluntaria y no es Información Confidencial del Cliente, incluso si se designa como tal. GitHub puede ejercer y explotar plenamente dicha Retroalimentación con el propósito de (i) mejorar la operación, funcionalidad y uso de las ofertas de productos existentes y futuras de GitHub; y (ii) publicación de estadísticas agregadas sobre la calidad de los Productos, siempre que no se utilicen datos en ninguna de estas publicaciones para identificar específicamente al Cliente, sus empleados o el código de software propietario del Cliente. - -### 1.12. Cumplimiento con las Leyes y Regulaciones. - -El cliente cumplirá con todas las leyes y regulaciones aplicables, incluyendo, entre otras, las leyes y regulaciones de protección de datos y empleo, en su uso de los productos. - -### 1.13 Disposiciones generales. - -#### 1.13.1 Legislación aplicable; Jurisdicción. - -Si la sede principal del cliente se encuentra en el Continente Americano, el presente Acuerdo se regirá por las leyes del estado de California y se interpretará de acuerdo a ellas sin dar efecto a los principios de conflicto de leyes, cualquier procedimiento o acción legal que surja del presente Acuerdo se presentará exclusivamente ante las cortes federales o estatales ubicadas en el Distrito Norte de California, y por el presente las Partes convienen competencia y jurisdicción personal de dichos tribunales. Si la sede principal del Cliente se encuentra fuera de América, el presente Acuerdo se regirá por las leyes de Irlanda, cualquier procedimiento o acción legal que surja del presente Acuerdo se presentará exclusivamente ante las cortes ubicadas en Dublín, y por el presente las Partes convienen competencia y jurisdicción personal de dichos tribunales. Las partes acuerdan expresamente que no se aplicarán a este Acuerdo la Convención de las Naciones Unidas sobre Contratos de Compraventa Internacional de Bienes y la Ley Uniforme de Transacciones Electrónicas. Sin perjuicio de cualquier disposición contraria anterior, GitHub puede presentar una reclamación para obtener una compensación equitativa en cualquier corte de jurisdicción competente. - -#### 1.13.2 Usuarios del Gobierno de los EE.⁰UU. Usuarios del Gobierno. - -Los Productos se desarrollaron exclusivamente con fondos privados y se consideran "Software informático comercial" y "Documentación de software informático comercial" según se indica en los Reglamentos Federales de Adquisición 12.212 y 27.405-3 y en el Suplemento del Reglamento Federal de Adquisición del Ministerio de Defensa 227.7202-3. Los Productos tienen licencia para el Usuario final gubernamental de los EE.⁰UU. como software informático restringido y datos de derechos limitados. Ningún dato técnico ni software informático se desarrolla conforme a lo dispuesto en el presente Acuerdo. Cualquier uso, divulgación, modificación, distribución o reproducción de los Productos o la Documentación por parte del Gobierno de los EE.⁰UU. o de sus contratistas está sujeto a las restricciones establecidas en el presente Acuerdo. Cualquier otro uso está prohibido. - -#### 1.13.3 Exportación. - -Los Productos están sujetos a las restricciones de exportación del Gobierno de los EE.⁰UU. y las restricciones de importación de ciertos gobiernos extranjeros, y el Cliente cumplirá con todas las leyes y reglamentaciones de exportación e importación aplicables para el uso de los Productos por parte del Cliente. El Cliente no debe retirar o exportar desde los Estados Unidos ni permitir que terceros lo hagan, tampoco debe permitir la exportación o reexportación de alguna parte de los Productos o de algún producto directo de estos: (i) hacia (o a un ciudadano residente de) ningún país embargado o que apoya a grupos terroristas; (ii) a cualquier persona que se encuentre en la Lista de Órdenes Denegadas del Departamento de Comercio de los Estados Unidos o la Lista de Personas Especialmente Designadas del Departamento del Tesoro de los EE.⁰UU.; (iii) a cualquier país en el cual dicha exportación esté restringida o prohibida, o en el cual el gobierno o cualquiera de sus agencias exige una licencia de exportación u otra aprobación gubernamental en el momento de la exportación o reexportación sin primero haber obtenido esa licencia o aprobación; o (iv) que de otra manera infrinja las restricciones, leyes o reglamentaciones de exportación o importación de cualquier agencia o autoridad de los Estados Unidos o extranjera. Commerce Department's Table of Denial Orders or U.S. Treasury Department's list of Specially Designated Nationals; (iii) to any country to which such export or re-export is restricted or prohibited, or as to which the U.S. government or any agency thereof requires an export license or other governmental approval at the time of export or re-export without first obtaining such license or approval; or (iv) otherwise in violation of any export or import restrictions, laws or regulations of any United States or foreign agency or authority. El Cliente manifiesta y garantiza que (a) el Cliente no se encuentra situado en un país prohibido ni es ciudadano, residente o se encuentra bajo el control de un país prohibido y que no se encuentra en ninguna lista partidaria prohibida y (b) ninguno de los datos del Cliente está controlado por el Reglamento Internacional sobre el Tráfico de Armas de los EE.⁰UU. International Traffic in Arms Regulations. El Cliente reconoce y acepta que se encuentra restringido el uso de los Productos para el diseño y el desarrollo de armas nucleares, químicas y biológicas o la tecnología de misiles sin permiso previo del Gobierno de los EE.⁰UU. Government. - -#### 1.13.4 Prohibición de hacer publicidad sin permiso. - -GitHub puede identificar al Cliente como un cliente para los clientes actuales y futuros. Sin embargo, GitHub no puede usar el nombre o el logo del Cliente en ninguna publicidad o material de marketing sin el permiso del Cliente. - -#### 1.13.5 Asignación. - -Ninguna de las Partes puede asignar o de otro modo transferir el presente Acuerdo, ni total ni parcialmente, sin previo consentimiento escrito de la otra Parte, dicho consentimiento no será retenido injustificadamente y cualquier intento de hacerlo será nulo y sin efecto, salvo que GitHub pueda asignar el presente Acuerdo en su totalidad, previa notificación a la otra parte pero sin el consentimiento de la otra Parte, en conexión con una fusión, adquisición, reorganización corporativa o venta de todos o casi todos los negocios o activos de la parte que asigna. - -#### 1.13.6 Notificaciones. - -A menos que se indique lo contrario en el presente, cualquier notificación, solicitud, demanda u otra comunicación conforme a lo dispuesto en el presente Acuerdo se debe realizar por escrito (se acepta el correo electrónico), debe mencionar el presente Acuerdo y se considerará otorgada adecuadamente: (i) ante su recepción, si se entrega personalmente; (ii) un (1) día hábil tras la recepción de la confirmación por parte del destinatario, si es por correo electrónico; (iii) cinco (5) días hábiles luego de enviarse por correo registrado o certificado, con confirmación escrita de recepción y correo electrónico; o (iv) tres (3) días hábiles tras el depósito con un correo expreso reconocido internacionalmente y correo electrónico, con confirmación escrita de recepción. Las Notificaciones se pueden enviar a la(s) dirección(es) establecidas en el presente Acuerdo, a menos que una de las Partes notifique a la otra que esas direcciones cambiaron. - -#### 1.13.7 Fuerza Mayor. - -GitHub será excusado de la responsabilidad hasta el punto en que sea incapaz de ejecutar cualquier obligación conforme a lo dispuesto en el presente Acuerdo debido a causas extraordinarias más allá de su control razonable, incluidos los hechos fortuitos, los desastres naturales, las huelgas, los disturbios, los bloqueos, los actos de guerra, las epidemias, o las fallas eléctricas, en las telecomunicaciones o en las redes. - -#### 1.13.8 Contratistas independientes. - -Cada una de las Partes es un contratista independiente con respecto al objeto del presente Acuerdo. Nada de lo dispuesto en el presente Acuerdo será considerado o interpretado de forma tal que dé lugar a la creación de una asociación legal, sociedad, empresa mixta, empleo, agencia, fiduciaria u otra relación similar entre las Partes, y ninguna de las Partes puede vincular a la otra por contrato. - -#### 1.13.9 Renuncia. - -Se puede renunciar a las obligaciones de una de las Partes según lo dispuesto en el presente Acuerdo solamente por escrito con la firma de un representante autorizado de la otra Parte. Ninguna demora o falta de una de las Partes en relación a este Acuerdo en el ejercicio de algún derecho según este documento obrará como renuncia a dicho derecho, y el ejercicio único o parcial de estos derechos no imposibilitará otro ejercicio al respecto o el ejercicio de cualquier derecho según este documento por ley o normas de equidad. - -#### 1.13.10 Acuerdo completo. - -El presente Acuerdo, junto con los Apéndices y cada Formulario de pedidos y SOW, representa el acuerdo completo y el entendimiento de las Partes con respecto a su objeto, y reemplaza a todos los acuerdos y entendimientos anteriores o contemporáneos, ya sean orales o escritos, entre las Partes con respecto a dicho objeto. Los términos de cualquier Orden de compra del Cliente, términos o condiciones escritas, u otro documento que el Cliente envíe a GitHub que contengan términos que sean diferentes de los términos del presente Acuerdo o que agreguen algo a este, cualquier Formulario de pedidos o SOW serán nulos y sin efecto. - -#### 1.13.11 Modificaciones; Orden de prelación. - -GitHub se reserva el derecho, a su exclusivo criterio, de modificar el presente Acuerdo en cualquier momento y actualizará este Acuerdo en el caso en que ocurran dichas modificaciones. GitHub notificará al Cliente sobre los cambios sustanciales al presente Acuerdo, tales como cambios en los precios, al menos 30 días antes de que el cambio entre en vigencia publicando un aviso en el Servicio. Para modificaciones no sustanciales, el uso continuo del Servicio por parte del Cliente representa la aceptación de nuestras revisiones sobre el presente Acuerdo. El Cliente puede visualizar todas las modificaciones al presente Acuerdo en nuestro repositorio [Site Policy](https://github.com/github/site-policy). En el caso en que exista algún conflicto entre los términos del presente Acuerdo y cualquier Formulario de pedidos o SOW, los términos del Formulario de pedidos o SOW prevalecerán solamente con respecto a ese Formulario de pedidos o SOW. - -#### 1.13.12 Aplicabilidad. - -Si una corte de jurisdicción competente considera que alguna disposición del presente Acuerdo es ilegal, nula o inaplicable, las Partes modificarán o reformarán el presente Acuerdo para darle el mayor efecto posible a esa disposición. Cualquier disposición que no se pueda modificar o reformar de esta forma se considerará eliminada y las provisiones restantes del presente Acuerdo continuarán en pleno vigor y efecto. - - -## SECCIÓN 2: TÉRMINOS DE LA LICENCIA DEL SERVIDOR GITHUB ENTERPRISE - -La presente Sección 2 detalla los términos aplicables al uso del Software por parte del Cliente. - -### 2.1 Otorgamiento de la Licencia. - -GitHub le otorga al Cliente una licencia de plazo limitado no exclusiva, intransferible, multinacional y exenta de regalías para instalar y usar el Software para los propósitos comerciales internos del Cliente durante el Plazo de suscripción aplicable, de acuerdo con la Documentación y solamente por el número de Licencias de suscripción establecidos en el Formulario de pedidos del Cliente. El Software incluye componentes autorizados por terceros a GitHub, incluido el software cuya licencia exige que GitHub facilite el código fuente para que esos componentes estén disponibles. El código fuente para dichos componentes se facilitará previa solicitud. Sin limitar lo anterior, esta licencia permite que el cliente descargue y ejecute la imagen del contenedor de la edición estándar de Microsoft SQL Server para los archivos de Linux ("**Imágenes de SQL Server**"), que solo se puede utilizar con el software como se documenta. El derecho del cliente a usar las imágenes de SQL Server finaliza cuando el cliente ya no tiene derechos para usar el software y el cliente debe desinstalar las imágenes de SQL Server cuando su derecho a usarlos finalice. Microsoft Corporation puede inhabilitar las imágenes de SQL Server en cualquier momento. - -### 2.2 Restricciones de las licencias. - -A excepción de lo expresamente permitido por ley o por la licencia correspondiente de terceros, el Cliente y sus Afiliados no deben ni deben permitir que terceros realicen lo siguiente: (i) otorgar sublicencias, vender, alquilar, ceder, transferir, asignar o redistribuir el Software; (ii) alojar el Software para el beneficio de terceros; (iii) divulgar o permitir a terceros el acceso al Software, a excepción de lo expresamente permitido en la presente Sección 2; (iv) hackear o modificar la Clave de la licencia o evitar o cambiar cualquier proceso de registro; (v) a excepción de las Modificaciones del Cliente, modificar o crear trabajos a partir del Software, o fusionar el Software con otro software; (vi) desmontar, descompilar, derivar cualquier ofuscación del código, o de otra manera practicar ingeniería inversa en el software o intentar obtener su código fuente, total o parcial; (vii) modificar, ocultar o eliminar cualquier notificación de los derechos de propiedad incluidos en el Software o la Documentación o sobre estos; o (viii) de otra manera usar o copiar el Software o la Documentación de una forma que no se encuentre expresamente permitida en el presente Acuerdo. - -### 2.3 Entrega. - -GitHub facilitará la Clave de la licencia al Cliente para descargar en un sitio web seguro protegido con contraseña. Todas las entregas conforme a lo dispuesto en la presente Sección 2 serán electrónicas. Para evitar dudas, el Cliente es responsable de la instalación de cualquier Software y reconoce que GitHub no tiene ninguna obligación de entrega adicional con respecto al Software después de la entrega de la Clave de la licencia. Cuando las actualizaciones estén disponibles, GitHub las facilitará para la descarga en el mismo sitio web. El Cliente debe Actualizar el Software sobre una base comercialmente razonable pero no menos de una (1) vez al año. El Cliente es responsable de mantener la confidencialidad de sus nombres de usuario y sus contraseñas. - -### 2.4 Verificación. - -A pedido de GitHub, el Cliente proporcionará de inmediato a GitHub un informe generado por el Software para verificar que el Cliente está usando el Software de acuerdo con el presente Acuerdo. GitHub facturará al Cliente por cualquier uso adicional, con vigencia a partir de la fecha en que su uso excedió los términos del presente Acuerdo. - -### 2.5 Actualizaciones; Lanzamientos. - -#### 2.5.1 Términos generales. - -GitHub facilitará al Cliente las Actualizaciones y Lanzamientos del Software en el mismo sitio web seguro donde el Cliente descargó el Software y la Clave de la licencia. - -#### 2.5.2 Lanzamientos compatibles. - -GitHub solamente dará Soporte un Lanzamiento dado del Software durante un (1) año desde la fecha del Lanzamiento original, o seis (6) meses desde la última Actualización del lanzamiento, lo que sea más prolongado. Si el Cliente requiere Soporte para Lanzamientos anteriores del Software, en ese caso el Cliente debe pagar por ese Soporte de acuerdo con los términos de un Formulario de pedidos o SOW convenidos mutuamente. - -### 2.6 Consideraciones sobre la Protección de Datos para el Uso de GitHub Insights y Learning Lab para Enterprise Server. - -Si el uso planificado del cliente de GitHub Insights o Learning Lab for Enterprise Server implica el procesamiento de datos personales, el cliente es el único responsable de determinar si completar o no una evaluación de impacto de protección de datos o el análisis legal formal del uso planificado del cliente. A criterio exclusivo del cliente, ya sea usar GitHub Insights o Learning Lab for Enterprise Server para procesar los datos de los empleados y/o usuarios del cliente, y si el cliente lo hace, el cliente es el único responsable de llevar a cabo dicho procesamiento de conformidad con la legislación aplicable. - - -### SECCIÓN 3: TÉRMINOS DE SERVICIO DE GITHUB ENTERPRISE CLOUD - -Tras la creación de una Cuenta corporativa y/o una Organización en el Servicio por parte del Cliente o por parte de GitHub en nombre del Cliente, la presente Sección 3 detalla los términos aplicables al uso del Servicio por parte del Cliente. - -### 3.1 Términos de la cuenta. - -#### 3.1.1 Controles de la cuenta. - -**(i) Usuarios.** El Cliente reconoce que los Usuarios conservan el control administrativo final sobre sus cuentas individuales y sobre el Contenido de las mismas. [Las Condiciones de Servicio Estándar de GitHub](/github/site-policy/github-terms-of-service) rigen la utilización del Servicio para los usuarios, con excepto lo relacionado con las actividades del usuario bajo la presente Sección 3. - -**(ii) Organizaciones.** El Cliente conserva el control administrativo final sobre cualquier Organización creada en nombre del Cliente y sobre el Contenido generado por el Usuario publicado en los repositorios dentro de su(s) Organización(es), sujetos a la presente Sección 3. La presente Sección 3 regirá el uso de la(s) Organización(es) del Cliente. - -#### 3.1.2 Requisitos de la cuenta. - -Para crear una cuenta, el Cliente debe adherirse a los siguientes puntos: - -**(i)** El Cliente no debe crear una cuenta para que la use cualquier persona menor de 13 años. Si GitHub se entera de que existe algún Usuario menor de 13 años, cancelará esa cuenta de Usuario de inmediato. Si el Cliente o su(s) Usuario(s) están ubicados en un país fuera de los Estados Unidos, la edad mínima de ese país puede ser mayor; en ese caso, el Cliente es responsable de cumplir con las leyes de ese país. - -**(ii)** Un Inicio de sesión de un Usuario no se debe compartir con múltiples personas. - -**(iii)** El cliente no deberá utilizar el Servicio (a) si este viola las leyes de sanción o control de exportaciones de los Estados Unidos o de cualquier otra jurisdicción aplicable, (b) si se ubica en o reside habitualmente en un país o territorio sujeto a sanciones generales administrades por la Oficina de Control de Bienes Extranjeros de los EE.UU. (OFAC, por sus siglas en inglés), o (c) si el Cliente es o está trabajando por parte de un [Nacional Especialmente Designado (SDN, por sus siglas en inglés)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) o una persona sujeta a bloqueos o prohibiciones de la parte denegada similares. Para obtener más información, consulte la [Política de Controles de Exportación de GitHub](/articles/github-and-export-controls). - -#### 3.1.3 Seguridad de la cuenta. - -El Cliente es responsable por lo siguiente: (i) todos los Contenidos publicados y las actividades que ocurran en su Cuenta corporativa; (ii) mantener la seguridad de sus credenciales de inicio de sesión de su cuenta; y (iii) de inmediato [notificar a GitHub](https://support.github.com/contact) al enterarse de cualquier uso no autorizado del Servicio o acceso a este a través de su cuenta. GitHub no será responsable de ninguna pérdida o daño que surja del incumplimiento por parte del Cliente con la presente Sección 3.1.3. - -#### 3.1.4 Términos adicionales. - -En algunas situaciones, pueden aplicarse términos de terceros al uso del Servicio por parte del Cliente. Por ejemplo, el Cliente puede ser miembro de una Organización con sus propios términos o acuerdos de licencia; el Cliente puede descargar una aplicación que se integre con el Servicio; o el Cliente puede usar el Servicio para autenticarse a otro servicio. Mientras el presente Acuerdo es el acuerdo completo de GitHub con el Cliente, los términos de las otras partes rigen sus relaciones con el Cliente. - -#### 3.1.5 Términos del Gobierno federal de los EE.⁰UU. Términos del Gobierno federal de los EE.⁰UU. - -If Customer is a U.S. federal government agency or otherwise accessing or using any portion of the Service in a government capacity, the [U.S. Federal Government Amendment](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) applies, and Customer agrees to its provisions. - -### 3.2 Cumplimiento con las leyes; Uso aceptable; Privacidad. - -#### 3.2.1 Cumplimiento con las leyes y regulaciones. -El uso del Servicio por parte del Cliente no debe infringir las leyes vigentes, incluidas las leyes de propiedad intelectual o el nombre comercial, las leyes de control de las exportaciones o las regulaciones en su jurisdicción. - -#### 3.2.2 Uso aceptable. -El uso que el Cliente dé al servicio deberá cumplir con las [Políticas de Uso Aceptado de GitHub](/articles/github-acceptable-use-policies) y los [Lineamientos de la Comunidad de GitHub](/articles/github-community-guidelines). El Cliente no debe usar el Servicio en ninguna jurisdicción si contiene Contenidos o actividades ilegales, obscenos, ofensivos o fraudulentos, tales como promover o causar daño, vulnerar la integridad o la seguridad de una red o sistema o interferir en ellos, evadir filtros, enviar mensajes no solicitados, abusivos o engañosos, virus o códigos perjudiciales, o socavar los derechos de terceros. - -#### 3.2.3 Privacidad. -[La Declaración de Privacidad de GitHub](/articles/github-privacy-statement) y la [Adenda de Protección de Datos de GitHub](/github/site-policy/github-data-protection-addendum) proporciona notificación detallada de las prácticas de privacidad y uso de datos así como de las obligaciones de seguridad y procesamiento de GitHub con respecto a los Datos Personales del Cliente. Cualquier persona, entidad o servicio que recolecte datos de este servicio deberá cumplir con la [Declaración de Privacidad de GitHub](/articles/github-privacy-statement), particularmente con respecto a la recolección de Información Personal de los Usuarios (como se define en la Declaración de Privacidad de GitHub). Si el Cliente recopila cualquier Información personal del usuario proveniente de GitHub, el Cliente solamente la usará para el propósito por el cual el Usuario externo lo autorizó. El Cliente asegurará razonablemente dicha Información personal y el Cliente responderá de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" de GitHub o de Usuarios externos. - -### 3.3 Responsabilidad del Contenido; Propiedad; Derechos de la licencia. - -#### 3.3.1 Responsabilidad para el Contenido generado por el usuario. -El Cliente puede crear o cargar Contenido generado por el Usuario mientras usa el Servicio. El Cliente es el único responsable de cualquier Contenido generado por el Usuario que se publique, cargue, vincule o ponga a disposición de cualquier otra manera a través del Servicio, independientemente de la forma de ese Contenido generado por el Usuario. GitHub no es responsable de ninguna visualización pública o uso indebido del Contenido generado por el Usuario. - -#### 3.3.2 Propiedad del Contenido, Derecho a publicar y Otorgamientos de licencia. - -**(i)** El Cliente mantiene la propiedad sobre el Contenido del Cliente que el Cliente crea o posee. El Cliente reconoce lo siguiente: (a) que es responsable del Contenido del Cliente, (b) que solo enviará el Contenido del Cliente que el Cliente tenga derecho a publicar (incluido el Contenido generado por el Usuario o por terceros) y (c) que el Cliente cumplirá plenamente con cualquier licencia de terceros relacionada con el Contenido del Cliente que el Cliente publica. - -**(ii)** El Cliente otorga los derechos establecidos en las Secciones 3.3.3 a 3.3.6, gratuitos y para los fines identificados en esas secciones hasta el momento en que el Cliente elimine el Contenido del Cliente de los servidores de GitHub, excepto para los Contenidos que el Cliente haya publicado de forma pública y que los Usuarios externos hayan bifurcado, en cuyo caso la licencia se perpetúa hasta el momento en que todas las Bifurcaciones del Contenido del Cliente se hayan eliminado de los servidores de GitHub. Si el Cliente carga Contenido del Cliente que ya viene con una licencia y le otorga a GitHub los permisos que necesita para ejecutar el Servicio, no se requiere ninguna licencia adicional. - -#### 3.3.3 Otorgamiento de licencia a GitHub. -El Cliente le otorga a GitHub el derecho a almacenar, analizar y mostrar el Contenido del Cliente y de hacer copias incidentales solo como sea necesario para proporcionar el Servicio. Esto incluye el derecho a copiar el Contenido del Cliente en la base de datos de GitHub y a hacer copias de seguridad; mostrarle el Contenido del Cliente al Cliente y a quienes el Cliente decida; analizar el Contenido del Cliente en un índice de búsqueda o, de lo contrario, analizarlo en los servidores de GitHub; compartir el Contenido del Cliente con Usuarios externos con los cuales el Cliente elige compartirlo; y reproducir el Contenido del Cliente, en el caso de que se trate de música o vídeo. Estos derechos se aplican tanto a los Repositorios privados como a los públicos. Esta licencia no le otorga a GitHub el derecho a vender el Contenido del Cliente o a distribuirlo o utilizarlo por fuera del Servicio. El Cliente le otorga a GitHub los derechos que necesita para usar el Contenido del Cliente sin atribución y para hacer las adaptaciones razonables del Contenido del Cliente como sea necesario para proporcionar el Servicio. - -#### 3.3.4 Otorgamiento de la licencia a Usuarios externos. -**(i)** Cualquier Contenido que el Cliente publica de forma pública, incluidas propuestas, comentarios y contribuciones a los repositorios de Usuarios externos, puede ser visto por otras personas. El Cliente acepta permitir que Usuarios externos vean y bifurquen los repositorios del Cliente cuando configura sus repositorios para que se vean públicamente. - -**(ii)** Si el Cliente configura sus páginas y repositorios para que se vean públicamente, el Cliente les otorga a los Usuarios externos una licencia no exclusiva y multinacional para usar, mostrar y ejecutar el Contenido del Cliente a través del Servicio y para reproducir el Contenido del Cliente únicamente en el Servicio, según se permite a través de la funcionalidad que proporciona GitHub (por ejemplo, a través de la Bifurcación). El cliente puede otorgar más derechos sobre el contenido del mismo si el éste [adopta una licencia](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Si el Cliente está cargando Contenido del Cliente que no creó ni posee, el Cliente es responsable de asegurar que el Contenido del Cliente que carga cuente con licencia conforme a los términos que otorgan estos permisos a los Usuarios externos. - -#### 3.3.5 Contribuciones conforme a la Licencia del repositorio. -Siempre que el Cliente hace una contribución a un repositorio que contiene un aviso de licencia, el Cliente licencia tal contribución conforme a los mismos términos y acepta que tiene derecho a licenciar dicha contribución conforme a esos términos. Si el Cliente tiene otro acuerdo para licenciar sus contribuciones conforme a términos diferentes, tal como un acuerdo de licencia de colaborador, ese acuerdo prevalecerá. - -#### 3.3.6 Derechos morales. -El Cliente conserva todos los derechos morales sobre el Contenido del Cliente que carga, publica o envía a cualquier parte del Servicio, incluidos los derechos de integridad y atribución. Sin embargo, el Cliente renuncia a estos derechos y acepta no ejercerlos contra GitHub, únicamente, para permitir que GitHub haga uso razonable de los derechos otorgados en la Sección 3.3, pero no de otra manera. - -### 3.4. Repositorios privados. - -#### 3.4.1 Control. -El Cliente es responsable de administrar el acceso a sus Repositorios privados, incluidas las invitaciones, el control administrativo de las Organizaciones y los equipos, y la anulación del acceso. - -#### 3.4.2 Confidencialidad. -GitHub considera que el Contenido del Cliente en los Repositorios privados del Cliente constituye Información confidencial del Cliente. GitHub protegerá y mantendrá de forma estrictamente confidencial el Contenido del Cliente en sus Repositorios privados de acuerdo con la Sección 1.4. - -#### 3.4.3 Acceso. -GitHub solo puede acceder a los Repositorios privados del Cliente (i) con el consentimiento y el conocimiento del Cliente, por razones de asistencia o (ii) cuando se requiere el acceso por razones de seguridad. El Cliente puede decidir habilitar más acceso a sus Repositorios privados. Por ejemplo, el Cliente puede habilitar varios servicios o funciones de GitHub que requieren derechos adicionales sobre el Contenido del Cliente en los Repositorios privados. Estos derechos pueden variar según el servicio o la función, pero GitHub continuará considerando el Contenido del Cliente en los Repositorios privados del Cliente como Información confidencial. GitHub proporcionará una explicación sobre esos derechos si esos servicios o funciones requieren más derechos de los que necesita para proporcionar el Servicio. - -#### 3.4.4 Exclusiones. -Si GitHub tiene razones para creer que el Contenido de un Repositorio privado incumple la ley o este Acuerdo, GitHub tiene derecho a acceder, revisar y eliminar ese Contenido. Además, GitHub puede ser obligado por ley a divulgar el Contenido de los Repositorios privados del Cliente. A menos que los requisitos previstos por la ley indiquen lo contrario o que sea en respuesta a una amenaza de seguridad u otro riesgo para la seguridad, GitHub dará aviso de tales acciones. - -### 3.5. Notificaciones de propiedad intelectual. - -#### 3.5.1 Derechos de GitHub sobre el Contenido. -La apariencia del Servicio es propiedad intelectual de © GitHub, Inc. Todos los derechos reservados. El Cliente no puede duplicar, copiar o volver a usar ninguna parte de los elementos o conceptos de HTML/CSS, Javascript o de diseño visual sin autorización expresa por escrito de GitHub. - -#### 3.5.2 Violación de la propiedad intelectual y la política de DMCA. - -Si el Cliente es propietario de los derechos de autor y determina que el Contenido del Servicio viola dichos derechos, éste podrá contactar a GitHub de acuerdo con la [Política sobre la Ley de Derechos de Autor de la Era Digital](https://github.com/contact/dmca) de GitHub si le notifica a través de su [Formato DMCA](https://github.com/contact/dmca-notice) o si envía un mensaje de correo electrónico a copyright@github.com. - -#### 3.5.3 Nombres comerciales y logos de GitHub. - -Si el Cliente desea usar los nombres comerciales de GitHub, debe seguir todas las pautas de nombres comerciales de GitHub, incluidas las que se encuentran en la [Página de logos y uso de GitHub](https://github.com/logos). - -### 3.6 Suspensión. -En cualquier momento, GitHub tiene derecho a suspender el acceso a todo el Servicio o a cualquier parte de este, incluido eliminar Contenido, por incumplimiento del presente Acuerdo o para proteger la integridad, operatividad y seguridad del Servicio, lo cual entrará en vigor de inmediato, con notificación, a menos que dicha notificación esté prohibida por ley o por un procedimiento legal o que impida la prevención de un daño inminente al Servicio o a cualquier tercero. Normalmente, GitHub envía las notificaciones en forma de mensajes emergentes o por correo electrónico en el momento de la suspensión o con anterioridad. GitHub personalizará, a su criterio y de buena fe, cualquier suspensión que sea necesaria para preservar la integridad, operatividad y seguridad del Servicio. - -### 3.7 Service Level Agreement. - -GitHub’s quarterly uptime commitment for the Service is provided in the [Enterprise Service Level Agreement](/github/site-policy/github-enterprise-service-level-agreement). Customer will be entitled to a service credit if GitHub does not meet its service level. - -### 3.8 Cambios del servicio. -GitHub cambia el Servicio mediante Actualizaciones y adición de nuevas características. GitHub se reserva el derecho, sujeto a la Sección 3.7, de modificar o interrumpir el Servicio (o cualquier parte de este) en cualquier momento, de forma temporal o permanente, con o sin notificación. - -### 3.9 Características Adicionales del Servicio. - -Algunas características de servicio pueden estar sujetas a términos adicionales como se establece en los [términos de producto adicionales de GitHub](/github/site-policy/github-additional-product-terms). Al acceder o utilizar estas características, el cliente acepta las condiciones de producto adicionales de GitHub. - -## PRUEBA A: DEFINICIONES - -**"Usuario activo"** se refiere a un Usuario que trata de acceder al Servicio en el momento de una Interrupción. - -**"Software agregado"** se refiere a Advanced Security, Insights, Learning Lab for Enterprise Server y otros productos adicionales de software agregado que GitHub puede ofrecer de vez en cuando. - -**"Seguridad avanzada"** se refiere a la característica de software que permite que el cliente identifique vulnerabilidades de seguridad mediante un análisis de código semántico personalizable y automatizado. - -**"Subsidiaria"** se refiere a cualquier entidad que controla directa o indirectamente, que es controlada o se encuentra bajo el control normal de una parte, donde "control" significa tener más del cincuenta por ciento (50⁰%) de la propiedad o el derecho a dirigir la administración de la entidad. - -**“Todos los usuarios”** se refiere, en conjunto, a los Usuarios del Cliente y los Usuarios externos que usan el Servicio. - -**“Américas”** se refiere a los Estados Unidos, Canadá, México o un país de América Central o América del Sur o el Caribe. - -**"Vistas previas beta"** se refiere al software, los servicios o las funciones identificadas como alfa, beta, vista previa, acceso temprano o evaluación, o a las palabras o frases con significados similares. - -**"Información confidencial"** se refiere a toda la información no pública divulgada por cualquiera de las Partes a otros, ya sea por escrito, en forma oral o por otros medios, designada como confidencial o que la Parte receptora sabe o razonablemente debe saber, conforme a las circunstancias en torno a la divulgación y la naturaleza de la información, que es confidencial para la Parte reveladora. Para evitar dudas, ningún Contenido publicado en el Servicio se considerará Información confidencial excepto el Contenido del Cliente almacenado únicamente en los Repositorios privados del Cliente. La Información confidencial no incluye ninguna información que (i) era de conocimiento público o se dio a conocer públicamente por motivos ajenos a la parte receptora; (ii) era legítimamente conocida o se dio a conocer en forma legítima a la Parte receptora sin restricciones de propiedad o confidencialidad por parte de una fuente que no es la parte reveladora y que tiene derecho a divulgarla; (iii) es aprobada por la Parte reveladora para su divulgación sin restricciones en un documento escrito firmado por un funcionario debidamente autorizado de dicha Parte reveladora; (iv) la Parte receptora desarrolla independientemente sin el acceso a la Información confidencial de la otra Parte ni el uso de esta; o (v) está o estuvo almacenada o publicada en el Servicio y fuera de los Repositorios privados del Cliente. - -**“Conexión”** o **“Conexión con GitHub”** se refiere a una función incluida en el Software que habilita al Cliente a conectar el Software con GitHub.com. El uso de conexión con GitHub está sujeto a los términos de conexión de GitHub establecidos en los [Términos adicionales del producto de GitHub](/github/site-policy/github-additional-product-terms). - -**"Contenido"** se refiere, entre otros, a textos, datos, artículos, imágenes, fotografías, gráficos, software, aplicaciones, diseños, funciones y otros materiales que se presentan, se muestran o se ponen a disposición a través del Servicio. - -**"Cuenta corporativa"** se refiere a una cuenta creada por el Usuario en nombre de una entidad. - -**"Cliente"** significa, colectivamente, la compañía u organización que ha ingresado en el presente Acuerdo con GitHub al dar clic en el botón "ESTOY DE ACUERDO" o similar o al acceder a los Productos, sus Afiliados y Representantes. - -**"Contenido del Cliente"** se refiere al Contenido que el Cliente crea, posee o sobre el cual el Cliente tiene los derechos. - -**“Modificaciones del Cliente”** se refiere a las modificaciones del Software que el Cliente puede hacer únicamente con el fin de realizar corrección de errores, personalizaciones o funciones adicionales para cualquier biblioteca con licencia en las licencias de código abierto que se pueden incluir con el Software o vincularse a este. - -**"Documentación"** se refiere a cualquier manual, documentación y otros materiales de soporte relacionados con el Software o el Servicio que GitHub proporciona o pone a disposición del Cliente. - -**"Fecha de entrada en vigor"** es la primera de las fechas en las cuales el Cliente (i) acepta los términos y condiciones del presente Acuerdo, tal como se describe anteriormente, o (ii) realiza el primer pedido de los Productos. - -**"Servicios esenciales"** se refiere a los servicios esenciales para la funcionalidad de control de la versión principal de GitHub, que incluyen crear, bifurcar y clonar repositorios; crear, confirmar y fusionar ramas; crear, revisar y fusionar solicitudes de extracción; y las interfaces web, API y Git del cliente para los flujos de Git principales. Los siguientes ejemplos muestran funciones periféricas y servicios que no están incluidos: webhooks, Gists, Páginas y notificaciones por correo electrónico. - -**"Usuario externo"** se refiere a un individuo, que no incluye a los Usuarios del Cliente, que visita o usa el Servicio. "Tarifas" se refiere a las tarifas que el Cliente debe pagarle a GitHub para (i) usar los Productos durante el Término de suscripción correspondiente o (ii) recibir Servicios profesionales, como tales tarifas se reflejan en el Formulario de pedidos o SOW. - -**"Comentarios"** se refiere a cualquier idea, conocimiento, algoritmo, contribución de código, sugerencia, solicitud de mejora, recomendación o cualquier otro comentario sobre los productos o servicios de GitHub. - -**"Cuotas"** significa las tarifas que el Cliente debe hacer a GitHub para (i) utilizar los Productos durante el Plazo de Suscripción aplicable o (ii) recibir Servicios Profesionales, ya que dichas tarifas se reflejan en un Formato de Compra o SOW. - -**“Bifurcación”** se refiere a copiar el Contenido de un repositorio en otro repositorio. - -**"GitHub"** se refiere, en conjunto, a GitHub, Inc., sus Subsidiarias y Representantes. - -**"Contenido de GitHub"** se refiere al Contenido que GitHub crea, posee o el contenido sobre el cual tiene los derechos. - -**"Insights de GitHub"** o **Insights** se refiere a la característica de software que le brinda a los clientes métricas, analíticas y recomendaciones relacionadas con el uso del software. GitHub Insights no incluye características tradicionales de GitHub incluyendo perspectivas de organización y de repositorio. - -**"GitHub One"** se refiere al paquete de productos que incluye GitHub Enterprise, Advanced Security, Insights, Learning Lab for Enterprise Server y Premium Plus o soporte de ingeniería Direct. - -**"Learning Lab for Enterprise Server"** hace referencia a la función de software que permite a los usuarios aprendan sobre la funcionalidad de GitHub, incluyendo la documentación asociada. - -**"Clave de licencia"** se refiere a los archivos de datos que usa el mecanismo de control de acceso del Software que le permiten al Cliente instalar, operar y usar el Software. - -**“Cuenta de máquina”** se refiere a una cuenta registrada por una persona que acepta los términos aplicables del servicio en nombre de la Cuenta de máquina, proporciona una dirección de correo electrónico válida y es responsable de sus acciones. Una Cuenta de máquina se usa exclusivamente para ejecutar tareas automatizadas. Múltiples usuarios pueden dirigir las acciones de una Cuenta de máquina, pero el propietario de la cuenta es responsable en última instancia de las acciones de la máquina. - -**"Formulario de pedidos"** se refiere a la documentación electrónica o por escrito (incluido un presupuesto) que las Partes usan para pedir los Productos. - -**“Organización”** se refiere a un espacio de trabajo compartido que se puede asociar con una única entidad o con uno o más Usuarios donde múltiples Usuarios pueden colaborar en muchos proyectos a la vez. Un Usuario puede ser miembro de más de una Organización. - -**"Interrupción"** se refiere a la interrupción de un Servicio esencial que afecta a más del 50⁰% de los Usuarios activos. - -**“Repositorio privado”** se refiere a un repositorio que permite que un Usuario controle el acceso al Contenido. - -**"Servicios profesionales"** se refiere a los servicios de capacitación, consultoría o implementación que GitHub proporciona conforme a un SOW ejecutado recíprocamente. Los Servicios profesionales no incluyen el Soporte. - -**“Repositorio público”** se refiere a un repositorio cuyo Contenido es visible para todos los Usuarios. - -**"Lanzamiento"** se refiere a un lanzamiento de Software que GitHub generalmente pone a disposición de sus clientes, junto con cualquier cambio correspondiente en la Documentación, que contiene mejoras, funciones o funcionalidades nuevas, que se suelen indicar con un cambio en el dígito a la derecha del primer punto decimal (por ejemplo, x.x.x a x.y.x) o a la izquierda del primer punto decimal (por ejemplo, x.x.x a y.x.x). - -**"Representantes"** se refiere a empleados, agentes, contratistas independientes, consultores y asesores legales y financieros de una de las Partes. - -**“Extracción”** se refiere a extraer datos del Servicio a través de un proceso automatizado, como un bot o agente de búsqueda, y que no incluye la recopilación de información a través de la API de GitHub. - -**"Servicio"** se refiere al servicio alojado de GitHub Enterprise Cloud. El Servicio incluye: Cuenta(s) de organización, inicio único de sesión de SAML, provisión de acceso y cualquier Documentación correspondiente. Esta lista de funciones y servicios no es exhaustiva y puede ser actualizada de vez en cuando. - -**"Crédito de servicio"** se refiere a un crédito en dólares, calculado como se establece a continuación, que GitHub puede acreditar a una cuenta elegible. - -**"Software"** significa el Software local de GitHub Enterprise Server. El Software incluye la característica de GitHub Connect, cualquier Documentación aplicable, cualquier Actualización al Software que Github proporcione al cliente o al que éste pueda acceder bajo el presente Acuerdo, y, si se incluye en la suscripción del Cliente, al Software Complementario. - -**"SOW"** se refiere a una declaración de trabajo ejecutada recíprocamente que detalla los Servicios profesionales que GitHub realizará, cualquier Tarifa relacionada y las obligaciones relacionadas de cada una de las Partes. - -**“Licencia de suscripción”** se refiere a la licencia asignada a cada Usuario para instalar, operar, acceder y usar los Productos en nombre del Cliente. El Cliente puede asignar solamente una Licencia de suscripción por Usuario en sus instancias del servidor de GitHub Enterprise y Organizaciones de GitHub Enterprise Cloud. Cada Usuario tendrá acceso a tantas instancias del servidor de Enterprise del Cliente o a Organizaciones de Enterprise Cloud como el Cliente lo permita. Para mayor claridad, sin embargo, una vez que el Cliente asigna una Licencia de suscripción a un Usuario, el Cliente no estará autorizado a bifurcar la Licencia de suscripción de modo que un Usuario podrá usar una Licencia de suscripción en el servidor de Enterprise mientras otro Usuario usa la misma Licencia de suscripción en otra instancia del servidor de GitHub Enterprise o en una Organización de GitHub Enterprise Cloud. - -**“Plazo de la suscripción”** se refiere a un (1) año a partir de la fecha de entrada en vigor correspondiente de un pedido o como se indique en el Formulario de pedidos. - -**“Soporte”** se refiere al soporte técnico para el Software o el Servicio que GitHub puede proporcionar. - -**“Actualizar”** se refiere a un lanzamiento de Software que GitHub, generalmente, pone a disposición de sus clientes, junto con cualquier cambio correspondiente en la Documentación, que contiene correcciones o solución de errores, que se suele indicar con un cambio en el dígito a la derecha del segundo punto decimal (por ejemplo, x.x.x a x.x.y). - -**“Tiempo de actividad”** se refiere al porcentaje de tiempo en un trimestre dado en que los Servicios esenciales de GitHub no se detendrán por una Interrupción que afecte a más del 50⁰% de los Usuarios activos. - -**"Usuario"** significa (i) con respecto al Software, una sola persona o Cuenta de Máquina que inicia la ejecución de dicho Software o interactúa o dirige a éste al desempeño de sus funciones; y (ii) con respecto al Servicio, un individuo o Cuenta de Máquina que (a) accede o utiliza el Servicio, (b) accede a, o utiliza, cualquier parte de la cuenta del Cliente, o (c) dirige el uso de la cuenta del Cliente en la ejecución de sus funciones, en cada caso, en representación del Cliente. La cantidad de Usuarios no debe exceder el número de Licencias de suscripción que el Cliente compró. - -**“Contenido generado por el Usuario”** se refiere al Contenido que un tercero o un Usuario externo crea o posee. diff --git a/translations/es-XL/content/github/site-policy/github-event-code-of-conduct.md b/translations/es-XL/content/github/site-policy/github-event-code-of-conduct.md deleted file mode 100644 index d654973cc2..0000000000 --- a/translations/es-XL/content/github/site-policy/github-event-code-of-conduct.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Código de conducta del evento de GitHub -redirect_from: - - /articles/github-event-code-of-conduct -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Los eventos de GitHub son eventos comunitarios destinados a la creación de redes y la colaboración en la comunidad tecnológica. - -Valoramos la participación de cada miembro y deseamos que todos los asistentes tengan una experiencia agradable y satisfactoria. En consecuencia, se espera que todos los asistentes muestren respeto y cortesía a otros asistentes durante todos los eventos alojados en el espacio de GitHub. - -Para dejar en claro lo que se espera, todos los asistentes, oradores, expositores, organizadores y voluntarios en cualquier evento en el espacio de GitHub están obligados a cumplir con el siguiente código de conducta. Los organizadores aplicarán este código a lo largo de todo el evento. - -### Código de conducta - -GitHub se dedica a brindar una experiencia de evento positiva y sin acoso para todo el mundo, independientemente de su edad, género, identidad y expresión de género, orientación sexual, discapacidad, apariencia personal, complexión, etnia, raza, religión, nacionalidad o nivel de experiencia. No toleramos el acoso a los participantes del evento en ninguna forma, ni toleramos ningún comportamiento que razonablemente conduzca a que otro participante del evento se sienta en peligto, inseguro o asustado por su bienestar físico o emocional. Todas las comunicaciones deben ser adecuadas para un público profesional que incluya personas de muchos orígenes diferentes. - -Algunos ejemplos de comportamientos alentados que contribuyen a un entorno positivo incluyen los siguientes: - -* Uso de un lenguaje acogedor e inclusivo -* Ser respetuoso desde diferentes puntos de vista y experiencias -* Aceptar con agradecimiento las críticas constructivas -* Centrarse en lo que es mejor para todos en el evento -* Mostrar empatía hacia otros participantes - -Un comportamiento inaceptable incluye: - -* El uso de lenguaje o imágenes sexualizados o el contacto físico inapropiado, la atención sexual o los acercamientos -* Trolleo, comentarios insultantes o despectivos, ataques personales o políticos, o alteración sostenida de las conversaciones u otras situaciones -* Intimidación deliberada, acecho, seguimiento o acoso con fotografías o grabaciones -* Acoso de cualquier tipo, incluso de una manera graciosa o irónica -* Otras conductas que razonablemente podrían considerarse inapropiadas en un entorno profesional - -Sé amable con los demás. No insultes ni desanimes a otros asistentes. Comportarte profesionalmente. Recuerda que el acoso y las bromas sexistas, racistas o excluyentes no son adecuadas en este evento. - -Cada huésped del evento es totalmente responsable de sus propias acciones. - -Gracias por ayudar a hacer de este un espacio acogedor y agradable para todos. - -#### Informe de un incidente - -Si estás siendo hostigado, notas que alguien más está siendo acosado, o tienes alguna otra inquietud, comunícate con el organizador por correo electrónico (events@github.com) o por teléfono/texto (+ 1 415 842 2837), o habla con otro empleado de GitHub o un oficial de seguridad. - -GitHubbers estará encantado de ayudar a los participantes a ponerse en contacto con la seguridad o la aplicación de la ley local, acompañar a seguridad o de otro modo ayudar a aquellos que experimentan acoso a sentirse seguros durante la conferencia. Valoramostu asistencia. - -### Crédito - -Algunas partes de este código de conducta se basan en el [ejemplo de política anti-acoso](https://geekfeminism.wikia.org/wiki/Conference_anti-harassment/Policy) de Geek Feminism wiki, creado por la iniciativa Ada y otros voluntarios, bajo una licencia Creative Commons Zero. diff --git a/translations/es-XL/content/github/site-policy/github-event-terms.md b/translations/es-XL/content/github/site-policy/github-event-terms.md deleted file mode 100644 index ab7790c6f1..0000000000 --- a/translations/es-XL/content/github/site-policy/github-event-terms.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Términos del evento de GitHub -redirect_from: - - /articles/github-event-terms -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Al confirmar su asistencia o asistiendo a un evento de GitHub, incluyendo cualquiera de los eventos o actividades organizadas por GitHub en asociación con el evento de GitHub (en conjunto, el "Evento"), señalas que has leído, comprendes y aceptas los siguientes términos y condiciones del evento. - -### 1. Requisitos básicos para asistir, incluyendo el [Código de conducta del evento](/articles/github-event-code-of-conduct) - -Para participar en el Evento afirmas que: - -- tienes el poder y la autoridad necesarios para participar en los presentes términos del evento - -- has leído y comprendido estos términos del evento, así como los [términos de servicio de GitHub.com ](/articles/github-terms-of-service/) - -- aceptas regirte por el [Código de conducta del evento](/articles/github-event-code-of-conduct), que busca brindar una experiencia libre de acoso para todos - -- si se sirve alcohol en un evento de GitHub, afirmas que tienes al menos 21 años de edad, o de cualquier otra manera eres mayor de edad legal de consumo en tu jurisdicción. - -Se espera que los participantes detengan cualquier acoso u otro comportamiento prohibido para cumplir de inmediato. Si un participante se involucra en un comportamiento que viola el [Código de Conducta del Evento](/articles/github-event-code-of-conduct) o estos términos, los organizadores del evento pueden tomar cualquier acción que consideren adecuada, incluyendo la advertencia del infractor o la expulsión del evento o la conferencia sin reembolso. - -### 2. Fotos - -GitHub o sus socios en ocasiones toman fotos y videos en eventos de GitHub. Al participar o asistir al evento, aceptas que puedas aparecer en algunas de estas fotos y vídeos y autorizas el uso de los mismos por parte de GitHub. Por otro lado, si llevas fotos o vídeos de los asistentes en el evento y nos los proporcionas, nos autorizas a utilizarlos de la misma manera y representamos que los asistentes que aparecen en tus fotos y vídeos también han dado su consentimiento para dicho uso. - -### 3. Riesgo, responsabilidad e indemnización - -#### Asunción del riesgo -A pesar de que intentamos crear un entorno seguro en el evento, suceden accidentes u otras cosas malas, incluso para las personas buenas. Te pedimos que hagas tu parte para ayudar a limitar la posibilidad de que puedas lesionarte en el evento. - -Aceptas considerar detenidamente los riesgos inherentes a cualquier actividad en la que elijas participar y tomar las precauciones razonables antes de elegir asistir a un evento de GitHub o participar en él. Por ejemplo, deberías asegurarte de estar en buena salud física antes de participar en cualquier actividad física en un evento de GitHub y siempre deberías beber de manera responsable teniendo en cuenta los riesgos asociados con conducir ebrio y participar en actividades mientras se deteriora tu juicio. Siempre es bueno recordar que otros asistentes al evento pueden ser menos responsables que tú y pueden crear un riesgo adicional para ti a pesar de sus mejores intenciones. - -En resumen, comprendes que tu asistencia y participación en cualquier evento de GitHub es voluntaria y aceptas asumir la responsabilidad de cualquier lesión resultante en la máxima medida permitida por la ley aplicable. - -De la misma forma, aceptas que GitHub no es responsable de ninguna lesión o accidente que puedas sostener en cualquier evento que GitHub no organice o controle. - -#### Liberación de responsabilidad -Tú (por ti mismo, tus herederos, representantes personales o cesionarios, y cualquier otra persona que pueda hacer un reclamo en tu nombre) por la presente se liberan, renuncian, descargan y hacen el pacto de no demandar a GitHub y sus respectivas empresas matrices, subsidiarias, afiliadas, funcionarios, directores, socios, accionistas, miembros, agentes, empleados, vendedores, patrocinadores y voluntarios de todas las reclamaciones, demandas, causas de acción, daños, pérdidas o gastos (incluyendo los costos judiciales y los honorarios razonables de abogados) que puedan surgir, resultar o relacionarse de alguna manera con tu asistencia en el evento o cualquier evento relacionado, excepto, por supuesto, por cualquier negligencia grave o mala conducta intencional de nuestra parte. - -#### Indemnización -De la misma forma, aceptas indemnizar y eximir de toda responsabilidad a GitHub, sus matrices, subsidiarias, afiliados, funcionarios, directores, empleados, agentes y representantes, incluyendo los costos, pasivos y honorarios legales, de cualquier reclamación o demanda hecha por cualquier tercero por causa, que esté relacionada o en conexión con tu asistencia o conducta en el evento o cualquier evento relacionado. - -### 4. Terminación - -Si bien esperamos que no lo haga, GitHub puede prohibir tu asistencia a cualquier evento de GitHub en cualquier momento si no cumples con los presentes términos del evento y el [Código de conducta del evento](/articles/github-event-code-of-conduct), los[términos de servicio de GitHub.com](/articles/github-terms-of-service/), o por cualquier motivo o sin motivo, sin previo aviso ni responsabilidad de ningún tipo. La sección 3 (riesgo, responsabilidad e indemnización) continuará aplicándose después de cualquier terminación. - -### 5. Elección de la ley y lugar de residencia - -La ley de California regirá estos términos del evento, así como cualquier reclamación, causa de acción o disputa que pueda surgir entre tú y GitHub (una "reclamación"), sin tener en cuenta las disposiciones de conflicto de leyes. PARA CUALQUIER RECLAMACIÓN PRESENTADA POR CUALQUIERA DE LAS PARTES, ACEPTAS SOMETERTE Y DAR TU CONSENTIMIENTO A LA JURISDICCIÓN PERSONAL Y EXCLUSIVA EN EL LUGAR EXCLUSIVO DE LOS TRIBUNALES ESTATALES Y FEDERALES UBICADOS DENTRO DEL CONDADO DE SAN FRANCISCO, CALIFORNIA. - -### 6. Términos varios - -Aceptas que no te representarás a ti mismo como empleado, representante o agente de GitHub (a menos que, por supuesto, realmente estés contratado por GitHub). Nos reservamos el derecho a cancelar el evento o cualquier evento relacionado en cualquier momento, por cualquier motivo y sin responsabilidad o perjuicio. Cualquier falla por parte de GitHub para ejercer o hacer cumplir cualquier derecho o disposición de estos términos no constituye una renuncia a tal derecho o disposición. Si alguna disposición de estos términos se encuentra como inejecutable o inválida, esa disposición se limitará o eliminará en la medida mínima necesaria para que los términos del evento permanezcan en plena vigencia y efecto y exigibles. diff --git a/translations/es-XL/content/github/site-policy/github-gifts-and-entertainment-policy.md b/translations/es-XL/content/github/site-policy/github-gifts-and-entertainment-policy.md deleted file mode 100644 index 13e6743b36..0000000000 --- a/translations/es-XL/content/github/site-policy/github-gifts-and-entertainment-policy.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Política de entretenimiento y obsequios de GitHub -redirect_from: - - /articles/github-gifts-and-entertainment-policy -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -GitHub reconoce que nuestro negocio se basa en relaciones positivas y transparentes. Si bien las interacciones informales y los intercambios de regalos pueden ser parte del desarrollo de esas relaciones e incluso pueden considerarse habituales en algunos países, debemos asegurarnos de que estemos siguiendo las leyes antisoborno. Tenemos la obligación legal de comportarnos éticamente, incluyendo no usar dichas interacciones para crear una ventaja especial o influir en una transacción. - -### Políticas de empresa -Como recordatorio, nuestro Código de Ética dice: -> Nunca debes pagar, ofrecer pagar, prometer pagar, inducir, aceptar o autorizar el pago de ninguna otra cosa de valor, a ninguna persona, incluyendo a ninguna persona en una posición de poder o autoridad, por ejemplo, funcionarios del gobierno o en transacciones comerciales, con el fin de obtener o mantener negocios, o asegurar cualquier otra ventaja inapropiada para GitHub o Microsoft. Tampoco debes solicitar o aceptar sobornos, ni ningún otro pago indebido en efectivo. ... [Los empleados de GitHub] están obligados a mantener registros precisos y razonables de todas las transacciones que implican cualquier gasto hecho en nombre de GitHub, por ejemplo, al mantener los recibos y proporcionar descripciones precisas de tus gastos, o cualquier otra transacción que implique la eliminación o la transferencia de los activos de GitHub. Such actions are required by the U.S. Foreign Corrupt Practices Act, the U.K. Estas acciones se exigen por la ley de prácticas corruptas extranjeras de los EE. UU., la ley de soborno del Reino Unido de 2010 y las leyes antisoborno de otras jurisdicciones en las que GitHub hace negocios y que también son simplemente la manera correcta de proceder. - -El código ético de GitHub detalla ciertas situaciones, incluyendo sobre regalos, viajes y entretenimiento; facilitación de pagos; donaciones caritativas; puestos laborales y trabajar con representantes, así como la descripción de quién se considera un funcionario del gobierno. - -Nuestras Normas de Conducta prohíben: -> Sobornar a funcionarios del gobierno u otras personas para obtener una ventaja injusta y tomar sobornos de cualquier persona. - -Eso significa que no solo se debe administrar dinero en efectivo o equivalente en efectivo de ningún tipo, sino no entregar nada de valor a nadie (incluyendo los empleados públicos, funcionarios del gobierno o cualquier persona en una posición de poder o autoridad, así como personas que no estén en cualquiera de esas posiciones privilegiadas) con el fin de influir en ellos o de que cualquier persona pueda influir en GitHub. Such activity is prohibited by the U.S. Se prohíbe dicha actividad por la ley de prácticas corruptas extranjeras de los EE. UU. y las leyes antisoborno del Reino Unido, que rigen las acciones de GitHub en todo el mundo. - -### Ejemplos de regalos aceptables e inaceptables -Entonces, ¿Qué significa "de valor"? Ten en cuenta que no se aceptan regalos a funcionarios del gobierno (ok, tal vez calcomanías). Siempre debes preguntarles qué permiten y qué prohíben sus políticas. Pero si tienes dudas, por favor, consulta la ley para asegurarte. For example, many U.S. Por ejemplo, muchos legisladores estadounidenses no te permitirán llevarlos a cenar y pagar. - -En cuanto a otros clientes o clientes potenciales, ciertas cosas pueden parecer triviales pero tienen un gran valor para otra persona. Por ejemplo, si bien puede que no parezca una gran cosa para ti lograr que se contrate a la hija de tu amigo como pasante, puede ser de gran valor para ellos. Pero si no está calificada y mueves influencias para hacer que suceda, entonces no está bien. Además, si la intención es influir de manera inadecuada, cualquier cosa, por pequeña que sea, se puede considerar "de valor". - -🙅 _Aquí hay otras cosas que no son correctas:_ - -- Pasaje aéreo de primera clase para las oficinas de GitHub para sesiones de instrucción ejecutiva ✈️ + 🍾 -- Tours en bodegas 🍷 -- Recomendar al niño de un amigo para admisión a una escuela privada prestigiosa 🎓 -- Entradas a Disneyland 👸, la Copa del mundo 🥅, los Juegos Olímpicos 🏅 -- Un balón ⚽️ autografiado por un jugador famoso -- Una contribución a una organización benéfica - -🙆 _Aquí se presentan algunas cosas que en realidad están bien para los clientes o clientes potenciales:_ - -- Flores -- Pasaje aéreo de clase turista a las oficinas de GitHub para sesiones de reuniones ejecutivas ✈️ -- Boletos tipo gradas para un evento deportivo ⚾️ -- Una cena de precio razonable en la ciudad 🍽 -- Una pequeña caja de chocolates como agradecimiento de fin de año 🍫 - -Todo lo anterior se aplica a la _toma_ de sobornos también. Por lo tanto, si un proveedor o posible proveedor te envía algo "de valor", no lo aceptes o, al menos, aplica la ley antes de hacerlo. - -### Proceso -Si estás planeando brindar o aceptar un regalo informal (que no es uno de nuestros artículos promocionales como camisetas y conjunto de calcomanías), por favor asegúrate de seguir el proceso que se presenta a continuación. - -Ten en cuenta que lo que es una cantidad aceptable puede variar. Por ejemplo, gastar $50 en la cena puede considerarse mucho dinero en algunos países, pero no tanto en otros. Por lo tanto, si tienes duda, ¡Pregunta! - -1. En términos generales, para cualquier gasto que exceda de $150, necesitarás aprobación (en cada ocasion) del Jurídico, por escrito. Y para cualquier regalo que recibas que supere los $150, deberás informar de ello (en cada ocasión) a Jurídico, por escrito. (Jurídico sólo lo pondera en el tema de soborno. Es posible que aún debas verificar con Finanzas por otras razones.) - -2. Cuando envíes tu informe de gastos para el reembolso, por favor: - - Indica el destinatario y el propósito del regalo en las notas; e - - Incluye una copia de la aprobación por correo electrónico - -### Consecuencias -¿Qué sucede si no sigues la política y GitHub termina pagando a un cliente potencial y a su familia para volar en primera clase a Japón y asistir a los Juegos Olímpicos de Tokio? ¿O si le entregas con arreglo previo una maleta de euros a un funcionario del gobierno en un casillero de estación de tren? - -MULTAS y CÁRCEL. No necesariamente solo para GitHub. Puedes llegar a pasar algunos años en la cárcel y no importará si el cliente alguna vez envió una orden a GitHub después de su viaje a Japón o si el funcionario del gobierno incluso recogió la maleta de dinero en efectivo. Básicamente, no importa si realmente _hiciste_ un soborno. Sin embargo, el intento es lo que cuenta. - -### Más información -Para obtener más información y contexto sobre las reglas, el cumplimiento y las sanciones, el Departamento de Justicia de los EE. UU. [Guía de recursos para la ley de prácticas corruptas extranjeras de los EE. UU.](https://www.justice.gov/sites/default/files/criminal-fraud/legacy/2015/01/16/guide.pdf) es un excelente recurso. Foreign Corrupt Practices Act is an excellent resource. diff --git a/translations/es-XL/content/github/site-policy/github-government-takedown-policy.md b/translations/es-XL/content/github/site-policy/github-government-takedown-policy.md deleted file mode 100644 index b493e2221c..0000000000 --- a/translations/es-XL/content/github/site-policy/github-government-takedown-policy.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Política de retiro gubernamental de GitHub -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -#### ¿Qué es esto? -De vez en cuando, GitHub recibe solicitudes de los gobiernos para retirar contenido que se declaró ilegal en su jurisdicción local. Aunque no siempre estemos de acuerdo con esas leyes, podemos necesitar bloquear el contenido si recibimos una solicitud completa de un funcionario del gobierno para que nuestros usuarios en esa jurisdicción puedan continuar teniendo acceso a GitHub para colaborar y construir software. - -#### ¿Qué es una solicitud completa de retiro del gobierno? -Para que cuente como una solicitud completa, una solicitud o aviso debe: -- provenir de una agencia gubernamental oficial correspondiente -- identificar contenido ilegal -- especificar la fuente de ilegalidad en dicha jurisdicción (ley u orden judicial). - -#### ¿Qué ocurre cuando recibimos una solicitud de retiro completa de un gobierno? - -Cuando recibimos una notificación de una agencia gubernamental oficial correspondiente que identifique contenido ilegal y especifique la fuente de la ilegalidad, nosotros -- notificamos a los usuarios afectados del contenido específico que presuntamente viola la ley y que esta es una solicitud de retiro legal -- permitimo a los usuarios afectados apelar la decisión como parte de dicha notificación -- limitamos el alcance geográfico de la retiro cuando sea posible y lo incluimos como parte de la notificación -- publicamos la solicitud oficial que condujo al retiro en nuestro repositorio [gov-takedowns](https://github.com/github/gov-takedowns) público. - -#### ¿Por qué publicamos avisos de retiro? -Nos preocupa la censura de Internet y creemos que la transparencia a un nivel específico y actual es esencial para una buena gobernanza. Al hacer públicamente los avisos, podemos informar mejor al público sobre el contenido que se retiene de GitHub y las razones. Publicamos notificaciones de retiro para documentar su potencial de desintensificar el discurso. - -#### ¿Qué significa que publiquemos una notificación en nuestro repositorio de retiro del gobierno? -Significa que recibimos la notificación en la fecha indicada. *No* significa que el contenido es ilegal o sea incorrecto. *No* significa que el usuario identificado en la notificación haya hecho algo incorrecto. No hacemos ni implicamos ningún juicio sobre el mérito de las reclamaciones que hacen. Publicamos estas notificaciones y solicitudes sólo para propósitos informativos. - -#### Reportes de transparencia -Además de publicar notificaciones de retiro del gobierno en nuestro repositorio de retiros del gobierno, las informamos en nuestro reporte de transparencia. También rastreamos e informamos en nuestro reporte de transparencia sobre los retiros del gobierno con base en violaciones de los Términos de Servicio de GitHub. Procesamos dichas violaciones como procesaríamos una violación de los Términos de Servicio denunciada por cualquier otro. diff --git a/translations/es-XL/content/github/site-policy/github-gpl-cooperation-commitment.md b/translations/es-XL/content/github/site-policy/github-gpl-cooperation-commitment.md deleted file mode 100644 index 58a030f379..0000000000 --- a/translations/es-XL/content/github/site-policy/github-gpl-cooperation-commitment.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: GitHub GPL Cooperation Commitment -redirect_from: - - /articles/github-gpl-cooperation-commitment -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Este compromiso se refiere a las contribuciones de GitHub a Git, el kernel de Linux y otros programas bajo licencias cubiertas (desplácese hasta el final para las definiciones). - -Basamos nuestra proposición en la plantilla [](https://github.com/gplcc/gplcc/blob/master/Company/GPL%20Cooperation%20Commitment-Company-Template.md) para empresas. Consulta el [sitio del Comité de Cooperación GPL](https://gplcc.github.io/gplcc/) para conocer cómo otras empresas, individuos y proyectos pueden adoptar este compromiso. - -### Nuestro compromiso - -Antes de presentar o continuar procesando cualquier procedimiento legal o reclamación (excepto una acción defensiva) que surja de la terminación de una licencia cubierta, GitHub se compromete a extenderse a la persona o entidad (“tú”) acusada de violar la Licencia Cubierta, las siguientes disposiciones relativas a la subsanación y la reincorporación, tomado de la versión 3 de GPL. Tal y como se utiliza aquí, el término "esta Licencia" se refiere a la Licencia cubierta específica que se está cumpliendo. - -Sin embargo, si cesas toda violación de esta Licencia, entonces tu licencia de un titular de derechos de autor particular se reestablece (a) de forma proporcional, a menos y hasta que el titular de los derechos de autor explícitamente y finalmente termina tu licencia, y (b) de forma permanente, si el titular de los derechos de autor no te notifica la violación por algún medio razonable antes de los 60 días posteriores a la cesación. - -Además, tu licencia de un determinado titular de derechos de autor se reestablece permanentemente si el titular de los derechos de autor te notifica la violación por algunos medios razonables, esta es la primera vez que recibes un aviso de violación de esta Licencia (por cualquier trabajo) de ese titular de los derechos de autor y subsanas la violación antes de 30 días después de la recepción de la notificación. - -GitHub pretende que este Comité sea irrevocable, vinculante y exigible contra GitHub y asignados o sucesores de los derechos de autor de GitHub. - -GitHub puede modificar este Comité publicando una nueva edición en esta página o una ubicación posterior. - -Definiciones - -‘Licencia cubierta’ hace referencia a la Licencia Pública General GNU, versión 2 (GPLv2), la Licencia Pública General Menor GNU, versión 2. (LGPLv2.1), o la Licencia Pública General de la Biblioteca GNU, versión 2 (LGPLv2), todo publicado por la Free Software Foundation. - -‘Acción Defensiva’ significa un proceso legal o una reclamación de GitHub contra ti en respuesta a un proceso previo o reclamación iniciada por ti o tu afiliado. - -'GitHub' significa GitHub, Inc. y sus filiales. - -Este trabajo está disponible bajo una licencia interlacional Creative Commons Attribution-ShareAlike 4.0. diff --git a/translations/es-XL/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md b/translations/es-XL/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md deleted file mode 100644 index fd9c1568fb..0000000000 --- a/translations/es-XL/content/github/site-policy/github-insights-and-data-protection-for-your-organization.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: GitHub Insights and data protection for your organization -intro: '{% data variables.product.prodname_insights %} analyzes your {% data variables.product.prodname_ghe_server %} data. This data could include personal data of individuals in your organization who may have the right to understand how such personal data is being used.' -product: '{% data reusables.gated-features.github-insights %}' -redirect_from: - - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.21/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.20/github/site-policy/github-insights-and-data-protection-for-your-organization -versions: - free-pro-team: '*' -topics: - - Policy - - Legal ---- - -For more information about the terms that govern {% data variables.product.prodname_insights %}, see your {% data variables.product.prodname_ghe_one %} subscription agreement. - -For the avoidance of doubt, none of the foregoing information should be considered legal advice provided by {% data variables.product.prodname_dotcom %}. You are responsible for securing your own legal analysis of the information provided herein and for your compliance with privacy and data protection laws. It is up to you whether to use {% data variables.product.prodname_insights %} to process your employees’ and users’ data, and if you do so, you are solely responsible for conducting such processing in compliance with applicable law. - -### The organization’s roles and responsibilities - -When using {% data variables.product.prodname_insights %}, your organization is the data controller because your organization determines whether, how, and why {% data variables.product.prodname_insights %} will process any individual’s personal data. Your organization is solely responsible for ensuring that you are complying with all applicable laws in processing data with {% data variables.product.prodname_insights %}. - -### Data privacy recommendations - -You have full control over which metrics, reports, repositories, and contributors to include before beginning use of {% data variables.product.prodname_insights %}. The data you process with {% data variables.product.prodname_insights %} can only be pulled from your installation of {% data variables.product.prodname_ghe_server %}. Consider balancing the risks versus the benefits of analyzing personal data. - -- **Develop a clear analysis plan**: You must understand clearly what you want to analyze and why, and then consider how {% data variables.product.prodname_insights %} may help you find those answers. - -- **Consider a data protection impact assessment**: If your proposed use of {% data variables.product.prodname_insights %} involves processing personal data, consider completing a data protection impact assessment or otherwise completing formal legal analysis of your planned use. - -### Decide what data to use - -- **Decide which repositories to include**: Before you start an analysis in {% data variables.product.prodname_insights %}, consider which repositories to include. Administrators can include repositories when adding organizations and can enable and disable repositories at any time. For more information on adding organizations to {% data variables.product.prodname_insights %}, see "[Managing organizations](/insights/installing-and-configuring-github-insights/managing-organizations)." For more information on enabling and disabling repositories, see "[Managing repositories](/insights/installing-and-configuring-github-insights/managing-repositories)." - -- **Decide which metrics and reports to include**: Administrators can enable and disable metrics and reports available for all users at any time. Administrators control the {% data variables.product.prodname_insights %} data that users have access to in your installation of {% data variables.product.prodname_ghe_server %}. For more information, see "[Managing available metrics and reports](/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports)." - -- **Decide which contributors to include**: Administrators can disable a specific contributor’s data from being processed in the metrics and reports. For more information on managing contributor data, see "[Managing contributors and teams](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)." - -### User rights - -Under various data protection regulations, such as the General Data Protection Regulation (GDPR), users may have the right to request exclusion from processing, access, and correction, or to request deletion of their personal data. As the data controller, your organization should evaluate whether a particular user request is valid and, if appropriate, take action to fulfill the request. - -- **Exclusion of processing**: Users may have the right to have their personal data excluded from being processed. Administrators have the ability to remove a contributor’s data from being processed in {% data variables.product.prodname_insights %}, and the resulting reports and metrics will exclude the contributor’s data accordingly. For more information, see "[Managing contributors and teams](/insights/installing-and-configuring-github-insights/managing-contributors-and-teams)." - -- **Access**: Users may have the right to demand to see what personal data is being processed. Each metric and report has a detailed description of what personal data is being processed. For more information, see "[Metrics available with {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)." Raw data is available through the {% data variables.product.prodname_enterprise %} API. Your organization is responsible for any decisions to process personal data and for fulfilling any such requests. - -- **Correction and deletion**: Users may have the right to rectify or delete their personal data. The data used in {% data variables.product.prodname_insights %} is derived from the existing data you add to or generate from your {% data variables.product.prodname_ghe_server %} installation. Correction and deletion should follow your organization's existing process to correct and delete data from {% data variables.product.prodname_ghe_server %}. - -- **Transparency regarding processing**: Each metric and report has a detailed description of what personal data is being processed. For more information, see "[Metrics available with {% data variables.product.prodname_insights %}](/insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights)." diff --git a/translations/es-XL/content/github/site-policy/github-logo-policy.md b/translations/es-XL/content/github/site-policy/github-logo-policy.md deleted file mode 100644 index ad03e18acf..0000000000 --- a/translations/es-XL/content/github/site-policy/github-logo-policy.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Política de logo de GitHub -redirect_from: - - /articles/i-m-developing-a-third-party-github-app-what-do-i-need-to-know/ - - /articles/using-an-octocat-to-link-to-github-or-your-github-profile/ - - /articles/github-logo-policy -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Puede añadir {% data variables.product.prodname_dotcom %} logos a tu sitio web o aplicación de terceros en algunos escenarios. Para obtener más información y directrices específicas, consulta la[{% data variables.product.prodname_dotcom %} página de Logos y Uso](https://github.com/logos). - -También puedes usar un octocat como tu avatar personal o en tu sitio web para vincular a tu cuenta, {% data variables.product.prodname_dotcom %} pero no para tu empresa o un producto que estás construyendo. {% data variables.product.prodname_dotcom %} tiene una extensa colección de octocats en el [Octodex](https://octodex.github.com/). Para obtener más información sobre cómo usar los octocats de Octodex, consulta las [preguntas frecuentes de Octodex](https://octodex.github.com/faq/). diff --git a/translations/es-XL/content/github/site-policy/github-marketplace-developer-agreement.md b/translations/es-XL/content/github/site-policy/github-marketplace-developer-agreement.md deleted file mode 100644 index 830ae1d78c..0000000000 --- a/translations/es-XL/content/github/site-policy/github-marketplace-developer-agreement.md +++ /dev/null @@ -1,273 +0,0 @@ ---- -title: Política de Desarrolladores para el Mercado de Github -redirect_from: - - /articles/github-marketplace-developer-agreement -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -**ESTOS TÉRMINOS Y CONDICIONES (EL "ACUERDO") REGULAN TU PARTICIPACIÓN EN EL PROGRAMA DEL MERCADO DE GITUB. AL INSCRIBIRTE PARA PARTICIPAR EN EL PROGRAMA DE MERCADO O AL HACER CLIC EN "ACEPTO" A CONTINUACIÓN, CONFIRMAS QUE ENTIENDES EL PRESENTE ACUERDO Y QUE ACEPTAS TODOS SUS TÉRMINOS Y CONDICIONES. SI ESTÁS INGRESANDO EN EL PRESENTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA ENTIDAD LEGAL, DECLARAS QUE TIENES LA AUTORIDAD LEGAL PARA VINCULAR A LA ENTIDAD CON EL PRESENTE ACUERDO, EN CUYO CASO "TÚ" SIGNIFICARÁ LA ENTIDAD QUE REPRESENTAS.** - -Fecha de entrada en vigor: 21 de julio de 2020 - -### 1. DEFINICIONES - -Los términos con mayúscula inicial utilizados en el presente acuerdo y no definidos en el presente documento deberán tener el significado establecido en los términos de servicio de GitHub ubicados en [https://docs.github.com/articles/github-terms-of-service](/articles/github-terms-of-service) (los "Términos" o "ToS"). - -"Acción" significa un mecanismo que te permite implementar lógica personalizada sin tener que crear una aplicación para realizar una tarea particular con GitHub. - -"Características de la marca" se refiere a los nombres comerciales, marcas comerciales, marcas de servicio, logotipos, nombres de dominio y otras características distintivas de la marca de cada parte, respectivamente, ya que son propiedad de dicha parte (o con licencia) de vez en cuando. - -"Programador" se refiere a ti y tu eres la empresa o persona que ha creado el software y los materiales digitales para su uso en conexión con GitHub y accesibles a través del mercado. - -"Aplicación del Programador" o "Producto del Programador" significa el Software, contenido y materiales digitales creados por ti para su uso en conexión con GitHub y que son accesibles a través del mercado e incluye Acciones. - -"Usuario final" hace referencia a cualquier persona, empresa u otra entidad legal que adquiera licencias para el Producto de Programadores a través del mercado de GitHub. - -"GitHub API" se refiere a la interfaz del programa de aplicación patentada de GitHub. El acceso y el uso de la API de GitHub se rige por los ToS. - -"Mercado de GitHub" o "mercado" se refiere al sitio del mercado en línea patentado operado por GitHub, donde los productos del programador se pueden entregar a los usuarios finales. - -“Listado” hace referencia al contenido proporcionado para listar el producto del Programador en el mercado de GitHub. - -"Impuestos" se refiere a cualquier ingreso federal, estatal, local o extranjero, ingresos brutos, franquicia, estimación, mínimo alternativo, ventas, uso, transferencia, valor agregado, consumo, propiedad real o personal, retenciones u otros impuestos, de cualquier tipo, incluyendo los intereses, sanciones o adiciones a impuestos o importes adicionales con respecto a lo anterior." - -"Datos de uso" hace referencia a los datos relacionados con el mercado generados en relación con el uso del usuario final del mercado de GitHub y la licencia de los productos para Programadores, incluyendo, sin limitación a estadísticas de uso y datos de ventas agregados. Los datos de uso no incluyen y específicamente excluyen la información bancaria y de pago. - -### 2. OBJETIVO Y CONCESIÓN DE LICENCIA - -**2.1** El presente acuerdo establece los términos y condiciones de acuerdo con los cuales el Programador puede publicar listados en el mercado GitHub para la compra de productos del programador por parte de los usuarios finales y el uso en conexión con GitHub.com. El presente acuerdo se aplica a los productos del Programador distribuidos para productos gratuitos y de Programador para los cuales se cobra una tarifa a los usuarios finales. El programador acepta usar el mercado de GitHub únicamente para los fines permitidos por el presente acuerdo o según lo permita la legislación aplicable. Entre GitHub y el Programador, el Programador es el único responsable de los productos del Programador. - -**2.2** El Programador otorga a GitHub una licencia no exclusiva, en todo el mundo, transferible, sublicenciable, totalmente pagada y exenta de regalías para (a) alojar, vincular, reproducir, modificar, ejecutar públicamente, exhibir públicamente, probar, distribuir, poner a disposición, licenciar y usar de cualquier otra manera el listado; (b) reproducir, ejecutar, exhibir, usar y acceder a la lista con fines de administración y demostración en relación con la operación y la comercialización del mercado; y (c) reproducir, mostrar, distribuir y usar de cualquier otra manera las características de la marca del Programador que este le haya suministrado a GitHub conforme a lo dispuesto en el presente acuerdo únicamente para su uso en relación con el mercado y para cumplir con sus obligaciones conforme al acuerdo. - -**2.3** Además de las licencias concedidas anteriormente, GitHub puede incluir características de la marca del Programador suministradas por el programador para GitHub conforme a lo dispuesto en el presente acuerdo en cualquier presentación, comunicación, material de marketing, comunicados de prensa, listas de clientes (incluyendo, entre otras, las listas de clientes, publicadas en los sitios web de GitHub), campañas publicitarias y otras garantías publicitarias para propósitos de comercializar el mercado. Si el Programador descontinúa la distribución de productos específicos del programador en el mercado, GitHub dejará de usar las características de marca de los productos del Programador descontinuados después de un período de tiempo comercialmente razonable. Nada en el presente acuerdo otorga al Programador un derecho a usar ninguna de las características de la marca GitHub. - -**2.4** El programador otorga a cada usuario final un derecho o licencia no exclusivo, en todo el mundo, para llevar a cabo, mostrar y usar los productos del Programador y cualquier contenido al que se acceda o se transmita a través de los productos del Programador en relación con el mercado. El Programador debe incluir un acuerdo de licencia de usuario final ("EULA") por separado en sus productos de Programador que regirá los derechos del usuario final sobre los productos del Programador en lugar de la frase anterior. El Programador reconoce y acepta que el EULA aplicable para cada producto de Programador se encuentra únicamente entre el Programador y el usuario final. GitHub no será responsable, ni tendrá ninguna responsabilidad en absoluto, en virtud de ningún EULA. - -**2.5** Excepto por los derechos de licencia concedidos en el presente acuerdo, (a) el programador retiene todos los derechos sobre los productos del Programador; (b) cada una de las partes conserva todos los derechos que tiene independientes del presente acuerdo, incluyendo los derechos conforme a la ley de derechos de autor de los Estados Unidos o leyes similares de otras jurisdicciones; y (c) cada una de las partes posee todos los derechos, título e interés en sus respectivas características de marca. Cada una de las partes es responsable de proteger y hacer cumplir sus propios derechos respectivos y ninguna de las partes tiene la obligación de hacerlo en nombre del otro. - -**2.6** El programador reconoce y acepta que GitHub tendrá derecho a proporcionar el nombre del Programador, la dirección y otros detalles de contacto a cualquier tercero que razonablemente, en la única determinación de GitHub, afirme que el Programador no posee todos los derechos de propiedad intelectual necesarios sobre o para los productos del programador. - -### 3. RESTRICCIONES Y RESPONSABILIDADES - -Independientemente de cualquiera de los requisitos establecidos en la sección 2, Propósito y Concesión de Licencia, antes mencionados, el Programador reconoce y acepta que su uso del mercado y la participación en el programa están explícitamente condicionados al apego del Programador al presente acuerdo, incluyendo, entre otras, las restricciones y los requisitos de cumplimiento establecidos en la presente sección 3. - -**3.1** El Programador acepta que protegerá la privacidad y los derechos legales de todos los usuarios finales. Si un usuario final proporciona a un Programador, o el producto de lo contrario recopila, divulga, accede o usa, nombres de usuario final, contraseñas u otra información personal, el Programador debe (a) informar a los usuarios finales que dicha información estará disponible para los productos del programador; y (b) proporcionar un aviso de privacidad legalmente adecuado y protección a los usuarios finales. Además, los productos de Programador solo pueden usar la información para el propósito limitado para el cual el Programador ha obtenido permiso del usuario final. Si los productos del Programador almacenan o transmiten información personal o confidencial proporcionada u obtenida por los usuarios finales, entonces el Programador debe asegurarse de que toda esa actividad se realice de manera segura y deba responder de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" de GitHub o de los usuarios finales del mercado. - -**3.2** Para usar y acceder a la API de GitHub, el Programador debe obtener las credenciales de la API (un "token") al convertirse en un suscriptor. El Programador no puede compartir su token con ningún tercero, debe mantener seguro dicho token y toda la información de inicio de sesión y usará el token como el único medio del programador para acceder a la API de GitHub. - -**3.3** El programador reconoce y acepta que no participará en ninguna actividad con el mercado, incluyendo la distribución de productos del programador, que viola las políticas del mercado o que: - -- 1\. Viola cualquier ley o normativa aplicable o promueve actividades ilícitas; -- 2\. Contiene o instala cualquier malware o exploits activos, o utiliza nuestra plataforma para la entrega de exploits (como parte de un sistema de comando y control); -- 3\. Interfiere, altera, interrumpe, daña o accede de manera no autorizada a las máquinas, los sistemas, el hardware, los servidores, las redes, los dispositivos, los datos u otras propiedades o servicios de cualquier tercero; -- 4\. Incluye contenido falso o engañoso; -- 5\. Que infrinja cualquier derecho de propiedad de cualquiera de las partes, incluidos la patente, el nombre comercial, el secreto comercial, la propiedad intelectual, el derecho a publicidad o cualquier otro derecho; -- 6\. Que sea calumnioso, difamatorio o fraudulento; -- 7\. Habilita la descarga no autorizada de contenido de streaming o medios; -- 8\. Muestra o vincula a contenido ilegal; -- 9\. Acosa, abusa, amenaza o incita a cualquier persona o grupo, incluyendo los empleados, los funcionarios y los agentes de GitHub, o cualquier usuario final; -- 10\. Que constituya o contenga contenido sexualmente explícito u obsceno; -- 11\. Sea discriminatorio o abusivo hacia cualquier persona o grupo; -- 12\. Desvía a los usuarios finales o proporciona enlaces a cualquier otro sitio que imita al mercado o se hace pasar a sí mismo como mercado. - -**3.4** El Programador no podrá, en ningún caso, a través de productos de desarrollo o de cualquier otra manera, empaquetar nuevamente o revender el mercado, la API de GitHub o los datos de uso. Al Programador no se les permite usar la API de GitHub ni ningún dato de uso de ninguna manera que pueda socavar la seguridad del servicio, la API de GitHub, los datos de uso o cualquier otro dato o información almacenada o transmitida utilizando el mercado. Además, el Programador no debe, y no intentará, interferir, modificar o inhabilitar ninguna característica, control de funcionalidad o seguridad del mercado o de la API de GitHub, rechazar, evitar, eludir, eliminar, desactivar o impedir ningún mecanismo de protección para el mercado o la API de GitHub, o realizar ingeniería inversa, descompilar, desmontar o derivar código fuente, ideas subyacentes, algoritmos, estructura o formulario organizativo desde el mercado o la API de GitHub. - -**3.5** El Programador reconoce que el Programador es el único responsable y que GitHub no tiene responsabilidad ni obligación de ningún tipo, por el contenido, desarrollo, operación, soporte o mantenimiento de los productos del programador. Sin limitar el comienzo, el Programador será el único responsable de: -- (i) la instalación técnica y el funcionamiento de sus productos de Programador; -- (ii) crear y mostrar información y contenido sobre, a través o dentro de sus productos de Programador; -- (iii) asegurar que sus productos de Programador no violen o infrinjan los derechos de propiedad intelectual de un tercero; -- (iv) asegurar que los productos del Programador no sean ofensivos, profanos, obscenos, injuriosos o ilegales; -- (v) asegurar que sus productos de Programador no contengan o introduzcan software malintencionado en el mercado, la API de GitHub, cualquier dato de uso u otros datos almacenados o transmitidos utilizando el mercado; y -- (vi) asegurar que sus productos de Programador no estén diseñados o utilizados con el fin de enviar mensajes electrónicos comerciales a ningún usuario, agente o usuario final de GitHub.com sin su consentimiento. - -**3.6** El programador respetará y cumplirá con las limitaciones técnicas e implementadas por políticas de la API de GitHub y las restricciones del presente acuerdo en el diseño y la implementación de productos para Programador. Sin perjuicio de lo anterior, el Programador no violará ninguna limitación de tasa explícita en la convocatoria o el uso de la API de GitHub. - -**3.7** GitHub se reserva el derecho a rescindir el presente acuerdo de inmediato si GitHub determina que el programador ha incumplido cualquier requisito u obligación de la presente sección 3. - -**3.8** Ninguna disposición del presente Acuerdo impedirá que alguna de las partes desarrolle y/o publique aplicaciones que sean similares o que compitan de cualquier otra manera con las solicitudes de la otra parte. - -### 4. ELIMINACIONES - -**4.1** Tus eliminaciones. Al proporcionar a GitHub una notificación por escrito de treinta (30) días antes del 1er día del mes calendario subsiguiente, puedes eliminar tus anuncios de la distribución futura por medio del mercado, pero debes cumplir con el presente acuerdo para cualquier lista distribuida a través del mercado, incluyendo, entre otros, los requisitos de reembolso. Eliminar tu lista de la distribución futura por medio del mercado no (a) afecta los derechos de licencia de los usuarios finales que previamente compraron o instalaron tu perfil o (b) cambia tu obligación de entregar o apoyar un listado que haya sido adquirido o instalado previamente por los usuarios. - -Sin perjuicio de lo anterior, en ningún caso GitHub mantendrá en ninguna parte del mercado, ninguna lista que hayas eliminado del mercado y le haya dado un aviso por escrito a GitHub de que dicha eliminación se debió a: - -- (i) una acusación de infracción o infracción real de cualquier derecho de autor, marca registrada, secreto comercial, imagen comercial, patente u otro derecho de propiedad intelectual de ninguna persona, -- (ii) una acusación de difamación o difamación real, -- (iii) una acusación de violación o violación real de los derechos de publicidad o privacidad de un tercero, o -- (iv) una acusación o determinación de que dicha lista no cumple con la legislación aplicable. - -Si eliminas una lista del mercado conforme a las cláusulas (i), (ii), (iii) or (iv) de la presente sección 4.1 y un usuario final que compró dicho listado dentro de un año antes de la fecha de retirada, GitHub no es responsable de los reembolsos al comprador afectado de ninguna cantidad pagada por dicho cliente final durante el año anterior a la fecha de retirada de dicha lista afectada. - -**4,2** Revisión y eliminaciones de GitHub. Si bien GitHub no está obligada a supervisar el listado o su contenido, GitHub puede, en cualquier momento, revisar o evaluar tu lista para cumplir con el presente acuerdo, las políticas del programa de mercado y cualquier otro término, obligación, ley o regulación aplicables. GitHub se reserva el derecho de negarse a incluir una lista en el mercado a su entera discreción. Es posible que se te solicite que proporciones información sobre ti (como la identificación o los detalles de contacto) como parte del proceso de registro del mercado o como parte de tu uso continuo del mercado. Aceptas que cualquier información que le des al mercado siempre será precisa, correcta y actualizada. Como parte de la especificación de tu lista, GitHub puede pedirte que incluyas en el archivo la información de tu lista, como tu nombre y dirección de correo electrónico. GitHub puede usar esta información cuando presente la lista en nuestro directorio o para otros usos. - -Si notificas a GitHub o de otra forma tiene conocimiento y determina a su exclusivo criterio que una lista o cualquier parte de la misma o de tus características de marca: -- (a) viola los derechos de propiedad intelectual o cualquier otro derecho de terceros; -- (b) viola cualquier ley aplicable o está sujeta a un mandato; -- (c) es pornográfica, obscena o de otro modo viola las políticas de alojamiento de GitHub u otros términos de servicio que puedan actualizarse por GitHub de vez en cuando a su entera discreción; -- (d) se está distribuyendo incorrectamente; -- (e) puede crear responsabilidad por parte de GitHub o a cualquier tercero; -- (f) se considera como maliciosa o defectuosa por GitHub; -- (g) viola los términos de este Acuerdo o las políticas del programa del mercado; -- (h) la visualización de la lista está afectando a la integridad de los servidores de GitHub (es decir, los usuarios no pueden acceder a dicho contenido o de otra forma experimentan dificultad); -- (i) se considera por GitHub que adiciona un riesgo indebido a los datos de los usuarios finales del mercado o perjudica la experiencia del usuario del mercado o de GitHub; -- (j) está sujeta a quejas de los usuarios en cuanto a la violación de su EULA, o -- (k) de otro modo viola los Términos o este Acuerdo, - -GitHub puede: Evitar que la lista se pueda poner a disposición en el mercado; eliminar el listado del mercado; marcar, filtrar o modificar materiales relacionados (incluyendo, entre otros, descripciones, capturas de pantalla o metadatos); o reclasificar la lista a su exclusivo criterio. GitHub se reserva el derecho a suspender u obstruir cualquier lista del mercado a su exclusivo criterio. - -En el caso de que tu publicación se elimine involuntariamente porque es defectuosa, maliciosa, viola los derechos de propiedad intelectual de otra persona, difama, viola el derecho de publicidad o privacidad de un tercero, o no cumple con las leyes aplicables y un usuario final compró dicho listado dentro de un año antes de la fecha de la eliminación: - -- (i) debes reembolsar al comprador afectado todas las cantidades pagadas por dicho cliente final durante el año anterior a la fecha de eliminación de dicha lista afectada. -- (ii) GitHub puede, a su exclusivo criterio, retener de tus ventas futuras la cantidad en la subsección (i) anterior. - -**4.3** De vez en cuando, GitHub puede revisar si hay actualizaciones disponibles para el listado, incluyendo pero sin limitación a correcciones de errores o funcionalidad mejorada. Si actualizas tu lista en el mercado, aceptas que dicha actualización se solicitará, descargará e instalará automáticamente sin previo aviso. GitHub no ofrece ninguna garantía con respecto al momento de dichas actualizaciones. Para evitar dudas, las actualizaciones al listado están sujetas a los mismos términos y condiciones que el listado, incluyendo, sin limitación, la sección 4.2 del presente acuerdo (revisión y eliminación de GitHub). - -**4.4** Eliminaciones del usuario final. Si un usuario final usa tu producto de Programador de manera que viole los términos, entonces tenemos el derecho de suspender o terminar el acceso del usuario final al producto del Programador sin ninguna responsabilidad para ti. - -### 5. REPRESENTACIONES, GARANTÍAS Y CONVENIOS - -**5.1** El Programador declara y garantiza que el Programador notificó a todos los usuarios de dichas aplicaciones de desarrollo que los datos de su cuenta se transmitirán fuera del servicio y los términos del programador controlarán la privacidad, seguridad o integridad de los datos de la cuenta. El Programador además declara y garantiza que, en la medida en que las aplicaciones del programador almacenen, procesen o transmitan datos de la cuenta, ni el programador ni la aplicación del programador, sin el consentimiento del usuario previo adecuado o excepto en la medida que lo exija la ley aplicable, -- (i) modificará el contenido de los datos de la cuenta de una manera que afecte negativamente a la integridad de los datos de la misma; -- (ii) revelará datos de cuenta a terceros; o -- (iii) usará datos de cuenta para cualquier otro propósito que no sea proporcionar la funcionalidad de la aplicación del Programador a los usuarios de dicha aplicación de Programador. El programador debe mantener y manejar todos los datos de la cuenta de acuerdo con las medidas de privacidad y seguridad razonablemente adecuadas para preservar la confidencialidad y la seguridad de todos los datos de la cuenta y todas las leyes y regulaciones de privacidad aplicables. - -**5.2** El Programador acepta que cumplirá con el Anexo de protección de datos de GitHub. - -**5.3** El Programador declara, garantiza y pacta que: (i) sus productos de Programador y las características de la marca del Programador no violarán, malinterpretarán o infringirán los derechos de propiedad intelectual de ningún tercero; (ii) el Programador cumplirá con todas las leyes y regulaciones locales, estatales, nacionales e internacionales aplicables, incluidas, entre otras, todas las leyes de control de exportación aplicables y mantendrá todas las licencias, permisos y otros permisos necesarios para desarrollar, implementar y distribuir sus productos de desarrollo; y (iii) sus productos de Programador no contendrán o introducirán en el mercado, la API de GitHub, cualquier dato de uso u otros datos almacenados o transmitidos utilizando el mercado, cualquier software malintencionado; (vi) sus productos de Programador no estarán diseñados o se utilizarán con el fin de enviar mensajes electrónicos comerciales a ningún cliente de GitHub, agentes o usuarios finales sin su consentimiento; (v) tendrán todo derecho, poder y autoridad para otorgar las licencias concedidas a GitHub y a los usuarios finales en el presente documento; (vi) reconocerá el derecho de GitHub a cobrar las tarifas de las transacciones y/o los listados conforme a lo dispuesto en la sección 6 del presente documento; las imágenes y el texto que se usan para comercializar los productos de desarrollo o que el programador ha subido al mercado son veraces, precisos y no pretenden confundir o confundir al usuario final. - -**5.4** DESCARGO DE GARANTÍAS. TODOS LOS ASPECTOS DEL MERCADO Y DE LA API DE GITHUB, INCLUYENDO TODOS LOS COMPONENTES DEL SERVIDOR Y DE LA RED, SE PROPORCIONAN "TAL CUAL" Y "SEGÚN DISPONIBILIDAD", SIN GARANTÍAS DE NINGÚN TIPO EN LA MEDIDA EN QUE LO PERMITA LA LEY Y GITHUB RENUNCIA EXPRESAMENTE A TODAS LAS GARANTÍAS, YA SEAN EXPRESAS O IMPLÍCITAS, INCLUYENDO, ENTRE OTRAS, CUALQUIER GARANTÍA IMPLÍCITA DE COMERCIABILIDAD, TÍTULO, IDONEIDAD PARA UN PROPÓSITO PARTICULAR Y NO EL DE INFRACCIÓN. EL PROGRAMADOR RECONOCE QUE GITHUB NO GARANTIZA QUE EL MERCADO O LA API DE GITHUB NO SE INTERRUMPIRÁN, OPORTUNAMENTE, DE MANERA SEGURA, SIN ERRORES O QUE ESTARÁ LIBRE DE VIRUS, MALWARE O GUSANOS (TAMBIÉN CONOCIDO COMO CÓDIGO INFORMÁTICO U OTRA TECNOLOGÍA ESPECÍFICAMENTE DISEÑADA PARA INTERRUMPIR, INHABILITAR O DAÑAR TU SOFTWARE, HARDWARE, SISTEMA INFORMÁTICO O RED) Y NINGUNA INFORMACIÓN O ASESORAMIENTO OBTENIDO POR PARTE DE UN PROGRAMADOR DE GITHUB O A TRAVÉS DEL MERCADO O DE LA API DE GITHUB CREARÁ NINGUNA GARANTÍA QUE NO ESTÉ EXPRESAMENTE ESTABLECIDA EN LOS PRESENTES TÉRMINOS. GITHUB NO ES RESPONSABLE Y ESPECÍFICAMENTE RECHAZA CUALQUIER RESPONSABILIDAD POR CUALQUIER USO NO AUTORIZADO DE PRODUCTOS DEL PROGRAMADOR FUERA DEL MERCADO. - -### 6. PRECIOS Y TÉRMINOS DE PAGO - -**6.1** GitHub será el comerciante de los productos de Programador comprados por usuarios finales a través del mercado. - -**6.2** Los precios de las listas del mercado de las aplicaciones del Desarrollador se configurarán en dólares estadounidenses (USD). El desarrollador tiene un control total sobre la fijación de precios para cada listado y una vez establecido, dicho precio no se puede cambiar. Puedes retirar un plan de precios para un listado existente y agregar un nuevo plan de precios para dicho listado, siempre que dicho plan de precios nuevo no afecte de forma negativa a los usuarios finales existentes. Los precios que configuraste para los productos de Programador determinarán la cantidad de pago que recibirás. GitHub remitirá el 75% del precio de venta en dólares estadounidenses sin reducción para los impuestos, excepto para cualquier retención de impuestos que se requiera conforme a la legislación aplicable. El 25% restante del precio de venta se asignará y retendrá por GitHub. Al final de cada mes y al alcanzar un valor mínimo de $500 USD, GitHub reenviará tu parte de los pagos. - -**6.3** Requisitos de Reembolso. Serás responsable de especificar los términos y condiciones relativos a los reembolsos a tus usuarios finales. En ningún caso GitHub será responsable de proporcionar ayuda alguna con los reembolsos, ni será GitHub será responsable del pago de ningún reembolso. - -**6.4** Apoyas tu producto de Programador. Serás el único responsable del soporte y el mantenimiento de tus productos de Programador y de cualquier queja sobre tus productos de Programador. Tu información de contacto de soporte será mostrada en cada página de detalles de la aplicación y estará a disposición de los usuarios con fines de soporte al cliente. Si no se proporciona el soporte adecuado para tus productos de Programador, se puede dar como resultado una exposición del producto menos destacada o, en algunos casos, la eliminación del mercado o en cualquier otro lugar en GitHub.com donde los productos del programador previamente comprados o descargados se almacenen en nombre de los usuarios. - -### 7. PROPIEDAD - -Sujeto a las licencias limitadas expresamente establecidas en el presente Acuerdo, nada en el presente acuerdo transfiere o asigna a una parte ninguno de los derechos de propiedad intelectual de la otra parte sobre sus características de marca u otra tecnología, y nada en el presente acuerdo transfiere o asigna a una parte ninguno de los derechos de propiedad intelectual de la otra parte. - -### 8. LIMITACIÓN DE RESPONSABILIDAD - -BAJO NINGUNA CIRCUNSTANCIA Y BAJO NINGUNA TEORÍA LEGAL (YA SEA EN EL CONTRATO, AGRAVIO, NEGLIGENCIA O DE CUALQUIER OTRA MANERA) GITHUB, O SUS AFILIADOS, EJECUTIVOS, DIRECTORES, EMPLEADOS, AGENTES O PROVEEDORES SERÁN RESPONSABLES ANTE EL PROGRAMADOR O CUALQUIER TERCERO CONFORME A LO DISPUESTO EN EL PRESENTE ACUERDO POR NINGÚN DAÑO INDIRECTO, INCIDENTAL, ESPECIAL, EJEMPLAR, CONSECUENTE, PUNITIVO U OTRO DAÑO SIMILAR, INCLUYENDO PÉRDIDAS DE BENEFICIOS, VENTAS O NEGOCIOS PERDIDOS, DATOS PERDIDOS, INTERRUPCIONES COMERCIALES O CUALQUIER OTRA PÉRDIDA INCURRIDA POR EL PROGRAMADOR O CUALQUIER TERCERO EN RELACIÓN EL PRESENTE ACUERDO, INDEPENDIENTEMENTE DE SI SE HA ADVERTIDO A LOS DESARROLLADORES DE LA POSIBILIDAD O DE HABER PODIDO PREVER DICHOS DAÑOS, INDEPENDIENTEMENTE DE CUALQUIER DISPOSICIÓN CONTRARIA EN EL PRESENTE ACUERDO, LA RESPONSABILIDAD AGREGADA DE GITHUB AL PROGRAMADOR O A CUALQUIER TERCERO QUE SURJA DEL PRESENTE ACUERDO NO SUPERARÁ LOS SEIS (6) MESES DE GASTO. - -### 9. INDEMNIZACIÓN - -**9.1** En la medida máxima permitida por la legislación aplicable, el Programador acepta defender, indemnizar y eximir de toda responsabilidad a GitHub, sus filiales y sus respectivos directores, funcionarios, empleados y agentes de cualquier reclamación, acciones, demandas o procedimientos, así como cualquier pérdida, responsabilidad, daño, costo y gasto (incluyendo los honorarios razonables de abogados) que surjan de o estén relacionados con (a) el uso del mercado por parte de un programador en violación del presente acuerdo, los términos o cualquier ley o regulación aplicable; (b) productos del programador que infrinjan cualquier derecho de autor, marca registrada, secreto comercial, patente u otro derecho de propiedad intelectual de cualquier tercero; (c) cualquier pérdida o divulgación de datos o información personal por parte de los productos del programador; y (d) EULA (o ToS) del Programador. - -### 10. TERMINACIÓN - -**10.1** El presente acuerdo continuará aplicándose hasta que se rescinda por cualquiera de las partes como se indica a continuación. - -**10.2** Cualquiera de las partes puede rescindir el presente acuerdo por cualquier motivo al proporcionar un aviso por escrito a los otros cuarenta y cinco (45) días anteriores al mes calendario inmediatamente siguiente. Durante este período de 45 días, los términos vigentes en el momento en que se proporcionó la notificación de terminación regirán por la duración del período de aviso de 45 días hasta la fecha de terminación real. - -**10.3** GitHub puede rescindir el presente acuerdo en cualquier momento si (a) has incumplido alguna disposición del presente acuerdo o (b) que GitHub está obligado a hacerlo por ley. - -**10.4** Efectos de la terminación por parte del Programador. Al recibir una notificación por escrito con anticipación de cuarenta y cinco (45) días de terminación por parte del Programador, se inhabilitará al programador para que no tome nuevos clientes a través del mercado. Cualquier tarifa pendiente se reenviará tras la terminación y la eliminación del producto de Programador del mercado. Si se inicia la terminación como resultado de una modificación de GitHub a estos términos (sección 11), los términos en vigencia inmediatamente anteriores de dicha modificación regirán por la duración del período de aviso de 45 días hasta la fecha de terminación real. - -**10.5** Las obligaciones en las secciones 2, 3, 4, 5, 8, 9 y 12-18 sobrevivirán a cualquier vencimiento o terminación del presente acuerdo. - -### 11. MODIFICACIÓN - -El programador reconoce y acepta que GitHub puede modificar el presente acuerdo, el mercado, la API de GitHub, las políticas generales de la API, la política de privacidad de GitHub, los ToS del programa de Programadores de GitHub y los ToS de GitHub.com de vez en cuando (una "Modificación"). Todas las modificaciones se comunicarán a través del mercado, el sitio web de GitHub en www.GitHub.com o mediante una forma de comunicación directa de GitHub al Programador. El Programador reconoce y acepta que dichas modificaciones pueden implementarse en cualquier momento y sin previo aviso al Programador. El Programador debe, dentro de los cuarenta y cinco (45) días a partir de la fecha de la primera notificación de cualquier modificación (o dicho período de tiempo más corto especificado en el aviso de la(s) modificación es)) (el "Período de Conformidad") cumplir con dichas modificaciones mediante la implementación y el uso de la versión más reciente de la API de GitHub en la versión más reciente de los productos del Programador y la realización de cualquier cambio en los productos del programador que puede requerirse como resultado de dichas modificaciones. El Programador reconoce que una modificación puede tener un efecto adverso en los productos del programador, incluyendo, entre otros, el cambio de la manera en que las aplicaciones se comunican con la API de GitHub. GitHub no será responsable de ningún tipo del Programador o de ningún usuario final con respecto a dichas modificaciones o cualquier efecto adverso derivado de dichas modificaciones. El acceso continuado del Programador o el uso del mercado o de la API de GitHub después del período de conformidad constituirá la aceptación vinculante de la(s) modificación(es) en litigio. - -### 12. ASIGNACIÓN; ACUERDO COMPLETO; REVISIONES - -**12.1** El programador no puede, directa o indirectamente, por operación de la ley o de cualquier otra manera, asignar la totalidad o parte del presente acuerdo o los derechos del Programador conforme a lo dispuesto en el presente acuerdo o delegar el desempeño de las obligaciones del Programador conforme a lo dispuesto en el presente acuerdo sin el consentimiento previo por escrito de GitHub. Los derechos otorgados en el presente acuerdo pueden asignarse o transferirse por GitHub sin la aprobación previa del programador. Además, GitHub puede delegar sus responsabilidades u obligaciones conforme a lo dispuesto en el presente acuerdo sin el consentimiento del Programador. - -**12.2** El presente acuerdo, junto con los términos, constituye el acuerdo completo entre las partes con respecto al objeto del presente acuerdo. El incumplimiento por parte de GitHub de hacer cumplir en cualquier momento cualquier disposición del presente acuerdo no constituye una renuncia a esa disposición o a cualquier otra disposición del presente acuerdo. - -### 13. DIVISIBILIDAD - -Si alguna disposición del presente acuerdo se considera inejecutable por parte de un tribunal de jurisdicción competente, dicha disposición se modificará por el Tribunal y se interpretará de manera que se logre mejor la disposición original en la medida en que lo permita la ley y las disposiciones restantes del presente acuerdo permanecerán vigentes. - -### 14. RELACIÓN DE LAS PARTES - -Las partes son contratistas independientes. El presente acuerdo no crea una relación de colaboración, franquicia, empresa conjunta, agencia, fiduciaria o de empleo entre las partes. El Programador acepta que cada miembro del grupo de compañías al que pertenece GitHub será un tercero beneficiario del presente acuerdo y que dichas otras compañías tendrán derecho a hacer cumplir y basarse directamente en cualquier disposición del presente acuerdo que confiere un beneficio o otorga un derecho a favor o GitHub. Ninguna otra persona, empresa o entidad legal será un tercero beneficiario del acuerdo. - -### 15. AVISOS - -Todas las notificaciones que GitHub debe proporcionar al Programador conforme a lo dispuesto en el presente acuerdo pueden entregarse por escrito (i) por el servicio de entrega a domicilio ("Courier") reconocido a nivel nacional o por correo electrónico a la dirección de correo electrónico de contacto proporcionada por el programador a GitHub; o (ii) correo electrónico a la dirección de correo electrónico proporcionada por el Programador. mail to the contact mailing address provided by Developer to GitHub; or (ii) electronic mail to the electronic mail address provided by Developer. Developer must give notice to GitHub in writing by Courier or U.S. GitHub, Inc., en atención al: Departamento Jurídico, 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107 EE. UU. Todas las notificaciones se considerarán entregadas inmediatamente después de la entrega por correo electrónico, o si se entregan de otra manera al recibirlo o, si son anteriores, dos (2) días hábiles después de haber sido depositadas por correo o con un mensajero como se permitió anteriormente. - -### 16. LEGISLACIÓN APLICABLE - -El presente acuerdo se regirá por las leyes del estado de California sin tener en cuenta los principios de conflicto de leyes. Por la presente, el Programador acepta expresamente someterse a la jurisdicción personal exclusiva de los tribunales federales y estatales del estado de California, en el Condado de San Francisco, con el fin de resolver cualquier disputa relacionada con el presente acuerdo. Sin perjuicio de lo anterior, GitHub tendrá derecho a buscar acciones cautelares u otros tipos de remedio legal urgente en cualquier jurisdicción. - -### 17. RESTRICCIONES DE EXPORTACIÓN - -LOS PRODUCTOS PARA PROGRAMADORES QUE SE DISTRIBUYEN POR MEDIO DEL MERCADO PUEDEN ESTAR SUJETOS A CONTROLES DE EXPORTACIÓN O RESTRICCIONES POR PARTE DE LOS ESTADOS UNIDOS U OTROS PAÍSES O TERRITORIOS. EL PROGRAMADOR ACEPTA CUMPLIR CON TODAS LAS LEYES Y REGULACIONES VIGENTES EN LOS ESTADOS UNIDOS Y LAS EXPORTACIONES INTERNACIONALES. ESTAS LEYES PUEDEN INCLUIR RESTRICCIONES EN LOS DESTINOS, EL CONTENIDO Y/O LOS USUARIOS FINALES. - -### 18. DATOS DE USO -Con el fin de operar y mejorar el mercado, GitHub puede recopilar datos de uso del mercado y API de GitHub o en cualquier lugar que los productos de programador previamente comprados o descargados se almacenen en nombre de los usuarios finales por parte de GitHub. Los datos de uso se mantendrán de acuerdo con las políticas de privacidad de GitHub vigentes en ese momento. Los datos de uso limitados pueden estar disponibles para su uso por parte del Programador a la exclusiva discreción de GitHub. - -# Anexo 1: Anexo de protección de datos - -El presente anexo de protección de datos (este "Anexo") se adjunta y forma parte del acuerdo del Programador del mercado de GitHub entre tú y GitHub (el "Acuerdo"). Los términos que no se definen en el presente Anexo tienen los significados que se les atribuyen en el Acuerdo. En el caso de un conflicto o incoherencia, los términos del presente Anexo sustituirán a los del acuerdo. - -**A1-1. Propósito y ámbito** GitHub mantiene la información personal de personas en todo el mundo, algunas de las cuales son residentes de países y áreas con leyes de protección de datos sólidas. Este Anexo establece tus responsabilidades cuando recibes y procesas cualquier dato protegido de GitHub. - -**A1-2. Definiciones** - -- a. "Leyes Aplicables de Protección de Datos" significa cualquier ley, regulación, marco de trabajo regulatorio u otras legislaciones relacionadas con el procesamiento y uso de la Información Personal de acuerdo a como sean aplicables al Acuerdo, incluyendo: - - El Reglamento General de Protección de Datos de la UE 2016/679 (“GDPR”), en conjunto con cualquier regulación o ley correspondiente o implementada equivalente; - - La Ley de Privacidad de los Consumidores de California de 2018, Cal. Civ. Code §§1798.100 et seq. ("CCPA"); and - - La Ley de Protección de Datos del Reino Unido de 2018 y la implementación de RGDP que se contiene en la misma. -- b. "Información personal" se refiere a cualquier información que se relacione con Usuario Final de GitHub, cliente o empleado individuales que pudiera, sola o en conjunto con otra información, identificarle personalmente, ya sea que la suministre GitHub para que el desarrollador la procese o que la genere el Desarrollador en el transcurso de llevar a cabo sus obligaciones bajo este acuerdo. -- c. "Procesamiento" se refiere a cualquier operación o conjunto de operaciones realizadas en los datos protegidos de GitHub, ya sea por medios manuales o automáticos, que incluyen recopilación, registro, organización, almacenamiento, adaptación, alteración, recuperación, consulta, uso, divulgación mediante transmisión, difusión o puesta a disposición, bloqueo, supresión o destrucción de cualquier otra manera. -- d. "Datos protegidos" se refiere a cualquier información confidencial transferida por GitHub al Programador sobre un usuario final de GitHub, que incluya la información personal, los metadatos, los datos de uso u otros datos o información que esté asociada con los usuarios finales de GitHub. - -**A1-3. Cumplimiento con las Leyes de Transferencia de Datos** - -- a. Cumplimiento con GitHub. GitHub cumple con las Leyes de Protección de Datos Aplicables. GitHub se basa en las Cláusulas Contractuales Estándar ("SCCs") para todas las transferencias fuera de la Unión Europea, Área Económica Europea, Reino Unido, y Suiza para proporcionar sus servicios. Adicionalmente, GitHub está certificado en el Marco del Escudo de Privacidad de U.E. - E.U.A. y de Suiza - E.U.A. y los compromisos que estos implican, aunque GitHub no depende de los de U.E.-E.U.A. Privacy Shield Framework as a legal basis for transfers of Personal Information in light of the judgment of the Court of Justice of the EU in Case C-311/18. GitHub solo transferirá información personal al Programador para los fines limitados y especificados para los cuales se recopiló. -- b. Cumplimiento del Programador. El desarrollador representa y garantiza que (i) cumplirá con las Leyes de Protección de Datos Aplicables; y (ii) cumplirá con los requisitos del Área Económica Europea y la ley Suiza de protección de datos con respecto a la recolección, uso, transferencia, retenció y otro tipo de Información Personal del Área Económica Europea, Reino Unido y Suiza. Todas las transferencias de Información Personal a un país tercero o a una organización internacional estarán sujetos a las salvaguardas adecuadas como se describe en el artículo 46 de la RGPD y dichas transferencias y salvaguardas se documentarán de acuerdo con el artículo 30(2) de la misma. - -**A1-4. Protección de datos** - -- a. Notificaciones. El Programador debe identificarse como el recopilador y procesador de todos los datos que reúne del usuario final. El Programador no debe limitarse a recopilar información personal en nombre de GitHub. El Programador debe proporcionar un aviso suficiente de sus prácticas de privacidad al usuario final, por ejemplo, al publicar una política de privacidad. -- b. Limitación de propósitos. - - i. GitHub proporcionará a los Programadores los elementos de datos protegidos con el fin de establecer y facilitar una relación entre el Programador y el usuario final y permitir que el Programador brinde servicios al usuario final. El Programador debe limitar su uso de los datos protegidos con ese fin, a menos que el usuario final acepte permitir diferentes usos. - - ii. El Programador debe procesar y comunicar los datos protegidos a terceros únicamente para los fines limitados y específicos de proporcionar sus servicios al usuario final, tal como se describe en su acuerdo con el usuario final, a menos que este acepte permitir diferentes usos. -- c. Calidad y proporcionalidad de los datos. El Programador debe mantener los datos protegidos precisos y actualizados. -- d. Seguridad. El Programador debe tomar todas las medidas de seguridad razonables adecuadas para los riesgos, por ejemplo, contra la destrucción accidental o ilícita, o la pérdida accidental, alteración, divulgación o acceso no autorizado, presentadas al procesar los datos protegidos. -- e. Retención y eliminación de datos. Tras la solicitud razonable de GitHub, a menos que se prohiba por ley, el Programador debe regresar o destruir toda la información personal y los datos relacionados en todas las ubicaciones en las que se almacena después de que ya no sean necesarios para los fines limitados y especificados para los cuales fueron recopilados. El Programador debe tener disponible o desarrollar procesos de destrucción de la información que cumplan con los requisitos de seguridad de GitHub en la sección 3.8 del acuerdo. -- f. Subprocesamiento y transferencia ulterior. El Programador es responsable de las transferencias posteriores de datos protegidos a sus subprocesadores. En caso de que el desarrollador deba transferir los datos protegidos a un tercero, o de que se instale, use o habilite servicios de terceros para procesar dichos datos en nombre del desarrollador, dicho desarrollador deberá garantizar que el tercero proporcionará por lo menos el mismo nivel de protección de la privacidad como se requiere en el presente. - -**A1-5. Uso de datos protegidos** - -- a. Uso permitido. El Programador solo puede procesar los datos protegidos para los fines establecidos en la sección 4 (b) (i) y ningún otro propósito. -- b. Sin uso en Marketing. El Programador no debe usar los datos protegidos para publicitar ningún producto o servicio de terceros y no puede vender los datos protegidos a ningún tercero. -- c. Decisiones automatizadas. En el caso de que el Programador tome decisiones automatizadas que afecten los derechos de los clientes de GitHub, incluyendo el empleo, el crédito o el estado, el Programador debe proporcionar un aviso a las personas. - -**A1-6. Cumplimiento** - -- a. El programador debe cumplir con las solicitudes razonables de información sobre sus prácticas de privacidad y el uso de datos de la siguiente manera: - - i. A petición, el Programador hará su declaración de privacidad, política de privacidad, aviso de privacidad o cualquier documentación similar disponible. El Programador también proporcionará un aviso de cualquier informe de cumplimiento relevante, incluyendo el cumplimiento del escudo de la privacidad. - - ii. El Programador cumplirá con las obligaciones de seguridad de la información y auditoría en la sección 3.7 del acuerdo del Programador del mercado de GitHub. - -**A1-7. Terminación** - -- a. Suspensión. En el caso de que el Programador incumpla con sus obligaciones de mantener un nivel adecuado de protección de la privacidad, GitHub puede suspender de forma temporal la transferencia de datos protegidos o prohibir la recopilación y el procesamiento de datos protegidos en nombre de GitHub hasta que se repare el incumplimiento o se termine el acuerdo. -- b. Terminación con causa. GitHub puede rescindir el Acuerdo sin perjuicio de cualquier otra reclamación en derecho o en equidad en el caso de que: - - i. el Programador notifique a GitHub que ya no puede cumplir con sus obligaciones de privacidad; - - ii. la transferencia, recopilación o procesamiento de los datos protegidos se haya suspendido temporalmente por más de un mes conforme a 7(a); - - iii. el Programador esté en incumplimiento sustancial o persistente de cualquier garantía o representación conforme a lo dispuesto en el presente anexo de protección de datos; - - iv. el Programador ya no dirige el negocio, se disuelve, entra en suspensión de pagos o se realiza una orden de liquidación en nombre del Programador. -- c. Incumplimiento. El incumplimiento de lo dispuesto en el presente anexo de protección de datos se considera una violación material conforme al acuerdo de servicios maestros. -- d. Notificación. En el caso de que el programador determine que ya no puede cumplir con sus obligaciones de privacidad conforme a lo dispuesto en el presente acuerdo, debe notificar a GitHub de inmediato. En el caso de que el programador haya sido certificado bajo el escudo de la privacidad y permita que la certificación caduque o no pueda permanecer certificada bajo el escudo de la privacidad, el Programador debe notificar a GitHub de inmediato. -- e. Modificaciones. GitHub puede modificar el presente Anexo de vez en cuando, según lo requiera la ley, con un aviso de treinta días para el Programador. Si el Programador no puede cumplir con las modificaciones del anexo, GitHub puede rescindir el acuerdo. -- f. Después de la terminación, el Programador debe: - - i. tomar las medidas razonables y apropiadas para detener el procesamiento de los datos protegidos; - - ii. dentro de los treinta días posteriores a la terminación, eliminar cualquier tienda de desarrolladores de datos protegidos en nombre de GitHub; y - - iii. proporcionar a GitHub la garantía razonable de que el Programador ha dejado de procesar los datos protegidos y eliminado los datos protegidos almacenados. - -**A1-8. Responsabilidad por el procesamiento de datos** -- a. Responsabilidad directa. El programador será responsable ante GitHub de los daños reales causados por cualquier incumplimiento del presente anexo sujeto a los términos de la sección 8, Limitación de Responsabilidad del Acuerdo del Programador del Mercado. diff --git a/translations/es-XL/content/github/site-policy/github-marketplace-terms-of-service.md b/translations/es-XL/content/github/site-policy/github-marketplace-terms-of-service.md deleted file mode 100644 index 173fa43a1a..0000000000 --- a/translations/es-XL/content/github/site-policy/github-marketplace-terms-of-service.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -title: Términos de servicio de Mercado GitHub -redirect_from: - - /articles/github-marketplace-terms-of-service -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -¡Bienvenido a Mercado GitHub ("Mercado")! Estamos felices de que estés aquí. Por favor, lee cuidadosamente estos Términos de Servicio ("Términos del Mercado") antes de ingresar o usar Mercado GitHub. Mercado GitHub es una plataforma que te permite comprar productos de programador (de forma gratuita o por un cargo) que se pueden utilizar con tu cuenta GitHub.com ("Productos de programador"). Aunque GitHub, Inc. lo vende, ("GitHub", "nosotros") los productos de programador pueden elaborarse y mantenerse por GitHub o por proveedores de software terceros y podría ser necesario que aceptes los términos de servicio por separado. Tu uso y/o compra de Productos de Programador está sujeta a estos Términos de Mercados y a las tarifas aplicables y también puede estar sujeta a términos adicionales proporcionados por el licenciador de ese Producto de Programador (el "Proveedor del Producto"). - -Al usar el Mercado, aceptas estar obligado por estas Condiciones de Mercado. - -Fecha de entrada en vigencia: 11 de octubre de 2017 - -### A. Términos de servicio de GitHub.com - -GitHub proporciona el mercado y se rige por los [Términos de servicio](/articles/github-terms-of-service/) o el [Términos de servicio corporativos](/articles/github-corporate-terms-of-service/) ("Términos de GitHub"), dependiendo de tu tipo de cuenta, así como de los presentes términos del mercado. Si configuras los Productos de Programador para que trabajen con una o más cuentas en el sitio web GitHub.com, tu uso de los Productos de Programador también se regirá por sus Términos de GitHub aplicables. Cualquier término en mayúsculas no definido en este documento se definirá en los términos aplicables de GitHub. - -No puedes utilizar un Producto de Programador para violar tus Términos de GitHub aplicables. Muchos de estos Productos de Programadro se utilizan exclusivamente para realizar tareas automatizadas. Además, varios usuarios pueden dirigir las acciones de un Producto de Programador. Sin embargo, si compras y/o configuras un Producto de Programador en tu cuenta o eres propietario de una cuenta con un Producto de Programador integrado, entonces serás responsable de las acciones del Producto del Programador que se llevan a cabo en o a través de tu cuenta. - -### B. Requisitos de uso - -A fin de poder usar el Mercado, debes tener 13 años o más (si vives en los Estados Unidos; si vives en otro país, debes cumplir con las leyes de edad mínima de tu país), tener una cuenta de GitHub válida y haber aceptado tus términos de GitHub y estos términos de mercado aplicables. - -Si estás de acuerdo con estos Términos de Mercado en nombre de una empresa, organización u otra entidad legal, significa que tienes la autoridad para vincular a esa entidad, a sus afiliados y a todos los usuarios que ingresen al mercado en su nombre a estos Términos del Mercado. Si no tienes autoridad, no debe aceptar estos Términos del Mercado y no puedes utilizar los servicios del mismo. - -### C. Productos de Programador y Proveedores de Productos - -Si instalas y/o compras un Producto de Programador, entonces estás comprando los Productos de Programador de GitHub y tienes que hacer los pagos relacionados directamente a GitHub. Sin embargo, estás recibiendo acceso y los derechos de usar ese Producto de Programador de un proveedor de productos, no de GitHub (a menos que sea un producto de programador propiedad de GitHub). El Proveedor del Producto es el único responsable del Producto de Programador que proporciona, el contenido del mismo y cualquier reclamación que tú o cualquier otra parte pueda tener relacionada con ese Producto de Programador o el uso de ese Producto de Programador. - -No somos parte del acuerdo entre tú y el Proveedor de Productos con respecto a dicho Producto de Programador. No somos responsables de dicho Producto de Programador, el contenido en él, o cualquier reclamación que tú o cualquier otra parte pueda tener relacionada con ese Producto de Programador o el uso de dicho Producto de Programador. Sin embargo, somos un tercero beneficiario del acuerdo entre tú y el proveedor de productos para cada producto de programador y tendremos el derecho (y se considerará que has aceptado el derecho) de hacer cumplir ese acuerdo en tu contra como un tercero beneficiario. - -### D. Pago, calendario de facturación y cancelación - -GitHub tramitará todos los pagos por Productos de Programador. Las condiciones de tu pago y las comisiones se regirán por [Sección K. Pago](/articles/github-terms-of-service/#k-payment) o la sección análoga de tus Condiciones de GitHub aplicables. Al usar el Mercado aceptas pagar a GitHub cualquier cargo incurrido en relación con tu compra del Producto de Programador. Cada compra es un contrato electrónico entre tú y GitHub y tú y el Proveedor de Productos. Eres responsable de proporcionarnos un medio de pago válido para las compras de Productos de Programador. Si sólo estás comprando productos de programador gratuitos, no estás obligado a proporcionar información de pago. - -**Calendario de facturación; Sin reembolsos.** Tu calendario de pago se determina por el calendario de pago que elegiste cuando creaste tu cuenta de GitHub (por ejemplo, gratis, mensual, anual). Para planes de pago mensuales o anuales, las compras en el mercado se facturan por adelantado de forma mensual o anual respectivamente y no son reembolsables. No habrá reembolsos o créditos por meses parciales de servicio, reembolsos por descenso de categoría o reembolsos por meses sin uso; sin embargo, el servicio permanecerá activo durante el período de facturación pagado. Si deseas cancelar los servicios del Producto de Programador, puedes hacerlo entrando en sus Ajustes en la barra de navegación global en la parte superior de la pantalla. - -Si tienes una pregunta, inquietud o disputa con respecto a tu facturación, ponte en contacto con [el soporte de GitHub](https://support.github.com/contact). - -### E. Tus datos y la política de privacidad de GitHub - -**Privacidad.** Cuando compras o te suscribes a un Producto de Programador, GitHub debe compartir cierta información personal (como se define en la [Declaración de privacidad de GitHub](/articles/github-privacy-statement/)) con el proveedor de productos para proporcionarte el producto de programador, independientemente de tu configuración de privacidad. Dependiendo de los requisitos del producto para programador que elijas, GitHub puede compartir solamente el nombre de tu cuenta de usuario, ID y la dirección de correo electrónico principal o el acceso al contenido de tus repositorios, incluyendo la capacidad de leer y modificar tus datos privados. Podrás ver el alcance de los permisos que el Producto del Programador está solicitando y aceptarlos o rechazarlos cuando le concedes la autorización a través de OAuth. En línea con la [Declaración de privacidad de GitHub](/articles/github-privacy-statement/), sólo proporcionaremos al Proveedor del Producto la cantidad mínima de información necesaria para el propósito de la transacción. - -Si cancelas los servicios del Producto de Programador y revocas el acceso a través de la configuración de tu cuenta, el Proveedor del Producto ya no podrá acceder a tu cuenta. El Proveedor de Producto es responsable de eliminar tu Información Personal de tus sistemas dentro de su ventana definida. Ponte en contacto con el Proveedor del Producto para asegurar que tu cuenta se canceló correctamente. - -**Reclamación de seguridad de datos.** Cuando compras o te suscribes a un Producto de Programador, la seguridad del Producto de Programador y la custodia de tus datos son responsabilidad del Proveedor del Producto. Es tu responsabilidad entender las consideraciones de seguridad de la compra y uso del Producto de Programador para tus propias consideraciones de seguridad, riesgo y cumplimiento. - -### F. Derechos a Productos de Programador - -Los derechos que se te otorgan para usar cualquier Producto de Programador son personales y no son transferibles a terceros, como tus usuarios finales. Cualquier derecho de proporcionar o revender los Productos de Programador a terceros debe otorgarse directamente por el Proveedor del Producto. - -### G. Actualizaciones a Productos de Programador - -De vez en cuando, GitHub.com puede comprobar con servidores remotos (alojados por GitHub o por terceros) si existen actualizaciones disponibles para los Productos de Programador, incluyendo pero sin limitación a correcciones de errores o funcionalidad mejorada. Aceptas que dichas actualizaciones se solicitarán, descargarán e instalarán automáticamente, sin previo aviso. - -### H. Bloqueo de Productos de Programador - -GitHub puede bloquear un Producto de Programador de nuestros servidores, o desactivar su funcionalidad, por razones legales o de política. En el caso que debamos bloquear o desactivar un Producto de Programador, trabajaremos con el Proveedor del Producto para notificar a los usuarios afectados. - -### I. Descargo de responsabilidad; Limitación de responsabilidad; Liberación e indemnización - -**Descargo de responsabilidad.** El uso que hagas del Mercado y de los Productos de Programador obtenidos a través del mercado es bajo tu propio riesgo. Además de lo indicado expresamente, GitHub proporciona el mercado y los Productos de Programador “TAL CUAL” y “SEGÚN ESTÉN DISPONIBLES”. GitHub no hace o implica ninguna garantía o compromiso sobre el mercado y los Productos de Programador, incluyendo, sin limitación a la funcionalidad específica disponible a través del mercado y los Productos de Programador, su fiabilidad, disponibilidad o capacidad para satisfacer tus necesidades. - -Nos reservamos el derecho en cualquier momento y de vez en cuando de modificar o interrumpir, temporal o permanentemente, el mercado b (o cualquier parte de este) con o sin notificación. - -**Limitación de responsabilidades.** Comprendes y aceptas que GitHub no será responsable ante ti o ningún tercero por ninguna pérdida de ganancias, uso, buena voluntad o datos, o por ningún incidente, daños indirectos, especiales, consecuenciales o ejemplares que surjan o resulten de: (i) el uso o la incapacidad de utilizar el mercado o cualquier producto de programador; (ii) cualquier modificación, cambio de precios, suspensión o interrupción del mercado o productos de programador; (iii) el mercado en general o el software o sistemas que hacen que el mercado esté disponible; (iv) acceso no autorizado a tus transmisiones o datos no autorizados; (v) declaraciones o conducta de cualquier tercero, Proveedor de Productos, o Producto del Programador en el mercado; (vi) cualesquier otra interacción de usuario que introduzcas o recibas a través de tu uso del mercado; o (vii) cualquier otro asunto relacionado con el mercado. - -**Liberación e indemnización.** Si tienes una disputa con uno o más Proveedor de Productos, aceptas liberar a GitHub de todos y cada uno de las reclamaciones, demanda y daños (reales y consecuentes) de todo tipo y naturaleza, conocidos y desconocidos, que surjan de o en cualquier forma relacionados con dichas disputas. - -Aceptas indemnizarnos, defendernos y eximirnos de toda responsabilidad contra cualquiera y toda reclamación, responsabilidad y gastos, incluyendo los honorarios de los abogados, que surgen de tu uso del mercado, incluyendo, sin limitación a la violación de estos Términos del Mercado, considerando que GitHub (1) le dé un aviso por escrito de la reclamación, demanda, juicio o procedimiento; (2) te da control exclusivo de la defensa y liquidación del reclamo, demanda, traje o procedimiento (siempre y cuando no pueda liquidar ninguna reclamación, demanda, juicio o procedimiento a menos que la liquidación libere incondicionalmente a GitHub de toda responsabilidad); y (3) te proporciona toda la asistencia razonable, a tu cargo. - -### J. Varios - -1. **Ley aplicable** Aceptas que estos Términos del Mercado y tu uso de los Productos de Programador se rigen por la ley de California y cualquier disputa relacionada con los Productos de Programador debe llevarse ante un tribunal de jurisdicción competente ubicado en o cerca de San Francisco, California. - -2. **No asignable.** GitHub puede asignar o delegar estos Términos del Mercado y/o la [Declaración de privacidad de GitHub](/articles/github-privacy-statement/), total o parcialmente, a cualquier persona o entidad en cualquier momento con o sin tu consentimiento. No puedes asignar ni delegar ningún derecho u obligación bajo los Términos o Declaración de Privacidad del Mercado sin nuestro consentimiento previo por escrito y cualquier asignación no autorizada y delegación por ti es nula. - -3. **Divisibilidad, sin exención y supervivencia.** Si alguna parte de estos Términos del Mercado no es válida o no aplica, esa parte de los Términos del Mercado se interpretará para reflejar la intención original de las partes. Las partes restantes permanecerán en pleno vigor y efecto. El hecho de que GitHub no ejerza o ejecute cualquier derecho o provisión de estos Términos del Mercado no constituirá una renuncia a dicho derecho o disposición. Nuestros derechos bajo estos Términos del Mercado sobrevivirán a cualquier cancelación de estos Términos del Mercado. - -4. **Sin modificaciones; Acuerdo completo.** Estos Términos del Mercado sólo pueden modificarse mediante una enmienda por escrito firmada por un representante autorizado de GitHub, o por la publicación por GitHub de una versión revisada. Estos Términos del Mercado, junto con la [Declaración de Privacidad de GitHub](/articles/github-privacy-statement/), representan la declaración completa y exclusiva del acuerdo entre usted y nosotros. Estos Términos del Mercado reemplazan cualquier propuesta o acuerdo previo oral o escrito y cualquier otra comunicación entre tú y GitHub relacionada con el tema de estos términos. - -5. **Encabezados de las secciones.** A lo largo de estos Términos del Mercado, cada sección incluye títulos de los siguientes términos y condiciones. Los títulos de estas secciones no son legalmente vinculantes. - -6. **Licencia para las Políticas de GitHub.** Estos Términos del Mercado están licenciados bajo esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). - -7. **Póngase en contacto con nosotros.** ¿Preguntas sobre las condiciones del mercado? [Contáctanos](https://support.github.com/contact). diff --git a/translations/es-XL/content/github/site-policy/github-open-source-applications-terms-and-conditions.md b/translations/es-XL/content/github/site-policy/github-open-source-applications-terms-and-conditions.md deleted file mode 100644 index 41fd70c720..0000000000 --- a/translations/es-XL/content/github/site-policy/github-open-source-applications-terms-and-conditions.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Términos y condiciones de la aplicación de código abierto de GitHub -redirect_from: - - /articles/github-open-source-applications-terms-and-conditions -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Estos términos y condiciones de las aplicaciones de código abierto de GitHub ("términos de la aplicación") son un acuerdo legal entre tú (ya sea como individuo o en nombre de una entidad) y GitHub, Inc. sobre el uso de las aplicaciones de GitHub, como GitHub Desktop™ y la documentación asociada ("Software"). Estos Términos de la Aplicación se aplican a la versión ejecutable del Software. El código fuente para el software está disponible por separado y de forma gratuita en los acuerdos de licencia de software de código abierto. Si no estás de acuerdo con todos los términos en los presentes términos de la aplicación, no descargues, instales, uses o copies el software. - -### Conexión a GitHub - -Si configuras el software para que funcione con una o más cuentas en el sitio web GitHub.com o con una instancia de GitHub Enterprise, tu uso del software también se regirá por tus términos de servicio del sitio web GitHub.com aplicables y/o el acuerdo de licencia aplicable a tu instancia de GitHub Enterprise ("términos de GitHub"). - -Cualquier uso del software que viole los Términos de GitHub aplicables también será una violación de estos Términos de la Aplicación. - -### Licencias y avisos de código abierto - -La licencia de código abierto para el Software está incluida en la documentación de "Avisos de Código Abierto" que se incluye con el software. Esa documentación también incluye copias de todas las licencias de código abierto aplicables. - -En la medida en que los términos de las licencias aplicables a los componentes de código abierto requieran que GitHub realice una oferta para proporcionar código fuente en conexión con el software, se hará la presente oferta y puedes ejecutarla poniéndote en contacto con GitHub: https://github.com/contact - -A menos que se acepte lo contrario por escrito con GitHub, tu acuerdo con GitHub siempre incluirá, como mínimo, estos términos de aplicación. Las licencias de software de código abierto para el código fuente del software constituyen acuerdos escritos por separado. En la medida limitada en que las licencias de software de código abierto sustituyan de forma expresa estos términos de aplicación, las licencias de código abierto rigen tu acuerdo con GitHub para el uso del software o componentes específicos incluidos del software. - -### Logotipos de GitHub - -La concesión de licencia incluida con el software no es para las marcas comerciales de GitHub, que incluyen los diseños de logotipos de software. GitHub se reserva todos los derechos de marca comercial y derecho de autor sobre todas las marcas de GitHub. Los logotipos de GitHub incluyen, por ejemplo, los diseños estilizados que incluyen el "logotipo" en el título del archivo en la carpeta "Logotipos". - -Los nombres GitHub, GitHub Desktop, GitHub para Mac, GitHub para Windows, Atom, The Octocat y los logotipos de GitHub relacionados y/o los nombres estilizados son marcas comerciales de GitHub. Aceptas no mostrar o usar estas marcas comerciales de ninguna manera sin el permiso previo por escrito de GitHub, excepto según lo permitido por los logotipos y la política de uso de GitHub: https://github.com/logos. - -### Privacidad - -El software puede recopilar información personal. Puedes controlar qué información recopila el software en el panel de configuraciones. Si el software recopila información personal en nombre de GitHub, GitHub procesará esa información de acuerdo con la [Declaración de privacidad de GitHub](/articles/github-privacy-statement/). - -### Servicios adicionales - -**Servicios de actualización automática** - -El Software puede incluir un servicio de actualización automática ("Servicio"). Si decides utilizar el servicio o descargas software que habilita automáticamente el servicio, GitHub actualizará automáticamente el software cuando haya una nueva versión disponible. - -**Renuncias y limitaciones de responsabilidad** - -EL SERVICIO SE PROPORCIONA "TAL CUAL" Y NO SE OTORGA NINGUNA GARANTÍA, YA SEA EXPLÍCITA O IMPLÍCITA. TU USO DEL SERVICIO ES A TU PROPIO RIESGO. GitHub no garantiza que (i) el servicio cumplirá con tus requisitos específicos; (II) el servicio es totalmente compatible con cualquier plataforma en particular; (III) tu uso del servicio se ininterrumpirá, oportunamente, de manera segura o libre de errores; (IV) los resultados que se pueden obtener del uso del servicio serán exactos o confiables; (v) la calidad de cualquier producto, servicio, información u otro material adquirido u obtenido por ti a través del servicio cumplirá con tus expectativas; o (VI) se corregirán cualquier error en el servicio. - -EXPRESAMENTE COMPRENDES Y ACEPTAS QUE GITHUB NO SERÁ RESPONSABLE DE NINGÚN DAÑO DIRECTO, INDIRECTO, INCIDENTAL, ESPECIAL, CONSECUENTE O EJEMPLARES, INCLUYENDO, ENTRE OTROS, LOS DAÑOS POR PÉRDIDA DE BENEFICIOS, BUENA VOLUNTAD, USO, DATOS U OTRAS PÉRDIDAS INTANGIBLES (INCLUSO SI SE HA ADVERTIDO A GITHUB SOBRE LA POSIBILIDAD DE DICHOS DAÑOS) RELACIONADOS CON EL SERVICIO, incluyendo, por ejemplo: (i) el uso o la incapacidad de usar el servicio; (II) el costo de la adquisición de bienes y servicios sustitutivos resultantes de cualquier mercancía, dato, información o servicios adquiridos u obtenidos o mensajes recibidos o transacciones concertados a través o desde del servicio; (III) acceso no autorizado o alteración de tus transmisiones o datos; (IV) declaraciones o conductas de cualquier tercero en el servicio; (v) o cualquier otro asunto relacionado con el servicio. - -GitHub se reserva el derecho en cualquier momento y de vez en cuando de modificar o interrumpir, de manera temporal o permanente, el servicio (o cualquier parte del mismo) con o sin aviso. GitHub no será responsable ante ti ni ante ningún tercero por cualquier cambio de precio, suspensión o interrupción del servicio. - -### Varios - -1. Ninguna renuncia. La incapacidad de GitHub para ejercer o hacer cumplir cualquier derecho o disposición de estos términos de la aplicación no constituirá una renuncia a dicho derecho o disposición. - -2. Acuerdo completo. Estos términos de la aplicación, junto con cualquier aviso de privacidad aplicable, constituyen el acuerdo completo entre tú y GitHub y rigen tu uso del software, reemplazando cualquier acuerdo anterior entre tú y GitHub (incluyendo, entre otras, cualquier versión anterior de los términos de la aplicación). - -3. Legislación aplicable. Aceptas que estos términos de la aplicación y tu uso del software están regidos por la ley de California y cualquier disputa relacionada con el software debe ser llevada a un tribunal de jurisdicción competente ubicado en o cerca de San Francisco, California. - -4. Paquetes de terceros. El software admite "paquetes" de terceros que pueden modificar, agregar, eliminar o alterar la funcionalidad del software. Estos paquetes no están cubiertos por los presentes términos de la aplicación y pueden incluir su propia licencia que rige tu uso de ese paquete en particular. - -5. Sin modificaciones; contrato completo. Estos términos de la aplicación solo se pueden modificar mediante una enmienda por escrito firmada por un representante autorizado de GitHub, o mediante la publicación por parte de GitHub de una versión revisada. Estos términos de la aplicación, junto con cualquier licencia y aviso de código abierto aplicable y la declaración de privacidad de GitHub, representan la declaración completa y exclusiva del acuerdo entre tú y nosotros. Estos términos de la aplicación sustituyen cualquier propuesta o acuerdo previo oral o escrito y cualquier otra comunicación entre tú y GitHub relacionada con el tema de estos términos. - -6. Licencia a políticas de GitHub. Estos términos de aplicación están licenciados bajo esta [Licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). - -7. Contáctanos. ¿Preguntas sobre los Términos de Servicio? [Contáctanos](https://support.github.com/contact). diff --git a/translations/es-XL/content/github/site-policy/github-pre-release-program.md b/translations/es-XL/content/github/site-policy/github-pre-release-program.md deleted file mode 100644 index 6e7a1c4734..0000000000 --- a/translations/es-XL/content/github/site-policy/github-pre-release-program.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Programa de prelanzamiento de GitHub -redirect_from: - - /articles/github-pre-release-program -versions: - free-pro-team: '*' -topics: - - Policy - - Legal ---- - -¡Gracias por registrarte para participar en los programas de prelanzamiento de GitHub! Como miembro de confianza de nuestra comunidad, tu opinión sobre las características nuevas y experimentales es importante para nosotros. Con el fin de compartir con ustedes estos nuevos productos y servicios, muchos de los cuales siguen siendo secretos y en desarrollo, necesitaremos que acepten un conjunto especial de términos. Bienvenido al acuerdo del programa de prelanzamiento ("Acuerdo"). - -El presente acuerdo es un acuerdo legal entre tú ("tú", "tu") y GitHub, Inc. (“GitHub”, “nosotros”). Asegúrate de leer el presente acuerdo detenidamente - solo puedes ser un participante del programa de prelanzamiento si aceptas todos los términos del presente acuerdo. Al hacer clic en el botón "registrarse para el programa de prelanzamiento de GitHub", o al participar como participante del programa de pre-lanzamiento de cualquier manera - por ejemplo, al ingresar a información acerca de los productos o servicios de GitHub que aún no están disponibles para el público en general, estás aceptando regirte por todos los términos del presente acuerdo. SI ESTÁS INGRESANDO EN EL PRESENTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA ENTIDAD LEGAL, DECLARAS QUE TIENES LA AUTORIDAD LEGAL PARA VINCULAR A LA ENTIDAD CON EL PRESENTE ACUERDO, EN CUYO CASO "TÚ" SIGNIFICARÁ LA ENTIDAD QUE REPRESENTAS. SI NO TIENES ESA AUTORIDAD, O SI NO ESTÁS DE ACUERDO CON LOS TÉRMINOS Y CONDICIONES DEL PRESENTE ACUERDO, NO DEBES HACER CLIC EN EL BOTÓN "REGISTRARSE PARA EL PROGRAMA DE PRELANZAMIENTO DE GITHUB" Y NO PUEDES SER UN PARTICIPANTE DEL PROGRAMA DE PRELANZAMIENTO. SI ERES UNA EMPRESA U OTRA ENTIDAD LEGAL, REPRESENTAS QUE LA PERSONA QUE HACE CLIC EN EL BOTÓN "REGISTRARSE PARA EL PROGRAMA DE PRELANZAMIENTO DE GITHUB" TIENE LA AUTORIDAD PARA VINCULARTE CON EL PRESENTE ACUERDO. - -### 1. Se aplicarán los términos de uso de GitHub.com o el acuerdo de licencia de software de GitHub Enterprise - - Debes tener una cuenta en GitHub.com o en una instancia con licencia de GitHub Enterprise para ser un participante del programa de prelanzamiento. Además de los términos de servicio de GitHub.com o tu acuerdo de licencia de GitHub Enterprise aplicable, según corresponda, (los "términos generalmente aplicables"), al hacer clic en el botón "registrarse para el programa de prelanzamiento de GitHub", también aceptas regirte por el presente acuerdo, de manera que ambos acuerdos se apliquen a ti simultáneamente. En el caso de un conflicto directo entre este Acuerdo y los Términos Generalmente Aplicables, tus Términos Generalmente Aplicables controlarán, excepto con respecto a cualquier uso de materiales de preliberación, en cuyo caso el presente Contrato controlará. - -### 2. Confidencialidad; acceso a los materiales de prelanzamiento - - Como participante del programa de prelanzamiento, puedes tener acceso a información especial que no está disponible para el resto del mundo. Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. - - Aceptas que toda información no pública que te proporcionemos, o a la que puedas tener acceso como participante del programa de prelanzamiento, se considerará información confidencial de GitHub (en conjunto, "información confidencial"), independientemente de si está marcada o identificada como tal. Aceptas utilizar esa información confidencial únicamente para el propósito expreso de las pruebas y la evaluación de los materiales de prelanzamiento (el "propósito") y no para ningún otro propósito. Debes usar el mismo grado de cuidado que usarías con tu información confidencial, pero no menos de las precauciones razonables para evitar cualquier uso no autorizado, divulgación, publicación o diseminación de nuestra información confidencial. Prometes no revelar, publicar o diseminar ninguna información confidencial a ningún tercero que no sea tus empleados y contratistas y posteriormente solo en la medida en que: (i) necesiten conocer la información confidencial para el propósito; (II) les haces conocer la naturaleza confidencial de la información confidencial; (III) sigues siendo responsable de los actos y omisiones de dichos empleados y contratistas; y (IV) no prohibimos o restringimos dicha divulgación. - - Comprendes que la divulgación o el uso no autorizados de nuestra información confidencial podrían causarnos un daño irreparable y una lesión significativa que podría ser difícil de cuantificar para nosotros. En consecuencia, aceptas que tendremos el derecho de buscar medidas cautelares inmediatas para asegurarnos de que cumplas con el presente acuerdo, además de cualesquier otro derecho y recurso que podamos tener. Si se te solicita por ley, regulación o una orden vinculante válida de un tribunal de jurisdicción competente para divulgar nuestra información confidencial, puedes hacerlo, pero solo si nos lo notificas antes de hacerlo y harás tu mejor esfuerzo para limitar dicha divulgación y buscar el tratamiento confidencial y protector de dicha información. - - Las obligaciones de la presente sección 2 no se aplicarán a la información que puedas probar que: (i) estuvo generalmente disponible para el público antes de que te la revelaramos; (II) estuvo generalmente disponible para el público después de que te la revelamos, sin acción o inacción por tu parte, o por parte de tus empleados o contratistas; (III) conocías antes de que te la revelaramos; (IV) te fue revelada por un tercero, que no tenía ninguna obligación de confidencialidad con respecto a la misma; (v) que desarrollaste de forma independiente sin violar ninguna obligación de confidencialidad con nosotros o cualquier tercero; o (VI) te dimos permiso para divulgar, en un escrito firmado por uno de nuestros representantes autorizados. Si te damos acceso a cualquier software, software de prelanzamiento o documentación o materiales relacionados, que pueden incluir videos u otras formas de contenido ("materiales de prelanzamiento"), entonces, sujeto a tu cumplimiento con los términos y condiciones del presente acuerdo y en los términos generalmente aplicables, por la presente te otorgamos un derecho y una licencia no exclusivos, intransferibles y revocable para usar los materiales de prelanzamiento durante la vigencia del presente acuerdo, exclusivamente para el propósito. Si los materiales de prelanzamiento están acompañados de un acuerdo de licencia separado, aceptas que se aplicarán el acuerdo de licencia por separado (además de cualquier disposición más restrictiva contenida en el presente acuerdo o tus términos de aplicación general). Aceptas no descompilar, hacer ingeniería inversa, desmontar o reducir de cualquier otra manera los materiales de prelanzamiento a una forma perceptible por el hombre y prometes no modificar, establecer redes, alquilar, arrendar, transmitir, vender o prestar los materiales de prelanzamiento, en su totalidad o en parte. Comprendes que no estamos obligados a proporcionarte ningún material de prelanzamiento, a proporcionarte actualizaciones, mejoras o correcciones en los materiales de prelanzamiento, o a notificarte de los cambios que realicemos a nuestros productos y servicios, ahora o en el futuro. - -### 3. Plazo y terminación - - El presente acuerdo comienza en la fecha en que haces clic en "acordar", y continúa durante un período de un (1) año. El presente acuerdo se renovará automáticamente por términos sucesivos de un año, a menos que cualquiera de las partes le dé un aviso por escrito al menos treinta (30) días antes del vencimiento del plazo actual que desea terminar, o una parte la terminará antes de acuerdo con lo dispuesto en la presente sección 3. - - Tanto tú como GitHub pueden rescindir el presente acuerdo por cualquier motivo, sin causa, después de treinta (30) días de aviso previo por escrito a la otra. El presente acuerdo terminará de inmediato, sin la obligación de aviso, si incumple cualquier término del presente acuerdo, los términos del programa o los TOS. - - Los derechos y obligaciones de las Secciones 1, 2 y 4 hasta 17 sobrevivirán a la rescisión o caducidad del presente Contrato. Tras la terminación o la expiración del presente acuerdo, todos los derechos y las licencias que te otorgaron en el presente acuerdo dejarán de existir de inmediato, regresarás (o, a petición nuestra, destruirás) toda nuestra información confidencial y cualquier copia (incluidas las copias electrónicas) que estén en tu posesión o control y certificaras por escrito que has cumplido con estos requisitos. - -### 4. Garantías y limitaciones de responsabilidades - - Nos garantizas que: (i) tienes la autoridad para ejecutar el presente acuerdo y para cumplir con sus obligaciones; (II) no harás declaraciones o representaciones falsas o engañosas con respecto a GitHub o a nuestros productos y servicios; y (III) no tomarás ninguna obligación o responsabilidad, ni hará ninguna representación, garantía o endoso a nadie en nuestro nombre (incluidos, entre otros, alguno de nuestros productos o servicios). - - COMPRENDES Y ACEPTAS QUE CUALQUIER MATERIAL O INFORMACIÓN QUE TE DEMOS O A LA QUE TENGAS ACCESO CONFORME A LO DISPUESTO EN EL PRESENTE ACUERDO (INCLUYENDO, ENTRE OTROS, CUALQUIER INFORMACIÓN CONFIDENCIAL O MATERIALES DE PRELANZAMIENTO) SE PROPORCIONAN "TAL CUAL", Y SIN GARANTÍA DE NINGÚN TIPO, EXPRESA O IMPLÍCITA. RENUNCIAMOS ESPECÍFICAMENTE A TODAS LAS GARANTÍAS O CONDICIONES IMPLÍCITAS DE COMERCIABILIDAD, IDONEIDAD PARA UN PROPÓSITO Y NO INFRACCIÓN PARTICULAR. - -### 5. Indemnización - - Te daremos acceso a muchos productos, servicios e información de prelanzamiento útiles, como los materiales de prelanzamiento y existen formas en las que puedes usarlos de manera inadecuada que podrían causarnos daño. Con eso en mente y dado que no podemos controlar las formas en las que usas lo que te proporcionamos, aceptas que nos indemnizarás, defenderás y eximirás de toda responsabilidad de cualquier reclamación que pueda surgir por debajo o fuera de tu participación en cualquier programa de prelanzamiento; tu negligencia o mala conducta intencional; cualquier tergiversación que realices con respecto a nosotros o a nuestros productos o servicios; o tu violación de cualquier parte del presente acuerdo. - -### 6. Limitación de responsabilidad - - EN NINGÚN CASO SEREMOS RESPONSABLES ANTE TI O ANTE NINGÚN TERCERO POR NINGÚN DAÑO INDIRECTO, ESPECIAL, INCIDENTAL, CONSECUENTE, EJEMPLAR O PUNITIVO, INCLUYENDO, ENTRE OTROS, LOS DAÑOS POR DATOS PERDIDOS, PÉRDIDAS DE BENEFICIOS O COSTOS DE ADQUISICIÓN DE BIENES O SERVICIOS SUSTITUTIVOS, SIN PERJUICIO DE LO QUE SE CAUSE Y BAJO CUALQUIER TEORÍA DE RESPONSABILIDAD, YA SEA POR CONTRATO, AGRAVIO (INCLUYENDO LA RESPONSABILIDAD DE PRODUCTOS , RESPONSABILIDAD ESTRICTA Y NEGLIGENCIA), O CUALQUIER OTRA TEORÍA, Y SI SABÍAMOS O NO O DEBERÍAMOS HABER SABIDO SOBRE LA POSIBILIDAD DE DICHOS DAÑOS. EN NINGÚN CASO NUESTRA RESPONSABILIDAD TOTAL ANTE TI DERIVADA DEL PRESENTE ACUERDO O RELACIONADA CON ÉL POR CUALQUIER CAUSA, E INDEPENDIENTEMENTE DE LA FORMA DE ACCIÓN, YA SEA POR CONTRATO O POR AGRAVIO, EXCEDE EL MAYOR DE (I) LOS MONTOS QUE REALMENTE PAGÓ CONFORME A LO DISPUESTO EN EL PRESENTE ACUERDO; O (II) 500 DÓLARES ($500). LAS LIMITACIONES ANTERIORES SE APLICARÁN A PESAR DEL FRACASO DEL PROPÓSITO ESENCIAL DE CUALQUIER SOLUCIÓN LIMITADA QUE SE INDIQUE EN EL PRESENTE ACUERDO. - -### 7. Control de exportación - - No se te permite exportar o volver a exportar ninguna información confidencial, excepto según lo autorizado por la ley de los Estados Unidos y las leyes de la jurisdicción en la que se obtuvo la información confidencial. In particular, you aren’t allowed to export or re-export our Confidential Information into any U.S. embargoed countries, to anyone on the U.S. Treasury Department's list of Specially Designated Nationals, or to anyone on the U.S. Department of Commerce Denied Person's List or Entity List. Al participar en un programa de prelanzamiento o recibir alguna de nuestra información confidencial, declaras y garantizas que no estás ubicado en ningún país de este tipo o en ninguna lista. - -### 8. Derechos de propiedad - - Aceptas que GitHub y sus licenciantes son propietarios de todos los derechos, títulos e interés en los materiales de prelanzamiento y todos los demás productos y servicios de GitHub; toda la información y los datos relativos a sus configuraciones y combinaciones; y todas las modificaciones y obras derivadas de cualquiera de las anteriores. Aceptas no eliminar, alterar, cubrir o ofuscar ningún derecho de autor u otros avisos de derechos de propiedad que colocamos o insertamos en los materiales de prelanzamiento o cualquier otro producto y servicio de GitHub. - -### 9. Usuarios gubernamentales - - Si eres una entidad gubernamental, esta sección aplica para ti. Cierta parte de nuestra información confidencial puede considerarse "artículos comerciales", ya que ese término se define en 48 C. § 2,101, que consiste en "software informático comercial" y "documentación del software informático comercial", ya que dichos términos se usan en 48 C. § 12,212 o 48 C. § 227.7202, según corresponda. Consistente con 48 C. § 12,212 o 48 C. § 227.7202-1 a 227.7202-4, según corresponda, la documentación del software informático comercial y del software informático comercial se licencia para los usuarios finales del gobierno de los EE. UU. (a) únicamente como elementos comerciales y (b) con solo aquellos derechos que se conceden a todos los demás usuarios finales conforme a los términos y condiciones del presente documento. GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107. - -### 10. Desarrollo independiente - - Ninguna parte del presente acuerdo perjudicará nuestro derecho a desarrollar, adquirir, licenciar, comercializar, promocionar o distribuir productos, software o tecnologías que puedan competir con tus productos. - -### 11. Privacidad - - Como parte del desarrollo y la evaluación de nuestros programas de evaluación, GitHub necesita recopilar información sobre cómo tu uso de los servicios y los programas y cómo GitHub puede mejorarlos. Al aceptar participar en los programas de prelanzamiento de GitHub, aceptas que has leído y has dado tu consentimiento a nuestra [Política de privacidad completa](/articles/github-privacy-statement/). - - Es posible que recopilemos cierta información personal adicional de los participantes en los programas de prelanzamiento. Por ejemplo, es posible que invites a los participantes a enviarnos comentarios (como se explica en la sección 12). Podríamos hacer preguntas acerca de las experiencias de cada usuario, la familiaridad con el producto o la información demográfica. Utilizamos esta información para mejorar nuestros productos y servicios y no las vendemos a terceros o anunciantes. Puedes declinar enviarnos tus comentarios, declinar la respuesta a preguntas específicas o contactarnos para eliminar o alterar la información que hemos recopilado sobre ti. - - GitHub's servers are located in the United States. Procesamos y controlamos tus datos en los Estados Unidos. Sin embargo, solo tú eres responsable de determinar qué datos personales nos envías. Consulta nuestra política de privacidad para obtener más información. - -### 12. Comentarios - - Siempre estamos tratando de mejorar los productos y servicios y tus comentarios como un participante del programa de pre-lanzamiento nos ayudarán a hacerlo. Si decides darnos cualquier idea, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario para nuestros productos o servicios (colectivamente, "Comentarios"), reconoces y aceptas que GitHub tendrá una licencia sin cargo de regalías completamente pagada, mundial, transferible, irrevocable para implementar, usar, modificar, explotar comercialmente y/o incorporar los Comentarios en nuestros productos, servicios y documentación. - -### 13. Contratistas independientes - - Las partes del presente acuerdo son contratistas independientes. Ninguna de las partes se considerará como un empleado, agente, socio, franquiciador, franquiciada o representante legal de la otra para ningún propósito y ninguna de las partes tendrá ningún derecho, poder o autoridad para crear ninguna obligación o responsabilidad en nombre de la otra. - -### 14. Assignment - - No puedes ceder o transferir el presente acuerdo o ninguno de tus derechos en virtud del mismo, en su totalidad o en parte, por el funcionamiento de la ley o de cualquier otra manera, sin nuestro consentimiento previo por escrito. - -### 15. Legislación aplicable y jurisdicción - - El presente acuerdo se interpretará y entenderá de acuerdo con las leyes del estado de California, sin tener en cuenta los principios de conflicto de leyes. Todas las disputas que surjan del presente Acuerdo estarán sujetas a la jurisdicción exclusiva del estado y los tribunales federales ubicados en el Condado de San Francisco, California y cada una de las partes consiente a la jurisdicción personal en dicho lugar. - -### 16. Modificaciones; renuncias; inexistencia de terceros beneficiarios - - Es posible que el presente acuerdo no se cambie, excepto mediante un escrito firmado por ambas partes. Cualquier renuncia a las disposiciones del presente acuerdo o de los derechos o recursos de una parte conforme a lo dispuesto en el presente acuerdo debe ser por escrito para que sea efectiva. Si se encuentra que algún término, condición o disposición del presente acuerdo no es válido o no ejecutable, los términos restantes seguirán siendo válidos y exigibles en la medida en que lo permita la ley. Cada uno de nosotros acepta expresamente que no hay terceros beneficiarios del presente acuerdo. - -### 17. Entire Agreement - - El presente acuerdo y los términos generalmente aplicables contienen el acuerdo completo de las partes con respecto al tema y sustituyen todas las comunicaciones, representaciones, entendimientos y acuerdos previos, ya sean escritos u orales. Los términos o condiciones de cualquiera de tus pedidos de compras, confirmacones u otros documentos que nos envíes en relación con el presente acuerdo serán nulos y sin efecto. diff --git a/translations/es-XL/content/github/site-policy/github-privacy-statement.md b/translations/es-XL/content/github/site-policy/github-privacy-statement.md deleted file mode 100644 index abf7a39a72..0000000000 --- a/translations/es-XL/content/github/site-policy/github-privacy-statement.md +++ /dev/null @@ -1,324 +0,0 @@ ---- -title: Declaración de Privacidad de GitHub -redirect_from: - - /privacy/ - - /privacy-policy/ - - /privacy-statement/ - - /github-privacy-policy/ - - /articles/github-privacy-policy/ - - /articles/github-privacy-statement/ -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Fecha de entrada en vigor: 22 de julio del 2020 - -Gracias por confiar a GitHub Inc. (“GitHub”, “nosotros”) tu código fuente, tus proyectos y tu información personal. Conservar tu información privada es una responsabilidad importante, y queremos que sepas cómo lo hacemos. - -Todos los términos en mayúsculas tienen su definición en las [Condiciones de Servicio de GitHub](/github/site-policy/github-terms-of-service) a menos de que se indique lo contrario. - - -### La versión corta - -Utilizamos tu información personal como lo describe la presente Declaración de Privacidad. Sin importar quién seas, dónde vives, o cuál sea tu nacionalidad, proporcionames el mismo estándar alto de protección de la privacidad a todos nuestros usuarios en el mundo, sin importar su país de orígen o su ubicación. - -Por supuesto, la versión corta y el Resumen que aparecen a continuación no informan todos los detalles, por lo tanto, sigue leyendo para acceder a ellos. - -### Resumen - -| Sección | ¿Qué puedes encontrar allí? | -| ---------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [Qué información recopila GitHub](#what-information-github-collects) | GitHub recopila información directamente a partir de tu registro, tus pagos, tus transacciones y del perfil del usuario. Asimismo, cuando resulta necesario, recopilamos datos automáticamente a partir de tu información de uso, cookies y tecnologías similares, y de la información del dispositivo, sujeto a tu consentimiento. Puede que GitHub también recopile Información personal del usuario a partir de terceros. Solo recopilamos la mínima cantidad de información personal necesaria a través de ti, a menos que decidas proporcionar más. | -| [Qué información GitHub _no_ recopila](#what-information-github-does-not-collect) | No recopilamos intencionalmente información de niños menores de 13 años y no recopilamos [Información personal sensible](https://gdpr-info.eu/art-9-gdpr/). | -| [Cómo utiliza GitHub tu información](#how-github-uses-your-information) | En esta sección, describimos las formas en las que utilizamos tu información, incluyendo el proporcionarte el Servicio, comunicarnos contigo, para propósitos de seguridad y cumplimiento, y para mejorar nuestro Servicio. También describimos la base legal sobre la cual procesamos tu información personal, cuando se exige legalmente. | -| [Cómo compartimos la información que recopilamos](#how-we-share-the-information-we-collect) | Puede que compartamos tu información con terceros en una de las siguientes circunstancias: con tu consentimiento, con nuestros proveedores de servicio, por motivos de seguridad, para cumplir con nuestras obligaciones legales o cuando exista un cambio de control o venta de las entidades corporativas o unidades de negocios. En GitHub, no vendemos tu información personal y no alojamos publicidad. Puedes consultar una lista de los proveedores de servicio que acceden a tu información. | -| [Otra información importante](#other-important-information) | Proporcionamos más información específica sobre los contenidos del repositorio, la información pública y las Organizaciones de GitHub. | -| [Servicios adicionales](#additional-services) | Proporcionamos información sobre las ofertas de servicio adicionales, incluso aplicaciones de terceros, Páginas de GitHub y aplicaciones de GitHub. | -| [Cómo puedes acceder y controlar la información que recopilamos](#how-you-can-access-and-control-the-information-we-collect) | Proporcionamos formas para que accedas, modifiques o elimines tu información personal. | -| [Uso de cookies y seguimiento](#our-use-of-cookies-and-tracking) | Utilizamos cookies para la funcionalidad general de nuestro Sitio web y una pequeña cantidad de servicios de análisis y de seguimiento en pocas partes de nuestro sitio. Ofrecemos una página que hace que esto sea muy transparente. Consulta esta sección para obtener más información. | -| [Cómo asegura GitHub tu información](#how-github-secures-your-information) | Tomamos todas las medidas razonablemente necesarias para proteger la confidencialidad, integridad y disponibilidad de tu información personal en GitHub y para proteger la resistencia de nuestros servidores. | -| [Prácticas de privacidad mundiales de GitHub](#githubs-global-privacy-practices) | Proporcionamos el mismo estándar alto de protección de la privacidad a todos nuestros usuarios en el mundo entero. | -| [Cómo nos comunicamos contigo](#how-we-communicate-with-you) | Nos comunicamos contigo por correo electrónico. Puedes controlar la manera en que te contactamos en las configuraciones de la cuenta o poniéndote en contacto con nosotros. | -| [Resolver reclamos](#resolving-complaints) | En el caso improbable de que no podamos resolver una inquietud sobre la privacidad de forma rápida y exhaustiva, proporcionaremos un medio de resolución por medio de una disputa. | -| [Cambios en tu Declaración de privacidad](#changes-to-our-privacy-statement) | Te notificamos los cambios importantes en esta Declaración de privacidad 30 días antes de que cualquier cambio entre en vigencia. Puedes rastrear los cambios en nuestro repositorio de Políticas del sitio. | -| [Licencia](#license) | La presente Declaración de privacidad está autorizada por la [licencia Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). | -| [Contactarse con GitHub](#contacting-github) | Siéntete libre de contactarnos si tienes preguntas acerca de nuestra Declaración de privacidad. | -| [Traducciones](#translations) | Proporcionamos enlaces a algunas traducciones de la Declaración de privacidad. | - -## Declaración de Privacidad de GitHub - -### Qué información recopila GitHub - -La "**Información personal del usuario**" es cualquier información acerca de alguno de nuestros Usuarios que podría, de manera independiente o junto con otra información, identificarlo individualmente, o que está vinculada o conectada de cualquier otra forma con él. Información como un nombre de usuario y contraseña, una dirección de correo electrónico, un nombre real, una dirección de Protocolo de Internet (IP) y una fotografía son ejemplos de "Información personal del usuario". - -La Información personal del usuario no incluye información agregada, información de carácter no personal que no identifica a un Usuario o que no se puede vincular o conectar de manera razonable con él. Podemos utilizar dicha información agregada que no identifica de manera personal a un usuario con motivos de investigación y para operar, analizar y optimizar nuestro Sitio web y el Servicio. - -#### Información que los usuarios proporcionan directamente a GitHub - -##### Información de registro -Necesitamos cierta información básica al momento de creación de la cuenta. Cuando creas tu propio nombre de usuario y contraseña, te solicitamos una dirección de correo electrónico válida. - -##### Información de Pago -Si te registras para una Cuenta paga, envías fondos a través del Programa de patrocinadores de GitHub o compras una aplicación en el Mercado GitHub, recopilamos tu nombre completo y la información de la tarjeta de crédito o la información de PayPal. Ten en cuenta que GitHub no procesa ni almacena tu información de tarjeta de crédito o información de PayPal, pero sí lo hace nuestro procesador de pago subcontratado. - -Si detallas y vendes una aplicación en el [Mercado GitHub](https://github.com/marketplace), te solicitamos la información de tu banco. Si recabas fondos a través del [Programa de Patrocinadores de GitHub](https://github.com/sponsors), necesitamos algo de [información adicional](/github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer#submitting-your-bank-information) mediante el proceso de registro para que participes y recibas los fondos a través de estos servicios y para propósitos de cumplimiento. - -##### Información de perfil -Puedes decidir proporcionarnos más información para tu Perfil de cuenta, como tu nombre completo, un avatar que puede incluir una fotografía, tu biografía, tu ubicación, tu empresa y una URL a un sitio web de terceros. Esta información puede incluir Información personal del usuario. Ten en cuenta que tu información de perfil puede ser visible para otros Usuarios de nuestro Servicio. - -#### Información que GitHub recopila automáticamente a partir del uso del Servicio - -##### Información transaccional -Si tienes una Cuenta paga con nosotros, vendes una aplicación detallada en el [Mercado GitHub](https://github.com/marketplace) o recaudas fondos a través del [Programa de patrocinadores de GitHub](https://github.com/sponsors), automáticamente recopilamos determinada información acerca de tus transacciones en el Servicio, como la fecha, la hora y el monto cobrado. - -##### Información de uso -Si accedes a nuestro Servicio o Sitio web, automáticamente recopilamos la misma información básica que recopila la mayoría de los servicios, sujeto a tu consentimiento cuando resulte necesario. Esto incluye información acerca de cómo utilizas el Servicio, por ejemplo, las páginas que miras, el sitio referido, tu dirección IP e información de sesión, y la fecha y hora de cada solicitud. Recopilamos esta información de todos los visitantes del Sitio web, tengan o no una Cuenta. Esta información puede incluir Información personal del usuario. - -##### Cookies e información de tecnologías similares -Como se describe con más detalle a continuación, y sujeto a tu consentimiento, cuando resulta necesario, recopilamos automáticamente información de cookies y tecnologías similares (como ID y configuraciones de la cookie) a fin de mantenerte registrado, recordarte tus preferencias e identificarte a ti y a tu dispositivo. - -##### Información de dispositivo -Puede que recopilemos determinada información acerca de tu dispositivo, como la dirección IP, el navegador o información de la aplicación del cliente, preferencias de idioma, sistema operativo y versión de la aplicación, tipo e ID del dispositivo y modelo y fabricante del dispositivo. Esta información puede incluir Información personal del usuario. - -#### Información que recopilamos de terceros - -GitHub puede recopilar Información personal del usuario a partir de terceros. Por ejemplo, esto puede ocurrir si inicias sesión para capacitarte o recibir información acerca de GitHub de parte de alguno de nuestros proveedores, socios o subsidiarias. GitHub no compra Información personal del usuario a agentes de datos de terceros. - -### Qué información no recopila GitHub - -No recopilamos de manera intencional “**[Información personal sensible](https://gdpr-info.eu/art-9-gdpr/)**”, como datos personales que revelan origen racial o étnico, opiniones políticas, creencias religiosas o filosóficas o afiliación sindical, y tampoco procesamos datos genéticos ni datos biométricos con el único fin de identificar a una persona física, datos del estado de salud o datos sobre la vida sexual o la orientación sexual de una persona física. Si decides almacenar alguna Información personal en tus servidores, eres responsable de cumplir con cualquier control regulatorio al respecto de esos datos. - -Si eres un niño menor de 13 años, no puedes tener una Cuenta en GitHub. GitHub no recopila intencionalmente información de niños menores de 13 años ni dirige ninguno de nuestros contenidos de manera específica a ellos. Si sabemos o tenemos motivos para sospechar que eres un Usuario menor de 13 años, tendremos que cerrar tu Cuenta. No queremos desalentarte de que aprendas nuestro código, pero esas son las reglas. Por favor, consulta nuestras [Condiciones de Servicio](/github/site-policy/github-terms-of-service) para la información acerca de la cancelación de la cuenta. Puede que los diferentes países tengan diferentes límites de edad mínimos. Si estás por debajo de la edad mínima para brindar consentimiento para la recopilación de datos en tu país, no puedes tener una Cuenta en GitHub. - -No recopilamos de manera intencional la Información personal del usuario que está **almacenada en tus repositorios** u otros ingresos de contenido de forma libre. Toda información personal dentro del repositorio de un usuario es responsabilidad del propietario del repositorio. - -### Cómo utiliza GitHub tu información - -- Podemos utilizar tu información con los siguientes fines: -- Utilizamos tu [Información de registro](#registration-information) para crear tu cuenta y para proporcionarte el Servicio. -- Utilizamos tu [Información de pago](#payment-information) para proporcionarte el servicio de Cuenta paga, el servicio de Mercado, el Programa de patrocinadores o cualquier otro servicio pago de GitHub que solicites. -- Utilizamos tu Información personal del usuario, específicamente tu nombre de usuario, para identificarte en GitHub. -- Utilizamos tu [Información del perfil](#profile-information) para completar tu perfil de Cuenta y para compartir ese perfil con otros usuarios, si nos pides que lo hagamos. -- Utilizamos tu dirección de correo electrónico para comunicarnos contigo, si estuviste de acuerdo con ello, **y solo por las razones con las que estuviste de acuerdo**. Consulta nuestra sección en [comunicación por correo electrónico](#how-we-communicate-with-you) para obtener más información. -- Utilizamos Información personal del usuario para responder a las solicitudes de soporte técnico. -- Utilizamos Información personal del usuario y otros datos para hacerte recomendaciones, por ejemplo, sugerir proyectos que puedes querer seguir o con los que puedes querer contribuir. Aprendemos de tu comportamiento público en GitHub, por ejemplo, los proyectos a los que les pones estrellas, para determinar tus intereses de codificación y recomendamos proyectos similares. Estas recomendaciones son decisiones automáticas, pero no tienen un impacto legal en tus derechos. -- Podemos utilizar Información personal del usuario para invitarte a formar parte de las encuestas, los programas beta u otros proyectos de investigación, sujeto a tu consentimiento cuando resulte necesario. -- Utilizamos [Información de uso](#usage-information) e [Información del dispositivo](#device-information) para comprender mejor cómo utilizan GitHub nuestros Usuarios y para mejorar nuestro Sitio web y el Servicio. -- Si es necesario, podemos utilizar tu Información personal del usuario por motivos de seguridad o para investigar posibles fraudes o intentos de dañar a GitHub o a nuestros Usuarios. -- Podríamos utilizar tu Información personal de usuario para cumplir con nuestras obligaciones legales, proteger nuestra propiedad intelectual y hacer cumplir nuestras [Condiciones de Servicio](/github/site-policy/github-terms-of-service). -- Restringimos nuestro uso de tu Información personal del Usuario para los fines detallados en esta Declaración de privacidad. Si necesitamos utilizar tu Información personal del usuario para otros fines, te pediremos permiso primero. Siempre puedes ver qué información tenemos, cómo la estamos utilizando y qué permisos nos has dado en tu [perfil de usuario](https://github.com/settings/admin). - -#### Nuestras bases legales para el procesamiento de información - -En la medida que el procesamiento de tu Información personal del usuario esté sujeto a determinadas normas internacionales (incluido, entre otros, el Reglamento General de Protección de Datos [RGPD]) de la Unión Europea, se le exige a GitHub que te notifique acerca de la base legal sobre la cual procesamos la Información personal del usuario. GitHub procesa la Información personal del usuario sobre las siguientes bases legales: - -- Ejecución del contrato: - * Cuando creas una Cuenta de GitHub, proporcionas tu [Información de registro](#registration-information). Solicitamos esta información para que celebres el acuerdo de Términos del Servicio con nosotros y procesamos esa información sobre la base de la ejecución de ese contrato. También procesamos tu nombre de usuario y dirección de correo electrónico sobre otras bases legales, como se describe a continuación. - * Si tienes una Cuenta paga con nosotros, recopilamos y procesamos más [Información de pago](#payment-information) sobre la base de la ejecución de ese contrato. - * Cuando compras o vendes una aplicación listada en nuestro Marketplace o, cuando envías o recibes fondos a través del Programa GitHub Sponsors, procesamos la [Información de pago](#payment-information) y elementos adicionales para realizar el contrato que se aplica a esos servicios. -- Consentimiento: - * Dependemos de tu consentimiento para utilizar tu Información personal del usuario en las siguientes circunstancias: cuando completas la información en tu [perfil de usuario](https://github.com/settings/admin); cuando decides participar en una capacitación de GitHub, proyecto de investigación, programa beta o encuesta; y con fines de marketing cuando corresponda. Toda esta Información personal del Usuario es completamente opcional, y tienes la capacidad de acceder a ella, modificarla y eliminarla en cualquier momento. Aunque no puedes eliminar tu dirección de correo electrónico por completo, puedes volverlo privado. Puedes retirar tu consentimiento en cualquier momento. -- Intereses legítimos: - * En general, el recordatorio del procesamiento de Información personal del usuario que hacemos es necesario con fines de nuestro legítimo interés, por ejemplo, con fines de cumplimiento legal, fines de seguridad o para mantener la permanente confidencialidad, integridad, disponibilidad y resistencia de los sistemas, el sitio web y el Servicio de GitHub. -- Si quieres solicitar la eliminación de datos que procesamos sobre la base del consentimiento u objetar el procesamiento de la información personal que hacemos, utiliza nuestro [Formulario de contacto sobre Privacidad](https://support.github.com/contact/privacy). - -### Cómo compartimos la información que recopilamos - -Podemos compartir tu Información personal del usuario con terceros en alguna de las siguientes circunstancias: - -#### Con tu consentimiento -Compartimos tu Información Personal del Usuario, si lo consientes, después de dejarte saber qué información será compartida, con quién y por qué. Por ejemplo, si compras una aplicación detallada en nuestro Mercado, compartimos tu nombre de usuario para permitirle al Programador de la aplicación que te proporcione los servicios. Asimismo, te puedes dirigir a nosotros a través de tus acciones en GitHub para compartir tu Información personal del usuario. Por ejemplo, si te unes a una Organización, indicas tu intención de proporcionarle al usuario de la Organización la capacidad de ver tu actividad en el registro de acceso de la Organización. - -#### Con proveedores de servicios -Compartimos información personal del usuario con un número limitado de proveedores de servicios que la procesan en nuestro nombre para proporcionar o mejorar nuestro servicio, y quienes han aceptado restricciones de privacidad similares a las de nuestra Declaración de Privacidad firmando acuerdos de protección de datos o haciendo compromisos similares. Nuestros proveedores de servicio realizan el procesamiento de pagos, la emisión de tickets de soporte técnico del cliente, la transmisión de datos de red, la seguridad y otros servicios similares. Mientras GitHub procesa toda la Información Personal del Usuario en los Estados Unidos, nuestros proveedores de servicios pueden procesar datos fuera de los Estados Unidos o de la Unión Europea. Si te gustaría saber quiénes son nuestros proveedores de servicios, por favor consulta nuestra página sobre nuestros [Subprocesadores](/github/site-policy/github-subprocessors-and-cookies). - -#### Con fines de seguridad -Si eres un miembro de una organización, GitHub puede compartir tu nombre de usuario, [Información de Uso](#usage-information), e [Información de Dispositivo](#device-information) asociadas con dicha organización con un propietario y/o administrador de la misma al punto en que tal información se proporcione únicamente para investigar o responder a un incidente de seguridad que afecte o ponga en riesgo la seguridad de esta organización en particular. - -#### Para divulgación legal -GitHub se esfuerza por conseguir transparencia en el cumplimiento de los procesos legales y las obligaciones legales. A menos que no lo permita la ley o una orden judicial, o en circunstancias únicas y apremiantes, hacemos un esfuerzo razonable para notificarles a los usuarios cualquier divulgación obligatoria o exigida de su información personal. Si así se requiere, GitHub puede divulgar Información personal del usuario u otra información que recopilamos acerca de ti para cumplir con la ley y responder una citación válida, orden judicial, orden de allanamiento u orden gubernamental similar, o cuando consideremos de buena fe que la divulgación es necesaria para cumplir con nuestras obligaciones legales, para proteger nuestra propiedad o nuestros derechos, los de terceros o los del público en general. - -Para obtener más información acerca de la divulgación en respuesta a solicitudes legales, consulta nuestros [Lineamientos para las Solicitudes Legales de Datos de Usuario](/github/site-policy/guidelines-for-legal-requests-of-user-data). - -#### Cambios por control o venta -Podemos compartir Información Personal del Usuario si estamos involucrados en una fusión, venta o adquisición de entidades corporativas o unidades de negocio. Si ocurre cualquier cambio de propiedad, nos aseguraremos de que sea conforme a los términos que preservan la confidencialidad de la Información personal del usuario y, antes de hacer cualquier transferencia de tu Información personal del usuario, lo notificaremos en nuestro Sitio web o por correo electrónico. La organización que reciba alguna Información personal del usuario tendrá que respetar cualquier compromiso que hayamos asumido en nuestra Declaración de privacidad o Términos del Servicio. - -#### Información agregada y sin indentificación personal -Compartimos cierta información agregada y no identificativa personal con otros acerca de cómo nuestros usuarios, de forma colectiva, utilice GitHub, o cómo nuestros usuarios responden a nuestras otras ofertas, tales como nuestras conferencias o eventos. Por ejemplo, [podemos compilar estadísticas sobre la actividad de código abierto en GitHub](https://octoverse.github.com/). - -**No** vendemos tu Información personal del usuario con fines monetarios o en función de consideraciones de otro tipo. - -Tenga en cuenta: La Ley de Privacidad del Consumidor de California de 2018 (“CCPA”) les exige a las empresas que expliciten en su política de seguridad si divulgan o no información personal a cambio de retribuciones monetarias u otras consideraciones de valor. While CCPA only covers California residents, we voluntarily extend its core rights for people to control their data to _all_ of our users, not just those who live in California. Puedes conocer más acerca de la CCPA y de cómo cumplimos con sus disposiciones [aquí](/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act). - -### Otra información importante - -#### Contenidos del repositorio - -El personal de GitHub [no accede a los repositorios privados a menos de que lo requiera](/github/site-policy/github-terms-of-service#e-private-repositories) por motivos de seguridad, para asistir al propietario del repositorio con un asunto de soporte, para mantener la integridad del Servicio o para cumplir con nuestras obligaciones legales. Sin embargo, si bien no buscamos contenido en tus repositorios generalmente, podríamos escanear nuestros servidores y su contenido para detectar ciertos tokens o firmas de seguridad, malware activo conocido, u otro tipo de contenido que sepamos que viola nuestras condiciones, tales como contenido violento extremista o terrorista o imágenes de explotación infantil con base en las técnicas algorítmicas de huellas digitales. Nuestras Condiciones de Servicio te proporcionan [más detalles](/github/site-policy/github-terms-of-service#e-private-repositories). - -Si tu repositorio es público, cualquier persona puede ver los contenidos. Si incluyes [Información personal sensible](https://gdpr-info.eu/art-9-gdpr/) en tu repositorio público, como direcciones de correo electrónico o contraseñas, esa información se puede indexar por medio de motores de búsqueda o puede ser utilizada por terceros. - -Por favor, consulta más sobre la [Información Personal del Usuario en los repositorios públicos](/github/site-policy/github-privacy-statement#public-information-on-github). - -#### Información pública en GitHub - -Muchos de los servicios y características de GitHub están orientados al público. Si tu contenido es público, los terceros pueden acceder y utilizarlo de acuerdo con nuestros Términos de servicio, como ver tu perfil o los repositorios o extraer datos por medio de nuestra API. Nosotros no vendemos ese contenido; es tuyo. Sin embargo, permitimos que terceros, como organizaciones de investigación o archivos, compilen información de GitHub orientada al público. Se ha sabido que otros terceros, como corredores de datos, también han extraído y compilado información de GitHub. - -Tu Información personal del usuario, asociada con tu contenido, puede ser recopilada por terceros en estas compilaciones de datos de GitHub. Si no quieres que tu información personal de usuario aparezca en las compilaciones de los datos de GitHub de terceros, por favor no hagas tu Información Personal de Usuario disponible públicamente y asegúrate de [configurar tu dirección de correo electrónico en tu perfil de usuario para que sea privada](https://github.com/settings/emails), así como en tu [configuración de confirmaciones de git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Actualmente configuramos la dirección de correo electrónico de los usuarios como privada por defecto, pero es posible que los usuarios de GitHub heredados necesiten actualizar sus configuraciones. - -Si quieres compilar datos de GitHub, debes cumplir con nuestras condiciones de servicio con respecto al [scraping](/github/site-policy/github-acceptable-use-policies#5-scraping-and-api-usage-restrictions) y a la [privacidad](/github/site-policy/github-acceptable-use-policies#6-privacy), y podrías utilizar únicamente cualquier Información Personal de Usuario de cara al público que obtengas con el propósito para el cual lo autorizó nuestro usuario. Por ejemplo, donde un usuario de GitHub haya puesto una dirección de correo electrónico de cara al público para propósitos de identificación y atribución, no la utilices para publicidad comercial. Esperamos que protejas de manera razonable cualquier Información Personal de Usuario que hayas reunido de GitHub y respondas de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" que haga GitHub u otros usuarios de GitHub. - -Del mismo modo, los proyectos en GitHub pueden incluir Información Personal de Usuario disponible públicamente como parte del proceso de colaboración. Si tienes alguna queja sobre cualquier tipo de Información Personal de Usuario en GitHub, por favor, consulta nuestra sección de [resolución de quejas](/github/site-policy/github-privacy-statement#resolving-complaints). - - -#### Organizaciones - -Puedes indicar, a través de tus acciones en GitHub, que estás dispuesto a compartir tu Información Personal de Usuario. Si colaboras o te conviertes en miembro de una Organización, los propietarios de su cuenta podrán recibir tu Información personal del usuario. Cuando aceptas una invitación a una Organización, se te notificará de los tipos de información que los propietarios pueden ver (para obtener más información, consulta la sección [Acerca de la Membrecía de Organización](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Si aceptas una invitación a una organización con un [dominio verificado](/github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain), entonces los propietarios de dicha organización podrán ver tu(s) dirección(es) de correo electrónico completa(s) dentro de l(los) dominio(s) verificado(s) de la organización. - -Por favor, nota que GitHub podría compartir tu nombre de usuario, [información de uso](#usage-information). e [Información de Dispositivo](#device-information) con el(los) propietario(s) de la organización a la cual perteneces, en medida en que tu Información Personal de Usuario se proporcione únicamente para investigar o responder a incidentes de seguridad que afecten o pongan en riesgo la seguridad de esta organización en particular. - -Si colaboras con, o te conviertes en miembro de una cuenta que ha aceptado las [Condiciones de Servicio Corporativas](/github/site-policy/github-corporate-terms-of-service) y con una Adenda de Protección de Datos (DPA) para esta Declaración de Privacidad, entonces, dicha DPA regirá sobre los otros instrumentos en caso de que haya un conflicto con esta Declaración de Privacidad y con la DPA con respecto a tu actividad en la cuenta. - -Contacta a los propietarios de la cuenta para obtener más información sobre la manera en que procesan tu Información personal del usuario y los modos de acceder, actualizar, modificar o borrar la Información personal del usuario almacenada en esa cuenta. - -### Servicios adicionales - -#### Aplicaciones de terceros - -Tienes la opción de habilitar o agregar aplicaciones de terceros, conocidas como "Productos de programador", a tu cuenta. Estos Productos de Desarrollador no son necesarios para usar GitHub. Compartirás tu Información personal del usuario a terceros cuando nos lo solicites, como al comprar un Producto de programador de Marketplace; sin embargo, eres responsable del uso del Producto de programador de un tercero y por la cantidad de Información personal del usuario que eliges compartir con este. Puede revisar nuestra [documentación de API](/v3/users/) para ver qué información se proporciona cuando te autenticas en un Producto de Desarrollador usando tu perfil de GitHub. - -#### Páginas de GitHub - -Si creas un sitio web de Páginas de GitHub, es tu responsabilidad publicar una declaración de privacidad que describa con precisión cómo recolectar, usar y compartir información personal y otra información de visitantes, y cómo cumples con las leyes, normas y reglamentos de privacidad de datos vigentes. Ten en cuenta que GitHub puede recopilar Información personal del usuario de los visitantes a tu sitio web de Páginas de GitHub incluyendo registros de las direcciones IP del visitante, para mantener la seguridad e integridad del sitio web y del servicio. - -#### Aplicaciones de GitHub - -También puedes agregar aplicaciones desde GitHub, tales como nuestra aplicación de Escritorio, nuestra aplicación de Atom, u otras aplicaciones y características de las cuentas, a tu propia cuenta. Estas aplicaciones tienen sus propios términos y pueden recopilar diferentes tipos de Información personal del usuario; sin embargo, todas las aplicaciones de GitHub están sujetas a esta Declaración de Privacidad, y siempre recogeremos la cantidad mínima de Información personal del usuario necesaria y la usaremos únicamente para el propósito por el que nos la diste. - -### Cómo puedes acceder y controlar la información que recopilamos - -Si ya eres un usuario de GitHub, puedes acceder, actualizar, modificar o eliminar la información básica de tu perfil de usuario [editando tu perfil de usuario](https://github.com/settings/profile) o poniéndote en contacto con [el Soporte de GitHub](https://support.github.com/contact) o [el Soporte Premium de GitHub](https://enterprise.githubsupport.com/hc/en-us). Puedes controlar la información que recopilamos acerca de ti limitando la información que contiene tu perfil, manteniendo tu información actual, o poniéndote en contacto con [GitHub Support](https://support.github.com/contact) o [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). - -Si GitHub procesa información sobre ti, como la información que [GitHub recibe de terceros](#information-we-collect-from-third-parties), y no tienes una cuenta, entonces puedes, sujeto a la ley vigente, acceder, actualizar, modificar, eliminar u objetar el procesamiento de tu información personal poniéndote en contacto con [GitHub Support](https://support.github.com/contact) o [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). - -#### Portabilidad de datos - -Como usuario de GitHub, siempre puedes llevar tus datos contigo. Puedes [clonar tus repositorios en tu escritorio](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop), por ejemplo, o puedes utilizar nuestras [herramientas de portabilidad de datos](https://developer.github.com/changes/2018-05-24-user-migration-api/) para descargar la información que tenemos sobre ti. - -#### Retención de datos y eliminación de datos - -Generalmente, GitHub conserva la Información personal del usuario mientras tu cuenta esté activa o cuando sea necesaria para brindarte servicios. - -If you would like to cancel your account or delete your User Personal Information, you may do so in your [user profile](https://github.com/settings/admin). Conservamos y utilizamos tu información según se necesita para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir nuestros acuerdos, pero salvo requisitos legales, eliminaremos tu perfil completo (dentro de lo razonable) dentro de los 90 días siguientes a tu solicitud. Puedes ponerte en contacto con [GitHub Support](https://support.github.com/contact) o [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us) para solicitar la eliminación de los datos que procesamos sobre la base del consentimiento en un plazo de 30 días. - -Después de que una cuenta se ha eliminado, ciertos datos, tales como contribuciones a los repositorios de otros usuarios y comentarios en asuntos ajenos, permanecerán. Sin embargo, eliminaremos o desidentificaremos tu Información personal del usuario, incluyendo tu nombre de usuario y dirección de correo electrónico del campo de autor de propuestas, solicitudes de extracción y comentarios al asociarlos con un [usuario fantasma](https://github.com/ghost). - -Una vez dicho esto, la dirección de correo electrónico que suministraste [a través de tu configuración de confirmaciones de Git](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address) siembre se asociará con tus confirmaciones en el sistema de Git. Si eliges hacer tu dirección de correo electrónico privada, también deberías actualizar la configuración de tu confirmación de cambios de Git. No podemos cambiar o eliminar datos en el historial de confirmación de Git (el software de Git está diseñado para mantener un registro) pero te permitimos controlar qué información pones en ese registro. - -### Uso de cookies y seguimiento - -#### Cookies - -GitHub utiliza cookies para hacer que las interacciones con nuestro servicio sean fáciles y significativas. Las cookies son pequeños archivos de texto que los sitios web almacenan a menudo en discos duros o dispositivos móviles de los visitantes. Utilizamos cookies (y tecnologías similares, como HTML5 localStorage) para mantenerte conectado, recordar tus preferencias y proporcionar información para el desarrollo futuro de GitHub. Por razones de seguridad, utilizamos cookies para identificar un dispositivo. Al utilizar nuestro Sitio Web, aceptas que podamos colocar este tipo de cookies en tu ordenador o dispositivo. Si desactivas tu navegador o la capacidad de tu dispositivo para aceptar estas cookies, no podrás iniciar sesión ni utilizar los servicios de GitHub. - -Proporcionamos una página web sobre [cookies y rastreo](/github/site-policy/github-subprocessors-and-cookies) que describe las cookies que implementamos, las necesidades que tenemos para utilizarlas y los tipos de cookies que manejamos (temporales y permanentes). También enumera a nuestros proveedores analíticos externos y a otros proveedores de servicios y detalla exactamente qué partes de nuestro Sitio Web les permitimos rastrear. - -#### Seguimiento y análisis - -Utilizamos una serie de proveedores analíticos y proveedores de servicios externos para ayudarnos a evaluar el uso de GitHub por parte de nuestros usuarios, compilar informes estadísticos sobre actividad y mejorar nuestro contenido y el rendimiento del sitio web. Solo utilizamos estos proveedores analíticos externos en ciertas áreas de nuestro sitio web, y todos ellos han firmado acuerdos de protección de datos con nosotros que limitan el tipo de Información personal del usuario que pueden recopilar y la finalidad para la que pueden procesar la información. Además, utilizamos nuestro propio software de análisis interno para proporcionar características y mejorar nuestro contenido y rendimiento. - -Algunos navegadores han incorporado características de "No rastrear" (DNT) que pueden enviar una señal a los sitios web que visitas, que indica que no deseas ser rastreado. GitHub responde a las señales DNT del navegador y sigue el estándar [W3C para responder a las señales DNT](https://www.w3.org/TR/tracking-dnt/). Si no has habilitado DNT en un navegador que lo admita, las cookies de algunas partes de nuestro sitio web rastrearán tu actividad de navegación en línea en otros servicios en el transcurso del tiempo, aunque no permitimos que terceros que no sean nuestros proveedores analíticos y de servicios hagan un seguimiento de la actividad de los usuarios de GitHub a lo largo del tiempo en GitHub. - -### Cómo asegura GitHub tu información - -GitHub toma todas las medidas razonablemente necesarias para proteger la Información personal del usuario contra accesos no autorizados, modificación o destrucción; mantener la exactitud de los datos y ayudar a asegurar el uso adecuado de la Información personal del usuario. - -GitHub aplica un programa escrito de información de seguridad. Nuestro programa: -- se alinea con los marcos reconocidos de la industria; -- incluye protecciones de seguridad diseñadas de manera razonable para proteger la confidencialidad, la integridad, la disponibilidad y la flexibilidad de los datos de usuarios; -- es adecuado para la naturaleza, el tamaño y la complejidad de las operaciones comerciales de GitHub; -- incluye procesos de respuesta frente a un incidente y notificación de filtración de datos; y -- cumple con las leyes y regulaciones vigentes relacionadas a la seguridad de la información en las regiones geográficas donde GitHub realiza operaciones. - -En caso de una filtración de datos que afecte tu Información personal del usuario, actuaremos rápidamente para mitigar el impacto de una infracción y notificar a los usuarios afectados sin demoras indebidas. - -La transmisión de datos en GitHub es cifrada usando SSH, HTTPS (TLS) y el contenido del repositorio de git es cifrado en reposo. Administramos nuestras propias jaulas y racks en centros de datos de alto nivel con un alto nivel de seguridad física y de red, y cuando los datos se almacenan con un proveedor de almacenamiento de terceros se cifran. - -Ningún método de transmisión, o método de almacenamiento electrónico, es 100 % seguro. Por lo tanto, no podemos garantizar su seguridad absoluta. Para obtener más información, consulta nuestras [divulgaciones de seguridad](https://github.com/security). - -### Prácticas de privacidad mundiales de GitHub - -GitHub, Inc. and, for those in the European Economic Area, the United Kingdom, and Switzerland, GitHub B. V. are the controllers responsible for the processing of your personal information in connection with the Service, except (a) with respect to personal information that was added to a repository by its contributors, in which case the owner of that repository is the controller and GitHub is the processor (or, if the owner acts as a processor, GitHub will be the subprocessor); or (b) when you and GitHub have entered into a separate agreement that covers data privacy (such as a Data Processing Agreement). - -Nuestras direcciones físicas son: - -- GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107. -- GitHub B.V., Vijzelstraat 68-72, 1017 HL Amsterdam, The Netherlands. - -Almacenamos y procesamos la información que recolectamos en los Estados Unidos de acuerdo con esta Declaración de Privacidad, aunque nuestros proveedores de servicios podrían almacenar y procesar los datos fuera de los Estados Unidos. Sin embargo, entendemos que tenemos usuarios de diferentes países y regiones con diferentes expectativas de privacidad e intentamos satisfacer esas necesidades incluso cuando los Estados Unidos no tienen el mismo marco de privacidad que otros países. - -Proporcionamos el mismo estándar alto de protección de privacidad—como se describe en la presente Declaración de Privacidad—a todos nuestros usuarios en todo el mundo, sin importar su país de origen o ubicación, y estamos orgullosos de los niveles de notificaciones, elección, responsabilidad, seguridad, integridad de datos, acceso y recursos que proporcionamos. Trabajamos duro para cumplir con las leyes vigentes sobre privacidad de datos dondequiera que hagamos negocios, al trabajar con nuestro Oficial de Protección de Datos como parte de un equipo multifuncional que supervisa nuestros esfuerzos de cumplimiento de la privacidad. Además, si nuestros proveedores o afiliados tienen acceso a la Información personal del usuario, deben firmar acuerdos que los obliguen a cumplir con nuestras políticas de privacidad y con las leyes vigentes sobre privacidad de datos. - -En particular: - - - GitHub proporciona métodos claros de consentimiento sin ambigüedad, informado, específico y libremente dado en el momento de la recopilación de datos, cuando recopilamos tu Información personal del usuario utilizando el consentimiento como base. - - Solo recopilamos la cantidad mínima de Información personal del usuario necesaria para nuestros propósitos, a menos que decidas proporcionar más. Te animamos a que sólo nos proporciones la cantidad de datos que consideres oportuno compartir. - - Te ofrecemos métodos sencillos de acceso, modificación o eliminación de la Información personal del usuario que hemos recopilado, en los casos legalmente permitidos. - - Proporcionamos a nuestros usuarios aviso, elección, responsabilidad, seguridad y acceso con respecto a su Información personal del usuario y limitamos el propósito por el cual procesarla. También proporcionamos a nuestros usuarios un método de recurso y cumplimiento. - -#### Transferencias de datos transfronterizas - -GitHub procesa información personal tanto dentro como fuera de los Estados Unidos y se basa en las Cláusulas Contractuales Estándar como un mecanismo legal para transferir datos legalmente desde el Área Económica Europea, el Reino Unido y Suiza hacia los Estados Unidos. Adicionalmente, GitHub se certifica en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A y Suiza-U. S. A. Para conocer más sobre las transferencias de datos interfronterizas, consulta nuestras [Prácticas de Privacidad Globales](/github/site-policy/global-privacy-practices). - -### Cómo nos comunicamos contigo - -Utilizamos tu dirección de correo electrónico para comunicarnos contigo, si estuviste de acuerdo con ello, **y solo por las razones con las que estuviste de acuerdo**. Por ejemplo, si contactas a nuestro equipo de Soporte con una solicitud, te responderemos por correo electrónico. Tienes mucho control sobre cómo se utiliza y comparte tu dirección de correo electrónico en y a través de GitHub. Puedes administrar tus preferencias de comunicación en tu perfil de usuario [](https://github.com/settings/emails). - -Por diseño, el sistema de control de versiones de Git asocia muchas acciones con la dirección de correo electrónico de un usuario, como mensajes de confirmación. No podemos cambiar muchos aspectos del sistema Git. Si deseas que tu dirección de correo electrónico siga siendo privada, incluso cuando estés comentando en los repositorios públicos, [puedes crear una dirección de correo electrónico privada en tu perfil de usuario](https://github.com/settings/emails). También deberías [actualizar tu configuración local de Git para utilizar tu dirección de correo electrónico privada](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Esto no cambiará la forma en que nos pondremos en contacto contigo, pero afectará la manera en que otros te vean. Actualmente configuramos la dirección de correo electrónico de los usuarios de forma privada por defecto, pero es posible que los usuarios de GitHub heredados necesiten actualizar sus configuraciones. Por favor, consulta la información adicional sobre las direcciones de correo electrónico en los mensajes de confirmación [aquí](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). - -Dependiendo de tu [configuración de correo electrónico](https://github.com/settings/emails), GitHub puede enviar ocasionalmente correos electrónicos de notificación sobre los cambios en un repositorio que estás viendo, nuevas características, solicitudes de comentarios, cambios importantes en la política o para ofrecer asistencia al cliente. También enviamos correos electrónicos de marketing, basados en tus opciones y de acuerdo con las leyes y regulaciones vigentes. Hay un enlace "darse de baja" ubicado en la parte inferior de cada uno de los correos electrónicos de marketing que te enviamos. Ten en cuenta que no puedes optar por no recibir comunicaciones importantes de nosotros, como correos electrónicos de nuestro equipo de soporte o correos electrónicos del sistema, pero puedes configurar la configuración de las notificaciones en tu perfil para optar por no recibir otras comunicaciones. - -Nuestros correos electrónicos pueden contener una etiqueta de píxeles, que es una pequeña imagen clara que puede decirnos si has abierto o no un correo electrónico y cuál es tu dirección IP. Utilizamos esta etiqueta de píxeles para que nuestro correo electrónico sea más efectivo para ti y para asegurarnos de que no te estamos enviando correo electrónico no deseado. - -### Resolver reclamos - -Si tienes inquietudes acerca de la forma en que GitHub está manejando tu Información personal del usuario, por favor haznos un comentario inmediatamente. Queremos ayudar. Puedes ponerte en contacto con nosotros completando el [Formulario de contacto de privacidad](https://support.github.com/contact/privacy). También puedes enviarnos un correo electrónico directamente a privacy@github.com con el asunto "Confirmaciones de privacidad". Responderemos rápidamente, dentro de los 45 días a más tardar. - -También puedes ponerte en contacto directamente con nuestro Responsable de Protección de Datos. - -| Nuestra casa central de los Estados Unidos | Nuestra oficina de la UE | -| ------------------------------------------ | ------------------------ | -| Oficial de Protección de Datos de GitHub | GitHub BV | -| 88 Colin P. Kelly Jr. St. | Vijzelstraat 68-72 | -| San Francisco, CA 94107 | 1017 HL Amsterdam | -| Estados Unidos | Países Bajos | -| privacy@github.com | privacy@github.com | - -#### Proceso de resolución de disputas - -En el improbable caso de que surja una disputa entre tú y GitHub con respecto al manejo de tu Información personal del usuario, haremos todo lo posible por resolverla. Adicionalmente, si eres un residente de un estado miembro de la UE, tienes el derecho de emitir una queja con tu autoridad supervisora local, y podrías tener más [opciones](/github/site-policy/global-privacy-practices#dispute-resolution-process). - -### Cambios en tu Declaración de privacidad - -Aunque es probable que la mayoría de los cambios sean mínimos, GitHub puede cambiar nuestra Declaración de privacidad de manera ocasional. Les notificaremos a los Usuarios acerca de los cambios materiales a esta Declaración de privacidad por medio de nuestro Sitio web, al menos, 30 días antes de que el cambio entre en vigencia a través de la publicación de un aviso en nuestra página de inicio o enviando un correo electrónico a la dirección principal de correo electrónico que se especifica en tu cuenta de GitHub. También actualizaremos nuestro [Repositorio de políticas del sitio](https://github.com/github/site-policy/), que realiza un seguimiento de todos los cambios de esta política. Por cambios en esta Declaración de privacidad que no sean cambios sustanciales o que no afecten tus derechos, alentamos a los Usuarios a revisar nuestro repositorio de Políticas del sitio de manera frecuente. - -### Licencia - -La presente Declaración de privacidad está autorizada conforme a esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). - -### Contactarse con GitHub -Las preguntas al respecto de la Declaración de privacidad de GitHub o de las prácticas de manejo de la información se deben realizar por medio de nuestro [Formulario de contacto de privacidad](https://support.github.com/contact/privacy). - -### Traducciones - -A continuación, aparecen traducciones de este documento a otros idiomas. En caso de cualquier conflicto, incertidumbre o aparente inconsistencia entre cualquiera de esas versiones y la versión en inglés, la versión en inglés es la versión que prima. - -#### Francés -Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(12.20.19)(FR).pdf) - -#### Otras traducciones - -Para las traducciones de esta declaración hacia otros idiomas, por favor visita [https://docs.github.com/](/) y selecciona el idioma desde el menú desplegable debajo de "Inglés". diff --git a/translations/es-XL/content/github/site-policy/github-registered-developer-agreement.md b/translations/es-XL/content/github/site-policy/github-registered-developer-agreement.md deleted file mode 100644 index 6d867d8eab..0000000000 --- a/translations/es-XL/content/github/site-policy/github-registered-developer-agreement.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -title: Acuerdo de programador registrado de GitHub -redirect_from: - - /articles/github-registered-developer-agreement -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -GitHub tiene la suerte de tener muchos programadores integrándose a nuestra plataforma. Creemos que es grandioso y deseamos mejorar aún más esa experiencia. El Programa de Programadores de GitHub (el “Programa”) nos ayuda a contactarte, compartir información contigo y apoyar tus esfuerzos creativos mejor que nunca. La relación especial entre GitHub y la comunidad de programadores que el Programa crea requiere un conjunto especial de términos. Bienvenido al Acuerdo de Programador Registrado (“Contrato”). - -Este Acuerdo es un acuerdo legal entre tú (“tú”) y GitHub, Inc. (“GitHub”, “nosotros”). Asegúrate de leer cuidadosamente este Acuerdo - regula tu participación en el Programa, y sólo podemos permitirte participar en el Programa si aceptas todos los términos de este Acuerdo. Al hacer clic en "Acepto" abajo, o al participar en el Programa de cualquier otra forma - por ejemplo, accediendo a la información sobre los productos o características de GitHub que aún no están disponibles para el público en general, estás de acuerdo en cumplir todos los términos de este Acuerdo. SI ESTÁS INGRESANDO EN EL PRESENTE ACUERDO EN NOMBRE DE UNA EMPRESA U OTRA ENTIDAD LEGAL, DECLARAS QUE TIENES LA AUTORIDAD LEGAL PARA VINCULAR A LA ENTIDAD CON EL PRESENTE ACUERDO, EN CUYO CASO "TÚ" SIGNIFICARÁ LA ENTIDAD QUE REPRESENTAS. SI NO TIENES DICHA AUTORIDAD O SI NO ESTÁS DE ACUERDO CON LOS TÉRMINOS Y CONDICIONES DEL PRESENTE ACUERDO, DEBES SELECCIONAR EL BOTÓN "CANCEL" (CANCELAR) Y NO PUEDES PARTICIPAR EN EL PROGRAMA. SI ERES UNA EMPRESA U OTRA ENTIDAD LEGAL, REPRESENTAS QUE LA PERSONA QUE HACE CLIC EN "ACEPTO" TIENE LA AUTORIDAD PARA VINCULARTE CON EL PRESENTE ACUERDO. - -1. **Se aplicarán los términos de uso de GitHub.com** - - Necesitas tener una cuenta en GitHub.com para poder participar en el programa. Al hacer clic en "Acepto" en la parte inferior del presente acuerdo, también aceptas estar obligado por los [](/articles/github-terms-of-service) (los "TOS") de GitHub.com. En el caso de un conflicto directo entre el presente acuerdo y los TOS, el presente acuerdo regulará; a menos que se establezca de otra forma, ambos acuerdos se aplicarán al mismo tiempo. - -2. **Términos del programa** - - Publicamos los [Beneficios y lineamientos del programa](/program/) (el "Resumen del programa"). Como es de esperarse, la descripción general del programa cambiará de vez en cuando. Estos cambios se te aplicarán como participante en el programa, por lo que te invitamos a que revises de forma periódica la descripción del programa para seguir informado de cualquier cambio. Por una variedad de razones, es posible que necesitemos cambiar, suspender o interrumpir el programa o algunos de los beneficios que ofrecemos. Aceptas que podemos tomar dichas acciones sin responsabilidad contigo, excepto como se especifica en la sección 8. - -3. **Licencia API** - - Siempre y cuando continúes cumpliendo con los TOS, el presente acuerdo y los términos del programa, te otorgamos una licencia limitada, en todo el mundo, no exclusiva y no transferible durante la vigencia del presente acuerdo para acceder y utilizar nuestra API (tal como se define en el [O](/articles/github-terms-of-service)) únicamente con el fin de desarrollar, demostrar, probar y respaldar la interoperabilidad y las integraciones entre tus productos y servicios y nuestros productos y servicios. - - Prometes no actuar de forma incorrecta con nuestra API. Entre otras cosas, esto significa que no vas y no permitirás que otros modifiquen, publiquen, vendan, arrienden, licencien, distribuyan o sublicencien nuestra API; o descompilen, desarticulen, usen ingeniería inversa o intenten derivar el código fuente de nuestra API; reproduzcan, modifiquen o originen trabajos derivados de nuestra API; utilicen nuestra API para proporcionar servicios de burocracia, alojamiento de aplicaciones o procesamiento a terceros; incorporen o combinen de otro modo nuestra API con cualquiera de sus productos o servicios; o utilicen nuestra API para participar, apoyar, o habilitar cualquier tipo de actividad ilegal. - - Nos reservamos el derecho en cualquier momento a modificar o interrumpir, de manera temporal o permanente, tu acceso a la API (o cualquier parte de la misma) con o sin aviso. Es tu responsabilidad exclusiva asegurarte de que tu uso de la API sea compatible con la API vigente en ese momento. Además de los derechos que te otorgamos expresamente en el presente acuerdo o en los TOS, no te otorgamos ningún derecho o licencia a nuestra API, o a cualquier otro producto o servicio de GitHub. - -4. **Tus productos, servicios e integraciones** - - Tus productos, servicios e integraciones (colectivamente, tus “Productos”) son responsabilidad tuya. Eso significa que eres el único responsable de desarrollar, operar y mantener todos los aspectos de tus productos; asegurar que todos los materiales utilizados con o en tus productos sean legales en todas las jurisdicciones donde se usan tus productos y que no promocionen actividades ilegales; obtener cualquier derecho o licencia necesarios para usar y/o distribuir cualquier software de terceros que uses, incluyas, integres o distribuyas con tus productos; y proporcionar a los clientes del usuario final el mismo soporte técnico de alta calidad para tus productos cuando operan en conjunción con nuestra API o cualquier otro de nuestros productos y servicios como lo haces cuando operan por tu cuenta. - -5. **Marketing y Publicidad** - - El marketing y la divulgación de tus integraciones con GitHub es valioso para ambos. Queremos asegurarnos de que suceda de la manera correcta, por lo que hemos incluido un lenguaje aquí para ayudar a aclarar algunas cosas que "hacer" y que "evitar" básicas. - - Aceptas que no harás ninguna representación, garantía o endoso a nadie en nombre de GitHub (incluyendo, entre otras cosas, cualquier producto o servicio de GitHub). A menos que digamos específicamente que está bien en los términos del programa, prometes no declarar o insinuar que hemos desarrollado, respaldado, revisado o aprobado de alguna manera cualquiera de tus productos. - - Si decides promover o publicitar alguno de nuestros productos o servicios en relación con tus productos, deberás asegurarte de cumplir con los términos del presente acuerdo, los términos del programa, los TOS, nuestra [política de marcas comerciales](/articles/github-trademark-policy), y cualquier otra política de GitHub aplicable. Sujeto a los términos y condiciones del presente acuerdo y de los TOS y durante la vigencia del presente acuerdo, te otorgamos una licencia limitada, revocable, en todo el mundo, no exclusiva e intransferible para usar nuestras marcas comerciales, marcas de servicio y logotipos (colectivamente, las "marcas de GitHub") de acuerdo con nuestra [política de marcas comerciales](/articles/github-trademark-policy) y como se especifica en los términos del programa, únicamente con el fin de publicar tu membresía en el programa. - - Queremos decirle al mundo sobre ti y tu participación en el Programa. Para ayudarnos a hacerlo, nos otorgas una licencia limitada, revocable, en todo el mundo, no exclusiva y no transferible para usar tus marcas comerciales, marcas de servicio y logotipos (colectivamente, las "marcas de socios") en nuestros materiales de marketing, únicamente con el fin de promover el programa y publicar tu participación en él. - - A excepción de lo establecido en el presente acuerdo y en los términos de servicio, ninguna parte del presente acuerdo se considerará que otorga a una de las partes, algún derecho, título o interés sobre las marcas de la otra parte. Aceptas no, ya sea durante o después del plazo del presente acuerdo: (i) desafiar o ayudar a otras personas a desafiar las marcas de GitHub, o nuestro registro o cumplimiento de las marcas de GitHub; (II) tratar de adoptar, usar, solicitar o registrar cualquier marca comercial, marca de servicio, logotipo, URL, nombre de dominio de Internet o símbolo que sea confusamente similar a las marcas de GitHub; o (III) hacer que cualquier declaración negativa, falsa o despectivo (ya sea escrita u oral) a cualquier tercero acerca de nosotros, nuestros productos o nuestros servicios. - -6. **Confidencialidad; materiales de pre-lanzamiento** - - Como programador registrado en el programa, puedes obtener acceso a información especial que no esté disponible para el resto del mundo. Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. - - Aceptas que toda información no pública que te demos, o a la que puedas tener acceso como parte del programa, se considerará información confidencial de GitHub (en conjunto, "información confidencial"), independientemente de si está marcada o identificada como tal. Aceptas únicamente utilizar dicha información confidencial para tus fines autorizados como participante en el programa (el "propósito") y no para ningún otro propósito. Debes tomar las precauciones razonables para evitar cualquier uso, divulgación, publicación o divulgación no autorizada de nuestra información confidencial. Prometes no revelar, publicar o diseminar ninguna información confidencial a ningún tercero que no sea tus empleados y contratistas y posteriormente solo en la medida en que: (i) necesiten conocer la información confidencial para el propósito; (II) les haces conocer la naturaleza confidencial de la información confidencial; (III) continúes siendo responsable de los actos y omisiones de dichos empleados y contratistas; y (IV) no prohibimos o restringimos dicha divulgación. - - Comprendes que la divulgación o el uso no autorizados de nuestra información confidencial podrían causarnos un daño irreparable y una lesión significativa que podría ser difícil de cuantificar para nosotros. En consecuencia, aceptas que tendremos el derecho de buscar medidas cautelares inmediatas para asegurarnos de que cumplas con el presente acuerdo, además de cualesquier otro derecho y recurso que podamos tener. Si se te solicita por ley, regulación o una orden vinculante válida de un tribunal de jurisdicción competente para divulgar nuestra información confidencial, puedes hacerlo, pero solo si nos lo notificas antes de hacerlo y harás tu mejor esfuerzo para limitar dicha divulgación y buscar el tratamiento confidencial y protector de dicha información. - - Las obligaciones de la presente sección 6 no se aplicarán a la información que puedas probar que: (i) estuviera generalmente disponible para el público antes de que te la revelemos; (II) se convirtió generalmente disponible para el público después de que te la revelemos, sin acción o inacción por tu parte, o por parte de tus empleados o contratistas; (III) que conocías antes de que te la revelemos; (IV) le fue revelada por un tercero, que no tenía ninguna obligación de confidencialidad con respecto a la misma; (v) que desarrollaste de forma independiente sin violar ninguna obligación de confidencialidad con nosotros o cualquier tercero; o (VI) te dimos permiso para divulgar, en un escrito firmado por uno de nuestros representantes autorizados. - - Si te otortamos algún software de prelanzamiento o documentación o materiales relacionados, que puedan ncluir videos u otras formas de contenido ("materiales de prelanzamiento"), entonces, sujeto al cumplimiento de los términos y condiciones del presente acuerdo y de los TOS, por la presente te otorgamos un derecho y una licencia no exclusivos, intransferibles y revocables para usar los materiales de prelanzamiento únicamente para respaldar tus pruebas y/o el desarrollo de productos o servicios que están diseñados para funcionar en combinación con los sistemas o programas para los cuales se diseñan los materiales prelanzamiento. Si los materiales de prelanzamiento están acompañados de un acuerdo de licencia separado, aceptas que se aplicarán el acuerdo de licencia separado (además de cualquier disposición más restrictiva contenida en el presente acuerdo o en los términos de servicio). Aceptas no descompilar, hacer ingeniería inversa, desmontar o reducir de cualquier otra manera los materiales de prelanzamiento a una forma perceptible por el hombre y prometes no modificar, establecer redes, alquilar, arrendar, transmitir, vender o prestar los materiales de prelanzamiento, en su totalidad o en parte. Comprendes que no estamos obligados a proporcionarte ningún material de prelanzamiento, a proporcionarte actualizaciones, mejoras o correcciones en los materiales de prelanzamiento, o a notificarte de los cambios que realicemos a nuestros productos y servicios, ahora o en el futuro. - -7. **Cuotas y pago** - - Pueden haber honorarios asociados con la participación en el programa. Te diremos cuáles son esas tarifas en los términos del programa, ya que las actualizamos de vez en cuando (las "tarifas del programa"). Si nos proporcionaste tu información de pago antes, aceptas que podemos cobrar la misma tarjeta de crédito o cuenta de PayPal como parte del presente acuerdo. De lo contrario, deberás otortarnos una cuenta de pago válida y otra información de respaldo. Excepto que se disponga expresamente lo contrario en la sección 8, cualquier pago que nos realices para el programa no es reembolsable. Nos otorgas permiso para cobrar automáticamente tu cuenta de pago en el aniversario de tu primera fecha de pago para cubrir todas las tarifas del programa del año que viene, a menos que canceles el presente acuerdo de acuerdo con la sección 8. All fees are due in U.S. Todas las tarifas se deben pagar en dólares estadounidenses y son exclusivas de todos los impuestos, gravámenes o deberes impuestos por las autoridades fiscales (eres responsable de todos ellos, a excepción de los impuestos basados en nuestros ingresos). - -8. **Plazo y terminación** - - El presente acuerdo comienza en la fecha en que haces clic en "acordar", y continúa durante un período de un (1) año. El presente acuerdo se renovará automáticamente por términos sucesivos de un año, a menos que cualquiera de las partes le dé un aviso por escrito al menos treinta (30) días antes del vencimiento del plazo actual que quiere terminar o uno de nosotros lo terminará antes de acuerdo con lo dispuesto en la presente sección 8. - - Tanto tú como GitHub pueden rescindir el presente acuerdo por cualquier motivo, sin causa, después de treinta (30) días de aviso previo por escrito a la otra. Si finalizamos el presente acuerdo o suspendemos tu acceso al programa por cualquier motivo que no sea tu incumplimiento del presente acuerdo, los términos del programa o los TOS, nosotros, como tu único recurso y nuestra única obligación de dicha terminación, te reembolsaremos la parte proporcional de las tarifas del programa que nos pagaste por el plazo actual del presente acuerdo. El presente acuerdo terminará de inmediato, sin la obligación de aviso, si incumple cualquier término del presente acuerdo, los términos del programa o los TOS. - - Los derechos y obligaciones en las secciones 1, 2, 3 (segundo y tercer párrafo), 4, 5 (segundo y último párrafo), 6, 7 y 9 a 21 del presente acuerdo sobrevivirán a la terminación o a la expiración del presente acuerdo. Tras la terminación o la expiración del presente acuerdo, todos los derechos y las licencias que te otorgaron en el presente acuerdo dejarán de existir de inmediato, regresarás (o, a petición nuestra, destruirás) toda nuestra información confidencial y cualquier copia (incluidas las copias electrónicas) que estén en tu posesión o control y certificaras por escrito que has cumplido con estos requisitos. - -9. **Garantías y limitaciones de responsabilidades** - - Nos garantizas que: (i) tienes la autoridad para celebrar el presente acuerdo y para cumplir con sus obligaciones; (II) llevarás a cabo negocios de una manera que refleje favorablemente en todo momento en los productos y servicios de GitHub y nuestro buen nombre, buena voluntad y reputación; (III) no hará declaraciones o representaciones falsas o engañosas con respecto a GitHub o a nuestros productos y servicios; (IV) no tomarás ninguna obligación o responsabilidad, ni harás ninguna representación, garantía o endoso a nadie en nuestro nombre (incluyendo, entre otros, alguno de nuestros productos o servicios); y (v) no declararás o implicarás que hemos desarrollado, respaldado, revisado o aprobado de alguna manera cualquiera de tus productos. - - EL PROGRAMA, LA API Y CUALQUIER INFORMACIÓN CONFIDENCIAL QUE TE OTORGUEMOS (INCLUYENDO, ENTRE OTROS, LOS MATERIALES DE PRELANZAMIENTO) SE PROPORCIONAN "TAL CUAL" Y SIN GARANTÍAS DE NINGÚN TIPO, EXPRESAS O IMPLÍCITAS. RENUNCIAMOS ESPECÍFICAMENTE A TODAS LAS GARANTÍAS O CONDICIONES IMPLÍCITAS DE COMERCIABILIDAD, IDONEIDAD PARA UN PROPÓSITO Y NO INFRACCIÓN PARTICULAR. NO GARANTIZAMOS QUE LOS SERVICIOS O PRODUCTOS QUE PONGAMOS A TU DISPOSICIÓN SE REUNIRÁN CON LOS REQUISITOS DE TUS USUARIOS FINALES. - -10. **Indemnización** - - Te ofrecemos muchas cosas útiles de pre-lanzamiento como parte del programa y existen maneras en las que podrías usar esas cosas de forma inadecuada que podrían dañarnos. Con eso en mente y dado que no podemos controlar las formas en que participas en el programa, aceptas que nos indemnizarás, defenderás y eximirás de toda responsabilidad a cualquier reclamación que pueda surgir por debajo o fuera de tu participación en el programa; tu uso de la API, nuestra información confidencial o cualquier otro producto y servicio de GitHub; tu negligencia o mala conducta intencional; tus productos o cualquier integración que desarrolles, diseñes, promociones o distribuyas usando nuestra API o cualquier información confidencial; cualquier tergiversaciones que realices con respecto a nosotros o a nuestros productos o servicios; o tu violación de cualquier parte del presente acuerdo. - -11. **Limitación de responsabilidad** - - EN NINGÚN CASO SEREMOS RESPONSABLES ANTE TI O ANTE NINGÚN TERCERO POR NINGÚN DAÑO INDIRECTO, ESPECIAL, INCIDENTAL, CONSECUENTE, EJEMPLAR O PUNITIVO, INCLUYENDO, ENTRE OTROS, LOS DAÑOS POR DATOS PERDIDOS, PÉRDIDAS DE BENEFICIOS O COSTOS DE ADQUISICIÓN DE BIENES O SERVICIOS SUSTITUTIVOS, SIN PERJUICIO DE LO QUE SE CAUSE Y BAJO CUALQUIER TEORÍA DE RESPONSABILIDAD, YA SEA POR CONTRATO, AGRAVIO (INCLUYENDO LA RESPONSABILIDAD DE PRODUCTOS , RESPONSABILIDAD ESTRICTA Y NEGLIGENCIA), O CUALQUIER OTRA TEORÍA, Y SI SABÍAMOS O NO O DEBERÍAMOS HABER SABIDO SOBRE LA POSIBILIDAD DE DICHOS DAÑOS. EN NINGÚN CASO NUESTRA RESPONSABILIDAD TOTAL ANTE TI DERIVADA DEL PRESENTE ACUERDO O RELACIONADA CON ÉL POR CUALQUIER CAUSA, E INDEPENDIENTEMENTE DE LA FORMA DE ACCIÓN, YA SEA POR CONTRATO O POR AGRAVIO, EXCEDE EL MAYOR DE (I) LOS MONTOS QUE REALMENTE PAGÓ CONFORME A LO DISPUESTO EN EL PRESENTE ACUERDO; O (II) 500 DÓLARES ($500). LAS LIMITACIONES ANTERIORES SE APLICARÁN A PESAR DEL FRACASO DEL PROPÓSITO ESENCIAL DE CUALQUIER SOLUCIÓN LIMITADA QUE SE INDIQUE EN EL PRESENTE ACUERDO. - -12. **Control de exportación** - - No se te permite exportar o volver a exportar ninguna información confidencial, excepto según lo autorizado por la ley de los Estados Unidos y las leyes de la jurisdicción en la que se obtuvo la información confidencial. In particular, you aren’t allowed to export or re-export our Confidential Information into any U.S. embargoed countries, to anyone on the U.S. Treasury Department's list of Specially Designated Nationals, or to anyone on the U.S. Department of Commerce Denied Person's List or Entity List. Al unirte al programa o recibir cualquiera de nuestra información confidencial, declaras y garantizas que no estás ubicado en ningún país de estos o en una lista de esa índole. - -13. **Derechos de propiedad** - - Aceptas que GitHub y sus licenciantes son propietarios de todo derecho, título e interés en la API, los materiales de prelanzamiento y todos los demás productos y servicios de GitHub; toda la información y los datos relativos a sus configuraciones y combinaciones; y todas las modificaciones y obras derivadas de cualquiera de las anteriores. Aceptas no eliminar, alterar, cubrir o confundir ningún derecho de autor u otros avisos de derechos de propiedad que colocamos o insertamos en la API, los materiales de prelanzamiento o cualquier otro producto y servicio de GitHub. - -14. **Usuarios gubernamentales** - - Si eres una entidad gubernamental, esta sección aplica para ti. Cierta parte de nuestra información confidencial puede considerarse "artículos comerciales", ya que ese término se define en 48 C. § 2,101, que consiste en "software informático comercial" y "documentación del software informático comercial", ya que dichos términos se usan en 48 C. § 12,212 o 48 C. § 227.7202, según corresponda. Consistente con 48 C. § 12,212 o 48 C. § 227.7202-1 a 227.7202-4, según corresponda, la documentación del software informático comercial y del software informático comercial se licencia para los usuarios finales del gobierno de los EE. UU. (a) únicamente como elementos comerciales y (b) con solo aquellos derechos que se conceden a todos los demás usuarios finales conforme a los términos y condiciones del presente documento. GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107. - -15. **Desarrollo independiente** - - Ninguna parte del presente acuerdo perjudicará nuestro derecho a desarrollar, adquirir, licenciar, comercializar, promocionar o distribuir productos, software o tecnologías que puedan competir con tus productos. - -16. **Comentarios** - - Siempre estamos tratando de mejorar y tus comentarios nos ayudarán a hacerlo. Si decides hacernos comentarios, sugerencias o recomendaciones para el programa o para nuestros productos o servicios (colectivamente, "comentarios"), reconoces y aceptas que somos libres de usar esos comentarios de cualquier manera que queramos, sin restricciones (sujeto a cualquier patente o derecho de autor aplicable, por supuesto). - -17. **Contratistas independientes** - - Las partes del presente acuerdo son contratistas independientes. Ninguno de nosotros será considerado como empleado, agente, socio, franquiciador, franquiciado o representante legal del otro para ningún propósito y ninguno de nosotros tendrá ningún derecho, poder o autoridad para crear ninguna obligación o responsabilidad en nombre de la otra. - -18. **Assignment** - - No puedes ceder o transferir el presente acuerdo o ninguno de tus derechos en virtud del mismo, en su totalidad o en parte, por el funcionamiento de la ley o de cualquier otra manera, sin nuestro consentimiento previo por escrito. - -19. **Legislación aplicable y jurisdicción** - - El presente acuerdo se interpretará y entenderá de acuerdo con las leyes del estado de California, sin tener en cuenta los principios de conflicto de leyes. Todas las disputas que surjan del presente Acuerdo estarán sujetas a la jurisdicción exclusiva del estado y los tribunales federales ubicados en el Condado de San Francisco, California y cada uno de nosotros consiente la jurisdicción personal allí. - -20. **Modificaciones; renuncias; inexistencia de terceros beneficiarios** - - Es posible que el presente acuerdo no se cambie, excepto mediante un escrito firmado por ambas partes. Cualquier renuncia a las disposiciones del presente acuerdo o de los derechos o recursos de una parte conforme a lo dispuesto en el presente acuerdo debe ser por escrito para que sea efectiva. Si se encuentra que algún término, condición o disposición del presente acuerdo no es válido o no ejecutable, los términos restantes seguirán siendo válidos y exigibles en la medida en que lo permita la ley. Cada una de las partes acepta expresamente que no hay terceros beneficiarios del presente acuerdo. - -21. **Entire Agreement** - - El presente acuerdo, los términos de servicio y los términos del programa contienen el acuerdo completo de las partes con respecto al tema y sustituyen todas las comunicaciones, representaciones, entendimientos y acuerdos previos, ya sean escritos u orales. Los términos o condiciones de cualquiera de tus pedidos de compras, confirmacones u otros documentos que nos envíes en relación con el presente acuerdo serán nulos y sin efecto. diff --git a/translations/es-XL/content/github/site-policy/github-research-program-terms.md b/translations/es-XL/content/github/site-policy/github-research-program-terms.md deleted file mode 100644 index fc6de19e43..0000000000 --- a/translations/es-XL/content/github/site-policy/github-research-program-terms.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Términos del programa de investigación de GitHub -redirect_from: - - /articles/github-research-program-terms -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -¡Bienvenido al programa de investigación de GitHub (el "Programa")! Para participar, necesitaremos que accedas a un conjunto especial de términos, el acuerdo del programa de investigación de GitHub ("Acuerdo"). - -El presente acuerdo es un acuerdo legal entre tú ("tú", "tu") y GitHub, Inc. (“GitHub”, “nosotros”). Asegúrate de leer el presente Acuerdo detenidamente - solo puedes ser un participante del programa si aceptas todos los términos del presente acuerdo. Al participar en el programa de cualquier manera, por ejemplo, al ingresar a información sobre los productos o servicios de GitHub que aún no están disponibles para el público en general, estás aceptando estar sujeto a todos los términos del presente acuerdo. - -### A. Tu retroalimentación - -Siempre intentamos mejorar nuestros productos y servicios y tu retroalimentación como participante del programa nos ayudará a hacerlo. Si decides darnos alguna idea, conocimiento algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario para nuestros productos o servicios a través del programa (colectivamente, "Retroalimentación"), entonces necesitamos los derechos legales para usar y analizar esa información para dichos fines. En la jerga legal, eso significa que otorgas a GitHub una licencia libre de regalías, totalmente pagada, en todo el mundo, transferible, sublicenciable, irrevocable y perpetua para implementar, usar, modificar, explotar comercialmente y/o incorporar los comentarios en nuestros productos, servicios y documentación. - -### B. Confidentiality - -GitHub puede proporcionarle acceso a la información especial que no está disponible para el resto del mundo con el propósito de proporcionarnos comentarios a través del programa (el "Objetivo"). Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. - -Aceptas que toda información no pública que compartamos contigo o a la que puedas tener acceso como participante del programa se considerará información confidencial de GitHub (en conjunto, "información confidencial"), independientemente de si está marcada o identificada como tal. Aceptas usar esa información confidencial únicamente para el propósito que se indica arriba y no para ningún otro propósito. Debes usar el mismo grado de cuidado que usarías con tu información confidencial, pero no menos de las precauciones razonables para evitar cualquier uso no autorizado, divulgación, publicación o diseminación de nuestra información confidencial. Prometes no revelar, publicar o diseminar ninguna información confidencial a ningún tercero. - -Comprendes que la divulgación o el uso no autorizados de nuestra información confidencial podrían causarnos un daño irreparable y una lesión significativa que podría ser difícil de cuantificar para nosotros. En consecuencia, aceptas que tendremos el derecho de buscar medidas cautelares inmediatas para asegurarnos de que cumplas con el presente acuerdo, además de cualesquier otro derecho y recurso que podamos tener. Si se te solicita por ley, regulación o una orden vinculante válida de un tribunal de jurisdicción competente para divulgar nuestra información confidencial, puedes hacerlo, pero solo si nos lo notificas antes de hacerlo y harás tu mejor esfuerzo para limitar dicha divulgación y buscar el tratamiento confidencial y protector de dicha información. - -Las obligaciones de la presente sección 2 no se aplicarán a la información que puedas probar que: (i) estuvo generalmente disponible para el público antes de que te la revelaramos; (II) estuvo generalmente disponible para el público después de que te la revelamos, sin acción o inacción por tu parte, o por parte de tus empleados o contratistas; (III) conocías antes de que te la revelaramos; (IV) te fue revelada por un tercero, que no tenía ninguna obligación de confidencialidad con respecto a la misma; (v) que desarrollaste de forma independiente sin violar ninguna obligación de confidencialidad con nosotros o cualquier tercero; o (VI) te dimos permiso para divulgar, en un escrito firmado por uno de nuestros representantes autorizados. - -### C. Salvaguarda de derechos - -Toda la información confidencial sigue siendo propiedad exclusiva y propiedad de GitHub. Ninguna de las partes adquiere ningún derecho de propiedad intelectual conforme a lo dispuesto en el presente acuerdo, salvo que se especifique expresamente aquí. - -### D. Privacidad - -Al participar en este programa, aceptas el uso de tu información personal con fines de investigación y para ningún otro propósito. Como parte del programa, es posible que uses tu información personal para contactarte o conservar tu información, para contactarte en una fecha posterior. La información personal no incluye información agregada, que no identifiques personalmente. Es posible que uses la información de identificación personal o agregada que se recopila a través del programa para operar, analizar y mejorar nuestros productos y servicios. - -Puedes retirar tu consentimiento en cualquier momento y solicitar acceso o la eliminación de la información personal que tenemos sobre ti. Para obtener más información acerca de cómo puedes acceder, actualizar, modificar o eliminar la información personal que GitHub recopila a través del programa, consulta la[Declaración de privacidad de GitHub](/articles/github-privacy-statement/) o contáctanos a través de nuestra {% data variables.contact.contact_privacy %}. - -### E. Términos del software y los servicios de GitHub - -Si se necesita acceso a los servicios o al software de GitHub para participar en determinados estudios o actividades del programa, los servicios o el acuerdo de software correspondientes se aplicarán a tu uso de esos productos (los "términos generalmente aplicables"). En el caso de un conflicto directo entre el presente acuerdo y los términos generalmente aplicables, tus términos generalmente aplicables controlarán, excepto con respecto a cualquier uso de información confidencial (como se define a continuación), en cuyo caso el presente acuerdo controlará. - -### F. Exención de garantías - -Toda la información confidencial y otros materiales que recibes a través del programa se proporcionan "tal cual" y sin garantía de ningún tipo. Sin perjuicio de esto, renunciamos expresamente a todas las garantías, ya sean expresas, implícitas o reglamentarias, relacionadas con el programa, incluidas, entre otras, cualquier garantía de comerciabilidad, idoneidad para un propósito particular, título, seguridad, exactitud y no infracción. - -### G. Limitación de responsabilidad - -A excepción de lo prohibido por la ley, entiendes y aceptas que no seremos responsables ante ti o ningún tercero por cualquier pérdida de beneficios, uso, buena voluntad o datos, o por cualquier daño incidental, indirecto, especial, consecuente o ejemplar. - -Nuestra responsabilidad es limitada, ya sea que hayamos sido informados o no de la posibilidad de tales daños, e incluso si se descubre que un remedio establecido en este Acuerdo no ha cumplido su propósito esencial. No nos responsabilizaremos por ningún fallo o retraso debido a asuntos que escapen a nuestro control razonable. - -### H. Varios - -#### 1. Legislación aplicable -Excepto en la medida en que la ley aplicable establezca lo contrario, este Acuerdo entre tu persona y GitHub y cualquier acceso o uso del Sitio Web o del Servicio se rige por las leyes federales de los Estados Unidos de América y las leyes del Estado de California, sin tener en cuenta el conflicto de disposiciones legales. Tú y GitHub acuerdan someterse a la jurisdicción exclusiva y sede de los tribunales ubicados en la Ciudad y el Condado de San Francisco, California. - -#### 2. Intransferible -GitHub may assign or delegate this Agreement, in whole or in part, to any person or entity at any time with or without your consent, including the license grant in Section A. You may not assign or delegate any rights or obligations under this Agreement without our prior written consent, and any unauthorized assignment and delegation by you is void. - -#### 3. Divisibilidad, sin exención y supervivencia -Si alguna parte de este Acuerdo es considerada inválida o no aplicable, esa parte del Acuerdo será interpretada para reflejar la intención original de las partes. Las partes restantes permanecerán en pleno vigor y efecto. Cualquier incumplimiento por parte de GitHub para hacer cumplir cualquier disposición de este Acuerdo no será considerado una renuncia a nuestro derecho a hacer cumplir dicha disposición. Nuestros derechos en virtud de este Acuerdo sobrevivirán a cualquier rescisión de este Acuerdo. - -#### 4. Enmiendas, acuerdo completo -El presente acuerdo solo puede modificarse mediante una enmienda por escrito firmada por un representante autorizado de GitHub. El presente Acuerdo, junto con los términos generalmente aplicables y la declaración de privacidad de GitHub, representan la declaración completa y exclusiva del acuerdo entre tú y nosotros. Este Acuerdo sustituye cualquier propuesta o acuerdo previo oral o escrito, y cualquier otra comunicación entre tu persona y GitHub relacionada con el tema de estos términos, incluyendo cualquier acuerdo de confidencialidad o no divulgación. diff --git a/translations/es-XL/content/github/site-policy/github-sensitive-data-removal-policy.md b/translations/es-XL/content/github/site-policy/github-sensitive-data-removal-policy.md deleted file mode 100644 index 6ce47f15bd..0000000000 --- a/translations/es-XL/content/github/site-policy/github-sensitive-data-removal-policy.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Política de eliminación de datos sensibles de GitHub -redirect_from: - - /articles/github-sensitive-data-removal-policy -versions: - free-pro-team: '*' ---- - -Si crees que el contenido en GitHub infringe un derecho de autor válido que posees, por favor consulta nuestra [política de retiro DMCA](/articles/dmca-takedown-policy/) y nuestra [Guía para enviar una notificación de retiro DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice/). Confiamos en la notificación de la DMCA y en el proceso de retiro para la mayoría de nuestras acciones de eliminación. - -Sin embargo, entendemos que de vez en cuando se puede publicar contenido sensible y relacionado con la seguridad en GitHub, ya sea accidentalmente o con propósito. Proporcionamos nuestro proceso de eliminación de datos sensibles para borrar estos datos sensibles en determinadas circunstancias excepcionales en las que el proceso DMCA no aplicaría, tales como cuando su seguridad está en riesgo de contraseñas expuestas y no posees los derechos de autor sobre el contenido específico que necesitas eliminar, o el contenido no está protegido por derechos de autor. Esta guía describe la información que GitHub necesita de usted para procesar una solicitud para eliminar datos sensibles de un repositorio. - -### ¿Qué son los datos sensibles? - -Para los propósitos de este documento, "datos sensibles" se refiere al contenido que (i) deberías haberse mantenido confidencial, *y* (ii) cuya disponibilidad pública plantea un riesgo específico o dirigido de seguridad para ti o tu organización. - -#### Las solicitudes de eliminación de datos sensibles son adecuadas para: -- Credenciales de acceso, como nombres de usuario combinados con contraseñas, tokens de acceso, u otros secretos sensibles que pueden conceder acceso al servidor, red o dominio de tu organización. -- Los token AWS y otras credenciales de acceso similares que conceden acceso a un tercero en tu nombre. Debes tener la capacidad de mostrar que el token te pertenece. -- Documentación (como diagramas de red) que plantea un riesgo específico de seguridad para una organización. Los nombres de servidores internos, direcciones IP y URL, por sí solos, no son lo suficientemente sensibles; debe ser capaz de mostrar que el uso del nombre del servidor interno en un archivo o parte del código en particular que representa una amenaza para la seguridad. - -#### Las solicitudes de eliminación de datos sensibles son _no_ adecuadas para: -- Solicitudes para eliminar contenido que pueda infringir los derechos de autor de tu empresa o de tu organización. Si tienes preguntas sobre cómo maneja GitHub los asuntos relacionados con los derechos de autor o te gustaría informar sobre contenido que potencialmente infractor, por favor revisa nuestra [política de retiro DMCA](/articles/dmca-takedown-policy/). El proceso de eliminación de datos sensibles generalmente no está destinado a la eliminación de archivos o repositorios completos — solo para las partes específicas de datos sensibles en esos archivos. Mientras que puede haber casos en los que los archivos contienen solamente información confidencial, debes justificar el riesgo de seguridad para la eliminación de dichos archivos y esto puede aumentar el tiempo necesario para procesar tu solicitud. -- Disputas de marcas registradas. Si tiene preguntas sobre cómo maneja GitHub los asuntos relacionados con la marca o deseas informar sobre contenido que contiene marcas comerciales o marcas de servicio, revisa nuestra [Política de Marcas](/articles/github-trademark-policy/). -- Menciones simples de la identidad de tu empresa, nombre, marca, nombre de dominio, u otras referencias a tu empresa en archivos en GitHub. Debes tener la capacidad de articular por qué un uso de la identidad de tu empresa es una amenaza para la postura de seguridad de tu empresa antes de tomar medidas en virtud de esta política. -- Reclamaciones de privacidad. Si tiene inquietudes sobre tu propia privacidad o te estás comunicando con nosotros en nombre de tus empleados debido a una preocupación por la privacidad — por ejemplo, si hay direcciones de correo electrónico privadas u otra información personal publicada, por favor contáctanos a través de [nuestro formulario de contacto sobre privacidad](https://github.com/contact/privacy). -- Archivos completos o repositorios que no plantean un riesgo de seguridad específico, pero consideras que son censurables de otro modo. -- Contenido regido por nuestras [Directrices de la comunidad](/articles/github-community-guidelines/), tales como malware o herramientas de uso general. Si tienes dudas sobre nuestros Lineamientos de Comunidad crees que algún contenido de GitHub podría violarlos, puedes utilizar {% data variables.contact.report_content %} para contactarnos. - -### Cosas que debes saber - -**Realiza preguntas educadamente.** Un gran primer paso antes de enviarnos una solicitud para eliminar datos es intentar contactar directamente con el usuario. Pueden haber ingresado información de contacto en su página de perfil público o en el archivo de soporte o README del repositorio o podrías ponerte en contacto creando una propuesta o solicitud de extracción en el repositorio. Esto no es estrictamente necesario, pero es común. - -**Sin bots.** Debes tener un profesional capacitado para evaluar los hechos de cada solicitud que envíes. Si estás subcontratando tus labores a un tercero, asegúrate de saber cómo trabaja y asegúrate que no estén utilizando bots automatizados para presentar quejas en masa. Estas quejas a menudo incluyen datos que no suponen ninguna amenaza para la seguridad y no incluyen suficientes explicaciones, que requieran un retroceso adicional y resulten en retrasos, incluso cuando la queja es válida. - -**Envía la solicitud correcta.** Ofrecemos este proceso de eliminación de datos sensibles como un servicio excepcional únicamente para contenido de alto riesgo. No podemos utilizar este proceso para eliminar otros tipos de contenidos, como potencialmente infringir contenido y no podemos procesar ningún otro tipo de solicitudes de eliminación simultáneamente mientras procesamos solicitudes de eliminación de información sensible. Podremos ayudarlo más rápidamente si envías tus solicitudes de eliminación de datos confidenciales por separado de cualquier solicitud para eliminar contenido potencialmente infractor. Si no estás seguro de que su solicitud implique sólo datos confidenciales o también involucre otros asuntos legales, por favor pide asesoramiento legal. - -**Tiempo de procesamiento.** Mientras procesamos solicitudes de eliminación de datos sensibles lo antes posible, debido al volumen de solicitudes que procesamos, puede tomar algún tiempo para que tu solicitud se revise.< Las solicitudes adicionales, o múltiples solicitudes de puntos de contacto adicionales, pueden provocar retrasos. - -### ¿Cómo funciona realmente? - -1. **El reclamante investiga.** Corresponde a la parte solicitante llevar a cabo su propia investigación y proporcionarnos los [detalles que necesitamos](#your-request-must-include) — lo que es más importante, una explicación de cómo los datos plantean un riesgo para la seguridad. GitHub no está en posición de buscar o hacer determinaciones iniciales sobre datos sensibles en nombre de cualquier persona u organización. - -2. **El reclamante envía una solicitud de eliminación de datos sensibles.** Después de realizar una investigación, el demandante prepara y [envía una solicitud de eliminación de datos sensibles](#sending-a-sensitive-data-removal-request) a GitHub. Si la solicitud no está lo suficientemente detallada para demostrar el riesgo de seguridad y para que GitHub localice los datos, te responderemos y te solicitaremos más información. - -3. **GitHub pide al usuario que haga cambios.** En la mayoría de los casos, nos pondremos en contacto con el usuario que creó el repositorio y le daremos la oportunidad de eliminar o modificar los datos sensibles especificados en la solicitud o de disputar el reclamo. - -4. **El usuario notifica a GitHub de los cambios.** Si el usuario decide realizar los cambios especificados, debe comunicarnos dentro del período de tiempo que hayan sido permitidos. Si no lo hace, deshabilitaremos el repositorio. Si el usuario nos notifica que ha realizado cambios, verificaremos que los cambios se hayan realizado y notificaremos al demandante. - - O - -5. **El usuario puede impugnar la solicitud.** Si un usuario cree que el contenido en cuestión no es información sensible sujeta a esta Política, puede impugnarlo. Si lo hacen, generalmente dejaremos que el demandante se ponga en contacto con el usuario y trabaje directamente con él, dentro de los límites razonables. - -6. **Cambios a las revisiones del demandante.** Si el usuario realiza cambios, el demandante debe revisarlos. Si los cambios son insuficientes, el demandante debe proporcionar a GitHub detalles explicando por qué. GitHub puede desactivar el repositorio o dar al usuario una oportunidad adicional de hacer los cambios. - -7. **El usuario puede solicitar una ventana adicional para realizar cambios.** Si el usuario perdió su oportunidad de eliminar los datos confidenciales especificados en el aviso, podríamos permitirle una ventana adicional de aproximadamente 1 día hábil, previa solicitud, para realizar esos cambios. En ese caso, GitHub notificará al demandante. - -#### ¿Qué hay de las bifurcaciones? (o ¿Qué es una bifurcación?) -Una de las mejores características de GitHub es la capacidad de los usuarios de "bifurcar" los repositorios de otros. ¿Qué significa esto? En esencia, significa que los usuarios pueden hacer una copia de un proyecto en GitHub en sus propios repositorios. Como la licencia o la ley permite, los usuarios pueden hacer cambios en esa bifurcación para volver al proyecto principal o simplemente mantener como su propia variación de un proyecto. Cada una de estas copias es una "[bifurcación](/articles/github-glossary/#fork)" del repositorio original, que a su vez también se puede llamar la "matriz" de la bifurcación. - -GitHub no deshabilitará automáticamente las bifurcaciones cuando se deshabilite un repositorio matriz. Esto se debe a que las bifurcaciones pertenecen a diferentes usuarios y pueden haber sido alteradas de manera significativa. GitHub no lleva a cabo ninguna investigación independiente sobre las bifucaciones. Esperamos que quienes envíen solicitudes de eliminación de datos sensibles lleven a cabo esa investigación y, si consideran que las bifurcaciones también contienen datos sensibles, incluyan expresamente bifurcaciones en su solicitud. - -### Cómo enviar una solicitud de eliminación de datos sensibles - -Debido al tipo de contenido de los hosts de GitHub (principalmente de código de software) y a la forma en que se gestiona el contenido (con Git), necesitamos que las demandas sean lo más específicas posible. Para que podamos verificar que un usuario ha eliminado por completo los datos sensibles, necesitamos saber exactamente dónde buscar. - -Estas directrices están diseñadas para que el procesamiento de solicitudes para eliminar datos sensibles sean lo más sencillas posible. - -#### Tu solicitud debe incluir: - -1. Un enlace funcional y seleccionable a cada archivo que contiene datos sensibles. (Ten en cuenta que no podemos trabajar a partir de resultados de búsqueda, ejemplos o capturas de pantalla.) -2. Números de línea específicos dentro de cada archivo que contenga los datos sensibles. -3. Una breve descripción de cómo cada elemento identificado supone un riesgo de seguridad para ti o tu organización. ***Es importante que proporciones una explicación de cómo plantean los datos un riesgo de seguridad más allá de simplemente indicar que lo hace.*** -4. Si eres un tercero actuando como agente de una organización que se enfrenta a un riesgo de seguridad, incluye una declaración de que tienes un derecho legal a actuar en nombre de dicha organización. -5. OPCIONAL: Haznos saber si tu solicitud es especialmente urgente y por qué. Respondemos a todas las solicitudes de eliminación de datos sensibles lo antes posible. Sin embargo, si esta solicitud es especialmente sensible al tiempo, como una exposición de credenciales muy reciente, por favor explica por qué. - -### Como presentar tu solicitud - -Puedes enviar tu solicitud para eliminar datos confidenciales a través de nuestro [formulario de contacto](https://support.github.com/contact). Por favor, incluye una versión de texto plano de tu solicitud en el cuerpo de tu mensaje. El envío de tu solicitud en un archivo adjunto puede resultar en retrasos en el proceso. - -### Disputas - -Si recibiste una solicitud de eliminación de datos confidencial por nuestra parte puedes discutirlo respondiendo a nuestro correo electrónico y haciéndonos saber —con el mayor detalle posible— por qué consideras que el contenido en cuestión no es información sensible sujeta a esta Política. diff --git a/translations/es-XL/content/github/site-policy/github-sponsors-additional-terms.md b/translations/es-XL/content/github/site-policy/github-sponsors-additional-terms.md deleted file mode 100644 index 5b53982ec3..0000000000 --- a/translations/es-XL/content/github/site-policy/github-sponsors-additional-terms.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -title: Términos adicionales de los Patrocinadores de GitHub -redirect_from: - - /articles/github-sponsors-additional-terms -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Tu participación en el Programa de Patrocinadores de GitHub (el "Programa") está sujeta a las [Condiciones de Servicio de GitHub](/github/site-policy/github-terms-of-service) (el "Acuerdo") así como a las siguientes condiciones adicionales ("Condiciones Adicionales"). Cualquier uso del Programa de Patrocinadores de GitHub que viole el Acuerdo también constituirá una violación de estos Términos Adicionales. Todos los términos en mayúscula que se utilizan, pero no se definen a continuación, tienen los significados que se les asignan en el Acuerdo. Estos Términos Adicionales para el Programa de Patrocinadores de GitHub describen la relación entre GitHub y tú, el "Programador Patrocinado", para el Programa. Los Términos adicionales entran en vigor a partir de la fecha en que los aceptas ("Fecha de entrada en vigor"). - -### 1. Definiciones. - -Las "**Políticas de GitHub" **se refieren a todas las políticas y procedimientos ahora actuales de GitHub que el Desarrollador Patrocinado debe seguir de acuerdo con lo que se indica en el programa, incluyendo los [Lineamientos de la Comunidad de GitHub](/github/site-policy/github-community-guidelines). - -"**Patrocinador**" se refiere al Usuario que te compró una Suscripción o te pagó un Patrocinio a través de tu Cuenta de programador patrocinado. - -"**Cuenta de programador patrocinado**" se refiere a la cuenta que estableces a través del Programa para recibir el pago de los Patrocinadores. - -"**Contenido del programador patrocinado**" se refiere a todo el contenido que le envías a GitHub en relación con el Programa, incluido el Contenido generado por el usuario y Tu contenido, tus marcas, marcas registradas, marcas de servicio, nombres comerciales, logos o indicaciones de origen ("**Marcas del programador patrocinado**"), y los datos relacionados con tu Cuenta de programador patrocinado. - -"**Patrocinio**" se refiere a un pago que se te efectúa a través del Programa y el Servicio. - -"**Suscripción**" se refiere a un Patrocinio mensual periódico a cambio de bienes, servicios u otras ofertas que les proporcionas a los Patrocinadores. - -"**Pago del Desarrollador Patrocinado**" significa el valor neto del cien por ciento (100%) de los pagos brutos mensuales de GitHub que se reciben a modo de Patrocinios y Suscripciones a Cuentas de Desarrollador Patrocinado, mas cualquier Fondo Compensatorio aplicable, y otros montos de opciones de monetización que el Desarrollador Patrocinado elija utilizar, según sea aplicable, menos cualquier descuento, impuestos, cuotas, cantidades que GitHub no recolecte o que se reembolsen o cobren de vuelta, y cantidades debidas a cualquier tercero en conexión con el Programa con respecto a la Cuenta del Desarrollador Patrocinado, y otras Exclusiones según se detalla en la Sección 4. - -"**USD**" means United States Dollar. - -### 2. Uso aceptable. - -#### 2.1. Programa de Patrocinios de GitHub - -Para poder participar en el programa, debes cumplir con las leyes de mayoría de edad de tu país (por ejemplo, debes tener por lo menos 13 años de edad si vives en los Estados Unidos), tener una cuenta de GitHub válida y haber aceptado la [Sección de Uso Aceptable](/github/site-policy/github-terms-of-service#c-acceptable-use) en el acuerdo y en las Políticas de GitHub Aplicables, así como estas Condiciones Adicionales de los Patrocinadores de GitHub. - -Si tienes más de 13 años pero menos de 18, puedes otorgar y recibir fondos de Patrocinio, tomando en cuenta que Stripe, nuestro procesador de pagos, pueda recolectar información de verificación de tu tutor legal. - -Bajo ninguna circunstancia recibirás pagos o recabarás fondos que involucren: - -* fraude, rescate, violaciones de la propiedad intelectual u otros fines ilícitos; - -* tergiversación o engaño relacionado con los motivos por los cuales estás recaudando fondos o solicitando patrocinio; - -* la compra o venta de ICO, tokens de la utilidad u otros tipos de criptomoneda; - -* la compra o venta de valores, acciones u otros tipos de ofertas de inversión; - -* la venta de información personal o el procesamiento de información personal que viole cualquier legislación; - -* loterías, rifas, juegos de azar, esquemas piramidales, autonegociación, "esquemas hazte rico rápido", esquemas de marketing engañosos, esquemas de "donación por donación" o cualquier intento de jugar con los sistemas o servicios de GitHub o de terceros; y, - -* actividades con países, regiones, gobiernos, personas o entidades que no estén permitidas conforme a las sanciones impuestas por los EE. UU. y demás sanciones económicas que imponga la ley correspondiente, o actividades dentro de ellos o que los involucren. and other economic sanctions under applicable law. - -#### 2.2. Fondo Compensatorio para Patrocinios de GitHub -El Fondo Compensatorio para Patrocinios de GitHub pretende alentar a la comunidad que participa en el ecosistema de Software de Código Abierto (OSS, por sus siglas en inglés) para contribuir con fondos sostenibles para los individuos elegibles con Cuentas de Desarrollador Patrocinado. Todos los individuos que apliquen al Programa antes del 1 de enero de 2020 se revisarán para elegibilidad para el fondo Compensatorio, pero no todas las Cuentas de Desarrollador Patrocinado elegibles se escogerán. Las organizaciones no pueden participar en el Fondo Compensatorio para Patrocinios de GitHub, y no se escogerán las Cuentas de Desarrollador Patrocinadas elegibles que ya se encuentren patrocinadas por una organización. Encuentra las reglas adicionales a continuación. - -##### 2.2.1. Condiciones para el Fondo Compensatorio. -La elegibilidad para el Fondo Compensatorio para Patrocinios de GitHub se evalúa caso por caso y está sujeto a las siguientes limitaciones: - -* Debes tener una cuenta de GitHub, ser aceptado en el programa como un individuo, y contribuir activamente al OSS. Por favor nota que GitHub no permite operar más de una cuenta de usuario gratuita. De esta manera, la elegibilidad está disponible de manera individual y no se aprobará en cuentas múltiples de la misma persona. - -* Tu uso de GitHub y de tu Cuenta de Desarrollador Patrocinada debe ser, según nuestra determinación y exclusivo criterio, consistente con la misión de Patrocinios de GitHub para expandir las oportunidades para contribuir con el código abierto que se describe en los [Lineamientos de Comunidad de GitHub](/github/site-policy/github-community-guidelines). - -* No se te podrá elegir para ningún patrocinio que se origine de una cuenta de usuario u organización con un perfil de Patrocinios de GitHub publicado. - -* GitHub se reserva el derecho de mantener o rescindir el dinero del Fondo Compensatorio y de bloquear a cualquier usuario de su participación en el Fondo de Compensación para Patrocinios de GitHub, incluyendo, mas no limitándose a publicar el contenido o proyectos que GitHub determine como ofensivos u objetables de cualquier otra manera. - -##### 2.2.2. Periodo de Elección. -El periodo de elección comienza después de que GitHub acepta una Cuenta de Desarrollador Patrocinado individual en sus Patrocinios y publica el perfil de patrocinio para la cuenta. Para cada Cuenta de Desarrollador Patrocinada elegible para el Fondo Compensatorio para Patrocinios de GitHub, GitHub podrá elegir un patrocinio comunitario de hasta $5,000 dólares estadounidenses totales durante los primeros 12 meses en que la Cuenta de Desarrollador Patrocinada esté en el Programa. El periodo de consideraciones no puede extenderse por razón alguna. Durante el periodo deelección, GitHub no cobrará cuota alguna, así que el desarrollador patrocinado recibirá el 100% del patrocinio. Posteriormente, podríamos cobrar una cuota nominal por procesamiento. - -* Si el Patrocinio o la Suscripción Patrocinadora cesa por cualquier motivo, la elección asociada también cesará. No podrán elegirse aquellos fondos que se reembolsen al Patrocinador antes de la fecha de pago al Desarrollador Patrocinado. - -* Si sales de los Patrocinios de GitHub y te vuelves a unir posteriormente, el tiempo transcurrido entre tus periodos de participación podrá contarse en el periodo de elección, o éste podría caducar. - - -* Si GitHub descubre cualquier violación potencial, antes de que se otorgue el pago de cualquier fondo compensatorio durante el periodo de elección, GitHub podrá inhabilitar los pagos hasta que se haya completado una investigación, y los fondos compensatorios que se hayan otorgado al desarrollador patrocinado podrán revocarse si se encuentra que éstos constituyen una violación de la presente política. - -* {% data reusables.sponsors.github-contact-applicants %} - -### 3. Obligaciones del programador patrocinado. - -#### 3.1. General. -Tú: (A) crearás una Cuenta de programador patrocinado; (B) pondrás a disposición el Contenido del programador patrocinado a través del Programa y el Servicio, y (C) cumplirás con todas las políticas de GitHub. Serás el único responsable de la asistencia, el desarrollo y el mantenimiento de tu Cuenta de programador patrocinado y del Contenido del programador patrocinado, y de cualquier queja acerca de ellos. - -#### 3.2. Registro. -Si decides postularte al Programa, la entrada al Programa está supeditada a que completes el proceso de registro y a la aceptación en el Programa de parte de GitHub. Asimismo, puede que debas registrarte con el (los) proveedor(es) de servicio de pago seleccionado(s) por GitHub (como Stripe) para acceder y usar determinadas funciones del Programa. Te debes registrar con tu verdadera identidad y aceptar proporcionar y mantener tu información verdadera, precisa, actual y completa, tal como la solicita el formulario de registro del Programa. Los datos de registro y otra información determinada sobre ti se rigen por nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement) y por cualquier declaración de privacidad proporcionada por nuestro procesador de pagos. GitHub se reserva el derecho a rechazar la aceptación al Programa. - -#### 3.3. Monetización del contenido. -A través del Programa y el Servicio, GitHub puede proporcionarte varias opciones para monetizar tu Contenido del programador patrocinado. Algunas opciones pueden requerir que actualices determinadas configuraciones de tu Cuenta del programador patrocinado. Asimismo, pueden variar las maneras en que el Programa admite cada opción de monetización. Si utilizas una (o más) de estas opciones cambiando las configuraciones correspondientes, entonces, aceptas los términos que corresponden a esa opción. Algunas opciones de monetización pueden requerir que le proporciones más información a GitHub o a sus proveedores de servicio, o que aceptes otros términos de GitHub o términos de terceros. - -##### 3.3.1. Suscripciones. -El Programa te proporciona la capacidad de ofrecer Suscripciones. Si decides ofrecer Suscripciones, GitHub te pagará el Patrocinio de la suscripción, tal como se describe en la Sección 4. Eres responsable de determinar la naturaleza, contenido y capacidades de tu oferta de Suscrpciones, sujeta a estas Condiciones Adicionales y Políticas de GitHub aplicables. - -##### 3.3.2. Otros Patrocinios. -El Programa o Servicio podría proporcionarte la capacidad de aceptar una donación u otra clase de Patrocinio directo de otro Usuario sin una oferta de Suscripción. Sin embargo, ya que GitHub no lleva a cabo estos tipos de Patrocinio, deberás establecer una cuenta comercial con un servicio de pagos de terceros (tal como Stripe) y estar sujeto a los términos, condiciones y políticas de privacidad de la cuenta comercial de dicho proveedor. Cualquier cantidad que se te otorgue, sea o no una donación, se pagará directamente a tu cuenta comercial y no incluirá ningún Pago de Desarrollador Patrocinado. Aceptas que no le harás ningún reclamo ni le pedirás ninguna compensación a GitHub vinculado con las donaciones, y cualquier disputa relacionada con una donación será únicamente entre tú y el proveedor de servicios de pago externo. Eres responsable de dar cumplimiento a cualquier acuerdo, política y leyes o regulaciones aplicables del tercero proveedor de servicios. Para tu comodidad, GitHub puede decidir proporcionarte información o brindarte un informe sobre el monto de las donaciones que recibiste. - -##### 3.3.3. Publicidad. -Si bien entendemos que podrías querer promover a tus Patrocinadores publicando sus nombres o logos en tu cuenta, el enfoque principal de tu Contenido de Desarrolador Patrocinado no deberá ser la publicidad o el marketing promocional. Adicionalmente, no deberás celebrar ningún contrato de publicidad para promover cualquier producto o marca, ya que esto estaría prohibido por el [Acuerdo](/github/site-policy/github-terms-of-service) o por los Lineamientos de la Comunidad de GitHub. Si decides hospedar cualquier material promocional o publicitario en tu Contenido de Desarrollador Patrocinado, serás el único responsable de cumplir con todas las regulaciones y leyes aplicables, incluyendo los Lineamientos de la Comisión Federal de Comercio sobre Testimonios y Apoyos. Federal Trade Commission's Guidelines on Endorsements and Testimonials. - -### 4. Términos financieros. - -#### 4.1. Payment. -GitHub will pay you the Sponsored Developer Payment in accordance with this Section 4, so long as you meet the Sponsored Developer Obligations in Section 3 and are not in violation of these Additional Terms. Si algún mes no cumples con estas obligaciones, a nuestra absoluta discreción, podemos retener el Pago del programador patrocinado correspondiente a ese mes. Si no cumples o mantienes las Obligaciones del programador patrocinado durante dos (2) meses o más del Plazo (consecutivos o no consecutivos), GitHub puede cancelar estos Términos adicionales, tal como se describe en la Sección 6. - -#### 4.2. Exclusiones de Pago para el Desarrollador Patrocinado. -Los siguientes montos no están incluidos en los Pagos del programador patrocinado, o GitHub los puede retener, según corresponda. - -##### 4.2.1. Gastos del Desarrollador Patrocinado. -Deberás absorber todos los gastos que generes en relación con tu rendimiento bajo estas Condiciones Adicionales. No te reembolsaremos ni adelantaremos ningún gasto. - -##### 4.2.2. Impuestos. -GitHub pretende cumplir con todas las leyes de reporte de información y retención de impuestos que GitHub determine, razonablemente en su juicio, como aplicables a estos pagos. Si se deben retener impuestos sobre cualquier monto que te pagará GitHub o sobre los montos sujetos a la presentación de información impositiva conforme a las leyes correspondientes, GitHub deducirá tales impuestos del monto adeudado y se los pagará a la autoridad fiscal adecuada. Cuando sea necesario, obtendrá y te hará llegar un recibo oficial por cualquier impuesto retenido, según lo exijan las leyes correspondientes. GitHub hará los esfuerzos razonables para minimizar tales impuestos en la medida que la ley correspondiente lo permita, y cada parte cooperará de manera razonable con la otra parte para lograr las mínimas tasas impositivas o la eliminación de tales impuestos en virtud de las leyes o tratados de impuesto a las ganancias correspondientes. Esto incluye que le proporciones a GitHub la información adecuada requerida conforme a las leyes correspondientes, como los Formularios IRS W-8, W-9 u otra información para establecer exenciones a la retención. También serás responsable de cumplir con todos los términos y condiciones del procesador de pagos externo al respecto de la retención de impuestos y la presentación de informes, si corresponde. Asimismo, GitHub se reserva el derecho a suspender los pagos a tu cuenta hasta que le proporciones a GitHub la documentación o información adecuada requerida conforme a las leyes correspondientes para que GitHub determine cualquier retención de impuestos u obligaciones de presentación de informes que se apliquen a los pagos, de acuerdo con los presentes Términos adicionales o con el Acuerdo. - -##### 4.2.3. Retención de Pagos del Desarrollador Patrocinado por Incumplimiento. -En caso de que un Desarrollador Patrocinado incumpla, o se sospeche que incumpla, el Acuerdo o estas Condiciones Adicionales, GitHub se reserva el derecho de retener los pagos al Desarrollador patrocinado bajo estas Condiciones adicionales o, de otra manera, que estén pendientes de una investigación razonable por parte de GitHub. Si GitHub determina, a su absoluto criterio, que un Desarrollador Patrocinado se encuentra en incumplimiento del Acuerdo o de Estas Condiciones Adicionales, GitHub retendrá permanentemente cualquier cantidad debida al Desarrollador Patrocinado. - -#### 4.3. Plazos de Pago. -Durante el plazo, GitHub te emitirá todos los Pagos de Desarrollador patrocinados recibidos en cualquier mes dentro de 30 días después del cierre de dicho mes, sujeto a las variaciones descritas posteriormente. Los pagos se envían a través de Stripe Connect, transferencia ACH, o transferencia bancaria, a la cuenta bancaria que proporcionaste cuando aplicaste para los Patrocinios de Github. No somos responsables de la demora o la aplicación incorrecta de ningún pago del Programador patrocinado que se deba a que tú o tu banco hayan suministrado información incorrecta o incompleta, o a la falla del banco en la acreditación del pago a tu cuenta. - -- Para Cuentas de Desarrollador Patrocinadas recién creadas, GitHub te emitirá todos los Pagos de Desarrollador Patrocinado que se reciban en cualquier mes dentro de 90 días de la creación de tu Cuenta de Desarrollador Patrocinado, sujeto a las variaciones descritas posteriormente. Los pagos posteriores se emitirán en 30 días desde el cierre de mes, de acuerdo con esta sección. - -- Si se te paga mediante Stripe Connect, recibirás pagos en el día 22 de cada mes de acuerdo con tu balance al final del mes previo, sin importar la cantidad en el balance. - -- Si se te paga por transferencia ACH o transferencia bancaria, recibiras pagos en el tercer jueves del mes. GitHub te emitirá un pago por cada mes en el que tu balance llegue a $100 USD. Las contribuciones del Fondo de Compensación para Patrocinios de GitHub no no cuenta en este umbral. Si tu saldo está por debajo de los $100 al finalizar el mes, el saldo se acumulará hasta la próxima vez que tu saldo esté por encima del límite al finalizar el mes. Si sales de los Patrocinios de GitHub, GitHub emitirá un pago por el restante de tu balance, aún si éste es menor a $100. - -- Después de la terminación, te emitiremos todos los Pagos de Desarrollador Patrocinado, tanto recibidos como no pagados, en aproximadamente 90 días después del fin del mes calendario en el cual ubiquemos que estas Condiciones Adicionales han finalizado. - -#### 4.4. Método de Pago. -Remitiremos los pagos del Programador patrocinado por ACH/SEPA o los giraremos a la cuenta que especifiques, sujeto a los límites, los métodos y los plazos establecidos en nuestras políticas de pago vigentes al momento, que actualizaremos cada cierto tiempo. El método y límite de pago puede variar en función del país y de la información de cuenta que proporciones. Podemos, a nuestro absoluto criterio, combinar el Pago del programador patrocinado con cualquier otro pago que se te pueda deber. - -#### 4.5. Moneda. -Todas las referencias a la moneda son en dólares estadounidenses. Si te encuentras fuera de los Estados Unidos, puede que convirtamos los dólares estadounidenses a la moneda local de tu dirección de pago, utilizando nuestras tasas de conversión vigentes al momento. - -#### 4.6. Requisitos de reembolso. -Serás responsable de especificar los términos y condiciones sobre cualquier reembolso a tus patrocinadores, si hubiera alguno. En ningún caso GitHub será responsable de proporcionar ayuda alguna con los reembolsos, ni será GitHub será responsable del pago de ningún reembolso. - -#### 4.7. Información de pago solicitada. -Para pagarte, nos debes proporcionar la información financiera, impositiva y bancaria completa y precisa que solicitemos (por ejemplo, a través de la creación o configuración de cuenta, o de cualquier otra manera). Te notificaremos por cualquier medio de comunicación acerca de los cambios en el tipo de información que se requiere. Si no cumples en proporcionar de manera adecuada (o en mantener de manera adecuada) tal información, (a) podemos deducir de tu Pago de programador patrocinado cualquier tarifa bancaria relacionada, y (b) podemos poner fin a los presentes Términos adicionales, y puede que pierdas cualquier monto que te adeude GitHub. - -### 5. Declaraciones y garantías, limitación de responsabilidad, resarcimiento. - -#### 5.1. Por el Programador patrocinado. -El programador patrocinado declara y garantiza que: - -* tú tienes la autoridad para celebrar los presentes Términos adicionales y para realizarlos plenamente; - -* la ejecución y realización de los presentes Términos adicionales no violará ningún otro acuerdo u obligación entre tú y cualquier otra parte; - -* el contenido del Programador patrocinado no infringe, viola o malversa ningún derecho de terceros, incluido cualquier derecho de autor, marca comercial, patente, secreto comercial, derecho moral, derecho a la privacidad, derecho de publicidad o cualquier otra propiedad intelectual; - -* cumplirás con todas las leyes y regulaciones, y tu Contenido del programador patrocinado no es ilegal y no viola ninguna ley o regulación. - -#### 5.2. Descargo de garantías, limitación de responsabilidad, resarcimiento. -ACEPTAS DE MANERA EXPLÍCITA QUE LAS SECCIONES O (DESCARGO DE GARANTÍAS), P (LIMITACIÓN DE RESPONSABILIDAD) Y Q (EXENCIÓN Y RESARCIMIENTO) DEL ACUERDO SE APLICAN A LOS PRESENTES TÉRMINOS ADICIONALES. - -### 6. Plazo y terminación. - -#### 6.3. Terminación. -Los presentes Términos adicionales comienzan en la fecha de entrada en vigor y seguirán rigiendo siempre que participes del Programa. - -#### 6.2. Suspensión. -GitHub puede suspender tu Cuenta de programador patrocinado de inmediato si violas de cualquier manera los presentes Términos adicionales o el Acuerdo, o si eres colocado o ubicado en una lista comercial restringida, o si eres residente habitual de un país o territorio sujeto a las sanciones generales que administra la Oficina de Control de Activos Extranjeros (OFAC, por sus siglas en inglés) de los EE. UU. Office of Foreign Assets Control (OFAC). No poder corregir o solucionar el motivo de la suspensión puede dar lugar a la terminación de tu Cuenta de programador patrocinado. - -#### 6.4. Terminación. -Cualquiera de las partes podrá rescindir estos Términos Adicionales y tu Cuenta de Desarrollador Patrocinado en cualquier momento con o sin causa, con o sin previo aviso. Si incumples los presentes Términos adicionales o el Acuerdo, podemos ofrecerte un período para solucionar el incumplimiento, aunque no estamos obligados a hacerlo. - -#### 6. Plazo y terminación. -Si cualquiera de las Partes decide ponerles fin conforme a la Sección 6.3, la única obligación de GitHub será pagarle al Programador patrocinado el monto del Pago del programador patrocinado acumulado hasta la fecha de terminación, a menos que dichos pagos estén prohibidos por ley. - -### 7. Varios. - -#### 7.1. Acuerdo completo. -Los presentes Términos adicionales, junto con el Acuerdo, las Políticas de GitHub, la Declaración de privacidad de GitHub y cualquier término adicional por opciones de monetización diferentes constituyen el acuerdo completo entre tú y GitHub. - -#### 7.2. Modificaciones a los términos. -Nos reservamos el derecho, a nuestro absoluto criterio, de modificar los presentes Términos adicionales en cualquier momento. Te notificaremos acerca de las modificaciones sustanciales de los presentes Términos adicionales, tales como los cambios de precio, al menos 30 días antes de que entren en vigor, por medio de la publicación de un aviso en nuestro sitio web. La continuación de tu participación en el Programa implica que acuerdas con nuestras revisiones de los presentes Términos adicionales. Puedes visualizar todas las modificaciones a estos Términos en nuestro repositorio [Site Policy](https://github.com/github/site-policy)-. - -#### 7.3. Beneficiarios externos. -Con excepción de lo indicado expresamente, no se considerará que ninguna persona, firma, grupo o corporación además de las partes haya adquirido ningún derecho en virtud de ningún contenido de los presentes Términos adicionales. - -#### 7.4. Contratistas independientes. -Las partes son contratistas independientes. Ninguna parte es empleadora, empleada, agente, socia o representante legal de la otra para ningún propósito, y ninguna tiene ningún derecho, poder o autoridad para generar ninguna obligación o responsabilidad en nombre de la otra. - -#### 7.5. Publicidad. -Podemos emitir un comunicado de prensa u otra comunicación pública relacionada con tu participación en el Programa. diff --git a/translations/es-XL/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md b/translations/es-XL/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md deleted file mode 100644 index e2f49a76ec..0000000000 --- a/translations/es-XL/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -title: Acuerdo de GitHub contra la esclavitud moderna y el trabajo infantil -redirect_from: - - /articles/github-statement-against-modern-slavery-and-child-labor -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -*Declaración 2018* - -Según la organización internacional del trabajo (OIT), [40 millones de personas fueron víctimas de la esclavitud moderna y 152 millones niños fueron sometidos a trabajo infantil](https://www.ilo.org/global/about-the-ilo/newsroom/news/WCMS_574717/lang--en/index.htm) globalmente en 2016. Como lo informa la OIT[](https://www.ilo.org/global/topics/forced-labour/lang--en/index.htm): - - 1 de cada 4 víctimas de esclavitud moderna son niños. - - De los 24.9 millones de personas atrapadas en el trabajo forzoso, se explotan 16 millones personas en el sector privado, como el trabajo doméstico, la construcción o la agricultura; 4.8 millones de personas en la explotación sexual forzada y 4 millones de personas en el trabajo forzoso impuestas por las autoridades del estado. - - Las mujeres y las niñas se ven afectadas de manera desproporcionada por el trabajo forzoso, que representa el 99% de las víctimas en la industria sexual comercial y el 58% en otros sectores. - -GitHub deplora la presencia y la persistencia de la esclavitud moderna y el trabajo infantil y toma en serio su responsabilidad de asegurar que ni la esclavitud moderna ni el trabajo infantil se lleven a cabo en su cadena de suministro o en cualquier parte de su negocio. ("Esclavitud moderna" en esta declaración se refiere a la esclavitud, el trabajo forzoso u obligatorio, el tráfico, la servidumbre y los trabajadores que están encarcelados, identificados o Unidos. "Trabajo infantil" se refiere al trabajo realizado por alguien menor de 16 años de edad o menor de 14 años para trabajo liviano, considerando que no se limite a los periodos que interfieaen con la educación del niño y no en condiciones que interfieran con la salud o el bienestar del niño.) - -De acuerdo con la [Ley de Esclavitud Moderna del Reino Unido](https://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted), y en cumplimiento con el [ILO 2014 Protocolo para la Convención de Trabajo Forzado](https://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029)", la [ILO Declaración de Principios Fundamentales y Derechos en el Trabajo](https://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm), y la [meta 8.7 de las Metas de Desarrollo Sostenible de las Naciones Unidas](https://sustainabledevelopment.un.org/sdg8), esta Declaración de 2018 Contra la Esclavitud Moderna y el Trabajo Infantil ("la Declaración") describe los pasos que ha tomado GitHub para prevenir que se suscite la esclavitud moderna y el trabajo infantil en su negocio o cadena de suministro. - -### La estructura, empresas y las cadenas de suministro de GitHub - -GitHub es una plataforma de desarrollo de software con su sede en San Francisco y empleados y contratistas que trabajan en numerosos países. - -Todos los empleados de GitHub y los contratistas independientes individuales son voluntarios y están a la misma disposición. GitHub tiene una mano de obra distribuida en gran medida y se esfuerza por brindar compensaciones y beneficios competitivos a sus empleados y contratistas, independientemente de su ubicación. Esto es cierto ya sea que contratemos contratistas independientes directamente o a través de un intermediario. - -GitHub no conduce la manufactura o produce hardware, ni GitHub utiliza agencias de reclutamiento para los tipos de servicios a menudo realizados por los trabajadores migrantes. La naturaleza del negocio de GitHub no la somete a cambios repentinos en las presiones de carga de trabajo o de precios, que a menudo impulsan la demanda de prácticas que aumentan el riesgo de trabajo forzoso en las cadenas de suministro, como las horas extras forzadas. - -GitHub ofrece software gratuito y de pago y software basado en la web como un servicio para los clientes en todo el mundo. Los productos de GitHub incluyen: - - GitHub.com: Colaboración basada en la web y plataforma de hospedaje de código - - GitHub Enterprise: Colaboración local y software de alojamiento de código - - Atom: Editor de texto - - Electron: Marco para escribir aplicaciones multiplataforma de escritorio - - Escritorio de GitHub: Aplicación de escritorio para acceder a GitHub.com y GitHub Enterprise - -La cadena de suministro de GitHub está formada por bienes y servicios para nuestros productos y operaciones que incluyen servicios de computación, planificación de eventos, compra de artículos comerciales y promocionales, suministros de oficina y arrendamiento de instalaciones, como espacios de oficinas y centros de datos. - -### Políticas en relación con la esclavitud moderna y el trabajo infantil - -#### Esclavitud moderna y trabajo infantil - -**El código de ética de GitHub** prohíbe usar, participar, apoyar o tolerar de manera consciente la esclavitud moderna (esclavitud, trabajo forzoso u obligatorio, tráfico, servidumbre o trabajadores que están encarcelados, matriculados o adheridos) o trabajo infantil en sus operaciones comerciales. Cualquier empleado o contratista de GitHub que viole esta prohibición estará sujeto a la terminación de la relación laboral o comercial. - -**Los estándares de conducta de GitHub** prohíben conductas inseguras e ilegales, que incluyen el uso a sabiendas, la participación, el apoyo o la tolerancia de la esclavitud moderna (esclavitud, trabajo forzoso u obligatorio, tráfico, servidumbre o trabajadores que están encarcelados, identificados o vinculados) o trabajo infantil. - -GitHub cumple con las leyes que prohíben la trata y el trabajo infantil en las jurisdicciones en las que opera, incluyendo la [Regulación de adquisición federal de EE. UU. 22.17 sobre la lucha contra la trata de personas](https://www.govinfo.gov/content/pkg/CFR-2009-title48-vol1/pdf/CFR-2009-title48-vol1-part22-subpart22-17.pdf). - -Además, GitHub estableció una asociación con el programa FairHotel, lo que significa que GitHub alienta a sus empleados a elegir Hoteles aprobados por FairHotel, donde los trabajadores tienen salarios justos, beneficios adecuados y una voz en el trabajo. Ser un socio de FairHotel también significa que GitHub brinda negocios a los hoteles como un empleador justo. - -En el futuro, GitHub comunicará esta declaración a todos los empleados, contratistas y proveedores, incluyendo reclutadores y agencias de empleo. Además, GitHub está desarrollando capacitación para todos los empleados de GitHub sobre esclavitud moderna y trabajo infantil. Github [publica su declaración frente a la esclavitud moderna y el trabajo infantil públicamente.](/articles/github-statement-against-modern-slavery-and-child-labor) - -GitHub tiene una política de no represalias para informar las inquietudes relacionadas con el lugar de trabajo. De acuerdo con esta afirmación, GitHub les permite a los empleados y contratistas informar las propuestas relacionadas con la esclavitud moderna y el trabajo infantil sin temor a represalias. - -### Legislaciones y prácticas laborales - -Las prácticas laborales de GitHub son - -**justas**: - - GitHub paga a sus empleados y contratistas un salario justo, de acuerdo con los salarios legales aplicables - - GitHub mantiene condiciones de trabajo humanas - - GitHub no requiere que los trabajadores excedan las horas máximas de trabajo diario establecidas por las leyes o regulaciones locales y nacionales - - GitHub paga a sus empleados y contratistas de manera oportuna, con documentación (como un talón de pago) que indica la base sobre la que se les paga y mantiene los registros de los empleados de acuerdo con las leyes locales y nacionales - -**humanas y éticas**: - - GitHub usa solo mano de obra voluntaria - - GitHub prohíbe el trabajo infantil - - GitHub no participa en disciplina física o abuso - - GitHub no tolera acoso o discriminación ilegal en la fuerza laboral o en el lugar de trabajo - -**respetuosas**: - - GitHub protege los derechos de sus empleados a la libertad de asociación y la negociación colectiva de acuerdo con los requisitos legales, incluyendo el de publicar avisos legales de los derechos de los empleados conforme a la ley nacional de relaciones laborales - - GitHub brinda beneficios a los empleados en exceso o por encima de los niveles esperados en la industria - - GitHub invita a los empleados a informar cualquier queja en el lugar de trabajo y no tolera represalias por informar - -### Procesos de diligencia debida en relación con la esclavitud moderna y el trabajo infantil en sus cadenas comerciales y de suministro - -GitHub evalúa su cadena de negocio y de suministro para los riesgos relacionados con la esclavitud moderna y el trabajo infantil. Aprovechando la experiencia interna y externa en materia de derechos humanos, GitHub participó en un análisis de funcionalidad cruzada (que incluye políticas, asesoría legal, adquisiciones, finanzas y operaciones, especialmente recursos humanos) para determinar dónde existen los servicios laborales en su cadena de negocios y de suministro y para identificar los riesgos potenciales relacionados con la esclavitud moderna y el trabajo infantil. GitHub prioriza las áreas en las que esos riesgos pueden ser más significativos en términos de gravedad, escala o probabilidad para una mayor diligencia debida, monitoreo y verificación. GitHub continúa considerando dónde pueden ocurrir riesgos y cómo abordarlos. Además, GitHub ahora obtiene la certeza de sus proveedores de que tienen prácticas consistentes con esta declaración, incluso al cumplir con las leyes relacionadas con la esclavitud moderna o el trabajo infantil. - -### Lugares en las cadenas de negocios y suministros de GitHub donde hay un riesgo de esclavitud moderna y trabajo infantil y los pasos que GitHub ha tomado para evaluar y administrar dicho riesgo - -GitHub no identificó a ningún proveedor de alto riesgo; sin embargo, la esclavitud moderna o el trabajo infantil sería más probable que ocurra con los proveedores de servicios que implican mano de obra manual, como el apoyo a eventos, construcción, servicios de instalaciones y servicios de alimentos. GitHub auditará a sus proveedores existentes y requerirá que aquellos en esas áreas de mayor riesgo confirmen que brindan servicios consistentes con esta declaración. - -A pesar de que GitHub no sabe de ninguna esclavitud moderna o alegada moderna o trabajo infantil en su cadena de negocios o de suministro y no tiene una base creíble para creer que está ocurriendo, GitHub se compromete a proveer remedios si GitHub en sí misma causara la esclavitud moderna o el trabajo infantil y la remediación de patrones más amplios de no conformidad con esta declaración causada por deficiencias en los sistemas o procesos. La remediación de GitHub a las víctimas individuales incluiría protocolos de acción inmediata adecuada para eliminar las prácticas modernas de esclavitud y trabajo infantil, junto con recursos para servicios razonables y apropiados de víctimas diseñados para compensar el daño experimentado. - -### Efectividad para asegurar que no se esté produciendo la esclavitud moderna ni el trabajo infantil en las cadenas comerciales o de suministro de GitHub - -GitHub cumple y seguirá cumpliendo con las leyes relacionadas con la esclavitud moderna y el trabajo infantil. - -En el futuro, GitHub ahora requiere que sus proveedores cumplan con esta declaración, así como con las leyes relacionadas con la esclavitud moderna y el trabajo infantil. GitHub ahora también requiere que sus proveedores: - - no usen, participen, apoyen o toleren la esclavitud moderna o el trabajo infantil - - no utilicen prácticas engañosas o fraudulentas de reclutamiento o compromiso para empleados o trabajadores contratados - - no cobren a los empleados o a los trabajadores contratados cuotas de compromiso - - no destryan, oculten, confisquen o nieguen el acceso de un empleado o de cualquier trabajador contratante al pasaporte, la licencia de conducir u otros documentos de identidad; - - nos permitan terminar nuestros acuerdos con ellos por cualquier violación de sus obligaciones relacionadas con la esclavitud moderna o el trabajo infantil; y - - remedien cualquier daño causado a cualquier trabajador que se encuentre sometido a cualquier forma de esclavitud moderna o trabajo infantil, si así lo solicita la ley. - -Además, GitHub recomienda firmemente a sus proveedores que: - - lleven a cabo procesos antimodernos de esclavitud y diligencia debida del trabajo infantil, incluyendo evaluaciones de riesgo, para sus proveedores; - - tomen medidas para abordar riesgos identificados; y - - utilicen una esclavitud antimoderna similar y un lenguaje de trabajo infantil con sus proveedores. - -Las instrucciones de contratación de GitHub a los empleados que realizan compras de la empresa ahora incluyen una referencia al requisito de que los proveedores cumplan con el código de conducta del proveedor de Microsoft o esta declaración. - -### Capacitación para el personal de GitHub sobre la esclavitud moderna y la trata de personas - -GitHub está desarrollando la esclavitud moderna y la capacitación de trabajo infantil que será obligatoria para todos los empleados, con vistas a los negocios y la cadena de suministro de GitHub. GitHub hará hincapié en los proveedores que prestan servicios relacionados con el trabajo manual, como el apoyo a eventos, la construcción, los servicios de instalaciones y los servicios de alimentos, como áreas de mayor riesgo potencial. - -**El Consejo de administración de GitHub aprobó [esta declaración](/assets/images/help/site-policy/github-statement-against-modern-slavery-and-child-labor.pdf).** diff --git a/translations/es-XL/content/github/site-policy/github-subprocessors-and-cookies.md b/translations/es-XL/content/github/site-policy/github-subprocessors-and-cookies.md deleted file mode 100644 index be30abc70a..0000000000 --- a/translations/es-XL/content/github/site-policy/github-subprocessors-and-cookies.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -title: Subprocesadores y cookies de GitHub -redirect_from: - - /subprocessors/ - - /github-subprocessors/ - - /github-tracking/ - - /github-cookies/ - - /articles/github-subprocessors-and-cookies -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Fecha de entrada en vigencia: **12 de agosto de 2020** - -GitHub ofrece una gran cantidad de transparencia en cuanto a cómo usamos tus datos, cómo recopilamos tus datos y con quién los compartimos. Con ese fin proporcionamos esta página, la cual detalla [nuestros subprocesadores](#github-subprocessors), cómo usamos las [cookies](#cookies-on-github) y dónde y cómo realizamos cualquier [rastreo en GitHub](#tracking-on-github). - -### Subprocesadores de GitHub - -Cuando compartimos tu información con subprocesadores de terceros, como nuestros vendedores y proveedores de servicios, seguimos siendo responsables de ella. Trabajamos arduamente para mantener tu confianza cuando traemos nuevos proveedores y exigimos que todos los proveedores celebren acuerdos de protección de datos con nosotros que restrinjan su procesamiento de la información personal de los usuarios (tal como se define en la [Declaración de Privacidad](/articles/github-privacy-statement/)). - -| Nombre del subprocesador | Descripción del procesamiento | Ubicación del procesamiento | Ubicación Corporativa | -| ------------------------ | ----------------------------------------------------------- | --------------------------- | --------------------- | -| Automattic | Servicio de alojamiento | Estados Unidos | Estados Unidos | -| AWS Amazon | Alojamiento de datos | Estados Unidos | Estados Unidos | -| Braintree (PayPal) | Procesador de pagos de suscripción con tarjeta de crédito | Estados Unidos | Estados Unidos | -| Clearbit | Servicio de enriquecimiento de datos de marketing | Estados Unidos | Estados Unidos | -| Discourse | Proveedor de software del foro de la comunidad | Estados Unidos | Estados Unidos | -| DiscoverOrg | Servicio de enriquecimiento de datos de marketing | Estados Unidos | Estados Unidos | -| Eloqua | Automatización de campañas de marketing | Estados Unidos | Estados Unidos | -| Google Apps | Infraestructura interna de la empresa | Estados Unidos | Estados Unidos | -| Google Analytics | Análisis y rendimiento del sitio web | Estados Unidos | Estados Unidos | -| LinkedIn Navigator | Servicio de enriquecimiento de datos de marketing | Estados Unidos | Estados Unidos | -| Magic Robot | Informes de campaña (Adición del equipo de ventas) | Estados Unidos | Estados Unidos | -| MailChimp | Proveedor de servicios de correo de billetaje de clientes | Estados Unidos | Estados Unidos | -| Mailgun | Proveedor de servicios de correo transaccional | Estados Unidos | Estados Unidos | -| Microsoft | Servicios de Microsoft | Estados Unidos | Estados Unidos | -| Monday.com | Plataforma de colaboración en equipo y gestión de proyectos | Estados Unidos | Israel | -| Nexmo | Proveedor de notificaciones SMS | Estados Unidos | Estados Unidos | -| Oracle | Sistema financiero corporativo | Estados Unidos | Estados Unidos | -| Salesforce.com | Gestión de relaciones con clientes | Estados Unidos | Estados Unidos | -| Sendgrid | Proveedor de servicios de correo transaccional | Estados Unidos | Estados Unidos | -| Sentry.io | Proveedor de monitoreo de aplicaciones | Estados Unidos | Estados Unidos | -| Stripe | Proveedor de pagos | Estados Unidos | Estados Unidos | -| Twilio | Proveedor de notificaciones SMS | Estados Unidos | Estados Unidos | -| Zendesk | Sistema de tickets de soporte al cliente | Estados Unidos | Estados Unidos | -| Zuora | Sistema de facturación corporativa | Estados Unidos | Estados Unidos | - -Cuando traemos un nuevo subprocesador que maneja la información personal de nuestros usuarios o eliminas un subprocesador, o cambiamos la manera en que usamos un subprocesador, actualizaremos esta página. Si tienes preguntas o inquietudes acerca de un nuevo subprocesador, estaremos encantados de ayudarte. Ponte en contacto con nosotros vía{% data variables.contact.contact_privacy %}. - -### Cookies en GitHub - -GitHub utiliza cookies para hacer que las interacciones con nuestro servicio sean fáciles y significativas. Utilizamos cookies (y tecnologías similares, como HTML5 localStorage) para mantenerte conectado, recordar tus preferencias, proporcionar información para el futuro desarrollo de GitHub y para publicitar los productos y servicios de GitHub en sitios de terceros. - -Una cookie es un pequeño fragmento de texto que nuestro servidor Web almacena en tu computadora o dispositivo móvil, que tu navegador nos envía cuando regresas a nuestro sitio. Las cookies no necesariamente te identifican si simplemente estás visitando GitHub; sin embargo, una cookie puede almacenar un identificador único para cada usuario que inició sesión. Usamos cookies para mantenerte registrado, recordar tus preferencias y proporcionar información para el desarrollo futuro de GitHub. Por razones de seguridad, usamos cookies para identificar un dispositivo. Al usar nuestro sitio web, aceptas que podamos colocar este tipo de cookies en tu computadora o dispositivo. Si desactivas tu navegador o la capacidad de tu dispositivo para aceptar estas cookies, no podrás iniciar sesión ni utilizar los servicios de GitHub. En ciertas áreas del sitio web, también podríamos usar cookies para identificarte a ti y/o a tu dispositivo a fin de publicitar productos y servicios de GitHub en sitios de terceros. - -GitHub configura las siguientes cookies en nuestros usuarios por las siguientes razones: - -| Nombre de la cookie | Razón | -| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `user_session` | Esta cookie se utiliza para que inicies sesión. | -| `logged_in` | Esta cookie se utiliza para indicarnos que el usuario ya está registrado. | -| `dotcom_user` | Esta cookie se utiliza para indicarnos que el usuario ya está registrado. | -| `_gh_sess` | Esta cookie se usa para la aplicación temporal y el estado del marco entre las páginas copara indicar en qué paso está el usuario en un formulario de múltiples pasos. | -| `tz` | Esta cookie permite a tu navegador decirnos en qué zona horaria te encuentras. | -| `gist_user_session` | Esta cookie es usada por Gist cuando se ejecuta en un host por separado. | -| `saml_csrf_token` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para asociar un token con el cliente. | -| `saml_return_to` | Esta cookie se establece mediante el método de ruta de autenticación de SAML para mantener el estado durante el bucle de autenticación SAML. | -| `gist_oauth_csrf` | Esta cookie se establece por Gist para asegurar que el usuario que inició el flujo OAuth sea el mismo usuario que lo completa. | -| `__Host-user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite pueden verificar si una solicitud se origina desde GitHub. | -| `__Host-gist_user_session_same_site` | Esta cookie se configura para asegurar que los navegadores que soportan las cookies de SameSite pueden verificar si una solicitud se origina desde GitHub. | -| `_ga` | Esta cookie es utilizada por Google Analytics. | -| `_gat` | Esta cookie es utilizada por Google Analytics. | -| `_gid` | Esta cookie es utilizada por Google Analytics. | -| `_octo` | Esta cookie es utilizada por Octolytics, nuestro servicio analítico interno, para distinguir usuarios y clientes únicos. | -| `tracker` | Esta cookie rastrea la fuente de referencia para el análisis de registro. | - -Algunas páginas de nuestro sitio pueden establecer otras cookies de terceros. Por ejemplo, es posible que insertamos contenido, como vídeos, desde otro sitio que establezca una cookie. Si bien tratamos de minimizar estas cookies de terceros, no siempre podemos controlar qué cookies establece este contenido de terceros. - -### Rastreo en GitHub - -"[No realizar un seguimiento](https://www.eff.org/issues/do-not-track)"(DNT) es una preferencia de privacidad que puedes configurar en tu navegador si no deseas que los servicios en línea, en concreto las redes publicitarias, recopilen y compartan determinados tipos de información sobre tu actividad en línea a partir de servicios de seguimiento de terceros. GitHub responde a las señales DNT del navegador y sigue el estándar [W3C para responder a las señales DNT](https://www.w3.org/TR/tracking-dnt/). Si deseas configurar tu navegador para que indique que no deseas que se rastree, revisa la documentación de tu navegador acerca de cómo habilitar esa señal. También hay buenas aplicaciones que bloquean el seguimiento en línea, como [Privacy Badger](https://www.eff.org/privacybadger). - -Si no has habilitado DNT en un navegador que lo admita, las cookies en algunas partes de nuestro sitio web rastrearán tu actividad de navegación en línea en otros servicios en línea a lo largo del tiempo, aunque no permitimos que terceros que no sean nuestros proveedores de análisis y servicios rastreen la actividad de los usuarios de GitHub con el paso del tiempo en GitHub. Utilizamos estas cookies para permitirnos publicitar productos y servicios de GitHub en sitios web y servicios de terceros. También tenemos acuerdos con ciertos proveedores, como proveedores de análisis, que nos ayudan a rastrear los movimientos de los visitantes en ciertas páginas en nuestro sitio. Solo nuestros proveedores, que están recopilando información personal en nuestro nombre, pueden recopilar datos en nuestras páginas y hemos firmado acuerdos de protección de datos con cada proveedor que recopila estos datos en nuestro nombre. Utilizamos los datos que recibimos de estos proveedores para comprender mejor los intereses de nuestros visitantes, para comprender el rendimiento de nuestro sitio web y para mejorar nuestro contenido. Cualquier vendedor de análisis se incluirá en nuestra lista de Subprocesadores antes mencionada y es posible que veas una lista de cada página en la que recopilemos este tipo de datos que enunciamos a continuación. - -#### Google Analytics - -Utilizamos Google Analytics como un servicio analítico de terceros y para hacer un seguimiento de nuestras campañas publicitarias en sitios web y servicios de terceros. Utilizamos Google Analytics para recopilar información sobre cómo funciona nuestro sitio web y cómo nuestros usuarios, en general, navegan y usan GitHub. Esto nos ayuda a evaluar el uso de GitHub por parte de nuestros usuarios; compilar informes estadísticos sobre la actividad; y mejorar nuestro contenido y el rendimiento del sitio Web. Google brinda más información acerca de sus propias prácticas de privacidad y [ofrece un complemento del navegador para dejar de participar en el seguimiento de Google Analytics](https://tools.google.com/dlpage/gaoptout). - -#### Páginas en GitHub en las que se puede habilitar analytics - -Las páginas en las URL que contienen cualquiera de los siguientes dominios y rutas (incluidos los subdominios o subtrazados) en nuestros sitios pueden tener Analytics u otro código de seguimiento habilitado. Si deseas evitar que recopilemos información sobre tu actividad de navegación en GitHub, puedes usar un bloqueador de rastreo como [Privacy Badger](https://www.eff.org/privacybadger) u optar por el seguimiento de Google Analytics. - -- github.com/home (si has cerrado sesión o no tienes una cuenta, esta es la página que verás cuando vayas a github.com) -- github.com/about -- github.blog -- github.com/enterprise -- github.com/collections -- github.com/developer-stories -- github.com/events -- github.com/explore -- github.com/features -- github.com/logos -- github.com/nonprofit -- github.com/open-source -- github.com/personal -- github.com/pricing -- github.com/ten -- github.com/trending -- resources.github.com -- de.github.com -- fr.github.com diff --git a/translations/es-XL/content/github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing.md b/translations/es-XL/content/github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing.md deleted file mode 100644 index d487d47246..0000000000 --- a/translations/es-XL/content/github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing.md +++ /dev/null @@ -1,321 +0,0 @@ ---- -title: Términos complementarios de GitHub para las licencias por volumen de Microsoft -redirect_from: - - /articles/GitHub-Supplemental-Terms-for-Microsoft-Volume-Licensing/ - - /articles/github-supplemental-terms-for-microsoft-volume-licensing -versions: - free-pro-team: '*' ---- - -Fecha de entrada en vigor de la versión: 20 de julio de 2020 - -Los siguientes términos suplementarios de GitHub (incluyendo los formularios de pedidos correspondientes) complementan el acuerdo de licencias por volumen de Microsoft del cliente ("**Acuerdo del cliente de Microsoft**") y, junto con el acuerdo del cliente de Microsoft, rigen el uso de los productos por parte del cliente (como se define a continuación). El contrato de cliente de Microsoft se incorpora en este documento a través de esta referencia. Los términos con mayúscula inicial usados pero no definidos en estos términos suplementarios tienen los significados asignados a ellos en el contrato de cliente de Microsoft. - -Estos términos suplementarios se aplican a las siguientes ofertas de GitHub, como se define a continuación (en conjunto, el "**Productos**"): - -- GitHub Enterprise (que se compone del servidor de GitHub Enterprise, que puede incluir complemento de software y GitHub Enterprise Cloud) y GitHub One; - -- Cualquier Soporte relacionado; y - -- Cualquier Servicio profesional relacionado. - -Estos términos suplementarios de GitHub incluyen las siguientes secciones y anexos, cada uno de los cuales se incorpora por referencia en el presente documento: - -* SECCIÓN 1: Términos de la licencia del servidor de GitHub Enterprise; - -* SECCIÓN 2: Términos de servicio de GitHub Enterprise Cloud; - -* SECCIÓN 3: Disposiciones generales; y - -* PRUEBA A: Definiciones. - - - -## SECCIÓN 1: TÉRMINOS DE LA LICENCIA DEL SERVIDOR GITHUB ENTERPRISE - -La presente Sección 1 detalla los términos aplicables al uso del Software por parte del Cliente. - -### 1.1 Otorgamiento de la Licencia. - -GitHub le otorga al Cliente una licencia de plazo limitado no exclusiva, intransferible, multinacional y exenta de regalías para instalar y usar el Software para los propósitos comerciales internos del Cliente durante el Plazo de suscripción aplicable, de acuerdo con la Documentación y solamente por el número de Licencias de suscripción establecidos en el Formulario de pedidos del Cliente. El Software incluye componentes autorizados por terceros a GitHub, incluido el software cuya licencia exige que GitHub facilite el código fuente para que esos componentes estén disponibles. El código fuente para dichos componentes se facilitará previa solicitud. Sin limitar lo anterior, esta licencia permite que el cliente descargue y ejecute la imagen del contenedor de la edición estándar de Microsoft SQL Server para los archivos de Linux ("**Imágenes de SQL Server**"), que solo se puede utilizar con el software como se documenta. El derecho del cliente a usar las imágenes de SQL Server finaliza cuando el cliente ya no tiene derechos para usar el software y el cliente debe desinstalar las imágenes de SQL Server cuando su derecho a usarlos finalice. Microsoft Corporation puede inhabilitar las imágenes de SQL Server en cualquier momento. - -### 1.2 Restricciones. - -A excepción de lo expresamente permitido por la ley o por la licencia de terceros aplicable, el cliente y sus filiales no deben y no deben permitir que ningún tercero: (i) sublicencie, venda, alquile, arriende, transfiera, asigne o redistribuya el software; (II) aloje el software en beneficio de terceros; (III) divulgue o permita que un tercero acceda al software, excepto como se permita expresamente en la presente sección 1; (IV) hackee o modifique la clave de licencia, o evite o modifique cualquier proceso de registro de licencia; (v) excepto las modificaciones del cliente, modifique u origine trabajos derivados del software, o fusione el software con otro software; (VI) desmonte, descompile, omita cualquier ofuscación de código o, de lo contrario, haga ingeniería inversa del software o trate de derivar cualquiera de sus códigos fuente, en su totalidad o en parte; (VII) modifique, oscurezca o elimine cualquier aviso de derechos de propiedad incluido en o en el software o la documentación; o (VIII) de lo contrario, use o copie el software o la documentación de una manera que no esté expresamente permitida por estos términos suplementarios de GitHub. - -### 1.3 Delivery. - -GitHub facilitará la Clave de la licencia al Cliente para descargar en un sitio web seguro protegido con contraseña. All deliveries under this Section 1 will be electronic. Para evitar dudas, el Cliente es responsable de la instalación de cualquier Software y reconoce que GitHub no tiene ninguna obligación de entrega adicional con respecto al Software después de la entrega de la Clave de la licencia. Cuando las actualizaciones estén disponibles, GitHub las facilitará para la descarga en el mismo sitio web. El Cliente debe Actualizar el Software sobre una base comercialmente razonable pero no menos de una (1) vez al año. El Cliente es responsable de mantener la confidencialidad de sus nombres de usuario y sus contraseñas. - -### 1.4 Verification. - -A solicitud de GitHub, el cliente proporcionará de inmediato a GitHub un informe generado por software que verifica que el cliente está usando el software de acuerdo con estos términos suplementarios de GitHub. GitHub facturará al cliente por cualquier uso adicional, efectivo desde la fecha en que su uso superó por primera vez los términos de estos términos suplementarios de GitHub. - -### 1.5 Support - -GitHub proporcionará soporte técnico para el software como se describe más detalladamente en el acuerdo del cliente de Microsoft. GitHub podrá proporcionar ofertas de soporte ampliado para el Software y los servicios (incluyendo aquellas para Soporte Premium, Premium Plus, y Soporte Directo de Ingeniería) de acuerdo con las [Condiciones de soporte](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise), y en el nivel de soporte, cuotas y término de la suscripción que se especifica en un Formato de Compra o SOW. Sin perjuicio de cualquier disposición contraria en el acuerdo del cliente de Microsoft, (i) GitHub hará los esfuerzos razonables para corregir cualquier error material, reproducible en el software a la notificación del cliente de un error, pero no será responsable de proporcionar soporte cuando (a) alguien (que no sea GitHub) modifique el software; (b) el cliente cambie su sistema operativo o entorno de una manera que afecte adversamente el software o su desempeño; (c) el cliente use el software de una manera que no sea la autorizada conforme al acuerdo del cliente de Microsoft, esta sección 1 o la documentación; o (d) exista un accidente o negligencia del cliente, o mal uso del software; y (II) GitHub solo admitirá una versión determinada durante un (1) año a partir de la fecha de lanzamiento original, o seis (6) meses desde la última actualización del lanzamiento, la que sea más larga. - -### 1.6 Updates; Releases. - -#### 1.6.1 Generally. - -GitHub facilitará al Cliente las Actualizaciones y Lanzamientos del Software en el mismo sitio web seguro donde el Cliente descargó el Software y la Clave de la licencia. - -#### 1.6.2 Supported Releases. - -GitHub solamente dará Soporte un Lanzamiento dado del Software durante un (1) año desde la fecha del Lanzamiento original, o seis (6) meses desde la última Actualización del lanzamiento, lo que sea más prolongado. Si el Cliente requiere Soporte para Lanzamientos anteriores del Software, en ese caso el Cliente debe pagar por ese Soporte de acuerdo con los términos de un Formulario de pedidos o SOW convenidos mutuamente. - -### 1.7 Software agregado. - -El software agregado está licenciado por usuario. Para evitar dudas y a menos que se estipule lo contrario en un formulario de pedidos, la cantidad de licencias de suscripción que el cliente tiene en un momento dado para el software del complemento debe ser igual a la cantidad de licencias de suscripción que el cliente tiene para los productos conforme a lo dispuesto en el presente acuerdo. Por ejemplo, si el cliente desea comprar una suscripción a Insights y ya cuenta con licencias de suscripción para l100 usuarios para los productos, debe comprar licencias de suscripción para 100 usuarios para Insights. - -### 1.8 Consideraciones sobre la protección de datos para el uso de GitHub Insights and Learning Lab for Enterprise Server. - -Si el uso planificado del cliente de GitHub Insights o Learning Lab for Enterprise Server implica el procesamiento de datos personales, el cliente es el único responsable de determinar si completar o no una evaluación de impacto de protección de datos o el análisis legal formal del uso planificado del cliente. A criterio exclusivo del cliente, ya sea usar GitHub Insights o Learning Lab for Enterprise Server para procesar los datos de los empleados y/o usuarios del cliente, y si el cliente lo hace, el cliente es el único responsable de llevar a cabo dicho procesamiento de conformidad con la legislación aplicable. - -### 1.9 Garantía de Software Limitada. - -GitHub garantiza que, por 90 (90) días a partir de la fecha en que se encuentra disponible para la descarga inicial, el software sin modificar se ajustará sustancialmente a su documentación. GitHub no garantiza que el uso del software por parte del cliente será ininterrumpido, o que la operación del software estará libre de errores. Esta garantía no se aplicará si el cliente modifica o usa el software de cualquier manera que no esté expresamente permitida por la presente sección 1 y la documentación. La única obligación de GitHub, y el único remedio del cliente, por cualquier incumplimiento de esta garantía limitada será como se establece en el acuerdo del cliente de Microsoft. - -## SECTION 2: GITHUB ENTERPRISE CLOUD TERMS OF SERVICE - -Upon creation of a Corporate Account and/or an Organization on the Service by Customer or by GitHub on Customer’s behalf, this Section 2 details terms applicable to Customer’s use of the Service. - -### 2.1 Account Terms. - -#### 2.1.1 Account Controls. - - **(i) Usuarios.** El Cliente reconoce que los Usuarios conservan el control administrativo final sobre sus cuentas individuales y sobre el Contenido de las mismas. [Los términos de servicio estándar de GitHub](/github/site-policy/github-terms-of-service) rigen el uso del servicio por parte de los usuarios, excepto con respecto a las actividades de los usuarios conforme a lo dispuesto en la presente sección 2. - - **(ii) Organizaciones.** El Cliente conserva el control administrativo final sobre cualquier Organización creada en nombre del Cliente y sobre el Contenido generado por el Usuario publicado en los repositorios dentro de su(s) Organización(es), sujetos a la presente Sección 2. This Section 2 will govern the use of Customer’s Organization(s). - -#### 2.1.2 Account Requirements. - -Para crear una cuenta, el Cliente debe adherirse a los siguientes puntos: - -**(i)** El Cliente no debe crear una cuenta para que la use cualquier persona menor de 13 años. Si GitHub se entera de que existe algún Usuario menor de 13 años, cancelará esa cuenta de Usuario de inmediato. Si el Cliente o su(s) Usuario(s) están ubicados en un país fuera de los Estados Unidos, la edad mínima de ese país puede ser mayor; en ese caso, el Cliente es responsable de cumplir con las leyes de ese país. - -**(ii)** Un Inicio de sesión de un Usuario no se debe compartir con múltiples personas. - -**(iii)** El cliente no deberá utilizar el Servicio (a) si este viola las leyes de sanción o control de exportaciones de los Estados Unidos o de cualquier otra jurisdicción aplicable, (b) si se ubica en o reside habitualmente en un país o territorio sujeto a sanciones generales administrades por la Oficina de Control de Bienes Extranjeros de los EE.UU. (OFAC, por sus siglas en inglés), o (c) si el Cliente es o está trabajando por parte de un [Nacional Especialmente Designado (SDN, por sus siglas en inglés)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) o una persona sujeta a bloqueos o prohibiciones de la parte denegada similares. Para obtener más información, por favor consulta la [Política de controles comerciales de GitHub](/github/site-policy/github-and-trade-controls). - -#### 2.1.3 Account Security. - -El Cliente es responsable por lo siguiente: (i) todos los Contenidos publicados y las actividades que ocurran en su Cuenta corporativa; (ii) mantener la seguridad de sus credenciales de inicio de sesión de su cuenta; y (iii) de inmediato [notificar a GitHub](https://support.github.com/contact) al enterarse de cualquier uso no autorizado del Servicio o acceso a este a través de su cuenta. GitHub will not be liable for any loss or damage from Customer’s failure to comply with this Section 2.1.3. - -#### 2.1.4 Additional Terms. - -En algunas situaciones, pueden aplicarse términos de terceros al uso del Servicio por parte del Cliente. Por ejemplo, el Cliente puede ser miembro de una Organización con sus propios términos o acuerdos de licencia; el Cliente puede descargar una aplicación que se integre con el Servicio; o el Cliente puede usar el Servicio para autenticarse a otro servicio. Si bien el acuerdo del cliente de Microsoft, incluidos estos términos complementarios de GitHub, es el acuerdo completo de GitHub con el cliente, los términos de otras partes rigen sus relaciones con el cliente. - -#### 2.1.5 Términos del Gobierno federal de los EE.⁰UU. Términos del Gobierno federal de los EE.⁰UU. - -If Customer is a U.S. federal government agency or otherwise accessing or using any portion of the Service in a government capacity, the [U.S. Federal Government Amendment](/github/site-policy/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) applies, and Customer agrees to its provisions. - -### 2.2 Compliance with Laws; Acceptable Use; Privacy. - -#### 2.2.1 Compliance with Laws and Regulations. - -El uso del Servicio por parte del Cliente no debe infringir las leyes vigentes, incluidas las leyes de propiedad intelectual o el nombre comercial, las leyes de control de las exportaciones o las regulaciones en su jurisdicción. - -#### 2.2.2 Acceptable Use. - -El uso del servicio por parte del cliente debe cumplir con las [Políticas de Uso Aceptable de GitHub](/github/site-policy/github-acceptable-use-policies) y con [los Lineamientos de la Comunidad de GitHub](/github/site-policy/github-community-guidelines). El Cliente no debe usar el Servicio en ninguna jurisdicción si contiene Contenidos o actividades ilegales, obscenos, ofensivos o fraudulentos, tales como promover o causar daño, vulnerar la integridad o la seguridad de una red o sistema o interferir en ellos, evadir filtros, enviar mensajes no solicitados, abusivos o engañosos, virus o códigos perjudiciales, o socavar los derechos de terceros. - -#### 2.2.3 Privacy. -[La Declaración de Privacidad de GitHub](/github/site-policy/github-privacy-statement) y la [Adenda de Protección de Datos de GitHub](/github/site-policy/github-data-protection-addendum) proporciona notificación detallada de las prácticas de privacidad y uso de datos así como de las obligaciones de seguridad y procesamiento de GitHub con respecto a los Datos Personales del Cliente. Cualquier persona, entidad o servicio que recolecta datos del Servicio debe cumplir con la [Declaración de privacidad de GitHub](/github/site-policy/github-privacy-statement), particularmente en cuanto a la recopilación de la Información personal del Usuario (como se define en la Declaración de privacidad de GitHub). Si el Cliente recopila cualquier Información personal del usuario proveniente de GitHub, el Cliente solamente la usará para el propósito por el cual el Usuario externo lo autorizó. El Cliente asegurará razonablemente dicha Información personal y el Cliente responderá de inmediato a las quejas, las solicitudes de eliminación y las solicitudes de "no contactar" de GitHub o de Usuarios externos. - -### 2.3 Content Responsibility; Ownership; License Rights. - -#### 2.3.1 Responsibility for User-Generated Content. -El Cliente puede crear o cargar Contenido generado por el Usuario mientras usa el Servicio. El Cliente es el único responsable de cualquier Contenido generado por el Usuario que se publique, cargue, vincule o ponga a disposición de cualquier otra manera a través del Servicio, independientemente de la forma de ese Contenido generado por el Usuario. GitHub no es responsable de ninguna visualización pública o uso indebido del Contenido generado por el Usuario. - -#### 2.3.2 Ownership of Content, Right to Post, and License Grants. - -**(i)** El Cliente mantiene la propiedad sobre el Contenido del Cliente que el Cliente crea o posee. El Cliente reconoce lo siguiente: (a) que es responsable del Contenido del Cliente, (b) que solo enviará el Contenido del Cliente que el Cliente tenga derecho a publicar (incluido el Contenido generado por el Usuario o por terceros) y (c) que el Cliente cumplirá plenamente con cualquier licencia de terceros relacionada con el Contenido del Cliente que el Cliente publica. - -**(ii)** Customer grants the rights set forth in Sections 2.3.3 through 2.3.6, free of charge and for the purposes identified in those sections until such time as Customer removes Customer Content from GitHub servers, except for Content Customer has posted publicly and that External Users have Forked, in which case the license is perpetual until such time as all Forks of Customer Content have been removed from GitHub servers. Si el Cliente carga Contenido del Cliente que ya viene con una licencia y le otorga a GitHub los permisos que necesita para ejecutar el Servicio, no se requiere ninguna licencia adicional. - -#### 2.3.3 License Grant to GitHub. -El Cliente le otorga a GitHub el derecho a almacenar, analizar y mostrar el Contenido del Cliente y de hacer copias incidentales solo como sea necesario para proporcionar el Servicio. Esto incluye el derecho a copiar el Contenido del Cliente en la base de datos de GitHub y a hacer copias de seguridad; mostrarle el Contenido del Cliente al Cliente y a quienes el Cliente decida; analizar el Contenido del Cliente en un índice de búsqueda o, de lo contrario, analizarlo en los servidores de GitHub; compartir el Contenido del Cliente con Usuarios externos con los cuales el Cliente elige compartirlo; y reproducir el Contenido del Cliente, en el caso de que se trate de música o vídeo. Estos derechos se aplican tanto a los Repositorios privados como a los públicos. Esta licencia no le otorga a GitHub el derecho a vender el Contenido del Cliente o a distribuirlo o utilizarlo por fuera del Servicio. El Cliente le otorga a GitHub los derechos que necesita para usar el Contenido del Cliente sin atribución y para hacer las adaptaciones razonables del Contenido del Cliente como sea necesario para proporcionar el Servicio. - -#### 2.3.4 License Grant to External Users. -**(i)** Cualquier Contenido que el Cliente publica de forma pública, incluidas propuestas, comentarios y contribuciones a los repositorios de Usuarios externos, puede ser visto por otras personas. El Cliente acepta permitir que Usuarios externos vean y bifurquen los repositorios del Cliente cuando configura sus repositorios para que se vean públicamente. - -**(ii)** Si el Cliente configura sus páginas y repositorios para que se vean públicamente, el Cliente les otorga a los Usuarios externos una licencia no exclusiva y multinacional para usar, mostrar y ejecutar el Contenido del Cliente a través del Servicio y para reproducir el Contenido del Cliente únicamente en el Servicio, según se permite a través de la funcionalidad que proporciona GitHub (por ejemplo, a través de la Bifurcación). El Cliente puede otorgar derechos adicionales sobre el Contenido del Cliente si el Cliente [adopta una licencia](/github/building-a-strong-community/adding-a-license-to-a-repository#including-an-open-source-license-in-your-repository). Si el Cliente está cargando Contenido del Cliente que no creó ni posee, el Cliente es responsable de asegurar que el Contenido del Cliente que carga cuente con licencia conforme a los términos que otorgan estos permisos a los Usuarios externos. - -#### 2.3.5 Contributions Under Repository License. -Siempre que el Cliente hace una contribución a un repositorio que contiene un aviso de licencia, el Cliente licencia tal contribución conforme a los mismos términos y acepta que tiene derecho a licenciar dicha contribución conforme a esos términos. Si el Cliente tiene otro acuerdo para licenciar sus contribuciones conforme a términos diferentes, tal como un acuerdo de licencia de colaborador, ese acuerdo prevalecerá. - -#### 2.3.6 Moral Rights. -El Cliente conserva todos los derechos morales sobre el Contenido del Cliente que carga, publica o envía a cualquier parte del Servicio, incluidos los derechos de integridad y atribución. However, Customer waives these rights and agrees not to assert them against GitHub, solely to enable GitHub to reasonably exercise the rights granted in Section 2.3, but not otherwise. - -### 2.4. Repositorios privados. - -#### 2.4.1 Control. - -El Cliente es responsable de administrar el acceso a sus Repositorios privados, incluidas las invitaciones, el control administrativo de las Organizaciones y los equipos, y la anulación del acceso. - -#### 2.4.2 Confidentiality. - -GitHub considera que el Contenido del Cliente en los Repositorios privados del Cliente constituye Información confidencial del Cliente. GitHub protegerá y mantendrá estrictamente confidencial el contenido del cliente de los repositorios privados de acuerdo con la disposición de confidencialidad aplicable en el acuerdo del cliente de Microsoft. - -#### 2.4.3 Access. - -GitHub solo puede acceder a los Repositorios privados del Cliente (i) con el consentimiento y el conocimiento del Cliente, por razones de asistencia o (ii) cuando se requiere el acceso por razones de seguridad. El Cliente puede decidir habilitar más acceso a sus Repositorios privados. Por ejemplo, el Cliente puede habilitar varios servicios o funciones de GitHub que requieren derechos adicionales sobre el Contenido del Cliente en los Repositorios privados. Estos derechos pueden variar según el servicio o la función, pero GitHub continuará considerando el Contenido del Cliente en los Repositorios privados del Cliente como Información confidencial. GitHub proporcionará una explicación sobre esos derechos si esos servicios o funciones requieren más derechos de los que necesita para proporcionar el Servicio. - -#### 2.4.4 Exclusions. - -Si GitHub tiene motivos para creer que el contenido de un repositorio privado infringe la ley o estos términos suplementarios de GitHub, GitHub tiene derecho a acceder, revisar y eliminar ese contenido. Además, GitHub puede ser obligado por ley a divulgar el Contenido de los Repositorios privados del Cliente. A menos que los requisitos previstos por la ley indiquen lo contrario o que sea en respuesta a una amenaza de seguridad u otro riesgo para la seguridad, GitHub dará aviso de tales acciones. - -### 2.5. Notificaciones de propiedad intelectual. - -#### 2.5.1 GitHub's Rights to Content. - -La apariencia del Servicio es propiedad intelectual de © GitHub, Inc. Todos los derechos reservados. El Cliente no puede duplicar, copiar o volver a usar ninguna parte de los elementos o conceptos de HTML/CSS, Javascript o de diseño visual sin autorización expresa por escrito de GitHub. - -#### 2.5.2 Copyright Infringement and DMCA Policy. - -Si el Cliente es propietario de los derechos de autor y determina que el Contenido del Servicio viola dichos derechos, éste podrá contactar a GitHub de acuerdo con la [Política sobre la Ley de Derechos de Autor de la Era Digital](https://github.com/contact/dmca) de GitHub si le notifica a través de su [Formato DMCA](https://github.com/contact/dmca-notice) o si envía un mensaje de correo electrónico a copyright@github.com. - -#### 2.5.3 GitHub Trademarks and Logos. - -Si el Cliente desea usar los nombres comerciales de GitHub, debe seguir todas las pautas de nombres comerciales de GitHub, incluidas las que se encuentran en la [Página de logos y uso de GitHub](https://github.com/logos). - -### 2.6 Suspension. - -GitHub tiene el derecho de suspender el acceso a la totalidad o a cualquier parte del servicio, incluido el eliminar contenido, en cualquier momento por la violación del acuerdo del cliente de Microsoft, incluyendo estos términos suplementarios de GitHub, o para proteger la integridad, la operabilidad y la seguridad del servicio, con efecto inmediato, con o sin aviso. A menos que esté prohibido por ley o proceso legal o para prevenir daños inminentes al Servicio o a cualquier tercero, GitHub normalmente proporciona un aviso en forma de banner o correo electrónico en o antes de dicha suspensión. GitHub personalizará, a su criterio y de buena fe, cualquier suspensión que sea necesaria para preservar la integridad, operatividad y seguridad del Servicio. - -### Comunicaciones con GitHub. - -Con fines contractuales, el Cliente (1) consiente recibir comunicaciones en un formulario electrónico a través de la dirección de correo electrónico que se envío o a través del Servicio; y (2) acepta que todos los Términos de Servicio, acuerdos, avisos, revelaciones y otras comunicaciones que GitHub proporciona electrónicamente cumple con cualquier requerimiento legal que estas comunicaciones satisfagan si estuvieran en papel. Esta sección no afecta los derechos no renunciables del Cliente. - -### 2.8 Service Level Agreement. - -GitHub’s quarterly uptime commitment for the Service is provided in the [Enterprise Service Level Agreement](/github/site-policy/github-enterprise-service-level-agreement). Customer will be entitled to a service credit if GitHub does not meet its service level. - -### 2.9 Service Changes. - -GitHub cambia el Servicio mediante Actualizaciones y adición de nuevas características. Subject to Section 2.8, GitHub reserves the right at any time to modify or discontinue, temporarily or permanently, the Service (or any part of it) with or without notice. - -### 2.10 Características adicionales del servicio. - -Algunas características de servicio pueden estar sujetas a términos adicionales como se establece en los [términos de producto adicionales de GitHub](/github/site-policy/github-additional-product-terms). Al acceder o utilizar estas características, el cliente acepta las condiciones de producto adicionales de GitHub. - -## SECCIÓN 3: DISPOSICIONES GENERALES. - -This Section 3 sets forth the terms and conditions applicable to Customer’s purchase and use of any of the Products. - -### 3,1 Plazo; terminaciones; efecto de la terminación. - -#### 3.1.1 Term. -Estos términos suplementarios de GitHub continuarán en vigencia hasta que una parte la cancele de acuerdo con lo dispuesto en la presente sección 3.1. - -#### 3.1.2 Terminación por conveniencia; cancelación de la cuenta. -Cualquiera de las partes puede terminar un formulario de pedidos o estos términos suplementarios de GitHub, sin causa, al menos treinta (30) días de aviso por escrito antes del final del plazo de suscripción vigente en ese momento. Si el cliente opta por terminar un formulario de pedidos o estos términos suplementarios de GitHub, es responsabilidad del cliente cancelar correctamente su cuenta con GitHub entrando en configuraciones en la barra de navegación global en la parte superior de la pantalla. GitHub no puede cancelar cuentas en respuesta a un correo electrónico o a una solicitud telefónica. - -#### 3.1.3 Termination for Material Breach. -Cualquiera de las partes puede rescindir estos términos suplementarios de GitHub inmediatamente después de la notificación si la otra parte viola una obligación material conforme a lo dispuesto en los presentes términos suplementarios de GitHub y no remedia la violación dentro de los treinta (30) días a partir de la fecha en que recibe la notificación. GitHub puede poner fin a estos términos suplementarios de GitHub si la cuenta del cliente ha sido suspendida por más de 90 días. - -#### 3.1.4 Efecto de la terminación. -Tras la terminación de estos términos suplementarios de GitHub, el cliente no puede ejecutar formularios de pedidos adicionales; sin embargo, estos términos suplementarios de GitHub seguirán vigentes para el resto de los formularios de pedidos activos. Cuando un formulario de pedidos finaliza o expira, en cuanto a ese formulario de pedidos: (i) el plazo de suscripción finalizará de inmediato; (II) cualquier licencia de suscripción en el formulario de pedidos terminará automáticamente y el cliente ya no tendrá derecho a usar los productos; (III) si alguna tarifa se adeudaba antes de la terminación, el cliente debe pagar esas tarifas de inmediato; (IV) el cliente debe destruir todas las copias del software en posesión o control del cliente y certificar por escrito a GitHub que el cliente lo ha hecho; (v) cada una de las partes devolverá de inmediato (o, si la otra parte lo solicita, destruirá) toda la información confidencial que pertenezca a la otra en la medida permitida por el servicio. Sin perjuicio de lo anterior, el Cliente puede continuar accediendo al Software para migrar sus datos y puede solicitar la migración de los datos en sus repositorios por hasta noventa (90) días después de la terminación o la caducidad del presente Acuerdo o de un Formulario de pedidos; sin embargo, el Cliente no puede usar el Software o el Servicio sobre una base de producción durante ese período de tiempo. Cualquier disposición que por su naturaleza debiera mantenerse razonablemente en vigencia continuará luego de la terminación o la caducidad del presente Acuerdo o de un Formulario de pedidos. - -### 3.2 Retroalimentación. -El Cliente puede proporcionar Retroalimentación a GitHub con respecto a los Productos. La retroalimentación es voluntaria y no es Información Confidencial del Cliente, incluso si se designa como tal. GitHub puede ejercer y explotar plenamente dicha Retroalimentación con el propósito de (i) mejorar la operación, funcionalidad y uso de las ofertas de productos existentes y futuras de GitHub; y (ii) publicación de estadísticas agregadas sobre la calidad de los Productos, siempre que no se utilicen datos en ninguna de estas publicaciones para identificar específicamente al Cliente, sus empleados o el código de software propietario del Cliente. - -### 3.3. Cumplimiento con las leyes y regulaciones. -El cliente cumplirá con todas las leyes y regulaciones aplicables, incluyendo, entre otras, las leyes y regulaciones de protección de datos y empleo, en su uso de los productos. - -### 3.4 Orden de precedencia -En el caso de un conflicto entre los términos suplementarios, por una parte, y un formulario de pedidos, por otro lado, el formulario de pedidos se regirá con respecto a esa orden únicamente. En el caso de un conflicto entre los términos suplementarios (incluyendo cualquier formulario de pedidos) y el acuerdo del cliente de Microsoft, los términos suplementarios prevalecerán con respecto al asunto únicamente. - -## PRUEBA A: DEFINICIONES - -**"Usuario activo"** se refiere a un Usuario que trata de acceder al Servicio en el momento de una Interrupción. - -**"Software agregado"** se refiere a Advanced Security, Insights, Learning Lab for Enterprise Server y otros productos adicionales de software agregado que GitHub puede ofrecer de vez en cuando. - -**"Seguridad avanzada"** se refiere a la característica de software que permite que el cliente identifique vulnerabilidades de seguridad mediante un análisis de código semántico personalizable y automatizado. - -**"Subsidiaria"** se refiere a cualquier entidad que controla directa o indirectamente, que es controlada o se encuentra bajo el control normal de una parte, donde "control" significa tener más del cincuenta por ciento (50⁰%) de la propiedad o el derecho a dirigir la administración de la entidad. - -**“Todos los usuarios”** se refiere, en conjunto, a los Usuarios del Cliente y los Usuarios externos que usan el Servicio. - -**“Conexión”** o **“Conexión con GitHub”** se refiere a una función incluida en el Software que habilita al Cliente a conectar el Software con GitHub.com. El uso de conexión con GitHub está sujeto a los términos de conexión de GitHub establecidos en los [Términos adicionales del producto de GitHub](/github/site-policy/github-additional-product-terms). - -**"Contenido"** se refiere, entre otros, a textos, datos, artículos, imágenes, fotografías, gráficos, software, aplicaciones, diseños, funciones y otros materiales que se presentan, se muestran o se ponen a disposición a través del Servicio. - -**"Cuenta corporativa"** se refiere a una cuenta creada por el Usuario en nombre de una entidad. - -**Cliente** significa, colectivamente, la empresa u organización que ha celebrado estos términos suplementarios de GitHub con GitHub al hacer clic en el botón "Acepto" o en un botón similar o al acceder a los productos y a los afiliados y representantes del cliente. - -**"Contenido del Cliente"** se refiere al Contenido que el Cliente crea, posee o sobre el cual el Cliente tiene los derechos. - -**“Modificaciones del Cliente”** se refiere a las modificaciones del Software que el Cliente puede hacer únicamente con el fin de realizar corrección de errores, personalizaciones o funciones adicionales para cualquier biblioteca con licencia en las licencias de código abierto que se pueden incluir con el Software o vincularse a este. - -**"Documentación"** se refiere a cualquier manual, documentación y otros materiales de soporte relacionados con el Software o el Servicio que GitHub proporciona o pone a disposición del Cliente. - -**"Fecha de vigencia"** es la primera fecha en que el cliente (i) acepta los términos y condiciones de estos términos suplementarios de GitHub, como se describe arriba, o (II) coloca primero un pedido para los productos. - -**"Servicios esenciales"** se refiere a los servicios esenciales para la funcionalidad de control de la versión principal de GitHub, que incluyen crear, bifurcar y clonar repositorios; crear, confirmar y fusionar ramas; crear, revisar y fusionar solicitudes de extracción; y las interfaces web, API y Git del cliente para los flujos de Git principales. Los siguientes ejemplos muestran funciones periféricas y servicios que no están incluidos: webhooks, Gists, Páginas y notificaciones por correo electrónico. - -**"Usuario externo"** se refiere a un individuo, que no incluye a los Usuarios del Cliente, que visita o usa el Servicio. - -**"Cuotas"** significa que las cuotas que el cliente tiene que pagar a GitHub por (i) usar los Productos durante el término de suscripción aplicable o (ii) recibir Servicios Profesionales, ya que dichas cuotas se reflejan en un formulario de pedido o SOW. - -**"Retroalimentación"** hace referencia a cualquier idea, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario sobre productos o servicios de GitHub. - -**“Bifurcación”** se refiere a copiar el Contenido de un repositorio en otro repositorio. - -**"GitHub"** se refiere, en conjunto, a GitHub, Inc., sus Subsidiarias y Representantes. - -**"Contenido de GitHub"** se refiere al Contenido que GitHub crea, posee o el contenido sobre el cual tiene los derechos. - -**"Insights de GitHub"** o **Insights** se refiere a la característica de software que le brinda a los clientes métricas, analíticas y recomendaciones relacionadas con el uso del software. GitHub Insights no incluye características heredadas de GitHub incluyendo información de la organización e información del repositorio. - -**"GitHub One"** se refiere al paquete de productos que incluye GitHub Enterprise, Advanced Security, Insights, Learning Lab for Enterprise Server y Premium Plus o soporte de ingeniería Direct. - -**"Learning Lab for Enterprise Server"** hace referencia a la función de software que permite a los usuarios aprendan sobre la funcionalidad de GitHub, incluyendo la documentación asociada. - -**"Clave de licencia"** se refiere a los archivos de datos que usa el mecanismo de control de acceso del Software que le permiten al Cliente instalar, operar y usar el Software. - -**“Cuenta de máquina”** se refiere a una cuenta registrada por una persona que acepta los términos aplicables del servicio en nombre de la Cuenta de máquina, proporciona una dirección de correo electrónico válida y es responsable de sus acciones. Una Cuenta de máquina se usa exclusivamente para ejecutar tareas automatizadas. Múltiples usuarios pueden dirigir las acciones de una Cuenta de máquina, pero el propietario de la cuenta es responsable en última instancia de las acciones de la máquina. - -**"Formulario de pedidos"** se refiere a la documentación electrónica o por escrito (incluido un presupuesto) que las Partes usan para pedir los Productos. - -**“Organización”** se refiere a un espacio de trabajo compartido que se puede asociar con una única entidad o con uno o más Usuarios donde múltiples Usuarios pueden colaborar en muchos proyectos a la vez. Un Usuario puede ser miembro de más de una Organización. - -**"Interrupción"** se refiere a la interrupción de un Servicio esencial que afecta a más del 50⁰% de los Usuarios activos. - -**“Repositorio privado”** se refiere a un repositorio que permite que un Usuario controle el acceso al Contenido. - -**"Servicios profesionales"** se refiere a los servicios de capacitación, consultoría o implementación que GitHub proporciona conforme a un SOW ejecutado recíprocamente. Los Servicios profesionales no incluyen el Soporte. - -**“Repositorio público”** se refiere a un repositorio cuyo Contenido es visible para todos los Usuarios. - -**"Lanzamiento"** se refiere a un lanzamiento de Software que GitHub generalmente pone a disposición de sus clientes, junto con cualquier cambio correspondiente en la Documentación, que contiene mejoras, funciones o funcionalidades nuevas, que se suelen indicar con un cambio en el dígito a la derecha del primer punto decimal (por ejemplo, x.x.x a x.y.x) o a la izquierda del primer punto decimal (por ejemplo, x.x.x a y.x.x). - -**"Representantes"** se refiere a empleados, agentes, contratistas independientes, consultores y asesores legales y financieros de una de las Partes. - -**“Extracción”** se refiere a extraer datos del Servicio a través de un proceso automatizado, como un bot o agente de búsqueda, y que no incluye la recopilación de información a través de la API de GitHub. - -**"Servicio"** se refiere al servicio alojado de GitHub Enterprise Cloud. El Servicio incluye: Cuenta(s) de organización, inicio único de sesión de SAML, provisión de acceso y cualquier Documentación correspondiente. Esta lista de funciones y servicios no es exhaustiva y puede ser actualizada de vez en cuando. - -**"Crédito de servicio"** se refiere a un crédito en dólares, calculado como se establece a continuación, que GitHub puede acreditar a una cuenta elegible. - -**"Software"** significa el Software local de GitHub Enterprise Server. El Software incluye la característica de GitHub Connect, cualquier Documentación aplicable, cualquier Actualización al Software que Github proporcione al Cliente o al que éste pueda acceder bajo las presentes Condiciones Adicionales de GitHub y, si se incluyese en la suscripción del Cliente, el Software Complementario. - -**"SOW"** se refiere a una declaración de trabajo ejecutada recíprocamente que detalla los Servicios profesionales que GitHub realizará, cualquier Tarifa relacionada y las obligaciones relacionadas de cada una de las Partes. - -**“Licencia de suscripción”** se refiere a la licencia asignada a cada Usuario para instalar, operar, acceder y usar los Productos en nombre del Cliente. El Cliente puede asignar solamente una Licencia de suscripción por Usuario en sus instancias del servidor de GitHub Enterprise y Organizaciones de GitHub Enterprise Cloud. Cada Usuario tendrá acceso a tantas instancias del servidor de Enterprise del Cliente o a Organizaciones de Enterprise Cloud como el Cliente lo permita. Para mayor claridad, sin embargo, una vez que el Cliente asigna una Licencia de suscripción a un Usuario, el Cliente no estará autorizado a bifurcar la Licencia de suscripción de modo que un Usuario podrá usar una Licencia de suscripción en el servidor de Enterprise mientras otro Usuario usa la misma Licencia de suscripción en otra instancia del servidor de GitHub Enterprise o en una Organización de GitHub Enterprise Cloud. Las Licencias de suscripción se otorgan por Usuario y la misma Licencia de suscripción no puede ser utilizada por múltiples Usuarios. El Cliente puede reasignar una Licencia de suscripción a un nuevo Usuario solo después de noventa (90) días desde la última reasignación de esa misma Licencia de suscripción, excepto que la reasignación se deba a (i) la pérdida o la falla permanente del hardware, (ii) la terminación del empleo o el contrato del Usuario, o (iii) la readjudicación temporal de las Licencias de Suscripción para cubrir una ausencia del Usuario. Cuando el Cliente reasigna una Licencia de suscripción de un Usuario a otro, el Cliente debe bloquear el acceso del Usuario anterior a la Licencia de suscripción y a las Organizaciones del Cliente. - -**“Plazo de la suscripción”** se refiere a un (1) año a partir de la fecha de entrada en vigor correspondiente de un pedido o como se indique en el Formulario de pedidos. - -**“Soporte”** se refiere al soporte técnico para el Software o el Servicio que GitHub puede proporcionar. - -**“Actualizar”** se refiere a un lanzamiento de Software que GitHub, generalmente, pone a disposición de sus clientes, junto con cualquier cambio correspondiente en la Documentación, que contiene correcciones o solución de errores, que se suele indicar con un cambio en el dígito a la derecha del segundo punto decimal (por ejemplo, x.x.x a x.x.y). - -**“Tiempo de actividad”** se refiere al porcentaje de tiempo en un trimestre dado en que los Servicios esenciales de GitHub no se detendrán por una Interrupción que afecte a más del 50⁰% de los Usuarios activos - -**"Usuario"** significa (i) con respecto al Software, una sola persona o Cuenta de Máquina que inicia la ejecución de dicho Software o interactúa o dirige a éste al desempeño de sus funciones; y (ii) con respecto al Servicio, un individuo o Cuenta de Máquina que (a) accede o utiliza el Servicio, (b) accede a, o utiliza, cualquier parte de la cuenta del Cliente, o (c) dirige el uso de la cuenta del Cliente en la ejecución de sus funciones, en cada caso, en representación del Cliente. La cantidad de Usuarios no debe exceder el número de Licencias de suscripción que el Cliente compró. - -**“Contenido generado por el Usuario”** se refiere al Contenido que un tercero o un Usuario externo crea o posee. diff --git a/translations/es-XL/content/github/site-policy/github-terms-of-service.md b/translations/es-XL/content/github/site-policy/github-terms-of-service.md deleted file mode 100644 index 7f4966d562..0000000000 --- a/translations/es-XL/content/github/site-policy/github-terms-of-service.md +++ /dev/null @@ -1,316 +0,0 @@ ---- -title: Términos de servicio de GitHub -redirect_from: - - /tos/ - - /terms/ - - /terms-of-service/ - - /github-terms-of-service-draft/ - - /articles/github-terms-of-service -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -¡Gracias por usar GitHub! Estamos felices de que estés aquí. Por favor, lee cuidadosamente estos Términos de Servicio antes de ingresar o usar GitHub. Ya que se trata de un contrato tan importante entre nosotros y nuestros usuarios, intentamos ser muy claros. Para tu comodidad, presentamos estos términos en un breve resumen no vinculante seguido de los términos legales completos. - -### Resumen - -| Sección | ¿Qué puedes encontrar allí? | -| --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [A. Definiciones](#a-definitions) | Algunos términos básicos, definidos de forma que te ayude a entender este acuerdo. Consulta la copia de seguridad de esta sección para obtener una aclaración. | -| [B. Términos de la cuenta](#b-account-terms) | Estos son los requisitos básicos para tener una cuenta en GitHub. | -| [C. Uso aceptable](#c-acceptable-use) | Estas son las reglas básicas que debes seguir cuando uses tu cuenta de GitHub. | -| [D. Contenido generado por el usuario](#d-user-generated-content) | Eres responsable del contenido que publicas en GitHub. Sin embargo, tienes ciertas responsabilidades al respecto y te pedimos que nos otorgues algunos derechos de manera que podamos proporcionarte los servicios. | -| [E. Repositorios privados](#e-private-repositories) | Esta sección expone cómo tratará GitHub el contenido que publiques en los repositorios privados. | -| [F. Copyright & Política DMCA](#f-copyright-infringement-and-dmca-policy) | Esta sección explica la forma en la que GitHub responderá si crees que alguien está infringiendo tus derechos de autor en GitHub. | -| [G. Notificación de propiedad intelectual](#g-intellectual-property-notice) | Describe los derechos de GitHub en el sitio web y el servicio. | -| [H. Términos de la API](#h-api-terms) | Estas son las reglas para usar las API de GitHub, ya sea que estés usando la API para el desarrollo o la recopilación de datos. | -| [I. Términos de producto adicionales](#i-github-additional-product-terms) | Tenemos algunas reglas específicas para las características y productos de GitHub. | -| [J. Vista previa Beta](#j-beta-previews) | Estos son algunos de los términos adicionales que se aplican a las características de GitHub que continúan en desarrollo. | -| [K. Pago](#k-payment) | Eres responsable del pago. Somos responsables de facturarte con exactitud. | -| [L. Cancelación y terminación](#l-cancellation-and-termination) | Puedes cancelar este acuerdo y cerrar tu cuenta en cualquier momento. | -| [M. Comunicaciones con GitHub](#m-communications-with-github) | Sólo utilizamos el correo electrónico y otros medios electrónicos para estar en contacto con nuestros usuarios. No ofrecemos soporte telefónico. | -| [N. Exención de garantías](#n-disclaimer-of-warranties) | Proporcionamos nuestro servicio tal y como es y no hacemos promesas ni garantías sobre este servicio. **Lee esta sección cuidadosamente; deberías entender qué esperar.** | -| [O. Limitación de responsabilidad](#o-limitation-of-liability) | No seremos responsables de daños o pérdidas derivadas de tu uso o incapacidad para usar el servicio o de cualquier otra forma que surja en virtud de este acuerdo. **Lee esta sección cuidadosamente; esto limita nuestras obligaciones contigo.** | -| [P. Liberación e indemnización](#p-release-and-indemnification) | Eres completamente responsable de tu uso del servicio. | -| [Q. Cambios a estos Términos de Servicio](#q-changes-to-these-terms) | Podemos modificar este acuerdo, pero te notificaremos con 30 días de antelación sobre los cambios que afecten tus derechos. | -| [R. Varios](#r-miscellaneous) | Consulta esta sección para obtener detalles legales, incluyendo nuestra elección de la ley. | - -### Términos de servicio de GitHub -Fecha de entrada en vigencia: 2 de abril de 2020 - - -### A. Definiciones -**Versión resumida:** *Utilizamos estos términos básicos a lo largo del acuerdo y tienen significados específicos. Es necesario que comprendas el significado de cada uno de nuestros términos. No habrá una evaluación sobre ello, pero es información útil.* - -1. Una "Cuenta" representa tu relación legal con GitHub. Una "Cuenta de Usuario" representa la autorización individual del Usuario para iniciar sesión y utilizar el Servicio y sirve como identidad del Usuario en GitHub. “Organización” se refiere a un espacio de trabajo compartido que se puede asociar con una única entidad o con uno o más Usuarios donde múltiples Usuarios pueden colaborar en muchos proyectos a la vez. Una Cuenta de Usuario puede ser miembro de cualquier número de organizaciones. -2. El "Acuerdo" se refiere, colectivamente, a todos los términos, condiciones, avisos contenidos o a los que se hace referencia en el presente documento (los "Términos de Servicio" o los "Términos") y todas las demás reglas de funcionamiento, políticas (incluyendo la Declaración de Privacidad de GitHub, disponible en [github.com/site/privacy](https://github.com/site/privacy)) y procedimientos que podemos publicar de vez en cuando en el Sitio Web. La mayoría de nuestras políticas de sitio están disponibles en [docs.github.com/categories/site-policy](/categories/site-policy). -3. "Vistas Previas Beta" se refiere al software, los servicios o las características identificadas como alfa, beta, vista previa, acceso temprano o evaluación o a las palabras o frases con significados similares. -4. "Contenido" se refiere al contenido presentado o mostrado a través del sitio web, incluyendo, sin limitación al código, texto, datos, artículos, imágenes, fotografías, gráficos, software, aplicaciones, paquetes, diseños, características y otros materiales disponibles en el Sitio Web o disponibles de otra forma a través del Servicio. "Contenido" también incluye Servicios. “Contenido generado por el usuario” es Contenido, escrito o no, creado o cargado por nuestros Usuarios. "Tu Contenido" es Contenido que creas o posees. -5. “GitHub” y “Nosotros” se refieren a GitHub, Inc., así como a nuestros afiliados, directores, subsidiarios, contratistas, licenciadores, oficiales, agentes y empleados. -6. El “Servicio” se refiere a las aplicaciones, software, productos y servicios proporcionados por GitHub, incluyendo cualquier Vista Previa Beta. -7. “El Usuario”, “Tú” y “tu” se refieren a la persona, empresa u organización que ha visitado o está utilizando el Sitio Web o Servicio; que ingresa o utiliza cualquier parte de la Cuenta; o que dirije el uso de la Cuenta en el desempeño de sus funciones. Un usuario debe tener al menos 13 años de edad. Las condiciones especiales pueden aplicarse para cuentas empresariales o gubernamentales (véase [Section B(5): Términos Adicionales](#5-additional-terms)). -8. El "Sitio Web" se refiere al sitio web de GitHub ubicado en [github. om](https://github.com/) y todos los contenidos, servicios y productos proporcionados por GitHub en o a través del sitio web. También se refiere a subdominios propiedad de GitHub de github.com, tales como [education.github.com](https://education.github.com/) y [pages.github.com](https://pages.github.com/). Estos Términos también rigen los sitios web de la conferencia de GitHub, como [githubuniverse.com](https://githubuniverse.com/) y sitios web de productos, como [atom.io](https://atom.io/). Ocasionalmente, los sitios web propiedad de GitHub pueden proporcionar condiciones de servicio diferentes o adicionales. Si estos términos adicionales entran en conflicto con este Contrato, los términos más específicos se aplican a la página o servicio correspondiente. - -### B. Términos de la cuenta -**Versión resumida:** *Las Cuentas de Usuario y las Organizaciones tienen diferentes controles administrativos; una persona debe crear tu cuenta; debes tener 13 años o más; debes proporcionar una dirección de correo electrónico válida; y no es posible tener más de una cuenta gratuita. Eres el único responsable de tu Cuenta y de todo lo que ocurra mientras estas conectado o usando tu Cuenta. Eres responsable de mantener tu cuenta segura.* - -#### 1. Controles de la cuenta -- Usuarios. Sujeto a estos términos, conserva el control administrativo definitivo sobre tu cuenta de usuario y el Contenido dentro de ella. - -- Organizaciones. El "propietario" de una Organización que fue creada bajo estos Términos tiene el control administrativo final sobre esa Organización y el Contenido dentro de ella. Dentro del Servicio, un propietario puede administrar el acceso del Usuario a los datos y proyectos de la Organización. Una Organización puede tener múltiples propietarios, pero debe haber al menos una Cuenta de Usuario designada como propietario de una Organización. Si eres el propietario de una Organización bajo estos términos, te consideramos responsable de las acciones que se llevan a cabo en o a través de dicha Organización. - -#### 2. Información requerida -Debes proporcionar una dirección de correo electrónico válida para completar el proceso de registro. Cualquier otra información solicitada, como tu nombre real, es opcional, a menos que aceptes estos términos en nombre de una entidad legal (en cuyo caso necesitamos más información sobre la entidad legal) o si optas por una [Cuenta de pago](#k-payment), en cuyo caso será necesaria información adicional para fines de facturación. - -#### 3. Requisitos de la cuenta -Tenemos unas cuantas reglas simples para cuentas de usuario en el servicio de GitHub. -- Debes ser una persona para crear una cuenta. No se permiten las cuentas que registren ni los "bots", ni otros métodos automatizados. Permitimos cuentas de máquina: -- Una cuenta de máquina se refiere a una cuenta registrada por una persona que acepta los términos aplicables del servicio en nombre de la Cuenta, proporciona una dirección de correo electrónico válida y es responsable de sus acciones. Una Cuenta de máquina se usa exclusivamente para ejecutar tareas automatizadas. Múltiples usuarios pueden dirigir las acciones de una cuenta de máquina, pero el propietario de la cuenta es responsable en última instancia de las acciones de la máquina. No puedes mantener más de una cuenta de máquina gratuita además de tu cuenta de usuario gratuita. -- Una persona o entidad legal no puede mantener más de una cuenta gratuita (si también decide controlar una cuenta de máquina, está bien, pero sólo se puede utilizar para ejecutar una máquina). -- Debes ser mayor de 13 años. Si bien estamos encantados de ver a los geniales programadores jóvenes entusiasmados aprendiendo a programar, debemos cumplir con la ley de los Estados Unidos. GitHub no dirige nuestro Servicio a niños menores de 13 años y no permitimos ningún Usuario menor de 13 años en nuestro Servicio. Si tenemos conocimiento de algún usuario menor de 13 años, [daremos por terminada inmediatamente la cuenta del usuario](#l-cancellation-and-termination). Si estás ubicado en un país fuera de los Estados Unidos, la edad mínima de ese país puede ser mayor; en ese caso, el Cliente es responsable de cumplir con las leyes de ese país. -- Su inicio de sesión sólo puede usarse por una persona — es decir, un único inicio de sesión no puede ser compartido por varias personas. Una Organización de pago sólo puede proporcionar acceso a tantas cuentas de usuario como su suscripción lo permita. -- No puedes usar GitHub en violación de las leyes de control de exportación o sanciones de los Estados Unidos o de cualquier otra jurisdicción aplicable. No puedes usar GitHub si estás trabajando o en nombre de un [Nacional Especialmente Diseñado (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) o una persona sujeta a prohibiciones similares de bloqueo o denegadas por una agencia gubernamental de EE. UU. government agency. GitHub puede permitir que personas en ciertos países o territorios sancionados accedan a ciertos servicios de GitHub de conformidad con las autorizaciones del gobierno de los Estados Unidos. government authorizations. Para obtener más información, consulta nuestra[Política de Controles de Exportación](/articles/github-and-export-controls). - -#### 4. Seguridad de la cuenta de usuario -Eres responsable de mantener tu Cuenta segura mientras utilizas nuestro Servicio. Ofrecemos herramientas como autenticación de dos factores para ayudarte a mantener la seguridad de tu cuenta pero el contenido de tu Cuenta y su seguridad depende de ti. -- Eres responsable de todo el contenido publicado y la actividad que se produzca bajo tu Cuenta (incluso cuando el contenido sea publicado por otros que tienen Cuentas bajo tu Cuenta). -- Eres responsable de mantener la seguridad de tu cuenta y contraseña. GitHub no será responsable de ninguna pérdida o daño que surja del incumplimiento de esta obligación de seguridad. -- Debes notificar inmediatamente [a GitHub](https://support.github.com/contact) si tienes conocimiento de cualquier uso no autorizado, o acceso a nuestro Servicio a través de tu Cuenta, incluyendo cualquier uso no autorizado de tu contraseña o Cuenta. - -#### 5. Términos adicionales -En algunas situaciones, pueden aplicarse términos de terceros a tu uso de GitHub. Por ejemplo, puedes ser miembro de una Organización en GitHub con tus propios términos o acuerdos de licencia; puedes descargar una aplicación que se integre con GitHub; o puedes usar el Servicio para autenticarte a otro servicio. Ten en cuenta que aunque estos Términos son nuestro acuerdo total contigo, los términos de otras partes rigen sus relaciones contigo. - -Si eres un usuario del gobierno o de otro modo accedes o utilizas cualquier servicio de GitHub en una capacidad gubernamental, esta [Enmienda del Gobierno a los Términos de Servicio de GitHub](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) aplican para ti y debes aceptar sus disposiciones. - -Si te registraste en la nube GitHub Enterprise, la [ Apéndice Enterprise Cloud ](/articles/github-enterprise-cloud-addendum/) aplica para ti y debes aceptar sus disposiciones. - -### C. Uso aceptable -**Versión simplificada:** *GitHub presenta una amplia variedad de proyectos en equipo en todo el mundo y dicha cooperación solamente funciona cuando nuestros usuarios pueden trabajar juntos con buenas intenciones. Mientras usas el Servicio, debes cumplir con los términos de esta sección, que incluyen algunas restricciones sobre el contenido que puedes publicar, que realizar en el servicio y otras limitaciones. En síntesis, la idea es que sean geniales entre sí.* - -Tu uso del sitio web y del servicio no debe violar ninguna ley aplicable, incluyendo leyes de derechos de autor o de marcas, leyes de control de exportación o sanciones, u otras leyes de su jurisdicción. Eres responsable de asegurarte que tu uso del Servicio cumpla con las leyes y cualquier normativa aplicable. - -Aceptas que en ningún caso violarás nuestras [Políticas de uso aceptable](/articles/github-acceptable-use-policies) o [Directrices de la comunidad](/articles/github-community-guidelines). - -### D. Contenido generado por el usuario -/**Versión resumida+*:** *Eres propietario del contenido que creas, pero nos permitirás ciertos derechos para que podamos mostrar y compartir el contenido que publiques. Continúas teniendo el control sobre tu contenido y responsabilidad por el mismo y los derechos que nos concedes están limitados a aquellos que necesitamos para proporcionar el servicio. Tenemos derecho a eliminar el contenido o cerrar cuentas si lo necesitamos.* - -#### 1. Responsabilidad para el Contenido generado por el usuario -Puedes crear o cargar Contenido generado por el Usuario mientras usas el Servicio. Eres el único responsable del contenido y por cualquier daño que resulte de cualquier Contenido generado por el Usuario que publiques, cargues, enlaces o que de otra forma esté disponible a través del Servicio, independientemente de la forma de dicho Contenido. No eres responsable de ninguna visualización pública o uso indebido del Contenido generado por el Usuario. - -#### 2. GitHub puede eliminar contenido -No pre-seleccionamos el Contenido generado por el Usuario, pero tenemos el derecho (aunque no la obligación) de rechazar o eliminar cualquier contenido generado por el usuario que, a nuestra sola discreción, viole cualquier [condición o política de GitHub](/github/site-policy). - -#### 3. Propiedad del Contenido, Derecho a publicar y Otorgamientos de licencia -Conservas la propiedad y la responsabilidad de tu contenido. Si estás publicando algo que no hayas creado tu mismo o de lo cual no posees los derechos, aceptas que eres responsable de cualquier Contenido que publiques; que sólo enviarás contenido que tengas derecho a publicar; y que cumplirás plenamente con cualquier licencia de terceros relacionada con el Contenido que publiques. - -Ya que conservas la propiedad y la responsabilidad de tu contenido, necesitamos que nos concedas — y a otros usuarios de GitHub — ciertos permisos legales, listados en las Secciones D. — D.7. Estas licencias se aplican a Tu Contenido. Si cargas Contenido que ya viene con una licencia que le otorga a GitHub los permisos que necesita para ejecutar el Servicio, no se requiere ninguna licencia adicional. Debes comprender que no recibirás ningún pago por ninguno de los derechos otorgados en las Secciones D.4 — D.7. Las licencias que nos concedes terminarán cuando retires Tu Contenido de nuestros servidores, a menos que otros Usuarios lo hayan bifurcado. - -#### 4. Licencia otorgada -Necesitamos el derecho legal de hacer cosas como alojar Tu Contenido, publicarlo y compartirlo. Nos concedes y a nuestros sucesores legales el derecho a almacenar, analizar y mostrar tu contenido, y hacer copias incidentales según sea necesario para prestar el Sitio Web y prestar el Servicio. Esto incluye el derecho a hacer cosas como copiarlo a nuestra base de datos y hacer copias de seguridad; mostrártelo y mostrarlo a otros usuarios; analizarlo en un índice de búsqueda o analizarlo en nuestros servidores; compartirlo con otros usuarios; y ejecutarlo, en caso de que Tu Contenido sea algo como música o vídeo. - -Esta licencia no le otorga a GitHub el derecho a vender Tu Contenido o de otra forma distribuirlo o utilizarlo por fuera de nuestra prestación del Servicio. - -#### 5. Otorgamiento de la licencia a otros Usuarios -Cualquier contenido generado por el usuario que postees públicamente, incluyendo temas, comentarios y contribuciones a los repositorios de otros usuarios, puede ser visto por otros. Al configurar tus repositorios para ser vistos públicamente, aceptas permitir a otros ver y "bifurcar" tus repositorios (esto significa que otros pueden hacer sus propias copias de Contenido de tus repositorios en los repositorios que controlan). - -Si configuras tus páginas y repositorios para ser vistos públicamente, estás otorgando a cada usuario de GitHub una licencia no exclusiva a nivel mundial para usar, mostrar, y reproducir Tu Contenido a través del Servicio de GitHub y para reproducir Tu Contenido únicamente en GitHub según lo permitido a través de la funcionalidad de GitHub (por ejemplo, a través de bifurcación). Puedes otorgar derechos adicionales si [adoptas una licencia](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Si estás cargando Contenido que no creaste ni posees, eres responsable de asegurar que el Contenido del Cliente que carga cuente con licencia conforme a los términos que otorgan estos permisos a los Usuarios externos. - -#### 6. Contribuciones conforme a la Licencia del repositorio -Siempre que hagas una contribución a un repositorio que contenga un aviso de licencia, estás autorizando tu contribución conforme a los mismos términos y aceptas que tienes derecho a licenciar dicha contribución conforme a esos términos. Si tienes otro acuerdo para licenciar tus contribuciones conforme a términos diferentes, tal como un acuerdo de licencia de colaborador, ese acuerdo prevalecerá. - -¿No es así justo como funciona ahora? Sí. Esto se acepta ampliamente como la norma en la comunidad de código abierto; se conoce comúnmente por el abreviado "inbound=outbound". Lo estamos haciendo explícito. - -#### 7. Derechos morales -Conservas todos los derechos morales sobre Tu Contenido que cargas, publicas o envías a cualquier parte del Servicio, incluyendo los derechos de integridad y atribución. Sin embargo, renuncias a estos derechos y aceptas no ejercerlos contra nosotros para ejercer razonablemente los derechos otorgados en la Sección D.4, pero no de otra manera. - -En la medida en que este acuerdo no sea exigible por la legislación aplicable, concedes a GitHub los derechos que necesitamos para usar Tu Contenido sin atribución y para hacer adaptaciones razonables de Tu Contenido según sea necesario para prestar el Sitio Web y el Servicio. - -### E. Repositorios privados -**Versión resumida:** *Puedes tener acceso a repositorios privados. Tratamos el contenido de los repositorios privados como confidencial y sólo accedemos a él por razones de soporte, con tu consentimiento o si es necesario por razones de seguridad.* - -#### 1. Control de repositorios privados -Algunas cuentas pueden tener repositorios privados, que permiten al Usuario controlar el acceso al Contenido. - -#### 2. Control de repositorios privados -GitHub considera que el contenido de los repositorios privados es confidencial para ti. GitHub protegerá el contenido de los repositorios privados del uso no autorizado, el acceso, o divulgación de la misma manera que utilizaríamos para proteger nuestra propia información confidencial de naturaleza similar y, en ningún caso, con un grado de atención más razonable. - -#### 3. Acceso -El personal de GitHub solo puede acceder al contenido de tus repositorios privados en las siguientes situaciones: -- Con su consentimiento y conocimiento, por razones de soporte. Si GitHub ingresa a un repositorio privado por razones de soporte, sólo lo haremos con el consentimiento y el conocimiento del propietario. -- Cuando se requiere acceso por razones de seguridad, incluyendo cuando se requiere acceso para mantener la confidencialidad, integridad, disponibilidad y resistencia continua de los sistemas y el Servicio de GitHub. - -Puedes decidir habilitar acceso adicional a tus repositorios privados. Por ejemplo: -- Puedes habilitar diversos servicios o funciones de GitHub que requieren derechos adicionales sobre Tu Contenido en los repositorios privados. Estos derechos pueden variar dependiendo del servicio o función, pero GitHub continuará tratando su contenido de repositorio privado como confidencial. Si estos servicios o características requieren derechos además de aquellos que necesitamos para proporcionar el servicio de GitHub, le daremos una explicación sobre esos derechos. - -#### 4. Exclusiones -Si tienes razones para creer que el contenido de un repositorio privado incumple la ley o de estos Términos, tenemos el derecho de ingresar, revisar y eliminar dicho contenido. Además, podemos estar [obligados por ley](/github/site-policy/github-privacy-statement#for-legal-disclosure) a divulgar el contenido de tus repositorios privados. - -### F. Violación de la propiedad intelectual y la política de DMCA -Si crees que el contenido de nuestro sitio web viola tus derechos de autor, por favor contáctanos de acuerdo con nuestra [Política sobre la Ley de Derechos de Autor Digital del Milenio](/articles/dmca-takedown-policy/). Si eres propietario de derechos de autor y consideras que el contenido en GitHub viola tus derechos, por favor contáctanos a través de [nuestro sencillo formulario DMCA](https://github.com/contact/dmca) o enviando un correo electrónico a copyright@github.com. Puede haber consecuencias legales por enviar un aviso de sumisión falso o poco serio. Antes de enviar una solicitud de sumisión, debes considerar usos legales tales como uso justo y usos autorizados. - -Cancelaremos las Cuentas de [infractores insistentes](/articles/dmca-takedown-policy/#e-repeated-infringement) de esta política. - -### G. Notificación de propiedad intelectual -**Versión resumida:** *Somos dueños del servicio y de todo nuestro contenido. Para que puedas utilizar nuestro contenido, te damos ciertos derechos, pero sólo puedes utilizar nuestro contenido de la forma que lo hemos permitido.* - -#### 1. Derechos de GitHub sobre el Contenido -GitHub y nuestros licenciatarios, vendedores, agentes y/o nuestros proveedores de contenidos conservan la propiedad de todos los derechos de propiedad intelectual de cualquier tipo relacionados con el Sitio Web y el Servicio. Nos reservamos todos los derechos que no se le conceden expresamente en virtud de este Acuerdo o por ley. La apariencia del Sitio Web y el Servicio es propiedad intelectual de GitHub, Inc. Todos los derechos reservados. No puedes duplicar, copiar o volver a usar ninguna parte de los elementos o conceptos de HTML/CSS, Javascript o de diseño visual sin autorización expresa por escrito de GitHub. - -#### 2. Nombres comerciales y logos de GitHub -Si deseas usar las marcas registradas de GitHub, debes seguir todas nuestras directrices de marca registrada, incluyendo las que aparecen en nuestra página de logos: https://github.com/logos. - -#### 3. Licencia a políticas de GitHub -La presente Declaración de privacidad está autorizada conforme a esta [licencia de Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para obtener más detalles, consulta nuestro [repositorio de políticas del sitio](https://github.com/github/site-policy#license). - -### H. Términos de la API -**Versión resumida:** *Aceptas estos términos de servicio, además de esta sección H, al usar cualquiera de las API de GitHub (Interfaz del Proveedor de la Aplicación), incluyendo el uso de la API a través de un producto de terceros que ingresa a GitHub.* - -Las solicitudes abusivas o excesivamente frecuentes a GitHub a través de la API pueden resultar en la suspensión temporal o permanente del acceso de tu Cuenta a la API. GitHub, a nuestra sola discreción, determinará el abuso o el uso excesivo de la API. Intentaremos avisarte por correo electrónico antes de la suspensión. - -No puedes compartir tokens API para exceder las limitaciones de velocidad de GitHub. - -No puedes utilizar la API para descargar datos o Contenido de GitHub con fines de spamming, incluyendo el propósito de vender la información personal de los usuarios de GitHub, tales como reclutadores, cazatalentos y bolsas de trabajo. - -Todo uso de la API de GitHub está sujeto a estos términos de servicio y a la [Declaración de privacidad de GitHub](https://github.com/site/privacy). - -GitHub puede ofrecer acceso basado en suscripción a nuestra API para aquellos usuarios que requieren acceso de alto rendimiento o acceso que resultaría en reventa del servicio de GitHub. - -### I. Términos adicionales de los productos de GitHub -**Versión resumida:** *Debes seguir ciertos términos y condiciones específicos para las diversas características y productos de GitHub y aceptas los Términos y Condiciones Suplementarios cuando estés de acuerdo con este Contrato.* - -Algunas características del servicio pueden estar sujetas a términos adicionales específicos de esa característica o producto según lo establecido en los términos adicionales del producto de GitHub. Al ingresar o utilizar los Servicios, también aceptas los [Términos de adicionales del producto de GitHub](/github/site-policy/github-additional-product-terms). - -### J. Vista previa Beta -**Versión resumida:** *Las vistas previas Beta no pueden ser soportadas o pueden cambiar en cualquier momento, puedes recibir información confidencial a través de aquellos programas que deben permanecer confidenciales mientras el programa es privado y nos encantaría tener tu opinión para mejorar nuestras Vistas Previas Beta.* - -#### 1. Sujeto a cambio - -Las Vistas previas Beta pueden no ser compatibles y pueden cambiarse en cualquier momento sin previo aviso. Además, las Vistas Previas Beta no están sujetas a las mismas medidas de seguridad y de auditoría a las que se encuentra sujeto el Servicio. **Al hacer uso de una Vista Previa beta, la estás utilizando bajo tu propio riesgo.** - -#### 2. Confidentiality - -Como usuario de las Vistas Previas Beta, puedes tener acceso a información especial que no está disponible para el resto del mundo. Debido a la naturaleza delicada de esta información, es importante que nos aseguremos que mantengas esa información en secreto. - -**Obligaciones de confidencialidad.** Aceptas que cualquier información no pública de Vista Previa Beta que te proporcionamos, como información sobre una vista previa privada Beta, se considerará información confidencial de GitHub (colectivamente, “Información Confidencial”), independientemente de si está marcada o identificada como tal. Aceptas usar dicha Información Confidencial únicamente para el propósito expreso de probar y evaluar la Vista Previa Beta (el “Propósito”) y para ningún otro propósito. Debes tener el mismo cuidado que con tu propia información confidencial pero no menos de las precauciones razonables para prevenir cualquier uso no autorizado, revelación, publicación o divulgación de nuestra Información Confidencial. Te comprometes a no revelar, publicar o divulgar ninguna Información Confidencial a terceros a menos que no prohibamos o restrinjamos dicha divulgación (por ejemplo, puede ser parte de una discusión de grupo organizada por GitHub acerca de una característica de la Vista Previa Beta). - -**Excepciones.** La Información Confidencial no incluirá información que: (a) sea o esté disponible públicamente sin violación de este Contrato a través de ningún acto o inacción por su parte (como cuando una Vista Previa Beta privada se convierte en una Vista Previa Beta pública); (b) conozcas antes de que lo divulguemos; (c) esté desarrollada independientemente por ti sin violación de ninguna obligación de confidencialidad con nosotros o con terceros; o (d) sea revelada con permiso de GitHub. No violarás los términos de este Acuerdo si se te pide revelar Información Confidencial de acuerdo con el funcionamiento de la ley, siempre y cuando GitHub haya recibido un aviso por escrito razonable para objetar, a menos que la ley lo prohíba. - -#### 3. Comentarios - -Siempre estamos tratando de mejorar los productos y servicios y tus comentarios como usuario de las Vistas Previas Beta nos ayudarán a hacerlo. Si decides darnos cualquier idea, conocimiento, algoritmos, contribuciones de código, sugerencias, solicitudes de mejora, recomendaciones o cualquier otro comentario para nuestros productos o servicios (colectivamente, "Comentarios"), reconoces y aceptas que GitHub tendrá una licencia sin cargo de regalías completamente pagada, mundial, transferible, irrevocable para implementar, usar, modificar, explotar comercialmente y/o incorporar los Comentarios en nuestros productos, servicios y documentación. - -### K. Pago -**Versión resumida:** *Eres responsable de cualquier cargo asociado con tu uso de GitHub. Somos responsables de comunicarte esos cobros con claridad y precisión y de hacerte saber con mucha antelación si esos precios cambian.* - -#### 1. Precios -Nuestros precios y términos de pago están disponibles en [github.com/pricing](https://github.com/pricing). Si aceptas un precio de suscripción, ese seguirá siendo tu precio durante la duración del plazo de pago; sin embargo, los precios están sujetos a cambios al final de un plazo de pago. - -#### 2. Mejoras, descensos y cambios -- Te cobraremos inmediatamente cuando pase del plan gratuito a cualquier plan de pago. -- Si cambias de un plan de facturación mensual a un plan de facturación anual, GitHub te cobrará por un año completo en la próxima fecha de facturación mensual. -- Si mejoras a un mayor nivel de servicio, te cobraremos el plan actualizado inmediatamente. -- Puedes cambiar tu nivel de servicio en cualquier momento [eligiendo una opción de plan](https://github.com/pricing) o entrando a tu [configuración de facturación](https://github.com/settings/billing). Si decides bajar la categoría de tu Cuenta, puedes perder el acceso al Contenido, características o capacidad de tu Cuenta. Consulta nuestra sección sobre [Cancelación](#l-cancellation-and-termination) para obtener información sobre cómo obtener una copia de ese contenido. - -#### 3. Programación de facturación; no reembolsos -**Pago basado en el plan** para planes de pago mensuales o anuales, el Servicio se cobra con antelación de forma mensual o anual respectiva y no es reembolsable. No habrá reembolsos o créditos Para meses parciales de servicio, reembolsos o reembolsos durante meses sin usar con una cuenta abierta; sin embargo, el servicio permanecerá activo durante el período de facturación pagado. Para tratar a todos por igual, no se harán excepciones. - -**Pago basado en el uso** Algunas funciones de servicio se facturan según su uso. Una cantidad limitada de estas características del Servicio puede incluirse en su plan por un período limitado sin cargo adicional. Si decides comprar características de Servicio pagadas más allá de la cantidad incluida en tu plan, pagarás por estas funciones del Servicio con base en tu uso real en el mes anterior. El pago mensual de estas compras se cobrará de forma periódica en mora. Consulte los [Términos adicionales del producto de GitHub para conocer más detalles](/github/site-policy/github-additional-product-terms). - -**Facturación** Para usuarios facturados, el usuario acepta pagar los cobros en su totalidad, por adelantado sin deducción ni saldar cuentas de ningún tipo, en dólares americanos. estadounidenses. El usuario debe pagar las cuotas dentro de treinta (30) días a partir de la fecha de facturación de GitHub. Los importes pagaderos en virtud de este Acuerdo no son reembolsables, excepto que se estipule de otro modo en este Acuerdo. Si el usuario no paga las cuotas a tiempo, GitHub se reserva el derecho, además de tomar cualquier otra acción conforme a derecho o equidad, a (i) cobrar intereses sobre importes vencidos en 1.0% al mes o el tipo de interés más alto permitido por la ley, el que sea menor y a cobrar todos los gastos de recuperación y (ii) cancelar el formulario de pedido aplicable. El usuario es el único responsable de todos los impuestos, tarifas, obligaciones y valoraciones gubernamentales (a excepción de los impuestos basados en los ingresos netos de GitHub) que se imponen o vencen en relación con el presente Acuerdo. - -#### 4. Autorización -Al aceptar estos términos, nos das permiso para hacer un cargo a tu tarjeta de crédito en el archivo Cuenta de PayPal, u otros métodos de pago aprobados para los cobros que autorizas para GitHub. - -#### 5. Responsabilidad de pago -Eres responsable de todas las cuotas, incluyendo los impuestos, asociados con tu uso del Servicio. Al utilizar el Servicio, aceptas pagar a GitHub cualquier cobro incurrido en relación con tu uso del Servicio. Si impugnas el asunto, ponte en contacto con [el soporte de GitHub](https://support.github.com/contact). Eres responsable de proporcionarnos un medio de pago válido para las pagar las Cuentas. Las cuentas gratuitas no están obligadas a proporcionar información de pago. - -### L. Cancelación y terminación -**Versión resumida:** *Puedes cerrar tu Cuenta en cualquier momento. Si lo haces, trataremos tu información de forma responsable.* - -#### 1. Cancelación de la cuenta -Es tu responsabilidad cancelar correctamente tu cuenta con GitHub. Puedes [cancelar tu cuenta en cualquier momento](/articles/how-do-i-cancel-my-account/) entrando a tu Configuración en la barra de navegación global en la parte superior de la pantalla. La pantalla de la Cuenta proporciona un enlace simple y sin preguntas de cancelación. No podemos cancelar Cuentas en respuesta a una solicitud de correo electrónico o teléfono. - -#### 2. Tras la cancelación -Conservaremos y usaremos tu información cuando sea necesario para cumplir con nuestras obligaciones legales, resolver disputas y hacer cumplir nuestros acuerdos, pero sin requerimientos legales, borraremos tu perfil completo y el Contenido de tus repositorios dentro de los 90 días posteriores a la cancelación o terminación (aunque es posible que permanezca alguna información en las copias de seguridad cifradas). Esta información no se puede recuperar una vez que su cuenta sea cancelada. - -No eliminaremos el contenido con el que hayas contribuido a los repositorios de otros usuarios o que otros usuarios hayan bifurcado. - -Si se solicita, haremos un esfuerzo razonable para proporcionar al propietario de una cuenta una copia de los contenidos legales, no infringido de la Cuenta después de la cancelación, terminación o descenso de categoría. Debes hacer esta solicitud dentro de los 90 días siguientes a la cancelación, terminación o descenso de categoría. - -#### 3. GitHub pueder rescindir -GitHub tiene derecho a suspender o rescindir tu acceso a todas o a cualquier parte del sitio web en cualquier momento con o sin causa, con o sin previo aviso, efectivo inmediatamente. GitHub se reserva el derecho de denegar el servicio a cualquier persona por cualquier motivo en cualquier momento. - -#### 4. Continuidad -Todas las disposiciones de este Acuerdo que, por su naturaleza, deben sobrevivir a la terminación *sobrevivirán* la terminación — incluyendo, sin limitación: Disposiciones de propiedad, exenciones de garantía, indemnización y limitaciones de responsabilidad. - -### M. Comunicaciones con GitHub -**Versión resumida:** *Utilizamos correo electrónico y otros medios electrónicos para mantenernos en contacto con nuestros usuarios.* - -#### 1. Comunicación electrónica requerida -Para propósitos contractuales, (1) otorgarás tu consentimiento para recibir nuestras comunicaciones en forma electrónica a través de la dirección de correo electrónico que ingresaste o a través del Servicio; y (2) aceptarás que todos los Términos de Servicio, acuerdos, avisos, revelaciones, y otras comunicaciones que le proporcionamos electrónicamente satisfacen cualquier requisito legal que dichas comunicaciones satisfagan si estuvieran en papel. Esta sección no afecta tus derechos no renunciables. - -#### 2. El aviso legal para GitHub debe ser por escrito -Las comunicaciones realizadas a través del correo electrónico o el sistema de mensajería de soporte de GitHub no constituirán un aviso legal a GitHub ni a ninguno de sus oficiales, empleados, agentes o representantes en cualquier situación en la que el aviso a GitHub se requiera por contrato o cualquier ley o reglamento. El aviso legal a GitHub debe ser por escrito y [presentado al agente legal de GitHub](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests). - -#### 3. Sin soporte telefónico -GitHub sólo ofrece soporte por correo electrónico, comunicaciones en el servicio y mensajes electrónicos. No ofrecemos soporte telefónico. - -### N. Exención de garantías -**Versión resumida:** *Proporcionamos nuestro servicio tal y como es y no hacemos promesas ni garantías sobre este servicio. Lee esta sección cuidadosamente; deberías entender qué esperar.* - -GitHub proporciona el sitio web y el servicio “tal cual” y “según disponibilidad”, sin garantía de ningún tipo. Sin perjuicio de esto, renunciamos expresamente a todas las garantías, ya sean explícitas, implícitas o reglamentarias, respecto al Servicio Web y el Servicio incluyendo entre otras cualquier garantía implícita de comercialización, idoneidad para un propósito en particular, título, seguridad, precisión y de no incumplimiento. - -GitHub no garantiza que los Servicios cumplan con tus requisitos; que el Servicio no se interrumpa y sea oportuno, seguro o sin errores; que la información que se provee a través de los Servicios sea precisa, confiable o correcta; que cualquier defecto o error será corregido; que el Servicio estará disponible en cualquier momento o ubicación en particular; o que el Servicio se encuentra libre de virus u otros componentes dañinos. Asumes toda la responsabilidad y el riesgo de pérdida resultante de su descarga y/o uso de archivos, información, contenido u otro material obtenido del Servicio. - -### O. Limitación de responsabilidad -**Versión resumida:** *No seremos responsables de daños o pérdidas derivadas de tu uso o incapacidad para usar el servicio o de cualquier otra forma que surja en virtud de este acuerdo. Lee esta sección cuidadosamente; esto limita nuestras obligaciones contigo.* - -Comprendes y aceptas que no seremos responsables ante ti o ante ningún tercero por ninguna pérdida de ganancias, uso, buena voluntad, o datos, o para cualquier daño accidental, indirecto, especial, consecuencial o exemplatorio, que surjan sin embargo de - -- el uso, divulgación o visualización de tu contenido generado por el usuario; -- tu uso o incapacidad para usar el Servicio; -- cualquier modificación, cambio de precios, suspensión o interrupción del Servicio; -- el Servicio generalmente o el software o sistemas que hacen el Servicio disponible; -- acceso no autorizado a o alteraciones de tus transmisiones o datos; -- declaración o conducta de cualquier tercero en el Servicio; -- cualquier otra interacción de usuario que introduzca o reciba a través del uso del Servicio; o -- cualquier otro asunto relacionado con el Servicio. - -Nuestra responsabilidad es limitada, ya sea que hayamos sido informados o no de la posibilidad de tales daños, e incluso si se descubre que un remedio establecido en este Acuerdo no ha cumplido su propósito esencial. No nos responsabilizaremos por ningún fallo o retraso debido a asuntos que escapen a nuestro control razonable. - -### P. Liberación e indemnización -**Versión resumida:** *Eres responsable de tu uso del servicio. Si dañas a otra persona o entras en una disputa con otra persona, no estaremos implicados.* - -Si tienes una disputa con uno o más usuarios, aceptas liberar a GitHub de todos y cada uno de los reclamos, demandas y daños (reales y consecuentes) de todo tipo y naturaleza, conocidos y desconocidos, que surjan de o de cualquier forma relacionados con tales disputas. - -Aceptas indemnizarnos, defendernos y liberarnos de toda responsabilidad contra cualquier reclamación, responsabilidad y gastos, incluyendo los honorarios de abogados, derivados del uso del Sitio Web y del Servicio, incluyendo sin limitación a tu violación de este Acuerdo, considerando que GitHub (1) te dé un aviso por escrito de la reclamación, demanda, juicio o procedimiento; (2) te da control exclusivo de la defensa y resolución de reclamaciones, demanda, juicio o diligencia (siempre y cuando no pueda solucionar ninguna reclamación, demanda, juicio o diligencia, a menos que el acuerdo libere incondicionalmente a GitHub de toda responsabilidad); y (3) te proporcione toda la asistencia razonable, a su cargo. - -### Q. Modificaciones a estos términos -**Versión resumida:** *Desamos que nuestros usuarios estén informados sobre los cambios importantes en nuestros términos, pero algunos cambios no son tan importantes — no queremos molestarte cada vez que arreglamos un error tipográfico. Así que mientras podamos modificar este acuerdo en cualquier momento, notificaremos a los usuarios de cualquier cambio que afecte a sus derechos y te daremos tiempo para ajustarte a ellos.* - -Nos reservamos el derecho, a nuestro exclusivo criterio, de modificar el presente Acuerdo en cualquier momento y actualizaremos este Acuerdo en el caso en que ocurran dichas modificaciones. Notificaremos a nuestros Usuarios sobre los cambios sustanciales al presente Acuerdo, tales como cambios en los precios, al menos 30 días antes de que el cambio entre en vigencia publicando un aviso en el Servicio. Para modificaciones no sustanciales, el uso continuo del Servicio por parte del Cliente representa la aceptación de nuestras revisiones sobre el presente Acuerdo. Puedes visualizar todas las modificaciones a estos Términos en nuestro repositorio [Site Policy](https://github.com/github/site-policy)-. - -Nos reservamos el derecho en cualquier momento y de vez en cuando de modificar o interrumpir, temporal o permanentemente, el Sitio Web (o cualquier parte de este) con o sin notificación. - -### R. Varios - -#### 1. Legislación aplicable -Excepto en la medida en que la ley aplicable establezca lo contrario, este Acuerdo entre tu persona y GitHub y cualquier acceso o uso del Sitio Web o del Servicio se rige por las leyes federales de los Estados Unidos de América y las leyes del Estado de California, sin tener en cuenta el conflicto de disposiciones legales. Tú y GitHub acuerdan someterse a la jurisdicción exclusiva y sede de los tribunales ubicados en la Ciudad y el Condado de San Francisco, California. - -#### 2. Intransferible -GitHub puede asignar o delegar estos Términos de Servicio y/o la [Declaración de privacidad de GitHub](https://github.com/site/privacy), en su totalidad o en parte, a cualquier persona o entidad en cualquier momento con o sin tu consentimiento, incluyendo la concesión de licencia en la Sección D.4. No puedes asignar ni delegar ningún derecho u obligación bajo los Términos de Servicio o Declaración de Privacidad sin nuestro previo consentimiento por escrito y ninguna asignación no autorizada y delegación por ti es nula. - -#### 3. Encabezados y resúmenes de sección -A lo largo de este Acuerdo, cada sección incluye títulos y breves resúmenes de los siguientes términos y condiciones. Estos títulos de sección y breves resúmenes no son legalmente vinculantes. - -#### 4. Divisibilidad, sin exención y supervivencia -Si alguna parte de este Acuerdo es considerada inválida o no aplicable, esa parte del Acuerdo será interpretada para reflejar la intención original de las partes. Las partes restantes permanecerán en pleno vigor y efecto. Cualquier incumplimiento por parte de GitHub para hacer cumplir cualquier disposición de este Acuerdo no será considerado una renuncia a nuestro derecho a hacer cumplir dicha disposición. Nuestros derechos en virtud de este Acuerdo sobrevivirán a cualquier rescisión de este Acuerdo. - -#### 5. Enmiendas, acuerdo completo -Este Acuerdo sólo puede modificarse por una enmienda por escrito firmada por un representante autorizado de GitHub o por la publicación de GitHub de una versión revisada de acuerdo con la sección [Q. Cambios a estos términos](#q-changes-to-these-terms). Estos Términos de Servicio, junto con la Declaración de Privacidad de GitHub, representan la declaración completa y exclusiva del acuerdo entre tu persona y nosotros. Este Acuerdo sustituye cualquier propuesta o acuerdo previo oral o escrito, y cualquier otra comunicación entre tu persona y GitHub relacionada con el tema de estos términos, incluyendo cualquier acuerdo de confidencialidad o no divulgación. - -#### 6. Preguntas -¿Preguntas sobre los Términos de Servicio? [Contáctanos](https://support.github.com/contact). diff --git a/translations/es-XL/content/github/site-policy/github-trademark-policy.md b/translations/es-XL/content/github/site-policy/github-trademark-policy.md deleted file mode 100644 index 39083842ef..0000000000 --- a/translations/es-XL/content/github/site-policy/github-trademark-policy.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Política de marca registrada de GitHub -redirect_from: - - /articles/github-trademark-policy -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -### ¿Qué es una Violación de la Política de Marcas de GitHub? - -Utilizar el nombre de una empresa o negocio, logotipo, u otros materiales protegidos por marca registrada de una manera que pueda inducir a un error o confundir a otros con respecto a su marca o afiliación comercial pueden considerarse una violación de la política de marcas registradas. - -### ¿Qué no es una Violación de la Política de Marcas de GitHub? - -El uso de la marca de otro de una manera que no tenga nada que ver con el producto o servicio para el que se concedió la marca no es una violación de la política de marcas registradas. Los nombres de usuario de GitHub están disponibles en una base de primera vez, en el orden de solicitud y no se pueden reservar. Una cuenta de GitHub con un nombre de usuario que resulte ser la misma que una marca registrada no es, por sí mismo, necesariamente una violación de nuestra política de marcas. - -### ¿Cómo responde GitHub al reporte de las Violaciones de Política de Marcas? - -Cuando recibimos reportes de violaciones de la política de marcas registradas por parte de titulares de registros de marcas federales o internacionales, revisamos la cuenta y podemos tomar las siguientes acciones: - -* Cuando exista una intención clara de engañar a otros a través del uso no autorizado de una marca, GitHub suspenderá la cuenta y notificará al titular de la misma. -* Cuando determinamos que una cuenta parece estar confundiendo a los usuarios, pero no se hace pasar de manera intencional como el bien o servicio con marca registrada, le damos al titular de la cuenta la oportunidad de aclarar cualquier posible confusión. También podemos lanzar un nombre de usuario para el uso activo del titular de la marca. - -### ¿Cómo reporto una violación de la política de marcas? - -Los titulares de marcas registradas pueden denunciar posibles violaciones de la política de marcas a GitHub a través de nuestro [formulario de contacto](https://support.github.com/contact). Envía solicitudes relacionadas con marcas comerciales utilizando tu dirección de correo electrónico de la empresa e incluye toda la información que se solicita a continuación para ayudar a agilizar nuestra respuesta. También asegúrate de describirnos claramente por qué la cuenta puede causar confusión con tu marca o cómo puede la cuenta debilitar o perjudicar a tu marca. - -### ¿Qué información se requiere cuando se informa de las violaciones de las políticas de marcas? - -Para investigar las violaciones de la política de marcas, por favor proporciona toda la siguiente información: - -* Nombre de usuario de la cuenta reportada -* Nombre de tu empresa -* La cuenta GitHub de tu empresa (si existe) -* Sitio web de la empresa -* La palabra de tu marca, símbolo, etc. -* Número de registro de marca -* Oficina de registro de marcas (ej., USPTO) -* Descripción de la confusión (por ejemplo, se hace pasar por su empresa, incluyendo descripciones específicas de contenido o comportamiento) -* Acción solicitada (por ejemplo, eliminación de una cuenta en violación o transferencia de un nombre de usuario con marca a una cuenta de empresa existente) -* Incluye la siguiente declaración: "Tengo la creencia de buena fe de que el uso de la marca descrita anteriormente no está autorizado por el propietario de la marca, o su agente, o la ley. He considerado los usos nominativos y otros usos legítimos". -* También incluye la siguiente declaración: "Juro, bajo pena de perjurio, que la información de esta notificación es fiel y que soy el propietario de los derechos de autor o estoy autorizado para actuar en nombre del propietario, de un derecho exclusivo que se infringe presuntamente." -* Incluye tu firma física o electrónica. - -* Nota: Se requiere un número de registro federal o internacional de marcas registradas. Si el nombre que estás reportando no es **** una marca registrada (por ejemplo, una agencia gubernamental u organización sin fines de lucro), comunícanos: - * Tu nombre y apellido - * Posición - * Dirección - * Teléfono - * Correo electrónico (debe ser de dominio de una empresa) diff --git a/translations/es-XL/content/github/site-policy/github-username-policy.md b/translations/es-XL/content/github/site-policy/github-username-policy.md deleted file mode 100644 index b2d5cfa897..0000000000 --- a/translations/es-XL/content/github/site-policy/github-username-policy.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Política de nombre de usuario de GitHub -redirect_from: - - /articles/name-squatting-policy/ - - /articles/github-username-policy -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Los nombres de cuentas de GitHub se proporcionan dependiendo de quién los reclame primero, y se pretende que se comiencen a utilizar activamente de inmediato. - -#### ¿Qué pasa si el nombre de usuario que quiero ya está en uso? - -Ten en mente que no toda la actividad en GitHub está disponible públicamente para su consulta; puede que las cuentas sin actividad visible estén activas. - -Si ya han reclamado el nombre de usuario que quieres, considera otros nombres o variaciones únicas de éste. Puedes identificar un nombre de usuario aún disponible si utilizas números, guiones, o una morfología alterna. - -#### Política de marcas - -Si consideras que la cuenta de alguien está violando tus derechos de marca, puedes encontrar más información sobre cómo hacer una queja de marca en nuestra página de [Política de Marca](/articles/github-trademark-policy/). - -#### Política de ocupación de nombre - -GitHub prohibe el acaparamiento de nombres de cuenta, y dichos nombres de cuenta no pueden reservarse o mantenerse en inactividad para reclamarse posteriormente. Las cuentas que violen esta política de acaparamiento serán eliminadas o renombradas sin previo aviso. Los intentos de vender, comprar o solicitar otras formas de pago a cambio de nombres de cuenta están prohibidos y pueden resultar en una suspensión de cuenta permanente. diff --git a/translations/es-XL/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/es-XL/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md deleted file mode 100644 index fbe605d725..0000000000 --- a/translations/es-XL/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Aviso de GitHub acerca de la Ley de Privacidad del Consumidor de California -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Válida desde el 1 de enero de 2020 - -### Aviso de GitHub para los Residentes de California - -La [Ley de Privacidad del Consumidor de California](https://leginfo.legislature.ca.gov/faces/billCompareClient.xhtml?bill_id=201720180AB375) de 2018, (Cal. Civ. Code §1798.100 y siguientes., en su texto reformado, “CCPA”) otorga a los residentes de California los derechos y control sobre su información personal. ("GitHub", "nosotros") proporciona esta declaración a los residentes ("tú") de acuerdo con los requisitos bajo la CCPA para realizar ciertas divulgaciones sobre la recolección y procesamiento de su información personal. Esta es la descripción de los derechos del consumidor de GitHub específica para California bajo la CCPA. Para obtener más información acerca de cómo hemos extendido los derechos básicos de la CCPA para controlar la información personal de todos nuestros usuarios en los Estados unidos, por favor consulta nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement). - -### No vendemos tu información personal - -Bajo la CCPA, un negocio que vende la información personal de los residentes de California a otros: 1) debe notificar a los residentes de California antes de vender su información personal a otros; y 2) deberá proporcionar el derecho de negarse a la venta de su información personal. - -GitHub _no_ vende información personal, incluyendo aquella de cualquier menor de 16 años. Por lo tanto, esta notificación y los requisitos para negarse no aplican a GitHub. - -## Tus derechos bajo la CCPA - -La CCPA proporciona a los residentes de California ciertos derechos relacionados con su información personal. Para emitir una solicitud basada en estos derechos, por favor contáctanos a través de nuestro [formulario de contacto](https://support.github.com/contact). - -Cuando recibimos una solicitud, verificamos que la persona que la hace sea el dueño de la misma de acuerdo con dicha solicitud. Los residentes de California podrán ejercer sus derechos por ellos mismos, o podrán utilizar a un agente autorizado para hacer solicitudes para divulgar cierta información acerca del procesamiento de la suya o para eliminar la información personal en su represetnación. Si utilizas a un agente autorizado para emitir una solicitud, podríamos solicitar que nos proporciones información adicional para demostrar que el agente está actuando en tu representación. - -Con respecto a su información personal, los residentes de California podrán ejercer los derechos descritos posteriormente. - -### 1. Derecho a saber qué tipo de información personal se está recolectando, para qué propósito y con quién se comparte - -Los residentes de California tiene el derecho a solicitar una divulgación de negocios sobre las categorías y partes específicas de la información personal que se ha recolectado de ellos en los 12 meses anteriores, y las categorías de las fuentes de donde dicha información personal se recabó, el propósito comercial o de negocios para recolectarla o venderla, y las categorías de terceros con quienes el negocio comparte la información personal. - -Si solicitas que un negocio divulgue las categorías y partes específicas de la información personal que se ha recolectado de ti, tienes el derecho a recibir dicha información, sin costo alguno, dos veces por año. La información podrá entregarse electrónicamente o por correo, y si se proporciona electrónicoamente, deberá estar en un formato portable y, hasta donde sea técnicamente posible, listo para su uso, que permita al residente de California transmitir dicha información de forma relativamente fácil a otra entidad. Puedes utilizar la [API de Migración de Usuarios](/v3/migrations/users/) de GitHub para acceder y descargar tus datos. Conoce más [aquí](https://github.blog/2018-12-19-download-your-data/). - -### 2. Derecho a conocer si tu información personal se vende o divulga para propósitos de negocios y a quién - -Los residentes de California tienen el derecho a solicitar información de un negocio que vende o divulga la información personal para propósitos de negocios en listas separadas de categorías de la información personal recolectada, vendida o divulgada para propósitos de negocios en 12 meses previos, incluyendo las categorías de terceros a quienes se vendió o divulgó la información por motivo de negocios. - -### 3. Derecho a negarse a la venta de su información personal - -Como se explica anteriormente, la CCPA requiere que los negocios que venden información personal permitan a los residentes negarse a la venta de su información. - -Reiteramos, GitHub no vende información personal. - -### 4. Derecho a no discriminar servicios o precios si ejerces tus derechos a la privacidad - -La CCPA prohíbe que los negocios discriminen a un residente de California por ejercer cualquiera de sus derechos bajo la misma, incluyendo el -- negar bienes o servicios -- cobrar precios o tasas diferentes por bienes o servicios, incluyendo a través del uso de descuentos u otros beneficios o mediante la imposición de multas -- proporcionar un nivel de calidad o de bienes o servicios diferente -- sugerir que la persona que está ejerciendo sus derechos recibirá un precio o tasa diferente en los bienes o servicios o un nivel de calidad diferente en éstos - -### 5. Derecho al borrado - -Los residentes de california tienen el derecho de solicitar que un negocio elimine cualquier información personal que éste haya recolectado de ellos, sujeto a las excepciones en la CCPA §1798.105. - -## Nuestro manejo de la Información Personal - -Aunque la siguiente tabla contiene información acerca de las categorías de información personal que recolectamos, procesamos y compartimos, por favor consulta la [Declaración de Privacidad](/github/site-policy/github-privacy-statement) para encontrar todos los detalles. - -| **Categoría de información personal recolectada en los últimos 12 meses** | **Categoría de fuentes desde donde se ha recolectado la información personal** | **Propósito(s) comercial o de negocios para recolectar la información personal** | **Categorías de los terceros con los que se comparte la información personal** | **Categorías de la información personal divulgada por propósitos comerciales o de negocios** | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Identificadores (tales como nombre real, alias, dirección postal, identificador personal único, dirección de Protocolo de Internet de identificación en línea, dirección de correo electrónico, nombre de cuenta, u otros identificadores similares) | Información que proporciona el consumidor directamente o automáticamente a través de su interacción con nuestro Servicio y/o Sitio Web | Detectar incidentes de seguridad, proteger contra actividad maligna, engañosa, fraudulenta o ilegal, y perseguir a los responsables de dicha actividad

    Arreglo de errores para identificarlos y repararlos si impiden la funcionalidad existente buscada

    Llevar a cabo servicios por parte del negocio o proveedor de servicios

    Llevar a cabo investigaciones internas para desarrollo tecnológico y demostración

    Llevar a cabo actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorar, actualizar o ampliar el servicio | Proveedores de servicios, clientes aplicables, aplicación de la ley | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | -| Cualquier categoría de información personal descrita en la subdivisión (e) de Cal. Civ. Code §1798.80 (la cual define a la "información personal" como "cualquier tipo de información que identifica, relaciona, describe, o es capaz de asociarse con un individuo en particular" — con ejemplos que incluyen nombre, dirección, número de tarjeta de crédito o débito—y excluye la información disponible al público en general) | Información que el consumidor proporciona directamente | Perseguir a aquellos responsables por actividades malignas, engañosas, fraudulentas o ilegales.

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | -| Las características de las clasificaciones protegidas bajo la ley federal de California (tales como género, edad) | Información que el consumidor decida proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | -| Información comercial (tal como aquella acerca de la compra, obtención, consideración de bienes o servicios, u otro tipo de historial o tendencia de compra o consumo) | Información que proporciona el consumidor directamente o automáticamente a través de su interacción con nuestros Servicios | Depuración para identificar y reparar errores que perjudican la funcionalidad deseada

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios | Esta categoría de información personal se ha divulgado para propósitos comerciales o de negocios | | Información de actividad en internet o en otra red electrónica (tal como historial de internet, historial de búsqueda, e información relacionada con la interacción de un cliente con una aplicación o sitio web de internet) | Información que el cliente proporciona automáticamente a través de su interacción con nuestros Servicios | Detectar incidentes de seguridad, proteger contra la actividad maligna, engañosa, fraudulenta, o ilegal, y perseguir a los responsables de dicha actividad

    Depurar para identificar y reparar errores que perjudican la funcionalidad deseada

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios

    Realizar investigación interna sobre demostraciones y desarrollo tecnológico

    Realizar actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorarlo, actualizarlo o ampliarlo | Proveedores de servicio, clientes aplicables, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | - Datos de Geolocalización (tales como la dirección IP) | Información que el consumidor proporciona automáticamente a través de su interacción con nuestros servicios | Detectar incidentes de seguridad, proteger contra actividades malignas, engañosas fraudulentas o ilegales, y perseguir a los responsables de dicha actividad

    Depurar para identificar y reparar los errores que perjudican la funcionalidad deseada

    Llevar a cabo servicios a nombre del negocio o proveedor de servicios

    Realizar investigación interna sobre demostraciones y desarrollo tecnológico

    Realizar actividades para verificar o mantener la calidad o seguridad de un servicio, y para mejorarlo, actualizarlo o ampliarlo | Proveedores de servicio, clientes aplicables, aplicación de leyes | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios |Información de audio, electrónica, visual o similar | Información que el consumidor podrá elegir proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Información profesional o relacionada con el empleo | Información que el consumidor podrá elegir proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Infomración de la educación que no está disponible públicamente ni identifica a las personas | Esta categoría de información personal se ha divulgado con fines comerciales o de negocios | Información como se define en la Ley de Privacidad y Derechos Educacionales Familiares (20 U. S.C. Sec. 1232g; 34 C. F.R. Parte 99) | Información que el consumidor pudiera proporcionar directamente | Llevar a cabo servicios (perfil de usuario) | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | Inferencias extraídas de cualquier información identificada en esta tabla para crear un perfil acerca de un consumidor, el cual refleje las preferencias del mismo | Información que el consumidor proporciona directamente o automáticamente a través de su interacción con nuestros Servicios | Llevar a cabo servicios a nombre del negocio o proveedor de servicios | Proveedores de servicios | Esta categoría de información personal se ha divulgado para fines comerciales o de negocios | - -## Ejemplos bajo la CCPA - -La CCPA proporciona exclusiones hasta, e incluyendo, el 31 de diciembre de 2020, de ciertas divulgaciones de las antes citadas, las cuales se sitúen en los 12 últimos meses incluyendo la **exclusión de negocio a negocio**: - - la información personal que se refleje en comunicaciones verbales o escritas o en transacciones entre GitHub y una persona natural, en donde la persona natural actúe como un empleado, propietario, director, oficial, o contratista de una compañía, sociedad, único dueño, organización sin fines de lucro, o agencia de gobierno, y cuyas comunicaciones o transacciones con GitHub ocurran únicamente dentro del contexto de que GitHub lleve a cabo indagaciones previas, o proporcione o reciba un producto o servicio de o por parte de tal compañía, sociedad, duelo único, organización sin fines de lucro o agencia del gobierno. - -Si tienes cualquier duda acerca de esta página, por favor contáctanos a través de nuestro [formulario de contacto](https://support.github.com/contact). diff --git a/translations/es-XL/content/github/site-policy/global-privacy-practices.md b/translations/es-XL/content/github/site-policy/global-privacy-practices.md deleted file mode 100644 index e59fe2a08e..0000000000 --- a/translations/es-XL/content/github/site-policy/global-privacy-practices.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Prácticas de Privacidad Globales -redirect_from: - - /eu-safe-harbor/ - - /articles/global-privacy-practices -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Fecha de entrada en vigor: 22 de julio del 2020 - -GitHub Proporciona el mismo estándar alto de protección de privacidad—tal como se describe en la [Declaración de Privacidad](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices) de GitHub—a todos nuestros usuarios y clientes en todo el mundo, sin importar su país de origen o ubicación, y GitHub se enorgullece del nivel de notificación, elección, responsabilidad, seguridad, integridad de datos, acceso, y recursos que proporcionamos. - -GitHub también cumple con ciertos marcos de trabajo relacionados con la transferencia de los datos desde el Área Económica Europea, el Reino Unido y Suiza (colectivamente conocidos como "UE") hacia los Estados Unidos. Cuando GitHub se involucra en dichas transferencias, GitHub se basa en las Cláusulas Contractuales Estándar como el mecanismo legal para ayudarlo a garantizar tus derechos y que tu información personal viaje con la protección adecuada. Adicionalmente, GitHub se certifica en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A y Suiza-U. S. A. Para aprender más sobre las decisiones de la Comisión Europea sobre la transferencia internacioal de datos, consulta este artículo en el [Sitio web de la Comisión Europea](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en). - -### Cláusulas Contractuales Estándar - -GitHub se basa en las Cláusulas Contractuales Estándar aprobadas por la Comisión Europea ("SCCs") como un mecanismo legal para las transferencia de datos desde la UE. Las SCCs son compromisos contractuales entre compañías que transfieren datos personales que las vinculan para proteger la privacidad y seguridad de dichos datos. GitHub adoptó las SCCs para que los flujos de datos necesarios puedan protegerse cuando se transfieren hacia afuera de la UE a países que la Comisión Europea no ha estimado pueden proteger los datos personales adecuadamente, incluyendo el proteger la transferencia de estos hacia los Estados Unidos. - -Para aprender más sobre las SCCs, consulta este artículo en el [Sitio web dela Comisión Europea](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en). - -### Marco del Escudo de Privacidad - -GitHub está certificado en los Marcos de Trabajo de Escudo de Privacidad de UE-U. S. A y U. S. A-Suiza y en los compromisos que éstos conllevan, a pear de que GitHub no se basa en el Marco de Trabajo de Escudo de Privacidad de UE-U. S. A. como una base legal para transferencias de información personal ante el juicio de la Corte de Justicia de la UE en el caso C-311/18. - -Los Marcos de Trabajo de Escudo de Privacidad de UE-E.U.A. y Suiza-E.U.A. se implementan por el Departamento de Comercio de los E.U.A. de acuerdo con la recoleción, uso, y retención de la Información Personal transferida desde la Unión Europea, el Reino Unido, y Suiza hacia los Estados Unidos. GitHub ha certificado al Departamento de Comercio que se apega a los Principios del Escudo de Privacidad. Si nuestros proveedores o afiliados procesan la Información Personal de los Usuarios en nuestro nombre de forma inconsistente con los principios de cualquiera de los Marcos de Trabajo de Escudo de Privacidad, GitHub seguirá siendo responsable a menos de que provemos que no lo somos para dicho evento que genera el daño. - -Para propósitos de nuestras certificaciones bajo los Marcos de Trabajo del Escudo de Privacidad, si hubiese cualquier conflicto entre las condiciones en estas Prácticas de Privacidad Globales y en los Principios del Escudo de Privacidad, los últimos deberán prevalecer. Para obtener más información sobre el programa Escudo de Privacidad y para ver nuestra certificación, visite el sitio web [de Escudo de Privacidad](https://www.privacyshield.gov/). - -Los Marcos de Trabajo del Escudo de Privacidad se basan en siete principios, y GitHub se apega a ellos de las siguientes formas: - -- **Notificaciones** - - Te informamos cuando recopilamos tu información personal. - - Te damos a conocer, en nuestra [Declaración de Privacidad](/articles/github-privacy-statement/)de los fines que tenemos para recopilar y utilizar tu información a quién compartimos esa información con y bajo qué restricciones y qué acceso tiene a tus datos. - - Te informamos que estamos participando en el marco del Escudo de Privacidad y lo qué significa para ti. - - Tenemos un {% data variables.contact.contact_privacy %} donde puedes contactarnos con preguntas sobre tu privacidad. - - Te informamos acerca de tu derecho a invocar arbitraje vinculante, sin costo alguno para ti, en el improbable caso de una disputa. - - Te informamos que estamos sujetos a la jurisdicción de la Comisión Federal de Comercio. -- **Opción** - - Te permitimos elegir lo que sucede con tus datos. Antes de que utilicemos tus datos para un propósito distinto para el cual nos los proporcionaste, te avisaremos y obtendremos tu permiso. - - Te proporcionarremos mecanismos razonables para hacer tu elección. -- **Responsabilidad de la transferencia continua** - - Cuando transferimos tu información a proveedores de terceros que la procesan en nuestro nombre, sólo estamos enviando tus datos a terceros, bajo contrato con nosotros, que los salvaguardarán consistentemente con nuestra Declaración de Privacidad. Cuando transferimos tus datos a nuestros proveedores bajo el Escudo de Privacidad, seguimos siendo responsables de ello. - - Compartimos sólo la cantidad de datos con nuestros proveedores de terceros cuando sea necesario para completar tu transacción. -- **Seguridad** - - Protegeremos tu información personal con [todas las medidas de seguridad razonables y apropiadas](https://github.com/security). -- **Limitación de integridad y propósito de datos** - - Solo recopilamos tus datos para las finalidades pertinentes para proporcionarte nuestros servicios. - - Recopilamos tan poca información tuya como podamos, a menos que decidas proporcionarnos más. - - Tomamos medidas razonables para asegurar que tus datos sean exactos, actuales y fiables para su uso previsto. -- **Acceso** - - Siempre puedes acceder a los datos que tenemos sobre ti en tu perfil de usuario [](https://github.com/settings/profile). Puedes ingresar, actualizar, alterar o eliminar tu información allí. -- **Recursos, cumplimiento y responsabilidad** - - Si tienes alguna pregunta sobre nuestras prácticas de privacidad, puedes contactarnos con nuestro {% data variables.contact.contact_privacy %} y responderemos en un plazo máximo de 45 días. - - En el improbable caso de una disputa que no podamos resolver, tienes acceso a un arbitraje vinculante sin coste alguno para ti. Consulta la [Declaración de privacidad](/articles/github-privacy-statement/)para obtener más información. - - Realizaremos auditorías periódicas de nuestras prácticas de privacidad relevantes para verificar el cumplimiento de las promesas que hemos hecho. - - Exigimos a nuestros empleados que respeten nuestras promesas de privacidad y la violación de nuestras políticas de privacidad está sujeta a una acción disciplinaria e inclusive hasta la terminación del empleo. - - -#### Proceso de resolución de disputas - -Como se explica a detalle en la sección de [Resolución de Quejas](/github/site-policy/github-privacy-statement#resolving-complaints) de nuestra [Declaración de Privacidad](/github/site-policy/github-privacy-statement), te exhortamos a contactarnos en caso de que tengas alguna queja relacionada con el Escudo de Privacidad (o sobre la privacidad en general). Para cualquier queja que no pueda resolverse directamente con GitHub, hemos escogido cooperar con la Autoridad de Protección de datos de la UE reelevante, o con un panel establecido por las autoridades europeas de protección de datos, para resolver disputas con los individuos de la UE, y con la Comisión Federal para la Protección de Datos y la Información (FDPIC, por sus siglas en inglés) para resolver las disputas con los individuos suizos. Por favor contáctanos si deseas que te dirijamos a los contactos de tu autoridad de protección de datos. - -Además, si eres residente de un estado miembro de la UE, tienes derecho a presentar una queja ante tu autoridad supervisora local. - -#### Arbitraje independiente - -En determinadas circunstancias limitadas, la UE, el Espacio Económico Europeo (EEE), Suiza y las personas del Reino Unido pueden recurrir al arbitraje vinculante del Escudo de privacidad como último recurso, si todas las demás formas de resolución de disputas no tuvieron éxito. Para obtener más información acerca de este método de resolución y su disponibilidad, consulta más detalles sobre el [Escudo de privacidad](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). El arbitraje no es obligatorio, es una herramienta que puedes utilizar si así lo decides. - -Estamos sujetos a la jurisdicción de la Comisión Federal de Comercio (FTC) de los EE. UU. - -Consulta la [Declaración de privacidad](/articles/github-privacy-statement/)para obtener más información. diff --git a/translations/es-XL/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md b/translations/es-XL/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md deleted file mode 100644 index 0f7e8c965a..0000000000 --- a/translations/es-XL/content/github/site-policy/guide-to-submitting-a-dmca-counter-notice.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Guía para enviar una contranotificación de DMCA -redirect_from: - - /dmca-counter-notice-how-to/ - - /articles/dmca-counter-notice-how-to/ - - /articles/guide-to-submitting-a-dmca-counter-notice -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Esta guía describe la información que GitHub necesita para procesar una contra notificación de DMCA. Si tienes preguntas más generales sobre qué es la DMCA o cómo procesa GitHub las solicitudes de retiro de DMCA, por favor revisa nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy). - -Si consideras que tu contenido en GitHub fue inhabilitado erróneamente por una solicitud de retiro de DMCA. tienes derecho de disputar el retiro enviando una contra notificación. Si lo haces, esperaremos 10-14 días y posteriormente volveremos a habilitar tu contenido a menos que el propietario de los derechos de autor inicie una acción legal contra ti antes de entonces. Nuestro formulario de contra notificación indicado a continuación es coherente con el formulario sugerido por el estatuto DMCA, que se puede encontrar en el sitio web oficial de la Oficina de Derechos de Autor de EE. UU.: . Copyright Office's official website: . - -Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal. - -### Antes de comenzar - -***Di la Verdad.*** La DMCA requiere que jures tu contra notificación *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [Código de Estados Unidos, Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm). Code, Title 18, Section 1621.) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. - -***Investiga.*** Enviar una contra notificación DMCA puede tener consecuencias legales reales. Si la parte que denuncia no está de acuerdo en que tu notificación de retiro fue errónea, podrían decidir presentar una demanda contra ti para mantener el contenido deshabilitado. Deber llevar a cabo una investigación exhaustiva sobre las acusaciones hechas en la notificación de retiro y probablemente hablar con un abogado antes de enviar una contra notificación. - -***Debes tener una razón fundada para emitir una contranotificación.*** Para emitir una contranotificación, deberás tener una "certeza de buena fe de que el material se eliminó o inhabilitó como resultado de un error o mala identificación del material que se quiere eliminar o inhabilitar". (U.S. ([Título 17 del Código de los EEUU, Sección 512(g)](https://www.copyright.gov/title17/92chap5.html#512)). Ya sea que decidas explicar o no el por qué crees que hubo un error, dependerá de ti y de tu abogado, pero *sí* necesitas identificar un error antes de emitir una contranotificación. En el pasado, recibimos contra notificaciones que citan errores en la notificación de retiro, tales como: La parte que reclama no tiene el derecho de autor; tengo una licencia; el código se liberó bajo una licencia de código abierto que permite mi uso; o la queja no tiene en cuenta el hecho de que mi uso está protegido por la doctrina del uso legal. Por supuesto, podría haber otros defectos con la notificación de retiro.

    - -***Las leyes de derechos de autor son complicadas.*** En ocasiones una notificación de retiro podría hacer referencia a una infracción que parece extraña o indirecta. Las leyes de derechos de autor son complicadas y pueden dar lugar a resultados inesperados. En algunos casos una notificación de retiro podría señalar que su código fuente infringe por lo que puede ocasiones posteriormente que se compile y ejecute. Por ejemplo: - - - La notificación podrá reclamar que tu software se utiliza para [evitar los controles de acceso](https://www.copyright.gov/title17/92chap12.html) a los trabajos con derechos de autor. - - [Algunas veces](https://www.copyright.gov/docs/mgm/) la distribución de software puede considerarse como una infracción a los derechos de autor, si induces a los usuarios finales a utilizar el software para infringir el trabajo con derechos de autor. - - Una queja de derechos de autor también podría basarse en [copia no literal](https://en.wikipedia.org/wiki/Substantial_similarity) de elementos de diseño en el software, en lugar del código fuente en sí mismo, en otras palabras, alguien envió una notificación diciendo que piensa que tu *diseño* es demasiado similar al de ellos. - -Estos son sólo algunos ejemplos de la complejidad de la legislación sobre derechos de autor. Dado que hay muchos matices a la ley y algunas preguntas sin resolver en este tipo de casos, es especialmente importante obtener asesoramiento profesional si las acusaciones de infracción no parecen sencillas. - -***Una contra notificación es una declaración legal.*** Te pedimos que completes todos los campos de una contra notificación en su totalidad, porque una denuncia es una declaración legal — no sólo para nosotros, sino para la parte demandante. Como mencionamos anteriormente, si la parte reclamante desea mantener el contenido desactivado después de recibir una contra notificación, tendrán que iniciar una acción legal que busque una orden judicial para impedirle participar en actividades de infracción relacionadas con el contenido de GitHub. En otras palabras, podrías ser demandado (y das tu consentimiento en la contra notificación). - -***Tu contra notificación se publicará.*** Como se indica en nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy#d-transparency), **después de redactar información personal,** publicamos todas las contra notificaciones completas y accionables en [https://github. om/github/dmca](https://github.com/github/dmca). También ten en cuenta que, aunque sólo publicaremos notificaciones rectificadas, podemos proporcionar una copia completa y no editada de cualquier notificación que recibamos directamente para cualquier parte cuyos derechos se verían afectados por esta. Si estás preocupado por tu privacidad, podrías pedir que un abogado u otro representante legal presente la contra notificación en tu nombre. - -***GitHub no es el juez.*** GitHub ejerce poca discreción en este proceso además de determinar si las notificaciones cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que las notificaciones deben realizarse bajo pena de perjurio. - -***Recursos Adicionales.*** Si necesitas ayuda adicional, hay muchos recursos de autoayuda en línea. Lumen tiene un conjunto informativo de guías sobre [copyright](https://www.lumendatabase.org/topics/5) y [puerto seguro de DMCA](https://www.lumendatabase.org/topics/14). Si estás implicado con un proyecto de código abierto que necesita asesoramiento legal, puedes ponerse en contacto con el [Centro de asesoramiento legal sobre software libre](https://www.softwarefreedom.org/about/contact/). Y si consideras que tienes un caso especialmente desafiante, organizaciones sin fines de lucro como la [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) también pueden estar dispuestas a ayudarte directamente o a referirte a un abogado. - - - -### Tu contra notificación debe... - -1. **Incluir la siguiente declaración: "He leído y entendido la guía de GitHub para presentar una contra notificación DMCA.** No nos negaremos a procesar una contra notificación completa si no incluye esta declaración; sin embargo, sabremos que no has leído estas directrices y podríamos solicitarte que lo hagas. - -2. ***Identificar el contenido que fue desactivado y la ubicación donde apareció.*** El contenido deshabilitado debería haber sido identificado por la URL en la notificación de retiro. Simplemente necesitas copiar la(s) URL(s) que deseas cuestionar. - -3. **Proporcionar tu información de contacto.** Incluye tu dirección de correo electrónico, nombre, número de teléfono y dirección. - -4. ***Incluir la siguiente declaración: "Juro, bajo pena de perjurio, que tengo una creencia de buena fe de que el material se eliminó o deshabilitó como resultado de un error o mala identificación del material a ser eliminado o desactivado.*** También puedes elegir comunicar las razones por las que crees que hubo un error o una mala identificación. Si piensas en tu contra notificación como una "nota" a la parte reclamante, Esta es una oportunidad para explicar por qué no deben dar el siguiente paso y presentar una demanda en respuesta. Esta es otra razón más para trabajar con un abogado al enviar una contra notificación. - -5. ***Incluir la siguiente declaración: "Acepto la jurisdicción del Tribunal Federal de Distrito para el distrito judicial en el que se encuentra mi dirección (si es en los Estados Unidos, de lo contrario el Distrito Norte de California donde se encuentra GitHub) y aceptaré el servicio de trámite de la persona que proporcionó la notificación del DMCA o de un agente de dicha persona."*** - -6. **Incluye tu firma física o electrónica.** - - - -### Cómo enviar tu contra notificación - -La forma más rápida de obtener una respuesta es ingresar tu información y responder a todas las preguntas de nuestro {% data variables.contact.contact_dmca %}. - -También puedes enviar una notificación por correo electrónico a . Puedes incluir un archivo adjunto si lo deseas, pero por favor incluye una versión de texto simple de tu carta en el cuerpo de tu mensaje. - -Si debes enviar tu notificación por correo físico, también puedes hacerlo pero tardaremos *substancialmente* en recibirla y responder a ella y el periodo de espera de 10 a 14 días comienza a partir de cuando *recibamos* tu contra notificación. Las notificaciones que recibimos por correo electrónico de texto plano tienen una respuesta mucho más rápida que los archivos adjuntos PDF o el correo. Si aún deseas enviarnos tu aviso, nuestra dirección es: - - - -``` -GitHub, Inc -En atención a: Agente de DMCA -88 Colin P Kelly Jr St -San Francisco, CA. 94107 -``` diff --git a/translations/es-XL/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md b/translations/es-XL/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md deleted file mode 100644 index e4f0ebe209..0000000000 --- a/translations/es-XL/content/github/site-policy/guide-to-submitting-a-dmca-takedown-notice.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Guía para enviar un aviso de retiro de DMCA -redirect_from: - - /dmca-notice-how-to/ - - /articles/dmca-notice-how-to/ - - /articles/guide-to-submitting-a-dmca-takedown-notice -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Esta guía describe la información que GitHub necesita para procesar una solicitud de retiro de DMCA. Si tienes preguntas más generales sobre qué es la DMCA o cómo procesa GitHub las solicitudes de retiro de DMCA, por favor revisa nuestra [política de retiro de DMCA](/articles/dmca-takedown-policy). - -Debido al tipo de contenido de los hosts de GitHub (principalmente de código de software) y a la forma en que se gestiona el contenido (con Git), necesitamos que las demandas sean lo más específicas posible. Estas directrices están diseñadas para que el procesamiento de las notificaciones de supuestas infracciones sea lo más sencillo posible. Nuestra forma de notificación indicada a continuación es coherente con el formulario sugerido por el estatuto DMCA, que se puede encontrar en el sitio web oficial de la Oficina de Derechos de Autor de EE. UU.: . Copyright Office's official website: . - -Como en todas las cuestiones jurídicas, siempre es mejor consultar con un profesional sobre tus preguntas o situación específicas. Te recomendamos enfáticamente que lo hagas antes de emprender cualquier acción que pueda afectar tus derechos. Esta guía no es asesoramiento legal y no debería ser tomada como tal. - -### Antes de comenzar - -***Di la Verdad.*** La DMCA requiere que prestes atención a los hechos en tu queja de derechos de autor *bajo pena de perjurio*. Es un crimen federal mentir intencionadamente en una declaración jurada. (*Consulta* [Código de Estados Unidos, Título 18, Sección 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm). Code, Title 18, Section 1621.) La presentación de información falsa también podría resultar en responsabilidad civil, es decir, podrías ser demandado por daños monetarios. La DMCA por sí misma [proporciona daños](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations) contra cualquier persona que, a sabiendas, tergiversa materialmente dicha actividad o material infractor. - -***Investiga.*** Millones de usuarios y organizaciones se esfuerzan demasiado en los proyectos que crean y contribuyen en GitHub. La presentación de una queja de DMCA contra un proyecto de este tipo es una acusación legal seria que conlleva consecuencias reales para las personas reales. Por eso, te pedimos que realices una investigación exhaustiva y consultes con un abogado antes de enviar una solicitud de retiro para asegurarte que el uso no sea realmente permisible. - -***Primero pregunta amablemente.*** Un gran primer paso antes de enviarnos una notificación de retiro es intentar contactar directamente al usuario. Pueden haber enumerado información de contacto en su página de perfil público o en el README del repositorio, o podrías ponerse en contacto abriendo una propuesta o solicitud de extracción en el repositorio. Esto no es estrictamente necesario, pero es común. - -***Envia una solicitud de corrección.*** Sólo podemos aceptar notificaciones de retiro de DMCA para obras protegidas por derechos de autor y que identifiquen un trabajo específico con derechos de autor. Si tienes una queja sobre el abuso de la marca registrada, consulta nuestra [política de marcas](/articles/github-trademark-policy/). Si desea eliminar datos sensibles como contraseñas, consulta nuestra [política sobre datos sensibles](/articles/github-sensitive-data-removal-policy/). Si usted está tratando con difamación u otro comportamiento abusivo, por favor consulta nuestras [Directrices de la comunidad](/articles/github-community-guidelines/). - -***El código es diferente de otro contenido creativo.*** GitHub está construido para colaborar en el código de software. Esto hace que la identificación de una infracción válida de derechos de autor sea más complicada de lo que podría ser de otra manera para, fotos, música o videos, por ejemplo. - -Existen diversas razones por las que el código es diferente de otros contenidos creativos. Por ejemplo: - -- Un repositorio puede incluir bits y partes de código de muchas personas diferentes, pero sólo un archivo o incluso una subrutina dentro de un archivo infringe tus derechos de autor. -- El código mezcla funcionalidad con expresión creativa, pero los derechos de autor sólo protegen los elementos expresivos, no las partes que son funcionales. -- A menudo hay licencias a considerar. El hecho de que una parte del código tenga una notificación de derechos de autor no significa necesariamente que sea infractora. Es posible que el código se esté utilizando de acuerdo con una licencia de código abierto. -- Un uso particular puede ser [uso legítimo](https://www.lumendatabase.org/topics/22) si solamente utiliza una pequeña cantidad del contenido protegido por derechos de autor, si utiliza ese contenido de forma transformativa, lo utiliza para fines educativos, o alguna combinación de lo anterior. Dado que el código naturalmente se presta a dichos usos, cada caso de uso es diferente y debe considerarse por separado. -- Se puede alegar que el código infringe de muchas formas diferentes, exigiendo explicaciones detalladas e identificaciones de obras. - -Esta lista no es exhaustiva, por lo que hablar con un profesional legal sobre tu propuesta de reclamación es doblemente importante cuando se trata de un código. - -***Sin bots.*** Deberías contar con un profesional capacitado para evaluar los datos de cada notificación de retito que envíes. Si estás subcontratando tus labores a un tercero, asegúrate de saber cómo trabajand y asegúrate que no estén utilizando bots automatizados para presentar quejas en masa. ¡Estas quejas a menudo no son válidas y su procesamiento da lugar a la supresión innecesaria de proyectos! - -***Los temas de derechos de autor son difíciles.*** Puede ser muy difícil determinar si un trabajo en particular está protegido o no por derechos de autor. Por ejemplo, los hechos (incluyendo los datos) generalmente no tienen derechos de autor. Las palabras y las frases cortas generalmente no tienen derechos de autor. Las URLs y los nombres de dominio generalmente no tienen derechos de autor. Dado que sólo puede utilizar el proceso DMCA para abordar contenido protegido por derechos de autor, deberías hablar con un abogado si tienes preguntas sobre si tu contenido es o no protegible. - -***Puedes recibir una contra notificación.*** Cualquier usuario afectado por tu notificación de retiro puede decidir enviar una [contra notificación](/articles/guide-to-submitting-a-dmca-counter-notice). Si lo hacen, reactivaremos tu contenido en un plazo de 10 a 14 días a menos que nos notifique que has iniciado una acción legal encaminada a impedir que el usuario se involucre en infringir la actividad relacionada con el contenido en GitHub. - -***Tu queja se publicará.*** Como se indica en nuestra [política de DMCA](/articles/dmca-takedown-policy#d-transparency), después de modificar la información personal, publicamos todas las notificaciones de retiro completas y accionables en [https://github. om/github/dmca](https://github.com/github/dmca). - -***GitHub no es el juez.*** GitHub ejerce poca discreción en el proceso además de determinar si las notificaciones cumplen con los requisitos mínimos de la DMCA. Corresponde a las partes (y a sus abogados) evaluar el mérito de sus reclamaciones, teniendo en cuenta que las notificaciones deben realizarse bajo pena de perjurio. - -### Tu queja debe ... - -1. **Incluir la siguiente declaración: "He leído y entendido la guía de GitHub para presentar una notificación de DMCA.** No nos negaremos a procesar una queja completa si no incluye esta declaración. Pero sabremos que no has leído estas directrices y podríamos solicitarte que regreses y lo lleves a cabo. - -2. **Identifica el trabajo con derechos de autor que consideras que ha sido infringido.** Esta información es importante porque ayuda al usuario afectado a evaluar su reclamación y le da la capacidad de comparar su trabajo con el tuyo. La especificidad de su identificación dependerá de la naturaleza del trabajo que consideras que ha sido infringido. Si has publicado tu trabajo, solo podrás enlazar a una página web donde reside. Si es autónoma y no está publicada, puedes describirlo y explicar que es propietario. Si lo has registrado en la Oficina de Derechos de Autor, debes incluir el número de registro. Si estás alegando que el contenido alojado es una copia directa y literal de tu trabajo, también puedes explicar ese hecho. - -3. **Identifica el material al que haces referencia que está infringiendo el trabajo protegido por derechos de autor que aparece en el artículo #2, anterior.** Es importante ser lo más específico posible en tu identificación. Esta identificación debe ser razonablemente suficiente para permitir a GitHub localizar el material. Como mínimo, esto significa que debe incluir la URL del material que supuestamente infringe sus derechos de autor. Si aseguras que se infringe menos de un repositorio completo, identifica el(los) archivo(s) específicos o números de línea dentro de un archivo al que te refieres. Si aseguras que se infringe todo el contenido en una URL, por favor se explícito al respecto también. Por último, ten en cuenta que GitHub *no* deshabilitará automáticamente los [forks](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) al desactivar un repositorio matriz. Si has investigado y analizado los forks de un repositorio y crees que también están infringiendo, por favor identifique explícitamente cada fork supuestamente infractor. Por favor, confirma también que has investigado cada caso individual y que tus declaraciones juradas se aplican a cada fork identificado. - -4. **Explica lo que el usuario afectado tendría que hacer para remediar la infracción.** De nuevo, la especificidad es importante. Cuando transmitimos su queja al usuario, esto les dirá lo que tienen que hacer para evitar que el resto de su contenido esté desactivado. ¿Necesita el usuario añadir una declaración de atribución? ¿Necesitan eliminar ciertas líneas dentro de su código, o archivos completos? Por supuesto, entendemos en algunos casos, todo el contenido de un usuario puede infringirse presuntamente y no hay nada que puedan hacer más que borrarlo todo. Si ese es el caso, por favor deja esto claro también. - -5. **Proporciona tu información de contacto.** Incluye tu dirección de correo electrónico, nombre, número de teléfono y dirección. - -6. **Proporciona información de contacto, si la conoces, para el presunto infractor.** Generalmente esto se realizará proporcionando el nombre de usuario de GitHub asociado con el contenido presuntamente infractor. Sin embargo, puede haber casos en los que tengas conocimientos adicionales sobre el presunto infractor. Si es así, por favor comparte esa información con nosotros. - -7. **Incluye la siguiente declaración: "Tengo buena fe en que el uso de los materiales protegidos por derechos de autor descritos anteriormente en las páginas web infractoras no está autorizado por el propietario de los derechos de autor, o su agente, o la ley. He tenido en cuenta el uso justo."** - -8. **También incluye la siguiente declaración: "Juro, bajo pena de perjurio, que la información de esta notificación es exacta y que soy el propietario de los derechos de autor, o estoy autorizado para actuar en nombre del propietario, de un derecho exclusivo que se infringe presuntamente".** - -9. **Incluye tu firma física o electrónica.** - -### Quejas sobre Tecnología de Anti Elusión - -La Ley de Derechos de Autor también prohíbe la elusión de medidas tecnológicas que controlen eficazmente el acceso a las obras protegidas por los derechos de autor. Si crees que el contenido alojado en GitHub viola esta prohibición, por favor envíanos un informe a través de nuestro {% data variables.contact.contact_dmca %}, e incluye información específica sobre qué contenido viola esa prohibición, qué medidas tecnológicas aplicas y por qué el contenido viola la prohibición. - -### Como presentar tu queja - -La forma más rápida de obtener una respuesta es ingresar tu información y responder a todas las preguntas de nuestro {% data variables.contact.contact_dmca %}. - -También puedes enviar una notificación por correo electrónico a . Puedes incluir un archivo adjunto si lo deseas, pero por favor incluye una versión de texto simple de tu carta en el cuerpo de tu mensaje. - -Si debes enviar tu aviso por correo físico, también puedes hacerlo pero tardará *substancialmente* en que lo recibamos y respondamos al mismo. Las notificaciones que recibimos por correo electrónico de texto plano tienen una respuesta mucho más rápida que los archivos adjuntos PDF o el correo. Si aún deseas enviarnos tu aviso, nuestra dirección es: - -``` -GitHub, Inc -En atención a: Agente de DMCA -88 Colin P Kelly Jr St -San Francisco, CA. 94107 -``` diff --git a/translations/es-XL/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/es-XL/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md deleted file mode 100644 index bd96daef66..0000000000 --- a/translations/es-XL/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -title: Pautas para las solicitudes legales de los datos del usuario -redirect_from: - - /law-enforcement-guidelines/ - - /articles/guidelines-for-legal-requests-of-user-data -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -¿Eres un agente de la policía que lleva a cabo una investigación que pueda implicar contenido de usuario alojado en GitHub? O quizá seas una persona consciente de la privacidad y te gustaría saber qué información compartimos con las fuerzas policiales y bajo qué circunstancias. Cualquiera que sea la razón, estás en la página correcta. - -En estas pautas, proporcionamos algunos antecedentes sobre lo que es GitHub, los tipos de datos que tenemos y las condiciones bajo las cuales divulgaremos información privada del usuario. Sin embargo, antes de entrar en los detalles, aquí se presentan algunos detalles importantes que quizás deseas saber: - -- [**Notificaremos a los usuarios afectados**](#we-will-notify-any-affected-account-owners) sobre cualquier solicitud de información de su cuenta a menos que se prohíba hacerlo por ley u orden judicial. -- No divulgaremos **datos de seguimiento de ubicación**, tales como registros de direcciones IP, sin una [orden judicial válida o orden de registro](#with-a-court-order-or-a-search-warrant). -- No divulgaremos ningún **contenido privado del usuario**, incluyendo el contenido de repositorios privados, sin una [orden de registro válida](#only-with-a-search-warrant). - -### Acerca de estas pautas - -Nuestros usuarios confían en nosotros con sus proyectos de software y código - a menudo algunos de sus activos personales o comerciales más valiosos. Mantener esa confianza es esencial para nosotros, lo que significa mantener los datos de los usuarios seguros y privados. - -Mientras que la abrumadora mayoría de nuestros usuarios utilizan los servicios de GitHub para crear nuevas empresas, para construir nuevas tecnologías y para el mejoramiento general de la humanidad, reconocemos que con millones de usuarios repartidos por todo el mundo, no hay duda de que habrá algunas excepciones. En esos casos, deseamos ayudar a las fuerzas policiales a servir a su legítimo interés de proteger al público. - -Al proporcionar pautas para el personal encargado de hacer cumplir la ley, esperamos lograr un equilibrio entre los intereses a menudo contrapuestos de la privacidad y la justicia de los usuarios. Esperamos que estas pautas ayuden a establecer expectativas por ambas partes, así como a añadir transparencia a los procesos internos de GitHub. Nuestros usuarios deben saber que valoramos su información privada y que hacemos nuestro mejor esfuerzo para protegerla. Como mínimo, esto significa la liberación de datos a terceros solo cuando se hayan cumplido los requisitos legales adecuados. Por el mismo token, también esperamos educar a los profesionales de la aplicación de la ley sobre los sistemas de GitHub, para que puedan adaptar de manera más eficiente sus solicitudes de datos y dirigir justo esa información necesaria para llevar a cabo su investigación. - -### Terminología GitHub - -Antes de solicitarnos que divulguemos datos, podría ser útil entender cómo se implementa nuestro sistema. GitHub aloja millones de repositorios de datos usando el [sistema de control de versiones Git](https://git-scm.com/video/what-is-version-control). Los repositorios en GitHub—que pueden ser públicos o privados—se utilizan más comúnmente para proyectos de desarrollo de software pero también se utilizan a menudo para trabajar en el contenido de todo tipo. - -- [**Usuarios**](/articles/github-glossary#user) — Los usuarios están representados en nuestro sistema como cuentas personales de GitHub. Cada usuario tiene un perfil personal y puede tener múltiples repositorios. Los usuarios pueden crear o ser invitados a unirse a organizaciones o a colaborar en el repositorio de otro usuario. - -- [**Colaboradores**](/articles/github-glossary#collaborator) — Un colaborador es un usuario con acceso de lectura y escritura a un repositorio que ha sido invitado a contribuir por el propietario del repositorio. - -- [**Organizaciones**](/articles/github-glossary#organization) — Las organizaciones son un grupo de dos o más usuarios que normalmente reflejan las organizaciones del mundo real, como empresas o proyectos. Son administrados por usuarios y pueden contener tanto repositorios como equipos de usuarios. - -- [**Repositorios**](/articles/github-glossary#repository) — Un repositorio es uno de los elementos más básicos de GitHub. Pueden ser los más fáciles de imaginar como una carpeta de un proyecto. Un repositorio contiene todos los archivos del proyecto (incluida la documentación) y almacena cada historial de revisión del archivo. Los repositorios pueden tener múltiples colaboradores y, a discreción de sus administradores, pueden ser públicos o no. - -- [**Páginas**](/articles/what-is-github-pages) — Las páginas de GitHub son páginas web públicas libremente alojadas por GitHub que los usuarios pueden publicar fácilmente a través del código almacenado en sus repositorios. Si un usuario u organización tiene una página de GitHub, generalmente se puede encontrar en una URL como `https://username. ithub.io` o pueden tener la página web mapeada a su propio nombre de dominio personalizado. - -- [**Gists**](/articles/creating-gists) — Gists son fragmentos de código fuente u otro texto que los usuarios pueden usar para almacenar ideas o compartir con amigos. Al igual que los repositorios normales de GitHub, las listas se crean con Git, por lo que son automáticamente versionadas, bifurcables y descargables. Las listas pueden ser públicas o secretas (accesibles solo a través de una URL conocida). Los Gists públicos no pueden convertirse en Gists secretos. - -### Datos de usuario en GitHub.com - -Aquí hay una lista no exhaustiva de los tipos de datos que mantenemos sobre usuarios y proyectos en GitHub. - -- -**Datos de cuenta pública** — Hay una variedad de información disponible públicamente en GitHub sobre los usuarios y sus repositorios. Los perfiles de usuario se pueden encontrar en una URL como `https://github.com/username`. Los perfiles de usuario muestran información acerca de cuándo creó su cuenta el usuario, así como su actividad pública en GitHub.com e interacciones sociales. Los perfiles de usuario públicos también pueden incluir información adicional que un usuario pudo haber decidido compartir públicamente. Visualización de todos los perfiles públicos del usuario: - - Nombre de usuario - - Los repositorios que el usuario ha marcado - - Los otros usuarios de GitHub que el usuario sigue - - Los usuarios que los siguen - - Opcionalmente, un usuario también puede elegir compartir la siguiente información públicamente: - - Su nombre real - - Un avatar - - Una empresa afiliada - - Su ubicación - - Una dirección de correo electrónico pública - - Su página web personal - - Organizaciones de las que el usuario es miembro (*dependiendo de las preferencias de las organizaciones o de los usuarios*) - -- -**Datos privados de la cuenta** — GitHub también recopila y mantiene cierta información privada sobre los usuarios como se describe en nuestra [Política de Privacidad](/articles/github-privacy-statement).+ Puede incluir: - - Direcciones de correo electrónico privadas - - Detalles de pago - - Registros de acceso de seguridad - - Datos sobre interacciones con los repositorios privados - - Para obtener un sentido del tipo de información de cuenta privada que recopila GitHub, puedes visitar tu {% data reusables.user_settings.personal_dashboard %} y navegar por las secciones de la barra de menú de la izquierda. - -- -**Datos de cuenta de la organización** — La información sobre organizaciones, sus usuarios administrativos y repositorios está disponible públicamente en GitHub. Los perfiles de la organización se pueden encontrar en una URL como `https://github.com/organization`. Los perfiles de las organizaciones públicas también pueden incluir información adicional que los propietarios han decidido compartir públicamente. Visualización de todos los perfiles públicos de la organización: - - Nombre de la organización - - Los repositorios que los propietarios han marcado - - Todos los usuarios de GitHub que son propietarios de la organización - - Opcionalmente, los usuarios administrativos también pueden optar por compartir públicamente la siguiente información: - - Un avatar - - Una empresa afiliada - - Su ubicación - - Miembros directos y equipos - - Colaboradores - -- -**Datos del repositorio público** — GitHub es el hogar de millones de proyectos públicos de software de código público. Puede navegar casi cualquier repositorio público (por ejemplo, el [Proyecto Atom](https://github.com/atom/atom)) para tener un sentido de la información que GitHub recopila y mantiene sobre repositorios. Puede incluir: - - - El código - - Versiones anteriores del código - - Versiones de lanzamiento estables del proyecto - - Información sobre colaboradores, contibuyentes y miembros del repositorio - - Registros de operaciones de Git como confirmaciones, ramificar, subir, extraer, bifurcar y clonar - - Conversaciones relacionadas con operaciones de Git como comentarios sobre solicitudes de extracción o confirmaciones - - Documentación del proyecto como Cuestiones y páginas Wiki - - Estadísticas y gráficos que muestran contribuciones al proyecto y a la red de colaboradores - -- -**Datos privados del repositorio** — GitHub recopila y mantiene el mismo tipo de datos para los repositorios privados que se pueden ver en los repositorios públicos, excepto que solamente los usuarios invitados específicamente puedan acceder a los datos del repositorio privado. - -- -**Otros datos** - Adicionalmente, GitHub recopila datos analíticos tales como visitas de páginas e información ocasionalmente voluntaria por nuestros usuarios (por ejemplo, comunicaciones con nuestro equipo de soporte, información de la encuesta y/o registros del sitio). - -### Notificaremos a los propietarios de las cuentas afectadas - -Es nuestra política notificar a los usuarios sobre cualquier solicitud pendiente con respecto a sus cuentas o repositorios, a menos que se nos prohíba por ley u orden judicial hacerlo. Antes de revelar la información del usuario haremos un esfuerzo razonable para notificar a cualquier dueño de la cuenta afectada enviando un mensaje a su dirección de correo electrónico verificada proporcionándoles una copia de la cita, orden judicial u orden para que puedan tener la oportunidad de impugnar el proceso legal si lo desean. En circunstancias (raras) exigentes, podemos retrasar la notificación si determinamos que el retraso es necesario para prevenir la muerte o daños graves. - -### Divulgación de información no pública - -Es nuestra política divulgar información de usuario no pública en relación con una investigación civil o criminal solo con el consentimiento del usuario o tras la recepción de una citación válida, demanda de investigación civil, orden judicial, orden de búsqueda u otro proceso legal válido similar. En ciertas circunstancias exigentes (véase abajo), también podemos compartir información limitada pero sólo correspondiente a la naturaleza de las circunstancias y requeriremos un proceso legal para cualquier tema adicional. GitHub se reserva el derecho de objetar cualquier solicitud de información no pública. Cuando GitHub acuerde producir información no pública en respuesta a una solicitud legal, realizaremos una búsqueda razonable para la información solicitada. Estos son los tipos de información que acordaremos producir, dependiendo del tipo de proceso legal que atendamos: - -- -**Con el consentimiento del usuario** — GitHub proporcionará información de cuenta privada, si se solicita, directamente al usuario (o un propietario, en el caso de una cuenta de organización) o a un tercero designado con el consentimiento por escrito del usuario una vez que GitHub esté satisfecho de que el usuario haya verificado su identidad. - -- -**Con una citación ** — Si atiende una solicitud de investigación civil válida o un proceso legal similar emitido en relación con una investigación penal o civil oficial, podemos proporcionar cierta información de cuenta no pública, que puede incluir: - - - Nombre(s) asociados con la cuenta - - Dirección(es) de correo electrónico asociada(s) a la cuenta - - Información de facturación - - Fecha de registro y fecha de finalización - - Dirección IP, fecha y hora al momento del registro de la cuenta - - Dirección(es) IP utilizada para acceder a la cuenta en un momento o evento específico relevante para la investigación - -En el caso de cuentas de organización, podemos proporcionar el(los) nombre(s) y la(s) dirección(es) de correo electrónico del propietario(s) de la cuenta, así como la fecha y la dirección IP en el momento de la creación de la cuenta de la organización. No produciremos información sobre otros miembros o colaboradores, si existen, a la cuenta de la organización o cualquier información adicional relacionada con el propietario o dueño de la cuenta identificada sin una solicitud de seguimiento para esos usuarios específicos. - -Tenga en cuenta que la información disponible variará de un caso a otro. Parte de la información es opcional para que los usuarios la proporcionen. En otros casos, es posible que no hayamos recopilado ni conservado la información. - -- -**Con una orden judicial *o* una orden de registro** — No divulgaremos registros de acceso a la cuenta a menos que se nos obligue a hacerlo por (i) una orden judicial emitida bajo 18 U. S.C. Sección 2703(d), sobre una muestra de hechos específicos y articulables que demuestran que existen motivos razonables para creer que la información solicitada es relevante y material para una investigación criminal en curso; o (ii) una orden de búsqueda emitida bajo los procedimientos descritos en las Normas Federales de Procedimiento Penal o procedimientos equivalentes de la orden estatal sobre una muestra de causa probable. Además de la información no pública de la cuenta de usuario listada anteriormente podemos proporcionar registros de acceso a la cuenta en respuesta a una orden judicial o a una orden de registro, que puede incluir: - - - Cualquier registro que revele los movimientos de un usuario a lo largo de un período de tiempo - - Configuración de la cuenta o repositorio privado (por ejemplo, qué usuarios tienen ciertos permisos, etc.) - - Datos analíticos específicos del usuario o IP, como el historial de navegación - - Registros de acceso de seguridad distintos a la creación de cuentas o para una fecha y hora específica - -- -**Sólo con una orden de registro** — No divulgaremos el contenido privado de ninguna cuenta de usuario a menos que se lo obligue a hacerlo bajo una orden de registro emitida de acuerdo con los procedimientos descritos en las Normas Federales de Procedimiento Penal o procedimientos equivalentes de la orden estatal al mostrar una causa probable. Además de la información no pública de la cuenta de usuario y los registros de acceso a la cuenta mencionados anteriormente también proporcionaremos contenido privado de la cuenta de usuario en respuesta a una orden de registro, que puede incluir: - - - Contenidos de Gists secretos - - Código fuente u otro contenido en los repositorios privados - - Registros de contribución y colaboración para los repositorios privados - - Comunicaciones o documentación (como Cuestiones o Wikis) en depósitos privados - - Cualquier clave de seguridad usada para autenticación o cifrado - -- **Bajo circunstancias exigentes** — Si recibimos una solicitud de información bajo ciertas circunstancias exigentes (donde creemos que la divulgación es necesaria para prevenir una emergencia que implique peligro de muerte o lesiones físicas graves a una persona), podemos divulgar información limitada que determinamos necesaria para permitir que las fuerzas policiales atiendan la emergencia. Para cualquier información adicional, necesitaríamos una citación, una orden de registro, una orden judicial, como se describe anteriormente. Por ejemplo, no divulgaremos contenidos de repositorios privados sin una orden de registro. Antes de divulgar la información, confirmamos que la solicitud procedía de una agencia policial, que una autoridad haya enviado una notificación oficial resumiendo la emergencia y cómo la información solicitada ayudará a resolver la emergencia. - -### Reembolso de costes - -Nos reservamos el derecho de solicitar el reembolso de los gastos administrativos asociados con la respuesta a las solicitudes de información, de acuerdo con lo permitido por la ley. - -### Conservación de datos - -We will take steps to preserve account records for up to 90 days upon formal request from U.S. law enforcement in connection with official criminal investigations, and pending the issuance of a court order or other process. - -### Cómo enviar solicitudes - -Envía solicitudes a: - -``` -GitHub, Inc. -c/o Corporation Service Company -2710 Gateway Oaks Drive, Suite 150N -Sacramento, CA 95833-3505 -``` - -También puedes enviar una copia de cortesía a legal@support.github.com. - -Por favor, realiza tus solicitudes lo más específicas y limitadas posible, incluyendo la siguiente información: - -- Información completa sobre la autoridad que emite la solicitud de información -- El nombre y el gafete/ID del agente responsable -- Una dirección de correo electrónico oficial y número de teléfono de contacto -- El usuario, organización, nombre(s) del repositorio de interés -- Las URLs de cualquier página, lista o archivos de interés -- La descripción de los tipos de registros que necesitas - -Por favor, espera al menos dos semanas para que podamos examinar tu solicitud. - -### Solicitudes de aplicación de la ley extranjera - -Como empresa de Estados Unidos con sede en California, GitHub no está obligada a proporcionar datos a los gobiernos extranjeros en respuesta al proceso legal emitido por autoridades extranjeras. Los funcionarios encargados de hacer cumplir la ley extranjera que deseen solicitar información a GitHub deben ponerse en contacto con la Oficina de Asuntos Internacionales del Departamento de Justicia de los Estados Unidos. GitHub responderá rápidamente a las solicitudes que se emitan a través del tribunal de los Estados Unidos mediante un tratado de asistencia legal mutuo (“MLAT”) o exhorto. court by way of a mutual legal assistance treaty (“MLAT”) or letter rogatory. - -### Preguntas - -¿Tiene otras preguntas, comentarios o sugerencias? Ponte en contacto con {% data variables.contact.contact_support %}. diff --git a/translations/es-XL/content/github/site-policy/index.md b/translations/es-XL/content/github/site-policy/index.md deleted file mode 100644 index 51458c278a..0000000000 --- a/translations/es-XL/content/github/site-policy/index.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Política del sitio -redirect_from: - - /categories/61/articles/ - - /categories/site-policy -versions: - fpt: '*' -topics: - - Policy - - Legal -children: - - /github-terms-of-service - - /github-corporate-terms-of-service - - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers - - /global-privacy-practices - - /github-sponsors-additional-terms - - /github-codespaces-privacy-statement - - /github-terms-for-additional-products-and-features - - /github-logo-policy - - /github-username-policy - - /submitting-content-removal-requests - - /dmca-takedown-policy - - /guide-to-submitting-a-dmca-takedown-notice - - /guide-to-submitting-a-dmca-counter-notice - - /github-trademark-policy - - /github-private-information-removal-policy - - /github-subprocessors-and-cookies - - /github-bug-bounty-program-legal-safe-harbor - - /responsible-disclosure-of-security-vulnerabilities - - /guidelines-for-legal-requests-of-user-data - - /github-government-takedown-policy - - /github-acceptable-use-policies - - /githubs-notice-about-the-california-consumer-privacy-act - - /github-community-guidelines - - /github-community-forum-code-of-conduct - - /github-registered-developer-agreement - - /github-marketplace-terms-of-service - - /github-marketplace-developer-agreement - - /github-research-program-terms - - /github-open-source-applications-terms-and-conditions - - /github-and-trade-controls - - /github-deceased-user-policy - - /github-statement-against-modern-slavery-and-child-labor - - /github-anti-bribery-statement - - /github-candidate-privacy-policy - - /github-gifts-and-entertainment-policy - - /github-event-terms - - /github-event-code-of-conduct - - /github-gpl-cooperation-commitment ---- -### Índice diff --git a/translations/es-XL/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md b/translations/es-XL/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md deleted file mode 100644 index e5039528de..0000000000 --- a/translations/es-XL/content/github/site-policy/responsible-disclosure-of-security-vulnerabilities.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Divulgación responsable de vulnerabilidades de seguridad -redirect_from: - - /responsible-disclosure/ - - /articles/responsible-disclosure-of-security-vulnerabilities -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Deseamos mantener a GitHub seguro para todos. Si has descubierto una vulnerabilidad de seguridad en GitHub, apreciamos tu ayuda para revelárnosla de manera responsable. - -### Programa de recompensas - -Al igual que muchas otras grandes empresas de software, GitHub proporciona una recompensa de errores para mejorar la relación con los investigadores de seguridad. La idea es simple: Los hackers y los investigadores de seguridad (como tú) encuentran y reportan vulnerabilidades a través de nuestro proceso de divulgación responsable. Posteriormente, para reconocer el esfuerzo significativo que estos investigadores suelen presentan cuando cazan errores, los recompensamos con algo de dinero en efectivo. - -Revisa el sitio [Recompensa de Errores de GitHub](https://bounty.github.com) para obtener detalles de recompensas, revisa también nuestros términos amplios de la [Disposición de seguridad legal ](/articles/github-bug-bounty-program-legal-safe-harbor) y ¡Feliz caza! diff --git a/translations/es-XL/content/github/site-policy/submitting-content-removal-requests.md b/translations/es-XL/content/github/site-policy/submitting-content-removal-requests.md deleted file mode 100644 index aa67915846..0000000000 --- a/translations/es-XL/content/github/site-policy/submitting-content-removal-requests.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Enviar solicitudes de eliminación de contenido -redirect_from: - - /articles/submitting-content-removal-requests -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -Entendemos que los derechos de autor, marca registrada, o contenido sensible puede publicarse en GitHub –ya sea accidentalmente o con fin– a veces en repositorios que no posees. Debido a que la naturaleza de este contenido varía y debido a las diferentes leyes aplicables, cada categoría tiene sus propios requisitos de presentación de informes definidos en nuestras políticas. - -Si quieres solicitar que el contenido se elimine de GitHub, por favor toma algo de tiempo para consultar cada una de estas políticas y sus respectivos requisitos para informar antes de enviar un informe. Si recibimos un informe incompleto, tendremos que pedir aclaraciones o revisiones y tendrás que enviar nuevamente un informe revisado. - -Ten en cuenta que no podemos ayudarte a determinar qué política es adecuada para su situación específica. Si revisaste las siguientes políticas y aún tienes preguntas sobre si el contenido debe informarse o no como copyright o datos sensibles, recomendamos consultar con asesoría jurídica independiente. - -### [Política de retiro de DMCA](/articles/dmca-takedown-policy) -La Política de Retiro de DMCA se puede utilizar para informar del contenido que consideras que infringe un copyright propiedad de tu parte o de su organización. Una vez que hayas revisado la política, es posible que también desees revisar nuestra [Guía para enviar una Política de Retiro de DMCA](/articles/guide-to-submitting-a-dmca-takedown-notice/) antes de enviar un informe. - -### [Política de marca registrada de GitHub](/articles/github-trademark-policy) -La Política de Marcas de GitHub se puede utilizar para informar del contenido que parece utilizar su nombre de empresa o de negocio, logotipo, u otros materiales protegidos por marca de una manera que pueda engañar o confundir a otros sobre la marca o la afiliación comercial. - -### [Política de eliminación de datos sensibles de GitHub](/articles/github-sensitive-data-removal-policy) -La Política de Eliminación de Datos Sensibles de GitHub se puede utilizar para informar de datos que son sensibles o confidenciales y plantean un riesgo de seguridad, pero eso no está necesariamente protegido por derechos de autor o marca registrada. diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/index.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/index.md deleted file mode 100644 index 2074b91788..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Soporte a la comunidad de código abierto con los patrocinadores de GitHub -shortTitle: Patrocinadores de GitHub -intro: 'You can support the people and organizations who design, build, and maintain the open source projects you depend on by compensating them via {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /categories/supporting-the-open-source-community-with-github-sponsors -versions: - free-pro-team: '*' -children: - - /overview - - /sponsoring-open-source-contributors - - /receiving-sponsorships-through-github-sponsors ---- -### Índice diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/overview/about-github-sponsors.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/overview/about-github-sponsors.md deleted file mode 100644 index 8e163f3816..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/overview/about-github-sponsors.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Acerca de los Patrocinadores de GitHub -intro: '{% data variables.product.prodname_sponsors %}permite a la comunidad de desarrolladores apoyar financieramente al personal y organizaciones que diseñan, construyen y mantienen los proyectos de código abierto de los cuales dependen, directamente en {% data variables.product.product_name %}.' -redirect_from: - - /articles/about-github-sponsors - - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors -versions: - free-pro-team: '*' ---- -### Acerca de {% data variables.product.prodname_sponsors %} - -{% data reusables.sponsors.sponsorship-details %}{% data reusables.sponsors.no-fees %} Para obtener más información, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". - -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_sponsors %} para colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario ](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)". - -{% data reusables.sponsors.you-can-be-a-sponsored-organization %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)". - -Cuando te conviertes en un desarrollador patrocinado u organización patrocinada, aplicarán las condiciones adicionales de {% data variables.product.prodname_sponsors %}. Para obtener más información, consulta la sección "[Condiciones Adicionales de GitHub Sponsors](/github/site-policy/github-sponsors-additional-terms)". - -### Acerca de {% data variables.product.prodname_matching_fund %} - -{% note %} - -**Nota:**{% data reusables.sponsors.matching-fund-eligible %} - -{% endnote %} - -El {% data variables.product.prodname_matching_fund %} pretende beneficiar a los miembros de la comunidad de {% data variables.product.prodname_dotcom %} quienes desarrollan software de código abierto que promueve los [Lineamientos de la Comunidad de {% data variables.product.prodname_dotcom %}](/github/site-policy/github-community-guidelines). Las organizaciones patrocinadas no son elegibles para {% data variables.product.prodname_matching_fund %}. - -Para ser elegible para el {% data variables.product.prodname_matching_fund %}, debes crear un perfil que atraiga a la comunidad que te mantendrá a largo plazo. Para obtener más información acerca de crear un perfil llamativo, consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)". - -{% data reusables.sponsors.legal-additional-terms %} - -### Intercambiar opiniones acerca de {% data variables.product.prodname_sponsors %} - -Este es sólo el inicio — nos encantaría tener tu opinión para garantizar que {% data variables.product.prodname_sponsors %} siga satisfaciendo tus necesidades. Por favor, envíanos tu retroalimentación o sugerencias contactando a [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). - -Actualmente, solo los usuarios individuales pueden patrocinar a desarrolladores y organizaciones. Si a tu organización le interesa patrocinar desarrolladores, por favor, háznoslo saber contactando a [{% data variables.contact.github_support %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub+Sponsors). - -### Leer más -- "[Patrocinar a contribuyentes de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)" -- "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)". -- "[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-XL/content/github/supporting-the-open-source-community-with-github-sponsors/overview/index.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/overview/index.md deleted file mode 100644 index 4e8fd67642..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/overview/index.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Resumen -intro: 'Aprende sobre {% data variables.product.prodname_sponsors %} y sobre cómo puedes involucrarte como patrocinador o como colaborador de código abierto.' -versions: - free-pro-team: '*' -children: - - /about-github-sponsors ---- - diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md deleted file mode 100644 index b5fe779c0e..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Acerca de los patrocinadores para colaboradores de código abierto en GitHub -intro: 'Si aportas valor a un proyecto de código abierto, puedes convertirte en un colaborador patrocinado para recibir pagos por tu trabajo.' -redirect_from: - - /articles/about-github-sponsors-for-sponsored-developers - - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers - - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors -versions: - free-pro-team: '*' ---- -### Unirte a {% data variables.product.prodname_sponsors %} - -{% data reusables.sponsors.you-can-be-a-sponsored-developer %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)". - -{% data reusables.sponsors.you-can-be-a-sponsored-organization %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)". - -Una vez que te hayas unido a {% data variables.product.prodname_sponsors %}, puedes añadir un botón de "patrocinar" al repositorio de código abierto en el que contribuyes para incrementar la visibilidad de tu perfil de {% data variables.product.prodname_sponsors %} y de otras plataformas de fondeo. Para obtener más información, consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)". - -Puedes configurar una meta para tus patrocinios. Para obtener más información, consulta la sección "[Administrar tu meta de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal)". - -{% data reusables.sponsors.github-contact-applicants %} - -### Niveles de patrocinio - -{% data reusables.sponsors.tier-details %}Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)", "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)", y "[Cambiar tus niveles de patrocinio](/articles/changing-your-sponsorship-tiers)". - -### Pagos de patrocinios - -{% data reusables.sponsors.no-fees %} - -{% data reusables.sponsors.payout-info %} - -Para obtener más información, consulta "[Administrar tus pagos de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors)". - -### Leer más -- "[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-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/changing-your-sponsorship-tiers.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/changing-your-sponsorship-tiers.md deleted file mode 100644 index 57d72b5bda..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/changing-your-sponsorship-tiers.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Cambiar tus niveles de patrocinio -intro: Puedes agregar un nuevo nivel de patrocinio o editar o retirar un nivel existente. -redirect_from: - - /articles/changing-your-sponsorship-tiers - - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers -versions: - free-pro-team: '*' ---- -### Acerca de los niveles de patrocinio - -{% data reusables.sponsors.tier-details %} - -{% data reusables.sponsors.maximum-tier %} - -### Añadir un nivel para tu perfil de desarrollador patrocinado - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} -{% data reusables.sponsors.click-add-tier %} -{% data reusables.sponsors.tier-price-description %} -{% data reusables.sponsors.save-tier-draft %} -{% data reusables.sponsors.review-and-publish-tier %} - -### Añadir un nivel para tu perfil de organización patrocinada - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} -{% data reusables.sponsors.click-add-tier %} -{% data reusables.sponsors.tier-price-description %} -{% data reusables.sponsors.save-tier-draft %} -{% data reusables.sponsors.review-and-publish-tier %} - -### Editar o revocar un nivel para tu perfil de desarrollador patrocinado - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} -{% data reusables.sponsors.edit-tier %} -{% data reusables.sponsors.tier-price-description %} -{% data reusables.sponsors.tier-update %} -{% data reusables.sponsors.retire-tier %} - -### Editar o revocar un nivel para tu perfil de organización patrocinada - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} -{% data reusables.sponsors.edit-tier %} -{% data reusables.sponsors.tier-price-description %} -{% data reusables.sponsors.tier-update %} -{% data reusables.sponsors.retire-tier %} diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md deleted file mode 100644 index 03a119516e..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Configurar webhooks para eventos en tu cuenta patrocinada -intro: Puedes configurar wehbhooks para que te envíen una alerta cuando recibas nuevos patrocinios o cuando los patrocinadores existentes realicen cambios a sus patrocinios. -versions: - free-pro-team: '*' -redirect_from: - - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account ---- -Para monitorear los cambios a tus patrocinios, tales como las cancelaciones al final de un periodo de pago, puedes crear webhooks para tu cuenta patrocinada de usuario u organización. Cuando estableces un webhook para tu cuenta patrocinada de usuario u organización, recibirás actualizaciones cuando se creen, editen o borren los patrocinios. Para obtener más información, consulta el [evento de webhook de `sponsorship`](/webhooks/event-payloads/#sponsorship). - -### Administrar los webhooks para tu cuenta de usuario patrocinada - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-webhooks-tab %} -{% data reusables.sponsors.add-webhook %} -{% data reusables.sponsors.add-payload-url %} -{% data reusables.sponsors.webhook-content-formatting %} -{% data reusables.sponsors.webhook-secret-token %} -{% data reusables.sponsors.add-active-triggers %} -{% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} - -### Administrar webhooks para tu cuenta de organización patrocinada - -Los propietarios de organización pueden configurar webhooks para sus organizaciones patrocinadas. - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-webhooks-tab %} -{% data reusables.sponsors.add-webhook %} -{% data reusables.sponsors.add-payload-url %} -{% data reusables.sponsors.webhook-content-formatting %} -{% data reusables.sponsors.webhook-secret-token %} -{% data reusables.sponsors.add-active-triggers %} -{% data reusables.sponsors.confirm-add-webhook %} -{% data reusables.sponsors.manage-existing-webhooks %} diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md deleted file mode 100644 index a166d3ee8b..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Comunicarse con tus patrocinadores -intro: Puedes enviar un correo electrónico a los patrocinadores que optaron por recibir actualizaciones sobre tu trabajo. -redirect_from: - - /articles/contacting-your-sponsors - - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors -versions: - free-pro-team: '*' ---- -Tus patrocinadores pueden elegir si desean recibir actualizaciones por correo electrónico sobre tu trabajo. Para obtener más información, consulta "[Administar tu patrocinio](/articles/managing-your-sponsorship)". - -La actualización vendrá de la dirección principal de correo electrónico en tu cuenta de usuario o de aquella de tipo `noreply@github.com` de tu organización. Si habilitaste la privacidad de direcciones de correo electrónico en tu cuenta de usuario, la actualización vendrá entonces de `noreply@github.com`. Para obtener más información, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)". - -### Contactar a los patrocinadores de tu cuenta de usuario - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.sponsors-updates-tab %} -{% data reusables.sponsors.draft-new-update %} -{% data reusables.sponsors.send-update-to-sponsors %} -{% data reusables.sponsors.write-sponsor-update %} -{% data reusables.sponsors.publish-sponsor-update %} - -### Contactar a los patrocinadores de tu organización - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.sponsors-updates-tab %} -{% data reusables.sponsors.draft-new-update %} -{% data reusables.sponsors.send-update-to-sponsors %} -{% data reusables.sponsors.write-sponsor-update %} -{% data reusables.sponsors.publish-sponsor-update %} diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md deleted file mode 100644 index d7cca4d35b..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Editar los detalles de tu perfil para los Patrocinadores de GitHub -intro: Puedes actualizar la información que ven los patrocinadores potenciales acerca de tu trabajo. -redirect_from: - - /articles/editing-your-sponsored-developer-profile - - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile - - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors -versions: - free-pro-team: '*' ---- -### Acerca de los perfiles de patrocinador - -Tu perfil de {% data variables.product.prodname_sponsors %} les dice a los patrocinadores potenciales por qué deberían patrocinarte. Las personas ven tu perfil de patrocinio cuando dan clic en el botón **Patrocinar** en tu perfil personal o de organización. Te recomendamos incluir la información siguiente. - -- Trabajo de código abierto al que has contribuido. -- Por qué estás comprometido con el desarrollo de código abierto. - -También puedes establecer metas para explicar los diferentes niveles de patrocinio que te permitirán trabajar para la comunidad. - -### Editar tu perfil de programador patrocinado - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### Editar tu perfil de organización patrocinada - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.meet-the-team %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/index.md deleted file mode 100644 index 3323979723..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/index.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Recibir patrocinios a través de patrocinadores de GitHub -shortTitle: Recibir patrocinios -intro: 'You or your organization can become a sponsored open source contributor to receive payments for your work, update your sponsorship details, and view and contact your sponsors.' -redirect_from: - - /articles/receiving-sponsorships-as-a-sponsored-developer - - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer -versions: - free-pro-team: '*' -children: - - /about-github-sponsors-for-open-source-contributors - - /setting-up-github-sponsors-for-your-user-account - - /setting-up-github-sponsors-for-your-organization - - /editing-your-profile-details-for-github-sponsors - - /managing-your-sponsorship-goal - - /changing-your-sponsorship-tiers - - /viewing-your-sponsors-and-sponsorships - - /managing-your-payouts-from-github-sponsors - - /configuring-webhooks-for-events-in-your-sponsored-account - - /contacting-your-sponsors - - /tax-information-for-github-sponsors ---- - diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md deleted file mode 100644 index e436d11aa0..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Administrar tus pagos desde Patrocinadores de GitHub -intro: 'Puedes ver información sobre pagos pasados y futuros desde {% data variables.product.prodname_sponsors %} y editar tu información bancaria.' -redirect_from: - - /articles/managing-your-payouts-from-github-sponsors - - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors -versions: - free-pro-team: '*' ---- -### Acerca de los pagos de {% data variables.product.prodname_sponsors %} - -Solo puedes administrar tus pagos de {% data variables.product.prodname_sponsors %} si recibes tu pago a través de Stripe Connect. Si se te paga a través de transferencia ACH o transferencia bancaria en tu cuenta de usuario, no verás la pestaña de **Pagos** en tu tablero de colaborador de código abierto. Las organizaciones patrocinadas solo podrán utilizar Stripe Connect para los pagos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_sponsors %} para los colaboradores de código abierto](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts)". - -{% data reusables.sponsors.payout-info %} - -### Visualizar y editar la información de pago para tu cuenta de usuario patrocinado - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} - -### Visualizar y editar la información de pago para tu cuenta de organización patrocinada - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-payouts-tab %} -{% data reusables.sponsors.edit-bank-information %} diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md deleted file mode 100644 index b6156be0c8..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Administrar tu meta de patrocinio -intro: Puedes configurar una meta para tu perfil de desarrollador u organización patrocinados para ayudar a la comunidad a entender el impacto que tiene el patrocinarte. -versions: - free-pro-team: '*' -redirect_from: - - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal ---- -### Acerca de las metas de patrocinio - -Puedes configurar una meta de financiamiento para tu perfil de desarrollador u organización patrocinados y compartirla con tu comunidad. Las metas te ayudan a entender el impacto que tienes en la comunidad de código abierto y aumentan tu presencia en el programa de {% data variables.product.prodname_sponsors %}. - -Tu meta puede configurar un objetivo para la cantidad de patrocinadores que quieres tener o la cantidad de dinero que quieres ganar mensualmente. Solo puedes configurar una meta a la vez. Después de que llegues a tu meta, puedes configurar otra. - -### Configurar una meta para una organización patrocinada - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.set-a-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### Configurar una meta para un desarrollador patrocinado - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.set-a-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### Editar una meta - -Cuando editas una meta, no puedes escoger la meta que ya hayas alcanzado. Por ejemplo, si ya tienes 5 patrocinadores, no puedes editar tu meta para que ahora sea de 4 patrocinadores. - -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.edit-goal %} -{% data reusables.sponsors.select-goal-type %} -{% data reusables.sponsors.publish-goal %} - -### Retirar una meta - -Después de que retiras una meta, no podrás reactivarla. En vez de esto, debes crear una meta nueva. - -{% data reusables.sponsors.navigate-to-your-goals-tab %} -{% data reusables.sponsors.edit-goal %} -{% data reusables.sponsors.retire-goal %} diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md deleted file mode 100644 index 26f54f2f67..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: Configurar los Patrocinadores de GitHub para tu organización -intro: 'Tu organización puede unirse a {% data variables.product.prodname_sponsors %} para recibir pagos por tu trabajo.' -redirect_from: - - /articles/setting-up-github-sponsorship-for-your-organization - - /articles/receiving-sponsorships-as-a-sponsored-organization - - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization -permissions: 'Los propietarios de organización pueden configurar {% data variables.product.prodname_sponsors %} para una organización.' -versions: - free-pro-team: '*' ---- -### Unirte a {% data variables.product.prodname_sponsors %} - -{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %} - -Después de recibir una invitación para que tu organización se una a {% data variables.product.prodname_sponsors %} puedes completar los pasos a continuación para que se convierta en una organización patrocinada. - -Para unirte a {% data variables.product.prodname_sponsors %} como un colaborador individual independiente a una organización, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)". - -{% data reusables.sponsors.navigate-to-github-sponsors %} -{% data reusables.sponsors.view-eligible-accounts %} -3. A la derecha de tu organización, da clic en **Unirse a la lista de espera**. -{% data reusables.sponsors.contact-info %} -{% data reusables.sponsors.accept-legal-terms %} - -### Completar un perfil de organización patrocinada - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.meet-the-team %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### Crear niveles de patrocinio - -{% data reusables.sponsors.tier-details %} - -{% data reusables.sponsors.maximum-tier %} - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} -{% data reusables.sponsors.click-add-tier %} -{% data reusables.sponsors.tier-price-description %} -{% data reusables.sponsors.save-tier-draft %} -{% data reusables.sponsors.review-and-publish-tier %} -{% data reusables.sponsors.add-more-tiers %} - -### Emitir tu información bancaria - -Como organización patrocinada, deberás recibir pagos en una cuenta bancaria dedicada a tu organización en una región compatible. Puedes obtener una cuenta bancaria comercial a través de servicios como [Open Collective](https://opencollective.com/) y [Stripe Atlas](https://stripe.com/atlas). {% data reusables.sponsors.stripe-supported-regions %} - -{% data reusables.sponsors.double-check-stripe-info %} - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.create-stripe-account %} - -Para obtener más información acerca de cómo configurar Stripe Connect utilizando Open Collective, consulta la sección [Configurar {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) en los documentos de Open Collective. - -### Emitir tu información de facturación - -{% data reusables.sponsors.tax-form-information-org %} - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.settings-tab %} -{% data reusables.sponsors.country-of-residence %} -{% data reusables.sponsors.overview-tab %} -{% data reusables.sponsors.tax-form-link %} - -### Habilitar la autenticación de dos factores (2FA) en tu cuenta {% data variables.product.prodname_dotcom %} - -Antes de que tu organización pueda convertirse en patrocinada, deberás habilitar la autenticación de dos factores en tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". - -### Enviar tu aplicación a {% data variables.product.prodname_dotcom %} para su aprobación - -{% data reusables.sponsors.navigate-to-org-sponsors-dashboard %} -{% data reusables.sponsors.request-approval %} - -{% data reusables.sponsors.github-review-app %} - -### Leer más -- "[Acerca de {% data variables.product.prodname_sponsors %}](/articles/about-github-sponsors)" -- "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors)". diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md deleted file mode 100644 index 650868e2bc..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Configurar a los Patrocinadores de GitHub para tu cuenta de usuario -intro: 'Puedes convertirte en un programador patrocinado al unirte a {% data variables.product.prodname_sponsors %}, completar tu perfil de programador patrocinado, crear niveles de patrocinio, enviar tu información bancaria y fiscal, y permitir una autenticación de dos factores en tu cuenta de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /articles/becoming-a-sponsored-developer - - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer - - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account -versions: - free-pro-team: '*' ---- -### Unirte a {% data variables.product.prodname_sponsors %} - -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %} - -Para unirte a {% data variables.product.prodname_sponsors %} comoorganización, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)". - -{% data reusables.sponsors.navigate-to-github-sponsors %} -2. Si eres un propietario de organización, tienes más de una cuenta elegible. Da clic en **Ver tus cuentas elegibles** y, posteriormente, en la lista de cuentas, encuentra tu cuenta de usuario. -3. Da clic en **Unirse a la lista de espera**. -{% data reusables.sponsors.contact-info %} -{% data reusables.sponsors.accept-legal-terms %} - -Si tienes una cuenta bancaria en una región compatible, {% data variables.product.prodname_dotcom %} revisará tu aplicación dentro de dos semanas. - -### Completar un perfil de programador patrocinado - -Una vez que {% data variables.product.prodname_dotcom %} revise tu aplicación, podrás configurar tu perfil de desarrollador patrocinado para que las personas puedan comenzar a patrocinarte. - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-profile-tab %} -{% data reusables.sponsors.short-bio %} -{% data reusables.sponsors.add-introduction %} -{% data reusables.sponsors.edit-featured-work %} -{% data reusables.sponsors.opt-in-to-being-featured %} -{% data reusables.sponsors.save-profile %} - -### Crear niveles de patrocinio - -{% data reusables.sponsors.tier-details %} - -{% data reusables.sponsors.maximum-tier %} - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} -{% data reusables.sponsors.click-add-tier %} -{% data reusables.sponsors.tier-price-description %} -{% data reusables.sponsors.save-tier-draft %} -{% data reusables.sponsors.review-and-publish-tier %} -{% data reusables.sponsors.add-more-tiers %} - -### Emitir tu información bancaria - -Si vives en una región compatible, puedes seguir estas instrucciones para emitir tu información bancaria y crear una cuenta de Stripe Connect. {% data reusables.sponsors.stripe-supported-regions %} - -{% data reusables.sponsors.double-check-stripe-info %} - -Si vives en una región que no es compatible y se te acepta en el beta de {% data variables.product.prodname_sponsors %}, recibirás un correo electrónico con isntrucciones para proporcionar tu información bancaria para que puedas recibir pagos a través de transferencia ACH o transferencia bancaria. - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.create-stripe-account %} - -### Emitir tu información de facturación - -{% data reusables.sponsors.tax-form-information-dev %} - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -{% data reusables.sponsors.settings-tab %} -{% data reusables.sponsors.country-of-residence %} -{% data reusables.sponsors.overview-tab %} -{% data reusables.sponsors.tax-form-link %} - -### Habilitar la autenticación de dos factores (2FA) en tu cuenta {% data variables.product.prodname_dotcom %} - -Antes de que puedas convertirte en un programador patrocinado, debes habilitar 2FA en tu cuenta {% data variables.product.product_name %}. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". - -### Enviar tu aplicación a {% data variables.product.prodname_dotcom %} para su aprobación - -{% data reusables.sponsors.navigate-to-dev-sponsors-dashboard %} -4. Haz clic en **Request approval** (Solicitar aprobación). ![Botón Request approval (Solicitar aprobación)](/assets/images/help/sponsors/request-approval-button.png) - -{% data reusables.sponsors.github-review-app %} diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md deleted file mode 100644 index 8450e481e5..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Información de facturación para los Patrocinadores de GitHub -intro: 'Los desarrolladores y organizaciones patrocinados deben emitir su información fiscal a {% data variables.product.prodname_dotcom %} y son responsables de evaluar y pagar sus propios impuestos.' -redirect_from: - - /articles/tax-information-for-sponsored-developers - - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers - - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-github-sponsors -versions: - free-pro-team: '*' ---- -Si eres contribuyente en los Estados Unidos, debes enviar un W-9 antes de poder recibir pagos. Si eres un contribuyente en cualquier otra región de los Estados Unidos, deberás emitir un W-8BEN antes de que puedas recibir pagos. Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-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](/github/supporting-the-open-source-community-with-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 contribuyente en los Estados Unidos y ganas más de $600 en un año fiscal, {% data variables.product.prodname_dotcom %} te enviará un 1099 antes del 31 de enero del siguiente año calendario. No proporcionamos formularios fiscales para los contribuyentes internacionales. - -{% 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 %} - -### Leer más - -- [Ver tus patrocinadores y patrocinios](/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md deleted file mode 100644 index 74e3986158..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Ver tus patrocinadores y patrocinios -intro: Puedes ver y exportar la información detallada y la analítica de tus patrocinadores y patrocinios. -redirect_from: - - /articles/viewing-your-sponsors-and-sponsorships - - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships -versions: - free-pro-team: '*' ---- -Puedes ver la analítica de tus patrocinios actuales y pasados, los pagos que has recibido de tus patrocinadores, y los eventos tales como las cancelaciones y cambios de nivel de patrocinio para tus patrocinios. También puedes ver la actividad tal como los nuevos patrocinios, cambios, y cancelaciones de los mismos. Puedes filtrar la lista de actividades por fecha. También puedes exportar datos del patrocinio en formato CSV o JSON para la cuenta que estás viendo. - -Puedes acceder a toda esta información desde tu tablero de Patrocinadores. - -### Visualizar tu tablero de Patrocinadores - -1. En la esquina superior derecha de cualquier página, da clic en tu foto de perfil, posteriormente, da clic en **{% data variables.product.prodname_sponsors %}**. ![Botón de {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. En la lista que se muestra, a la derecha de la cuenta u organización cuyo tablero de patrocinadores quieres ver, da clic en **Tablero**. ![Botón de tablero para patrocinadores del desarrollador](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) - -### Ver tus patrocinadores y patrocinios - -1. Ve a tu tablero de Patrocinadores, consulta la sección [Visualizar tu tablero de patrocinadores](#viewing-your-sponsors-dashboard). -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. Como alternativa, para filtrar los patrocinadores por nivel, utiliza el menú desplegable de **Filter** (Filtro), haz clic en **Active tiers** (Niveles activos) o **Retired tiers** (Niveles retirados) y selecciona un nivel. ![Menú desplegable para filtrar por nivel](/assets/images/help/sponsors/filter-drop-down.png) - -### Visualizar la actividad de patrocinio reciente - -1. Ve a tu tablero de patrocinadores, consulta la sección [Visualizar tu tablero de patrocinadores](#viewing-your-sponsors-dashboard). -1. En la barra lateral izquierda, da clic en **Actividad**. ![Pestaña de actividad](/assets/images/help/sponsors/activity-tab.png) - -### Exportar tus datos de patrocinio - -1. Ve a tu tablero de patrocinadores, consulta la sección [Visualizar tu tablero de patrocinadores](#viewing-your-sponsors-dashboard). -{% data reusables.sponsors.navigate-to-sponsors-tab %} -1. Da clic en **Exportar todo**. ![Botón de exportar todo](/assets/images/help/sponsors/export-all.png) - - Este botón no se mostrará si no tienes patrocinadores. - -1. Elige un formato y periodo de tiempo para los datos que quieres exportar. Posteriormente, da clic en **Comenzar exportación**. ![Opciones para exportar datos](/assets/images/help/sponsors/export-your-sponsors.png) - - {% data variables.product.prodname_dotcom %} Comienza a exportar datos para todos tus patrocinadores desde el mes que seleccionaste. Se te enviará un correo electrónico enseguida con un adjunto que contiene los datos. Después de que la exportación se complete, puedes exportar otro mes de datos. Puedes exportar hasta 10 conjuntos de datos por hora para cualquiera de tus organizaciones patrocinadas o cuentas de usuario. diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/index.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/index.md deleted file mode 100644 index 9be1b69722..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Patrocinar a colaboradores de código abierto -intro: 'Puedes patrocinar colaboradores, recibir actualizaciones sobre los programadores y las organizaciones que patrocinas, y mostrar una insignia de patrocinador en todo {% data variables.product.product_name %}.' -redirect_from: - - /articles/sponsoring-open-source-developers - - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers -versions: - free-pro-team: '*' -children: - - /sponsoring-an-open-source-contributor - - /managing-your-sponsorship ---- - diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md deleted file mode 100644 index 6409b66cd4..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Administrar tu patrocinio -intro: 'Puedes administrar quién puede ver tu patrocinio, así como si recibes o no actualizaciones por correo electrónico por parte de los colaboradores de código abierto patrocinados.' -redirect_from: - - /articles/managing-your-sponsorship - - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship -versions: - free-pro-team: '*' ---- -Para obtener más información sobre cómo cambiar tu nivel de patrocinio, consulta "[Actualizar un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)." - -### Administrar la configuración de privacidad para tu patrocinio de desarrollador - -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} -{% data reusables.sponsors.who-can-see-your-sponsorship %} -{% data reusables.sponsors.update-sponsorship %} - -### Administrar la configuración de privacidad para tu patrocinio de organización - -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.who-can-see-your-sponsorship %} -{% data reusables.sponsors.update-sponsorship %} - -### Administrar las actualizaciones de correo electrónico de un programador patrocinado - -Puedes elegir si un programador patrocinado puede enviarte actualizaciones por correo electrónico sobre su trabajo. El programador patrocinado no tendrá acceso a tu dirección de correo electrónico. - -{% data reusables.sponsors.navigate-to-sponsored-developer %} -{% data reusables.sponsors.manage-developer-sponsorship %} -{% data reusables.sponsors.developer-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} - -### Administrar las actualizaciones por correo electrónico de una organización patrocinada - -Puedes elegir si una organización patrocinada puede enviarte o no actualizaciones de su trabajo por correo electrónico. La organización patrocinada no tendrá acceso a tu dirección de correo electrónico. - -{% data reusables.sponsors.navigate-to-sponsored-org %} -{% data reusables.sponsors.manage-org-sponsorship %} -{% data reusables.sponsors.org-sponsored-choose-updates %} -{% data reusables.sponsors.update-sponsorship %} diff --git a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md deleted file mode 100644 index a677ae763e..0000000000 --- a/translations/es-XL/content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Patrocinar a un colaborador de código abierto -intro: 'Puedes generar un pago mensual recurrente para un desarrollador u organización que diseñe, cree, o mantenga los proyectos de código abierto de los que dependes.' -redirect_from: - - /articles/sponsoring-a-developer - - /articles/sponsoring-an-open-source-contributor - - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer - - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor -versions: - free-pro-team: '*' ---- -### Acerca de patrocinar desarrolladores y organizaciones - -{% data reusables.sponsors.sponsorship-details %}{% data reusables.sponsors.no-fees %} Para obtener más información, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". - -Cuando patrocinas a un colaborador de código abierto, el cambio tomará lugar inmediatamente. {% data reusables.sponsors.prorated-sponsorship %} - -Si el colaborador de código abierto patrocinado revoca tu nivel, éste nivel permanecerá configurado para ti hasta que escojas un nivel diferente, o hasta que canceles tu suscripción. Para obtener más información, consulta "[Actualizar un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)." - -Si el colaborador de código abierto que quieres patrocinar no tiene un perfil de organización o desarrollador patrocinados, puedes alentarlo a crear un perfil de este tipo. Para obtener más información, consulta las secciónes "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization)". - -{% data reusables.sponsors.sponsorships-not-tax-deductible %} - -{% note %} - -**Nota:**{% data variables.product.prodname_dotcom %} no se responzabiliza por cómo se auto-representan los desarrolladores ni tampoco respalda ninguno de los proyectos de código abierto patrocinados. Las alegaciones son responsabilidad total del desarrollador que recibe los fondos. Asegúrate de que confías en una persona antes de ofrecerle un patrocinio. Para obtener más información, consulta la sección de [Condiciones Adicionales de {% data variables.product.prodname_sponsors %}](/github/site-policy/github-sponsors-additional-terms). - -{% endnote %} - -### Patrocinar a un programador - -Antes de que patrocines a un desarrollador, deberás contar con una dirección de correo electrónico verificada. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)". - -1. En {% data variables.product.product_name %}, desplázate hasta el perfil de la persona a la que deseas patrocinar. -2. Dentro del nombre del programador, haz clic en **Sponsor (Patrocinador)**. ![Botón de Patrocinador](/assets/images/help/profile/sponsor-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.select-sponsorship-billing %} - ![Botón de Editar pago](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) -{% data reusables.sponsors.who-can-see-your-sponsorship %} - ![Botones radiales para elegir quién puede ver tu patrocinio](/assets/images/help/sponsors/who-can-see-sponsorship.png) -{% data reusables.sponsors.developer-sponsored-choose-updates %} -7. Haz clic en **Sponsor (Patrocinador) _DEVELOPER_**. ![Botón del Programador patrocinado](/assets/images/help/sponsors/sponsor-developer-button.png) - -### Patrocinar una organización - -Antes de que puedas patrocinar a una organización, deberás contar con una dirección de correo electrónico verificada. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)". - -1. En {% data variables.product.product_name %}, navega a la página de la organización que quieres patrocinar. -2. A un costado del nombre de la misma, da clic en **Patrocinar**. ![Botón de Patrocinador](/assets/images/help/sponsors/sponsor-org-button.png) -{% data reusables.sponsors.select-a-tier %} -{% data reusables.sponsors.select-sponsorship-billing %} - ![Botón de Editar pago](/assets/images/help/sponsors/edit-org-sponsorship-payment-button.png) -{% data reusables.sponsors.who-can-see-your-sponsorship %} - ![Botones radiales para elegir quién puede ver tu patrocinio](/assets/images/help/sponsors/who-can-see-org-sponsorship.png) -{% data reusables.sponsors.org-sponsored-choose-updates %} -7. Da clic en **Patrocinar _ORGANIZACIÓN_**. ![Botón de patrocinar organización](/assets/images/help/sponsors/sponsor-org-confirm-button.png) diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/index.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/index.md deleted file mode 100644 index 367b3f0362..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Enseñar y aprender con Educación GitHub -redirect_from: - - /categories/teaching-and-learning-with-github-education -versions: - free-pro-team: '*' -children: - - /using-github-at-your-educational-institution - - /using-github-for-your-schoolwork - - /using-github-in-your-classroom-and-research ---- -### Índice diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-campus-advisors.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-campus-advisors.md deleted file mode 100644 index 222f0d1f02..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-campus-advisors.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Acerca de Asesores de campus -intro: 'Como instructor o mentor, aprende a usar {% data variables.product.prodname_dotcom %} en tu escuela con el soporte técnico y la capacitación de Asesores de campus.' -redirect_from: - - /articles/about-campus-advisors - - /github/teaching-and-learning-with-github-education/about-campus-advisors -versions: - free-pro-team: '*' ---- -Profesores, maestros y mentores pueden usar la capacitación en línea de Asesores de campus para ser expertos en Git y {% data variables.product.prodname_dotcom %} y aprender las mejores prácticas para enseñarles a los alumnos con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Asesores de campus](https://education.github.com/teachers/advisors)". - -{% note %} - -**Nota:** Como instructor, no puedes crear cuentas de {% data variables.product.prodname_dotcom %} para tus alumnos. Los alumnos deben crear sus propias cuentas de {% data variables.product.prodname_dotcom %}. - -{% endnote %} diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-campus-experts.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-campus-experts.md deleted file mode 100644 index 0998e5abed..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-campus-experts.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Acerca de Expertos en campus -intro: 'Como estudiante, aprende las habilidades que necesitas para crear un portfolio real y una comunidad tecnológica de tu escuela, con la capacitación de Expertos en campus de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /articles/about-campus-experts - - /github/teaching-and-learning-with-github-education/about-campus-experts -versions: - free-pro-team: '*' ---- -Aprende habilidades comunicativas en público, escritura técnica, liderazgo comunitario y habilidades de desarrollo de software como un Experto en campus de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Expertos en campus](https://education.github.com/students/experts)". diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-github-education.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-github-education.md deleted file mode 100644 index a58fa6ed83..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/about-github-education.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Acerca de Educación GitHub -intro: '{% data variables.product.prodname_education %} ofrece un producto gratuito especial para las escuelas que quieren aprovechar al máximo {% data variables.product.prodname_dotcom %} para su comunidad y que aceptan los requisitos específicos del programa.' -redirect_from: - - /articles/about-github-education - - /github/teaching-and-learning-with-github-education/about-github-education -versions: - free-pro-team: '*' ---- -Si tu escuela acepta cumplir con ciertos requisitos, tu escuela secundaria, universidad o seminario intensivo profesional puede obtener {% data variables.product.prodname_education %}, que ofrece lo mejor de {% data variables.product.prodname_dotcom %} gratis, e incluye: -- {% data variables.product.prodname_ghe_cloud %} y/o {% data variables.product.prodname_ghe_server %} -- Capacitación para docentes para el Git principal y {% data variables.product.prodname_dotcom %} con nuestro programa Asesores de campus -- Acceso automatizado a las funciones premium de {% data variables.product.prodname_education %}, como {% data variables.product.prodname_student_pack %} -- Desarrollo de liderazgo y capacitación técnica para estudiantes con el programa Expertos en campus - -Para obtener más información, consulta la página [oficial {% data variables.product.prodname_education %}](https://education.github.com/partners/schools). Para conocer más acerca de los programas de capacitación para líderes estudiantiles y docentes, consulta "[{% data variables.product.prodname_dotcom %} Expertos en campus](https://education.github.com/students/experts)" y "[Asesores de campus](https://education.github.com/teachers/advisors)". - -Si eres un estudiante validado o académico y tu escuela no está asociada con {% data variables.product.prodname_dotcom %} como una escuela {% data variables.product.prodname_education %}, aún puedes solicitar descuentos de forma individual para usar {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Usar {% data variables.product.prodname_dotcom %} para tu trabajo escolar](/articles/using-github-for-your-schoolwork/)" o "[Usar {% data variables.product.prodname_dotcom %} en tu aula y en tu investigación](/articles/using-github-in-your-classroom-and-research/)". diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/index.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/index.md deleted file mode 100644 index 052fe0faf1..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Utilizar GitHub en tu institución educativa -intro: 'Aumenta los beneficios de utilizar {% data variables.product.prodname_dotcom %} en tu institución para los estudiantes, instructores y el personal de TI con {% data variables.product.prodname_education %} y nuestros múltiples programas de capacitación para estudiantes e instructores.' -redirect_from: - - /articles/using-github-at-your-educational-institution -versions: - free-pro-team: '*' -children: - - /about-github-education - - /about-campus-experts - - /about-campus-advisors ---- - diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/about-github-education-for-students.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/about-github-education-for-students.md deleted file mode 100644 index 9b14f31836..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/about-github-education-for-students.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Acerca de Educación GitHub para estudiantes -intro: '{% data variables.product.prodname_education %} le ofrece a los estudiantes experiencia práctica con acceso gratuito a diversas herramientas de programadores de los socios de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /articles/about-github-education-for-students - - /github/teaching-and-learning-with-github-education/about-github-education-for-students -versions: - free-pro-team: '*' ---- -Usar {% data variables.product.prodname_dotcom %} para tus proyectos escolares es un modo práctico de colaborar con otros y crear un portfolio que exhiba experiencia práctica. - -{% 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 %}. Como estudiante, también puedes solicitar el {% data variables.product.prodname_student_pack %}, que ofrece acceso gratuito a herramientas y servicios usados por programadores profesionales. Para obtener más información, consulta "[Postularse para un paquete de desarrollo para estudiantes](/articles/applying-for-a-student-developer-pack)" y [{% data variables.product.prodname_education %}](https://education.github.com/pack). - -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 "[Postularse para un descuento para educador o investigador](/articles/applying-for-an-educator-or-researcher-discount)". - -### Leer más - -- "[Acerca de {% data variables.product.prodname_education %} para educadores e investigadores](/articles/about-github-education-for-educators-and-researchers)" diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/applying-for-a-student-developer-pack.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/applying-for-a-student-developer-pack.md deleted file mode 100644 index cd2538275b..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/applying-for-a-student-developer-pack.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Aplicar un paquete de desarrollo para estudiantes -intro: 'Como estudiante, puedes aplicar para el {% data variables.product.prodname_student_pack %}, que incluye ofertas y beneficios de los socios de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /articles/applying-for-a-student-developer-pack - - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack -versions: - free-pro-team: '*' ---- -{% data reusables.education.about-github-education-link %} - -### Requisitos - -Para ser elegible para el {% data variables.product.prodname_student_pack %}, debes: -- Estar inscrito actualmente en un curso que otorgue un título o diploma que garantice un curso de estudio como colegio, escuela secundaria, facultad, universidad, escolarización en casa o institución educativa similar -- Tener una dirección de correo electrónico verificable suministrada por la escuela o cargar documentos que demuestren tu situación de estudiante actual -- Tener una cuenta de usuario de [{% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account) -- Tener al menos 13 años - -Entre los documentos que prueban tu situación de estudiante actual se incluye una foto de tu Id escolar, programa de clases, transcripciones y carta de verificación de afiliación o inscripción. - -Es posible que se te pida periódicamente que vuelvas a verificar tu estado académico actual para confirmar que eres estudiante. - -{% note %} - -**Nota:** No puedes transferir tus descuentos académicos de una cuenta a otra. Si tienes más de una cuenta a la que deseas aplicarle el descuenta, considera [fusionar](/articles/merging-multiple-user-accounts) tus cuentas de usuario y [cambiar el nombre](/articles/changing-your-github-username) a la cuenta retenida si así lo deseas. - -{% endnote %} - -Para obtener información sobre cómo renovar tu {% data variables.product.prodname_student_pack %}, consulta "[Caducidad y renovaciones](/articles/applying-for-a-student-developer-pack/#expiration-and-renewals)". - -### Aplicar para un {% data variables.product.prodname_student_pack %} - -{% data reusables.education.benefits-page %} -3. En "¿Qué es lo que mejor describe tu estado académico?", selecciona **Student** (Estudiante). ![Selecciona el estado académico](/assets/images/help/education/academic-status-student.png) -{% data reusables.education.select-email-address %} -{% data reusables.education.upload-proof-status %} -{% data reusables.education.school-name %} -{% data reusables.education.plan-to-use-github %} -{% data reusables.education.submit-application %} - -### Caducidad y renovaciones - -Una vez que caduca tu acceso a {% data variables.product.prodname_student_pack %}, puedes volver a aplicar si sigues siendo elegible, aunque es posible que las ofertas de algunos socios no puedan renovarse. La mayoría de las ofertas regulares de nuestros socios comiencen una vez que las configuraste. Para obtener más información, consulta la página [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). - -Para ver cuándo caduca tu acceso gratis al {% data variables.product.prodname_student_pack %}, visita los [ajustes de facturación](https://github.com/settings/billing). - -### Leer más - -- "[¿Por qué no aprobaron mi aplicación para un {% data variables.product.prodname_student_pack %}?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)" -- "[Registrarse para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)" -- [{% data variables.product.prodname_education %}](https://education.github.com) diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/index.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/index.md deleted file mode 100644 index 06cee5e15e..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Utilizar GitHub para tu trabajo escolar -intro: 'Como estudiante, utiliza {% data variables.product.prodname_dotcom %} para colaborar en tus proyectos escolares y crear experiencias de la vida real.' -redirect_from: - - /articles/using-github-for-your-schoolwork -versions: - free-pro-team: '*' -children: - - /about-github-education-for-students - - /applying-for-a-student-developer-pack - - /why-wasnt-my-application-for-a-student-developer-pack-approved ---- - diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md deleted file mode 100644 index 64b7f4b1d1..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: ¿Por qué no se aprobó mi solicitud para un paquete de desarrollo para estudiantes? -intro: 'Revisa las razones comunes por las que las solicitudes para el {% data variables.product.prodname_student_pack %} no se aprueban y lee las sugerencias para volver a solicitarlo con éxito.' -redirect_from: - - /articles/why-was-my-application-for-a-student-developer-pack-denied/ - - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved - - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved - - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved -versions: - free-pro-team: '*' ---- -{% tip %} - -**Sugerencia:** {% data reusables.education.about-github-education-link %} - -{% endtip %} - -### Documentos de afiliación académica poco claros - -Si la imagen que cargaste no identifica claramente tu situación académica actual, solicitamos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} - -{% data reusables.education.pdf-support %} - -### Usar un correo electrónico académico con un dominio no verificado - -Si tu dirección de correo electrónico académica tiene un dominio no verificado, requerimos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} - -{% data reusables.education.pdf-support %} - -### Usar un correo electrónico académico de una escuela con políticas de correo electrónico poco estrictas - -Si tu escuela expide direcciones de correo electrónico antes del pago de la inscripción, requerimos más pruebas de tu situación académica. {% data reusables.education.upload-proof-reapply %} - -{% data reusables.education.pdf-support %} - -Si tienes otras preguntas o inquietudes acerca del dominio de la escuela solicita al personal de informática de tu escuela que nos contacte. - -### Dirección de correo electrónico académica que ya se usó - -Si tu dirección de correo electrónico académica ya se usó para solicitar un {% data variables.product.prodname_student_pack %} para una cuenta {% data variables.product.prodname_dotcom %} diferente, no puedes volver a usar la dirección de correo electrónico académica para solicitar con éxito otro {% data variables.product.prodname_student_pack %} hasta que ese descuento haya vencido. - -{% note %} - -**Nota:** mantener más de una cuenta individual no respeta los {% data variables.product.prodname_dotcom %} [Términos del servicio](/articles/github-terms-of-service/#3-account-requirements). - -{% endnote %} - -Si tienes más de una cuenta de usuario, debes fusionar tus cuentas. Para conservar el descuento, debes mantener la cuenta a la que se le otorgó el descuento. Puedes renombrar la cuenta retenida y conservar tu historial de contribuciones agregando todas las direcciones de correo electrónico a la cuenta retenida. - -Para obtener más información, consulta: -- "[Fusionar cuentas de usuario múltiples](/articles/merging-multiple-user-accounts)" -- "[Cambiar tu nombre de usuario {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username)" -- "[Agregar una dirección de correo electrónico a tu cuenta {% data variables.product.prodname_dotcom %}](/articles/adding-an-email-address-to-your-github-account)" - -### Situación de estudiante inadmisible - -No eres apto para un {% data variables.product.prodname_student_pack %} si: -- Estás inscrito en un programa de aprendizaje informal que no forma parte del [Programa del campus de {% data variables.product.prodname_dotcom %}](https://education.github.com/schools) y no estás inscrito en un curso de estudio que te otorgue un diploma o un título. -- Tienes menos de 13 años. - -Tu instructor todavía puede solicitar un descuento para uso escolar {% data variables.product.prodname_education %}. Si estás estudiando en una escuela o programa intensivo de codificación, podrás inscribirte en {% data variables.product.prodname_student_pack %} si tu escuela se une al [Programa del campus de {% data variables.product.prodname_dotcom %}](https://education.github.com/schools). - -### Leer más - -- "[Solicitar un paquete de desarrollo para estudiantes](/articles/applying-for-a-student-developer-pack)" -- "[Solicitar un paquete de desarrollo para estudiantes](/articles/applying-for-a-student-developer-pack)" diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers.md deleted file mode 100644 index b936619c9c..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Acerca de Educación GitHub para educadores e investigadores -intro: '{% data variables.product.prodname_education %} ofrece una variedad de herramientas para ayudar a los educadores y los investigadores a trabajar de manera más eficaz dentro y fuera del aula.' -redirect_from: - - /articles/about-github-education-for-educators-and-researchers - - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers -versions: - free-pro-team: '*' ---- -{% data reusables.education.about-github-education-link %} - -### {% data variables.product.prodname_education %} para educadores - -Con los servicios y las herramientas de {% data variables.product.prodname_education %} para educadores de todos los niveles, puedes: - - Usar [{% data variables.product.prodname_classroom %}](https://classroom.github.com) para distribuir el código, hacerles comentarios a los estudiantes y recolectar las tareas en {% data variables.product.prodname_dotcom %}. - - Unirte a nuestra [{% data variables.product.prodname_education_community %}](https://education.github.com/forum) para debatir tendencias actuales sobre educación tecnológica con tus pares de todo el mundo. - - Acceder y adaptar nuestros [planes de lecciones de código abierto](https://education.github.community/t/open-source-lesson-plans/1591) para enseñar Git y {% data variables.product.prodname_dotcom %}. - - [Solicitar un botín {% data variables.product.prodname_dotcom %}](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33) con beneficios y materiales educativos para tus estudiantes. - {% data reusables.education.apply-for-team %} - -### {% data variables.product.prodname_education %} para investigadores - -Con los servicios y las herramientas de {% data variables.product.prodname_education %} para investigadores, puedes: - - Colaborar con otros en tu trabajo de investigación en todo el mundo en {% data variables.product.prodname_dotcom %}. - - [Aprender](https://education.github.com/stories) cómo usan {% data variables.product.prodname_dotcom %} las instituciones académicas en todo el mundo para su investigación. - {% data reusables.education.apply-for-team %} - -### Leer más - -- "[Acerca de {% data variables.product.prodname_education %} para estudiantes](/articles/about-github-education-for-students)" diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/applying-for-an-educator-or-researcher-discount.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/applying-for-an-educator-or-researcher-discount.md deleted file mode 100644 index 00bc53150a..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/applying-for-an-educator-or-researcher-discount.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Aplicar para un descuento de educador o investigador -intro: 'Si eres educador o investigador, puedes aplicar para recibir {% data variables.product.prodname_team %} para la cuenta de tu organización de manera gratuita.' -redirect_from: - - /articles/applying-for-a-classroom-discount/ - - /articles/applying-for-a-discount-for-your-school-club/ - - /articles/applying-for-an-academic-research-discount/ - - /articles/applying-for-a-discount-for-your-first-robotics-team/ - - /articles/applying-for-an-educator-or-researcher-discount - - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount -versions: - free-pro-team: '*' ---- -### Acerca de descuentos para educadores e investigadores - -{% data reusables.education.about-github-education-link %} - -Para aplicar para un descuento como educador o investigador, debes: -- Ser educador, miembro de una factultad, o investigador -- Have a verifiable school-issued email address -- Upload documents that prove your school affiliation -- Tener una cuenta de usuario de [{% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account) - -### Aplicar para un descuento de educador o investigador - -{% data reusables.education.benefits-page %} -3. En "¿Qué es lo que mejor describe tu estado académico?", selecciona **Faculty** (Facultad). ![Selecciona el estado académico](/assets/images/help/education/academic-status-faculty.png) -{% data reusables.education.select-email-address %} -{% data reusables.education.upload-proof-status %} -{% data reusables.education.school-name %} -{% data reusables.education.plan-to-use-github %} -{% data reusables.education.submit-application %} - -### Actualizar tu organización - -Después de que se apruebe tu solicitud para un descuento de investigador o de maestro, puedes mejorar las organizaciones que utilizas con tu comunidad educativa a {% data variables.product.prodname_team %}, lo cual permitirá que tengas usuarios y repositorios privados ilimitados con todas las características gratuitamente. Puedes actualizar una organización existente o crear una organización nueva para actualizarla. - -#### Actualizar una organización existente - -{% data reusables.education.upgrade-page %} -{% data reusables.education.upgrade-organization %} - -#### Actualizar una organización nueva - -{% data reusables.education.upgrade-page %} -1. Da clic en {% octicon "plus" aria-label="The plus symbol" %}**Crear una organización**. ![Botón para crear una organizacion](/assets/images/help/education/create-org-button.png) -3. Lee la información, posteriormente da clic en **Crear organización**. ![Botón Create organization (Crear organización)](/assets/images/help/education/create-organization-button.png) -4. Debajo de "Elige tu plan", da clic en **Elegir {% data variables.product.prodname_free_team %}**. -5. Sigue las propuestas para crear tu organización. -{% data reusables.education.upgrade-page %} -{% data reusables.education.upgrade-organization %} - -### Leer más - -- "[¿Por que no ha sido aprobada mi aplicación para recibir un descuento como educador o investigador?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)" -- [{% data variables.product.prodname_education %}](https://education.github.com) -- [Videos de {% data variables.product.prodname_classroom %}](https://classroom.github.com/videos) -- [{% data variables.product.prodname_education_community %}](https://education.github.community/) diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/index.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/index.md deleted file mode 100644 index 98a446a0c1..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Utilizar GitHub en tu clase e investigación -intro: 'Como educador o investigador, utiliza {% data variables.product.prodname_dotcom %} para colaborar con el trabajo en clase, con el grupo de estudiantes o de investigación, y mucho más.' -redirect_from: - - /articles/using-github-in-your-classroom-and-research -versions: - free-pro-team: '*' -children: - - /about-github-education-for-educators-and-researchers - - /applying-for-an-educator-or-researcher-discount - - /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved ---- - diff --git a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md b/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md deleted file mode 100644 index 16f94b6653..0000000000 --- a/translations/es-XL/content/github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: ¿Por qué mi solicitud para un descuento de educador o de investigador no se aprobó? -intro: Revisa las razones comunes por las que las solicitudes para un descuento de educador o de investigador no se aprueban y lee las sugerencias para volver a solicitarlo con éxito. -redirect_from: - - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied/ - - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved - - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved - - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved -versions: - free-pro-team: '*' ---- -{% tip %} - -**Sugerencia:** {% data reusables.education.about-github-education-link %} - -{% endtip %} - -### Documentos poco claros de la prueba de afiliación - -Si la imagen que cargaste no identifica claramente tu empleo actual con una escuela o una universidad, debes volver a presentar la solicitud y cargar otra imagen de la identificación de tu facultad o carta de verificación de empleo con información clara. - -{% data reusables.education.pdf-support %} - -### Usar un correo electrónico académico con un dominio no verificado - -Si tu dirección de correo electrónico académica tiene un dominio no verificado, podemos solicitar más pruebas de tu situación académica. {% data reusables.education.upload-different-image %} - -{% data reusables.education.pdf-support %} - -### Usar un correo electrónico académico de una escuela con políticas de correo electrónico poco estrictas - -Si los ex alumnos y los profesores retirados de tu escuela tienen acceso vitalicio a las direcciones de correo electrónico suministradas por la escuela, podemos requerir más pruebas de tu situación académica. {% data reusables.education.upload-different-image %} - -{% data reusables.education.pdf-support %} - -Si tienes otras preguntas o inquietudes acerca del dominio de la escuela, solicita al personal de informática de tu escuela que nos contacte. - -### Personas que no son estudiantes solicitan un paquete de desarrollo para estudiantes - -Los educadores y los investigadores no son elegibles para las ofertas de los socios que vienen con el [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). Cuando vuelves a presentar una solicitud, asegúrate de elegir **Profesor** para describir tu situación académica. - -### Leer más - -- "[Solicitar un descuento de educador o de investigador](/articles/applying-for-an-educator-or-researcher-discount)" diff --git a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md b/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md deleted file mode 100644 index 805297f054..0000000000 --- a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Acerca del uso de tus datos de GitHub -redirect_from: - - /articles/about-github-s-use-of-your-data - - /articles/about-githubs-use-of-your-data -intro: '{% data variables.product.product_name %} usa los datos de tu repositorio para conectarte con información, proyectos, personas y herramientas relevantes.' -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -### Acerca del uso de tus datos de {% data variables.product.product_name %} - -{% data variables.product.product_name %} agrega metadatos y analiza patrones de contenidos con el fin de suministrar información generalizada dentro del producto. Usa datos de los repositorios públicos y también usa metadatos y agrega datos de repositorios privados cuando el propietario de un repositorio ha elegido compartir los datos con {% data variables.product.product_name %} mediante una opción. Si aceptas el uso de datos de un repositorio privado, entonces se realizará un análisis de solo lectura de ese repositorio privado específico. - -{% data reusables.repositories.about-github-archive-program %} Para obtener más información, consulta la sección "[Acerca de archivar contenido y datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". - -{% data reusables.user_settings.export-data %} Para obtener más información, consulta "[Solicitar un archivo de los datos de tu cuenta personal](/articles/requesting-an-archive-of-your-personal-account-s-data)". - -Si decides utilizar datos para un repositorio privado, seguiremos tratando tus datos privados, código abierto, o secretos comerciales como confidenciales y privados de acuerdo con nuestras [Condiciones de Servicio](/articles/github-terms-of-service/). La información que obtenemos viene solo de los datos agregados. Para obtener más información, consulta la sección "[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)". - -Anunciaremos nuevas funciones sustanciales que usen metadatos o datos agregados en el [{% data variables.product.prodname_dotcom %}blog](https://github.com/blog). - -### Cómo mejoran los datos las recomendaciones de seguridad - -Como ejemplo de cómo deberían usarse tus datos, podemos detectar y alertarte sobre una vulnerabilidad de seguridad en las dependencias de tu repositorio público. 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)". - -Para detectar posibles vulnerabilidades de seguridad {% data variables.product.product_name %} escanea los contenidos del archivo de manifiesto de dependencias para hacer una lista de las dependencias de tu proyecto. - -{% data variables.product.product_name %} también aprende de los cambios que realizas en tu manifiesto de dependencias. Por ejemplo, si actualizas una dependencia vulnerable a una versión segura después de recibir una alerta de seguridad y otros hacen lo mismo, {% data variables.product.product_name %} aprende cómo hacer un parche en la vulnerabiidad y puede recomendar un parche similar para el repositorio afectado. - -### Privacidad y uso compartido de datos - -Los datos del repositorio privado se escanean mediante una máquina y nunca es leído por el personal de {% data variables.product.product_name %}. El ojo humano nunca verá los contenidos de tus repositorios privados, a excepción de lo que se describe en nuestros [Términos de servicio](/articles/github-terms-of-service/#3-access). - -Tus datos personales individuales o del repositorio no se compartirán con terceros. Podemos compartir datos agregados obtenidos de nuestro análisis con nuestros socios. diff --git a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/index.md b/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/index.md deleted file mode 100644 index 973dd586bb..0000000000 --- a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Comprender cómo GitHub usa y protege tus datos -redirect_from: - - /categories/understanding-how-github-uses-and-protects-your-data -versions: - fpt: '*' -children: - - /about-githubs-use-of-your-data - - /requesting-an-archive-of-your-personal-accounts-data - - /managing-data-use-settings-for-your-private-repository - - /opting-into-or-out-of-the-github-archive-program-for-your-public-repository ---- -### Índice diff --git a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md deleted file mode 100644 index dcbabed015..0000000000 --- a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Administrar la configuración de uso de datos para tu repositorio privado -intro: 'Para ayudar a que {% data variables.product.product_name %} te conecte a las herramientas, proyectos, personas e información relevantes, puedes configurar el uso de datos para tu repositorio privado.' -redirect_from: - - /articles/opting-into-or-out-of-data-use-for-your-private-repository - - /github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -### Acerca del uso de datos para tu repositorio privado - -When you enable data use for your private repository, you'll be able to access the dependency graph, where you can track your repository's dependencies and receive {% data variables.product.prodname_dependabot_short %} alerts when {% data variables.product.product_name %} detects vulnerable dependencies. 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#github-dependabot-alerts-for-vulnerable-dependencies)". - -### Habilitar o inhabilitar las características para el uso de datos - -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} - -{% data reusables.security.security-and-analysis-features-enable-read-only %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-security-and-analysis %} -4. Debajo de "Configurar la seguridad y las características de análisis", a la derecha de la característica, da clic en **Inhabilitar** o **Habilitar**. ![Botón de "Habilitar" o "Inhabilitar" para las características de "Configurar la seguridad y el análisis"](/assets/images/help/repository/security-and-analysis-disable-or-enable.png) - -### Leer más - -- "[Acerca del uso de tus datos de {% data variables.product.prodname_dotcom %}](/articles/about-github-s-use-of-your-data)" -- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" diff --git a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md b/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md deleted file mode 100644 index 7098c4e1f5..0000000000 --- a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Aceptar o rechazar el ingreso al Prgrama de GitHub Archive para tu repositorio público -intro: 'Puedes gestionar si {% data variables.product.prodname_dotcom %} incluye tu repositorio público en el {% data variables.product.prodname_archive %} para ayudarte a garantizar la preservación a largo plazo del código abierto global.' -permissions: 'People with admin permissions to a public repository can opt into or out of the {% data variables.product.prodname_archive %}.' -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -{% data reusables.repositories.about-github-archive-program %} Para obtener más información, consulta la sección "[Acerca de archivar contenido y datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". - -Si rechazas el ingreso de un repositorio al {% data variables.product.prodname_archive %}, éste se excluirá de cualquier archivo a largo plazo que {% data variables.product.prodname_dotcom %} pudiera crear posteriormente. También enviaremos una solicitud a cada una de nuestras organizaciones socias para eliminar el repositorio de sus datos. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Debajo de "Características", selecciona o deselecciona **Preservar este repositorio**. ![Casilla para permitir a {% data variables.product.prodname_dotcom %} incluir tu código en el {% data variables.product.prodname_archive %}](/assets/images/help/repository/github-archive-program-checkbox.png) - -### Leer más -- [{% data variables.product.prodname_archive %} Preguntas Frecuentes](https://archiveprogram.github.com/faq/) diff --git a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md b/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md deleted file mode 100644 index 6ac1d64bd9..0000000000 --- a/translations/es-XL/content/github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Solicitar un archivo de tus datos de cuenta personal -redirect_from: - - /articles/requesting-an-archive-of-your-personal-account-s-data - - /articles/requesting-an-archive-of-your-personal-accounts-data -intro: '{% data reusables.user_settings.export-data %}' -versions: - fpt: '*' -topics: - - Policy - - Legal ---- - -{% data variables.product.product_name %} almacena metadatos del repositorio y del perfil desde tu actividad de cuenta personal. Puedes exportar tus datos de cuenta personal a través de los parámetros {% data variables.product.prodname_dotcom_the_website %} o con la API de migración de usuarios. - -Para obtener más información, acerca de los datos que almacena {% data variables.product.product_name %} y que está disponible para exportarse, consulta las secciones "[Descargar el archivo de migración de un usuario](/v3/migrations/users/#download-a-user-migration-archive)" y "[Acerca del uso de {% data variables.product.product_name %} para tus datos](/articles/about-github-s-use-of-your-data). - -Cuando solicites una exportación de tus datos personales a través de los parámetros de {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.product_name %} comprime tus datos personales en un archivo `tar.gz` y te envía un correo electrónico a tu dirección principal de correo electrónico con un enlace de descarga. - -Por defecto, el enlace de descarga vence después de siete días. En cualquier momento previo a que venza el enlace de descarga, puedes habilitar el enlace desde los parámetros del usuario. Para obtener más información, consulta "[Eliminar el acceso a un archivo de datos de tu cuenta personal](/articles/requesting-an-archive-of-your-personal-account-s-data/#deleting-access-to-an-archive-of-your-personal-accounts-data)". - -Si tu sistema operativo no puede descomprimir el archivo `tar.gz` de forma nativa, puedes utilizar una herramienta de terceros para extraer los archivos archivados. Para obtener más información, consulta "[Cómo descomprimir un tar.gz file](https://opensource.com/article/17/7/how-unzip-targz-file)" en Opensource.com. - -El archivo `tar.gz` generado refleja los datos almacenados en el momento que comenzaste la exportación de datos. - -### Descargar un archivo de datos de tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.account_settings %} -3. En "Export account data" (Exportar datos de cuenta), haz clic en **Start export** (Comenzar exportación) o **New export** (Nueva exportación). ![Botón Start personal data export (Comenzar exportación de datos personales) resaltado](/assets/images/help/repository/export-personal-data.png) ![Botón New personal data export (Nueva exportación de datos personales) resaltado](/assets/images/help/repository/new-export.png) -4. Una vez que la exportación esté lista para descargar, {% data variables.product.product_name %} te enviará un enlace de descarga a tu dirección principal de correo electrónico. -5. Haz clic en el enlace de descarga de tu correo electrónico y vuelve a ingresar tu contraseña, si se te solicita. -6. Serás redirigido a un archivo `tar.gz` que podrás descargar. - -### Eliminar acceso a un archivo de datos de tu cuenta personal - -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.account_settings %} -3. Para inhabilitar el enlace de descarga que se te envió al correo electrónico antes de que venza, en "Export account data" (Exportar datos de cuenta), encuentra la descarga de exportación de datos que quieres inhabilitar y haz clic en **Delete** (Eliminar). ![Botón Delete personal data export package (Eliminar paquete de exportación de datos personales) resaltado](/assets/images/help/repository/delete-export-personal-account-data.png) diff --git a/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/caching-your-github-credentials-in-git.md b/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/caching-your-github-credentials-in-git.md deleted file mode 100644 index 28cfab7f02..0000000000 --- a/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/caching-your-github-credentials-in-git.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: Almacenar tus credenciales de GitHub en el caché dentro de Git -redirect_from: - - /firewalls-and-proxies/ - - /articles/caching-your-github-password-in-git - - /github/using-git/caching-your-github-password-in-git - - /github/using-git/caching-your-github-credentials-in-git -intro: 'Si estás [clonando los repositorios de {% data variables.product.product_name %} mediante HTTPS](/github/using-git/which-remote-url-should-i-use), puedes utilizar un asistente de credenciales para decirle a Git que recuerde tus credenciales.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Si clonas repositorios de {% data variables.product.product_name %} mediante SSH, entonces te autenticas 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)". - -{% mac %} - -{% tip %} - -**Sugerencias:** - -- Debes tener Git **1.7.10** o una versión más nueva para usar el ayudante de credenciales osxkeychain. -- Si has instalado Git mediante [Homebrew](http://brew.sh/), el `osxkeychain helper` debe estar instalado anteriormente. -- Si estás utilizando Mac OS X10.7 o superior y tienes instalado Git a través de las herramientas de la línea de comando Xcode de Apple, luego `osxkeychain helper` se incluirá automáticamente en tu instalación Git. - -{% endtip %} - -Instala Git y `osxkeychain helper` e informa a Git que lo use. - -1. Descubre si Git y `osxkeychain helper` ya están instalados: - ```shell - $ git credential-osxkeychain - # Test for the cred helper - > Usage: git credential-osxkeychain <get|store|erase> - ``` -2. Si el asistente `osxkeychain helper` no está instalado, y estás utilizando OS X versión 10.9 o superior, tu computadora te pedirá que lo descargues como parte de las Herramientas de la línea de comandos de Xcode: - ```shell - $ git credential-osxkeychain - > xcode-select: note: no developer tools were found at '/Applications/Xcode.app', - > requesting install. Escoge una opción en el diálogo para descargar las herramientas del programador de la línea de comando. - ``` - - Como opción, puedes instalar Git y el asistente `osxkeychain helper` usando [Homebrew](http://brew.sh/): - ```shell - $ brew install git - ``` - -4. Pídele a Git que use el asistente `osxkeychain helper` con la configuración global `credential.helper`: - ```shell - $ git config --global credential.helper osxkeychain - # Set git to use the osxkeychain credential helper - ``` - -La próxima vez que clones una URL de HTTPS que requiera autenticación, Git te pedirá tu nombre de usuario y contraseña. {% data reusables.user_settings.password-authentication-deprecation %} - -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. No se te solicitará teclear tus credenciales en Git nuevamente a menos de que éstas cambien. - -{% endmac %} - -{% windows %} - -{% tip %} - -**Sugerencia:** Necesitarás Git **1.7.10** o una versión más nueva para usar el ayudante de credenciales. - -{% endtip %} - -También puedes instalar un shell Git nativo, como [Git para Windows](https://git-for-windows.github.io/). Con Git para Windows, al ejecutar lo siguiente en la línea de comandos, se almacenarán tus credenciales: - -```shell -$ git config --global credential.helper wincred -``` - -{% endwindows %} - -{% linux %} - -{% tip %} - -**Sugerencia:** Necesitarás Git **1.7.10** o una versión más nueva para usar el ayudante de credenciales. - -{% endtip %} - -Activa tu ayudante de credenciales de manera que Git guarde tu contraseña en la memoria para otra oportunidad. Por defecto, Git guardará en la memoria caché tu contraseña durante 15 minutos. - -1. En Terminal, escribe lo siguiente: - ```shell - $ git config --global credential.helper cache - # Set git to use the credential memory cache - ``` -2. Para cambiar el intervalo por defecto de la memoria caché de la contraseña, escribe lo siguiente: - ```shell - $ git config --global credential.helper 'cache --timeout=3600' - # Set the cache to timeout after 1 hour (setting is in seconds) - ``` - -{% endlinux %} - -### Leer más - -- "[Actualizar credenciales desde la Keychain OSX](/articles/updating-credentials-from-the-osx-keychain/)" -- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" diff --git a/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/index.md b/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/index.md deleted file mode 100644 index 89666da693..0000000000 --- a/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Comenzar con Git y GitHub -intro: '' -redirect_from: - - /articles/getting-started-with-git-and-github -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /setting-your-username-in-git - - /caching-your-github-credentials-in-git - - /why-is-git-always-asking-for-my-password - - /updating-credentials-from-the-osx-keychain ---- - diff --git a/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/setting-your-username-in-git.md b/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/setting-your-username-in-git.md deleted file mode 100644 index cf34182307..0000000000 --- a/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/setting-your-username-in-git.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Configurar tu nombre de usuario en Git -intro: 'Git utiliza un nombre de usuario para asociar las confirmaciones con una identidad. El nombre de usuario de Git no es tu mismo nombre de usuario de {% data variables.product.product_name %}.' -redirect_from: - - /articles/setting-your-username-in-git - - /github/using-git/setting-your-username-in-git -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -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. - -### Configurar tu nombre de usuario de Git para *cada* repositorio en tu computadora - -{% data reusables.command_line.open_the_multi_os_terminal %} - -2. {% data reusables.user_settings.set_your_git_username %} - ```shell - $ git config --global user.name "Mona Lisa" - ``` - -3. {% data reusables.user_settings.confirm_git_username_correct %} - ```shell - $ git config --global user.name - > Mona Lisa - ``` - -### Configurar tu nombre de usuario de Git para un repositorio único - -{% data reusables.command_line.open_the_multi_os_terminal %} - -2. Cambia el directorio de trabajo actual al repositorio local donde deseas configurar el nombre que está asociado con tus confirmaciones de Git. - -3. {% data reusables.user_settings.set_your_git_username %} - ```shell - $ git config user.name "Mona Lisa" - ``` - -3. {% data reusables.user_settings.confirm_git_username_correct %} - ```shell - $ git config user.name - > Mona Lisa - ``` - -### Leer más - -- "[Establecer tu dirección de correo electrónico de confirmaciones](/articles/setting-your-commit-email-address)" -- ["Configuración de Git" del libro _Pro Git_](https://git-scm.com/book/en/Customizing-Git-Git-Configuration) diff --git a/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/why-is-git-always-asking-for-my-password.md b/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/why-is-git-always-asking-for-my-password.md deleted file mode 100644 index 363e49c1cd..0000000000 --- a/translations/es-XL/content/github/using-git/getting-started-with-git-and-github/why-is-git-always-asking-for-my-password.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: ¿Por qué Git me pregunta siempre mi contraseña? -intro: 'Si Git te solicita el nombre de usuario y la contraseña cada vez que tratas de interactuar con GitHub, probablemente estás usando la URL del clon HTTPS para tu repositorio.' -redirect_from: - - /articles/why-is-git-always-asking-for-my-password - - /github/using-git/why-is-git-always-asking-for-my-password -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Utilizar una URL remota de tipo HTTPS tiene algunas ventajas comparadas con el uso de SSH. Es más fácil de configurar que SSH, y habitualmente trabaja mediante cortafuectos y proxies estrictos. Sin embargo, también te solicita que ingreses tus credenciales de GitHub cada vez que extraes o subes un repositorio. - -Puedes evitar que se te solicite tu contraseña si configuras Git para que [almacene tus credenciales en el caché](/github/using-git/caching-your-github-credentials-in-git). {% data reusables.user_settings.password-authentication-deprecation %} - -Ya que hayas configurado el almacenamiento de credenciales en caché, Git utilizará to token de acceso personal almacenado en caché automáticamente en vez de utilizar una contraseña cada que extraigas o cargues información a un repositorio utilizando HTTPS. - - -### Leer más - -* "[¿Qué URL remota debería utilizar?](/articles/which-remote-url-should-i-use/#cloning-with-https-urls)" -* "[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" -* "[Agregar tu llave SSH al ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)" diff --git a/translations/es-XL/content/github/using-git/index.md b/translations/es-XL/content/github/using-git/index.md deleted file mode 100644 index b02632de85..0000000000 --- a/translations/es-XL/content/github/using-git/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Utilizar GitHub -intro: 'Conoce los flujos de trabajo comunes y avanzados de Git para mejorar tu experiencia con {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /categories/19/articles/ - - /categories/using-git -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /getting-started-with-git-and-github - - /learning-about-git - - /using-common-git-commands - - /managing-remote-repositories - - /using-advanced-git-commands ---- -### Índice diff --git a/translations/es-XL/content/github/using-git/learning-about-git/associating-text-editors-with-git.md b/translations/es-XL/content/github/using-git/learning-about-git/associating-text-editors-with-git.md deleted file mode 100644 index 4bd474c69d..0000000000 --- a/translations/es-XL/content/github/using-git/learning-about-git/associating-text-editors-with-git.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -title: Asociar editores de texto con Git -intro: Usar un editor de texto para abrir y editar tus archivos con Git. -redirect_from: - - /textmate/ - - /articles/using-textmate-as-your-default-editor/ - - /articles/using-sublime-text-2-as-your-default-editor/ - - /articles/associating-text-editors-with-git - - /github/using-git/associating-text-editors-with-git -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% mac %} - -### 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" - ``` - -### Utilizar Visual Studio Code como tu editor - -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: - ```shell - $ git config --global core.editor "code --wait" - ``` - -### Usar Sublime Text como tu editor - -1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: - ```shell - $ git config --global core.editor "subl -n -w" - ``` - -### Usar TextMate como editor - -1. Instala [TextMate](https://macromates.com/). -2. Instala la utilidad de shell `mate` de TextMate. Para obtener más información, consulta "[mate y rmate](https://macromates.com/blog/2011/mate-and-rmate/)" en la documentación de TextMate. -{% data reusables.command_line.open_the_multi_os_terminal %} -4. Escribe este comando: - ```shell - $ git config --global core.editor "mate -w" - ``` -{% endmac %} - -{% windows %} - -### 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. -3. Escribe este comando: - ```shell - $ git config --global core.editor "atom --wait" - ``` - -### Utilizar Visual Studio Code como tu editor - -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: - ```shell - $ git config --global core.editor "code --wait" - ``` - -### Usar Sublime Text como tu editor - -1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: - ```shell - $ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w" - ``` - -### Usar Notepad++ como editor - -1. Instala Notepad++ desde https://notepad-plus-plus.org/. Para obtener más información, consulta la sección "[Comenzar](https://npp-user-manual.org/docs/getting-started/)" en la documentación de Notepad++. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: - ```shell - $ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin" - ``` -{% endwindows %} - -{% linux %} - -### 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" - ``` - -### Utilizar Visual Studio Code como tu editor - -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: - ```shell - $ git config --global core.editor "code --wait" - ``` - -### Usar Sublime Text como tu editor - -1. Instala [Sublime Text](https://www.sublimetext.com/). Para obtener más información, consulta la sección "[Instalación](https://docs.sublimetext.io/guide/getting-started/installation.html)" en la documentación de Sublime Text. -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Escribe este comando: - ```shell - $ git config --global core.editor "subl -n -w" - ``` - -{% endlinux %} diff --git a/translations/es-XL/content/github/using-git/learning-about-git/configuring-git-to-handle-line-endings.md b/translations/es-XL/content/github/using-git/learning-about-git/configuring-git-to-handle-line-endings.md deleted file mode 100644 index 097e3fa126..0000000000 --- a/translations/es-XL/content/github/using-git/learning-about-git/configuring-git-to-handle-line-endings.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Configurar Git para manejar finales de línea -intro: 'Para evitar problemas en tus diferencias, puedes configurar Git para manejar correctamente los finales de línea.' -redirect_from: - - /dealing-with-lineendings/ - - /line-endings/ - - /articles/dealing-with-line-endings/ - - /articles/configuring-git-to-handle-line-endings - - /github/using-git/configuring-git-to-handle-line-endings -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -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 puede producir resultados inesperados si, por ejemplo, trabajas en una máquina Windows y tu colaborador hizo un cambio desde OS X. - -Puedes configurar Git para que maneje los fines de línea automáticamente y así puedas colaborar eficazmente con las personas que utilizan otros sistemas operativos. - -### Parámetros globales para finales de línea - -El comando `git config core.autocrlf` se usa para cambiar el modo en que Git maneja los finales de línea. Toma un solo argumento. - -{% mac %} - -En OS X, simplemente escribes `input` en la configuración. Por ejemplo: - -```shell -$ git config --global core.autocrlf input -# Configure Git to ensure line endings in files you checkout are correct for OS X -``` - -{% endmac %} - -{% windows %} - -En Windows, simplemente escribes `true` en la configuración. Por ejemplo: - -```shell -$ git config --global core.autocrlf true -# Configure Git to ensure line endings in files you checkout are correct for Windows. -# For compatibility, line endings are converted to Unix style when you commit files. -``` - -{% endwindows %} - -{% linux %} - -En Linux, simplemente escribes `input` en la configuración. Por ejemplo: - -```shell -$ git config --global core.autocrlf input -# Configure Git to ensure line endings in files you checkout are correct for Linux -``` - -{% endlinux %} - -### Parámetros por repositorio - -Como ocpión, puedes configurar un archivo de tipo *.gitattributes* para administrar cómo Git lee los fines de línea en un repositorio específico. Cuando confirmas este archivo en un repositorio, éste invalida la configuración de `core.autocrlf` para todos los colaboradores del mismo. Esto garantiza un comportamiento consistente para todos los usuarios, sin importar su configuración y ambiente de Git. - -El archivo *.gitattributes* debe crearse en la raíz del repositorio y confirmarse como cualquier otro archivo. - -Un archivo *.gitattributes* se asemeja a una tabla con dos columnas: - -* A la izquierda está el nombre del archivo que coincide con Git. -* A la derecha está la configuración de fin de línea que Git debería usar para esos archivos. - -#### Ejemplo - -Aquí hay un ejemplo de archivo *.gitattributes*. Puedes usarlo como plantilla para tus repositorios: - -``` -# Esteblece el comportamiento predeterminado, en caso de que las personas no tengan configurado core.autocrlf. -* text=auto - -# Declara explícitamente los archivos de texto que siempre quieres que estén normalizados y convertidos -# a finales de línea nativos en el control. -*.c text -*.h text - -# Declara los archivos que siempre tendrán los finales de línea CRLF en el control. -*.sln text eol=crlf - -# Denota todos los archivos que son absolutamente binarios y no deberían modificarse. -*.png binary -*.jpg binary -``` - -Notarás que los archivos coinciden—`*.c`, `*.sln`, `*.png`—, separados con un espacio, y luego se les dará una configuración —`text`, `text eol=crlf`, `binary`. Revisaremos algunas configuraciones posibles a continuación. - -- `text=auto` Git manejará los archivos en cualquier manera que crea sea mejor. Esta es una buena opción predeterminada. - -- `text eol=crlf` Git siempre convertirá los fines de línea en `CRLF` a la salida. Deberías usar esto para los archivos que deben conservar los finales `CRLF`, incluso en OSX o Linux. - -- `text eol=lf` Git siempre convertirá los finales de línea en `LF` a la salida. Deberías usar esto para los archivos que deben conservar los finales LF, incluso en Windows. - -- `binary` Git entenderá que los archivos especificados no son de texto, y no deberá intentar cambiarlos. El parámetro `binario` también es un alias para `text -diff`. - -### Actualizar un repositorio después de los finales de línea - -Cuando configuras la opción `core.autocrlf` o confirmas un archivo de tipo *.gitattributes* podrías encontrar que Git reporta cambios a archivos que no has modificado. Git ha cambiado los fines de línea para que concuerden con tu nueva configuración. - -Para garantizar que todos los fines de línea en tu repositorio concuerdan con tu nueva configuración, respalda tus archivos con Git, borra los archivos en tu repositorio (con excepción de el directorio `.git`), y luego restablece todos los archivos al mismo tiempo. - -1. Guarda los archivos actuales en Git, de manera que nada de tu trabajo se pierda. - ```shell - $ git add . -u - $ git commit -m "Saving files before refreshing line endings" - ``` -2. Agrega todos los archivos cambiados nuevamente y normaliza los finales de línea. - ```shell - $ git add --renormalize . - ``` -3. Muestra los archivos reescritos, normalizados. - ```shell - $ git status - ``` -4. Confirma los cambios en tu repositorio. - ```shell - $ git commit -m "Normalize all the line endings" - ``` - -### Leer más - -- [Personalizar Git - Atributos de Git](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) en el libro de Pro Git -- [git-config](https://git-scm.com/docs/git-config) en las páginas man para Git -- [Comenzar -Configuración Inicial](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) en el libro de Pro Git -- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) por [Tim Clem](https://github.com/tclem) diff --git a/translations/es-XL/content/github/using-git/learning-about-git/git-workflows.md b/translations/es-XL/content/github/using-git/learning-about-git/git-workflows.md deleted file mode 100644 index 31243ed980..0000000000 --- a/translations/es-XL/content/github/using-git/learning-about-git/git-workflows.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Flujos de trabajo de Git -intro: 'El flujo de {% data variables.product.prodname_dotcom %} es un flujo de trabajo ligero basado en ramas que soporta equipos y proyectos que despliegan frecuentemente.' -redirect_from: - - /articles/what-is-a-good-git-workflow/ - - /articles/git-workflows - - /github/using-git/git-workflows -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Puedes adoptar el método de flujo de {% data variables.product.prodname_dotcom %} para estandarizar como funciona tu equipo y como colabora con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Flujo de GitHub](/github/collaborating-with-issues-and-pull-requests/github-flow)" y " [Entender el flujo de GitHub](http://guides.github.com/overviews/flow/)" en las Guías de {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-XL/content/github/using-git/learning-about-git/ignoring-files.md b/translations/es-XL/content/github/using-git/learning-about-git/ignoring-files.md deleted file mode 100644 index fed1fc07b2..0000000000 --- a/translations/es-XL/content/github/using-git/learning-about-git/ignoring-files.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Ignorar archivos -redirect_from: - - /git-ignore/ - - /ignore-files/ - - /articles/ignoring-files - - /github/using-git/ignoring-files -intro: 'Puedes configurar Git para que ignore archivos que no quieres ingresar en {% data variables.product.product_name %}.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Configurar archivos ignorados para solo un repositorio - -Puedes crear un archivo de tipo *.gitignore* en el directorio raíz de tu repositorio para indicarle a Git qué archivos y directorios ignorar cuando haces una confirmación. Para compartir las reglas para ignorar con otros usuarios que clonan el repositorio, confirma el archivo de tipo *.gitignore* en tu repositorio. - -GitHub mantiene una lista oficial de archivos recomendados de tipo *.gitignore* para varios sistemas operativos, ambientes y lenguajes de programación populares en el repositorio público `github/gitignore`. También puedes usar gitignore.io para crear un archivo *.gitignore* para tu sistema operativo, lenguaje de programación o IDE. Para obtener más información, consulta la sección "[github/gitignore](https://github.com/github/gitignore)" y el sitio "[gitignore.io](https://www.gitignore.io/)". - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Navega a la ubicación de tu repositorio de Git. -3. Crea un archivo de tipo *.gitignore* para tu repositorio. - ```shell - $ touch .gitignore - ``` - -Para ver un archivo de tipo *.gitignore* de ejemplo, consulta la sección "[Algunas configuraciones comunes de .gitignore](https://gist.github.com/octocat/9257657)" en el repositorio de Octocat. - -Si quieres ignorar un archivo que ya se haya ingresado, deberás dejar de rastrearlo antes de que agregues una regla para ignorarlo. Desde tu terminal, deja de rastrear el archivo. - -```shell -$ git rm --cached FILENAME -``` - -### Configurar archivos ignorados para todos los repositorios en tu computador - -También puedes crear un archivo global de tipo *.gitignore* para definir una lista de reglas para ignorar archivos en cada repositorio de Git en tu computador. Por ejemplo, puedes crear el archivo en *~/.gitignore_global* y agregarle algunas normas. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Configura Git para que utilice el archivo de exclusión *~/.gitignore_global* en todos los repositorios de Git. - ```shell - $ git config --global core.excludesfile ~/.gitignore_global - ``` - -### Excluir archivos locales sin crear un archivo de tipo *.gitignore* - -Si no quieres crear un archivo *.gitignore* para compartir con otros, puedes crear normas que no estén confirmadas con el repositorio. Puedes utilizar esta técnica para los archivos generados de forma local que no esperas que otros usuarios generen, tales como los archivos creados por tu editor. - -Utiliza tu editor de texto favorito para abrir el archivo llamado *.git/info/exclude* dentro de la raíz de tu repositorio de Git. Cualquier norma que agregues aquí no se registrará y solo ignorará archivos de tu repositorio local. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Navega a la ubicación de tu repositorio de Git. -3. Utilizando tu editor de texto favorito, abre el archivo *.git/info/exclude*. - -### Leer más - -* [Ignorar archivos](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) en el libro de Pro Git -* [.gitignore](https://git-scm.com/docs/gitignore) en las páginas de man de Git -* [Una colección de plantillas útiles de *.gitignore* ](https://github.com/github/gitignore) en el repositorio github/gitignore -* Sitio de [gitignore.io](https://www.gitignore.io/) diff --git a/translations/es-XL/content/github/using-git/learning-about-git/index.md b/translations/es-XL/content/github/using-git/learning-about-git/index.md deleted file mode 100644 index 3e1e04f8be..0000000000 --- a/translations/es-XL/content/github/using-git/learning-about-git/index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Obtener información sobre Git -intro: '' -redirect_from: - - /articles/learning-about-git -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /git-workflows - - /associating-text-editors-with-git - - /configuring-git-to-handle-line-endings - - /ignoring-files ---- - diff --git a/translations/es-XL/content/github/using-git/managing-remote-repositories/about-remote-repositories.md b/translations/es-XL/content/github/using-git/managing-remote-repositories/about-remote-repositories.md deleted file mode 100644 index 647aa01aaf..0000000000 --- a/translations/es-XL/content/github/using-git/managing-remote-repositories/about-remote-repositories.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Acerca de los repositorios remotos -redirect_from: - - /articles/working-when-github-goes-down/ - - /articles/sharing-repositories-without-github/ - - /articles/about-remote-repositories - - /github/using-git/about-remote-repositories -intro: 'El enfoque colaborador de GitHub para el desarrollo depende en publicar confirmaciones de cambios desde tu repositorio local para que otras personas lo vean, lo extraigan y lo actualicen.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Una URL remota es la manera de Git de decir "el lugar donde se almacena tu código". Esa URL podría ser tu repositorio en GitHub o la bifurcación de otro usuario o incluso en un servidor completamente diferente. - -Solo puedes subir a dos tipos de direcciones URL: - -* Una URL HTTPS como `https://{% data variables.command_line.backticks %}/user/repo.git` -* Una URL SSH como `git@{% data variables.command_line.backticks %}:user/repo.git` - -Git asocia una URL remota con un nombre y tu remoto predeterminado generalmente se llama `origen`. - -Para obtener información sobre las diferencias entre estas URL, consulta "[¿Qué URL remota debo usar?](/articles/which-remote-url-should-i-use)" - -### Crear remotos - -Puedes usar el comando `git remote add` para hacer coincidir una URL remota con un nombre. Por ejemplo, escribirás lo siguiente en la línea de comandos: - -```shell -git remote add origin <REMOTE_URL> -``` - -Esto asocia el nombre `origin` con `REMOTE_URL`. - -Puedes usar el comando `git remote set-url` para [cambiar la URL de un remoto](/articles/changing-a-remote-s-url). diff --git a/translations/es-XL/content/github/using-git/managing-remote-repositories/adding-a-remote.md b/translations/es-XL/content/github/using-git/managing-remote-repositories/adding-a-remote.md deleted file mode 100644 index 7c1f400dd3..0000000000 --- a/translations/es-XL/content/github/using-git/managing-remote-repositories/adding-a-remote.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Agregar un remoto -intro: 'Para agregar un remoto nuevo, usa el comando `git remote add` en el terminal, dentro del directorio donde está almacenado tu repositorio.' -redirect_from: - - /articles/adding-a-remote - - /github/using-git/adding-a-remote -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -El comando `git remote add` toma dos argumentos: - -* Un nombre remoto, por ejemplo, `origin` -* Una URL remota, por ejemplo, `https://{% data variables.command_line.backticks %}/user/repo.git` - -Por ejemplo: - -```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/user/repo.git -# Set a new remote - -$ git remote -v -# Verify new remote -> origin https://{% data variables.command_line.codeblock %}/user/repo.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/user/repo.git (push) -``` - -¿No estás seguro de que URL usar? Examina "[¿Qué URL remota debería usar?](/articles/which-remote-url-should-i-use)" - -### Solución de problemas - -Puedes encontrar estos errores al tratar de agregar un remoto. - -#### El `nombre` remoto ya existe - -Este error significa que trataste de agregar un remoto con un nombre que ya existe en tu repositorio local: - -```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife -> fatal: remote origin already exists. -``` - -Para arreglar esto, puedes - -* Usar un nombre diferente para el nuevo remoto -* [Renombrar el remoto existente](/articles/renaming-a-remote) -* [Eliminar el remoto existente](/articles/removing-a-remote) - -### Leer más - -- "[Trabajar con remotos" desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-XL/content/github/using-git/managing-remote-repositories/changing-a-remotes-url.md b/translations/es-XL/content/github/using-git/managing-remote-repositories/changing-a-remotes-url.md deleted file mode 100644 index c8b131d906..0000000000 --- a/translations/es-XL/content/github/using-git/managing-remote-repositories/changing-a-remotes-url.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: Cambiar la URL de un remoto -redirect_from: - - /articles/changing-a-remote-s-url - - /articles/changing-a-remotes-url - - /github/using-git/changing-a-remotes-url -intro: El comando `git remote set-url` cambia una URL del repositorio remoto existente. -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% tip %} - -**Sugerencia:** Para obtener información sobre la diferencia entre las URL HTTPS y SSH consulta "[¿Qué URL remota debería usar?](/articles/which-remote-url-should-i-use)" - -{% endtip %} - -El comando `git remote set-url` toma dos argumentos: - -* Un nombre de remoto existente. Por ejemplo, `origin` o `upstream` son dos de las opciones comunes. -* Una nueva URL para el remoto. Por ejemplo: - * Si estás actualizando para usar HTTPS, tu URL puede verse como: -```shell -https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git -``` - * Si estás actualizando para usar SSH, tu URL puede verse como: -```shell -git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git -``` - -### Cambiar direcciones URL remotas de SSH a HTTPS - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Cambiar el directorio de trabajo actual en tu proyecto local. -3. Enumerar tus remotos existentes a fin de obtener el nombre de los remotos que deseas cambiar. - ```shell - $ git remote -v - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) - ``` -4. Cambiar tu URL remota de SSH a HTTPS con el comando `git remote set-url`. - ```shell - $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git - ``` -5. Verificar que la URL remota ha cambiado. - ```shell - $ git remote -v - # Verify new remote URL - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) - ``` - -La próxima vez que ejecutes `git`, `git pull` o `git push` en el repositorio remoto, se te pedirá el nombre de usuario y la contraseña de GitHub. - -- Si tienes habilitada la [autenticación de dos factores](/articles/securing-your-account-with-two-factor-authentication-2fa), debes [crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token) para usar en lugar de tu contraseña de GitHub. -- Puedes [utilizar un ayudante de credenciales](/github/using-git/caching-your-github-credentials-in-git) para que Git recuerde tu nombre de usuario y contraseña cada vez que se comunique con GitHub. - -### Switching remote URLs from HTTPS to SSH - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Cambiar el directorio de trabajo actual en tu proyecto local. -3. Enumerar tus remotos existentes a fin de obtener el nombre de los remotos que deseas cambiar. - ```shell - $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) - ``` -4. Cambiar tu URL remota de HTTPS a SSH con el comando `git remote set-url`. - ```shell - $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git - ``` -5. Verificar que la URL remota ha cambiado. - ```shell - $ git remote -v - # Verify new remote URL - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) - ``` - -### Solución de problemas - -Puedes encontrar estos errores cuando intentes cambiar un remoto. - -#### No existe tal remoto '[name]' - -Este error significa que el remoto que trataste de cambiar no existe: - -```shell -$ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife -> fatal: No such remote 'sofake' -``` - -Comprueba que escribiste correctamente el nombre del remoto. - -### Leer más - -- ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-XL/content/github/using-git/managing-remote-repositories/index.md b/translations/es-XL/content/github/using-git/managing-remote-repositories/index.md deleted file mode 100644 index 15122e5982..0000000000 --- a/translations/es-XL/content/github/using-git/managing-remote-repositories/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Administrar repositorios remotos -intro: 'Aprende a trabajar con tus repositorios locales en tu computadora y repositorios remotos alojados en {% data variables.product.product_name %}.' -redirect_from: - - /categories/18/articles/ - - /remotes/ - - /categories/managing-remotes/ - - /articles/managing-remote-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-remote-repositories - - /which-remote-url-should-i-use - - /adding-a-remote - - /changing-a-remotes-url - - /renaming-a-remote - - /removing-a-remote ---- - diff --git a/translations/es-XL/content/github/using-git/managing-remote-repositories/removing-a-remote.md b/translations/es-XL/content/github/using-git/managing-remote-repositories/removing-a-remote.md deleted file mode 100644 index df7e347ecb..0000000000 --- a/translations/es-XL/content/github/using-git/managing-remote-repositories/removing-a-remote.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Eliminar un remoto -intro: Utiliza el comando `git remote rm` para eliminar una URL remota de tu repositorio. -redirect_from: - - /articles/removing-a-remote - - /github/using-git/removing-a-remote -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -El comando `git remote rm` toma un argumento: - -* El nombre de un remoto, por ejemplo `destination` (destino) - -### Ejemplo - -These examples assume you're [cloning using HTTPS](/articles/which-remote-url-should-i-use/#cloning-with-https-urls), which is recommended. - -```shell -$ git remote -v -# Ver los remotos actuales -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) -> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch) -> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push) - -$ git remote rm destination -# Eliminar remoto -$ git remote -v -# Verificar que se haya ido -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) -``` - -{% warning %} - -**Nota**: `git remote rm` no elimina el repositorio remoto del servidor. Simplemente, elimina de tu repositorio local el remoto y sus referencias. - -{% endwarning %} - -### Solución de problemas - -Te puedes encontrar con estos errores al intentar eliminar un remoto. - -#### No se pudo eliminar la sección de configuración 'remote.[name]' - -Este error significa que el remoto que trataste de eliminar no existe: - -```shell -$ git remote rm sofake -> error: No se pudo eliminar la sección de configuración 'remote.sofake' -``` - -Comprueba que escribiste correctamente el nombre del remoto. - -### Leer más - -- ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-XL/content/github/using-git/managing-remote-repositories/renaming-a-remote.md b/translations/es-XL/content/github/using-git/managing-remote-repositories/renaming-a-remote.md deleted file mode 100644 index ea348e5fb5..0000000000 --- a/translations/es-XL/content/github/using-git/managing-remote-repositories/renaming-a-remote.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Renombrar un remoto -intro: Utiliza el comando `git remote rename` para renombrar un remoto existente. -redirect_from: - - /articles/renaming-a-remote - - /github/using-git/renaming-a-remote -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -El comando `git remote rename` toma dos argumentos: - -* Un nombre de remoto existente, por ejemplo, `origen` -* Un nombre nuevo para el remoto, por ejemplo, `destino` - -### Ejemplo - -These examples assume you're [cloning using HTTPS](/articles/which-remote-url-should-i-use/#cloning-with-https-urls), which is recommended. - -```shell -$ git remote -v -# Ver remotos existentes -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) - -$ git remote rename origin destination -# Cambiar el nombre del remoto de 'origen' a 'destino' - -$ git remote -v -# Verificar el nombre nuevo del remoto -> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) -``` - -### Solución de problemas - -Puedes encontrar estos errores cuando intentes renombrar un remoto. - -#### No se pudo renombrar la sección de configuración 'remoto.[nombre antiguo]' con 'remoto.[nombre nuevo]' - -Este error significa que el remoto que probaste con el nombre del remoto antiguo que escribiste no existe. - -Puedes verificar los remotos que existen actualmente con el comando `git remote -v`: - -```shell -$ git remote -v -# Ver remotos existentes -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) -``` - -#### El [nombre nuevo] del remoto ya existe. - -Este error significa que el nombre del remoto que quieres utilizar ya existe. Para resolverlo, utiliza un nombre de remoto diferente o renombra el remoto original. - -### Leer más - -- ["Working with Remotes" (Trabajar con remotos) desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/es-XL/content/github/using-git/managing-remote-repositories/which-remote-url-should-i-use.md b/translations/es-XL/content/github/using-git/managing-remote-repositories/which-remote-url-should-i-use.md deleted file mode 100644 index 9fc067743f..0000000000 --- a/translations/es-XL/content/github/using-git/managing-remote-repositories/which-remote-url-should-i-use.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: ¿Qué URL remota debería utilizar? -redirect_from: - - /articles/which-url-should-i-use/ - - /articles/which-remote-url-should-i-use - - /github/using-git/which-remote-url-should-i-use -intro: 'Existen varias formas de clonar los repositorios disponibles en {% data variables.product.prodname_dotcom %}.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cuando ves un repositorio mientras estás registrado en tu cuenta, las URL que puedes utilizar para clonar el proyecto en tu computadora están disponibles debajo de los detalles del repositorio: - -Para obtener información acerca de configurar o cambiar tu URL remota, consulta "[Cambiar la URL de un remoto](/articles/changing-a-remote-s-url)". - -### Cloning with HTTPS URLs - -Las URL clon `https://` están disponibles en todos los repositorios, públicos y privados. Estas URL funcionan aún si estás tras un cortafuegos o proxy. - -Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un repositorio mendiante URL con HTTPS en la línea de comando, Git te pedirá tu nombre de usuario y contraseña de {% data variables.product.product_name %}. {% data reusables.user_settings.password-authentication-deprecation %} - -{% data reusables.command_line.provide-an-access-token %} - -{% tip %} - -**Tips**: - -- Puedes utilizar un asistente de credenciales para que Git recuerde tus credenciales de {% data variables.product.prodname_dotcom %} cada que habla con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[ Almacenar tus credencialesde {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git)". - -- Para clonar un repositorio sin autenticarse en {% data variables.product.product_name %} desde la línea de comando, puedes utilizar {% data variables.product.prodname_desktop %} como alternativa. Para obtener más información, consulta la sección "[Clonar un repositorio desde {% data variables.product.prodname_dotcom %} hacia {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". - -{% endtip %} - - {% if currentVersion == "free-pro-team@latest" %}Si prefieres utilizar SSH pero no puedes conectarte por el puerto 22, podrías utilizar SSH a través del puerto HTTPS. Para obtener más información, consulta la sección "[Utilizar SSH a través del puerto HTTPS](/github/authenticating-to-github/using-ssh-over-the-https-port)".{% endif %} - -### Clonar con URL de SSH - -Las URL de SSH brindan acceso a un repositorio de Git por medio de SSH, un protocolo seguro. Para utilizar estas URL, debes generar un par de claves SSH en tu computador y añadir la llave **pública** a tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Conectarse a {% data variables.product.prodname_dotcom %} con SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)". - -Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un repositorio remoto utilizando URL de SSH, se te solicitará una contraseña y deberás ingresar tu frase de acceso con llave de SSH. Para obtener más información, consulta la sección "[Trabajar con frases de acceso con llave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)". - -{% if currentVersion == "free-pro-team@latest" %}Si estás intentando acceder a una organización que utiliza el inicio de sesión único (SSO) de SAML, debes autorizar tu llave de SSH para acceder a la organización antes de que te autentiques. 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/about-authentication-with-saml-single-sign-on)" y "[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 %} - -{% tip %} - -**Tip**: Puedes utilizar una URL con SSH para clonar un repositorio a tu computador, o como una forma segura de desplegar tu código en servidores productivos. También puedes utilizar el envío a un agente de SSH con tu script de despliegue para evitar administrar llaves en el servidor. Para obtener más información, consulta la sección "[Utilizar el Reenvío de Agente de SSH](/v3/guides/using-ssh-agent-forwarding/)". - -{% endtip %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} - -### Cloning with {% data variables.product.prodname_cli %} - -You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, the [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/) documentation. - -{% endif %} - -### Clonar con Subversion - -También puedes utilizar un cliente de [Subversion](https://subversion.apache.org/) para acceder a cualquier repositorio en {% data variables.product.prodname_dotcom %}. Subversion ofrece características diferentes a Git. Para obtener más información, consulta la sección "[¿Cuáles son las diferencias entre Subversion y Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" - -También puedes acceder a los repositorios de {% data variables.product.prodname_dotcom %} desde clientes de Subversion. Para obtener más información, consulta la sección "[Soporte para clientes de Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)". - -### Leer más - -- [Trabajar con URL Remotas](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) del sitio del libro de _Pro Git_ diff --git a/translations/es-XL/content/github/using-git/updating-credentials-from-the-macos-keychain.md b/translations/es-XL/content/github/using-git/updating-credentials-from-the-macos-keychain.md deleted file mode 100644 index 3a6bb55ffa..0000000000 --- a/translations/es-XL/content/github/using-git/updating-credentials-from-the-macos-keychain.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Actualizar credenciales desde la Keychain OSX -intro: 'Necesitarás actualizar tus credenciales guardadas en el asistente `git-credential-osxkeychain` si cambias tu nombre de usuario, contraseña o token de acceso personal en {% data variables.product.product_name %}.' -redirect_from: - - /articles/updating-credentials-from-the-osx-keychain - - Entrada de contraseña de GitHub en Keychain -versions: - free-pro-team: '*' - enterprise-server: '*' ---- - -{% data reusables.user_settings.password-authentication-deprecation %} - -### Actualizar tus credenciales a través de Keychain Access (Acceso keychain) - -1. Click on the Spotlight icon (magnifying glass) on the right side of the menu bar. Type `Keychain access` then press the Enter key to launch the app. ![Barra Spotlight Search (Búsqueda de Spotlight)](/assets/images/help/setup/keychain-access.png) -2. En Keychain Access (Acceso keychain), busca **{% data variables.command_line.backticks %}**. -3. Encuentra la entrada "internet password" (contraseña de internet) para `{% data variables.command_line.backticks %}`. ![Entrada de contraseña de GitHub en Keychain](/assets/images/help/setup/keychain-entry.png) -4. Edita o borra la entrada según corresponda. - -### Eliminar tus credenciales a través de la línea de comando - -A través de la línea de comando, puedes utilizar el ayudante de credenciales directamente para borrar la entrada keychain. - -Para hacerlo, escribe el siguiente comando: - -```shell -$ git credential-osxkeychain erase -host={% data variables.command_line.codeblock %} -protocol=https -> [Press Return] -``` - -Si resulta exitoso, no se imprimirá nada. Para ver si funciona, prueba y clona un repositorio desde {% data variables.product.product_location %}. Si te solicita una contraseña, la entrada keychain se eliminó. - -### Leer más - -- [Almacenar tus credenciales de {% data variables.product.prodname_dotcom %} en el caché dentro de Git](/github/using-git/caching-your-github-credentials-in-git/)" diff --git a/translations/es-XL/content/github/using-git/using-advanced-git-commands/about-git-rebase.md b/translations/es-XL/content/github/using-git/using-advanced-git-commands/about-git-rebase.md deleted file mode 100644 index 0d579d6385..0000000000 --- a/translations/es-XL/content/github/using-git/using-advanced-git-commands/about-git-rebase.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: Acerca del cambio de base de Git -redirect_from: - - /rebase/ - - articles/interactive-rebase/ - - /articles/about-git-rebase - - /github/using-git/about-git-rebase -intro: 'El comando `git rebase` te permite cambiar fácilmente una serie de confirmaciones, modificando el historial de tu repositorio. Puedes reordenar, editar o combinar confirmaciones.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Generalmente, usarás `git rebase` para: - -* Editar mensajes de confirmación previos. -* Combinar varias confirmaciones en una. -* Eliminar o revertir confirmaciones que ya no son necesarias. - -{% warning %} - -**Advertencia**: Como cambiar el historial de tu confirmación puede hacer las cosas difíciles para todos los que usan el repositorio, se considera una mala práctica cambiar de base las confirmaciones cuando ya las subiste a un repositorio. Para aprender cómo cambiar de base de forma segura en {% data variables.product.product_location %}, consulta "[Acerca de las fusiones de solicitud de extracción](/articles/about-pull-request-merges)". - -{% endwarning %} - -### Cambiar de base las confirmaciones con una rama - -Para cambiar de base todas las confirmaciones entre otra rama y el estado de rama actual, puedes ingresar el siguiente comando en tu shell (ya sea el símbolo del sistema para Windows o la terminal para Mac y Linux): - -```shell -$ git rebase --interactive other_branch_name -``` - -### Cambiar de base las confirmaciones en un momento específico - -Para cambiar de base las últimas confirmaciones en tu rama actual, puedes ingresar el siguiente comando en tu shell: - -```shell -$ git rebase --interactive HEAD~7 -``` - -### Comandos disponibles mientras se cambia de base - -Hay seis comandos disponibles mientras se cambia la base: - -
    -
    pick
    -
    pick simplemente significa que la confirmación está incluida. Reordenar los comandos pick cambia el orden de las confirmaciones cuando el cambio de base está en progreso. Si eliges no incluir una confirmación, debes eliminar la línea completa.
    - -
    reword
    -
    El comando reword es similar a pick, pero después de usarlo, el proceso de cambio de base se pausará y te dará una oportunidad de alterar el mensaje de confirmación. Cualquier cambio hecho por la confirmación no se ve afectado.
    - -
    editar
    -
    Si eliges edit una confirmación, se te dará la oportunidad de modificar la confirmación, lo que significa que puedes agregar o cambiar la confirmación por completo. También puedes realizar más confirmaciones antes de continuar con el cambio de base. Esto te permite dividir una confirmación grande en otras más pequeñas o eliminar cambios erróneos hechos en una confirmación.
    - -
    combinar
    -
    Este comando te permite combinar dos o más confirmaciones en una única confirmación. Una confirmación se combina en la confirmación de arriba. Git te da la oportunidad de escribir un mensaje de confirmación nuevo describiendo ambos cambios.
    - -
    fixup
    -
    Esto es similar a squash, pero se descarta el mensaje de la confirmación que se fusiona. La confirmación simplemente se fusiona en la confirmación de arriba y el mensaje de la confirmación anterior se usa para describir ambos cambios.
    - -
    exec
    -
    Esto te permite ejecutar comandos shell de forma arbitraria con una confirmación.
    -
    - -### Un ejemplo del uso de `git rebase` - -Sin importar qué comando uses, Git iniciará [tu editor de texto predeterminado](/articles/associating-text-editors-with-git) y abrirá un archivo que detalla las confirmaciones en el rango que has elegido. Ese archivo se ve así: - -``` -pick 1fc6c95 Patch A -pick 6b2481b Patch B -pick dd1475d something I want to split -pick c619268 A fix for Patch B -pick fa39187 something to add to patch A -pick 4ca2acc i cant' typ goods -pick 7b36971 something to move before patch B - -# Cambiar de base 41a72e6..7b36971 a 41a72e6 -# -# Commandos: -# p, pick = usar la confirmación -# r, reword = usar la confirmación, pero editar el mensaje de confirmación -# e, edit = usar la confirmación, pero detenerse para correcciones -# s, squash = usar la confirmación, pero unirla con la confirmación anterior -# f, fixup = como "squash", pero descartar el mensaje de registro de esta confirmación -# x, exec = ejecutar comando (el resto de la línea) usando shell -# -# Si eliminas una línea aquí, ESA CONFIRMACIÓN SE PERDERÁ. -# Sin embargo, si eliminas todo, este cambio de base será interrumpido. -# -``` - -Desglosando esta información, de principio a fin, vemos que: - -- Se enumeran siete confirmaciones, lo que indica que hubo siete cambios entre nuestro punto de partida y el estado de nuestra rama actual. -- Las confirmaciones que eliges cambiar de base se clasifican en el orden de los cambios más antiguos (arriba) a los cambios más nuevos (abajo). -- Cada línea detalla un comando (por defecto, `pick`), la confirmación SHA y el mensaje de confirmación. Todo el procedimiento `git rebase` se centra en tu manipulación de estas tres columnas. Los cambios que realizas son *rebased* en tu repositorio. -- Después de las confirmaciones, Git te dice el rango de confirmaciones con las que estamos trabajando (`41a72e6..7b36971`). -- Finalmente, Git te ayuda diciéndote los comandos que están disponibles para ti cuando cambias de base las confirmaciones. - -### Leer más - -- "[Usar Git rebase](/articles/using-git-rebase)" -- [El capítulo "Ramificación de Git" del libro _Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing) -- [El capítulo "Cambio de base interactivo" del libro _Pro Git_](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple) -- "[Combinar confirmaciones con cambio de base](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)" -- "[Sincronizar tu rama](/desktop/contributing-to-projects/syncing-your-branch)" en la documentación de {% data variables.product.prodname_desktop %} diff --git a/translations/es-XL/content/github/using-git/using-advanced-git-commands/about-git-subtree-merges.md b/translations/es-XL/content/github/using-git/using-advanced-git-commands/about-git-subtree-merges.md deleted file mode 100644 index d3662a62be..0000000000 --- a/translations/es-XL/content/github/using-git/using-advanced-git-commands/about-git-subtree-merges.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: Acerca de las fusiones de subárbol de Git -redirect_from: - - /articles/working-with-subtree-merge/ - - /subtree-merge/ - - /articles/about-git-subtree-merges - - /github/using-git/about-git-subtree-merges -intro: 'Si necesitas gestionar múltiples proyectos dentro de un solo repositorio, puedes usar una "fusión de subárbol" para manejar todas las referencias.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Habitualmente, una fusión de subárbol se usa para contener un repositorio dentro de otro repositorio. El "subrepositorio" se almacena en una carpeta del repositorio principal. - -La mejor manera de explicar las fusiones de subárbol es mostrar por ejemplo. Haremos lo siguiente: - -- Crear un repositorio vacío llamado `test` que represente nuestro proyecto. -- Fusionar otro repositorio en él como un subárbol llamado `Spoon-Knife`. -- El proyecto `test` usará ese subproyecto como si fuera parte del mismo repositorio. -- Recuperar actualizaciones desde `Spoon-Knife` hacia el proyecto `test`. - -### Configurar el repositorio vacío para una fusión de subárbol - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Crear un directorio nuevo y navegar a él. - ```shell - $ mkdir test - $ cd test - ``` -3. Inicializar un repositorio de Git nuevo. - ```shell - $ git init - > Initialized empty Git repository in /Users/octocat/tmp/test/.git/ - ``` -4. Crear y confirmar un archivo nuevo. - ```shell - $ touch .gitignore - $ git add .gitignore - $ git commit -m "initial commit" - > [master (root-commit) 3146c2a] initial commit - > 0 files changed, 0 insertions(+), 0 deletions(-) - > create mode 100644 .gitignore - ``` - -### Agregar un nuevo repositorio como subárbol - -1. Agregar una URL remota nueva que apunte a un proyecto por separado en el que estemos interesados. - ```shell - $ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git - > Updating spoon-knife - > warning: no common commits - > remote: Counting objects: 1732, done. - > remote: Compressing objects: 100% (750/750), done. - > remote: Total 1732 (delta 1086), reused 1558 (delta 967) - > Receiving objects: 100% (1732/1732), 528.19 KiB | 621 KiB/s, done. - > Resolving deltas: 100% (1086/1086), done. - > From git://github.com/octocat/Spoon-Knife - > * [new branch] master -> Spoon-Knife/master - ``` -2. Fusionar el proyecto `Spoon-Knife` en el proyecto de Git local. Esto no modifica ninguno de tus archivos localmente, pero prepara Git para el siguiente paso. - - Si estás usando Git 2.9 o superior: - ```shell - $ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/master - > Automatic merge went well; stopped before committing as requested - ``` - - Si estás usando Git 2.8 o inferior: - ```shell - $ git merge -s ours --no-commit spoon-knife/master - > Automatic merge went well; stopped before committing as requested - ``` -3. Crear un nuevo directorio denominado **spoon-knife**, y copiar el historial de Git del proyecto `Spoon-Knife` en él. - ```shell - $ git read-tree --prefix=spoon-knife/ -u spoon-knife/master - ``` -4. Confirmar los cambios para mantenerlos seguros. - ```shell - $ git commit -m "Subtree merged in spoon-knife" - > [master fe0ca25] Subtree merged in spoon-knife - ``` - -Aunque solo hemos agregado un subproyecto, se puede incorporar cualquier número de subproyectos en un repositorio de Git. - -{% tip %} - -**Sugerencia**: Si creas un clon nuevo del repositorio en el futuro, no se crearán los remotos que agregaste. Deberás volver a agregarlos mediante [el comando `git remote add`](/articles/adding-a-remote). - -{% endtip %} - -### Sincronizando con actualizaciones y cambios - -Cuando se agrega un subproyecto, no se mantiene sincronizado automáticamente con los cambios ascendentes. Necesitarás actualizar el subproyecto con el siguiente comando: - -```shell -$ git pull -s subtree remotename branchname -``` - -Para el ejemplo de más arriba, esto sería: - -```shell -$ git pull -s subtree spoon-knife master -``` - -### Leer más - -- [El capítulo "Fusión de subárbol" del libro _Pro Git_](https://git-scm.com/book/en/Git-Tools-Subtree-Merging) -- "[Cómo usar la estrategia de fusión de subárbol](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)" diff --git a/translations/es-XL/content/github/using-git/using-advanced-git-commands/index.md b/translations/es-XL/content/github/using-git/using-advanced-git-commands/index.md deleted file mode 100644 index 5810dcff03..0000000000 --- a/translations/es-XL/content/github/using-git/using-advanced-git-commands/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Utilizar comandos de Git avanzados -intro: '' -redirect_from: - - /categories/52/articles/ - - /categories/advanced-git/ - - /articles/using-advanced-git-commands - - /github/using-git/changing-author-info -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-git-rebase - - /using-git-rebase-on-the-command-line - - /resolving-merge-conflicts-after-a-git-rebase - - /about-git-subtree-merges - - /splitting-a-subfolder-out-into-a-new-repository ---- - diff --git a/translations/es-XL/content/github/using-git/using-advanced-git-commands/resolving-merge-conflicts-after-a-git-rebase.md b/translations/es-XL/content/github/using-git/using-advanced-git-commands/resolving-merge-conflicts-after-a-git-rebase.md deleted file mode 100644 index f9b516662d..0000000000 --- a/translations/es-XL/content/github/using-git/using-advanced-git-commands/resolving-merge-conflicts-after-a-git-rebase.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Resolver conflictos de fusión después de una rebase de Git -intro: 'Cuando realizas una operación `git rebase`, normalmente mueves confirmaciones de un lado a otro. Por este motivo, puedes generar una situación en la que se introduzca un conflicto de fusión. Esto implica que dos de tus confirmaciones modificaron la misma línea del mismo archivo, y Git no sabe qué cambio aplicar.' -redirect_from: - - /articles/resolving-merge-conflicts-after-a-git-rebase - - /github/using-git/resolving-merge-conflicts-after-a-git-rebase -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Después de reordenar y manipular confirmaciones utilizando `git rebase`, si ocurre un conflicto de fusión, Git te lo informará con el siguiente mensaje impreso en el terminal: - -```shell -error: no se pudo aplicar fa39187... algo para agregar al parte A - -Cuando hayas resuelto este problema, ejecuta "git rebase --continue". -Si prefieres saltear este parche, ejecuta "git rebase --skip". -Para revisar la rama original y detener el proceso de rebase, ejecuta "git rebase --abort". -No se pudo aplicar fa39187f3c3dfd2ab5faa38ac01cf3de7ce2e841... Cambia el archivo falso -``` - -Aquí Git te está diciendo qué confirmación está causando el conflicto (`fa39187`). Se te ofrecen tres opciones: - -* Puedes ejecutar `git rebase --abort` para deshacer por completo la rebase. Git te regresará al estado de tu rama tal como estaba antes de haber pedido `git rebase`. -* Puedes ejecutar `git rebase --skip` para saltear por completo la confirmación. Esto significa que no se incluirá ninguno de los cambios introducidos por la confirmación problemática. Es muy poco común que elijas esta opción. -* Puedes corregir el conflicto. - -Para corregir el conflicto, puedes seguir [los procedimientos estándar para resolver conflictos de fusión desde la línea de comando](/articles/resolving-a-merge-conflict-using-the-command-line). Cuando termines, tendrás que pedir `git rebase --continue` para que Git continúe procesando el resto de la rebase. diff --git a/translations/es-XL/content/github/using-git/using-advanced-git-commands/splitting-a-subfolder-out-into-a-new-repository.md b/translations/es-XL/content/github/using-git/using-advanced-git-commands/splitting-a-subfolder-out-into-a-new-repository.md deleted file mode 100644 index 8a23a4d967..0000000000 --- a/translations/es-XL/content/github/using-git/using-advanced-git-commands/splitting-a-subfolder-out-into-a-new-repository.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Dividir una subcarpeta en un nuevo repositorio -redirect_from: - - /articles/splitting-a-subpath-out-into-a-new-repository/ - - /articles/splitting-a-subfolder-out-into-a-new-repository - - /github/using-git/splitting-a-subfolder-out-into-a-new-repository -intro: Puedes convertir una carpeta dentro de un repositorio de Git en un nuevo repositorio. -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Si creas un nuevo clon del repositorio, no perderás ninguno de tus historiales o cambios de Git cuando divides una carpeta en un repositorio separado. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Cambia el directorio de trabajo actual a la ubicación donde deseas crear tu nuevo repositorio. -3. Clona el repositorio que contiene la subcarpeta. - ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME - ``` -4. Cambia el directorio de trabajo actual por tu repositorio clonado. - ```shell - $ cd REPOSITORY-NAME - ``` -5. Para filtrar la subcarpeta desde el resto de los archivos en el repositorio, ejecuta [`git filter-branch`](https://git-scm.com/docs/git-filter-branch), proporcionando esta información: - - `FOLDER-NAME`: la carpeta dentro de tu proyecto desde la que desearías crear un repositorio separado. - - {% windows %} - - {% tip %} - - **Sugerencia:** los usuarios de Windows deberían utilizar `/` para delimitar carpetas. - - {% endtip %} - - {% endwindows %} - - `BRANCH-NAME`: la rama por defecto de tu proyecto actual, por ejemplo, `master` (principal) o `gh-pages`. - ```shell - $ git filter-branch --prune-empty --subdirectory-filter FOLDER-NAME BRANCH-NAME - # Filter the specified branch in your directory and remove empty commits - > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) - > Ref 'refs/heads/BRANCH-NAME' was rewritten - ``` - El repositorio debería ahora únicamente contener archivos que estuvieron en tu subcarpeta. - -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) - - {% tip %} - - **Sugerencia:** Para obtener información sobre la diferencia entre las URL HTTPS y SSH consulta "[¿Qué URL remota debería usar?](/articles/which-remote-url-should-i-use)" - - {% endtip %} - -8. Verifica el nombre remoto existente para tu repositorio. Por ejemplo, `origin` o `upstream` son dos de las opciones comunes. - ```shell - $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push) - ``` - -9. Configura una URL remota nueva para tu nuevo repositorio utilizando el nombre remoto existente y la URL del repositorio remoto que copiaste en el paso 7. - ```shell - git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git - ``` -10. Verifica que la URL remota haya cambiado con el nombre de tu nuevo repositorio. - ```shell - $ git remote -v - # Verify new remote URL - > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push) - ``` -11. Sube tus cambios al nuevo repositorio en {% data variables.product.product_name %}. - ```shell - git push -u origin BRANCH-NAME - ``` diff --git a/translations/es-XL/content/github/using-git/using-advanced-git-commands/using-git-rebase-on-the-command-line.md b/translations/es-XL/content/github/using-git/using-advanced-git-commands/using-git-rebase-on-the-command-line.md deleted file mode 100644 index f6460f605a..0000000000 --- a/translations/es-XL/content/github/using-git/using-advanced-git-commands/using-git-rebase-on-the-command-line.md +++ /dev/null @@ -1,137 +0,0 @@ ---- -title: Utilizar la rebase de Git en la línea de comando -redirect_from: - - /articles/using-git-rebase/ - - /articles/using-git-rebase-on-the-command-line - - /github/using-git/using-git-rebase-on-the-command-line -intro: Aquí hay un breve tutorial acerca de usar `git rebase` en la línea de comando. -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -En este ejemplo, abordaremos todos los comandos disponibles de `git rebase`, excepto `exec`. - -Comenzaremos nuestra rebase ingresando `git rebase --interactive HEAD~7` en el terminal. Nuestro editor de texto preferido mostrará las siguientes líneas: - -``` -pick 1fc6c95 Patch A -pick 6b2481b Patch B -pick dd1475d something I want to split -pick c619268 A fix for Patch B -pick fa39187 something to add to patch A -pick 4ca2acc i cant' typ goods -pick 7b36971 something to move before patch B -``` - -En este ejemplo, haremos lo siguiente: - -* Combinar la quinta confirmación (`fa39187`) con la confirmación `"Patch A"` (`1fc6c95`), utilizando `squash` (combinar). -* Mover la última confirmación (`7b36971`) hacia arriba antes de la confirmación `"Patch B"` (`6b2481b`) y la conservarla como `pick`. -* Fusionar la confirmación `"A fix for Patch B"` (`c619268`) con la confirmación `"Patch B"` (`6b2481b`) y omitir el mensaje de confirmación utilizando `fixup`. -* Separar la tercera confirmación (`dd1475d`) en dos confirmaciones más pequeñas utilizando `edit` (editar). -* Corregir el mensaje de confirmación de la confirmación mal escrita (`4ca2acc`), utilizando `reword` (otro texto). - -¡Uf! Parece mucho trabajo, pero haciendo cada paso por vez, podemos concretar esos cambios fácilmente. - -Para comenzar, tendremos que modificar los comandos en el archivo para que luzca como sigue: - -``` -pick 1fc6c95 Patch A -squash fa39187 something to add to patch A -pick 7b36971 something to move before patch B -pick 6b2481b Patch B -fixup c619268 A fix for Patch B -edit dd1475d something I want to split -reword 4ca2acc i cant' typ goods -``` - -Hemos cambiado cada comando de la línea desde `pick` al comando que nos interesa. - -Ahora, guarda y cierra el editor; esto comenzará la rebase interactiva. - -Git saltea el primer comando de rebase, `pick 1fc6c95`, ya que no necesita hacer nada. Va al siguiente comando, `squash fa39187`. Como esta operación requiere tu entrada, Git vuelve a abrir tu editor de texto. El archivo que abre luce parecido a lo siguiente: - -``` -# Es una combinación de dos confirmaciones. -# El mensaje de la primera confirmación es: - -Patch A - -# Este es el mensaje de la 2.a confirmación: - -something to add to patch A - -# Ingresa el mensaje de confirmación para tus cambios. Las líneas que comienzan con -# con '#' se ignoran, y un mensaje vacío anula la confirmación. -# Actualmente no se encuentra en una rama. -# Cambios por confirmar: -# (usa "git reset HEAD ..." para deshacer) -# -# modificado: a -# -``` - -Este archivo es la manera de Git de decir, "Oye, esto es lo que estoy a punto de hacer con esta `squash` (combinación)". Detalla el primer mensaje de confirmación (`"Patch A"`) y el segundo mensaje de confirmación (`"something to add to patch A"`). Si estás satisfecho con estos mensajes de confirmación, puedes guardar el archivo y cerrar el editor. De lo contrario, tienes la opción de cambiar el mensaje de confirmación, simplemente, cambiando el texto. - -Cuando el editor esté cerrado, la rebase continúa: - -``` -pick 1fc6c95 Patch A -squash fa39187 something to add to patch A -pick 7b36971 something to move before patch B -pick 6b2481b Patch B -fixup c619268 A fix for Patch B -edit dd1475d something I want to split -reword 4ca2acc i cant' typ goods -``` - -Git procesa los dos comandos `pick` (para `pick 7b36971` y `pick 6b2481b`). *También* procesa el comando `fixup` (`fixup c619268`), ya que este no necesita ninguna interacción. `fixup` fusiona los cambios de `c619268` en la confirmación que tiene ante sí, `6b2481b`. Ambos cambios tendrán el mismo mensaje de confirmación: `"Patch B"`. - -Git llega a la operación `edit dd1475d`, se detiene e imprime el siguiente mensaje para el terminal: - -```shell -Puedes modificar la confirmación ahora con - - git commit --amend - -Una vez que estés satisfecho con tus cambios, ejecuta - - git rebase --continue -``` - -En este punto, puedes editar cualquiera de los archivos de tu proyecto para hacer más cambios. Para cada cambio que hagas, tendrás que realizar una confirmación nueva. Lo puedes hacer ingresando el comando `git commit --amend`. Cuando termines de hacer todos tus cambios, puedes ejecutar `git rebase --continue`. - -Luego Git llega al comando `reword 4ca2acc`. Este abre tu editor de texto una vez más y presenta la siguiente información: - -``` -i cant' typ goods - -# Ingresa el mensaje de confirmación para tus cambios. Las líneas que comienzan con -# con '#' se ignoran, y un mensaje vacío anula la confirmación. -# Actualmente no se encuentra en una rama. -# Cambios por confirmar: -# (use "git reset HEAD^1 ..." to unstage) -# -# modificado: a -# -``` - -Como antes, Git muestra el mensaje de confirmación para que lo edites. Puedes cambiar el texto (`"i cant' typ goods"`), guardar el archivo y cerrar el editor. Git terminará la rebase y te devolverá al terminal. - -### Subir código de rebase a GitHub - -Como has modificado el historial de Git, el `git push origin` común **no** funcionará. Tendrás que modificar el comando realizando un "empuje forzado" de tus últimos cambios: - -```shell -$ git push origin master --force -``` - -{% warning %} - -El cargar forzadamente tiene implicaciones serias ya que cambia la secuencia del historial de confirmaciones para la rama. Utilízalo con cuidado, especialmente si muchas personas acceden a tu repositorio. - -{% endwarning %} - -### Leer más - -* "[Resolver conflictos de fusión después de una rebase de Git](/articles/resolving-merge-conflicts-after-a-git-rebase)" diff --git a/translations/es-XL/content/github/using-git/using-common-git-commands/dealing-with-non-fast-forward-errors.md b/translations/es-XL/content/github/using-git/using-common-git-commands/dealing-with-non-fast-forward-errors.md deleted file mode 100644 index 05d5d1ff01..0000000000 --- a/translations/es-XL/content/github/using-git/using-common-git-commands/dealing-with-non-fast-forward-errors.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Tratamiento de errores sin avance rápido -intro: 'En ocasiones, Git no puede efectuar tu cambio en un repositorio remoto sin perder confirmaciones. Cuando esto sucede, los cambios que deseas subir se rechazan.' -redirect_from: - - /articles/dealing-with-non-fast-forward-errors - - /github/using-git/dealing-with-non-fast-forward-errors -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Si otra persona ha subido cambios en la misma rama que tú, Git no podrá subir tus cambios: - -```shell -$ git push origin master -> To https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git -> ! [rejected] master -> master (non-fast-forward) -> error: failed to push some refs to 'https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git' -> To prevent you from losing history, non-fast-forward updates were rejected -> Merge the remote changes (e.g. 'git pull') before pushing again. See the -> 'Note about fast-forwards' section of 'git push --help' for details. -``` - -Puedes resolver este problema [extrayendo y fusionando](/articles/getting-changes-from-a-remote-repository) los cambios realizados en la rama remota con los cambios que has hecho localmente: - -```shell -$ git fetch origin -# Fetches updates made to an online repository -$ git merge origin YOUR_BRANCH_NAME -# Merges updates made online with your local work -``` - -O bien, puedes simplemente usar `git pull` para ejecutar al mismo tiempo ambos comandos: - -```shell -$ git pull origin YOUR_BRANCH_NAME -# Grabs online updates and merges them with your local work -``` diff --git a/translations/es-XL/content/github/using-git/using-common-git-commands/getting-changes-from-a-remote-repository.md b/translations/es-XL/content/github/using-git/using-common-git-commands/getting-changes-from-a-remote-repository.md deleted file mode 100644 index ddf6a0ab65..0000000000 --- a/translations/es-XL/content/github/using-git/using-common-git-commands/getting-changes-from-a-remote-repository.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Obtener cambios de un repositorio remoto -intro: Puedes usar los comandos Git más frecuentes para acceder a repositorios remotos. -redirect_from: - - /articles/fetching-a-remote/ - - /articles/getting-changes-from-a-remote-repository - - /github/using-git/getting-changes-from-a-remote-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Estos comandos son muy útiles cuando interactúas con [un repositorio remoto](/articles/about-remote-repositories). `clone` y `fetch` descargan código remoto de la URL de un repositorio remoto en tu computadora local, `merge` se usa para fusionar el trabajo de diferentes personas con el tuyo, y `pull` es una combinación de `fetch` y `merge`. - -### Clonar un repositorio - -Para obtener una copia completa del repositorio de otro usuario, usa `git clone` de la siguientes manera: - -```shell -$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git -# Clona el repositorio en tu computadora -``` - -Puedes elegir entre [distintas URL](/articles/which-remote-url-should-i-use) cuando clonas un repositorio. Cuando inicias sesión en {% data variables.product.prodname_dotcom %}, estas URL están disponibles debajo de los detalles del repositorio: - -![Lista de URL remotas](/assets/images/help/repository/remotes-url.png) - -Cuando ejecutas `git clone`, se producen las siguientes acciones: -- Se forma una nueva carpeta llamada `repo`. -- Esta carpeta se inicializa como un repositorio de Git. -- Se crea un remoto llamado `origin` que apunta a la URL desde donde clonaste. -- Todos los archivos y confirmaciones del repositorio se descargan aquí. -- La rama predeterminada está desmarcada - -Para cada rama `foo` en el repositorio remoto, se crea la rama de seguimiento remoto correspondiente `refs/remotes/origin/foo` en tu repositorio local. Por lo general, puedes abreviar estos nombres de rama de seguimiento remoto como `origin/foo`. - -### Extraer cambios de un repositorio remoto - -Usa `git fetch` para recuperar trabajo nuevo realizado por otras personas. Extraer desde un repositorio permite obtener todas las etiquetas y ramas de seguimiento remoto *sin* fusionar estos cambios en tus propias ramas. - -Si ya tienes un repositorio local [con una URL remota](/articles/adding-a-remote) configurada para el proyecto deseado, puedes obtener toda la información nueva usando `git fetch *remotename*` en la terminal: - -```shell -$ git fetch remotename -# Extrae las actualizaciones realizadas en un repositorio remoto -``` - -Si no, siempre puedes [agregar un nuevo remoto](/articles/adding-a-remote) y luego extraer. - -### Fusionar cambios en tu rama local - -La fusión combina tus cambios locales con los cambios realizados por otros. - -Por lo general, fusionas una rama de seguimiento remoto (es decir, una rama extraída desde un repositorio remoto) con tu rama local: - -```shell -$ git merge remotename/branchname -# Fusiona actualizaciones realizadas en línea con tu trabajo local -``` - -### Extraer cambios de un repositorio remoto - -`git pull` es un atajo conveniente para realizar tanto `git fetch` y `git merge` en el mismo comando: - -```shell -$ git pull remotename branchname -# Obtiene actualizaciones en línea y las fusiona con tu trabajo local. -``` - -Como `pull` realiza una fusión en los cambios recuperados, debes asegurarte de que tu trabajo local esté confirmado antes de ejecutar el comando `pull`. Si se produce un [conflicto de fusión](/articles/resolving-a-merge-conflict-using-the-command-line) que no puedes resolver, o si decides abandonar la fusión, puedes usar `git merge --abort` para hacer que la rama vuelva al estado anterior antes de que extrajeras. - -### Leer más - -- "[Trabajar con remotos" desde el libro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes){% if currentVersion == "free-pro-team@latest" %} -- "[Solucionar problemas de conectividad ](/articles/troubleshooting-connectivity-problems)"{% endif %} diff --git a/translations/es-XL/content/github/using-git/using-common-git-commands/index.md b/translations/es-XL/content/github/using-git/using-common-git-commands/index.md deleted file mode 100644 index e4c946fa02..0000000000 --- a/translations/es-XL/content/github/using-git/using-common-git-commands/index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Utilizar comandos de Git comunes -intro: '' -redirect_from: - - /articles/using-common-git-commands -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /pushing-commits-to-a-remote-repository - - /getting-changes-from-a-remote-repository - - /dealing-with-non-fast-forward-errors ---- - diff --git a/translations/es-XL/content/github/using-git/using-common-git-commands/pushing-commits-to-a-remote-repository.md b/translations/es-XL/content/github/using-git/using-common-git-commands/pushing-commits-to-a-remote-repository.md deleted file mode 100644 index d14c47bcb9..0000000000 --- a/translations/es-XL/content/github/using-git/using-common-git-commands/pushing-commits-to-a-remote-repository.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: Subir confirmaciones de cambios a un repositorio remoto -intro: Utiliza `git push` para subir confirmaciones de cambios realizadas en tu rama local a un repositorio remoto. -redirect_from: - - /articles/pushing-to-a-remote/ - - /articles/pushing-commits-to-a-remote-repository - - /github/using-git/pushing-commits-to-a-remote-repository -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -El comando `git push` toma dos argumentos: - -* Un nombre remoto, por ejemplo, `origin` -* Una rama remota, por ejemplo, `master` (principal) - -Por ejemplo: - -```shell -git push <REMOTENAME> <BRANCHNAME> -``` - -Como ejemplo, generalmente ejecutas `git push origin master` para subir los cambios locales a tu repositorio en línea. - -### Renombrar ramas - -Para renombrar una rama, utilizarías el mismo comando `git push`, pero agregarías un argumento más: el nombre de la nueva rama. Por ejemplo: - -```shell -git push <REMOTENAME> <LOCALBRANCHNAME>:<REMOTEBRANCHNAME> -``` - -Esto sube `LOCALBRANCHNAME` a tu `REMOTENAME`, pero es renombrado a `REMOTEBRANCHNAME`. - -### Abordar errores sin avance rápido - -Si tu copia local de un repositorio está desincronizada, o "atrasada", con respecto al repositorio ascendente al que estás subiendo, recibirás un mensaje que dice que `non-fast-forward updates were rejected (las actualizaciones sin avance rápido se rechazaron)`. Esto significa que debes recuperar, o "extraer", los cambios ascendentes, antes de poder subir tus cambios locales. - -Para obtener más información sobre este error, consulta "[Abordar errores sin avance rápido](/articles/dealing-with-non-fast-forward-errors)." - -### Subir etiquetas - -Por defecto, y sin parámetros adicionales, `git push` envía todas las ramas que coinciden para que tengan el mismo nombre que las ramas remotas. - -Para subir una etiqueta única, puedes emitir el mismo comando que al subir una rama: - -```shell -git push <REMOTENAME> <TAGNAME> -``` - -Para subir todas tus etiquetas, puede escribir el comando: - -```shell -git push <REMOTENAME> --tags -``` - -### Eliminar una etiqueta o rama remota - -La sintaxis para borrar una rama es un poco críptica a primera vista: - -```shell -git push <REMOTENAME> :<BRANCHNAME> -``` - -Nota que hay un espacio antes de los dos puntos. El comando se parece a los mismos pasos que tomarías para renombrar una rama. Sin embargo, aquí estás diciéndole a Git que no suba _nada_ dentro de `BRANCHNAME` en `REMOTENAME`. Debido a esto, `git push` elimina la rama en el repositorio remoto. - -### Remotos y bifurcaciones - -Posiblemente ya sepas que [puedes "bifurcar" repositorios](https://guides.github.com/overviews/forking/) en GitHub. - -Cuando clonas un repositorio de tu propiedad, le proporcionas una URL remota que le indica a Git dónde extraer y subir actualizaciones. Si deseas colaborar con el repositorio original, agregarías una nueva a URL remota, normalmente llamada `upstream` (ascendente), a tu clon de Git local: - -```shell -git remote add upstream <THEIR_REMOTE_URL> -``` - -Ahora, puedes extraer actualizaciones y ramas de *sus* bifurcaciones: - -```shell -git extrae ascendente -# Toma las ramas de los remotos ascendentes -> remoto: Contando objetos: 75, realizado. -> remoto: Comprimiendo objetos: 100 % (53/53), realizado. -> remoto: Total 62 (delta 27), reutilizados 44 (delta 9) -> Descompimiendo objetos: 100 % (62/62), realizado. -> Desde https://{% data variables.command_line.codeblock %}/octocat/repo -> * [nueva rama] master -> upstream/master -``` - -Cuando hayas finalizado tus cambios locales, puedes subir tu rama local a GitHub e [iniciar una solicitud de extracción](/articles/about-pull-requests). - -Para obtener más información sobre cómo trabajar con bifurcaciones, consulta "[Sincronizar una bifurcación](/articles/syncing-a-fork)". - -### Leer más - -- [El capítulo "Remotos" del libro "Pro Git"](https://git-scm.com/book/ch5-2.html) -- [Documentación en línea sobre `git remote`](https://git-scm.com/docs/git-remote.html) -- "[Git cheatsheet](/articles/git-cheatsheet)" (Hoja introductoria de Git) -- "[Flujos de trabajo de Git](/articles/git-workflows)" diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/about-repository-graphs.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/about-repository-graphs.md deleted file mode 100644 index ff4c3b35b7..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/about-repository-graphs.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Acerca de los gráficos del repositorio -intro: Los gráficos del repositorio te ayudan a ver y analizar datos para tu repositorio. -redirect_from: - - /articles/using-graphs/ - - /articles/about-repository-graphs - - /github/visualizing-repository-data-with-graphs/about-repository-graphs -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Los gráficos de un repositorio te dan información sobre el tráfico de {% if currentVersion == "free-pro-team@latest" %}, los proyectos que dependen del repositorio, {% endif %} los colaboradores y las confirmaciones para el repositorio y la red y las bifurcaciones de un repositorio. Si tú mantienes un repositorio, puedes usar estos datos para comprender mejor quién está usando tu repositorio y por qué lo están usando. - -{% if currentVersion == "free-pro-team@latest" %} - -Algunos gráficos del repositorio solo están disponibles en repositorios públicos con {% data variables.product.prodname_free_user %}: -- Pulso -- Colaboradores -- Tráfico -- Confirmaciones -- Frecuencia de código -- Red - -Todos los otros gráficos del repositorio están disponibles en todos los repositorios. Cada gráfico del repositorio está disponible en repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} y {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} - -{% endif %} - -### Leer más - -- "[Acceso a datos básicos del repositorio](/articles/accessing-basic-repository-data)" -- "[Analizar cambios en el contenido de un repositorio](/articles/analyzing-changes-to-a-repository-s-content)" -- "[Comprender las conexiones entre repositorios](/articles/understanding-connections-between-repositories)" diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/index.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/index.md deleted file mode 100644 index 33572db98f..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Acceso a datos básicos del repositorio -intro: 'Puedes ver información básica sobre un repositorio, como la actividad del repositorio{% if currentVersion == "free-pro-team@latest" %}, el tráfico,{% endif %} y la actividad de la contribución.' -redirect_from: - - /articles/accessing-basic-repository-data -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /about-repository-graphs - - /viewing-a-summary-of-repository-activity - - /viewing-a-projects-contributors - - /viewing-traffic-to-a-repository ---- - diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-projects-contributors.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-projects-contributors.md deleted file mode 100644 index b551eee981..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-projects-contributors.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Ver los colaboradores de un proyecto -intro: 'Puedes ver quién aportó confirmaciones a un repositorio{% if currentVersion == "free-pro-team@latest" %} y sus dependencias{% endif %}.' -redirect_from: - - /articles/i-don-t-see-myself-in-the-contributions-graph/ - - /articles/viewing-contribution-activity-in-a-repository/ - - /articles/viewing-a-projects-contributors - - /github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors -product: '{% data reusables.gated-features.repository-insights %}' -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -### Acerca de los colaboradores - -Puedes ver hasta 100 colaboradores de un repositorio{% if currentVersion != "free-pro-team@latest" %}, incluidos los coautores de confirmaciones,{% endif %} en el gráfico de colaboradores. Las confirmaciones de fusión y las confirmaciones vacías no se cuentan en las contribuciones para este gráfico. - -{% if currentVersion == "free-pro-team@latest" %} -You can also see a list of people who have contributed to the project's Python dependencies. Para acceder a esta lista de colaboradores de la comunidad, visita `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`. -{% endif %} - -### Acceder al gráfico de colaboradores - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -3. En la barra lateral izquierda, haz clic en **Contributors (Colaboradores)**. ![Pestaña de colaboradores](/assets/images/help/graphs/contributors_tab.png) -4. Como alternativa, para ver colaboradores durante un período de tiempo específico, haz clic, después arrastra hasta que se selecciona el período de tiempo. ![Rango de tiempo seleccionado en el gráfico de colaboradores](/assets/images/help/graphs/repo_contributors_click_drag_graph.png) - -### Resolución de problemas con colaboradores - -Si no apareces en el gráfico de colaboradores de un repositorio, puede deberse a que: -- No eres uno de los 100 colaboradores principales. -- Tus confirmaciones no se han fusionado en la rama por defecto. -- La dirección de correo electrónico que utilizaste como el autor de las confirmaciones no se ha agregado a tu cuenta {% data variables.product.product_name %}. - -{% tip %} - -**Tip:** Para listar todos los colaboradores de una confirmación en un repositorio, consulta la sección "[Repositorios](/v3/repos/#list-contributors)". - -{% endtip %} - -Si todas tus confirmaciones en el repositorio están en ramas que no son por defecto, no estarás en el gráfico de colaboradores. Por ejemplo, las confirmaciones en la rama `gh-pages` no están incluidas en el gráfico excepto que `gh-pages` sea la rama por defecto del repositorio. Para que tus confirmaciones se fusionen en la rama por defecto, puedes crear una solicitud de extracción. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)." - -Si la dirección de correo electrónico que utilizaste como el autor de las confirmaciones no se ha agregado a tu cuenta {% data variables.product.product_name %}, tus confirmaciones no se vincularán a tu cuenta y no aparecerás en el gráfico de colaboradores. Para obtener más información, consulta "[Configurar tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)" y "[Agregar una dirección de correo electrónico a tu cuenta {% data variables.product.product_name %}](/articles/adding-an-email-address-to-your-github-account)." diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-summary-of-repository-activity.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-summary-of-repository-activity.md deleted file mode 100644 index 144526c1e9..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-summary-of-repository-activity.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Ver un resumen de la actividad de un repositorio -intro: 'Puedes ver un resumen de la actividad de un repositorio a través de Pulse. Pulse incluye una lista de solicitudes de extracción abiertas y fusionadas, propuestas abiertas y cerradas y un gráfico que muestra la actividad de confirmación de los 15 usuarios principales que confirmaron la rama por defecto del proyecto en el [período de tiempo] seleccionado [time period](/articles/viewing-a-summary-of-repository-activity#filtering-by-time).' -product: '{% data reusables.gated-features.repository-insights %}' -redirect_from: - - /articles/viewing-a-summary-of-repository-activity - - /github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -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. - -### Acceder a Pulse - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} - -### Filtrar por tiempo - -Por defecto, Pulse muestra los últimos siete días de actividad del repositorio. Para elegir un período de tiempo diferente, haz clic en el menú desplegable de **Period (Período)** en el ángulo superior derecho del resumen de Pulse. - -![Filtrar la actividad de Pulse por tiempo](/assets/images/help/pulse/pulse_time_filter_dropdown.png) diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-traffic-to-a-repository.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-traffic-to-a-repository.md deleted file mode 100644 index e4f88be595..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-traffic-to-a-repository.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Viewing traffic to a repository -intro: 'Anyone with push access to a repository can view its traffic, including full clones (not fetches), visitors from the past 14 days, referring sites, and popular content in the traffic graph.' -product: 'This repository insights graph is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[About repository graphs](/articles/about-repository-graphs)" and "[{% data variables.product.prodname_dotcom %}''s products](/articles/github-s-products)."{% endif %}' -redirect_from: - - /articles/viewing-traffic-to-a-repository - - /github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository -versions: - free-pro-team: '*' -topics: - - Repositories ---- -You can navigate to referring sites, excluding search engines and {% data variables.product.product_name %} itself, from the links the specific paths were referred from. The popular content links to the specific content that generated traffic. - -Referring sites and popular content are ordered by views and unique visitors. Full clones and visitor information update hourly, while referring sites and popular content sections update daily. All data in the traffic graph uses the UTC+0 timezone, regardless of your location. - -{% tip %} - -**Tip:** You can hover over a specific day in the traffic graph to view the exact data for that day. - -{% endtip %} - -![Repository traffic graphs with tooltip](/assets/images/help/graphs/repo_traffic_graphs_tooltip_dotcom.png) - -### Accessing the traffic graph - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -3. In the left sidebar, click **Traffic**. -![Traffic tab](/assets/images/help/graphs/traffic_tab.png) diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/index.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/index.md deleted file mode 100644 index f298011998..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Analizar cambios en el contenido de un repositorio -intro: 'Puedes ver los cambios en el contenido de un repositorio al analizar las confirmaciones del repositorio, la frecuencia de confirmación, y las incorporaciones y eliminaciones de contenido.' -redirect_from: - - /articles/viewing-commit-frequency-in-a-repository/ - - /articles/analyzing-changes-to-a-repository-s-content - - /articles/analyzing-changes-to-a-repositorys-content -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /visualizing-commits-in-a-repository - - /visualizing-additions-and-deletions-to-content-in-a-repository ---- - diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/visualizing-additions-and-deletions-to-content-in-a-repository.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/visualizing-additions-and-deletions-to-content-in-a-repository.md deleted file mode 100644 index 5f3310cc09..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/visualizing-additions-and-deletions-to-content-in-a-repository.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Ver incorporaciones y eliminaciones al contenido de un repositorio -intro: El gráfico de frecuencia de código muestra las incorporaciones y eliminaciones de contenido de cada semana en el historial de un repositorio. -product: '{% data reusables.gated-features.repository-insights %}' -redirect_from: - - /articles/visualizing-additions-and-deletions-to-content-in-a-repository - - /github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -{% if currentVersion == "free-pro-team@latest" %} - -![Gráfico de frecuencia de código](/assets/images/help/graphs/repo_code_frequency_graph_dotcom.png) - -{% endif %} - -### Acceder al gráfico de frecuencia de código - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -3. En la barra lateral izquierda, haz clic en **Code frequency (Frecuencia del código)**. ![Pestaña de frecuencia de código](/assets/images/help/graphs/code_frequency_tab.png) diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/visualizing-commits-in-a-repository.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/visualizing-commits-in-a-repository.md deleted file mode 100644 index 7b6f2d64fa..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/visualizing-commits-in-a-repository.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Ver confirmaciones en un repositorio -intro: Puedes ver todas las confirmaciones realizadas a un repositorio en el último año (excluidas las confirmaciones de fusión) en el gráfico de confirmación. -product: '{% data reusables.gated-features.repository-insights %}' -redirect_from: - - /articles/visualizing-commits-in-a-repository - - /github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -El gráfico superior muestra las confirmaciones del año completo por semana. - -![Gráfico anual de confirmaciones de un repositorio](/assets/images/help/graphs/repo_commit_activity_year_graph.png) - -El gráfico inferior muestra la cantidad promedio de confirmaciones por día de la semana para la semana seleccionada. - -![Gráfico semanal de confirmaciones de un repositorio](/assets/images/help/graphs/repo_commit_activity_week_graph.png) - -### Acceder al gráfico de confirmación - -{% data reusables.repositories.navigate-to-repo %} -{% 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) diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/index.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/index.md deleted file mode 100644 index af7d0b8d78..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/index.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Visualizar datos del repositorio con gráficos -redirect_from: - - /categories/44/articles/ - - /categories/graphs-and-contributions/ - - /categories/graphs/ - - /categories/visualizing-repository-data-with-graphs -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /accessing-basic-repository-data - - /analyzing-changes-to-a-repositorys-content - - /understanding-connections-between-repositories ---- -### Índice - - - - diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/about-the-dependency-graph.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/about-the-dependency-graph.md deleted file mode 100644 index 20a670b7df..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/about-the-dependency-graph.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: About the dependency graph -intro: 'Detailed information about the dependency graph, the ecosystems it supports, and how it determines which packages a repository depends on.' -versions: - enterprise-server: <=2.22 -topics: - - Repositories -redirect_from: - - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph ---- -### Dependency graph availability - -The dependency graph is available for every{% if currentVersion == "free-pro-team@latest" %} public{% endif %} repository that defines dependencies in a supported package ecosystem using a supported file format.{% if currentVersion == "free-pro-team@latest" %} Repository administrators can also set up the dependency graph for private repositories.{% endif %} - -{% data reusables.repositories.enable-security-alerts %} - -### About the dependency graph - -The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows{% if currentVersion == "free-pro-team@latest" %}: - -- Dependencies, the ecosystems and packages it depends on -- Dependents, the repositories and packages that depend on it{% else %} dependencies, that is, the ecosystems and packages it depends on. {% data variables.product.prodname_ghe_server %} does not calculate information about dependents, the repositories and packages that depend on a repository.{% endif %} - -When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% if currentVersion == "free-pro-team@latest" %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below. - -### Dependencies included - -The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes: - -- Direct dependencies, that are explicitly defined in a manifest or lock file -- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies - -The dependency graph identifies indirect dependencies{% if currentVersion == "free-pro-team@latest" %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. - -{% if currentVersion == "free-pro-team@latest" %} -### Dependents included - -For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %} - -### Using the dependency graph - -You can use the dependency graph to: - -- Explore the repositories your code depends on{% if currentVersion == "free-pro-team@latest" %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% if currentVersion == "free-pro-team@latest" %} -- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %} -- View and update vulnerable dependencies for your repository. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." - -### Enabling the dependency graph - -{% if currentVersion == "free-pro-team@latest" %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %}If the dependency graph is not available in your system, your site administrator can enable the dependency graph and {% data variables.product.prodname_dependabot_short %} alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} If the dependency graph is not available in your system, your site administrator can enable the dependency graph and security alerts. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." - -{% endif %} - -When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% if currentVersion == "free-pro-team@latest" %} and every push to other repositories in the graph{% endif %}. - -### Supported package ecosystems - -The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% if currentVersion == "free-pro-team@latest" %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for vulnerable dependencies.{% endif %} - -| Package manager | Languages | Recommended formats | All supported formats | -| --- | --- | --- | ---| -| Composer | PHP | `composer.lock` | `composer.json`, `composer.lock` | -| `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | -| Maven | Java, Scala | `pom.xml` | `pom.xml` | -| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| -| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile.lock`, `setup.py`* | -| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` | -| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` | - -{% note %} - -**Note:** If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project. - -{% endnote %} - -### Further reading - -- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia -- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"{% endif %} diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/exploring-the-dependencies-of-a-repository.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/exploring-the-dependencies-of-a-repository.md deleted file mode 100644 index 11d0616cec..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/exploring-the-dependencies-of-a-repository.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: Explorar las dependencias de un repositorio -intro: 'Al utilizar la gráfica de dependencias, puedes ver los paquetes de los cuales depende tu proyecto {% if currentVersion == "free-pro-team@latest" %} y los repositorios que dependen de él{% endif %}. Adicionalmente, puedes ver cualquier vulnerabilidad que se detecte en sus dependencias.' -redirect_from: - - /github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository -versions: - enterprise-server: <=2.22 -topics: - - Repositories ---- -### Visualizar la gráfica de dependencias - -{% data reusables.repositories.enable-security-alerts %} - -La gráfica de dependencias muestra las dependencias{% if currentVersion == "free-pro-team@latest" %} y los dependientes{% endif %} de tu repositorio. Para obtener más información acerca de la detección de dependencias y de cuáles ecosistemas son compatibles, consulta la sección [Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.click-dependency-graph %}{% if currentVersion == "free-pro-team@latest" %} -4. Opcionalmente, debajo de "Gráfica de dependencias", da clic en **Dependientes**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %} - -#### Vista de dependencias - -{% if currentVersion == "free-pro-team@latest" %} -Las dependencias se agrupan por ecosistema. Puedes expandir una dependencia para ver a su vez sus dependencias. Para las dependencias en repositorios públicos hospedadas en {% data variables.product.product_name %}, también puedes dar clic en una de ellas para ver el repositorio. Las dependencias en los repositorios privados, paquetes privados, o archivos no reconocidos se muestran en texto simple. - -Si se han detectado vulnerabilidades en el repositorio, estas se muestran en la parte superior de la vista para los usuarios con acceso a {% data variables.product.prodname_dependabot_alerts %}. - -![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph.png) - -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %} -Se listará cualquier dependencia directa e indirecta que se especifique en los archivos de bloqueo o de manifiesto del repositorio, agrupadas por ecosistema. If vulnerabilities have been detected in the repository, these are shown at the top of the view for users with access to {% data variables.product.prodname_dependabot_short %} alerts. - -{% note %} - -**Nota:** {% data variables.product.prodname_ghe_server %} no llena la vista de **Dependientes**. - -{% endnote %} - -![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph_server.png) - -{% note %} - -**Nota:** {% data variables.product.prodname_ghe_server %} no llena la vista de **Dependientes**. - -{% endnote %} - -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -Se listará cualquier dependencia directa e indirecta que se especifique en los archivos de bloqueo o de manifiesto del repositorio, agrupadas por ecosistema. Si se detectan vulnerabilidades en el repositorio, estas se mostrarán en la parte superior de la vista para los usuarios con acceso a las alertas de seguridad. - -{% note %} - -**Nota:** {% data variables.product.prodname_ghe_server %} no llena la vista de **Dependientes**. - -{% endnote %} - -![Gráfico de dependencias](/assets/images/help/graphs/dependencies_graph_server.png) - -{% note %} - -**Nota:** {% data variables.product.prodname_ghe_server %} no llena la vista de **Dependientes**. - -{% endnote %} - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -#### Vista de dependientes - -Para los repositorios públicos, la vista de dependientes muestra cómo otros repositorios utilizan este repositorio. Para mostrar únicamente los repositorios que contienen una biblioteca en un administrador de paquetes, da cilc en **CANTIDAD de paquetes** inmediatamente sobre la lista de repositorios dependientes. La cantidad de dependientes es aproximada y podría no siempre empatar con los dependientes listados. - -![Gráfico de dependencias](/assets/images/help/graphs/dependents_graph.png) - -### Habilitar e inhabilitar la gráfica de dependencias para un repositorio privado - -Los administradores del repositorio pueden habilitar o inhabilitar la gráfica de dependencias para los repositorios privados. - -También puedes habilitar o inhabilitar la gráfica de dependencias para todos los repositorios que pertenecen a tu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar la seguridad y la configuración de análisis para tu cuenta de usuario" o la sección](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)"[Administrar la configuración de seguridad y análisis para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)". - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-security-and-analysis %} -4. Lee los mensajes sobre el otorgar acceso de solo lectura a {% data variables.product.product_name %} para los datos del repositorio para así habilitar la gráfica de dependencias, posteriormente, da clic en **Habilitar** junto a "Gráfica de Dependencias". ![Botón de "Habilitar" para la gráfica de dependencias](/assets/images/help/repository/dependency-graph-enable-button.png) - -Puedes inhabilitar la gráfica de dependencias en cualquier momento si das clic en **Inhabilitar** junto a "Gráfica de Dependencias" en la pestaña de Seguridad & análisis. -{% endif %} - -### Solución de problemas del gráfico de dependencias - -Si tu gráfica de dependencias está vacía, puede que haya un problema con el archivo que contiene tus dependencias. Revisa el archivo para asegurarte de que tiene el formato correcto para el tipo de archivo. - -{% if currentVersion == "free-pro-team@latest" %} -Si este archivo tiene el formato correcto, entonces revisa su tamaño. La gráfica de dependencias ignora los archivos individuales de manifiesto y de bloqueo que pesen más de 0.5 Mb, a menos de que seas un usuario de {% data variables.product.prodname_enterprise %}. Este procesa hasta 20 archivos de manifiesto o de bloqueo por repositorio predeterminadamente, así que puedes dividir las dependencias en archivos más pequeños en los subdirectorios del repositorio.{% endif %} - -Si un archivo de manifiesto o de bloqueo no se procesa, sus dependencias se omiten de la gráfica de dependencias y no podrán verificar si hay dependencias vulnerables. - -### Leer más - -- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% if currentVersion == "free-pro-team@latest" %} -- "[Viewing insights for your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization)" -- "[Ver y actualizar las dependencias vulnerables en tu repositorio](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" -- "[Entender cómo {% data variables.product.product_name %} utiliza y protege tus datos](/github/understanding-how-github-uses-and-protects-your-data)" -{% endif %} diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/index.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/index.md deleted file mode 100644 index b5edccbfac..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Entender las conexiones entre repositorios -intro: 'Puedes entender mejor las conexiones que existen entre repositorios viendo la red de un repositorio{% if currentVersion == "free-pro-team@latest" %}, los proyectos que dependen del repositorio{% endif %} y sus bifurcaciones.' -redirect_from: - - /articles/understanding-connections-between-repositories -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories -children: - - /viewing-a-repositorys-network - - /listing-the-forks-of-a-repository - - /viewing-the-dependencies-of-a-repository - - /about-the-dependency-graph - - /exploring-the-dependencies-of-a-repository ---- - diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/listing-the-forks-of-a-repository.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/listing-the-forks-of-a-repository.md deleted file mode 100644 index 46635371c0..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/listing-the-forks-of-a-repository.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Detallar las bifurcaciones de un repositorio -intro: El Gráfico de miembros muestra todas las bifurcaciones de un repositorio. -redirect_from: - - /articles/listing-the-forks-of-a-repository - - /github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -Las bifurcaciones se detallan alfabéticamente por el nombre de usuario de la persona que bifurcó el repositorio. Puedes hacer clic en el nombre de usuario para ser redirigido a la página de perfil del usuario {% data variables.product.product_name %} o hacer clic en el nombre de la bifurcación para ser redirigido a la bifurcación específica del repositorio. - -{% if currentVersion == "free-pro-team@latest" %} - -![Gráfico de miembros del repositorio](/assets/images/help/graphs/repo_forks_graph_dotcom.png) - -{% else %} - -![Gráfico de miembros del repositorio](/assets/images/help/graphs/repo_members_graph.png) - -{% endif %} - -### Acceder al Gráfico de miembros - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -3. En la barra lateral izquierda, haz clic en **Forks** (Bifurcaciones). ![Pestaña Forks (Bifurcaciones)](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) diff --git a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/viewing-a-repositorys-network.md b/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/viewing-a-repositorys-network.md deleted file mode 100644 index fdbc54c182..0000000000 --- a/translations/es-XL/content/github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/viewing-a-repositorys-network.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Ver la red de un repositorio -intro: 'El gráfico de red muestra el historial de la rama de la red del repositorio completa, incluidas las ramas del repositorio raíz y las ramas de las bifurcaciones que contienen confirmaciones únicas de la red.' -product: '{% data reusables.gated-features.repository-insights %}' -redirect_from: - - /articles/viewing-a-repository-s-network - - /articles/viewing-a-repositorys-network - - /github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network -versions: - free-pro-team: '*' - enterprise-server: '*' - github-ae: '*' -topics: - - Repositories ---- -![Gráfico de red del repositorio](/assets/images/help/graphs/repo_network_graph.png) - -{% tip %} - -**Sugerencia:** para ver ramas antiguas, haz clic y arrastra dentro del gráfico. - -{% endtip %} - -### Acceder al gráfico de la red - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -3. En la barra lateral izquierda, haz clic en **Network (Red)**. ![Pestaña de red](/assets/images/help/graphs/network_tab.png) diff --git a/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md deleted file mode 100644 index 09640496f8..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Acerca de los dominios personalizados y las Páginas de GitHub -intro: '{% data variables.product.prodname_pages %} respalda el uso de dominios personalizados o el cambio la raíz de la URL del sitio desde el valor predeterminado, como `octocat.github.io`, para cualquier dominio que posea.' -redirect_from: - - /articles/about-custom-domains-for-github-pages-sites/ - - /articles/about-supported-custom-domains/ - - /articles/custom-domain-redirects-for-your-github-pages-site/ - - /articles/about-custom-domains-and-github-pages - - /github/working-with-github-pages/about-custom-domains-and-github-pages -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' ---- -### Dominios personalizados compatibles - -{% data variables.product.prodname_pages %} trabaja con dos tipos de dominios: subdominios y dominios apex. Para conocer un lista de los dominios personalizados compatibles, consulta "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)". - -| Tipo de dominio personalizado compatible | Ejemplo | -| ---------------------------------------- | ------------------ | -| Subdominio `www` | `www.example.com` | -| Subdominio personalizado | `blog.example.com` | -| Dominio apex | `example.com` | - -Puedes configurar uno o ambos tipos de dominios personalizados para tu sitio. Recomendamos siempre usar un subdominio `www`, incluso si también usas un dominio apex. Para obtener más información, consulta "[Usar un dominio apex para tu sitio {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)". - -Después de que configuras un dominio personalizado para un usuario o sitio de organización, el dominio personalizado reemplazará a la porción de `.github.io` o `.github.io` de la URL para cualquier sitio de proyecto que pertenezca a la cuenta que no haya configurado un dominio personalizado. Por ejemplo, si el dominio personalizado para tu sitio de usuario es `www.octocat.com`, y tienes un sitio de proyecto sin un dominio personalizado configurado que se publica desde un repositorio denominado `octo-project`, el sitio {% data variables.product.prodname_pages %} para ese repositorio estará disponible en `www.octocat.com/octo-project`. - -### Uso de un subdominio para tu sitio {% data variables.product.prodname_pages %} - -Un subdominio es la parte de una URL antes del dominio raíz. Puedes configurar tu subdominio como `www` o como una sección distinta de tu sitio, como `blog.example.com`. - -Los subdominios se configuran con un registro `CNAME` a través de su proveedor DNS. 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#configuring-a-subdomain)". - -#### Subdominios `www` - -Un subdominio `www` es el tipo de subdominio más usado comúnmente. Por ejemplo, `www.example.com` incluue un subdominio `www`. - -Los subdominios `www` son el tipo de dominio personalizado m ás estable porque los subdominios `www` no están afectados por los cambios en las direcciones IP de los servidores de {% data variables.product.product_name %}. Tu sitio también se cargará más rápido porque la protección del ataque de denegación de servicio (DoS) puede implementarse de forma más eficiente. - -#### Subdominios personalizados - -Un subdominio personalizado es un tipo de subdominio que no usa el subdominio `www` estándar. Los subdominios personalizados se utilizan principalmente cuando se necesitan dos secciones distintas de su sitio. Por ejemplo, puedes crear un sitio llamado `blog.example.com` y personalizar esa sección independientemente de `www.example.com`. - -### Uso de un dominio apex para tu sitio {% data variables.product.prodname_pages %} - -Un dominio apex es un dominio personalizado que no contiene un subdominio, como `ejemplo.com`. Los dominios apex también son conocidos como dominios apex base, vacíos, desnudos, o de zona. - -Un dominio apex está configurado con un registro `A`, `ALIAS` o `ANAME` a través de su proveedor DNS. 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#configuring-an-apex-domain)". - -{% data reusables.pages.www-and-apex-domain-recommendation %} - -### Actualizar dominios personalizados cuando tu sitio de {% data variables.product.prodname_pages %} está inhabilitado - -Si tu sitio {% data variables.product.prodname_pages %} no está habilitado pero tiene configurado un dominio personalizado, inmediatamente deberías actualizar o eliminar tus registros de DNS para evitar el riesgo de una adquisición de dominio. La configuración de tu dominio personalizado con tu proveedor DNS mientras tu sitio está inhabilitado, podría hacer que alguien más aloje un sitio en un o de tus subdominios. 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)". - -Existen algunos motivos por los que tu sitio pueda estar inhabilitado automáticamente. - -- Si bajaste de categoría de {% data variables.product.prodname_pro %} a {% data variables.product.prodname_free_user %}, todos los sitios de {% data variables.product.prodname_pages %} que se publicaron actualmente desde repositorios privados en tu cuenta quedarán sin publicar. Para obtener más información, consulta "[Bajar de categoría tu plan de facturación de {% data variables.product.prodname_dotcom %}](/articles/downgrading-your-github-billing-plan)". -- Si transfieres a un repositorio privado a una cuenta personal que está usando {% data variables.product.prodname_free_user %}, el repositorio perderá acceso a la función de {% data variables.product.prodname_pages %}, y el sitio de {% data variables.product.prodname_pages %} actualmente publicado, quedará sin publicar. Para obtener más información, consulta "[Transferir un repositorio](/articles/transferring-a-repository). - -### Leer más - -- "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/index.md deleted file mode 100644 index 7fe61731ec..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Configurar un dominio personalizado para tu sitio de Páginas de GitHub -intro: 'Puedes personalizar el nombre de dominio de tu sitio de {% data variables.product.prodname_pages %}.' -redirect_from: - - /articles/tips-for-configuring-an-a-record-with-your-dns-provider/ - - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site/ - - /articles/configuring-an-a-record-with-your-dns-provider/ - - /articles/using-a-custom-domain-with-github-pages/ - - /articles/tips-for-configuring-a-cname-record/ - - /articles/setting-up-a-custom-domain-with-pages/ - - /articles/setting-up-a-custom-domain-with-github-pages/ - - /articles/configuring-a-custom-domain-for-your-github-pages-site -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' -children: - - /about-custom-domains-and-github-pages - - /managing-a-custom-domain-for-your-github-pages-site - - /troubleshooting-custom-domains-and-github-pages ---- - diff --git a/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md deleted file mode 100644 index dcad2fd4de..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -title: Configurar un dominio personalizado para tu sitio de Páginas de GitHub -intro: 'Puedes configurar o actualizar determinados registros DNS y las configuraciones de tu repositorio para que apunten el dominio predeterminado de tu sitio de {% data variables.product.prodname_pages %} a un dominio personalizado.' -redirect_from: - - /articles/quick-start-setting-up-a-custom-domain/ - - /articles/setting-up-an-apex-domain/ - - /articles/setting-up-a-www-subdomain/ - - /articles/setting-up-a-custom-domain/ - - /articles/setting-up-an-apex-domain-and-www-subdomain/ - - /articles/adding-a-cname-file-to-your-repository/ - - /articles/setting-up-your-pages-site-repository/ - - /articles/managing-a-custom-domain-for-your-github-pages-site - - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' ---- -Las personas con permisos de administración para un repositorio pueden configurar un dominio personalizado para un sitio de {% data variables.product.prodname_pages %}. - -### Acerca de la configuración de dominios personalizados - -Asegúrate de agregar tu dominio personalizado al sitio de {% data variables.product.prodname_pages %} antes de configurar el dominio personalizado con tu proveedor DNS. Configurar tu dominio personalizado con tu proveedor DNS sin agregar tu dominio personalizado a {% data variables.product.product_name %} podría dar como resultado que alguien aloje un sitio en uno de tus subdominios. - -{% windows %} - -El comando `dig`, que se puede usar para verificar la correcta configuración de los registros DNS, no está incluido en Windows. Antes de poder verificar que tus registros DNS estén configurados correctamente, debes instalar [BIND](https://www.isc.org/bind/). - -{% endwindows %} - -{% note %} - -**Nota:** Los cambios DNS pueden tardar hasta 24 horas en propagarse. - -{% endnote %} - -### Configurar un subdominio - -Para configurar un `www` o un subdominio personalizado, como `www.example.com` o `blog.example.com`, debes crear un archivo _CNAME_ en el repositorio de tu sitio y configurar un registro `CNAME` con tu proveedor DNS. - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.pages.save-custom-domain %} -5. Desplázate hasta tu proveedor DNS y crea un registro `CNAME` que apunte tu subdominio al dominio predeterminado de tu sitio. Por ejemplo, si quieres usar el subdominio `www.example.com` para tu sitio de usuario, crea un registro `CNAME` que apunte `www.example.com` a `.github.io`. If you want to use the subdomain `www.anotherexample.com` for your organization site, create a `CNAME` record that points `www.anotherexample.com` to `.github.io`. The `CNAME` file should always point to `.github.io` or `.github.io`, excluding the repository name. {% data reusables.pages.contact-dns-provider %}{% data reusables.pages.default-domain-information %} -{% data reusables.command_line.open_the_multi_os_terminal %} -6. Para confirmar que tu registro DNS esté configurado correctamente, usa el comando `dig` reemplazando _WW.EXAMPLE.COM_ por tu subdominio. -```shell - $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd - > ;WWW.EXAMPLE.COM. IN A - > WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io. - > YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER . - > GITHUB-PAGES-SERVER . 22 IN A 192.0.2.1 -``` -{% data reusables.pages.build-locally-download-cname %} -{% data reusables.pages.enforce-https-custom-domain %} - -### Configurar un dominio apex - -Para configurar un dominio apex, como `example.com`, debes configurar un archivo _CNAME_ en tu repositorio de {% data variables.product.prodname_pages %} y un registro `ALIAS`, `ANAME` o `A` con tu proveedor DNS. - -{% data reusables.pages.www-and-apex-domain-recommendation %} - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.pages.save-custom-domain %} -5. Desplázate hasta tu proveedor DNS y crea un registro `ALIAS`, `ANAME` o `A`. {% 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 un registro `A`, apunta tu dominio apex a las direcciones IP para {% data variables.product.prodname_pages %}. - ```shell - 185.199.108.153 - 185.199.109.153 - 185.199.110.153 - 185.199.111.153 - ``` -{% 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. - ```shell - $ dig EXAMPLE.COM +noall +answer - > EXAMPLE.COM 3600 IN A 185.199.108.153 - > EXAMPLE.COM 3600 IN A 185.199.109.153 - > EXAMPLE.COM 3600 IN A 185.199.110.153 - > EXAMPLE.COM 3600 IN A 185.199.111.153 - ``` -{% data reusables.pages.build-locally-download-cname %} -{% data reusables.pages.enforce-https-custom-domain %} - -### Leer más - -- "[Solución de problemas de dominios personalizados y {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)" diff --git a/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md deleted file mode 100644 index 43fc660bb7..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Solucionar problemas de dominios personalizados y Páginas de GitHub -intro: 'Puedes buscar errores comunes para resolver los problemas que existan con los dominios personalizados o HTTPS para tu sitio de {% data variables.product.prodname_pages %}.' -redirect_from: - - /articles/my-custom-domain-isn-t-working/ - - /articles/custom-domain-isn-t-working/ - - /articles/troubleshooting-custom-domains/ - - /articles/troubleshooting-custom-domains-and-github-pages - - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' ---- -### Errores _CNAME_ - -Los dominios personalizados se almacenan en un archivo _CNAME_ en la raíz de tu fuente de publicación. Puedes agregar o actualizar este archivo a través de la configuración del repositorio o manualmente. 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)". - -Para que tu sitio se represente en el dominio correcto, asegúrate de que el archivo _CNAME_ aún exista en el repositorio. Por ejemplo, muchos generadores de sitios estáticos realizan empujes forzados a tu repositorio, que pueden sobrescribir el archivo _CNAME_ que se agregó a tu repositorio cuando configuraste tu dominio personalizado. Si compilas tu sitio localmente y subes los archivos generados a {% data variables.product.product_name %}, asegúrate de extraer primero la confirmación que agregó el archivo _CNAME_ a tu repositorio local. De este modo, el archivo se incluirá en la compilación. - -Luego, asegúrate de que el archivo _CNAME_ tenga el formato correcto. - -- El nombre de archivo _CNAME_ debe estar todo en mayúsculas. -- El archivo _CNAME_ puede contener solo un dominio. Para apuntar múltiples dominios a tu sitio, debes configurar un redireccionamiento a través de tu proveedor DNS. -- La entrada _CNAME_ debe ser el dominio solo. Por ejemplo, `www.example.com`,`blog.example.com` o `example.com`. -- La entrada _CNAME_ solo se puede usar una vez en {% data variables.product.product_name %}. Por ejemplo, si el archivo _CNAME_ de otro repositorio contiene `example.com`, no puedes usar `example.com` en el archivo _CNAME_ para tu repositorio. - -### Error de configuración DNS - -Si tienes problemas para apuntar el dominio predeterminado para tu sitio a tu dominio personalizado, contáctate con tu proveedor DNS. - -También puedes probar si los registros DNS de tu dominio personalizado están configurados correctamente. 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)". - -### Nombres de dominios personalizados que no son compatibles - -Si tu dominio personalizado no es compatible, puede que debas cambiar tu dominio a un dominio compatible. También te puedes contactar con tu proveedor DNS para ver si ofrece servicios de reenvío para los nombres de dominio. - -Asegúrate de que en tu sitio no ocurra lo siguiente: -- Uso de más de un dominio apex. Por ejemplo, `example.com` y `anotherexample.com`. -- Uso de más de un subdominio `www`. Por ejemplo, `www.example.com` y `www.anotherexample.com`. -- Uso de un dominio apex y de un subdominio personalizado. Por ejemplo, `example.com` y `docs.example.com`. - -{% warning %} - -**Advertencia:** Es altamente recomendable no utilizar registros DNS comodines, como `*.example.com`. Un registro DNS comodín le permitirá a cualquiera que aloje un sitio {% data variables.product.prodname_pages %} en uno de tus subdominios. - -{% endwarning %} - -Para obtener una lista de dominios personalizados que son compatibles, consulta "[Acerca de los dominios personalizados y de las {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)". - -### Errores HTTPS - -A los sitios {% data variables.product.prodname_pages %} que utilizan dominios personalizados que no están configurados de manera correcta con _CNAME_, `ALIAS`, `ANAME` o registros DNS `A` se puede acceder por HTTPS. Para obtener más información, consulta "[Asegurar tu sitio de {% data variables.product.prodname_pages %} con HTTPS](/articles/securing-your-github-pages-site-with-https)". - -Puede tardar hasta una hora que tu sitio se vuelva disponible a través de HTTPS una vez que configures tu dominio personalizado. Después de actualizar los ajustes DNS existentes, puede que debas eliminar y volver a agregar tu dominio personalizado a tu repositorio del sitio para activar el proceso de habilitación HTTPS. 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)". - -Si estás usando registros de Autorización de la Autoridad de Certificación (CAA), debe existir al menos un registro CAA con el valor `letsencrypt.org` para que tu sitio sea accesible a través de HTTPS. Para obtener más información, consulta "[Autorización de la Autoridad de Certificado (CAA)](https://letsencrypt.org/docs/caa/)" en la documentación de Let's Encrypt. - -### Formato de URL en Linux - -Si la URL de tu sitio contiene un nombre de usuario o nombre de organización que comienza o termina con un guion, o que contiene guiones consecutivos, las personas que naveguen con Linux recibirán un error del servidor cuando traten de visitar tu sitio. Para corregir esto, cambia tu nombre de usuario de {% data variables.product.product_name %} y elimina cualquier caracter que no sea alfanumérico. Para obtener más información, consulta [Cambiar tu {% data variables.product.prodname_dotcom %} nombre de usuario](/articles/changing-your-github-username/)" - -### Caché del navegador - -Si has cambiado o eliminado recientemente tu dominio personalizado y no puedes acceder a la URL nueva en tu navegador, puede que debas limpiar el caché de tu navegador para llegar a la URL nueva. Para obtener más información acerca de limpiar tu caché, consulta la documentación de tu navegador. diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/about-github-pages.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/about-github-pages.md deleted file mode 100644 index 6769a34bad..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/about-github-pages.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: Acerca de GitHub Pages -intro: 'Puedes usar {% data variables.product.prodname_pages %} para albergar un sitio web sobre ti mismo, tu organización o tu proyecto directamente desde un repositorio {% data variables.product.product_name %}.' -redirect_from: - - /articles/what-are-github-pages/ - - /articles/what-is-github-pages/ - - /articles/user-organization-and-project-pages/ - - /articles/using-a-static-site-generator-other-than-jekyll/ - - /articles/mime-types-on-github-pages/ - - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio/ - - /articles/about-github-pages - - /github/working-with-github-pages/about-github-pages -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de {% data variables.product.prodname_pages %} - -{% data variables.product.prodname_pages %} es un servicio de alojamiento de sitio estático que toma archivos HTML, CSS y JavaScript directamente desde un repositorio en {% data variables.product.product_name %}, opcionalmente ejecuta los archivos a través de un proceso de complilación y publica un sitio web. Puedes ver ejemplos de sitios de {% data variables.product.prodname_pages %} en la recopilación de ejemplos de [{% data variables.product.prodname_pages %}](https://github.com/collections/github-pages-examples). - -{% if currentVersion == "free-pro-team@latest" %} -Puedes alojar tu sitio en el dominio `github.io` de {% data variables.product.prodname_dotcom %} o en tu propio dominio personalizado. Para obtener más información, consulta "[Usar un dominio personalizado con {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)". -{% endif %} - -Para empezar, vea "[Creando un sitio {% data variables.product.prodname_pages %}](/articles/creating-a-github-pages-site)." - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Disabling publication of {% data variables.product.prodname_pages %} sites for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization)." -{% endif %} - -### Tipos de sitios {% data variables.product.prodname_pages %} - -Existen tres tipos básicos de {% data variables.product.prodname_pages %} sitios: de proyecto, de usuario y de la organización. Los sitios de proyecto están conectados coon un proyecto específico alojado en {% data variables.product.product_name %}, como una biblioteca JavaScript o una colección de recetas. Los sitios de usuario y organización están conectados a una cuenta específica de {% data variables.product.product_name %}. - -Para publicar un sitio de usuario debes crear un repositorio que pertenezca a tu cuenta de usuario y se llame {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. Para publicar un sitio de organización debes crear un repositorio que pertenezca a una organización y que se llame {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. {% if currentVersion == "free-pro-team@latest" %}A menos que esté usando un dominio personalizado, los sitios de usuario y de organización están disponibles en `http(s)://.github.io` o `http(s)://.github.io`.{% endif %} - -Los archivos fuente para un sitio de proyecto se almacenan en el mismo repositorio que su proyecto. {% if currentVersion == "free-pro-team@latest" %}A menos que esté usando un dominio prsonalizado, los sitios del proyecto están disponibles en `http(s)://.github.io/` o `http(s)://.github.io/`.{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -Para obtener más información sobre cómo los dominios personalizados afectan a la URL de tu sitio, consulta "[Acerca de los dominios personalizados y {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)". -{% endif %} - -Solo puedes crear un sitio de usuario u organización para cada cuenta de {% data variables.product.product_name %}. Los sitios de proyectos, ya sean propiedad de una cuenta de organización de de usuario, son ilimitados. - -{% if currentVersion != "free-pro-team@latest" %} -La URL donde tu sitio está disponible depende de si el aislamiento del subdominio está habilitado para {% data variables.product.product_location %}. - -| Tipo de sitio | Aislamiento de subdominio habilitado | Aislamiento de subdominio inhabilitado | -| ------------- | ------------------------------------ | -------------------------------------- | -| | | | - Usuario | - -`http(s)://pages.///` | `http(s):///pages///` | Organization | `http(s)://pages.///` | `http(s):///pages///` | Sitio del proyecto que pertenece a la cuenta del usuario | `http(s)://pages.///` | `http(s):///pages///` Sitio del proyecto que pertenece a la cuenta de la organización | `http(s)://pages.///` | `http(s):///pages///` - -Para obtener más información, consulta "[Habilitar el aislamiento del subdominio](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" o comunícate con el administrador del sitio. -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -{% note %} - -**Nota:** Los repositorios que usan el esquema de nombres `.github.com` heredado seguirán publicándose, pero los visitantes serán redirigidos desde `http(s)://.github.com` hasta `http(s)://.github.io`. Si existen tanto un repositorio `.github.com` como `.github.io`, solo el repositorio `.github.io` será publicado. - -{% endnote %} -{% endif %} - -### Publicar fuentes para sitios {% data variables.product.prodname_pages %} - -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 reusables.pages.private_pages_are_public_warning %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - -Si la fuente de publicación predeterminada existe en tu repositorio, {% data variables.product.prodname_pages %} publicará automáticamente un sitio desde esta fuente. La fuente de publicación predeterminada para los sitios de usuario y de organización es la raíz de la rama predeterminada para el repositorio. La fuente de publicación predeterminada para los sitios de proyecto es la raíz de la rama `gh-pages`. - -Si quieres mantener los archivos fuente para tu sitio en una ubicación distinta, puedes cambiar la fuente de publicación para tu sitio. Puedes publicar tu sitio desde cualquier rama en el repositorio, ya sea desde la raíz del repositorio en esa rama, `/`, o desde la carpeta de `/docs` en ella. Para obtener más información, consulta "[Configurar una fuente de publicación para tu sitio {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". - -Si eliges la carpeta de `/docs` o cualquier rama como tu fuente de publicación, {% data variables.product.prodname_pages %} leerá todo para publicar tu sitio{% if currentVersion == "free-pro-team@latest" %}, incluyendo el archivo _CNAME_,{% endif %} desde la carpeta de `/docs`.{% if currentVersion == "free-pro-team@latest" %} Por ejemplo, cuando editas tu dominio personalizado a través de la configuración de {% data variables.product.prodname_pages %}, dicho dominio escribirá en `/docs/CNAME`. Para más información sobre los archivos _CNAME_, consulta "[Administrar un dominio personalizado para tu sitio {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} - -{% else %} - -La fuente de publicación predeterminada para los sitios de usuario y organización es la rama `principal`. Si el repositorio para tu sitio de usuario u organización tiene una rama `principal`, tu sitio se publicará automáticamente desde esa rama. No puedes elegir una fuente de publicación diferente para sitios de usuario u organización. - -La fuente de publicación predeterminada para un sitio de proyecto es la rama `gh-pages`. Si el repositorio para tu sitio de proyecto tiene una rama `gh-pages`, tu sitio se publicará automáticamente desde esa rama. - -Los sitios del proyecto también pueden publicarse desde la rama `principal` o una carpeta `/docs` en la rama `master`. Para publicar tu sitio desde una de estas fuentes, debes configurar una fuente de publicación diferente. Para obtener más información, consulta "[Configurar una fuente de publicación para tu sitio {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". - - Si eliges la carpeta `/docs` de la rama `principal` como tu fuente de publicación, {% data variables.product.prodname_pages %} leerá todo para publicar tu sitio{% if currentVersion == "free-pro-team@latest" %}, incluido el archivo _CNAME_,{% endif %} desde la carpeta `/docs`.{% if currentVersion == "free-pro-team@latest" %} Por ejemplo, cuando editas tu dominio personalizado a través de los parámetros {% data variables.product.prodname_pages %}, el dominio personalizado se escribirá en `/docs/CNAME`. Para más información sobre los archivos _CNAME_, consulta "[Administrar un dominio personalizado para tu sitio {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} - - No puedes publicar tu sitio de proyecto desde ninguna otra rama, aún si la rama predeterminada es diferente a `master` o `gh-pages`. - -{% endif %} - -### Generadores de sitios estáticos - -{% data variables.product.prodname_pages %} publica cualquier archivo estático que subas a tu repositorio. Puedes crear tus propios archivos estáticos o usar un generador de sitios estáticos para que desarrolle tu sitio. También puedes personalizar tu propio proceso de compilación de forma local o en otro servidor. Recomendamos Jekyll, un generador de sitio estático con soporte integrado para {% data variables.product.prodname_pages %} y un proceso de compilación simplificado. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." - -{% data variables.product.prodname_pages %} usará Jekyll para compilar tu sitio por defecto. Si deseas usar un generador de sitio estático diferente a Jekyll, desactiva el proceso de compilación de Jekyll creando un archivo vacío denominado `en la raíz de tu fuente de publicación, luego seguir las instrucciones del generador de sitio estático para desarrollar tu sitio localmente.

    - -

    {% data variables.product.prodname_pages %} no soporta idiomas del lado del servidor como PHP, Ruby o Python.

    - -

    Guías para usar {% data variables.product.prodname_pages %}

    - -

    {% if currentVersion == "free-pro-team@latest" %}

    - -
      -
    • los sitios {% data variables.product.prodname_pages %} creados después del 15 de junio de 2016 y utilizando dominios github.io` se brindan a través de HTTPS. Si creaste tu sitio antes del 15 de junio de 2016, puedes habilitar el soporte HTTPS para el tráfico hasta tu sitio. Para obtener más información, consulta "[Asegurar tu {% data variables.product.prodname_pages %} con HTTPS](/articles/securing-your-github-pages-site-with-https)".
      • -- {% data reusables.pages.no_sensitive_data_pages %} -- Tu uso de {% data variables.product.prodname_pages %} está sujeto a los [Términos del servicio de GitHub](/articles/github-terms-of-service/), incluida la prohibición de reventa.
    - -#### Límites de uso -{% endif %} -los sitios {% data variables.product.prodname_pages %} están sujetos a los siguientes límites de uso: - - - Los repositorios de fuente de {% data variables.product.prodname_pages %} tienen un límite recomendado de 1 GB.{% if currentVersion == "free-pro-team@latest" %} Para más información, consulta "[¿Cuál es la cuota de mi disco?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} - - Los sitios de {% data variables.product.prodname_pages %} publicados no pueden ser mayores a 1 GB. -{% if currentVersion == "free-pro-team@latest" %} - - Los sitios de {% data variables.product.prodname_pages %} tienen un *soft* límite de ancho de banda de 100GB por mes. - - Los sitios de {% data variables.product.prodname_pages %} tienen un *soft* límite de 10 construcciones por hora. - -Si tu sitio excede estas cuotas de uso, es posible que no podamos prestar servicio a tu sitio, o puedes recibir un correo electrónico formal de {% data variables.contact.contact_support %} sugiriendo estrategias para reducir el impacto de tu sitio en nuestros servidores, lo que incluye poner una red de distribución de contenido de un tercero (CDN) al frente de tu sitio, usar las otras características de {% data variables.product.prodname_dotcom %}, como lanzamientos, o mudar a un servicio de alojamiento diferente que pueda satisfacer mejor tus necesidades. - -#### Usos prohibidos - -{% data variables.product.prodname_pages %} no pretende ser un servicio de alojamiento web gratuito ni permite que se use de ese modo para realizar tus negocios en línea, un sitio de comercio electrónico, o cualquier otro sitio web que esté principalmente dirigido a facilitar las operaciones comerciales o brindar software comercial como un servicio (SaaS). - -Además, los sitios de {% data variables.product.prodname_pages %} deben evitar: - - - el contenido o la actividad que sea ilegal o esté prohibida por nuestros [Términos de servicio](/articles/github-terms-of-service/) o [Pautas de la comunidad](/articles/github-community-guidelines/) - - el contenido o la actividad violentas o amenazadoras - - la actividad masiva automatizada excesiva (por ejemplo, envío de spam) - - la actividad que comprometa a los usuarios o los servicios de GitHub - - los esquemas del tipo 'hágase rico rápidamente' - - el contenido sexualmente obsceno - - el contenido que falsea de manera fraudulenta tu identidad o el propósito del sitio - -Si tienes consultas acerca de si tu uso o tu intención de uso corresponde a alguna de estas categorías, comunícate con {% data variables.contact.contact_support %}. -{% endif %} - -### Tipos MIME en {% data variables.product.prodname_pages %} - -Un tipo MIME es un encabezado que un servidor envía a un navegador, proporcionando información sobre la naturaleza y el formato de los archivos que solicitó el navegador. {% data variables.product.prodname_pages %} soporta más de 750 tipos MIME entre las miles de extensiones de archivo. La lista de los tipos de MIME compatibles se genera desde el [mime-db project](https://github.com/jshttp/mime-db). - -Si bien no puedes especificar los tipos de MIME personalizados en una base por perfil o por repositorio, puedes agregar o modificar los tipos de MIME para usar en {% data variables.product.prodname_pages %}. Para obtener más información, consulta [los lineamientos de contribución de mime-db](https://github.com/jshttp/mime-db#adding-custom-media-types). - -### Leer más - -- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) en {% data variables.product.prodname_learning %} -- "[{% data variables.product.prodname_pages %}](/v3/repos/pages)" diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md deleted file mode 100644 index 2431e6da52..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Agregar un tema a tu sitio de Páginas de GitHub con el selector de tema -intro: 'Puedes añadir un tema a tu sitio de {% data variables.product.prodname_pages %} para personalizar la apariencia de tu sitio.' -redirect_from: - - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser/ - - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser/ - - /articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser - - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' ---- -Las personas con permisos de administración para un repositorio pueden usar el selector de temas para agregar un tema al sitio de {% data variables.product.prodname_pages %}. - -### Acerca del selector de temas - -El selector de temas agrega un tema de Jekyll a tu repositorio. Para obtener más información acerca de Jekyll, consulta "[Acerca de las {% data variables.product.prodname_pages %} y Jekyll](/articles/about-github-pages-and-jekyll)". - -La forma en que funciona el selector de temas depende de si tu repositorio es público o privado. - - Si las {% data variables.product.prodname_pages %} ya están habilitadas para tu repositorio, el selector de temas agregará tu tema a la fuente de publicación actual. - - Si tu repositorio es público y {% data variables.product.prodname_pages %} se encuentra inhabilitado para éste, mediante el selector de temas podrás habilitar {% data variables.product.prodname_pages %} y configurar la rama predeterminada como tu fuente de publicación. - - Si tu repositorio es público, y las {% data variables.product.prodname_pages %} están inhabilitadas para tu repositorio, debes habilitar las {% data variables.product.prodname_pages %} configurando una fuente de publicación antes de poder usar el selector de temas. - -Para obtener más información acerca de las fuentes de publicación, consulta "[Acerca de las {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". - -Si antes agregaste manualmente un tema de Jekyll a tu repositorio, puede que esos archivos se apliquen incluso después de que uses el selector de temas. Para evitar conflictos, elimina todas las carpetas y archivos de temas agregados manualmente antes de usar el selector de temas. Para obtener más información, consulta "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". - -### Agregar un tema con el selector de temas - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Debajo de "{% data variables.product.prodname_pages %}", haz clic en **Choose a theme** (Elegir un tema) o **Change theme** (Cambiar tema). ![Elija un botón del tema](/assets/images/help/pages/choose-a-theme.png) -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) - - Para editar el archivo ahora, consulta "[Editar archivos en tu repositorio](/articles/editing-files-in-your-repository/)". - -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. - -### Leer más - -- [Temas](https://jekyllrb.com/docs/themes/) en el sitio de Jekyll diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md deleted file mode 100644 index 823e971488..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Configurar una fuente de publicación para tu sitio de Páginas de GitHub -intro: 'Si usas la fuente de publicación predeterminada para tu sitio de {% data variables.product.prodname_pages %}, tu sitio se publicará automáticamente. También puedes elegir publicar tu{% if currentVersion ver_lt "enterprise-server@2.23" %} proyecto{% endif %} sitio desde una rama o carpeta diferente.' -redirect_from: - - /articles/configuring-a-publishing-source-for-github-pages/ - - /articles/configuring-a-publishing-source-for-your-github-pages-site - - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site -product: '{% data reusables.gated-features.pages %}' -permissions: 'Las personas con permisos de administrador o de mantenedor para un repositorio pueden configurar una fuente de publicación para un sitio de {% data variables.product.prodname_pages %}.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Para obtener más información acerca de las fuentes de publicación, consulta "[Acerca de las {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". - -### Elegir una fuente de publicación - -Before you configure a publishing source, make sure the branch{% if currentVersion ver_lt "enterprise-server@2.22" %} or folder{% endif %} you want to use as your publishing source already exists in your repository.{% if currentVersion ver_lt "enterprise-server@2.22" %} For example, before you can publish your project site from the `/docs` folder on the `master` branch of your repository, you or a collaborator must create a `/docs` folder on the default `master` branch of your repository.{% endif %} - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.repositories.sidebar-settings %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} -3. Debajo de "{% data variables.product.prodname_pages %}", utiliza el menú desplegable de **Ninguno** o de **Rama** y selecciona una fuente de publicación. ![Menú desplegable para seleccionar una fuente de publicación](/assets/images/help/pages/publishing-source-drop-down.png) -4. Opcionalmente, utiliza el menú desplegable para seleccionar una carpeta para tu fuente de publicación. ![Menú desplegable para seleccionar una carpeta para una fuente de publicación](/assets/images/help/pages/publishing-source-folder-drop-down.png) -5. Haz clic en **Save (Guardar)**. ![Botón para guardar los cambios en la configuración de la fuente de publicación](/assets/images/help/pages/publishing-source-save.png) - {% else %} -3. Debajo de "{% data variables.product.prodname_pages %}", usa el menú desplegable **Source** (Fuente) y selecciona una fuente de publicación. ![Menú desplegable para seleccionar una fuente de publicación](/assets/images/help/pages/publishing-source-drop-down.png) -{% endif %} - -### Solución de problemas de publicación con tu sitio de {% data variables.product.prodname_pages %} - -{% data reusables.pages.admin-must-push %} - -If you choose the `docs` folder on {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}any{% else %}the `master`{% endif %} branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. Para obtener más información, consulta "[Solución de problemas de errores de compilación de Jekyll para los sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)". diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md deleted file mode 100644 index 34d5a3b15e..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Crear una página 404 personalizada para tu sitio de Páginas de GitHub -intro: Puedes mostrar una página personalizada de error 404 cuando se intente acceder a páginas que no existen en tu sitio. -redirect_from: - - /articles/custom-404-pages/ - - /articles/creating-a-custom-404-page-for-your-github-pages-site - - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -{% data reusables.pages.navigate-site-repo %} -{% data reusables.pages.navigate-publishing-source %} -{% data reusables.files.add-file %} -3. En el campo para el nombre de archivo, escribe `404.html` o `404.md`. ![Campo File name (Nombre de archivo)](/assets/images/help/pages/404-file-name.png) -4. Si denominaste tu archivo `404.md`, agrega el siguiente texto preliminar de YAML al comienzo del archivo: - ``` - --- - permalink: /404.html - --- - ``` -5. Debajo del texto preliminar de YAML, si aparece, agrega el contenido que quieras mostrar en tu página 404. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -### Leer más - -- [Texto preliminar](http://jekyllrb.com/docs/frontmatter) en la documentación de Jekyll diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/creating-a-github-pages-site.md deleted file mode 100644 index 8b0bbf26f6..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/creating-a-github-pages-site.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Crear un sitio de Páginas de GitHub -intro: 'Puede crear un sitio de {% data variables.product.prodname_pages %} en un repositorio nuevo o existente.' -redirect_from: - - /articles/creating-project-pages-using-the-command-line/ - - /articles/creating-a-github-pages-site - - /github/working-with-github-pages/creating-a-github-pages-site -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Crear un repositorio para tu sitio - -{% data reusables.pages.new-or-existing-repo %} - -{% data reusables.pages.private_pages_are_public_warning %} - -{% data reusables.repositories.create_new %} -{% data reusables.repositories.owner-drop-down %} -{% data reusables.pages.create-repo-name %} -{% data reusables.repositories.choose-repo-visibility %} -{% data reusables.repositories.initialize-with-readme %} -{% data reusables.repositories.create-repo %} - -### Crear tu sitio - -{% data reusables.pages.must-have-repo-first %} - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.pages.decide-publishing-source %} -3. Si ya existe la fuente de publicación que elegiste, desplázate hasta la fuente de publicación. Si la fuente de publicación que elegiste no existe, crear la fuente de publicación. -4. En la raíz de la fuente de publicación, crea un archivo nuevo denominado `index.md` que contenga el contenido que quieras mostrar en la página principal de tu sitio. -{% data reusables.pages.configure-publishing-source %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.pages.visit-site %} - -{% data reusables.pages.admin-must-push %} - -### Pasos siguientes - -Puedes agregar más páginas a tu sitio creando más archivos nuevos. Cada archivo estará disponible en tu sitio en la misma estructura de directorios que tu fuente de publicación. Por ejemplo, si la fuente de publicación para tu sitio de proyectos es la rama `gh-pages`, y creas un archivo nuevo denominado `/about/contact-us.md` en la rama `gh-pages`, el archivo estará disponible en {% if currentVersion == "free-pro-team@latest" %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.md`. - -También puedes agregar un tema para personalizar la apariencia de tu sitio. Para obtener más información, consulta {% if currentVersion == "free-pro-team@latest" %}"[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con el selector de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}". - -Para personalizar aún más tu sitio, puedes usar Jekyll, un generador de sitio estático con soporte integrado para {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." - -### Leer más - -- "[Solucionar problemas de errores de construcción de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" -- "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository/)" -- "[Crear archivos nuevos](/articles/creating-new-files)" diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/index.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/index.md deleted file mode 100644 index ab7ad8bfa2..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Comenzar con Páginas de GitHub -intro: 'Puedes configurar un sitio básico de {% data variables.product.prodname_pages %} para ti, para tu organización o para tu proyecto.' -redirect_from: - - /categories/github-pages-basics - - /articles/additional-customizations-for-github-pages/ - - /articles/getting-started-with-github-pages -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-github-pages - - /creating-a-github-pages-site - - /adding-a-theme-to-your-github-pages-site-with-the-theme-chooser - - /configuring-a-publishing-source-for-your-github-pages-site - - /creating-a-custom-404-page-for-your-github-pages-site - - /securing-your-github-pages-site-with-https - - /using-submodules-with-github-pages - - /unpublishing-a-github-pages-site ---- - diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md deleted file mode 100644 index 299db9c83e..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Asegurar tu sitio de Páginas de GitHub con HTTPS -intro: 'HTTPS agrega una capa de encriptación que evita que otros se entrometan o manipulen el tráfico en tu sitio. Puedes aplicar HTTPS en tu sitio {% data variables.product.prodname_pages %} para redirigir de forma transparente todas las solicitudes de HTTP a HTTPS.' -product: '{% data reusables.gated-features.pages %}' -redirect_from: - - /articles/securing-your-github-pages-site-with-https - - /github/working-with-github-pages/securing-your-github-pages-site-with-https -versions: - free-pro-team: '*' ---- -Las personas con permisos de administración para un repositorio pueden aplicar HTTPS para un sitio de {% data variables.product.prodname_pages %}. - -### Acerca de HTTPS y de las {% data variables.product.prodname_pages %} - -Todos los sitios {% data variables.product.prodname_pages %}, incluidos los sitios que están correctamente configurados con un dominio personalizado, admiten HTTPS y la aplicación de HTTPS. Para obtener más información acerca de los dominios personalizados, consulta "[Acerca de los dominios personalizados y de las {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" y "[Solución de problemas de los dominios personalizados y de las {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)". - -La aplicación de HTTPS es necesaria para los sitios {% data variables.product.prodname_pages %} utilizando un dominio `github.io` que fueron creados después del 15 de junio de 2016. Si creaste tu sitio antes del 15 de junio de 2016, puedes habilitar de forma manual la aplicación de HTTPS. - -{% data reusables.pages.no_sensitive_data_pages %} - -{% data reusables.pages.private_pages_are_public_warning %} - -### Aplicar HTTPS en tu sitio {% data variables.product.prodname_pages %} - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.repositories.sidebar-settings %} -3. Debajo de "{% data variables.product.prodname_pages %}", selecciona **Enforce HTTPS** (Aplicar HTTPS). ![Aplicar casilla de verificación de HTTPS](/assets/images/help/pages/enforce-https-checkbox.png) - -### Resolver problemas con contenido mixto - -Si habilitas HTTPS para tu sitio de {% data variables.product.prodname_pages %}, pero el HTML de tu sitio sigue referenciando imágenes, CSS o JavaScript a través de HTTP, significa que tu sitio está ofreciendo *contenido mixto*. Ofrecer contenido mixto puede hacer que tu sitio sea menos seguro y generar problemas al cargar activos. - -Para eliminar el contenido mixto de tu sitio, asegúrate de que todos tus activos se ofrezcan mediante HTTPS cambiando `http://` por `https://` en el HTML de tu sitio. - -Normalmente, los activos se encuentran en las siguientes ubicaciones: -- Si tu sitio usa Jekyll, es probable que tus archivos HTML se encuentren en la carpeta de *_layouts*. -- Habitualmente, CSS se encuentra en la sección `` de tu archivo HTML. -- Habitualmente, JavaScript se encuentra en la sección `` o simplemente antes de la etiqueta de cierre ``. -- Las imágenes se suelen encontrar en la sección ``. - -{% tip %} - -**Sugerencia:** Si no puedes encontrar tus activos en los archivos fuente de tu sitio, prueba buscando los archivos fuente de tu sitio para `http` en el editor de texto o en {% data variables.product.product_name %}. - -{% endtip %} - -#### Ejemplos de activos referenciados en un archivo HTML - -| Tipo de activo | HTTP | HTTPS | -|:--------------:|:----------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------------------:| -| CSS | `` | `` | -| JavaScript | `` | `` | -| Image | `Logo` | `Logo` | diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md deleted file mode 100644 index 4cd4d37923..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Anular la publicación de un sitio de Páginas de GitHub -intro: 'Puedes anular la publicación de tu sitio de {% data variables.product.prodname_pages %} para que el sitio deje de estar disponible para {% if currentVersion == "free-pro-team@latest" %}el público{% else %}cualquier persona que use {% data variables.product.product_location %}{% endif %}.' -redirect_from: - - /articles/how-do-i-unpublish-a-project-page/ - - /articles/unpublishing-a-project-page/ - - /articles/unpublishing-a-project-pages-site/ - - /articles/unpublishing-a-user-pages-site/ - - /articles/unpublishing-a-github-pages-site - - /github/working-with-github-pages/unpublishing-a-github-pages-site -product: '{% data reusables.gated-features.pages %}' -permissions: 'Las personas con permisos administrativos en un repositorio pueden anular la publicación de un sitio de {% data variables.product.prodname_pages %}.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Anular la publicación de un sitio de proyecto - -{% data reusables.repositories.navigate-to-repo %} -2. Si existe una rama de `gh-pages` en el repositorio, elimina la rama de `gh-pages`. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)". -3. Si la rama de `gh-pages` fue tu fuente de publicación, -{% if currentVersion == "free-pro-team@latest" %}avanza hasta el paso 6{% else %}ahora tu sitio dejó de estar publicado, y te puedes saltear los pasos restantes{% endif %}. -{% data reusables.repositories.sidebar-settings %} -5. Debajo de "{% data variables.product.prodname_pages %}", usa el menú desplegable **Source** (Fuente) y seleccionar **None** (Ninguno). ![Menú desplegable para seleccionar una fuente de publicación](/assets/images/help/pages/publishing-source-drop-down.png) -{% data reusables.pages.update_your_dns_settings %} - -### Anular la publicación de un sitio de usuario o de organización - -{% data reusables.repositories.navigate-to-repo %} -2. Delete the branch that you're using as a publishing source, or delete the entire repository. Para obtener más información, consulta "[Crear y eliminar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" y "[Eliminar un repositorio](/articles/deleting-a-repository)". -{% data reusables.pages.update_your_dns_settings %} diff --git a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/using-submodules-with-github-pages.md deleted file mode 100644 index 3a23db02c9..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/getting-started-with-github-pages/using-submodules-with-github-pages.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Usar submódulos con las Páginas de GitHub -intro: 'Puedes usar submódulos con las {% data variables.product.prodname_pages %} para incluir otros proyectos en el código de tu sitio.' -redirect_from: - - /articles/using-submodules-with-pages/ - - /articles/using-submodules-with-github-pages - - /github/working-with-github-pages/using-submodules-with-github-pages -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' ---- -Si el repositorio para tu sitio de {% data variables.product.prodname_pages %} contiene submódulos, sus contenidos se extraerán automáticamente cuando se compile tu sitio. - -Solo puedes usar submódulos que apunten a los repositorios públicos, porque el servidor de {% data variables.product.prodname_pages %} no puede acceder a los repositorios privados. - -Utiliza la URL de solo lectura `https://` para tus submódulos, incluidos los submódulos anidados. Puedes hacer este cambio en tu archivo _.gitmodules_. - -### Leer más - -- "[Heramientas Git - Submódulos](https://git-scm.com/book/en/Git-Tools-Submodules)" del libro _Pro Git_ -- "[Solucionar problemas de errores de construcción de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" diff --git a/translations/es-XL/content/github/working-with-github-pages/index.md b/translations/es-XL/content/github/working-with-github-pages/index.md deleted file mode 100644 index 2822d943eb..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/index.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Trabajar con Páginas de GitHub -shortTitle: Páginas de GitHub -intro: 'Puedes crear un sitio web directamente desde un repositorio de {% data variables.product.product_name %}.' -redirect_from: - - /categories/20/articles/ - - /categories/95/articles/ - - /categories/github-pages-features/ - - /pages/ - - /categories/96/articles/ - - /categories/github-pages-troubleshooting/ - - /categories/working-with-github-pages -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /getting-started-with-github-pages - - /setting-up-a-github-pages-site-with-jekyll - - /configuring-a-custom-domain-for-your-github-pages-site ---- -### Índice - - - - - - diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md deleted file mode 100644 index f4b7c28562..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -title: Acerca de las Páginas de GitHub y Jekyll -intro: 'Jekyll es un generador de sitios estáticos con soporte integrado para {% data variables.product.prodname_pages %}.' -redirect_from: - - /articles/about-jekyll-themes-on-github - - /articles/configuring-jekyll - - /articles/configuring-jekyll-plugins - - /articles/using-syntax-highlighting-on-github-pages - - /articles/files-that-start-with-an-underscore-are-missing - - /articles/sitemaps-for-github-pages/ - - /articles/search-engine-optimization-for-github-pages/ - - /articles/repository-metadata-on-github-pages/ - - /articles/atom-rss-feeds-for-github-pages/ - - /articles/redirects-on-github-pages/ - - /articles/emoji-on-github-pages/ - - /articles/mentions-on-github-pages/ - - /articles/using-jekyll-plugins-with-github-pages/ - - /articles/adding-jekyll-plugins-to-a-github-pages-site/ - - /articles/about-github-pages-and-jekyll - - /github/working-with-github-pages/about-github-pages-and-jekyll -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de Jekyll - -Jekill es un generador de sitio estático con soporte incorporado para {% data variables.product.prodname_pages %} y un proceso de construcción simplificado. Jekyll toma los archivos Markdown y HTML y crea un sitio web estático completo en función de la opción de diseño. Jekyll soporta Markdown y Liquid, un lenguaje de plantillas que carga contenido dinámico en tu sitio. Para obtener más información, consulta [Jekyll](https://jekyllrb.com/). - -Jekyll no está oficialmente admitido por Windows. Para obtener más información, consulta "[Jekyll en Windows](http://jekyllrb.com/docs/windows/#installation)" en la documentación de Jekyll. - -Recomandamos usar Jekyll con {% data variables.product.prodname_pages %}. Si lo prefieres, puedes usar otros generadores de sitio estático o personalizar tu propio proceso de compilación localmente o en otro servidor. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)". - -### Configurando Jekyll en tu sitio {% data variables.product.prodname_pages %} - -Puedes configurar la mayoría de los parámetros de Jekyll, como los temas y los plugins del sitio, al editar tu archivo *_config.yml*. Para obtener más información, consulte "[Configuración](https://jekyllrb.com/docs/configuration/)" en la documentación de Jekyll. - -Algunos parámetros de configuración no pueden cambiarse para los sitios {% data variables.product.prodname_pages %} sites. - -``` -lsi: false -safe: true -source: [your repo's top level directory] -incremental: false -highlighter: rouge -gist: - noscript: false -kramdown: - math_engine: mathjax - syntax_highlighter: rouge -``` - -De manera predeterminada, Jekyll no compila archivos o carpetas que: -- están situados en una carpeta denominada `/node_modules` o `/vendor` -- comienza con `_`, `.`, o `#` -- termina con `~` -- están excluidos por el parámetro `exclude` en tu archivo de configuración - -Si deseas que Jekyll procese alguno de estos archivos, puedes usar el parámetro `includes` en tu archivo de configuración. - -### Texto preliminar - -{% data reusables.pages.about-front-matter %} - -Puedes añadir `site.github` a una publicación o página para añadir cualquier metadato de referencias de repositorio a tu sitio. Para obtener más información, consulta "[Usar `site.github`](https://jekyll.github.io/github-metadata/site.github/)" en la documentación de metadatos de Jekyll. - -### Temas - -{% data reusables.pages.add-jekyll-theme %} Para obtenerr más información, consulta "[Temas](https://jekyllrb.com/docs/themes/)" en la documentación de Jekyll. - -{% if currentVersion == "free-pro-team@latest" %} -Puedes agregar un tema soportado a tu sitio en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Temas soportados](https://pages.github.com/themes/)" en el sitio {% data variables.product.prodname_pages %} y "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con el selector de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser)." - -Para usar cualquier otro tema de código abierto de Jekyll en {% data variables.product.prodname_dotcom %}, puedes añadirlo manualmente.{% else %} Puedes añadir el tema a tu sitio manualmente. {% endif %} Para obtener más información, consulta {% if currentVersion == "free-pro-team@latest" %}los "[temas hospedados en {% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) y {% else %}"[Temas compatibles](https://pages.github.com/themes/)" en el sitio de {% data variables.product.prodname_pages %} y {% endif %}"[Añadir un tema a tu sitio de {% data variables.product.prodname_pages %} usando Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". - -Puedes sobrescribir cualquiera de los valores por defecto de tu tema editando los archivos del tema. Para obtener más información, consulta la documentación de tu tema y "[Sobrescribir los valores predeterminados del tema](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" en la documentación de Jekyll. - -### Plugins - -Puedes descargar o crear plugins Jekyll para ampliar la funcionalidad de Jekyll para tu sitio. Por ejemplo, el plugin [jemoji](https://github.com/jekyll/jemoji) te permite usar el emoji con formato {% data variables.product.prodname_dotcom %} en cualquier página de tu sitio del mismo modo que lo harías en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Plugins](https://jekyllrb.com/docs/plugins/)" en la documentación de Jekyll. - -{% data variables.product.prodname_pages %} usa plugins que están habilitados por defecto y no pueden estar inhabilitados: -- [`jekyll-coffeescript`](https://github.com/jekyll/jekyll-coffeescript) -- [`jekyll-default-layout`](https://github.com/benbalter/jekyll-default-layout) -- [`jekyll-gist`](https://github.com/jekyll/jekyll-gist) -- [`jekyll-github-metadata`](https://github.com/jekyll/github-metadata) -- [`jekyll-optional-front-matter`](https://github.com/benbalter/jekyll-optional-front-matter) -- [`jekyll-paginate`](https://github.com/jekyll/jekyll-paginate) -- [`jekyll-readme-index`](https://github.com/benbalter/jekyll-readme-index) -- [`jekyll-titles-from-headings`](https://github.com/benbalter/jekyll-titles-from-headings) -- [`jekyll-relative-links`](https://github.com/benbalter/jekyll-relative-links) - -Puedes habilitar plugins adicionales al agregar la gema del plugin en los ajustes de `plugins` en tu archivo *_config.yml*. Para obtener más información, consulte "[Configuración](https://jekyllrb.com/docs/configuration/)" en la documentación de Jekyll. Para conocer la lista de los plugins soportados, consulta "[Versiones de dependencia](https://pages.github.com/versions/)" en el sitio {% data variables.product.prodname_pages %}. - -Para obtener información de uso de un plugin específico, consulta la documentación del plugin. - -{% tip %} - -**Sugerencia:** Puedes asegurarte de que estás usando la versión más reciente de todos los plugins al mantener actualizada la gema de {% data variables.product.prodname_pages %}. Para obtener más información, consulta "[Comprobar tus páginas de GitHub localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" y "[Versiones de dependencia](https://pages.github.com/versions/)" en el sitio de {% data variables.product.prodname_pages %}. - -{% endtip %} - -{% data variables.product.prodname_pages %} no puede compilar sitios mediante plugins no compatibles. Si deseas usar plugins no compatibles, genera tu sitio localmente y luego sube los archivos estáticos del sitio a {% data variables.product.product_name %}. - -### Resaltado de la sintaxis - -Para facilitar la lectura de tu sitio, los fragmentos de código se resaltan en los sitios de {% data variables.product.prodname_pages %} de la misma manera que se resaltan en {% data variables.product.product_name %}. Para más información sobre como enfatizar sintaxis en {% data variables.product.product_name %}, vea "[Creando y resaltando bloques de código](/articles/creating-and-highlighting-code-blocks)." - -Por defecto, los bloques de código en su sitio serán resaltados por Jekyll. Jekyll utiliza el resaltador de [Rouge](https://github.com/jneen/rouge), compatible con [Pygments](http://pygments.org/). Si especificas Pygments en tu archivo *_config.yml*, el Rouge se utilizará en su lugar. Jekyll no puede usar ningún otro resaltador de sintaxis, y obtendrás una advertencia de compilación de página si especificas otro en tu archivo *_config.yml*. Para más información, vea "[Acerca de los errores de construcción de sitios Jekyll {% data variables.product.prodname_pages %} ](/articles/about-jekyll-build-errors-for-github-pages-sites)." - -Si quieres usar otro resaltador, como `highlight.js`, debes desactivar el resaltador de sintaxis de Jekyll actualizando el archivo de tu proyecto *_config.yml*. - -``` -kramdown: - syntax_highlighter_opts: - disable : true -``` - -Si tu tema no incluye CSS para resaltar la sintaxis, puedes generar la sintaxis de {% data variables.product.prodname_dotcom %} resaltando CSS y añadirlo a tu archivo `style.css` de proyecto. - -```shell -$ rougify style github > style.css -``` - -### Construyendo su sitio localmente - -{% data reusables.pages.test-locally %} diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md deleted file mode 100644 index 16afc048a3..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Acerca de los errores de compilación para sitios de Páginas de GitHub -intro: 'Si Jekyll encuentra un error al compilar tu sitio de {% data variables.product.prodname_pages %} localmente o en {% data variables.product.product_name %}, recibirás un mensaje de error con más información.' -redirect_from: - - /articles/viewing-jekyll-build-error-messages/ - - /articles/generic-jekyll-build-failures/ - - /articles/about-jekyll-build-errors-for-github-pages-sites - - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Acerca de los errores de compilación de Jekyll - -Algunas veces, {% data variables.product.prodname_pages %} no intentará compilar tu sitio después de que subas los cambios a la fuente de publicación de tu sitio.{% if currentVersion == "free-pro-team@latest" %} -- La persona que subió los cambios no ha verificado su dirección de correo electrónico. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/articles/verifying-your-email-address)".{% endif %} -- Estás subiendo con una llave de despliegue. Si deseas automatizar las subidas al repositorio de tu sitio, puedes configurar un usuario de máquina en su lugar. Para obtener más información, consulta la sección "[Administrar las llaves de despliegue](/v3/guides/managing-deploy-keys/#machine-users)". -- Estás usando un servicio CI que no está configurado para compilar tu fuente de publicación. Por ejemplo, Travis CI no compilará la rama `gh-pages` a menos que añadas la rama a una lista de seguridad. Para obtener más información, consulta "[Personalizar la compilación](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches)" en Travis CI o en la documentación del servicio de CI. - -{% note %} - -**Nota:** Es posible que tome hasta 20 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}. - -{% endnote %} - -Si Jekyll intenta compilar tu sitio y encuentra un error, recibirás un mensaje de error de compilación. Hay dos tipos principales de mensajes de error de construcción de Jekyll. -- Un mensaje de "Aviso de compilación de página" significa que la compilación se ha completado correctamente, pero es posible que debas hacer cambios para prevenir problemas futuros. -- Un mensaje "Page build failed" (Falló la construcción de página) significa que no se pudo completar la compilación. Si Jekyll puede detectar el motivo de la falla, verás un mensaje de error descriptivo. - -Para obtener más información sobre cómo resolver errores de compilación, consulta "[Solución de problemas de errores de compilación de Jekyll para los sitios de {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)". - -### Ver mensajes de error de construcción de Jekyll - -Recomendamos probar su sitio localmente, lo que le permite ver mensajes de error de compilación en la línea de comandos, y abordar cualquier fallo de construcción antes de presionar los cambios a {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu sitio de {% data variables.product.prodname_pages %} localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -Cuando creas una solicitud de extracción para actualizar tu fuente de publicación en {% data variables.product.product_name %}, puedes ver los mensajes de error de compilación en la pestaña **Checks** (Comprobaciones) de la solicitud de extracción. Para obtener más información, consulta "[Acerca de las verificaciones de estado ](/articles/about-status-checks)". -{% endif %} - -Cuando subas los cambios a tu fuente de publicación en {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} intentará compilar tu sitio. Si se produce un error durante la compilación, recibirás un corro electrónico en tu dirección principal de correo electrónico. También recibirás correos electrónicos para advertencias de compilación. {% data reusables.pages.build-failure-email-server %} - -Puedes ver errores de compilación (pero no advertencias de compilación) para tu sitio en {% data variables.product.product_name %} en la pestaña **Settings** (Configuración) del repositorio de tu sitio. - -Puedes configurar un servicio externo como [Travis CI](https://travis-ci.org/) para que muestre mensajes de error después de cada confirmación. - -1. Si no lo has hecho, agrega un archivo denominado _Gemfile_ en la raíz de tu fuente de publicación, con el siguiente contenido: - ``` - source `https://rubygems.org` - gem `github-pages` - ``` - -2. Configura el repositorio de tu sitio para el servicio de comprobación que elijas. Por ejemplo, para usar [Travis CI](https://travis-ci.org/), agrega un archivo denominado _.travis.yml_ en la raíz de tu fuente de publicación, con el siguiente contenido: - ``` - language: ruby - rvm: - - 2.3 - script: "bundle exec jekyll build" - ``` -3. Es posible que necesites activar tu repositorio con el servicio de comprobación de terceros. Para obtener más información, consulta la documentación del servicio de comprobación. diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md deleted file mode 100644 index cc7973fdda..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Agregar un tema a tu sitio de Páginas de GitHub con Jekyll -intro: Puedes personalizar tu sitio Jekyll agregando y personalizando un tema. -redirect_from: - - /articles/customizing-css-and-html-in-your-jekyll-theme/ - - /articles/adding-a-jekyll-theme-to-your-github-pages-site/ - - /articles/adding-a-theme-to-your-github-pages-site-using-jekyll - - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Las personas con permisos de escritura para un repositorio pueden agregar un tema a un sitio de {% data variables.product.prodname_pages %} con Jekyll. - -{% data reusables.pages.test-locally %} - -### Agregar un tema - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.pages.navigate-publishing-source %} -2. Navega hasta *_config.yml*. -{% data reusables.repositories.edit-file %} -4. Agrega una nueva línea al archivo para el nombre del tema. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} - - Para usar un tema compatible, e{% else %}{% endif %}scribe `tema: THEME-NAME`, reemplazando _THEME-NAME_ por el nombre del tema, tal como se muestra en el README del repositorio del tema. Para conocer la lista de temas compatibles, consulta "[Temas compatibles](https://pages.github.com/themes/)" en el sitio de {% data variables.product.prodname_pages %}. ![Supported theme in config file](/assets/images/help/pages/add-theme-to-config-file.png){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} - - Para usar cualquier otro tema de Jekyll alojado en {% data variables.product.prodname_dotcom %}, escribe `remote_theme: THEME-NAME`, reemplazando THEME-NAME por el nombre del tema, tal como se muestra en el README del repositorio del tema. ![Unsupported theme in config file](/assets/images/help/pages/add-remote-theme-to-config-file.png){% endif %} -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} - -### Personalizar el CSS de tu tema - -{% data reusables.pages.best-with-supported-themes %} - -{% data reusables.pages.theme-customization-help %} - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.pages.navigate-publishing-source %} -1. Crea un archivo nuevo denominado _/assets/css/style.scss_. -2. Agrega el siguiente contenido en la parte superior del archivo: - ``` - --- - --- - - @import "{{ site.theme }}"; - ``` -3. Agrega cualquier CSS o Sass personalizado que quieras (incluidas importaciones) inmediatamente después de la línea `@import`. - -### Personalizar el diseño HTML de tu tema - -{% data reusables.pages.best-with-supported-themes %} - -{% data reusables.pages.theme-customization-help %} - -1. En {% data variables.product.prodname_dotcom %}, desplázate hasta el repositorio fuente de tu tema. Por ejemplo, el repositorio fuente para Minima es https://github.com/jekyll/minima. -2. En la carpeta *_layouts*, desplázate hasta el archivo _default.html_ de tu tema. -3. Copia los contenidos del archivo. -{% data reusables.pages.navigate-site-repo %} -{% data reusables.pages.navigate-publishing-source %} -6. Crea un archivo denominado *_layouts/default.html*. -7. Pega el contenido del diseño personalizado que copiaste anteriormente. -8. Personaliza el diseño como desees. - -### Leer más - -- "[Crear archivos nuevos](/articles/creating-new-files)" diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md deleted file mode 100644 index 95639da5c3..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Agregar contenido a tu sitio de Páginas de GitHub con Jekyll -intro: 'Puedes agregar una página nueva o publicar tu sitio Jekyll a tu sitio en las {% data variables.product.prodname_pages %}.' -product: '{% data reusables.gated-features.pages %}' -redirect_from: - - /articles/adding-content-to-your-github-pages-site-using-jekyll - - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Las personas con permisos de escritura para un repositorio pueden agregar contenido a un sitio de {% data variables.product.prodname_pages %} con Jekyll. - -### Acerca del contenido en sitios Jekyll - -Antes de poder agregar contenido a un sitio Jekyll en las {% data variables.product.prodname_pages %}, debes crear un sitio Jekyll. Para obtener más información, consulta "[Crear un sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/creating-a-github-pages-site-with-jekyll)". - -Los principales tipos de contenido para sitios Jekyll son páginas y publicaciones. Una página es para el contenido independiente que no está asociado con una fecha específica, como una página "Acerca de". El sitio Jekyll predeterminado contiene un archivo denominado `about.md`, que se representa como una página en tu sitio en `TU-SITE-URL/about`. Puedes editar los contenidos de ese archivo para personalizar tu página "Acerca de" y usar la página "Acerca de" como plantilla para crear páginas nuevas. Para obtener más información, consulta "[Páginas](https://jekyllrb.com/docs/pages/)" en la documentación de Jekyll. - -Una publicación es una entrada de blog. El sitio Jekyll predeterminado contiene un directorio denominado `_posts` que contiene un archivo de publicación predeterminada. Puedes editar los contenidos de esa publicación y usar la publicación predeterminada como plantilla para crear publicaciones nuevas. Para obtener más información, consulta "[Publicaciones](https://jekyllrb.com/docs/posts/)" en la documentación de Jekyll. - -Tu tema incluye diseños predeterminados, inclusiones y hojas de estilos que se aplicarán automáticamente a las páginas y publicaciones nuevas de tu sitio; sin embargo, puedes reemplazar cualquiera de estas formas predeterminadas. Para obtener más información, consulta "[Acerca de las {% data variables.product.prodname_pages %} y Jekyll](/articles/about-github-pages-and-jekyll#themes)". - -{% data reusables.pages.about-front-matter %} - -{% data reusables.pages.test-locally %} - -### Agregar una página nueva a tu sitio - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.pages.navigate-publishing-source %} -3. En la raíz de tu fuente de publicación, crea un archivo nuevo para tu página denominado _PAGE-NAME.md_, reemplazando _PAGE-NAME_ por un nombre de archivo significativo para la página. -4. Agrega el siguiente texto preliminar de YAML a la parte superior del archivo, reemplazando _PAGE TITLE_ por el título de la página y _URL-PATH_ por la ruta que quieras para la URL de la página. Por ejemplo, si la URL base de tu sitio es `https://octocat.github.io` y tu _URL-PATH_ es `/about/contact/`, tu página se encontrará en `https://octocat.github.io/about/contact`. - ```shell - layout: page - title: "PAGE TITLE" - permalink: /URL-PATH/ - ``` -5. Debajo del texto preliminar, agrega contenido para tu página. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} - -### Agregar una publicación nueva a tu sitio - -{% data reusables.pages.navigate-site-repo %} -{% data reusables.pages.navigate-publishing-source %} -3. Desplázate hasta el directorio `_posts`. -4. Crea un archivo nuevo denominado _YYYY-MM-DD-NAME-OF-POST.md_, reemplazando _YYY-MM-DD_ por la fecha de tu publicación y _NAME-OF-POST_ por el nombre de tu publicación. -4. Agrega el siguiente texto preliminar de YAML en la parte superior del archivo, reemplazando _POST TITLE_ por el título de la publicación, _YYYYY-MM-DD hh:mm:ss -0000_ por la fecha y hora de la publicación, y _CATEGORY-1_ y _CATEGORY-2_ por tantas categorías como las que quieras para tu publicación. - ```shell - layout: page - title: "POST TITLE" - date: YYYY-MM-DD hh:mm:ss -0000 - categories: CATEGORY-1 CATEGORY-2 - ``` -5. Debajo del texto preliminar, agrega contenido para tu publicación. -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_file_change %} - -### Pasos siguientes - -{% data reusables.pages.add-jekyll-theme %} Para obtener más información, consulta "[Agregar un tema a tu sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md deleted file mode 100644 index ab875b496c..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: Creating a GitHub Pages site with Jekyll -intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.' -product: '{% data reusables.gated-features.pages %}' -redirect_from: - - /articles/creating-a-github-pages-site-with-jekyll - - /github/working-with-github-pages/creating-a-github-pages-site-with-jekyll -permissions: 'People with admin permissions for a repository can create a {% data variables.product.prodname_pages %} site with Jekyll.' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Prerequisites - -Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." - -{% data reusables.pages.recommend-bundler %} - -{% data reusables.pages.jekyll-install-troubleshooting %} - -### Creating a repository for your site - -{% data reusables.pages.new-or-existing-repo %} - -{% data reusables.pages.private_pages_are_public_warning %} - -{% data reusables.repositories.create_new %} -{% data reusables.repositories.owner-drop-down %} -{% data reusables.pages.create-repo-name %} -{% data reusables.repositories.choose-repo-visibility %} - -### Creating your site - -{% data reusables.pages.must-have-repo-first %} - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository. - ```shell - $ cd PARENT-FOLDER - ``` -3. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository. - ```shell - $ git init REPOSITORY-NAME - > Initialized empty Git repository in /Users/octocat/my-site/.git/ - # Creates a new folder on your computer, initialized as a Git repository - ``` - 4. Change directories to the repository. - ```shell - $ cd REPOSITORY-NAME - # Changes the working directory - ``` -{% data reusables.pages.decide-publishing-source %} -{% data reusables.pages.navigate-publishing-source %} - For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. - ```shell - $ mkdir docs - # Creates a new folder called docs - $ cd docs - ``` - If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch. - ```shell - $ git checkout --orphan gh-pages - # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch - ``` - 7. To create a new Jekyll site, use the `jekyll new` command, replacing _VERSION_ with the current dependency version for Jekyll. For more information, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. - - If you installed Bundler: - ```shell - $ bundle exec jekyll VERSION new . - # Creates a Jekyll site in the current directory - ``` - - If you don't have Bundler installed: - ```shell - $ jekyll VERSION new . - # Creates a Jekyll site in the current directory - ``` -8. Open the Gemfile that was created and follow the instructions in the Gemfile's comments to use {% data variables.product.prodname_pages %}. - ![Instructions for updating Gemfile](/assets/images/help/pages/gemfile-instructions.png) -9. Update the `gem "github-pages"` line so that the line looks like this, replacing _VERSION_ with the current dependency version for `github-pages`. For more information, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. -```shell -gem "github-pages", "~> VERSION", group: :jekyll_plugins -``` -10. Save and close the Gemfile. -11. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." -12. Add your {% data variables.product.product_name %} repository as a remote, replacing {% if currentVersion != "free-pro-team@latest" %}_HOSTNAME_ with your appliance's hostname,{% endif %} _USER_ with the account that owns the repository{% if currentVersion != "free-pro-team@latest" %},{% endif %} and _REPOSITORY_ with the name of the repository. -```shell -{% if currentVersion == "free-pro-team@latest" %} -$ git remote add origin https://github.com/USER/REPOSITORY.git -{% else %} -$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git -{% endif %} -``` -13. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on. - ```shell - $ git push -u origin BRANCH - ``` -{% data reusables.pages.configure-publishing-source %} -{% data reusables.pages.navigate-site-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.pages.visit-site %} - -{% data reusables.pages.admin-must-push %} - -### Next steps - -To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)." - -{% data reusables.pages.add-jekyll-theme %} For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)." diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/index.md deleted file mode 100644 index 87b8e3e36f..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Configurar un sitio de Páginas de GitHub con Jekyll -intro: 'Puedes usar Jekyll, un generador de sitio estático popular, para personalizar aún más tu sitio de {% data variables.product.prodname_pages %}.' -redirect_from: - - /articles/using-jekyll-with-pages/ - - /articles/using-jekyll-as-a-static-site-generator-with-github-pages - - /articles/setting-up-a-github-pages-site-with-jekyll -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' -children: - - /about-github-pages-and-jekyll - - /creating-a-github-pages-site-with-jekyll - - /testing-your-github-pages-site-locally-with-jekyll - - /adding-content-to-your-github-pages-site-using-jekyll - - /setting-a-markdown-processor-for-your-github-pages-site-using-jekyll - - /adding-a-theme-to-your-github-pages-site-using-jekyll - - /about-jekyll-build-errors-for-github-pages-sites - - /troubleshooting-jekyll-build-errors-for-github-pages-sites ---- - diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md deleted file mode 100644 index b5757c7676..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Configurar un procesador Markdown para tu sitio de páginas de GitHub usando Jekyll -intro: 'Puedes elegir un procesador Markdown para determinar la manera en que Markdown se representa en tu sitio de {% data variables.product.prodname_pages %}.' -redirect_from: - - /articles/migrating-your-pages-site-from-maruku/ - - /articles/updating-your-markdown-processor-to-kramdown/ - - /articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll - - /github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -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 %} admite dos procesadores Markdown: [kramdown](http://kramdown.gettalong.org/) y el propio procesador [CommonMark](https://commonmark.org/) de {% data variables.product.prodname_dotcom %}, que se utiliza para representar el formato Markdown de {% data variables.product.prodname_dotcom %} 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)." - -Puedes usar Flavored Markdown de {% data variables.product.prodname_dotcom %} con cualquiera de los procesadores, pero solamente nuestro procesador CommonMark siempre encontrará 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*. -{% data reusables.repositories.edit-file %} -4. Encuentra la línea que comienza con `markdown:` y cambia el valor a `kramdown` o `GFM`. ![Configuración Markdown en config.yml](/assets/images/help/pages/config-markdown-value.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose-commit-email %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -### Leer más - -- [Documentación de kramdown](https://kramdown.gettalong.org/documentation.html) -- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md deleted file mode 100644 index d4600f6331..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Probar tu sitio de Páginas de GitHub localmente con Jekyll -intro: 'Puedes compilar tu sitio de {% data variables.product.prodname_pages %} localmente para previsualizar y probar los cambios en tu sitio.' -redirect_from: - - /articles/setting-up-your-pages-site-locally-with-jekyll/ - - /articles/setting-up-your-github-pages-site-locally-with-jekyll/ - - /articles/testing-your-github-pages-site-locally-with-jekyll - - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -Cualquier persona con permisos de lectura para un repositorio puede probar un sitio de {% data variables.product.prodname_pages %} localmente. - -### Prerrequisitos - -Antes de que puedas usar Jekyll para probar un sitio, debes hacer lo siguiente: - - Instalar [Jekyll](https://jekyllrb.com/docs/installation/). - - Crear un sitio de Jekyll. Para obtener más información, consulta "[Crear un sitio de {% data variables.product.prodname_pages %} con Jekyll](/articles/creating-a-github-pages-site-with-jekyll)". - -{% data reusables.pages.recommend-bundler %} - -{% data reusables.pages.jekyll-install-troubleshooting %} - -### Construyendo su sitio localmente - -{% data reusables.command_line.open_the_multi_os_terminal %} -{% data reusables.pages.navigate-publishing-source %} -3. Ejecuta tu sitio Jekyll de forma local. - ```shell - $ bundle exec jekyll serve - > Configuration file: /Users/octocat/my-site/_config.yml - > Source: /Users/octocat/my-site - > Destination: /Users/octocat/my-site/_site - > Incremental build: disabled. Enable with --incremental - > Generating... - > done in 0.309 seconds. - > Auto-regeneration: enabled for '/Users/octocat/my-site' - > Configuration file: /Users/octocat/my-site/_config.yml - > Server address: http://127.0.0.1:4000/ - > Server running... press ctrl-c to stop. - ``` -3. Para previsualizar tu sitio, en tu navegador web, navega hasta `http://localhost:4000`. - -### Actualizar la gema de {% data variables.product.prodname_pages %} - -Jekyll es un proyecto de código abierto activo que se actualiza de manera frecuente. Si la gema de `github-pages` de tu computadora está desactualizada con respecto a la gema de `github-pages` del servidor de {% data variables.product.prodname_pages %}, tu sitio puede verse diferente cuando se compile localmente en comparación a cómo se vea cuando se publique en {% data variables.product.product_name %}. Para evitar esto, actualiza de manera regular la gema de `github-pages` en tu computadora. - -{% data reusables.command_line.open_the_multi_os_terminal %} -2. Actualiza la gema de `github-pages`. - - Si instalaste Bundler, ejecuta `bundle update github-pages`. - - Si no tienes instalado Bundler, ejecuta `gem update github-pages`. - -### Leer más - -- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) en la documentación de Jekyll diff --git a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md deleted file mode 100644 index d843216daf..0000000000 --- a/translations/es-XL/content/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ /dev/null @@ -1,187 +0,0 @@ ---- -title: Troubleshooting Jekyll build errors for GitHub Pages sites -intro: 'You can use Jekyll build error messages to troubleshoot problems with your {% data variables.product.prodname_pages %} site.' -redirect_from: - - /articles/page-build-failed-missing-docs-folder/ - - /articles/page-build-failed-invalid-submodule/ - - /articles/page-build-failed-missing-submodule/ - - /articles/page-build-failed-markdown-errors/ - - /articles/page-build-failed-config-file-error/ - - /articles/page-build-failed-unknown-tag-error/ - - /articles/page-build-failed-tag-not-properly-terminated/ - - /articles/page-build-failed-tag-not-properly-closed/ - - /articles/page-build-failed-file-does-not-exist-in-includes-directory/ - - /articles/page-build-failed-file-is-a-symlink/ - - /articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository/ - - /articles/page-build-failed-file-is-not-properly-utf-8-encoded/ - - /articles/page-build-failed-invalid-post-date/ - - /articles/page-build-failed-invalid-sass-or-scss/ - - /articles/page-build-failed-invalid-highlighter-language/ - - /articles/page-build-failed-relative-permalinks-configured/ - - /articles/page-build-failed-syntax-error-in-for-loop/ - - /articles/page-build-failed-invalid-yaml-in-data-file/ - - /articles/page-build-failed-date-is-not-a-valid-datetime/ - - /articles/troubleshooting-github-pages-builds/ - - /articles/troubleshooting-jekyll-builds/ - - /articles/troubleshooting-jekyll-build-errors-for-github-pages-sites - - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites -product: '{% data reusables.gated-features.pages %}' -versions: - free-pro-team: '*' - enterprise-server: '*' ---- -### Troubleshooting build errors - -If Jekyll encounters an error building your {% data variables.product.prodname_pages %} site locally or on {% data variables.product.product_name %}, you can use error messages to troubleshoot. For more information about error messages and how to view them, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." - -If you received a generic error message, check for common issues. -- You're using unsupported plugins. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)."{% if currentVersion == "free-pro-team@latest" %} -- Your repository has exceeded our repository size limits. For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota)"{% endif %} -- You changed the `source` setting in your *_config.yml* file. {% data variables.product.prodname_pages %} overrides this setting during the build process. -- A filename in your publishing source contains a colon (`:`) which is not supported. - -If you received a specific error message, review the troubleshooting information for the error message below. - -After you've fixed any errors, push the changes to your site's publishing source to trigger another build on {% data variables.product.product_name %}. - -### Config file error - -This error means that your site failed to build because the *_config.yml* file contains syntax errors. - -To troubleshoot, make sure that your *_config.yml* file follows these rules: - -{% data reusables.pages.yaml-rules %} - -{% data reusables.pages.yaml-linter %} - -### Date is not a valid datetime - -This error means that one of the pages on your site includes an invalid datetime. - -To troubleshoot, search the file in the error message and the file's layouts for calls to any date-related Liquid filters. Make sure that any variables passed into date-related Liquid filters have values in all cases and never pass `nil` or `""`. For more information, see "[Liquid filters](https://help.shopify.com/en/themes/liquid/filters)" in the Liquid documentation. - -### File does not exist in includes directory - -This error means that your code references a file that doesn't exist in your *_includes* directory. - -{% data reusables.pages.search-for-includes %} If any of the files you've referenced aren't in the *_includes* directory, copy or move the files into the *_includes* directory. - -### File is a symlink - -This error means that your code references a symlinked file that does not exist in the publishing source for your site. - -{% data reusables.pages.search-for-includes %} If any of the files you've referenced are symlinked, copy or move the files into the *_includes* directory. - -### File is not properly UTF-8 encoded - -This error means that you used non-Latin characters, like `日本語`, without telling the computer to expect these symbols. - -To troubleshoot, force UTF-8 encoding by adding the following line to your *_config.yml* file: -``` -encoding: UTF-8 -``` - -### Invalid highlighter language - -This error means that you specified any syntax highlighter other than [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/) in your configuration file. - -To troubleshoot, update your *_config.yml* file to specify [Rouge](https://github.com/jneen/rouge) or [Pygments](http://pygments.org/). For more information, see "[About {% data variables.product.product_name %} and Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting)." - -### Invalid post date - -This error means that a post on your site contains an invalid date in the filename or YAML front matter. - -To troubleshoot, make sure all dates are formatted as YYYY-MM-DD HH:MM:SS for UTC and are actual calendar dates. To specify a time zone with an offset from UTC, use the format YYYY-MM-DD HH:MM:SS +/-TTTT, like `2014-04-18 11:30:00 +0800`. - -If you specify a date format in your *_config.yml* file, make sure the format is correct. - -### Invalid Sass or SCSS - -This error means your repository contains a Sass or SCSS file with invalid content. - -To troubleshoot, review the line number included in the error message for invalid Sass or SCSS. To help prevent future errors, install a Sass or SCSS linter for your favorite text editor. - -### Invalid submodule - -This error means that your repository includes a submodule that hasn't been properly initialized. - -{% data reusables.pages.remove-submodule %} - -If do you want to use the submodule, make sure you use `https://` when referencing the submodule (not `http://`) and that the submodule is in a public repository. - -### Invalid YAML in data file - -This error means that one of more files in the *_data* folder contains invalid YAML. - -To troubleshoot, make sure the YAML files in your *_data* folder follow these rules: - -{% data reusables.pages.yaml-rules %} - -{% data reusables.pages.yaml-linter %} - -For more information about Jekyll data files, see "[Data Files](https://jekyllrb.com/docs/datafiles/)" in the Jekyll documentation. - -### Markdown errors - -This error means that your repository contains Markdown errors. - -To troubleshoot, make sure you are using a supported Markdown processor. For more information, see "[Setting a Markdown processor for your {% data variables.product.prodname_pages %} site using Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll)." - -Then, make sure the file in the error message uses valid Markdown syntax. For more information, see "[Markdown: Syntax](https://daringfireball.net/projects/markdown/syntax)" on Daring Fireball. - -### Missing docs folder - -This error means that you have chosen the `docs` folder on a branch as your publishing source, but there is no `docs` folder in the root of your repository on that branch. - -To troubleshoot, if your `docs` folder was accidentally moved, try moving the `docs` folder back to the root of your repository on the branch you chose for your publishing source. If the `docs` folder was accidentally deleted, you can either: -- Use Git to revert or undo the deletion. For more information, see "[git-revert](https://git-scm.com/docs/git-revert.html)" in the Git documentation. -- Create a new `docs` folder in the root of your repository on the branch you chose for your publishing source and add your site's source files to the folder. For more information, see "[Creating new files](/articles/creating-new-files)." -- Change your publishing source. For more information, see "[Configuring a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages)." - -### Missing submodule - -This error means that your repository includes a submodule that doesn't exist or hasn't been properly initialized. - -{% data reusables.pages.remove-submodule %} - -If you do want to use a submodule, initialize the submodule. For more information, see "[Git Tools - Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules)" in the _Pro Git_ book. - -### Relative permalinks configured - -This errors means that you have relative permalinks, which are not supported by {% data variables.product.prodname_pages %}, in your *_config.yml* file. - -Permalinks are permanent URLs that reference a particular page on your site. Absolute permalinks begin with the root of the site, while relative permalinks begin with the folder containing the referenced page. {% data variables.product.prodname_pages %} and Jekyll no longer support relative permalinks. For more information about permalinks, see "[Permalinks](https://jekyllrb.com/docs/permalinks/)" in the Jekyll documentation. - -To troubleshoot, remove the `relative_permalinks` line from your *_config.yml* file and reformat any relative permalinks in your site with absolute permalinks. For more information, see "[Editing files in your repository](/articles/editing-files-in-your-repository)." - -### Symlink does not exist within your site's repository - -This error means that your site includes a symbolic link (symlink) that does not exist in the publishing source for your site. For more information about symlinks, see "[Symbolic link](https://en.wikipedia.org/wiki/Symbolic_link)" on Wikipedia. - -To troubleshoot, determine if the file in the error message is used to build your site. If not, or if you don't want the file to be a symlink, delete the file. If the symlinked file is necessary to build your site, make sure the file or directory the symlink references is in the publishing source for your site. To include external assets, consider using {% if currentVersion == "free-pro-team@latest" %}`git submodule` or {% endif %}a third-party package manager such as [Bower](https://bower.io/).{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Using submodules with {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages)."{% endif %} - -### Syntax error in 'for' loop - -This error means that your code includes invalid syntax in a Liquid `for` loop declaration. - -To troubleshoot, make sure all `for` loops in the file in the error message have proper syntax. For more information about proper syntax for `for` loops, see "[Iteration tags](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for)" in the Liquid documentation. - -### Tag not properly closed - -This error message means that your code includes a logic tag that is not properly closed. For example, {% raw %}`{% capture example_variable %}` must be closed by `{% endcapture %}`{% endraw %}. - -To troubleshoot, make sure all logic tags in the file in the error message are properly closed. For more information, see "[Liquid tags](https://help.shopify.com/en/themes/liquid/tags)" in the Liquid documentation. - -### Tag not properly terminated - -This error means that your code includes an output tag that is not properly terminated. For example, {% raw %}`{{ page.title }` instead of `{{ page.title }}`{% endraw %}. - -To troubleshoot, make sure all output tags in the file in the error message are terminated with `}}`. For more information, see "[Liquid objects](https://help.shopify.com/en/themes/liquid/objects)" in the Liquid documentation. - -### Unknown tag error - -This error means that your code contains an unrecognized Liquid tag. - -To troubleshoot, make sure all Liquid tags in the file in the error message match Jekyll's default variables and there are no typos in the tag names. For a list of default varibles, see "[Variables](https://jekyllrb.com/docs/variables/)" in the Jekyll documentation. - -Unsupported plugins are a common source of unrecognized tags. If you use an unsupported plugin in your site by generating your site locally and pushing your static files to {% data variables.product.product_name %}, make sure the plugin is not introducing tags that are not in Jekyll's default variables. For a list of supported plugins, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll#plugins)." diff --git a/translations/es-XL/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md b/translations/es-XL/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md deleted file mode 100644 index f79aed5fa7..0000000000 --- a/translations/es-XL/content/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Acerca del Soporte prémium de GitHub para GitHub Enterprise Cloud -intro: '{% data variables.contact.premium_support %} es una oferta de soporte suplementaria y pagada para los clientes de {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_one %}.' -redirect_from: - - /articles/about-github-premium-support - - /articles/about-github-premium-support-for-github-enterprise-cloud -versions: - fpt: '*' -topics: - - Jobs ---- - -{% note %} - -**Notas:** - -- Los términos del {% data variables.contact.premium_support %} están sujetos a cambios sin aviso y entraron en vigencia a partir de septiembre de 2018. - -- {% data reusables.support.data-protection-and-privacy %} - -- Este artículo contiene los términos de {% data variables.contact.premium_support %} para clientes de {% data variables.product.prodname_ghe_cloud %}. Es posible que los términos sean diferentes para los clientes de {% data variables.product.prodname_ghe_server %} o los clientes de {% data variables.product.prodname_enterprise %} que compran {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} de manera conjunta. Para obtener más información, consulta "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise-server)" y "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/enterprise-support/about-github-premium-support-for-github-enterprise)". - -{% endnote %} - -### Acerca del {% data variables.contact.premium_support %} - -{% data variables.contact.premium_support %} ofrece: - - Soporte técnico por escrito, en inglés, a través del portal de soporte de 24 horas al día, 7 días a la semana. - - Soporte técnico telefónico, en inglés, 24 horas al día, 7 días a la semana. - - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados - - Acceso a contenido prémium - - Revisiones de estado programadas - - Servicios administrados. - -{% data reusables.support.about-premium-plans %} - -{% data reusables.support.signing-up-for-premium-support %} - -{% data reusables.support.scope-of-support %} - -{% data reusables.support.contacting-premium-support %} - -### Horas de operación - -{% data variables.contact.premium_support %} está disponible las 24 horas del día, los 7 días de la semana. - -{% data reusables.support.service-level-agreement-response-times %} - -### Asignar una prioridad a un ticket de soporte - -Cuando contactas a {% data variables.contact.premium_support %}, puedes escoger una de cuatro prioridades para el ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, o{% data variables.product.support_ticket_priority_low %}. - -{% data reusables.support.github-can-modify-ticket-priority %} - -{% data reusables.support.ghec-premium-priorities %} - -### Resolver y cerrar tickets de soporte - -{% data variables.contact.premium_support %} puede considerar un ticket como resuelto después de proporcionar una explicación, recomendación, instrucción de uso, o de solución alternativa, - -Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.premium_support %} puede pedirte que elimines el complemento, el módulo o el código no compatible mientras intentas resolver el problema. {% data variables.contact.premium_support %} puede considerar el ticket como resuelto si el problema se soluciona cuando se elimina el plug-in, módulo, o código personalizado no compatible. - -{% data variables.contact.premium_support %}Puede cerrar los tickets si están fuera del alcance de soporte o si se te ha intentado contactar varias veces sin recibir una respuesta. Si {% data variables.contact.premium_support %} cierra un ticket por no haber recibido respuesta, puedes solicitar que lo reabra. - -{% data reusables.support.receiving-credits %} - -{% data reusables.support.accessing-premium-content %} - -### Leer más - -- "[Enviar un ticket](/articles/submitting-a-ticket)" diff --git a/translations/es-XL/content/github/working-with-github-support/about-github-support.md b/translations/es-XL/content/github/working-with-github-support/about-github-support.md deleted file mode 100644 index 4f4a4f4226..0000000000 --- a/translations/es-XL/content/github/working-with-github-support/about-github-support.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Acerca de GitHub Support -intro: '{% data variables.contact.github_support %} puede ayudarte a solucionar los problemas con los que te encuentres cuando utilices {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /articles/about-github-support -versions: - fpt: '*' -topics: - - Jobs ---- - -### Acerca de {% data variables.contact.github_support %} - -Las opciones de soporte varían dependiendo de tu producto de {% data variables.product.prodname_dotcom_the_website %}. Si cuentas con un producto pagado, puedes contactar a {% data variables.contact.github_support %} en inglés. Tu cuenta también puede incluir {% data variables.contact.premium_support %}. - -| | {% data variables.product.prodname_gcf %} | Soporte estándar | Soporte premium | -| ------------------------------------------------------ | ---------------------------------------------- | ---------------- | --------------- | -| {% data variables.product.prodname_free_user %} | X | | | -| {% data variables.product.prodname_pro %} | X | X | | -| {% data variables.product.prodname_team %} | X | X | | -| {% data variables.product.prodname_ghe_cloud %} | X | X | X | -| {% data variables.product.prodname_ghe_server %} | X | X | X | - -Para ver si actualmente hay algún incidente que afecte los servicios en {% data variables.product.prodname_dotcom %}, o para suscribirse y recibir notificaciones de actualizaciones de estado futuras, visita la [Página de Estado](https://www.githubstatus.com/) de {% data variables.product.prodname_dotcom %}. - -### Contactar a {% data variables.contact.github_support %} - -Las cuentas organizacionales y de usuario de {% data variables.product.prodname_free_user %} pueden utilizar el {% data variables.contact.community_support_forum %} para buscar temas, hacer preguntas, compartir soluciones e interactuar con {% data variables.contact.community_support %}. También puedes contactar a {% data variables.contact.contact_support %} para reportar problemas de cuentas, seguridad y abuso. - -En cuentas pagadas, puedes ya sea contactar a {% data variables.contact.contact_support %} y, dependiendo de tu plan, contactar a {% data variables.contact.premium_support %}, o bien, a {% data variables.contact.contact_ent_support %}. Para obtener más información acerca de contactar a {% data variables.contact.premium_support %}, consulta la sección "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)" o "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_server %}](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise)". - -### Otorgar a {% data variables.contact.github_support %} acceso temporal a un repositorio privado - -Si {% data variables.contact.github_support %} necesita acceder a un repositorio privado para tratar tu solicitud de soporte, el dueño de éste recibirá un correo electrónico con un enlace para aceptar o rechazar el acceso temporal. El propietario tendrá 20 días para aceptar o rechazar la solicitud antes de que ésta caduque. Si el propietario acepta la solicitud, {% data variables.contact.github_support %} tendrá acceso al repositorio por cinco días. - -{% data variables.contact.github_support %} jamás accederá a tus repositorios privados sin tu consentimiento explícito. Para obtener más información, consulta las [Condiciones de Servicio](/articles/github-terms-of-service#3-access). diff --git a/translations/es-XL/content/github/working-with-github-support/github-enterprise-cloud-support.md b/translations/es-XL/content/github/working-with-github-support/github-enterprise-cloud-support.md deleted file mode 100644 index 3097601a3b..0000000000 --- a/translations/es-XL/content/github/working-with-github-support/github-enterprise-cloud-support.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Asistencia para Enterprise Cloud de GitHub -redirect_from: - - /articles/business-plan-support/ - - /articles/github-business-cloud-support/ - - /articles/github-enterprise-cloud-support -intro: '{% data variables.product.prodname_ghe_cloud %} incluye un tiempo de respuesta objetivo de ocho horas para las solicitudes de asistencia prioritarias, de lunes a viernes en tu zona horaria local.' -versions: - fpt: '*' -topics: - - Jobs ---- - -{% note %} - -**Notq:** Los clientes de {% data variables.product.prodname_ghe_cloud %} pueden registrarse para {% data variables.contact.premium_support %}. Para obtener más información, consulta "[Acerca de {% data variables.contact.premium_support %} para {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)". - -{% endnote %} - -Puedes enviar preguntas prioritarias si has comprado {% data variables.product.prodname_ghe_cloud %} o si eres miembro, colaborador externo o gerente de facturación de una organización {% data variables.product.prodname_dotcom %} actualmente suscrita en {% data variables.product.prodname_ghe_cloud %}. - -Preguntas que califican para recibir respuestas prioritarias: -- Incluyen preguntas relacionadas con tu imposibilidad para acceder o usar la funcionalidad de control de la versión principal de {% data variables.product.prodname_dotcom %} -- Incluyen situaciones relacionadas con la seguridad de tu cuenta -- No incluyen servicios y funciones periféricos, como preguntas acerca de Gists, {% data variables.product.prodname_pages %} o notificaciones de correo electrónico -- Incluyen preguntas acerca de organizaciones que actualmente usan {% data variables.product.prodname_ghe_cloud %} - -Para calificar para una respuesta prioritaria, debes hacer lo siguiente: -- Enviar tu pregunta a [{% data variables.contact.enterprise_support %}](https://enterprise.githubsupport.com/hc/en-us/requests/new?github_product=cloud) desde una dirección de correo verificada que esté asociada con la organización que actualmente usa {% data variables.product.prodname_ghe_cloud %} -- Enviar un ticket de asistencia nuevo para cada situación prioritaria particular -- Enviar tu pregunta de lunes a viernes en tu zona horaria local -- Comprender que la respuesta a una pregunta prioritaria será recibida por correo electrónico -- Colaborar con {% data variables.contact.github_support %} y proporcionar toda la información que solicite {% data variables.contact.github_support %} - -{% tip %} - -**Consejo:** Las preguntas no califican para recibir respuestas prioritarias si se envían durante un feriado local de tu jurisdicción. - -{% endtip %} - -El tiempo de respuesta objetivo de ocho horas: -- Comienza cuando {% data variables.contact.github_support %} recibe tu pregunta que califica -- No comienza hasta que hayas proporcionada la suficiente información para responder la pregunta, a menos que específicamente indiques que no cuentas con la información suficiente -- No aplica durante los fines de semana de tu zona horaria local o durante los feriados locales de tu jurisdicción - -{% note %} - -**Nota:** {% data variables.contact.github_support %} no garantiza una resolución para tu pregunta prioritaria. {% data variables.contact.github_support %} puede escalar problemas al estado de pregunta prioritaria o bajarlos en función de nuestra evaluación razonable de la información que nos proporcionas. - -{% endnote %} diff --git a/translations/es-XL/content/github/working-with-github-support/github-marketplace-support.md b/translations/es-XL/content/github/working-with-github-support/github-marketplace-support.md deleted file mode 100644 index 7737b43f3c..0000000000 --- a/translations/es-XL/content/github/working-with-github-support/github-marketplace-support.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Asistencia de Mercado GitHub -intro: 'Para recibir ayuda con la compra o el pago de una app desde {% data variables.product.prodname_marketplace %}, contáctate con {% data variables.contact.contact_support %}. Para recibir ayuda con el uso de una app {% data variables.product.prodname_marketplace %}, contáctate con el proveedor de la app.' -redirect_from: - - /articles/github-marketplace-support -versions: - fpt: '*' -topics: - - Jobs ---- - - -### Contactarse con el proveedor de la app para recibir asistencia - -Todas las apps de {% data variables.product.prodname_marketplace %} incluyen un enlace para contactarse con el equipo de asistencia de la app. - -{% data reusables.marketplace.visit-marketplace %} -2. Navega por la página de tu app. -3. En la barra lateral izquierda, dentro de "Developer tools" (Herramientas del programador), haz clic en **Support** (Asistencia). -4. En la página de asistencia de la app, sigue las instrucciones de la página de la app para contactarte con el equipo de asistencia de la app. - -### Leer más - -- "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)" -- "[Comprar e instalar aplicaciones en {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)" -- "[Administrar la facturación de las apps de {% data variables.product.prodname_marketplace %}](/articles/managing-billing-for-github-marketplace-apps)" diff --git a/translations/es-XL/content/github/working-with-github-support/index.md b/translations/es-XL/content/github/working-with-github-support/index.md deleted file mode 100644 index 647c128c7b..0000000000 --- a/translations/es-XL/content/github/working-with-github-support/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Trabajar con el soporte de GitHub -redirect_from: - - /categories/working-with-github-support - - /forum -versions: - fpt: '*' -topics: - - Jobs -children: - - /about-github-support - - /github-enterprise-cloud-support - - /about-github-premium-support-for-github-enterprise-cloud - - /github-marketplace-support - - /submitting-a-ticket ---- -### Índice diff --git a/translations/es-XL/content/github/working-with-github-support/submitting-a-ticket.md b/translations/es-XL/content/github/working-with-github-support/submitting-a-ticket.md deleted file mode 100644 index 084314987c..0000000000 --- a/translations/es-XL/content/github/working-with-github-support/submitting-a-ticket.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Emitir un ticket -intro: 'Puedes emitir un ticket a {% data variables.contact.github_support %} utilizando el portal de soporte.' -redirect_from: - - /articles/submitting-a-ticket -versions: - fpt: '*' -topics: - - Jobs ---- - -Si tu cuenta utiliza un producto pagado de {% data variables.product.prodname_dotcom %}, puedes contactar directamente a {% data variables.contact.github_support %}. Si tu cuenta utiliza {% data variables.product.prodname_free_user %} para cuentas organizacionales y de usuario, puedes contactar a {% data variables.contact.contact_support %} para reportar problemas con la cuenta, seguridad y abuso. Para obtener más informaciónm, consulta la sección "[Acerca de GitHub Support](/github/working-with-github-support/about-github-support)". - -Si utilizas {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_cloud %}, o el {% data variables.product.premium_support_plan %} deberás emitir tickets utilizando el {% data variables.contact.enterprise_portal %}. - -### Emitir un ticket utilizando el {% data variables.contact.support_portal %} - -1. Navega al {% data variables.contact.contact_support_portal %}. -2. Debajo de "Nombre", ingresa tu nombre. ![Campo de nombre](/assets/images/help/support/name-field.png) -3. Utiliza el menú desplegable de correo electrónico y selecciona la dirección de correo electrónico que deseas contacte {% data variables.contact.github_support %}.![Campo de correo electrónico](/assets/images/help/support/email-field.png) -4. Debajo de "Tema", teclea un título descriptivo para el problema que estás experimentando. ![Campo de asuto](/assets/images/help/support/subject-field.png) -5. Debajo de "Cómo podemos ayudar", proporciona cualquier tipo de información adicional que ayudará al equipo de soporte a solucionar el problema. La información útil podría incluir: ![Campo de cómo podemos ayudar](/assets/images/help/support/how-can-we-help-field.png) - - Pasos para reproducir el incidente - - Cualquier circunstancia especial relacionada con el descubrimiento del problema (por ejemplo, la primera vez que se suscitó, o su materialización después de cierto evento, frecuencia en la que se presenta, impacto al negocio, y urgencia sugerida) - - Redacción exacta de los mensajes de error -6. Opcionalmente, adjunta archivos arrastrando y soltando, cargando, o pegando desde el portapapeles. -7. Da clic en **Enviar solicitud**. ![Botón de eenviar solicitud](/assets/images/help/support/send-request-button.png) - -### Emitir un ticket utilizando el {% data variables.contact.enterprise_portal %} - -1. Navega por el {% data variables.contact.contact_enterprise_portal %}. -5. Da clic en **Emite un Ticket** ![Emite un ticket al equipo de Soporte Empresarial](/assets/images/enterprise/support/submit-ticket-button.png) -{% data reusables.enterprise_enterprise_support.submit-support-ticket-first-section %} -{% data reusables.enterprise_enterprise_support.submit-support-ticket-second-section %} - -### Leer más -- "[Productos de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/githubs-products)" -- "[Acerca de {% data variables.contact.github_support %}](/articles/about-github-support)" -- "[Acerca de {% data variables.contact.premium_support %} for {% data variables.product.prodname_ghe_cloud %}](/articles/about-github-premium-support-for-github-enterprise-cloud)." diff --git a/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md deleted file mode 100644 index 58446454d5..0000000000 --- a/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: Crear gists -intro: 'Puedes crear dos tipos de gists: públicos y secretos. Crea un gist público si estás preparado para compartir tus ideas con todo el mundo o crea un gist secreto si no estás listo para hacerlo.' -redirect_from: - - /articles/about-gists/ - - /articles/cannot-delete-an-anonymous-gist/ - - /articles/deleting-an-anonymous-gist/ - - /articles/creating-gists - - /github/writing-on-github/creating-gists -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Acerca de los gists - -Todo gist es un repositorio Git, lo que significa que se puede bifurcar y clonar. Si has iniciado sesión en {% data variables.product.product_name %}, cuando crees un gist, este se asociará con tu cuenta y lo verás en tu lista de gists cuando te dirijas a tu {% data variables.gists.gist_homepage %}. - -Los gists pueden ser públicos o secretos. Los gists públicos se muestran en {% data variables.gists.discover_url %}, donde las personas pueden explorar los nuevos gists a medida que estos se crean. También se los puede buscar, para que puedas usarlos si deseas que otras personas encuentren tu trabajo y lo vean. {% data reusables.gist.cannot-convert-public-gists-to-secret %} - -Los gists secretos no se muestran en {% data variables.gists.discover_url %}{% if currentVersion != "free-pro-team@latest" %}, {% endif %} y no se pueden buscar. {% data reusables.gist.cannot-convert-public-gists-to-secret %}Los gists secretos no son privados. Si envías la URL de un gist secreto a un amigo, este podrá verlo. Sin embargo, si alguien que no conoces descubre la URL, también podrá 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. - -{% if currentVersion != "free-pro-team@latest" %} - -Si el administrador de tu sitio ha inhabilitado el modo privado, también puedes usar gists anónimos, que pueden ser públicos o privados. - -{% data reusables.gist.anonymous-gists-cannot-be-deleted %} - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} - -Recibirás una notificación si: -- Seas el autor de un gist. -- Alguien te mencione en un gist. -- Puedes suscribirte a un gist haciendo clic en **Suscribir** en la parte superior de cualquier gist. -{% endif %} - -You can pin gists to your profile so other people can see them easily. Para obtener más información, consulta "[A nclar elementos a tu perfil](/articles/pinning-items-to-your-profile)". - -Puedes descubrir gists creados por otros usuarios si te diriges a la {% data variables.gists.gist_homepage %} y haces 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). - -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). - -Puedes descargar un archivo ZIP de un gist haciendo clic en el botón **Descargar ZIP** en la parte superior del gist. Puedes insertar un gist en cualquier campo de texto compatible con Javascript, como una publicación en un blog. Para insertar el código, haz clic en el icono del portapapeles junto a la URL **Insertar** de un gist. Para insertar un archivo de gist específico, anexa la URL **Insertar** con `?file=FILENAME`. - -{% if currentVersion == "free-pro-team@latest" %} - -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 "[Asignar archivos GeoJSON en {% data variables.product.product_name %}](/articles/mapping-geojson-files-on-github)". - -{% endif %} - -### Crear un gist - -También puedes arrastrar y soltar un archivo de texto desde tu escritorio directamente en el editor de gist. - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% note %} - -You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation. - -{% endnote %} -{% endif %} - -1. Inicia sesión en {% data variables.product.product_name %}. -2. Dirígete a tu {% data variables.gists.gist_homepage %}. -3. Escribe una descripción opcional y un nombre para tu gist. ![Descripción del nombre del gist](/assets/images/help/gist/gist_name_description.png) - -4. Escribe el texto de tu gist en el cuadro de texto para el gist. ![Cuadro de texto para el gist](/assets/images/help/gist/gist_text_box.png) - -5. Realiza una de las siguientes acciones: - - Para crear un gist público, da clic en **Crear un gist público**. - - Para crear un gist secreto, da clic en **Crear un Gist secreto**. ![Botón para crear el gist](/assets/images/help/gist/gist_create_btn.png) - - {% note %} - - **Nota:{% data reusables.gist.cannot-convert-public-gists-to-secret %}** - - {% endnote %} diff --git a/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md deleted file mode 100644 index b2842cd6c9..0000000000 --- a/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -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.' -redirect_from: - - /articles/forking-and-cloning-gists - - /github/writing-on-github/forking-and-cloning-gists -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Bifurcar gists - -Cada gist indica qué bifurcaciones tienen actividad, lo que hace que sea más fácil encontrar cambios interesantes realizados por compañeros de trabajo o por completos extraños. - -![Bifurcaciones del gist](/assets/images/help/gist/gist_forks.png) - -### Clonar gists - -Si deseas hacer cambios locales en un gist y subirlos a la web, puedes clonar un gist y hacer confirmaciones de la misma manera que lo harías con cualquier repositorio de Git. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". - -![Botón Clonar gist](/assets/images/help/gist/gist_clone_btn.png) - -### Ver el historial de confirmaciones de un gist - -Para ver el historial completo de confirmaciones de un gist, haz clic en la pestaña "Revisiones" en la parte superior del gist. - -![Pestaña Revisiones de gist](/assets/images/help/gist/gist_revisions_tab.png) - -Verás el historial completo de confirmaciones del gist con sus diferencias. - -![Página de revisiones de gist](/assets/images/help/gist/gist_history.png) diff --git a/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md b/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md deleted file mode 100644 index a3287b8c1d..0000000000 --- a/translations/es-XL/content/github/writing-on-github/editing-and-sharing-content-with-gists/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Editar y compartir contenido con gists -intro: '' -redirect_from: - - /categories/23/articles/ - - /categories/gists/ - - /articles/editing-and-sharing-content-with-gists -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /creating-gists - - /forking-and-cloning-gists ---- - diff --git a/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md b/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md deleted file mode 100644 index 0e7b5b6ff5..0000000000 --- a/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Acerca de escritura y formato en GitHub -intro: GitHub combina una sintáxis para el texto con formato llamado formato Markdown de GitHub con algunas características de escritura únicas. -redirect_from: - - /articles/about-writing-and-formatting-on-github - - /github/writing-on-github/about-writing-and-formatting-on-github -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -[Markdown](http://daringfireball.net/projects/markdown/) es una sintáxis fácil de leer y fácil de escribir para el texto simple con formato. - -Le hemos agregado alguna funcionalidad personalizada para crear el formato Markdown de {% data variables.product.prodname_dotcom %}, usado para dar formato a la prosa y al código en todo nuestro sitio. - -También puedes interactuar con otros usuarios en las solicitudes de extracción y las propuestas, usando funciones como [@menciones](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [propuesta y referencias PR](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) y [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji). - -### Barra de herramientas de formato de texto - -Cada campo de comentario en {% data variables.product.product_name %} contiene una barra de herramientas de formato de texto, lo que te permite dar formato a tu texto sin tener que aprender la sintáxis de Markdown. Además del formato de Markdown como la negrita y la cursiva y crear encabezados, enlaces y listados, la barra de herramientas incluye características específicas de {% data variables.product.product_name %}, como las @menciones, los listados de tareas y los enlaces a propuestas y solicitudes de extracción. - -![Barra de herramientas de Markdown](/assets/images/help/writing/markdown-toolbar.gif) - -### Leer más - -- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) -- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" -- "[Trabajar con formato avanzado](/articles/working-with-advanced-formatting)" -- "[Dominar Markdown](https://guides.github.com/features/mastering-markdown/)" diff --git a/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md deleted file mode 100644 index ba0896e826..0000000000 --- a/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -title: Sintaxis de escritura y formato básicos -intro: Crear formatos sofisticados para tu prosa y código en GitHub con sintaxis simple. -redirect_from: - - /articles/basic-writing-and-formatting-syntax - - /github/writing-on-github/basic-writing-and-formatting-syntax -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Encabezados - -Para crear un encabezado, agrega uno a seis símbolos `#` antes del encabezado del texto. La cantidad de `#` que usas determinará el tamaño del ecanbezado. - -``` -# El encabezado más largo -## El segundo encabezado más largo -###### El encabezado más pequeño -``` - -![Encabezados H1, H2 y H6 representados](/assets/images/help/writing/headings-rendered.png) - -### Estilo de texto - -Puedes indicar énfasis con texto en negrita, cursiva o tachado. - -| Estilo | Sintaxis | Atajo del teclado | Ejemplo | Resultado | -| ---------------------------- | ----------------- | ------------------- | ----------------------------------------------- | --------------------------------------------- | -| Negrita | `** **` o `__ __` | command/control + b | `**Este texto está en negrita**` | **Este texto está en negrita** | -| Cursiva | `* *` o `_ _` | command/control + i | `*Este texto está en cursiva*` | *Este texto está en cursiva* | -| Tachado | `~~ ~~` | | `~~Este texto está equivocado~~` | ~~Este texto está equivocado~~ | -| Cursiva en negrita y anidada | `** **` y `_ _` | | `**Este texto es _extremadamente_ importante**` | **Este texto es _extremadamente_ importante** | -| Todo en negrita y cursiva | `*** ***` | | `***Todo este texto es importante***` | ***Todo este texto es importante*** | - -### Cita de texto - -Puedes citar texto con un `>`. - -``` -Tal como dice Abraham Lincoln: - -> Con perdón de la expresión -``` - -![Texto citado representado](/assets/images/help/writing/quoted-text-rendered.png) - -{% tip %} - -**Sugerencia:** Al revisar una conversación, puedes citar un texto automáticamente en un comentario al resaltar el texto y luego escribir el código `r`. Puedes citar un comentario completo al hacer clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, y luego en **Quote reply** (Citar respuesta). Para obtener más información sobre atajo del teclado, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/)". - -{% endtip %} - -### Código de cita - -Puedes indicar un código o un comando dentro de un enunciado con comillas simples. El texto dentro de las comillas simples no será formateado. - -``` -Usa `git status` para enumerar todos los archivos nuevos o modificados que aún no han sido confirmados. -``` - -![Bloque de código en línea representado](/assets/images/help/writing/inline-code-rendered.png) - -Para formatear código o texto en su propio bloque distintivo, usa comillas triples. - -
    -Algunos de los comandos de Git básicos son:
-```
-git status
-git add
-git commit
-```
-
    - -![Bloque de código representado](/assets/images/help/writing/code-block-rendered.png) - -Para obtener más información, consulta "[Crear y resaltar bloques de código](/articles/creating-and-highlighting-code-blocks)". - -### Enlaces - -Puedes crear un enlace en línea al encerrar el texto del enlace entre corchetes `[ ]`, y luego encerrar la URL entre paréntesis `( )`. También puedes usar el atajo del teclado `command + k` para crear un enlace. - -`Este sitio se construyó usando [GitHub Pages](https://pages.github.com/).` - -![Enlace representado](/assets/images/help/writing/link-rendered.png) - -{% tip %} - -**Sugerencias:** {% data variables.product.product_name %} automáticamente crea enlaces cuando las direcciones URL válidas están escritas en un comentario. Para obtener más información, consulta "[Referencias autovinculadas y direcciones de URL](/articles/autolinked-references-and-urls)". - -{% endtip %} - -### Enlaces de sección - -{% data reusables.repositories.section-links %} - -### Enlaces relativos - -{% data reusables.repositories.relative-links %} - -### Listas - -Puedes realizar una lista desordenada al anteceder una o más líneas de texto con `-` o `*`. - -``` -- George Washington -- John Adams -- Thomas Jefferson -``` - -![Lista desordenada representada](/assets/images/help/writing/unordered-list-rendered.png) - -Para ordenar tu lista, antecede cada línea con un número. - -``` -1. James Madison -2. James Monroe -3. John Quincy Adams -``` - -![Lista ordenada representada](/assets/images/help/writing/ordered-list-rendered.png) - -#### Listas anidadas - -Puedes crear una lista anidada al dejar sangría en uno o más elementos de la lista debajo de otro elemento. - -Para crear una lista anidada mediante el editor web en {% data variables.product.product_name %} o un editor de texto que usa una fuente monoespaciada, como [Atom](https://atom.io/), puedes alinear tu lista visualmente. Escribe los caracteres con espacio frente a tu elemento de la lista anidada hasta que el carácter del marcador de lista (`-` or `*`) se encuentre directamente debajo del primer carácter del texto en el elemento que se encuentra por debajo. - -``` -1. Primer elemento de la lista - - Primer elemento de la lista anidado - - Segundo elemento de la lista anidado -``` - -![Lista anidada con alineación resaltada](/assets/images/help/writing/nested-list-alignment.png) - -![Lista con dos niveles de elementos anidados](/assets/images/help/writing/nested-list-example-1.png) - -Para crear una lista anidada en el editor de comentarios en {% data variables.product.product_name %}, que no usa una fuente monoespaciada, puedes observar el elemento de la lista inmediatamente anterior a la lista anidada y contar el número de caracteres que aparecen antes del contenido del elemento. Luego escribe ese número de caracteres de espacio frente al elemento de la lista anidada. - -En este ejemplo, puedes agregar un elemento de la lista anidada debajo del elemento de la lista `100. Primer elemento de la lista` con una sangría mínima de cinco espacios para el elemento de la lista anidada, dado que hay cinco caracteres (`100.`) antes del `Primer elemento de la lista`. - -``` -100. Primer elemento de la lista - - Primer elemento de la lista anidada -``` - -![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. - -``` -100. Primer elemento de la lista - - Primer elemento de la lista anidada - - Segundo elemento de la lista anidada -``` - -![Lista con dos niveles de elementos anidados](/assets/images/help/writing/nested-list-example-2.png) - -Para conocer más ejemplos, consulta las [Especificaciones de formato Markdown de GitHub](https://github.github.com/gfm/#example-265). - -### Listas de tareas - -{% data reusables.repositories.task-list-markdown %} - -If a task list item description begins with a parenthesis, you'll need to escape it with `\`: - -`- [ ] \(Optional) Abre una propuesta de seguimiento` - -Para obtener más información, consulta "[Acerca de las listas de tareas](/articles/about-task-lists)". - -### Mencionar personas y equipos - -Puedes mencionar a una persona o [equipo](/articles/setting-up-teams/) en {% data variables.product.product_name %} al escribir `@` más el nombre de usuario o el nombre del equipo. This will trigger a notification and bring their attention to the conversation. Las personas también recibirán una notificación si editas un comentario para mencionar su nombre de usuario o el nombre del equipo. Para obtener más información acerca de las notificaciones, consulta la sección {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[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 %}". - -`@github/support ¿Qué piensas sobre estas actualizaciones?` - -![@mention representado](/assets/images/help/writing/mention-rendered.png) - -Cuando mencionas a un equipo padre, los miembros de los equipos hijo también reciben notificaciones, simplificando la comunicación con múltiples grupos de personas. Para obtener más información, consulta "[Acerca de los equipos](/articles/about-teams)". - -Si escribes un símbolo `@` aparecerá una lista de personas o equipos en el proyecto. La lista filtra a medida que escribes, por lo que una vez que escribes el nombre de la persona o del equipo que estás buscando, puedes usar las teclas de flecha para seleccionarlos y presionar cada pestaña para ingresar para completar el nombre. En el caso de los equipos, escribe el nombre de la @organización/equipo y todos los miembros del equipo que se suscribirán a la conversación. - -Los resultados autocompletados se restringen a los colaboradores del repositorio y a otros participantes en el hilo. - -### Hacer referencia a propuestas y solicitudes de extracción - -Puedes mencionar una lista de las propuestas y las solicitudes de extracción sugeridas dentro del repositorio al escribir `#`. Escribe el número o el título de la propuesta o la solicitud de extracción para filtrar la lista, y luego presiona cada pestaña o ingresa para completar el resultado resaltado. - -Para obtener más información, consulta "[Referencias y direcciones URL autovinculadas](/articles/autolinked-references-and-urls)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -### Hacer referencia a recursos externos - -{% data reusables.repositories.autolink-references %} - -{% endif %} - -### Adjuntos de contenido - -Algunas {% data variables.product.prodname_github_app %} brindan información en {% data variables.product.product_name %} para las URL que se vinculan con 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/help/writing/content-attachment.png) - -Para ver los adjuntos de contenido, debes tener un {% data variables.product.prodname_github_app %} que use la API de los adjuntos de contenido instalada en el repositorio.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta "[Instalar una app en tu cuenta personal](/articles/installing-an-app-in-your-personal-account)" y "[Instalar una app en tu organización](/articles/installing-an-app-in-your-organization)".{% endif %} - -Los adjuntos de contenido no se mostrarán para las URL que son parte de un enlace de Markdown. - -Para obtener más información sobre el desarrollo de una {% data variables.product.prodname_github_app %} que utilice adjuntos de contenido, consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments)". - -### Usar emojis - -Puedes agregar emojis a tu escritura al escribir `:EMOJICODE:`. - -`@octocat :+1: This PR looks great - it's ready to merge! :shipit:` - -![Emoji representado](/assets/images/help/writing/emoji-rendered.png) - -Si escribes `:` aparecerá una lista con los emojis sugeridos. La lista filtrará a medida que escribes; por lo tanto, una vez que encuentres el emoji que estás buscando, presiona **Tab** (Tabulador) o **Enter** (Intro) para completar el resultado resaltado. - -Para conocer una lista completa de los emojis y los códigos disponibles, revisa [emoji-cheat-sheet.com](http://emoji-cheat-sheet.com). - -### Párrafos - -Puedes crear un nuevo párrafo al dejar una línea en blanco entre las líneas de texto. - -### Importar formato de Markdown - -Puedes pedirle a {% data variables.product.product_name %} que ignore (o evada) el formato de Markdown usando la `\` antes del caracter de Markdown. - -`Cambiemos el nombre de \*our-new-project\* a \*our-old-project\*.` - -![Carácter evadido representado](/assets/images/help/writing/escaped-character-rendered.png) - -Para obtener más información, consulta "[Sintaxis de Markdown" de Daring Fireball](https://daringfireball.net/projects/markdown/syntax#backslash), - -### Leer más - -- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) -- "[Acerca de escritura y formato en GitHub](/articles/about-writing-and-formatting-on-github)" -- "[Trabajar con formato avanzado](/articles/working-with-advanced-formatting)" -- "[Dominar Markdown](https://guides.github.com/features/mastering-markdown/)" diff --git a/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md b/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md deleted file mode 100644 index bc0df60144..0000000000 --- a/translations/es-XL/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Introducción a la escritura y el formato en GitHub -redirect_from: - - /articles/markdown-basics/ - - /articles/things-you-can-do-in-a-text-area-on-github/ - - /articles/getting-started-with-writing-and-formatting-on-github -intro: 'Puedes usar características simples para darles formato a tus comentarios e interactuar con otros en propuestas, solicitudes de extracción y wikis en GitHub.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /about-writing-and-formatting-on-github - - /basic-writing-and-formatting-syntax ---- - diff --git a/translations/es-XL/content/github/writing-on-github/index.md b/translations/es-XL/content/github/writing-on-github/index.md deleted file mode 100644 index 16b6b739fc..0000000000 --- a/translations/es-XL/content/github/writing-on-github/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Escribir en GitHub -redirect_from: - - /categories/88/articles/ - - /articles/github-flavored-markdown/ - - /articles/writing-on-github/ - - /categories/writing-on-github -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /getting-started-with-writing-and-formatting-on-github - - /working-with-advanced-formatting - - /working-with-saved-replies - - /editing-and-sharing-content-with-gists ---- -### Índice diff --git a/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md b/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md deleted file mode 100644 index 7c77e26277..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Referencias y direcciones URL autovinculadas -intro: 'Las referencias a las direcciones URL, propuestas, solicitudes de extracción y confirmaciones se acortan automáticamente y se convierten en vínculos.' -redirect_from: - - /articles/autolinked-references-and-urls - - /github/writing-on-github/autolinked-references-and-urls -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Direcciones URL - -{% data variables.product.product_name %} automáticamente crea vínculos desde las direcciones URL estándar. - -`Visita https://github.com` - -![URL autovinculada presentada](/assets/images/help/writing/url-autolink-rendered.png) - -Para obtener información sobre cómo crear vínculos, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax/#links)". - -### Propuestas y solicitudes de extracción - -Dentro de las conversaciones en {% data variables.product.product_name %}, las referencias a las propuestas y solicitudes de extracción se convierten automáticamente en vínculos acortados. Para obtener más información, consulta "[Acerca de las conversaciones en {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)". - -{% note %} - -**Nota:** Las referencias autovinculadas no se crearon en páginas wikis o archivos en un repositorio. - -{% endnote %} - -| Tipo de referencia | Referencia en bruto | Vínculo acortado | -| --------------------------------------------------------------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------- | -| URL de propuesta o solicitud de extracción | https://github.com/jlord/sheetsee.js/issues/26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) | -| `#` y número de propuesta o solicitud de extracción | #26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) | -| `GH` y número de propuesta y solicitud de extracción | GH-26 | [GH-26](https://github.com/jlord/sheetsee.js/issues/26) | -| `Nombre de usuario/N.º de repositorio` y número de propuesta o solicitud de extracción. | jlord/sheetsee.js#26 | [jlord/sheetsee.js#26](https://github.com/jlord/sheetsee.js/issues/26) | -| `Organization_name/Repository#` y número propuesta o solicitud de extracción | github/linguist#4039 | [github/linguist#4039](https://github.com/github/linguist/pull/4039) | - -### Confirmar SHA - -Las referencias a un hash SHA de confirmación se convertirán automáticamente en enlaces acortados para la confirmación en {% data variables.product.product_name %}. - -| Tipo de referencia | Referencia en bruto | Vínculo acortado | -| ----------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | -| URL de confirmación | https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | -| Username/Repository@SHA | User/Repository@SHA: jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord/sheetsee.js@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -### Personalizar enlaces automáticos a recursos externos - -{% data reusables.repositories.autolink-references %} - -{% endif %} - -### Leer más - -- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md deleted file mode 100644 index 77cf0fc861..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Crear y resaltar bloques de código -intro: Compartir muestras de código con bloques de código cercados y habilitar el resaltado de la sintaxis -redirect_from: - - /articles/creating-and-highlighting-code-blocks - - /github/writing-on-github/creating-and-highlighting-code-blocks -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Bloques de código cercados - -Puedes crear bloques de código cercados al colocar comillas simples triples \`\`\` antes y después del bloque de código. Te recomendamos dejar una línea en blanco antes y después de los bloques de código para facilitar la lectura del formato sin procesar. - -
    -```
-function test() {
-  console.log("notice the blank line before this function?");
-}
-```
-
    - -![Bloque de código cercado representado](/assets/images/help/writing/fenced-code-block-rendered.png) - -{% tip %} - -**Sugerencia:** Para preservar tu formato en una lista, asegúrate de dejar una sangría de ocho espacios para los bloques de código no cercados. - -{% endtip %} - -### Resaltado de la sintaxis - -Puedes agregar un identificador opcional de idioma para habilitar el resaltado de la sintaxis en tu bloque de código cercado. - -Por ejemplo, para resaltar la sintaxis del código Ruby: - - ```ruby - require 'redcarpet' - markdown = Redcarpet.new("Hello World!") - puts markdown.to_html - puts markdown.to_html - ``` - -![Bloque de código cercado representado con sintaxis de Ruby resaltada](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png) - -Usamos [Lingüista](https://github.com/github/linguist) para realizar la detección del idioma y seleccionar [gramáticas independientes](https://github.com/github/linguist/blob/master/vendor/README.md) para el resaltado de la sintaxis. Puedes conocer las palabra clave válidas en [el archivo YAML de idiomas](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). - -### Leer más - -- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) -- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/index.md b/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/index.md deleted file mode 100644 index 348b41701e..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/index.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Trabajar con formato avanzado -intro: 'Los formatos como tablas, resaltado de la sintaxis y enlace automático te permiten organizar la información compleja claramente en tus solicitudes de extracción, propuestas y comentarios.' -redirect_from: - - /articles/working-with-advanced-formatting -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /organizing-information-with-tables - - /creating-and-highlighting-code-blocks - - /autolinked-references-and-urls - - /attaching-files - - /creating-a-permanent-link-to-a-code-snippet - - /using-keywords-in-issues-and-pull-requests ---- - diff --git a/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md b/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md deleted file mode 100644 index 6ffe93bbe0..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Organizar la información en tablas -intro: 'Puedes construir tablas para organizar la información en comentarios, propuestas, solicitudes de extracción y wikis.' -redirect_from: - - /articles/organizing-information-with-tables - - /github/writing-on-github/organizing-information-with-tables -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -### Crear una tabla - -Puede crear tablas con barras verticales `|` y guiones `-`. Los guiones se usan para crear el encabezado de cada columna, mientras que las barras verticales separan cada columna. Debes incluir una línea en blanco antes de tu tabla para que se representen correctamente. - -``` - -| Primer encabezado | Segundo encabezado | -| ------------- | ------------- | -| Contenido de la celda | Contenido de la celda | -| Contenido de la celda | Contenido de la celda | -``` - -![Tabla presentada](/assets/images/help/writing/table-basic-rendered.png) - -Las barras verticales en cada lado de la tabla son opcionales. - -Las celdas pueden variar en el ancho y no es necesario que estén perfectamente alineadas dentro de las columnas. Debe haber al menos tres guiones en cada columna de la línea de encabezamiento. - -``` -| Comando | Descripción | -| --- | --- | -| git status | Enumera todos los archivos nuevos o modificados | -| git diff | Muestra las diferencias de archivo que no han sido preparadas | -``` - -![Tabla presentada con ancho de celda variado](/assets/images/help/writing/table-varied-columns-rendered.png) - -### Formatear el contenido dentro de tu tabla - -Puedes utilizar [formato](/articles/basic-writing-and-formatting-syntax) como enlaces, bloques de códigos insertados y el estilo de texto dentro de tu tabla: - -``` -| Comando | Descripción | -| --- | --- | -| `git status` | Enumera todos los archivos *nuevos o modificados* | -| `git diff` | Muestra las diferencias de archivo que **no han sido** preparadas | -``` - -![Tabla presentada con texto formateado](/assets/images/help/writing/table-inline-formatting-rendered.png) - -Puedes alinear el texto a la izquierda, la derecha o en el centro de una columna al incluir dos puntos `:` a la izquierda, la derecha, o en ambos lados de los guiones dentro de la línea de encabezamiento. - -``` -| Alineado a la izquierda | Alineado en el centro | Alineado a la derecha | -| :--- | :---: | ---: | -| git status | git status | git status | -| git diff | git diff | git diff | -``` - -![Tabla presentada con alineación de texto a la izquierda, a la derecha o al centro](/assets/images/help/writing/table-aligned-text-rendered.png) - -Para incluir una barra vertical `|` como contenido dentro de tu celda, utiliza una `\` antes de la barra: - -``` -| Nombre | Símbolo | -| --- | --- | -| Comilla simple | ` | -| Barra vertical | \| | -``` - -![Tabla presentada con una barra vertical liberada](/assets/images/help/writing/table-escaped-character-rendered.png) - -### Leer más - -- [{% data variables.product.prodname_dotcom %} Especificaciones del formato Markdown](https://github.github.com/gfm/) -- [Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)" diff --git a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/about-saved-replies.md b/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/about-saved-replies.md deleted file mode 100644 index 0416957679..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/about-saved-replies.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Acerca de las respuestas guardadas -intro: Puedes usar una respuesta guardada para responder a una propuesta o una solicitud de extracción. -redirect_from: - - /articles/about-saved-replies - - /github/writing-on-github/about-saved-replies -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -![Respuestas guardadas](/assets/images/help/settings/saved-replies.png) - -Las respuestas guardadas te permiten crear una respuesta reusable para las propuestas y las solicitudes de extracción. Ahorra tiempo creando una respuesta guardada para las respuestas que usas con mayor frecuencia. - -Una vez que has agregado una respuesta guardada, se puede usar tanto en las propuestas como en las solicitudes de extracción. Las respuestas guardadas están asociadas a tu cuenta de usuario. Una vez que son creadas, podrás usarlas en todos los repositorios y las organizaciones. - -Puedes crear un máximo de 100 respuestas guardadas. Si has alcanzado el límite máximo, puedes eliminar las respuestas guardadas que ya no usas o editar las respuestas guardadas existentes. - -También puedes usar la respuesta guardada "Duplicar propuesta" proporcionada por {% data variables.product.product_name %} para marcar una propuesta como un duplicado y hacerle un seguimiento con una propuesta similar. - -### Leer más - -- "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" -- "[Usar respuestas guardadas](/articles/using-saved-replies)" -- "[Editar una respuesta guardada](/articles/editing-a-saved-reply)" -- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" diff --git a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md b/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md deleted file mode 100644 index 7cca71c158..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Crear una respuesta guardada -intro: 'Si sueles agregar el mismo comentario una y otra vez, puedes crear una respuesta guardada.' -redirect_from: - - /articles/creating-a-saved-reply - - /github/writing-on-github/creating-a-saved-reply -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.saved_replies %} -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**. ![Agregar una respuesta guardada](/assets/images/help/settings/saved-replies-add-button.png) - -### Leer más - -- "[Usar respuestas guardadas](/articles/using-saved-replies)" -- "[Editar una respuesta guardada](/articles/editing-a-saved-reply)" -- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" diff --git a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/deleting-a-saved-reply.md b/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/deleting-a-saved-reply.md deleted file mode 100644 index 7f3473dc6a..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/deleting-a-saved-reply.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Eliminar una respuesta guardada -intro: 'Si adviertes que ya no usas una respuesta guardada, puedes eliminarla.' -redirect_from: - - /articles/deleting-a-saved-reply - - /github/writing-on-github/deleting-a-saved-reply -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.saved_replies %} -3. En "Respuestas guardadas", junto a la respuesta guardada que deseas eliminar, haz clic en {% octicon "x" aria-label="The X" %}. - ![Eliminar respuesta guardada](/assets/images/help/settings/saved-replies-delete-existing.png) diff --git a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md b/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md deleted file mode 100644 index 67fa2e1f02..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Editar una respuesta guardada -intro: Puedes editar el título y el cuerpo de una respuesta guardada. -redirect_from: - - /articles/changing-a-saved-reply/ - - /articles/editing-a-saved-reply - - /github/writing-on-github/editing-a-saved-reply -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.saved_replies %} -3. En "Respuestas guardadas", junto a la respuesta guardada que deseas editar, haz clic en {% octicon "pencil" aria-label="The pencil" %}. - ![Editar una respuesta guardada](/assets/images/help/settings/saved-replies-edit-existing.png) -4. En "Editar una respuesta guardada", puedes editar el título y el contenido de la respuesta guardada. ![Editar título y contenido](/assets/images/help/settings/saved-replies-edit-existing-content.png) -5. Haz clic en **Actualizar una respuesta guardada**. ![Actualizar una respuesta guardada](/assets/images/help/settings/saved-replies-save-edit.png) - -### Leer más - -- "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" -- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" -- "[Usar respuestas guardadas](/articles/using-saved-replies)" diff --git a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/index.md b/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/index.md deleted file mode 100644 index 53987436bc..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Trabajar con respuestas guardadas -intro: 'Para ahorrar tiempo y asegurarte de enviar un mensaje consistente, puedes agregar respuestas guardadas a las propuestas y los comentarios de la solicitud de extracción.' -redirect_from: - - /articles/working-with-saved-replies -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /about-saved-replies - - /creating-a-saved-reply - - /editing-a-saved-reply - - /deleting-a-saved-reply - - /using-saved-replies ---- - diff --git a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/using-saved-replies.md b/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/using-saved-replies.md deleted file mode 100644 index ebbe10b832..0000000000 --- a/translations/es-XL/content/github/writing-on-github/working-with-saved-replies/using-saved-replies.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Utilizar respuestas guardadas -intro: 'Cuando comentas una propuesta o solicitud de extracción, puedes agregar una respuesta guardada que ya hayas establecido. La respuesta guardada puede ser todo el comentario o, si quieres personalizarlo, puedes agregar o eliminar contenido.' -redirect_from: - - /articles/using-saved-replies - - /github/writing-on-github/using-saved-replies -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -2. Haz clic en la propuesta o solicitud de extracción deseada. -3. Para agregar una respuesta guardada, en el campo de comentarios, haz clic en {% octicon "reply" aria-label="The mail reply" %}. ![Botón Saved replies (Respuestas guardadas)](/assets/images/help/writing/saved-replies-button.png) -4. Desde la lista, selecciona la respuesta guardada que quieres agregar en el comentario. ![Respuestas guardadas](/assets/images/help/settings/saved-replies.png) - -{% tip %} - -**Sugerencias:** -- Puedes utilizar un atajo del teclado para completar automáticamente el comentario con una respuesta guardada. Para obtener más información, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/#comments)". -- Puedes filtrar la lista escribiendo el título de la respuesta guardada. - -{% endtip %} - -### Leer más - -- "[Crear una respuesta guardada](/articles/creating-a-saved-reply)" -- "[Editar una respuesta guardada](/articles/editing-a-saved-reply)" -- "[Eliminar una respuesta guardada](/articles/deleting-a-saved-reply)" diff --git a/translations/es-XL/content/graphql/guides/forming-calls-with-graphql.md b/translations/es-XL/content/graphql/guides/forming-calls-with-graphql.md deleted file mode 100644 index b119ac6a27..0000000000 --- a/translations/es-XL/content/graphql/guides/forming-calls-with-graphql.md +++ /dev/null @@ -1,413 +0,0 @@ ---- -title: Formar llamados con GraphQl -intro: 'Aprende cómo autenticarte en la API de GraphQL, y luego cómo crear y ejecutar consultas y mutaciones.' -redirect_from: - - /v4/guides/forming-calls - - /graphql/guides/forming-calls -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Autenticarse con GraphQL - -Para comunicarte con el servidor de GraphQL, deberás tener un token OAuth con el alcance correcto. - -Sigue los pasos en "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)" para crear un token. Los alcances que requieres dependen del tipo de datos que quieras solicitar. Por ejemplo, selecciona los alcances del **Usuario** para solicitar datos de usuario. Si necesitas acceder a la información de un repositorio, selecciona los alcances de **Repositorio** adecuados. - -{% if currentVersion == "free-pro-team@latest" %} - -Para empatar el comportamiento del [Explorador de GraphQL](/v4/guides/using-the-explorer), solicita los siguientes alcances: - -{% else %} - -Se recomiendan los siguientes alcances: - -{% endif %} - -``` -user -public_repo -repo -repo_deployment -repo:status -read:repo_hook -read:org -read:public_key -read:gpg_key -``` - -La API te notifica si algún recurso requiere de un alcance específico. - -### Terminal de GraphQL - -La API de REST tiene varias terminales; la API de GraphQL solo tiene una terminal: - -
    {% data variables.product.graphql_url_pre %}
    - -La terminal permanece constante sin importar la operación que realices. - -### Comunicarse con GraphQL - -Ya que las operaciones de GraphQL consisten en JSON de línea múltiple, GitHub te recomienda utilizar el [Explorador](/v4/guides/using-the-explorer) para hacer llamados de GraphQL. También puedes utilizar cURL o cualquier otra biblioteca que entienda HTTP. - -En REST, [Los verbos HTTP](/v3/#http-verbs) determinan la operación realizada. En GraphQL, proporcionarás un cuerpo codificado con JSON ya sea que realices una consulta o una mutación, para que el verbo HTTP sea `POST`. La excepción es una [consulta de introspección](/v4/guides/intro-to-graphql#discovering-the-graphql-api), lo cual es un simple `GET` en la terminal. Para obtener más información sobre GraphQL contra REST, consulta la sección "[Migrarse desde REST a GraphQL](/v4/guides/migrating-from-rest)". - -Para consultar GraphQL utilizando cURL, realiza una solicitud de `POST` con una carga útil de JSON. La carga útil deberá contener una cadena llamada `query`: - -```shell -curl -H "Authorization: bearer token" -X POST -d " \ - { \ - \"query\": \"query { viewer { login }}\" \ - } \ -" {% data variables.product.graphql_url_code %} -``` - -{% tip %} - -**Nota**: El valor de cadena de `"query"` deve escaoar caracteres de nueva línea o el modelo no lo analizará correctamente. Para el cuerpo `POST`, utiliza comillas dobles externas y comillas dobles internas escapadas. - -{% endtip %} - -#### Acerca de las operaciones de consulta y mutación - -Los dos tipos de operación permitidos en la API de GraphQL de GitHub son _consultas_ y _mutaciones_. Comparando GraphQL con REST, las consultas operan como solicitudes de tipo `GET`, mientras que las mutaciónes operan como `POST`/`PATCH`/`DELETE`. El [nombre de la mutación](/v4/mutation/) determina qué modificación se llevará a cabo. - -Para obtener información acerca de la limitación de tasas, consulta la sección "[Limitaciones de recursos para GraphQL](/v4/guides/resource-limitations/)". - -Las consultas y mutaciones comparten formatos similares con algunas diferencias importantes. - -#### Acerca de las consultas - -Las consultas de GraphQL devuelven únicamente datos que especificas. Para formar una consulta, debes especificar [campos dentro de campos](/v4/guides/intro-to-graphql#field) (tambien conocidos como _subcampos anidados_) hasta que te devuelva únicamente [escalares](/v4/scalar/). - -Las consultas se estructuran de la siguiente forma: - -
    query {
-  JSON objects to return
-}
    - -Para ver un ejemplo de uso real, consulta "[Ejemplo de consulta](#example-query)". - -#### Acerca de las mutaciones - -Para formar una mutación, debes especificar tres cosas: - -1. _Nombre de la mutación_. El Tipo de modificación que quieres realizar. -2. _Objeto de entrada_. Los datos que quieres enviar al servidor, compuestos de _campos de entrada_. Pásalo como un argumento al nombre de la mutación. -3. _Objeto de la carga útil_. Los datos que quieres retribuir del servidor, compuestos de _campos de devolución_. Pásalos como el cuerpo del nombre de la mutación. - -Las mutaciones se estructuran de la siguiente forma: - -
    mutation {
-  mutationName(input: {MutationNameInput!}) {
-    MutationNamePayload
-}
    - -El objeto de entrada en este ejemplo es `MutationNameInput`, y la carga útil del objeto es `MutationNamePayload`. - -En la referencia de [mutaciones](/v4/mutation/), los _campos de entrada_ listados son los que quieres pasar como el objeto de entrada. Los _campos de devolución_ son lo que pasas como el objeto de carga útil. - -Para ver un ejemplo de uso real, consulta "[Ejemplo de mutación](#example-mutation)". - -### Trabajar con variables - -Las [variables](https://graphql.github.io/learn/queries/#variables) pueden conformar consultas más dinámicas y poderosas, y pueden reducir la complejidad cuando pasas objetos de entrada de las mutaciones. - -{% note %} - -**Nota**: si estás utilizando el explorador, asegúrate de ingresar las variables en el [Panel de Variables de Consulta](/v4/guides/using-the-explorer/#using-the-variable-pane), y no incluyas la palabra `variables` antes del objeto JSON. - -{% endnote %} - -Aquí hay una consulta de ejemplo con una sola variable: - -```graphql -query($number_of_repos:Int!) query($number_of_repos:Int!) { - viewer { - name - repositories(last: $number_of_repos) { - nodes { - name - } - } - } -} -variables { - "number_of_repos": 3 -} -``` - -Hay tres pasos para utilizar las variables: - -1. Definir la variable fuera de la operación en un objeto `variables`: - - ```graphql - variables { - "number_of_repos": 3 - } - ``` - - El objeto debe ser un JSON válido. Este ejemplo muestra una variable de tipo `Int`, pero es posible definir tipos de variable más complejos, tales como los objetos de entrada. También puedes definir variables múltiples aquí. - -2. Pasa la variable a la operación como un argumento: - - ```graphql - query($number_of_repos:Int!){ - ``` - - El argumento es un par de valor-clave, en donde la clave es el _nombre_ que comienza con `$` (por ejemplo, `$number_of_repos`), y el valor es el _tipo_ (por ejemplo, `Int`). Agrega un `!` para indicar si se requiere el tipo. Si has identificado variables múltiples, inclúyelas aquí como argumentos múltiples. - -3. Utiliza la variable dentro de la operación: - - ```graphql - repositories(last: $number_of_repos) { - ``` - - En este ejemplo, sustituimos la variable por la cantidad de repositorios a devolver. Especificamos un tipo en el paso 2, ya que GraphQL requiere de una escritura inflexible. - -Este proceso hace dinámico al argumento de la consulta. Ahora podemos simplemente cambiar el valor en el objeto `variables` y mantener el resto del query tal cual. - -Utilizar variables como argumentos te permite actualizar los valores en el objeto `variables` dinámicamente sin cambiar la consulta. - -### Consulta de ejemplo - -Analicemos una consulta más compleja y pongamos esta información en contexto. - -La siguiente consulta busca el repositorio `octocat/Hello-World`, encuentra los 20 informes de problemas más recientes que se han cerrado, y devuelve el título de cada informe de problemas, la URL, y las primeras 5 etiquetas: - -```graphql -query { - repository(owner:"octocat", name:"Hello-World") { - issues(last:20, states:CLOSED) { - edges { - node { - title - url - labels(first:5) { - edges { - node { - name - } - } - } - } - } - } - } -} -``` - -Analizando la composición línea por línea: - -* `consulta {` - - Ya que queremos leer los dtos del servidor, y no modoficarlo, `query` es la operación raíz. (si no especificas una operación, `query` también es la operación predeterimanda). - -* `repository(owner:"octocat", name:"Hello-World") {` - - Para iniciar la consulta, queremos encontrar un objeto [`repository`](/v4/object/repository/). La validación del modelo indica que este objeto requiere un argumento `owner` y `name`. - -* `issues(last:20, states:CLOSED) {` - - Para explicar que se buscan todos los informes de problemas en el repositorio, llamamos al objeto `issues`. (_Podríamos_ consultar un solo `issue` en un `repository`, pero eso necesitaría que sepamos el número del informe de problemas que queremos se devuelva y proporcionarlo como argumento). - - Algunos detalles acerca del objeto `issues`: - - - Los [docs](/v4/object/repository/) nos dicen que este objeto es del tipo `IssueConnection`. - - La validación del modelo indica que este objeto requiere de una cantidad de resultados `last` o `first` como un argumento, así que proporcionamos `20`. - - Los [docs](/v4/object/repository/) también nos dicen que este objeto acepta un argumento `sttes`, el cual es un enumerador [`IssueState`](/v4/enum/issuestate/) que acepta valores de `OPEN` o `CLOSED`. Para encontrar únicamente los informes de problemas cerrados, le damos a la clave `states` un valor de `CLOSED`. - -* `edges {` - - Sabemos que `issues` es una conexión, ya que tiene el tipo `IssueConnection`. Para devolver datos acerca de los informes de problemas individuales, tenemos que acceder al nodo a través de `edges`. - -* `node {` - - Aquí devolvemos el nodo al final del borde. Los [docs `IssueConnection`](/v4/object/issueconnection) indican que el nodo al final del tipo `IssueConnection` es un objeto `Issue`. - -* Ahora que sabemos que estamos recuperando un objeto `Issue`, podemos ver al [docs](/v4/object/issue) y especificar los campos que queremos recuperar: - - ```graphql - title - url - labels(first:5) { - edges { - node { - name - } - } - } - ``` - - Aquí especificamos los campos `title`, `url`, y `labels` del objeto `Issue`. - - El campo `labels` tiene el tipo [`LabelConnection`](/v4/object/labelconnection/). Así como el con el objeto `issues`, ya que `labels` es una conexión, debemos navegar por sus bordes hacia un nodo conectado: el objeto `label`. En el nodo, podemos especificar los campos del objeto `label` que intentamos recuperar, en este caso, `name`. - -Notarás que ejecutar esta consulta en el repositorio público `Hello-World` de Octocat no recuperará muchas etiquetas. Intenta ejecutarlo en uno de tus propios repositorios que utilice etiquetas, y seguramente verás la diferencia. - -### Mutación de ejemplo - -Las mutaciones a menudo requieren información que solo puedes encontrar si realizas una consulta primero. Este ejemplo muestra dos operaciones: - -1. Una consulta para obtener la ID de un informe de problemas. -2. Una mutación para agregar una reacción de emoji a dicho informe. - -```graphql -query FindIssueID { - repository(owner:"octocat", name:"Hello-World") { - issue(number:349) { - id - } - } -} - -mutation AddReactionToIssue { - addReaction(input:{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}) { - reaction { - content - } - subject { - id - } - } -} -``` - -{% tip %} - -Aunque puedes incluir una consulta y una mutación en la misma ventana del explorador si le das nombres ( en este ejemplo, `FindIssueID` y `AddReactionToIssue`), las operaciones se ejecutará como llamados separados a la terminal de GraphQL. No se puede realizar una consulta al mismo tiempo que una mutación, o viceversa. - -{% endtip %} - -Analicemos el ejemplo. La tarea parece simple: agregar una reacción de emoji a un informe de problemas. - -Así que, ¿qué es lo que sabemos para comenzar con la consulta? Aún no sabemos nada. - -Ya que queremos modificar los datos en el servidor (agregar un emoji a un informe de problemas), comenzamos buscando el modelo para una mutación útil. Los docs de referencia muestran la mutación [`addReaction`](/v4/mutation/addreaction) con la descripción: `Adds a reaction to a subject.`. ¡Perfecto! - -Los documentos para la mutación listan tres campos de entrada: - -* `clientMutationId` (`String`) -* `subjectId` (`ID!`) -* `content` (`ReactionContent!`) - -Los signos `!` indican que `subjectId` y `content` son campos requeridos. Hace sentido que se requiera de un `content`: queremos agregar una reacción, así que necesitaremos especificar qué emoji se utilizará. - -Pero, ¿por qué se requiere la `subjectId`? Esto es porque `subjectId` es la única manera de identificar a _cuál_ informe de problemas en _cuál_ repositorio se reaccionará. - -Es por esto que comenzamos el ejemplo con una consulta: para obtener la `ID`. - -Examinemos la consulta línea por línea: - -* `query FindIssueID {` - - Aquí estamos realizando una consulta, y la nombramos `FindIssueID`. Nota que el nombrar una consulta es opcional; le dimos un nombre para que podamos incluirlo en la misma ventana del explorador que utiliza la mutación. - -* `repository(owner:"octocat", name:"Hello-World") {` - - Especificamos el repositorio consultando el objeto `repository` y pasando los argumentos `owner` y `name`. - -* `issue(number:349) {` - - Especificamos el informe de problemas al cual se reaccionará consultando el objeto `issue` y pasando un argumento `number`. - -* `id` - - Aquí es donde recuperamos la `id` de `https://github.com/octocat/Hello-World/issues/349` para pasar como la `subjectId`. - -Cuando ejecutamos la consulta, obtenemos la `id`: `MDU6SXNzdWUyMzEzOTE1NTE=` - -{% tip %} - -**Nota**: La `id` que se devuelve en la consulta es el valor que pasaremos como la `subjectID` en la mutación. Ni los docs ni la introspección de modelo indicarán esta relación; necesitarás entender los conceptos detrás de los nombres para averiguarla. - -{% endtip %} - -Una vez conociendo la ID, podemos proceder con la mutación: - -* `mutation AddReactionToIssue {` - - Aquí realizamos una mutación, y la nombramos `AddReactionToIssue`. Como con las consultas, nombrar una mutación es opcional; le dimos un nombre para poder incluirlo en la misma ventana del explorador que la consulta. - -* `addReaction(input:{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}) {` - - Examinemos esta línea: - - - `addReaction` es el nombre de la mutación. - - `input` es la clave de argumento requerida. Esto siempre será la `input` para una mutación. - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` es el valor requerido del argumento. Esto siempre será un [objeto de entrada](/v4/input_object/) (de ahí las corcheas) compuesto de campos de entrada (`subjectId` y `content` en este caso) para una mutación. - - ¿Cómo sabemos qué valor utilizar para el contenido? Los [docs `addReaction`](/v4/mutation/addreaction/) nos dicen que el campo `content` es de tipo [`ReactionContent`](/v4/enum/reactioncontent/), lo cual es un [enumerador](/v4/enum) ya que solo ciertas reacciones de emoji son compatibles con los informes de problemas de GitHub. Estos son los valores permitidos para las reacciones (nota que algunos valores son diferentes de sus nombres de emoji correspondientes): - - {% data reusables.repositories.reaction_list %} - -* El resto del llamado se compone del objeto de carga útil. Aquí es donde especificamos los datos que queremos recuperar del servidor después de que realicemos la mutación. Estas líneas vienen de los [docs `AddReaction`](/v4/mutation/addreaction), que tienen tres campos de recuperación posibles: - - - `clientMutationId` (`String`) - - `reaction` (`Reaction!`) - - `subject` (`Reactable!`) - - En este ejemplo, recuperamos los dos campos requeridos (`reaction` y `subject`), ambos de los cuales tienen subcampos requeridos (respectivamente, `content` y `id`). - -Cuando ejecutamos la mutación, esta es la respuesta: - -```json -{ - "data": { - "addReaction": { - "reaction": { - "content": "HOORAY" - }, - "subject": { - "id": "MDU6SXNzdWUyMTc5NTQ0OTc=" - } - } - } -} -``` - -¡Listo! Revisa tu [reacción al informe de problemas](https://github.com/octocat/Hello-World/issues/349) pasando el puntero del mouse sobre :tada: para encontrar tu nombre de usuario. - -Una última nota: cuando pasas varios campos en un objeto de entrada, la sintaxis puede ser difícil de manejar. Mover los campos hacia una [variable](#working-with-variables) puede ayudar. Así es como podrías reescribir la mutación original utilizando una variable: - -```graphql -mutation($myVar:AddReactionInput!) mutation($myVar:AddReactionInput!) { - addReaction(input:$myVar) { - reaction { - content - } - subject { - id - } - } -} -variables { - "myVar": { - "subjectId":"MDU6SXNzdWUyMTc5NTQ0OTc=", - "content":"HOORAY" - } -} -``` - -{% note %} - -Podrás notar que el valor de campo `content` en el ejemplo pasado (en donde se usa directamente en la mutación) no tiene comillas encerrando a `HOORAY`, pero sí las tiene cuando se incluye en la variable. Esto es por una razón: -* Cuando utlilzas `content` directamente en la mutación, el modelo espera que el valor sea de tipo [`ReactionContent`](/v4/enum/reactioncontent/), lo cual es un _enumerador_, no una cadena. La validación del modelo arrojará un error si agregas comillas antes y después del valor de enumerador, ya que éstas están reservadas para las cadenas. -* Cuando utilizas `content` en una variable, la sección de variables debe ser un JSON válido, así que las comillas son necesarias. La validación del modelo interpreta correctamente el tipo `ReactionContent` cuando se pasa la variable a la mutación durante la ejecución. - -Para obtener más información acerca de la diferencia entre enumeradores y cadenas, consulta [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). - -{% endnote %} - -### Leer más - -Puedes hacer mucho _más_ cuando conformes llamados de GraphQL. Aquí hay algunos lugares que te pueden interesar posteriormente: - -* [Paginación](https://graphql.github.io/learn/pagination/) -* [Fragmentos](https://graphql.github.io/learn/queries/#fragments) -* [Fragmentos dentro de líneas](https://graphql.github.io/learn/queries/#inline-fragments) -* [Directivas](https://graphql.github.io/learn/queries/#directives) diff --git a/translations/es-XL/content/graphql/guides/index.md b/translations/es-XL/content/graphql/guides/index.md deleted file mode 100644 index cc7e386951..0000000000 --- a/translations/es-XL/content/graphql/guides/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Guías -intro: 'Aprende sobre como emepzar con GraphQL, migrarte desde REST hacia GraphQL, y cómo utilizar la API de GraphQL de GitHub para tareas diversas.' -redirect_from: - - /v4/guides -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API -children: - - /introduction-to-graphql - - /forming-calls-with-graphql - - /using-global-node-ids - - /migrating-from-rest-to-graphql - - /using-the-explorer - - /managing-enterprise-accounts - - /using-the-graphql-api-for-discussions ---- - diff --git a/translations/es-XL/content/graphql/guides/introduction-to-graphql.md b/translations/es-XL/content/graphql/guides/introduction-to-graphql.md deleted file mode 100644 index 906673c9c9..0000000000 --- a/translations/es-XL/content/graphql/guides/introduction-to-graphql.md +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Introducción a GraphQL -intro: Aprende terminología y conceptos útiles para utilizar la API de GraphQL de GitHub. -redirect_from: - - /v4/guides/intro-to-graphql - - /graphql/guides/intro-to-graphql -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Terminología de GraphQL - -La API de GraphQL de GitHub representa un cambio conceptual y arquitectónico de la API de REST de GitHub. Seguramente encontrarás nueva terminología en los [documentos de referencia](/v4/) de la API de GraphQL. - -### Modelo - -Un modelo define un tipo de sistema de la API de GraphQL. Describe el conjunto de datos posibles (objetos, campos, relaciones, todo) a los que puede acceder un cliente. Los llamados desde el cliente se [validan](https://graphql.github.io/learn/validation/) y [ejecutan](https://graphql.github.io/learn/execution/) contra un modelo. Un cliente puede encontrar información acerca del modelo a través de [introspección](#discovering-the-graphql-api). UN modelo reside en el servidor de la API de GraphQL. Para obtener más información, consulta la sección "[Descubriendo la API de GraphQL](#discovering-the-graphql-api)". - -### Campo - -Un campo es una unidad de datos que puedes recuperar de un objeto. Como dicen los [documentos oficiales de GraphQL](https://graphql.github.io/learn/schema/): "El lenguaje de consulta GraphQL se trata básicamente de seleccionar campos en los objetos". - -Las [especificaciones oficiales](https://graphql.github.io/graphql-spec/June2018/#sec-Language.Fields) dicen también acerca de los campos: - -> Todas las operaciones de GraphQL deben especificar sus selecciones en campos que regresarán valores escalares para garantizar una respuesta conformada sin ambigüedad. - -Esto significa que si intentas recuperar un campo que no es un valor escalar, la validación del modelo arrojará un error. Debes agregar subcampos anidados hasta que todos los campos recuperen valores escalares. - -### Argumento - -Un argumento es un conjuto de pares clave-valor adjuntos a un campo específico. Algunos campos requieren un argumento. Las [mutaciones](/v4/guides/forming-calls#about-mutations) requieren un objeto de entrada como argumento. - -### Implementación - -El modelo de GraphQL podría utilizar el término _implementa_ para definir cómo un objeto hereda de una [interface](/v4/interface). - -Aquí se muestra un ejemplo artificial de un modelo que define la interface `X` y el objeto `Y`: - -``` -interface X { - some_field: String! - other_field: String! -} - -type Y implements X { - some_field: String! - other_field: String! - new_field: String! -} -``` - -Esto significa que el objeto `Y` requiere los mismos tipos de campos/argumentos/recuperaciones que requiere la interface `X`, mientras que agregan nuevos campos específicos para el objeto `Y`. (El signo `!` significa que el campo es requerido). - -En los documentos de referencia, podrás notar que: - -* Cada [object](/v4/objeto) lista la(s) interface(s) _desde las cuales hereda_ obajo **Implementaciones**. - -* Cada [interface](/v4/interface) lista los objetos _que heredan desde ella_ bajo **Implementaciones**. - -### Conexión - -Las conexiones permiten consultar objetos relacionados como parte del mismo llamado. Con las conexiones, puedes utilizar un solo llamado de GraphQL y, en contraste, tendrías que utilizar múltiples llamados en una API de REST. Para obtener más información, consulta "[Migrar de REST a GraphQL](/v4/guides/migrating-from-rest)". - -Es útil imaginar una gráfica: puntos conectados con líneas. Los puntos son nodos, las líneas son bordes. Una conexión define una relación entre nodos. - -### Borde - -Los bordes representan las conexiones entre nodos. Cuando consultas una conexión, cruzas sus bordes para obtener sus nodos. Cada campo de `edges` tiene un campo de `node` y uno de `cursor`. Los cursores se utilizan para la [paginación](https://graphql.github.io/learn/pagination/). - -### Node - -_Nodo_ es un término genérico para un objeto. Puedes buscar un nodo directamente, o puedes acceder a nodos relacionados a través de una conexión. Si especificas un `node` que no regrese un valor [escalar](/v4/scalar), deberás incluir los subcampos hasta que todos los campos recuperen valores escalares. Para obtener información sobre el acceso a las ID de los nodos a través de la API de REST y utilizarlos en las consultas de GraphQL, consulta la sección "[Utilizar ID de Nodos Globales](/v4/guides/using-global-node-ids)". - -## Descubrir la API de GraphQL - -GraphQL es [introspectivo](https://graphql.github.io/learn/introspection/). Esto significa que puedes consultar un modelo de GraphQL para encontrar detalles de éste mismo. - -* Consulta `__schema` para listar todos los tipos definidos en el modelo y obtener detalles de cada uno: - - ```graphql -query { - __schema { - types { - name - kind - description - fields { - name - } - } - } -} - ``` - -* Consulta `__type` para obtener detalles de cualquier tipo: - - ```graphql -query { - __type(name: "Repository") { - name - kind - description - fields { - name - } - } -} - ``` - -* También puedes ejecutar una _consulta de introspección_ del modelo a través de la solicitud `GET`: - - ```shell - $ curl -H "Authorization: bearer token" {% data variables.product.graphql_url_pre %} - ``` - - Estos resultados están en JSON, así que recomendamos imprimirlos notablemente para su lectura y búsqueda más fácil. Puedes utilizar una herramienta de línea de comandos como [jq](https://stedolan.github.io/jq/) o enlazar los resultados en `python -m json.tool` para lograrlo. - - Como alternativa, puedes pasar el tipo de medios `idl` para recuperar los resultados en formato IDL, el cual es una versión condensada del mismo modelo: - - ```shell - $ curl -H "Authorization: bearer token" -H "Accept: application/vnd.github.v4.idl" \ - {% data variables.product.graphql_url_pre %} - ``` - - {% note %} - - **Nota**: La consulta de introspección probablemente es la única solicitud de tipo `GET` que ejecutarás en GraphQL. Si estás pasando un cuerpo, el método de solicitud de GraphQL es de tipo `POST`, ya sea para consultas o mutaciones. - - {% endnote %} - - Para obtener más información acerca de realizar consultas, consulta la sección "[Formar llamados con GraphQL](/v4/guides/forming-calls)". diff --git a/translations/es-XL/content/graphql/guides/managing-enterprise-accounts.md b/translations/es-XL/content/graphql/guides/managing-enterprise-accounts.md deleted file mode 100644 index a3c85c4849..0000000000 --- a/translations/es-XL/content/graphql/guides/managing-enterprise-accounts.md +++ /dev/null @@ -1,200 +0,0 @@ ---- -title: Administrar cuentas empresariales -intro: Puedes administrar tu cuenta empresarial y las organizaciones que le pertenecen con la API de GraphQL. -redirect_from: - - /v4/guides/managing-enterprise-accounts -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de administrar cuentas empresariales con GraphQL - -Para ayudarte a monitorear y hacer cambios en tu organización y mantener el cumplimiento, puedes utilizar la API de Cuentas Empresariales y la API de Bitácoras de Auditoría, las cuales se encuentran disponibles únicamente como API de GraphQL. - -Las terminales de cuenta empresarial funcionan tanto para GitHub Enterprise Cloud y GitHub Enterprise Server. - -GraphQL te permite solicitar y recuperar únicamente los datos que especificas. Por ejemplo, puedes crear una consulta de GraphQL, o hacer una solicitud de información, para ver todos los nuevos miembros que se agregaron a tu organización. O puedes hacer una mutación, o cambio, para invitar a un administrador a tu cuenta empresarial. - -Con la API de Bitácoras de Auditoria, puedes monitorear cuando alguien: -- Accede a tu configuración de organización o de repositorio. -- Cambia los permisos. -- Agrega o elimina usuarios en una organización, repositorio, o equipo. -- Promueve algún usuario a administrador. -- Cambia los permisos de GitHub App. - -La API de Bitácoras de Auditoría te permite mantener las copias de tus datos de bitácoras de auditoria. Para las consultas realizadas con la API de Bitácoras de Auditoria, la respuesta de GraphQL puede incluir datos de hasta 90 a 120 días. Para encontrar una lista de los campos disponibles con la API de Bitácoras de Auditoria, consulta la "[interface AuditEntry](/v4/interface/auditentry/)". - -Con la API de Cuentas Empresariales puedes: -- Listar y revisar todas las organizaciones y repositorios que pertenecen a tu cuenta empresarial. -- Cambiar la configuración de la cuenta empresarial. -- Configurar políticas para la configuración en tu cuenta empresarial y sus organizaciones. -- Invitar administradores a tu cuenta empresarial. -- Crear nuevas organizaciones en tu cuenta empresarial. - -Para encontrar una lista de los campos disponibles con la API de Cuentas Empresariales, consulta "[Campos y tipos de GraphQL para la API de cuenta empresarial](/v4/guides/managing-enterprise-accounts/#graphql-fields-and-types-for-the-enterprise-accounts-api)". - -### Comenzar a utilizar GraphQL para cuentas empresariales - -Sigue estos pasos para comenzar a utilizar GraphQL para administrar tus cuentas empresariales: - - Autenticando con un token de acceso personal - - Elegir un cliente de GraphQL o utilizar el Explorador de GraphQL - - Configurar Insomnia para utilizar la API de GraphQL - -Para encontrar algunas consultas de ejemplo, visita la sección "[Una consulta de ejemplo utilizando la API de Cuentas Empresariales](#an-example-query-using-the-enterprise-accounts-api)". - -#### 1. Autenticarte con tu token de acceso personal - -1. Para autenticarte con GraphQL, necesitas generar un token de acceso personal (PAT) desde la configuración de desarrollador. 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)". - -2. Porporciona permisos de control total a tu token de acceso personal para las áreas de GHES a las que quisieras acceder. Para tener permiso total a los repositorios privados, organizaciones, equipos, datos de usuario y acceso a la facturación empresarial y datos de perfil, te recomendamos que selecciones estos alcances para tu token de acceso persoanal: - - `repo` - - `admin:org` - - `usuario` - - `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. - - `read:enterprise`: Lee datos del perfil empresarial. - - ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/permissions-for-access-token.png) - -4. Copia tu token de acceso personal y mantenlo en un lugar seguro hasta que lo agregues a tu cliente de GraphQL. - -#### 2. Elige un cliente de GraphQL - -Te recomendamos utilizar GraphiQL u otro cliente independiente de GraphQL que te permita configurar la URL base. - -También podrás considerar utilizar estos clientes de GraphQL: - - [Insomnia](https://insomnia.rest/graphql/) - - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/) - - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/) - -Los siguientes pasos utilizarán Insomnia. - -#### 3. Configurar Insomnia para utilizar la API de GraphQL de GitHub con cuentas empresariales - -1. Agrega la url base y el método `POST` a tu cliente de GraphQL. Cuando utilices GraphQL para solicitar información (consultas), cambiar información (mutaciones), o transferir datos utilizando la API de GitHub, el método HTTP predeterminado es `POST` y la url base sigue esta sintaxis: - - Para tu instancia empresarial: `https:///api/graphql` - - Para GitHub Enterprise Cloud: `https://api.github.com/graphql` - -2. Para autenticarte, abre el menú de opciones de autenticación y selecciona **Token titular**. A continuación, agrega tu token de acceso personal, el cual habías copiado. - - ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/insomnia-base-url-and-pat.png) - - ![Opciones de permisos para el token de acceso personal](/assets/images/developer/graphql/insomnia-bearer-token-option.png) - -3. Incluye la información del encabezado. - - Agrega `Content-Type` como el encabezado y `application/json` como el valor. ![Encabezado estándar](/assets/images/developer/graphql/json-content-type-header.png) ![Encabezado con valor de vista previa para la API de Bitácoras de Auditoría](/assets/images/developer/graphql/preview-header-for-2.18.png) - -Ahora estás listo para comenzar a hacer consultas. - -### Un ejemplo de consulta utilizando la API de Cuentas Empresariales - -Esta consulta de GraphQL solicita la cantidad total de repositorios `public` en cada una de las organizaciones de tus aplicativos utilizando la API de cuentas empresariales. Para personalizar esta consulta, reemplaza `` con el slug de tu instancia empresarial. - -```graphql -query publicRepositoriesByOrganization { - organizationOneAlias: organization(login: "") { - # How to use a fragment - ...repositories - } - organizationTwoAlias: organization(login: "") { - ...repositories - } - # organizationThreeAlias ... and so on up-to lets say 100 -} -# How to define a fragment -fragment repositories on Organization { - name - repositories(privacy: PUBLIC){ - totalCount - } -} -``` - -La siguiente consulta de GraphQL muestra lo retador que es recuperar la cantidad de repositorios `public` en cada organización sin utilizar la API de Cuenta Empresarial. Nota que la API de Cuentas Empresariales de GraphQL ha hecho esta tarea más simple para las empresas, ya que solo necesitas personalizar una sola variable. Para personalizar esta consulta, reemplaza `` y ``, etc. con los nombres de organización en tu instancia. - -```graphql -# Each organization is queried separately -{ - organizationOneAlias: organization(login: "nameOfOrganizationOne") { - # How to use a fragment - ...repositories - } - organizationTwoAlias: organization(login: "nameOfOrganizationTwo") { - ...repositories - } - # organizationThreeAlias ... and so on up-to lets say 100 -} - -## How to define a fragment -fragment repositories on Organization { - name - repositories(privacy: PUBLIC){ - totalCount - } -} -``` - -### Consulta a cada organización por separado - -```graphql -query publicRepositoriesByOrganization { - organizationOneAlias: organization(login: "") { - # How to use a fragment - ...repositories - } - organizationTwoAlias: organization(login: "") { - ...repositories - } - # organizationThreeAlias ... and so on up-to lets say 100 -} -# How to define a fragment -fragment repositories on Organization { - name - repositories(privacy: PUBLIC){ - totalCount - } -} -``` - -Esta consulta de GraphQL solicita las últimas 5 entradas de bitácora para una organización empresarial. Para personalizar este query, reemplaza `` y ``. - -```graphql -{ - organization(login: "") { - auditLog(last: 5, query: "actor:") { - edges { - node { - ... on AuditEntry { -# Get Audit Log Entry by 'Action' - action - actorLogin - createdAt -# User 'Action' was performed on - user{ - name - email - } - } - } - } - } - } -} -``` - -Para obtener más información acerca de cómo comenzar con GraphQL, consulta las secciónes "[Introducción a GraphQL](/v4/guides/intro-to-graphql/)" y "[Formar Llamados con GraphQL](/v4/guides/forming-calls/)". - -### Campos y tipos de GraphQL para la API de Cuentas Empresariales - -Aquí tienes un resumen de las nuevas consultas, mutaciones y tipos definidos por modelos disponibles para utilizarse con la API de Cuentas Empresariales. - -Para obtener más detalles acerca de las nuevas consultas, mutaciones y tipos definidos por modelos disponibles para utilizarse con la API de Cuentas Empresariales, observa la barra lateral con las definiciones detalladas de GraphQL desde cualquier [página de referencia de GraphQL](/v4/). - -Puedes acceder a los documentos de referencia desde dentro del explorador de GraphQL en GitHub. Para obtener más información, consulta la sección "[Utilizar el explorador](/v4/guides/using-the-explorer#accessing-the-sidebar-docs)". Para obtener otro tipo de información, tal como los detalles de autenticación y el límite de tasas, revisa las [guías](/v4/guides). diff --git a/translations/es-XL/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/es-XL/content/graphql/guides/migrating-from-rest-to-graphql.md deleted file mode 100644 index b9a9ca090f..0000000000 --- a/translations/es-XL/content/graphql/guides/migrating-from-rest-to-graphql.md +++ /dev/null @@ -1,211 +0,0 @@ ---- -title: Migrar desde Rest hacia GraphQL -intro: 'Aprende las mejores prácticas y consideraciones para migrar desde la API de Rest de {% data variables.product.prodname_dotcom %} hacia la API de GrpahQL de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /v4/guides/migrating-from-rest - - /graphql/guides/migrating-from-rest -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Diferencias en la lógica de la API - -Migrar desde Rest hacia GraphQL represente un cambio significativo en la lógica de las API. Las diferencias entre REST como un estilo y GraphQL como una especificación hacen difícil —y a menudo indeseable— reemplazar los llamados de la API de REST con las consultas de la API de GraphQL de una forma uno a uno. Hemos incluido ejemplos específicos de migración a continuación. - -Para migrar tu código desde la [API de REST](/v3) hacia la API de GraphQL: - -- Revisa las [especificaciones de GraphQL](https://graphql.github.io/graphql-spec/June2018/) -- Revisa el [modelo de GraphQL](/v4/reference/) de Github -- Considera la manera en la que cualquier código existente que tengas interactúa con la API de REST de GitHub -- Utiliza [Las ID de Nodo Global](/v4/guides/using-global-node-ids) para referenciar objetos entre versiones de API - -Las ventajas significativas de GraphQL incluyen: - -- [Obtener los datos que necesitas y únicamente eso](#example-getting-the-data-you-need-and-nothing-more) -- [Campos anidados](#example-nesting) -- [Escritura inflexible](#example-strong-typing) - -Aquí hay algunos ejemplos de cada una. - -## Ejemplo: obtener los datos que necesitas y únicamente eso - -Una sola llamada de la API de REST recupera una lista de los miembros de tu organización: -```shell -curl -v {% data variables.product.api_url_pre %}/orgs/:org/members -``` - -La carga útil de REST contiene datos en exceso si tu meta es recuperar únicamente los nombres y enlaces a los avatares. Sin embargo, la consulta de GraphQL recupera únicamente lo que especificas: - -```graphql -query { - organization(login:"github") { - membersWithRole(first: 100) { - edges { - node { - name - avatarUrl - } - } - } - } -} -``` - -Considera otro ejemplo: recuperar una lista de solicitudes de extracción y revisar si cada una es fusionable. Un llamado a la API de REST recupera un listado de solicitudes de extracción y sus [resúmenes de representación](/v3/#summary-representations): -```shell -curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls -``` - -El determinar si una solicitud de extracción es fusionable requiere que recuperes cada solicitud individualmente de acuerdo con su [representación detallada](/v3/#detailed-representations) (una carga útil grande) y que revises si el atributo `mergeable` es verdadero o falso: -```shell -curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number -``` - -Con GraphQL, puedes recuperar únicamente los atributos `number` y `mergeable` para cada solicitud de extracción: - -```graphql -query { - repository(owner:"octocat", name:"Hello-World") { - pullRequests(last: 10) { - edges { - node { - number - mergeable - } - } - } - } -} -``` - -## Ejemplo: Anidar - -Hacer consultas con campos anidados te permite reemplazar varios llamados de REST con menos consultas de GraphQL. Por ejemplo, recuperar una solicitud de extracción junto con sus confirmaciones, comentarios no revisados, y revisiones utilizando la **API de REST** requiere de cuatro llamados por separado: -```shell -curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number -curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number/commits -curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/issues/:number/comments -curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number/reviews -``` - -Utilizando la **API de GraphQL**, puedes recuperar los datos con una sola consulta utilizando los campos anidados: - -```graphql -{ - repository(owner: "octocat", name: "Hello-World") { - pullRequest(number: 1) { - commits(first: 10) { - edges { - node { - commit { - oid - message - } - } - } - } - comments(first: 10) { - edges { - node { - body - author { - login - } - } - } - } - reviews(first: 10) { - edges { - node { - state - } - } - } - } - } -} -``` - -También puedes extender la capacidad de esta consulta si [sustituyes una variable](/v4/guides/forming-calls/#working-with-variables) para el número de la solicitud de extracción. - -## Ejemplo: Escritura inflexible - -Los modelos de GraphQL tienen una escritura inflexible, lo cual hace más seguro el manejo de los datos. - -Considera como ejemplo agregar un comentario a un informe de problemas o solicitud de extracción utilizando una [mutación](/v4/mutation) de GraphQL, y por error, especificar un integral en vez de una cadena para el valor de [`clientMutationId`](/v4/mutation/addcomment/): - -```graphql -mutation { - addComment(input:{clientMutationId: 1234, subjectId: "MDA6SXNzdWUyMjcyMDA2MTT=", body: "Looks good to me!"}) "Looks good to me!"}) { - clientMutationId - commentEdge { - node { - body - repository { - id - name - nameWithOwner - } - issue { - number - } - } - } - } -} -``` - -Ejecutar esta consulta recuperará errores que especificarán los tipos esperados para esta operación: - -```json -{ - "data": null, - "errors": [ - { - "message": "Argument 'input' on Field 'addComment' has an invalid value. Expected type 'AddCommentInput!'.", - "locations": [ - { - "line": 3, - "column": 3 - } - ] - }, - { - "message": "Argument 'clientMutationId' on InputObject 'AddCommentInput' has an invalid value. Expected type 'String'.", - "locations": [ - { - "line": 3, - "column": 20 - } - ] - } - ] -} -``` - -Poner comillas en `1234` transformará el valor de un integral al de una cadena, el tipo esperado: - -```graphql -mutation { - addComment(input:{clientMutationId: "1234", subjectId: "MDA6SXNzdWUyMjcyMDA2MTT=", body: "Looks good to me!"}) { - clientMutationId - commentEdge { - node { - body - repository { - id - name - nameWithOwner - } - issue { - number - } - } - } - } -} -``` diff --git a/translations/es-XL/content/graphql/guides/using-global-node-ids.md b/translations/es-XL/content/graphql/guides/using-global-node-ids.md deleted file mode 100644 index 81827b3797..0000000000 --- a/translations/es-XL/content/graphql/guides/using-global-node-ids.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -title: Utilizar las ID de nodo global -intro: Puedes obtener ID de nodo global de objetos a través de la API de REST y utilizarlos en operaciones de GraphQL. -redirect_from: - - /v4/guides/using-global-node-ids -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -Puedes acceder a la mayoría de objetos en GitHub (usuarios, informes de problemas, solicitudes de extracción, etc.) utilizando ya sea la API de Rest o la de GraphQL. Con una [actualización reciente](https://developer.github.com/changes/2017-12-19-graphql-node-id/), puedes encontrar la **ID de nodo global** de muchos objetos desde dentro de la API de REST y utilizar estas ID en tus operaciones de GraphQL. - -{% note %} - -**Nota:** en REST, el campo de ID de nodo global se llama `node_id`. En GraphQL, es un campo de `id` en la interface del `node`. Para repasar lo que significa "nodo" en GraphQL, consulta la sección "[Introducción a GraphQL](/v4/guides/intro-to-graphql/#node)". - -{% endnote %} - -### Darle uso a las ID de nodo global - -Puedes seguir estos tres pasos para utilizar las ID de nodo global efectivamente: - -1. Llama a una terminal de REST que recupere el `node_id` de un objeto. -2. Encuentra el tipo del objeto en GraphQL. -3. Utiliza la ID y tipo para hacer una búsqueda directa de nodo en GraphQL. - -Revisemos un ejemplo. - -### 1. Llama a una terminal de REST que recupere la ID de nodo de un objeto - -Si [solicitas el usuario autenticado](/v3/users/#get-the-authenticated-user): - -```shell -$ curl -i -u username:token {% data variables.product.api_url_pre %}/user -``` - -obtendrás una respuesta que incluye el `node_id` del usuario autenticado: - -```json -{ - "login": "octocat", - "id": 1, - "avatar_url": "https://github.com/images/error/octocat_happy.gif", - "gravatar_id": "", - "url": "https://api.github.com/users/octocat", - "html_url": "https://github.com/octocat", - "followers_url": "https://api.github.com/users/octocat/followers", - "following_url": "https://api.github.com/users/octocat/following{/other_user}", - "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}", - "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}", - "subscriptions_url": "https://api.github.com/users/octocat/subscriptions", - "organizations_url": "https://api.github.com/users/octocat/orgs", - "repos_url": "https://api.github.com/users/octocat/repos", - "events_url": "https://api.github.com/users/octocat/events{/privacy}", - "received_events_url": "https://api.github.com/users/octocat/received_events", - "type": "User", - "site_admin": false, - "name": "monalisa octocat", - "company": "GitHub", - "blog": "https://github.com/blog", - "location": "San Francisco", - "email": "octocat@github.com", - "hireable": false, - "bio": "There once was...", - "public_repos": 2, - "public_gists": 1, - "followers": 20, - "following": 0, - "created_at": "2008-01-14T04:33:35Z", - "updated_at": "2008-01-14T04:33:35Z", - "private_gists": 81, - "total_private_repos": 100, - "owned_private_repos": 100, - "disk_usage": 10000, - "collaborators": 8, - "two_factor_authentication": true, - "plan": { - "name": "Medium", - "space": 400, - "private_repos": 20, - "collaborators": 0 - }, - "node_id": "MDQ6VXNlcjU4MzIzMQ==" -} -``` - -### 2. Encuentra el tipo de objeto en GraphQL - -En este ejemplo, el valor de `node_id` es `MDQ6VXNlcjU4MzIzMQ==`. Puedes utilizar este valor para consultar el mismo objeto en GraphQL. - -Aunque necesitas saber el _tipo_ del objeto primero. Puedes revisar el tipo con una consulta simple de GraphQl: - -```graphql -query { - node(id:"MDQ6VXNlcjU4MzIzMQ==") { - __typename - } -} -``` - -Este tipo de consulta —que es encontrar el nodo por ID— se conoce como "búsqueda directa de nodo". - -Cuando ejecutas esta consulta, encontrarás que el `__typename` es [`User`](/v4/object/user/). - -### 3. Haz una búsqueda directa de nodo en GraphQL - -Una vez que hayas confirmado el tipo, puedes utilizar un [fragmento dentro de la línea](https://graphql.github.io/learn/queries/#inline-fragments) para acceder al objeto por su ID y recuperar datos adicionales. En este ejemplo, definimos los campos que queremos consultar en `User`: - -```graphql -query { - node(id:"MDQ6VXNlcjU4MzIzMQ==") { - ... on User { - name - login - } - } -} -``` - -Este tipo de consulta es el acercamiento estándar para buscar un objeto por su ID de nodo global. - -### Utilizar las ID de nodo global en migraciones - -Cuando construyes integraciones que utilizan ya sea la API de REST o de GraphQL, la mejor práctica es persistir la ID de nodo global para que puedas referenciar fácilmente los objetos a través de las versiones de las API. Para obtener más información sobre cómo llevar a cabo la transición entre REST y GraphQL, consulta la sección "[Migrar de REST a GraphQL](/v4/guides/migrating-from-rest/)". diff --git a/translations/es-XL/content/graphql/guides/using-the-explorer.md b/translations/es-XL/content/graphql/guides/using-the-explorer.md deleted file mode 100644 index 11e2f5a570..0000000000 --- a/translations/es-XL/content/graphql/guides/using-the-explorer.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -title: Utilizar el Explorador -intro: 'Puedes ejecutar consultas en datos reales de {% data variables.product.prodname_dotcom %} utilizando el explorador de GraphQL, un ambiente de desarrollo integrado en tu buscador que incluye documentos, sintaxis resaltada y errores de validación.' -redirect_from: - - /v4/guides/using-the-explorer -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -## Acerca del explorador de GraphQL - -{% if currentVersion == "free-pro-team@latest" %} - -El [Explorador de GraphQL](/v4/explorer) es una instancia de [GraphQL](https://github.com/graphql/graphiql), la cual es una "IDE de GraphQL gráfica e interactiva en el mismo buscador". - -{% note %} - -**Nota**: {% data variables.product.prodname_dotcom %} ha inhabilitado las [mutaciones](/v4/mutation/) en el explorador, pero puedes utilizarlas en tu propia instancia de GraphiQL. - -{% endnote %} - -{% else %} - -[GraphiQL](https://github.com/graphql/graphiql), también mencionado en esta documentación como el explorador de GraphQL, es una "IDE de GraphQL gráfica e interactiva en el mismo buscador". - -{% endif %} - -### Utilizar GrpahiQL - -Para utilizar la app de GraphiQL, descárgala e instálala desde https://github.com/skevy/graphiql-app. - -#### Configurar GraphiQL - -1. Obtén un [token de OAuth](/v4/guides/forming-calls#authenticating-with-graphql). -1. Lanzar GraphiQL. -1. En la esquina superior derecha de GraphiQL, da clic en **Editar Encabezados de HTTP**. -1. En el campo **Clave**, ingresa `Authorization`. En el campo **Valor**, ingresa `Bearer `, en donde `` es tu token de OAuth generado. ![encabezados de graphiql](/assets/images/developer/graphiql-headers.png) -1. Da clic en la casilla a la derecha del token para guardarlo. -1. Para gregresar al editor, da clic fuera de el modo **Editar Encabezados de HTTP**. -1. En el campo **Terminal GraphQL** ingresa `{% data variables.product.graphql_url_pre %}`. -1. En el menú desplegable **Método**, selecciona **POST**. - -{% note %} - -**Nota**: Para obtener más información acerca del porqué `POST` es el método, consulta la sección "[Comunicarse con GraphQL](/v4/guides/forming-calls#communicating-with-graphql)". - -{% endnote %} - -Puedes probar tu acceso si te consultas a ti mismo: - -```graphql -query { - viewer { - login - } -} -``` - -Si todo funcionó correctamente, esto mostrará tu ingreso. Estás listo para comenzar a hacer consultas. - -### Acceder a los documentos de la barra lateral - -Todos los tipos en el modelo de GraphQL incluyen un campo de `description` compilado en la documentación. El pánel retráctil **Docs** en el costado derecho de la página del explorador te permite buscar documentación acerca de tu tipo de sistema. Los documentos se actualizan automáticamente y eliminarán los campos obsoletos. - -{% note %} - -La barra lateral de **Docs** tiene el mismo contenido que se genera automáticamente del modelo bajo "[Referencia](/v4/)", aunque con diferente formato en algunas partes. - -{% endnote %} - -### Utilizar el pánel de variable - -Algunos llamados de ejemplo incluyen [variables](/v4/guides/forming-calls#working-with-variables) escritas como éstas: - -```graphql -query($number_of_repos:Int!){ - viewer { - name - repositories(last: $number_of_repos) { - nodes { - name - } - } - } -} -variables { - "number_of_repos": 3 -} -``` - -Este es el formato correcto para emitir la llamada a través de `POST` en cURL (mientras que [escapes las líneas nuevas](/v4/guides/forming-calls#communicating-with-graphql)). - -Si quieres ejecutar la llamada en el explorador, ingresa el segmento `query` en el panel principal y las variables en el panel de **Variables de Consulta** debajo de éste. Omite la palabra `variables` en el explorador: - -```graphql -{ - "number_of_repos": 3 -} -``` - -### Solicitar soporte - -{% data reusables.support.help_resources %} - -### Solución de errores - -Ya que GraphQL es [introspectivo](/v4/guides/intro-to-graphql#discovering-the-graphql-api), el explorador soporta: - -* Autocompleción inteligente consciente del modelo actual -* Vistas previas de validación de errores mientras tecleas - -Si ingresas una consulta que no esté bien estructurada o no pase el [modelo de validación](/v4/guides/intro-to-graphql#schema), un mensaje emergente te avisará de un error. Si ejecutas la consulta, el error se devolverá en el panel de respuesta. - -Una respuesta de GraphQL contiene varias claves: un hash de `data` y un arreglo de `errors`. - -```json -{ - "data": null, - "errors": [ - { - "message": "Objects must have selections (field 'nodes' returns Repository but has no selections)", - "locations": [ - { - "line": 5, - "column": 8 - } - ] - } - ] -} -``` - -Es posible que te encuentres con un error inesperado que no está relacionado con el modelo. Si esto pasa, el mensaje incluirá el código de referencia que puedes utilizar cuando reportas el problema: - -```json -{ - "data": null, - "errors": [ - { - "message": "Something went wrong while executing your query. Es muy probable que esto sea un error de GitHub. Please include \"7571:3FF6:552G94B:69F45B7:5913BBEQ\" when reporting this issue." - } - ] -} -``` - -{% note %} - -**Nota:** {% data variables.product.prodname_dotcom %} recomienda que revises si hay errores antes de utilizar datos en un ambiente productivo. En GraphQL, la falla no es total: algunas porciones de las consultas de GraphQL pueden tener éxito y otras pueden fallar. - -{% endnote %} diff --git a/translations/es-XL/content/graphql/index.md b/translations/es-XL/content/graphql/index.md deleted file mode 100644 index e20c6cba62..0000000000 --- a/translations/es-XL/content/graphql/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: API de GraphQL de GitHub -intro: 'Puedes utilizar la API de GraphQL de {% data variables.product.prodname_dotcom %} para crear consultas precisas y flexibles para los datos que necesitas integrar con {% data variables.product.prodname_dotcom %}.' -shortTitle: API de GraphQL -redirect_from: - - /v4 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /overview - - /reference - - /guides ---- - diff --git a/translations/es-XL/content/graphql/overview/about-the-graphql-api.md b/translations/es-XL/content/graphql/overview/about-the-graphql-api.md deleted file mode 100644 index 57a2436c0c..0000000000 --- a/translations/es-XL/content/graphql/overview/about-the-graphql-api.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Acerca de la API de GraphQL -intro: 'La API de GraphQL de {% data variables.product.prodname_dotcom %} ofrece flexibilidad y la capacidad de definir precisamente los datos que quieres recuperar.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Resumen - -Aquí hay algunos enlaces rápidos para ponerte en marcha con la API de GraphQL v4: - -* [Autenticación](/v4/guides/forming-calls/#authenticating-with-graphql) -* [Terminal raíz](/v4/guides/forming-calls/#the-graphql-endpoint) -* [Introspección del modelo](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) -* [Límites de tasa](/v4/guides/resource-limitations/) -* [Migrar desde REST](/v4/guides/migrating-from-rest) - -### Acerca de GraphQL - -El lenguaje de consulta de [GraphQL](https://graphql.github.io/) es: - -* **Una [especificación](https://graphql.github.io/graphql-spec/June2018/).** La especificación determina la validez del [modelo](/v4/guides/intro-to-graphql#schema) en el servidor de la API. El modelo determina la validez de las llamadas al cliente. - -* **[Lenguaje inflexible](#about-the-graphql-schema-reference).** El modelo define el sistema de tipos de la API y todas las relaciones con objetos. - -* **[Introspectivo](/v4/guides/intro-to-graphql#discovering-the-graphql-api).** Un cliente puede consultar el modelo para obtener detalles del mismo. - -* **[Jerárquico](/v4/guides/forming-calls).** La forma de un llamado de GraphQL imita la forma de los datos JSON que recupera. Los [Campos anidados](/v4/guides/migrating-from-rest/#example-nesting) te permiten consultar y recibir únicamente los dtos que especificas en una sola transacción. - -* **Una capa de aplicación.** GraphQL no es un modelo de almacenamiento o un lenguaje de consulta de bases de datos. _graph_ se refiere a estructuras gráficas definidas en el modelo, en donde los [nodos](/v4/guides/intro-to-graphql#node) definen objetos y los [bordes](/v4/guides/intro-to-graphql#edge) definen relaciones entre objetos. La API recorre y recupera datos de la aplicación basándose en las definiciones del modelo, independientemente de cómo se almacenan los datos. - -### Por qué GitHub utiliza GraphQL - -GitHub eligió GraphQL para la API v4 porque ofrece significativamente más flexibilidad para nuestros intregradores. La capacidad de definir precisamente los datos que quieres —y _únicamente_ estos— es una ventaja poderosa sobre las terminales de la API de REST v3. GraphQL te permite reemplazar varias solicitudes de REST con _una sola llamada_ para agregar los datos que especifiques. - -Para obtener más detalles acerca de por qué GitHub se ha migrado a GraphQL, consulta la[publicación de anuncios del blog](https://githubengineering.com/the-github-graphql-api/). - -### Acerca de la referencia del modelo de GraphQL - -Los documentos en la barra lateral se generan del [modelo](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) de GraphQL de {% data variables.product.prodname_dotcom %}. Todas las llamadas se validan y ejecutan contra el modelo. Utiliza estos documentos para encontrar los datos a los que puedes llamar: - -* Operaciones permitidas: [consultas](/v4/query) y [mutaciones](/v4/mutation). - -* Tipos definidos por el modelo: [escalares](/v4/scalar), [objetos](/v4/object), [enumeradores](/v4/enum), [interfaces](/v4/interface), [uniones](/v4/union), y [objetos de entrada](/v4/input_object). - -Puedes acceder a este mismo contenido a través de la [Barra lateral de documentos del explorador](/v4/guides/using-the-explorer#accessing-the-sidebar-docs). Nota que podrías necesitar depender de ambos, los documentos y la validación del modelo, para hacer una llamada a la API de GraphQL. - -Para obtener otro tipo de información, tal como los detalles de autenticación y el límite de tasas, revisa las [guías](/v4/guides). - -### Solicitar soporte - -{% data reusables.support.help_resources %} diff --git a/translations/es-XL/content/graphql/overview/breaking-changes.md b/translations/es-XL/content/graphql/overview/breaking-changes.md deleted file mode 100644 index bcf2fbd360..0000000000 --- a/translations/es-XL/content/graphql/overview/breaking-changes.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Cambios sustanciales -intro: 'Aprende sobre los cambios sustanciales recientes y venideros a la API de GraphQL de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /v4/breaking_changes -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de los cambios sustanciales - -Los cambios sustanciales son aquellos que pudieran necesitar que nuestros integradores realicen alguna acción al respecto. Dividimos estos cambios en dos categorías: - - - **Sustanciales:** Cambios que modificarán consultas existentes a la API de GraphQL. Por ejemplo, eliminar un campo sería un cambio sustancial. - - **Peligrosos:** Cambios que no modificaran las consultas existentes, pero podrían afectar el comportamiento del tiempo de ejecución de los clientes. Agregar un valor de enumerador es un ejemplo de un cambio peligroso. - -Nos esforzamos por proporcionar API estables para nuestros integradores. Cuando alguna característica nueva está evolucionando aún, la lanzamos detrás de una [vista previa del modelo](/v4/previews/). - -Anunciaremos los cambios sustanciales por venir por lo menos tres meses antes de aplicarlos al modelo de GraphQL, para proporcionar a los integradores tiempo para realizar los ajustes necesarios. Los cambios toman efecto en el primer día de un trimestre (1 de enero, 1 de abril, 1 de julio, o 1 de octubre). Por ejemplo, si anunciamos un cambio en el 15 de enero, se aplicará en el 1 de julio. - -{% for date in graphql.upcomingChangesForCurrentVersion %} -### Cambios programados para {{ date[0] }} - -{% for change in date[1] %} -
      -
    • {% if change.criticality == 'breaking' %}Sustancial{% else %}Peligroso{% endif %}Se hará un cambio a {{ change.location }}. - -

      Descripción: {{ change.description }}

      - -

      Razón:{{ change.reason }}

      -
      • -
    - -{% endfor %} -{% endfor %} diff --git a/translations/es-XL/content/graphql/overview/changelog.md b/translations/es-XL/content/graphql/overview/changelog.md deleted file mode 100644 index 48a1fa4b29..0000000000 --- a/translations/es-XL/content/graphql/overview/changelog.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Bitácora de Cambios -intro: 'La bitácora de cambios del modelo de GraphQL es una lista de cambios recientes y venideros a nuestro modelo de la API de GraphQL. Este incluye cambios compatibles con versiones anteriores, y cambios sustanciales venideros.' -redirect_from: - - /v4/changelog -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -Los cambios sustanciales incluyen aquellos que modificarán las consultas existentes o que podrían afectar el comportamiento del tiempo de ejecución de los clientes. Para un listado de cambios sustanciales y cuándo ocurrirán, consulta nuestra [bitácora de cambios sustanciales](/v4/breaking_changes). - -{% for entry in graphql.changelog %} -### Cambios de modelo para {{ entry.date }} - -{% for schemaChange in entry.schemaChanges %} -{{ schemaChange.title }} - -{% for change in schemaChange.changes %} -* {{ change }} -{% endfor %} -{% endfor %} - -{% for previewChange in entry.previewChanges %} -{{ previewChange.title }} - -{% for change in previewChange.changes %} -* {{ change }} -{% endfor %} -{% endfor %} - -{% for upcomingChange in entry.upcomingChanges %} -{{ upcomingChange.title }} - -{% for change in upcomingChange.changes %} -* {{ change }} -{% endfor %} -{% endfor %} - -{% endfor %} diff --git a/translations/es-XL/content/graphql/overview/explorer.md b/translations/es-XL/content/graphql/overview/explorer.md deleted file mode 100644 index 29cb28206e..0000000000 --- a/translations/es-XL/content/graphql/overview/explorer.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Explorador -redirect_from: - - /v4/explorer - - /v4/explorer-new -versions: - fpt: '*' - ghes: '*' - ghae: '*' -layout: graphql-explorer -topics: - - API ---- - -Puedes acceder al Explorador de GraphQL de GitHub en https://developer.github.com/v4/explorer. diff --git a/translations/es-XL/content/graphql/overview/index.md b/translations/es-XL/content/graphql/overview/index.md deleted file mode 100644 index 59ce1af60c..0000000000 --- a/translations/es-XL/content/graphql/overview/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Resumen -intro: 'Aprende acerca de la API de GraphQL de {% data variables.product.prodname_dotcom %}, las vistas previas para los cambios venideros, sustanciales y sobre las limitaciones. También puedes utilizar el explorador de GraphQL para interactuar con la API en datos reales de {% data variables.product.prodname_dotcom %}.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /about-the-graphql-api - - /public-schema - - /schema-previews - - /breaking-changes - - /changelog - - /explorer - - /resource-limitations ---- - diff --git a/translations/es-XL/content/graphql/overview/public-schema.md b/translations/es-XL/content/graphql/overview/public-schema.md deleted file mode 100644 index 010dc99f95..0000000000 --- a/translations/es-XL/content/graphql/overview/public-schema.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Modelo público -intro: 'Descarga el modelo público para la API de GraphQL de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /v4/public_schema -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -Puedes [realizar una introspección](/v4/guides/intro-to-graphql/#discovering-the-graphql-api) contra la API de GraphQL directamente. - -Como alternativa, puedes descargar la última versión del modelo público aquí: - -{% if currentVersion == "free-pro-team@latest" %} - -[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs.graphql`](/public/schema.docs.graphql) - -{% else %} - -[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-enterprise.graphql`](/public/{{ currentVersion }}/schema.docs-enterprise.graphql) ({{ allVersions[currentVersion].versionTitle }}) - -{% endif %} diff --git a/translations/es-XL/content/graphql/overview/resource-limitations.md b/translations/es-XL/content/graphql/overview/resource-limitations.md deleted file mode 100644 index 65c403a965..0000000000 --- a/translations/es-XL/content/graphql/overview/resource-limitations.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -title: Limitaciones de los recursos -intro: 'La API de GraphQL de {% data variables.product.prodname_dotcom %} cuenta con limitaciones para la protección contra las llamadas excesivas o abusivas a los servidores de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /v4/guides/resource-limitations -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -## Límite de nodo - -Para pasar la validación del [modelo](/v4/guides/intro-to-graphql#schema), todas las [llamadas](/v4/guides/forming-calls) la API v4 de GraphQL deben cumplir con los siguientes estándares: - -* Los clientes deben suministrar un argumento `first` o `last` en cualquier [conexión](/v4/guides/intro-to-graphql#connection). -* Los valores de `first` y `last` deben estar dentro de 1-100. -* Las llamadas individuales no pueden solicitar más de 500,000 [nodos](/v4/guides/intro-to-graphql#node) en total. - -#### Calcular los nodos en una llamada - -Estos dos ejemplos te muestran cómo calcular los nodos totales en una llamada. - -1. Consulta simple: 
    query {
-    viewer {
-      repositories(first: 50) {
-        edges {
-          repository:node {
-            name
-
-            issues(first: 10) {
-              totalCount
-              edges {
-                node {
-                  title
-                  bodyHTML
-                }
-              }
-            }
-          }
-        }
-      }
-    }
-  }
    - - Cálculo: 
    50         = 50 repositories
-   +
-  50 x 10  = 500 repository issues
-
-              = 550 total nodes
    - -2. Consulta compleja: 
    query {
-    viewer {
-      repositories(first: 50) {
-        edges {
-          repository:node {
-            name
-
-            pullRequests(first: 20) {
-              edges {
-                pullRequest:node {
-                  title
-
-                  comments(first: 10) {
-                    edges {
-                      comment:node {
-                        bodyHTML
-                      }
-                    }
-                  }
-                }
-              }
-            }
-
-            issues(first: 20) {
-              totalCount
-              edges {
-                issue:node {
-                  title
-                  bodyHTML
-
-                  comments(first: 10) {
-                    edges {
-                      comment:node {
-                        bodyHTML
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      }
-
-      followers(first: 10) {
-        edges {
-          follower:node {
-            login
-          }
-        }
-      }
-    }
-  }
    - - Cálculo: 
    50              = 50 repositories
-   +
-  50 x 20       = 1,000 pullRequests
-   +
-  50 x 20 x 10 = 10,000 pullRequest comments
-   +
-  50 x 20       = 1,000 issues
-   +
-  50 x 20 x 10 = 10,000 issue comments
-   +
-  10              = 10 followers
-
-                   = 22,060 total nodes
    - -### Limite de tasa - -El límite de la API v4 de GraphQL es diferente a los [límites de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting) de la API v3 de REST. - -¿Por qué son diferentes los límites de tasa de la API? Con [GraphQL](/v4/), una llamada de GraphQL puede reemplazar [varias llamadas de REST](/v4/guides/migrating-from-rest/). Una sola llamada compleja de GraphQL puede ser el equivalente a miles de solicitudes de REST. Si bien una sola llamada de GraphQL caería muy debajo del límite de tasa de la API de REST, la consulta podría ser igual de cara en términos de procesamiento para los servidores de GitHub. - -Para representar con precisión el costo de una consulta al servidor, la API v4 de GraphQL calcula la **puntuación de tasa límite** de una llamada con base en una escala de puntos normalizada. Los factores de puntuación de una consulta en argumentos "firs" y "last" en una conexión padre y sus hijos. - -* La fórmula utiliza los argumentos `first` y `last` en una conexión padre y en sus hijos para pre-calcular la carga potencial en los sistemas de GitHub, tal como MySQL, ElasticSearch y Git. -* Cada conexión nueva tiene su propio valor de puntos. Los puntos se combinan con otros puntos desde la llamada en una puntuación de tasa límite general. - -El límite de tasa de la API v4 de GraphQL es de **5,000 puntos por hora**. - -{% if currentVersion == "free-pro-team@latest" %} - -Para las {% data variables.product.prodname_github_apps %} o las {% data variables.product.prodname_oauth_app %}s que pertenezcan a una cuenta de {% data variables.product.prodname_ghe_cloud %}, las solicitudes a los recursos que pertenecen a la misma cuenta de {% data variables.product.prodname_ghe_cloud %} tienen un límite incrementado de 15,000 puntos por hora. - -{% endif %} - -Nota que 5,000 puntos por hora no es lo mismo que 5,000 llamadas por hora: la API v4 de GraphQL y la API v3 de REST utilizan límites de tasa diferentes. - -{% note %} - -**Nota**: La fórmula y el límite de tasa actuales están sujetos a cambio mientras observamos cómo los desarrolladores utilizan la API v4 de GraphQL. - -{% endnote %} - -#### Recuperar el estado de límite de tasa de una llamada - -Con la API v3 de REST, puedes revisar el estado de límite de tasa si [inspeccionas](/rest/overview/resources-in-the-rest-api#rate-limiting) los encabezados HTTP devueltos. - -Con la API v4 de GraphQL, puedes revisar el estado de límite de tasa si consultas los campos en el objeto `rateLimit`: - -```graphql -query { - viewer { - login - } - rateLimit { - limit - cost - remaining - resetAt - } -} -``` - -* El campo `limit` devuelve el número máximo de puntos que se permite consumir al cliente en una ventana de 60 minutos. - -* El campo `cost` devuelve el costo en puntos para la llamada actual que cuenta contra el límite de tasa. - -* El campo `remaining` devuelve la cantidad de puntos restantes en la ventana de límite de tasa actual.) - -* EL campo `resetAt` devuelve la hora en la que se reinicia la ventana de límite de tasa actual en [segundos de satélite UTC](http://en.wikipedia.org/wiki/Unix_time). - -#### Calcular el puntaje de límite de tasa antes de ejecutar la llamada - -Al consultar el objeto `rateLimit` se devuelve el puntaje de una llamada, pero ejecutar la llamada tiene un costo en el límite. Para evitar este dilema, puedes calcular el puntaje de una llamada antes de ejecutarla. Los siguientes cálculos funcionan casi de la misma manera que lo que devuelve `rateLimit { cost }`. - -1. Agrega la cantidad de solicitudes requeridas para completar cada conexión única en la llamada. Asume que cada solicitud alcanzará los límites de los argumentos `first` o `last`. -2. Divide la cantidad entre **100** y redondea el resultado para obtener el costo final agregado. Este paso normaliza las cantidades grandes. - -{% note %} - -**Nota**: El costo mínimo de una llamada a la API v4 de GraphQL es **1**, lo cual representa solo una solicitud. - -{% endnote %} - -Aquí se muestra una consulta y cálculo de puntaje de ejemplo: - -```graphql -query { - viewer { - login - repositories(first: 100) { - edges { - node { - id - - issues(first: 50) { - edges { - node { - id - - labels(first: 60) { - edges { - node { - id - name - } - } - } - } - } - } - } - } - } - } -} -``` - -Esta consulta requiere de 5,101 solicitudes para completarse: - -* Aunque se devolvieron 100 repositorios, la API se tiene que conectar a la cuenta del visualizador **una vez** para obtener la lista de repositorios. Así que, las solicitudes de repositorios = **1** -* Aunque estámos obteniendo 50 informes de problemas de vuelta, la API tiene que conectarse a cada uno de los **100** repositorios para obtener la lista de informes de problemas. Así que, las solicitudes de informes de problemas = **100** -* Aunque estamos obteniendo 60 etiquetas de vuelta, la API se tiene que conectar a cada uno de los **5,000** informes de problemas potenciales totales para obtener la lista de etiquetas. Así que, las solicitudes de etiquetas = **5,000** -* Total = **5,101** - -Si lo dividimos entre 100 y lo redondeamos, obtenemos el puntaje final de la consulta: **51** diff --git a/translations/es-XL/content/graphql/overview/schema-previews.md b/translations/es-XL/content/graphql/overview/schema-previews.md deleted file mode 100644 index 814a77724f..0000000000 --- a/translations/es-XL/content/graphql/overview/schema-previews.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Vistas previas del modelo -intro: 'Puedes obtener una vista previa de las características y cambios por venir para el modelo de GraphQL de {% data variables.product.prodname_dotcom %} antes de que se agreguen a la API de GraphQL de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /v4/previews -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de las vistas previas del modelo - -Durante el periodo de vista previa, podríamos cambiar algunas características con base en la retroalimentación de los desarrolladores. Si realizamos cambios, lo anunciaremos en el [blog de desarrolladores](https://developer.github.com/changes/) sin aviso previo. - -Para aceder a una vista previa de modelo, necesitamos que nos proporciones un [tipo de medios](/v3/media) 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. - -{% note %} - -**Nota:** En este momento no se puede acceder a los miembros de modelo de GraphQL bajo vista previa a través del explorador. - -{% endnote %} - -{% for preview in graphql.previewsForCurrentVersion %} -### {{ preview.title }} - -{{ preview.description }} - -Para alternar esta vista previa y acceder a los siguientes miembros de modelo, debes proporcionar un tipo de medios personalizado en el encabezado `Accept`: - -``` -{{ preview.accept_header }} -``` - -Miembros del modelo previstos: - -{% for schemaMemberPath in preview.toggled_on %} -- `{{ schemaMemberPath }}` -{% endfor %} - -{% if preview.announcement %} -**Anunciados:** [{{ preview.announcement.date }}]({{ preview.announcement.url }}) -{% endif %} - -{% if preview.updates %} -{% for update in preview.updates %} -**Actualizados:** [{{ update.date }}]({{ update.url }}) -{% endfor %} -{% endif %} - -{% endfor %} diff --git a/translations/es-XL/content/graphql/reference/enums.md b/translations/es-XL/content/graphql/reference/enums.md deleted file mode 100644 index 499fa548fa..0000000000 --- a/translations/es-XL/content/graphql/reference/enums.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Enumeradores -redirect_from: - - /v4/enum - - /v4/reference/enum -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de los enumeradores - -Los [Enumeradores](https://graphql.github.io/graphql-spec/June2018/#sec-Enums) representan conjuntos de valores posibles para un campo. - -Por ejemplo, el objeto [`Issue`](/v4/object/issue) tiene un campo llamado `state`. El estado es un enumerador (específicamente, de tipo [`IssueState`](/v4/enum/issuestate/)) ya que éste puede ser `OPEN` o `CLOSED`. - -Para obtener más información, consulta la sección "[Introducción a GraphQL](/v4/guides/intro-to-graphql)". - -{% for item in graphql.schemaForCurrentVersion.enums %} - {% include graphql-enum %} -{% endfor %} diff --git a/translations/es-XL/content/graphql/reference/index.md b/translations/es-XL/content/graphql/reference/index.md deleted file mode 100644 index 490e811c77..0000000000 --- a/translations/es-XL/content/graphql/reference/index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Referencia -intro: 'Consulta la documentación de referencia para aprender sobre los tipos de datos disponibles en el modelo de la API de GraphQL de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /v4/reference -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /queries - - /mutations - - /objects - - /interfaces - - /enums - - /unions - - /input-objects - - /scalars ---- - diff --git a/translations/es-XL/content/graphql/reference/input-objects.md b/translations/es-XL/content/graphql/reference/input-objects.md deleted file mode 100644 index 9ed439aa26..0000000000 --- a/translations/es-XL/content/graphql/reference/input-objects.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Objetos de entrada -redirect_from: - - /v4/input_object - - /v4/reference/input_object -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de los objetos de entrada - -Los [objetos de entrada](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects) pueden describirse como "objetos estructurables" ya que incluyen un conjunto de campos de entrada que definen al objeto. - -Por ejemplo, [`CommitAuthor`](/v4/input_object/commitauthor/) toma un campo llamado `emails`. Proporcionar un valor para `emails` transforma a `CommitAuthor` en una lista de objetos `User` que contienen esa dirección de correo electrónico. Nota que los [objetos](/v4/object) **podrían** tener objetos de entrada, mientras que las [mutaciones](/v4/mutation) **requieren** objetos de entrada. - -Para obtener más información, consulta la sección "[Acerca de las mutaciones](/v4/guides/forming-calls#about-mutations)". - -{% for item in graphql.schemaForCurrentVersion.inputObjects %} - {% include graphql-input-object %} -{% endfor %} diff --git a/translations/es-XL/content/graphql/reference/interfaces.md b/translations/es-XL/content/graphql/reference/interfaces.md deleted file mode 100644 index 0e3e17fa30..0000000000 --- a/translations/es-XL/content/graphql/reference/interfaces.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Interfaces -redirect_from: - - /v4/interface - - /v4/reference/interface -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de las interfaces - -Las [interfaces](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces) sirven como objetos padre de los cuales obtendrán sus herencias los demás objetos. - -Por ejemplo, [`Lockable`](/v4/interface/lockable/) es una interface, ya que tanto los objetos [`Issue`](/v4/object/issue/) como los objetos [`PullRequest`](/v4/object/pullrequest/) se pueden fijar. Una interface tiene su propia lista de campos nombrados que se comparte mediante objetos de implementación. - -Para obtener más información, consulta la sección "[Implementación](/v4/guides/intro-to-graphql#implementation)". - -{% for item in graphql.schemaForCurrentVersion.interfaces %} - {% include graphql-interface %} -{% endfor %} diff --git a/translations/es-XL/content/graphql/reference/mutations.md b/translations/es-XL/content/graphql/reference/mutations.md deleted file mode 100644 index 2eb1fd9eea..0000000000 --- a/translations/es-XL/content/graphql/reference/mutations.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Mutaciones -redirect_from: - - /v4/mutation - - /v4/reference/mutation -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de las mutaciones - -Cada modelo de GraphQL tiene un tipo de raíz tanto para consultas como para mutaciones. El [tipo mutación](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) define las operaciones de GraphQL que cambian los datos en el servidor. Es análogo a realizar verbos HTTP tales como `POST`, `PATCH`, y `DELETE`. - -Para obtener más información, consulta la sección "[Acerca de las mutaciones](/v4/guides/forming-calls#about-mutations)". - -{% for item in graphql.schemaForCurrentVersion.mutations %} - {% include graphql-mutation %} -{% endfor %} diff --git a/translations/es-XL/content/graphql/reference/objects.md b/translations/es-XL/content/graphql/reference/objects.md deleted file mode 100644 index 1dce30f87a..0000000000 --- a/translations/es-XL/content/graphql/reference/objects.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Objetos -redirect_from: - - /v4/object - - /v4/reference/object -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de los objetos - -Los [objetos](https://graphql.github.io/graphql-spec/June2018/#sec-Objects) en GraphQL representan los recursos a los cuales puedes acceder. Un objeto puede contener una lista de campos, los cuales se teclean específicamente. - -Por ejemplo, el objeto [`Repository`](/graphql/reference/objects#repository) tiene un campo llamado `name`, el cual es una `String`. - -Para obtener más información, consulta la sección "[Introducción a GraphQL](/v4/guides/intro-to-graphql)". - - - diff --git a/translations/es-XL/content/graphql/reference/queries.md b/translations/es-XL/content/graphql/reference/queries.md deleted file mode 100644 index a085b567f3..0000000000 --- a/translations/es-XL/content/graphql/reference/queries.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Consultas -miniTocMaxHeadingLevel: 2 -redirect_from: - - /v4/query - - /v4/reference/query -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de las consultas - -Cada modelo de GraphQL tiene un tipo de raíz tanto para consultas como para mutaciones. El [tipo de consulta](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) define las operaciones de GraphQL que recuperan datos del servidor. - -Paraobtener más información, consulta la sección "[Acerca de las consultas](/v4/guides/forming-calls#about-queries)". - -## Conexiones - -{% for item in graphql.schemaForCurrentVersion.queries.connections %} - {% include graphql-query %} -{% endfor %} - -## Campos - -{% for item in graphql.schemaForCurrentVersion.queries.fields %} - {% include graphql-query %} -{% endfor %} diff --git a/translations/es-XL/content/graphql/reference/scalars.md b/translations/es-XL/content/graphql/reference/scalars.md deleted file mode 100644 index 794a63ebb8..0000000000 --- a/translations/es-XL/content/graphql/reference/scalars.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Escalares -redirect_from: - - /v4/scalar - - /v4/reference/scalar -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de los escalares - -Los [escalares](https://graphql.github.io/graphql-spec/June2018/#sec-Scalars) son valores primitivos: `Int`, `Float`, `String`, `Boolean`, o `ID`. - -Cuando llamas a la API de GraphQL, debes especificar subcampos anidados hasta que recuperes únicamente escalares. - -Para obtener más información, consulta la sección "[introducción a GraphQL](/v4/guides/intro-to-graphql#field)". - -{% for item in graphql.schemaForCurrentVersion.scalars %} - {% include graphql-scalar %} -{% endfor %} diff --git a/translations/es-XL/content/graphql/reference/unions.md b/translations/es-XL/content/graphql/reference/unions.md deleted file mode 100644 index 1720fdbbae..0000000000 --- a/translations/es-XL/content/graphql/reference/unions.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Uniones -redirect_from: - - /v4/union - - /v4/reference/union -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de las uniones - -Una [unión](https://graphql.github.io/graphql-spec/June2018/#sec-Unions) es un tipo de objeto que representa muchos otros objetos. - -Por ejemplo, un campo marcado como un [`ProjectCardItem`](/v4/union/projectcarditem/) podría ser un [`Issue`](/v4/object/issue/) o una [`PullRequest`](/v4/object/pullrequest/) ya que cada uno de estos objetos puede estar dentro de una tarjeta de proyecto. Utilizar una unión en vez de un objeto te otorga flexibilidad. - -Para obtener más información, consulta la sección "[Introducción a GraphQL](/v4/guides/intro-to-graphql)". - -{% for item in graphql.schemaForCurrentVersion.unions %} - {% include graphql-union %} -{% endfor %} diff --git a/translations/es-XL/content/index.md b/translations/es-XL/content/index.md deleted file mode 100644 index 379286c915..0000000000 --- a/translations/es-XL/content/index.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: '{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}.com{% endif %} Documentación de Ayuda' -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 - - /github/writing-on-github/basic-writing-and-formatting-syntax - popular: - - /github/collaborating-with-issues-and-pull-requests/about-pull-requests - - /github/authenticating-to-github - - /github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line - - /github/getting-started-with-github/managing-remote-repositories - - /github/working-with-github-pages -versions: '*' -children: - - github - - admin - - billing - - organizations - - code-security - - actions - - packages - - developers - - rest - - graphql - - insights - - issues - - discussions - - codespaces - - sponsors - - communities - - pages - - education - - desktop - - early-access -externalProducts: - cli: - id: cli - name: GitHub CLI - href: 'https://cli.github.com/manual' - external: true - atom: - id: atom - name: Atom - href: 'https://atom.io/docs' - external: true - electron: - id: electron - name: Electron - href: 'https://electronjs.org/docs' - external: true - codeql: - id: codeql - name: CodeQL - href: 'https://codeql.github.com/docs' - external: true ---- - diff --git a/translations/es-XL/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md b/translations/es-XL/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md deleted file mode 100644 index fb96878282..0000000000 --- a/translations/es-XL/content/packages/getting-started-with-github-container-registry/about-github-container-registry.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: About GitHub Container Registry -intro: 'The {% data variables.product.prodname_github_container_registry %} allows you to seamlessly host and manage Docker container images in your organization or personal user account on {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_github_container_registry %} allows you to configure who can manage and access packages using fine-grained permissions.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' ---- - -{% note %} - -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. - -{% endnote %} - - -{% data reusables.package_registry.container-registry-feature-highlights %} - -To share context about your package's use, you can link a repository to your container image on {% data variables.product.prodname_dotcom %}. For more information, see "[Connecting a repository to a container image](/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image)." - -### Formatos compatibles - -The {% data variables.product.prodname_container_registry %} currently only supports Docker images. - - -### Visibility and access permissions for container images - -If you have admin permissions to a container image, you can set the container image to private or public. Public images allow anonymous access and can be pulled without authentication or signing in via the CLI. - -As an admin, you can also grant access permissions for a container image that are separate from the permissions you've set at the organization and repository levels. - -For container images published and owned by a user account, you can give any person an access role. For container images published and owned by an organization, you can give any person or team in the organization an access role. - -| Permission role | Access description | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -| Lectura | Can download package.
    Can read package metadata. | -| Escritura | Can upload and download this package.
    Can read and write package metadata. | -| Admin | Can upload, download, delete, and manage this package.
    Can read and write package metadata.
    Can grant package permissions. | - -For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." - -### Acerca de la facturación para {% data variables.product.prodname_github_container_registry %} - -{% data reusables.package_registry.billing-for-container-registry %} - -### Contactar con soporte técnico - -If you have feedback or feature requests for {% data variables.product.prodname_github_container_registry %}, use the [feedback form](https://support.github.com/contact/feedback?contact%5Bcategory%5D=packages). - -Contacta el {% data variables.contact.github_support %} sobre {% data variables.product.prodname_github_container_registry %} usando [nuestro formulario de contacto](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) si: - -* Encuentras algo que contradice la documentación. -* Encuentras errores vagos o poco claros. -* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally-identifying information. diff --git a/translations/es-XL/content/packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry.md b/translations/es-XL/content/packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry.md deleted file mode 100644 index b15e35f1b0..0000000000 --- a/translations/es-XL/content/packages/getting-started-with-github-container-registry/core-concepts-for-github-container-registry.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Core concepts for GitHub Container Registry -intro: 'Below is a list of common {% data variables.product.prodname_github_container_registry %} terms we use across our sites and documentation.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' ---- - -{% data reusables.package_registry.container-registry-beta %} - -### {% data variables.product.prodname_github_container_registry %} - -The {% data variables.product.prodname_github_container_registry %} is a registry for containers with support for Docker images. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)". - -### Package - -A package is a self-contained and reusable piece of software that includes code and metadata that a developer bundles together in a common place for others to use. A package's metadata may include the version number, name, and the code's dependencies. Packages simplify using and distributing solutions to common problems such as needing frameworks for developing or testing a project, linters to improve code quality, or industry-standard machine learning tools to power your application. Packages exist in many ecosystems. For example, you can package Node.js and Java code or container images. - -### Container - -A container is a unit of software designed to reliably deploy software in a standardized way on any platform. A container operates as an isolated virtual environment or instance that can run various software packages and components on the same host kernel as your operating system. Containers use fewer resources than virtual machines because they don't need to include their own virtual hardware to run. Containers are created using a container image file, such as a Dockerfile, and a container client or runtime program. - -### Container image - -A container image is a type of package archive that specifies the software requirements to run an app from a container. A container image typically includes the app's code, libraries, and runtime instructions. To ensure that the same image details are used wherever an image is deployed and run, a container image is automatically versioned and cannot be changed once a container image is built in a container. - -### Contenedor Docker - -A Docker container is a type of open source container built on the Docker platform. Docker's original image format has become the OCI (Open Container Initiative) Image Specification. For more information, see the "[Docker documentation](https://docs.docker.com/get-started/overview/)." diff --git a/translations/es-XL/content/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization.md b/translations/es-XL/content/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization.md deleted file mode 100644 index 7a3471c31b..0000000000 --- a/translations/es-XL/content/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Enabling GitHub Container Registry for your organization -intro: 'In an organization, organization admins can allow organization members to publish public or private container images to {% data variables.product.prodname_github_container_registry %}.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' ---- - -{% data reusables.package_registry.container-registry-beta %} - -Before organization members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization admin must enable package creation. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %} -5. Under "Package creation", choose whether you want to enable the creation of public or private container images. - - To enable organization members to create a public container image, click **Public**. - - To enable organization members to create a private container image that is only visible to other organization members, click **Private**. You can further customize the visibility of a private container image. For more information, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." - - ![Options to enable public or private packages ](/assets/images/help/package-registry/package-creation-org-settings.png) diff --git a/translations/es-XL/content/packages/getting-started-with-github-container-registry/index.md b/translations/es-XL/content/packages/getting-started-with-github-container-registry/index.md deleted file mode 100644 index 3cb47ac9d2..0000000000 --- a/translations/es-XL/content/packages/getting-started-with-github-container-registry/index.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Getting started with GitHub Container Registry -intro: 'Learn about {% data variables.product.prodname_container_registry %} concepts and how to migrate your Docker images from {% data variables.product.prodname_registry %}.' -versions: - free-pro-team: '*' -children: - - /about-github-container-registry - - /core-concepts-for-github-container-registry - - /migrating-to-github-container-registry-for-docker-images - - /enabling-github-container-registry-for-your-organization ---- -{% data reusables.package_registry.container-registry-beta %} -For more information about configuring, deleting, pushing, or pulling container images, see "[Managing container images with {% data variables.product.prodname_github_container_registry %}](/packages/managing-container-images-with-github-container-registry)." diff --git a/translations/es-XL/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md b/translations/es-XL/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md deleted file mode 100644 index 75a9f87b66..0000000000 --- a/translations/es-XL/content/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -title: Migrating to GitHub Container Registry for Docker images -intro: 'If you''ve used the GitHub Packages Docker registry to store Docker images, you can migrate to the new {% data variables.product.prodname_container_registry %}.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' ---- - -### Key differences between {% data variables.product.prodname_github_container_registry %} and the Docker package registry - -{% data reusables.package_registry.container-registry-beta %} - -The {% data variables.product.prodname_github_container_registry %} supersedes the existing Packages Docker registry and is optimized to support some of the unique needs of containers. - -{% data reusables.package_registry.container-registry-feature-highlights %} - -Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)". - -### Billing changes - -{% data reusables.package_registry.billing-for-container-registry %} - -### Domain changes - -The domain for the {% data variables.product.prodname_container_registry %} is `ghcr.io`. - -| Registry | URL de Ejemplo | -| ---------------------------------------------------------------------- | --------------------------------------------------- | -| {% data variables.product.prodname_registry %} Docker registry | `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME` | -| {% data variables.product.prodname_github_container_registry %} | `ghcr.io/OWNER/IMAGE_NAME` | - -### Authenticating with the container registry - -You will need to authenticate to the {% data variables.product.prodname_container_registry %} with the base URL `ghcr.io`. We recommend creating a new access token for using the {% data variables.product.prodname_container_registry %}. - -{% data reusables.package_registry.authenticate-to-container-registry %} - -### Migrating a Docker image using the Docker CLI - -To move Docker images that you host on {% data variables.product.prodname_registry %} Docker registry, you must republish the images to {% data variables.product.prodname_container_registry %}. We recommend republishing your existing Docker images using the command line on your local machine. - -1. Sign in to the Docker registry using a temporary PAT with at least the `read:packages` scope. This PAT will only be used to sign in to the Docker registry to pull down images and can be deleted afterward. - {% raw %} - ```shell - $ echo $READ_PACKAGES_TOKEN | docker login docker.pkg.github.com -u USERNAME --password-stdin - ``` - {% endraw %} -2. Pull down the image you'd like to migrate, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with tag for the image you want to install. For example, `docker pull docker.pkg.github.com/octo-org/octoshift/octoshift:latest` pulls the latest tag of the `octoshift/octoshift` image in the octo-org organization. - ```shell - $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - -3. Re-tag the image with the new domain and a new image name. Para obtener más información, consulta "[Etiqueta Docker](https://docs.docker.com/engine/reference/commandline/tag/)" en la documentación de Docker. Use the same URL that you used in the previous step for the SOURCE URL. Replace the TARGET_OWNER with the user or organization that you are migrating the container image to and replace the TARGET_IMAGE_NAME with the new {% data variables.product.prodname_container_registry %} image name. - ```shell - $ docker tag docker.pkg.github.com/SOURCE_OWNER/SOURCE_REPOSITORY/SOURCE_IMAGE_NAME:VERSION ghcr.io/TARGET_OWNER/TARGET_IMAGE_NAME:VERSION - ``` - -4. Sign in to the new {% data variables.product.prodname_container_registry %}. We recommend creating a new PAT limited to the `read:packages` and `write:packages` scopes since you no longer need the `repo` scope and your previous PAT may not have the `write:packages` scope. - {% raw %} - ```shell - $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin - ``` - {% endraw %} -5. Push your re-tagged image to the {% data variables.product.prodname_container_registry %}. - ```shell - $ docker push ghcr.io/OWNER/IMAGE_NAME:VERSION - ``` - -### Updating your {% data variables.product.prodname_actions %} workflow - -If you have a {% data variables.product.prodname_actions %} workflow that uses a Docker image from the {% data variables.product.prodname_registry %} Docker registry, you may want to update your workflow to the {% data variables.product.prodname_container_registry %} to allow for anonymous access for public container images, finer-grain access permissions, and better storage and bandwidth compatibility for containers. - -1. Migrate your Docker images to the new {% data variables.product.prodname_container_registry %} at `ghcr.io`. For an example, see "[Migrating a Docker image using the Docker CLI](#migrating-a-docker-image-using-the-docker-cli)." - -2. In your {% data variables.product.prodname_actions %} workflow file, update the package url from `https://docker.pkg.github.com` to `ghcr.io`. - -3. Add your new {% data variables.product.prodname_container_registry %} authentication personal access token (PAT) as a GitHub ACtions secret. {% data variables.product.prodname_github_container_registry %} does not support using `GITHUB_TOKEN` for your PAT so you must use a different custom variable, such as `CR_PAT`. Para obtener más información, consulta "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)". - -4. In your {% data variables.product.prodname_actions %} workflow file, update the authentication PAT by replacing your Docker registry PAT ({% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}) with a new variable for your {% data variables.product.prodname_container_registry %} PAT, such as {% raw %}`${{ secrets.CR_PAT }}`{% endraw %}. - -#### Example of updated workflow - -If part of your workflow accessed a Docker image hosted by the Docker registry like this: - -{% raw %} -```yaml -echo ${{ secrets.GITHUB_TOKEN }} | docker login https://docker.pkg.github.com -u $GITHUB_ACTOR --password-stdin -docker pull docker.pkg.github.com/github/octoshift/octoshift:latest -docker build . --tag docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA --cache-from docker.pkg.github.com/github/octoshift/octoshift:latest -docker push docker.pkg.github.com/github/octoshift/octoshift:$GITHUB_SHA -``` -{% endraw %} - -Then you'll need to update your workflow with the new {% data variables.product.prodname_container_registry %} URL and PAT like this: - -{% raw %} -```yaml -# new login with new container registry url and PAT -echo ${{ secrets.CR_PAT }} | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin -# new container registry urls added -docker pull ghcr.io/github/octoshift:latest -docker build . --tag ghcr.io/github/octoshift:$GITHUB_SHA --cache-from ghcr.io/github/octoshift:latest -docker push ghcr.io/github/octoshift:$GITHUB_SHA -``` -{% endraw %} diff --git a/translations/es-XL/content/packages/index.md b/translations/es-XL/content/packages/index.md deleted file mode 100644 index 32b6a8b956..0000000000 --- a/translations/es-XL/content/packages/index.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Documentación de GitHub Packages -shortTitle: Paquetes de GitHub -intro: 'Aprende a publicar y consumir paquetes de forma segura, almacena tus paquetes junto con tu código y comparte tus paquetes de forma privada con tu equipo o de manera pública con la comunidad de código abierto. También puedes automatizar tus paquetes con {% data variables.product.prodname_actions %}.' -featuredLinks: - guides: - - /packages/learn-github-packages - - /packages/managing-github-packages-using-github-actions-workflows - - /packages/learn-github-packages/installing-a-package - popular: - - /packages/working-with-a-github-packages-registry/working-with-the-npm-registry - - '{% ifversion fpt %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}' - - /packages/learn-github-packages - - /packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry - guideCards: - - '{% ifversion fpt %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}' - - /packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry -redirect_from: - - /github/managing-packages-with-github-packages - - /categories/managing-packages-with-github-package-registry - - /github/managing-packages-with-github-package-registry -versions: - fpt: '*' - ghes: '*' - ghae: '*' -introLinks: - quickstart: /packages/quickstart - reference: /packages/manage-packages -changelog: - label: packages - prefix: 'Packages: ' -layout: product-landing -children: - - /quickstart - - /learn-github-packages - - /working-with-a-github-packages-registry - - /managing-github-packages-using-github-actions-workflows ---- -{% data reusables.package_registry.packages-ghes-release-stage %} diff --git a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md b/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md deleted file mode 100644 index 05fc53b92d..0000000000 --- a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Configuring access control and visibility for container images -intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' ---- - -{% data reusables.package_registry.container-registry-beta %} - -### Configuring access to container images for your personal account - -If you have admin permissions to a user-account owned container image, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)." - -{% data reusables.package_registry.package-settings-from-user-level %} -1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a user account. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) -1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) - -The selected users will automatically be given access and don't need to accept an invitation first. - -### Configuring access to container images for an organization - -If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](/packages/getting-started-with-github-container-registry/about-github-container-registry#visibility-and-access-permissions-for-container-images)." - -If your package is owned by an organization and private, then you can only give access to other organization members or teams. - -For organization image containers, organizations admins must enable packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." - -{% data reusables.package_registry.package-settings-from-org-level %} -1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access. ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png) -1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level. ![Container access options](/assets/images/help/package-registry/container-access-control-options.png) - -The selected users or teams will automatically be given access and don't need to accept an invitation first. - -### Configuring visibility of container images for your personal account - -When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings. - -A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. - -{% data reusables.package_registry.package-settings-from-user-level %} -5. Under "Danger Zone", choose a visibility setting: - - To make the container image visible to anyone, click **Make public**. - {% warning %} - - **Warning:** Once you make a package public, you cannot make it private again. - - {% endwarning %} - - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) - -### Configuring visibility of container images for an organization - -When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings. - -A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again. - -For organization image containers, organizations admins must enable public packages before you can set the visibility to public. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." - -{% data reusables.package_registry.package-settings-from-org-level %} -5. Under "Danger Zone", choose a visibility setting: - - To make the container image visible to anyone, click **Make public**. - {% warning %} - - **Warning:** Once you make a package public, you cannot make it private again. - - {% endwarning %} - - To make the container image visible to a custom selection of people, click **Make private**. ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png) diff --git a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image.md b/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image.md deleted file mode 100644 index dc24c20131..0000000000 --- a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: Connecting a repository to a container image -intro: 'You can link a repository with a container image locally and on {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' ---- - -When you link a container image with a repository, the package landing page will show information and links from the repository, such as the README. - -To connect a repository and a container image on {% data variables.product.prodname_dotcom %}, they must share the same owner on {% data variables.product.prodname_dotcom %}. For example, both `my_repo` and `hello_docker` are owned by the user `monalisa`: -```shell -https://github.com/monalisa/my_repo -https://github.com/monalisa/hello_docker -``` - -### Connecting a repository to a user-owned container image on {% data variables.product.prodname_dotcom %} - -{% data reusables.package_registry.package-settings-from-user-level %} - -{% data reusables.package_registry.repository_connection_steps %} - -### Connecting a repository to an organization-owned container image on {% data variables.product.prodname_dotcom %} - -{% data reusables.package_registry.package-settings-from-org-level %} - -{% data reusables.package_registry.repository_connection_steps %} - -### Connecting a repository to a container image on the command line - -1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details: - - ```shell - LABEL org.opencontainers.image.source https://github.com/OWNER/REPO - ``` - For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile: - ```shell - LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo - ``` - For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. - -2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`. - - ```shell - $ docker build -t hello_docker . - ``` -3. Optionally, review details for the Docker image you want to tag. - ```shell - $ docker images - > REPOSITORY TAG IMAGE ID CREATED SIZE - > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB - > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB - > hello-world latest fce289e99eb9 16 months ago 1.84kB - ``` - -4. Tag your Docker image with your desired image name and hosting destination. - ```shell - $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG - ``` - Por ejemplo: - ```shell - $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest - ``` - -5. If you haven't already, authenticate to {% data variables.product.prodname_github_container_registry %}. For more information, see "[Authenticating to GitHub Container Registry](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-github-container-registry)." - {% raw %} - ```shell - $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin - > Login Succeeded - ``` - {% endraw %} -6. Push your container image to {% data variables.product.prodname_github_container_registry %}. - ```shell - $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG - ``` - Por ejemplo: - ```shell - $ docker push ghcr.io/monalisa/hello_docker:latest - ``` diff --git a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md b/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md deleted file mode 100644 index 0c91851694..0000000000 --- a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/deleting-a-container-image.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Deleting a container image -intro: 'You can delete a version of a private container image using GraphQL or on {% data variables.product.prodname_dotcom %}.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' ---- - -{% data reusables.package_registry.container-registry-beta %} - -### Acerca de la eliminación de paquetes - -You can remove an entire container image or a specific version on {% data variables.product.prodname_dotcom %}. To delete a container image, you must use the UI. Using GraphQL to delete a container image is not supported at this time. - -To delete a container image, you must have admin permissions to the container image. - -When deleting public packages, be aware that you may break projects that depend on your package. - - - -### Nombres y versiones de paquetes reservados - -{% data reusables.package_registry.package-immutability %} - -### Deleting a version of a user-owned container image on {% data variables.product.prodname_dotcom %} - -{% data reusables.package_registry.package-settings-from-user-level %} -5. On the left, click **Manage versions**. -5. A la derecha de la versión que deseas eliminar, haz clic en **Delete (Eliminar)**. ![Botón para eliminar paquete](/assets/images/help/package-registry/delete-package-button.png) -6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-package-deletion.png) - -### Deleting a version of an organization-owned container image on {% data variables.product.prodname_dotcom %} - -{% data reusables.package_registry.package-settings-from-org-level %} -5. On the left, click **Manage versions**. -5. A la derecha de la versión que deseas eliminar, haz clic en **Delete (Eliminar)**. ![Botón para eliminar paquete](/assets/images/help/package-registry/delete-package-button.png) -6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-package-deletion.png) diff --git a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/index.md b/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/index.md deleted file mode 100644 index f8d3f83d59..0000000000 --- a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Managing container images with GitHub Container Registry -intro: 'Learn how to manage container images using a supported CLI or on {% data variables.product.prodname_dotcom %}.' -versions: - free-pro-team: '*' -children: - - /configuring-access-control-and-visibility-for-container-images - - /connecting-a-repository-to-a-container-image - - /pushing-and-pulling-docker-images - - /deleting-a-container-image ---- - diff --git a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md b/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md deleted file mode 100644 index 028e572886..0000000000 --- a/translations/es-XL/content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: Pushing and pulling Docker images -intro: 'You can store and manage Docker images in {% data variables.product.prodname_github_container_registry %}.' -product: '{% data reusables.gated-features.packages %}' -versions: - free-pro-team: '*' ---- - -{% data reusables.package_registry.container-registry-beta %} - -To push and pull container images owned by an organization, an organization admin must enable {% data variables.product.prodname_github_container_registry %} for the organization. For more information, see "[Enabling GitHub Container Registry for your organization](/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization)." - -### Autenticar a {% data variables.product.prodname_github_container_registry %} - -{% data reusables.package_registry.authenticate-to-container-registry %} - -### Pushing container images - -This example pushes the latest version of `IMAGE-NAME`. - ```shell - $ docker push ghcr.io/OWNER/IMAGE_NAME.latest - ``` - -This example pushes the `2.5` version of the image. - ```shell - $ docker push ghcr.io/OWNER/IMAGE-NAME:2.5 - ``` - -When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." - -### Pulling container images - -#### Pull by digest - -To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value. - -1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:` - ```shell - $ docker inspect ghcr.io/OWNER/IMAGE_NAME - ``` -2. Remove image locally as needed. - ```shell - $ docker rmi ghcr.io/OWNER/IMAGE_NAME.latest - ``` - -3. Pull the container image with `@YOUR_SHA_VALUE` after the image name. - ```shell - $ docker pull ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs - ``` - -#### Pull by name - - ```shell - $ docker pull ghcr.io/OWNER/IMAGE_NAME - ``` - -#### Pull by name and version - -Docker CLI example showing an image pulled by its name and the `1.14.1` version tag: - ```shell - $ docker pull ghcr.io/OWNER/IMAGE_NAME:1.14.1 - > 5e35bd43cf78: Pull complete - > 0c48c2209aab: Pull complete - > fd45dd1aad5a: Pull complete - > db6eb50c2d36: Pull complete - > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e - > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 - > ghcr.io/orgname/image-name/release:1.14.1 - ``` - -#### Pull by name and latest version - - ```shell - $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest - > latest: Pulling from user/image-name - > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 - > Status: Downloaded newer image for ghcr.io/user/image-name:latest - > ghcr.io/user/image-name:latest - ``` - -### Building container images - -This example builds the `hello_docker` image: - ```shell - $ docker build -t hello_docker . - ``` - -### Tagging container images - -1. Find the ID for the Docker image you want to tag. - ```shell - $ docker images - > REPOSITORY TAG IMAGE ID CREATED SIZE - > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB - > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB - > hello-world latest fce289e99eb9 16 months ago 1.84kB - ``` - -2. Tag your Docker image using the image ID and your desired image name and hosting destination. - ```shell - $ docker tag 38f737a91f39 ghcr.io/OWNER/NEW_IMAGE_NAME:latest - ``` diff --git a/translations/es-XL/content/packages/publishing-and-managing-packages/about-github-packages.md b/translations/es-XL/content/packages/publishing-and-managing-packages/about-github-packages.md deleted file mode 100644 index 6002d67e6f..0000000000 --- a/translations/es-XL/content/packages/publishing-and-managing-packages/about-github-packages.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -title: Acerca de GitHub Packages -intro: '{% 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.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/about-github-package-registry - - /github/managing-packages-with-github-package-registry/about-github-package-registry - - /github/managing-packages-with-github-packages/about-github-packages -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -### Acerca de {% data variables.product.prodname_registry %} - -{% data variables.product.prodname_registry %} es un servicio de alojamiento de paquetes, totalmente integrado con {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_registry %} combina tu código fuente y tus paquetes en un solo lugar para proporcionar facturación y gestión de permisos integrada, para que puedas centralizar tu desarrollo de software en {% data variables.product.product_name %}. - -Puedes integrar {% data variables.product.prodname_registry %} con las API de {% data variables.product.product_name %}, {% data variables.product.prodname_actions %} y webhooks para crear un flujo de trabajo de DevOps de extremo a extremo que incluya tu código, CI y soluciones de implementación. - -Puedes alojar múltiples paquetes en un repositorio y ver más información acerca de cada paquete al ver el README del paquete, las estadísticas de descarga, el historial de la versión y mucho más. - -{% if currentVersion == "free-pro-team@latest" %} -Cuando creas un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes usar el `GITHUB_TOKEN` para publicar e instalar paquetes en {% data variables.product.prodname_registry %} sin la necesidad de almacenar y administrar un token de acceso personal. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)". - -{% data reusables.package_registry.container-registry-beta %} - -{% endif %} - -#### Ver paquetes - -You can review the package's README, some metadata like licensing, download statistics, version history, and more on {% data variables.product.product_name %}. Para obtener más información, consulta "[Visualizar paquetes](/packages/publishing-and-managing-packages/viewing-packages)". - -#### About package permissions and visibility -{% if currentVersion == "free-pro-team@latest" %} -| | Package registries | {% data variables.product.prodname_github_container_registry %} | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Hosting locations | You can host multiple packages in one repository. | You can host multiple container images in one organization or user account. | -| Permissions | {% data reusables.package_registry.public-or-private-packages %} Puedes utilizar los roles y equipos de {% data variables.product.prodname_dotcom %} para limitar quién puede instalar o publicar cada paquete, ya que los paquetes heredan los permisos del repositorio. Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete como una dependencia en un proyecto, y cualquier persona con permisos de escritura puede publicar una nueva versión del paquete. | For each container image, you can choose the access level that others have. The permissions for container image access are separate from your organization and repository permissions. | - Visibility | {% data reusables.package_registry.public-or-private-packages %} | You can set the visibility of each of your container images. A private container image is only visible to people and teams who are given access within your organization. A public container image is visible to anyone. | Anonymous access | N/A | You can access public container images anonymously. - -{% else %} -| | Package registries | -| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Hosting locations | You can host multiple packages in one repository. | -| Permissions | {% data reusables.package_registry.public-or-private-packages %} Puedes utilizar los roles y equipos de {% data variables.product.prodname_dotcom %} para limitar quién puede instalar o publicar cada paquete, ya que los paquetes heredan los permisos del repositorio. Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete como una dependencia en un proyecto, y cualquier persona con permisos de escritura puede publicar una nueva versión del paquete. | -| Visibility | {% data reusables.package_registry.public-or-private-packages %} | - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -For more information about permissions and visibility for {% data variables.product.prodname_github_container_registry %}, see "[Configuring access control and visibility for containers](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -### Acerca de la facturación para {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.packages-billing %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)". - - -{{ site.data.reusables/package_registry/container-registry-beta-billing-note }} -{% endif %} - -### Formatos y clientes admitidos - -{% data variables.product.prodname_registry %} usa los comandos de herramientas del paquete nativo con los que ya estás familiarizado para publicar e instalar versiones del paquete. - -{% if currentVersion == "free-pro-team@latest" %} -#### Support for {% data variables.product.prodname_github_container_registry %} - -The {% data variables.product.prodname_github_container_registry %} hosts containers at `ghcr.io/OWNER/IMAGE-NAME`. - -| Cliente del paquete | Lenguaje | Formato del paquete | Descripción | -| ------------------- | -------- | ------------------- | ----------------------- | -| docker | N/A | `Dockerfile` | Gestor de paquetes Node | - -For more information about the container support offered by {% data variables.product.prodname_github_container_registry %}, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)." -{% endif %} - -#### Support for package registries - -{% if currentVersion == "free-pro-team@latest" %} -Package registries use `PACKAGE-TYPE.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL, replacing `PACKAGE-TYPE` with the Package namespace. For example, your Gemfile will be hosted at `rubygem.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`. - -{% else %} - -The package types supported on {% data variables.product.product_location_enterprise %} may vary since your site administrator can enable or disable support for different package types. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." - -If {% data variables.product.product_location_enterprise %} has subdomain isolation enabled, then package registries will use `PACKAGE-TYPE.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL, replacing `PACKAGE-TYPE` with the Package namespace. For example, your Dockerfile will be hosted at `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME`. - -If {% data variables.product.product_location_enterprise %} has subdomain isolation disabled, then package registries will use `HOSTNAME/_registry/PACKAGE-TYPE/OWNER/REPOSITORY/IMAGE-NAME` as the package host URL. For example, your Gemfile will be hosted at `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME`, replacing *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance. |{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Package namespace | -| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | ----------------------------------------------------- | -| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `npm.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gema` | `rubygems.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | nuget.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME` | - -{% else %} - -With subdomain isolation enabled on {% data variables.product.product_location_enterprise %}: - -| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Package namespace | -| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | ----------------------------------------------- | -| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `npm.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gema` | `rubygems.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `maven.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | `nuget.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | -| N/A | Plataforma de administración del contenedor Docker | `Dockerfile` | `Docker` | `docker.HOSTNAME/OWNER/REPOSITORY/IMAGE-NAME` | - -With subdomain isolation disabled on {% data variables.product.product_location_enterprise %}: - -| Lenguaje | Descripción | Formato del paquete | Cliente del paquete | Package namespace | -| ---------- | -------------------------------------------------------------- | ----------------------------------- | ------------------- | --------------------------------------------------------- | -| JavaScript | Gestor de paquetes Node | `package.json` | `npm` | `HOSTNAME/_registry/npm/OWNER/REPOSITORY/IMAGE-NAME` | -| Ruby | Gestor de paquetes RubyGems | `Gemfile` | `gema` | `HOSTNAME/_registry/rubygems/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de administración y comprensión Apache Maven | `pom.xml` | `mvn` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | -| Java | Herramienta de automatización de construcción Gradle para Java | `build.gradle` o `build.gradle.kts` | `gradle` | `HOSTNAME/_registry/maven/OWNER/REPOSITORY/IMAGE-NAME` | -| .NET | Administración del paquete NuGet para .NET | `nupkg` | `dotnet` CLI | `HOSTNAME/_registry/nuget/OWNER/REPOSITORY/IMAGE-NAME` | - -{% note %} - -**Note:** Docker is not supported when subdomain isolation is disabled. - -{% endnote %} - -For more information about subdomain isolation, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." - -{% endif %} - -Para obtener más información acerca de la configuración de tu cliente de paquete para usar con {% data variables.product.prodname_registry %}, consulta [Usar {% data variables.product.prodname_registry %} con el ecosistema de tu proyecto](/packages/using-github-packages-with-your-projects-ecosystem)." - -### Autenticar a {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -{% if currentVersion == "free-pro-team@latest" %} -### Sobre tokens - -| Ámbito | Descripción | -| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `read:packages` | Download and install container images from {% data variables.product.prodname_github_container_registry %} | -| `write:packages` | Upload and publish container images to {% data variables.product.prodname_github_container_registry %} | -| `delete:packages` | Delete specified versions of private or public container images from {% data variables.product.prodname_github_container_registry %}. For more information, see "[Deleting a container image](/packages/managing-container-images-with-github-container-registry/deleting-a-container-image)." | - -To learn about available scopes and permissions for container images, see "[About {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)" or "[Configuring access control and visibility for container images](/packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images)." - -Para obtener más información, consulta las secciones "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token/)" y "[Alcances disponibles](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)". - -{% endif %} - -### Administrar paquetes - -Para instalar o publicar un paquete, debes usar un token con el ámbito adecuado, y tu cuenta de usuario debe tener los permisos pertinentes para ese repositorio. - -Por ejemplo: -- Para descargar e instalar paquetes desde un repositorio, tu token debe tener el ámbito `read:packages`, y tu cuenta de usuario debe tener permisos de lectura para el repositorio. Si el repositorio es privado, tu token también debe tener el ámbito `repo`. -- Para eliminar una versión especificada de un paquete privado en {% data variables.product.product_name %}, tu token debe tener los ámbitos `delete:packages` y `repo`. Los paquetes públicos no se pueden eliminar. Para obtener más información, consulta "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package)". - -| Ámbito | Descripción | Permisos de repositorio | -| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | -| `read:packages` | Descarga e instala paquetes de {% data variables.product.prodname_registry %} | lectura | -| `write:packages` | Carga y publica paquetes en {% data variables.product.prodname_registry %} | escritura | -| `delete:packages` | Elimina versiones especificadas de paquetes privados de {% data variables.product.prodname_registry %} | admin | -| `repo` | Instala, carga y elimina determinados paquetes en repositorios privados (junto con `read:packages`, `write:packages` o `delete:packages`) | lectura, escritura o admin | - -Cuando creas un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes usar el `GITHUB_TOKEN` para publicar e instalar paquetes en {% data variables.product.prodname_registry %} sin la necesidad de almacenar y administrar un token de acceso personal. - -Para obtener más información, consulta: -- Encuentras algo que contradice la documentación -- "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token/)" -- Tu paquete publicado contiene datos confidenciales, como violaciones del RGPD, claves de API o información de identificación personal - -### Administrar paquetes - -Puedes eliminar una versión de un paquete privado en {% data variables.product.product_name %} o usar la API de GraphQL. Cuando usas la API de GraphQL para consultar y eliminar paquetes privados, debes usar el mismo token que usas para autenticarte en {% data variables.product.prodname_registry %}. Para obtener más información, consulta las secciones "[Borrar un paquete](/packages/publishing-and-managing-packages/deleting-a-package)" y "[Formar llamadas con GraphQL](/v4/guides/forming-calls/)". - -Puedes configurar webhooks para suscribirte a eventos relacionados con paquetes, como cuando se publica o se actualiza un paquete. Para obtener más información, consulta el "[evento de webhook de `package`](/webhooks/event-payloads/#package)". - -### Contactar con soporte técnico - -{% if currentVersion == "free-pro-team@latest" %} -Si tienes comentarios o solicitudes de características para {% data variables.product.prodname_registry %}, usa el formulario de comentarios de [ para {% data variables.product.prodname_registry %}](https://support.github.com/contact/feedback?contact%5Bcategory%5D=github-packages). - -Contacta el {% data variables.contact.github_support %} sobre {% data variables.product.prodname_registry %} usando [nuestro formulario de contacto](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) si: - -* Encuentras algo que contradice la documentación -* Encuentras errores vagos o poco claros -* Tu paquete publicado contiene datos confidenciales, como violaciones del RGPD, claves de API o información de identificación personal - -{% else %} -If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators. - -{% endif %} diff --git a/translations/es-XL/content/packages/publishing-and-managing-packages/deleting-a-package.md b/translations/es-XL/content/packages/publishing-and-managing-packages/deleting-a-package.md deleted file mode 100644 index e5ad7c057b..0000000000 --- a/translations/es-XL/content/packages/publishing-and-managing-packages/deleting-a-package.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: Eliminar un paquete -intro: 'Puedes eliminar una versión de un paquete privado utilizando GraphQL o en {% data variables.product.product_name %}.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /github/managing-packages-with-github-packages/deleting-a-package -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - - -{% if currentVersion == "free-pro-team@latest" %} -### Acerca de la eliminación de paquetes privados - -En circunstancias especiales, por ejemplo, por razones legales o para cumplir con los estándares del RGPD, puedes solicitarle a {% data variables.contact.github_support %} que elimine un paquete público por ti, usando [nuestro formulario de contacto](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry). - -{% endif %} - -### Acerca de la eliminación de paquetes privados - -Solo puedes eliminar una versión especificada de un paquete privado en {% data variables.product.product_name %} o con la API de GraphQL. Para hacer que un paquete privado completo deje de aparecer en {% data variables.product.product_name %}, primero debes eliminar todas las versiones del paquete. - -{% if currentVersion == "free-pro-team@latest" %} -### Acerca de la eliminación paquetes públicos - -Para evitar que se rompan proyectos que dependan de tus paquetes, no puedes eliminar un paquete público completo o versiones específicas de un paquete público. - -En circunstancias especiales, por ejemplo, por razones legales o para cumplir con los estándares del RGPD, puedes solicitarle a {% data variables.contact.github_support %} que elimine un paquete público por ti, usando [nuestro formulario de contacto](https://github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Package%20Registry). - -{% else %} - -A continuación aparece un comando cURL de ejemplo para eliminar una versión de paquete con el ID de versión de paquete de `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, usando un token de acceso personal. - -{% endif %} - -### Nombres y versiones de paquetes reservados - -{% data reusables.package_registry.package-immutability %} - -### Eliminar una versión de un paquete privado en {% data variables.product.product_name %} - -Para eliminar una versión de un paquete privado, debes tener permisos de administrador en el repositorio. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.package_registry.packages-from-code-tab %} -3. Haz clic en el nombre del paquete que deseas eliminar. ![Nombre del paquete](/assets/images/help/package-registry/select-pkg-cloud.png) -4. A la derecha, usa el menú desplegable **Edit package (Editar paquete)** y selecciona "Manage versions" (Administrar versiones). ![Nombre del paquete](/assets/images/help/package-registry/manage-versions.png) -5. A la derecha de la versión que deseas eliminar, haz clic en **Delete (Eliminar)**. ![Botón para eliminar paquete](/assets/images/help/package-registry/delete-package-button.png) -6. Para confirmar la eliminación, escribe el nombre del paquete y haz clic en **I understand the consequences, delete this version (Comprendo las consecuencias, eliminar esta versión)**. ![Botón para confirmar la eliminación del paquete](/assets/images/help/package-registry/confirm-package-deletion.png) - -### Eliminar una versión de un paquete privado con GraphQL - -Usa la mutación `deletePackageVersion` en la API de GraphQL. Debes usar un token con los ámbitos `read:packages`, `delete:packages` y `repo`. Para obtener más información acerca de los tokens, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". - -A continuación aparece un comando cURL de ejemplo para eliminar una versión de paquete con el ID de versión de paquete de `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, usando un token de acceso personal. - -{% if currentVersion == "free-pro-team@latest" %} -``` -curl -X POST \ --H "Accept: application/vnd.github.package-deletes-preview+json" \ --H "Authorization: bearer TOKEN" \ --d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ -https://api.github.com/graphql -``` - -{% else %} - -``` -curl -X POST \ --H "Accept: application/vnd.github.package-deletes-preview+json" \ --H "Authorization: bearer TOKEN" \ --d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \ -HOSTNAME/graphql -``` - -{% endif %} - -Para encontrar todos los paquetes privados que publicaste en {% data variables.product.prodname_registry %}, junto con los ID de versión de los paquetes, puedes usar la conexión `registryPackagesForQuery`. Necesitarás un token con los ámbitos `read:packages` y `repo`. Necesitarás un token con los ámbitos `read:packages` y `repo`. - -Para obtener más información acerca de la mutación `deletePackageVersion`, consulta "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)". - -No puedes eliminar un paquete completo, pero si eliminas todas las versiones de un paquete, dejará de aparecer en {% data variables.product.product_name %} diff --git a/translations/es-XL/content/packages/publishing-and-managing-packages/index.md b/translations/es-XL/content/packages/publishing-and-managing-packages/index.md deleted file mode 100644 index 10af42ce52..0000000000 --- a/translations/es-XL/content/packages/publishing-and-managing-packages/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Publicar y administrar paquetes -shortTitle: Publicar y administrar paquetes -intro: 'Puedes publicar nuevos paquetes en {% data variables.product.prodname_registry %}, ver e instalar paquetes existentes y, en circunstancias especiales, eliminar paquetes existentes.' -redirect_from: - - /github/managing-packages-with-github-packages/publishing-and-managing-packages -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' -children: - - /about-github-packages - - /publishing-a-package - - /viewing-packages - - /installing-a-package - - /deleting-a-package ---- -{% data reusables.package_registry.packages-ghes-release-stage %} diff --git a/translations/es-XL/content/packages/publishing-and-managing-packages/installing-a-package.md b/translations/es-XL/content/packages/publishing-and-managing-packages/installing-a-package.md deleted file mode 100644 index ce7c3c6257..0000000000 --- a/translations/es-XL/content/packages/publishing-and-managing-packages/installing-a-package.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Instalar un paquete -intro: 'Puedes instalar un paquete desde {% data variables.product.prodname_registry %} y usar el paquete como dependencia en tu propio proyecto.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /github/managing-packages-with-github-packages/installing-a-package -permissions: Cualquier persona con permisos de lectura para un repositorio puede instalar un paquete desde ese repositorio. -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -### 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)". - -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. - -### Instalar un paquete - -Puedes instalar un paquete desde {% data variables.product.prodname_registry %} usando cualquier cliente de paquete compatible siguiendo las mismas pautas generales. - -1. Autenticar para {% data variables.product.prodname_registry %} usando las instrucciones para tu cliente de paquete. Para obtener más información, consulta "[Acerca de los tokens](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". -2. Instala el paquete usando las instrucciones para tu cliente de paquete. - -Para obtener instrucciones específicas para tu cliente de paquete, consulta "[Usar {% data variables.product.prodname_registry %} con el ecosistema de tu proyecto](/packages/using-github-packages-with-your-projects-ecosystem)". diff --git a/translations/es-XL/content/packages/publishing-and-managing-packages/publishing-a-package.md b/translations/es-XL/content/packages/publishing-and-managing-packages/publishing-a-package.md deleted file mode 100644 index c0ace75cab..0000000000 --- a/translations/es-XL/content/packages/publishing-and-managing-packages/publishing-a-package.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Publicar un paquete -intro: 'Puedes publicar un paquete en {% data variables.product.prodname_registry %} para que el paquete esté disponible para que otros lo descarguen y lo vuelvan a utilizar.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /github/managing-packages-with-github-packages/publishing-a-package -permissions: Cualquier persona con permisos de escritura para un repositorio puede publicar un paquete en ese repositorio. -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -### Acerca de los paquetes publicados - -Puedes ayudar a la gente a entender y usar tu paquete proporcionando una descripción y otros detalles como instrucciones de instalación y uso en la página del paquete. GitHub proporciona metadatos para cada versión, como la fecha de publicación, la actividad de descarga y las versiones recientes. Para obtener una página de paquete de ejemplo, consulta [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). - -{% data reusables.package_registry.public-or-private-packages %} Un repositorio puede contener más de un paquete. Para evitar confusiones, asegúrate de que el archivo README y la descripción proporcionen información clara de cada paquete. - -{% data reusables.package_registry.package-immutability %} - -{% if currentVersion == "free-pro-team@latest" %} -Si una versión nueva de un paquete soluciona una vulnerabilidad de seguridad, deberás publicar una asesoría de seguridad en tu repositorio. {% data variables.product.prodname_dotcom %} revisa cada asesoría de seguridad publicada y podria utilizarla para enviar alertas de {% data variables.product.prodname_dependabot_short %} a los repositorios afectados. Para obtener más información, consulta la sección "[Acerca de las Asesorías de Seguridad de GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)". -{% endif %} - -### Publicar un paquete - -Puedes publicar un paquete en {% data variables.product.prodname_registry %} mediante cualquier cliente de paquete compatible siguiendo las mismas pautas generales. - -1. Crea o usa un token de acceso existente con los ámbitos adecuados para la tarea que deseas realizar. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". -2. Autentícate en {% data variables.product.prodname_registry %} mediante tu token de acceso y las instrucciones para tu cliente del paquete. -3. Publica el paquete siguiendo las instrucciones para el cliente de tu paquete. - -Para obtener instrucciones específicas para tu cliente de paquete, consulta "[Usar {% data variables.product.prodname_registry %} con el ecosistema de tu proyecto](/packages/using-github-packages-with-your-projects-ecosystem)". - -Después de que publiques un paquete, puedes verlo en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Ver paquetes](/packages/publishing-and-managing-packages/viewing-packages)." diff --git a/translations/es-XL/content/packages/publishing-and-managing-packages/viewing-packages.md b/translations/es-XL/content/packages/publishing-and-managing-packages/viewing-packages.md deleted file mode 100644 index d6006ed586..0000000000 --- a/translations/es-XL/content/packages/publishing-and-managing-packages/viewing-packages.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Ver paquetes -intro: Puedes ver detalles de los paquetes publicados en un repositorio y acotar los resultados por organización o por usuario. -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/viewing-a-repositorys-packages - - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages - - /github/managing-packages-with-github-packages/viewing-packages -permissions: Cualquier persona con permisos de lectura para un repositorio puede ver los paquetes del repositorio. -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -### Ver paquetes de un repositorio - -Los paquetes deben estar instalados al nivel del repositorio, pero puedes ver todos los paquetes de una organización y todos los paquetes que has publicado. {% data reusables.package_registry.package-page-info %} - -### Ver paquetes de un repositorio - -Puedes ver todos los paquetes de un repositorio y buscar un paquete específico en el repositorio. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.package_registry.packages-from-code-tab %} -{% data reusables.package_registry.navigate-to-packages %} - -### Ver los paquetes de una organización - -Puedes ver todos los paquetes instalados en una organización y buscar un paquete específico instalado en los repositorios de una organización. - -{% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -3. Debajo del nombre de tu organización, da clic -{% octicon "package" aria-label="The package icon" %} **Packages**. -{% data reusables.package_registry.navigate-to-packages %} - -### Ver tus paquetes - -Puedes ver todos los paquetes que has instalado y buscar uno específico en todas las organizaciones y repositorios. - -{% data reusables.profile.access_profile %} -2. En la parte superior de la página de perfil, en la navegación principal, haz clic en **Packages (Paquetes)**. ![Pestaña Project (Proyecto)](/assets/images/help/package-registry/user-packages-tab.png) -{% data reusables.package_registry.navigate-to-packages %} - -### Leer más - -- "[Buscar paquetes](/github/searching-for-information-on-github/searching-for-packages)" diff --git a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md b/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md deleted file mode 100644 index 13b5a865bc..0000000000 --- a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -title: Configuring Apache Maven for use with GitHub Packages -intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-apache-maven-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% data reusables.package_registry.admins-can-configure-package-types %} - -### Authenticating to {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -#### Authenticating with a personal access token - -{% data reusables.package_registry.required-scopes %} - -You can authenticate to {% data variables.product.prodname_registry %} with Apache Maven by editing your *~/.m2/settings.xml* file to include your personal access token. Create a new *~/.m2/settings.xml* file if one doesn't exist. - -In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your personal access token. - -In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% if currentVersion != "free-pro-team@latest" %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}*REPOSITORY* with the name of the repository you'd like to publish a package to or install a package from, and *OWNER* with the name of the user or organization account that owns the repository. {% data reusables.package_registry.lowercase-name-field %} - -If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag. - -{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation enabled: -{% endif %} - -``` - - - - github - - - - - github - - - central - https://repo1.maven.org/maven2 - true - true - - - github - GitHub OWNER Apache Maven Packages - https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY - - - - - - - - github - USERNAME - TOKEN - - - -``` - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation disabled: - -``` - - - - github - - - - - github - - - central - https://repo1.maven.org/maven2 - true - true - - - github - GitHub OWNER Apache Maven Packages - https://HOSTNAME/_registry/maven/OWNER/REPOSITORY - - - - - - - - github - USERNAME - TOKEN - - - -``` -{% endif %} - -#### Authenticating with the `GITHUB_TOKEN` - -{% data reusables.package_registry.package-registry-with-github-tokens %} - -### Publishing a package - -{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example:test` in a repository called `OWNER/test`. - -If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository. - -For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). - -1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% if currentVersion != "free-pro-team@latest" %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project. - {% if currentVersion != "free-pro-team@latest" %} - If your instance has subdomain isolation enabled: - {% endif %} - ``` - - - github - GitHub OWNER Apache Maven Packages - https://{% if currentVersion == "free-pro-team@latest" %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY - - - ``` - {% if currentVersion != "free-pro-team@latest" %} - If your instance has subdomain isolation disabled: - ``` - - - github - GitHub OWNER Apache Maven Packages - https://HOSTNAME/_registry/maven/OWNER/REPOSITORY - - - ``` - {% endif %} -2. Publish the package. - - ```shell - $ mvn deploy - ``` - -{% data reusables.package_registry.viewing-packages %} - -### Installing a package - -To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation. - -{% data reusables.package_registry.authenticate-step %} -2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package. - - ``` - - - com.example - test - 1.0.0-SNAPSHOT - - - ``` -3. Install the package. - - ```shell - $ mvn install - ``` - -### Further reading - -- "[Configuring Gradle for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages)" -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages.md b/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages.md deleted file mode 100644 index 59c0d2c8b8..0000000000 --- a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -title: Configuring Docker for use with GitHub Packages -intro: 'You can configure the Docker client to use {% data variables.product.prodname_registry %} to publish and retrieve docker images.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-docker-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% data reusables.package_registry.admins-can-configure-package-types %} - -### About Docker and {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.docker_registry_deprecation_status %} - -When installing or publishing a docker image, {% data variables.product.prodname_registry %} does not currently support foreign layers, such as Windows images. - -{% if currentVersion != "free-pro-team@latest" %} - -Before you can use the Docker registry on {% data variables.product.prodname_registry %}, the site administrator for {% data variables.product.product_location_enterprise %} must enable Docker support and subdomain isolation for your instance. For more information, see "[Managing GitHub Packages for your enterprise](/enterprise/admin/packages)." - -{% endif %} - -### Authenticating to {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.docker_registry_deprecation_status %} - -{% data reusables.package_registry.authenticate-packages %} - -#### Authenticating with a personal access token - -{% data reusables.package_registry.required-scopes %} - -You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command. - -To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file. - -{% if currentVersion == "free-pro-team@latest" %} -{% raw %} - ```shell - $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin - ``` -{% endraw %} -{% endif %} - -{% if currentVersion != "free-pro-team@latest" %} -{% raw %} - ```shell - $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin -``` -{% endraw %} -{% endif %} - -To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% if currentVersion != "free-pro-team@latest" %}, `HOSTNAME` with the URL for {% data variables.product.product_location_enterprise %},{% endif %} and `~/TOKEN.txt` with the file path to your personal access token for {% data variables.product.product_name %}. - -For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)." - -#### Authenticating with the `GITHUB_TOKEN` - -{% data reusables.package_registry.package-registry-with-github-tokens %} - -### Publishing a package - -{% data reusables.package_registry.docker_registry_deprecation_status %} - -{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. - -{% data reusables.package_registry.lowercase-name-field %} - -{% data reusables.package_registry.viewing-packages %} - -1. Determine the image name and ID for your docker image using `docker images`. - ```shell - $ docker images - > < > - > REPOSITORY TAG IMAGE ID CREATED SIZE - > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB - ``` -2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if currentVersion != "free-pro-team@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location_enterprise %},{% endif %} and *VERSION* with package version at build time. - {% if currentVersion == "free-pro-team@latest" %} - ```shell - $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% else %} - ```shell - $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% endif %} -3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% if currentVersion != "free-pro-team@latest" %} *HOSTNAME* with the hostname of {% data variables.product.product_location_enterprise %},{% endif %} and *PATH* to the image if it isn't in the current working directory.s - {% if currentVersion == "free-pro-team@latest" %} - ```shell - $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH - ``` - {% else %} - ```shell - $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH - ``` - {% endif %} -4. Publish the image to {% data variables.product.prodname_registry %}. - {% if currentVersion == "free-pro-team@latest" %} - ```shell - $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% else %} - ```shell - $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION - ``` - {% endif %} - {% note %} - - **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. - - {% endnote %} - -#### Example publishing a Docker image - -{% data reusables.package_registry.docker_registry_deprecation_status %} - -You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. - -{% if currentVersion == "free-pro-team@latest" %} -```shell -$ docker images - -> REPOSITORY TAG IMAGE ID CREATED SIZE -> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB - -# Tag the image with OWNER/REPO/IMAGE_NAME -$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0 - -# Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 -``` - -{% else %} - -```shell -$ docker images - -> REPOSITORY TAG IMAGE ID CREATED SIZE -> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB - -# Tag the image with OWNER/REPO/IMAGE_NAME -$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 - -# Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 -``` - -{% endif %} - -You can publish a new Docker image for the first time and name it `monalisa`. - -{% if currentVersion == "free-pro-team@latest" %} -```shell -# Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION -# Assumes Dockerfile resides in the current working directory (.) -$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 . - -# Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 -``` - -{% else %} -```shell -# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION -# Assumes Dockerfile resides in the current working directory (.) -$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . - -# Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 -``` -{% endif %} - -### Installing a package - -{% data reusables.package_registry.docker_registry_deprecation_status %} - -You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% if currentVersion != "free-pro-team@latest" %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance, {% endif %} and *TAG_NAME* with tag for the image you want to install. {% data reusables.package_registry.lowercase-name-field %} - -{% if currentVersion == "free-pro-team@latest" %} -```shell -$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME -``` -{% else %} -```shell -$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME -``` -{% endif %} - -{% note %} - -**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. - -{% endnote %} - -### Further reading - -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md b/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md deleted file mode 100644 index 8589ea0ca0..0000000000 --- a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -title: Configuring `dotnet` CLI for use with GitHub Packages -intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-nuget-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages - - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% data reusables.package_registry.admins-can-configure-package-types %} - -### Authenticating to {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -#### Authenticating with a personal access token - -{% data reusables.package_registry.required-scopes %} - -To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client. - -You must replace: -- `USERNAME` with the name of your user account on {% data variables.product.prodname_dotcom %}. -- `TOKEN` with your personal access token. -- `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if currentVersion != "free-pro-team@latest" %} -- `HOSTNAME` with the host name for your {% data variables.product.prodname_ghe_server %} instance. - -If your instance has subdomain isolation enabled: -{% endif %} - -```xml - - - - - - - - - - - - - -``` - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation disabled: - -```xml - - - - - - - - - - - - - -``` -{% endif %} - -#### Authenticating with the `GITHUB_TOKEN` - -{% data reusables.package_registry.package-registry-with-github-tokens %} - -### Publishing a package - -You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file. When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/en-us/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. - -{% data reusables.package_registry.viewing-packages %} - -{% data reusables.package_registry.authenticate-step %} -2. Create a new project. - ```shell - dotnet new console --name OctocatApp - ``` -3. Add your project's specific information to your project's file, which ends in *.csproj*. You must replace: - - `OWNER` with the name of the user or organization account that owns the repository containing your project. - - `REPOSITORY` with the name of the repository containing the package you want to publish. - - `1.0.0` with the version number of the package.{% if currentVersion != "free-pro-team@latest" %} - - `HOSTNAME` with the host name for your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - ``` xml - - - - Exe - netcoreapp3.0 - OctocatApp - 1.0.0 - Octocat - GitHub - This package adds an Octocat! - https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY - - - - ``` -4. Package the project. - ```shell - dotnet pack --configuration Release - ``` - -5. Publish the package using the `key` you specified in the *nuget.config* file. - ```shell - dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" - ``` - -### Publishing multiple packages to the same repository - -To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. - -For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository: - -``` xml - - - - Exe - netcoreapp3.0 - OctodogApp - 1.0.0 - Octodog - GitHub - This package adds an Octodog! - https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs - - - -``` - -``` xml - - - - Exe - netcoreapp3.0 - OctocatApp - 1.0.0 - Octocat - GitHub - This package adds an Octocat! - https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs - - - -``` - - -### Installing a package - -Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/en-us/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. - -{% data reusables.package_registry.authenticate-step %} - -2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file, replacing the `OctokittenApp` package with your package dependency and `1.0.0` with the version you want to use: - ``` xml - - - - Exe - netcoreapp3.0 - OctocatApp - 1.0.0 - Octocat - GitHub - This package adds an Octocat! - https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY - - - - - - - - ``` - -3. Install the packages with the `restore` command. - ```shell - dotnet restore - ``` - -### Further reading - -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md b/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md deleted file mode 100644 index cd19ba6ac8..0000000000 --- a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages.md +++ /dev/null @@ -1,234 +0,0 @@ ---- -title: Configurar Gradle para usar con paquetes de GitHub -intro: 'Puedes configurar Gradle para publicar paquetes para {% data variables.product.prodname_registry %} y utilizar paquetes almacenados en {% data variables.product.prodname_registry %} como dependencias en un proyecto Java.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-gradle-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -**Nota:** Cuando instalas o publicas una imagen de docker, {% data variables.product.prodname_registry %} no es compatible con capas externas, tales como imágenes de Windows. - -### Autenticar a {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -#### Autenticando con un token de acceso personal - -{% data reusables.package_registry.required-scopes %} - -Puedes autenticar a {% data variables.product.prodname_registry %} con Gradle usando ya sea Gradle Groovy o Kotlin DSL editando tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL) para incluir tu token de acceso personal. También puedes configurar Gradle Groovy y Kotlin DSL para que reconozcan un paquete único o múltiples paquetes en un repositorio. - -{% if currentVersion != "free-pro-team@latest" %} -Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance. -{% endif %} - -Reemplaza *USERNAME* con tu nombre de usuario {% data variables.product.prodname_dotcom %}, *TOKEN* con tu token de acceso personal, *REPOSITORY* con el nombre del repositorio que contiene el paquete que deseas publicar y *OWNER* con el nombre de la cuenta de usuario o de organización en {% data variables.product.prodname_dotcom %} que posee el repositorio. {% data reusables.package_registry.lowercase-name-field %} - -{% note %} - -**Nota:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} Para obtener un ejemplo, consulta "[Configurar Apache Maven para usar con {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)." - -{% endnote %} - -##### Ejemplo de uso de Gradle Groovy para un paquete único en un repositorio - -```shell -plugins { - id("maven-publish") -} - -publishing { - repositories { - maven { - name = "GitHubPackages" - url = uri("https://maven.pkg.github.com/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") - } - } - } - publications { - gpr(MavenPublication) { - from(components.java) - } - } -} -``` - -##### Ejemplo usando Gradle Groovy para múltiples paquetes en el mismo repositorio - -```shell -plugins { - id("maven-publish") apply false -} - -subprojects { - apply plugin: "maven-publish" - publishing { - repositories { - maven { - name = "GitHubPackages" - url = uri("https://maven.pkg.github.com/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") - } - } - } - publications { - gpr(MavenPublication) { - from(components.java) - } - } - } -} -``` - -##### Ejemplo de uso de Kotlin DSL para un paquete único en el mismo repositorio - -```shell -plugins { - `maven-publish` -} - -publishing { - repositories { - maven { - name = "GitHubPackages" - url = uri("https://maven.pkg.github.com/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") - } - } - } - publications { - register("gpr") { - from(components["java"]) - } - } -} ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") - } - } - } - publications { - register("gpr") { - from(components["java"]) - } - } -} -``` - -##### Ejemplo de uso de Kotlin DSL para múltiples paquetes en el mismo repositorio - - ```shell - plugins { - `maven-publish` apply false - } - - subprojects { - apply(plugin = "maven-publish") - configure { - repositories { - maven { - name = "GitHubPackages" - url = uri("https://maven.pkg.github.com/OWNER/REPOSITORY") - credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") - } - } - } - publications { - register("gpr") { - from(components["java"]) - } - } - } - } ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") - } - } - } - publications { - register("gpr") { - from(components["java"]) - } - } - } - } - ``` - - #### Autenticarse con el `GITHUB_TOKEN` - - {% data reusables.package_registry.package-registry-with-github-tokens %} - - Para obtener más información acerca del uso de `GITHUB_TOKEN` con Maven, consulta "[Publicar paquetes Java con Maven](/actions/language-and-framework-guides/publishing-java-packages-with-maven#publishing-packages-to-github-packages)". - - ### Publicar un paquete - - {% data reusables.package_registry.default-name %} Por ejemplo, {% data variables.product.prodname_dotcom %} publicará un paquete denominado `com.example.test` en el repositorio `OWNER/test` {% data variables.product.prodname_registry %}. - - {% data reusables.package_registry.viewing-packages %} - - {% data reusables.package_registry.authenticate-step %} - 2. Después de crear tu paquete, puedes publicar el paquete. - - ```shell - $ gradle publish - ``` - -### Instalar un paquete - -Puedes instalar un paquete agregando el paquete como una dependencia 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). - - Ejemplo de uso de Grady Groovy: - ```shell - dependencies { - implementation 'com.example:package' - } - ``` - Ejemplo de uso de Kotlin DSL: - ```shell - dependencies { - implementation("com.example:package") - } - ``` - -3. Agrega el complemento Maven a tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL). - - Ejemplo de uso de Grady Groovy: - ```shell - plugins { - id 'maven' - } - ``` - Ejemplo de uso de Kotlin DSL: - ```shell - plugins { - `maven` - } - ``` - - 3. Instala el paquete. - - ```shell - $ gradle install - ``` - -### Leer más - -- "[Configurar Apache Maven para usar con {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)" -- "[Eliminar un paquete](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md b/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md deleted file mode 100644 index efc0e2d450..0000000000 --- a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -title: Configuring npm for use with GitHub Packages -intro: 'You can configure npm to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in an npm project.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-npm-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% data reusables.package_registry.admins-can-configure-package-types %} - -### Authenticating to {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -#### Authenticating with a personal access token - -{% data reusables.package_registry.required-scopes %} - -You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token. - -To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% if currentVersion != "free-pro-team@latest" %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist. - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation enabled: -{% endif %} - -```shell -//{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN -``` - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation disabled: - -```shell -//HOSTNAME/_registry/npm/:_authToken=TOKEN -``` -{% endif %} - -To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address. - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation enabled: -{% endif %} - -```shell -$ npm login --registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} -> Username: USERNAME -> Password: TOKEN -> Email: PUBLIC-EMAIL-ADDRESS -``` - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation disabled: - -```shell -$ npm login --registry=https://HOSTNAME/_registry/npm/ -> Username: USERNAME -> Password: TOKEN -> Email: PUBLIC-EMAIL-ADDRESS -``` -{% endif %} - -#### Authenticating with the `GITHUB_TOKEN` - -{% data reusables.package_registry.package-registry-with-github-tokens %} - -### Publishing a package - -By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. You can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation. - -You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)." - -You can set up the scope mapping for your project using either a local *.npmrc* file in the project or using the `publishConfig` option in the *package.json*. {% data variables.product.prodname_registry %} only supports scoped npm packages. Scoped packages have names with the format of `@owner/name`. Scoped packages always begin with an `@` symbol. You may need to update the name in your *package.json* to use the scoped name. For example, `"name": "@codertocat/hello-world-npm"`. - -{% data reusables.package_registry.viewing-packages %} - -#### Publishing a package using a local *.npmrc* file - -You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}. {% data reusables.package_registry.lowercase-name-field %} - -{% data reusables.package_registry.authenticate-step %} -{% data reusables.package_registry.create-npmrc-owner-step %} -{% data reusables.package_registry.add-npmrc-to-repo-step %} -4. Verify the name of your package in your project's *package.json*. The `name` field must contain the scope and the name of the package. For example, if your package is called "test", and you are publishing to the "My-org" {% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`. -{% data reusables.package_registry.verify_repository_field %} -{% data reusables.package_registry.publish_package %} - -#### Publishing a package using `publishConfig` in the *package.json* file - -You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation. - -1. Edit the *package.json* file for your package and include a `publishConfig` entry. - {% if currentVersion != "free-pro-team@latest" %} - If your instance has subdomain isolation enabled: - {% endif %} - ```shell - "publishConfig": { - "registry":"https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" - }, - ``` - {% if currentVersion != "free-pro-team@latest" %} - If your instance has subdomain isolation disabled: - ```shell - "publishConfig": { - "registry":"https://HOSTNAME/_registry/npm/" - }, - ``` - {% endif %} -{% data reusables.package_registry.verify_repository_field %} -{% data reusables.package_registry.publish_package %} - -### Publishing multiple packages to the same repository - -To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package. - -To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. - -{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name. If you store the *package.json* file outside the root directory of your repository, you can use the `directory` field to specify the location where {% data variables.product.prodname_registry %} can find the *package.json* files. - -```shell -"repository" : { - "type" : "git", - "url": "ssh://git@{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY.git", - "directory": "packages/name" - }, -``` - -### Installing a package - -You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation. - -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. - -{% data reusables.package_registry.authenticate-step %} -{% data reusables.package_registry.create-npmrc-owner-step %} -{% data reusables.package_registry.add-npmrc-to-repo-step %} -4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency. - - ``` - { - "name": "@my-org/server", - "version": "1.0.0", - "description": "Server app that uses the @octo-org/octo-app package", - "main": "index.js", - "author": "", - "license": "MIT", - "dependencies": { - "@octo-org/octo-app": "1.0.0" - } - } - ``` -5. Install the package. - - ```shell - $ npm install - ``` - -#### Installing packages from other organizations - -By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% if currentVersion != "free-pro-team@latest" %}*HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. {% data reusables.package_registry.lowercase-name-field %} - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation enabled: -{% endif %} - -```shell -registry=https://{% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}/OWNER -@OWNER:registry={% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} -@OWNER:registry={% if currentVersion == "free-pro-team@latest" %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} -``` - -{% if currentVersion != "free-pro-team@latest" %} -If your instance has subdomain isolation disabled: - -```shell -registry=https://HOSTNAME/_registry/npm/OWNER -@OWNER:registry=HOSTNAME/_registry/npm/ -@OWNER:registry=HOSTNAME/_registry/npm/ -``` -{% endif %} - -### Further reading - -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages.md b/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages.md deleted file mode 100644 index 35f32a1ae3..0000000000 --- a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: Configuring RubyGems for use with GitHub Packages -intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /articles/configuring-rubygems-for-use-with-github-package-registry - - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry - - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -{% data reusables.package_registry.admins-can-configure-package-types %} - -### Prerequisites - -- You must have rubygems 2.4.1 or higher. To find your rubygems version: - - ```shell - $ gem --version - ``` - - - You must have bundler 1.6.4 or higher. To find your Bundler version: - ```shell - $ bundle --version - Bundler version 1.13.7 - ``` - - - Install keycutter to manage multiple credentials. To install keycutter: - ```shell - $ gem install keycutter - ``` - -### Authenticating to {% data variables.product.prodname_registry %} - -{% data reusables.package_registry.authenticate-packages %} - -#### Authenticating with a personal access token - -{% data reusables.package_registry.required-scopes %} - -You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems. - -To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your personal access token. Create a new *~/.gem/credentials* file if this file doesn't exist. - -For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your personal access token. - -```shell ---- -:github: Bearer TOKEN -``` - -To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace: - - `USERNAME` with your {% data variables.product.prodname_dotcom %} username. - - `TOKEN` with your personal access token. - - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% if currentVersion != "free-pro-team@latest" %} - - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance. -{% endif %} - -If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example. - -```shell ---- -:backtrace: false -:bulk_threshold: 1000 -:sources: -- https://rubygems.org/ -- https://USERNAME:TOKEN@{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/ -:update_sources: true -:verbose: true - -``` - -To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% if currentVersion != "free-pro-team@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - -{% data reusables.package_registry.lowercase-name-field %} - -```shell -$ bundle config https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN -``` - -#### Authenticating with the `GITHUB_TOKEN` - -{% data reusables.package_registry.package-registry-with-github-tokens %} - -### Publishing a package - -{% data reusables.package_registry.default-name %} For example, when you publish `octo-gem` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/octo-gem` repository. For more information on creating your gem, see "[Make your own gem](http://guides.rubygems.org/make-your-own-gem/)" in the RubyGems documentation. - -{% data reusables.package_registry.viewing-packages %} - -{% data reusables.package_registry.authenticate-step %} -2. Build the package from the *gemspec* to create the *.gem* package. - ```shell - gem build OCTO-GEM.gemspec - ``` -3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `OCTO-GEM` with the name of your gem package.{% if currentVersion != "free-pro-team@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - - ```shell - $ gem push --key github \ - --host https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ - OCTO-GEM-0.0.1.gem - ``` - -### Publishing multiple packages to the same repository - -To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% if currentVersion != "free-pro-team@latest" %} Replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - -``` -gem.metadata = { "github_repo" => "ssh://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } -``` - -### Installing a package - -You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing you *Gemfile*. - -{% data reusables.package_registry.authenticate-step %} -2. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% if currentVersion != "free-pro-team@latest" %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% endif %} - - ``` - source "https://rubygems.org" - - gem "rails" - - source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do - gem "GEM NAME" - end - ``` - -3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](http://bundler.io/v1.5/gemfile.html). - - ``` - source "https://{% if currentVersion == "free-pro-team@latest" %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" - source "https://rubygems.org" - - gem "rails" - gem "GEM NAME" - ``` - -4. Install the package: - ```shell - $ gem install octo-gem --version "0.1.1" - ``` - -### Further reading - -- "[Deleting a package](/packages/publishing-and-managing-packages/deleting-a-package/)" diff --git a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/index.md b/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/index.md deleted file mode 100644 index bc89edcbd5..0000000000 --- a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/index.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Usar GitHub Packages con el ecosistema de tu proyecto -shortTitle: Usar GitHub Packages con el ecosistema de tu proyecto -intro: 'Puedes configurar {% data variables.product.prodname_actions %} o a tu cliente de paquete para que funcione con {% data variables.product.prodname_registry %}.' -redirect_from: - - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' -children: - - /using-github-packages-with-github-actions - - /configuring-docker-for-use-with-github-packages - - /configuring-apache-maven-for-use-with-github-packages - - /configuring-gradle-for-use-with-github-packages - - /configuring-npm-for-use-with-github-packages - - /configuring-dotnet-cli-for-use-with-github-packages - - /configuring-rubygems-for-use-with-github-packages ---- -{% data reusables.package_registry.packages-ghes-release-stage %} diff --git a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions.md b/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions.md deleted file mode 100644 index 8875879a16..0000000000 --- a/translations/es-XL/content/packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Using GitHub Packages with GitHub Actions -intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.' -product: '{% data reusables.gated-features.packages %}' -redirect_from: - - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions -versions: - free-pro-team: '*' - enterprise-server: '>=2.22' ---- - -{% data reusables.package_registry.packages-ghes-release-stage %} - -### About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} - -{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)." - -You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow. - -{% if currentVersion == "free-pro-team@latest" %} -#### Authenticating to {% data variables.product.prodname_github_container_registry %} - -{% data reusables.package_registry.container-registry-beta %} - -{% data reusables.package_registry.authenticate_with_pat_for_container_registry %} - -For an authentication example, see "[Authenticating with the {% data variables.product.prodname_container_registry %}](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images#authenticating-with-the-container-registry)." - -{% endif %} - -#### Authenticating to package registries on {% data variables.product.prodname_dotcom %} - -{% if currentVersion == "free-pro-team@latest" %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. The `GITHUB_TOKEN` has `read:packages` and `write:packages` scopes to the current repository. For forks, the token also has the `read:packages` scope for the parent repository. - -You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." - -### Publishing a package using an action - -You can publish packages as part of your continuous integration (CI) flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to the default branch, the workflow runs CI tests. If those tests pass, the workflow publishes a new package version to {% data variables.product.prodname_registry %}. This workflow automates the creation of new package versions only if the code meets your quality standards. - -{% data reusables.package_registry.actions-configuration %} - -### Installing a package using an action - -You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies. - -Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use `GITHUB_TOKEN`.{% if currentVersion == "free-pro-team@latest" %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)."{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -`GITHUB_TOKEN` cannot install packages from any private repository besides the repository where the action runs. You cannot currently use `GITHUB_TOKEN` to authenticate to {% data variables.product.prodname_github_container_registry %}. -{% endif %} - -{% data reusables.package_registry.actions-configuration %} diff --git a/translations/es-XL/content/rest/guides/basics-of-authentication.md b/translations/es-XL/content/rest/guides/basics-of-authentication.md deleted file mode 100644 index 2269b6f217..0000000000 --- a/translations/es-XL/content/rest/guides/basics-of-authentication.md +++ /dev/null @@ -1,308 +0,0 @@ ---- -title: Información básica sobre la autenticación -intro: Aprende acerca de las formas diferentes de autenticarse con algunos ejemplos. -redirect_from: - - /guides/basics-of-authentication - - /v3/guides/basics-of-authentication - - /rest/basics-of-authentication -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -En esta sección, vamos a enfocarnos en lo básico de la autenticación. Específicamente, vamos a crear un servidor en Ruby (utilizando [Sintatra][Sinatra]) que implemente el [flujo web][webflow] de una aplicación en varias formas diferentes. - -{% tip %} - -Puedes descargar todo el código fuente de este proyecto [del repo platform-samples](https://github.com/github/platform-samples/tree/master/api/). - -{% endtip %} - -### Registrar tu app - -Primero, necesitas [registrar tu aplicación][new oauth app]. A cada aplicación de OAuth que se registra se le asigna una ID de Cliente única y un Secreto de Cliente. ¡El Secreto de Cliente no puede compartirse! Eso incluye el verificar la secuencia en tu repositorio. - -Puedes llenar toda la información como más te guste, con excepción de la **URL de rellamado para la autorización**. Esta es fácilmente la parte más importante para configurar tu aplicación. Es la URL de rellamado a la cual {% data variables.product.product_name %} devuelve al usuario después de una autenticación exitosa. - -Ya que estamos ejecutando un servidor común de Sinatra, la ubicación de la instancia local se configura como `http://localhost:4567`. Vamos a llenar la URL de rellamado como `http://localhost:4567/callback`. - -### Aceptar la autorización del usuario - -{% data reusables.apps.deprecating_auth_with_query_parameters %} - -Ahora, vamos a comenzar a llenar nuestro servidor común. Crea un archivo que se llame _server.rb_ y pégale esto: - -``` ruby -require 'sinatra' -require 'rest-client' -require 'json' - -CLIENT_ID = ENV['GH_BASIC_CLIENT_ID'] -CLIENT_SECRET = ENV['GH_BASIC_SECRET_ID'] - -get '/' do - erb :index, :locals => {:client_id => CLIENT_ID} -end -``` - -Tu ID de cliente y tus llaves secretas de cliente vienen de [la página de configuración de tu aplicación][app settings]. **_Jamás_** deberías almacenar estos valores en {% data variables.product.product_name %}--o en ningún otro lugar público, para el caso. Te recomendamos almacenarlos como [variables de ambiente][about env vars]--que es exactamente lo que hicimos aquí. - -Posteriormente, pega este contenido en _views/index.erb_: - -``` erb - - - - -

    - Well, hello there! -

    -

    - We're going to now talk to the GitHub API. Ready? - Click here to begin! -

    -

    - If that link doesn't work, remember to provide your own Client ID! -

    - - -``` - -(Si no estás familiarizado con la forma en que funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra guide].) - -También, ten en cuenta que la URL utiliza el parámetro de consulta `scope` para definir los [alcances][oauth scopes] que solicita la aplicación. Para nuestra aplicación, estamos solicitando el alcance `user:email` para leer las direcciones de correo electrónico privadas. - -Navega en tu buscador hacia `http://localhost:4567`. Después de dar clic en el enlace, se te llevará a {% data variables.product.product_name %} y se te mostrará un diálogo que se ve más o menos así: ![Diálogo de OAuth de GitHub](/assets/images/oauth_prompt.png) - -Si confías en ti mismo, da clic en **Autorizar App**. ¡Oh-oh! Sinatra te arroja un error `404`. ¡¿Qué pasa?! - -Bueno, ¡¿recuerdas cuando especificamos la URL de rellamado como `callback`? No proporcionamos una ruta para ésta, así que {% data variables.product.product_name %} no sabe dónde dejar al usuario después de autorizar la app. ¡Arreglémoslo ahora! - -#### Proporcionar un rellamado - -En _server.rb_, agrega una ruta para especificar lo que debe hacer la rellamada: - -``` ruby -get '/callback' do - # get temporary GitHub code... - session_code = request.env['rack.request.query_hash']['code'] - - # ... and POST it back to GitHub - result = RestClient.post('https://github.com/login/oauth/access_token', - {:client_id => CLIENT_ID, - :client_secret => CLIENT_SECRET, - :code => session_code}, - :accept => :json) - - # extract the token and granted scopes - access_token = JSON.parse(result)['access_token'] -end -``` - -Después de que la app se autentica exitosamente, {% data variables.product.product_name %} proporciona un valor temporal de `code`. Necesitas hacer `POST` para este código en {% data variables.product.product_name %} para intercambiarlo por un `access_token`. Para simplificar nuestras solicitudes HTTP de GET y de POST, utilizamos el [rest-client][REST Client]. Nota que probablemente jamás accedas a la API a través de REST. Para aplicarlo con más seriedad, probablemente debas usar [una biblioteca escrita en tu lenguaje preferido][libraries]. - -#### Verificar los alcances otorgados - -De ahora en adelante, los usuarios podrán [editar los alcances que solicitaste][edit scopes post] y se podría otorgar menos accesos a tu aplicación comparado con aquellos que solicitaste originalmente. Así que, antes de hacer cualquier solicitud con el token, deberías revisar los alcances que el usuario otorgó para dicho token. - -Los alcances que otorgamos se devuelven como parte de la respuesta de intercambiar un token. - -``` ruby -get '/callback' do - # ... - # Get the access_token using the code sample above - # ... - - # check if we were granted user:email scope - scopes = JSON.parse(result)['scope'].split(',') - has_user_email_scope = scopes.include? 'user:email' -end -``` - -En nuestra aplicación, estamos utilizando `scopes.include?` para verificar si se nos otorgó el alcance de `user:email` que necesitamos para recuperar las direcciones de correo electrónico. Si la aplicación hubiera preguntado por otros alcances, habríamos verificado esas también. - -También, ya que hay una relación jerárquica entre alcances, debes verificar que se te haya otorgado el nuvel más bajo de los alcances que se requieren. Por ejemplo, si la aplicación hubiera pedido el alcance `user`, puede que se le haya otorgado únicamente el alcance `user:email`. En ese caso, a la applicación no se le hubiera otorgado lo que pidió, pero los alcances que obtuvo hubieran seguido siendo suficientes. - -No es suficiente verificar los alcances solo antes de hacer las solicitudes, ya que es posible que los usuarios cambien los alcances entre tus solicitudes de verificación y las solicitudes reales. En caso de que esto suceda, las llamadas a la API que esperas tengan éxito podrían fallar con un estado `404` o `401`, o bien, podrían devolver un subconjunto de información diferente. - -Para ayudarte a manejar estas situaciones fácilmente, todas las respuestas de la API a las solicitudes que se hagan con tokens válidos también contienen un [encabezado de `X-OAuth-Scopes`][oauth scopes]. Este encabezado contiene la lista de alcances del token que se utilizó para realizar la solicitud. Adicionalmente, la API de Aplicaciones de OAuth proporciona una terminal para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} \[verificar la validez de un token\]\[/v3/apps/oauth_applications/#check-a-token\]{% else %}\[verificar la validez de un token\]\[/v3/apps/oauth_applications/#check-an-authorization\]{% endif %}. Utiliza esta información para detectar los cambios en los alcances de los tokens, y para informar a tus usuarios sobre los cambios diposnibles en la funcionalidad de la aplicación. - -#### Realizar solicitudes autenticadas - -Por fin, con este token de acceso, podrás hacer solicitudes autenticadas como el usuario que inició sesión: - -``` ruby -# fetch user information -auth_result = JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user', - {:params => {:access_token => access_token}})) - -# if the user authorized it, fetch private emails -if has_user_email_scope - auth_result['private_emails'] = - JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user/emails', - {:params => {:access_token => access_token}})) -end - -erb :basic, :locals => auth_result -``` - -Podemos hacer lo que queramos con nuestros resultados. En este caso, solo las vaciaremos directamente en _basic.erb_: - -``` erb -

    Hello, <%= login %>!

    -

    - <% if !email.nil? && !email.empty? %> It looks like your public email address is <%= email %>. - <% else %> It looks like you don't have a public email. That's cool. - <% end %> -

    -

    - <% if defined? private_emails %> - With your permission, we were also able to dig up your private email addresses: - <%= private_emails.map{ |private_email_address| private_email_address["email"] }.join(', ') %> - <% else %> - Also, you're a bit secretive about your private email addresses. - <% end %> -

    -``` - -### Implementar la autenticación "persistente" - -Estaríamos hablando de un pésimo modelo si requerimos que los usuarios inicien sesión en la app cada vez que necesiten acceder a la página web. Por ejemplo, intenta navegar directamente a `http://localhost:4567/basic`. Obtendrás un error. - -¿Qué pasaría si pudiéramos eludir todo el proceso de "da clic aquí" y solo lo _recordáramos_, siempre y cuando los usuarios estuviera ingresados en {% data variables.product.product_name %} y así, ellos pudieran acceder a esta aplicación? ¡Agárrate! porque _eso es exactamente lo que vamos a hacer_. - -Nuestro pequeño servidor que mostramos antes es muy simple. Para poder insertar algún tipo de autenticación inteligente, vamos a optar por utilizar sesiones para almacenar los tokens. Esto hará que la autenticación sea transparente para el usuario. - -También, ya que estamos haciendo persistir a los alcances dentro de la sesión, necesitaremos gestionar los casos cuando el usuario actualice los alcances después de que los verifiquemos, o cuando revoque el token. Para lograrlo, utilizaremos un bloque de `rescue` y verificaremos que la primera llamada a la API sea exitosa, lo cual verificará que el token sea válido. Después de esto, verificaremos el encabezado de respuesta de `X-OAuth-Scopes` para verificar que el usuario no haya revocado el alcance `user:email`. - -Crea un archivo que se llame _advanced_server.rb_, y pega estas líneas en él: - -``` ruby -require 'sinatra' -require 'rest_client' -require 'json' - -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below -# if ENV['GITHUB_CLIENT_ID'] && ENV['GITHUB_CLIENT_SECRET'] -# CLIENT_ID = ENV['GITHUB_CLIENT_ID'] -# CLIENT_SECRET = ENV['GITHUB_CLIENT_SECRET'] -# end - -CLIENT_ID = ENV['GH_BASIC_CLIENT_ID'] -CLIENT_SECRET = ENV['GH_BASIC_SECRET_ID'] - -use Rack::Session::Pool, :cookie_only => false - -def authenticated? - session[:access_token] -end - -def authenticate! - erb :index, :locals => {:client_id => CLIENT_ID} -end - -get '/' do - if !authenticated? - authenticate! - else - access_token = session[:access_token] - scopes = [] - - begin - auth_result = RestClient.get('{% data variables.product.api_url_code %}/user', - {:params => {:access_token => access_token}, - :accept => :json}) - rescue => e - # request didn't succeed because the token was revoked so we - # invalidate the token stored in the session and render the - # index page so that the user can start the OAuth flow again - - session[:access_token] = nil - return authenticate! - end - - # the request succeeded, so we check the list of current scopes - if auth_result.headers.include? :x_oauth_scopes - scopes = auth_result.headers[:x_oauth_scopes].split(', ') - end - - auth_result = JSON.parse(auth_result) - - if scopes.include? 'user:email' - auth_result['private_emails'] = - JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user/emails', - {:params => {:access_token => access_token}, - :accept => :json})) - end - - erb :advanced, :locals => auth_result - end -end - -get '/callback' do - session_code = request.env['rack.request.query_hash']['code'] - - result = RestClient.post('https://github.com/login/oauth/access_token', - {:client_id => CLIENT_ID, - :client_secret => CLIENT_SECRET, - :code => session_code}, - :accept => :json) - - session[:access_token] = JSON.parse(result)['access_token'] - - redirect '/' -end -``` - -La mayoría de este código debería serte familiar. Por ejemplo, aún estamos utilizando `RestClient.get` para llamar a la API de {% data variables.product.product_name %}, y aún estamos pasando nuestros resultados par que se interpreten en una plantilla de ERB (en esta ocasión, se llama `advanced.erb`). - -También, ahora tenemos el método `authenticated?`, el cual verifica si el usuario ya se autenticó. Si no, se llamará al método `authenticate!`, el cual lleva a cabo el flujo de OAuth y actualiza la sesión con el token que se otorgó y con los alcances. - -Después, crea un archivo en _views_, el cual se llame _advanced.erb_ y pega este markup dentro de él: - -``` erb - - - - -

    Well, well, well, <%= login %>!

    -

    - <% if !email.empty? %> It looks like your public email address is <%= email %>. - <% else %> It looks like you don't have a public email. That's cool. - <% end %> -

    -

    - <% if defined? private_emails %> - With your permission, we were also able to dig up your private email addresses: - <%= private_emails.map{ |private_email_address| private_email_address["email"] }.join(', ') %> - <% else %> - Also, you're a bit secretive about your private email addresses. - <% end %> -

    - - -``` - -Desde la líne de comandos, llama a `ruby advanced_server.rb`, lo cual inicia tu servidor en el puerto `4567` -- el mismo puerto que utilizamos cuando tuvimos una app de Sinatra sencilla. Cuando navegas a `http://localhost:4567`, la app llama a `authenticate!`, lo cual te redirige a `/callback`. Entonces, `/callback` nos regresa a `/` y, ya que estuvimos autenticados, interpreta a _advanced.erb_. - -Podríamos simplificar completamente esta ruta redonda si solo cambiamos nuestra URL de rellamado en {% data variables.product.product_name %} a `/`. Pero, ya que tanto _server.rb_ como _advanced.rb_ dependen de la misma URL de rellamado, necesitamos hacer un poco más de ajustes para que funcione. - -También, si nunca hubiéramos autorizado esta aplicación para acceder a nuestros datos de {% data variables.product.product_name %}, habríamos visto el mismo diálogo de confirmación del pop-up anterior para advertirnos. - -[webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ -[Sinatra]: http://www.sinatrarb.com/ -[about env vars]: http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables -[Sinatra guide]: https://github.com/sinatra/sinatra-book/blob/master/book/Introduction.markdown#hello-world-application -[REST Client]: https://github.com/archiloque/rest-client -[libraries]: /libraries/ -[oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[edit scopes post]: https://developer.github.com/changes/2013-10-04-oauth-changes-coming/ -[new oauth app]: https://github.com/settings/applications/new -[app settings]: https://github.com/settings/developers diff --git a/translations/es-XL/content/rest/guides/best-practices-for-integrators.md b/translations/es-XL/content/rest/guides/best-practices-for-integrators.md deleted file mode 100644 index bcce944dc3..0000000000 --- a/translations/es-XL/content/rest/guides/best-practices-for-integrators.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -title: Mejores prácticas para los integradores -intro: 'Crea una app que interactúe confiablemente con la API de {% data variables.product.prodname_dotcom %} y proporcione la mejor experiencia para tus usuarios.' -redirect_from: - - /guides/best-practices-for-integrators/ - - /v3/guides/best-practices-for-integrators -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - -¡Estás interesado en integrarte con la plataforma de GitHub? [Estás en las manos correctas](https://github.com/integrations). Esta guía te ayudará a crear una app que proporcione la mejor de las experiencias para tus usuarios *y* que garantice su confiabilidad al interactuar con la API. - - -### Asegura las cargas útiles que se entregen desde GitHub - -Es muy importante que asegures [las cargas útiles que se envíen desde GitHub][event-types]. Aunque en una carga útil jamás se transmita información personal (como las contraseñas), no es bueno filtrar *ninguna* información. Algunos de los tipos de información que pudieran ser sensibles incluyen las direcciones de correo electrónico del confirmante o los nombres de los repositorios privados. - -Hya varios pasos que puedes tomar para asegurar la recepción de las cárgas útiles que GitHub entregue: - -1. Asegúrate de que tu servidor receptor tenga una conexión HTTPS. Predeterminadamente, GitHub verificará los certificados SSl cuando entregue las cargas útiles.{% if currentVersion == "free-pro-team@latest" %} -1. Puedes agregar [La dirección IP que utilizamos cuando entregamos ganchos](/github/authenticating-to-github/about-githubs-ip-addresses) a tu lista de conexiones permitidas de tu servidor. Para garantizar que siempre estés verificando la dirección IP correcta, puedes [utilizar la terminal de `/meta`](/v3/meta/#meta) para encontrar la dirección que utilizamos.{% endif %} -1. Proporciona [un token secreto](/webhooks/securing/) para garantizar que las cargas útiles vengan de GitHub definitivamente. Al requerir un token secreto, te estás asegurando de que ninguno de los datos que recibe tu servidor viene de GitHub en lo absoluto. Idealmente, deberías proporcionar un token secreto diferente *por cada usuario* de tu servicio. Así, si un token se pone en riesgo, nadie más se vería afectado. - -### Favorece el trabajo asincrónico sobre el sincronizado - -GitHub espera que las integraciones respondan dentro de los primeros {% if currentVersion == "free-pro-team@latest" %}10{% else %}30{% endif %} segundos de que se reciba la carga útil del webhook. Si tu servicio demora más que eso para completarse, entonces GitHub finaliza la conexión y se pierde la carga útil. - -Ya que es imposible predecir qué tan rápido completará esto tu servidor, deberías hacer todo "el trabajo real" en un job que actúe en segundo plano. [Resque](https://github.com/resque/resque/) (para Ruby), [RQ](http://python-rq.org/) (para Python), o [RabbitMQ](http://www.rabbitmq.com/) (para JAVA) son algunos ejemplos de bibliotecas que pueden manejar jobs de segundo plano para procesamiento y formación en cola. - -Nota que, aún si tienes un job ejecutándose en segundo plano, GitHub sigue esperando que tu servidor responda dentro de {% if currentVersion == "free-pro-team@latest" %}diez{% else %}veinte{% endif %} segundos. Tu servidor necesita reconocer que recibió la carga útil mediante el envío de algún tipo de respuesta. Es crítico que tu servicio realice cualquier validación de una carga útil tan pronto sea posible, para que puedas reportar con exactitud si tu servidor continuará con la solicitud o no. - -### Utiliza códigos de estado de HTTP adecuados cuando respondas a GitHub - -Cada webhook tiene su propia sección de "Entregas Recientes", la cual lista si los despliegues tuvieron éxito o no. - -![Vista de entregas recientes](/assets/images/webhooks_recent_deliveries.png) - -Deberías utilizar códigos de estado de HTTP adecuados para informar a los usuarios. Puedes utilizar códigos como el `201` o el `202` para reconocer la recepción de las cargas útiles que no se van a procesar (por ejemplo, una carga útil que entregue una rama que no sea la predeterminada). Reserva el código de error `500` para las fallas catastróficas. - -### Proporciona al usuario tanta información como sea posible - -Los usuarios pueden profundizar en las respuestas del servidor que envíes de vuelta a GitHub. Asegúrate de que tus mensajes son claros e informativos. - -![Visualizar la respuesta de una carga útil](/assets/images/payload_response_tab.png) - -### Sigue cualquier redireccionamiento que te envíe la API - -GitHub es muy explícito en decirte cuando un recurso se migró y lo hace proporcionándote un código de estado de redirección. Debes seguir estas redirecciones. Cada respuesta de redirección configura el encabezado `Location` con la URI nueva a la cual debes dirigirte. Si recibes una redirección, es mejor que actualices tu código para seguir a la nueva URI, en caso de que estés utilizando una ruta obsoleta que tal ves eliminemos. - -Hemos proporcionado [una lista de códigos de estado de HTTP](/v3/#http-redirects) que puedes consultar cuando estés diseñando tu app para seguir las redirecciones. - -### No analices las URL manualmente - -A menudo, las respuestas a la API contienen datos en forma de URL. Por ejemplo, cuando solicitamos un repositorio, estamos enviando una clave denominada `clone_url` con la URL que puedes utilizar para clonar el repositorio. - -Para mantener la estabilidad de tu app, no deberías analizar estos datos o tratr de adivinar y construir el formato de las URL futuras. Tu app puede fallar si decidimos cambiar la URL. - -Por ejemplo, cuando estamos trabajando con resultados paginados, a menudo es tentador construir las URL que adjunten `?page=` al final. Evita esa tentación. [Nuestra guía sobre paginación](/guides/traversing-with-pagination) te ofrece tips de seguridad sobre cómo seguir resultados paginados de manera confiable. - -### Verifica el tipo de evento y de acción antes de procesar el evento - -Hay varios [tipos de eventos de webhook][event-types], y cada evento puede tener varias acciones. En medida en que el conjunto de características de GitHub crece, de vez en cuando agregaremos tipos de evento para nuevas acciones a los tipos de evento existentes. Asegúrate de que tu aplicación verifique el tipo y acción de un evento explícitamente antes de que hagas cualquier procesamiento de webhook. El encabezado de solicitud de `X-GitHub-Event` puede utilizarse para saber qué evento se recibió, para que el procesamiento se pueda gestionar de manera adecuada. De manera similar, la carga útil tiene una clave de `action` de alto nivel que puede utilizarse para saber qué acción se llevó a cabo en el objeto relevante. - -Por ejemplo, si configuraste un webhook de GitHub para "Enviarme **todo**", tu aplicación comenzará a recibir tipos de evento y acciones nuevos conforme se agreguen. Por lo tanto, **no se recomienda utilizar ningún tipo de cláusula "else" que reciba todo**. Toma como ejemplo el siguiente extracto de código: - -```ruby -# Not recommended: a catch-all else clause -def receive - event_type = request.headers["X-GitHub-Event"] - payload = request.body - - case event_type - when "repository" - process_repository(payload) - when "issues" - process_issues(payload) - else - process_pull_requests - end -end -``` - -En este ejemplo, se llamará correctamente a los métodos de `process_repository` y `process_issues` si se recibió un evento de `repository` o de `issues`. Sin embargo, cualquier otro tipo de evento resultaría en que se llamara a `process_pull_requests`. En medida en que se agreguen tipos de evento nuevos, esto dará como resultado un comportamiento incorrecto y los tipos de evento nuevos se procesarían de la misma forma que se haría con un evento de `pull_request`. - -En vez de esto, te sugerimos revisar los tipos de evento explícitamente y tomar acciones adecuadas para cada caso. En el siguiente ejemplo, estamos verificando explícitamente si hay eventos de `pull_request` y la cláusula `else` simplemente registra lo que recibimos en un tipo de evento nuevo: - -```ruby -# Recommended: explicitly check each event type -def receive - event_type = request.headers["X-GitHub-Event"] - payload = JSON.parse(request.body) - - case event_type - when "repository" - process_repository(payload) - when "issues" - process_issue(payload) - when "pull_request" - process_pull_requests(payload) - else - puts "Oooh, something new from GitHub: #{event_type}" - end -end -``` - -Ya que cada evento puede tener acciones múltiples también, se recomienda que las acciones se verifiquen de forma similar. Por ejemplo, el [`IssuesEvent`](/webhooks/event-payloads/#issues) tiene muchas acciones posibles. Estas incluyen a `opened` cuando se crea el informe de problemas, a `closed` cuando el informe de problemas se cierra, y a `assigned` cuando este informe se asigna a alguien. - -De la misma forma como agregamos tipos de evento, podemos agregar acciones nuevas a los eventos existentes. Por lo tanto, nuevamente **no se recomienda utilizar ningún tipo de cláusula "else" para recibir todo** cuando verificamos la acción de un evento. En vez de esto, te sugerimos verificar las acciones de evento explícitamente como lo hicimos con el tipo de evento. Un ejemplo de esto se ve muy similar a lo que sugerimos para los tipos de evento anteriormente: - -```ruby -# Recommended: explicitly check each action -def process_issue(payload) - case payload["action"] - when "opened" - process_issue_opened(payload) - when "assigned" - process_issue_assigned(payload) - when "closed" - process_issue_closed(payload) - else - puts "Oooh, something new from GitHub: #{payload["action"]}" - end -end -``` - -En este ejemplo, la acción `closed` se verifica primero antes de llamar al método `process_closed`. Cualquier acción sin identificar se registra para referencias futuras. - -{% if currentVersion == "free-pro-team@latest" %} - -### Lidiar con los límites de tasa - -El [límite de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting) de la API de GitHub se asegura de que la API sea rápida y esté disponible para todos. - -Si alcanzas un límite de tasa, se espera que te retires y no sigas haciendo solicitudes y que intentes más tarde cuando se te permita hacerlo. Si no lo haces, podríamos prohibir tu app. - -Siempre puedes [verificar el estado de tu límite de tasa](/rest/reference/rate-limit) en cualquier momento. El verificar tu límite de tasa no representa costo alguno para éste. - -### Lidiar con los abusos al límite de tasa - -[La sobre-explotación de los límites de tasa](/rest/overview/resources-in-the-rest-api#abuse-rate-limits) es otra forma en la que garantizamos la disponibilidad de la API. Para evitar llegar a este límite, deberás asegurarte de que tu aplicación siga los siguientes lineamientos. - -* Hacer solicitudes autenticadas, o utilizar la ID de cliente y secreto de tu aplicación. Las solicitudes sin autenticar están sujetas a un abuso del límite de tasa más agresivo. -* Hacer solicitudes en serie para solo un usuario o ID de cliente. No hagas solicitudes para solo un usuario o ID de cliente simultáneamente. -* Si haces muchas solicitudes de tipo `POST`, `PATCH`, `PUT`, o `DELETE` para un solo usuario o ID de cliente, espera por lo menos un segundo entre cada una. -* Cuando se te limita, utiliza el encabezado de respuesta `Retry-After` para bajar la velocidad. El valor del encabezado `Retry-After` siembre será un número entero, el cual representará la cantidad de segundos que debes esperar antes de volver a hacer la solicitud. Por ejemplo, `Retry-After: 30` significa que debes esperar 30 segundos antes de enviar más solicitudes. -* Las solicitudes que crean contenido que activa notificaciones, tales como informes de problemas, comentarios y solicitudes de extracción, puede limitarse aún más y no incluirá un encabezado de `Retry-After` en la respuesta. Por favor, crea este contenido con un ritmo razonable para evitar que se te limite nuevamente. - -Nos reservamos el derecho de cambiar estos lineamientos como sea necesario para garantizar la disponibilidad. - -{% endif %} - -### Lidiar con los errores de la API - -Aunque tu código jamás introducirá un error, podrías encontrarte con que has dado con varios errores sucesivos cuando intentas acceder a la API. - -En vez de ignorar los códigos de estado `4xx` y `5xx` repetidamente, debes asegurarte de que estás interactuando correctamente con la API. Por ejemplo, si una terminal solicita una secuencia y estás pasando un valor numérico, vas a recibir un error de validación `5xx`, y tu llamada no tendrá éxito. De forma similar, el intentar acceder a una terminal inexistente o no autorizada dará como resultado un error `4xx`. - -El ignorar los errores de validación constantes a propóstio podría resultar en la suspensión de tu app por abuso. - -[event-types]: /webhooks/event-payloads - -[event-types]: /webhooks/event-payloads diff --git a/translations/es-XL/content/rest/guides/building-a-ci-server.md b/translations/es-XL/content/rest/guides/building-a-ci-server.md deleted file mode 100644 index 5ef7d50166..0000000000 --- a/translations/es-XL/content/rest/guides/building-a-ci-server.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: Crear un servidor de IC -intro: Crea tu propio sistema de IC utilizando la API de Estados. -redirect_from: - - /guides/building-a-ci-server/ - - /v3/guides/building-a-ci-server -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -La [API de Estados][status API] es responsable de unir las confirmaciones con un servicio de pruebas para que cada carga que hagas pueda probarse y se represente en una solicitud de extracción de {% data variables.product.product_name %}. - -Esta guía utilizará esa API para ejemplificar una configuración que puedes utilizar. En nuestro escenario, nosotros: - -* Ejecutaremos nuestra suit de IC cuando se abra una Solicitud de Extracción (configuraremos el estado de IC como pendiente). -* Cuando finalice la IC, configuraremos el estado de la Solicitud de Extracción como corresponda. - -Nuestro sistema de IC y nuestro servidor host serán imaginarios. Podrían ser Travis, Jenkins, o algo completamente distinto. El meollo de esta guía será configurar y ajustar el servidor que administra la comunicación. - -Si aún no lo has hecho, asegúrate de [descargar ngrok][ngrok], y de aprender a [utilizarlo][using ngrok]. Consideramos que es una herramienta muy útil para exponer las conexiones locales. - -Nota: puedes descargar todo el código fuente para este proyecto [del repo platform-samples][platform samples]. - -### Escribir tu servidor - -Escribiremos una app de Sinatra rápidamente para probar que nuestras conexiones locales estén funcionando. Comencemos con esto: - -``` ruby -require 'sinatra' -require 'json' - -post '/event_handler' do - payload = JSON.parse(params[:payload]) - "Well, it worked!" -end -``` - -(Si no estás familiarizado con como funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra].) - -Inicia este servidor. Predeterminadamente, Sinatra inicia en el puerto `4567`, así que también debes configurar ngrok para comenzar a escuchar este puerto. - -Para que este servidor funcione, necesitaremos configurar un repositorio con un webhook. El webhook debe configurarse para que se active cada que se crea o fusiona una Solicitud de Extracción. Sigue adelante y crea un repositorio en el que quieras hacer tus experimentos. ¿Podríamos sugerirte que sea [el repositorio Spoon/Knife de @octocat](https://github.com/octocat/Spoon-Knife)? Después de esto, crearás un webhook nuevo en tu repositorio y lo alimentarás con la URL que te dio ngrok para luego escoger a `application/x-www-form-urlencoded` como el tipo de contenido: - -![Una URL de ngrok nueva](/assets/images/webhook_sample_url.png) - -Haz clic en **Actualizar webhook**. Deberás ver una respuesta en el cuerpo que diga `Well, it worked!`. ¡Genial! Da clic en **Déjame selecionar eventos individuales**, y selecciona lo siguiente: - -* Estado -* Solicitud de Extracción - -Estos son los eventos que {% data variables.product.product_name %} enviará a nuestro servidor cuando ocurra cualquier acción relevante. Vamos a actualizar nuestro servidor para que *solo* gestione el escenario de Solicitud de Extracción ahora: - -``` ruby -post '/event_handler' do - @payload = JSON.parse(params[:payload]) - - case request.env['HTTP_X_GITHUB_EVENT'] - when "pull_request" - if @payload["action"] == "opened" - process_pull_request(@payload["pull_request"]) - end - end -end - -helpers do - def process_pull_request(pull_request) - puts "It's #{pull_request['title']}" - end -end -``` - -¿Qué está pasando? Cada evento que {% data variables.product.product_name %} envía adjunta un encabezado de HTTP de `X-GitHub-Event`. Solo nos interesan los eventos de Solicitud de Extracción por el momento. Desde ahí, tomaremos la carga útil de información y devolveremos el campo de título. En un escenario ideal, a nuestro servidor le interesaría cada vez que se actualiza una solicitud de extracción, no únicamente cuando se abre. Eso garantizaría que todas las cargas pasen la prueba de IC. Pero para efectos de esta demostración, solo nos interesará cuándo se abren. - -Para probar esta prueba de concepto, haz algunos cambios en una rama de tu repositorio de pruebas, y abre una solicitud de extracción. ¡Tu servidor deberá responder de acuerdo con los casos! - -### Trabajar con los estados - -Ya que configuramos el servidor, estamos listos para comenzar con nuestro primer requisito, que es configurar (y actualizar) los estados de IC. Nota que en cualquier momento que actualices tu servidor, puedes dar clic en **Volver a entregar** para enviar la misma carga útil. ¡No necesitas hacer una solicitud de extracción cada que haces un cambio! - -Ya que estamos interactuando con la API de {% data variables.product.product_name %}, utilizaremos a [Octokit.rb][octokit.rb] para administrar nuestras interacciones. Configuraremos a ese cliente con - -``` ruby -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below -ACCESS_TOKEN = ENV['MY_PERSONAL_TOKEN'] - -before do - @client ||= Octokit::Client.new(:access_token => ACCESS_TOKEN) -end -``` - -Después de ésto, solo necesitaremos actualizar la solicitud de extracción en {% data variables.product.product_name %} para dejar en claro lo que estamos procesando en la IC: - -``` ruby -def process_pull_request(pull_request) - puts "Processing pull request..." - @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'pending') -end -``` - -Estamos haciendo tres cosas muy básicas aquí: - -* buscando el nombre completo del repositorio -* buscando el último SHA de la solicitud de extracción -* configurando el estado como "pendiente" - -¡Listo! Desde estepunto puedes ejecutar el proceso que sea que necesites para ejecutar tu suit de pruebas. Tal vez vas a pasar tu código a Jenkins, o a llamar a otro servicio web a través de su API, como con [Travis][travis api]. Después de eso, asegúrate actualizar el estado una vez más. En nuestro ejemplo, solo lo configuraremos como `"success"`: - -``` ruby -def process_pull_request(pull_request) - @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'pending') - sleep 2 # do busy work... - @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'success') - puts "Pull request processed!" -end -``` - -### Conclusión - -En GitHub, utilizamos una versión de [Janky][janky] durante años para administrar nuestra IC. El flujo básico es esencial y exactamente el mismo que en el servidor que acabamos de crear. En GitHub, nosotros: - -* Notificamos todo a Jenkins cuando se crea o actualiza una solicitud de extracción (a través de Janky) -* Esperamos una respuesta del estado de la IC -* Si el código tiene luz verde, lo fusionamos con la solicitud de extracción - -Todas estas comunicaciones se canalizan de vuelta a nuestras salas de chat. No necesitas crear tu propia configuración de IC para utilizar este ejemplo. Siempre puedes confiar en las [Integraciones de GitHub][integrations]. - -[status API]: /v3/repos/statuses/ -[ngrok]: https://ngrok.com/ -[using ngrok]: /webhooks/configuring/#using-ngrok -[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server -[Sinatra]: http://www.sinatrarb.com/ -[octokit.rb]: https://github.com/octokit/octokit.rb -[travis api]: https://api.travis-ci.org/docs/ -[janky]: https://github.com/github/janky -[integrations]: https://github.com/integrations diff --git a/translations/es-XL/content/rest/guides/delivering-deployments.md b/translations/es-XL/content/rest/guides/delivering-deployments.md deleted file mode 100644 index 6c8e26d4f4..0000000000 --- a/translations/es-XL/content/rest/guides/delivering-deployments.md +++ /dev/null @@ -1,158 +0,0 @@ ---- -title: Entregar despliegues -intro: 'Al utilizar la API de REST de Despliegues, puedes crear herramientas personalizadas que interactúen con tu servidor y con una app de terceros.' -redirect_from: - - /guides/delivering-deployments/ - - /guides/automating-deployments-to-integrators/ - - /v3/guides/delivering-deployments -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -La [API de Despliegues][deploy API] le proporciona a tus proyectos hospedados en {% data variables.product.product_name %} la capacidad de lanzarlos a un servidor que te pertenezca. En combinación con [la API de Estados][status API], podrás coordinar tus despliegues en el momento en que tu código llegue a `master`. - -Esta guía utilizará esa API para ejemplificar una configuración que puedes utilizar. En nuestro escenario, nosotros: - -* Fusionamos una solicitud de extracción -* Cuando finaliza la IC, configuramos el estado de la solicitud de extracción según corresponda. -* Cuando se fusiona la solicitud de extracción, ejecutamos nuestro despliegue en nuestro servidor. - -Nuestro sistema de IC y nuestro servidor host serán imaginarios. Podrían ser Heroku, Amazon, o algo completamente diferente. El meollo de esta guía será configurar y ajustar el servidor que administra la comunicación. - -Si aún no lo has hecho, asegúrate de [descargar ngrok][ngrok], y de aprender a [utilizarlo][using ngrok]. Consideramos que es una herramienta muy útil para exponer las conexiones locales. - -Nota: puedes descargar todo el código fuente para este proyecto [del repo platform-samples][platform samples]. - -### Escribir tu servidor - -Escribiremos una app de Sinatra rápidamente para probar que nuestras conexiones locales estén funcionando. Comencemos con esto: - -``` ruby -require 'sinatra' -require 'json' - -post '/event_handler' do - payload = JSON.parse(params[:payload]) - "Well, it worked!" -end -``` - -(Si no estás familiarizado con como funciona Sinatra, te recomendamos [leer la guía de Sinatra][Sinatra].) - -Inicia este servidor. Predeterminadamente, Sinatra inicia en el puerto `4567`, así que también debes configurar ngrok para comenzar a escuchar este puerto. - -Para que este servidor funcione, necesitaremos configurar un repositorio con un webhook. El webhook debe configurarse para que se active cada que se crea o fusiona una solicitud de extracción. Sigue adelante y crea un repositorio en el que quieras hacer tus experimentos. ¿Podríamos sugerirte que sea [el repositorio Spoon/Knife de @octocat](https://github.com/octocat/Spoon-Knife)? Después de esto, crearás un webhook nuevo en tu repositorio y lo alimentarás con la URL que te dio ngrok para luego escoger a `application/x-www-form-urlencoded` como el tipo de contenido: - -![Una URL de ngrok nueva](/assets/images/webhook_sample_url.png) - -Haz clic en **Actualizar webhook**. Deberás ver una respuesta en el cuerpo que diga `Well, it worked!`. ¡Genial! Da clic en **Déjame selecionar eventos individuales**, y selecciona lo siguiente: - -* Despliegue -* Estado del despliegue -* Solicitud de Extracción - -Estos son los eventos que {% data variables.product.product_name %} enviará a nuestro servidor cuando ocurra cualquier acción relevante. Configuraremos nuestro servidor para que *solo* gestione cuando las solicitudes de extracción se fusionen ahora mismo: - -``` ruby -post '/event_handler' do - @payload = JSON.parse(params[:payload]) - - case request.env['HTTP_X_GITHUB_EVENT'] - when "pull_request" - if @payload["action"] == "closed" && @payload["pull_request"]["merged"] - puts "A pull request was merged! A deployment should start now..." - end - end -end -``` - -¿Qué está pasando? Cada evento que {% data variables.product.product_name %} envía adjunta un encabezado de HTTP de `X-GitHub-Event`. Solo nos interesan los eventos de Solicitud de Extracción por el momento. Cuando una solicitud de extracción se fusiona (su estado es `closed`, y `merged` se encuentra como `true`), iniciaremos un despliegue. - -Para probar esta prueba de concepto, haz algunos cambios en una rama de tu repositorio de pruebas, y abre una solicitud de extracción y fusiónala. ¡Tu servidor deberá responder de acuerdo con los casos! - -### Trabajar con despliegues - -Como ya tenemos nuestro servidor configurado, el código ya se revisó, y nuestras solicitudes de extracción se fusionaron, entonces queremos desplegar nuestro proyecto. - -Comenzaremos modificando nuestro detector de eventos para que procese las solicitudes de extracción cuando se fusiones, y para que comience a poner atención a los despliegues: - -``` ruby -when "pull_request" - if @payload["action"] == "closed" && @payload["pull_request"]["merged"] - start_deployment(@payload["pull_request"]) - end -when "deployment" - process_deployment(@payload) -when "deployment_status" - update_deployment_status -end -``` - -Basándonos en la información de la solicitud de extracción, comenzaremos llenando el método de `start_deployment`: - -``` ruby -def start_deployment(pull_request) - user = pull_request['user']['login'] - payload = JSON.generate(:environment => 'production', :deploy_user => user) - @client.create_deployment(pull_request['head']['repo']['full_name'], pull_request['head']['sha'], {:payload => payload, :description => "Deploying my sweet branch"}) -end -``` - -Los despliegues pueden tener algunos metadatos adjuntos en forma de una `payload` y una `description`. Aunque estos valores son opcionales, es de gran ayuda utilizarlos para registrar y representar la información. - -Cuando se crea un despliegue nuevo, se activa un evento completamente separado. Por eso es que tenemos un caso nuevo de `switch` en el gestor de eventos para nuestro `deployment`. Puedes utilizar esta información para que se te notifique cuando se active un despliegue. - -Los despliegues pueden tomar mucho tiempo, así que queremos detectar varios eventos, tales como cuando el despliegue se cree, y en qué estado está. - -Simulemos un despliegue que tome algunas acciones, y pondremos atención en el efecto que tiene sobre la salida. Primero, vamos a completar nuestro métoddo de `process_deployment`: - -``` ruby -def process_deployment - payload = JSON.parse(@payload['payload']) - # you can send this information to your chat room, monitor, pager, etc. - puts "Processing '#{@payload['description']}' for #{payload['deploy_user']} to #{payload['environment']}" - sleep 2 # simulate work - @client.create_deployment_status("repos/#{@payload['repository']['full_name']}/deployments/#{@payload['id']}", 'pending') - sleep 2 # simulate work - @client.create_deployment_status("repos/#{@payload['repository']['full_name']}/deployments/#{@payload['id']}", 'success') -end -``` - -Por último, estimularemos el almacenamiento de la información de los estados como una salida de la consola: - -``` ruby -def update_deployment_status - puts "Deployment status for #{@payload['id']} is #{@payload['state']}" -end -``` - -Bamos a explicar lo que está pasando. `start_deployment` creó un despliegue nuevo, lo cual activó el evento `deployment`. Desde ahí, llamamos a `process_deployment` para estimular las acciones que están sucediendo. Durante este procesamiento, también llamamos a `create_deployment_status`, el cual permite que un receptor sepa lo que está pasando, mientras cambiamos el estado a `pending`. - -Después de que termine el despliegue, configuramos el estado como `success`. - -### Conclusión - -En GitHub siempre hemos utilizado una versión de [Heaven][heaven] durante años para administrar nuestros despliegues. El flujo básico es esencial y exactamente el mismo que en el servidor que acabamos de crear. En GitHub, nosotros: - -* Esperamos una respuesta del estado de la IC -* Si el código tiene luz verde, lo fusionamos con la solicitud de extracción -* Heaven toma el código fusionado y lo despliega en nuestros servidores productivos y de pruebas -* Mientras tanto, Heaven también notifica a todos acerca de la compilación, a través de [Hubot][hubot] que espera en nuestras salas de chat - -¡Listo! No necesitas crear tu propia configuración de despliegue para utilizar este ejemplo. Siempre puedes confiar en las [Integraciones de GitHub][integrations]. - -[deploy API]: /v3/repos/deployments/ -[status API]: /guides/building-a-ci-server -[ngrok]: https://ngrok.com/ -[using ngrok]: /webhooks/configuring/#using-ngrok -[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/delivering-deployments -[Sinatra]: http://www.sinatrarb.com/ -[heaven]: https://github.com/atmos/heaven -[hubot]: https://github.com/github/hubot -[integrations]: https://github.com/integrations diff --git a/translations/es-XL/content/rest/guides/discovering-resources-for-a-user.md b/translations/es-XL/content/rest/guides/discovering-resources-for-a-user.md deleted file mode 100644 index 7f04080525..0000000000 --- a/translations/es-XL/content/rest/guides/discovering-resources-for-a-user.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -title: Descubrir los recursos para un usuario -intro: Aprende cómo encontrar los repositorios y organizaciones a los cuales puede acceder tu app para un usuario de manera confiable para tus solicitudes autenticadas a la API de REST. -redirect_from: - - /guides/discovering-resources-for-a-user/ - - /v3/guides/discovering-resources-for-a-user -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -Cuando se hacen solicitudes autenticadas a la API de {% data variables.product.product_name %}, las aplicaciones a menudo tienen que obtener los repositorios y organizaciones del usuario. En esta guía, te explicaremos cómo descubrir estos recursos de forma confiable. - -Para interactuar con la API de {% data variables.product.product_name %}, estaremos utilizando [Octokit.rb][octokit.rb]. Puedes encontrar todo el código fuente de este proyecto en el repositorio [platform-samples][platform samples]. - -### Empezar - -Si aún no lo has hecho, deberías leer la guía de ["Conceptos Básicos de la Autenticación"][basics-of-authentication] antes de comenzar a trabajar en los siguientes ejemplos. Éstos asumen que tienes una [aplicación de OAuth registrada][register-oauth-app] y de que [tu aplicación tiene un token de OAuth para un usuario][make-authenticated-request-for-user]. - -### Descubre los repositorios a los cuales tu app puede acceder para un usuario - -Adicionalmente a tener sus propios repositorios personales, un usuario puede ser un colaborador en los repositorios que pertenezcan a otros usuarios y organizaciones. En conjunto, estos son los repositorios en donde el usuario tiene acceso privilegiado: ya sea un repositorio privado en donde el usuario tiene acceso de lectura o escritura, o un repositorio público en donde el usuario tiene acceso de escritura. - -Los [alcances de OAuth][scopes] y las [políticas de aplicación de la organización][oap] determinan a cuáles de estos repositorios puede acceder tu app para un usuario. Utiliza el siguiente flujo de trabajo para descubrir estos repositorios. - -Como siempre, primero necesitaremos la biblioteca de Ruby del [Octokit.rb de GitHub][octokit.rb]. Luego, configuraremos a Octokit.rb para que nos gestione automáticamente la [paginación][pagination]. - -``` ruby -require 'octokit' - -Octokit.auto_paginate = true -``` - -Después, pasaremos el [Token de OAuth para un usuario específico][make-authenticated-request-for-user] de nuestra aplicación: - -``` ruby -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below. -client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"] -``` - -Luego estaremos listos para obtener los [repositorios a los cuales puede acceder nuestra aplicación para el usuario][list-repositories-for-current-user]: - -``` ruby -client.repositories.each do |repository| - full_name = repository[:full_name] - has_push_access = repository[:permissions][:push] - - access_type = if has_push_access - "write" - else - "read-only" - end - - puts "User has #{access_type} access to #{full_name}." -end -``` - -### Descubre las organizaciones a las cuales puede acceder tu app para un usuario - -Las aplicaciones pueden llevar a cabo todo tipo de tareas relacionadas con las organizaciones para un usuario. Para llevar a cabo estas tareas, la app necesita una [Autorización de OAuth][scopes] con permisos suficientes. Por ejemplo, el alcance `read:org` te permite [listar los equipos][list-teams], y el alcance `user` te permite [publicitar la membresía organizacional del usuario][publicize-membership]. Una vez que un usuario haya otorgado uno o más de estos alcances a tu app, estarás listo para obtener las organizaciones de éste. - -Tal como hicimos cuando descubrimos los repositorios anteriormente, comenzaremos requiriendo la biblioteca de Ruby [Octokit.rb de GitHub][octokit.rb] y configurándola para que se encarge de la [paginación][pagination] por nosotros: - -``` ruby -require 'octokit' - -Octokit.auto_paginate = true -``` - -Después, pasaremos el [Token de OAuth para un usuario específico][make-authenticated-request-for-user] de nuestra aplicación para inicializar nuestro cliente de la API: - -``` ruby -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below. -client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"] -``` - -Después, podremos [listar las organizaciones a las cuales tiene acceso nuestra aplicación para el usuario][list-orgs-for-current-user]: - -``` ruby -client.organizations.each do |organization| - puts "User belongs to the #{organization[:login]} organization." -end -``` - -#### No dependas de las organizaciones públicas - -Si leíste los documentos de principio a fin, tal vez hayas notado que hay un [Método de la API para listar las membrecías de organizaciones públicas de un usuario][list-public-orgs]. La mayoría de las aplicaciones deberían evitar este método de la API. Este método solo devuelve las membrecías de las organizaciones públicas del usuario y no sus membrecías de organizaciones privadas. - -Al fungir como una aplicación, habitualmente lo que buscas es todas las organizaciones del usuario (tanto públicas como privadas) en las cuales tu app tenga acceso autorizado. El flujo de trabajo anterior te proporcionará exactamente eso. - -[basics-of-authentication]: /v3/guides/basics-of-authentication/ -[list-public-orgs]: /v3/orgs/#list-organizations-for-a-user -[list-repositories-for-current-user]: /v3/repos/#list-repositories-for-the-authenticated-user -[list-orgs-for-current-user]: /v3/orgs/#list-organizations-for-the-authenticated-user -[list-teams]: /v3/teams/#list-teams -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests -[make-authenticated-request-for-user]: /v3/guides/basics-of-authentication/#making-authenticated-requests -[oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ -[octokit.rb]: https://github.com/octokit/octokit.rb -[octokit.rb]: https://github.com/octokit/octokit.rb -[pagination]: /v3/#pagination -[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user -[publicize-membership]: /v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user -[register-oauth-app]: /v3/guides/basics-of-authentication/#registering-your-app -[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ diff --git a/translations/es-XL/content/rest/guides/getting-started-with-the-checks-api.md b/translations/es-XL/content/rest/guides/getting-started-with-the-checks-api.md deleted file mode 100644 index 93fb0da7a1..0000000000 --- a/translations/es-XL/content/rest/guides/getting-started-with-the-checks-api.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Empezar con la API de Verificaciones -intro: 'La API de Ejecuciones de Verificación te permite crear GitHub Apps que ejecuten verificaciones poderosas contra los cámbios de código en un repositorio. Puedes crear apps que lleven a cabo integración contínua, limpieza de código, o servicios de escaneo de código y que proporcionen retroalimentación detallada en las confirmaciones.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Resumen - -En vez de proporcionar estados de creación de pase/fallo, las GitHub Apps pueden reportar estados enriquecidos, anotar información detallada en las líneas de código y re-ejecutar las pruebas. La funcionalidad de la API de Verificaciones se encuentra disponible exclusivamente para tus GitHub Apps. - -Para obtener un ejemplo de cómo utilizar la API de Verificaciones con una {% data variables.product.prodname_github_app %}, consulta la sección "[Crear pruebas de IC con la API de verificaciones](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)". - -### Acerca de las suites de verificaciones - -Cuando alguien carga código a un repositorio, GitHub crea una suite de verificación para la última confirmación. Una suite de verificación es un conjunto de [ejecuciones de verificación](/rest/reference/checks#check-runs) que crea una sola GitHub App para una confirmación específica. Las suites de Verificación resumen el estado y la conclusión de la ejecución de verificación que incluye dicha suite. - -![Flujo de trabajo de las suites de verificación](/assets/images/check_suites.png) - -La suite de verificación reporta la `conclusion` de la ejecución de verificación con la prioridad más alta en `conclusion` de la suite de verificación. Por ejemplo, si tres ejecuciones de verificación tienen conclusiones de `timed_out`, `success`, y `neutral`, la conclusión de la suite de verificación será `timed_out`. - -Predeterminadamente, GitHub crea una suite de verificación automáticamente cuando se carga el código al repositorio. Este flujo predeterminado evía el evento `check_suite` (con la acción `requested`) a todas las GitHub Apps que tengan el permiso de `checks:write`. Cuando tu GitHub App recibe el evento `check_suite`, esta púede crear ejecuciones de verificación nuevas para la última confirmación. GitHub agrega las ejecuciones de verificación nuevas a la [suite de verificación](/rest/reference/checks#check-suites) correcta con base en el repositorio y SHA de dicha ejecución de verificación. - -Si no quieres utilizar el flujo automático predeterminado, puedes controlar cuando creas las suites de verificación. Para cambiar la configuración predeterminada para la creación de suites de verificación, utiliza la terminal [Actualizar las preferencias del repositorio para las suites de verificación](/rest/reference/checks#update-repository-preferences-for-check-suites). Todos los cambios que se realicen en la configuración del flujo automático se registran en la bitácora de auditoría del repositorio. Si inhabilitaste el flujo automático, puedes crear una suite de verificación utilizando la terminal [Crear una suite de verificación](/rest/reference/checks#create-a-check-suite). Debes seguir utilizando la terminal [Crear una ejecución de verificación](/rest/reference/checks#create-a-check-run) para proporcionar retroalimentación sobre una confirmación. - -{% data reusables.apps.checks-availability %} - -Para utilizar la API de suites de verificación, la GitHub App debe tener el permiso de `checks:write` y también suscribirse al webhook de [check_suite](/webhooks/event-payloads/#check_suite). - -{% data reusables.shortdesc.authenticating_github_app %} - -### Acerca de las ejecuciones de verificación - -Una ejecución de verificación es una prueba individual que forma parte de una suite de verificación. Cada ejecución incluye un estado y una conclusión. - -![Flujo de trabajo de las ejecuciones de verificación](/assets/images/check_runs.png) - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -Si una ejecución de verificación permanece en un estado incompleto por más de 14 días, entonces la `conclusion` de ésta se convierte en `stale` y aparece en {% data variables.product.prodname_dotcom %} como quedada con el -{% octicon "issue-reopened" aria-label="The issue-reopened icon" %}. Solo {% data variables.product.prodname_dotcom %} puede marcar las ejecuciones de verificación como `stale`. Para obtener más información acerca de las conclusiones posibles para una ejecución de verificación, consulta el [parámetro de `conclusion`](/rest/reference/checks#create-a-check-run--parameters). -{% endif %} - -Puedes crear la ejecución de verificación tan pronto como recibas el webhook de [`check_suite`](/webhooks/event-payloads/#check_suite), aún si ésta todavía no se completa. Puedes actualizar el `status` de la ejecución de verificación ya que se completa con los valores `queued`, `in_progress`, o `completed`, y puedes actualizar la `output` conforme vayan estando disponibles los detalles adicionales. Una ejecución de verificación puede contener estampas de tiempo, un enlace para encontrar más detalles en tu sitio externo, anotaciones detalladas para líneas de código específcas, e información acerca del análisis que se llevó a cabo. - -![Anotaciones de la ejecución de verificación](/assets/images/check_run_annotations.png) - -Una verificación también puede volverse a ejecutar en la IU de GitHub. Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles. Cuando esto ocurre, la GitHub App que creó la ejecución de verificación recibirá el webhook [`check_run`](/webhooks/event-payloads/#check_run) que solicita una ejecución de verificación nueva. Si creas una ejecución de verificación sin crear una suite de verificación, GitHub la creará para tí automáticamente. - -{% data reusables.apps.checks-availability %} - -Para utilizar la API de Ejecuciones de Verificación, la GitHub App debe tener el permiso de `checks:write` y también debe poder suscribirse al webhook de [check_run](/webhooks/event-payloads#check_run). - -### Ejecuciones de verificación y acciones solicitadas - -Cuando configuras una ejecución de verificación con las acciones solicitadas (no se debe confundir esto con {% data variables.product.prodname_actions %}), puedes mostrar un botón en la vista de la solicitud de extracción en {% data variables.product.prodname_dotcom %} que permita a las personas solicitar tu {% data variables.product.prodname_github_app %} para llevar a cabo tareas adicionales. - -Por ejemplo, una app de limpieza de código puede utilizar las acciones solicitadas para mostrar un botón en una solicitud de extracción para arreglar automáticamente los errores de sintaxis detectados. - -Para crear un botón que pueda solicitarle a tu app acciones adicionales, utiliza el [objeto`actions`](/rest/reference/checks#create-a-check-run--parameters) cuando [Creas una ejecución de verificación](/rest/reference/checks/#create-a-check-run). Por ejemplo, el objeto `actions` que se muestra a continuación muestra un botón en una solicitud de extracción con la etiqueta "Fix This". El botón aparece después de que se completa la ejecución de verificación. - - ```json - "actions": [{ - "label": "Fix this", - "description": "Let us fix that for you", - "identifier": "fix_errors" - }] - ``` - - ![Botón de acción solicitada para la ejecución de verificación](/assets/images/github-apps/github_apps_checks_fix_this_button.png) - -Cuando un usuario da clic en el botón, {% data variables.product.prodname_dotcom %} envía el [webhook de `check_run.requested_action`](/webhooks/event-payloads/#check_run) a tu app. Cuando tu app recibe el evento de webhook de `check_run.requested_action`, este puede buscar la clave de `requested_action.identifier` en la carga útil del webhook para determinar qué botón se pulsó y llevar a cabo la tarea solicitada. - -Para obtener un ejemplo detallado de cómo configurar las acciones solicitadas con la API de Verificaciones, consulta la sección "[Crear pruebas de IC con la API de verificaciones](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/#part-2-creating-the-octo-rubocop-ci-test)". diff --git a/translations/es-XL/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/es-XL/content/rest/guides/getting-started-with-the-git-database-api.md deleted file mode 100644 index e5d5ad223d..0000000000 --- a/translations/es-XL/content/rest/guides/getting-started-with-the-git-database-api.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Comenzar con la API de la Base de Datos de Git -intro: 'La API de la Base de datos de Git te da acceso de escritura y lectora para los objetos sin procesar de Git que se encuentran en tu base de datos de Git en {% data variables.product.product_name %} y para listar y actualizar tus referencias (cabezas de rama y etiquetas).' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Resumen - -Básicamente, esto te permite volver a implementar muchas de las funcionalidades de Git sobre nuestra API mediante la creación de objetos sin procesar (raw) directamente en la base de datos y actualizando las referencias de rama que técnicamente podrían hacer todo lo que pueda hacer Git sin que se éste se instale. - -La API de la Base de Datos de Git devolverá un `409 Conflict` si el repositorio de Git está vacío o no disponible. Que un repositorio se muestre como no disponible habitualmente significa que {% data variables.product.product_name %} está en el proceso de crearlo. Para los casos de repositorios vacíos, puedes utilizar la terminal "[Crear o actualizar el contenido de un archivo](/v3/repos/contents/#create-or-update-file-contents)" para crear contenido e inicializar el repositorio para que puedas utilizar la API de la Base de Datos de Git. Contacta a {% data variables.contact.contact_support %} si este estado de respuesta persiste. - -![resumen de la base de datos de git](/assets/images/git-database-overview.png) - -Para obtener más información sobre la base de datos de objetos de Git, por favor lee el capítulo [Internos de Git](http://git-scm.com/book/en/v1/Git-Internals) en el libro Pro de Git. - -Como ejemplo, si quieres confirmar un cambio en un archivo de tu repositorio, lo que harías es: - -* Obtener el objeto de la confirmación actual -* Recuperar el árbol al cual apunta -* Recuperar el contenido del objeto del blob que tiene el árbol para esa ruta de archivo en particular -* Cambiar el contenido de alguna manera y publicar un objeto de blob nuevo con este contenido nuevo, obteniendo el SHA del blob a cambio -* Publicar un nuevo objeto de árbol con ese indicador de la ruta del archivo reemplazándolo con el SHA de tu blob nuevo y obteniendo a cambio el SHA del árbol -* Crear un objeo de confirmación nuevo con el SHA de la confirmación actual como el padre y el SHA del árbol nuevo, obteniendo a cambio el SHA de la confirmación -* Actualizar la referencia de tu rama para apuntar al nuevo SHA de la confirmación - -Puede que parezca complejo, pero en realidad es bastante simple cuando entiendes el modelo y te proporciona la oportunidad de hacer un sin fin de cosas cuando lo haces potencialmente con la API. - -### Verificar la capacidad de fusión de las solicitudes de extracción - -{% warning %} - -**¡Advertencia!** Por favor no dependas de utilizar Git directamente de {% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}[`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}[`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference){% endif %} para las actualizaciones a las referencias de `merge` de Git, ya que este contenido se vuelve obsoleto sin aviso previo. - -{% endwarning %} - -Una API consumible debe solicitar explícitamente que una solicitud de extracción cree una confirmación de fusión de _prueba_. Una confirmación de fusión de _prueba_ se crea cuando ves la solicitud de extracción en la IU y cuando se muestra el botón de "Fusionar", o cuando [obtienes](/v3/pulls/#get-a-pull-request), [creas](/v3/pulls/#create-a-pull-request), o [editas](/v3/pulls/#update-a-pull-request) una solicitud de extracción utilizando la API de REST. Sin esta solicitud, las Referencias de Git para `merge` se harán obsoletas hasta la próxima vez que alguien vea la solicitud de extracción. - -Si actualmente usas métodos de sondeo que produzcan referencias de Git de `merge`, entoces GitHub recomienda que utilices los siguientes pasos para obtener los últimos cambios desde la rama base (habitualmente `master`): - -1. Recibir el webhook de la solicitud de extracción. -2. Llamar a [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) para iniciar un job en segundo plano para crear el candidato de la confirmación de fusión. -3. Sondear tu repositorio utilizando [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/v3/pulls/#get-a-pull-request) para ver si el atributo `mergeable` está como `true` o como `false`. Puedes utilizar Git directamente o {% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}[`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}[`GET /repos/{owner}/{repo}/git/refs/{ref}`](/v3/git/refs/#get-a-reference){% endif %} para las actualizaciones a las referencias de `merge` de Git únicamente después de llevar a cabo los pasos anteriores. diff --git a/translations/es-XL/content/rest/guides/getting-started-with-the-rest-api.md b/translations/es-XL/content/rest/guides/getting-started-with-the-rest-api.md deleted file mode 100644 index 0e3e144e32..0000000000 --- a/translations/es-XL/content/rest/guides/getting-started-with-the-rest-api.md +++ /dev/null @@ -1,395 +0,0 @@ ---- -title: Iniciar con la API de REST -intro: 'Aprende las bases para utilizar la API de REST, comenzando con la autenticación y algunos ejemplos de las terminales.' -redirect_from: - - /guides/getting-started/ - - /v3/guides/getting-started -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -Vamos a explicar los conceptos centrales de la API mientras incluímos algunos casos de uso cotidiano. - -### Resumen - -La mayoría de las aplicaciones utilizan una [biblioteca de seguridad][wrappers] en el lenguaje de programación que escojas, pero es importante que te familiarices con los métodos HTTP básicos de la API primero. - -No hay una forma más fácil de hacerlo que a través de [cURL][curl].{% if currentVersion == "free-pro-team@latest" %} Si estás utilizando un cliente alternativo, nota qeu necesitas enviar un [encabezado de Agente de Usuario](/rest/overview/resources-in-the-rest-api#user-agent-required) válido en tu solicitud.{% endif %} - -#### Hola Mundo - -Comencemos por probar nuestra configuración. Abre una instancia de la línea de comandos e ingresa el siguiente comando: - -```shell -$ curl {% data variables.product.api_url_pre %}/zen - -> Keep it logically awesome. -``` - -La respuesta será una selección aleatoria de nuestra filosofía de diseño. - -Posteriormente, vamos a hacer `GET` para el [perfil de GitHub][users api] de [Chris Wanstrath][defunkt github]: - -```shell -# GET /users/defunkt -$ curl {% data variables.product.api_url_pre %}/users/defunkt - -> { -> "login": "defunkt", -> "id": 2, -> "url": "{% data variables.product.api_url_pre %}/users/defunkt", -> "html_url": "https://github.com/defunkt", -> ... -> } -``` - -Mmmm, sabe a [JSON][json]. Vamos a agregar el marcador `-i` para que incluya los encabezados: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/users/defunkt - -> HTTP/1.1 200 OK -> Server: GitHub.com -> Date: Sun, 11 Nov 2012 18:43:28 GMT -> Content-Type: application/json; charset=utf-8 -> Connection: keep-alive -> ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6" -> X-RateLimit-Limit: 60 -> X-RateLimit-Remaining: 57 -> X-RateLimit-Reset: 1352660008 -> X-GitHub-Media-Type: github.v3 -> Vary: Accept -> Cache-Control: public, max-age=60, s-maxage=60 -> X-Content-Type-Options: nosniff -> Content-Length: 692 -> Last-Modified: Tue, 30 Oct 2012 18:58:42 GMT - -> { -> "login": "defunkt", -> "id": 2, -> "url": "{% data variables.product.api_url_pre %}/users/defunkt", -> "html_url": "https://github.com/defunkt", -> ... -> } -``` - -Hay algunas partes interesantes en los encabezados de la respuesta. Como lo esperábamos, el `Content-Type` es `application/json`. - -Cualquier encabezado que comience como `X` se refiere a un encabezado personalizado, y no se incluirá en la especificación de HTTPS. Por ejemplo: - -* `X-GitHub-Media-Type` tiene un valor de `github.v3`. Esto nos permite saber el [tipo de medios][media types] para la respuesta. Los tipos de medios nos han ayudado a versionar nuestra salida en la API v3. Hablaremos más sobre esto después. -* Toma nota de los encabezados `X-RateLimit-Limit` y `X-RateLimit-Remaining`. Este par de encabezados indica [cuántas solicitudes puede hacer un cliente][rate-limiting] en un periodo de tiempo consecutivo (habitualmente una hora) y cuántas de estas solicitudes ha gastado el cliente hasta ahora. - -### Autenticación - -Los clientes sin autenticar pueden hacer hasta 60 solicitudes por hora. Para obtener más solicitudes por hora, necesitaremos _autenticarnos_. De hecho, necesitaremos la [autenticación][authentication] para hacer cualquier cosa interesante con la API de {% data variables.product.product_name %}. - -#### Utilizar tokens de acceso personal - -La mejor y más fácil forma de autenticarse con la API de {% data variables.product.product_name %} es utilizando la Autenticación Básica [a través de los tokens de OAuth](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens). Éstos incluyen [tokens de acceso personal][personal token]. - -Utiliza el marcador `-u` para configurar tu nombre de usuario: - -```shell -$ curl -i -u your_username {% data variables.product.api_url_pre %}/users/octocat - -``` - -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. - -```shell -$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat - -``` - -Cuando te autentiques, debes ver como tu límite de tasa sube hasta 5,000 solicitudes por hora, como se indicó en el encabezado `X-RateLimit-Limit`. Adicionalmente a proporcionar más llamadas por hora, la autenticación te permite leer y escribir información privada utilizando la API. - -Puedes [crear un**token de acceso personal**][personal token] fácilmente utilizando tu [página de configuración para tokens de acceso personal][tokens settings]: - -![Selección de token personal](/assets/images/personal_token.png) - -#### Obtén tu propio perfil de usuario - -Cuando te autenticas adecuadamente, puedes sacar provecho de los permisos asociados con tu cuenta de {% data variables.product.product_name %}. Por ejemplo, intenta obtener - -```shell -$ curl -i -u your_username:your_token {% data variables.product.api_url_pre %}/user - -> { -> ... -> "plan": { -> "space": 2516582, -> "collaborators": 10, -> "private_repos": 20, -> "name": "medium" -> } -> ... -> } -``` - -Esta vez, adicionalmente al mismo conjunto de información pública que recuperamos antes para [@defunkt][defunkt github], deberías ver también la información no pública para tu perfil de usuario. Por ejemplo, verás un objeto de `plan` en la respuesta, el cuál proporciona detalles sobre el plan de {% data variables.product.product_name %} de la cuenta. - -#### Utiilzar tokens de OAuth para las apps - -Las apps que necesitan leer o escribir información privada utilizando la API en nombre de otro usuario deben utilizar [OAuth][oauth]. - -OAuth utiliza _tokens_. Los Tokens proporcionan dos características grandes: - -* **Acceso revocable**: los usuarios pueden revocar la autorización a las apps de terceros en cualquier momento -* **Acceso limitado**: los usuarios pueden revisar el acceso específico que proporcionará un token antes de autorizar una app de terceros - -Los tokens deben crearse mediante un [flujo web][webflow]. Una aplicación envía a los usuarios a {% data variables.product.product_name %} para que inicien sesión. Entonces, {% data variables.product.product_name %} presenta un diálogo que indica el nombre de la app así como el nivel de acceso que ésta tiene una vez que el usuario la autorice. Después de que un usuario autoriza el acceso, {% data variables.product.product_name %} lo redirecciona de vuelta a la aplicación: - -![Diálogo de OAuth de GitHub](/assets/images/oauth_prompt.png) - -**¡Trata a los tokens de OAuth como si fueran contraseñas!** No los compartas con otros usuarios ni los almacenes en lugares inseguros. Los tokens en estos ejemplos son falsos y los nombres se cambiaron para proteger a los inocentes. - -Ahora que ya entendimos cómo hacer llamadas autenticadas, vamos a pasar a la [API de repositorios][repos-api]. - -### Repositorios - -Casi cualquier uso significativo de la API de {% data variables.product.product_name %} involucra algún nivel de información de un repositorio. Podemos hacer [`GET` para los detalles de un repositorio][get repo] de la misma forma que recuperamos los detalles del usuario anteriormente: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/repos/twbs/bootstrap -``` - -De la misma forma, podemos [ver los repositorios del usuario autenticado][user repos api]: - -```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ - {% data variables.product.api_url_pre %}/user/repos -``` - -O podemos [listar los repositorios de otro usuario][other user repos api]: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/repos -``` - -O podemos [listar los repositorios de una organización][org repos api]: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/orgs/octo-org/repos -``` - -La información que se devuelve de estas llamadas dependerá de los alcances que tenga nuestrotoken cuando nos autenticamos: - -* Un token con el [alcance][scopes] de `public_repo` devolverá una respuesta que incluya todos los repositorios públicos a los cuales tenemos acceso de visualización en github.com. -* Un token con [scope][scopes] de `repo` devuelve una respuesta que incluye a todos los repositorios públicos y privados a los que tenemos acceso para ver en github.com. - -Como indican los [docs][repos-api], estos métodos toman un parámetro de `type` que puede filtrar los repositorios que se regresan con base en el tipo de acceso que el usuario tiene en ellos. De esta forma, podemos obtener los solo los repositorios que nos pertenezcan directamente, repositorios de organizacion o repositorios en los que el usuario colabore a través del equipo. - -```shell -$ curl -i "{% data variables.product.api_url_pre %}/users/octocat/repos?type=owner" -``` - -En este ejemplo, tomamos únicamente los repositorios que pertenecen a octocat, no aquellos en los que ella colabora. Nota la URL que se cita arriba. Dependiendo de tu configuración de shell, cURL a veces requiere una URL citada, o de lo contrario ignora la secuencia de consulta. - -#### Crear un repositorio - -El obtener información para los repositorios existentes es un caso de uso común, pero la API de {% data variables.product.product_name %} también puede crear repositorios nuevos. Para [crear un repositorio][create repo], necesitamos hacer `POST` a algún JSON que contenga los detalles y las opciones de configuración. - -```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ - -d '{ \ - "name": "blog", \ - "auto_init": true, \ - "private": true, \ - "gitignore_template": "nanoc" \ - }' \ - {% data variables.product.api_url_pre %}/user/repos -``` - -En este ejemplo mínimo, creamos un repositorio nuevo para nuestro blog (que se servirá en [GitHub Pages][pages], probablemente). Aunque el blog será público, lo hemos hecho privado. En este paso único, también lo inicializamos con un README y con una [plantilla de.gitignore][gitignore templates] aderezada con [nanoc][nanoc]. - -El repositorio que se obtiene como resultado se puede encontrar en `https://github.com//blog`. Para crear un repositorio bajo una organización para la cual eres propietario, solo cambia el método de la API de `/user/repos` a `/orgs//repos`. - -Posteriormente vamos a obtener nuestro repositorio recién creado: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/repos/pengwynn/blog - -> HTTP/1.1 404 Not Found - -> { -> "message": "Not Found" -> } -``` - -¡Oh no! ¿A dónde se fue? Ya que creamos el repositorio como _privado_, necesitamos autenticarnos para poder verlo. Si eres un usuario experimentado en HTTP, tal vez esperes recibir un código `403` en vez de ésto. Ya que no queremos filtrar información acerca de los repositorios privados, la API de {% data variables.product.product_name %} devuelve un código `404` en este caso, como diciendo "no podemos confirmar ni negar la existencia de este repositorio". - -### Problemas - -La IU de informe de problemas en {% data variables.product.product_name %} pretende proporcionar suficiente flujo de trabajo mientras evita estorbarte. Con la [API de Informes de Problemas][issues-api] de {% data variables.product.product_name %}, puedes extraer datos para crear informes de problemas desde otras herramientas para crear flujos de trabajo que funcionan para tu equipo. - -Tal como en github.com, la API proporciona algunos cuantos métodos para ver los informes de problemas para el usuario autenticado. Para [ver todos tus informes de problemas][get issues api], llama a `GET /issues`: - -```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ - {% data variables.product.api_url_pre %}/issues -``` - -Para obtener únicamente los [informes de problemas bajo alguna de tus organizaciones de {% data variables.product.product_name %}][get issues api], llama a `GET -/orgs//issues`: - -```shell -$ curl -i -H "Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4" \ - {% data variables.product.api_url_pre %}/orgs/rails/issues -``` - -También podemos obtener [todos los informes de problemas que estén bajo un solo repositorio][repo issues api]: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues -``` - -#### Paginación - -Un proyecto con el tamaño de Rails tiene miles de informes de problemas. Necesitaremos [paginar][pagination], haciendo varias llamadas a la API para obtener los datos. Vamos a repetir la última llamada, esta vez tomando nota de los encabezados de respuesta: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/repos/rails/rails/issues - -> HTTP/1.1 200 OK - -> ... -> Link: <{% data variables.product.api_url_pre %}/repositories/8514/issues?page=2>; rel="next", <{% data variables.product.api_url_pre %}/repositories/8514/issues?page=30>; rel="last" -> ... -``` - -El [encabezado de code>Link][link-header] proporciona una respuesta para enlazar a los recursos externos, en este caso, a las páginas de datos adicionales. Ya que nuestra llamada encontró más de treinta informes de problemas (el tamaño predeterminado de página), la API no s dice dónde podemos encontrar la siguiente página y la última página de los resultados. - -#### Crear una propuesta - -Ahora que hemos visto cómo paginar las listas de informes de problemas, vamos a [crear un informe de problemas][create issue] desde la API. - -Para crear un informe de problemas, necesitamos estar autenticados, así que pasaremos un token de OAuth en el encabezado. También, pasaremos el título, cuerpo, y etiquetas en el cuerpo de JSON a la ruta `/issues` debajo del repositorio en el cual queremos crear el informe de problemas: - -```shell -$ curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \ -$ -d '{ \ -$ "title": "New logo", \ -$ "body": "We should have one", \ -$ "labels": ["design"] \ -$ }' \ -$ {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues - -> HTTP/1.1 201 Created -> Location: {% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17 -> X-RateLimit-Limit: 5000 - -> { -> "pull_request": { -> "patch_url": null, -> "html_url": null, -> "diff_url": null -> }, -> "created_at": "2012-11-14T15:25:33Z", -> "comments": 0, -> "milestone": null, -> "title": "New logo", -> "body": "We should have one", -> "user": { -> "login": "pengwynn", -> "gravatar_id": "7e19cd5486b5d6dc1ef90e671ba52ae0", -> "avatar_url": "https://secure.gravatar.com/avatar/7e19cd5486b5d6dc1ef90e671ba52ae0?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-user-420.png", -> "id": 865, -> "url": "{% data variables.product.api_url_pre %}/users/pengwynn" -> }, -> "closed_at": null, -> "updated_at": "2012-11-14T15:25:33Z", -> "number": 17, -> "closed_by": null, -> "html_url": "https://github.com/pengwynn/api-sandbox/issues/17", -> "labels": [ -> { -> "color": "ededed", -> "name": "design", -> "url": "{% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/labels/design" -> } -> ], -> "id": 8356941, -> "assignee": null, -> "state": "open", -> "url": "{% data variables.product.api_url_pre %}/repos/pengwynn/api-sandbox/issues/17" -> } -``` - -La respuesta nos entrega un par de sugerencias para el informe de problemas recién creado, tanto en el encabezado de respuesta de `Location` como en el campo de `url` de la respuesta de JSON. - -### Solicitudes condicionales - -Una gran parte de ser un buen ciudadano de la API es respetar los límites de tasa al almacenar información en el caché, la cual no haya cambiado. La API es compatible con las [solicitudes condicionales][conditional-requests] y te ayuda a hacer lo correcto. Considera el primer llamado que hicimos para obtener el perfil de defunkt: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/users/defunkt - -> HTTP/1.1 200 OK -> ETag: "bfd85cbf23ac0b0c8a29bee02e7117c6" -``` - -Además del cuerpo de JSON, toma nota del código de estado HTTP de `200` y del encabezado `ETag`. La [ETag][etag] es una huella digital de la respuesta. Si la pasamos en llamadas subsecuentes, podemos decirle a la API que nos entregue el recurso nuevamente, únicamente si cambió: - -```shell -$ curl -i -H 'If-None-Match: "bfd85cbf23ac0b0c8a29bee02e7117c6"' \ -$ {% data variables.product.api_url_pre %}/users/defunkt - -> HTTP/1.1 304 Not Modified -``` - -El estado `304` indica que el recurso no ha cambiado desde la última vez que lo solicitamos y que la respuesta no contendrá ningún cuerpo. Como bonificación, las respuestas `304` no contarán para tu [límite de tasa][rate-limiting]. - -¡Qué! ¡Ahora sabes los fundamentos de la API de {% data variables.product.product_name %}! - -* Autenticación básica & de OAuth -* Obtener y crear repositorios e informes de problemas -* Solicitudes condicionales - -Sigue aprendiendo con la siguiente guía de la API ¡[Fundamentos de la Autenticación][auth guide]! - -[wrappers]: /libraries/ -[curl]: http://curl.haxx.se/ -[media types]: /rest/overview/media-types -[oauth]: /apps/building-integrations/setting-up-and-registering-oauth-apps/ -[webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/ -[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/ -[repos-api]: /v3/repos/ -[repos-api]: /v3/repos/ -[pages]: http://pages.github.com -[nanoc]: http://nanoc.ws/ -[gitignore templates]: https://github.com/github/gitignore -[issues-api]: /v3/issues/ -[link-header]: http://www.w3.org/wiki/LinkHeader/ -[conditional-requests]: /v3/#conditional-requests -[rate-limiting]: /v3/#rate-limiting -[rate-limiting]: /v3/#rate-limiting -[users api]: /v3/users/#get-a-user -[defunkt github]: https://github.com/defunkt -[defunkt github]: https://github.com/defunkt -[json]: http://en.wikipedia.org/wiki/JSON -[authentication]: /v3/#authentication -[personal token]: /articles/creating-an-access-token-for-command-line-use -[personal token]: /articles/creating-an-access-token-for-command-line-use -[tokens settings]: https://github.com/settings/tokens -[pagination]: /v3/#pagination -[get repo]: /v3/repos/#get-a-repository -[create repo]: /v3/repos/#create-a-repository-for-the-authenticated-user -[create issue]: /v3/issues/#create-an-issue -[auth guide]: /guides/basics-of-authentication -[user repos api]: /v3/repos/#list-repositories-for-the-authenticated-user -[other user repos api]: /v3/repos/#list-repositories-for-a-user -[org repos api]: /v3/repos/#list-organization-repositories -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[get issues api]: /v3/issues/#list-issues-assigned-to-the-authenticated-user -[repo issues api]: /v3/issues/#list-repository-issues -[etag]: http://en.wikipedia.org/wiki/HTTP_ETag diff --git a/translations/es-XL/content/rest/guides/index.md b/translations/es-XL/content/rest/guides/index.md deleted file mode 100644 index 63f0477b2c..0000000000 --- a/translations/es-XL/content/rest/guides/index.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Guías -intro: 'Aprende como empezar con la API de REST, cómo funciona la autenticación, o cómo utilizar la API de REST para tareas diveras.' -redirect_from: - - /guides/ - - /v3/guides -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API -children: - - /getting-started-with-the-rest-api - - /basics-of-authentication - - /discovering-resources-for-a-user - - /delivering-deployments - - /rendering-data-as-graphs - - /working-with-comments - - /traversing-with-pagination - - /building-a-ci-server - - /best-practices-for-integrators - - /getting-started-with-the-git-database-api - - /getting-started-with-the-checks-api ---- -La intención de esta sección de documentos es que comiences a operar tan pronto como sea posible con aplicaciones de la API de {% data variables.product.product_name %} reales. Abordaremos todo lo que necesitas saber, desde la autenticación, hasta manipular los resultados, e incluso hasta combiar los resultados con otras apps. - -Cada tutorial en esta sección tendrá un proyecto, y cada proyecto se almacenará y documentará en nuestro repositorio público de [platform-samples](https://github.com/github/platform-samples). - -![El Electrocat](/assets/images/electrocat.png) -### Índice diff --git a/translations/es-XL/content/rest/guides/rendering-data-as-graphs.md b/translations/es-XL/content/rest/guides/rendering-data-as-graphs.md deleted file mode 100644 index 3dcbbc6673..0000000000 --- a/translations/es-XL/content/rest/guides/rendering-data-as-graphs.md +++ /dev/null @@ -1,341 +0,0 @@ ---- -title: Representar los datos en gráficas -intro: Aprende a visualizar los lenguajes de programación de tu repositorio utilizando la biblioteca D3.js y el Octokit de Ruby. -redirect_from: - - /guides/rendering-data-as-graphs/ - - /v3/guides/rendering-data-as-graphs -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -En esta guía vamos a utilizar la API para obtener información acerca de los repositorios que nos pertenecen y de los lenguajes de programación que los componen. Luego, vamos a visualizar la información en un par de formas diferentes utilizando la librería [D3.js][D3.js]. Para interactuar con la API de {% data variables.product.product_name %}, estaremos utilizando la excelente biblioteca de Ruby, [Octokit][Octokit]. - -Si aún no lo has hecho, deberías leer la guía de ["Fundamentos de la Autenticación"][basics-of-authentication] antes de comenzar con este ejemplo. Puedes encontrar el código fuente completo para este proyecto en el repositorio [platform-samples][platform samples]. - -¡Comencemos de inmediato! - -### Configurar una aplicación de OAuth - -Primero, [registra una aplicación nueva][new oauth application] en {% data variables.product.product_name %}. Configura la URL principal y la de rellamado como `http://localhost:4567/`. Tal como lo hemos hecho [antes][basics-of-authentication], vamos a gestionar la autenticación para la API implementando un recurso intermedio de Rack utilizando [sinatra-auth-github][sinatra auth github]: - -``` ruby -require 'sinatra/auth/github' - -module Example - class MyGraphApp < Sinatra::Base - # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! - # Instead, set and test environment variables, like below - # if ENV['GITHUB_CLIENT_ID'] && ENV['GITHUB_CLIENT_SECRET'] - # CLIENT_ID = ENV['GITHUB_CLIENT_ID'] - # CLIENT_SECRET = ENV['GITHUB_CLIENT_SECRET'] - # end - - CLIENT_ID = ENV['GH_GRAPH_CLIENT_ID'] - CLIENT_SECRET = ENV['GH_GRAPH_SECRET_ID'] - - enable :sessions - - set :github_options, { - :scopes => "repo", - :secret => CLIENT_SECRET, - :client_id => CLIENT_ID, - :callback_url => "/" - } - - register Sinatra::Auth::Github - - get '/' do - if !authenticated? - authenticate! - else - access_token = github_user["token"] - end - end - end -end -``` - -Configura un archivo similar de _config.ru_ como en el ejemplo previo: - -``` ruby -ENV['RACK_ENV'] ||= 'development' -require "rubygems" -require "bundler/setup" - -require File.expand_path(File.join(File.dirname(__FILE__), 'server')) - -run Example::MyGraphApp -``` - -### Obtener la información del repositorio - -En esta ocasión, para poder hablar con la API de {% data variables.product.product_name %}, vamos a utilizar la [Biblioteca de Ruby, Octokit][Octokit]. Esto es mucho más fácil que hacer un montón de llamadas de REST directamente. Además, un Githubber desarrolló Octokit, y se mantiene activamente, así que sabes que funcionará. - -Autenticarse con la API a través de Octokit es fácil. Solo pasa tu información de inicio de sesión y tu token en el constructor `Octokit::Client`: - -``` ruby -if !authenticated? - authenticate! -else - octokit_client = Octokit::Client.new(:login => github_user.login, :oauth_token => github_user.token) -end -``` - -Vamos a hacer algo interesante con los datos acerca de nuestros repositorios. Vamos a ver los diferentes lenguajes de programación que utilizan y a contar cuáles se utilizan más a menudo. Para hacerlo, primero necesitamos tomar una lista de nuestros repositorios desde la API. Con Octokit, esto se ve así: - -``` ruby -repos = client.repositories -``` - -Después, vamos a iterar sobre cada repositorio y a contar los lenguajes con los que {% data variables.product.product_name %} los asocia: - -``` ruby -language_obj = {} -repos.each do |repo| - # sometimes language can be nil - if repo.language - if !language_obj[repo.language] - language_obj[repo.language] = 1 - else - language_obj[repo.language] += 1 - end - end -end - -languages.to_s -``` - -Cuando reinicias tu servidor, tu página web debe mostrar más o menos esto: - -``` ruby -{"JavaScript"=>13, "PHP"=>1, "Perl"=>1, "CoffeeScript"=>2, "Python"=>1, "Java"=>3, "Ruby"=>3, "Go"=>1, "C++"=>1} -``` - -Hasta ahora vamos bien, pero no se ve muy amigable para un humano. Sería genial poder tener algún tipo de visualización para entender cómo se distribuye este conteo de lenguajes. Vamos a alimentar a D3 con nuestros conteos para obtener una gráfica de barras clara que represente la popularidad de los lenguajes que utilizamos. - -### Visualizar los conteos de los lenguajes - -D3.js, o simplemente D3, es una biblioteca completa para crear muchos tipos de gráficos, tablas, y visualizaciones interactivas. El utilizarlo a detalle va más allá del alcance de esta guía, pero para ver un buen artículo introductorio al respecto, revisa ["D3 para mortales"][D3 mortals]. - -D3 es una biblioteca de JavaScript a la que le gusta trabajar con matrices de datos. Así que, vamos a convertir a nuestro hash de Ruby en una matriz de JSON para que JavaScript la utilice en el buscador. - -``` ruby -languages = [] -language_obj.each do |lang, count| - languages.push :language => lang, :count => count -end - -erb :lang_freq, :locals => { :languages => languages.to_json} -``` - -Simplemente estamos iterando sobre cada par de clave-valor en nuestro objeto y lo estamos cargando en una matriz nueva. La razón por la cual no lo hicimos antes es porque no queríamos iterar sobre nuestro objeto de `language_obj` mientras lo estábamos creando. - -Ahora, _lang_freq.erb_ va a necesitar algo de JavaScript para apoyar a que se interprete una gráfica de barras. Por ahora, puedes simplemente utilizar el código que se te proporciona aquí y referirte a los recursos cuyo enlace se señala anteriormente si quieres aprender más sobre cómo funciona D3: - -``` html - - - - - - - - -

    Check this sweet data out:

    -
    - - - - -``` - -¡Uf! Nuevamente, no te preocupes de la mayoría de lo que está haciendo este código. La parte relevante es lo que está hasta arriba--`var data = <%= languages %>;`--lo cual indica que estamos pasando nuestra matriz previamente creada de `languages` en el ERB para su manipulación. - -Tal como sugiere la guía de "D3 para Mortales", esto no es necesariamente la mejor forma de utilizar D3. Pero nos sirve para ilustrar cómo puedes utilizar la biblioteca, junto con Octokit, para hacer algunas cosas verdaderamente increíbles. - -### Combinar las diferentes llamadas de la API - -Ahora es el momento de hacer una confesión: el atributo de `language` dentro de los repositorios solo identifica el lenguaje "primario" que se definió. Esto significa que, si tienes un repositorio que combine varios lenguajes, el que tenga más bytes de código se considera comoel primario. - -Vamos a combinar algunas llamadas a la API para obtener una representación _fidedigna_ de qué lenguaje tiene la mayor cantidad de bytes escritos en todo nuestro código. Un [diagrama de árbol][D3 treemap] deberá ser la mejor forma de visualizar los tamaños de los lenguajes de código que utilizamos, en vez de obtener solo el conteo. Necesitaremos construir una matriz de objetos que se vea más o menos así: - -``` json -[ { "name": "language1", "size": 100}, - { "name": "language2", "size": 23} - ... -] -``` - -Como ya tenemos una lista de repositorios anteriormente, vamos a inspeccionar cada uno y a llamar al [método de la API para listar los lenguajes][language API]: - -``` ruby -repos.each do |repo| - repo_name = repo.name - repo_langs = octokit_client.languages("#{github_user.login}/#{repo_name}") -end -``` - -Desde aquí, agregaremos de forma acumulativa en una "lista maestra" cada lenguaje que se encuentre: - -``` ruby -repo_langs.each do |lang, count| - if !language_obj[lang] - language_obj[lang] = count - else - language_obj[lang] += count - end -end -``` - -Después de ésto, daremos formato al contenido en una estructura que entienda el D3: - -``` ruby -language_obj.each do |lang, count| - language_byte_count.push :name => "#{lang} (#{count})", :count => count -end - -# some mandatory formatting for D3 -language_bytes = [ :name => "language_bytes", :elements => language_byte_count] -``` - -(Para obtener más información sobre a magia del diagrama de árbo del D3, échale un vistazo a [este tutorial sencillo][language API].) - -Para concluir, pasamos la información de JSON a la misma plantilla de ERB: - -``` ruby -erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_count => language_bytes.to_json} -``` - -Como antes, hay mucho JavaScript que puedes dejar directamente en tu plantilla: - -``` html -
    - -``` - -¡Y voilá! Hermosos rectángulos que contienen los lenguajes de tu repositorio con proporciones relativas que se pueden ver inmediatamente. Tal vez necesites modificar la altura y el ancho de tu diagrama de árbol para pasarlo como los primeros dos argumentos en el `drawTreemap` anterior y así lograr que se muestre adecuadamente toda la información. - - -[D3.js]: http://d3js.org/ -[basics-of-authentication]: /rest/guides/basics-of-authentication -[basics-of-authentication]: /rest/guides/basics-of-authentication -[sinatra auth github]: https://github.com/atmos/sinatra_auth_github -[Octokit]: https://github.com/octokit/octokit.rb -[Octokit]: https://github.com/octokit/octokit.rb -[D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ -[D3 treemap]: http://bl.ocks.org/mbostock/4063582 -[language API]: /v3/repos/#list-repository-languages -[language API]: /v3/repos/#list-repository-languages -[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs -[new oauth application]: https://github.com/settings/applications/new diff --git a/translations/es-XL/content/rest/guides/traversing-with-pagination.md b/translations/es-XL/content/rest/guides/traversing-with-pagination.md deleted file mode 100644 index d97a62143a..0000000000 --- a/translations/es-XL/content/rest/guides/traversing-with-pagination.md +++ /dev/null @@ -1,210 +0,0 @@ ---- -title: Desplazarse con la paginación -intro: Explora las formas para utilizar la paginación en la administración de tus respuestas con algunos ejemplos de cómo utilizar la API de Búsqueda. -redirect_from: - - /guides/traversing-with-pagination/ - - /v3/guides/traversing-with-pagination -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -La API de {% data variables.product.product_name %} proporciona una gran cantidad de información para el consumo de los desarrolladores. La mayoría de las veces incluso podrías encontrar que estás pidiendo _demasiada_ información y, para mantener felices a nuestros servidores, la API [paginará los elementos solicitados][pagination] automáticamente. - -En esta guía haremos algunos llamados a la API de Búsqueda de {% data variables.product.product_name %} e iteraremos sobre los resultados utilizando la paginación. Puedes encontrar todo el código fuente de este proyecto en el repositorio [platform-samples][platform samples]. - -### Fundamentos de la Paginación - -Para empezar, es importante saber algunos hechos acerca de recibir elementos paginados: - -1. Las diferentes llamadas a la API responden con predeterminados diferentes también. Por ejemplo, una llamada a [Listar repositorios públicos](/v3/repos/#list-public-repositories) proporciona elementos paginados en conjuntos de 30, mientras que una llamada a la API de Búsqueda de GitHub proporciona elementos en conjuntos de 100 -2. Puedes especificar cuantos elementos quieres recibir (hasta llegar a 100 como máxmo); pero, -3. Por razones técnicas, no todas las terminales se comportan igual. Por ejemplo, los [eventos](/v3/activity/events/) no te dejarán usar un máximo de elementos a recibir. Asegúrate de leer la documentación sobre cómo gestionar los resultados paginados para terminales específicas. - -Te proporcionamos la información sobre la paginación en [el encabezado de enlace](http://tools.ietf.org/html/rfc5988) de una llamada a la API. Por ejemplo, vamos a hacer una solicitud de curl a la API de búsqueda para saber cuántas veces se utiliza la frase `addClass` en los proyectos de Mozilla: - -```shell -$ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user:mozilla" -``` - -El parámetro `-I` indica que solo nos interesan los encabezados y no el contenido en sí. Al examinar el resultado, notarás alguna información en el encabezado de enlace, la cual se ve así: - - Link: <{% data variables.product.api_url_code %}/search/code?q=addClass+user%3Amozilla&page=2>; rel="next", - <{% data variables.product.api_url_code %}/search/code?q=addClass+user%3Amozilla&page=34>; rel="last" - -Vamos a explicarlo. `rel="next"` dice que la siguiente página es la `page=2`. Esto tiene sentido ya que, predeterminadamente, todas las consultas paginadas inician en la página `1.` y `rel="last"` proporciona más información, lo cual nos dice que la última página de los resultados es la `34`. Por lo tanto, tenemos otras 33 páginas de información que podemos consumir acerca de `addClass`. ¡Excelente! - -Confía **siempre** en estas relaciones de enlace que se te proporcionan. No intentes adivinar o construir tu propia URL. - -#### Navegar a través de las páginas - -Ahora que sabescuántas páginas hay para recibir, puedes comenzar a navegar a través de ellas para consumir los resultados. Esto se hace pasando un parámetro de `page`. Predeterminadamente, la `page` siempre comienza en `1`. Vamos a saltar a la página 14 para ver qué pasa: - -```shell -$ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user:mozilla&page=14" -``` - -Aquí está el encabezado de enlace una vez más: - - Link: <{% data variables.product.api_url_code %}/search/code?q=addClass+user%3Amozilla&page=15>; rel="next", - <{% data variables.product.api_url_code %}/search/code?q=addClass+user%3Amozilla&page=34>; rel="last", - <{% data variables.product.api_url_code %}/search/code?q=addClass+user%3Amozilla&page=1>; rel="first", - <{% data variables.product.api_url_code %}/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev" - -Como era de esperarse, la `rel="next"` está en 15, y la `rel="last"` es aún 34. Pero ahora tenemos más información: `rel="first"` indica la URL de la _primera_ página, y lo que es más importante, `rel="prev"` te dice el número de página de la página anterior. Al utilizar esta información, puedes construir alguna IU que le permita a los usuarios saltar entre la lista de resultados principal, previa o siguiente en una llamada a la API. - -#### Cambiar la cantidad de elementos recibidos - -Al pasar el parámetro `per_page`, puedes especificar cuantos elementos quieres que devuelva cada página, hasta un máximo de 100 de ellos. Vamos a comenzar pidiendo 50 elementos acerca de `addClass`: - -```shell -$ curl -I "{% data variables.product.api_url_pre %}/search/code?q=addClass+user:mozilla&per_page=50" -``` - -Nota lo que hace en la respuesta del encabezado: - - Link: <{% data variables.product.api_url_code %}/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next", - <{% data variables.product.api_url_code %}/search/code?q=addClass+user%3Amozilla&per_page=50&page=20>; rel="last" - -Como habrás adivinado, la información de la `rel="last"` dice que la última página ahora es la 20. Esto es porque estamos pidiendo más información por página acerca de nuestros resultados. - -### Consumir la información - -No debes estar haciendo llamadas de curl de bajo nivel para poder trabajar con la paginación, así que escribamos un script de Ruby sencillo que haga todo lo que acabamos de describir anteriormente. - -Como siempre, primero solicitaremos la biblioteca de Ruby [Octokit.rb de GitHub][octokit.rb] y pasaremos nuestro [token de acceso personal][personal token]: - -``` ruby -require 'octokit' - -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below -client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] -``` - -Después, ejecutaremos la búsqueda utilizando el método `search_code` de Octokit. A diferencia de cuando se utiliza `curl`, también podemos recuperar de inmediato la cantidad de resultados, así que hagámoslo: - -``` ruby -results = client.search_code('addClass user:mozilla') -total_count = results.total_count -``` - -Ahora tomemos el número de la última página de forma similar a la información de `page=34>; rel="last"` en el encabezado de enlace. Octokit.rb es compatible con información de paginación a través de una implementación llamada "[Relaciones de enlace de hipermedios][hypermedia-relations]." No entraremos en detalles sobre lo que es, pero basta con decir que cada elemento en la variable de `results` tiene un hash que se llama `rels`, el cual contiene información sobre `:next`, `:last`, `:first`, y `:prev`, dependiendo del resultado en el que estés. Estas relaciones también contienen información sobre la URL resultante llamando a `rels[:last].href`. - -Ahora que sabemos esto, vamos a tomar el número de página del último resultado y a presentar toda esta información al usuario: - -``` ruby -last_response = client.last_response -number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1] - -puts "There are #{total_count} results, on #{number_of_pages} pages!" -``` - -Por último, vamos a iterar entre los resultados. Puedes hacerlo con un bucle como `for i in 1..number_of_pages.to_i`, pero mejor vamos a seguir los encabezados de `rels[:next]` para recuperar la información de cada página. Para mantener la simplicidad, solo vamos a tomar la ruta del archivo del primer resultado de cada página. Para hacerlo, vamos a necesitar un bucle; y al final de cada bucle, vamos a recuperar los datos que se configuraron para la siguiente página siguiendo la información de `rels[:next]`. El bucle terminará cuando ya no haya información de `rels[:next]` que consumir (es decir, cuando estemos en `rels[:last]`). Se verá más o menos así: - -``` ruby -puts last_response.data.items.first.path -until last_response.rels[:next].nil? - last_response = last_response.rels[:next].get - puts last_response.data.items.first.path -end -``` - -Cambiar la cantidad de elementos por página es extremadamente simple con Octokit.rb. Simplemente pasa un hash de opciones de `per_page` a la construcción del cliente inicial. Después de ésto, tu código debería permanecer intacto: - -``` ruby -require 'octokit' - -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below -client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] - -results = client.search_code('addClass user:mozilla', :per_page => 100) -total_count = results.total_count - -last_response = client.last_response -number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1] - -puts last_response.rels[:last].href -puts "There are #{total_count} results, on #{number_of_pages} pages!" - -puts "And here's the first path for every set" - -puts last_response.data.items.first.path -until last_response.rels[:next].nil? - last_response = last_response.rels[:next].get - puts last_response.data.items.first.path -end -``` - -### Construir enlaces de paginación - -Habitualmente, con la paginación, tu meta no es concentrar todos los resultados posibles, sino más bien producir un conjunto de navegación, como éste: - -![Muestra de los enlaces de paginación](/assets/images/pagination_sample.png) - -Vamos a modelar una micro versión de lo que esto podría implicar. - -Desde el código anterior, ya sabemos que podemos obtener el `number_of_pages` en los resultados paginados desde la primera llamada: - -``` ruby -require 'octokit' - -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below -client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] - -results = client.search_code('addClass user:mozilla') -total_count = results.total_count - -last_response = client.last_response -number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1] - -puts last_response.rels[:last].href -puts "There are #{total_count} results, on #{number_of_pages} pages!" -``` - -Desde aquí, podemos construir una hermosa representación en ASCII de las cajas de número: -``` ruby -numbers = "" -for i in 1..number_of_pages.to_i - numbers << "[#{i}] " -end -puts numbers -``` - -Vamos a simular que un usuario da clic en alguna de estas cajas mediante la construcción de un número aleatorio: - -``` ruby -random_page = Random.new -random_page = random_page.rand(1..number_of_pages.to_i) - -puts "A User appeared, and clicked number #{random_page}!" -``` - -Ahora que tenemos un número de página, podemos usar el Octokit para recuperar explícitamente dicha página individual si pasamos la opción `:page`: - -``` ruby -clicked_results = client.search_code('addClass user:mozilla', :page => random_page) -``` - -Si quisiéramos ponernos elegantes, podríamos también tomar la página anterior y posterior para generar los enlaces de los elementos anterior (`<<`) y posterior (`>>`): - -``` ruby -prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)" -next_page_href = client.last_response.rels[:next] ? client.last_response.rels[:next].href : "(none)" - -puts "The prev page link is #{prev_page_href}" -puts "The next page link is #{next_page_href}" -``` - -[pagination]: /v3/#pagination -[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination -[octokit.rb]: https://github.com/octokit/octokit.rb -[personal token]: /articles/creating-an-access-token-for-command-line-use -[hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination diff --git a/translations/es-XL/content/rest/guides/working-with-comments.md b/translations/es-XL/content/rest/guides/working-with-comments.md deleted file mode 100644 index dacf7c1e88..0000000000 --- a/translations/es-XL/content/rest/guides/working-with-comments.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Trabajar con los comentarios -intro: 'Puedes acceder y administrar los comentarios en tus solicitudes de extracción, informes de problemas o confirmaciones si utilizas la API de REST.' -redirect_from: - - /guides/working-with-comments/ - - /v3/guides/working-with-comments -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -Para cualquier solicitud de extracción, {% data variables.product.product_name %} proporciona tres tipos de visualizaciones de comentario: [comentarios en la solicitud de extracción][PR comment] integrales, [comentarios en una línea específica][PR line comment] dentro de la solicitud de extracción, y [comentarios sobre una confirmación específica][commit comment] dentro de la solicitud de extracción. - -Cada uno de estos tipos de comentario pasa por una porción diferente de la API de {% data variables.product.product_name %}. En esta guía exploraremos cómo puedes acceder y manipular cada uno de ellos. En cada ejemplo utilizaremos [esta muestra de Solicitud de Extracción que se hizo][sample PR] en el repositorio de "octocat". Como siempre, puedes encontrar las muestras en [nuestro repositorio de platform-samples][platform-samples]. - -### Comentarios de las Solicitudes de Extracción - -Para acceder a loscomentarios de una solicitud de extracción deberás de pasar por la [API de Informes de Problemas][issues]. Esto puede parecer contraintuitivo al principio. Pero una vez que entiendes que una Solicitud de Extracción es solo un informe de problemas con código, tendrá sentido utuilizar la API de Informes de Problemas para crear comentarios en una solicitud de extracción. - -Demostraremos cómo obtener comentarios de una solicitud de extracción mediante la creación de un script de Ruby que utilice [Octokit.rb][octokit.rb]. También deberás crear un [token de acceso personal][personal token]. - -El código siguiente debería ayudarte a empezar a acceder a los comentarios de una solicitud de extracción utilizando Octokit.rb: - -``` ruby -require 'octokit' - -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below -client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] - -client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment| - username = comment[:user][:login] - post_date = comment[:created_at] - content = comment[:body] - - puts "#{username} made a comment on #{post_date}. It says:\n'#{content}'\n" -end -``` - -Aquí estamos llamando específicamente a la API de Informes de problemas para obtener los comentarios (`issue_comments`), proporcionando tanto el nombre del repositorio (`octocat/Spoon-Knife`) como la ID de la solicitud de extracción en la que estamos interesados (`1176`). Después, solo es cuestión de iterar a través de los comentarios para obtener la información sobre cada uno. - -### Comentarios en una línea de una solicitud de extracción - -Dentro de la vista de diferencias, puedes iniciar un debate sobre algún aspecto específico de un cambio particular que se haya hecho dentro de la solicitud de extracción. Estos comentarios ocurren en las líneas individuales dentro de un archivo que ha cambiado. La URL de la terminal para este debate veien de [la API de Revisión de Solicitudes de Extracción][PR Review API]. - -El código siguiente obtiene todos los comentarios de la solicitud de extracción que se hayan hecho en los archivos, si se le da un número particular de solicitud de extracción: - -``` ruby -require 'octokit' - -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below -client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] - -client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment| - username = comment[:user][:login] - post_date = comment[:created_at] - content = comment[:body] - path = comment[:path] - position = comment[:position] - - puts "#{username} made a comment on #{post_date} for the file called #{path}, on line #{position}. It says:\n'#{content}'\n" -end -``` - -Te darás cuenta de que es increíblemente similar al ejemplo anterior. La diferencia entre esta vista y el comentario de la solicitud de extracción es el enfoque de la conversación. El comentario que se haga en una solicitud de extracción deberá reservarse para debatir ideas sobre el enfoque general del código. Cualquier comentario que se haga como parte de una revisión de una Solicitud de Extracción deberá tratar específicamente la forma en la que se implementa un cambio específico dentro de un archivo. - -### Comentarios de las confirmaciones - -El último tipo de comentarios suceden específicamente en confirmaciones individuales. Es por esto que utilizan [la API de comentarios de las confirmaciones][commit comment API]. - -Para recuperar los comentarios en una confirmación, necesitarás utilizar el SHA1 de ésta. Es decir, no utilizarás ningún identificador relacionado con la Solicitud de Extracción. Aquí hay un ejemplo: - -``` ruby -require 'octokit' - -# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! -# Instead, set and test environment variables, like below -client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] - -client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a4edd96e").each do |comment| - username = comment[:user][:login] - post_date = comment[:created_at] - content = comment[:body] - - puts "#{username} made a comment on #{post_date}. It says:\n'#{content}'\n" -end -``` - -Ten en cuenta que esta llamada a la API recuperará comentarios de una sola línea, así como aquellos que se hagan en toda la confirmación. - -[PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792 -[PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889 -[commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848 -[sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176 -[platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments -[issues]: /v3/issues/comments/ -[personal token]: /articles/creating-an-access-token-for-command-line-use -[octokit.rb]: https://github.com/octokit/octokit.rb -[PR Review API]: /v3/pulls/comments/ -[commit comment API]: /v3/repos/comments/#get-a-commit-comment diff --git a/translations/es-XL/content/rest/index.md b/translations/es-XL/content/rest/index.md deleted file mode 100644 index 8cbfd264b3..0000000000 --- a/translations/es-XL/content/rest/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: API de REST de GitHub -shortTitle: API REST -intro: 'Puedes utilizar la API de REST de {% data variables.product.prodname_dotcom %} para crear llamadas y obtener los datos que necesitas para integrar con GitHub.' -redirect_from: - - /v3 -versions: - fpt: '*' - ghes: '*' - ghae: '*' -children: - - /overview - - /reference - - /guides ---- - diff --git a/translations/es-XL/content/rest/overview/api-previews.md b/translations/es-XL/content/rest/overview/api-previews.md deleted file mode 100644 index e5f9845c0d..0000000000 --- a/translations/es-XL/content/rest/overview/api-previews.md +++ /dev/null @@ -1,306 +0,0 @@ ---- -title: Vistas previas de la API -intro: Puedes utilizar las vistas previas de la API para probar características nuevas y proporcionar retroalimentación antes de que dichas características se hagan oficiales. -redirect_from: - - /v3/previews -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -Las vistas previas de la API te permiten probar API nuevas y cambios a los métodos existentes de las API antes de que se hagan oficiales en la API de GitHub. - -Durante el periodo de vista previa, podríamos cambiar algunas características con base en la retroalimentación de los desarrolladores. Si realizamos cambios, lo anunciaremos en el [blog de desarrolladores](https://developer.github.com/changes/) sin aviso previo. - -Para acceder a la vista previa de las API, necesitarás proporcionar un [tipo de medios](/v3/media) 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. - -{% if currentVersion == "free-pro-team@latest" %} -### Migraciones - -Te permite descargar repositorios desde tu usuario de GitHub o cuenta organizacional para revisar, respaldar y [migrar](/v3/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 %} - -### Despliegues ampliados - -Ejerce mayo control sobre los [despliegues](/v3/repos/deployments/) con más información y granularidad más fina. - -**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/) - -### Reacciones - -Administra las [reacciones](/v3/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/) - -### Línea de tiempo - -Obtén una [lista de eventos](/v3/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/) - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} -### Pages - -Obtén más información sobre tu sitio de [GitHub Pages](/v3/repos/pages/). - -**Tipo de medios personalizados:** `mister-fantastic-preview` **Anunciado en:**[2016-07-06](https://developer.github.com/changes/2016-07-06-github-pages-preview-api/) -{% endif %} - -{% if currentVersion != "free-pro-team@latest" %} -### Ambientes de pre-recepción - -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 %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -### Integraciones - -Administra las [integraciones](/early-access/integrations/) a través de la API. - -**Tipo de medios personalizados:** `machine-man-preview` **Anunciado en:**[2016-09-14](https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/) -{% endif %} - -### Proyectos - -Administra [proyectos](/v3/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/) - -### Búsqueda de confirmación - -[Busca confirmaciones](/v3/search/). - -**Tipo de medios personalizados:** `cloak-preview` **Anunciado en:**[2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) - -{% if currentVersion == "free-pro-team@latest" %} -### Métricas del perfil comunitario - -Recupera las [métricas del perfil comunitario](/v3/repos/community/) (también conocidas como salud de la comunidad) para cualquier repositorio público. - -**Tipo de medios personalizados:** `black-panther-preview` **Anunciado en:**[2017-02-09](https://developer.github.com/changes/2017-02-09-community-health/) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -### Bloqueo de usuarios - -Los usuarios pueden [bloquear a otros usuarios](/v3/users/blocking/). Las organizaciones también pueden [bloquear usuarios](/v3/orgs/blocking/). - -**Tipo de medios personalizado:** `giant-sentry-fist-preview` **Anunciado en:** [2011-05-31](https://github.com/blog/862-block-the-bullies) **Actualización 1:** [2016-04-04](https://github.com/blog/2146-organizations-can-now-block-abusive-users) **Actualización 2:** [2016-08-17](https://github.com/blog/2229-see-the-users-you-ve-blocked-on-your-settings-page) -{% endif %} - -### Temas del repositorio - -Ver una lista de los [temas del repositorio](/articles/about-topics/) en [llamadas](/v3/repos/) que devuelven los resultados del mismo. - -**Tipo de medios personalizados:** `mercy-preview` **Anunciado en:**[2017-01-31](https://github.com/blog/2309-introducing-topics) - -### Códigos de conducta - -Ver todos los [códigos de conducta](/v3/codes_of_conduct) u obtener qué código de conducta tiene actualmente un repositorio. - -**Tipo de medios personalizado:** `scarlet-witch-preview` - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %} -### Equipos anidados - -Incluir contenido anidado del equipo en cargas útiles del [equipo](/v3/teams/) - -**Tipo de medios personalizados:** `hellcat-preview` **Anunciado en:**[2017-09-01](https://developer.github.com/changes/2017-08-30-preview-nested-teams) - -{% endif %} - -{% if currentVersion != "free-pro-team@latest" %} - -### Webhooks globales - -Habilita los [webhooks globales](/v3/enterprise-admin/global_webhooks/) para una [organización](/webhooks/event-payloads/#organization) y para los tipos de evento del [usuario](/webhooks/event-payloads/#user). Esta vista previa de la API solo está disponible para {% data variables.product.prodname_ghe_server %}. - -**Tipo de medios personalizados:** `superpro-preview` **Anunciado en:**[2017-12-12](/v3/enterprise-admin/global_webhooks) - -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %} -### Transferencia de repositorio - -Transfiere u [repositorio](/v3/repos/) a una organización o usuario. - -**Tipo de medios personalizados:** `nightshade-preview` **Anunciado en:**[2017-11-09](https://developer.github.com/changes/2017-11-09-repository-transfer-api-preview) -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -### Agregar razón de bloqueo - -Ahora puedes agregar una razón cuando [bloquees un informe de problemas](/v3/issues/#lock-an-issue). - -**Tipo de medios personalizados:** `sailor-v-preview` **Anunciado en:**[2018-01-10](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} -### Debates de equipo - -Ahora puedes usar la API para administrar los [debates de equipo](/v3/teams/discussions) y los [comentarios sobre los debates de equipo](/v3/teams/discussion_comments). - -**Tipo de medios personalizados:** `echo-preview` **Anunciado en:**[2018-02-07](https://developer.github.com/changes/2018-02-07-team-discussions-api) - -{% endif %} - -### Requerir confirmaciones firmadas - -Ahora puedes utilizar la API para administrar la configuración para [requerir confirmaciones firmadas en ramas protegidas](/v3/repos/branches). - -**Tipo de medios personalizados:** `zzzax-preview` **Anunciado en:**[2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) - -### Requerir múltiples revisiones de aprobación - -Ahora puedes [requerir múltiples revisiones de aprobación](/v3/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) - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} -### Recuperar la información de la tarjeta de visita virtual - -Recupera la información de la [tarjeta de visita virtual de alguien](/v3/users/#get-contextual-information-for-a-user). - -**Tipo de medios personalizados:** `hagar-preview` **Anunciado en:**[2018-03-21](https://developer.github.com/changes/2018-03-21-hovercard-api-preview) - -{% endif %} - -### API de suites de verificación y ejecuciones de verificación - -Permite a una GitHub App ejecutar verificaciones externas en el código de un repositorio. Consulta las API de [Ejecuciones de verificación](/v3/checks/runs/) y [Suites de verificación](/v3/checks/suites/) para obtener más detalles. - -**Tipo de medios personalizados:** `antiope-preview` **Anunciado en:**[2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) - -{% if currentVersion != "free-pro-team@latest" %} - -### Acceso anónimo de Git a los repositorios - -Cuando una instancia de {% data variables.product.prodname_ghe_server %} está en modo privado, los administradores de sitio y de repositorio pueden habilitar el acceso anónimo de Git para los repositorios públicos. - -**Tipo de medios personalizados:** `x-ray-preview` **Anunciado en:**[2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/) - -{% endif %} - -### Detalles de la tarjeta de proyecto - -Las respuestas de la API de REST para los [eventos de los informes de problemas](/v3/issues/events/) y para [los eventos de la línea de tiempo de los informes de problemas](/v3/issues/timeline/) ahora devuelven el campo `project_card` para los eventos relacionados con los proyectos. - -**Tipo de medios personalizados:** `starfox-preview` **Anunciado en:**[2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) - -{% if currentVersion == "free-pro-team@latest" %} - -### Manifiestos de las GitHub Apps - -Los Manifiestos de las GitHub Apps permiten a las personas crear GitHub Apps preconfiguradas. Consulta la sección "[Crear GitHub Apps desde un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para obtener más detalles. - -**Tipo de medios personalizado:** `fury-preview` - -{% endif %} - -### Estados de despliegue - -Ahora puedes actualizar el `environment` de un [estado de despliegue](/v3/repos/deployments/#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/) - -### 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](/v3/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/) - -### 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/) - -{% if currentVersion == "free-pro-team@latest" %} - -### Restricciones de interacción para repositorios y organizaciones - -Te permite restringir interacciones temporalmente, tales como comentario abrir informes de problemas, y crear solicitudes de extracción para los repositorios u organizaciones de {% data variables.product.product_name %}. Cuando lo habilitas, únicamente el grupo específico de usuarios de {% data variables.product.product_name %} podrá participar en estas interacciones. Consulta las API de [Interacciones del repositorio](/v3/interactions/repos/) y de [Interacciones de la organización](/v3/interactions/orgs/) para obtener más detalles. - -**Tipo de medios personalizados:** `sombra-preview` **Anunciado en:**[2018-12-18](https://developer.github.com/changes/2018-12-18-interactions-preview/) - -{% endif %} - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %} -### Solicitudes de extracción en borrador - -Puedes utilizar la API de Borradores de Solicitudes de Extracción y sus terminales de [solicitudes de extracción](/v3/pulls/) para ver si una solicitud de extracción está en estado de borrador. Para aprender más sobre los borradores de las solicitudes de extracción, consulta la sección "[Acerca de las solicitudes de extracción](/articles/about-pull-requests/)". - -**Tipos de medios personalizados:** `shadow-cat-preview` **Anunciado en:**[2019-02-14](https://developer.github.com/changes/2019-02-14-draft-pull-requests/) - -{% endif %} - -### Habilitar e inhabilitar las páginas - -Puedes utilizar las terminales nuevas en la [API de páginas](/v3/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/) - -### Listar ramas o solicitudes de extracción para una confirmación - -Puedes utilizar dos terminales nuevas en la [API de Confirmaciones](/v3/repos/commits/) para listar las ramas o las solicitudes de extracción para una confirmación. - -**Tipo de medios personalizados:** `groot-preview` **Anunciado en:**[2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/) - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %} -### Desinstalar una GitHub App - -Los propietarios de las GitHub Apps ahora pueden desinstalar una app utilizando la [API de Apps](/v3/apps/#delete-an-installation-for-the-authenticated-app). - -**Tipo de medios personalizado:** `gambit-preview` -{% endif %} - -### Habilitar o inhabilitar las alertas vulnerables para un repositorio - -Puedes utilizar dos terminales nueva en la [API de Repos](/v3/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/) - -### Actualizar la rama de una solicitud de extracción - -Puedes utilizar una terminal nueva para [actualizar una rama de una solicitud de extracción](/v3/pulls/#update-a-pull-request-branch) con cambios desde el HEAD de la rama ascendente. - -**Tipo de medios personalizados:** `lydian-preview` **Anunciado en:**[2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) - -{% if currentVersion == "free-pro-team@latest" %} -### 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](/v3/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 - -Puedes Puedes utilizar una terminal nueva para [crear un repositorio utilizando una plantilla](/v3/repos/#create-a-repository-using-a-template) y para [crear un repositorio para el usuario autenticado](/v3/repos/#create-a-repository-for-the-authenticated-user) que constituye un repositorio de plantilla si configuras el parámetro `is_template` como `true`. [Obten un repositorio](/v3/repos/#get-a-repository) para verificar si se configuró como un repositorio de plantilla utilizando la clave `is_template`. - -**Tipos de medios personalizados:** `baptiste-preview` **Anunciado en:**[2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) - -{% if currentVersion == "enterprise-server@2.20" %} -### Nuevas terminales de la API de Aplicaciones OAuth - -Puedes administrar los tokens para las Apps de OAuth de forma más segura si utilizas tokens de OAuth como parámetros de entrada en vez de como parámetros de ruta con las nuevas terminales de la [API de aplicaciones de OAuth](/v3/apps/oauth_applications/). - -**Tipo de medios personalizados:** `doctor-strange-preview` **Anunciado en:**[2019-11-05](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -### Parámetro de visibilidad nuevo para la API de Repositorios - -Puedes configurar y recuperar la visibilidad de un repositorio en la [API de Repositorios](/v3/repos/). - -**Tipo de medios personalizados:** `nebula-preview` **Anunciado en:**[2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) -{% endif %} diff --git a/translations/es-XL/content/rest/overview/endpoints-available-for-github-apps.md b/translations/es-XL/content/rest/overview/endpoints-available-for-github-apps.md deleted file mode 100644 index efd763f348..0000000000 --- a/translations/es-XL/content/rest/overview/endpoints-available-for-github-apps.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Terminales disponibles para las Apps de GitHub -intro: Tu app puede hacer solicitudes a las siguientes terminales de REST. -redirect_from: - - /v3/apps/available-endpoints - - /rest/reference/endpoints-available-for-github-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -Debes utilizar un token de acceso a la isntalación para acceder a las terminales utilizando tu {% data variables.product.prodname_github_app %}. Para obtener más información, consulta la sección "[Autenticarse con {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". - -{% for thing in rest.operationsEnabledForApps[currentVersion] %} -{% assign category = thing[0] %} -{% assign operations = thing[1] %} -{% if operations.size > 0 %} -

    - {{ category }} -

    - -{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/overview/index.md b/translations/es-XL/content/rest/overview/index.md deleted file mode 100644 index fd2b85fa21..0000000000 --- a/translations/es-XL/content/rest/overview/index.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Resumen de la API de REST -shortTitle: Resumen -intro: 'Aprende sobre los recursos, bibliotecas, vistas previas y solución de problemas para la API de REST de {% data variables.product.prodname_dotcom %}.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API -children: - - /resources-in-the-rest-api - - /media-types - - /other-authentication-methods - - /troubleshooting - - /api-previews - - /libraries - - /openapi-description - - /endpoints-available-for-github-apps ---- -### Índice diff --git a/translations/es-XL/content/rest/overview/libraries.md b/translations/es-XL/content/rest/overview/libraries.md deleted file mode 100644 index 9e3235e63f..0000000000 --- a/translations/es-XL/content/rest/overview/libraries.md +++ /dev/null @@ -1,165 +0,0 @@ ---- -title: Bibliotecas -intro: 'Puedes utilizar la biblioteca oficial de Octokit y otras bibliotecas de terceros para extender y simplificar cómo utilizas la API de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /libraries/ - - /v3/libraries -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -
    - El Gundamcat -

    Octokit tiene
    - muchos sabores

    -

    Utiliza la biblioteca oficial de Octokit, o elige entre cualquiera de las bibliotecas de terceros disponibles.

    -
    -
    Ruby octokit.rb
    -
    .NET octokit.net
    -
    JavaScript octokit/rest.js
    -
    -
    - -# Bibliotecas de terceros - -### Clojure - -* [Tentacles][tentacles] - -### Dart - -* [github.dart][github.dart] - -### Emacs Lisp - -* [gh.el][gh.el] - -### Erlang - -* [octo.erl][octo-erl] - -### Go - -* [go-github][] - -### Haskell - -* [github][haskell-github] - -### Java - -* La biblioteca de la [API de Java de GitHub (org.eclipse.egit.github.core)](https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core) es parte del [Conector Mylyn de GitHub](https://github.com/eclipse/egit-github) y pretende ser compatible integralmente para la API v3 de GitHub. Las compilaciones se encuentran disponibles en la [Central Maven](http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22org.eclipse.egit.github.core%22). -* La [API de GitHub para Java (org.koshuke.github)](http://github-api.kohsuke.org/) define una representación orientada a objetos de la API de GitHub. -* La [API de GitHub JCabi](http://github.jcabi.com) se basa en la API de JSON para Java7 (JSR-353) y simplifica las pruebas con un talón de GitHub para el tiempo de ejecución, y abarca toda la API. - -### JavaScript - -* [Biblioteca de NodeJS de GitHub][octonode] -* [programa de seguridad gh3 de la API v3 de lado del cliente][gh3] -* [Programa de seguridad de GitHub.js al rededor de la API de GitHub][github] -* [Biblioteca de CoffeeScript basada en promesas para el buscador o para NodeJS][github-client] - -### Julia - -* [GitHub.jl][github.jl] - -### OCaml - -* [ocaml-github][ocaml-github] - -### Perl - -* [Pithub][pithub-github] ([CPAN][pithub-cpan]) -* [Net::GitHub][net-github-github] ([CPAN][net-github-cpan]) - -### PHP - -* [GitHub PHP Client][github-php-client] -* [PHP GitHub API][php-github-api] -* [GitHub API][github-api] -* [Paquete de Joomla! Package][joomla] -* [Extensión de Github Nette][kdyby-github] -* [GitHub API Easy Access][milo-github-api] -* [Puente de GitHub para Laravel][github-laravel] -* [Programa de seguridad PHP5.6|PHP7 para Cliente & Webhook][flexyproject-githubapi] - -### Python - -* [PyGithub][jacquev6_pygithub] -* [libsaas][libsaas] -* [github3.py][github3py] -* [sanction][sanction] -* [agithub][agithub] -* [octohub][octohub] -* [Github-Flask][github-flask] -* [torngithub][torngithub] - -### Ruby - -* [Gema de la API de GitHub][ghapi] -* [Ghee][ghee] - -### Scala - -* [Hubcat][hubcat] -* [Github4s][github4s] - -### Shell - -* [ok.sh][ok.sh] - -[tentacles]: https://github.com/Raynes/tentacles - -[github.dart]: https://github.com/DirectMyFile/github.dart - -[gh.el]: https://github.com/sigma/gh.el - -[octo-erl]: https://github.com/sdepold/octo.erl - -[go-github]: https://github.com/google/go-github - -[haskell-github]: https://github.com/fpco/GitHub - -[octonode]: https://github.com/pksunkara/octonode -[gh3]: https://github.com/k33g/gh3 -[github]: https://github.com/michael/github -[github-client]: https://github.com/philschatz/github-client - -[github.jl]: https://github.com/WestleyArgentum/GitHub.jl - -[ocaml-github]: https://github.com/mirage/ocaml-github - -[net-github-github]: https://github.com/fayland/perl-net-github -[net-github-cpan]: https://metacpan.org/pod/Net::GitHub -[pithub-github]: https://github.com/plu/Pithub -[pithub-cpan]: http://metacpan.org/module/Pithub - -[github-php-client]: https://github.com/tan-tan-kanarek/github-php-client -[php-github-api]: https://github.com/KnpLabs/php-github-api -[github-api]: https://github.com/yiiext/github-api -[joomla]: https://github.com/joomla-framework/github-api -[kdyby-github]: https://github.com/kdyby/github -[milo-github-api]: https://github.com/milo/github-api -[github-laravel]: https://github.com/GrahamCampbell/Laravel-GitHub -[flexyproject-githubapi]: https://github.com/FlexyProject/GitHubAPI - -[jacquev6_pygithub]: https://github.com/PyGithub/PyGithub -[libsaas]: https://github.com/ducksboard/libsaas -[github3py]: https://github.com/sigmavirus24/github3.py -[sanction]: https://github.com/demianbrecht/sanction -[agithub]: https://github.com/jpaugh/agithub "Agnostic GitHub" -[octohub]: https://github.com/turnkeylinux/octohub -[github-flask]: http://github-flask.readthedocs.org -[torngithub]: https://github.com/jkeylu/torngithub - -[ghapi]: https://github.com/peter-murach/github -[ghee]: https://github.com/rauhryan/ghee - -[hubcat]: https://github.com/softprops/hubcat -[github4s]: https://github.com/47deg/github4s - -[ok.sh]: https://github.com/whiteinge/ok.sh diff --git a/translations/es-XL/content/rest/overview/media-types.md b/translations/es-XL/content/rest/overview/media-types.md deleted file mode 100644 index 6d5c90d8a1..0000000000 --- a/translations/es-XL/content/rest/overview/media-types.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -title: Tipós de medios -intro: Aprende sobre los tipos de medios para especificar el formato de los datos que quieres consumir. -redirect_from: - - /v3/media -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - -Los tipos de medios personalizados se utilizan en la API para permitir que los consumidores elijan el formato de los datos que quieren recibir. Esto se hace al agregar uno o más de los siguientes tipos al encabezado de `Accept` cuando haces una solicitud. Los tipos de medios son específicos para los recursos, lo que les permite cambiar independientemente y aceptar los formatos que otros usarios no aceptan. - -Todos los tipos de medios de {% data variables.product.product_name %} se ven así: - - application/vnd.github[.version].param[+json] - -Los tipos de medios más básicos que la API acepta son: - - application/json - application/vnd.github+json - -Ninguno de estos especifica una [versión][versions], así que siempre obtendrás la representación actual y predeterminada en JSON de los recursos. - -{% note %} - -**Importante:** La versión predeterminada de la API podría cambiar posteriormente. Si estás creando una aplicación y te importa la estabilidad de la API, asegúrate solicitar una versión específica en el encabezado `Accept` como se muestra en los siguientes ejemplos. - -{% endnote %} - -Puedes especificar una versión así: - - application/vnd.github.v3+json - -Si estás especificando una propiedad (tal como full/raw/etc como se define más adelante), pon la versión antes de la propiedad: - - application/vnd.github.v3.raw+json - -Puedes verificar la versión actual a través de los encabezados de cada respuesta. Busca el encabezado `X-GitHub-Media-Type`: - -```shell -$ curl {% data variables.product.api_url_pre %}/users/technoweenie -I -> HTTP/1.1 200 OK -> X-GitHub-Media-Type: github.v3 - -$ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \ -$ -H "Accept: application/vnd.github.full+json" -> HTTP/1.1 200 OK -> X-GitHub-Media-Type: github.v3; param=full; format=json - -$ curl {% data variables.product.api_url_pre %}/users/technoweenie -I \ -$ -H "Accept: application/vnd.github.v3.full+json" -> HTTP/1.1 200 OK -> X-GitHub-Media-Type: github.v3; param=full; format=json -``` - -### Porpiedades del cuerpo del comentario - -El cuerpo de un comentario puede escribirse en el [Lenguaje Markdown Enriquecido de GitHub][gfm]. Los [informes de problemas](/v3/issues/), [comentarios de informes de problemas](/v3/issues/comments/), [comentarios de la solicitud de extracción](/v3/pulls/comments/), y las API de [los comentarios de un gist](/v3/gists/comments/) siempre aceptan los mismos tipos de medios: - -#### Sin procesar - - application/vnd.github.VERSION.raw+json - -Devuelve el cuerpo en markdown sin procesar. La respuesta incluirá a `body`. Esto es lo predeterminado si no pasas ningún tipo de medios específico. - -#### Texto - - application/vnd.github.VERSION.text+json - -Devuelve una presentación únicamente de texto para el cuerpo de markdown. La respuesta incluirá a `body_text`. - -#### HTML - - application/vnd.github.VERSION.html+json - -Duevuelve el HTML interpretado del markdown del cuerpo. La respuesta incluirá a `body_html`. - -#### Completo - - application/vnd.github.VERSION.full+json - -Devuelve las representaciones de HTML, texto y sin procesar. La respuesta incluirá a `body`, `body_text`, y `body_html`: - -### Propiedades de los blobs de Git - -Se permiten los siguientes tipos de medios cuando [obtengas un blob](/v3/git/blobs/#get-a-blob): - -#### JSON - - application/vnd.github.VERSION+json - application/json - -Devuelve una representación en JSON del blob con un `content` en forma de una secuencia cifrada de base64. Esto es lo predeterminado si no se pasa nada más. - -#### Sin procesar - - application/vnd.github.VERSION.raw - -Devuelve los datos del blob sin procesar. - -### Confirmaciones, comparación de la confirmación, y solicitudes de extracción - -La [API de confirmaciones](/v3/repos/commits/) y la [API de solicitudes de extracción](/v3/pulls/) son compatibles con los formatos de [diferencias][git-diff] y de [parchado][git-patch]: - -#### diferencia - - application/vnd.github.VERSION.diff - -#### parche - - application/vnd.github.VERSION.patch - -#### sha - - application/vnd.github.VERSION.sha - -### Contenidos del repositorio - -#### Sin procesar - - application/vnd.github.VERSION.raw - -Devuelve el contenido sin procesar de un archivo. Esto es lo predeterminado si no pasas ningún tipo de medios específico. - -#### HTML - - application/vnd.github.VERSION.html - -Para archivos de markup tales como Markdown o AsciiDoc, puedes recuperar la interpretación en HTML si utilizas el tipo de medios `.html`. Los lenguajes de Markup se interpretan en HTML utilizando nuestra [biblioteca de Markup](https://github.com/github/markup) de código abierto. - -### Gists - -#### Sin procesar - - application/vnd.github.VERSION.raw - -Devuelve el contenido sin procesar de un gist. Esto es lo predeterminado si no pasas ningún tipo de medios específico. - -#### base64 - - application/vnd.github.VERSION.base64 - -El contenido del gist se cifra en base64 antes de que se envíe. Esto puede serte útil si tu gist contiene cualquier secuencia inválida en UTF-8. - -[gfm]: http://github.github.com/github-flavored-markdown/ -[git-diff]: http://git-scm.com/docs/git-diff -[git-patch]: http://git-scm.com/docs/git-format-patch -[versions]: /v3/versions diff --git a/translations/es-XL/content/rest/overview/other-authentication-methods.md b/translations/es-XL/content/rest/overview/other-authentication-methods.md deleted file mode 100644 index 73860c050c..0000000000 --- a/translations/es-XL/content/rest/overview/other-authentication-methods.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: Otros métodos de autenticación -intro: Puedes utilizar la autenticación básica para hacer pruebas en un ambiente diferente al productivo. -redirect_from: - - /v3/auth -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -Cuando la API proporciona varios métodos de autenticación, te recomendamos fuertemente utilizar [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) para las aplicaciones productivas. Los otros métodos que se proporcionan tienen la intención de que se utilicen para scripts o para pruebas (por ejemplo, en los casos en donde utilizar todo el OAuth sería exagerado). Las aplicaciones de terceros que dependen de {% data variables.product.product_name %} para la autenticación no piden ni recolectan las credenciales de {% data variables.product.product_name %}. En vez de esto, deben utilizar el [flujo web de OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). - -### Autenticación Básica - -La API es compatible con la autenticación básica de acuerdo a lo que se define en el [RFC2617](http://www.ietf.org/rfc/rfc2617.txt) con algunas diferencias menores. La diferencia principal es que el RFC requiere de solicitudes sin autenticar para que se le den respuestas `401 Unauthorized`. En muchos lugares, esto divulgaría la existencia de los datos de los usuarios. En cambio, la API de {% data variables.product.product_name %} responde con un `404 Not Found`. Esto puede causar problemas para las bibliotecas de HTTP que asumen una respuesta de `401 Unauthorized`. La solución es construir manualmente el encabezado de `Authorization`. - -#### A través de OAuth y los tokens de acceso personal - -Te recomendamos utilizar tokens de OAuth para autenticarte en la API de GitHub. Los tokens de OAuth incluyen a los [tokens de acceso personal][personal-access-tokens] y habilitan al usuario para revocar el acceso en cualquier momento. - -```shell -$ curl -u username:token {% data variables.product.api_url_pre %}/user -``` - -Este acercamiento es útil si tus herramientas solo son compatibles con la Autenticación Básica pero quieres sacar ventaja de las características de seguridad de los tokens de acceso de OAuth. - -#### A través de nombre de usuario y contraseña - -{% data reusables.apps.deprecating_password_auth %} - -Para utilizar la autenticación básica con la API de {% data variables.product.product_name %}, simplemente envía el nombre de usuario y contraseña asociados con la cuenta. - -Por ejemplo, si estás accediendo a la API a través de [cURL][curl], el siguiente comando te autenticaría si lo reemplazas al `` con tu nombre de usuario de {% data variables.product.product_name %}. (cURL te pedirá ingresar la contraseña.) - -```shell -$ curl -u username {% data variables.product.api_url_pre %}/user -``` -Si habilitaste la autenticación de dos factores, asegúrate de que entiendes como [trabajar con ella](/v3/auth/#working-with-two-factor-authentication). - -{% if currentVersion == "free-pro-team@latest" %} -#### Autenticarse con el SSO de SAML - -{% note %} - -**Nota:** Las integraciones y las aplicaciones de OAuth que generan tokens en nombre de otros se autorizan automáticamente. - -{% endnote %} - -Si estás usando la API para acceder a una organización que requiere el [SSO de SAML][saml-sso] para la autenticación, necesitarás crear un token de acceso personal (PAT) y [autorizarlo][allowlist] para esa organización. Visita la URL especificada en `X-GitHub-SSO` para autorizar el token para la organización. - -```shell -$ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test - -> X-GitHub-SSO: required; url=https://github.com/orgs/octodocs-test/sso?authorization_request=AZSCKtL4U8yX1H3sCQIVnVgmjmon5fWxks5YrqhJgah0b2tlbl9pZM4EuMz4 -{ - "message": "Resource protected by organization SAML enforcement. You must grant your personal token access to this organization.", - "documentation_url": "https://docs.github.com" -} -``` - -Cuando solicites datos que pudieran venir de organizaciones múltiples (por ejemplo, [solicitar la lista de informes de problemas que creó el usuario][user-issues]), el encabezado `X-GitHub-SSO` indica qué organizaciones te solicitarán autorizar tu token de acceso personal: - -```shell -$ curl -v -H "Authorization: token TOKEN" {% data variables.product.api_url_pre %}/user/issues - -> X-GitHub-SSO: partial-results; organizations=21955855,20582480 -``` - -El valor `organizations` es una lista separada por comas de las ID de organización para aquellas que requieren autorización de tu token de acceso personal. -{% endif %} - -### Trabajar con la autenticación de dos factores - -{% data reusables.apps.deprecating_password_auth %} - -Cuando habilitas la autenticación de dos factores, [La Autenticación Básica](#basic-authentication) para la _mayoría_de las terminales en la API de REST necesita que utilices un token de acceso personal o un token de OAuth en vez de tu nombre de usuario o contraseña. - -Puedes generar un token de acceso personal nuevo {% if currentVersion == "free-pro-team@latest" %}con los [ajustes de desarrollador de {% data variables.product.product_name %}](https://github.com/settings/tokens/new){% endif %} o utilizar la terminal "[Crear una autorización nueva][create-access]" en la API de autorizaciones de OAuth para generar un nuevo token de OAuth. Para obtener más información, consulta la sección"[Crear un token de acceso personal para la línea de comandos](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Entonces utilizarías estos tokens para [autenticarte utilizando un token de OAuth][oauth-auth] con la API de GitHub. La única vez que necesitas autenticarte con tu usuario y contraseña es cuando creas tu token de OAuth o cuando utilizas la API de autorizaciones de OAuth. - -#### Utilizar la API de Autorizaciones de OAuth con autenticación de dos factores - -Cuando haces llamadas a la API de Autorizaciones de OAuth, la Autenticación Básica requiere que utilces una contraseña de única vez (OTP) así como tu nombre de usuario y contraseña en vez de utilizar tokens. Cuando intentas autenticarte con la API de Autorizaciones de OAuth, el servidor te responderá con un `401 Unauthorized` y con uno de estos encabezados para decirte que necesitas un código de autenticación de dos factores: - -`X-GitHub-OTP: required; SMS` or `X-GitHub-OTP: required; app`. - -Este encabezado te dice cómo tu cuenta recibe sus códigos de autenticación de dos factores. Dependiendo de cómo configures tu cuenta, podrías recibir tus códigos de OTP por SMS o utilizarías una aplicación tal como Google Autenticator o como 1Password. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". Passa la OTP en el encabezado: - -```shell -$ curl --request POST \ - --url https://api.github.com/authorizations \ - --header 'authorization: Basic PASSWORD' \ - --header 'content-type: application/json' \ - --header 'x-github-otp: OTP' \ - --data '{"scopes": ["public_repo"], "note": "test"}' -``` - -[create-access]: /v3/oauth_authorizations/#create-a-new-authorization -[curl]: http://curl.haxx.se/ -[oauth-auth]: /v3/#authentication -[personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line -[saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on -[allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on -[user-issues]: /v3/issues/#list-issues-assigned-to-the-authenticated-user diff --git a/translations/es-XL/content/rest/overview/resources-in-the-rest-api.md b/translations/es-XL/content/rest/overview/resources-in-the-rest-api.md deleted file mode 100644 index e43181a088..0000000000 --- a/translations/es-XL/content/rest/overview/resources-in-the-rest-api.md +++ /dev/null @@ -1,619 +0,0 @@ ---- -title: Recursos en la API de REST -intro: 'Aprende como navegar en los recursos que proporciona la API de {% data variables.product.prodname_dotcom %}.' -redirect_from: - - /rest/initialize-the-repo/ -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - -Esto describe los recursos que conforman la API de REST oficial de {% data variables.product.product_name %}. Si tienes cualquier tipo de problema o solicitud, por favor contacta a {% data variables.contact.contact_support %}. - - -### Versión actual - -Predeterminadamente, todas las solicitudes a `{% data variables.product.api_url_code %}` reciben la [versión](/v3/versions)**v3** de la API de REST. Te alentamos a [solicitar explícitamente esta versión a través del encabezado `Aceptar`](/v3/media/#request-specific-version). - - Accept: application/vnd.github.v3+json - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} - -Para obtener información acerca de la API de GraphQL de GitHub, consulta la [documentación de la V4](/v4). Para obtener más información acerca de migrarse a GraphQL, consulta la sección "[Migrarse desde REST](/v4/guides/migrating-from-rest/)". - -{% endif %} - -### Modelo - -{% if currentVersion == "free-pro-team@latest" %}Todos los accesos de las API son através de HTTPS, y se accede a{% else %}La API{% endif %} desde `{% data variables.product.api_url_code %}`. Todos los datos se -envían y reciben como JSON. - -```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat/orgs - -> HTTP/1.1 200 OK -> Server: nginx -> Date: Fri, 12 Oct 2012 23:33:14 GMT -> Content-Type: application/json; charset=utf-8 -> Connection: keep-alive -> ETag: "a00049ba79152d03380c34652f2cb612" -> X-GitHub-Media-Type: github.v3 -> X-RateLimit-Limit: 5000 -> X-RateLimit-Remaining: 4987 -> X-RateLimit-Reset: 1350085394{% if currentVersion != "free-pro-team@latest" %} -> X-GitHub-Enterprise-Version: {{ currentVersion }}.0{% endif %} -> Content-Length: 5 -> Cache-Control: max-age=0, private, must-revalidate -> X-Content-Type-Options: nosniff -``` - -Los campos en blanco se incluyen como `null` en vez de omitirse. - -Todas las marcas de tiempo se regresan en formato ISO 8601: - - AAAA-MM-DDTHH:MM:SSZ - -Para obtener más información acerca de las zonas horarias en las marcas de tiempo, consulta [esta sección](#timezones). - -#### Representaciones de resumen - -Cuando recuperas una lista de recursos, la respuesta incluye un _subconjunto_ de los atributos para ese recurso. Esta es la representación "resumen" del recurso. (Algunos atributos son caros en términos de cómputo para que la API los proporcione. Por razones de rendimiento, la representación de resumen excluye esos atributos. Para obtener estos atributos, recupera la representación "detallada"). - -**Ejemplo**: Cuando obtienes una lista de repositorios, obtienes la representación de resumen de cada uno de ellos. Aquí, recuperamos la lista de repositorios que pertenecen a la organización [octokit](https://github.com/octokit): - - GET /orgs/octokit/repos - -#### Representaciones detalladas - -Cuando recuperas un recurso individual, la respuesta incluye habitualmente _todos_ los atributos para ese recurso. Esta es la representación "detallada" del recurso. (Nota que la autorización algunas veces influencia la cantidad de detalles que se incluyen en la representación). - -**Ejemplo**: Cuando obtienes un repositorio individual, obtienes la representación detallada del repositorio. Aquí, recuperamos el repositorio [octokit/octokit.rb](https://github.com/octokit/octokit.rb): - - GET /repos/octokit/octokit.rb - -La documentación proporciona un ejemplo de respuesta para cada método de la API. La respuesta de ejemplo ilustra todos los atributos que se regresan con ese método. - -### Autenticación - -Hay dos maneras de autenticarse a través de la API v3 de {% data variables.product.product_name %}. Las solicitudes que requieren autenticación regresarán `404 Not Found`, en vez de `403 Forbidden`, en algunos lugares. Esto es para prevenir la fuga accidental de repositorios privados para usuarios no autorizados. - -#### Autenticación básica - -```shell -$ curl -u "username" {% data variables.product.api_url_pre %} -``` - -#### Token de OAuth (enviado en un encabezado) - -```shell -$ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %} -``` - -{% note %} - -Nota: GitHub recomienda enviar los tokens de OAuth utilizando el encabezado de autorización. - -{% endnote %} - -Lee [más acerca de OAuth2](/apps/building-oauth-apps/). Nota que los tokens de OAuth2 pueden adquirirse utilizando el [flujo de la aplicación web](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para las aplicaciones productivas. - -#### Llave/secreto de OAuth2 - -{% data reusables.apps.deprecating_auth_with_query_parameters %} - -```shell -curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos' -``` - -El utilizar tu `client_id` y `client_secret` _no_ te autentica como un usuario, únicamente identifica tu aplicación de OAuth para incrementar tu límite de tasa. Los permisos se otorgan únicamente a usuarios, no a aplicaciones, y úicamente obtendrás datos que un usuario no autenticado vería. Es por esto que deberías utilizar únicamente la llave/secreto de OAuth2 en escenarios de servidor a servidor. No compartas el secreto de cliente de tu aplicación de OAuth con tus usuarios. - -{% if currentVersion != "free-pro-team@latest" %} -No podrás autenticarte utilizndo tu llave y secreto de OAuth2 si estás en modo privado, y el intentarlo regresará el mensaje `401 Unauthorized`. For more information, see "[Enabling private mode](/enterprise/admin/installation/enabling-private-mode)". -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} - -Lee [más acerca de limitar la tasa de no autenticación](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). - -{% endif %} - -#### Límite de ingresos fallidos - -Autenticarse con credenciales inválidas regresará el mensaje `401 Unauthorized`: - -```shell -$ curl -i {% data variables.product.api_url_pre %} -u foo:bar -> HTTP/1.1 401 Unauthorized - -> { -> "message": "Bad credentials", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" -> } -``` - -Después de detectar varias solicitudes con credenciales inválidas dentro de un periodo de tiempo corto, la API rechazará temporalmente todos los intentos de autenticación para el usuario en cuestión (incluyendo aquellos con credenciales válidas) con el mensaje `403 Forbidden`: - -```shell -$ curl -i {% data variables.product.api_url_pre %} -u valid_username:valid_password -> HTTP/1.1 403 Forbidden - -> { -> "message": "Maximum number of login attempts exceeded. Please try again later.", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3" -> } -``` - -### Parámetros - -Muchos métodos de la API toman parámetros opcionales. Para las solicitudes de tipo `GET`, cualquier parámetro que no se haya especificado como un segmento en la ruta puede pasarse como un parámetro de secuencia de consulta HTTP: - -```shell -$ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed" -``` - -En este ejemplo, los valores 'vmg' and 'redcarpet' se proporcionan para los parámetros `:owner` y `:repo` en la ruta mientras que se pasa a `:state` en la secuencia de la consulta. - -Para las solicitudes de tipo `POST`, `PATCH`, `PUT`, and `DELETE`, los parámetros que no se incluyen en la URL deben codificarse como JSON con un Content-Type de 'application/json': - -```shell -$ curl -i -u username -d '{"scopes":["public_repo"]}' {% data variables.product.api_url_pre %}/authorizations -``` - -### Terminal raíz - -Puedes emitir una solicitud de tipo `GET` a la terminal raíz para obtener todas las categorías de la terminal que son compatibles con la API de REST: - -```shell -$ curl {% if currentVersion != "free-pro-team@latest" %}-u username:password {% endif %}{% data variables.product.api_url_pre %} -``` - -{% if currentVersion != "free-pro-team@latest" %} - -{% note %} - -**Nota:** Para {% data variables.product.prodname_ghe_server %}, [como para todas las otras terminales](/v3/enterprise-admin/#endpoint-urls), necesitaras pasar tu nombre de usuario y contraseña. - -{% endnote %} - -{% endif %} - -### IDs de nodo globales de GraphQL - -Consulta la guía sobre cómo "[Utilizar las ID de Nodo Global](/v4/guides/using-global-node-ids)" para obtener información detallada sobre cómo encontrar las `node_id` a través de la API de REST y utilizarlas en las operaciones de GraphQL. - -### Errores de cliente - -Existen tres posibles tipos de errores de cliente en los llamados a la API que reciben cuerpos de solicitud: - -1. Enviar un JSON inválido dará como resultado una respuesta de tipo `400 Bad Request`. - - HTTP/1.1 400 Bad Request - Content-Length: 35 - - {"message":"Problems parsing JSON"} - -2. Enviar el tipo incorrecto de valores de JSON dará como resultado una respuesta de tipo `400 Bad -Request`. - - HTTP/1.1 400 Bad Request - Content-Length: 40 - - {"message":"Body should be a JSON object"} - -3. Enviar campos inválidos dará como resultado una respuesta de tipo `422 Unprocessable Entity`. - - HTTP/1.1 422 Unprocessable Entity - Content-Length: 149 - - { - "message": "Validation Failed", - "errors": [ - { - "resource": "Issue", - "field": "title", - "code": "missing_field" - } - ] - } - -Todos los objetos de error tienen propiedades de campo y de recurso para que tu cliente pueda ubicar el problema. También hay un código de error para que sepas qué es lo que está mal con el campo. Estos son los posibles códigos de error de validación: - -| Nombre del código de error | Descripción | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | -| `missing` | Un recurso no existe. | -| `missing_field` | No se ha configurado un campo requerido en un recurso. | -| `no válida` | The formatting of a field is invalid. Review the documentation for the for more specific information. | -| `already_exists` | Otro recurso tiene el mismo valor que este campo. This can happen in resources that must have some unique key (such as label names). | -| `unprocessable` | Las entradas proporcionadas son inválidas. | - -Los recursos también podría enviar errores de validación personalizados (en donde `code` sea `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error. - -### Redireccionamientos HTTP - -La API v3 utiliza redireccionamientos HTTP cuando sea adecuado. Los clientes deberán asumir que cualquier solicitud podría resultar en un redireccionamiento. Recibir un redireccionamiento HTTP *no* es un error y los clientes deberán seguirlo. Las respuestas de redireccionamiento tendrán un campo de encabezado de tipo `Location` que contendrá el URI del recurso al cual el cliente deberá repetir la solicitud. - -| Status Code | Descripción | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `301` | Redirección permanente. El URI que utilizaste para hacer la solicitud se reemplazó con aquél especificado en el campo de encabezado `Location`. Ésta y todas las solicitudes futuras a este recurso se deberán dirigir al nuevo URI. | -| `302`, `307` | Redireccion temporal. La solicitud deberá repetirse literalmente al URI especificado en el campo de encabezado `Location`, pero los clientes deberán seguir utilizando el URI original para solicitudes futuras. | - -Podrían utilizarse otros códigos de estado de redirección de acuerdo con la especificación HTTP 1.1. - -### Verbos HTTP - -Cuando sea posible, la API v3 intentará utilizar los verbos HTTP adecuados para cada acción. - -| Verbo | Descripción | -| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `HEAD` | Puede emitirse contra cualquier recurso para obtener solo la información del encabezado HTTP. | -| `GET` | Se utiliza para recuperar recursos. | -| `POST` | Se utiliza para crear recursos. | -| `PATCH` | Used for updating resources with partial JSON data. Por ejemplo, un recurso de emisión tiene los atributos `title` y `body`. Una solicitud de PATCH podría aceptar uno o más de los atributos para actualizar el recurso. PATCH is a relatively new and uncommon HTTP verb, so resource endpoints also accept `POST` requests. | -| `PUT` | Se utiliza para reemplazar recursos o colecciones. Para las solicitudes de `PUT` sin el atributo `body`, asegúrate de configurar el encabezado `Content-Length` en cero. | -| `DELETE` | Se utiliza para borrar recursos. | - -### Hypermedia - -Todos los recursos pueden tener una o más propiedades de `*_url` que los enlacen con otros recursos. Estos pretenden proporcionar las URL explícitas para que los clientes adecuados de la API no tengan que construir las URL por ellos mismos. Se recomienda ampliamente que los clientes de la API los utilicen. El hacerlo facilitará a los desarrolladores el realizar mejoras futuras a la API. Se espera que todas las URL sean plantillas de URI [RFC 6570][rfc] adecuadas. - -Puedes entonces expandir estas plantillas utilizando algo como la gema [uri_template][uri]: - - >> tmpl = URITemplate.new('/notifications{?since,all,participating}') - >> tmpl.expand - => "/notifications" - - >> tmpl.expand :all => 1 - => "/notifications?all=1" - - >> tmpl.expand :all => 1, :participating => 1 - => "/notifications?all=1&participating=1" - -### Paginación - -Las solicitudes que recuperan varios elementos se paginarán a 30 elementos predeterminadamente. Puedes especificar más páginas con el parámetro `?page`. Para algunos recursos, también puedes configurar un tamaño de página personalizado de hasta 100 elementos con el parámetro `?per_page`. Nota que, por razones técnicas, no todas las terminales respetan el parámetro `?per_page`, consulta la sección de [eventos](/v3/activity/events/) por ejemplo. - -```shell -$ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' -``` - -Nota que la enumeración de página es basada en 1 y que el omitir el parámetro `?page` regresará la primera página. - -For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. - -#### Encabezado de enlace - -{% note %} - -**Nota:** Es importante formar llamados con valores de encabezado de enlace en vez de construir tus propias URL. - -{% endnote %} - -El [Encabezado de enlace](http://tools.ietf.org/html/rfc5988) incluye información de paginación: - - 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" - -_Este ejemplo incluye un salto de línea para legibilidad._ - -Este encabezado de respuesta de `Link` contiene uno o más enlaces de relación de [Hypermedia](/v3/#hypermedia), algunos de los cuales podrían requerir expansión como [plantillas URI](http://tools.ietf.org/html/rfc6570). - -Los valores de `rel` posibles son: - -| Nombre | Descripción | -| ----------- | -------------------------------------------------------------------------- | -| `siguiente` | La relación del enlace para la página subsecuente inmediata de resultados. | -| `last` | La relación del enlace para la última página de resultados. | -| `first` | The link relation for the first page of results. | -| `prev` | La relación del enlace para la página previa inmediata de resultados. | - -### Limitación de tasas - -Para las solicitudes de la API que utilizan Autenticación Básica u OAuth, puedes hacer hasta 5,000 solicitudes por hora. Las solicitudes autenticadas se asocian con el usuario autenticado, sin importar si se utilizó [Autenticación Básica](#basic-authentication) o [un token OAuth](#oauth2-token-sent-in-a-header). Esto significa que todas las aplicaciones de OAuth que autorice un usuario compartirán la misma cuota de 5,000 solicitudes por hora cuando se autentiquen con tokens diferentes que pertenezcan al mismo usuario. - -{% if currentVersion == "free-pro-team@latest" %} - -Para los usuarios que pertenezcan a una cuenta de {% data variables.product.prodname_ghe_cloud %}, las solicitudes que se hacen utilizando un token de OAuth para los recursos que pertenecen a la misma cuenta de {% data variables.product.prodname_ghe_cloud %} tienen un límite incrementado de 15,000 solicitudes por hora. - -{% endif %} - -Para las solicitudes no autenticadas, el límite de tasa permite hasta 60 solicitudes por hora. Las solicitudes no autenticadas se asocian con la dirección IP que las origina, y no con el usuario que realiza la solicitud. - -{% data reusables.enterprise.rate_limit %} - -Nota que [la API de búsqueda tiene reglas personalizadas de límite de tasa](/v3/search/#rate-limit). - -Los encabezados HTTP recuperados para cualquier solicitud de la API muestran tu estado actual de límite de tasa: - -```shell -$ curl -i {% data variables.product.api_url_pre %}/users/octocat -> HTTP/1.1 200 OK -> Date: Mon, 01 Jul 2013 17:27:06 GMT -> X-RateLimit-Limit: 60 -> X-RateLimit-Remaining: 56 -> X-RateLimit-Reset: 1372700873 -``` - -| Nombre del Encabezado | Descripción | -| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-RateLimit-Limit` | La cantidad máxima de solicitudes que puedes hacer por hora. | -| `X-RateLimit-Remaining` | La cantidad de solicitudes que quedan en la ventana de límite de tasa actual. | -| `X-RateLimit-Reset` | La hora en la que se restablecerá la ventana de límite de tasa actual en [segundos de tiempo satelital UTC](http://en.wikipedia.org/wiki/Unix_time). | - -Si necesitas ver la hora en un formato diferente, cualquier lenguaje de programación moderno puede ayudarte con esta tarea. Por ejemplo, si abres la consola en tu buscador web, puedes obtener fácilmente el tiempo de restablecimiento como un objeto de Tiempo de JavaScript. - -``` javascript -new Date(1372700873 * 1000) -// => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT) -``` - -Si excedes el límite de tasa, se regresará una respuesta de error: - -```shell -> HTTP/1.1 403 Forbidden -> Date: Tue, 20 Aug 2013 14:50:41 GMT -> X-RateLimit-Limit: 60 -> X-RateLimit-Remaining: 0 -> X-RateLimit-Reset: 1377013266 - -> { -> "message": "API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)", -> "documentation_url": "{% data variables.product.doc_url_pre %}/v3/#rate-limiting" -> } -``` - -Puedes [revisar tu estado de límite de tasa](/v3/rate_limit) sin incurrir en una consulta de la API. - -#### Incrementar el límite de tasa de no autenticados para las aplicaciones de OAuth - -Si tu aplicación de OAuth necesita hacer llamados no autenticados con un límite de tasa más alto, puedes pasar la ID de cliente y secreto de tu app ante la ruta de la terminal. - -```shell -$ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos -> HTTP/1.1 200 OK -> Date: Mon, 01 Jul 2013 17:27:06 GMT -> X-RateLimit-Limit: 5000 -> X-RateLimit-Remaining: 4966 -> X-RateLimit-Reset: 1372700873 -``` - -{% note %} - -**Nota:** Jamás compartas tu secreto de cliente con nadie ni lo incluyas en el código de cara al cliente del buscador. Utiliza únicamente el método que se muestra aquí para las llamadas de servidor a servidor. - -{% endnote %} - -#### Quedarse dentro del límite de tasa - -Si excedes tu límite de tasa utilizando Autenticación Básica u OAuth, es probable que puedas arreglar el problema si guardas en caché las respuestas de la API y utilizas [solicitudes condicionales](#conditional-requests). - -#### Abusar del límite de tasa - -Para prorpocionar un servicio de calidad en {% data variables.product.product_name %}, los límites de tasa adicionales podrían aplicar a algunas acciones cuando se utiliza la API. Por ejemplo, utilizar la API para crear contenido rápidamente, encuestar agresivamente en vez de utilizar webhooks, hacer solicitudes múltiples concurrentes, o solicitar repetidamente datos que son caros a nivel computacional, podría dar como resultado un abuso de tasa. - -El abuso de límite de tasa no pretende interferir con el uso legítimo de la API. Tus límites de tasa habituales deben ser el único límite en el cual te enfoques. Para garantizar que estás actuando como un buen ciudadano de la API, revisa nuestros [lineamientos de mejores prácticas](/guides/best-practices-for-integrators/). - -Si tu aplicación activa este límite de tasa, recibirás una respuesta informativa: - -```shell -> HTTP/1.1 403 Forbidden -> Content-Type: application/json; charset=utf-8 -> 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 %}/v3/#abuse-rate-limits" -> } -``` - -{% if currentVersion == "free-pro-team@latest" %} - -### Se requiere un agente de usuario - -Todas las solicitudes a la API DEBEN incluir un encabezado de `User-Agent` válido. Las solicitudes sin encabezado de `User-Agent` se rechazarán. Te solicitamos que utilices tu nombre de usuario de {% data variables.product.product_name %}, o el nombre de tu aplicación, para el valor del encabezado de `User-Agent`. Esto nos permite contactarte en caso de que haya algún problema. - -Aquí hay un ejemplo: - -```shell -User-Agent: Awesome-Octocat-App -``` - -cURL envía un encabezado de `User-Agent` válido predeterminadamente. Si proporcionas un encabezado de `User-Agent` inválido a través de cURL (o a través de un cliente alterno), recibirás una respuesta de `403 Forbidden`: - -```shell -$ curl -iH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta -> HTTP/1.0 403 Forbidden -> Connection: close -> Content-Type: text/html - -> Request forbidden by administrative rules. -> Please make sure your request has a User-Agent header. -> Check for other possible causes. -``` - -{% endif %} - -### Solicitudes condicionales - -La mayoría de las respuestas regresan un encabezado de `ETag`. Muchas de las respuestas también regresan un encabezado de `Last-Modified`. Puedes utilizar los valores de estos encabezados para hacer solicitudes subsecuentes a estos recursos utilizando los encabezados `If-None-Match` y `If-Modified-Since`, respectivamente. Si el recurso no ha cambiado, el servidor regresará un `304 Not Modified`. - -{% if currentVersion == "free-pro-team@latest" %} - -{% tip %} - -**Nota**: Hacer una solicitud condicional y recibir una respuesta de tipo 304 no cuenta contra tu [Límite de Tasa](#rate-limiting), así que te alentamos a utilizarlo cuando sea posible. - -{% endtip %} - -{% endif %} - -```shell -$ curl -i {% data variables.product.api_url_pre %}/user -> HTTP/1.1 200 OK -> Cache-Control: private, max-age=60 -> ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" -> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT -> Vary: Accept, Authorization, Cookie -> X-RateLimit-Limit: 5000 -> X-RateLimit-Remaining: 4996 -> X-RateLimit-Reset: 1372700873 - -$ curl -i {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"' -> HTTP/1.1 304 Not Modified -> Cache-Control: private, max-age=60 -> ETag: "644b5b0155e6404a9cc4bd9d8b1ae730" -> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT -> Vary: Accept, Authorization, Cookie -> X-RateLimit-Limit: 5000 -> X-RateLimit-Remaining: 4996 -> X-RateLimit-Reset: 1372700873 - -$ curl -i {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT" -> HTTP/1.1 304 Not Modified -> Cache-Control: private, max-age=60 -> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT -> Vary: Accept, Authorization, Cookie -> X-RateLimit-Limit: 5000 -> X-RateLimit-Remaining: 4996 -> X-RateLimit-Reset: 1372700873 -``` - -### Intercambio de recursos de origen cruzado - -La API es compatible con el Intercambio de Recursos de Origen Cruzado (CORS, por sus siglas en inglés) para las solicitudes de AJAX de cualquier origen. Puedes leer la [Recomendación del W3C sobre CORS](http://www.w3.org/TR/cors/), o [esta introducción](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) de la Guía de Seguridad de HTML 5. - -Aquí hay una solicitud de ejemplo que se envió desde una consulta de buscador `http://example.com`: - -```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -HTTP/1.1 302 Found -Access-Control-Allow-Origin: * -Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval -``` - -Así se ve una solicitud de prevuelo de CORS: - -```shell -$ curl -i {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS -HTTP/1.1 204 No Content -Access-Control-Allow-Origin: * -Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With -Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE -Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval -Access-Control-Max-Age: 86400 -``` - -### Rellamados de JSON-P - -Puedes enviar un parámetro de `?callback` a cualquier llamado de GET para envolver los resultados en una función de JSON. Esto se utiliza típicamente cuando los buscadores quieren insertar contenido de {% data variables.product.product_name %} en las páginas web evitando los problemas de dominio cruzado. La respuesta incluye la misma salida de datos que la API común, mas la información relevante del Encabezado HTTP. - -```shell -$ curl {% data variables.product.api_url_pre %}?callback=foo - -> /**/foo({ -> "meta": { -> "status": 200, -> "X-RateLimit-Limit": "5000", -> "X-RateLimit-Remaining": "4966", -> "X-RateLimit-Reset": "1372700873", -> "Link": [ // pagination headers and other links -> ["{% data variables.product.api_url_pre %}?page=2", {"rel": "next"}] -> ] -> }, -> "data": { -> // the data -> } -> }) -``` - -Puedes escribir un agente de JavaScript para procesar la rellamada. Aquí hay un ejemplo minimalista que puedes probar: - - - - - - - -

    Open up your browser's console.

    - - - -Todos los encabezados consisten en el mismo valor de secuencia que los encabezados HTTP con una excepción notoria: El Enlace. Los encabezados de enlace se pre-analizan y se presentan como una matriz de tuplas de `[url, options]`. - -Un enlace que se ve así: - - Link: ; rel="next", ; rel="foo"; bar="baz" - -... se verá así en la salida de la rellamada: - -```json -{ - "Link": [ - [ - "url1", - { - "rel": "next" - } - ], - [ - "url2", - { - "rel": "foo", - "bar": "baz" - } - ] - ] -} -``` - -### Zonas horarias - -Algunas solicitudes que crean datos nuevos, tales como aquellas para crear una confirmación nueva, te permiten proporcionar información sobre la zona horaria cuando especificas o generas marcas de tiempo. Aplicamos las siguientes reglas, en orden de prioridad, para determinar la información de la zona horaria para los llamados a la API. - -* [Proporcionar explícitamente una marca de tiempo de tipo ISO 8601 con información de la zona horaria](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) -* [Utilizar el encabezado de `Time-Zone`](#using-the-time-zone-header) -* [Utilizar la última zona horaria conocida del usuario](#using-the-last-known-timezone-for-the-user) -* [Poner como defecto UTC en ausencia de otra información de zona horaria](#defaulting-to-utc-without-other-timezone-information) - -#### Proporcionar explícitamente una marca de tiempo de tipo ISO 8601 con información de la zona horaria - -Para las llamadas a la API que permitan que se especifique una marca de tiempo, utilizamos esa marca de tiempo exacta. Como ejemplo de esto, está la [API de Confirmaciones](/v3/git/commits). - -Estas marcas de tiempo se ven más o menos como `2014-02-27T15:05:06+01:00`. También, puedes ver [este ejemplo](/v3/git/commits/#example-input) como se pueden especificar las marcas de tiempo. - -#### Utilizar el encabezado de `Time-Zone` - -Es posible proporcionar un encabezado de `Time-Zone` que defina la zona horaria de acuerdo con la [lista de nombres de la base de datos Olson](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). - -```shell -$ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md -``` - -Esto significa que generamos una marca de tiempo para el momento en el se haga el llamado a tu API en la zona horaria que defina este encabezado. Por ejemplo, la [API de Contenidos](/v3/repos/contents/) genera una confirmación de git para cada adición o cambio y utiliza este tiempo actual como la marca de tiempo. Este encabezado determinará la zona horaria que se utiliza para generar la marca de tiempo actual. - -#### Utilizar la última zona horaria conocida del usuario - -Si no se especifica ningún encabezado de `Time-Zone` y haces una llamada autenticada a la API, utilizaremos esta última zona horaria para el usuario autenticado. La última zona horaria conocida se actualiza cuando sea que busques el sitio web de {% data variables.product.product_name %}. - -#### Poner como defecto UTC en ausencia de otra información de zona horaria - -Si los pasos anteriores no dan como resultado ninguna información, utilizaremos UTC como la zona horaria para crear la confirmación de git. - -[rfc]: http://tools.ietf.org/html/rfc6570 -[uri]: https://github.com/hannesg/uri_template - -[pagination-guide]: /guides/traversing-with-pagination diff --git a/translations/es-XL/content/rest/overview/troubleshooting.md b/translations/es-XL/content/rest/overview/troubleshooting.md deleted file mode 100644 index 8d7a71002c..0000000000 --- a/translations/es-XL/content/rest/overview/troubleshooting.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Solución de problemas -intro: Aprende cómo resolver los problemas más comunes que las personas pueden encontrar en la API de REST. -redirect_from: - - /v3/troubleshooting -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - - - -Si estás encontrando algunas situaciones extrañas en la API, aquí hay una lista de posibles soluciones a algunos de estos problemas que podrías estar experimentando. - -### ¿Por qué estoy obteniendo un error `404` en un repositorio que sí existe? - -Habitualmente, enviamos un error `404` cuando tu cliente no está autenticado adecuadamente. Puede que esperes ver un `403 Forbidden` en estos casos. Sin embargo, ya que no queremos proporcionar _ningun_ tipo de información acerca de los repositorios privados, en vez de esto, la API devuelve un `404`. - -Para solucionar los problemas, asegúrate de que [te estás autenticando correctamente](/guides/getting-started/), que [tu token de acceso de OAuth tenga los alcances requeridos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), y que las [restricciones de las aplicaciones de terceros][oap-guide] no estén bloqueando tu acceso. - -### ¿Por qué no veo todos mis resultados? - -La mayoría de las llamadas a la API que acceden a una lista de recursos (_por ejemplo_, usuarios, informes de problemas, _etc._) son compatibles con la paginación. Si estás haciendo solicitudes y recibes un conjunto de resultados incompleto, probablemente solo estás viendo la primera página. Necesitarás solicitar las páginas restantes para obtener más resultados. - -Es importante que *no* intentes adivinar el formato de la URL de paginación. No todas las llamadas a la API utilizan la misma estructura. En vez de esto, extrae la información de paginación del [Encabezado de Enlace](/v3/#pagination), el cual se envía en cada solicitud. - -[oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/es-XL/content/rest/reference/actions.md b/translations/es-XL/content/rest/reference/actions.md deleted file mode 100644 index d429847927..0000000000 --- a/translations/es-XL/content/rest/reference/actions.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -title: Acciones -product: '{% data reusables.gated-features.actions %}' -redirect_from: - - /v3/actions -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -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 %} en las {% data variables.product.prodname_github_app %} necesitan los mismos 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)". - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Artefactos - -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 %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'artifacts' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Secretos - -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_app %} 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. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Ejecutores autoalojados - -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)". - -La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_app %} debe contar con el permiso de `administration` para los repositorios o aquél de `organization_self_hosted_runners` para las organizaciones. Los usuarios autenticados deben tener acceso administrativo al repositorio o a la organización para utilizar esta API. - -Puedes administrar los ejecutores auto-programados 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#actions)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Grupos de ejecutores auto-hospedados - -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)". - -La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_app %} debe contar con el permiso de `administration` para los repositorios o aquél de `organization_self_hosted_runners` para las organizaciones. Los usuarios autenticados deben tener acceso administrativo al repositorio o a la organización para utilizar esta API. - -Puedes administrar los grupos de ejecutores auto-hospedados 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#actions)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'self-hosted-runner-groups' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Flujos de trabajo - -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 %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'workflows' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Jobs de los flujos de trabajo - -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 %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'workflow-jobs' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Ejecuciones de flujo de trabajo - -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 %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'workflow-runs' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/activity.md b/translations/es-XL/content/rest/reference/activity.md deleted file mode 100644 index 06fdc4772f..0000000000 --- a/translations/es-XL/content/rest/reference/activity.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -title: Actividad -redirect_from: - - /v3/activity -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Eventos - -La API de eventos es una API de solo lectura para los eventos de {% data variables.product.prodname_dotcom %}. Estos eventos alimentan a los diversos flujos de actividad en el sitio. - -La API de eventos puede devolver tipos diferentes de eventos que se activan por actividad en {% data variables.product.product_name %}. La API de eventos puede devolver tipos diferentes de eventos que se activan por actividad en {% data variables.product.product_name %}. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos, consulta la sección "[Tipos de evento en {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)". Para obtener más información, consulta la "[API de Eventos de Informes de Problemas](/rest/reference/issues#events)". - -Los eventos se optimizan para el sondeo con el encabezado "ETag". Si no se han desencadenado eventos nuevos, verás la respuesta "304 Sin Modificar", y tu límite de tasa actual permanecerá intacto. También hay un encabezado de "X-Poll-Interval" que especifica la frecuencia (en segundos) en la que se te permite hacer sondeos. Este tiempo podría incrementarse durante los periodos de carga fuerte en el servidor. Por favor obedece al encabezado. - -``` shell -$ curl -I {% data variables.product.api_url_pre %}/users/tater/events -> HTTP/1.1 200 OK -> X-Poll-Interval: 60 -> ETag: "a18c3bded88eb5dbb5c849a489412bf3" - -# The quotes around the ETag value are important -$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \ -$ -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"' -> HTTP/1.1 304 Not Modified -> X-Poll-Interval: 60 -``` - -Los eventos son compatibles con la paginación, sin embargo, la opción `per_page` no es compatible. El tamaño de página fijo es de 30 elementos. Se puede obtener hasta diez páginas para obtener un total de 300 eventos. Para obtener más información, consulta la sección "[Desplazarse con la paginación](/rest/guides/traversing-with-pagination)". - -Solo los eventos creados en los últimos 90 días se incluirán en las líneas de tiempo. Los eventos de más de 90 días de antigüedad no se incluirán (aún si la cantidad total de eventos en la línea de tiempo es de 300). - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Fuentes - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'feeds' %}{% include rest_operation %}{% endif %} -{% endfor %} - -### Ejemplo de obtención de un canal de Atom - -Para obtener un canal en formato de Atom, debes especificar el tipo `application/atom+xml` en el encabezado `Accept`. Por ejemplo, para obtener un canal de Atom para las asesorías de seguridad de GitHub: - - curl -H "Accept: application/atom+xml" https://github.com/security-advisories - -#### Respuesta - -```shell -HTTP/1.1 200 OK -``` - -```xml - - - tag:github.com,2008:/security-advisories - - GitHub Security Advisory Feed - - GitHub - - 2019-01-14T19:34:52Z - - tag:github.com,2008:GHSA-abcd-12ab-23cd - 2018-07-26T15:14:52Z - 2019-01-14T19:34:52Z - [GHSA-abcd-12ab-23cd] Moderate severity vulnerability that affects Octoapp - - - <p>Octoapp node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via <strong>proto</strong>, causing the addition or modification of an existing property that will exist on all objects.</p> - <p><strong>Affected Packages</strong></p> - - <dl> - <dt>Octoapp</dt> - <dd>Ecosystem: npm</dd> - <dd>Severity: moderate</dd> - <dd>Versions: &lt; 4.17.5</dd> - <dd>Fixed in: 4.17.5</dd> - </dl> - - <p><strong>References</strong></p> - - <ul> - <li>https://nvd.nist.gov/vuln/detail/CVE-2018-123</li> - </ul> - - - - -``` - -## Notificaciones - -Los usuarios reciben notificaciones para las conversaciones en los repositorios que observan, incluyendo: - -* Las de los informes de problemas y sus comentarios -* Las de las solicitudes de extracción en sus comentarios -* Las de los comentarios en cualquier confirmación - -También se envían notificaciones para las conversaciones en los repositorios sin observar cuando el usuario está involucrado, incluyendo: - -* **@menciones** -* Asignaciones de informes de problemas -* Confirmaciones que confirme o cree el usuario -* Cualquier debate en el que el usuario participe activamente - -Todas las llamadas de la API para notificaciones necesitan los alcances de la API para `notifications` o `repo`. El hacerlo te dará acceso de solo lectura a algunos contenidos de informes de problemas y de confirmaciones. Aún necesitarás el alcance de `repo` para acceder a los informes de problemas y a las confirmaciones desde sus respectivas terminales. - -Las notificaciones se devuelven como "hilos". Un hilo contiene información acerca del debate actual sobre un informe de problemas, solicitud de extracción o confirmación. - -Las notificaciones se optimizan para el sondeo con el encabezado `Last-Modified`. Si no hay notificaciones nuevas, verás una respuesta `304 Not Modified`, la cual dejará tu límite de tasa intacto. Hay un encabezado de `X-Poll-Interval` que especifica la frecuencia (en segundos) en la que se te permite hacer sondeos. Este tiempo podría incrementarse durante los periodos de carga fuerte en el servidor. Por favor obedece al encabezado. - -``` shell -# Add authentication to your requests -$ curl -I {% data variables.product.api_url_pre %}/notifications -HTTP/1.1 200 OK -Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT -X-Poll-Interval: 60 - -# Pass the Last-Modified header exactly -$ curl -I {% data variables.product.api_url_pre %}/notifications -$ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT" -> HTTP/1.1 304 Not Modified -> X-Poll-Interval: 60 -``` - -### Razones para obtener las notificaciones - -Cuando recuperas respuestas de la API de Notificaciones, cada carga útil tiene una clave que se titula `reason`. Estas corresponden a los eventos que activan una notificación. - -Hay una lista potencial de `reason` para recibir una notificación: - -| Nombre de la razón | Descripción | -| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `assign` | Se te asignó al informe de problemas. | -| `autor` | Creaste el hilo. | -| `comentario` | Comentaste en el hilo. | -| `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. | -| `review_requested` | Se te solicitó, o se solicitó a un equipo del cual eres miembro, revisar una solicitud de extracción.{% if currentVersion == "free-pro-team@latest" %} -| `security_alert` | {% data variables.product.prodname_dotcom %} descubrió una [vulnerabilidad de seguridad](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) en tu repositorio.{% endif %} -| `state_change` | Cambiaste el estado del hilo (por ejemplo, cerraste un informe de problemas o fusionaste una solicitud de extracción). | -| `subscribed` | Estás observando el repositorio. | -| `team_mention` | Estuviste en un equipo al que se mencionó. | - -Toma en cuenta que la `reason` se modificará conforme al hilo, y puede cambiar si esta `reason` es diferente en una notificación posterior. - -Por ejemplo, si eres el autor de un informe de problemas, las notificaciones subsecuentes de dicho informe tendrán una `reason` o un `author`. Si entonces se te **@menciona** en el mismo informe de problemas, las notificaciones que obtengas de ahí en adelante tendrán una `reason` o una `mention`. La `reason` se queda como una `mention`, sin importar si nunca se te menciona. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'notifications' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Marcar con una estrella - -El marcar a los repositorios con una estrella es una característica que permite a los usuarios marcar a los repositorios como favoritos. Las estrellas se muestran junto a los repositorios para denotar un nivel aproximado de interés. Las estrellas no tienen efecto alguno en las notificaciones o en los canales de actividad. - -### Marcar con estrella vs. Observar - -En agosto de 2012, [cambiamos la forma en la que funciona el observar repositorios](https://github.com/blog/1204-notifications-stars) en {% data variables.product.prodname_dotcom %}. Muchas aplicaciones de cliente de la API podrían estar utilizando las terminales de "observación" originales para acceder a estos datos. Ahora puedes comenzar a utilizar las terminales de "estrella" como sustitución (como se describe más adelante). Para obtener más información, consulta la [publicación de Cambio de la API de observaciones](https://developer.github.com/changes/2012-09-05-watcher-api/) y la "[API para Observar Repositorios](/rest/reference/activity#watching)". - -### Tipos de medio personalizados para marcar con estrella - -Hay un tipo de medios personalizado compatible para la API de REST para Marcar con estrella. Cuando utilizas este tipo de medios personalizado, recibirás una respuesta con la marca de tiempo `starred_at` que indica la hora en el que se creó la estrella. La respuesta también tiene una segunda propiedad que incluye el recurso que se devuelve cuando no se incluye el tipo de medios personalizado. La propiedad que contiene el recurso puede ser `user` o `repo`. - - application/vnd.github.v3.star+json - -Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'starring' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Observar - -Observar un repositorio registra al usuario para recibir notificaciones en debates nuevos, así como en los eventos de los canales de actividad del mismo. Para marcar a un repositorio como favorito de forma sencilla, consulta la sección "[Marcar repositorios con una estrella](/rest/reference/activity#starring)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'watching' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/apps.md b/translations/es-XL/content/rest/reference/apps.md deleted file mode 100644 index 24eff86e66..0000000000 --- a/translations/es-XL/content/rest/reference/apps.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: Aplicaciones -redirect_from: - - /v3/apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -La API de GitHub Apps te permite obtener información de alto nivel acerca de una GitHub App así como la información específica acerca de las instalaciones de la misma. Para conocer más sobre las GitHub Apps, consulta la sección "[Autenticarte como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)". - -{% data reusables.apps.general-apps-restrictions %} - -Esta página lista las terminales a las que puedes acceder mientras te autenticas como una GitHub App. Consulta la sección "[Autenticarse como una GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)" para conocer más. - -Cuando estás autenticado como una GitHub App, la API de GitHub Apps te habilita para obtener información de alto nivel sobre una GitHub App así como para obtener información específica sobre las instalaciones de éstas. - -Puedes acceder a las terminales de la API v3 de REST mientras estás autenticado como una GitHub App. Estas terminales tienen una sección de "Notas" que contiene una viñeta que dice "Funciona con las GitHub Apps". También puedes acceder a estas terminales mientras estás autenticado como un usuario. - -Un subconjunto de terminales de la API v3 de REST requiere que te autentiques como una instalación de una GitHub App. Consulta las [Instalaciones](/v3/apps/installations/) para obtener una lista de estas terminales. - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## API de las Aplicaciones de OAuth - -Puedes utilizar esta API para administrar los tokens de OAuth que utiliza una aplicación de OAuth para acceder a las cuentas de {% data variables.product.prodname_dotcom %} de las personas. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'oauth-applications' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Instalaciones - -La API de instalaciones te habilita para obtener información acerca de las instalaciones de tu GitHub App y para realizar acciones dentro de esas instalaciones. Una _instalación_ se refiere a cualquier cuenta de usuario o de organización que tenga la app instalada. Para obtener más información sobre cómo autenticarte como una instalación y limitar el acceso a repositorios específicos, consulta la sección "[Autenticarte como una instalación](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -Para listar las instalaciones de una GitHub App para una organización, consulta la sección "[Listar instalaciones de la app para una organización](/v3/orgs/#list-app-installations-for-an-organization)". -{% endif %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'installations' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% if currentVersion == "free-pro-team@latest" %} -## Marketplace - -Para obtener más información acerca de {% data variables.product.prodname_marketplace %}, consulta "[GitHub Marketplace](/marketplace/)". - -La API de {% data variables.product.prodname_marketplace %} te permite ver qué clientes están utilizando un plan de precios, ver sus compras y también ver si una cuenta tiene una suscripción activa. - -### Hacer pruebas con terminales de muestra - -Esta API incluye terminales que te permiten [probar tu {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) con **datos de muestra**. Los datos de muestra son datos falsos y preprogramados que no cambiarán con base en las suscripciones reales. - -Para hacer pruebas con estos datos, utiliza una terminal de muestra en vez de su contraparte productiva. Esto te permite probar si la lógica de la API tendrá éxito antes de listar tus {% data variables.product.prodname_github_app %} en {% data variables.product.prodname_marketplace %}. - -Asegúrate de reemplazar tus terminales de muestra con aquellas productivas antes de desplegar tu {% data variables.product.prodname_github_app %}. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'marketplace' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} diff --git a/translations/es-XL/content/rest/reference/billing.md b/translations/es-XL/content/rest/reference/billing.md deleted file mode 100644 index d933d1d220..0000000000 --- a/translations/es-XL/content/rest/reference/billing.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Facturación -versions: - fpt: '*' -topics: - - API ---- - -Puedes monitorear tus cargos y uso de {% data variables.product.prodname_actions %} y de {% data variables.product.prodname_registry %} para un usuario y organización a través de la API de Facturación. - -Puedes obtener información de facturación 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#billing)". - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/checks.md b/translations/es-XL/content/rest/reference/checks.md deleted file mode 100644 index a31a30fc59..0000000000 --- a/translations/es-XL/content/rest/reference/checks.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Verificaciones -redirect_from: - - /v3/checks -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -La API de Verificaciones te permite crear GitHub Apps que ejecuten verificaciones poderosas contra los cámbios de código en un repositorio. Puedes crear apps que lleven a cabo integración contínua, limpieza de código, o servicios de escaneo de código y que proporcionen retroalimentación detallada en las confirmaciones. Para obtener más información, consulta la sección "[Empezar con la API de verificaciones](/rest/guides/getting-started-with-the-checks-api)" y "[Crear pruebas de IC con la API de verificaciones](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/)". - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Ejecuciones de Verificación - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'runs' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Comprobar Suites - -{% note %} - - **Nota:** Una GitHub App solo recibe un evento de [`check_suite`](/webhooks/event-payloads/#check_suite) por SHA de confirmación, aún si cargas este SHA en más de una rama. Para saber cuándo se carga un SHA de confirmación a una rama, puedes suscribirte a los eventos de [`create`](/webhooks/event-payloads/#create) de la misma. - -{% endnote %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'suites' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/codes-of-conduct.md b/translations/es-XL/content/rest/reference/codes-of-conduct.md deleted file mode 100644 index b20b480e56..0000000000 --- a/translations/es-XL/content/rest/reference/codes-of-conduct.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Códigos de conducta -redirect_from: - - /v3/codes_of_conduct - - /v3/codes-of-conduct -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -Puedes usar la API de Códigos de Conducta para recuperar la información acerca del código de conducta de un repositorio. Para obtener el código de conducta de un repositorio, utiliza la terminal "[Obtener un repositorio](/v3/repos/#get-a-repository)". - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/emojis.md b/translations/es-XL/content/rest/reference/emojis.md deleted file mode 100644 index 87abc6dc01..0000000000 --- a/translations/es-XL/content/rest/reference/emojis.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Emojis -redirect_from: - - /v3/emojis - - /v3/misc -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/enterprise-admin.md b/translations/es-XL/content/rest/reference/enterprise-admin.md deleted file mode 100644 index 0203697bc6..0000000000 --- a/translations/es-XL/content/rest/reference/enterprise-admin.md +++ /dev/null @@ -1,332 +0,0 @@ ---- -title: Administración de GitHub Enterprise -allowTitleToDifferFromFilename: true -redirect_from: - - /v3/enterprise-admin - - /v3/enterprise -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -You can use these {% data variables.product.prodname_ghe_cloud %} endpoints to administer your enterprise account. - -{% if currentVersion == "free-pro-team@latest" %} - -{% note %} - -**Nota:** Este artículo aplica a {% data variables.product.prodname_ghe_cloud %}. Si quieres ver la versión para {% data variables.product.prodname_ghe_server %}, utiliza el menú desplegable de **{% data ui.pages.article_version %}**. - -{% endnote %} - -{% endif %} - -{% if currentVersion != "free-pro-team@latest" %} - -### URL de las Terminales - -Las terminales de la API de REST—excepto aquellas API de [Consola de Administración](#management-console)—llevan un prefijo con la siguiente URL: - -```shell -http(s)://hostname/api/v3/ -``` - -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/ -``` - -### 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/)** (que se pueden crear utilizando la [API de Autorizaciones](/rest/reference/oauth-authorizations#create-a-new-authorization)) o con **[autenticación básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if currentVersion != "free-pro-team@latest" %} 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 puede accederse a las terminales de la API para la administración empresarial si se trata de administradores de sitio de {% data variables.product.product_name %}, excepto por 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/). - -### Información de la versión - -La versión actual de una instancia de {% data variables.product.product_name %} se devuelve en el encabezado de respuesta de todas las 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/). - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} - -## Facturación - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'billing' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -## GitHub Actions - -{% 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 %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) que cuenten con el [SSO de SAML](/v3/auth/#authenticating-for-saml-sso) habilitado. Para obtener más información acerca de SCIM, consulta "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/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 | Tipo | Descripción | -| ---------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `userName` | `secuencia` | El nombre de usuario para el usuario. | -| `name.givenName` | `secuencia` | El primer nombre del usuario. | -| `name.lastName` | `secuencia` | El apellido del usuario. | -| `correos electrónicos` | `array` | 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` | `array` | 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 | Tipo | 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` | `array` | 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 != "free-pro-team@latest" %} - -## 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. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'admin-stats' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Webhooks globales - -Los webhooks globales se instalan en una instancia de {% data variables.product.prodname_enterprise %}. Puedes utilizar los webhooks globales para controlar, responder o aplicar reglas automáticamente para la administración de usuarios, organizaciones, equipos y repositorios en tu instancia. Los webhooks globales se pueden suscribir a los tipos de evento para [organizaciones](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuarios](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositorios](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipos](/developers/webhooks-and-events/webhook-events-and-payloads#team), [miembros](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membrecías](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [bifuraciones](/developers/webhooks-and-events/webhook-events-and-payloads#fork), y [pings](/developers/webhooks-and-events/about-webhooks#ping-event). - -*Esta API 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. Para aprender cómo configurar los webhooks globales, consulta la sección [Acerca de los webhooks globales](/enterprise/admin/user-management/about-global-webhooks). - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'global-webhooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## LDAP - -Puedes utilizar la API de LDAP para actualizar las relaciones de cuenta entre un usuario de {% data variables.product.prodname_ghe_server %} o un equipo y su entrada enlazada de LDAP o poner en cola una sincronización nueva. - -Con las terminales de mapeo de LDAP, puedes actualizar el Nombre Distintivo (DN, por sus siglas en inglés) al cual mapea un usuario o equipo. Nota que las terminales de LDAP generalmente solo son efectivas si tu aplicativo de {% data variables.product.prodname_ghe_server %} [habilitó la sincronización con LDAP](/enterprise/admin/authentication/using-ldap). La terminal de [mapeo de LDAP para actualización para un usuario](#update-ldap-mapping-for-a-user) puede utilizarse cuando se habilita LDAP, aún si la sincronización con LDAP está inhabilitada. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'ldap' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## 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. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'license' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Consola de administración - -La API de la Consola de Administración te ayuda a administrar tu {% data variables.product.prodname_ghe_server %} instalación. - -{% tip %} - -Debes configurar el número de puerto explícitamente cuando haces llamadas de la API hacia la Consola de Administración. Si se habilita el TLS en tu instancia empresarial, el número de puerto es `8443`; de lo contrario, el número de puerto será `8080`. - -Si no quieres proporcionar un número de puerto, necesitarás configurar tu herramienta para seguir automáticamente las redirecciones. - -También necesitas agregar el [marcador `-k`](http://curl.haxx.se/docs/manpage.html#-k) cuando utilices `curl`, ya que {% data variables.product.prodname_ghe_server %} utiliza un certificado auto-firmado antes de que [agregues tu propio certificado TLS](/enterprise/admin/guides/installation/configuring-tls/). - -{% endtip %} - -### Autenticación - -Necesitas pasar tu [Contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/) como un token de autenticación para cada terminal de la API de ésta, con excepción de [`/setup/api/start`](#create-a-github-enterprise-server-license). - -Utiliza el parámetro de `api_key` para enviar este token con cada solicitud. Por ejemplo: - -```shell -$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password' -``` - -También puedes utilizar la autenticación HTTP estándar para enviar este token. Por ejemplo: - -```shell -$ curl -L 'https://api_key:your-amazing-password@hostname:admin_port/setup/api' -``` - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'management-console' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Organizaciones - -La API de Administración de la organización te permite crear organizaciones en un aplicativo de {% data variables.product.prodname_ghe_server %}. *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. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## 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. - -### Atributos de objeto - -| Nombre | Tipo | Descripción | -| -------------------------------- | ----------- | --------------------------------------------------------- | -| `name (nombre)` | `secuencia` | El nombre del gancho. | -| `enforcement` | `secuencia` | El estado de imposición del gancho en este repositorio. | -| `allow_downstream_configuration` | `boolean` | Si los repositorios pueden ignorar la imposición o no. | -| `configuration_url` | `secuencia` | URL para la terminal en donde se configuró la imposición. | - -Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. - -`configuration_url` podría ser un enlace a esta terminal o ser la configuración global de este gancho. Solo los administradores de sistema pueden acceder a la configuración global. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'org-pre-receive-hooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Ambientes de pre-recepción - -La API de Ambientes de Pre-recepción te permite crear, listar, actualizar y borrar ambientes para 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. - -### Atributos de objeto - -#### Ambiente de pre-recepción - -| Nombre | Tipo | Descripción | -| --------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------- | -| `name (nombre)` | `secuencia` | El nombre del ambiente como se muestra en la IU. | -| `image_url` | `secuencia` | La URL del tarball que se descargará y extraerá. | -| `default_environment` | `boolean` | Si este es el ambiente predeterminado que viene con {% data variables.product.prodname_ghe_server %} o no. | -| `descargar` | `objeto` | El estado de descarga de este ambiente. | -| `hooks_count` | `número` | La cantidad de ganchos de pre-recepción que utilizan este ambiente. | - -#### Descarga del Ambiente de Pre-recepción - -| Nombre | Tipo | Descripción | -| --------------- | ----------- | -------------------------------------------------------------------------------- | -| `state` | `secuencia` | El estado de la mayoría de las descargas recientes. | -| `downloaded_at` | `secuencia` | La hora en la cual iniciaron la mayoría de las descrgas recientes. | -| `message` | `secuencia` | Cuando algo falla, este tendrá cualquier mensaje de error que se haya producido. | - -Los valores posibles para `state` son `not_started`, `in_progress`, `success`, `failed`. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'pre-receive-environments' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## 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. - -### Atributos de objeto - -#### Ganchos de pre-recepción - -| Nombre | Tipo | Descripción | -| -------------------------------- | ----------- | ----------------------------------------------------------------------------------- | -| `name (nombre)` | `secuencia` | El nombre del gancho. | -| `script` | `secuencia` | El script que ejecuta el gancho. | -| `script_repository` | `objeto` | El repositorio de GitHub en donde se mantiene el script. | -| `entorno` | `objeto` | El ambiente de pre-recepción en donde se ejecuta el script. | -| `enforcement` | `secuencia` | El estado de las imposiciones para este gancho. | -| `allow_downstream_configuration` | `boolean` | Si las imposiciones pueden o no ignorarse a nivel de organización o de repositorio. | - -Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'pre-receive-hooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Ganchos de pre-recepción del repositorio - -La API de Ganchos de Pre-recepción para Repositorios te permite ver y modificar la imposición de los ganchos de pre-recepción que están disponibles para un repositorio. - -### Atributos de objeto - -| Nombre | Tipo | Descripción | -| ------------------- | ----------- | --------------------------------------------------------- | -| `name (nombre)` | `secuencia` | El nombre del gancho. | -| `enforcement` | `secuencia` | El estado de imposición del gancho en este repositorio. | -| `configuration_url` | `secuencia` | URL para la terminal en donde se configuró la imposición. | - -Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. El valor `disabled` indica que el gancho de pre-recepción no se ejecutará. El valor `enabled` indica que se ejecutará y rechazará cualquier carga que resulte en un estado diferente a zero. El valor `testing` indica que el script va a ejecutarse pero no va a causar que se rechace ninguna carga. - -`configuration_url` podría ser un enlace a este repositorio, al propietario de su organización o a su configuración global. La autorización para acceder a esta terminal en `configuration_url` se determina a nivel de administrador de sitio o de propietario. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'repo-pre-receive-hooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Buscar en los índices - -La API de Búsqueda en los índices te permite poner en cola varias tareas de búsqueda en los índices. *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. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'search-indexing' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Usuarios - -La API de Administración de usuarios te permite promover, degradar, suspender y dejar de suspender a los usuarios en un aplicativo de {% data variables.product.prodname_ghe_server %}. *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 %} -{% endfor %} - -{% endif %} diff --git a/translations/es-XL/content/rest/reference/gists.md b/translations/es-XL/content/rest/reference/gists.md deleted file mode 100644 index 57d42475d1..0000000000 --- a/translations/es-XL/content/rest/reference/gists.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Gists -redirect_from: - - /v3/gists -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Autenticación - -Puedes leer gists públicos {% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "2.9" %}y crearlos para usuarios anónimos sin un token{% else %} de forma anónima, pero debes haber iniciado sesión en GitHub para crear gists.{% endif %} Para leer o escribir gists en nombre de un usuario, necesitas el alcance de OAuth para gists y un token. Par aobtener más información, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps)". - - - -### Truncamiento - -La API de Gist proporciona hasta un megabyte de contenido para cada archivo en el gist. Cada archivo que se devuelve para un gist a través de la API tiene una clave que se llama `truncated`. Si `truncated` aparece como `true`, significa que el archivo es demasiado grande y solo se devolvió una parte de su contenido en `content`. - -Si necesitas el contenido completo del archivo, puedes hacer una solicitud de tipo `GET` a la URL que se especifica en `raw_url`. Ten en cuent que, para los archivos mayores a diez megabytes, necesitarás clonar el gist a través de la URL que proprocionó `git_pull_url`. - -Adicionalmente a el truncamiento del contenido específico del archivo, la lista de archivos completa podría truncarse si la cantidad total excede los 300 archivos. Si la clave `truncated` de nivel superior aparece como `true`, únicamente se han devuelto los primeros 300 archivos en la lista. Si necesitas recuperar todos los archivos del gist, necesitarás clonarlo a través de la URL que te proporcionó `git_pull_url`. - -### Tipos de medios personalizados para los gists - -Estos son los tipos de medios compatibles para recuperar el contenido de los gists. - - application/vnd.github.VERSION.raw - application/vnd.github.VERSION.base64 - -Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)". - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Comentarios - -### Tipos de medios personalizados para los comentarios de los Gists - -Estos son los tipos de medios compatibles para los comentarios de los gists. - - application/vnd.github.VERSION.raw - application/vnd.github.VERSION.base64 - -Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/git.md b/translations/es-XL/content/rest/reference/git.md deleted file mode 100644 index 09bb2d5556..0000000000 --- a/translations/es-XL/content/rest/reference/git.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Base de datos de Git -allowTitleToDifferFromFilename: true -redirect_from: - - /v3/git -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -La API de la Base de datos de Git te da acceso de escritura y lectora para los objetos sin procesar de Git que se encuentran en tu base de datos de Git en {% data variables.product.product_name %} y para listar y actualizar tus referencias (cabezas de rama y etiquetas). Para obtener más información acerca de utilizar la API de la Base de Datos de Git, consulta la secicón "[Empezar con la API de datos de Git](/rest/guides/getting-started-with-the-git-database-api)". - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Blobs - -Un blob (objeto binario grande, por sus siglas en inglés) de Git es el tipo de objeto que se utiliza para almacenar el contenido de cada archivo en un repositorio. El hash SHA-1 del archivo se calcula y almacena en el objeto del blob. Estas terminales te permiten leer y escribir [objetos de blob](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) en tu base de datos de Git en {% data variables.product.product_name %}. Los blobs aprovechan [estos tipos de medios personalizados](#custom-media-types). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/rest/overview/media-types). - -### Tipos de medios personalizados para los blobs - -Estos son los tipos de medios compatibles para los blobs. - - application/json - application/vnd.github.VERSION.raw - -Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'blobs' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Confirmaciones - -Una confirmación de Git es una impresión de pantalla de la jerarquía ([árbol de Git](/v3/git/trees)) y del contenido de los archivos ([blob de Git](/v3/git/blobs)) en un reposiotorio de Git. Estas terminales te permiten leer y escribir [objetos de confirmación](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) en tu base de datos en {% data variables.product.product_name %}. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Referencias - -Una referencia (`git ref`) es simplemente un archivo que contiene un hash SHA-1 de una confirmación de Git. Cuando te refieres a una confirmación de Git, puedes utilizar la referencia de Git, la cual es un nombre fácil de recordar, en vez de utilizar el hash. La referencia de Git puede reescribirse para apuntar a una confirmación nueva. Una rama es solo una referencia de Git que almacena el hash de la confirmación de Git nueva. Estas terminales te permiten leer y escribir [referencias](https://git-scm.com/book/en/v1/Git-Internals-Git-References) en tu base de datos de Git en {% data variables.product.product_name %}. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'refs' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Etiquetas - -Una etiqueta de git es similar a una [referencia de Git](/v3/git/refs), pero la confirmación de Git a la que apunta jamás cambia. Las etiquetas de git son útiles cuando quieres apuntar a algún lanzamiento específico. Estas terminales te permiten leer y escribir [objetos de etiquetas](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags)en tu base de datos de Git en {% data variables.product.product_name %}. La API de etiquetas de Git son compatibles únicamente con los [objetos de etiqueta anotados](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), no con etiquetas ligeras. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'tags' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Árboles - -Un objeto de árbol de Git crea la jerarquía entre archivos para un repositorio de Git. Puedes utilizar el objeto de árbol de Git para crear una relación entre directorios y entre los archivos que contienen. Estas terminales te permiten leer y escribir [objetos de árbol](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects)en tu base de datos de Git en {% data variables.product.product_name %}. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'trees' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/gitignore.md b/translations/es-XL/content/rest/reference/gitignore.md deleted file mode 100644 index 216c45322c..0000000000 --- a/translations/es-XL/content/rest/reference/gitignore.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Gitignore -redirect_from: - - /v3/gitignore -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -Cuando creas un repositorio de {% data variables.product.product_name %} nuevo a través de la API, puedes especificar una [plantilla de .gitignore](/github/using-git/ignoring-files) para que aplique al repositorio cuando éste se cree. La API de plantillas de .gitignore lista y recupera plantillas del [repositorio de .gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}. - -### Tipos de medios personalizados para gitignore - -Puedes utilizar este tipo de medios personalizado cuando obtengas una plantilla de gitignore. - - application/vnd.github.VERSION.raw - -Para obtener más información, consulta la sección "[Tipos de medios](/rest/overview/media-types)". - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/index.md b/translations/es-XL/content/rest/reference/index.md deleted file mode 100644 index d299f08ee0..0000000000 --- a/translations/es-XL/content/rest/reference/index.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Referencia -shortTitle: Referencia -intro: Lee la documentación de referencia para conocer sobre los recursos que están disponibles en la API de REST de GitHub. -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API -children: - - /actions - - /activity - - /apps - - /billing - - /checks - - /codes-of-conduct - - /code-scanning - - /emojis - - /enterprise-admin - - /gists - - /git - - /gitignore - - /interactions - - /issues - - /licenses - - /markdown - - /meta - - /migrations - - /oauth-authorizations - - /orgs - - /packages - - /projects - - /pulls - - /rate-limit - - /reactions - - /repos - - /scim - - /search - - /secret-scanning - - /teams - - /users - - /permissions-required-for-github-apps ---- -### Índice - diff --git a/translations/es-XL/content/rest/reference/interactions.md b/translations/es-XL/content/rest/reference/interactions.md deleted file mode 100644 index 92d753cfac..0000000000 --- a/translations/es-XL/content/rest/reference/interactions.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Interacciones -redirect_from: - - /v3/interactions -versions: - fpt: '*' -topics: - - API ---- - -Los usuarios interactuan con los repositorios al comentar, abrir informes de problemas y crear solicitudes de extracción. Las API de interacciones permiten a las personas con acceso adminsitrativo o de propietario resgringir temporalmente a usuarios específicos de la interacción con los repositorios públicos. - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Organización - -La API de Interacciones de la Organización permite a los propietarios de las organizaciones restringir temporalmente qué usuarios pueden comentar, abrir informes de problemas, o crear solicitudes de extracción en los repositorios públicos de la organización. {% data reusables.interactions.interactions-detail %} Aquí tienes más detalles sobre los grupos de usuarios de {% data variables.product.product_name %}: - -* {% data reusables.interactions.existing-user-limit-definition %} en la organización. -* {% data reusables.interactions.contributor-user-limit-definition %} en la organización. -* {% data reusables.interactions.collaborator-user-limit-definition %} en la organización. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Repositorio - -La API de interacciones con el repositorio le permite a las personas con acceso administrativo o de propietario restringir temporalmente qué usuarios pueden comentar, abrir informes de problemas, o crear solicitudes de extracción en un repositorio público. {% data reusables.interactions.interactions-detail %} Aquí tienes más detalles sobre los grupos de usuarios de {% data variables.product.product_name %}: - -* {% data reusables.interactions.existing-user-limit-definition %} en el repositorio. -* {% data reusables.interactions.contributor-user-limit-definition %} en el repositorio. -* {% data reusables.interactions.collaborator-user-limit-definition %} en el repositorio. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/issues.md b/translations/es-XL/content/rest/reference/issues.md deleted file mode 100644 index 0c53f9f86f..0000000000 --- a/translations/es-XL/content/rest/reference/issues.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Problemas -redirect_from: - - /v3/issues -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Tipos de mendios personalizados para los informes de problemas - -Estos son los tipos de medios compatibles para los informes de problemas. - - application/vnd.github.VERSION.raw+json - application/vnd.github.VERSION.text+json - application/vnd.github.VERSION.html+json - application/vnd.github.VERSION.full+json - -Para obtener más información acerca de los tipos de medios, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Asignatarios - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'assignees' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Comentarios - -La API de Comentarios par los Informes de Problemas es compatible con listar, ver, editar y crear comentarios en informes de problemas y solicitudes de extracción. - -Los comentarios de los informes de problemas utilizan [estos tipos de medios personalizados](#custom-media-types). Puedes leer más acerca del uso de tipos de medios en la API [aquí](/v3/media/). - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Eventos - -La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos](/developers/webhooks-and-events/github-event-types)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'events' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Etiquetas - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'labels' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Hitos - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'milestones' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Línea de tiempo - -La API de eventos para la línea de tiempo puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad de la línea de tiempo en los informes de problemas y solicitudes de extracción. La API de eventos para Informes de problemas puede devolver diferentes tipos de eventos que se activan de acuerdo a la actividad en los informes de problemas y solicitudes de extracción. Para obtener más información acerca de los eventos específicos que puedes recibir de la API de Eventos para Solicitudes de Extracción, consulta la sección "[Tipos de evento de las Solicitudes de Extracción](/developers/webhooks-and-events/issue-event-types)". Para obtener más información, consulta la "[API de Eventos de GitHub](/developers/webhooks-and-events/github-event-types)". - -Puedes utilizar esta API para mostrar información sobre los informes de problemas y solicitudes de extracción o para determinar a quién debería notificársele sobre los comentarios en los informes de problemas. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'timeline' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/licenses.md b/translations/es-XL/content/rest/reference/licenses.md deleted file mode 100644 index cc5d12640d..0000000000 --- a/translations/es-XL/content/rest/reference/licenses.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Licencias -redirect_from: - - /v3/licenses -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -La API de licencias devuelve metadatos acerca de las liciencias de código abierto populares y acerca de la información sobre un archivo de licencia específico de un proyecto. - -La API de licencias utiliza [el Licenciatario de código abierto de la Gema de Ruby ](https://github.com/benbalter/licensee) para intentar identificar la licencia del proyecto. Este licenciatario empata el contenido del archivo de `LICENSE` de un proyecto (si es que existe) contra una lista corta de licencias conocidas. Como resultado, la API no toma en cuenta las licencias de las dependencias del proyecto u otros medios de documentar la licencia de un proyecto tales como las referencias al nombre de la licencia en la documentación. - -Si una licencia empata, la llave de licencia y el nombre devuelto se apegan a la [especificación SPDX](https://spdx.org/). - -**Nota:** Estas terminales también devolverán la información de licencia de un repositorio: - -- [Obtener un repositorio](/v3/repos/#get-a-repository) -- [Listar los repositorios para un usuario](/v3/repos/#list-repositories-for-a-user) -- [Listar los repositorios de una organización](/v3/repos/#list-organization-repositories) -- [Listar las bifurcaciones](/v3/repos/forks/#list-forks) -- [Listar los repositorios que el usuario está observando](/v3/activity/watching/#list-repositories-watched-by-a-user) -- [Listar los repositorios de equipo](/v3/teams/#list-team-repositories) - -{% warning %} - -GitHub puede ser muchas cosas, pero no es un buró legal. Como tal, GitHub no proporcional consejo legal. Al utilizar la API de licencias o al enviarnos un mensaje de correo electrónico acerca de ellas no estás incurriendo en ningún consejo legal ni creando una relación abogado-cliente. Si tienes cualquier pregunta acerca de lo que puedes o no hacer con una licencia específica, debes acudir a tu propio consejero legal antes de continuar. De hecho, siempre debes consultar con tu propio abogado antes de que decidas tomar cualquier decisión que pudiera tener implicaciones legales o que pudiera impactar tus derechos. - -GitHub creó la API de Licencias para ayudar a los usuarios a obtener información acerca de las licencias de código abierto y de los proyectos que las utilizan. Esperamos que te sea útil, pero ten presente que no somos abogados (por lo menos, la mayoría de nosotros no lo son) y que cometemos errores como todo el mundo. Es por esto que GitHub te proporciona una API "tal y como está" y no garantiza nada con respecto a la información o a las licencias que se proporcionan en o a través de ella, y se desllinda de cualquier responsabilidad derivada de los daños que pudiesen resultar de su uso. - -{% endwarning %} - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/markdown.md b/translations/es-XL/content/rest/reference/markdown.md deleted file mode 100644 index e9fd3a40e9..0000000000 --- a/translations/es-XL/content/rest/reference/markdown.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Markdown -redirect_from: - - /v3/markdown -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/meta.md b/translations/es-XL/content/rest/reference/meta.md deleted file mode 100644 index 2e34842566..0000000000 --- a/translations/es-XL/content/rest/reference/meta.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Meta -redirect_from: - - /v3/meta -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/migrations.md b/translations/es-XL/content/rest/reference/migrations.md deleted file mode 100644 index d31cdb99c6..0000000000 --- a/translations/es-XL/content/rest/reference/migrations.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -title: Migraciones -redirect_from: - - /v3/migrations - - /v3/migration - - /v3/migration/migrations -versions: - fpt: '*' -topics: - - API ---- - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Organización - -La API de Migraciones solo está disponible para los propietarios autenticados de la organización. Para obtener más información, consulta las secciones "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization)." y "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)". - -{% data variables.migrations.organization_migrations_intro %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Importaciones de Código Fuente - -{% data variables.migrations.source_imports_intro %} - -Una importación de código fuente habitual inicia la importación y luego actualiza (opcionalmente) a los autores y/o actualiza las preferencias para utilizar el LFS de Ggit si existen archivos grandes en la importación. También puedes crear un webhook que escuche al [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) para encontrar el estado de la importación. - -Se puede ver un ejemplo más detallado en este diagrama: - -``` -+---------+ +--------+ +---------------------+ -| Tooling | | GitHub | | Original Repository | -+---------+ +--------+ +---------------------+ - | | | - | Start import | | - |----------------------------->| | - | | | - | | Download source data | - | |--------------------------------------------->| - | | Begin streaming data | - | |<---------------------------------------------| - | | | - | Get import progress | | - |----------------------------->| | - | "status": "importing" | | - |<-----------------------------| | - | | | - | Get commit authors | | - |----------------------------->| | - | | | - | Map a commit author | | - |----------------------------->| | - | | | - | | | - | | Finish streaming data | - | |<---------------------------------------------| - | | | - | | Rewrite commits with mapped authors | - | |------+ | - | | | | - | |<-----+ | - | | | - | | Update repository on GitHub | - | |------+ | - | | | | - | |<-----+ | - | | | - | Map a commit author | | - |----------------------------->| | - | | Rewrite commits with mapped authors | - | |------+ | - | | | | - | |<-----+ | - | | | - | | Update repository on GitHub | - | |------+ | - | | | | - | |<-----+ | - | | | - | Get large files | | - |----------------------------->| | - | | | - | opt_in to Git LFS | | - |----------------------------->| | - | | Rewrite commits for large files | - | |------+ | - | | | | - | |<-----+ | - | | | - | | Update repository on GitHub | - | |------+ | - | | | | - | |<-----+ | - | | | - | Get import progress | | - |----------------------------->| | - | "status": "complete" | | - |<-----------------------------| | - | | | - | | | -``` - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'source-imports' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Usuario - -La API de migraciones de usuario solo está disponible para los propietarios de cuentas autenticadas. Para obtener más información, consulta la sección "[Otros métodos de autenticación](/rest/overview/other-authentication-methods)". - -{% data variables.migrations.user_migrations_intro %} Para encontrar una lista descargable de datos de migración, consulta "[Descarga un archivo de migración de usuario](#download-a-user-migration-archive)". - -Antes de descargar un archivo deberás iniciar la migración del usuario. Una vez que el estado de la migración sea `exported`, podrás descargarla. - -Ya que hayas creado el archivo de migración, este estará disponible para su descarga por siete días. Pero puedes borrar el archivo de migración del usuario antes si lo prefieres. Puedes desbloquear tu repositorio cuando la migración aparezca como `exported` para comenzar a utilizar tu repositorio nuevamente o borrarlo si ya no necesitas los datos del código fuente. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/oauth-authorizations.md b/translations/es-XL/content/rest/reference/oauth-authorizations.md deleted file mode 100644 index e20b7dd964..0000000000 --- a/translations/es-XL/content/rest/reference/oauth-authorizations.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Autorizaciones de OAuth -redirect_from: - - /v3/oauth_authorizations - - /v3/oauth-authorizations -versions: - ghes: '*' ---- - -{% data reusables.apps.deprecating_token_oauth_authorizations %} -{% data reusables.apps.deprecating_password_auth %} - -Puedes utilizar esta API para administrar el acceso que las aplicaciones de OAuth tienen en tu cuenta. Solo puedes acceder a esta API a través de la [Autenticación Básica](/rest/overview/other-authentication-methods#basic-authentication) utilizando tu nombre de usuario y contraseña, y no los tokens. - -Si tú o tus usuarios habilitaron la autenticación de dos factores, asegúrate de que entiendes cómo [trabajar con la autenticación de dos factores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication). - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/orgs.md b/translations/es-XL/content/rest/reference/orgs.md deleted file mode 100644 index 3cd0ddf41f..0000000000 --- a/translations/es-XL/content/rest/reference/orgs.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Organizaciones -allowTitleToDifferFromFilename: true -redirect_from: - - /v3/orgs -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Bloquear usuarios - -El token que se utiliza para autenticar la llamada debe tener el alcance de `admin:org` para poder hacer cualquier llamada de bloqueo para una organización. De lo contrario, la respuesta devolverá un `HTTP 404`. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Miembros - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Colaboradores externos - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'outside-collaborators' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Webhooks - -Los webhooks de la organización te permiten recibir cargas útiles HTTP de tipo `POST` cada que suceden eventos específicos dentro de la misma. Cuando te suscribes a estos eventos puedes crear integraciones que reaccionen a las acciones de {% data variables.product.prodname_dotcom %}.com. Para obtener más información sobre las acciones a las cuales te puedes suscribir, consulta los "[tipos de eventos de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)". - -### Alcances & Restricciones - -Todas las acciones en contra de los webhooks de una organización requieren que el usuario autenticado sea un administrador de la organización que se está administrando. Adicionalmente, los tokens de OAuth requieren el alcance `admin:org_hook`. Par aobtener más información, consulta la sección "[Alcances para las Apps de OAuth](/developers/apps/scopes-for-oauth-apps)". - -Para porteger los datos sensibles que pueden encontrarse en las configuraciones de los webhooks, también imponemos las siguientes reglas de control de accesos: - -- Las aplicaciones de OAuth no pueden listar, ver o editar los webhooks que no crearon ellas mismas. -- Los usuarios no pueden listar, ver o editar los webhooks que crearon las aplicaciones de OAuth. - -### Recibir Webhooks - -Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS. - -Para encontrar más de las mejores prácticas, [consulta nuestra guía](/guides/best-practices-for-integrators/). - -#### Encabezados de Webhook - -{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/webhooks/event-payloads/#delivery-headers) para encontrar más detalles. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'hooks' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/permissions-required-for-github-apps.md b/translations/es-XL/content/rest/reference/permissions-required-for-github-apps.md deleted file mode 100644 index 4c0a8183a9..0000000000 --- a/translations/es-XL/content/rest/reference/permissions-required-for-github-apps.md +++ /dev/null @@ -1,884 +0,0 @@ ---- -title: Permisos que requieren las Github Apps -intro: 'Puedes encontrar los permisos que requiere cada terminal compatible con {% data variables.product.prodname_github_app %}.' -redirect_from: - - /v3/apps/permissions -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Acerca de los permisos de las {% data variables.product.prodname_github_app %} - -Las {% data variables.product.prodname_github_app %}s se crean con un conjunto de permisos. Los permisos definen a qué recursos puede acceder la {% data variables.product.prodname_github_app %} a través de la API. Para obtener más información, consulta la sección "[Configurar los permisos para las GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)". - -### Permisos de metadatos - -Las GitHub Apps tienen el permiso de metadatos de `Read-only` predeterminadamente. El permiso de metadatos proporciona acceso a una recopilación de terminales de solo lectura con los metadatos de varios recursos. Estas terminales no filtran información sensible de los repositorios privados. - -{% data reusables.apps.metadata-permissions %} - - -- [`GET /`](/v3/#root-endpoint) -- [`GET /codes_of_conduct`](/v3/codes_of_conduct/#get-all-codes-of-conduct) -- [`GET /codes_of_conduct/:key`](/v3/codes_of_conduct/#get-a-code-of-conduct) -- [`GET /emojis`](/v3/emojis/#emojis) -- [`GET /feeds`](/v3/activity/feeds/#get-feeds) -- [`GET /licenses`](/v3/licenses/#get-all-commonly-used-licenses) -- [`GET /licenses/:key`](/v3/licenses/#get-a-license) -- [`POST /markdown`](/v3/markdown/#render-a-markdown-document) -- [`POST /markdown/raw`](/v3/markdown/#render-a-markdown-document-in-raw-mode) -- [`GET /meta`](/v3/meta/#meta) -- [`GET /organizations`](/v3/orgs/#list-organizations) -- [`GET /orgs/:org`](/v3/orgs/#get-an-organization) -- [`GET /orgs/:org/projects`](/v3/projects/#list-organization-projects) -- [`GET /orgs/:org/repos`](/v3/repos/#list-organization-repositories) -- [`GET /rate_limit`](/v3/rate_limit/#get-rate-limit-status-for-the-authenticated-user) -- [`GET /repos/:owner/:repo`](/v3/repos/#get-a-repository) -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/community/profile`](/v3/repos/community/#get-community-profile-metrics) -{% endif %} -- [`GET /repos/:owner/:repo/contributors`](/v3/repos/#list-repository-contributors) -- [`GET /repos/:owner/:repo/forks`](/v3/repos/forks/#list-forks) -- [`GET /repos/:owner/:repo/languages`](/v3/repos/#list-repository-languages) -- [`GET /repos/:owner/:repo/license`](/v3/licenses/#get-the-license-for-a-repository) -- [`GET /repos/:owner/:repo/stargazers`](/v3/activity/starring/#list-stargazers) -- [`GET /repos/:owner/:repo/stats/code_frequency`](/v3/repos/statistics/#get-the-weekly-commit-activity) -- [`GET /repos/:owner/:repo/stats/commit_activity`](/v3/repos/statistics/#get-the-last-year-of-commit-activity) -- [`GET /repos/:owner/:repo/stats/contributors`](/v3/repos/statistics/#get-all-contributor-commit-activity) -- [`GET /repos/:owner/:repo/stats/participation`](/v3/repos/statistics/#get-the-weekly-commit-count) -- [`GET /repos/:owner/:repo/stats/punch_card`](/v3/repos/statistics/#get-the-hourly-commit-count-for-each-day) -- [`GET /repos/:owner/:repo/subscribers`](/v3/activity/watching/#list-watchers) -- [`GET /repos/:owner/:repo/tags`](/v3/repos/#list-repository-tags) -- [`GET /repos/:owner/:repo/topics`](/v3/repos#get-all-repository-topics) -- [`GET /repositories`](/v3/repos/#list-public-repositories) -- [`GET /user/repos`](/v3/repos/#list-repositories-for-the-authenticated-user) -- [`GET /user/starred`](/v3/activity/starring/#list-repositories-starred-by-a-user) -- [`GET /user/subscriptions`](/v3/activity/watching/#list-repositories-watched-by-a-user) -- [`GET /users`](/v3/users/#list-users) -- [`GET /users/:username`](/v3/users/#get-a-user) -- [`GET /users/:username/followers`](/v3/users/followers/#list-followers-of-a-user) -- [`GET /users/:username/following`](/v3/users/followers/#list-the-people-a-user-follows) -- [`GET /users/:username/following/:target_user`](/v3/users/followers/#check-if-a-user-follows-another-user) -- [`GET /users/:username/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-a-user) -- [`GET /users/:username/orgs`](/v3/orgs/#list-organizations-for-a-user) -- [`GET /users/:username/received_events`](/v3/activity/events/#list-events-received-by-the-authenticated-user) -- [`GET /users/:username/received_events/public`](/v3/activity/events/#list-public-events-received-by-a-user) -- [`GET /users/:username/repos`](/v3/repos/#list-repositories-for-a-user) -- [`GET /users/:username/subscriptions`](/v3/activity/watching/#list-repositories-watched-by-a-user) - -_Colaboradores_ -- [`GET /repos/:owner/:repo/collaborators`](/v3/repos/collaborators/#list-repository-collaborators) -- [`GET /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#check-if-a-user-is-a-repository-collaborator) - -_Comentarios sobre confirmación de cambios_ -- [`GET /repos/:owner/:repo/comments`](/v3/repos/comments/#list-commit-comments-for-a-repository) -- [`GET /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#get-a-commit-comment) -- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-commit-comment) -- [`GET /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#list-commit-comments) - -_Eventos_ -- [`GET /events`](/v3/activity/events/#list-public-events) -- [`GET /networks/:owner/:repo/events`](/v3/activity/events/#list-public-events-for-a-network-of-repositories) -- [`GET /orgs/:org/events`](/v3/activity/events/#list-public-organization-events) -- [`GET /repos/:owner/:repo/events`](/v3/activity/events/#list-repository-events) -- [`GET /users/:username/events`](/v3/activity/events/#list-events-for-the-authenticated-user) -- [`GET /users/:username/events/public`](/v3/activity/events/#list-public-events-for-a-user) - -_Git_ -- [`GET /gitignore/templates`](/v3/gitignore/#get-all-gitignore-templates) -- [`GET /gitignore/templates/:key`](/v3/gitignore/#get-a-gitignore-template) - -_Claves_ -- [`GET /users/:username/keys`](/v3/users/keys/#list-public-keys-for-a-user) - -_Miembros de la organización_ -- [`GET /orgs/:org/members`](/v3/orgs/members/#list-organization-members) -- [`GET /orgs/:org/members/:username`](/v3/orgs/members/#check-organization-membership-for-a-user) -- [`GET /orgs/:org/public_members`](/v3/orgs/members/#list-public-organization-members) -- [`GET /orgs/:org/public_members/:username`](/v3/orgs/members/#check-public-organization-membership-for-a-user) - -_Buscar_ -- [`GET /search/code`](/v3/search/#search-code) -- [`GET /search/commits`](/v3/search/#search-commits) -- [`GET /search/issues`](/v3/search/#search-issues-and-pull-requests) -- [`GET /search/labels`](/v3/search/#search-labels) -- [`GET /search/repositories`](/v3/search/#search-repositories) -- [`GET /search/topics`](/v3/search/#search-topics) -- [`GET /search/users`](/v3/search/#search-users) - -{% if currentVersion == "free-pro-team@latest" %} -### Permiso sobre las "acciones" - -- [`GET /repos/:owner/:repo/actions/artifacts`](/v3/actions/artifacts/#list-artifacts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) -{% endif %} - -### Permiso sobre la "administración" - -- [`POST /orgs/:org/repos`](/v3/repos/#create-an-organization-repository) (:write) -- [`PATCH /repos/:owner/:repo`](/v3/repos/#update-a-repository) (:write) -- [`DELETE /repos/:owner/:repo`](/v3/repos/#delete-a-repository) (:write) -{% if currentVersion == "free-pro-team@latest" %} -- [`Get GET /repos/:owner/:repo/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-a-repository) (:read) -- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-a-repository) (:write) -- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-a-repository) (:write)git -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#enable-automated-security-fixes) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/v3/repos/#disable-automated-security-fixes) (:write) -{% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:write) -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#get-interaction-restrictions-for-a-repository) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#set-interaction-restrictions-for-a-repository) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/interaction-limits`](/v3/interactions/repos/#remove-interaction-restrictions-for-a-repository) (:write) -{% endif %} -- [`PUT /repos/:owner/:repo/topics`](/v3/repos/#replace-all-repository-topics) (:write) -- [`POST /repos/:owner/:repo/transfer`](/v3/repos/#transfer-a-repository) (:write) -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#enable-vulnerability-alerts) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/v3/repos/#disable-vulnerability-alerts) (:write) -{% endif %} -- [`POST /user/repos`](/v3/repos/#create-a-repository-for-the-authenticated-user) (:write) -- [`PATCH /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#accept-a-repository-invitation) (:write) -- [`DELETE /user/repository_invitations/:invitation_id`](/v3/repos/invitations/#decline-a-repository-invitation) (:write) - -_Ramas_ -- [`GET /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#get-branch-protection) (:read) -- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#update-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/v3/repos/branches/#delete-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#get-admin-branch-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#set-admin-branch-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/v3/repos/branches/#delete-admin-branch-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#get-pull-request-review-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#update-pull-request-review-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/v3/repos/branches/#delete-pull-request-review-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#get-commit-signature-protection) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#create-commit-signature-protection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/v3/repos/branches/#delete-commit-signature-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#get-status-checks-protection) (:read) -- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#update-status-check-potection) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/v3/repos/branches/#remove-status-check-protection) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#get-all-status-check-contexts) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#add-status-check-contexts) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#set-status-check-contexts) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/v3/repos/branches/#remove-status-check-contexts) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#get-access-restrictions) (:read) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/v3/repos/branches/#delete-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#list-teams-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#add-team-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#set-team-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/v3/repos/branches/#remove-team-access-restrictions) (:write) -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#list-users-with-access-to-the-protected-branch) (:read) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#add-user-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#set-user-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/v3/repos/branches/#remove-user-access-restrictions) (:write) - -_Colaboradores_ -- [`PUT /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#add-a-repository-collaborator) (:write) -- [`DELETE /repos/:owner/:repo/collaborators/:username`](/v3/repos/collaborators/#remove-a-repository-collaborator) (:write) - -_Invitaciones_ -- [`GET /repos/:owner/:repo/invitations`](/v3/repos/invitations/#list-repository-invitations) (:read) -- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#update-a-repository-invitation) (:write) -- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/v3/repos/invitations/#delete-a-repository-invitation) (:write) - -_Claves_ -- [`GET /repos/:owner/:repo/keys`](/v3/repos/keys/#list-deploy-keys) (:read) -- [`POST /repos/:owner/:repo/keys`](/v3/repos/keys/#create-a-deploy-key) (:write) -- [`GET /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#get-a-deploy-key) (:read) -- [`DELETE /repos/:owner/:repo/keys/:key_id`](/v3/repos/keys/#delete-a-deploy-key) (:write) - -_Equipos_ -- [`GET /repos/:owner/:repo/teams`](/v3/repos/#list-repository-teams) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:write) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) - -{% if currentVersion == "free-pro-team@latest" %} -_Tráfico_ -- [`GET /repos/:owner/:repo/traffic/clones`](/v3/repos/traffic/#get-repository-clones) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/paths`](/v3/repos/traffic/#get-top-referral-paths) (:read) -- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/v3/repos/traffic/#get-top-referral-sources) (:read) -- [`GET /repos/:owner/:repo/traffic/views`](/v3/repos/traffic/#get-page-views) (:read) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -### Permiso sobre el "bloqueo" - -- [`GET /user/blocks`](/v3/users/blocking/#list-users-blocked-by-the-authenticated-user) (:read) -- [`GET /user/blocks/:username`](/v3/users/blocking/#check-if-a-user-is-blocked-by-the-authenticated-user) (:read) -- [`PUT /user/blocks/:username`](/v3/users/blocking/#block-a-user) (:write) -- [`DELETE /user/blocks/:username`](/v3/users/blocking/#unblock-a-user) (:write) -{% endif %} - -### Permiso sobre las "verificaciones" - -- [`POST /repos/:owner/:repo/check-runs`](/v3/checks/runs/#create-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#update-a-check-run) (:write) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`POST /repos/:owner/:repo/check-suites`](/v3/checks/suites/#create-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/v3/checks/suites/#update-repository-preferences-for-check-suites) (:write) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) - -### Permiso sobre el "contenido" - -- [`GET /repos/:owner/:repo/:archive_format/:ref`](/v3/repos/contents/#download-a-repository-archive) (:read) -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#get-an-artifact) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/v3/actions/artifacts/#delete-an-artifact) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/v3/actions/artifacts/#download-an-artifact) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/v3/actions/workflow-jobs/#get-a-job-for-a-workflow-run) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/v3/actions/workflow-jobs/#download-job-logs-for-a-workflow-run) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs`](/v3/actions/workflow-runs/#list-workflow-runs-for-a-repository) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/v3/actions/workflow-runs/#get-a-workflow-run) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/v3/actions/artifacts/#list-workflow-run-artifacts) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/v3/actions/workflow-runs/#cancel-a-workflow-run) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/v3/actions/workflow-jobs/#list-jobs-for-a-workflow-run) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#download-workflow-run-logs) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/v3/actions/workflow-runs/#delete-workflow-run-logs) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/v3/actions/workflow-runs/#re-run-a-workflow) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#get-a-repository-secret) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows`](/v3/actions/workflows/#list-repository-workflows) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/v3/actions/workflows/#get-a-workflow) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/v3/actions/workflow-runs/#list-workflow-runs) (:read) -{% endif %} -- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/v3/checks/runs/#get-a-check-run) (:read) -- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/v3/checks/runs/#list-check-run-annotations) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/v3/checks/suites/#get-a-check-suite) (:read) -- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/v3/checks/runs/#list-check-runs-in-a-check-suite) (:read) -- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/v3/checks/suites/#rerequest-a-check-suite) (:write) -- [`GET /repos/:owner/:repo/commits`](/v3/repos/commits/#list-commits) (:read) -- [`GET /repos/:owner/:repo/commits/:sha`](/v3/repos/commits/#get-a-commit) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/v3/checks/runs/#list-check-runs-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/v3/checks/suites/#list-check-suites-for-a-git-reference) (:read) -- [`GET /repos/:owner/:repo/community/code_of_conduct`](/v3/codes_of_conduct/#get-the-code-of-conduct-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/compare/:base...:head`](/v3/repos/commits/#compare-two-commits) (:read) -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- [`POST /repos/:owner/:repo/dispatches`](/v3/repos/#create-a-repository-dispatch-event) (:write) -{% endif %} -- [`POST /repos/:owner/:repo/forks`](/v3/repos/forks/#create-a-fork) (:read) -- [`POST /repos/:owner/:repo/merges`](/v3/repos/merging/#merge-a-branch) (:write) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#merge-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/v3/repos/contents/#get-a-repository-readme) (:read) - -_Ramas_ -- [`GET /repos/:owner/:repo/branches`](/v3/repos/branches/#list-branches) (:read) -- [`GET /repos/:owner/:repo/branches/:branch`](/v3/repos/branches/#get-a-branch) (:read) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#list-apps-with-access-to-the-protected-branch) (:write) -- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#add-app-access-restrictions) (:write) -- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#set-app-access-restrictions) (:write) -- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/v3/repos/branches/#remove-user-access-restrictions) (:write) -{% endif %} - -_Comentarios sobre confirmación de cambios_ -- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#update-a-commit-comment) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/v3/repos/comments/#delete-a-commit-comment) (:write) -- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-commit-comment) (:read) -- [`POST /repos/:owner/:repo/commits/:sha/comments`](/v3/repos/comments/#create-a-commit-comment) (:read) - -_Git_ -- [`POST /repos/:owner/:repo/git/blobs`](/v3/git/blobs/#create-a-blob) (:write) -- [`GET /repos/:owner/:repo/git/blobs/:sha`](/v3/git/blobs/#get-a-blob) (:read) -- [`POST /repos/:owner/:repo/git/commits`](/v3/git/commits/#create-a-commit) (:write) -- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/v3/git/commits/#get-a-commit) (:read) -- [`POST /repos/:owner/:repo/git/refs`](/v3/git/refs/#create-a-reference) (:write) -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} -- [`GET /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#get-a-reference) (:read) -- [`GET /repos/:owner/:repo/git/refs`](/v3/git/refs/#list-references) (:read) -{% else %} -- [`GET /repos/:owner/:repo/git/ref/:ref`](/v3/git/refs/#get-a-reference) (:read) -- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/v3/git/refs/#list-matching-references) (:read) -{% endif %} -- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#update-a-reference) (:write) -- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/v3/git/refs/#delete-a-reference) (:write) -- [`POST /repos/:owner/:repo/git/tags`](/v3/git/tags/#create-a-tag-object) (:write) -- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/v3/git/tags/#get-a-tag) (:read) -- [`POST /repos/:owner/:repo/git/trees`](/v3/git/trees/#create-a-tree) (:write) -- [`GET /repos/:owner/:repo/git/trees/:sha`](/v3/git/trees/#get-a-tree) (:read) - -{% if currentVersion == "free-pro-team@latest" %} -_Importar_ -- [`GET /repos/:owner/:repo/import`](/v3/migrations/source_imports/#get-an-import-status) (:read) -- [`PUT /repos/:owner/:repo/import`](/v3/migrations/source_imports/#start-an-import) (:write) -- [`PATCH /repos/:owner/:repo/import`](/v3/migrations/source_imports/#update-an-import) (:write) -- [`DELETE /repos/:owner/:repo/import`](/v3/migrations/source_imports/#cancel-an-import) (:write) -- [`GET /repos/:owner/:repo/import/authors`](/v3/migrations/source_imports/#get-commit-authors) (:read) -- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/v3/migrations/source_imports/#map-a-commit-author) (:write) -- [`GET /repos/:owner/:repo/import/large_files`](/v3/migrations/source_imports/#get-large-files) (:read) -- [`PATCH /repos/:owner/:repo/import/lfs`](/v3/migrations/source_imports/#update-git-lfs-preference) (:write) -{% endif %} - -_Reacciones_ - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% endif %} - -_Lanzamientos_ -- [`GET /repos/:owner/:repo/releases`](/v3/repos/releases/#list-releases) (:read) -- [`POST /repos/:owner/:repo/releases`](/v3/repos/releases/#create-a-release) (:write) -- [`GET /repos/:owner/:repo/releases/:release_id`](/v3/repos/releases/#get-a-release) (:read) -- [`PATCH /repos/:owner/:repo/releases/:release_id`](/v3/repos/releases/#update-a-release) (:write) -- [`DELETE /repos/:owner/:repo/releases/:release_id`](/v3/repos/releases/#delete-a-release) (:write) -- [`GET /repos/:owner/:repo/releases/:release_id/assets`](/v3/repos/releases/#list-release-assets) (:read) -- [`GET /repos/:owner/:repo/releases/assets/:asset_id`](/v3/repos/releases/#get-a-release-asset) (:read) -- [`PATCH /repos/:owner/:repo/releases/assets/:asset_id`](/v3/repos/releases/#update-a-release-asset) (:write) -- [`DELETE /repos/:owner/:repo/releases/assets/:asset_id`](/v3/repos/releases/#delete-a-release-asset) (:write) -- [`GET /repos/:owner/:repo/releases/latest`](/v3/repos/releases/#get-the-latest-release) (:read) -- [`GET /repos/:owner/:repo/releases/tags/:tag`](/v3/repos/releases/#get-a-release-by-tag-name) (:read) - -### Permiso sobre los "despliegues" - -- [`GET /repos/:owner/:repo/deployments`](/v3/repos/deployments/#list-deployments) (:read) -- [`POST /repos/:owner/:repo/deployments`](/v3/repos/deployments/#create-a-deployment) (:write) -- [`GET /repos/:owner/:repo/deployments/:deployment_id`](/v3/repos/deployments/#get-a-deployment) (:read){% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- [`DELETE /repos/:owner/:repo/deployments/:deployment_id`](/v3/repos/deployments/#delete-a-deployment) (:write){% endif %} -- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses`](/v3/repos/deployments/#list-deployment-statuses) (:read) -- [`POST /repos/:owner/:repo/deployments/:deployment_id/statuses`](/v3/repos/deployments/#create-a-deployment-status) (:write) -- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/v3/repos/deployments/#get-a-deployment-status) (:read) - -### Permiso sobre los "correos electrónicos" - -{% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /user/email/visibility`](/v3/users/emails/#set-primary-email-visibility-for-the-authenticated-user) (:write) -{% endif %} -- [`GET /user/emails`](/v3/users/emails/#list-email-addresses-for-the-authenticated-user) (:read) -- [`POST /user/emails`](/v3/users/emails/#add-an-email-address-for-the-authenticated-user) (:write) -- [`DELETE /user/emails`](/v3/users/emails/#delete-an-email-address-for-the-authenticated-user) (:write) -- [`GET /user/public_emails`](/v3/users/emails/#list-public-email-addresses-for-the-authenticated-user) (:read) - -### Permiso sobre los "seguidores" - -- [`GET /user/followers`](/v3/users/followers/#list-followers-of-a-user) (:read) -- [`GET /user/following`](/v3/users/followers/#list-the-people-a-user-follows) (:read) -- [`GET /user/following/:username`](/v3/users/followers/#check-if-a-person-is-followed-by-the-authenticated-user) (:read) -- [`PUT /user/following/:username`](/v3/users/followers/#follow-a-user) (:write) -- [`DELETE /user/following/:username`](/v3/users/followers/#unfollow-a-user) (:write) - -### Permiso sobre las "llaves gpg" - -- [`GET /user/gpg_keys`](/v3/users/gpg_keys/#list-gpg-keys-for-the-authenticated-user) (:read) -- [`POST /user/gpg_keys`](/v3/users/gpg_keys/#create-a-gpg-key-for-the-authenticated-user) (:write) -- [`GET /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#get-a-gpg-key-for-the-authenticated-user) (:read) -- [`DELETE /user/gpg_keys/:gpg_key_id`](/v3/users/gpg_keys/#delete-a-gpg-key-for-the-authenticated-user) (:write) - -### Permiso sobre los "informes de problemas" - -Los informes de problemas y las solicitudes de extracción están estrechamente relacionadas. Para obtener más información, consulta la sección "[Listar informes de problemas asignados al usuario autenticado](/v3/issues/#list-issues-assigned-to-the-authenticated-user)". Si tu GitHub App tiene permisos sobre los informes de problemas pero no los tiene en las solicitudes de extracción, entonces estas terminales se limitaran a los informes de problemas. Se filtrarán las terminales que devuelvan tanto informes de problemas como solicitudes de extracción. Las terminales que permitan operaciones tanto en los informes de problemas como en las solicitudes de extracción se restringirán a los informes de problemas únicamente. - -- [`GET /repos/:owner/:repo/issues`](/v3/issues/#list-repository-issues) (:read) -- [`POST /repos/:owner/:repo/issues`](/v3/issues/#create-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#get-an-issue) (:read) -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) - -_Asignatarios_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) - -_Eventos_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [Obtener un evento de un informe de problemas](/v3/issues/events/#get-an-issue-event) (:read) - -_Etiquetas_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) - -_Hitos_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) - -_Reacciones_ -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#list-reactions-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} - -### Permiso sobre las "llaves" - -_Claves_ -- [`GET /user/keys`](/v3/users/keys/#list-public-ssh-keys-for-the-authenticated-user) (:read) -- [`POST /user/keys`](/v3/users/keys/#create-a-public-ssh-key-for-the-authenticated-user) (:write) -- [`GET /user/keys/:key_id`](/v3/users/keys/#get-a-public-ssh-key-for-the-authenticated-user) (:read) -- [`DELETE /user/keys/:key_id`](/v3/users/keys/#delete-a-public-ssh-key-for-the-authenticated-user) (:write) - -### Permiso sobre los "miembros" - -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#list-idp-groups-for-a-team) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/v3/teams/team_sync/#create-or-update-idp-group-connections) (:write) -{% endif %} -- [`GET /orgs/:org/outside_collaborators`](/v3/orgs/outside_collaborators/#list-outside-collaborators-for-an-organization) (:read) -- [`PUT /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#convert-an-organization-member-to-outside-collaborator) (:write) -- [`DELETE /orgs/:org/outside_collaborators/:username`](/v3/orgs/outside_collaborators/#remove-outside-collaborator-from-an-organization) (:write) -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/team-sync/groups`](/v3/teams/team_sync/#list-idp-groups-for-an-organization) (:write) -{% endif %} -- [`GET /orgs/:org/team/:team_id`](/v3/teams/#get-a-team-by-name) (:read) -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users`](/v3/scim/#list-scim-provisioned-identities) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`POST /scim/v2/orgs/:org/Users`](/v3/scim/#provision-and-invite-a-scim-user) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#get-scim-provisioning-information-for-a-user) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#set-scim-information-for-a-provisioned-user) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#update-an-attribute-for-a-scim-user) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/v3/scim/#delete-a-scim-user-from-an-organization) (:write) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -_Invitaciones_ -- [`GET /orgs/:org/invitations`](/v3/orgs/members/#list-pending-organization-invitations) (:read) -- [`POST /orgs/:org/invitations`](/v3/orgs/members/#create-an-organization-invitation) (:write) -- [`GET /orgs/:org/invitations/:invitation_id/teams`](/v3/orgs/members/#list-organization-invitation-teams) (:read) -- [`GET /teams/:team_id/invitations`](/v3/teams/members/#list-pending-team-invitations) (:read) -{% endif %} - -_Miembros de la organización_ -- [`DELETE /orgs/:org/members/:username`](/v3/orgs/members/#remove-an-organization-member) (:write) -- [`GET /orgs/:org/memberships/:username`](/v3/orgs/members/#get-organization-membership-for-a-user) (:read) -- [`PUT /orgs/:org/memberships/:username`](/v3/orgs/members/#set-organization-membership-for-a-user) (:write) -- [`DELETE /orgs/:org/memberships/:username`](/v3/orgs/members/#remove-organization-membership-for-a-user) (:write) -- [`PUT /orgs/:org/public_members/:username`](/v3/orgs/members/#set-public-organization-membership-for-the-authenticated-user) (:write) -- [`DELETE /orgs/:org/public_members/:username`](/v3/orgs/members/#remove-public-organization-membership-for-the-authenticated-user) (:write) -- [`GET /user/memberships/orgs`](/v3/orgs/members/#list-organization-memberships-for-the-authenticated-user) (:read) -- [`GET /user/memberships/orgs/:org`](/v3/orgs/members/#get-an-organization-membership-for-the-authenticated-user) (:read) -- [`PATCH /user/memberships/orgs/:org`](/v3/orgs/members/#update-an-organization-membership-for-the-authenticated-user) (:write) - -_Miembros del equipo_ -- [`GET /teams/:team_id/members`](/v3/teams/members/#list-team-members) (:read) -- [`GET /teams/:team_id/memberships/:username`](/v3/teams/members/#get-team-membership-for-a-user) (:read) -- [`PUT /teams/:team_id/memberships/:username`](/v3/teams/members/#add-or-update-team-membership-for-a-user) (:write) -- [`DELETE /teams/:team_id/memberships/:username`](/v3/teams/members/#remove-team-membership-for-a-user) (:write) - -_Equipos_ -- [`GET /orgs/:org/teams`](/v3/teams/#list-teams) (:read) -- [`POST /orgs/:org/teams`](/v3/teams/#create-a-team) (:write) -- [`GET /orgs/:org/teams/:team_slug`](/v3/teams/#get-a-team-by-name) (:read) -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %} -- [`GET /teams/:team_id`](/v3/teams/#get-a-team) (:read) -{% endif %} -- [`PATCH /teams/:team_id`](/v3/teams/#update-a-team) (:write) -- [`DELETE /teams/:team_id`](/v3/teams/#delete-a-team) (:write) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- [`GET /teams/:team_id/projects`](/v3/teams/#list-team-projects) (:read) -- [`GET /teams/:team_id/projects/:project_id`](/v3/teams/#check-team-permissions-for-a-project) (:read) -- [`PUT /teams/:team_id/projects/:project_id`](/v3/teams/#add-or-update-team-project-permissions) (:read) -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) -{% endif %} -- [`GET /teams/:team_id/repos`](/v3/teams/#list-team-repositories) (:read) -- [`GET /teams/:team_id/repos/:owner/:repo`](/v3/teams/#check-team-permissions-for-a-repository) (:read) -- [`PUT /teams/:team_id/repos/:owner/:repo`](/v3/teams/#add-or-update-team-repository-permissions) (:read) -- [`DELETE /teams/:team_id/repos/:owner/:repo`](/v3/teams/#remove-a-repository-from-a-team) (:write) -- [`GET /teams/:team_id/teams`](/v3/teams/#list-child-teams) (:read) - -### Permiso sobre la "administración de la oprganización" - -- [`PATCH /orgs/:org`](/v3/orgs/#update-an-organization) (:write) -{% if currentVersion == "free-pro-team@latest" %} -- [`GET /orgs/:org/interaction-limits`](/v3/interactions/orgs/#get-interaction-restrictions-for-an-organization) (:read) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`PUT /orgs/:org/interaction-limits`](/v3/interactions/orgs/#set-interaction-restrictions-for-an-organization) (:write) -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -- [`DELETE /orgs/:org/interaction-limits`](/v3/interactions/orgs/#remove-interaction-restrictions-for-an-organization) (:write) -{% endif %} - -### Permiso sobre los "ganchos de la organización" - -- [`GET /orgs/:org/hooks`](/v3/orgs/hooks/#list-organization-webhooks) (:read) -- [`POST /orgs/:org/hooks`](/v3/orgs/hooks/#create-an-organization-webhook) (:write) -- [`GET /orgs/:org/hooks/:hook_id`](/v3/orgs/hooks/#get-an-organization-webhook) (:read) -- [`PATCH /orgs/:org/hooks/:hook_id`](/v3/orgs/hooks/#update-an-organization-webhook) (:write) -- [`DELETE /orgs/:org/hooks/:hook_id`](/v3/orgs/hooks/#delete-an-organization-webhook) (:write) -- [`POST /orgs/:org/hooks/:hook_id/pings`](/v3/orgs/hooks/#ping-an-organization-webhook) (:write) - -_Equipos_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) - -{% if currentVersion != "free-pro-team@latest" %} -### Permiso sobre los "ganchos de pre-recepción de la organización" - -- [`GET /orgs/:org/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) (:read) -- [`GET /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) (:read) -- [`PATCH /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) (:write) -- [`DELETE /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) (:write) -{% endif %} - -### Permiso sobre los "proyectos de la organización" - -- [`POST /orgs/:org/projects`](/v3/projects/#create-an-organization-project) (:write) -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) - -{% if currentVersion == "free-pro-team@latest" %} -### Permiso sobre el "bloqueo de usuarios de la organización" - -- [`GET /orgs/:org/blocks`](/v3/orgs/blocking/#list-users-blocked-by-an-organization) (:read) -- [`GET /orgs/:org/blocks/:username`](/v3/orgs/blocking/#check-if-a-user-is-blocked-by-an-organization) (:read) -- [`PUT /orgs/:org/blocks/:username`](/v3/orgs/blocking/#block-a-user-from-an-organization) (:write) -- [`DELETE /orgs/:org/blocks/:username`](/v3/orgs/blocking/#unblock-a-user-from-an-organization) (:write) -{% endif %} - -### Permiso sobre las "páginas" - -- [`GET /repos/:owner/:repo/pages`](/v3/repos/pages/#get-a-github-pages-site) (:read) -- [`POST /repos/:owner/:repo/pages`](/v3/repos/pages/#create-a-github-pages-site) (:write) -- [`PUT /repos/:owner/:repo/pages`](/v3/repos/pages/#update-information-about-a-github-pages-site) (:write) -- [`DELETE /repos/:owner/:repo/pages`](/v3/repos/pages/#delete-a-github-pages-site) (:write) -- [`GET /repos/:owner/:repo/pages/builds`](/v3/repos/pages/#list-github-pages-builds) (:read) -- [`POST /repos/:owner/:repo/pages/builds`](/v3/repos/pages/#request-a-github-pages-build) (:write) -- [`GET /repos/:owner/:repo/pages/builds/:build_id`](/v3/repos/pages/#get-github-pages-build) (:read) -- [`GET /repos/:owner/:repo/pages/builds/latest`](/v3/repos/pages/#get-latest-pages-build) (:read) - -### Permiso sobre las "solicitudes de extracción" - -Las solicitudes de extracción y los informes de problemas tienen una relación estrecha. Si tu GitHub App tiene permisos sobre las solicitudes de extracción pero no sobre los informes de problemas, estas terminales se limitarán a las solicitudes de extracción. Se filtrarán las terminales que devuelvan tanto informes de problemas como solicitudes de extracción. Las terminales que permitan operaciones tanto en solicitudes de extracción como en informes de problemas se restringirán a las solicitudes de extracción únicamente. - -- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/v3/issues/#update-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#list-issue-comments) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/v3/issues/comments/#create-an-issue-comment) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#lock-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/v3/issues/#unlock-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/v3/issues/timeline/#list-timeline-events-for-an-issue) (:read) -- [`GET /repos/:owner/:repo/issues/comments`](/v3/issues/comments/#list-issue-comments-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#get-an-issue-comment) (:read) -- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#update-an-issue-comment) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/v3/issues/comments/#delete-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls`](/v3/pulls/#list-pull-requests) (:read) -- [`POST /repos/:owner/:repo/pulls`](/v3/pulls/#create-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#get-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/v3/pulls/#update-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#list-review-comments-on-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/v3/pulls/comments/#create-a-review-comment-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/v3/pulls/#list-commits-on-a-pull-request) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/v3/pulls/#list-pull-requests-files) (:read) -- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/v3/pulls/#check-if-a-pull-request-has-been-merged) (:read) -- [`GET /repos/:owner/:repo/pulls/comments`](/v3/pulls/comments/#list-review-comments-in-a-repository) (:read) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#get-a-review-comment-for-a-pull-request) (:read) -- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#update-a-review-comment-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/v3/pulls/comments/#delete-a-review-comment-for-a-pull-request) (:write) - -_Asignatarios_ -- [`GET /repos/:owner/:repo/assignees`](/v3/issues/assignees/#list-assignees) (:read) -- [`GET /repos/:owner/:repo/assignees/:username`](/v3/issues/assignees/#check-if-a-user-can-be-assigned) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#add-assignees-to-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/v3/issues/assignees/#remove-assignees-from-an-issue) (:write) - -_Eventos_ -- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/v3/issues/events/#list-issue-events) (:read) -- [`GET /repos/:owner/:repo/issues/events/:event_id`](/v3/issues/events/#get-an-issue-event) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/v3/pulls/reviews/#submit-a-review-for-a-pull-request) (:write) - -_Etiquetas_ -- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#list-labels-for-an-issue) (:read) -- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#add-labels-to-an-issue) (:write) -- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#set-labels-for-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/v3/issues/labels/#remove-all-labels-from-an-issue) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/v3/issues/labels/#remove-a-label-from-an-issue) (:write) -- [`GET /repos/:owner/:repo/labels`](/v3/issues/labels/#list-labels-for-a-repository) (:read) -- [`POST /repos/:owner/:repo/labels`](/v3/issues/labels/#create-a-label) (:write) -- [`GET /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#get-a-label) (:read) -- [`PATCH /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#update-a-label) (:write) -- [`DELETE /repos/:owner/:repo/labels/:name`](/v3/issues/labels/#delete-a-label) (:write) - -_Hitos_ -- [`GET /repos/:owner/:repo/milestones`](/v3/issues/milestones/#list-milestones) (:read) -- [`POST /repos/:owner/:repo/milestones`](/v3/issues/milestones/#create-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#get-a-milestone) (:read) -- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#update-a-milestone) (:write) -- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/v3/issues/milestones/#delete-a-milestone) (:write) -- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/v3/issues/labels/#list-labels-for-issues-in-a-milestone) (:read) - -_Reacciones_ -- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/v3/reactions/#create-reaction-for-an-issue) (:write) -- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-an-issue-comment) (:read) -- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-an-issue-comment) (:write) -- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#list-reactions-for-a-pull-request-review-comment) (:read) -- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/v3/reactions/#create-reaction-for-a-pull-request-review-comment) (:write) -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} -- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction-legacy) (:write) -- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-commit-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-reaction) (:write) -- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-an-issue-comment-reaction) (:write) -- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/v3/reactions/#delete-a-pull-request-comment-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-reaction) (:write) -- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/v3/reactions/#delete-team-discussion-comment-reaction) (:write){% else %}- [`DELETE /reactions/:reaction_id`](/v3/reactions/#delete-a-reaction) (:write){% endif %} - -_Revisores solicitados_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#list-requested-reviewers-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#request-reviewers-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/v3/pulls/review_requests/#remove-requested-reviewers-from-a-pull-request) (:write) - -_Revisiones_ -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#list-reviews-for-a-pull-request) (:read) -- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/v3/pulls/reviews/#create-a-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#get-a-review-for-a-pull-request) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#update-a-review-for-a-pull-request) (:write) -- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/v3/pulls/reviews/#delete-a-pending-review-for-a-pull-request) (:write) -- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/v3/pulls/reviews/#list-comments-for-a-pull-request-review) (:read) -- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/v3/pulls/reviews/#dismiss-a-review-for-a-pull-request) (:write) - -### Permisos sobre los "ganchos del repositorio" - -- [`GET /repos/:owner/:repo/hooks`](/v3/repos/hooks/#list-repository-webhooks) (:read) -- [`POST /repos/:owner/:repo/hooks`](/v3/repos/hooks/#create-a-repository-webhook) (:write) -- [`GET /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#get-a-repository-webhook) (:read) -- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#update-a-repository-webhook) (:write) -- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/v3/repos/hooks/#delete-a-repository-webhook) (:write) -- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/v3/repos/hooks/#ping-a-repository-webhook) (:read) -- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/v3/repos/hooks/#test-the-push-repository-webhook) (:read) - -{% if currentVersion != "free-pro-team@latest" %} -### Permiso sobre los "ganchos de pre-recepción del repositorio" - -- [`GET /repos/:owner/:repo/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) (:read) -- [`PATCH /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) (:write) -- [`DELETE /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) (:write) -{% endif %} - -### Permiso sobre los "proyectos del repositorio" - -- [`GET /projects/:project_id`](/v3/projects/#get-a-project) (:read) -- [`PATCH /projects/:project_id`](/v3/projects/#update-a-project) (:write) -- [`DELETE /projects/:project_id`](/v3/projects/#delete-a-project) (:write) -- [`POST /projects/:project_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`GET /projects/:project_id/columns`](/v3/projects/columns/#list-project-columns) (:read) -- [`POST /projects/:project_id/columns`](/v3/projects/columns/#create-a-project-column) (:write) -- [`GET /projects/columns/:column_id`](/v3/projects/columns/#get-a-project-column) (:read) -- [`PATCH /projects/columns/:column_id`](/v3/projects/columns/#update-a-project-column) (:write) -- [`DELETE /projects/columns/:column_id`](/v3/projects/columns/#delete-a-project-column) (:write) -- [`GET /projects/columns/:column_id/cards`](/v3/projects/cards/#list-project-cards) (:read) -- [`POST /projects/columns/:column_id/cards`](/v3/projects/cards/#create-a-project-card) (:write) -- [`POST /projects/columns/:column_id/moves`](/v3/projects/columns/#move-a-project-column) (:write) -- [`GET /projects/columns/cards/:card_id`](/v3/projects/cards/#get-a-project-card) (:read) -- [`PATCH /projects/columns/cards/:card_id`](/v3/projects/cards/#update-a-project-card) (:write) -- [`DELETE /projects/columns/cards/:card_id`](/v3/projects/cards/#delete-a-project-card) (:write) -- [`POST /projects/columns/cards/:card_id/moves`](/v3/projects/cards/#move-a-project-card) (:write) -- [`GET /repos/:owner/:repo/projects`](/v3/projects/#list-repository-projects) (:read) -- [`POST /repos/:owner/:repo/projects`](/v3/projects/#create-a-repository-project) (:write) - -_Equipos_ -- [`DELETE /teams/:team_id/projects/:project_id`](/v3/teams/#remove-a-project-from-a-team) (:read) - -{% if currentVersion == "free-pro-team@latest" %} -### Permiso sobre los "secretos" - -* [`GET /repos/:owner/:repo/actions/secrets/public-key`](/v3/actions/secrets/#get-a-repository-public-key) (:read) -* [`GET /repos/:owner/:repo/actions/secrets`](/v3/actions/secrets/#list-repository-secrets) (:read) -* [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#get-a-repository-secret) (:read) -* [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-a-repository-secret) (:write) -* [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-a-repository-secret) (:write) -* [`GET /orgs/:org/actions/secrets/public-key`](/v3/actions/secrets/#get-an-organization-public-key) (:read) -* [`GET /orgs/:org/actions/secrets`](/v3/actions/secrets/#list-organization-secrets) (:read) -* [`GET /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#get-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#create-or-update-an-organization-secret) (:write) -* [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#list-selected-repositories-for-an-organization-secret) (:read) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/v3/actions/secrets/#set-selected-repositories-for-an-organization-secret) (:write) -* [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#add-selected-repository-to-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/v3/actions/secrets/#remove-selected-repository-from-an-organization-secret) (:write) -* [`DELETE /orgs/:org/actions/secrets/:secret_name`](/v3/actions/secrets/#delete-an-organization-secret) (:write) - -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -### Permiso sobre los "eventos de seguridad" - -- [`GET /repos/:owner/:repo/code-scanning/alerts`](/v3/code-scanning/#list-code-scanning-alerts-for-a-repository) (:read) -- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_id`](/v3/code-scanning/#get-a-code-scanning-alert) (:read) -{% endif %} - -{% if currentVersion == "free-pro-team@latest" %} -### Permiso sobre los "ejecutores auto-hospedados" -- [`GET /orgs/:org/actions/runners/downloads`](/v3/actions/self-hosted-runners/#list-runner-applications-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/registration-token`](/v3/actions/self-hosted-runners/#create-a-registration-token-for-an-organization) (:write) -- [`GET /orgs/:org/actions/runners`](/v3/actions/self-hosted-runners/#list-self-hosted-runners-for-an-organization) (:read) -- [`GET /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#get-a-self-hosted-runner-for-an-organization) (:read) -- [`POST /orgs/:org/actions/runners/remove-token`](/v3/actions/self-hosted-runners/#create-a-remove-token-for-an-organization) (:write) -- [`DELETE /orgs/:org/actions/runners/:runner_id`](/v3/actions/self-hosted-runners/#delete-a-self-hosted-runner-from-an-organization) (:write) -{% endif %} - -### Permiso sobre "un archivo" - -- [`GET /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#get-repository-content) (:read) -- [`PUT /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#create-or-update-file-contents) (:write) -- [`DELETE /repos/:owner/:repo/contents/:path`](/v3/repos/contents/#delete-a-file) (:write) - -### Permiso sobre el "marcar con una estrella" - -- [`GET /user/starred/:owner/:repo`](/v3/activity/starring/#check-if-a-repository-is-starred-by-the-authenticated-user) (:read) -- [`PUT /user/starred/:owner/:repo`](/v3/activity/starring/#star-a-repository-for-the-authenticated-user) (:write) -- [`DELETE /user/starred/:owner/:repo`](/v3/activity/starring/#unstar-a-repository-for-the-authenticated-user) (:write) - -### Permiso sobre los "estados" - -- [`GET /repos/:owner/:repo/commits/:ref/status`](/v3/repos/statuses/#get-the-combined-status-for-a-specific-reference) (:read) -- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/v3/repos/statuses/#list-commit-statuses-for-a-reference) (:read) -- [`POST /repos/:owner/:repo/statuses/:sha`](/v3/repos/statuses/#create-a-commit-status) (:write) - -### Permiso sobre los "debates de equipo" - -- [`GET /teams/:team_id/discussions`](/v3/teams/discussions/#list-discussions) (:read) -- [`POST /teams/:team_id/discussions`](/v3/teams/discussions/#create-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#get-a-discussion) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#update-a-discussion) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number`](/v3/teams/discussions/#delete-a-discussion) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#list-discussion-comments) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/v3/teams/discussion_comments/#create-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#get-a-discussion-comment) (:read) -- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#update-a-discussion-comment) (:write) -- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/v3/teams/discussion_comments/#delete-a-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion-comment) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion-comment) (:write) -- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#list-reactions-for-a-team-discussion) (:read) -- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/v3/reactions/#create-reaction-for-a-team-discussion) (:write) diff --git a/translations/es-XL/content/rest/reference/projects.md b/translations/es-XL/content/rest/reference/projects.md deleted file mode 100644 index e50da23dd1..0000000000 --- a/translations/es-XL/content/rest/reference/projects.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: Proyectos -redirect_from: - - /v3/projects -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Tarjetas - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'cards' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Colaboradores - -Esta API te permite interactuar con los proyectos de una organización. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Columnas - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'columns' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/pulls.md b/translations/es-XL/content/rest/reference/pulls.md deleted file mode 100644 index c01502ab86..0000000000 --- a/translations/es-XL/content/rest/reference/pulls.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: Extracciones -redirect_from: - - /v3/pulls -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -La API de Solicitudes de Extracción te permite listar, ver, editar, crear e incluso fusionar solicitudes de extracción. Los comentarios en las solicitudes de extracción se pueden administrar a través de la [API de Comentarios de los Informes de Problemas](/rest/reference/issues#comments). - -Cada solicitud de extracción es un informe de problemas, pero no todos los informes de problemas son una solicitud de extracción. Es por esto que las acciones "compartidas" para ambas características, como el manipular a los asignados, etiquetas e hitos, se proporcionan dentro de la [API de Informes de Problemas](/v3/issues). - -### Tipos de medios personalizados para las solicitudes de extracción - -Estos son los tipos de medios compatibles para las solicitudes de extracción. - - application/vnd.github.VERSION.raw+json - application/vnd.github.VERSION.text+json - application/vnd.github.VERSION.html+json - application/vnd.github.VERSION.full+json - application/vnd.github.VERSION.diff - application/vnd.github.VERSION.patch - -Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". - - - -Si existe alguna diff que se haya dañado, contacta a {% data variables.contact.contact_support %}. Incluye el nombre del repositorio y la ID de la solicitud de extracción en tu mensaje. - -### Relaciones de los enlaces - -Las solicitudes de extracción tienen estas posibles relaciones de enlaces: - -| Nombre | Descripción | -| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `self` | La ubicación de la API para esta Solicitud de Extracción. | -| `html` | La ubicación de HTML para esta Solicitud de Extracción. | -| `propuesta` | La ubicación de la API para el [informe de problemas](/v3/issues/) de esta Solicitud de Extracción. | -| `comentarios` | La ubicación de la API para los [Comentarios del informe de problemas](/v3/issues/comments/) de esta Solicitud de Extracción. | -| `review_comments` | La ubicación de la API para los [Comentarios de revisión](/v3/pulls/comments/) de esta Solicitud de Extracción. | -| `review_comment` | La [plantilla de URL](/v3/#hypermedia) para construir la ubicación de la API para un [Comentario de revisión](/v3/pulls/comments/) en el repositorio de esta Solicitud de Extracción. | -| `commits` | La ubicación de la API para las [confirmaciones](#list-commits-on-a-pull-request) de esta solicitud de extracción. | -| `estados` | La ubicación de la API para los [estados de las confirmaciones](/v3/repos/statuses/) de esta Solicitud de Extracción, los cuales son los estados de su rama `head`. | - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Revisiones - -Las revisiones de las solicitudes de extracción son grupos de Comentarios de Revisión de las Solicitudes de Extracción en las mismas, los cuales se agrupan con un estado y, opcionalmente, con un comentario en el cuerpo. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'reviews' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Comentarios de revisión - -Los comentarios de revisión de las solicitudes de extracción son comentarios de una porción de la diff unificada durante la revisión de esta solicitud. Los comentarios de confirmación y comentarios de la solicitud de extracción son diferentes de aquellos sobre la revisión de estas solicitudes. Se aplican comentarios de confirmación directamente a un confirmación, así como se aplican comentarios del informe de problemas sin referenciar una porción de la diff unificada. Para obtener más información, consulta las secciones "[Crear un comentario sobre una confirmación](/rest/reference/git#create-a-commit)" y "[Crear un comentario sobre un informe de problemas](/rest/reference/issues#create-an-issue-comment)". - -### Tipos de medios personalizados para los comentarios sobre las revisiones de las solicitudes de extracción - -Estos son los tipos de medios compatibles para los comentarios sobre las revisiones de las solicitudes de exstracción. - - application/vnd.github.VERSION.raw+json - application/vnd.github.VERSION.text+json - application/vnd.github.VERSION.html+json - application/vnd.github.VERSION.full+json - -Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Solicitudes de revisión - -Los autores de las solicitudes de extracción y los propietarios y colaboradores de los repositorios pueden solicitar una revisión de una solicitud de extracción a cualquiera con acceso de escritura en el repositorio. Cada revisor solicitado recibirá una notificación solicitándoles revisar la solicitud de extracción. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'review-requests' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/rate-limit.md b/translations/es-XL/content/rest/reference/rate-limit.md deleted file mode 100644 index 5f11369b58..0000000000 --- a/translations/es-XL/content/rest/reference/rate-limit.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Limite de tasa -redirect_from: - - /v3/rate_limit - - /v3/rate-limit -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -La documentación general de la API de REST describe las [reglas de los límites de tasa](/rest/overview/resources-in-the-rest-api#rate-limiting). Puedes revisar tu estado actual de límite de tasa en cualquier momento utilizando la API de Límites de Tasa que se describe a continuación. - -### Entender el estado de tu límite de tasa - -La API de Búsqueda tiene un [límite de tasa personalizado](/v3/search/#rate-limit) separado de aquél que rige el resto de la API de REST. La API de GraphQL también tiene un [límite de tasa personalizado](/v4/guides/resource-limitations/#rate-limit) que está separado y se calcula diferente que los límites de tasa de la API de REST. - -Es por esto que la respuesta de la API de Límites de Tasa categoriza tu límite de tasa. Debajo de `resources`, verás cuatro objetos: - -* El objeto `core` proporciona tu estado de límite de tasa para todos los recursos no relacionados a búsquedas en la API de REST. - -* El objeto `search` proporciona el estado de tu límite de tasa para la [API de Búsqueda](/v3/search/). - -* El objeto `graphql` proporciona el estado de tu límite de tasa para la [API de GraphQL](/v4/). - -* El objeto `integration_manifest` proporciona el estado de tu límite de tasa para la terminal [Conversión de código para el Manifiesto de GitHub App](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration). - -Para obtener más información sobre los valores y encabezados en la respuesta de límite de tasa, consulta la sección "[Limitar las tasas](/v3/#rate-limiting)". - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/reactions.md b/translations/es-XL/content/rest/reference/reactions.md deleted file mode 100644 index 3c98c78004..0000000000 --- a/translations/es-XL/content/rest/reference/reactions.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Reacciones -redirect_from: - - /v3/reactions -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -### Tipos de reacción - -Cuando creas una reacción, los valores permitidos para el parámetro `content` son los siguientes (con el emoji correspondiente como referencia): - -{% data reusables.repositories.reaction_list %} - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/repos.md b/translations/es-XL/content/rest/reference/repos.md deleted file mode 100644 index a4cc776b5b..0000000000 --- a/translations/es-XL/content/rest/reference/repos.md +++ /dev/null @@ -1,330 +0,0 @@ ---- -title: Repositorios -allowTitleToDifferFromFilename: true -redirect_from: - - /v3/repos -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Ramas - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'branches' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Colaboradores - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'collaborators' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Comentarios - -### Tipos de medios personalizados para los comentarios de las confirmaciones - -Estos son los tipos de medios compatibles para los comentarios de las confirmaciones. Puedes leer más acerca del uso de los tipos de medios en la API [aquí](/v3/media/). - - application/vnd.github-commitcomment.raw+json - application/vnd.github-commitcomment.text+json - application/vnd.github-commitcomment.html+json - application/vnd.github-commitcomment.full+json - -Para obtener más información, consulta la sección "[Tipos de medios personalizados](/rest/overview/media-types)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'comments' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Confirmaciones - -La API de Confirmaciones del Repositorio puede listar, ver y comparar las confirmaciones de un repositorio. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Comunidad - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'community' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Contenido - -Las terminales de esta API te permiten crear, modificar y borrar contenido cifrado en Base64 en un repositorio. Para solicitar el formato sin procesar y interpretado en HTML (cuando sea posible), utiliza los tipos de medios personalizados para el contenido de un repositorio. - -### Tipos de medios personalizados para el contenido de un repositorio - -Los [README](/v3/repos/contents/#get-a-repository-readme), [archivos](/v3/repos/contents/#get-repository-content), y [symlinks](/v3/repos/contents/#get-repository-content) son compatibles con los siguientes tipos de medios: - - application/vnd.github.VERSION.raw - application/vnd.github.VERSION.html - -Utiliza el tipo de medios `.raw` para recuperar el contenido del archivo. - -Para archivos de markup tales como Markdown o AsciiDoc, puedes recuperar la interpretación en HTML si utilizas el tipo de medios `.html`. Los lenguajes de Markup se interpretan en HTML utilizando nuestra [biblioteca de Markup](https://github.com/github/markup) de código abierto. - -[Todos los objetos](/v3/repos/contents/#get-repository-content) son compatibles con los siguientes tipos de medios personalizados: - - application/vnd.github.VERSION.object - -Utiliza el parámetro de tipo de medios `object` para recuperar el contenido en un formato de objeto consistente sin importar el tipo de contenido. Por ejemplo, en vez de ser una matriz de objetos para un directorio, la respuesta será un objeto con un atributo de `entries` que contenga la matriz de objetos. - -Puedes leer más acerca del uso de los tipos de medios en la API [aquí](/v3/media/). - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'contents' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Llaves de implementación - -{% data reusables.repositories.deploy-keys %} - -Las llaves de despliegue pueden ya sea configurarse utilizando las siguientes terminales de la API, o mediante GitHub. Para aprender cómo configurar las llaves de despliegue en GitHub, consulta la sección "[Administrar las llaves de despliegue](/developers/overview/managing-deploy-keys)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Implementaciones - -Los despliegues son slicitudes para desplegar una ref específica (rma, SHA, etiqueta). GitHub despliega un [evento de `deployment`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) al que puedan escuchar los servicios externos y al con el cual puedan actuar cuando se creen los despliegues nuevos. Los despliegues habilitan a los desarrolladores y a las organizaciones para crear herramientas sin conexión directa en torno a los despliegues, sin tener que preocuparse acerca de los detalles de implementación de entregar tipos de aplicaciones diferentes (por ejemplo, web o nativas). - -Los estados de despliegue permiten que los servicios externos marquen estos despliegues con un estado de `error`, `failure`, `pending`, `in_progress`, `queued`, o `success` que pueden consumir los sistemas que escuchan a los [eventos de `deployment_status`](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status). - -Los estados de despliegue también incluyen una `description` y una `log_url` opcionales, las cuales se recomiendan ampliamente, ya que hacen que los estados de despliegue sean más útiles. La `log_url` es la URL completa para la salida del despliegue, y la `description` es el resumen de alto nivel de lo que pasó con este despliegue. - -GitHub envía eventos de `deployment` y `deployment_status` cuando se crean despliegues y estados de despliegue nuevos. Estos eventos permiten que las integraciones de terceros reciban respuesta de las solicitudes de despliegue y actualizan el estado de un despliegue conforme éste progrese. - -Debajo encontrarás un diagrama de secuencia simple que explica cómo funcionarían estas interacciones. - -``` -+---------+ +--------+ +-----------+ +-------------+ -| Tooling | | GitHub | | 3rd Party | | Your Server | -+---------+ +--------+ +-----------+ +-------------+ - | | | | - | Create Deployment | | | - |--------------------->| | | - | | | | - | Deployment Created | | | - |<---------------------| | | - | | | | - | | Deployment Event | | - | |---------------------->| | - | | | SSH+Deploys | - | | |-------------------->| - | | | | - | | Deployment Status | | - | |<----------------------| | - | | | | - | | | Deploy Completed | - | | |<--------------------| - | | | | - | | Deployment Status | | - | |<----------------------| | - | | | | -``` - -Ten en cuenta que GitHub jamás accede a tus servidores realmente. La interacción con los eventos de despliegue dependerá de tu integración de terceros. Varios sistemas pueden escuchar a los eventos de despliegue, y depende de cada uno de ellos decidir si son responsables de cargar el código a tus servidores, si crean código nativo, etc. - -Nota que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo_deployment`concede acceso dirigido a los despliegues y estados de despliegue **sin** otorgar acceso al código del repositorio, mientras que los alcances `public_repo` y `repo` otorgan permiso para el código también. - -### Despliegues inactivos - -Cuando configuras el estado de un despliegue como `success`, entonces todos los despliegues de ambiente no productivos y no transitorios previos en el mismo repositorio se pondrán como `inactive`. Para evitar esto, puedes configurar a `auto_inactive` como `false` cuando creas el estado del servidor. - -Puedes comunicar que un ambiente transitorio ya no existe si configuras el `state` como `inactive`. El configurar al `state` como `inactive`muestra el despliegue como `destroyed` en {% data variables.product.prodname_dotcom %} y elimina el acceso al mismo. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Bifurcaciones - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'forks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Invitaciones - -La API de Invitaciones al Repositorio permite a los usuarios o a los servicios externos invitar a otros usuarios para colaborar en un repositorio. Los usuarios invitados (o los servicios externos en nombre de estos) pueden elegir aceptar o rechazar la invitación. - -Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) `repo:invite` otorga un acceso dirigido a las invitaciones **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código así como para las invitaciones. - -### Invitar a un usuario a un repositorio - -Utiliza la terminal de la API para agregar un colaborador. Para obtener más información, consulta la sección "[Agregar un colaborador del repositorio](/rest/reference/repos#add-a-repository-collaborator)". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Fusionar - -La API de Fusión de Repositorios puede fusionar ramas en un repositorio. Esto logra esencialmente lo mismo que el fusionar una rama con otra en un repositorio local para después cargarlo a {% data variables.product.product_name %}. El beneficio es que esta fusión se lleva a cabo del lado del servidor y no se requiere un repositorio local. Esto lo hace más adecuado para la automatización y para otras herramientas mientras que el mantener repositorios locales sería incómodo e ineficiente. - -El usuario autenticado será el autor de cualquier fusión que se realice a través de esta terminal. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'merging' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Pages - -La API de {% data variables.product.prodname_pages %} recupera información sobre tu configuración de {% data variables.product.prodname_pages %} y sobre los estados de tus compilaciones. La información sobre este sitio y sobre las compilaciones solo es accesible mediante los propietarios autenticados, aún cuando los sitios web son públicos. For more information, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages)." - -En las terminales de la API de {% data variables.product.prodname_pages %} que llevan una clave de `status` en su respuesta, el valor puede ser uno de entre los siguientes: -* `null`: El sitio aún tiene que crearse. -* `queued`: Se solicitó la compilación, pero no ha iniciado. -* `building`: La compilación está en curso. -* `built`: Se creó el sitio. -* `errored`: Indica que ocurrió un error durante la compilación. - -En {% data variables.product.prodname_pages %}, las terminales de la API que {% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} son compatibles con el `mister-fantastic-preview` y que {% endif %} devuelven la información de sitio de GitHub Pages, las respuestas de JSON incluyen estos campos: -* `html_url`: La URL absoluta (incluyendo el modelo) del sitio de Páginas que se interpretó. For example, `https://username.github.io`. -* `source`: Un objeto que contiene la rama origen y el directorio del sitio de Páginas que se interpretó. Esto incluye: - - `branch`: La rama del repositorio que se utilizó para publicar los [archivos de código fuente de tu sitio](/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por ejemplo, _master_ o _gh-pages_. - - `path`: El directorio del repositorio desde el cual publica el sitio. Podría ser `/` o `/docs`. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'pages' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Lanzamientos - -{% note %} - -**Nota:** La API de Lanzamientos reemplaza a la API de Descargas. Puedes recuperar el conteo de descargas y la URL de descarga del buscador desde las terminales en esta API, las cuales devuelven los lanzamientos y los activos de éstos. - -{% endnote %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'releases' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Estadísticas - -La API de Estadísticas del Repositorio te permite recuperar los datos que {% data variables.product.product_name %} utiliza para visualizar los diferentes tipos de actividad del repositorio. - -### Unas palabras sobre el almacenamiento en caché - -El calcular las estadísitcas del repositorio es una operación costosa, así que intentamos devolver los datos almacenados en caché cuando nos es posible. Si los datos no se han almacenado en caché cuando consultas la estadística de un repositorio, recibirás una respuesta `202`; también se dispara un job en segundo plano para comenzar a compilar estas estadísticas. Permite que el job se complete, y luego emite la solicitud nuevamente. Si el job ya terminó, esa solicitud recibirá una respuesta `200` con la estadística en el cuerpo de la respuesta. - -Las estadísticas del repositorio se almacenan en caché con el SHA de la rama predeterminada de éste, la cual es habitualmente master; el hacer cargas a la rama predeterminada restablece el caché de las estadísticas. - -### Las estadísticas excluyen algunos tipos de confirmaciones - -Las estadísticas que expone la API empatan con aquellas que muestran [diversas gráficas del repositorio](/github/visualizing-repository-data-with-graphs/about-repository-graphs). - -Para resumir: -- Todas las estadísticas excluyen las confirmaciones de fusión. -- Las estadísticas del colaborador también excluyen a las confirmaciones vacías. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'statistics' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Estados - -La API de estados permite que los servicios externos marquen las confirmaciones con un estado de `error`, `failure`, `pending`, o `success`, el cual se refleja después en las solicitudes de extracción que involucran a esas confirmaciones. - -Los estados también incluyen una `description` y una `target_url` opcionales, y recomendamos ampliamente proporcionarlas, ya que hacen mucho más útiles a los estados en la IU de GitHub. - -Como ejemplo, un uso común es que los servicios de integración contínua marquen a las confirmaciones como compilaciones que pasan o fallan utilizando los estados. La `target_url` sería la URL completa de la salida de la compilación, y la `description` sería el resumen de alto nivel de lo que pasó con la compilación. - -Los estados pueden incluir un `context` para indicar qué servicio está proporcionando ese estado. Por ejemplo, puedes hacer que tu servicio de integración continua cargue estados con un contexto de `ci`, y que una herramienta de auditoria de seguridad cargue estados con un contexto de `security`. Puedes utilizar entonces el [Obtener el estado combinado para una referencia específica](/rest/reference/repos#get-the-combined-status-for-a-specific-reference) para recuperar todo el estado de una confirmación. - -Toma en cuenta que el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps) de `repo:status` otorga acceso dirigido a los estados **sin** otorgar también el acceso al código del repositorio, mientras que el alcance `repo` otorga permisos para el código y también para los estados. - -Si estás desarrollando una GitHub App y quieres proporcionar información más detallada sobre un servicio externo, tal vez quieras utilizar la [API de Verificaciones](/rest/reference/checks). - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Tráfico - -Para los repositorios en los que tienes acceso de carga, la API de tráfico proporciona acceso a la información proporcionada en tu gráfica de repositorio. Para obtener más información, consulta la sección "Ver el tráfico de un repositorio." - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Webhooks - -La API de Webhooks del Repositorio le permite a los administradoresd e un repositorio administrar los ganchos de post-recepción para el mismo. Los webhooks se pueden administrar utilizando la API de HTTP de JSON, o la API de [PubSubHubbub](#PubSubHubbub). - -Si te gustaría configurar un solo webhook para recibir eventos de todos los repositorios de tu organización, consulta nuestra documentación de la API para los [Webhooks de una Organización](/rest/reference/orgs#webhooks). - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'hooks' %}{% include rest_operation %}{% endif %} -{% endfor %} - -### Recibir Webhooks - -Para que {% data variables.product.product_name %} envíe cargas útiles de webhooks, se necesita que se pueda acceder a tu servidor desde la internet. También sugerimos ampliamente utilizar SSL para que podamos enviar cargas útiles cifradas a través de HTTPS. - -#### Encabezados de Webhook - -{% data variables.product.product_name %} enviará varios encabezados de HTTP para diferenciar los tipos de eventos y los identificadores de las cargas útiles. Consulta la sección de [encabezados de webhook](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers) para encontrar más detalles. - -### PubSubHubbub - -GitHub también puede fungir como un centro de [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub) para todos los repositorios. PSHB es un proptocolo simple de publicación/suscripción que permite a los servidores registrarse para recibir actualizaciones de cuándo se actualiza un tema. Las actualizaciones se mandan con una solicitud HTTP de tipo POST a una URL de rellamado. Las URL de tema para las cargas a un repositorio de GitHub están en este formato: - -`https://github.com/{owner}/{repo}/events/{event}` - -El veneto puede ser cualquier evento de webhook disponible. Para obtener más información, consulta la sección "[eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhook-events-and-payloads)". - -#### Formato de respuesta - -El formato predeterminado es lo que [deberían esperar los ganchos de pre-recepción existentes](/post-receive-hooks/): Un cuerpo de JSON que se envía como parámetro de `payload` en un POST. También puedes especificar si quieres recibir el cuerpo en JSON sin procesar, ya sea un encabezado de `Accept` o una extensión `.json`. - - Accept: application/json - https://github.com/{owner}/{repo}/events/push.json - -#### URL de Rellamado -Las URL de rellamado puede utilizar el protocolo `http://`. - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %}También puedes hacer rellamados de `github://` para especificar un servicio de GitHub. -{% data reusables.apps.deprecating_github_services_ghe %} -{% endif %} - - # Send updates to postbin.org - http://postbin.org/123 - -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %} - # Send updates to Campfire github://campfire?subdomain=github&room=Commits&token=abc123 -{% endif %} - -#### Suscribirse - -La terminal de PubSubHubbub de GitHub es: `{% data variables.product.api_url_code %}/hub`. Una solicitud exitosa con curl se vería así: - -``` shell -curl -u "user" -i \ - {% data variables.product.api_url_pre %}/hub \ - -F "hub.mode=subscribe" \ - -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \ - -F "hub.callback=http://postbin.org/123" -``` - -Las solicitudes de PubSubHubbub pueden enviarse varias veces. Si el gancho ya existe, se modificará de acuerdo con la solicitud. - -##### Parámetros - -| Nombre | Tipo | Descripción | -| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `hub.mode` | `secuencia` | **Requerido**. Ya sea `subscribe` o `unsubscribe`. | -| `hub.topic` | `secuencia` | **Requerido**. La URI del repositorio de GitHub al cual suscribirse. La ruta debe estar en el formato `/{owner}/{repo}/events/{event}`. | -| `hub.callback` | `secuencia` | La URI para recibir las actualizaciones del tema. | -| `hub.secret` | `secuencia` | Una llave secreta compartida que genera un HMAC de SHA1 del contenido del cuerpo de salida. Puedes verificar si una carga vino de GitHub si comparas el cuerpo de la solicitud sin procesar con el contenido del encabezado `X-Hub-Signature`. Puedes ver [la documentación de PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obtener más detalles. | diff --git a/translations/es-XL/content/rest/reference/scim.md b/translations/es-XL/content/rest/reference/scim.md deleted file mode 100644 index 54274806a5..0000000000 --- a/translations/es-XL/content/rest/reference/scim.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: SCIM -redirect_from: - - /v3/scim -versions: - fpt: '*' -topics: - - API ---- - -### Aprovisionamiento de SCIM para las Organizaciones - -Los proveedores de identidad (IdP) habilitados para SCIM utilizan la API de SCIM para automatizar el aprovisionamiento de la membrecía de las organizaciones de {% data variables.product.product_name %}. 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/). La terminal de SCIM de {% data variables.product.product_name %} que deben utilizar los IdP es: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`. - -{% note %} - -**Nota:** La API de SCIM está disponible solo para las organizaciones en [{% data variables.product.prodname_ghe_cloud %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts) que tienen habilitado el [SSO de SAML](/v3/auth/#authenticating-for-saml-sso). Para obtener más información acerca de SCIM, consulta "[Acerca de SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)". - -{% endnote %} - -### Autenticar las llamadas a la API de SCIM - -Debes autenticarte como un propietario de una organización de {% data variables.product.product_name %} para utilizar la 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 puedes utilizar un token de acceso personal, pero primero debes [autorizarlo para su uso con tu orgnización que cuenta con el SSO 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. - -### Atributos de Usuario de SCIM compatibles - -| Nombre | Tipo | Descripción | -| ---------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `userName` | `secuencia` | El nombre de usuario para el usuario. | -| `name.givenName` | `secuencia` | El primer nombre del usuario. | -| `name.lastName` | `secuencia` | El apellido del usuario. | -| `correos electrónicos` | `array` | Lista de correos electrónicos del usuario. | -| `externalId` | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` de un usuario ya sea con el proveedor de SAML, o utilizando la terminal de [Listar las identidades aprovisionadas de SCIM](#list-scim-provisioned-identities) y filtrando otros atributos conocidos, tales como el nombre de usuario de GitHub o la dirección de correo electrónico de un usuario. | -| `id` | `secuencia` | Identificador que genera la terminal de SCIM de GitHub. | -| `active` | `boolean` | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false). | - -{% note %} - -**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/organizations/{org}/Users/{scim_user_id} -``` - -{% endnote %} - -{% include rest_operations_at_current_path %} diff --git a/translations/es-XL/content/rest/reference/search.md b/translations/es-XL/content/rest/reference/search.md deleted file mode 100644 index 20f1eaf5bd..0000000000 --- a/translations/es-XL/content/rest/reference/search.md +++ /dev/null @@ -1,153 +0,0 @@ ---- -title: Buscar -redirect_from: - - /v3/search -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -La API de Búsqueda te ayuda a buscar el elemento específico que quieres encontrar. Por ejemplo, puedes buscar un usuario o un archivo específico en el repositorio. Tómalo como el simil de realizar una búsqueda en Google. Se diseñó para ayudarte a encontrar el resultado exacto que estás buscando (o tal vez algunos de los resultados que buscas). Tal como la búsqueda en Google, a veces quieres ver algunas páginas de los resultados de búsqueda para que puedas encontrar el elemento que mejor satisfaga tus necesidades. Para satisfacer esta necesidad, la API de Búsqueda de {% data variables.product.product_name %} proporciona **hasta 1,000 resultados por búsqueda**. - -Puedes delimitar tu búsqueda utilizando consultas. Para aprender más sobre la sintaxis de las consultas de búsqueda, dirígete a "[Construir una consulta de búsqueda](/v3/search/#constructing-a-search-query)". - -### Clasificar los resultados de la búsqueda - -A menos de que se proporcione algún otro tipo de opción como parámetro de consulta, los resultados se clasificarán de acuerdo a la exactitud de la coincidencia en orden descendente. Varios factores se combinan para impulsar el elemento más relevante hasta arriba de la lista de resultados. - -### Limite de tasa - -La API de Búsqueda tiene un límite de tasa personalizado. Para las solicitudes que utilizan [Autenticación Básica](/v3/#authentication), [OAuth](/v3/#authentication), o [secreto e ID de cliente](/v3/#increasing-the-unauthenticated-rate-limit-for-oauth-applications), puedes hacer hasta 30 solicitudes por minuto. Para las solicitudes sin autenticar, el límite de tasa te permite hacer hasta 10 por minuto. - -{% data reusables.enterprise.rate_limit %} - -Consulta la [documentación del límite de tasa](/rest/reference/rate-limit) para obtener más detalles sobre cómo determinar tu estado de límite de tasa actual. - -### Construir una consulta de búsqueda - -Cada terminal en la API de búsqueda utiliza [parámetros de búsqueda](https://en.wikipedia.org/wiki/Query_string) para realizar búsqeudas en {% data variables.product.product_name %}. Observa la terminal individual an la API de Búsqueda para encontrar un ejemplo que incluye los parámetros de consulta y de terminal. - -Una consulta puede contener cualquier combinación de calificadores de búsqueda compatibles con GitHub.com. El formato de esta consulta de búsqueda es: - -``` -q=SEARCH_KEYWORD_1+SEARCH_KEYWORD_N+QUALIFIER_1+QUALIFIER_N -``` - -Por ejemplo, si quisieras buscar todos los _repositorios_ que pertenecen a `defunkt` y que contienen la palabra `GitHub` y `Octocat` en el archivo de README, utilizarías la siguiente consulta con la terminal de _buscar repositorios_: - -``` -q=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/)". - -### Limitaciones sobre la longitud de la consulta - -La API de búsqueda no es compatible con consultas que: -- sean mayores a 256 caracteres (sin incluir los operadores o calificativos). -- tengan más de cinco operadores de `AND`, `OR`, o `NOT`. - -Estas consultas de búsqueda devolverán un mensaje de error de "Validation failed". - -### Tiempos excedidos y resultados incompletos - -Para que la API de Búsqueda se mantenga rápida para todos, limitamos el tiempo que puede jecutarse cualquier consulta específica. Para las consultas que [exceden el límite de tiempo](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), la API devuelve las coincidencias que ya se habían encontrado antes de exceder el tiempo, y la respuesta tiene la propiedad `incomplete_results` como `true`. - -Llegar a una interrupción no necesariamente significa que los resultados de búsqueda estén incompletos. Puede que se hayan encontrado más resultados, pero también puede que no. - -### Errores de acceso o resultados de búsqueda faltantes - -Necesitas autenticarte exitosamente y tener acceso a los repositorios en tus consultas de búsqueda, de lo contrario, verás un error de `422 Unprocessible Entry` con un mensaje de "Validation Failed". Por ejemplo, tu búsqueda fallará si tu consulta incluye los calificadores `repo:`, `user:`, o `org:` que solicitan los recursos a los cuales no tienes acceso cuando inicias sesión en {% data variables.product.prodname_dotcom %}. - -Cuando tu consulta de búsqueda solicita recursos múltiples, la respuesta solo contendrá aquellos a los que tengas acceso y **no** proporcionará un mensaje de error que liste los recursos que no se devolvieron. - -Por ejemplo, si tu consulta de búsqueda quiere buscar en los repositorios `octocat/test` y `codertocat/test`, pero solo tienes acceso a `octocat/test`, tu respuesta mostrará los resultados de búsqueda para `octocat/test` y no mostrará nada para `codertocat/test`. Este comportamiento simula cómo funciona la búsqueda en {% data variables.product.prodname_dotcom %}. - -{% include rest_operations_at_current_path %} - - -### Metadatos en el texto coincidente - -En GitHub, puedes utilizar el contexto que te proporcionan los extractos de código y los puntos destacados en los resultados de búsqueda. La API de Búsqueda ofrece metadatos adicionales que te permiten resaltar los términos de búsqueda coincidentes cuando se muestran los resultados de la búsqueda. - -![resaltado del fragmento de código](/assets/images/text-match-search-api.png) - -Las solicitudes pueden decidir recibir esos fragmentos de texto en la respuesta, y cada fragmento se acompaña de intervalos numéricos que identifican la ubicación exacta de cada término de búsqueda coincidente. - -Para obtener estos metadatos en tus resultados de búsqueda, especifica el tipo de medios `text-match` en tu encabezado de `Accept`. - -```shell -application/vnd.github.v3.text-match+json -``` - -Cuando proporcionas el tipo de medios `text-match`, recibirás una clave extra en la carga útil de JSON llamada `text_matches`, la cual proporciona información acerca de la posición de tus términos de búsqueda dentro del texto y la `property` que incluye dicho término de búsqueda. Dentro de la matriz `text_matches`, cada objeto incluye los siguientes atributos: - -| Nombre | Descripción | -| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `object_url` | La URL del recurso que contiene una propiedad de secuencia que empata con uno de los términos de búsqueda. | -| `object_type` | El nombre del tipo de recurso que existe en la `object_url` específica. | -| `propiedad` | El nombre de la propiedad del recurso que existe en la `object_url`. Esa propiedad es una secuencia que empata con uno de los términos de la búsqueda. (En el JSON que se devuelve de la `object_url`, el contenido entero para el `fragment` se encontrará en la propiedad con este nombre.) | -| `fragmento` | Un subconjunto del valor de `property`. Este es el fragmento de texto que empata con uno o más de los términos de búsqueda. | -| `matches` | Una matriz de uno o más términos de búsqueda presentes en el `fragment`. Los índices (es decir, "intervalos") son relativos al fragmento. (No son relativos al contenido _completo_ de `property`.) | - -#### Ejemplo - -Si utilizas cURL y también el [ejemplo de búsqueda de informe de problemas](#search-issues-and-pull-requests) anterior, nuestra solicitud de la API se vería así: - -``` shell -curl -H 'Accept: application/vnd.github.v3.text-match+json' \ -'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc' -``` - -La respuesta incluirá una matriz de `text_matches` para cada resultado de búsqueda. En el JSON que se muestra a continuación, tenemos dos objetos en la matriz `text_matches`. - -La primera coincidencia de texto ocurrió en la propiedad de `body` del informe de problemas. Aquí vemos un fragmento de texto del cuerpo del informe de problemas. El término de búsqueda (`windows`) aparece dos veces dentro de ese fragmento, y tenemos los índices para cada ocurrencia. - -La segunda coincidencia de texto ocurrió en la propiedad `body` de uno de los comentarios del informe de problemas. Tenemos la URL para el comentario del informe de problemas. Y, por supuesto, vemos un fragmento de texto del cuerpo del comentario. El término de búsqueda (`windows`) se muestra una vez dentro de ese fragmento. - -```json -{ - "text_matches": [ - { - "object_url": "https://api.github.com/repositories/215335/issues/132", - "object_type": "Issue", - "property": "body", - "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly distributed windows font that supports them then no problem (we can use html font tags) but otherwise the '(21)' style is probably better.\n", - "matches": [ - { - "text": "windows", - "indices": [ - 14, - 21 - ] - }, - { - "text": "windows", - "indices": [ - 78, - 85 - ] - } - ] - }, - { - "object_url": "https://api.github.com/repositories/215335/issues/comments/25688", - "object_type": "IssueComment", - "property": "body", - "fragment": " right after that are a bit broken IMHO :). I suppose we could have some hack that maxes out at whatever the font does...\n\nI'll check what the state of play is on Windows.\n", - "matches": [ - { - "text": "Windows", - "indices": [ - 163, - 170 - ] - } - ] - } - ] -} -``` diff --git a/translations/es-XL/content/rest/reference/teams.md b/translations/es-XL/content/rest/reference/teams.md deleted file mode 100644 index d38c817fbe..0000000000 --- a/translations/es-XL/content/rest/reference/teams.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Equipos -redirect_from: - - /v3/teams -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -Esta API solo está disponible para los miembros autenticados de la [organization](/v3/orgs) del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`. {% data variables.product.prodname_dotcom %} genera el `slug` del equipo a partir del `name` del mismo. - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Debates - -La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Puedes utilizar los debates de equipo para sostener conversaciones que no son específicas de un repositorio o proyecto. Cualquier miembro de la [organización](/v3/orgs) del equipo puede crear y leer las publicaciones de debates públicos. La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Puedes utilizar los debates de equipo para sostener conversaciones que no son específicas de un repositorio o proyecto. Esta API solo está disponible para los miembros autenticados de la organization del equipo. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'discussions' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Comentarios de debate - -La API de comentarios para debates de equipo te permite obtener, crear, editar y borrar los comentarios del debate en una publicación de un [debate de equipo](/v3/teams/discussions). Cualquier miembro de la [organización](/v3/orgs) del equipo puede crear y leer los comentarios de un debate público. La API de debates de equipo te permite obtener, crear, editar y borrar las publicaciones de un debate en la página de un equipo. Esta API solo está disponible para los miembros autenticados de la organization del equipo. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'discussion-comments' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Miembros - -Esta API solo está disponible para los miembros autenticados de la organization del equipo. Los tokens de acceso de OAuth requieren el [alcance](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) `read:org`. - -{% note %} - -**Nota:** Cuando configuras la sincornizacion de equipos para un equipo con el proveedor de identidad (IdP) de tu organización, verás un error si intentas utilizar la API para hacer cambios en la membrecía de dicho equipo. Si tienes acceso para administrar las membrecías de usuario en tu IdP, puedes administrar la membrecía del equipo de GitHub a través de tu proveedor de identidad, lo cual agrega y elimina automáticamente a los miembros en una organización. Para obtener más información, consulta la sección "Sincronizar equipos entre tu proveedor de identidad y GitHub". - -{% endnote %} - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Sincronización de equipos - -La API de sincronización de equipos te permite administrar las conexiones entre los equipos de {% data variables.product.product_name %} y los grupos del proveedor de identidad (IdP) externo. Para utilizar esta API, el usuario autenticado debe ser un mantenedor del equipo o un propietario de la organización asociada con éste. El token que utilizas para autenticarte también necesitará autorizarse para su uso con tu proveedor IdP (SSO). Para obtener más información, consulta la sección "Autorizar un token de acceso personal para su uso con una organización que tiene inicio de sesión único de SAML". - -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". - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/content/rest/reference/users.md b/translations/es-XL/content/rest/reference/users.md deleted file mode 100644 index 4f0dad35a8..0000000000 --- a/translations/es-XL/content/rest/reference/users.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Usuarios -redirect_from: - - /v3/users -versions: - fpt: '*' - ghes: '*' - ghae: '*' -topics: - - API ---- - -Muchos de los recursos en la API de los usuarios proporcionan un atajo para obtener información acerca del usuario autenticado actualmente. Si una URL de solicitud no incluye un parámetro de `{username}`, entonces la respuesta será para el usuario que inició sesión (y deberás pasar la [información de autenticación](/rest/overview/resources-in-the-rest-api#authentication) con tu solicitud). La información privada adicional, tal como si un usuario habilitó la autenticación de dos factores, se incluye cuando ingresó con la autenticación básica o con OAuth con el alcance de `user`. - -{% for operation in currentRestOperations %} - {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} -{% endfor %} - -## Bloquear usuarios - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Emails (Correos electrónicos) - -Administrar las direcciones de correo electrónico a través de la API requiere que ingreses con la autenticación básica o con OAuth con un alcance correcto para la terminal. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'emails' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Seguidores - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'followers' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Llaves SSH de Git - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'keys' %}{% include rest_operation %}{% endif %} -{% endfor %} - -## Claves GPG - -Los datos que se devuelven en el campo de respuesta de `public_key` no son una llave con formato de GPG. Cuando un usuario carga una llave GPG, se interpreta y la llave pública criptográfica se extrae y se almacena. Esta llave criptográfica es lo que devuelven las API en esta página. Esta llave no es apta para utilizarse directamente con programas como GPG. - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'gpg-keys' %}{% include rest_operation %}{% endif %} -{% endfor %} diff --git a/translations/es-XL/data/glossaries/README.md b/translations/es-XL/data/glossaries/README.md deleted file mode 100644 index 7961aba1f3..0000000000 --- a/translations/es-XL/data/glossaries/README.md +++ /dev/null @@ -1,7 +0,0 @@ -# Glosarios - -Los siguientes archivos comprenden nuestro [Glosario de Crowdin](https://support.crowdin.com/glossary/): - -* `external.yml` contiene las entradas de glosario de cara al usuario. -* `internal.yml` contiene las entradas que solo utilizan los traductores. Estos términos se muestran en la IU de Crowdin para proporcionar contexto adicional a los traductores sobre lo que están traduciendo, además de sugerir una secuencia localizada para ese término. -* `candidates.yml` contiene términos que podrían estar potencialmente tanto en el glosario interno como en el externo, pero no se han definido aún. diff --git a/translations/es-XL/data/glossaries/candidates.yml b/translations/es-XL/data/glossaries/candidates.yml deleted file mode 100644 index 5b6fb6a2f6..0000000000 --- a/translations/es-XL/data/glossaries/candidates.yml +++ /dev/null @@ -1,203 +0,0 @@ ---- -- - term: Soporte prémium -- - term: Soporte estándar -- - term: Incidente -- - term: enviar -- - term: persona de contacto -- - term: Gravedad -- - term: Acuerdo de nivel de servicio -- - term: crédito -- - term: equipo de gestión de cuentas -- - term: ticket -- - term: Soporte empresarial -- - term: portal de soporte -- - term: Urgente -- - term: Alto -- - term: Moderado -- - term: Bajo -- - term: paquete de soporte extendido -- - term: nombre de la empresa -- - term: modo de privacidad -- - term: Método de autenticación -- - term: horas de operación -- - term: liderazgo -- - term: Derivar a la gerencia -- - term: respuestas de tickets perdidos -- - term: Replicación geográfica -- - term: sistema de producción -- - term: datos confidenciales no identificados -- - term: justificación comercial -- - term: Créditos calificados -- - term: Contacto de ventas -- - term: Contacto de capacitación -- - term: Salida -- - term: alfanumérico -- - term: presupuesto -- - term: plan de precios -- - term: plan unitario -- - term: rol -- - term: canjear cupón -- - term: plan gratuito -- - term: gratis -- - term: descuento -- - term: revisión en espera -- - term: crédito de contribución -- - term: marcador de conflicto -- - term: Compromiso de trabajo en curso -- - term: compromiso de antepasado -- - term: gráfico de contribución -- - term: aprobar -- - term: descartar -- - term: etapa -- - term: invitación -- - term: tiempo de actividad -- - term: debate -- - term: política de servicio y privacidad -- - term: reinstalar -- - term: centro de administración -- - term: rol académico -- - term: descuento educativo -- - term: dominio deshechable -- - term: invertir -- - term: cuota -- - term: llave privada -- - term: llave pública -- - term: hotpaching -- - term: característica de lanzamiento -- - term: confirmación conjunta -- - term: aislamiento de subdominio -- - term: autenticación incorporada -- - term: límites de tasa de abuso -- - term: carga promedio -- - term: efímero -- - term: control de prevuelo -- - term: representante de cuenta -- - term: búsqueda unificada -- - term: usuario inactivo -- - term: entrega -- - term: titular legal -- - term: SSO de respuesta no solicitada -- - term: SSO iniciado por IdP -- - term: autenticidad de los mensajes -- - term: Todos los derechos reservados -- - term: Asesores de campus -- - term: Expertos en campus -- - term: modelos de desarrollo colaborativo -- - term: vista unificada -- - term: diferenciación de tres puntos -- - term: dif rica -- - term: conversación -- - term: gist público/secreto -- - term: extensión -- - term: empresas de contratación -- - term: pedidos de renovación -- - term: precio por usuario -- - term: observador -- - term: Firma de confirmación requerida -- - term: Comprobar Suites -- - term: descuento para aulas -- - term: paquete de desarrollo para estudiantes -- - term: descuento de investigación académica -- - term: Stargazers -- - term: spam sin salida diff --git a/translations/es-XL/data/glossaries/external.yml b/translations/es-XL/data/glossaries/external.yml deleted file mode 100644 index b28af95451..0000000000 --- a/translations/es-XL/data/glossaries/external.yml +++ /dev/null @@ -1,758 +0,0 @@ ---- -- - term: '@mención' - description: para notificar a una persona en GitHub usando "@" antes de su nombre de usuario. Los usuarios en una organización en GitHub también pueden ser parte de un equipo que puede ser mencionado. -- - term: token de acceso - description: >- - Un token que se usa en lugar de una contraseña cuando se realizan operaciones Git a través de HTTPS con Git en la línea de comandos o la API. También denominado un token de acceso personal. -- - 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. -- - term: Vista previa de API - description: >- - Una manera de probar nuevas API y cambiar a métodos API existentes antes de que se vuelvan parte de la API de GitHub oficial. -- - term: aparato - description: >- - Una aplicación de software combinada con Sólo lo Necesario de un Sistema Operativo (JeOS) para funcionar de manera óptima en el hardware estándar de la industria (generalmente, un servidor) o en una máquina virtual. -- - term: asignatario - description: El usuario que es asignado a una propuesta. -- - term: código de autenticación - description: >- - Un código que suministrarás, además de tu contraseña GitHub, cuando inicias sesión con 2FA a través del buscador. Este código se genera ya sea mediante una aplicación o se envía a tu teléfono mediante un mensaje de texto. También denominado "Código de autenticación 2FA". -- - term: rama base - description: La rama en la que los cambios se combinan cuando fusionas una solicitud de extracción. Cuando creas una solicitud de extracción, puedes cambiar la rama base desde la rama predeterminada del repositorio a otra rama si lo requieres. -- - term: autenticación básica - description: >- - Un método de autenticación en donde las credenciales se envían como texto sin cifrar. -- - term: biografía - description: >- - La descripción generada por el usuario encontrada en un perfil: https://docs.github.com/articles/adding-a-bio-to-your-profile/ -- - term: ciclo de facturación - description: El intervalo de tiempo para tu plan de facturación específico. -- - term: correo electrónico de facturación - description: >- - La dirección de correo electrónico de la organización donde GitHub envía los recibos, los cargos de tarjeta de crédito o PayPal y otras comunicaciones relacionadas a la facturación. -- - term: gerente de facturación - description: El miembro de la oranización que administra los parámetros de facturación para una organización. -- - term: plan de facturación - description: >- - Los planes de pago para usuarios y organizaciones que incluyen características establecidas para cada tipo de plan. -- - term: último responsable - description: >- - La función "último responsable" en Git describe las últimas modificaciones para cada línea e un archivo, que generalmente muestra la revisión, el autor y la hora. Esto es útil, por ejemplo, para detectar cuándo se agregó una función o qué confirmación de cambios llevó a un error en particular. -- - term: bloquear - description: >- - Eliminar la posibilidad de un usuario de colaborar con los repositorios de una organización. -- - term: rama - description: >- - Una rama es una versión paralela de un repositorio. Está dentro del repositorio, pero no afecta la rama maestra o principal, lo que te permite trabajar libremente sin interrumpir la versión "activa". Una vez que haz hecho las modificaciones que deseabas, puedes fusionar tu rama de nuevo en la rama maestra para publicar tus modificaciones. -- - term: restricción de rama - description: >- - Una restricción que los administradores de repositorio pueden activar para que solo ciertos usuarios o equipos puedan subir o hacer ciertas modificaciones en la rama. -- - term: Plan Business - description: >- - Un plan de facturación de la organización donde puedes colaborar en repositorios públicos y privados ilimitados, permitir o solicitar a los miembros de la organización autenticar GitHub usando SSO de SAML y aprovisionar y desaprovisionar acceso con SAML o SCIM. -- - term: certificado CA - description: >- - Un certificado digital emitido por una entidad de certificación (CA) que garantiza que hay conexiones válidas entre dos máquinas, como el equipo de un usuario y GitHub.com y que verifica la titularidad de un sitio. -- - term: tarjeta - description: Un cuadrado móvil dentro del tablero de proyecto asociado con una propuesta o una solicitud de extracción. -- - term: Verificación - description: >- - Una revisión es un tipo de revisión de estado en {% data variables.product.product_name %}. Ver "[Revisiones de estado](#status-checks)." -- - term: control - description: >- - Puedes usar el "control Git" en la línea de comandos para crear una nueva rama, modificar tu rama de trabajo actual a una rama diferente o incluso cambiar a una versión diferente de un archivo desde una rama diferente con "control git [branchname] [path to file]". La acción "control" actualiza todo a parte del árbol de trabajo con un objeto de árbol o blob desde la base de datos de objetos y actualiza el índice y HEAD si todo el árbol de trabajo apunta a una rama nueva. -- - term: cherry-picking - description: >- - Para elegir un subconjunto de modificaciones de una serie de modificaciones (generalmente, confirmaciones de cambios) y registrarlas como una nueva serie de modificaciones además de un código base diferente. En Git, esto lo realiza el comando "cherry-pick Git" para extraer el cambio introducido por una confirmación de cambios en otra rama y para registrarlo en función de la sugerencia de la rama actual como una confirmación de cambios nueva. -- - term: equipo hijo - description: >- - Dentro de los equipos anidados, el subequipo que hereda los permisos de acceso y las @menciones del equipo padre. -- - term: limpio - description: >- - Un árbol de trabajo está limpio si corresponde a la revisión referenciada en el HEAD actual. Consulta también "sucio". -- - term: clon - description: >- - Un clon es una copia de un repositorio que vive en tu equipo en vez de en algún lugar del servidor del sitio web o el acto de realizar dicha copia. Cuando haces un clon, puedes editar los archivos en tu editor preferido y usar Git para hacer un seguimiento de tus modificaciones sin tener que estar en línea. El repositorio que clonas sigue conectado a la versión remota para que puedas subir tus modificaciones locales al remoto para mantenerlos sincronizados cuando estás en línea. -- - term: agrupación - description: >- - La posibilidad de ejecutar los servicios GitHub Enterprise en varios nodos y equilibrar la carga de las solicitudes entre ellos. -- - term: Gráfico de frecuencia de código - description: >- - Un gráfico del repositorio que muestra las adiciones y las eliminaciones de contenido para cada semana en el historial de un repositorio. -- - term: código de conducta - description: Documento que define las normas para participar en una comunidad. -- - term: propietario del código - description: >- - Persona designada como propietario de una parte del código del repositorio. Se le solicita automáticamente al propietario del código que realice una revisión cuando alguien abre una solicitud de extracción (no en el modo borrador) que introduce cambios en el código que posee el propietario. -- - term: colaborador - description: >- - Un colaborador es una persona con acceso de escritura a un repositorio que ha sido invitada a contribuir a dicho repositorio por su propietario. -- - term: confirmar (confirmación de cambios) - description: >- - Una confirmación de cambios o "revisión", es una modificación individual a un archivo (o conjunto de archivos). Cuando realizas una confirmación de cambios para guardar tu trabajo, Git crea un ID único (también conocido como, "SHA" o "hash") que te permite mantener un registro de los cambios específicos confirmados junto con quién los realizó y cuándo. Las confirmaciones de cambios generalmente contienen un mensaje de confirmación que es una descripción breve de las modificaciones que fueron realizadas. -- - term: autor de la confirmación - description: El usuario que realiza la confirmación de cambios. -- - term: Gráfico de confirmación - description: >- - Un gráfico del repositorio que muestra todas las confirmaciones de cambios realizadas a un repositorio durante en el último año. -- - term: ID de confirmación - description: También conocido como SHA. Un hash de suma de comprobación de 40 caracteres que identifica la confirmación de cambios. -- - term: mensaje de confirmación - description: >- - Texto corto y descriptivo que acompaña una confirmación de cambios y comunica el cambio que presenta la confirmación de cambios. -- - term: rama de comparación - description: La rama que utilizas para crear una solicitud de extracción. Esta rama se compara con la rama base que escojas para la solicitud de extracción, y los cambios se identifican. Cuando la solicitud de extracción se fusiona, esta rama se actualiza con los cambios de la rama de comparación, también conocida como la "rama principal" de la solicitud de extracción. -- - term: integración continua - description: >- - También conocida como CI. Un proceso que ejecuta pruebas y compilaciones automatizadas una vez que una persona confirma los cambios para un repositorio configurado en GitHub. La CI es una buena práctica común en el desarrollo de software que ayuda a detectar errores. -- - term: gráfico de contribución - description: >- - La parte del perfil de un usuario que muestra sus contribuciones en un período de hasta un año, día a día. -- - term: pautas de contribución - description: Un documento que explica cómo las persona deberían contribuir con tu proyecto. -- - term: contribuciones - description: >- - Actividades específicas en GitHub que: - Agregarán un cuadrado al gráfico de contribuciones de un usuario: "[Que cuenta como una contribución](https://docs.github.com/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)" - Agregarán actividades a la cronología de un usuario en su perfil: "[Actividad de contribución](https://docs.github.com/articles/viewing-contributions-on-your-profile/#contribution-activity)" -- - term: colaborador - description: >- - Un colaborador es alguien que no tiene acceso de colaborador a un repositorio, pero ha contribuido en un proyecto y tenía una solicitud de extracción que había abierto fusionada en el repositorio. -- - term: Gráfico de colaboradores - description: Un gráfico del repositorio que muestra los principales 100 colaboradores de un repositorio. -- - term: cupón - description: >- - Un código proporcionado por GitHub que los usuarios o las organizaciones pueden usar para pagar el total o parte de su suscripción. -- - term: cron - description: Un programador de trabajo con límite de tiempo en los sistemas operativos de los equipos tipo Unix. -- - term: cURL - description: Se usa en las líneas de comandos o scripts para transferir datos. -- - term: Tablero - description: >- - Tu tablero personal es el concentrador principal para tu actividad en GitHub. Desde éste, puedes llevar el control de incidentes y solicitudes de extracción en los que estás trabajando o a los que estás siguiendo, navegar a tus repositorios y páginas de equipo principales, y aprender sobre la actividad reciente en los repositorios que estás observando o en los que estás participando. También puedes descubrir nuevos repositorios, los cuales se recomiendan con base en los usuarios que sigues y en los repositorios que has marcado con una estrella. Para ver únicamente la actividad de una organización específica, visita tu tablero de organización. Para obtener más información, consulta la sección "[Acerca de tu tablero profesional](/articles/about-your-personal-dashboard)" o "[Acerca de tu tablero de organización](/articles/about-your-organization-dashboard)." -- - term: rama por defecto - description: >- - La rama base en tu repositorio, en la cual se realizan automáticamente todas las solicitudes de extracción y las confirmaciones de cambios de código, a menos que especifiques una rama diferente. Esta rama generalmente se llama "maestro". -- - term: Gráfico de dependencias - description: >- - Un gráfico del repositorio que muestra los paquetes, los proyectos y los repositorios que dependen de un repositorio público. -- - term: Gráfico de dependencias - description: >- - Un gráfico del repositorio que muestra los paquetes y los proyectos de los que depende el respositorio. -- - term: llave de implementación - description: >- - Una clave de implementación es una clave SSH que se almacena en tu servidor y concede acceso a un único repositorio GitHub. Esta clave se adjunta directamente al repositorio en lugar de a una cuenta de usuario personal. -- - term: HEAD separado - description: >- - Git te advertirá si estás trabajando en un HEAD separado, lo que significa que Git no apunta a una rama y que cualquier confirmación de cambios que realices, no aparecerá en el historial de confirmaciones de cambios. Por ejemplo, cuando revisas una confirmación de cambios arbitraria que no es la última confirmación de cualquier rama en particular, estás trabajando en un "HEAD separado". -- - term: diagnóstico - description: Una descripción de los parámetros y el entorno de una instancia de GitHub Enterprise. -- - term: diferencia - description: >- - Una diferencia es la diferencia en cambios entre dos confirmaciones de cambios o los cambios guardados. La diferencia describirá visualmente lo que se agregó o se eliminó de un archivo desde su última confirmación de cambios. -- - term: sucio - description: >- - Un árbol de trabajo se considera "sucio" si contiene modificaciones que no han sido confirmadas en la rama actual. -- - term: notificaciones por correo electrónico - description: Las notificaciones enviadas a la dirección de correo electrónico de un usuario. -- - term: Cuenta de empresa - description: Las cuentas empresariales te permiten administrar centralmente las políticas y facturación de varias organizaciones de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.enterprise-accounts %} -- - term: Explorador - description: >- - Una instancia de GraphiQL, que es una "IDE GraphQL en el explorador interactiva gráfica". -- - term: avance rápido - description: >- - Un avance rápido es un tipo especial de fusión donde tienes una revisión y se "fusionan" los cambios de otra rama que resulta ser un descendiente de lo que tienes. En este caso, no realizas una confirmación de cambios de fusión nueva, si no que, en cambio, solo actualizas esta revisión. Esto sucederá con frecuencia en una rama de seguimiento remoto de un repositorio remoto. -- - term: rama de característica - description: >- - Una rama usada para experimentar con una nueva función o corregir una propuesta que no está en producción. También llamada rama de tema. -- - term: bloque de código cercado - description: 'Un bloque de código sangrado que puedes crear con el formato Markdown de GitHub utilizando triple diagonal inversa \`\`\` antes y después del mismo. Consulta el [example](https://docs.github.com/en/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).' -- - term: extraer - description: >- - Cuando usas `git fetch`, estás agregando cambios desde el repositorio remoto a tu rama de trabajo local sin confirmarlos. A diferencia de `git pull`, la recuperación te permite revisar los cambios antes de confirmarlos en tu rama local. -- - term: siguiendo (usuarios) - description: Obtener notificaciones acerca de la actividad y las contribuciones de otros usuarios. -- - term: empuje forzado - description: >- - Un empuje Git que sobreescribe el repositorio remoto con los cambios locales sin tener en cuenta los conflictos. -- - term: bifurcación - description: >- - Una bifurcación es una copia personal del repositorio de otro usuario que vive en tu cuenta. Las bifurcaciones te permiten realizar cambios libremente en un proyecto sin afectar el repositorio ascendente original. También puedes abrir una solicitud de extracción en el repositorio ascendente y mantener tu bifurcación sincronizada con los últimos cambios ya que ambos repositorios aún están conectados. -- - term: Plan gratuito - description: >- - El plan de facturación de la cuenta de un usuario que es gratuito. Los usuarios pueden colaborar en repositorios públicos ilimitados con colaboradores ilimitados. -- - term: Gist - description: >- - Un gist es un archivo compartible que puedes editar, clonar y bifurcar en GitHub. Puedes hacer que un gist sea público o secreto, aunque los gists estarán disponibles para cualquiera con la URL. -- - term: Git - description: >- - Git es un programa de código abierto para hacer un seguimiento de los cambios en los archivos de texto. Fue escrito por el autor del sistema operativo Linux y es la tecnología principal sobre la cual está contruida GitHub, la interfaz social y de usuario. -- - term: App GitHub - description: >- - Las Apps GitHub ofrecen un servicio a toda una organización y usan su propia identidad cuando desempeñan su función. Pueden ser instaladas directamente en las cuentas de usuario y de las organizaciones y pueden garantizar acceso a repositorios específicos. Vienen con permisos exhaustivos y webhooks integrados. -- - term: formato Markdown de GitHub - description: Markdown específico de GitHub usado para dar formato a la prosa y al código en GitHub. Consulta [Formato Markdown específico de GitHub](https://github.github.com/gfm/) o [Introducción a la escritura y el formato en GitHub](/articles/getting-started-with-writing-and-formatting-on-github). -- - term: Importador GitHub - description: >- - Una herramienta que importa de forma rápida repositorios de código fuente, incluido el historial de revisiones y confirmaciones de cambios, a GitHub para los usuarios. -- - term: Empleos GitHub - description: >- - Un sitio de GitHub donde los empleadores pueden publicar empleos en los que los usuarios de GitHub pueden estar interesados. -- - term: Mercado GitHub - description: >- - Un subsitio para que los usuarios y las organizaciones de GitHub compren e instalen aplicaciones que extiendan y complementen su flujo de trabajo. -- - term: Páginas de GitHub - description: >- - También se las conoce como Páginas. Un servicio de alojamiento del sitio estático diseñado para alojar tus páginas del proyecto, de la organización o personales directamente desde un repositorio de GitHub. -- - term: Wiki de GitHub - description: Una sección para alojar documentación de estilo wiki en un repositorio de GitHub. -- - term: archivo git - description: >- - Un archivo `.git` simple, que siempre está en la raíz de un árbol de trabajo y apunta al directorio de Git, que tiene el repositorio completo de Git y sus meta datos. Puedes ver este archivo para tu repositorio en la línea de comandos con `git rev-parse --git-dir`. que es el repositorio real. -- - term: GraphQL - description: >- - Un lenguaje de consulta para las API y un tiempo de ejecución para cumplir con esas consultas con tus datos existentes. -- - term: HEAD - description: Una confirmación definida de una rama, a menudo la confirmación más reciente en la punta de la rama. -- - term: rama principal - description: La rama cuyos cambios se combinaron en la rama base cuando fusionas una solicitud de extracción. También conocida como la "rama de comparación". -- - term: 'Hola, Mundo' - description: >- - Un programa "Hola, Mundo" es un programa que genera o muestra "Hola, Mundo" para un usuario. Como este programa generalmente es muy simple, se suele usar como un ejemplo de una sintaxis básica de lenguaje de programación y sirve como un primer ejercicio común para aprender un lenguaje de programación nuevo. -- - term: alta disponibilidad - description: >- - Un sistema o componente que está continuamente operativo por un conveniente largo período de tiempo. -- - term: gancho - description: >- - Durante la ejecución normal de varios comandos Git, se realizan llamadas a scripts opcionales que le permiten a un programador agregar funcionalidad o comprobación. Generalmente, los ganchos permiten que un comando sea preverificado y potencialmente interrumpido y permite una notificación posterior una vez realizada la operación. -- - term: nombre del host - description: >- - Sobrenombres en lenguaje natural que corresponden a la dirección de un dispositivo conectado a una red. -- - term: identicon - description: >- - Una imagen autogenerada usada como foto de perfil predeterminada cuando el usuario inicia sesión en GitHub. Los usuarios pueden reemplazar su identicon con su propia foto de perfil. -- - term: proveedor de identidad - description: >- - También conocido como IdP. Un proveedor de confianza que te permite usar el inicio de sesión único (SSO) de SAML para acceder a otros sitios web. -- - term: instancia - description: >- - La copia privada de GitHub de una organización contenida dentro de una máquina virtual que ellos configuran y controlan. -- - term: integración - description: >- - Una aplicación de terceros que se integra con GitHub. Estas pueden ser Apps GitHub, Apps OAuth o webhooks. -- - term: propuesta - description: >- - Las propuestas son preguntas, tareas o mejoras sugeridas relacionadas al repositorio. Las propuestas pueden ser creadas por cualquiera (para repositorios públicos) y son moderadas por los colaboradores del repositorio. Cada propuesta contiene su propio hilo de debate. También puedes categorizar una propuesta con etiquetas y asignársela a alguien. -- - term: Jekyll - description: Un generador de sitio estático para sitios de una organización, de un proyecto o personales. -- - term: selector de tema de Jekyll - description: >- - Una manera automatizada de seleccionar un tema visual para tu sitio Jekyll sin editar ni copiar archivos CSS. -- - term: clave de huella digital - description: Una secuencia corta de bytes usados para identificar una clave pública más larga. -- - term: keychain - description: Un sistema de administración de contraseñas en macOS. -- - term: palabra clave - description: Una palabra específica que cierra una propuesta cuando se usa dentro de una solicitud de extracción. -- - term: etiqueta - description: >- - Una etiqueta en una propuesta o solicitud de extracción. Los repositorios vienen con una serie de etiquetas predeterminadas, pero los usuarios pueden crear etiquetas personalizadas. -- - term: LFS - description: >- - Large File Storage de Git. Una extensión de Git de código abierto para controlar las versiones de archivos de gran tamaño. -- - term: licencia - description: >- - Un documento que puedes incluir con tu proyecto para hacerle saber a las personas qué pueden y qué no pueden hacer con tu código fuente. -- - term: Lingüista - description: >- - Una biblioteca usada en GitHub para detectar lenguajes blob, ignorar archivos binarios o vendorizado, suprimir los archivos generados en diffs y generar gráficos de desglose del lenguaje. -- - term: comentario en la línea - description: Un comentario dentro de una solicitud de extracción es una línea de código específica. -- - term: fin de línea - description: >- - Un caracter o caracteres invisibles que simbolizan el final de una línea en un archivo de texto. -- - term: cuenta personal bloqueada - description: >- - Una cuenta personal a la que el usuario no puede acceder. Las cuentas se bloquean cuando los usuarios degradan su cuenta paga a una gratis o si su plan de pago se venció. -- - term: Consola de administración - description: >- - Una sección dentro de la interfaz GitHub Enterprise que contiene funciones administrativas. -- - term: Markdown - description: >- - Markdown es un formato de archivo semántico increíblemente simple, no muy diferente a .doc, .rtf y .txt. Markdown que hace que sea fácil incluso para aquellos sin una formación en publicación web escribir prosa (incluso con enlaces, listas, viñetas, etc.) y mostrarla como un sitio web. GitHub admite Markdown y usa un formulario particular de Markdown llamado formato Markdown de GitHub. Consulta [Formato Markdown específico de GitHub](https://github.github.com/gfm/) o [Introducción a la escritura y el formato en GitHub](/articles/getting-started-with-writing-and-formatting-on-github). -- - term: Markup - description: Un sistema para anotar y dar formato a un documento. -- - term: principal - description: >- - La rama de desarrollo predeterminada. Siempre que crees un repositorio Git, se crea una rama llamada "principal" y se convierte en la rama activa. En la mayoría de los casos, esta contiene el desarrollo local, aunque esto es puramente por convención y no es requerido. -- - term: Gráfico de miembros - description: Un gráfico del repositorio que muestra todas las bifurcaciones de un repositorio. -- - term: mención - description: >- - Una notificación enviada a un usuario anteponiendo el símbolo @ al nombre de usuario. Los usuarios de una organización de GitHub también pueden ser parte de un equipo que puede ser mencionado. -- - term: fusionar - description: >- - La fusión toma los cambios de una rama (en el mismo repositorio o de una bifurcación) y los aplica en otra. Esto suele suceder como una "solicitud de extracción" (que puede considerarse como una solicitud a fusionar) o mediante la línea de comandos. Una fusión se puede realizar mediante una solicitud de extracción a través de la interfaz web GitHub.com si no hay cambios conflictivos o bien siempre se puede realizar a través de la línea de comandos. -- - term: conflicto de fusión - description: >- - Una diferencia que ocurre entre ramas fusionadas. Los conflictos de fusión suceden cuando las personas realizan diferentes cambios en la misma línea del mismo archivo o cuando una persona edita un archivo y otra persona elimina el mismo archivo. El conflicto de fusión se debe resolver antes de que puedas fusionar las ramas. -- - term: hito - description: >- - Una manera de hacer un seguimiento del progreso en grupos de propuestas o solicitudes de extracción en un repositorio. -- - term: espejo - description: Una copia nueva de un repositorio. -- - term: equipo anidado - description: >- - Un equipo hijo de un equipo padre. Puedes tener varios equipos hijo (o anidados). -- - term: Gráfico de conexiones - description: >- - Un gráfico del repositorio que muestra el historial de la rama de toda la red del repositorio, incluidas las ramas del repositorio raíz y las ramas de las bifurcaciones que contienen confirmaciones de cambios únicas para la red. -- - term: Noticias - description: >- - Una vista de la actividad de los repositorios o de las personas que ves. Las Noticias de una organización muestran la actividad en los repositorios que son propiedad de la organización. -- - term: sin avance rápido - description: >- - Cuando la copia local de un repositorio no está sincronizada con el repositorio ascendente y necesitas extraer los cambios ascendentes antes de subir tus cambios locales. -- - term: notificación - description: >- - Actualizaciones entregadas ya sea por la web o el correo electrónico, dependiendo de tus parámetros, que te brindan información acerca de las actividades en las que estás interesado. -- - term: App OAuth - description: >- - Una aplicación de terceros que usa tokens de acceso en lugar de contraseñas para acceder a información para usuarios. -- - term: token de OAuth - description: El token de acceso usado en Apps OAuth para acceder a información para usuarios. -- - term: colaborador externo - description: >- - Un usuario al que se le ha dado acceso a uno o más repositorios de una organización, pero no tiene otro acceso a la organización y no es un miembro de la organización. -- - term: código abierto - description: >- - El software de código abierto es un software que se puede usar, modificar y compartir (tanto de la forma modificada como no modificada) libremente por cualquiera. Hoy en día el concepto de "código abierto" suele extenderse más allá del software, para representar una filosofía de colaboración en la cual se facilitan los materiales de trabajo en línea para que cualquiera los bifurque, los modifique y debata y contribuya con ellos. -- - term: organización - description: >- - Las organizaciones son un grupo de dos o más usuarios que generalmente imitan a organizaciones del mundo real. Son administradas por usuarios y pueden contener tanto repositorios como equipos. -- - term: propietario de la organización - description: Usuarios que tienen un acceso administrativo completo a la organización que poseen. -- - term: origen - description: >- - El repositorio ascendente predeterminado. La mayoría de los proyectos tienen al menos un proyecto ascendente al que le hacen un seguimiento. Por defecto, el origen se usa con ese fin. -- - term: propietario - description: >- - Miembros de una organización que tienen acceso administrativo completo a la organización. -- - term: equipo padre - description: >- - Dentro de los equipos anidados, el equipo principal desde el cual los equipos hijo heredan los permisos de acceso y @menciones. -- - term: notificaciones de participación - description: >- - Una notificación acerca de una actualización en una conversación en una propuesta o solicitud de extracción donde tu nombre de usuario o equipo fue mencionado o donde previamente has respondido a un comentario. -- - term: enlace permanente - description: Un hipervínculo estático permanente a una página web en particular. -- - term: cuenta personal - description: >- - Una cuenta de GitHub que pertenece a un usuario individual. -- - term: dirección principal de correo electrónico - description: >- - La dirección principal de correo electrónico donde GitHub envía los recibos, los cargos de tarjeta de crédito o PayPal y otras comunicaciones relacionadas a la facturación. -- - term: repositorio anclado - description: >- - Un repositorio que un usuario ha decidido mostrar de forma prominente en su perfil. -- - term: ganchos de pre-recepción - description: >- - Los scripts que se ejecutan en el servidor GitHub Enterprise que puedes usar para implementar controles de calidad. -- - term: contribuciones privadas - description: Contribuciones hechas a un repositorio privado (vs. público). -- - term: repositorio privado - description: >- - Los repositorios privados solo son visibles para el propietario del repositorio y los colaboradores que el propietario especifique. -- - term: rama de producción - description: >- - Una rama con cambios finales que está lista para ser usada o implementada en una aplicación o un sitio. -- - term: perfil - description: La página que muestra información acerca de la actividad de un usuario. -- - term: foto de perfil - description: >- - Una imagen personalizada que los usuarios suben a GitHub para identificar su actividad, generalmente junto con su nombre de usuario. También se lo conoce como un avatar. -- - term: tablero de proyecto - description: >- - Los tableros dentro de GitHub que están hechos de propuestas, solicitudes de extracción y notas que son categorizados como tarjetas en columnas. -- - term: rama protegida - description: >- - Las ramas protegidas bloquean varias funciones de Git en una rama la cual un administrador de repositorio elige proteger. No pueden tener un empuje forzado, ni ser eliminadas, ni fusionarles cambios sin la aprobación de controles requerida ni las revisiones aprobadas requeridas ni cargarle archivos a esta desde la interfaz web de GitHub. Una rama protegida generalmente es la rama por defecto. -- - term: contribuciones públicas - description: Contribuciones hechas a un repositorio público (vs. privado). -- - term: repositorio público - description: >- - Un repositorio público puede ser visto por cualquiera, incluso por personas que no son usuarios de GitHub. -- - term: extraer - description: >- - Extraer se refiere a cuando se recuperan cambios y se fusionan. Por ejemplo, si alguien ha editado el archivo remoto en el que ambos están trabajando, querrás extraer esos cambios para tu copia local para que esté actualizado. También consulta recuperar. -- - term: acceso de lectura - description: Un sinónimo para acceso de lectura. -- - term: solicitud de extracción - description: >- - Las solicitudes de extracción son cambios propuestos para un repositorio enviado por un usuario y aceptado o rechazado por los colaboradores de un repositorio. Como las propuestas, las solicitudes de extracción tienen sus propios foros de debate. -- - term: revisión de solicitud de extracción - description: >- - Los comentarios de los colaboradores en una solicitud de extracción que aprueban los cambios o solicitan otros cambios antes de fusionar la solicitud de extracción. -- - term: Gráfico de pulso - description: Un gráfico del repositorio que te brinda una descripción de la actividad de un repositorio. -- - term: Gráfico perforado - description: >- - Un gráfico del repositorio que muestra la frecuencia de las actualizaciones para un repositorio en función del día de la semana y la hora del día. -- - term: subir - description: >- - Subir significa enviar tus cambios confirmados a un repositorio remoto en GitHub.com. Por ejemplo, si cambias algo de forma local, puedes subir esos cambios para que otros puedan acceder a ellos. -- - term: subir una rama - description: >- - Cuando subes una rama a un repositorio remoto, actualizas la rama remota con cambios de tu rama local. Cuando "subes una rama", Git buscará el HEAD ref en el repositorio remoto y verificará que sea un ancestro directo de el HEAD ref local de la rama. Una vez que se verifique, Git extrae todos los objetos (alcanzables desde el HEAD ref local y que no estén en el repositorio remoto) en la base de datos de objetos remotos y después actualiza el HEAD ref remoto. Si el HEAD remoto no es un ancestro del HEAD local, la subida fallará. -- - term: acceso de escritura - description: Un sinónimo para acceso de escritura. -- - term: acceso de lectura - description: >- - Un nivel de permiso en un repositorio que permite al usuario extraer o leer información desde el repositorio. Todos los repositorios públicos otorgan acceso de lectura a todos los usuarios de GitHub. Un sinónimo para acceso de lectura. -- - term: README - description: Un archivo de texto que contiene información acerca de los archivos en un repositorio que, generalmente, es el primer archivo que verá un visitante de tu repositorio. Un archivo README, junto con una licencia de repositorio, las pautas de contribución y un código de conducta, te ayuda a compartir expectativas y administrar contribuciones para tu proyecto. -- - term: rebase - description: >- - Volver a aplicar una serie de cambios de una rama a una base diferente y restablecer el HEAD de esa rama al resultado. -- - 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. -- - term: código de recuperación - description: Un código que te ayuda a volver a tener acceso a tu cuenta de GitHub. -- - term: lanzamiento - description: El modo que tiene GitHub de empaquetar y proporcionar el software a tus usuarios. -- - term: remoto - description: >- - Esta es la versión de un repositorio o rama que está alojada en un servidor, probablemente GitHub.com. Las versiones remotas se pueden conectar a clones locales para poder sincronizar los cambios. -- - term: repositorio remoto - description: >- - Un repositorio que se usa para hacer un seguimiento del mismo proyecto, pero reside en otro lugar. -- - term: URL remota - description: >- - El lugar donde se almacena tu código: un repositorio en GitHub, la bifurcación de otro usuario o incluso un servidor diferente. -- - term: réplica - description: >- - Una instancia de GitHub Enterprise que ofrece redundancia para la instancia principal de GitHub Enterprise. -- - term: repositorio - description: >- - Un repositorio es el elemento más básico de GitHub. Son más fáciles de imaginar como la carpeta de un proyecto. Un repositorio contiene todos los archivos del proyecto (incluida la documentación) y almacena el historial de revisión de cada archivo. Los repositorios pueden tener varios colaboradores y pueden ser públicos o privados. -- - term: gráfico del repositorio - description: Una representación visual de los datos de tu repositorio. -- - term: mantenedor del repositorio - description: >- - Alguien que administra un repositorio. Esta persona puede ayudar a evaluar prioridades de las propuestas y usar etiquetas y otras funciones para administrar el funcionamiento del repositorio. Esta persona también puede ser responsable de mantener los archivos README y de contribución actualizados. -- - term: revisión de solicitud de extracción requerida - description: >- - Las revisiones requeridas garantizan que las solicitudes de extracción tengan, al menos, una revisión aprobada antes de que los colaboradores puedan realizar cambios en una rama protegida. -- - term: verificación de estado requerida - description: >- - Verificaciones de las solicitudes de extracción que garantizan que todas las pruebas de integración continua (CI) requeridas sean aprobadas antes de que los colaboradores puedan realizar cambios en una rama protegida. -- - term: resolver - description: La acción de solucionar de forma manual lo que dejó una fusión automática fallida. -- - term: revertir - description: >- - Cuando reviertes una solicitud de extracción en GitHub, automáticamente se abre una solicitud de extracción nueva, que tiene una confirmación de cambios que revierte la confirmación de fusión de la solicitud de extracción original fusionada. En Git, puedes revertir las confirmaciones de cambio con `revertir git`. -- - term: revisión - description: >- - Las revisiones le permiten a otros con acceso a tu repositorio comentar los cambios propuestos en las solicitudes de extracción, aprobar los cambios o solicitar más cambios antes de que se fusione la solicitud de extracción. -- - term: directorio raíz - description: El primer directorio en jerarquía. -- - term: sistema de archivos raíz - description: El sistema operativo base y el entorno de la aplicación GitHub Enterprise. -- - term: respuesta guardada - description: >- - Un comentario que puedes guardar y agregar a tu cuenta de usuario de GitHub para que puedas usar en GitHub en las propuestas y en las solicitudes de extracción. -- - term: alcance - description: >- - Grupos de permisos con nombre que una App OAuth puede solicitar para acceder tanto a los datos públicos como los no públicos. -- - term: asiento - description: >- - Un usuario dentro de la organización de GitHub Enterprise. Se lo puede conocer como "cómputo de asientos". -- - term: equipo secreto - description: >- - Un equipo que solo es visible para otras personas del equipo y personas con premisos de propietario. -- - term: registro de seguridad - description: >- - Un registro que enumera las últimas 50 acciones o las realizadas dentro de los últimos 90 días. -- - term: gancho de servicio - description: >- - También llamado "webhook". Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización. -- - term: inicio de sesión único - description: >- - También llamado SSO. Le permite a los usuarios iniciar sesión en una única ubicación - un proveedor de identidad (IdP)- que luego le da acceso al usuario a otros proveedores de servicios. -- - term: instantánea - description: Un punto de control de una máquina virtual a partir de un momento específico. -- - term: combinar - description: Combinar varias confirmaciones de cambios en una única confirmación. También un comando Git. -- - term: Clave SSH - description: >- - Las claves SSH son una manera de identificarte a ti mismo en un servidor en línea, usando un mensaje cifrado. Es como si tu computadora tuviera su propia contraseña única para otro servicio. {% data variables.product.product_name %} utiliza claves SSH para transferir información de forma segura a tu computadora. -- - term: instancia de preparación - description: >- - Un modo de evaluar modificaciones antes de que sean aplicadas a tu instancia actual de GitHub Enterprise. -- - term: estado - 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: 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)." -- - term: estrella - description: >- - Un marcador o una muestra de reconocimiento para un repositorio. Las estrellas son un modo manual de clasificar la popularidad de los proyectos. -- - term: suscripción - description: Un plan GitHub de un usuario o una organización. -- - term: equipo - description: >- - Un grupo de miembros de una organización que refleja la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. -- - term: mantenedor del equipo - description: >- - Miembros de la organización que tienen un subconjunto de permisos disponibles para los propietarios de la organización para administrar equipos. -- - term: Plan de equipo - description: >- - El plan de facturación de una organización que te da repositorios públicos y privados ilimitados. -- - term: cronología - description: Una serie de eventos en una solicitud de extracción o en el perfil de un usuario. -- - term: rama de tema - description: >- - Una rama Git normal que usa un programador para identificar una línea conceptual de desarrollo. Como las ramas son muy fáciles de usar y económicas, suele ser conveniente tener varias ramas pequeñas y que cada una contenga conceptos muy bien definidos o cambios pequeños incrementales pero relacionados. También se puede denominar rama de característica. -- - term: temas - 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: Gráfico 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. -- - term: transferencia - description: >- - Transferir un repositorio significa cambiar el propietario de un repositorio. El nuevo propietario podrá administrar de inmediato los contenidos, las propuestas, las solicitudes de extracción, los lanzamientos y los parámetros del repositorio. -- - term: ascendente - description: >- - Cuando se habla de una rama o una bifurcación, la rama principal en el repositorio original suele conocerse como "ascendente", ya que es el lugar principal desde donde vendrán otros cambios. La rama/bifurcación en la que estás trabajando entonces se llama "descendente ". También llamada origen. -- - term: rama ascendente - description: >- - La rama por defecto que se fusiona en la rama en cuestión (o la rama en cuestión en la que es rebasada). Se configura mediante `branch..remote` y `branch..merge`. Si la rama ascendente de A es la origen/B, a veces, decimos "A hace un seguimiento de la origen/B". -- - term: usuario - description: >- - Los usuarios son personas con cuentas personales de GitHub. Cada usuario tiene un perfil personal y puede poseer varios repositorios, públicos o privados. Pueden crear o ser invitados a unirse a organizaciones o colaborar con el repositorio de otro usuario. -- - term: nombre de usuario - description: El identificador de un usuario en GitHub. -- - term: equipo visible - description: Un equipo que puede ser visto y @mencionado por cada miembro de la organización. -- - term: ver - description: >- - Puedes ver un repositorio o una propuesta para recibir notificaciones cuando se realizan actualizaciones a una propuesta o una solicitud de extracción. -- - term: ver notificaciones - description: Una notificación acerca de la actividad en un repositorio al que se ha subscripto un usuario. -- - term: notificaciones web - description: >- - Las notificaciones que se muestran en la interfaz web en GitHub: https://github.com/notifications -- - term: webhooks - description: >- - Los webhooks te permiten generar o configurar Apps GitHub que se suscriben a ciertos eventos en GitHub.com. Los webhooks ofrecen una manera de enviar las notificaciones a un servidor web externo siempre que ciertas acciones ocurran en un repositorio o una organización. También llamado gancho de servicio. -- - term: Compatible con GitHub - description: Un listado de integraciones que son compatibles con GitHub. -- - term: acceso de escritura - description: >- - Un nivel de permiso en un repositorio que le permite al usuario subir o escribir cambios para un repositorio. diff --git a/translations/es-XL/data/glossaries/internal.yml b/translations/es-XL/data/glossaries/internal.yml deleted file mode 100644 index c5e7bab645..0000000000 --- a/translations/es-XL/data/glossaries/internal.yml +++ /dev/null @@ -1,755 +0,0 @@ ---- -- - term: 2-up - description: El modo predeterminado de ver imágenes en GitHub. -- - term: base de datos alterna de objetos - description: >- - A través de mecanismos alternativos, un repositorio puede heredar parte de su base de datos de objetos de otra base de datos de objetos, que se denomina "alternativa". -- - term: AMI - description: >- - Imagen de máquina de Amazon. Un aparato virtual para usar con la Amazon Elastic Compute Cloud. -- - term: URL de imagen anonimizada - description: >- - Un proxy URL anónimo para cada imagen que oculta los detalles del navegador y la información relacionada de otros usuarios. -- - term: dominio apex - description: Un dominio de raíz que no contiene una parte de subdominio. -- - term: API - description: >- - Interfaz de programación de la aplicación. Un conjunto de métodos de comunicación claramente definidos entre varios componentes de software. -- - term: token API - description: >- - Un token que se usa en lugar de una contraseña en scripts y en la línea de comando. -- - term: app - description: >- - Servicio de terceros que se integra con GitHub. Por lo general, esto se refiere a las aplicaciones OAuth o a las Apps GitHub. También se las conoce como app. -- - term: aplicación - description: >- - Servicio de terceros que se integra con GitHub. Por lo general, esto se refiere a las aplicaciones OAuth o a las Apps GitHub. También se las conoce como app. -- - term: argumento - description: 'En GraphQL, un conjunto de pares de clave-valor que se adjunta a un campo específico.' -- - term: AsciiDoc - description: >- - Un formato de documento de texto para escribir notas, documentación, artículos, libros, libros electrónicos, diapositivas, páginas web, páginas de manual y blogs. -- - term: activos - description: 'Archivos individuales como imágenes, fotos, videos y archivos de texto.' -- - term: formato Atom - description: Un formato XML ligero que permite una fácil sindicación del contenido web. -- - term: registro de auditoría - description: >- - En una organización, el registro de auditoría incluye detalles acerca de las actividades realizadas en la organización, como quién realizó la acción, cuál fue la acción y cuándo fue realizada. -- - term: avatar - description: >- - Una imagen personalizada que los usuarios suben a GitHub para identificar su actividad, generalmente junto con su nombre de usuario. También se lo conoce como una foto de perfil. -- - term: AWS - description: Amazon Web Services. Una plataforma segura de servicios en la nube. -- - term: Azure - description: Una plataforma de informática en la nube de Microsoft. -- - term: repositorio en blanco - description: >- - Normalmente, un repositorio en blanco es un directorio con un nombre apropiado con un sufijo .git que no tiene una copia revisada localmente de ninguno de los archivos bajo control de revisión. Es decir, todos los archivos de control y administrativos Git que normalmente estarían presentes en el subdirectorio .git oculto están presentes directamente en el directorio del repositorio.git y ningún otro archivo está presente y revisado. Generalmente, quienes publican los repositorios públicos ponen a disposición los repositorios en blanco. -- - term: Limpiador para repositorio BFG - description: BFG. Una herramienta de terceros que limpia datos del historia de tu repositorio Git. -- - term: objeto blob - description: 'Objeto sin tipo, p. ej., los contenidos de un archivo.' -- - term: bot - description: Una aplicación de software que ejecuta tareas automatizadas. -- - term: Bundler - description: Una manera de administrar las Ruby gems de las que depende una aplicación. -- - term: camuflaje - description: >- - Un proxy de imagen SSL para evitar advertencias de contenido mixto en páginas seguras proporcionadas desde GitHub. -- - term: cadena - description: >- - Una lista de objetos, donde cada objeto en la lista contiene una referencia para su sucesor (por ejemplo, el sucesor de una confirmación de cambios podría ser uno de sus padres). -- - term: notación CIDR - description: Una representación compacta de una dirección IP y su prefijo de enrutamiento asociado. -- - term: CLI (interfaz de línea de comandos) - description: Interfaz de línea de comandos. -- - term: registro CNAME - description: >- - Registro de nombre canónico. Un tipo de registro de recursos en el Sistema de nombres de dominio (DNS) usado para especificar que el nombre de un dominio es un alias para otro dominio (el dominio 'canónico'). -- - term: solicitud condicional - description: >- - En la API REST, un método HTTP que solo se responde en ciertas circunstancias. -- - term: conexión - description: 'En GraphQL, una manera de consultar objetos relacionados como parte de la misma llamada.' -- - term: Núcleo de Git - description: >- - Utilidades y estructuras de datos fundamentales de Git. Expone solo herramientas de administración de código fuente limitadas. -- - term: CPU - description: Unidad de procesamiento central. -- - term: ayudante de credenciales - description: Un programa que almacena y extrae credenciales Git. -- - term: creole - description: >- - Un lenguaje Markup ligero, que apunta a ser un lenguaje Markup común para wikis, que permita y simplifique la transferencia de contenido entre diferentes motores wiki. -- - term: CSV - description: Archivos delimitados por comas. -- - term: DAG - description: >- - Gráfico acíclico dirigido. Los objetos de confirmación de cambios forman un gráfico acíclico dirigido, porque tienen padres (dirigidos) y el gráfico de objetos de confirmación de cambios es acíclico (no hay cadena que comience y termine con el mismo objeto). -- - term: objeto inalcanzable - description: >- - Un objeto inaccesible que no es accesible incluso desde otros objetos inaccesibles; un objeto inalcanzable no tiene referencias a él desde ninguna referencia ni objeto en el repositorio. -- - term: paquete de datos - description: >- - Paquete de ancho de banda y de almancenamiento que los usuarios pueden comprar. Cada paquete de datos ofrece 50 GB de ancho de banda y 50 GB para almacenamiento. -- - term: DELETE - description: Un tipo de método en la API REST. -- - term: DHCP - description: >- - Protocolo de configuración dinámica de host (DHCP). Un servidor de cliente/protocolo que proporciona automáticamente un host de protocolo de Internet con su dirección IP y otra información de configuración relacionada, como la máscara de subred y la puerta de enlace predeterminada. -- - term: directiva - description: >- - En GraphQL, un modo de afectar la ejecución de una consulta de la manera que el servidor lo desee. -- - term: directorio - description: La lista que obtienes con el comando "ls". -- - term: recuperación ante desastres - description: >- - También conocido como DR. Herramientas y procesos que recuperan los sistemas y la infraestructura tecnológica después de una catástrofe natural o de origen humano. -- - term: proveedor DNS - description: >- - Una empresa que le permite a los usuarios comprar y registrar un nombre de dominio único y conectar ese nombre a una dirección IP (Protocolo de Internet) indicando tu nombre de dominio a una dirección IP o a un nombre de dominio diferente. -- - term: DSA - description: Algoritmo de firma digital. Un estándar de procesamiento para las firmas digitales. -- - term: llave DSA - description: Claves públicas y privadas usadas en DSA. -- - term: Programa de acceso temprano - description: >- - Un programa de GitHub al que ingresan individuos y organizaciones para recibir funciones prelanzadas. -- - term: EBS - description: >- - Amazon Elastic Block Store. Ofrece volúmenes de almacenamiento de bloqueo persistente para usar con la instancia de Amazon EC2 en la nube de AWS. -- - term: EC2 - description: >- - Amazon Elastic Compute Cloud. Un servicio web que ofrece capacidad de cálculo redimensionable y segura en la nube. -- - term: borde - description: 'En GraphQL, las conexiones entre nodos.' -- - term: EIP - description: IP elástica. Una dirección IPv4 estática diseñada para una informática dinámica en la nube. -- - term: ElasticSearch - description: Un motor de búsqueda basado en Lucene. -- - term: unión maliciosa - description: >- - Un unión maliciosa es una fusión que introduce cambios que no aparecen en ningún padre. -- - term: excluir - description: >- - Una vez que una ruta coincide con cualquier pathspec no excluido, será ejecutada a través de todo pathspec excluido (firma especial: ! o su sinónimo ^). Si coincide, la ruta se ignora. Si no hay pathspec no excluido, la exclusión se aplica al resultado establecido como invocado sin ningún pathspec. -- - term: FIDO U2F - description: >- - Un estándar de autenticación abierta que refuerza y simplifica la autenticación de dos factores usando dispositivos NFC y USB especializados basado en una tecnología de seguridad similar encontrada en las tarjetas inteligentes. -- - term: campo - description: 'En GraphQL, una unidad de datos que puedes recuperar de un objeto.' -- - term: sistema de archivos - description: >- - Linus Torvalds originalmente diseñó Git para ser un sistema de archivos de espacio para usuarios, es decir, la infraestructura para mantener archivos y directorios. Esto garantizó la eficacia y la velocidad de Git. -- - term: discusión encendida - description: Un debate fuerte y agresivo en línea entre usuarios. -- - term: fragmento - description: 'En GraphQL, unidades reusables que te permiten crear conjuntos de campos.' -- - term: GCE - description: Google Compute Engine. -- - term: gema - description: Una herramienta de línea de comandos que puede instalar bibliotecas y administrar RubyGems. -- - term: Gemfile - description: Un formato para describir las dependencias gem para los programas Ruby. -- - term: GET - description: Un tipo de método en la API REST. -- - term: geoJSON - description: Un formato para codificar una variedad de estructuras de datos geográficos. -- - term: Política de Desarrolladores para el Mercado de Github - description: Un acuerdo que firman los usuarios cuando usan Mercado GitHub. -- - term: GPG - description: >- - GNU Privacy Guard. Software de cifrado que puedes usar para cifrar (y descifrar) archivos que contengan datos confidenciales. -- - term: llave GPG - description: Una clave de cifrado usada con GPG. -- - term: hash - description: Sinónimo para nombre del objeto. -- - term: encabezado - description: >- - Una referencia con nombre para la confirmación de cambios en el extremo de una rama. Los encabezados se almacenan en un archivo en el directorio $GIT_DIR/refs/heads/, excepto cuando usan refs empaquetados. -- - term: HEAD - description: Un tipo de método en la API REST. -- - term: encabezados - description: >- - En la API REST, un componente del mensaje requerido que define los metadatos de la tranasacción. -- - term: revisión de estado - description: >- - Un modo de permitir un balanceador de carga para detener el tráfico que se envía a un nodo que no está respondiendo si falla una revisión configurada previamente en ese nodo. -- - term: verbo HTTP - description: Un método HTTP. -- - term: Hyper-V - description: >- - Un producto de Microsoft que crea máquinas virtuales en sistemas x86-64 con Windows. -- - term: hipermedia - description: 'En la API REST, enlaces desde un estado de recurso a otro.' -- - term: icase - description: Coincidencia que no distingue mayúsculas de minúsculas. -- - term: implementación - description: 'En GraphQL, cómo un objeto hereda de una interfaz.' -- - term: índice - description: >- - Un conjunto de archivos con información estadística, cuyos contenidos se almacenan como objetos. El índice es una versión almacenada de tu árbol de trabajo. A decir verdad, también puede contener una segunda, e incluso una tercer versión de un árbol de trabajo, que se usan cuando se fusiona. -- - term: entrada de índice - description: >- - La información respecto a un archivo en particular, almacenada en el índice. Una entrada de índice puede ser no configurada, si se inició una fusión, pero aún no se finalizó (es decir, si el índice contiene varias versiones de ese archivo). -- - term: introspección - description: >- - También se la conoce como "introspectiva". Un modo de solicitar al esquema GraphQL información acerca de las consultas que admite. -- - term: notebook iPython - description: >- - Una aplicación basada en la web que captura todo el proceso de cálculo: desarrollo, documentación y código de ejecución, así como también comunica los resultados. -- - term: JIRA - description: Un producto de Atlassian que hace un seguimiento de las propuestas. -- - term: notebook Jupyter - description: Notebook que contiene tanto elementos de texto enriquecido como de código. -- - term: kernel - description: Un programa que es el núcleo del sistema operativo de un equipo. -- - term: kramdown - description: Procesador Markdown predeterminado 3.0.0 de Jekyll. -- - term: LDAP - description: Protocolo ligero de acceso a directorios. -- - term: limpiador - description: Un programa que verifica la calidad del código. -- - term: Liquid - description: Un lenguaje de plantillas que se usa para cargar contenido dinámico. -- - term: balanceador de carga - description: >- - Un dispositivo que actúa como un proxy inverso y distribuye tráfico de aplicación o de red a través de una cantidad de servidores. -- - term: tipo de media - description: Un identificador de dos partes para los formatos de archivo y los contenidos de formato. -- - term: MediaWiki - description: >- - Un software wiki de código abierto y gratuito escrito en el lenguaje de programación PHP que almacena los contenidos en una base de datos. -- - term: Mercurial - description: 'Una herramienta de administración de control de código fuente con distribución y gratuita.' -- - term: metadatos - description: Un conjunto de datos que describen y brindan información acerca de otros datos. -- - term: tipo MIME - description: >- - Extensiones de correo de Internet multipropósitos. Una manera de identificar archivos según su naturaleza y formato. -- - term: mutaciones - description: >- - En GraphQL, una manera de definir las operaciones GraphQL que modifican datos en el servidor. -- - term: servidor de nombres - description: >- - Un servidor en Internet especializado en manejar consultas respecto a la ubicación de varios servicios de un nombre de dominio. -- - term: NFC - description: >- - Transmisión de datos en proximidad. Un conjunto de protocolos de comunicación que le permite a dos dispositivos electrónicos, uno de los cuales generalmente es un dispositivo portátil como un smartphone, establecer comunicación llevándolos dentro de un cierto rango uno de otro. -- - term: nodo - description: >- - Un dispositivo electrónico activo que se conecta a una red y es capaz de crear, recibir o transmitir información en un canal de comunicaciones. -- - term: nodo - description: 'En GraphQL, un término genérico para un objeto.' -- - term: NTP - description: Protocolo de tiempo de la red. -- - term: objeto - description: >- - La unidad de almacenamiento en Git. Se identifica de forma unívoca mediante el SHA-1 de sus contenidos. Por consiguiente, un objeto no se puede modificar. -- - term: base de datos de objetos - description: >- - Almacena un conjunto de "objetos" y el nombre del objeto identifica un objeto individual. Los objetos generalmente viven en $GIT_DIR/objects/. -- - term: identificador de objeto - description: Sinónimo para nombre del objeto. -- - term: nombre del objeto - description: >- - El identificador único de un objeto. El nombre del objeto generalmente se representa con una cadena hexadecimal de 40 caracteres. Coloquialmente también se lo llama SHA-1. -- - term: tipo de objeto - description: >- - Uno de los identificadores "confirmación de cambios", "árbol", "etiqueta" o "blob" que describe el tipo de un objeto. -- - term: vincular - description: Fusionar más de dos ramas. -- - term: papel cebolla - description: >- - Una manera de ver imágenes en GitHub disminuyendo la opacidad de una imagen de reemplazo superpuesta. -- - term: OOM - description: Sin memoria. -- - term: Open Stack - description: Una plataforma de software para informática en la nube. -- - term: OpenSSH - description: >- - Un conjunto de utilidades a nivel de red relacionado con la seguridad basado en el protocolo Secure Shell (SSH). -- - term: lista ordenada - description: Una lista enumerada. -- - term: Org - description: >- - Un sistema de texto simple para mantener las notas, mantener las listas TODO, planificar proyectos y autorizar documentos. -- - term: paquete - description: >- - Un conjunto de objetos que han sido comprimidos en un archivo (para ahorrar espacio o para transmitirlos de forma eficiente). -- - term: índice del paquete - description: >- - La lista de identificadores, y otra información, de los objetos en un paquete, para ayudar a acceder de forma eficiente a los contenidos de un paquete. Los pathspec se usan en la línea de comandos de "git ls-files", "git ls-tree", "git add", "git grep", "git diff", "git checkout", y muchos otros comandos para limitar el alcance de las operaciones para algún subconjunto del árbol o del árbol de trabajo. -- - term: parámetro - description: >- - En la API REST, datos que son enviados en la solicitud o recibidos en la respuesta como parte de un parámetro de entrada o salida. -- - term: padre - description: >- - Un objeto de confirmación de cambios contiene una lista (posiblemente vacía) de el/los predecesor/es lógico/s en la línea de desarrollo, es decir, sus padres. -- - term: contraseña - description: >- - Una secuencia de palabras u otro texto usado para controlar el acceso a un sistema del equipo, programa o datos. -- - term: PATCH - description: Un tipo de método en la API REST. -- - term: pathspec - description: Patrón usado para limitar las rutas en los comandos de Git. -- - term: PEM - description: Correo con privacidad mejorada -- - term: identificador persistente - description: >- - También conocidos como identificadores de objetos digitales (DOI). Cadenas de caracteres y/o números únicos a nivel global que hacen referencia a un objeto digital. Los identificadores persistentes pueden ser prácticos ya que le permiten a un usuario acceder al recurso digital mediante un enlace persistente. -- - term: pickaxe - description: >- - Una opción para las rutinas de núcleo diferente que ayuda a seleccionar cambios que agregan o eliminan una cadena de texto dada. Con la opción --pickaxe-all, se puede usar para ver el conjunto de cambios completo que introducido o eliminado, dice, una línea de texto particular. -- - term: plugin - description: Un componente de software que agrega una función especial a un programa existente. -- - term: Pod - description: Documentación antigua simple. Un lenguaje mark-up usado por los programadores perl. -- - term: archivo puntero - description: Una referencia que apunta a un archivo real. -- - term: puerto - description: Un punto final de comunicación en un sistema operativo. -- - term: pregunta prioritaria - description: >- - Preguntas para el soporte técnico de GitHub de organizaciones en el Plan Business. Las preguntas deben cumplir con los criterios establecidos por GitHub para calificar como una pregunta prioritaria. -- - term: respuesta prioritaria - description: >- - Respuestas del soporte técnico de GitHub para las preguntas prioritarias de organizaciones en el Plan Business. -- - term: sondeo - description: >- - Controles automáticos regulares de otros programas o dispositivos hechos por un programa o dispositivo para ver en qué estado están. -- - term: POST - description: Un tipo de método en la API REST. -- - term: Programa de prelanzamiento - description: >- - Un programa de GitHub que le permite a los usuarios aplicar nuevas funciones y funcionalidad antes de ser lanzados oficialmente. -- - term: PUT - description: Un tipo de método en la API REST. -- - term: QCOW2 - description: Un formato de imagen. -- - term: código QR - description: >- - Código de respuesta rápida. Un código de barras es la etiqueta óptica de lectura mecánica que contiene información acerca del elemento al que está conectado. -- - term: consultas - description: 'En GraphQL, una manera de preguntar por campos específico en los objetos.' -- - term: límite de tasa - description: El proceso por el cual una API rechaza solicitudes. -- - term: RDoc - description: Un generador de documentación incrustada para el lenguaje de programación Ruby. -- - term: accesible - description: >- - Se dice que todos los ancestros de una confirmación de cambios dada son "accesibles" desde esa confirmación. En términos más generales, un objeto es accesible desde otro si podemos alcanzarlos de unos a otros mediante una cadena que sigue etiquetas para lo que sea que etiqueten, confirmaciones de cambios a sus padres o árboles, y árboles a los árboles o blobs que contengan. -- - term: ref - description: >- - Un nombre que comienza con refs/ (p. ej., refs/heads/master) a apunta a un nombre del objeto o a otro ref (el último se llama un ref simbólico). -- - term: reflog - description: Un reflog muestra el "historial" local de un ref. -- - term: refspec - description: >- - Un "refspec" es usado por recuperar y subir para describir la asignación entre ref remoto y ref local. -- - term: enlace relativo - description: Un enlace que es relativo para el archivo actual. -- - term: rama de seguimiento remoto - description: Un ref que se usa para seguir los cambios desde otro repositorio. -- - term: API REST - description: >- - Una API que define un conjunto de funciones para que los programadores puedan realizar solicitudes y recibir respuestas mediante HTTP. -- - term: texto reestructurado - description: Un sistema analizador y de sintaxis Markup de texto simple Lo que ves es lo que obtienes. -- - term: revisión - description: Sinónimo para confirmación de cambios. -- - term: retroceder - description: >- - Descartar parte del desarrollo, es decir, asignar el encabezado a una revisión anterior. -- - term: punto final raíz - description: 'En la API REST, el directorio en los que todos los puntos finales están debajo.' -- - term: RSA - description: Algoritmo usado para cifrar los datos de usuario usando una clave pública y una clave privada. -- - term: llave RSA - description: Una clave privada basada en el algoritmo RSA. -- - term: SAML - description: >- - Lenguaje Markup de aserción de seguridad. Un formato de datos estándar abierto basado en XML para intercambiar datos de autenticación y autorización entre las partes, en particular, entre un proveedor de identidad y un proveedor de servicios. -- - term: SAN - description: Nombre alternativo del firmante. -- - term: Sass - description: Un lenguaje de extensión CSS. -- - term: esquema - description: Metadatos que nos dicen cómo están estructurados nuestros datos. -- - term: SCIM - description: >- - Sistema para la administración de identidades entre dominios. Un estándar abierto para automatizar el intercambio de información de identidad del usuario entre los dominios de identidad. -- - term: SCM - description: Administración de código fuente (herramienta). -- - term: SCSS - description: Un lenguaje de extensión CSS. -- - term: cuenta de servicio - description: >- - Una cuenta de usuario especial que una aplicación o servicio usa para interactuar con el sistema operativo. -- - term: SHA-1 - description: >- - "Algoritmo Hash seguro 1"; una función de hash criptográfico. En el contexto de Git se usa como un sinónimo de nombre del objeto. -- - term: shell - description: Una interfaz de usuarios para acceder a los servicios de un sistema operativo. -- - term: repositorio superficial - description: >- - Un repositorio superficial tiene un historial incompleto y algunas de sus confirmaciones de cambios tienen padres cauterizados aparte (en otras palabras, se le pide a Git que haga como si esas confirmaciones no tuvieran padres, aunque se graban en el objeto de la confirmación). Esto, a veces, es útil cuando solo te interesa el historial reciente de un proyecto aunque el historial real grabado en el ascendente sea mucho más grande. Un repositorio superficial se crea dando la --opción de profundidad para git-clone(1) y su historial puede ser profundizado más tarde con git-fetch(1). -- - term: SMS - description: Un mensaje de texto. -- - term: SMTP - description: Protocolo simple de transferencia de correo. Un estándar para la transmisión de correo. -- - term: SNMP - description: Protocolo simple de administración de redes. Un protocolo para la administración de redes. -- - term: spam - description: Comunicaciones no solicitadas de otro usuario. -- - term: SSD - description: Unidad de estado sólido. -- - term: SSH - description: >- - Secure Shell (SSH) es un protocolo de red criptográfico para operar servicios de red de forma segura en una red no segura. -- - term: ssh-agent - description: Un programa para retener claves privadas usadas para la autenticación de claves públicas. -- - term: clave SSH - description: >- - Las claves SSH son una manera de identificarte en un servidor en línea, usando un mensaje cifrado. Es como si tu equipo tuviera su propia contraseña única para otro servicio. GitHub usa las claves SSH para transferir información de forma segura desde GitHub.com a tu equipo. -- - term: huella digital de la clave SSH - description: >- - Identifica y verifica el host al que te estás conectando y está basada en la clave pública del host. -- - term: SSL - description: Capa de sockets seguros. -- - term: generador de sitio estático - description: >- - Un programa que genera un sitio web solo HTML usando datos sin procesar (como archivos Markdown) y plantillas. -- - term: Cadena - description: Un tipo de objeto que denota texto simple. -- - term: archivo STL - description: >- - STL (STereoLithography) es un formato de archivo nativo para el software CAD de estereolitografía creado por los sistemas 3D. -- - term: subdominio - description: >- - Una parte personalizable y opcional del nombre de un dominio ubicada antes de la raíz o del dominio apex que se ve como el prefijo de un dominio. -- - term: submódulo - description: >- - Un repositorio que contiene el historial de un proyecto independiente dentro de otro repositorio (este último se denomina superproyecto). -- - term: subproyecto - description: >- - Un proyecto que se desarrolla y se administra fuera de tu proyecto principal. -- - term: Subversion - description: Un sistema de control de versión de código abierto. -- - term: modo sudo - description: >- - Una manera en que los usuarios ejecutan programas con los privilegios de seguridad de otro usuario. Los usuarios proporcionan su propia contraseña y son autenticados. -- - term: superproyecto - description: >- - Un repositorio que hace referencia a repositorios de otros proyectos en su árbol de trabajo como submódulos. El superproyecto conoce los nombres de (pero no guarda copias de) los objetos de confirmación de cambios de los submódulos contenidos. -- - term: paquete de soporte - description: >- - Un archivo tar comprimido en gzip que contiene registros importantes de tu instancia de GitHub Enterprise. -- - term: deslizar - description: Una manera de ver porciones de tu imagen de GitHub de lado a lado. -- - term: enlace simbólico - description: >- - Un archivo que contiene una referencia a otro archivo o directorio en la forma de una ruta absoluta o relativa y que afecta la resolución del nombre de ruta. -- - term: referencia simbólica - description: >- - Referencia simbólica: en lugar de contener el propio id SAH-1, es del formato ref: refs/some/thing y cuando se le hace referencia, recurrentemente se desreferencia de esta referencia. -- - term: etiqueta - description: >- - Una ref en el espacio de nombres refs/tags/ que apunta a un objeto de un tipo arbitrario (generalmente, una etiqueta apunta ya sea a una etiqueta o a un objeto de confirmación de cambios). Una etiqueta se usa principalmente para marcar un punto en particular en la cadena de ascendencia de la confirmación. -- - term: objeto de etiqueta - description: >- - Un objeto que contiene una ref apuntando a otro objeto, que puede contener un mensaje como un objeto de confirmación de cambios. También puede contener una firma (PGP), en cuyo caso se llama un "objeto de etiqueta firmado". -- - term: Team Foundation Server - description: >- - Un producto de Microsoft que ofrece administración de código fuente y otros servicios de equipo. -- - term: Textile - description: >- - Un lenguaje Markup ligero que usa una sintaxis de formato de texto para convertir texto simple en un Markup HTML estructurado. -- - term: TLS - description: Seguridad de la capa de transporte. -- - term: token - description: >- - Se puede usar en lugar de una contraseña. Los tokens pueden ser tokens de acceso personal, tokens de OAuth o tokens API. -- - term: topoJSON - description: Una extensión de GeoJSON que codifica topología. -- - term: aplicación TOTP - description: >- - Contraseña de un solo uso y duración definida. Este tipo de aplicación genera automáticamente un código de autenticación que cambia después de cierto período de tiempo. -- - term: árbol - description: >- - Ya sea un árbol de trabajo o un objeto de árbol junto con el blob dependiente y objetos de árbol (es decir, una representación almacenada de un árbol de trabajo). -- - term: objeto de árbol - description: >- - Un objeto que contiene una lista de nombres de archivo y modos, junto con refs para el blob o los objetos de árbol asociados. Un árbol es equivalente a un directorio. -- - term: TSV - description: Archivos separados por tabulaciones. -- - term: autenticación de dos factores - description: >- - También denominada 2FA. Una capa extra de seguridad que no solo requiere de un procedimiento de inicio de sesión estándar con nombre de usuario y contraseña, si no que también de un código de autenticación que es generado por una aplicación en el smartphone del usuario o enviado como un mensaje de texto (SMS). -- - term: UFW - description: Herramienta de configuración de firewall predeterminada de Ubuntu. -- - term: índice no configurado - description: Un índice que contiene entradas de índice no configuradas. -- - term: lista desordenada - description: Un lista con viñetas. -- - term: objeto inaccesible - description: 'Un objeto que no es accesible desde una rama, etiqueta ni ninguna otra referencia.' -- - term: URI - description: >- - Identificador uniforme de recursos. Una cadena de caracteres usada para identificar un recurso. -- - term: UTF-8 - description: Una codificación de caracteres capaz de codificar todo punto de código Unicode posible. -- - term: variable - description: 'En GraphQL, una manera de realizar consultas más dinámicas y eficaces.' -- - term: ID de IVA - description: Un número de identificación del impuesto al valor agregado para fines impositivos en la UE. -- - term: dirección de correo electrónico verificada - description: >- - Una dirección de correo electrónico asociado a una cuenta personal que el usuario ha verificado que es válida con un proceso de confirmación de seguridad. -- - term: máquina virtual - description: >- - Un entorno de aplicación que se instala en software e imita al hardware dedicado. También llamado una VM. -- - term: VPC - description: Nube privada virtual. Una red virtual dedicada a tu cuenta AWS. -- - term: VPN - description: Red privada virtual. -- - term: VMware - description: >- - Un producto Dell que ofrece servicios y software de virtualización de plataforma e informática en la nube. -- - term: permitido - description: >- - Una lista o registro de entidades a las que se les brinda un reconocimiento, acceso, movilidad, servicio o privilegio en particular. Las entidades en la lista serán aceptadas, aprobadas o reconocidas. -- - term: directorio de trabajo - description: El directorio de archivos en el que estás trabajando actualmente. -- - term: árbol de trabajo - description: >- - El árbol de archivos revisados reales. El árbol de trabajo generalmente contiene los contenidos del árbol de la confirmación de cambios del HEAD, además de cualquier cambio local que hayas realizado pero aún no confirmado. -- - term: WYSIWIG - description: >- - Lo que ves es lo que obtienes. Unas siglas que significan que el texto en pantalla se ve exactamente como será cuando sea procesado. -- - term: XenServer - description: Una plataforma de virtualización. -- - term: YAML - description: >- - Un lenguaje de serialización de datos natural que comúnmente se usa para archivos de configuración. -- - term: Integración continua - description: También abreviada como CI. -- - term: Entrega continua - description: También abreviada como CD. diff --git a/translations/es-XL/data/graphql/2.17/graphql_previews.enterprise.yml b/translations/es-XL/data/graphql/2.17/graphql_previews.enterprise.yml deleted file mode 100644 index e9f1c9c465..0000000000 --- a/translations/es-XL/data/graphql/2.17/graphql_previews.enterprise.yml +++ /dev/null @@ -1,268 +0,0 @@ ---- -- - title: Implementaciones - description: >- - Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. - toggled_by: ':flash-preview' - announcement: null - updates: null - toggled_on: - - DeploymentStatus.environment - - Mutation.createDeploymentStatus - - CreateDeploymentStatusInput - - CreateDeploymentStatusPayload - - Mutation.createDeployment - - CreateDeploymentInput - - CreateDeploymentPayload - owning_teams: - - '@github/ecosystem-api' -- - title: Vista Previa del Borrador de la Solicitud de Extracción - description: Esta vista previa agrega soporte para borradores de solicitudes de extracción. - toggled_by: ':shadow-cat-preview' - announcement: null - updates: null - toggled_on: - - Mutation.markPullRequestReadyForReview - - CreatePullRequestInput.draft - - PullRequest.isDraft - - MarkPullRequestReadyForReviewInput - - MarkPullRequestReadyForReviewPayload - owning_teams: - - '@github/pe-pull-requests' -- - title: Verificaciones - description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. - toggled_by: ':antiope-preview' - announcement: null - updates: null - toggled_on: - - CheckAnnotationRange - - CheckAnnotationPosition - - CheckAnnotationSpan - - CheckAnnotation - - CheckAnnotationConnection.nodes - - CheckAnnotationData - - CheckAnnotationEdge.node - - CheckAnnotationLevel - - CheckConclusionState - - CheckStatusState - - CheckSuiteAutoTriggerPreference - - CheckRun - - CheckRunConnection.nodes - - CheckRunEdge.node - - CheckRunAction - - CheckRunFilter - - CheckRunOutput - - CheckRunOutputImage - - CheckRunType - - CheckSuite - - CheckSuiteConnection.nodes - - CheckSuiteEdge.node - - CheckSuiteFilter - - CreateCheckRunInput - - CreateCheckRunPayload - - CreateCheckSuiteInput - - CreateCheckSuitePayload - - Commit.checkSuites - - Mutation.createCheckRun - - Mutation.createCheckSuite - - Mutation.rerequestCheckSuite - - Mutation.updateCheckRun - - Mutation.updateCheckSuitePreferences - - Subir - - RequestableCheckStatusState - - RerequestCheckSuiteInput - - RerequestCheckSuitePayload - - UpdateCheckRunInput - - UpdateCheckRunPayload - - UpdateCheckSuitePreferencesInput - - UpdateCheckSuitePreferencesPayload - owning_teams: - - '@github/ecosystem-primitives' -- - title: Debates de equipo - description: Agrega soporte para leer y administrar los debates entre equipos. - toggled_by: ':echo-preview' - announcement: null - updates: null - toggled_on: - - CreateTeamDiscussionCommentInput - - CreateTeamDiscussionCommentPayload - - CreateTeamDiscussionInput - - CreateTeamDiscussionPayload - - DeleteTeamDiscussionCommentInput - - DeleteTeamDiscussionCommentPayload - - DeleteTeamDiscussionInput - - DeleteTeamDiscussionPayload - - Mutation.createTeamDiscussion - - Mutation.createTeamDiscussionComment - - Mutation.deleteTeamDiscussion - - Mutation.deleteTeamDiscussionComment - - Mutation.updateTeamDiscussion - - Mutation.updateTeamDiscussionComment - - Team.discussion - - Team.discussions - - Team.discussionsResourcePath - - Team.discussionsUrl - - TeamDiscussion - - TeamDiscussionComment - - TeamDiscussionCommentConnection - - TeamDiscussionCommentEdge - - TeamDiscussionCommentOrder - - TeamDiscussionCommentOrderField - - TeamDiscussionConnection - - TeamDiscussionEdge - - TeamDiscussionOrder - - TeamDiscussionOrderField - - UpdateTeamDiscussionCommentInput - - UpdateTeamDiscussionCommentPayload - - UpdateTeamDiscussionInput - - UpdateTeamDiscussionPayload - owning_teams: - - '@github/identity' -- - title: Tarjetas de Visita Virtual - description: Esta vista previa agrega soporte para leer datos contextuales en tarjetas de visita virtual - toggled_by: ':hagar-preview' - announcement: null - updates: null - toggled_on: - - Issue.hovercard - - PullRequest.hovercard - - User.hovercard - - HovercardContext - - GenericHovercardContext - - Tarjeta de Visita Virtual - - OrganizationTeamsHovercardContext - - OrganizationsHovercardContext - - ReviewStatusHovercardContext - - ViewerHovercardContext - owning_teams: - - '@github/identity' -- - title: >- - MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. - description: >- - Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. - toggled_by: ':merge-info-preview' - announcement: null - updates: null - toggled_on: - - PullRequest.canBeRebased - - PullRequest.mergeStateStatus - owning_teams: - - '@github/pe-pull-requests' -- - title: Alertas de Vulnerabilidad en Repositorios - description: Esta vista previa agrega soporte para visualizar las alertas de vulnerabilidad para un repositorio. - toggled_by: ':vixen-preview' - announcement: null - updates: null - toggled_on: - - RepositoryVulnerabilityAlert - - Repository.vulnerabilityAlerts - - RepositoryVulnerabilityAlertConnection - - RepositoryVulnerabilityAlertEdge - owning_teams: - - '@github/ee-security-workflows' -- - title: Token de Clonado Temporal para Repositorios Privados - description: >- - Esta vista previa agrega soporte para acceder a un campo de token temporal para clonar repositorios privados. - toggled_by: ':daredevil-preview' - announcement: null - updates: null - toggled_on: - - Repository.tempCloneToken - owning_teams: - - '@github/experience-engineering-work' -- - title: Detalles de Eventos del Proyecto - description: >- - Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. - toggled_by: ':starfox-preview' - announcement: null - updates: null - toggled_on: - - AddedToProjectEvent.project - - AddedToProjectEvent.projectCard - - AddedToProjectEvent.projectColumnName - - ConvertedNoteToIssueEvent.project - - ConvertedNoteToIssueEvent.projectCard - - ConvertedNoteToIssueEvent.projectColumnName - - MovedColumnsInProjectEvent.project - - MovedColumnsInProjectEvent.projectCard - - MovedColumnsInProjectEvent.projectColumnName - - MovedColumnsInProjectEvent.previousProjectColumnName - - RemovedFromProjectEvent.project - - RemovedFromProjectEvent.projectColumnName - owning_teams: - - '@github/github-projects' -- - title: Vista Previa de Comentarios Minimizados - description: >- - Esta vista previa agrega soporte para comentarios minimizados en incidentes, solicitudes de extracción, confirmaciones y gists. - toggled_by: ':queen-beryl-preview' - announcement: null - updates: null - toggled_on: - - Mutation.minimizeComment - - Mutation.unminimizeComment - - Minimizable - owning_teams: - - '@github/pe-community-and-safety' -- - title: Crear adjuntos de contenido - description: Esta vista previa agrega soporte para crear adjuntos de contenido. - toggled_by: ':corsair-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createContentAttachment - owning_teams: - - '@github/ecosystem-primitives' -- - title: Vista Previa de Incidentes Fijados - description: Esta vista previa agrega soporte para los incidentes fijados. - toggled_by: ':elektra-preview' - announcement: null - updates: null - toggled_on: - - Repository.pinnedIssues - - PinnedIssue - - PinnedIssueEdge - - PinnedIssueConnection - - Mutation.pinIssue - - Mutation.unpinIssue - owning_teams: - - '@github/pe-pull-requests' -- - title: Vista Previa de Etiquetas - description: >- - Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. - toggled_by: ':bane-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createLabel - - CreateLabelPayload - - CreateLabelInput - - Mutation.deleteLabel - - DeleteLabelPayload - - DeleteLabelInput - - Mutation.updateLabel - - UpdateLabelPayload - - UpdateLabelInput - owning_teams: - - '@github/pe-pull-requests' -- - title: Importar Proyecto - description: Esta vista previa agrega soporte para importar proyectos. - toggled_by: ':slothette-preview' - announcement: null - updates: null - toggled_on: - - Mutation.importProject - owning_teams: - - '@github/pe-issues-projects' diff --git a/translations/es-XL/data/graphql/2.17/graphql_upcoming_changes.public-enterprise.yml b/translations/es-XL/data/graphql/2.17/graphql_upcoming_changes.public-enterprise.yml deleted file mode 100644 index 38df15bd2f..0000000000 --- a/translations/es-XL/data/graphql/2.17/graphql_upcoming_changes.public-enterprise.yml +++ /dev/null @@ -1,79 +0,0 @@ ---- -upcoming_changes: - - - location: Migration.uploadUrlTemplate - description: "Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución." - reason: "Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario." - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: Organization.members - description: "Se eliminará a `members`. Utiliza `Organization.membersWithRole` como sustitución." - reason: El campo `members` es obsoleto y se eliminará pronto. - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: xuorig - - - location: ContributionsCollection.firstIssueContribution.ignoreTimeRange - description: "Se eliminará a `ignoreTimeRange`. Utiliza una `ContributionsCollection` comenzando lo suficientemente antes" - reason: se eliminará a ignore_time_range - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: seejohnrun - - - location: ContributionsCollection.firstPullRequestContribution.ignoreTimeRange - description: "Se eliminará a `ignoreTimeRange`. Utiliza una `ContributionsCollection` comenzando lo suficientemente antes" - reason: se eliminará a ignore_time_range - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: seejohnrun - - - location: ContributionsCollection.firstRepositoryContribution.ignoreTimeRange - description: "Se eliminará a `ignoreTimeRange`. Utiliza una `ContributionsCollection` comenzando lo suficientemente antes" - reason: se eliminará a ignore_time_range - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: seejohnrun - - - location: ContributionsCollection.joinedGitHubContribution.ignoreTimeRange - description: "Se eliminará a `ignoreTimeRange`. Utiliza una `ContributionsCollection` comenzando lo suficientemente antes" - reason: se eliminará a ignore_time_range - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: seejohnrun - - - location: Organization.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: RepositoryOwner.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: ReviewDismissedEvent.message - description: "Se eliminará a `message`. Utiliza `dismissalMessage` en sustitución." - reason: "Se está elminando a `message` porque no es anulable, mientras que el campo subyacente es opcional." - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: nickvanw - - - location: ReviewDismissedEvent.messageHtml - description: "Se eliminará a `messageHtml`. Utiliza `dismissalMessageHTML` en sustitución." - reason: "Se está elminando a `messageHtml` porque no es anulable, mientras que el campo subyacente es opcional." - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: nickvanw - - - location: User.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 diff --git a/translations/es-XL/data/graphql/2.18/graphql_previews.enterprise.yml b/translations/es-XL/data/graphql/2.18/graphql_previews.enterprise.yml deleted file mode 100644 index f0788f9da0..0000000000 --- a/translations/es-XL/data/graphql/2.18/graphql_previews.enterprise.yml +++ /dev/null @@ -1,409 +0,0 @@ ---- -- - title: Registro de Auditoría - description: Esta vista previa agrega soporte para la lectura de entradas de Registros de Auditoría. - toggled_by: ':audit-log-preview' - announcement: null - updates: null - toggled_on: - - AccountPlanChangeAuditEntry.actorLocation - - BusinessAddOrganizationAuditEntry.actorLocation - - IssueCommentUpdateAuditEntry.actorLocation - - OauthApplicationDestroyAuditEntry.actorLocation - - OauthApplicationResetSecretAuditEntry.actorLocation - - OauthApplicationRevokeTokensAuditEntry.actorLocation - - OauthApplicationTransferAuditEntry.actorLocation - - OrgAcceptBusinessInvitationAuditEntry.actorLocation - - Organization.auditLog - - OrgAuditLogExportAuditEntry.actorLocation - - OrgBillingSignupErrorAuditEntry.actorLocation - - OrgCancelBusinessInvitationAuditEntry.actorLocation - - OrgCancelInvitationAuditEntry.actorLocation - - OrgConfigDisableContributorsOnlyAuditEntry.actorLocation - - OrgConfigDisableSockpuppetDisallowedAuditEntry.actorLocation - - OrgConfigEnableContributorsOnlyAuditEntry.actorLocation - - OrgConfigEnableSockpuppetDisallowedAuditEntry.actorLocation - - OrgCreateAuditEntry.actorLocation - - OrgRenameAuditEntry.actorLocation - - PrivateRepositoryForkingClearAuditEntry.actorLocation - - ProjectCreateAuditEntry.actorLocation - - RepoAddTopicAuditEntry.actorLocation - - RepoArchivedAuditEntry.actorLocation - - RepoChangeMergeSettingAuditEntry.actorLocation - - RepoCreateAuditEntry.actorLocation - - RepoDestroyAuditEntry.actorLocation - - RepoDisableAuditEntry.actorLocation - - RepoEnableAuditEntry.actorLocation - - RepoPagesCnameAuditEntry.actorLocation - - RepoPagesCreateAuditEntry.actorLocation - - RepoPagesDestroyAuditEntry.actorLocation - - RepoPagesHttpsRedirectDisabledAuditEntry.actorLocation - - RepoPagesHttpsRedirectEnabledAuditEntry.actorLocation - - RepoPagesSourceAuditEntry.actorLocation - - RepoRemoveTopicAuditEntry.actorLocation - - RepoRenameAuditEntry.actorLocation - - RepositoryVisibilityChangeClearAuditEntry.actorLocation - - RepoTransferAuditEntry.actorLocation - - RepoTransferStartAuditEntry.actorLocation - - RepoUnarchivedAuditEntry.actorLocation - - RepoUpdateMemberAuditEntry.actorLocation - - TeamChangePrivacyAuditEntry.actorLocation - - TeamCreateAuditEntry.actorLocation - - TeamDeleteAuditEntry.actorLocation - - TeamDestroyAuditEntry.actorLocation - - TeamRenameAuditEntry.actorLocation - - TeamUpdatePermissionAuditEntry.actorLocation - - TeamUpdateRepositoryPermissionAuditEntry.actorLocation - - UserAddEmailAuditEntry.actorLocation - - UserStatusUpdateAuditEntry.actorLocation - - AuditEntryActor - - OrganizationAuditEntry - - OrgRestoreMemberAuditEntryMembership - - AuditLogOrder - - AuditEntry - - EnterpriseAuditEntryData - - OauthApplicationAuditEntryData - - OrganizationAuditEntryData - - RepositoryAuditEntryData - - TeamAuditEntryData - - ActorLocation - - MembersCanDeleteReposClearAuditEntry - - MembersCanDeleteReposDisableAuditEntry - - MembersCanDeleteReposEnableAuditEntry - - OauthApplicationCreateAuditEntry - - OrgAddBillingManagerAuditEntry - - OrgAddMemberAuditEntry - - OrgBlockUserAuditEntry - - OrgConfigDisableCollaboratorsOnlyAuditEntry - - OrgConfigEnableCollaboratorsOnlyAuditEntry - - OrgDisableOauthAppRestrictionsAuditEntry - - OrgDisableSamlAuditEntry - - OrgDisableTwoFactorRequirementAuditEntry - - OrgEnableOauthAppRestrictionsAuditEntry - - OrgEnableSamlAuditEntry - - OrgEnableTwoFactorRequirementAuditEntry - - OrgInviteMemberAuditEntry - - OrgInviteToBusinessAuditEntry - - OrgOauthAppAccessApprovedAuditEntry - - OrgOauthAppAccessDeniedAuditEntry - - OrgOauthAppAccessRequestedAuditEntry - - OrgRemoveBillingManagerAuditEntry - - OrgRemoveMemberAuditEntry - - OrgRemoveOutsideCollaboratorAuditEntry - - OrgRestoreMemberAuditEntry - - OrgRestoreMemberMembershipOrganizationAuditEntryData - - OrgRestoreMemberMembershipRepositoryAuditEntryData - - OrgRestoreMemberMembershipTeamAuditEntryData - - OrgUnblockUserAuditEntry - - OrgUpdateDefaultRepositoryPermissionAuditEntry - - OrgUpdateMemberAuditEntry - - OrgUpdateMemberRepositoryCreationPermissionAuditEntry - - OrgUpdateMemberRepositoryInvitationPermissionAuditEntry - - PrivateRepositoryForkingDisableAuditEntry - - PrivateRepositoryForkingEnableAuditEntry - - RepoAccessAuditEntry - - RepoAddMemberAuditEntry - - RepoConfigDisableAnonymousGitAccessAuditEntry - - RepoConfigDisableCollaboratorsOnlyAuditEntry - - RepoConfigDisableContributorsOnlyAuditEntry - - RepoConfigDisableSockpuppetDisallowedAuditEntry - - RepoConfigEnableAnonymousGitAccessAuditEntry - - RepoConfigEnableCollaboratorsOnlyAuditEntry - - RepoConfigEnableContributorsOnlyAuditEntry - - RepoConfigEnableSockpuppetDisallowedAuditEntry - - RepoConfigLockAnonymousGitAccessAuditEntry - - RepoConfigUnlockAnonymousGitAccessAuditEntry - - RepoRemoveMemberAuditEntry - - RepositoryVisibilityChangeDisableAuditEntry - - RepositoryVisibilityChangeEnableAuditEntry - - TeamAddMemberAuditEntry - - TeamAddRepositoryAuditEntry - - TeamChangeParentTeamAuditEntry - - TeamRemoveMemberAuditEntry - - TeamRemoveRepositoryAuditEntry - - AuditLogOrderField - - OauthApplicationCreateAuditEntryState - - OauthApplicationRevokeTokensAuditEntryState - - OrgAddMemberAuditEntryPermission - - OrgRemoveBillingManagerAuditEntryReason - - OrgRemoveMemberAuditEntryMembershipType - - OrgRemoveMemberAuditEntryReason - - OrgRemoveOutsideCollaboratorAuditEntryMembershipType - - OrgRemoveOutsideCollaboratorAuditEntryReason - - OrgUpdateDefaultRepositoryPermissionAuditEntryPermission - - OrgUpdateMemberAuditEntryPermission - - OrgUpdateMemberRepositoryCreationPermissionAuditEntryVisibility - - RepoAccessAuditEntryVisibility - - RepoAddMemberAuditEntryVisibility - - RepoRemoveMemberAuditEntryVisibility - - PreciseDateTime - owning_teams: - - '@github/audit-log' -- - title: Implementaciones - description: >- - Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. - toggled_by: ':flash-preview' - announcement: null - updates: null - toggled_on: - - DeploymentStatus.environment - - Mutation.createDeploymentStatus - - CreateDeploymentStatusInput - - CreateDeploymentStatusPayload - - Mutation.createDeployment - - CreateDeploymentInput - - CreateDeploymentPayload - owning_teams: - - '@github/ecosystem-api' -- - title: Vista Previa del Borrador de la Solicitud de Extracción - description: Esta vista previa agrega soporte para borradores de solicitudes de extracción. - toggled_by: ':shadow-cat-preview' - announcement: null - updates: null - toggled_on: - - Mutation.markPullRequestReadyForReview - - CreatePullRequestInput.draft - - PullRequest.isDraft - - MarkPullRequestReadyForReviewInput - - MarkPullRequestReadyForReviewPayload - owning_teams: - - '@github/pe-pull-requests' -- - title: Verificaciones - description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. - toggled_by: ':antiope-preview' - announcement: null - updates: null - toggled_on: - - CheckAnnotationRange - - CheckAnnotationPosition - - CheckAnnotationSpan - - CheckAnnotation - - CheckAnnotationConnection.nodes - - CheckAnnotationData - - CheckAnnotationEdge.node - - CheckAnnotationLevel - - CheckConclusionState - - CheckStatusState - - CheckSuiteAutoTriggerPreference - - CheckRun - - CheckRunConnection.nodes - - CheckRunEdge.node - - CheckRunAction - - CheckRunFilter - - CheckRunOutput - - CheckRunOutputImage - - CheckRunType - - CheckSuite - - CheckSuiteConnection.nodes - - CheckSuiteEdge.node - - CheckSuiteFilter - - CreateCheckRunInput - - CreateCheckRunPayload - - CreateCheckSuiteInput - - CreateCheckSuitePayload - - Commit.checkSuites - - Mutation.createCheckRun - - Mutation.createCheckSuite - - Mutation.rerequestCheckSuite - - Mutation.updateCheckRun - - Mutation.updateCheckSuitePreferences - - Subir - - RequestableCheckStatusState - - RerequestCheckSuiteInput - - RerequestCheckSuitePayload - - UpdateCheckRunInput - - UpdateCheckRunPayload - - UpdateCheckSuitePayload.checkSuite - - UpdateCheckSuitePreferencesInput - - UpdateCheckSuitePreferencesPayload - owning_teams: - - '@github/ecosystem-primitives' -- - title: Debates de equipo - description: Agrega soporte para leer y administrar los debates entre equipos. - toggled_by: ':echo-preview' - announcement: null - updates: null - toggled_on: - - CreateTeamDiscussionCommentInput - - CreateTeamDiscussionCommentPayload - - CreateTeamDiscussionInput - - CreateTeamDiscussionPayload - - DeleteTeamDiscussionCommentInput - - DeleteTeamDiscussionCommentPayload - - DeleteTeamDiscussionInput - - DeleteTeamDiscussionPayload - - Mutation.createTeamDiscussion - - Mutation.createTeamDiscussionComment - - Mutation.deleteTeamDiscussion - - Mutation.deleteTeamDiscussionComment - - Mutation.updateTeamDiscussion - - Mutation.updateTeamDiscussionComment - - Team.discussion - - Team.discussions - - Team.discussionsResourcePath - - Team.discussionsUrl - - TeamDiscussion - - TeamDiscussionComment - - TeamDiscussionCommentConnection - - TeamDiscussionCommentEdge - - TeamDiscussionCommentOrder - - TeamDiscussionCommentOrderField - - TeamDiscussionConnection - - TeamDiscussionEdge - - TeamDiscussionOrder - - TeamDiscussionOrderField - - UpdateTeamDiscussionCommentInput - - UpdateTeamDiscussionCommentPayload - - UpdateTeamDiscussionInput - - UpdateTeamDiscussionPayload - owning_teams: - - '@github/identity' -- - title: Tarjetas de Visita Virtual - description: Esta vista previa agrega soporte para leer datos contextuales en tarjetas de visita virtual - toggled_by: ':hagar-preview' - announcement: null - updates: null - toggled_on: - - Issue.hovercard - - PullRequest.hovercard - - User.hovercard - - HovercardContext - - GenericHovercardContext - - Tarjeta de Visita Virtual - - OrganizationTeamsHovercardContext - - OrganizationsHovercardContext - - ReviewStatusHovercardContext - - ViewerHovercardContext - owning_teams: - - '@github/identity' -- - title: >- - MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. - description: >- - Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. - toggled_by: ':merge-info-preview' - announcement: null - updates: null - toggled_on: - - PullRequest.canBeRebased - - PullRequest.mergeStateStatus - owning_teams: - - '@github/pe-pull-requests' -- - title: Alertas de Vulnerabilidad en Repositorios - description: Esta vista previa agrega soporte para visualizar las alertas de vulnerabilidad para un repositorio. - toggled_by: ':vixen-preview' - announcement: null - updates: null - toggled_on: - - RepositoryVulnerabilityAlert - - Repository.vulnerabilityAlerts - - RepositoryVulnerabilityAlertConnection - - RepositoryVulnerabilityAlertEdge - owning_teams: - - '@github/ee-security-workflows' -- - title: Token de Clonado Temporal para Repositorios Privados - description: >- - Esta vista previa agrega soporte para acceder a un campo de token temporal para clonar repositorios privados. - toggled_by: ':daredevil-preview' - announcement: null - updates: null - toggled_on: - - Repository.tempCloneToken - owning_teams: - - '@github/experience-engineering-work' -- - title: Detalles de Eventos del Proyecto - description: >- - Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. - toggled_by: ':starfox-preview' - announcement: null - updates: null - toggled_on: - - AddedToProjectEvent.project - - AddedToProjectEvent.projectCard - - AddedToProjectEvent.projectColumnName - - ConvertedNoteToIssueEvent.project - - ConvertedNoteToIssueEvent.projectCard - - ConvertedNoteToIssueEvent.projectColumnName - - MovedColumnsInProjectEvent.project - - MovedColumnsInProjectEvent.projectCard - - MovedColumnsInProjectEvent.projectColumnName - - MovedColumnsInProjectEvent.previousProjectColumnName - - RemovedFromProjectEvent.project - - RemovedFromProjectEvent.projectColumnName - owning_teams: - - '@github/github-projects' -- - title: Vista Previa de Comentarios Minimizados - description: >- - Esta vista previa agrega soporte para comentarios minimizados en incidentes, solicitudes de extracción, confirmaciones y gists. - toggled_by: ':queen-beryl-preview' - announcement: null - updates: null - toggled_on: - - Mutation.minimizeComment - - Mutation.unminimizeComment - - Minimizable - owning_teams: - - '@github/ce-community-and-safety' -- - title: Crear adjuntos de contenido - description: Esta vista previa agrega soporte para crear adjuntos de contenido. - toggled_by: ':corsair-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createContentAttachment - owning_teams: - - '@github/ecosystem-primitives' -- - title: Vista Previa de Incidentes Fijados - description: Esta vista previa agrega soporte para los incidentes fijados. - toggled_by: ':elektra-preview' - announcement: null - updates: null - toggled_on: - - Repository.pinnedIssues - - PinnedIssue - - PinnedIssueEdge - - PinnedIssueConnection - - Mutation.pinIssue - - Mutation.unpinIssue - owning_teams: - - '@github/pe-pull-requests' -- - title: Vista Previa de Etiquetas - description: >- - Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. - toggled_by: ':bane-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createLabel - - CreateLabelPayload - - CreateLabelInput - - Mutation.deleteLabel - - DeleteLabelPayload - - DeleteLabelInput - - Mutation.updateLabel - - UpdateLabelPayload - - UpdateLabelInput - owning_teams: - - '@github/pe-pull-requests' -- - title: Importar Proyecto - description: Esta vista previa agrega soporte para importar proyectos. - toggled_by: ':slothette-preview' - announcement: null - updates: null - toggled_on: - - Mutation.importProject - owning_teams: - - '@github/pe-issues-projects' diff --git a/translations/es-XL/data/graphql/2.18/graphql_upcoming_changes.public-enterprise.yml b/translations/es-XL/data/graphql/2.18/graphql_upcoming_changes.public-enterprise.yml deleted file mode 100644 index e8e6fa9ed9..0000000000 --- a/translations/es-XL/data/graphql/2.18/graphql_upcoming_changes.public-enterprise.yml +++ /dev/null @@ -1,100 +0,0 @@ ---- -upcoming_changes: - - - location: Migration.uploadUrlTemplate - description: "Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución." - reason: "Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario." - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: Organization.members - description: "Se eliminará a `members`. Utiliza `Organization.membersWithRole` como sustitución." - reason: El campo `members` es obsoleto y se eliminará pronto. - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: xuorig - - - location: ContributionsCollection.firstIssueContribution.ignoreTimeRange - description: "Se eliminará a `ignoreTimeRange`. Utiliza una `ContributionsCollection` comenzando lo suficientemente antes" - reason: se eliminará a ignore_time_range - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: seejohnrun - - - location: ContributionsCollection.firstPullRequestContribution.ignoreTimeRange - description: "Se eliminará a `ignoreTimeRange`. Utiliza una `ContributionsCollection` comenzando lo suficientemente antes" - reason: se eliminará a ignore_time_range - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: seejohnrun - - - location: ContributionsCollection.firstRepositoryContribution.ignoreTimeRange - description: "Se eliminará a `ignoreTimeRange`. Utiliza una `ContributionsCollection` comenzando lo suficientemente antes" - reason: se eliminará a ignore_time_range - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: seejohnrun - - - location: ContributionsCollection.joinedGitHubContribution.ignoreTimeRange - description: "Se eliminará a `ignoreTimeRange`. Utiliza una `ContributionsCollection` comenzando lo suficientemente antes" - reason: se eliminará a ignore_time_range - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: seejohnrun - - - location: ReviewDismissedEvent.message - description: "Se eliminará a `message`. Utiliza `dismissalMessage` en sustitución." - reason: "Se está elminando a `message` porque no es anulable, mientras que el campo subyacente es opcional." - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: nickvanw - - - location: ReviewDismissedEvent.messageHtml - description: "Se eliminará a `messageHtml`. Utiliza `dismissalMessageHTML` en sustitución." - reason: "Se está elminando a `messageHtml` porque no es anulable, mientras que el campo subyacente es opcional." - date: '2019-07-01T00:00:00+00:00' - criticality: breaking - owner: nickvanw - - - location: ContributionOrder.field - description: "Se eliminará a `field`. Sólo hay compatibilidad par aun solo campo de orden." - reason: "Se eliminará a `field`." - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Issue.timeline - description: "Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: Organization.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: PullRequest.timeline - description: "Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: RepositoryOwner.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: User.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 diff --git a/translations/es-XL/data/graphql/2.19/graphql_previews.enterprise.yml b/translations/es-XL/data/graphql/2.19/graphql_previews.enterprise.yml deleted file mode 100644 index eae1937927..0000000000 --- a/translations/es-XL/data/graphql/2.19/graphql_previews.enterprise.yml +++ /dev/null @@ -1,228 +0,0 @@ ---- -- - title: Implementaciones - description: >- - Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. - toggled_by: ':flash-preview' - announcement: null - updates: null - toggled_on: - - DeploymentStatus.environment - - Mutation.createDeploymentStatus - - CreateDeploymentStatusInput - - CreateDeploymentStatusPayload - - Mutation.createDeployment - - CreateDeploymentInput - - CreateDeploymentPayload - owning_teams: - - '@github/ecosystem-api' -- - title: Vista Previa del Borrador de la Solicitud de Extracción - description: Esta vista previa agrega soporte para borradores de solicitudes de extracción. - toggled_by: ':shadow-cat-preview' - announcement: null - updates: null - toggled_on: - - Mutation.markPullRequestReadyForReview - - CreatePullRequestInput.draft - - PullRequest.isDraft - - MarkPullRequestReadyForReviewInput - - MarkPullRequestReadyForReviewPayload - owning_teams: - - '@github/pe-pull-requests' -- - title: Verificaciones - description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. - toggled_by: ':antiope-preview' - announcement: null - updates: null - toggled_on: - - CheckAnnotationRange - - CheckAnnotationPosition - - CheckAnnotationSpan - - CheckAnnotation - - CheckAnnotationConnection.nodes - - CheckAnnotationData - - CheckAnnotationEdge.node - - CheckAnnotationLevel - - CheckConclusionState - - CheckStatusState - - CheckSuiteAutoTriggerPreference - - CheckRun - - CheckRunConnection.nodes - - CheckRunEdge.node - - CheckRunAction - - CheckRunFilter - - CheckRunOutput - - CheckRunOutputImage - - CheckRunType - - CheckSuite - - CheckSuiteConnection.nodes - - CheckSuiteEdge.node - - CheckSuiteFilter - - CreateCheckRunInput - - CreateCheckRunPayload - - CreateCheckSuiteInput - - CreateCheckSuitePayload - - Commit.checkSuites - - Mutation.createCheckRun - - Mutation.createCheckSuite - - Mutation.rerequestCheckSuite - - Mutation.updateCheckRun - - Mutation.updateCheckSuitePreferences - - Subir - - RequestableCheckStatusState - - RerequestCheckSuiteInput - - RerequestCheckSuitePayload - - UpdateCheckRunInput - - UpdateCheckRunPayload - - UpdateCheckSuitePayload.checkSuite - - UpdateCheckSuitePreferencesInput - - UpdateCheckSuitePreferencesPayload - owning_teams: - - '@github/ecosystem-primitives' -- - title: >- - MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. - description: >- - Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. - toggled_by: ':merge-info-preview' - announcement: null - updates: null - toggled_on: - - PullRequest.canBeRebased - - PullRequest.mergeStateStatus - owning_teams: - - '@github/pe-pull-requests' -- - title: Alertas de Vulnerabilidad en Repositorios - description: Esta vista previa agrega soporte para visualizar las alertas de vulnerabilidad para un repositorio. - toggled_by: ':vixen-preview' - announcement: null - updates: null - toggled_on: - - RepositoryVulnerabilityAlert - - Repository.vulnerabilityAlerts - - RepositoryVulnerabilityAlertConnection - - RepositoryVulnerabilityAlertEdge - owning_teams: - - '@github/ee-security-workflows' -- - title: Token de Clonado Temporal para Repositorios Privados - description: >- - Esta vista previa agrega soporte para acceder a un campo de token temporal para clonar repositorios privados. - toggled_by: ':daredevil-preview' - announcement: null - updates: null - toggled_on: - - Repository.tempCloneToken - owning_teams: - - '@github/experience-engineering-work' -- - title: Detalles de Eventos del Proyecto - description: >- - Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. - toggled_by: ':starfox-preview' - announcement: null - updates: null - toggled_on: - - AddedToProjectEvent.project - - AddedToProjectEvent.projectCard - - AddedToProjectEvent.projectColumnName - - ConvertedNoteToIssueEvent.project - - ConvertedNoteToIssueEvent.projectCard - - ConvertedNoteToIssueEvent.projectColumnName - - MovedColumnsInProjectEvent.project - - MovedColumnsInProjectEvent.projectCard - - MovedColumnsInProjectEvent.projectColumnName - - MovedColumnsInProjectEvent.previousProjectColumnName - - RemovedFromProjectEvent.project - - RemovedFromProjectEvent.projectColumnName - owning_teams: - - '@github/github-projects' -- - title: Vista Previa de Comentarios Minimizados - description: >- - Esta vista previa agrega soporte para comentarios minimizados en incidentes, solicitudes de extracción, confirmaciones y gists. - toggled_by: ':queen-beryl-preview' - announcement: null - updates: null - toggled_on: - - Mutation.minimizeComment - - Mutation.unminimizeComment - - Minimizable - owning_teams: - - '@github/ce-community-and-safety' -- - title: Crear adjuntos de contenido - description: Esta vista previa agrega soporte para crear adjuntos de contenido. - toggled_by: ':corsair-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createContentAttachment - owning_teams: - - '@github/ecosystem-primitives' -- - title: Vista Previa de Incidentes Fijados - description: Esta vista previa agrega soporte para los incidentes fijados. - toggled_by: ':elektra-preview' - announcement: null - updates: null - toggled_on: - - Repository.pinnedIssues - - PinnedIssue - - PinnedIssueEdge - - PinnedIssueConnection - - Mutation.pinIssue - - Mutation.unpinIssue - owning_teams: - - '@github/pe-pull-requests' -- - title: Vista Previa de Etiquetas - description: >- - Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. - toggled_by: ':bane-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createLabel - - CreateLabelPayload - - CreateLabelInput - - Mutation.deleteLabel - - DeleteLabelPayload - - DeleteLabelInput - - Mutation.updateLabel - - UpdateLabelPayload - - UpdateLabelInput - owning_teams: - - '@github/pe-pull-requests' -- - title: Importar Proyecto - description: Esta vista previa agrega soporte para importar proyectos. - toggled_by: ':slothette-preview' - announcement: null - updates: null - toggled_on: - - Mutation.importProject - owning_teams: - - '@github/pe-issues-projects' -- - title: Vista Previa de Comentarios de Línea Múltiple - description: Esta vista previa agrega soporte para comentarios de línea múltiple y posicionados en un blob. - toggled_by: ':comfort-fade-preview' - announcement: null - updates: null - toggled_on: - - Mutation.addPullRequestReviewThread - - AddPullRequestReviewThreadInput - - AddPullRequestReviewInput.threads - - DiffSide - - PullRequestReviewThread.startLine - - PullRequestReviewThread.originalStartLine - - PullRequestReviewThread.startDiffSide - - PullRequestReviewThread.line - - PullRequestReviewThread.originalLine - - PullRequestReviewThread.diffSide - owning_teams: - - '@github/pe-pull-requests' diff --git a/translations/es-XL/data/graphql/2.19/graphql_upcoming_changes.public-enterprise.yml b/translations/es-XL/data/graphql/2.19/graphql_upcoming_changes.public-enterprise.yml deleted file mode 100644 index 84c15144a5..0000000000 --- a/translations/es-XL/data/graphql/2.19/graphql_upcoming_changes.public-enterprise.yml +++ /dev/null @@ -1,65 +0,0 @@ ---- -upcoming_changes: - - - location: Migration.uploadUrlTemplate - description: "Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución." - reason: "Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario." - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: ContributionOrder.field - description: "Se eliminará a `field`. Sólo hay compatibilidad par aun solo campo de orden." - reason: "Se eliminará a `field`." - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Issue.timeline - description: "Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: Organization.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: PullRequest.timeline - description: "Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: RepositoryOwner.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: User.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: AssignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: UnassignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling diff --git a/translations/es-XL/data/graphql/2.20/graphql_previews.enterprise.yml b/translations/es-XL/data/graphql/2.20/graphql_previews.enterprise.yml deleted file mode 100644 index 2d00f4a65d..0000000000 --- a/translations/es-XL/data/graphql/2.20/graphql_previews.enterprise.yml +++ /dev/null @@ -1,284 +0,0 @@ ---- -- - title: Paquetes de GitHub - description: Esta vista previa agrega soporte para los objetos que se relacionen con GitHub Packages. - toggled_by: ':packages-preview' - announcement: null - updates: null - toggled_on: - - Package - - PackageFile - - PackageFileOrder - - PackageFileOrderField - - PackageOrder - - PackageOrderField - - PackageOwner - - PackageStatistics - - PackageTag - - PackageVersion - - PackageVersionOrder - - PackageVersionOrderField - - PackageVersionStatistics - - Organization.packages - - PackageMetadatum.packageVersion - - Repository.packages - - User.packages - - PackageConnection.nodes - - PackageFileConnection.nodes - - PackageTagConnection.nodes - - PackageVersionConnection.nodes - - PackageEdge.node - - PackageFileEdge.node - - PackageTagEdge.node - - PackageVersionEdge.node - - CreateRegistryPackageFilePayload.packageFile - - CreateRegistryPackageVersionMetadataPayload.packageVersion - - CreateRegistryPackageVersionPayload.packageVersion - - DeleteRegistryPackagePayload.package - - DeleteRegistryPackageTagPayload.package - - SetRegistryPackageTagPayload.package - - UpdateRegistryPackageFilePayload.packageFile - - UpdateRegistryPackageVersionPayload.packageVersion - - CreatePackageVersionPayload.packageVersion - - UpdatePackageVersionPayload.packageVersion - - CreatePackageFilePayload.packageFile - - UpdatePackageFilePayload.packageFile - - CreatePackageVersionMetadataPayload.packageVersion - - AddPackageTagPayload.package - - DeletePackageTagPayload.package - owning_teams: - - '@github/pe-package-registry' -- - title: Implementaciones - description: >- - Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. - toggled_by: ':flash-preview' - announcement: null - updates: null - toggled_on: - - DeploymentStatus.environment - - Mutation.createDeploymentStatus - - CreateDeploymentStatusInput - - CreateDeploymentStatusPayload - - Mutation.createDeployment - - CreateDeploymentInput - - CreateDeploymentPayload - owning_teams: - - '@github/ecosystem-api' -- - title: Vista Previa del Borrador de la Solicitud de Extracción - description: Esta vista previa agrega soporte para borradores de solicitudes de extracción. - toggled_by: ':shadow-cat-preview' - announcement: null - updates: null - toggled_on: - - Mutation.markPullRequestReadyForReview - - CreatePullRequestInput.draft - - PullRequest.isDraft - - MarkPullRequestReadyForReviewInput - - MarkPullRequestReadyForReviewPayload - owning_teams: - - '@github/pe-pull-requests' -- - title: Verificaciones - description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. - toggled_by: ':antiope-preview' - announcement: null - updates: null - toggled_on: - - CheckAnnotationRange - - CheckAnnotationPosition - - CheckAnnotationSpan - - CheckAnnotation - - CheckAnnotationConnection.nodes - - CheckAnnotationData - - CheckAnnotationEdge.node - - CheckAnnotationLevel - - CheckConclusionState - - CheckStatusState - - CheckSuiteAutoTriggerPreference - - CheckRun - - CheckRunConnection.nodes - - CheckRunEdge.node - - CheckRunAction - - CheckRunFilter - - CheckRunOutput - - CheckRunOutputImage - - CheckRunType - - CheckSuite - - CheckSuiteConnection.nodes - - CheckSuiteEdge.node - - CheckSuiteFilter - - CreateCheckRunInput - - CreateCheckRunPayload - - CreateCheckSuiteInput - - CreateCheckSuitePayload - - Commit.checkSuites - - Mutation.createCheckRun - - Mutation.createCheckSuite - - Mutation.rerequestCheckSuite - - Mutation.updateCheckRun - - Mutation.updateCheckSuitePreferences - - Subir - - RequestableCheckStatusState - - RerequestCheckSuiteInput - - RerequestCheckSuitePayload - - UpdateCheckRunInput - - UpdateCheckRunPayload - - UpdateCheckSuitePayload.checkSuite - - UpdateCheckSuitePreferencesInput - - UpdateCheckSuitePreferencesPayload - owning_teams: - - '@github/ecosystem-primitives' -- - title: >- - MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. - description: >- - Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. - toggled_by: ':merge-info-preview' - announcement: null - updates: null - toggled_on: - - PullRequest.canBeRebased - - PullRequest.mergeStateStatus - owning_teams: - - '@github/pe-pull-requests' -- - title: UpdateRefsPreview - Actualiza varias refs en una sola operación. - description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. - toggled_by: ':update-refs-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateRefs - - GitRefname - - RefUpdate - - UpdateRefsInput - - UpdateRefsPayload - owning_teams: - - '@github/pe-repos' -- - title: Detalles de Eventos del Proyecto - description: >- - Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. - toggled_by: ':starfox-preview' - announcement: null - updates: null - toggled_on: - - AddedToProjectEvent.project - - AddedToProjectEvent.projectCard - - AddedToProjectEvent.projectColumnName - - ConvertedNoteToIssueEvent.project - - ConvertedNoteToIssueEvent.projectCard - - ConvertedNoteToIssueEvent.projectColumnName - - MovedColumnsInProjectEvent.project - - MovedColumnsInProjectEvent.projectCard - - MovedColumnsInProjectEvent.projectColumnName - - MovedColumnsInProjectEvent.previousProjectColumnName - - RemovedFromProjectEvent.project - - RemovedFromProjectEvent.projectColumnName - owning_teams: - - '@github/github-projects' -- - title: Vista Previa de Comentarios Minimizados - description: >- - Esta vista previa agrega soporte para comentarios minimizados en incidentes, solicitudes de extracción, confirmaciones y gists. - toggled_by: ':queen-beryl-preview' - announcement: null - updates: null - toggled_on: - - Mutation.minimizeComment - - Mutation.unminimizeComment - - Minimizable - owning_teams: - - '@github/ce-community-and-safety' -- - title: Crear adjuntos de contenido - description: Esta vista previa agrega soporte para crear adjuntos de contenido. - toggled_by: ':corsair-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createContentAttachment - owning_teams: - - '@github/ecosystem-primitives' -- - title: Vista Previa de Incidentes Fijados - description: Esta vista previa agrega soporte para los incidentes fijados. - toggled_by: ':elektra-preview' - announcement: null - updates: null - toggled_on: - - Repository.pinnedIssues - - PinnedIssue - - PinnedIssueEdge - - PinnedIssueConnection - - Mutation.pinIssue - - Mutation.unpinIssue - owning_teams: - - '@github/pe-pull-requests' -- - title: Vista Previa de Etiquetas - description: >- - Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. - toggled_by: ':bane-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createLabel - - CreateLabelPayload - - CreateLabelInput - - Mutation.deleteLabel - - DeleteLabelPayload - - DeleteLabelInput - - Mutation.updateLabel - - UpdateLabelPayload - - UpdateLabelInput - owning_teams: - - '@github/pe-pull-requests' -- - title: Importar Proyecto - description: Esta vista previa agrega soporte para importar proyectos. - toggled_by: ':slothette-preview' - announcement: null - updates: null - toggled_on: - - Mutation.importProject - owning_teams: - - '@github/pe-issues-projects' -- - title: Vista Previa de Comentarios de Línea Múltiple - description: Esta vista previa agrega soporte para comentarios de línea múltiple y posicionados en un blob. - toggled_by: ':comfort-fade-preview' - announcement: null - updates: null - toggled_on: - - Mutation.addPullRequestReviewThread - - AddPullRequestReviewThreadInput - - AddPullRequestReviewInput.threads - - DiffSide - - PullRequestReviewThread.startLine - - PullRequestReviewThread.originalStartLine - - PullRequestReviewThread.startDiffSide - - PullRequestReviewThread.line - - PullRequestReviewThread.originalLine - - PullRequestReviewThread.diffSide - owning_teams: - - '@github/pe-pull-requests' -- - title: Vista Previa de las Tareas de Revisión del Equipo - description: >- - Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. - toggled_by: ':stone-crop-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateTeamReviewAssignment - - UpdateTeamReviewAssignmentInput - - TeamReviewAssignmentAlgorithm - - Team.reviewRequestDelegationEnabled - - Team.reviewRequestDelegationAlgorithm - - Team.reviewRequestDelegationMemberCount - - Team.reviewRequestDelegationNotifyTeam - owning_teams: - - '@github/pe-pull-requests' diff --git a/translations/es-XL/data/graphql/2.20/graphql_upcoming_changes.public-enterprise.yml b/translations/es-XL/data/graphql/2.20/graphql_upcoming_changes.public-enterprise.yml deleted file mode 100644 index 3d6e0ab223..0000000000 --- a/translations/es-XL/data/graphql/2.20/graphql_upcoming_changes.public-enterprise.yml +++ /dev/null @@ -1,562 +0,0 @@ ---- -upcoming_changes: - - - location: Migration.uploadUrlTemplate - description: "Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución." - reason: "Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario." - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: ContributionOrder.field - description: "Se eliminará a `field`. Sólo hay compatibilidad par aun solo campo de orden." - reason: "Se eliminará a `field`." - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Issue.timeline - description: "Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: Organization.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: PullRequest.timeline - description: "Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: RepositoryOwner.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: User.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: AssignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: EnterpriseBillingInfo.availableSeats - description: "Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución." - reason: "Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva" - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: BlakeWilliams - - - location: EnterpriseBillingInfo.seats - description: "Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución." - reason: "Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva" - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: BlakeWilliams - - - location: UnassignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: Organization.registryPackages - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Organization.registryPackagesForQuery - description: "Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.color - description: "Se eliminará a `color`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.latestVersion - description: "Se eliminará a `latestVersion`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.name - description: "Se eliminará a `name`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.nameWithOwner - description: "Se eliminará a `nameWithOwner`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.packageFileByGuid - description: "Se eliminará a `packageFileByGuid`. Utiliza el objeto `Package`." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.packageFileBySha256 - description: "Se eliminará a `packageFileBySha256`. Utiliza el objeto `Package`." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.packageType - description: "Se eliminará a `packageType`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.preReleaseVersions - description: "Se eliminará a `preReleaseVersions`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.registryPackageType - description: "Se eliminará a `registryPackageType`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.repository - description: "Se eliminará a `repository`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.statistics - description: "Se eliminará a `statistics`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.tags - description: "Se eliminará a `tags`. Utiliza el objeto `Package`." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.topics - description: "Se eliminará a `topics`. Utiliza el objeto `Package`." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.version - description: "Se eliminará a `version`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.versionByPlatform - description: "Se eliminará a `versionByPlatform`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.versionBySha256 - description: "Se eliminará a `versionBySha256`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.versions - description: "Se eliminará a `versions`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.versionsByMetadatum - description: "Se eliminará a `versionsByMetadatum`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageDependency.dependencyType - description: "Se eliminará a `dependencyType`. Utiliza el objeto `PackageDependency` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageDependency.name - description: "Se eliminará a `name`. Utiliza el objeto `PackageDependency` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageDependency.version - description: "Se eliminará a `version`. Utiliza el objeto `PackageDependency` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.guid - description: "Se eliminará a `guid`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.md5 - description: "Se eliminará a `md5`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.metadataUrl - description: "Se eliminará a `metadataUrl`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.name - description: "Se eliminará a `name`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.packageVersion - description: "Se eliminará a `packageVersion`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.sha1 - description: "Se eliminará a `sha1`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.sha256 - description: "Se eliminará a `sha256`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.size - description: "Se eliminará a `size`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.url - description: "Se eliminará a `url`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageOwner.registryPackages - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageSearch.registryPackagesForQuery - description: "Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsThisMonth - description: "Se eliminará a `downloadsThisMonth`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsThisWeek - description: "Se eliminará a `downloadsThisWeek`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsThisYear - description: "Se eliminará a `downloadsThisYear`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsToday - description: "Se eliminará a `downloadsToday`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsTotalCount - description: "Se eliminará a `downloadsTotalCount`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageTag.name - description: "Se eliminará a `name`. Utiliza el objeto `PackageTag` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageTag.version - description: "Se eliminará a `version`. Utiliza el objeto `PackageTag` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.dependencies - description: "Se eliminará a `dependencies`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.fileByName - description: "Se eliminará a `fileByName`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.files - description: "Se eliminará a `files`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.installationCommand - description: "Se eliminará a `installationCommand`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.manifest - description: "Se eliminará a `manifest`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.platform - description: "Se eliminará a `platform`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.preRelease - description: "Se eliminará a `preRelease`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.readme - description: "Se eliminará a `readme`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.readmeHtml - description: "Se eliminará a `readmeHtml`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.registryPackage - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.release - description: "Se eliminará a `release`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.sha256 - description: "Se eliminará a `sha256`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.size - description: "Se eliminará a `size`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.statistics - description: "Se eliminará a `statistics`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.summary - description: "Se eliminará a `summary`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.updatedAt - description: "Se eliminará a `updatedAt`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.version - description: "Se eliminará a `version`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.viewerCanEdit - description: "Se eliminará a `viewerCanEdit`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "Se eliminará a `downloadsThisMonth`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "Se eliminará a `downloadsThisWeek`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "Se eliminará a `downloadsThisYear`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsToday - description: "Se eliminará a `downloadsToday`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "Se eliminará a `downloadsTotalCount`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Repository.registryPackages - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Repository.registryPackagesForQuery - description: "Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Sponsorship.maintainer - description: "Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución." - reason: "Se eliminará a `Sponsorship.maintainer`." - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: antn - - - location: User.registryPackages - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: User.registryPackagesForQuery - description: "Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi diff --git a/translations/es-XL/data/graphql/2.21/graphql_previews.enterprise.yml b/translations/es-XL/data/graphql/2.21/graphql_previews.enterprise.yml deleted file mode 100644 index 4f82ef8d59..0000000000 --- a/translations/es-XL/data/graphql/2.21/graphql_previews.enterprise.yml +++ /dev/null @@ -1,242 +0,0 @@ ---- -- - title: Acceso al borrado de versiones de paquetes - description: >- - Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados. - toggled_by: ':package-deletes-preview' - announcement: null - updates: null - toggled_on: - - Mutation.deletePackageVersion - - RegistryPackageVersion.deleted - owning_teams: - - '@github/pe-package-registry' -- - title: Paquetes de GitHub - description: Esta vista previa agrega soporte para los objetos que se relacionen con GitHub Packages. - toggled_by: ':packages-preview' - announcement: null - updates: null - toggled_on: - - Package - - PackageFile - - PackageFileOrder - - PackageFileOrderField - - PackageOrder - - PackageOrderField - - PackageOwner - - PackageStatistics - - PackageTag - - PackageVersion - - PackageVersionOrder - - PackageVersionOrderField - - PackageVersionStatistics - - Organization.packages - - PackageMetadatum.packageVersion - - Repository.packages - - User.packages - - PackageConnection.nodes - - PackageFileConnection.nodes - - PackageTagConnection.nodes - - PackageVersionConnection.nodes - - PackageEdge.node - - PackageFileEdge.node - - PackageTagEdge.node - - PackageVersionEdge.node - - CreatePackageVersionPayload.packageVersion - - UpdatePackageVersionPayload.packageVersion - - CreatePackageFilePayload.packageFile - - UpdatePackageFilePayload.packageFile - - CreatePackageVersionMetadataPayload.packageVersion - - AddPackageTagPayload.package - - DeletePackageTagPayload.package - owning_teams: - - '@github/pe-package-registry' -- - title: Implementaciones - description: >- - Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. - toggled_by: ':flash-preview' - announcement: null - updates: null - toggled_on: - - DeploymentStatus.environment - - Mutation.createDeploymentStatus - - CreateDeploymentStatusInput - - CreateDeploymentStatusPayload - - Mutation.createDeployment - - CreateDeploymentInput - - CreateDeploymentPayload - owning_teams: - - '@github/ecosystem-api' -- - title: Verificaciones - description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. - toggled_by: ':antiope-preview' - announcement: null - updates: null - toggled_on: - - CheckAnnotationRange - - CheckAnnotationPosition - - CheckAnnotationSpan - - CheckAnnotation - - CheckAnnotationConnection.nodes - - CheckAnnotationData - - CheckAnnotationEdge.node - - CheckAnnotationLevel - - CheckConclusionState - - CheckStatusState - - CheckSuiteAutoTriggerPreference - - CheckRun - - CheckRunConnection.nodes - - CheckRunEdge.node - - CheckRunAction - - CheckRunFilter - - CheckRunOutput - - CheckRunOutputImage - - CheckRunType - - CheckSuite - - CheckSuiteConnection.nodes - - CheckSuiteEdge.node - - CheckSuiteFilter - - CreateCheckRunInput - - CreateCheckRunPayload - - CreateCheckSuiteInput - - CreateCheckSuitePayload - - Commit.checkSuites - - Mutation.createCheckRun - - Mutation.createCheckSuite - - Mutation.rerequestCheckSuite - - Mutation.updateCheckRun - - Mutation.updateCheckSuitePreferences - - Subir - - RequestableCheckStatusState - - RerequestCheckSuiteInput - - RerequestCheckSuitePayload - - UpdateCheckRunInput - - UpdateCheckRunPayload - - UpdateCheckSuitePayload.checkSuite - - UpdateCheckSuitePreferencesInput - - UpdateCheckSuitePreferencesPayload - owning_teams: - - '@github/ce-extensibility' -- - title: >- - MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. - description: >- - Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. - toggled_by: ':merge-info-preview' - announcement: null - updates: null - toggled_on: - - PullRequest.canBeRebased - - PullRequest.mergeStateStatus - owning_teams: - - '@github/pe-pull-requests' -- - title: UpdateRefsPreview - Actualiza varias refs en una sola operación. - description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. - toggled_by: ':update-refs-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateRefs - - GitRefname - - RefUpdate - - UpdateRefsInput - - UpdateRefsPayload - owning_teams: - - '@github/pe-repos' -- - title: Detalles de Eventos del Proyecto - description: >- - Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. - toggled_by: ':starfox-preview' - announcement: null - updates: null - toggled_on: - - AddedToProjectEvent.project - - AddedToProjectEvent.projectCard - - AddedToProjectEvent.projectColumnName - - ConvertedNoteToIssueEvent.project - - ConvertedNoteToIssueEvent.projectCard - - ConvertedNoteToIssueEvent.projectColumnName - - MovedColumnsInProjectEvent.project - - MovedColumnsInProjectEvent.projectCard - - MovedColumnsInProjectEvent.projectColumnName - - MovedColumnsInProjectEvent.previousProjectColumnName - - RemovedFromProjectEvent.project - - RemovedFromProjectEvent.projectColumnName - owning_teams: - - '@github/github-projects' -- - title: Crear adjuntos de contenido - description: Esta vista previa agrega soporte para crear adjuntos de contenido. - toggled_by: ':corsair-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createContentAttachment - owning_teams: - - '@github/ce-extensibility' -- - title: Vista Previa de Incidentes Fijados - description: Esta vista previa agrega soporte para los incidentes fijados. - toggled_by: ':elektra-preview' - announcement: null - updates: null - toggled_on: - - Repository.pinnedIssues - - PinnedIssue - - PinnedIssueEdge - - PinnedIssueConnection - - Mutation.pinIssue - - Mutation.unpinIssue - owning_teams: - - '@github/pe-pull-requests' -- - title: Vista Previa de Etiquetas - description: >- - Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. - toggled_by: ':bane-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createLabel - - CreateLabelPayload - - CreateLabelInput - - Mutation.deleteLabel - - DeleteLabelPayload - - DeleteLabelInput - - Mutation.updateLabel - - UpdateLabelPayload - - UpdateLabelInput - owning_teams: - - '@github/pe-pull-requests' -- - title: Importar Proyecto - description: Esta vista previa agrega soporte para importar proyectos. - toggled_by: ':slothette-preview' - announcement: null - updates: null - toggled_on: - - Mutation.importProject - owning_teams: - - '@github/pe-issues-projects' -- - title: Vista Previa de las Tareas de Revisión del Equipo - description: >- - Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. - toggled_by: ':stone-crop-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateTeamReviewAssignment - - UpdateTeamReviewAssignmentInput - - TeamReviewAssignmentAlgorithm - - Team.reviewRequestDelegationEnabled - - Team.reviewRequestDelegationAlgorithm - - Team.reviewRequestDelegationMemberCount - - Team.reviewRequestDelegationNotifyTeam - owning_teams: - - '@github/pe-pull-requests' diff --git a/translations/es-XL/data/graphql/2.21/graphql_upcoming_changes.public-enterprise.yml b/translations/es-XL/data/graphql/2.21/graphql_upcoming_changes.public-enterprise.yml deleted file mode 100644 index 9fa8ff9fc7..0000000000 --- a/translations/es-XL/data/graphql/2.21/graphql_upcoming_changes.public-enterprise.yml +++ /dev/null @@ -1,569 +0,0 @@ ---- -upcoming_changes: - - - location: Migration.uploadUrlTemplate - description: "Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución." - reason: "Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario." - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: ContributionOrder.field - description: "Se eliminará a `field`. Sólo hay compatibilidad par aun solo campo de orden." - reason: "Se eliminará a `field`." - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Organization.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: RepositoryOwner.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: User.pinnedRepositories - description: "Se eliminará a `pinnedRepositories`. Utiliza ProfileOwner.pinnedItems en sustitución." - reason: se eliminará a pinnedRepositories - date: '2019-10-01T00:00:00+00:00' - criticality: breaking - owner: cheshire137 - - - location: AssignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: EnterpriseBillingInfo.availableSeats - description: "Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución." - reason: "Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva" - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: BlakeWilliams - - - location: EnterpriseBillingInfo.seats - description: "Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución." - reason: "Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva" - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: BlakeWilliams - - - location: UnassignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: Organization.registryPackages - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Organization.registryPackagesForQuery - description: "Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.color - description: "Se eliminará a `color`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.latestVersion - description: "Se eliminará a `latestVersion`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.name - description: "Se eliminará a `name`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.nameWithOwner - description: "Se eliminará a `nameWithOwner`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.packageFileByGuid - description: "Se eliminará a `packageFileByGuid`. Utiliza el objeto `Package`." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.packageFileBySha256 - description: "Se eliminará a `packageFileBySha256`. Utiliza el objeto `Package`." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.packageType - description: "Se eliminará a `packageType`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.preReleaseVersions - description: "Se eliminará a `preReleaseVersions`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.registryPackageType - description: "Se eliminará a `registryPackageType`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.repository - description: "Se eliminará a `repository`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.statistics - description: "Se eliminará a `statistics`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.tags - description: "Se eliminará a `tags`. Utiliza el objeto `Package`." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.topics - description: "Se eliminará a `topics`. Utiliza el objeto `Package`." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.version - description: "Se eliminará a `version`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.versionByPlatform - description: "Se eliminará a `versionByPlatform`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.versionBySha256 - description: "Se eliminará a `versionBySha256`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.versions - description: "Se eliminará a `versions`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackage.versionsByMetadatum - description: "Se eliminará a `versionsByMetadatum`. Utiliza el objeto `Package` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageDependency.dependencyType - description: "Se eliminará a `dependencyType`. Utiliza el objeto `PackageDependency` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageDependency.name - description: "Se eliminará a `name`. Utiliza el objeto `PackageDependency` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageDependency.version - description: "Se eliminará a `version`. Utiliza el objeto `PackageDependency` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.guid - description: "Se eliminará a `guid`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.md5 - description: "Se eliminará a `md5`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.metadataUrl - description: "Se eliminará a `metadataUrl`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.name - description: "Se eliminará a `name`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.packageVersion - description: "Se eliminará a `packageVersion`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.sha1 - description: "Se eliminará a `sha1`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.sha256 - description: "Se eliminará a `sha256`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.size - description: "Se eliminará a `size`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageFile.url - description: "Se eliminará a `url`. Utiliza el objeto `PackageFile` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageOwner.registryPackages - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageSearch.registryPackagesForQuery - description: "Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsThisMonth - description: "Se eliminará a `downloadsThisMonth`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsThisWeek - description: "Se eliminará a `downloadsThisWeek`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsThisYear - description: "Se eliminará a `downloadsThisYear`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsToday - description: "Se eliminará a `downloadsToday`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageStatistics.downloadsTotalCount - description: "Se eliminará a `downloadsTotalCount`. Utiliza el objeto `PackageStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageTag.name - description: "Se eliminará a `name`. Utiliza el objeto `PackageTag` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageTag.version - description: "Se eliminará a `version`. Utiliza el objeto `PackageTag` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.deleted - description: "Se eliminará a `deleted`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.dependencies - description: "Se eliminará a `dependencies`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.fileByName - description: "Se eliminará a `fileByName`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.files - description: "Se eliminará a `files`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.installationCommand - description: "Se eliminará a `installationCommand`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.manifest - description: "Se eliminará a `manifest`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.platform - description: "Se eliminará a `platform`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.preRelease - description: "Se eliminará a `preRelease`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.readme - description: "Se eliminará a `readme`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.readmeHtml - description: "Se eliminará a `readmeHtml`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.registryPackage - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.release - description: "Se eliminará a `release`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.sha256 - description: "Se eliminará a `sha256`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.size - description: "Se eliminará a `size`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.statistics - description: "Se eliminará a `statistics`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.summary - description: "Se eliminará a `summary`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.updatedAt - description: "Se eliminará a `updatedAt`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.version - description: "Se eliminará a `version`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersion.viewerCanEdit - description: "Se eliminará a `viewerCanEdit`. Utiliza el objeto `PackageVersion` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsThisMonth - description: "Se eliminará a `downloadsThisMonth`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsThisWeek - description: "Se eliminará a `downloadsThisWeek`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsThisYear - description: "Se eliminará a `downloadsThisYear`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsToday - description: "Se eliminará a `downloadsToday`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: RegistryPackageVersionStatistics.downloadsTotalCount - description: "Se eliminará a `downloadsTotalCount`. Utiliza el objeto `PackageVersionStatistics` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Repository.registryPackages - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Repository.registryPackagesForQuery - description: "Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Sponsorship.maintainer - description: "Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución." - reason: "Se eliminará a `Sponsorship.maintainer`." - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: antn - - - location: User.registryPackages - description: "Se eliminará a `registryPackages`. Utiliza el objeto `PackageOwner` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: User.registryPackagesForQuery - description: "Se eliminará a `registryPackagesForQuery`. Utiliza el objeto `PackageSearch` en sustitución." - reason: Renombrar los campos y objetos de GitHub Packages. - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: dinahshi - - - location: Issue.timeline - description: "Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: PullRequest.timeline - description: "Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea diff --git a/translations/es-XL/data/graphql/2.22/graphql_previews.enterprise.yml b/translations/es-XL/data/graphql/2.22/graphql_previews.enterprise.yml deleted file mode 100644 index 192bbc33f2..0000000000 --- a/translations/es-XL/data/graphql/2.22/graphql_previews.enterprise.yml +++ /dev/null @@ -1,200 +0,0 @@ ---- -- - title: Acceso al borrado de versiones de paquetes - description: >- - Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados. - toggled_by: ':package-deletes-preview' - announcement: null - updates: null - toggled_on: - - Mutation.deletePackageVersion - owning_teams: - - '@github/pe-package-registry' -- - title: Implementaciones - description: >- - Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. - toggled_by: ':flash-preview' - announcement: null - updates: null - toggled_on: - - DeploymentStatus.environment - - Mutation.createDeploymentStatus - - CreateDeploymentStatusInput - - CreateDeploymentStatusPayload - - Mutation.createDeployment - - CreateDeploymentInput - - CreateDeploymentPayload - owning_teams: - - '@github/ecosystem-api' -- - title: Verificaciones - description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. - toggled_by: ':antiope-preview' - announcement: null - updates: null - toggled_on: - - CheckAnnotationRange - - CheckAnnotationPosition - - CheckAnnotationSpan - - CheckAnnotation - - CheckAnnotationConnection.nodes - - CheckAnnotationData - - CheckAnnotationEdge.node - - CheckAnnotationLevel - - CheckConclusionState - - CheckStatusState - - CheckSuiteAutoTriggerPreference - - CheckRun - - CheckRunConnection.nodes - - CheckRunEdge.node - - CheckRunAction - - CheckRunFilter - - CheckRunOutput - - CheckRunOutputImage - - CheckRunType - - CheckSuite - - CheckSuiteConnection.nodes - - CheckSuiteEdge.node - - CheckSuiteFilter - - CreateCheckRunInput - - CreateCheckRunPayload - - CreateCheckSuiteInput - - CreateCheckSuitePayload - - Commit.checkSuites - - Mutation.createCheckRun - - Mutation.createCheckSuite - - Mutation.rerequestCheckSuite - - Mutation.updateCheckRun - - Mutation.updateCheckSuitePreferences - - Subir - - RequestableCheckStatusState - - RerequestCheckSuiteInput - - RerequestCheckSuitePayload - - UpdateCheckRunInput - - UpdateCheckRunPayload - - UpdateCheckSuitePayload.checkSuite - - UpdateCheckSuitePreferencesInput - - UpdateCheckSuitePreferencesPayload - owning_teams: - - '@github/ce-extensibility' -- - title: >- - MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. - description: >- - Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. - toggled_by: ':merge-info-preview' - announcement: null - updates: null - toggled_on: - - PullRequest.canBeRebased - - PullRequest.mergeStateStatus - owning_teams: - - '@github/pe-pull-requests' -- - title: UpdateRefsPreview - Actualiza varias refs en una sola operación. - description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. - toggled_by: ':update-refs-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateRefs - - GitRefname - - RefUpdate - - UpdateRefsInput - - UpdateRefsPayload - owning_teams: - - '@github/pe-repos' -- - title: Detalles de Eventos del Proyecto - description: >- - Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. - toggled_by: ':starfox-preview' - announcement: null - updates: null - toggled_on: - - AddedToProjectEvent.project - - AddedToProjectEvent.projectCard - - AddedToProjectEvent.projectColumnName - - ConvertedNoteToIssueEvent.project - - ConvertedNoteToIssueEvent.projectCard - - ConvertedNoteToIssueEvent.projectColumnName - - MovedColumnsInProjectEvent.project - - MovedColumnsInProjectEvent.projectCard - - MovedColumnsInProjectEvent.projectColumnName - - MovedColumnsInProjectEvent.previousProjectColumnName - - RemovedFromProjectEvent.project - - RemovedFromProjectEvent.projectColumnName - owning_teams: - - '@github/github-projects' -- - title: Crear adjuntos de contenido - description: Esta vista previa agrega soporte para crear adjuntos de contenido. - toggled_by: ':corsair-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createContentAttachment - owning_teams: - - '@github/ce-extensibility' -- - title: Vista Previa de Incidentes Fijados - description: Esta vista previa agrega soporte para los incidentes fijados. - toggled_by: ':elektra-preview' - announcement: null - updates: null - toggled_on: - - Repository.pinnedIssues - - PinnedIssue - - PinnedIssueEdge - - PinnedIssueConnection - - Mutation.pinIssue - - Mutation.unpinIssue - owning_teams: - - '@github/pe-pull-requests' -- - title: Vista Previa de Etiquetas - description: >- - Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. - toggled_by: ':bane-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createLabel - - CreateLabelPayload - - CreateLabelInput - - Mutation.deleteLabel - - DeleteLabelPayload - - DeleteLabelInput - - Mutation.updateLabel - - UpdateLabelPayload - - UpdateLabelInput - owning_teams: - - '@github/pe-pull-requests' -- - title: Importar Proyecto - description: Esta vista previa agrega soporte para importar proyectos. - toggled_by: ':slothette-preview' - announcement: null - updates: null - toggled_on: - - Mutation.importProject - owning_teams: - - '@github/pe-issues-projects' -- - title: Vista Previa de las Tareas de Revisión del Equipo - description: >- - Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. - toggled_by: ':stone-crop-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateTeamReviewAssignment - - UpdateTeamReviewAssignmentInput - - TeamReviewAssignmentAlgorithm - - Team.reviewRequestDelegationEnabled - - Team.reviewRequestDelegationAlgorithm - - Team.reviewRequestDelegationMemberCount - - Team.reviewRequestDelegationNotifyTeam - owning_teams: - - '@github/pe-pull-requests' diff --git a/translations/es-XL/data/graphql/2.22/graphql_upcoming_changes.public-enterprise.yml b/translations/es-XL/data/graphql/2.22/graphql_upcoming_changes.public-enterprise.yml deleted file mode 100644 index 1280279fc5..0000000000 --- a/translations/es-XL/data/graphql/2.22/graphql_upcoming_changes.public-enterprise.yml +++ /dev/null @@ -1,128 +0,0 @@ ---- -upcoming_changes: - - - location: Migration.uploadUrlTemplate - description: "Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución." - reason: "Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario." - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: AssignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: EnterpriseBillingInfo.availableSeats - description: "Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución." - reason: "Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva" - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: BlakeWilliams - - - location: EnterpriseBillingInfo.seats - description: "Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución." - reason: "Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva" - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: BlakeWilliams - - - location: UnassignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: Sponsorship.maintainer - description: "Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución." - reason: "Se eliminará a `Sponsorship.maintainer`." - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: antn - - - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "se eliminará a `isUnlicensed`." - reason: Todos los miembros pendientes consumen una licencia - date: '2020-07-01T00:00:00+00:00' - criticality: breaking - owner: BrentWheeldon - - - location: EnterpriseOwnerInfo.pendingCollaborators - description: "se eliminará a `pendingCollaborators`. En vez de esto, utiliza el campo `pendingCollaboratorInvitations`." - reason: Las invitaciones a los repositorios ahora pueden asociarse con una dirección de correo electrónico, no únicamente con un invitado. - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: jdennes - - - location: Issue.timeline - description: "Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: PullRequest.timeline - description: "Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: RepositoryCollaboratorEdge.permission - description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. - reason: Este campo podría devolver valores adicionales - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: oneill38 - - - location: RepositoryInvitation.permission - description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. - reason: Este campo podría devolver valores adicionales - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: oneill38 - - - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "Se eliminará a `INVITEE_LOGIN`." - reason: "`INVITEE_LOGIN` ya no es un valor de campo válido. Las invitaciones al repositorio pueden asociarse ahora con una dirección de correo electrónico, no solo con un invitado." - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: jdennes - - - location: Sponsorship.sponsor - description: "Se eliminará a `sponsor`. En vez de esto, utiliza `Sponsorship.sponsorEntity`." - reason: "Se eliminará a `Sponsorship.sponsor`." - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: nholden - - - location: TeamRepositoryEdge.permission - description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. - reason: Este campo podría devolver valores adicionales - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: oneill38 - - - location: EnterpriseMemberEdge.isUnlicensed - description: "se eliminará a `isUnlicensed`." - reason: Todos los miembros consumen una licencia - date: '2021-01-01T00:00:00+00:00' - criticality: breaking - owner: BrentWheeldon - - - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "se eliminará a `isUnlicensed`." - reason: Todos los colaboradores externos consumen una licencia - date: '2021-01-01T00:00:00+00:00' - criticality: breaking - owner: BrentWheeldon - - - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "se eliminará a `isUnlicensed`." - reason: Todos los colaboradores pendientes consumen una licencia - date: '2021-01-01T00:00:00+00:00' - criticality: breaking - owner: BrentWheeldon diff --git a/translations/es-XL/data/graphql/graphql_previews.yml b/translations/es-XL/data/graphql/graphql_previews.yml deleted file mode 100644 index e53245d759..0000000000 --- a/translations/es-XL/data/graphql/graphql_previews.yml +++ /dev/null @@ -1,217 +0,0 @@ ---- -- - title: Acceso al borrado de versiones de paquetes - description: >- - Esta vista previa agrega soporte para la mutación DeletePackageVersion, la cual habilita el borrado de versiones de paquetes privados. - toggled_by: ':package-deletes-preview' - announcement: null - updates: null - toggled_on: - - Mutation.deletePackageVersion - owning_teams: - - '@github/pe-package-registry' -- - title: Implementaciones - description: >- - Esta vista previa añade soporte para las mutaciones de despliegue y para nuevas características de despliegue. - toggled_by: ':flash-preview' - announcement: null - updates: null - toggled_on: - - DeploymentStatus.environment - - Mutation.createDeploymentStatus - - CreateDeploymentStatusInput - - CreateDeploymentStatusPayload - - Mutation.createDeployment - - CreateDeploymentInput - - CreateDeploymentPayload - owning_teams: - - '@github/ecosystem-api' -- - title: Verificaciones - description: Esta vista previa agrega soporte para leer las verificaciones que crea GitHub Apps. - toggled_by: ':antiope-preview' - announcement: null - updates: null - toggled_on: - - CheckAnnotationRange - - CheckAnnotationPosition - - CheckAnnotationSpan - - CheckAnnotation - - CheckAnnotationConnection.nodes - - CheckAnnotationData - - CheckAnnotationEdge.node - - CheckAnnotationLevel - - CheckConclusionState - - CheckStatusState - - CheckSuiteAutoTriggerPreference - - CheckRun - - CheckRunConnection.nodes - - CheckRunEdge.node - - CheckRunAction - - CheckRunFilter - - CheckRunOutput - - CheckRunOutputImage - - CheckRunType - - CheckSuite - - CheckSuiteConnection.nodes - - CheckSuiteEdge.node - - CheckSuiteFilter - - CreateCheckRunInput - - CreateCheckRunPayload - - CreateCheckSuiteInput - - CreateCheckSuitePayload - - Commit.checkSuites - - Mutation.createCheckRun - - Mutation.createCheckSuite - - Mutation.rerequestCheckSuite - - Mutation.updateCheckRun - - Mutation.updateCheckSuitePreferences - - Subir - - RequestableCheckStatusState - - RerequestCheckSuiteInput - - RerequestCheckSuitePayload - - UpdateCheckRunInput - - UpdateCheckRunPayload - - UpdateCheckSuitePayload.checkSuite - - UpdateCheckSuitePreferencesInput - - UpdateCheckSuitePreferencesPayload - owning_teams: - - '@github/ce-extensibility' -- - title: >- - MergeInfoPreview - Información más detallada sobre un estado de fusión de una solicitud de extracción. - description: >- - Esta vista previa agrega soporte para acceder a campos que proporcionan información más detallada sobre el estado de la fusión de una solicitud de extracción. - toggled_by: ':merge-info-preview' - announcement: null - updates: null - toggled_on: - - PullRequest.canBeRebased - - PullRequest.mergeStateStatus - owning_teams: - - '@github/pe-pull-requests' -- - title: UpdateRefsPreview - Actualiza varias refs en una sola operación. - description: Esta vista previa agrega soporte para actualizar varias refs en una sola operación. - toggled_by: ':update-refs-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateRefs - - GitRefname - - RefUpdate - - UpdateRefsInput - - UpdateRefsPayload - owning_teams: - - '@github/pe-repos' -- - title: Acceso a la Gráfica de Dependencias de los Repositorios - description: Esta vista previa agrega soporte para leer una gráfica de dependencias para un repositorio. - toggled_by: ':hawkgirl-preview' - announcement: null - updates: null - toggled_on: - - DependencyGraphManifest - - Repository.dependencyGraphManifests - - DependencyGraphManifestEdge - - DependencyGraphManifestConnection - - DependencyGraphDependency - - DependencyGraphDependencyEdge - - DependencyGraphDependencyConnection - - DependencyGraphPackageRelease.dependencies - owning_teams: - - '@github/dsp-dependency-graph' -- - title: Detalles de Eventos del Proyecto - description: >- - Esta vista previa añade detalles sobre el proyecto, tarjeta de proyecto y columna de proyecto a un evento de incidencia relacionado con un proyecto. - toggled_by: ':starfox-preview' - announcement: null - updates: null - toggled_on: - - AddedToProjectEvent.project - - AddedToProjectEvent.projectCard - - AddedToProjectEvent.projectColumnName - - ConvertedNoteToIssueEvent.project - - ConvertedNoteToIssueEvent.projectCard - - ConvertedNoteToIssueEvent.projectColumnName - - MovedColumnsInProjectEvent.project - - MovedColumnsInProjectEvent.projectCard - - MovedColumnsInProjectEvent.projectColumnName - - MovedColumnsInProjectEvent.previousProjectColumnName - - RemovedFromProjectEvent.project - - RemovedFromProjectEvent.projectColumnName - owning_teams: - - '@github/github-projects' -- - title: Crear adjuntos de contenido - description: Esta vista previa agrega soporte para crear adjuntos de contenido. - toggled_by: ':corsair-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createContentAttachment - owning_teams: - - '@github/ce-extensibility' -- - title: Vista Previa de Incidentes Fijados - description: Esta vista previa agrega soporte para los incidentes fijados. - toggled_by: ':elektra-preview' - announcement: null - updates: null - toggled_on: - - Repository.pinnedIssues - - PinnedIssue - - PinnedIssueEdge - - PinnedIssueConnection - - Mutation.pinIssue - - Mutation.unpinIssue - owning_teams: - - '@github/pe-pull-requests' -- - title: Vista Previa de Etiquetas - description: >- - Esta vista previa agrega soporte para crear, actualizar, agregar y borrar etiquetas. - toggled_by: ':bane-preview' - announcement: null - updates: null - toggled_on: - - Mutation.createLabel - - CreateLabelPayload - - CreateLabelInput - - Mutation.deleteLabel - - DeleteLabelPayload - - DeleteLabelInput - - Mutation.updateLabel - - UpdateLabelPayload - - UpdateLabelInput - owning_teams: - - '@github/pe-pull-requests' -- - title: Importar Proyecto - description: Esta vista previa agrega soporte para importar proyectos. - toggled_by: ':slothette-preview' - announcement: null - updates: null - toggled_on: - - Mutation.importProject - owning_teams: - - '@github/pe-issues-projects' -- - title: Vista Previa de las Tareas de Revisión del Equipo - description: >- - Esta vista previa agrega soporte para actualizar la configuración para las tareas de revisión del equipo. - toggled_by: ':stone-crop-preview' - announcement: null - updates: null - toggled_on: - - Mutation.updateTeamReviewAssignment - - UpdateTeamReviewAssignmentInput - - TeamReviewAssignmentAlgorithm - - Team.reviewRequestDelegationEnabled - - Team.reviewRequestDelegationAlgorithm - - Team.reviewRequestDelegationMemberCount - - Team.reviewRequestDelegationNotifyTeam - owning_teams: - - '@github/pe-pull-requests' diff --git a/translations/es-XL/data/graphql/graphql_upcoming_changes.public.yml b/translations/es-XL/data/graphql/graphql_upcoming_changes.public.yml deleted file mode 100644 index 5abdcf8573..0000000000 --- a/translations/es-XL/data/graphql/graphql_upcoming_changes.public.yml +++ /dev/null @@ -1,142 +0,0 @@ ---- -upcoming_changes: - - - location: Migration.uploadUrlTemplate - description: "Se eliminará a `uploadUrlTemplate`. Utiliza `uploadUrl` en sustitución." - reason: "Se está eliminando a `uploadUrlTemplate` porque no es una URL estándar y agrega un paso extra al usuario." - date: '2019-04-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: AssignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: EnterpriseBillingInfo.availableSeats - description: "Se eliminará a `availableSeats`. Utiliza EnterpriseBillingInfo.totalAvailableLicenses en sustitución." - reason: "Se reemplazará a `availableSeats` con `totalAvailableLicenses` para proporcionar más claridad en el valor que se devuelva" - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: BlakeWilliams - - - location: EnterpriseBillingInfo.seats - description: "Se eliminará a `seats`. Utiliza EnterpriseBillingInfo.totalLicenses en sustitución." - reason: "Se reemplazará a `seats` con `totalLicenses` para proporcionar más claridad en el valor que se devuelva" - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: BlakeWilliams - - - location: UnassignedEvent.user - description: "Se eliminará a `user`. Utiliza el campo `assignee` en sustitución." - reason: Los asignados ahora pueden ser maniquíes. - date: '2020-01-01T00:00:00+00:00' - criticality: breaking - owner: tambling - - - location: Query.sponsorsListing - description: "Se eliminará a `sponsorsListing`. Utiliza `Sponsorable.sponsorsListing` en sustitución." - reason: "Se eliminará a `Query.sponsorsListing`." - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: antn - - - location: Sponsorship.maintainer - description: "Se eliminará a `maintainer`. Utiliza `Sponsorship.sponsorable` en sustitución." - reason: "Se eliminará a `Sponsorship.maintainer`." - date: '2020-04-01T00:00:00+00:00' - criticality: breaking - owner: antn - - - location: EnterprisePendingMemberInvitationEdge.isUnlicensed - description: "se eliminará a `isUnlicensed`." - reason: Todos los miembros pendientes consumen una licencia - date: '2020-07-01T00:00:00+00:00' - criticality: breaking - owner: BrentWheeldon - - - location: EnterpriseOwnerInfo.pendingCollaborators - description: "se eliminará a `pendingCollaborators`. En vez de esto, utiliza el campo `pendingCollaboratorInvitations`." - reason: Las invitaciones a los repositorios ahora pueden asociarse con una dirección de correo electrónico, no únicamente con un invitado. - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: jdennes - - - location: Issue.timeline - description: "Se eliminará a `timeline`. Utiliza Issue.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: PullRequest.timeline - description: "Se eliminará a `timeline`. Utiliza PullRequest.timelineItems en sustitución." - reason: "Se eliminará a `timeline`" - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: mikesea - - - location: RepositoryCollaboratorEdge.permission - description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. - reason: Este campo podría devolver valores adicionales - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: oneill38 - - - location: RepositoryInvitation.permission - description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. - reason: Este campo podría devolver valores adicionales - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: oneill38 - - - location: RepositoryInvitationOrderField.INVITEE_LOGIN - description: "Se eliminará a `INVITEE_LOGIN`." - reason: "`INVITEE_LOGIN` ya no es un valor de campo válido. Las invitaciones al repositorio pueden asociarse ahora con una dirección de correo electrónico, no solo con un invitado." - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: jdennes - - - location: Sponsorship.sponsor - description: "Se eliminará a `sponsor`. En vez de esto, utiliza `Sponsorship.sponsorEntity`." - reason: "Se eliminará a `Sponsorship.sponsor`." - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: nholden - - - location: TeamRepositoryEdge.permission - description: El tipo para `permission` cambiará de `RepositoryPermission!` a `String`. - reason: Este campo podría devolver valores adicionales - date: '2020-10-01T00:00:00+00:00' - criticality: breaking - owner: oneill38 - - - location: EnterpriseMemberEdge.isUnlicensed - description: "se eliminará a `isUnlicensed`." - reason: Todos los miembros consumen una licencia - date: '2021-01-01T00:00:00+00:00' - criticality: breaking - owner: BrentWheeldon - - - location: EnterpriseOutsideCollaboratorEdge.isUnlicensed - description: "se eliminará a `isUnlicensed`." - reason: Todos los colaboradores externos consumen una licencia - date: '2021-01-01T00:00:00+00:00' - criticality: breaking - owner: BrentWheeldon - - - location: EnterprisePendingCollaboratorEdge.isUnlicensed - description: "se eliminará a `isUnlicensed`." - reason: Todos los colaboradores pendientes consumen una licencia - date: '2021-01-01T00:00:00+00:00' - criticality: breaking - owner: BrentWheeldon - - - location: MergeStateStatus.DRAFT - description: "`DRAFT` will be removed. Use PullRequest.isDraft instead." - reason: DRAFT state will be removed from this enum and `isDraft` should be used instead - date: '2021-01-01T00:00:00+00:00' - criticality: breaking - owner: nplasterer diff --git a/translations/es-XL/data/products.yml b/translations/es-XL/data/products.yml deleted file mode 100644 index b063b1fee6..0000000000 --- a/translations/es-XL/data/products.yml +++ /dev/null @@ -1,23 +0,0 @@ ---- -#this sequence sets the product order in the sidebar -#the product IDs match keys in lib/all-products.js -#note this file should not be translated -productsInOrder: - - github - - enterpriseServer - - acciones - - paquetes - - developers - - rest - - graphql - - insights - - desktop -#TODO this can be removed when the new versioning handling is in place -hasEnterpriseUserVersions: - - github - - acciones - - developers - - rest - - graphql - - insights - - paquetes diff --git a/translations/es-XL/data/reusables/actions/about-artifacts.md b/translations/es-XL/data/reusables/actions/about-artifacts.md deleted file mode 100644 index 7926bd44d7..0000000000 --- a/translations/es-XL/data/reusables/actions/about-artifacts.md +++ /dev/null @@ -1 +0,0 @@ -Los artefactos te habilitan para compartir datos entre jobs en un flujo de trabajo y para almacenar datos una vez que este flujo se complete. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/about-secrets.md b/translations/es-XL/data/reusables/actions/about-secrets.md deleted file mode 100644 index 07c14fecc7..0000000000 --- a/translations/es-XL/data/reusables/actions/about-secrets.md +++ /dev/null @@ -1 +0,0 @@ -Los secretos cifrados te permiten almacenar información sensible, tal como los tokens de acceso, en tu repositorio u organización. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/about-self-hosted-runners.md b/translations/es-XL/data/reusables/actions/about-self-hosted-runners.md deleted file mode 100644 index 145229ae24..0000000000 --- a/translations/es-XL/data/reusables/actions/about-self-hosted-runners.md +++ /dev/null @@ -1 +0,0 @@ -Los ejecutores auto-hospedados te permiten hospedr tus propios ejecutores y personalizar el ambiente que se utiliza para ejecutar jobs en tus flujos de trabajo de {% data variables.product.prodname_actions %}. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/about-workflow-jobs.md b/translations/es-XL/data/reusables/actions/about-workflow-jobs.md deleted file mode 100644 index d8ea2df414..0000000000 --- a/translations/es-XL/data/reusables/actions/about-workflow-jobs.md +++ /dev/null @@ -1 +0,0 @@ -Un job de flujode trabajo es un cconjunto de pasos que se ejecutan en el mismo ejecutor. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/about-workflow-runs.md b/translations/es-XL/data/reusables/actions/about-workflow-runs.md deleted file mode 100644 index 0de08cbeed..0000000000 --- a/translations/es-XL/data/reusables/actions/about-workflow-runs.md +++ /dev/null @@ -1 +0,0 @@ -Una ejecución de flujode trabajo es una instancia en tu flujo de trabajo que se ejecuta cuando ocurre el evento pre-configurado. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/about-workflows.md b/translations/es-XL/data/reusables/actions/about-workflows.md deleted file mode 100644 index 3b2c2715c4..0000000000 --- a/translations/es-XL/data/reusables/actions/about-workflows.md +++ /dev/null @@ -1 +0,0 @@ -Los flujos de trabajo automatizan el ciclo de vida de tu desarrollo de software con una amplia gama de herramientas y servicios. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/actions-app-actions-permissions-api.md b/translations/es-XL/data/reusables/actions/actions-app-actions-permissions-api.md deleted file mode 100644 index 0f009e6e70..0000000000 --- a/translations/es-XL/data/reusables/actions/actions-app-actions-permissions-api.md +++ /dev/null @@ -1 +0,0 @@ -Las {% data variables.product.prodname_github_app %}s deben contar con el permiso de `actions` para utilizar esta API. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/actions-authentication.md b/translations/es-XL/data/reusables/actions/actions-authentication.md deleted file mode 100644 index 848641b1fe..0000000000 --- a/translations/es-XL/data/reusables/actions/actions-authentication.md +++ /dev/null @@ -1 +0,0 @@ -Esta API está disponible para los usuarios autenticados, las {% data variables.product.prodname_oauth_app %}s, y las {% data variables.product.prodname_github_app %}s. 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 aquellos públicos. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/actions-not-verified.md b/translations/es-XL/data/reusables/actions/actions-not-verified.md deleted file mode 100644 index 1b58b2bce0..0000000000 --- a/translations/es-XL/data/reusables/actions/actions-not-verified.md +++ /dev/null @@ -1 +0,0 @@ -Cualquiera puede publicar una acción en {% data variables.product.prodname_marketplace %} siempre y cuando cumplan con las condiciones de servicio. A diferencia de las apps, las {% data variables.product.prodname_actions %} que se listan en {% data variables.product.prodname_marketplace %} no se verifican con {% data variables.product.prodname_dotcom %}. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/enterprise-actions-permissions.md b/translations/es-XL/data/reusables/actions/enterprise-actions-permissions.md deleted file mode 100644 index 4e18631034..0000000000 --- a/translations/es-XL/data/reusables/actions/enterprise-actions-permissions.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Políticas", selecciona una opción. ![Habilita, inhabilita o limita las acciones para esta cuenta empresarial](/assets/images/help/settings/actions-enable-enterprise-account.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/enterprise-beta.md b/translations/es-XL/data/reusables/actions/enterprise-beta.md deleted file mode 100644 index 876f328cd5..0000000000 --- a/translations/es-XL/data/reusables/actions/enterprise-beta.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion == "enterprise-server@2.22" %} -{% note %} - -**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. To review the external storage requirements and request access to the beta, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." - -{% endnote %} -{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/enterprise-github-hosted-runners.md b/translations/es-XL/data/reusables/actions/enterprise-github-hosted-runners.md deleted file mode 100644 index 1ef3c4ce19..0000000000 --- a/translations/es-XL/data/reusables/actions/enterprise-github-hosted-runners.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %} -{% note %} - -**Note:** {% data variables.product.prodname_dotcom %}-hosted runners are not currently supported on {% data variables.product.prodname_ghe_server %}. You can see more information about planned future support on the [{% data variables.product.prodname_roadmap %}](https://github.com/github/roadmap/issues/72). - -{% endnote %} -{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/actions/enterprise-marketplace-actions.md b/translations/es-XL/data/reusables/actions/enterprise-marketplace-actions.md deleted file mode 100644 index e4454f97ee..0000000000 --- a/translations/es-XL/data/reusables/actions/enterprise-marketplace-actions.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} - -{% note %} - -**Note:** {% data variables.product.prodname_actions %} on {% data variables.product.product_location %} may have limited access to actions on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}. 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)." - -{% endnote %} - -{% endif %} diff --git a/translations/es-XL/data/reusables/actions/enterprise-no-internet-actions.md b/translations/es-XL/data/reusables/actions/enterprise-no-internet-actions.md deleted file mode 100644 index 9f2287cfee..0000000000 --- a/translations/es-XL/data/reusables/actions/enterprise-no-internet-actions.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} is designed to work in environments without internet access. By default, workflows cannot use actions from {% data variables.product.prodname_dotcom_the_website %} and [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). diff --git a/translations/es-XL/data/reusables/actions/enterprise-setup-prereq.md b/translations/es-XL/data/reusables/actions/enterprise-setup-prereq.md deleted file mode 100644 index 3ead3e20f9..0000000000 --- a/translations/es-XL/data/reusables/actions/enterprise-setup-prereq.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %} - -#### Using self-hosted runners on {% data variables.product.prodname_ghe_server %} - -When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.prodname_ghe_server %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." - -{% endif %} diff --git a/translations/es-XL/data/reusables/apps/accept_new_permissions_steps.md b/translations/es-XL/data/reusables/apps/accept_new_permissions_steps.md deleted file mode 100644 index 1d4f1070d9..0000000000 --- a/translations/es-XL/data/reusables/apps/accept_new_permissions_steps.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Da clic en **Guardar cambios** al final de la página. -1. Si instalaste la app en tu cuenta, revisa tu correo electrónico y sigue el enlace para aceptar los permisos nuevos. Cada que cambias los permisos o los webhooks de tu app, los usuarios que la hayan instalado (incluyéndote a ti mismo) necesitarán aceptar los permisos nuevos antes de que los cambios surtan efecto. También puedes aceptar los permisos nuevos si navegas a tu [página de instalaciones](https://github.com/settings/installations) y das clic en "Configurar" junto a tu app. Verás un letrero en la parte superior de la página que te informará que la app está solicitando permisos diferentes. Da clic en "Detalles" y después en "Aceptar permisos nuevos". diff --git a/translations/es-XL/data/reusables/apps/api-rate-limits-non-ghec.md b/translations/es-XL/data/reusables/apps/api-rate-limits-non-ghec.md deleted file mode 100644 index 9f38778e66..0000000000 --- a/translations/es-XL/data/reusables/apps/api-rate-limits-non-ghec.md +++ /dev/null @@ -1 +0,0 @@ -Las {% data variables.product.prodname_github_app %} hacen solicitudes de servidor a servidor para utilizar el límite de tasa mínimo de la instalación, que 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-XL/data/reusables/apps/app-ruby-guides.md b/translations/es-XL/data/reusables/apps/app-ruby-guides.md deleted file mode 100644 index 168f7b9c60..0000000000 --- a/translations/es-XL/data/reusables/apps/app-ruby-guides.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Esta guía muestra el proceso de desarrollo de las apps utilizando el lenguaje de programación Ruby. Sin embargo, hay muchos [sabores de Octokit](/v3/libraries/). Si prefieres JavaScript, puedes utilizar al [Probot](https://probot.github.io/) y a [Node.js](https://octokit.github.io/rest.js/) para desarrollar las GitHub Apps. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/apps/app_manager_role.md b/translations/es-XL/data/reusables/apps/app_manager_role.md deleted file mode 100644 index 28b4f1eabc..0000000000 --- a/translations/es-XL/data/reusables/apps/app_manager_role.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, solo los propietarios de la organización pueden administrar los ajustes de las GitHub Apps en una organización. Para agregar usuarios adicionales para que administren las GitHub Apps en una organización, un propietario puede otorgarles permisos de administrador sobe ellas. Consula la sección "[Administradores de GitHub Apps](/articles/permission-levels-for-an-organization/#github-app-managers)" para aprender cómo agregar y eliminar administradores de GitHub Apps en tu organización. diff --git a/translations/es-XL/data/reusables/apps/beta_feature_activation.md b/translations/es-XL/data/reusables/apps/beta_feature_activation.md deleted file mode 100644 index 6a3233295d..0000000000 --- a/translations/es-XL/data/reusables/apps/beta_feature_activation.md +++ /dev/null @@ -1,2 +0,0 @@ -4. En la barra lateral izquierda, da clic en **Características del Beta**. ![Sección de las GitHub Apps o Apps de OAuth](/assets/images/github-apps/beta-features-option.png) -5. Junto a la característica beta que quieres habilitar para tu app, da clic en **Unirse**. ![Botón de unirse para habilitar la característica beta](/assets/images/github-apps/enable-beta-features.png) diff --git a/translations/es-XL/data/reusables/apps/checks-availability.md b/translations/es-XL/data/reusables/apps/checks-availability.md deleted file mode 100644 index a814224f54..0000000000 --- a/translations/es-XL/data/reusables/apps/checks-availability.md +++ /dev/null @@ -1 +0,0 @@ -El permiso de escritura para la API de Verificaciones solo está disponible para las Github Apps. Las Apps de OAuth y los usuarios autenticados pueden ver las ejecuciones de verificación y las suites de verificación, pero no pueden crearlas. Si no estás creando una GitHub App, puede que te interese la [API de estados](/v3/repos/statuses/). diff --git a/translations/es-XL/data/reusables/apps/deletes_ssh_keys.md b/translations/es-XL/data/reusables/apps/deletes_ssh_keys.md deleted file mode 100644 index 8a9330afa3..0000000000 --- a/translations/es-XL/data/reusables/apps/deletes_ssh_keys.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Advertencia**: Si revocas todos los permisos de una {% data variables.product.prodname_oauth_app %} borrarás cualquier llave SSH que haya generado la aplicación en nombre del usuario, , incluyendo las [llaves de despliegue](/v3/guides/managing-deploy-keys/#deploy-keys). - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/es-XL/data/reusables/apps/deprecating_auth_with_query_parameters.md deleted file mode 100644 index 5e48c8af04..0000000000 --- a/translations/es-XL/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% warning %} - -**Aviso de Obsoletización:** {% data variables.product.prodname_dotcom %} descontinuará la autenticación a la API utilizando parámetros de consulta. Se debe autenticar en la API con [autenticación básica de HTTP](/v3/auth/#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} El utilizar parámetros de consulta para autenticarse en la API ya no funcionará desde el 5 de mayo de 2021. {% endif %} Para obtener más información, incluyendo los periodos de interrupción programada, consulta la [publicación del blog](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). - -{% if currentVersion != "free-pro-team@latest" %} La autenticación a la API a través de parámetros de búsqueda, si bien está disponible, ya no es compatible por motivos de seguridad. En vez de ésto, recomendamos a los integradores que migren su token de acceso, `client_id`, o `client_secret` al encabezado. {% data variables.product.prodname_dotcom %} notificará sobre la eliminación de la autenticación por parámetros de consulta con tiempo suficiente. {% endif %} - -{% endwarning %} -{% endif %} diff --git a/translations/es-XL/data/reusables/apps/deprecating_github_services_ghe.md b/translations/es-XL/data/reusables/apps/deprecating_github_services_ghe.md deleted file mode 100644 index d2a2249d3c..0000000000 --- a/translations/es-XL/data/reusables/apps/deprecating_github_services_ghe.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %} -{% note %} - -**Nota:** El lanzamiento 2.17 de GitHub Enterprise y las versiones superiores ya no permiten que los administradores instalen GitHub Services nuevos, y los servicios existentes dejarán de funcionar en el lanzamiento 2.20 o superior de Github Enterprise. Puedes utilzar la [Guía para reemplazar GitHub Services](/v3/guides/replacing-github-services) para ayudarte a actualizar tus servicios a webhooks. - -{% endnote %} -{% endif %} diff --git a/translations/es-XL/data/reusables/apps/deprecating_password_auth.md b/translations/es-XL/data/reusables/apps/deprecating_password_auth.md deleted file mode 100644 index a077272608..0000000000 --- a/translations/es-XL/data/reusables/apps/deprecating_password_auth.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% warning %} - -**Aviso de Obsoletización:** {% data variables.product.prodname_dotcom %} descontinuará la autenticación mediante contraseña para la API. Ahora debes autenticarte a la API de {% data variables.product.prodname_dotcom %} con un token de la API tal como un token de acceso de OAuth, una GitHub App, un token de acceso a la instalación, o un token de acceso personal, dependiendo de lo que necesites hacer con dicho token.{% if currentVersion == "free-pro-team@latest" %} La autenticación por contraseña en la API se eliminará el 13 de Noviembre de 2020. {% endif %} Para obtener más información,{% if currentVersion == "free-pro-team@latest" %}incluyendo los periodos de inactividad programados,{% endif %} consulta la [publicación del blog](https://developer.github.com/changes/2020-02-14-deprecating-password-auth/). - -{% if currentVersion != "free-pro-team@latest" %} La autenticación por contraseña para la API sigue disponible actualmente y no se ha obsoletizado en {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_dotcom %} anunciará la obsoletización y proporcionará notificaciones oportunas antes de que elimine la compatibilidad para esta característica.{% endif %} - -{% endwarning %} -{% endif %} diff --git a/translations/es-XL/data/reusables/apps/deprecating_token_oauth_authorizations.md b/translations/es-XL/data/reusables/apps/deprecating_token_oauth_authorizations.md deleted file mode 100644 index 6e52518ba2..0000000000 --- a/translations/es-XL/data/reusables/apps/deprecating_token_oauth_authorizations.md +++ /dev/null @@ -1,16 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.20" %} -{% warning %} - -**Aviso de obsoletización:** El atributo `token` se obsoletizó en algunas respuestas de la API para Autorizaciones de OAuth: -* Listar tus autorizaciones -* Obtener una sola autorización -* Obtener o crear una autorización para una app específica - aún se devuelve el `token` para "crear" -* Obtener o crear una autorización para una app y huella digital específicos - aún se devuelve `token` para "crear" -* Actualizar una autrización existente - -Para reducir el impacto de eliminar el valor de `token`, la API de Autorizaciones de OAuth ahora incluye un atributo de solicitud nuevo (`fingerprint`), tres atributos de respuesta nuevos (`token_last_eight`, `hashed_token`, y `fingerprint`), y la terminal de [Obtener o crear una autorización para una app y huella digital específica](/rest/reference/oauth-authorizations#get-or-create-an-authorization-for-a-specific-app-and-fingerprint). - -Esta fucionalidad se convirtió en predeterminada para todas las solicitudes desde el 20 de abril de 2015. Por favor, consulta la [publicación del blog](https://developer.github.com/changes/2015-04-20-authorizations-api-response-changes-are-now-in-effect/) para obtener toda la información al respecto. - -{% endwarning %} -{% endif %} diff --git a/translations/es-XL/data/reusables/apps/expiring_user_authorization_tokens.md b/translations/es-XL/data/reusables/apps/expiring_user_authorization_tokens.md deleted file mode 100644 index fd54de3817..0000000000 --- a/translations/es-XL/data/reusables/apps/expiring_user_authorization_tokens.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -Para mantener más seguros los tokens de acceso de usuario a servidor, puedes utilizar tokens de acceso que caducarán después de 8 horas, y un token de actualización que se puede intercambiar por un token de acceso nuevo. Para obtener más información, consulta la sección "[Actualizar los tokens de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)". -{% endif %} diff --git a/translations/es-XL/data/reusables/apps/general-apps-restrictions.md b/translations/es-XL/data/reusables/apps/general-apps-restrictions.md deleted file mode 100644 index 36ece1240e..0000000000 --- a/translations/es-XL/data/reusables/apps/general-apps-restrictions.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}Si estás utilizando tu app con GitHub Actions y quieres modificar los archivos de flujo de trabajo, debes autenticarte por parte del usuario con un token de OAuth que incluya el alcance `workflow`. El usuario debe tener permisos de administrador o de escritura en el repositorio que contiene el archivo de flujo de trabajo. Para obtener más información, consulta la sección "[Entender los alcances para las apps de OAuth](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)".{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/apps/marketplace_revenue_share.md b/translations/es-XL/data/reusables/apps/marketplace_revenue_share.md deleted file mode 100644 index 9a45a7d307..0000000000 --- a/translations/es-XL/data/reusables/apps/marketplace_revenue_share.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Como parte del [Acuerdo de Desarrollador de Marketplace](/articles/github-marketplace-developer-agreement/), {% data variables.product.prodname_dotcom %} recibe un 25% de las ganancias de los listados de {% data variables.product.prodname_marketplace %}. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/apps/maximum-github-apps-allowed.md b/translations/es-XL/data/reusables/apps/maximum-github-apps-allowed.md deleted file mode 100644 index 393582506a..0000000000 --- a/translations/es-XL/data/reusables/apps/maximum-github-apps-allowed.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}Un usuario u organización puede ser propietario de hasta 100 GitHub Apps.{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/apps/maximum-oauth-apps-allowed.md b/translations/es-XL/data/reusables/apps/maximum-oauth-apps-allowed.md deleted file mode 100644 index 6bd1d10f6b..0000000000 --- a/translations/es-XL/data/reusables/apps/maximum-oauth-apps-allowed.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}Un usuario u organización puede ser propietario de hasta 100 Apps de OAuth.{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/apps/metadata-permissions.md b/translations/es-XL/data/reusables/apps/metadata-permissions.md deleted file mode 100644 index 454d57a032..0000000000 --- a/translations/es-XL/data/reusables/apps/metadata-permissions.md +++ /dev/null @@ -1 +0,0 @@ -Si configuras el permiso para metadatos como `No access` y seleccionas un permiso que requiere acceso al repositorio, GitHub anulará tu selección y configurará el permiso de metadatos como `Read-only` nuevamente. Para configurar el permiso de metadatos como `No access`, primero debes configurar todos los permisos que requieren acceso al repositorio como `No access`. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/apps/oauth-apps-restrictions.md b/translations/es-XL/data/reusables/apps/oauth-apps-restrictions.md deleted file mode 100644 index f2b9cde1d9..0000000000 --- a/translations/es-XL/data/reusables/apps/oauth-apps-restrictions.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}Si estás utilizando tu App de OAuth con GitHub Actions y quieres modificar tus archivos de flujo de trabajo, tu token de OAuth debe tener el alcance `workflow` y el usuario debe tener permisos de escritura o de lectura para el repositorio que contiene dichos archivos de flujo de trabajo. Para obtener más información, consulta la sección "[Entender los alcances para las apps de OAuth](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)".{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/apps/sinatra_restart_instructions.md b/translations/es-XL/data/reusables/apps/sinatra_restart_instructions.md deleted file mode 100644 index fc95fdf350..0000000000 --- a/translations/es-XL/data/reusables/apps/sinatra_restart_instructions.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Necesitarás reiniciar el servidor de Sinatra antes de que puedas probar los cambios. Introduce `Ctrl-C` para parar el servidor y después ejecuta `ruby template_server.rb` nuevamente. Si no quieres hacer esto cada que cambias el código de tu app, puedes buscar en [reloading](http://sinatrarb.com/faq.html#reloading). - -{% endnote %} diff --git a/translations/es-XL/data/reusables/apps/state_description.md b/translations/es-XL/data/reusables/apps/state_description.md deleted file mode 100644 index b077a301b3..0000000000 --- a/translations/es-XL/data/reusables/apps/state_description.md +++ /dev/null @@ -1 +0,0 @@ -Una secuencia aleatoria indescifrable. Se utiliza para protegerte contra los ataques de falsificación de solicitudes entre sitios. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md b/translations/es-XL/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md deleted file mode 100644 index c9b8665808..0000000000 --- a/translations/es-XL/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** la API de Verificaciones únicamente busca las cargas en el repositorio donde se creó el conjunto o ejecución de verificaciones. No se detectan aquellas cargas en ramas de repositorios bifurcados y estas devuelven un arreglo vacío de `pull_requests` y un valor `null` para la `head_branch`. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/audit_log/audit-log-search.md b/translations/es-XL/data/reusables/audit_log/audit-log-search.md deleted file mode 100644 index 85efebe30e..0000000000 --- a/translations/es-XL/data/reusables/audit_log/audit-log-search.md +++ /dev/null @@ -1,43 +0,0 @@ -El registro lista la siguiente información sobre cada acción: - -* En qué repositorio se realizó una acción -* El usuario que realizó la 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 - -Nota que no puedes buscar entradas utilizando texto. Sin embargo, puedes construir consultas de búsqueda utilizando una variedad de filtros. Muchos operadores que se utilizan cuando se busca el registro por queries, tales como `-`, `>`, o `<`, empatan con el mismo formato que si se busca con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". - -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -#### Búsqueda basada en la operación - -Utiliza el calificador `operation` para limitar las acciones en tipos específicos de operaciones. Por ejemplo: - - * `operation:access` encuentra todos los eventos en donde se accedió a un recurso. - * `operation:authentication` encuentra todos los eventos en donde se realizó un evento de autenticación. - * `operation:create` encuentra todos los eventos en donde se creó un recurso. - * `operation:modify` encuentra todos los eventos en donde se modificó un recurso existente. - * `operation:remove` encuentra todos los eventos en donde se eliminó un recurso existente. - * `operation:restore` encuentra todos los eventos en donde se restauró un recurso existente. - * `operation:transfer` encuentra todos los eventos en donde se transfirió un recurso existente. -{% endif %} - -#### Búsqueda basada en el repositorio - -Utiliza el calificador `repo` para limitar las acciones a un repositorio específico. Por ejemplo: - - * `repo:my-org/our-repo` encuentra todos los eventos que ocurrieron para el repositorio `our-repo` en la organización `my-org`. - * `repo:my-org/our-repo repo:my-org/another-repo` encuentra todos los eventos que ocurrieron tanto para los repositorios `our-repo` como `another-repo` en la organización `my-org`. - * `-repo:my-org/not-this-repo` excluye todos los eventos que ocurrieron para el repositorio `not-this-repo` en la organización `my-org`. - -Nota que debes incluir el nombre de cuenta dentro del calificador `repo`; no funcionará si buscas únicamente `repo:our-repo`. - -#### Búsqueda basada en el usuario - -El calificador `actor` puede incluir eventos que se basen en quién realizó la acción. Por ejemplo: - - * `actor:octocat` encuentra todos los eventos realizados por `octocat`. - * `actor:octocat actor:hubot` encuentra todos los eventos realizados tanto por `octocat` como por `hubot`. - * `-actor:hubot` excluye todos los eventos realizados por `hubot`. - -Ten en cuenta que solo puedes utilizar un nombre de usuario {% data variables.product.product_name %}, no el nombre real de una persona. diff --git a/translations/es-XL/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/es-XL/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md deleted file mode 100644 index 7e2f651489..0000000000 --- a/translations/es-XL/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de Parámetros, haz clic en **Audit Log (Registro de auditoría)**. ![Parámetros de registro de auditoría de org en barra lateral](/assets/images/help/organizations/org-settings-audit-log.png) diff --git a/translations/es-XL/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/es-XL/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md deleted file mode 100644 index 0768fe1a42..0000000000 --- a/translations/es-XL/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md +++ /dev/null @@ -1 +0,0 @@ -3. En la barra lateral izquierda, haz clic en **Audit Log (Registro de auditoría)**. ![Pestaña de registro de auditoría](/assets/images/enterprise/site-admin-settings/audit-log-tab.png) diff --git a/translations/es-XL/data/reusables/audit_log/export-log.md b/translations/es-XL/data/reusables/audit_log/export-log.md deleted file mode 100644 index df8dac28ce..0000000000 --- a/translations/es-XL/data/reusables/audit_log/export-log.md +++ /dev/null @@ -1,7 +0,0 @@ -Puedes exportar el registro como datos JSON o como un archivo con valores separados por comas (V). - -![Botón de exportar](/assets/images/help/organizations/org-audit-log-export.png) - -Para filtrar los resultados en tu exportación, busca utilizando uno o más de los calificadores antes de recurrir al menú desplegable **Export**. - -{% data reusables.audit_log.keys-and-example-values %} diff --git a/translations/es-XL/data/reusables/audit_log/exported-log-keys-and-values.md b/translations/es-XL/data/reusables/audit_log/exported-log-keys-and-values.md deleted file mode 100644 index 850d86734a..0000000000 --- a/translations/es-XL/data/reusables/audit_log/exported-log-keys-and-values.md +++ /dev/null @@ -1,16 +0,0 @@ -Después de que exportes el registro como JSON o CSV, verás las siguientes claves y valores en el archivo resultante. - -| Clave | Valor de ejemplo | -| ------------------------ | ------------------------------------------------------------------------------------- | -| `Acción` | team.create | -| `actor (actor)` | octocat | -| `usuario` | codertocat | -| `org` | octo-org | -| `repo` | octo-org/documentation | -| `created_at (creado en)` | 1429548104000 (Los registros horarios muestran la hora desde Epoch con milisegundos). | -| `data.hook_id` | 245 | -| `data.events` | ["issues", "issue_comment", "pull_request", "pull_request_review_comment"] | -| `data.events_were` | ["push", "pull_request", "issues"] | -| `data.target_login` | octocat | -| `data.old_user` | hubot | -| `data.team` | octo-org/engineering | diff --git a/translations/es-XL/data/reusables/audit_log/keys-and-example-values.md b/translations/es-XL/data/reusables/audit_log/keys-and-example-values.md deleted file mode 100644 index 05f71977aa..0000000000 --- a/translations/es-XL/data/reusables/audit_log/keys-and-example-values.md +++ /dev/null @@ -1,8 +0,0 @@ -| Qualifier | Valor de ejemplo | -| --------------- | ---------------------- | -| `Acción` | team.create | -| `actor (actor)` | octocat | -| `usuario` | codertocat | -| `org` | octo-org | -| `repo` | octo-org/documentation | -| `created` | 2019-06-01 | diff --git a/translations/es-XL/data/reusables/audit_log/octicon_icon.md b/translations/es-XL/data/reusables/audit_log/octicon_icon.md deleted file mode 100644 index 6193126263..0000000000 --- a/translations/es-XL/data/reusables/audit_log/octicon_icon.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior izquierda de cualquier página, haz clic en . ![Icono de Octocat](/assets/images/enterprise/navigation/octocat-icon.png) diff --git a/translations/es-XL/data/reusables/branches/default-branch-automatically-base-branch.md b/translations/es-XL/data/reusables/branches/default-branch-automatically-base-branch.md deleted file mode 100644 index e0dab3a781..0000000000 --- a/translations/es-XL/data/reusables/branches/default-branch-automatically-base-branch.md +++ /dev/null @@ -1 +0,0 @@ -La rama predeterminada es la rama base en tu repositorio, contra la cual se hacen automáticamente todas las solicitudes de extracción y confirmaciones de código, a menos de que especifiques una rama diferente. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/branches/new-repo-default-branch.md b/translations/es-XL/data/reusables/branches/new-repo-default-branch.md deleted file mode 100644 index f37c28155f..0000000000 --- a/translations/es-XL/data/reusables/branches/new-repo-default-branch.md +++ /dev/null @@ -1 +0,0 @@ -Cuando creas un repositorio con contenido en {% data variables.product.prodname_dotcom %}, éste se inicializa con una sola rama, llamada rama predeterminada. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/branches/set-default-branch.md b/translations/es-XL/data/reusables/branches/set-default-branch.md deleted file mode 100644 index 33293c0920..0000000000 --- a/translations/es-XL/data/reusables/branches/set-default-branch.md +++ /dev/null @@ -1 +0,0 @@ -Si tienes permisos administrativos en un repositorio, puedes cambiar la rama predeterminada para que sea otra rama existente. Para obtener más información, consulta la sección "[Configurar la rama predeterminada](/github/administering-a-repository/setting-the-default-branch)". diff --git a/translations/es-XL/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/translations/es-XL/data/reusables/cli/filter-issues-and-pull-requests-tip.md deleted file mode 100644 index 949b7938db..0000000000 --- a/translations/es-XL/data/reusables/cli/filter-issues-and-pull-requests-tip.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -{% tip %} - -**Tip**: You can also filter issues or pull requests using the {% data variables.product.prodname_cli %}. For more information, see "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" or "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)" in the {% data variables.product.prodname_cli %} documentation. - -{% endtip %} -{% endif %} diff --git a/translations/es-XL/data/reusables/code-scanning/about-code-scanning.md b/translations/es-XL/data/reusables/code-scanning/about-code-scanning.md deleted file mode 100644 index 70df68d69b..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/about-code-scanning.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_code_scanning_capc %} is a feature that you use to analyze the code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Any problems identified by the analysis are shown in {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %}. diff --git a/translations/es-XL/data/reusables/code-scanning/autobuild-add-build-steps.md b/translations/es-XL/data/reusables/code-scanning/autobuild-add-build-steps.md deleted file mode 100644 index 46e93c8be7..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/autobuild-add-build-steps.md +++ /dev/null @@ -1 +0,0 @@ -Si el código de C/C++, C# o Java de tu repositorio tiene un proceso de compilación no estándar o si está escrito en más de un lenguaje compilado, el `autobuild` podría fallar. Necesitarás eliminar el paso de `autobuild` del flujo de trabajo y agregar los pasos de compilación manualmente. diff --git a/translations/es-XL/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/es-XL/data/reusables/code-scanning/autobuild-compiled-languages.md deleted file mode 100644 index a006815c79..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/autobuild-compiled-languages.md +++ /dev/null @@ -1,5 +0,0 @@ -For compiled languages like C/C++, C#, and Java, the `autobuild` step in the default workflow attempts to build code before the action performs {% data variables.product.prodname_codeql %} analysis. En contraste con los otros lenguajes compilados, {% data variables.product.prodname_codeql %} analiza Go sin compilar el código. - -El proceso de `autobuild` solo intenta siempre compilar _un_ solo lenguaje compilado para un repositorio. El lenguaje que se selecciona automáticamente para el análisis es aquél con más archivos. - - diff --git a/translations/es-XL/data/reusables/code-scanning/beta.md b/translations/es-XL/data/reusables/code-scanning/beta.md deleted file mode 100644 index 38acfb5212..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** {% data variables.product.prodname_code_scanning_capc %} se encuentra acutalmente en beta y está sujeto a cambios. {% if currentVersion == "free-pro-team@latest" %}To request access to the beta, [join the waitlist](https://github.com/features/security/advanced-security/signup).{% else %}If your organization has an {% data variables.product.prodname_advanced_security %} license, you can [join the beta program](https://resources.github.com/beta-signup/).{% endif %} - -{% endnote %} diff --git a/translations/es-XL/data/reusables/code-scanning/click-alert-in-list.md b/translations/es-XL/data/reusables/code-scanning/click-alert-in-list.md deleted file mode 100644 index da6d4d3495..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/click-alert-in-list.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Escaneo de Código", da clic en la alerta que quieras ver. ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) diff --git a/translations/es-XL/data/reusables/code-scanning/codeql-query-suites.md b/translations/es-XL/data/reusables/code-scanning/codeql-query-suites.md deleted file mode 100644 index 871cabab73..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/codeql-query-suites.md +++ /dev/null @@ -1,8 +0,0 @@ -The following query suites are built into {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} and are available for use. - - | Conjunto de consultas | Descripción | - |:---------------------- |:------------------------------------------------------------------------------------ | - | `security-extended` | Las consultas de severidad y precisión más baja que aquellas predeterminadas | - | `security-and-quality` | Las consultas de `security-extended`, mas aquellas de mantenibilidad y confiabilidad | - -When you specify a query suite, the {% data variables.product.prodname_codeql %} analysis engine will run the queries contained within the suite for you, in addition to the default set of queries. diff --git a/translations/es-XL/data/reusables/code-scanning/codeql-runner-license.md b/translations/es-XL/data/reusables/code-scanning/codeql-runner-license.md deleted file mode 100644 index 17283fb710..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/codeql-runner-license.md +++ /dev/null @@ -1,10 +0,0 @@ -{% note %} - -{% if currentVersion == "free-pro-team@latest" %} -**Note:** The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://help.semmle.com/codeql/codeql-cli.html)." - -{% else %} -**Note:** The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. -{% endif %} - -{% endnote %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/code-scanning/edit-workflow.md b/translations/es-XL/data/reusables/code-scanning/edit-workflow.md deleted file mode 100644 index f839d990bf..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/edit-workflow.md +++ /dev/null @@ -1 +0,0 @@ -Habitualmente, no necesitas editar el flujo de trabajo predeterminado para {% data variables.product.prodname_code_scanning %}. However, if required, you can edit the workflow to customize some of the settings. For example, you can edit {% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_codeql_workflow %} to specify the frequency of scans, the languages or directories to scan, and what {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} looks for in your code. You might also need to edit the workflow if you use a specific set of commands to compile your code or if there is more than one compiled language in your repository. diff --git a/translations/es-XL/data/reusables/code-scanning/enabling-options.md b/translations/es-XL/data/reusables/code-scanning/enabling-options.md deleted file mode 100644 index 6b1c8b1a10..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/enabling-options.md +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - - - - - - - - - - - -
    - Type of analysis - - Options for generating alerts -
    - {% data variables.product.prodname_codeql %} - - Using {% data variables.product.prodname_actions %} (see "Enabling {% data variables.product.prodname_code_scanning %} using actions") or using the {% data variables.product.prodname_codeql_runner %} in a third-party continuous integration (CI) system (see "Running code scanning in your CI system"). -
    - Third‑party - - Using {% data variables.product.prodname_actions %} (see "Enabling {% data variables.product.prodname_code_scanning %} using actions") or generated externally and uploaded to {% data variables.product.product_name %} (see "Uploading a SARIF file to {% data variables.product.prodname_dotcom %}"). -
    \ No newline at end of file diff --git a/translations/es-XL/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md b/translations/es-XL/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md deleted file mode 100644 index 5612481d72..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} - -{% note %} - -**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location_enterprise %} before you can use this feature. If you want to use {% data variables.product.prodname_actions %} to scan your code, the site administrator must also enable {% data variables.product.prodname_actions %} and set up the infrastructure required. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." - -{% endnote %} - -{% endif %} diff --git a/translations/es-XL/data/reusables/code-scanning/enterprise-enable-code-scanning.md b/translations/es-XL/data/reusables/code-scanning/enterprise-enable-code-scanning.md deleted file mode 100644 index c230142938..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/enterprise-enable-code-scanning.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion ver_gt "enterprise-server@2.21" %} - -{% note %} - -**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location_enterprise %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." - -{% endnote %} - -{% endif %} diff --git a/translations/es-XL/data/reusables/code-scanning/example-configuration-files.md b/translations/es-XL/data/reusables/code-scanning/example-configuration-files.md deleted file mode 100644 index c3143f1e1a..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/example-configuration-files.md +++ /dev/null @@ -1,32 +0,0 @@ -Este archivo de configuración agrega el conjunto de consultas `security-and-quality` a la lista de consultas que se ejecutan con {% data variables.product.prodname_codeql %} cuando se escanea tu código. Para obtener más información acerca de los conjuntos de consultas que están disponibles para utilizarse, consulta la sección "[Ejecutar consultas adicionales](#running-additional-queries)". - -``` yaml -name: "My {% data variables.product.prodname_codeql %} config" - -queries: - - uses: security-and-quality -``` - -The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), and to exclude the _node_modules_ directory (also relative to the root), as well as any file whose name ends in _.test.js_. - -``` yaml -name: "My {% data variables.product.prodname_codeql %} config" - -disable-default-queries: true - -queries: - - name: Use an in-repository {% data variables.product.prodname_ql %} pack (run queries in the my-queries directory) - uses: ./my-queries - - name: Use an external JavaScript {% data variables.product.prodname_ql %} pack (run queries from an external repo) - uses: octo-org/javascript-qlpack@main - - name: Use an external query (run a single query from an external {% data variables.product.prodname_ql %} pack) - uses: octo-org/python-qlpack/show_ifs.ql@main - - name: Use a query suite file (run queries from a query suite in this repo) - uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls - -paths-ignore: - - node_modules - - '**/*.test.js' -paths: - - src -``` diff --git a/translations/es-XL/data/reusables/code-scanning/get-started-uploading-third-party-data.md b/translations/es-XL/data/reusables/code-scanning/get-started-uploading-third-party-data.md deleted file mode 100644 index 3e2e5bdfb3..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/get-started-uploading-third-party-data.md +++ /dev/null @@ -1 +0,0 @@ -Para comenzar, consulta la sección "[Subir un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github)". diff --git a/translations/es-XL/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md b/translations/es-XL/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md deleted file mode 100644 index efd0f23f4b..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_code_scanning_capc %} es interoperable con herramientas de escaneo de código de terceros que producen datos de Formato de Intercambio de Resultado de Análisis (SARIF). SARIF es un estándar de código abierto. Para obtener más información, consulta la sección "[Resultados de SARIF para {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/code-scanning/run-additional-queries.md b/translations/es-XL/data/reusables/code-scanning/run-additional-queries.md deleted file mode 100644 index 8c4fac0118..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/run-additional-queries.md +++ /dev/null @@ -1,9 +0,0 @@ -When you use {% data variables.product.prodname_codeql %} to scan code, the {% data variables.product.prodname_codeql %} analysis engine generates a database from the code and runs queries on it. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)". - -{% data variables.product.prodname_codeql %} analysis uses a default set of queries, but you can specify more queries to run, in addition to the default queries. Las consultas que quieras ejecutar deberán pertenecer a un paquete de {% data variables.product.prodname_ql %} y pueden estar en tu propio repositorio o en cualquier repositorio público. Para obtener más información, consulta la sección "[Acerca de los paquetes de {% data variables.product.prodname_ql %}](https://help.semmle.com/codeql/codeql-cli/reference/qlpack-overview.html)". - -Las consultas solo deberán depender de las bibliotecas estándar (es decir, aquellas referenciadas por una declaración `import LANGUAGE` en tu consulta), o de aquellas en el mismo paquete de {% data variables.product.prodname_ql %} que la consulta. Las bibliotecas estándar se ubican en el repositorio [github/codeql](https://github.com/github/codeql). For more information, see "[About CodeQL queries](https://help.semmle.com/QL/learn-ql/writing-queries/introduction-to-queries.html)." - -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. For more information about query suite definitions, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://help.semmle.com/codeql/codeql-cli/procedures/query-suites.html)." - -{% if currentVersion == "free-pro-team@latest" %}We don't recommend referencing query suites directly from the `github/codeql` repository, like `github/codeql/cpp/ql/src@main`. Such queries may not be compiled with the same version of {% data variables.product.prodname_codeql %} as used for your other queries, which could lead to errors during analysis.{% endif %} diff --git a/translations/es-XL/data/reusables/code-scanning/specify-language-to-analyze.md b/translations/es-XL/data/reusables/code-scanning/specify-language-to-analyze.md deleted file mode 100644 index 377c8258f3..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/specify-language-to-analyze.md +++ /dev/null @@ -1 +0,0 @@ -Si tu repositorio contiene código en varios lenguajes, puedes especificar aquellos que quieras analizar. Hay varias razones que por las cuales querrías prevenir que un lenguaje se analice. Por ejemplo, el proyecto puede tener dependencias en un lenguaje distinto al del cuerpo principal de tu código, y tal vez prefieras no ver las alertas para esas dependencias. diff --git a/translations/es-XL/data/reusables/code-scanning/supported-languages.md b/translations/es-XL/data/reusables/code-scanning/supported-languages.md deleted file mode 100644 index 91222f40b4..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/supported-languages.md +++ /dev/null @@ -1,6 +0,0 @@ -- C/C++ -- C# -- Go -- Java -- JavaScript/TypeScript -- Python diff --git a/translations/es-XL/data/reusables/code-scanning/you-can-upload-third-party-analysis.md b/translations/es-XL/data/reusables/code-scanning/you-can-upload-third-party-analysis.md deleted file mode 100644 index 9fe20ef7da..0000000000 --- a/translations/es-XL/data/reusables/code-scanning/you-can-upload-third-party-analysis.md +++ /dev/null @@ -1 +0,0 @@ -Puedes cargar archivos SARIF de herramientas de análisis estático de terceros a {% data variables.product.prodname_dotcom %} y ver las alertas de {% data variables.product.prodname_code_scanning %} en tu repositorio. diff --git a/translations/es-XL/data/reusables/command_line/change-current-directory-clone.md b/translations/es-XL/data/reusables/command_line/change-current-directory-clone.md deleted file mode 100644 index 36d7e5d402..0000000000 --- a/translations/es-XL/data/reusables/command_line/change-current-directory-clone.md +++ /dev/null @@ -1 +0,0 @@ -4. Cambia el directorio de trabajo actual a la ubicación en donde quieres clonar el directorio. diff --git a/translations/es-XL/data/reusables/command_line/git-clone-url.md b/translations/es-XL/data/reusables/command_line/git-clone-url.md deleted file mode 100644 index f5d7913ab6..0000000000 --- a/translations/es-XL/data/reusables/command_line/git-clone-url.md +++ /dev/null @@ -1,4 +0,0 @@ -5. Escribe `git clone`, y luego pega la URL que copiaste antes. - ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY - ``` \ No newline at end of file diff --git a/translations/es-XL/data/reusables/command_line/local-clone-created.md b/translations/es-XL/data/reusables/command_line/local-clone-created.md deleted file mode 100644 index dcc95bb352..0000000000 --- a/translations/es-XL/data/reusables/command_line/local-clone-created.md +++ /dev/null @@ -1,9 +0,0 @@ -6. Presiona **Enter** para crear tu clon local. - ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY - > Cloning into `Spoon-Knife`... - > remote: Counting objects: 10, done. - > remote: Compressing objects: 100% (8/8), done. - > remove: Total 10 (delta 1), reused 10 (delta 1) - > Unpacking objects: 100% (10/10), done. - ``` diff --git a/translations/es-XL/data/reusables/command_line/manipulating_file_prereqs.md b/translations/es-XL/data/reusables/command_line/manipulating_file_prereqs.md deleted file mode 100644 index 52e7ca04d2..0000000000 --- a/translations/es-XL/data/reusables/command_line/manipulating_file_prereqs.md +++ /dev/null @@ -1,4 +0,0 @@ -Este procedimiento supone que ya has: - - - [creado un repositorio en {% data variables.product.product_name %}](/articles/creating-a-new-repository) o que tienes un repositorio existente que es propiedad de alguien más con quien desees colaborar - - [clonado el repositorio de forma local en tu computadora](/articles/cloning-a-repository) diff --git a/translations/es-XL/data/reusables/command_line/open_the_multi_os_terminal.md b/translations/es-XL/data/reusables/command_line/open_the_multi_os_terminal.md deleted file mode 100644 index d93f5c5af2..0000000000 --- a/translations/es-XL/data/reusables/command_line/open_the_multi_os_terminal.md +++ /dev/null @@ -1 +0,0 @@ -1. Abre la TerminalTerminalGit Bash. diff --git a/translations/es-XL/data/reusables/command_line/provide-an-access-token.md b/translations/es-XL/data/reusables/command_line/provide-an-access-token.md deleted file mode 100644 index 0147f8d00a..0000000000 --- a/translations/es-XL/data/reusables/command_line/provide-an-access-token.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} Si estás accediendo a una organización que utiliza el SSO de SAML, también deberás autorizar tu token de acceso personal para ingresar a la organización antes de que te autentiques. Para obtener más información, consulta las secciónes "[Acerca de la autenticación, con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" y "[Autorizar un token de acceso personal para su uso 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)".{% endif %} diff --git a/translations/es-XL/data/reusables/command_line/providing-token-as-password.md b/translations/es-XL/data/reusables/command_line/providing-token-as-password.md deleted file mode 100644 index bfbc541ce7..0000000000 --- a/translations/es-XL/data/reusables/command_line/providing-token-as-password.md +++ /dev/null @@ -1,9 +0,0 @@ -Una vez que tengas un token, puedes ingresarlo en lugar de tu contraseña cuando realices operaciones de Git a través de HTTPS. - -Por ejemplo, en la línea de comando ingresarás lo siguiente: - -```shell -$ git clone https://{% data variables.command_line.codeblock %}/username/repo.git -Username: your_username -Password: your_token -``` diff --git a/translations/es-XL/data/reusables/command_line/start_ssh_agent.md b/translations/es-XL/data/reusables/command_line/start_ssh_agent.md deleted file mode 100644 index 7ab5d4bfe8..0000000000 --- a/translations/es-XL/data/reusables/command_line/start_ssh_agent.md +++ /dev/null @@ -1,5 +0,0 @@ -Inicia el agente SSH en segundo plano. -```shell -$ eval "$(ssh-agent -s)" -> Agent pid 59566 -``` diff --git a/translations/es-XL/data/reusables/command_line/switching_directories_procedural.md b/translations/es-XL/data/reusables/command_line/switching_directories_procedural.md deleted file mode 100644 index d5075ccb36..0000000000 --- a/translations/es-XL/data/reusables/command_line/switching_directories_procedural.md +++ /dev/null @@ -1 +0,0 @@ -1. Cambia el directorio de trabajo actual por tu repositorio local. diff --git a/translations/es-XL/data/reusables/command_line/use_with_support_only.md b/translations/es-XL/data/reusables/command_line/use_with_support_only.md deleted file mode 100644 index a4eed392a6..0000000000 --- a/translations/es-XL/data/reusables/command_line/use_with_support_only.md +++ /dev/null @@ -1 +0,0 @@ -**No uses** este comando sin indicación del [{% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/). El uso incorrecto podría causar daño o pérdida de datos. diff --git a/translations/es-XL/data/reusables/commits/about-commits.md b/translations/es-XL/data/reusables/commits/about-commits.md deleted file mode 100644 index 09601c0d8e..0000000000 --- a/translations/es-XL/data/reusables/commits/about-commits.md +++ /dev/null @@ -1,7 +0,0 @@ -De forma similar al guardar un archivo que se editó, una confirmación registra los cambios en uno o más archivos en tu rama. Git asigna una ID única a cada comentario, a la cual se le llama SHA o hash, la cual identifica: - -- Los cambios específicos -- Cuando se realizaron los cambios -- Quién creó los cambios - -Cuando realizas una confirmación, debes incluir un mensaje de confirmación que describa brevemente los cambios. diff --git a/translations/es-XL/data/reusables/community/report-content.md b/translations/es-XL/data/reusables/community/report-content.md deleted file mode 100644 index 8f7965b71b..0000000000 --- a/translations/es-XL/data/reusables/community/report-content.md +++ /dev/null @@ -1,4 +0,0 @@ -1. Puedes ver opciones de **Reportar a los administradores del repositorio** o **Reportar abuso al soporte de {% data variables.product.prodname_dotcom %}**. Si no, pasa al siguiente paso. - - Para reportar el contenido al soporte técnico de {% data variables.product.prodname_dotcom %} , haz clic en **Informar de abuso a {% data variables.product.prodname_dotcom %} Soporte**. - - Para reportar el contenido a los mantenedores de repositorio, utiliza el menú desplegable **Escoge una razón** para seleccionar una razón y da clic en **Reportar a los administradores del repositorio**. Tu reporte se ha emitido. ![modal de "Reportar contenido"](/assets/images/help/repository/report-content-modal.png) -2. Complete el formulario de "Reporte de contenido", luego haga clic en **Send Request (Enviar solicitud)**. ![formato de "Reportar contenido"](/assets/images/help/repository/report-content-to-support-form.png) diff --git a/translations/es-XL/data/reusables/community/tools-for-moderating.md b/translations/es-XL/data/reusables/community/tools-for-moderating.md deleted file mode 100644 index 6e1256cf91..0000000000 --- a/translations/es-XL/data/reusables/community/tools-for-moderating.md +++ /dev/null @@ -1 +0,0 @@ -Cuando ocurre un comportamiento negativo en tu comunidad, {% data variables.product.prodname_dotcom %} ofrece herramientas para aplicar tu código de conducta y desescalar conflictos. Por ejemplo, puedes bloquear una conversación para terminar una discusión acalorada. Para obtener más información, consulta "[Moderando comentarios y conversaciones](/github/building-a-strong-community/moderating-comments-and-conversations)" diff --git a/translations/es-XL/data/reusables/dashboard/access-org-dashboard.md b/translations/es-XL/data/reusables/dashboard/access-org-dashboard.md deleted file mode 100644 index 533540f7f8..0000000000 --- a/translations/es-XL/data/reusables/dashboard/access-org-dashboard.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Para acceder a la página del tablero de control, en la esquina superior izquierda de cualquier página en {% data variables.product.product_name %}, haz clic en el {% octicon "mark-github" aria-label="The github octocat logo" %}. -2. En la esquina superior izquierda de la página, haz clic en tu nombre de usuario y usa el menú desplegable para hacer clic en la organización deseada. ![Menú desplegable del interruptor de contexto del tablero de control que muestra diferentes opciones de organización](/assets/images/help/dashboard/dashboard-context-switcher.png) diff --git a/translations/es-XL/data/reusables/dashboard/recent-activity-qualifying-events.md b/translations/es-XL/data/reusables/dashboard/recent-activity-qualifying-events.md deleted file mode 100644 index 5371c0b827..0000000000 --- a/translations/es-XL/data/reusables/dashboard/recent-activity-qualifying-events.md +++ /dev/null @@ -1,8 +0,0 @@ -Las propuestas y las solicitudes de extracción abiertas aparecen en la sección de actividad reciente cuando: -- Has abierto una propuesta o solicitud de extracción. -- Alguien ha comentado en una propuesta o solicitud de extracción que abriste. -- Tu propuesta o solicitud de extracción fue reabierta. -- Se solicitó tu revisión en una solicitud de extracción. -- Se te asignó a una propuesta o solicitud de extracción. -- Hiciste referencia a una propuesta o solicitud de extracción por medio de un comentario. -- Hiciste un comentario en una propuesta o solicitud de extracción. diff --git a/translations/es-XL/data/reusables/dependabot/beta-note-no-link.md b/translations/es-XL/data/reusables/dependabot/beta-note-no-link.md deleted file mode 100644 index afcc666f9d..0000000000 --- a/translations/es-XL/data/reusables/dependabot/beta-note-no-link.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Las {% data variables.product.prodname_dependabot_version_updates %} se encuentran actualmente en beta y están sujetas a cambios. Para utilizar la característica del beta, sigue las instrucciones en este artículo. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/dependabot/beta-note.md b/translations/es-XL/data/reusables/dependabot/beta-note.md deleted file mode 100644 index f4134b6b55..0000000000 --- a/translations/es-XL/data/reusables/dependabot/beta-note.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Las {% data variables.product.prodname_dependabot_version_updates %} se encuentran actualmente en beta y están sujetas a cambios. Para utilizar la característica del beta, revisa el archivo de configuración para indicar al {% data variables.product.prodname_dependabot %} cuáles dependencias debe mantener para ti. Para obtener más detalles, consulta la sección "[Habilitar e inhabilitar las actualizaciones de versión](/github/administering-a-repository/enabling-and-disabling-version-updates)." - -{% endnote %} diff --git a/translations/es-XL/data/reusables/dependabot/check-in-dependabot-yml.md b/translations/es-XL/data/reusables/dependabot/check-in-dependabot-yml.md deleted file mode 100644 index fb92188de6..0000000000 --- a/translations/es-XL/data/reusables/dependabot/check-in-dependabot-yml.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa el archivo de configuración *dependabot.yml* en el directorio `.github` del repositorio. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dependabot/click-dependabot-tab.md b/translations/es-XL/data/reusables/dependabot/click-dependabot-tab.md deleted file mode 100644 index a9f6216603..0000000000 --- a/translations/es-XL/data/reusables/dependabot/click-dependabot-tab.md +++ /dev/null @@ -1 +0,0 @@ -4. Debajo de "Gráfica de dependencias", da clic en **{% data variables.product.prodname_dependabot_short %}**. ![Gráfica de dependencias, pestaña de {% data variables.product.prodname_dependabot_short %}](/assets/images/help/dependabot/dependabot-tab-beta.png) diff --git a/translations/es-XL/data/reusables/dependabot/create-dependabot-yml.md b/translations/es-XL/data/reusables/dependabot/create-dependabot-yml.md deleted file mode 100644 index d333016bd5..0000000000 --- a/translations/es-XL/data/reusables/dependabot/create-dependabot-yml.md +++ /dev/null @@ -1 +0,0 @@ -1. Crea un archivo de configuración *dependabot.yml*. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dependabot/default-dependencies-allow-ignore.md b/translations/es-XL/data/reusables/dependabot/default-dependencies-allow-ignore.md deleted file mode 100644 index 69fe64e303..0000000000 --- a/translations/es-XL/data/reusables/dependabot/default-dependencies-allow-ignore.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, todas las dependencias que se definen explícitamente en un manifiesto o archivo fijado se mantienen actualizadas. Puedes utilizar `allow` e `ignore` para personalizar qué dependencias quieres mantener con las actualizaciones de versión. El {% data variables.product.prodname_dependabot %} revisa las dependencias permitidas y después filtra cualquier dependencia o versión ignorada. Así que se ignorará cualquier dependencia que empate tanto con `allow` como con `ignore`. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dependabot/default-labels.md b/translations/es-XL/data/reusables/dependabot/default-labels.md deleted file mode 100644 index e4bbf3e4ce..0000000000 --- a/translations/es-XL/data/reusables/dependabot/default-labels.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, el {% data variables.product.prodname_dependabot %} levanta todas las solicitudes de extracción con la etiqueta `dependencies`. Si se define más de un administrador de paquetes, {% data variables.product.prodname_dependabot_short %} incluye una etiqueta adicional en cada una de las solicitudes de extracción. Esto indica qué lenguaje o ecosistema actualizará la solicitud de extracción, por ejemplo: `java` para las actualizaciones de Gradle `submodules` para las actualizaciones de los submódulos de git. El {% data variables.product.prodname_dependabot %} crea estas etiquetas predeterminadas automáticamente, de acuerdo lo necesite tu repositorio. diff --git a/translations/es-XL/data/reusables/dependabot/dependabot-tos.md b/translations/es-XL/data/reusables/dependabot/dependabot-tos.md deleted file mode 100644 index fb59e188c8..0000000000 --- a/translations/es-XL/data/reusables/dependabot/dependabot-tos.md +++ /dev/null @@ -1 +0,0 @@ -En las [Condiciones de Servicio de {% data variables.product.prodname_dotcom %}](/github/site-policy/github-terms-of-service) se incluyen al {% data variables.product.prodname_dependabot %} y a todas sus características relacionadas. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dependabot/initial-updates.md b/translations/es-XL/data/reusables/dependabot/initial-updates.md deleted file mode 100644 index 64472fcb2e..0000000000 --- a/translations/es-XL/data/reusables/dependabot/initial-updates.md +++ /dev/null @@ -1,3 +0,0 @@ -Cuando habilitas las actualizaciones de versión por primera vez, podrías tener muchas dependencias desactualizadas y algunas podrían estar varias versiones debajo de la última. {% data variables.product.prodname_dependabot %} verifica las dependencias que estén desactualizadas tan pronto se habilita. Podrías ver nuevas solicitudes de extracción para las actualizaciones de versión después de algunos minutos de haber agregado el archivo de configuración, dependiendo de la cantidad de archivos de manifiesto para los cuales configuras las actualizaciones. - -Para mantener la fácil administración y revisión de las solicitudes de extracción, {% data variables.product.prodname_dependabot_short %} levanta un máximo de cinco solicitudes de extracción para comenzar a actualizar a las dependencias a su versión más reciente. Si fusionas algunas de estas primeras solicitudes de extracción antes de la siguiente actualización programada, entonces se abrirá un máximo de cinco solicitudes para todas aquellas subsecuentes (puedes cambiar este límite). diff --git a/translations/es-XL/data/reusables/dependabot/option-affects-security-updates.md b/translations/es-XL/data/reusables/dependabot/option-affects-security-updates.md deleted file mode 100644 index 554f775bf0..0000000000 --- a/translations/es-XL/data/reusables/dependabot/option-affects-security-updates.md +++ /dev/null @@ -1 +0,0 @@ -Configurar esta opción también afectará a las solicitudes de extracción para las actualizaciones de seguridad en los archivos de manifiesto de este administrador de paquete, a menos de que utilices `target-branch` para revisar las actualizaciones de versión en una rama diferente a la predeterminada. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dependabot/private-dependencies.md b/translations/es-XL/data/reusables/dependabot/private-dependencies.md deleted file mode 100644 index 610a5ed6c9..0000000000 --- a/translations/es-XL/data/reusables/dependabot/private-dependencies.md +++ /dev/null @@ -1 +0,0 @@ -Actualmente, {% data variables.product.prodname_dependabot_version_updates %} no son compatibles con archivos de bloqueo o de manifiesto que contengan dependencias o registros de git privados. Esto es porque, cuando se ejecutan las actualizaciones de versión, {% data variables.product.prodname_dependabot_short %} debe poder resolver todas las dependencias de su fuente para verificar que dichas actualizaciones de versión hayan sido exitosas. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dependabot/supported-package-managers.md b/translations/es-XL/data/reusables/dependabot/supported-package-managers.md deleted file mode 100644 index f9cb69f91b..0000000000 --- a/translations/es-XL/data/reusables/dependabot/supported-package-managers.md +++ /dev/null @@ -1,15 +0,0 @@ -- Bundler: `bundler` -- Cargo: `cargo` -- Composer: `composer` -- Docker: `docker` -- Elm: `elm` -- git submodule: `gitsubmodule` -- GitHub Actions: `github-actions` -- Go modules: `gomod` -- Gradle: `gradle` -- Maven: `maven` -- Mix: `mix` -- npm: `npm` -- NuGet: `nuget` -- pip: `pip` -- Terraform: `terraform` diff --git a/translations/es-XL/data/reusables/dependabot/upgrade-dependency-to-minimum-secure-version.md b/translations/es-XL/data/reusables/dependabot/upgrade-dependency-to-minimum-secure-version.md deleted file mode 100644 index 74193dfd05..0000000000 --- a/translations/es-XL/data/reusables/dependabot/upgrade-dependency-to-minimum-secure-version.md +++ /dev/null @@ -1,7 +0,0 @@ -La solicitud de extracción mejorará la dependencia a la versión segura mínima que sea posible y necesaria para evitar la vulnerabilidad. - -{% note %} - -**Nota:** El tener pruebas automatizadas y procesos de aceptación establecidos para que las verificaciones se lleven a cabo antes de que se fusione la solicitud de extracción se considera como una buena práctica. Esto es particularmente importante si la versión que se sugiere mejorar contiene funcionalidades adicionales o un cambio que infrinja el código de tu proyecto. Para obtener más información acerca de la integración contínua, consulta la sección "[Acerca de la Integración Contínua](/actions/building-and-testing-code-with-continuous-integration/about-continuous-integration)". - -{% endnote %} diff --git a/translations/es-XL/data/reusables/dependabot/version-updates-for-actions.md b/translations/es-XL/data/reusables/dependabot/version-updates-for-actions.md deleted file mode 100644 index 7302f4637b..0000000000 --- a/translations/es-XL/data/reusables/dependabot/version-updates-for-actions.md +++ /dev/null @@ -1 +0,0 @@ -También puedes habilitar las {% data variables.product.prodname_dependabot_version_updates %} para las acciones que agregas a tu flujo de trabajo. Para obtener más información, consulta la sección "[Mantener tus acciones actualizadas con el {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot)". diff --git a/translations/es-XL/data/reusables/dependabot/warning-ignore-option.md b/translations/es-XL/data/reusables/dependabot/warning-ignore-option.md deleted file mode 100644 index a3b9cc0382..0000000000 --- a/translations/es-XL/data/reusables/dependabot/warning-ignore-option.md +++ /dev/null @@ -1,7 +0,0 @@ -{% warning %} - -**Advertencia**: Antes de que agregues una opción de `ignore` al archivo de configuración *dependabot.yml*, revisa si el repositorio ya tiene alguna preferencia de ignorar (Que se haya creado utilizando los comandos de `@dependabot ignore`). Cuando agregas una opción de `ignore` al archivo de configuración *dependabot.yml*, esto ignora cualquier preferencia de ignorar almacenada centralmente para ese administrador de paquetes, rama, y directorio. - -Esto afecta a las actualizaciones tanto de seguridad como de versión. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/desktop/2fa-in-browser.md b/translations/es-XL/data/reusables/desktop/2fa-in-browser.md deleted file mode 100644 index 95f254e0c5..0000000000 --- a/translations/es-XL/data/reusables/desktop/2fa-in-browser.md +++ /dev/null @@ -1,5 +0,0 @@ -1. Si has configurado la autenticación de dos factores (2FA) para {% data variables.product.prodname_dotcom %}, realiza una de las siguientes acciones: - - Si configuras 2FA por medio de SMS, recupera tu código 2FA de un mensaje SMS. - - Si configuras 2FA con una aplicación TOTP, genera un código 2FA. - - Ingresa entonces tu código de 2FA en el mensaje de {% data variables.product.prodname_dotcom %} y da clic en **Verificar**. ![El campo de código de autenticación 2FA](/assets/images/help/desktop/2fa-code-field.png) diff --git a/translations/es-XL/data/reusables/desktop/about-github-desktop.md b/translations/es-XL/data/reusables/desktop/about-github-desktop.md deleted file mode 100644 index e9a8b75f90..0000000000 --- a/translations/es-XL/data/reusables/desktop/about-github-desktop.md +++ /dev/null @@ -1,7 +0,0 @@ -{% data variables.product.prodname_desktop %} es una herramienta de código abierto que te permite ser más productivo. {% data variables.product.prodname_desktop %} fomenta que tú y tu equipo colaboren utilizando las mejoras prácticas con Git y {% data variables.product.prodname_dotcom %}. - -Ésto es solo una parte de lo mucho que puedes hacer con {% data variables.product.prodname_desktop %}: -- Añadir cambios a tu confirmación de forma interactiva -- Añadir co-autores rápidamente en tu confirmación -- Controlar ramas con solicitudes de extracción y ver los estados de CI -- Comparar las imágenes que han cambiado diff --git a/translations/es-XL/data/reusables/desktop/authenticate-in-browser.md b/translations/es-XL/data/reusables/desktop/authenticate-in-browser.md deleted file mode 100644 index a1a7f9151f..0000000000 --- a/translations/es-XL/data/reusables/desktop/authenticate-in-browser.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Para autenticarte en {% data variables.product.prodname_dotcom %}, escribe tus credenciales de {% data variables.product.prodname_dotcom %}.com y haz clic en **Sign in (Iniciar sesión)**. ![El botón de Inicio de sesión para {% data variables.product.prodname_dotcom %} en el navegador](/assets/images/help/desktop/sign-in-button-browser.png) - - Como alternativa, si ya hubieras iniciado sesión en {% data variables.product.prodname_dotcom %}, sigue los mensajes para regresar a {% data variables.product.prodname_desktop %} y así completar la autenticación. diff --git a/translations/es-XL/data/reusables/desktop/choose-a-branch-to-merge.md b/translations/es-XL/data/reusables/desktop/choose-a-branch-to-merge.md deleted file mode 100644 index 8eaebf8d99..0000000000 --- a/translations/es-XL/data/reusables/desktop/choose-a-branch-to-merge.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Choose a branch to merge into (Elige una rama para fusionarse en) BRANCH**. ![Elige una opción de rama en la lista de menús de ramas](/assets/images/help/desktop/merge-branch-button-list.png) diff --git a/translations/es-XL/data/reusables/desktop/choose-a-theme.md b/translations/es-XL/data/reusables/desktop/choose-a-theme.md deleted file mode 100644 index ffc0687492..0000000000 --- a/translations/es-XL/data/reusables/desktop/choose-a-theme.md +++ /dev/null @@ -1,2 +0,0 @@ -3. Haz clic en **Appearance (Apariencia)**. -4. Haz clic en el tema que quieres usar. Opcionalmente, puedes seleccionar **Cambiar de tema automáticamente para coincidir con el sistema** si quieres que {% data variables.product.prodname_desktop %} siempre haga coincidir el tema con tu computador. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/desktop/choose-clone-repository.md b/translations/es-XL/data/reusables/desktop/choose-clone-repository.md deleted file mode 100644 index 60d3ab7a9c..0000000000 --- a/translations/es-XL/data/reusables/desktop/choose-clone-repository.md +++ /dev/null @@ -1 +0,0 @@ -1. En el menú **File (Archivo)** haz clic en **Clone Repository (Clonar repositorio)**. diff --git a/translations/es-XL/data/reusables/desktop/choose-pr-from-list.md b/translations/es-XL/data/reusables/desktop/choose-pr-from-list.md deleted file mode 100644 index 70430fb0f8..0000000000 --- a/translations/es-XL/data/reusables/desktop/choose-pr-from-list.md +++ /dev/null @@ -1 +0,0 @@ -1. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que deseas visualizar. diff --git a/translations/es-XL/data/reusables/desktop/choose-product-authenticate.md b/translations/es-XL/data/reusables/desktop/choose-product-authenticate.md deleted file mode 100644 index 1cb028f54f..0000000000 --- a/translations/es-XL/data/reusables/desktop/choose-product-authenticate.md +++ /dev/null @@ -1 +0,0 @@ -1. A la derecha de "{% data variables.product.prodname_enterprise %} Server", da clic en **Iniciar sesión**. ![El botón de Iniciar sesión para GitHub Enterprise Server](/assets/images/help/desktop/sign-in-ghes.png) diff --git a/translations/es-XL/data/reusables/desktop/click-base-branch-in-drop-down.md b/translations/es-XL/data/reusables/desktop/click-base-branch-in-drop-down.md deleted file mode 100644 index e66a1e5be2..0000000000 --- a/translations/es-XL/data/reusables/desktop/click-base-branch-in-drop-down.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de la app, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y luego, en la lista de ramas, da clic en aquella que quieras sea la base de tu nueva rama. diff --git a/translations/es-XL/data/reusables/desktop/click-discard-files.md b/translations/es-XL/data/reusables/desktop/click-discard-files.md deleted file mode 100644 index bc8a11da9c..0000000000 --- a/translations/es-XL/data/reusables/desktop/click-discard-files.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Discard Changes (Descartar cambios)** o **Discard Selected Changes (Descartar cambios seleccionados)** para descartar cambios a uno o más archivos, o **Discard All Changes (Descartar todos los cambios)** para descartar cambios a todos los archivos desde la última confirmación. diff --git a/translations/es-XL/data/reusables/desktop/click-pull-requests.md b/translations/es-XL/data/reusables/desktop/click-pull-requests.md deleted file mode 100644 index fadac59c33..0000000000 --- a/translations/es-XL/data/reusables/desktop/click-pull-requests.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior del menú desplegable, haz clic en **Pull Requests (Solicitudes de extracción)**. diff --git a/translations/es-XL/data/reusables/desktop/click-save-git-config.md b/translations/es-XL/data/reusables/desktop/click-save-git-config.md deleted file mode 100644 index d4b241275b..0000000000 --- a/translations/es-XL/data/reusables/desktop/click-save-git-config.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/data/reusables/desktop/cloning-location-tab.md b/translations/es-XL/data/reusables/desktop/cloning-location-tab.md deleted file mode 100644 index c8253e6267..0000000000 --- a/translations/es-XL/data/reusables/desktop/cloning-location-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en la pestaña que corresponde a la ubicación del repositorio que deseas clonar. También puedes hacer clic en **URL** para introducir manualmente la ubicación del repositorio. diff --git a/translations/es-XL/data/reusables/desktop/cloning-repository-list.md b/translations/es-XL/data/reusables/desktop/cloning-repository-list.md deleted file mode 100644 index 98054b13f6..0000000000 --- a/translations/es-XL/data/reusables/desktop/cloning-repository-list.md +++ /dev/null @@ -1 +0,0 @@ -1. Elige dentro de la lista el repositorio que deseas clonar. diff --git a/translations/es-XL/data/reusables/desktop/commit-all-desc.md b/translations/es-XL/data/reusables/desktop/commit-all-desc.md deleted file mode 100644 index cce9ee7ca1..0000000000 --- a/translations/es-XL/data/reusables/desktop/commit-all-desc.md +++ /dev/null @@ -1 +0,0 @@ -Para agregar **todos los cambios en todos los archivos** en una única confirmación, mantén seleccionada la casilla de verificación que aparece en la parte superior de la lista seleccionada. diff --git a/translations/es-XL/data/reusables/desktop/commit-button.md b/translations/es-XL/data/reusables/desktop/commit-button.md deleted file mode 100644 index 7e4778a0dd..0000000000 --- a/translations/es-XL/data/reusables/desktop/commit-button.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro del campo Description (Descripción), haz clic en **Commit to (Confirmar a)BRANCH**. diff --git a/translations/es-XL/data/reusables/desktop/commit-message.md b/translations/es-XL/data/reusables/desktop/commit-message.md deleted file mode 100644 index fe80032afa..0000000000 --- a/translations/es-XL/data/reusables/desktop/commit-message.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte inferior de la lista de cambios, en el campo Summary (Resumen), escribe un mensaje de confirmación corto y significativo. De forma opcional, puedes añadir más información sobre el cambio en el campo Description (Descripción). diff --git a/translations/es-XL/data/reusables/desktop/commit-some-desc.md b/translations/es-XL/data/reusables/desktop/commit-some-desc.md deleted file mode 100644 index 6f04a0cb29..0000000000 --- a/translations/es-XL/data/reusables/desktop/commit-some-desc.md +++ /dev/null @@ -1 +0,0 @@ -Para agregar **todos los cambios en uno o más archivos** en una confirmación única, quita la marca de selección de las casillas de verificación que se encuentran junto a los archivos que no deseas incluir y deja seleccionados solamente los archivos que deseas incluir en la confirmación. Puedes cambiar la casilla de verificación con las teclas `Barra espaciadora` o `Enter` después de seleccionar un archivo. diff --git a/translations/es-XL/data/reusables/desktop/confirm-discard-files.md b/translations/es-XL/data/reusables/desktop/confirm-discard-files.md deleted file mode 100644 index 8ae2526ef1..0000000000 --- a/translations/es-XL/data/reusables/desktop/confirm-discard-files.md +++ /dev/null @@ -1 +0,0 @@ -1. Para confirmar los cambios, revisa los archivos afectados y haz clic en **Discard Changes (Descartar cambios)**. diff --git a/translations/es-XL/data/reusables/desktop/confirm-merging-branch.md b/translations/es-XL/data/reusables/desktop/confirm-merging-branch.md deleted file mode 100644 index 98b794a67c..0000000000 --- a/translations/es-XL/data/reusables/desktop/confirm-merging-branch.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en la rama que deseas fusionar en la rama actual y luego haz clic en **Merge (Fusionar) BRANCH en BRANCH**. diff --git a/translations/es-XL/data/reusables/desktop/confirm-new-branch-button.md b/translations/es-XL/data/reusables/desktop/confirm-new-branch-button.md deleted file mode 100644 index ab607c196f..0000000000 --- a/translations/es-XL/data/reusables/desktop/confirm-new-branch-button.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Create Branch (Crear rama)**. diff --git a/translations/es-XL/data/reusables/desktop/confirm-tag.md b/translations/es-XL/data/reusables/desktop/confirm-tag.md deleted file mode 100644 index f5ea7f4bdf..0000000000 --- a/translations/es-XL/data/reusables/desktop/confirm-tag.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Crear etiqueta**. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/desktop/copy-email-git-config.md b/translations/es-XL/data/reusables/desktop/copy-email-git-config.md deleted file mode 100644 index ba04ce0d0b..0000000000 --- a/translations/es-XL/data/reusables/desktop/copy-email-git-config.md +++ /dev/null @@ -1 +0,0 @@ -1. Copia la dirección de correo electrónico que deseas usar en tu configuración local de Git. diff --git a/translations/es-XL/data/reusables/desktop/create-new-branch.md b/translations/es-XL/data/reusables/desktop/create-new-branch.md deleted file mode 100644 index 9b63a250e1..0000000000 --- a/translations/es-XL/data/reusables/desktop/create-new-branch.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **New Branch (Nueva rama)**. diff --git a/translations/es-XL/data/reusables/desktop/create-tag.md b/translations/es-XL/data/reusables/desktop/create-tag.md deleted file mode 100644 index cc91bd24a9..0000000000 --- a/translations/es-XL/data/reusables/desktop/create-tag.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic derecho en la confirmación y da clic en **Crear Etiqueta...**. ![Selecciona el elemento de menú de crear etiqueta](/assets/images/help/desktop/select-create-tag.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/desktop/current-branch-menu.md b/translations/es-XL/data/reusables/desktop/current-branch-menu.md deleted file mode 100644 index 78b229867d..0000000000 --- a/translations/es-XL/data/reusables/desktop/current-branch-menu.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.prodname_desktop %}, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual**. ![Menú desplegable de la rama actual](/assets/images/help/desktop/current-branch-menu.png) diff --git a/translations/es-XL/data/reusables/desktop/delete-branch-mac.md b/translations/es-XL/data/reusables/desktop/delete-branch-mac.md deleted file mode 100644 index 9e02fa64a1..0000000000 --- a/translations/es-XL/data/reusables/desktop/delete-branch-mac.md +++ /dev/null @@ -1 +0,0 @@ -1. En tu barra de menú, da clic en **Rama** y luego en **Borrar...**. También puedes presionar shift⌘ commandD. diff --git a/translations/es-XL/data/reusables/desktop/delete-branch-win.md b/translations/es-XL/data/reusables/desktop/delete-branch-win.md deleted file mode 100644 index 3986b153f3..0000000000 --- a/translations/es-XL/data/reusables/desktop/delete-branch-win.md +++ /dev/null @@ -1 +0,0 @@ -1. En tu barra de menú, da clic en **Rama** y luego en **Borrar...**. También puedes presionar CtrlShiftD. diff --git a/translations/es-XL/data/reusables/desktop/download-desktop-page.md b/translations/es-XL/data/reusables/desktop/download-desktop-page.md deleted file mode 100644 index 04698cd4b1..0000000000 --- a/translations/es-XL/data/reusables/desktop/download-desktop-page.md +++ /dev/null @@ -1 +0,0 @@ -1. Visita la [página de descargas para {% data variables.product.prodname_desktop %} ](https://desktop.github.com/). diff --git a/translations/es-XL/data/reusables/desktop/get-an-account.md b/translations/es-XL/data/reusables/desktop/get-an-account.md deleted file mode 100644 index 6b37dbbd5c..0000000000 --- a/translations/es-XL/data/reusables/desktop/get-an-account.md +++ /dev/null @@ -1,4 +0,0 @@ -debes contar previamente con una cuenta de {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. - -- Para obtener más información sobre crear una cuenta de {% data variables.product.prodname_dotcom %}, consulta "[Registrar una nueva cuenta de {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account/)". -- Para una cuenta de {% data variables.product.prodname_enterprise %}, contacta a tu administrador de sitio de {% data variables.product.prodname_enterprise %}. diff --git a/translations/es-XL/data/reusables/desktop/history-tab.md b/translations/es-XL/data/reusables/desktop/history-tab.md deleted file mode 100644 index 6be245bc91..0000000000 --- a/translations/es-XL/data/reusables/desktop/history-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **History (Historial)**. ![La pestaña de historial seleccionada en la barra lateral](/assets/images/help/desktop/history-tab-in-commit-sidebar.png) diff --git a/translations/es-XL/data/reusables/desktop/launch-desktop-from-command-line.md b/translations/es-XL/data/reusables/desktop/launch-desktop-from-command-line.md deleted file mode 100644 index 9fc2b2eb74..0000000000 --- a/translations/es-XL/data/reusables/desktop/launch-desktop-from-command-line.md +++ /dev/null @@ -1 +0,0 @@ -Para iniciar {% data variables.product.prodname_desktop %} al último repositorio abierto, escribe `github`. Para lanzar {% data variables.product.prodname_desktop %} para un repositorio particular, teclea `github` seguido de la ruta al repositorio. diff --git a/translations/es-XL/data/reusables/desktop/mac-select-accounts.md b/translations/es-XL/data/reusables/desktop/mac-select-accounts.md deleted file mode 100644 index 1b14eebe3e..0000000000 --- a/translations/es-XL/data/reusables/desktop/mac-select-accounts.md +++ /dev/null @@ -1 +0,0 @@ -1. En la ventana Preferences (Preferencias), selecciona **Accounts (Cuentas)**. ![El panel Accounts (Cuentas) en la ventana Preferences (Preferencias)](/assets/images/help/desktop/mac-select-accounts-pane.png) diff --git a/translations/es-XL/data/reusables/desktop/mac-select-desktop-menu.md b/translations/es-XL/data/reusables/desktop/mac-select-desktop-menu.md deleted file mode 100644 index d7ab57dd66..0000000000 --- a/translations/es-XL/data/reusables/desktop/mac-select-desktop-menu.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra de menú, utiliza el menú desplegable de **{% data variables.product.prodname_desktop %}** y luego da clic en **Preferencias**. ![El valor de preferencias en el menú desplegable de {% data variables.product.prodname_desktop %}](/assets/images/help/desktop/mac-choose-preferences.png) diff --git a/translations/es-XL/data/reusables/desktop/make-changes.md b/translations/es-XL/data/reusables/desktop/make-changes.md deleted file mode 100644 index d0f6c36d52..0000000000 --- a/translations/es-XL/data/reusables/desktop/make-changes.md +++ /dev/null @@ -1 +0,0 @@ -1. Usando tu editor de texto favorito, por ejemplo, [Atom](https://atom.io/), realiza los cambios necesarios en los archivos de tu proyecto. diff --git a/translations/es-XL/data/reusables/desktop/name-branch.md b/translations/es-XL/data/reusables/desktop/name-branch.md deleted file mode 100644 index b39e6aa4ec..0000000000 --- a/translations/es-XL/data/reusables/desktop/name-branch.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de **Name (Nombre)**, escribe el nombre de la nueva rama. diff --git a/translations/es-XL/data/reusables/desktop/name-field-git-config.md b/translations/es-XL/data/reusables/desktop/name-field-git-config.md deleted file mode 100644 index 4e879a099f..0000000000 --- a/translations/es-XL/data/reusables/desktop/name-field-git-config.md +++ /dev/null @@ -1 +0,0 @@ -1. En el campo **Name (Nombre)**, ingresa el nombre que deseas usar para tu configuración Git. diff --git a/translations/es-XL/data/reusables/desktop/name-tag.md b/translations/es-XL/data/reusables/desktop/name-tag.md deleted file mode 100644 index 35b951fb62..0000000000 --- a/translations/es-XL/data/reusables/desktop/name-tag.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea el nombre de la etiqueta. ![Ingresa un nombre de eitqueta](/assets/images/help/desktop/enter-tag-name.png) diff --git a/translations/es-XL/data/reusables/desktop/paste-email-git-config.md b/translations/es-XL/data/reusables/desktop/paste-email-git-config.md deleted file mode 100644 index 78c2fb9528..0000000000 --- a/translations/es-XL/data/reusables/desktop/paste-email-git-config.md +++ /dev/null @@ -1 +0,0 @@ -1. En el campo **Email (Correo electrónico)**, pega la dirección de correo electrónico que copiaste de los parámetros de tu cuenta de {% data variables.product.prodname_dotcom %} o de {% data variables.product.prodname_enterprise %}. diff --git a/translations/es-XL/data/reusables/desktop/preferences-options-tabs.md b/translations/es-XL/data/reusables/desktop/preferences-options-tabs.md deleted file mode 100644 index d86faedbf6..0000000000 --- a/translations/es-XL/data/reusables/desktop/preferences-options-tabs.md +++ /dev/null @@ -1,5 +0,0 @@ - - Elige **Accounts** (Cuentas) para agregar o quitar una cuenta {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. - - Elija **Integrations (Integraciones)** para elegir un editor o shell. - - Elige **Git** para editar tu configuración de Git. - - Elige **Appearance (Apariencia)** para cambiar entre el tema claro u oscuro. - - Elige **Advanced** (Avanzado) para más opciones de configuración. diff --git a/translations/es-XL/data/reusables/desktop/protected-branches.md b/translations/es-XL/data/reusables/desktop/protected-branches.md deleted file mode 100644 index 94dd074d3c..0000000000 --- a/translations/es-XL/data/reusables/desktop/protected-branches.md +++ /dev/null @@ -1 +0,0 @@ -Los administradores de un repositorio pueden activar las protecciones en una rama. Si estás trabajando en una rama que está protegida, no podrás eliminar ni hacer un empuje forzado a la rama. Los administradores de repositorio pueden habilitar otras configuraciones de la rama protegida para requerir ciertos flujos de trabajo antes de que la rama se pueda fusionar. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". diff --git a/translations/es-XL/data/reusables/desktop/publish-repository.md b/translations/es-XL/data/reusables/desktop/publish-repository.md deleted file mode 100644 index 50312d51ce..0000000000 --- a/translations/es-XL/data/reusables/desktop/publish-repository.md +++ /dev/null @@ -1 +0,0 @@ -3. Haz clic en el botón **Publish Repository (Publicar repositorio)** en la barra de herramientas. ![El botón Publicar repositorio en la barra de herramientas](/assets/images/help/desktop/publish-repository-toolbar-button.png) diff --git a/translations/es-XL/data/reusables/desktop/push-origin.md b/translations/es-XL/data/reusables/desktop/push-origin.md deleted file mode 100644 index 22ade305c8..0000000000 --- a/translations/es-XL/data/reusables/desktop/push-origin.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Cargar al origen** para cargar tus cambios locales al repositorio remoto. ![El botón Subir](/assets/images/help/desktop/push-origin-button.png) diff --git a/translations/es-XL/data/reusables/desktop/resolve-merge-conflicts.md b/translations/es-XL/data/reusables/desktop/resolve-merge-conflicts.md deleted file mode 100644 index 24f5e7b0cc..0000000000 --- a/translations/es-XL/data/reusables/desktop/resolve-merge-conflicts.md +++ /dev/null @@ -1 +0,0 @@ -1. Resuelve cualquier conflicto de fusión que se produzca de la manera que prefieras, usando un editor de texto, la línea de comando o cualquier otra herramienta. Para obtener más información, consulta "[Abordar conflictos de fusión](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts)." diff --git a/translations/es-XL/data/reusables/desktop/retrieve-2fa.md b/translations/es-XL/data/reusables/desktop/retrieve-2fa.md deleted file mode 100644 index aa437467af..0000000000 --- a/translations/es-XL/data/reusables/desktop/retrieve-2fa.md +++ /dev/null @@ -1,5 +0,0 @@ -1. Si has configurado la autenticación de dos factores para {% data variables.product.prodname_enterprise %}, realiza una de las siguientes acciones: - - Si configuras 2FA por medio de SMS, recupera tu código 2FA de un mensaje SMS. - - Si configuras 2FA con una aplicación TOTP, genera un código 2FA. - - Ingresa entonces tu código de 2FA en el mensaje de {% data variables.product.prodname_desktop %} y da clic en **Iniciar Sesión**. ![El campo de código de autenticación 2FA](/assets/images/help/desktop/mac-2fa-code-prompt.png) diff --git a/translations/es-XL/data/reusables/desktop/return-to-desktop.md b/translations/es-XL/data/reusables/desktop/return-to-desktop.md deleted file mode 100644 index e42a6e3d5b..0000000000 --- a/translations/es-XL/data/reusables/desktop/return-to-desktop.md +++ /dev/null @@ -1 +0,0 @@ -1. Regresa a {% data variables.product.prodname_desktop %}. diff --git a/translations/es-XL/data/reusables/desktop/revert-commit.md b/translations/es-XL/data/reusables/desktop/revert-commit.md deleted file mode 100644 index 834d135944..0000000000 --- a/translations/es-XL/data/reusables/desktop/revert-commit.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic derecho en la confirmación que quieras revertir y da clic en **Revertir esta confirmación**. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/desktop/select-base-branch.md b/translations/es-XL/data/reusables/desktop/select-base-branch.md deleted file mode 100644 index e5f1298d3f..0000000000 --- a/translations/es-XL/data/reusables/desktop/select-base-branch.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecciona la rama actual o la rama por defecto (por lo general, la rama principal) en la que se basará la nueva rama. diff --git a/translations/es-XL/data/reusables/desktop/select-branch-to-delete.md b/translations/es-XL/data/reusables/desktop/select-branch-to-delete.md deleted file mode 100644 index 6ddbfa7646..0000000000 --- a/translations/es-XL/data/reusables/desktop/select-branch-to-delete.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de la app, da clic en {% octicon "git-branch" aria-label="The branch icon" %} **Rama Actual** y luego en la rama que quieres borrar. diff --git a/translations/es-XL/data/reusables/desktop/select-discard-files.md b/translations/es-XL/data/reusables/desktop/select-discard-files.md deleted file mode 100644 index 354a9bed23..0000000000 --- a/translations/es-XL/data/reusables/desktop/select-discard-files.md +++ /dev/null @@ -1 +0,0 @@ -1. En la lista de archivos cambiados, selecciona los archivos en los que deseas descartar los cambios desde la última confirmación. Para seleccionar varios archivos, haz clic en `shift` y haz clic en el rango de archivos desde los que deseas descartar los cambios. ![Selecciona varios archivos con cambios a descartar](/assets/images/help/desktop/select-multiple-files-discard.png) diff --git a/translations/es-XL/data/reusables/desktop/sign-in-choose-product.md b/translations/es-XL/data/reusables/desktop/sign-in-choose-product.md deleted file mode 100644 index d18944196a..0000000000 --- a/translations/es-XL/data/reusables/desktop/sign-in-choose-product.md +++ /dev/null @@ -1 +0,0 @@ -1. Inicia sesión en {% data variables.product.prodname_dotcom %} o {% data variables.product.prodname_enterprise %}. diff --git a/translations/es-XL/data/reusables/desktop/switching-between-branches.md b/translations/es-XL/data/reusables/desktop/switching-between-branches.md deleted file mode 100644 index 3922ebe8ed..0000000000 --- a/translations/es-XL/data/reusables/desktop/switching-between-branches.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de la lista de ramas, haz clic en la rama a la que deseas cambiar para continuar. diff --git a/translations/es-XL/data/reusables/desktop/tags-push-with-commits.md b/translations/es-XL/data/reusables/desktop/tags-push-with-commits.md deleted file mode 100644 index ef3164e597..0000000000 --- a/translations/es-XL/data/reusables/desktop/tags-push-with-commits.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, {% data variables.product.prodname_desktop %} cargará la etiqueta que creaste a tu repositorio con la confirmación asociada. diff --git a/translations/es-XL/data/reusables/desktop/update-email-address.md b/translations/es-XL/data/reusables/desktop/update-email-address.md deleted file mode 100644 index 79aed74fcd..0000000000 --- a/translations/es-XL/data/reusables/desktop/update-email-address.md +++ /dev/null @@ -1 +0,0 @@ -Si las confirmaciones que haces en {% data variables.product.prodname_desktop %} se asocian con la cuenta incorrecta de {% data variables.product.product_name %}, actualiza la dirección de correo electrónico en tu configuración de Git utilizando {% data variables.product.prodname_desktop %}. diff --git a/translations/es-XL/data/reusables/desktop/windows-choose-options.md b/translations/es-XL/data/reusables/desktop/windows-choose-options.md deleted file mode 100644 index 2bc077e1a2..0000000000 --- a/translations/es-XL/data/reusables/desktop/windows-choose-options.md +++ /dev/null @@ -1 +0,0 @@ -1. Utiliza el menú de **Archivo** y luego da clic en **Opciones**. ![El valor de Opciones en el menú desplegable de Configuración](/assets/images/help/desktop/windows-choose-options.png) diff --git a/translations/es-XL/data/reusables/desktop/windows-select-accounts.md b/translations/es-XL/data/reusables/desktop/windows-select-accounts.md deleted file mode 100644 index f24767759f..0000000000 --- a/translations/es-XL/data/reusables/desktop/windows-select-accounts.md +++ /dev/null @@ -1 +0,0 @@ -1. En la ventana de Opciones, selecciona **Accounts (Cuentas)**. ![El panel Accounts (Cuentas) en la ventana de Opciones](/assets/images/help/desktop/windows-select-accounts-pane.png) diff --git a/translations/es-XL/data/reusables/desktop/windows_git_bash.md b/translations/es-XL/data/reusables/desktop/windows_git_bash.md deleted file mode 100644 index 075f6353ff..0000000000 --- a/translations/es-XL/data/reusables/desktop/windows_git_bash.md +++ /dev/null @@ -1 +0,0 @@ -Si tienes [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) instalado, puedes usarlo para clonar repositorios y no manejar claves SSH. diff --git a/translations/es-XL/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md b/translations/es-XL/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md deleted file mode 100644 index 988b9dab32..0000000000 --- a/translations/es-XL/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md +++ /dev/null @@ -1,6 +0,0 @@ -**Si estás usando Git Bash**, activa el ssh-agent: -```shell -# inicia el ssh-agent en segundo plano -$ eval "$(ssh-agent -s)" -> Agent pid 59566 -``` diff --git a/translations/es-XL/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md b/translations/es-XL/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md deleted file mode 100644 index 56513a3949..0000000000 --- a/translations/es-XL/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md +++ /dev/null @@ -1,6 +0,0 @@ -**Si estás usando otro símbolo de terminal**, como [Git para Windows](https://git-for-windows.github.io/), activa el ssh-agent: -```shell -# start the ssh-agent in the background -$ eval $(ssh-agent -s) -> Agent pid 59566 -``` diff --git a/translations/es-XL/data/reusables/developer-site/limit_workflow_to_activity_types.md b/translations/es-XL/data/reusables/developer-site/limit_workflow_to_activity_types.md deleted file mode 100644 index 0513106c90..0000000000 --- a/translations/es-XL/data/reusables/developer-site/limit_workflow_to_activity_types.md +++ /dev/null @@ -1 +0,0 @@ -Por defecto, todos los tipos de actividad desencadenan un flujo de trabajo a ejecutarse. Puedes limitar tus ejecuciones de flujo de trabajo a tipos de actividad específicos usando la palabra clave `types`. Para obtener más información, consulta "[Sintaxis del flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)". diff --git a/translations/es-XL/data/reusables/developer-site/multiple_activity_types.md b/translations/es-XL/data/reusables/developer-site/multiple_activity_types.md deleted file mode 100644 index a3485ab600..0000000000 --- a/translations/es-XL/data/reusables/developer-site/multiple_activity_types.md +++ /dev/null @@ -1 +0,0 @@ -Más de un tipo de actividad desencadena este evento. diff --git a/translations/es-XL/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/es-XL/data/reusables/developer-site/pull_request_forked_repos_link.md deleted file mode 100644 index aeeccf6ddb..0000000000 --- a/translations/es-XL/data/reusables/developer-site/pull_request_forked_repos_link.md +++ /dev/null @@ -1,13 +0,0 @@ -##### Eventos de solicitud de extracción para repositorios bifurcados - -{% note %} - -**Nota:** los flujos de trabajo no se ejecutan en repositorios base privados cuando abres una solicitud de extracción desde un repositorio bifurcado. - -{% endnote %} - -Cuando creas una solicitud de extracción desde un repositorio bifurcado al repositorio base, {% data variables.product.prodname_dotcom %} envía el evento `pull_request` al repositorio base y no se producen eventos de solicitud de extracción en el repositorio bifurcado. - -Los flujos de trabajo no se ejecutan en repositorios bifurcados por defecto. Debes habilitar las Acciones de GitHub en la pestaña **Acciones** del repositorio bifurcado. - -Los permisos para el `GITHUB_TOKEN` en los repositorios bifurcados son de solo lectura. Para más información, consulta la sección "[Autenticarse con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." diff --git a/translations/es-XL/data/reusables/dotcom_billing/500-error.md b/translations/es-XL/data/reusables/dotcom_billing/500-error.md deleted file mode 100644 index c1b005a2fb..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/500-error.md +++ /dev/null @@ -1,5 +0,0 @@ -Si recibes un error 500 al intentar actualizar tu cuenta: - - Intenta limpiar la caché de tu navegador, luego vuelve a enviar tu información - - Comprueba y asegúrate de haber introducido correctamente tus datos de pago - -Si esta acción no resuelve el problema, comunícate con {% data variables.contact.contact_support %}. diff --git a/translations/es-XL/data/reusables/dotcom_billing/actions-minutes.md b/translations/es-XL/data/reusables/dotcom_billing/actions-minutes.md deleted file mode 100644 index 3cfff87816..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/actions-minutes.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "{% data variables.product.prodname_actions %}", visualiza los detalles de tus minutos usados. ![Detalles de uso de minutos](/assets/images/help/billing/actions-minutes.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/es-XL/data/reusables/dotcom_billing/actions-packages-report-download.md deleted file mode 100644 index 9e198c5cb7..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/actions-packages-report-download.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, da clic en **Obtener reporte de uso** para que se te envíe un archivo CSV por correo electrónico del uso de almacenamiento para {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} a la dirección de correo electrónico principal de la cuenta. ![Descargar reporte en CSV](/assets/images/help/billing/actions-packages-report-download.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md b/translations/es-XL/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md deleted file mode 100644 index 7cda523dff..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de " Almacenamiento de {% data variables.product.prodname_dotcom %} para Actions y Packages", visualiza los detalles de uso de almacenamiento para cada organización en tu cuenta empresarial, tanto para {% data variables.product.prodname_actions %} como para {% data variables.product.prodname_registry %}. ![Detalles de uso de almacenamiento](/assets/images/help/billing/actions-packages-storage-enterprise.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/actions-packages-storage.md b/translations/es-XL/data/reusables/dotcom_billing/actions-packages-storage.md deleted file mode 100644 index 9a7b00f243..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/actions-packages-storage.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Almacenamiento para Actions y Packages", visualiza los detalles de tu uso de almacenamiento combinado de {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %}. Los datos de uso de almacenamiento se sincronizan cada hora. ![Detalles de uso de almacenamiento](/assets/images/help/billing/actions-packages-storage.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/es-XL/data/reusables/dotcom_billing/actions-packages-unpaid-account.md deleted file mode 100644 index d870c94b2e..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/actions-packages-unpaid-account.md +++ /dev/null @@ -1,5 +0,0 @@ -Si tu cuenta tiene cargos pendientes sin pagar: - -* El almacenamiento o minutos que se incluyen en tu cuenta para {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} no se restablecerán hasta que se haya procesado exitosamente el pago. -* Para las cuentas que aún cuenten con minutos o almacenamiento libres para el periodo de facturación actual, {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} seguirán disponibles hasta que se alcance el límite de uso incluído. -* Para cuentas que han alcanzado el uso incluido para el periodo de facturación actual para {% data variables.product.prodname_actions %} o {% data variables.product.prodname_registry %}, se inhabilitará tanto {% data variables.product.prodname_actions %} como {% data variables.product.prodname_registry %} para prevenir cualquier uso excedente posterior. Si pagas la factura de tu cuenta, debes [contactar a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact) para procesar este pago y restablecer tu uso. diff --git a/translations/es-XL/data/reusables/dotcom_billing/add-payment-method.md b/translations/es-XL/data/reusables/dotcom_billing/add-payment-method.md deleted file mode 100644 index 0b7554fc15..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/add-payment-method.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Información de facturación", haz clic en **Add a payment method (Añadir un método de pago)**. ![Enlace para agregar un método de pago](/assets/images/help/billing/add-payment-method.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/add-seats.md b/translations/es-XL/data/reusables/dotcom_billing/add-seats.md deleted file mode 100644 index 43af59f589..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/add-seats.md +++ /dev/null @@ -1 +0,0 @@ -1. Utiliza el menú desplegable **Edit (Editar)** y haz clic en **Add seats (Añadir asientos)**. ![Menú desplegable de editar](/assets/images/help/billing/add-seats-dropdown.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dotcom_billing/cancel-pending-changes.md b/translations/es-XL/data/reusables/dotcom_billing/cancel-pending-changes.md deleted file mode 100644 index 6997511448..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/cancel-pending-changes.md +++ /dev/null @@ -1 +0,0 @@ -1. Junto al cambio pendiente que deseas cancelar, haz clic en **Cancel (Cancelar)**. ![Cancela el enlace junto a un cambio de suscripción pendiente](/assets/images/help/billing/cancel-pending-changes-link.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/change_plan_duration.md b/translations/es-XL/data/reusables/dotcom_billing/change_plan_duration.md deleted file mode 100644 index 9c980a2fe2..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/change_plan_duration.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Resumen de facturación", haz clic en **Change to yearly billing (Cambiar a facturación anual)** o **Change to monthly billing (Cambiar a facturación mensual)**. ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/billing/change-plan-duration-link.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md b/translations/es-XL/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md deleted file mode 100644 index e9072f4e4d..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Resumen de actualización", elige si quieres pagar mensualmente o anualmente. ![Botones de selección con opción de facturación mensual o anual](/assets/images/help/billing/choose-monthly-or-yearly-billing.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/choose_org_plan.md b/translations/es-XL/data/reusables/dotcom_billing/choose_org_plan.md deleted file mode 100644 index 95cc2a4ece..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/choose_org_plan.md +++ /dev/null @@ -1 +0,0 @@ -1. Si estás actualizando desde {% data variables.product.prodname_free_team %}, dentro de "Actualizando a", selecciona un producto. ![Botón Upgrade (Bajar de categoría)](/assets/images/help/billing/upgrade-to-product.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/confirm-add-seats.md b/translations/es-XL/data/reusables/dotcom_billing/confirm-add-seats.md deleted file mode 100644 index 504f927ba3..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/confirm-add-seats.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Agregar plazas**. ![Botón de agregar plazas](/assets/images/help/billing/add-seats-button.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md b/translations/es-XL/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md deleted file mode 100644 index 0ea1e78e81..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md +++ /dev/null @@ -1 +0,0 @@ -1. Para confirmar que deseas cancelar tus cambios de suscripción pendientes, haz clic en **OK (Aceptar)**. diff --git a/translations/es-XL/data/reusables/dotcom_billing/confirm_cancel_org_plan.md b/translations/es-XL/data/reusables/dotcom_billing/confirm_cancel_org_plan.md deleted file mode 100644 index f2505d50d9..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/confirm_cancel_org_plan.md +++ /dev/null @@ -1 +0,0 @@ -7. Lee la información acerca de las características a las que tu organización ya no tendrá acceso en tu próxima fecha de facturación y luego haz clic en **Comprendo. Bajar de categoría mi organización**. ![Botón Bajar de categoría](/assets/images/help/billing/downgrade-confirm-button.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/confirm_duration_change.md b/translations/es-XL/data/reusables/dotcom_billing/confirm_duration_change.md deleted file mode 100644 index db2f76a22f..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/confirm_duration_change.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa los detalles de tu nuevo plan de pago y luego haz clic en **Change plan duration (Cambiar duración del plan)**. diff --git a/translations/es-XL/data/reusables/dotcom_billing/downgrade-org-to-free.md b/translations/es-XL/data/reusables/dotcom_billing/downgrade-org-to-free.md deleted file mode 100644 index 49bc75122c..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/downgrade-org-to-free.md +++ /dev/null @@ -1 +0,0 @@ -1. Utiliza el menú desplegable de **Editar** y da clic en **Bajar de categoría a {% data variables.product.prodname_free_team %}**. diff --git a/translations/es-XL/data/reusables/dotcom_billing/download_receipt.md b/translations/es-XL/data/reusables/dotcom_billing/download_receipt.md deleted file mode 100644 index 02b716c3f1..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/download_receipt.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Historial de pagos", revisa tus pagos anteriores. Para descargar un recibo de un pago específico, haz clic en {% octicon "download" aria-label="The download icon" %}. ![Botón de recibo de descarga](/assets/images/help/settings/settings-download-receipt.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/enter-payment-info.md b/translations/es-XL/data/reusables/dotcom_billing/enter-payment-info.md deleted file mode 100644 index 1d8551ce75..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/enter-payment-info.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de "Información de facturación", elige pagar con una tarjeta de crédito o con PayPal. ![Cambiar métodos de pago de facturación](/assets/images/help/billing/billing_switch_payments.png) -1. Completa el formulario de información de pago. Posteriormente, da clic en **Emitir**. diff --git a/translations/es-XL/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md b/translations/es-XL/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md deleted file mode 100644 index d37a9e601b..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Visita la página [Redeem coupon (Canjear cupón)](https://github.com/redeem). -2. En el cuadro Enter coupon code (Ingresar el código de cupón), escribe tu código de cupón y haz clic en **Redeem (Canjear)**. ![Cuadro para Canjear cupón](/assets/images/help/settings/redeem-coupon-box.png) -3. Si no has iniciado sesión, puedes iniciar sesión en esta página, o crear una nueva cuenta para utilizar tu cupón. diff --git a/translations/es-XL/data/reusables/dotcom_billing/extra_info_receipt.md b/translations/es-XL/data/reusables/dotcom_billing/extra_info_receipt.md deleted file mode 100644 index 0f835ce8b8..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/extra_info_receipt.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Dentro de "Información de pago", en "Información adicional", haz clic en **Add information (Agregar información)**. ![Botón de información adicional de facturación](/assets/images/help/billing/settings_billing_add_billing_extra.png) -1. Escribe la información adicional que deseas en tu recibo y haz clic en **Save contact information (Guardar información de contacto)**. ![Campo de información de contacto](/assets/images/help/settings/Billing-extra-info-field.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/finish_upgrade.md b/translations/es-XL/data/reusables/dotcom_billing/finish_upgrade.md deleted file mode 100644 index 43929c7ea6..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/finish_upgrade.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa la información acerca del gasto y de tu fecha de facturación y luego haz clic en **Upgrade my account (Actualizar mi cuenta)** o **Upgrade my organization's account (Actualizar la cuenta de mi organización)**. diff --git a/translations/es-XL/data/reusables/dotcom_billing/lfs-add-data.md b/translations/es-XL/data/reusables/dotcom_billing/lfs-add-data.md deleted file mode 100644 index 36bd3d1e36..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/lfs-add-data.md +++ /dev/null @@ -1 +0,0 @@ -1. Junto a "Datos de {% data variables.large_files.product_name_short %}", haz clic en **Add more data (Añadir más datos)** o utiliza el menú desplegable de edición y haz clic en **Add more data packs (Añadir más paquetes de datos)**. ![Botón Agregar más datos](/assets/images/help/billing/data-pack-purchase-more.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/lfs-data.md b/translations/es-XL/data/reusables/dotcom_billing/lfs-data.md deleted file mode 100644 index 0d2af71e85..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/lfs-data.md +++ /dev/null @@ -1 +0,0 @@ -1. Ver detalles de tu ancho de banda y el uso de almacenamiento dentro de "Datos de {% data variables.large_files.product_name_short %}". ![Detalles del uso de datos de Git LFS](/assets/images/help/billing/lfs-data.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/lfs-remove-data.md b/translations/es-XL/data/reusables/dotcom_billing/lfs-remove-data.md deleted file mode 100644 index 9e196adc85..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/lfs-remove-data.md +++ /dev/null @@ -1 +0,0 @@ -1. Junto a "Datos de {% data variables.large_files.product_name_short %}", usa el menú desplegable de **Edit (Editar)** y haz clic en **Remove data packs (Eliminar paquetes de datos)**. ![Bajar de categoría tu plan de datos de Git LFS](/assets/images/help/large_files/downgrade_lfs_data_packs.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/monthly-spending-limit.md b/translations/es-XL/data/reusables/dotcom_billing/monthly-spending-limit.md deleted file mode 100644 index 0fa26818b9..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/monthly-spending-limit.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "límite mensual de gastos", elige limitar los gastos o permitir los gastos ilimitados. ![Botones radiales para limitar los gastos o permitir gastos ilimitados](/assets/images/help/billing/limit-or-unlimited.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/next_billing_date.md b/translations/es-XL/data/reusables/dotcom_billing/next_billing_date.md deleted file mode 100644 index 1b1dd5a7e9..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/next_billing_date.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Resumen de facturación", revisa cuándo vence tu próximo pago. ![Próxima fecha de facturación](/assets/images/help/billing/settings_billing_next_payment.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/number-of-seats.md b/translations/es-XL/data/reusables/dotcom_billing/number-of-seats.md deleted file mode 100644 index cc819a637a..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/number-of-seats.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Agregar asientos", escribe el número de asientos que deseas añadir. ![Entrada para agregar plazas](/assets/images/help/billing/add-seats-amount.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dotcom_billing/org-billing-perms.md b/translations/es-XL/data/reusables/dotcom_billing/org-billing-perms.md deleted file mode 100644 index db0538bf57..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/org-billing-perms.md +++ /dev/null @@ -1 +0,0 @@ -Únicamente los miembros de la organización que posean los roles de [*propietario*](/articles/permission-levels-for-an-organization) o [*gerente de facturación*](/articles/adding-a-billing-manager-to-your-organization) pueden acceder a los parámetros de facturación de tu organización o modificarlos. diff --git a/translations/es-XL/data/reusables/dotcom_billing/owned_by_business.md b/translations/es-XL/data/reusables/dotcom_billing/owned_by_business.md deleted file mode 100644 index 6aae041121..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/owned_by_business.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Opcionalmente, si tu organización pertenece a un negocio o institución, selecciona **Esta cuenta pertenece a un negocio**. ![Casilla para organizaciones que pertenecen a un negocio](/assets/images/help/organizations/organization-belongs-to.png) -2. Si tu organización pertenece a una institución o negocio, teclea el nombre de ésta. ![Campo Nombre de empresa o institución](/assets/images/help/organizations/name-of-business.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/packages-data.md b/translations/es-XL/data/reusables/dotcom_billing/packages-data.md deleted file mode 100644 index c65ed966b4..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/packages-data.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "{% data variables.product.prodname_registry %}", visualiza los detalles de tu uso de transferencia de datos. ![Detalles de uso de transferencia de datos](/assets/images/help/billing/packages-data.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/payment-methods.md b/translations/es-XL/data/reusables/dotcom_billing/payment-methods.md deleted file mode 100644 index ff8a72fa59..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/payment-methods.md +++ /dev/null @@ -1 +0,0 @@ -Puedes pagar {% data variables.product.product_name %} con tarjeta de crédito o mediante una cuenta PayPal. diff --git a/translations/es-XL/data/reusables/dotcom_billing/redeem_coupon.md b/translations/es-XL/data/reusables/dotcom_billing/redeem_coupon.md deleted file mode 100644 index e04f735473..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/redeem_coupon.md +++ /dev/null @@ -1 +0,0 @@ -5. Dentro de "Tu nuevo plan", revisa la información acerca de tu plan y tu descuento, y luego haz clic en **Redeem (Canjear)**. diff --git a/translations/es-XL/data/reusables/dotcom_billing/remove-payment-method.md b/translations/es-XL/data/reusables/dotcom_billing/remove-payment-method.md deleted file mode 100644 index c2df9ab04d..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/remove-payment-method.md +++ /dev/null @@ -1 +0,0 @@ -3. En la sección "Método de pago", dentro de tu método de pago, haz clic en **Remove (Eliminar)**. ![Botón para cambiar el plan del resumen de facturación](/assets/images/help/settings/remove_billing_info.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/remove_payment_info.md b/translations/es-XL/data/reusables/dotcom_billing/remove_payment_info.md deleted file mode 100644 index a191dbf6f4..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/remove_payment_info.md +++ /dev/null @@ -1 +0,0 @@ -1. Confirma el cambio haciendo clic en **Remove credit card (Eliminar tarjeta de crédito)** o **Remove PayPal account (Eliminar cuenta de PayPal)**. diff --git a/translations/es-XL/data/reusables/dotcom_billing/review-pending-changes.md b/translations/es-XL/data/reusables/dotcom_billing/review-pending-changes.md deleted file mode 100644 index 44edfaec51..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/review-pending-changes.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Suscripciones", revisa tus cambios pendientes. ![Sección de suscripciones de la configuración de facturación listando cualquier cambio pendiente de suscripción](/assets/images/help/billing/review-pending-subscription-changes.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/same-payment-method.md b/translations/es-XL/data/reusables/dotcom_billing/same-payment-method.md deleted file mode 100644 index c3b0875a6e..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/same-payment-method.md +++ /dev/null @@ -1 +0,0 @@ -Cuando actualizas tu método de pago para la suscripción {% data variables.product.prodname_dotcom %} de tu cuenta, tu nuevo método de pago se agrega automáticamente a tus otras suscripciones de productos pagos. diff --git a/translations/es-XL/data/reusables/dotcom_billing/show-plan-details.md b/translations/es-XL/data/reusables/dotcom_billing/show-plan-details.md deleted file mode 100644 index 1c0f2221e5..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/show-plan-details.md +++ /dev/null @@ -1 +0,0 @@ -1. De forma opcional, para ver los detalles de tu plan, haz clic en **Show details (Mostrar detalles)**. diff --git a/translations/es-XL/data/reusables/dotcom_billing/switch-legacy-billing.md b/translations/es-XL/data/reusables/dotcom_billing/switch-legacy-billing.md deleted file mode 100644 index ab639c5d51..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/switch-legacy-billing.md +++ /dev/null @@ -1 +0,0 @@ -Si tu organización está utilizando un plan de facturación por repositorio heredado, puedes cambiar a precio por usuario en cualquier momento. No podrás volver a cambiar al precio por repositorio una vez que hayas subido de categoría a precio por usuario. diff --git a/translations/es-XL/data/reusables/dotcom_billing/update-spending-limit.md b/translations/es-XL/data/reusables/dotcom_billing/update-spending-limit.md deleted file mode 100644 index cf00d83dcd..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/update-spending-limit.md +++ /dev/null @@ -1 +0,0 @@ -1. Si eliges limitar los gastos, debajo de "Limitar gastos", teclea un límite y posteriormente da clic en **Actualizar límite**. ![Campo para teclear el límite de gastos y botón de actualizar límite](/assets/images/help/billing/update-limit.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/update_payment_method.md b/translations/es-XL/data/reusables/dotcom_billing/update_payment_method.md deleted file mode 100644 index 17e5ad9cde..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/update_payment_method.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Información de facturación", haz clic en **Update payment method (Actualizar método de pago)**. ![Botón para actualizar método de pago](/assets/images/help/billing/update_payment_method.png) diff --git a/translations/es-XL/data/reusables/dotcom_billing/upgrade_org.md b/translations/es-XL/data/reusables/dotcom_billing/upgrade_org.md deleted file mode 100644 index 4ce919af96..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/upgrade_org.md +++ /dev/null @@ -1 +0,0 @@ -1. Si estás mejorando tu producto desde {% data variables.product.prodname_free_team %}, da clic en **Opciones de mejora**. Si estás mejorando tu producto desde {% data variables.product.prodname_team %}, utiliza el menú desplegable de **Editar** y da clic en **Mejorar**. ![Botón de mejorar opciones](/assets/images/help/billing/choose-monthly-or-yearly-billing.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/dotcom_billing/view-all-subscriptions.md b/translations/es-XL/data/reusables/dotcom_billing/view-all-subscriptions.md deleted file mode 100644 index c48a99ed6a..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/view-all-subscriptions.md +++ /dev/null @@ -1 +0,0 @@ -Para ver todas las suscripciones para tu cuenta de {% data variables.product.product_name %}, consulta [Ver tus suscripciones y la fecha de facturación](/articles/viewing-your-subscriptions-and-billing-date)". diff --git a/translations/es-XL/data/reusables/dotcom_billing/view-payment-history.md b/translations/es-XL/data/reusables/dotcom_billing/view-payment-history.md deleted file mode 100644 index 9ae5e5b66e..0000000000 --- a/translations/es-XL/data/reusables/dotcom_billing/view-payment-history.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Información de facturación", haz clic en **View payment method (Ver método de pago)**. ![Ver enlace de historial de pagos](/assets/images/help/billing/view-payment-history-link.png) diff --git a/translations/es-XL/data/reusables/education/about-github-education-link.md b/translations/es-XL/data/reusables/education/about-github-education-link.md deleted file mode 100644 index 4a4ee65540..0000000000 --- a/translations/es-XL/data/reusables/education/about-github-education-link.md +++ /dev/null @@ -1 +0,0 @@ -Antes de solicitar un descuento individual, comprueba si tu comunidad de aprendizaje ya está asociada con nosotros como escuela de {% data variables.product.prodname_education %}. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_education %}](https://education.github.com/partners/schools)". diff --git a/translations/es-XL/data/reusables/education/apply-for-team.md b/translations/es-XL/data/reusables/education/apply-for-team.md deleted file mode 100644 index 0323b64ca4..0000000000 --- a/translations/es-XL/data/reusables/education/apply-for-team.md +++ /dev/null @@ -1 +0,0 @@ -- Solicita gratis [{% data variables.product.prodname_team %}](/articles/github-s-products), que permite tener ilimitados usuarios y repositorios privados. Para obtener más información, consulta "[Postularse para un descuento para educador o investigador](/articles/applying-for-an-educator-or-researcher-discount)". diff --git a/translations/es-XL/data/reusables/education/benefits-page.md b/translations/es-XL/data/reusables/education/benefits-page.md deleted file mode 100644 index 71d47da819..0000000000 --- a/translations/es-XL/data/reusables/education/benefits-page.md +++ /dev/null @@ -1 +0,0 @@ -1. Ve a [{% data variables.product.prodname_education %}](https://education.github.com) y, en la parte superior derecha, haz clic en **Get benefits (Obtener beneficios)**. diff --git a/translations/es-XL/data/reusables/education/pdf-support.md b/translations/es-XL/data/reusables/education/pdf-support.md deleted file mode 100644 index 1026c09d05..0000000000 --- a/translations/es-XL/data/reusables/education/pdf-support.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** no se admiten archivos PDF y no puedes cargarlos como prueba de tu afiliación. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/education/plan-to-use-github.md b/translations/es-XL/data/reusables/education/plan-to-use-github.md deleted file mode 100644 index 6095f7d45b..0000000000 --- a/translations/es-XL/data/reusables/education/plan-to-use-github.md +++ /dev/null @@ -1 +0,0 @@ -1. Describe cómo planeas utilizar {% data variables.product.prodname_dotcom %}. ![Campo de descripción sobre cómo planeas utilizar {% data variables.product.prodname_dotcom %}](/assets/images/help/education/purpose-for-github-education.png) diff --git a/translations/es-XL/data/reusables/education/school-name.md b/translations/es-XL/data/reusables/education/school-name.md deleted file mode 100644 index 61df2edc9c..0000000000 --- a/translations/es-XL/data/reusables/education/school-name.md +++ /dev/null @@ -1 +0,0 @@ -5. Ingresa el nombre de tu escuela. ![Campo para el nombre de tu escuela](/assets/images/help/education/enter-school-name.png) diff --git a/translations/es-XL/data/reusables/education/select-email-address.md b/translations/es-XL/data/reusables/education/select-email-address.md deleted file mode 100644 index b71c9e0c88..0000000000 --- a/translations/es-XL/data/reusables/education/select-email-address.md +++ /dev/null @@ -1,7 +0,0 @@ -1. Selecciona o añade la dirección de correo electrónico que utilizas para la escuela. ![Selecciona la dirección de correo](/assets/images/help/education/select-email-address.png) - - {% tip %} - - **Sugerencia**: seleccionar una dirección de correo electrónico emitida por la escuela, si tienes una, te da mayor probabilidad de una revisión rápida. - - {% endtip %} diff --git a/translations/es-XL/data/reusables/education/submit-application.md b/translations/es-XL/data/reusables/education/submit-application.md deleted file mode 100644 index d44fcabb2d..0000000000 --- a/translations/es-XL/data/reusables/education/submit-application.md +++ /dev/null @@ -1,3 +0,0 @@ -8. Verifica los detalles de tu aplicación, luego haz clic en **Submit your information (Enviar tu información)**. ![Botón para enviar tu información](/assets/images/help/education/submit-your-information-button.png) - - Si tu solicitud es aprobada, recibirás un correo electrónico de confirmación. Las solicitudes generalmente se procesan en pocos días, pero puede llevar más tiempo durante las horas pico, así como durante el inicio de un nuevo semestre. diff --git a/translations/es-XL/data/reusables/education/upgrade-organization.md b/translations/es-XL/data/reusables/education/upgrade-organization.md deleted file mode 100644 index 5729f10ee3..0000000000 --- a/translations/es-XL/data/reusables/education/upgrade-organization.md +++ /dev/null @@ -1 +0,0 @@ -1. Junto a la organización que quieras mejorar, da clic en **Mejorar**. ![Botón Upgrade (Bajar de categoría)](/assets/images/help/education/upgrade-org-button.png) diff --git a/translations/es-XL/data/reusables/education/upgrade-page.md b/translations/es-XL/data/reusables/education/upgrade-page.md deleted file mode 100644 index bd8579e8d8..0000000000 --- a/translations/es-XL/data/reusables/education/upgrade-page.md +++ /dev/null @@ -1 +0,0 @@ -1. Diríjete a "Mejorar tu organización" en la página de [Mejoras de Organización](https://education.github.com/toolbox/offers/github-org-upgrades). diff --git a/translations/es-XL/data/reusables/education/upload-different-image.md b/translations/es-XL/data/reusables/education/upload-different-image.md deleted file mode 100644 index 87889bc4a8..0000000000 --- a/translations/es-XL/data/reusables/education/upload-different-image.md +++ /dev/null @@ -1 +0,0 @@ -Al volver a solicitar, carga una imagen diferente a la que incluiste en tu primera solicitud. Asegúrate de que sea claramente visible al menos una fecha que demuestre tu situación académica actual. diff --git a/translations/es-XL/data/reusables/education/upload-proof-reapply.md b/translations/es-XL/data/reusables/education/upload-proof-reapply.md deleted file mode 100644 index 8d874ed068..0000000000 --- a/translations/es-XL/data/reusables/education/upload-proof-reapply.md +++ /dev/null @@ -1 +0,0 @@ -Cuando presentes nuevamente una solicitud, carga una imagen de tu número de identificación dentro de la escuela, tu certificado analítico o cualquier otro documento que sirva como evidencia de tu situación académica, en el cual se pueda visualizar con claridad al menos una fecha. diff --git a/translations/es-XL/data/reusables/education/upload-proof-status.md b/translations/es-XL/data/reusables/education/upload-proof-status.md deleted file mode 100644 index 98674a6dbd..0000000000 --- a/translations/es-XL/data/reusables/education/upload-proof-status.md +++ /dev/null @@ -1,10 +0,0 @@ -1. Si se solicita, carga la prueba de tu situación académica. - - Haz clic en **Use your camera to take a picture (Utiliza tu cámara para sacar una foto)**. ![Botón para utilizar tu cámara para sacar una foto](/assets/images/help/education/upload-proof-status.png) - - Como alternativa, para cambiar la cámara que deseas utilizar, usa el menú desplegable de la cámara. ![Menú desplegable de la cámara](/assets/images/help/education/camera-drop-down.png) - - Coloca tu ID académico válido u otra prueba de tu situación académica actual en el cuadro, después haz clic en **Take a picture (Sacar una foto)**. ![Botón para sacar una foto](/assets/images/help/education/take-photo-button.png) - - Si no puedes sacar una foto de la prueba de tu situación académica, para cargar una imagen desde tu computadora en su lugar, haz clic en **Upload image (Cargar una imagen)**. ![Enlace para subir imagen](/assets/images/help/education/upload-image-link.png) - {% note %} - - **Nota:** no se admiten archivos PDF y no puedes cargarlos como prueba de tu situación académica. - - {% endnote %} diff --git a/translations/es-XL/data/reusables/enterprise-accounts/access-enterprise.md b/translations/es-XL/data/reusables/enterprise-accounts/access-enterprise.md deleted file mode 100644 index f789173563..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/access-enterprise.md +++ /dev/null @@ -1 +0,0 @@ -1. Visita la cuenta de tu empresa en `https://github.com/enterprises/ENTERPRISE-NAME`, reemplazando `ENTERPRISE-NAME` por el nombre de la cuenta de tu empresa. diff --git a/translations/es-XL/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md b/translations/es-XL/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md deleted file mode 100644 index 91170d7be7..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, bajo "Uso mensual de Actions y Packages de {% data variables.product.prodname_dotcom %}", da clic en **Obtener reporte de uso** para enviar un reporte en formato CSV por correo electrónico a la dirección principal configurada sobre {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} para cada una de las organizaciones que pertenecen a tu cuenta empresarial. ![Descargar reporte en CSV](/assets/images/help/billing/actions-packages-report-download-enterprise.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/actions-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/actions-tab.md deleted file mode 100644 index 7ef49f8f60..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/actions-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "{% octicon "law" aria-label="The law icon" %} Políticas", haz clic en **Acciones**. diff --git a/translations/es-XL/data/reusables/enterprise-accounts/admin-managing-licenses.md b/translations/es-XL/data/reusables/enterprise-accounts/admin-managing-licenses.md deleted file mode 100644 index bbc6191cd2..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/admin-managing-licenses.md +++ /dev/null @@ -1 +0,0 @@ -Los administradores de {% data variables.product.prodname_enterprise %} pueden utilizar una cuenta empresarial para ver y administrar las licencias de usuario en su instancia de {% data variables.product.prodname_ghe_server %}. Para comenzar con una cuenta empresarial, contacta a {% data variables.contact.contact_enterprise_sales %}, y consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/admin/installation/managing-your-github-enterprise-license)". diff --git a/translations/es-XL/data/reusables/enterprise-accounts/administrators-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/administrators-tab.md deleted file mode 100644 index 2a8a0e197e..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/administrators-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de "Personas {% octicon "person" aria-label="The People icon" %}", haz clic en **Administrators (Administradores)**. ![Pestaña de administradores](/assets/images/help/business-accounts/business-accounts-admin-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/audit-log-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/audit-log-tab.md deleted file mode 100644 index b120c9c738..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/audit-log-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Dentro de " Parámetros de {% octicon "gear" aria-label="The Settings gear" %} ", haz clic en **Audit log (Registro de auditoría)**. ![Pestaña de registro de auditoría en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/enterprise-account-settings-audit-log-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/billing-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/billing-tab.md deleted file mode 100644 index 5028402cde..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/billing-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Billing (Facturación)**. ![Pestaña de facturación en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/settings-billing-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/enterprise-accounts-billing.md b/translations/es-XL/data/reusables/enterprise-accounts/enterprise-accounts-billing.md deleted file mode 100644 index 016ae045e0..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/enterprise-accounts-billing.md +++ /dev/null @@ -1 +0,0 @@ -Las cuentas empresariales están actualmente disponibles para los clientes de {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %} que paguen por factura. La facturación para todas las organizaciones e instancias de {% data variables.product.prodname_ghe_server %} conectadas a tu cuenta empresarial se agregará en una sola factura. Para obtener más información acerca de administrar tu suscripción de {% data variables.product.prodname_ghe_cloud %}, consulta la sección "[Visualizar la suscripción y el uso de tu cuenta empresarial](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)". Para obtener más información acerca de la administración de tu configuración de facturación para {% data variables.product.prodname_ghe_server %}, consulta la sección "[Administrar la facturación para {% data variables.product.prodname_enterprise %}](/enterprise/admin/installation/managing-billing-for-github-enterprise)". diff --git a/translations/es-XL/data/reusables/enterprise-accounts/enterprise-administrators.md b/translations/es-XL/data/reusables/enterprise-accounts/enterprise-administrators.md deleted file mode 100644 index 8905ed26f2..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/enterprise-administrators.md +++ /dev/null @@ -1 +0,0 @@ -Actualmente, hay dos roles administrativos disponibles en las cuentas de empresa: los propietarios de las empresas, que pueden acceder y administrar todos los ajustes a través de la cuenta y los administradores de facturación, que sólo pueden acceder y administrar los parámetros de facturación de la cuenta de empresa. Los propietarios de las empresas también pueden ver a todos los miembros y colaboradores externos de cada organización que sea propiedad de la cuenta de empresa. diff --git a/translations/es-XL/data/reusables/enterprise-accounts/enterprise-licensing-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/enterprise-licensing-tab.md deleted file mode 100644 index 7aa2fd8159..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/enterprise-licensing-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de licencia en la barra lateral de configuración de cuenta empresarial](/assets/images/enterprise/business-accounts/enterprise-licensing-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/github-connect-tab.md deleted file mode 100644 index 210b139862..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/github-connect-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_connect %}**. ![Pestaña GitHub Connect en la barra lateral de parámetros de la cuenta de empresa](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/hooks-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/hooks-tab.md deleted file mode 100644 index 66d7101134..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/hooks-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "{% octicon "gear" aria-label="The Settings gear" %} Configuraciones", haz clic en **Hooks** (Ganchos). ![Pestaña Hooks (Ganchos) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/settings-hooks-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/license-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/license-tab.md deleted file mode 100644 index 061bb90138..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/license-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **License** (Licencia). ![Pestaña de licencia en la barra lateral de configuración de enterprise server](/assets/images/enterprise/business-accounts/license-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/messages-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/messages-tab.md deleted file mode 100644 index 7fbfd0ffc3..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/messages-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "{% octicon "gear" aria-label="The Settings gear" %} Configuraciones", haz clic en **Messages** (Mensajes). ![Pestaña Messages (Mensajes) en la barra lateral de parámetros de la empresa](/assets/images/enterprise/business-accounts/settings-messages-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/options-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/options-tab.md deleted file mode 100644 index ae04336d18..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/options-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Under {% if currentVersion ver_gt "enterprise-server@2.21" %} {% octicon "law" aria-label="The law icon" %} **Policies**{% else %}"{% octicon "gear" aria-label="The Settings gear" %} Settings"{% endif %}, click **Options**. ![Pestaña Options (Opciones) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/enterprise/business-accounts/settings-options-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/people-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/people-tab.md deleted file mode 100644 index b62267b863..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/people-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de Cuenta de empresa, haz clic en {% octicon "person" aria-label="The People icon" %} **Personas**. ![Pestaña People (Personas) en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/business-account-people-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/policies-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/policies-tab.md deleted file mode 100644 index 3c6ec397b1..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/policies-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de la cuenta de empresa, haz clic en {% octicon "law" aria-label="The law icon" %} **Policies** (Políticas). ![Pestaña Policies (Políticas) en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/enterprise-account-policies-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/projects-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/projects-tab.md deleted file mode 100644 index 3c93a06737..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/projects-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Projects** (Proyectos). ![Pestaña Projects (Proyectos) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/settings-projects-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/repo-creation-policy.md b/translations/es-XL/data/reusables/enterprise-accounts/repo-creation-policy.md deleted file mode 100644 index a39d234056..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/repo-creation-policy.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Repository creation" (Creación de repositorios), selecciona una política. ![Menú desplegable con opciones de políticas de creación de repositorios](/assets/images/help/business-accounts/repository-creation-policy-drop-down.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/repo-creation-types.md b/translations/es-XL/data/reusables/enterprise-accounts/repo-creation-types.md deleted file mode 100644 index 7b43427310..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/repo-creation-types.md +++ /dev/null @@ -1 +0,0 @@ -1. Si seleccionaste **Members can create repositories** (Los miembros pueden crear repositorios), selecciona uno o más tipos de repositorios. ![Casillas para tipos de repositorio](/assets/images/help/business-accounts/repository-creation-policy-repo-types.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/repositories-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/repositories-tab.md deleted file mode 100644 index f11f284d9f..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/repositories-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "{% octicon "law" aria-label="The law icon" %} Políticas", haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/policies-repositories-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/repository-deletion-policy.md b/translations/es-XL/data/reusables/enterprise-accounts/repository-deletion-policy.md deleted file mode 100644 index 4be845cba6..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/repository-deletion-policy.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Repository deletion and transfer" (Eliminación y transferencia de repositorios), usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de eliminación de repositorios](/assets/images/help/business-accounts/repository-deletion-policy-drop-down.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/repository-visibility-policy.md b/translations/es-XL/data/reusables/enterprise-accounts/repository-visibility-policy.md deleted file mode 100644 index 16eee6509a..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/repository-visibility-policy.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Repository visibility change" (Cambio de visibilidad de repositorios), usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de visibilidad de repositorios](/assets/images/help/business-accounts/repository-visibility-policy-drop-down.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/security-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/security-tab.md deleted file mode 100644 index 03d287eacd..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/security-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Security** (Seguridad). ![Pestaña Security (Seguridad) en la barra lateral de parámetros de la cuenta de empresa](/assets/images/help/business-accounts/enterprise-account-settings-security-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/settings-tab.md b/translations/es-XL/data/reusables/enterprise-accounts/settings-tab.md deleted file mode 100644 index 99f7f874d9..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/settings-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de la cuenta de empresa, haz clic en {% octicon "gear" aria-label="The Settings gear" %} **Settings** (Configuraciones). ![Pestaña Settings (Configuraciones) en la barra lateral de la cuenta de empresa](/assets/images/help/business-accounts/enterprise-account-settings-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/translations/es-XL/data/reusables/enterprise-accounts/user-provisioning-release-stage.md deleted file mode 100644 index ca43201b9e..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/user-provisioning-release-stage.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** El aprovisionamiento de usuario para las cuentas empresariales se encuentra actualmente en un beta privado y está sujeto a cambios. Para solicitar acceso al beta, [contacta a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact). - -{% endnote %} diff --git a/translations/es-XL/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md b/translations/es-XL/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md deleted file mode 100644 index e9775f0960..0000000000 --- a/translations/es-XL/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md +++ /dev/null @@ -1 +0,0 @@ -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-XL/data/reusables/enterprise/rate_limit.md b/translations/es-XL/data/reusables/enterprise/rate_limit.md deleted file mode 100644 index 4a9d1a9334..0000000000 --- a/translations/es-XL/data/reusables/enterprise/rate_limit.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} -Toma en cuenta que los límites que se mencionaron anteriormente son los límites de tasa predeterminados para una instancia de {% data variables.product.prodname_ghe_server %}. Contacta a tu administrador de sitio para confirmar si los límites de tasa están habilitados y cómo se configuraron. -{% endif %} diff --git a/translations/es-XL/data/reusables/enterprise/use-a-multiplexer.md b/translations/es-XL/data/reusables/enterprise/use-a-multiplexer.md deleted file mode 100644 index fd66b6bb25..0000000000 --- a/translations/es-XL/data/reusables/enterprise/use-a-multiplexer.md +++ /dev/null @@ -1 +0,0 @@ -This command can take some time to finish, so we recommend running the command in a terminal multiplexer like `screen` or `tmux`. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/apply-configuration.md b/translations/es-XL/data/reusables/enterprise_clustering/apply-configuration.md deleted file mode 100644 index 9bded333a4..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/apply-configuration.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Apply the new configuration. {% data reusables.enterprise.use-a-multiplexer %} - - ghe-cluster-config-apply diff --git a/translations/es-XL/data/reusables/enterprise_clustering/clustering-requires-https.md b/translations/es-XL/data/reusables/enterprise_clustering/clustering-requires-https.md deleted file mode 100644 index 3ba817c920..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/clustering-requires-https.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** La agrupación de {% data variables.product.prodname_ghe_server %} se debe configurar con HTTPS. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/enterprise_clustering/clustering-scalability.md b/translations/es-XL/data/reusables/enterprise_clustering/clustering-scalability.md deleted file mode 100644 index 53195270fd..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/clustering-scalability.md +++ /dev/null @@ -1 +0,0 @@ -La agrupación proporciona una mejor escalabilidad al distribuir la carga en múltiples nodos. Este escalado horizontal puede ser conveniente para algunas organizaciones con decenas de miles de programadores. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/configuration-file-heading.md b/translations/es-XL/data/reusables/enterprise_clustering/configuration-file-heading.md deleted file mode 100644 index 06b1491d91..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/configuration-file-heading.md +++ /dev/null @@ -1 +0,0 @@ -The cluster configuration file lists each node under a [cluster "HOSTNAME"] heading. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/enterprise_clustering/configuration-finished.md b/translations/es-XL/data/reusables/enterprise_clustering/configuration-finished.md deleted file mode 100644 index d20c300d4f..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/configuration-finished.md +++ /dev/null @@ -1,5 +0,0 @@ -1. After the configuration run finishes, {% data variables.product.prodname_ghe_server %} displays the following message. - - ```shell - Finished cluster configuration - ``` diff --git a/translations/es-XL/data/reusables/enterprise_clustering/health_checks.md b/translations/es-XL/data/reusables/enterprise_clustering/health_checks.md deleted file mode 100644 index 858e5cc924..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/health_checks.md +++ /dev/null @@ -1,5 +0,0 @@ -Configura el balanceador de carga para verificar una de estas URL: - - `https://HOSTNAME/status` si HTTPS está habilitado (por defecto) - - `http://HOSTNAME/status` si HTTPS está inhabilitado - -La verificación arrojará el código de estado `200` (OK) si el nodo es correcto y está disponible para responder a las solicitudes del usuario final. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md b/translations/es-XL/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md deleted file mode 100644 index fb58841728..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md +++ /dev/null @@ -1 +0,0 @@ -The order of the key-value pairs doesn't matter. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/load_balancer_dns.md b/translations/es-XL/data/reusables/enterprise_clustering/load_balancer_dns.md deleted file mode 100644 index fd1786f2ba..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/load_balancer_dns.md +++ /dev/null @@ -1 +0,0 @@ -Las búsquedas DNS para el nombre del host de {% data variables.product.prodname_ghe_server %} se deben resolver con el balanceador de carga. Es recomendable que habilites el aislamiento de subdominio. Si el aislamiento de subdominio está habilitado, un registro comodín adicional (`*.HOSTNAME`) también se debería resolver con el balanceador de carga. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/translations/es-XL/data/reusables/enterprise_clustering/load_balancer_intro.md b/translations/es-XL/data/reusables/enterprise_clustering/load_balancer_intro.md deleted file mode 100644 index aab677a046..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/load_balancer_intro.md +++ /dev/null @@ -1 +0,0 @@ -Un diseño de balanceador de carga utiliza un dispositivo de red para dirigir el tráfico de Git y HTTP a los aparatos individuales del {% data variables.product.prodname_ghe_server %}. Puedes utilizar un balanceador de carga para restringir el tráfico directo al aparato con fines de seguridad o para redirigir el tráfico, de ser necesario, sin cambios en los registros DNS. Es altamente recomendable utilizar un balanceador de carga basado en TPC que admita el protocolo PROXY. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/open-configuration-file.md b/translations/es-XL/data/reusables/enterprise_clustering/open-configuration-file.md deleted file mode 100644 index 03cd337e49..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/open-configuration-file.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Open the cluster configuration file at _/data/user/common/cluster.conf_ in a text editor. For example, you can use Vim. - - sudo vim /data/user/common/cluster.conf diff --git a/translations/es-XL/data/reusables/enterprise_clustering/proxy_preference.md b/translations/es-XL/data/reusables/enterprise_clustering/proxy_preference.md deleted file mode 100644 index acfe08cf91..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/proxy_preference.md +++ /dev/null @@ -1 +0,0 @@ -Si tu balanceador de carga lo admite, es altamente recomendable implementar el protocolo PROXY. Cuando no está disponible el soporte de PROXY, también se puede balancear la carga de los puertos HTTP y HTTPS usando el encabezado `X-Forwarded-For`. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/es-XL/data/reusables/enterprise_clustering/proxy_protocol_ports.md deleted file mode 100644 index 9afca0bede..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/proxy_protocol_ports.md +++ /dev/null @@ -1,10 +0,0 @@ -##### Mapeos de puertos de protocolo TCP de PROXY - -| Puerto fuente | Puerto de destino | Descripción del servicio | -|:-------------:|:-----------------:|:---------------------------:| -| 22 | 23 | Git sobre SSH | -| 80 | 81 | HTTP | -| 443 | 444 | HTTPS | -| 8080 | 8081 | Consola de gestión HTTP | -| 8443 | 8444 | Consola de gestión de HTTPS | -| 9418 | 9419 | Git | diff --git a/translations/es-XL/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md b/translations/es-XL/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md deleted file mode 100644 index bf4bff292d..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md +++ /dev/null @@ -1,5 +0,0 @@ -{% danger %} - -**Advertencia de seguridad**: Cuando estén habilitados el soporte de PROXY o el redireccionamiento de HTTP, es muy importante que ningún tráfico externo pueda llegar directamente a los aparatos del {% data variables.product.prodname_ghe_server %}. Si el tráfico externo no se bloquea correctamente, las direcciones IP de origen se pueden falsificar. - -{% enddanger %} diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md deleted file mode 100644 index a483dc23b6..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md +++ /dev/null @@ -1 +0,0 @@ -1. Usando el shell administrativo o DHCP, configura **solo** la dirección IP del nodo de reemplazo. No configures los otros parámetros. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md deleted file mode 100644 index d439ca5f7f..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md +++ /dev/null @@ -1 +0,0 @@ -1. Desde el mismo nodo, ejecuta `ghe-cluster-config-apply`. Esto validará el archivo de configuración, lo copiará en cada nodo de la agrupación y configurará cada nodo según el archivo `cluster.conf` modificado. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md deleted file mode 100644 index 4f45c0b070..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md +++ /dev/null @@ -1 +0,0 @@ -1. Desde el shell administrativo del nodo con el archivo `cluster.conf` modificado, ejecuta `ghe-cluster-config-init `. Esto iniciará el nodo recién agregado en la agrupación. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md deleted file mode 100644 index f9ce5e5c64..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md +++ /dev/null @@ -1,11 +0,0 @@ -1. Para marcar el nodo que falló fuera de línea, en cualquier nodo, modifica el [archivo de configuración de agrupación](/enterprise/{{ currentVersion }}/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file) (`cluster.conf`) en la sección de nodo correspondiente para incluir el texto `offline = true`. - - Por ejemplo, este archivo `cluster.conf` modificado marcará el nodo `ghe-data-node-3` como fuera de línea: - - - 
    [cluster "ghe-data-node-3"]
- hostname = ghe-data-node-3
- offline = true
- ipv4 = 192.168.0.6
- # ipv6 = fd12:3456:789a:1::6
-
    diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md deleted file mode 100644 index 875b558c0e..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md +++ /dev/null @@ -1,14 +0,0 @@ -1. Para agregar el nodo de reemplazo proporcionado recientemente, en cualquier nodo, modifica el archivo `cluster.conf` para eliminar el nodo fallido y agregar el nodo de reemplazo. Por ejemplo, este archivo `cluster.conf` modificado reemplaza el `ghe-data-node-3` con el nodo proporcionado recientemente, `ghe-replacement-data-node-3`: 
    -  [cluster "ghe-replacement-data-node-3"]
-    hostname = ghe-replacement-data-node-3
-    ipv4 = 192.168.0.7
-    # ipv6 = fd12:3456:789a:1::7
-    git-server = true
-    pages-server = true
-    mysql-server = true
-    elasticsearch-server = true
-    redis-server = true
-    memcache-server = true
-    metrics-server = true
-    storage-server = true
-
    diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md deleted file mode 100644 index 1e74882cf6..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md +++ /dev/null @@ -1 +0,0 @@ -1. Si vas a tomar un nodo fuera de línea que tiene `git-server = true` establecido en cluster.conf, evacua el nodo. Para obtener más información, consulta "[Evacuar un nodo de la agrupación](/enterprise/{{ currentVersion }}/admin/clustering/evacuating-a-cluster-node)". diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md deleted file mode 100644 index e1eb2f90eb..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md +++ /dev/null @@ -1 +0,0 @@ -1. [Aprovisiona e instala el {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance) con un nombre de host único en el nodo de reemplazo. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md deleted file mode 100644 index 602f5f1ce3..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md +++ /dev/null @@ -1,6 +0,0 @@ -1. Si vas a reemplazar el nodo principal de MySQL o el nodo principal de Redis, en `cluster.conf`, cambia el valor de `mysql-master` o `redis-master` por el nombre del nodo de reemplazo. - - Por ejemplo, este archivo `cluster.conf` modificado especifica un nodo de la agrupación recién aprovisionado, `ghe-replacement-data-node-1`, como nodo principal de MySQL y Redis: 
    -  mysql-master = ghe-replacement-data-node-1
-  redis-master = ghe-replacement-data-node-1
-
    diff --git a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md b/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md deleted file mode 100644 index 72b3027bf9..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md +++ /dev/null @@ -1 +0,0 @@ -1. Desde el shell administrativo del nodo en el que modificaste el archivo `cluster.conf`, ejecuta `ghe-cluster-config-init`. Esto validará el archivo de configuración, lo copiará en cada nodo de la agrupación y marcará el nodo fuera de línea. diff --git a/translations/es-XL/data/reusables/enterprise_clustering/ssh-to-a-node.md b/translations/es-XL/data/reusables/enterprise_clustering/ssh-to-a-node.md deleted file mode 100644 index f5d9b0349d..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/ssh-to-a-node.md +++ /dev/null @@ -1 +0,0 @@ -1. SSH into any node in your cluster. Para obtener más información, consulta "[Acceder al shell administrativo (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)." diff --git a/translations/es-XL/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/es-XL/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md deleted file mode 100644 index 0423edf09b..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md +++ /dev/null @@ -1,10 +0,0 @@ -##### Mapeos de puertos de protocolo TCP para usar sin soporte de PROXY - -| Puerto fuente | Puerto de destino | Descripción del servicio | -|:-------------:|:-----------------:|:---------------------------:| -| 22 | 22 | Git sobre SSH | -| 25 | 25 | SMTP | -| 80 | 80 | HTTP | -| 443 | 443 | HTTPS | -| 8080 | 8080 | Consola de gestión HTTP | -| 8443 | 8443 | Consola de gestión de HTTPS | diff --git a/translations/es-XL/data/reusables/enterprise_clustering/x-forwarded-for.md b/translations/es-XL/data/reusables/enterprise_clustering/x-forwarded-for.md deleted file mode 100644 index aa6a295b9d..0000000000 --- a/translations/es-XL/data/reusables/enterprise_clustering/x-forwarded-for.md +++ /dev/null @@ -1 +0,0 @@ -Usa el protocolo X-Forwarded-For **solo** cuando el protocolo PROXY no esté disponible. El encabezado `X-Forwarded-For` solo funciona con HTTP y HTTPS. La dirección IP informada para las conexiones de Git a través de SSH mostrarán la IP del balanceador de carga. diff --git a/translations/es-XL/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/es-XL/data/reusables/enterprise_deprecation/deprecation_details.md deleted file mode 100644 index 1bf0c8547b..0000000000 --- a/translations/es-XL/data/reusables/enterprise_deprecation/deprecation_details.md +++ /dev/null @@ -1 +0,0 @@ -No se realizarán lanzamientos de patch, ni siquiera para problemas de seguridad críticos. Para obtener un mejor desempeño, más seguridad y nuevas características, actualiza a la última versión de GitHub Enterprise. Para obtener ayuda con la actualización, contacta al soporte de GitHub Enterprise. diff --git a/translations/es-XL/data/reusables/enterprise_deprecation/version_was_deprecated.md b/translations/es-XL/data/reusables/enterprise_deprecation/version_was_deprecated.md deleted file mode 100644 index 132ee85cc9..0000000000 --- a/translations/es-XL/data/reusables/enterprise_deprecation/version_was_deprecated.md +++ /dev/null @@ -1 +0,0 @@ -Esta versión de GitHub Enterprise se discontinuó el diff --git a/translations/es-XL/data/reusables/enterprise_deprecation/version_will_be_deprecated.md b/translations/es-XL/data/reusables/enterprise_deprecation/version_will_be_deprecated.md deleted file mode 100644 index 465b1c3284..0000000000 --- a/translations/es-XL/data/reusables/enterprise_deprecation/version_will_be_deprecated.md +++ /dev/null @@ -1 +0,0 @@ -Esta versión de GitHub Enterprise se discontinuará el diff --git a/translations/es-XL/data/reusables/enterprise_enterprise_support/installing-releases.md b/translations/es-XL/data/reusables/enterprise_enterprise_support/installing-releases.md deleted file mode 100644 index 0488f7ac97..0000000000 --- a/translations/es-XL/data/reusables/enterprise_enterprise_support/installing-releases.md +++ /dev/null @@ -1,3 +0,0 @@ -### Instalar lanzamientos de {% data variables.product.prodname_ghe_server %} - -Para asegurar que el {% data variables.product.product_location_enterprise %} sea estable, debes instalar e implementar lanzamientos de {% data variables.product.prodname_ghe_server %}. Instalar lanzamientos del {% data variables.product.prodname_ghe_server %} garantiza que tengas las últimas características, modificaciones y mejoras así como también cualquier actualización a características, correcciones de código, patch u otras actualizaciones y correcciones generales para el {% data variables.product.prodname_ghe_server %}. diff --git a/translations/es-XL/data/reusables/enterprise_enterprise_support/sign-in-to-support.md b/translations/es-XL/data/reusables/enterprise_enterprise_support/sign-in-to-support.md deleted file mode 100644 index 3c760c35a0..0000000000 --- a/translations/es-XL/data/reusables/enterprise_enterprise_support/sign-in-to-support.md +++ /dev/null @@ -1 +0,0 @@ -1. Visita https://enterprise.github.com/support e inicia sesión en (si se solicita que lo hagas). diff --git a/translations/es-XL/data/reusables/enterprise_enterprise_support/submit-support-ticket-first-section.md b/translations/es-XL/data/reusables/enterprise_enterprise_support/submit-support-ticket-first-section.md deleted file mode 100644 index 2b58e91639..0000000000 --- a/translations/es-XL/data/reusables/enterprise_enterprise_support/submit-support-ticket-first-section.md +++ /dev/null @@ -1,16 +0,0 @@ -1. Debajo de "Tu dirección de correo electrónico", teclea la dirección de correo electrónico asociada con tu cuenta de {% data variables.product.product_name %}. ![Campo Tu dirección de correo electrónico](/assets/images/enterprise/support/support-ticket-email-address-field.png) -1. Debajo de "Asunto", teclea un título descriptivo para tu problema. ![Campo de asuto](/assets/images/enterprise/support/support-ticket-subject-field.png) -1. Debajo de "Descripción", proporciona información adicional que ayudará al equipo de {% data variables.contact.enterprise_support %} para solucionar el problema. La información útil podría incluir: ![Campo Descripción](/assets/images/enterprise/support/support-ticket-description-field.png) - - Pasos para reproducir el incidente - - Cualquier circunstancia especial relacionada con el descubrimiento del problema (por ejemplo, la primera vez que se suscitó, o su materialización después de cierto evento, frecuencia en la que se presenta, impacto al negocio, y urgencia sugerida) - - Redacción exacta de los mensajes de error -1. Desde el menú desplegable de {% data variables.product.prodname_enterprise %} del producto, selecciona {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}. ![Menú desplegable Prioridad](/assets/images/enterprise/support/support-ticket-ghe-product.png) -1. Desde el menú desplegable de "Prioridad" selecciona la urgencia adecuada. Para obtener más información, consulta la sección "[Asignar una prioridad a un ticket de soporte]{% if currentVersion == "free-pro-team@latest" %}(/articles/about-github-premium-support-for-github-enterprise-cloud#assigning-a-priority-to-a-support-ticket){% else %}(/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket){% endif %}." ![Menú desplegable Prioridad](/assets/images/enterprise/support/support-ticket-priority.png) - - Elige **{% data variables.product.support_ticket_priority_urgent %}** para reportar una {% if currentVersion == "free-pro-team@latest" %}falla crítica del sistema{% else %} fallas fatales del sistema, interrupciones que impactan las operaciones críticas del sistema, incidentes de seguridad, y licencias expiradas{% endif %}. - - Elige **{% data variables.product.support_ticket_priority_high %}** para reportar incidentes que impactan las operaciones de negocios, incluyendo {% if currentVersion == "free-pro-team@latest" %} eliminar datos sensibles (confirmaciones, incidentes, solicitudes de extracción, adjuntos cargados) de tus propias restauraciones de cuenta y de organización{% else %}, incidentes de rendimiento del sistema{% endif %}, o para reportar errores críticos. - - Elige **{% data variables.product.support_ticket_priority_normal %}** para {% if currentVersion == "free-pro-team@latest" %}solicitar una recuperación de cuenta o desmarcación de spam, reportar problemas de acceso de usuario{% else %}hacer solicitudes técnicas como cambios de configuración e integraciones de terceros{% endif %}, y reportar errores no críticos. - - Elige **{% data variables.product.support_ticket_priority_low %}** para hacer preguntas generales y emitir solicitudes de características nuevas, compras, capacitación, o revisiones de estado. {% if currentVersion != "free-pro-team@latest" %} -1. Desde el menú desplegable de "Series de {% data variables.product.prodname_enterprise %}", selecciona la versión de {% data variables.product.prodname_ghe_server %} que utilizas. ![{% data variables.product.prodname_enterprise %} Menú desplegable de series](/assets/images/enterprise/support/support-ticket-ghes-series.png) -{% endif %} -1. Desde el menú desplegable de "Región Global", selecciona APAC (Asia Pacífico), EMEA (Europa, Medio Oriente, y África), o América de acuerdo con tu región. ![Menú desplegable Región global](/assets/images/enterprise/support/support-ticket-global-region.png) -1. Da clic en **Agregar archivo**, posteriormente adjunta el archivo de diagnóstico que descargaste para incluir el diagnóstico en tu ticket de soporte. ![Añadir botón de archivo](/assets/images/enterprise/support/support-ticket-add-file.png) diff --git a/translations/es-XL/data/reusables/enterprise_enterprise_support/submit-support-ticket-second-section.md b/translations/es-XL/data/reusables/enterprise_enterprise_support/submit-support-ticket-second-section.md deleted file mode 100644 index c4baf04ef3..0000000000 --- a/translations/es-XL/data/reusables/enterprise_enterprise_support/submit-support-ticket-second-section.md +++ /dev/null @@ -1,4 +0,0 @@ -1. Haz clic en **Submit** (enviar). - -{% if currentVersion != "free-pro-team@latest" %} -Si eliges no incluir diagnósticos con tu ticket de soporte, puedes compartir la información de diagnóstico con el Soporte de {% data variables.product.prodname_enterprise %} después de enviar tu solicitud de soporte. Para obtener más información, consulta "[Proporcionar datos a Soporte de {% data variables.product.prodname_dotcom %}](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support)."{% endif %} diff --git a/translations/es-XL/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md b/translations/es-XL/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md deleted file mode 100644 index 218839c2de..0000000000 --- a/translations/es-XL/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md +++ /dev/null @@ -1 +0,0 @@ -Por lo general, solo harás esto si te has [contactado con el equipo de soporte](https://enterprise.github.com/support), y se te ha solicitado que lo hagas. diff --git a/translations/es-XL/data/reusables/enterprise_enterprise_support/upload-support-bundle.md b/translations/es-XL/data/reusables/enterprise_enterprise_support/upload-support-bundle.md deleted file mode 100644 index 0ad672bbf8..0000000000 --- a/translations/es-XL/data/reusables/enterprise_enterprise_support/upload-support-bundle.md +++ /dev/null @@ -1 +0,0 @@ -1. Visita https://enterprise.github.com/support/bundles/new y carga tu paquete de soporte. diff --git a/translations/es-XL/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md b/translations/es-XL/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md deleted file mode 100644 index cd6497e4e6..0000000000 --- a/translations/es-XL/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Si vas a usar una configuración de Replicación geográfica o una Agrupación de {% data variables.product.prodname_enterprise %}, debes usar el comando `ghe-cluster-support-bundle` para recuperar el paquete de soporte. Para obtener más información, consulta "[Utilidades de la línea de comandos](/enterprise/{{ currentVersion }}/admin/guides/installation/command-line-utilities/#ghe-cluster-support-bundle)". - -{% endnote %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/add-ssh-key-to-primary.md b/translations/es-XL/data/reusables/enterprise_installation/add-ssh-key-to-primary.md deleted file mode 100644 index 3d2d84ebbe..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/add-ssh-key-to-primary.md +++ /dev/null @@ -1 +0,0 @@ -1. Para agregar una llave pública a la lista de llaves autorizadas en el aparato principal, ingresa a `https://PRIMARY-HOSTNAME/setup/settings` y agrega a la lista la llave que copiaste de la réplica. diff --git a/translations/es-XL/data/reusables/enterprise_installation/aws-recommended-instance-types.md b/translations/es-XL/data/reusables/enterprise_installation/aws-recommended-instance-types.md deleted file mode 100644 index 088a69d0bc..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/aws-recommended-instance-types.md +++ /dev/null @@ -1,10 +0,0 @@ -De acuerdo con el número de licencias de usuario con las que cuentes, recomendamos los siguientes tipos de instancia. | -{% if currentVersion != "free-pro-team@latest" %} -| Licencias de usuario | Tipo recomendado | -|:---------------------------------------- | ----------------:| -| Prueba, Demo o 10 usuarios no frecuentes | r4.large | -| 10 - 3000 | r4.xlarge | -| 3000 - 5000 | r4.2xlarge | -| 5000 - 8000 | r4.4xlarge | -| 8000 - 10000+ | r4.8xlarge | -{% endif %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/aws-supported-instance-types.md b/translations/es-XL/data/reusables/enterprise_installation/aws-supported-instance-types.md deleted file mode 100644 index ba66070aeb..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/aws-supported-instance-types.md +++ /dev/null @@ -1,38 +0,0 @@ -{% data variables.product.prodname_ghe_server %} se admite en los siguientes tipos de instancias EC2. Para obtener más información, consulta [la página de AWS de resumen de tipo de instancia EC2 ](http://aws.amazon.com/ec2/instance-types/). - -| Tipo de instancia EC2 | Modelo | -| --------------------- | ---------------------------------- | -| C3 | c3.2xlarge, c3.4xlarge, c3.8xlarge | - -| Tipo de instancia EC2 | Modelo | -| --------------------- | ---------------------------------- | -| C4 | c4.2xlarge, c4.4xlarge, c4.8xlarge | - -| Tipo de instancia EC2 | Modelo | -| --------------------- | -------------------------------------------------------------------- | -| C5 | c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge, c5.18xlarge | - -| Tipo de instancia EC2 | Modelo | -| --------------------- | --------------------- | -| M3 | m3.xlarge, m3.2xlarge | - -| Tipo de instancia EC2 | Modelo | -| --------------------- | ----------------------------------------------------------- | -| M4 | m4.xlarge, m4.2xlarge, m4.4xlarge, m4.10xlarge, m4.16xlarge | - -| Tipo de instancia EC2 | Modelo | -| --------------------- | --------------------------------------------------------------------- | -| M5 | m5.large, m5.xlarge, m5.2xlarge, m5.4xlarge, m5.12xlarge, m5.24xlarge | - -| Tipo de instancia EC2 | Modelo | -| --------------------- | -------------------------------------------------------------------- | -| R4 | r4.large, r4.xlarge, r4.2xlarge, r4.4xlarge, r4.8xlarge, r4.16xlarge | - -| Tipo de instancia EC2 | Modelo | -| --------------------- | --------------------------------------------------------------------- | -| R5 | r5.large, r5.xlarge, r5.2xlarge, r5.4xlarge, r5.12xlarge, r5.24xlarge | - - -| Tipo de instancia EC2 | Modelo | -| --------------------- | ------------------------ | -| X1 | x1.16xlarge, x1.32xlarge | diff --git a/translations/es-XL/data/reusables/enterprise_installation/changing-hostname-not-supported.md b/translations/es-XL/data/reusables/enterprise_installation/changing-hostname-not-supported.md deleted file mode 100644 index 376504605c..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/changing-hostname-not-supported.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Advertencia**: No cambies el nombre de host para {% data variables.product.prodname_ghe_server %} después de la configuración inicial. Cambiar el nombre del host ocasionará un comportamiento inesperado que puede incluir y llegar hasta la interrupción del servicio. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md b/translations/es-XL/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md deleted file mode 100644 index 2df128533c..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md +++ /dev/null @@ -1,7 +0,0 @@ -Cuando bajes de categoría una mejora que ya hayas hecho, deberás utilizar un archivo de paquete de mejora con la extensión *.pkg*. No hay compatibilidad con los archivos de paquete de hotpatch con la extensión *.hpkg*. - -```shell -ghe-upgrade --allow-patch-rollback EARLIER-RELEASE-UPGRADE-PACKAGE.pkg -``` - -A reboot is required after running the command. Bajar de categoría una mejora previa no afecta la partición de datos, ya que las migraciones no se ejecutan en lanzamientos parchados. diff --git a/translations/es-XL/data/reusables/enterprise_installation/configuration-recognized.md b/translations/es-XL/data/reusables/enterprise_installation/configuration-recognized.md deleted file mode 100644 index 559974ab03..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/configuration-recognized.md +++ /dev/null @@ -1,5 +0,0 @@ -1. Una vez que la instancia se haya reiniciado completamente y que puedas acceder a ella, usa el shell administrativo para verificar el reconocimiento de la nueva configuración de recursos: -```shell -$ ssh -p 122 admin@HOSTNAME -$ ghe-system-info -``` diff --git a/translations/es-XL/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md b/translations/es-XL/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md deleted file mode 100644 index bcd59e9997..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md +++ /dev/null @@ -1 +0,0 @@ -1. Copia el nombre DNS público de la máquina virtual y pégalo en un navegador de red. diff --git a/translations/es-XL/data/reusables/enterprise_installation/create-attached-storage-volume.md b/translations/es-XL/data/reusables/enterprise_installation/create-attached-storage-volume.md deleted file mode 100644 index ede4a43925..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/create-attached-storage-volume.md +++ /dev/null @@ -1 +0,0 @@ -1. Crear un nuevo disco virtual para utilizarlo como un volumen adjunto de almacenamiento para los datos de tu instancia, y configurar el tamaño con base en la cantidad de licencias de usuario disponibles. diff --git a/translations/es-XL/data/reusables/enterprise_installation/create-ghe-instance.md b/translations/es-XL/data/reusables/enterprise_installation/create-ghe-instance.md deleted file mode 100644 index 9ba84aec92..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/create-ghe-instance.md +++ /dev/null @@ -1 +0,0 @@ -Para crear la instancia, deberás importar la imagen del {% data variables.product.prodname_ghe_server %} a tu máquina virtual y adjuntar un volumen de almacenamiento adicional para los datos de tu instancia. Para obtener más información, consulta "[Consideraciones relativas al hardware](#hardware-considerations)." diff --git a/translations/es-XL/data/reusables/enterprise_installation/disable-github-pages-warning.md b/translations/es-XL/data/reusables/enterprise_installation/disable-github-pages-warning.md deleted file mode 100644 index 9fcfe29ff9..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/disable-github-pages-warning.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Advertencia:** si se deshabilita el aislamiento del subdominio, recomendamos también deshabilitar {% data variables.product.prodname_pages %} en tu aparato. No habrá manera de aislar el contenido de las {% data variables.product.prodname_pages %} provisto por el usuario del resto de los datos de tu aparato. Para obtener más información, consulta "[Configurar las {% data variables.product.prodname_pages %} en tu aparato](/enterprise/admin/guides/installation/configuring-github-pages-on-your-appliance/)." - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/download-appliance.md b/translations/es-XL/data/reusables/enterprise_installation/download-appliance.md deleted file mode 100644 index 51c91b94b1..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/download-appliance.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Get the latest release of {% data variables.product.prodname_ghe_server %}** (Obtener el último lanzamiento del {% data variables.product.prodname_ghe_server %}). diff --git a/translations/es-XL/data/reusables/enterprise_installation/download-license.md b/translations/es-XL/data/reusables/enterprise_installation/download-license.md deleted file mode 100644 index 3303ad4c16..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/download-license.md +++ /dev/null @@ -1 +0,0 @@ -1. Para descargar tu archivo de licencia, haz clic en **Download license (Descargar licencia)**. diff --git a/translations/es-XL/data/reusables/enterprise_installation/download-note.md b/translations/es-XL/data/reusables/enterprise_installation/download-note.md deleted file mode 100644 index e9c7850b0b..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/download-note.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Si habilitaste las verificaciones de actualizaciones automáticas, no necesitas descargar el paquete de actualizaciones y puedes usar el archivo que se descargó automáticamente. Para obtener más información, consulta "[Enabling automatic update checks](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-automatic-update-checks/)" (Habilitar verificaciones de actualizaciones automáticas). - -{% endnote %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/download-package.md b/translations/es-XL/data/reusables/enterprise_installation/download-package.md deleted file mode 100644 index 3aaead283b..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/download-package.md +++ /dev/null @@ -1,4 +0,0 @@ -1. Descarga el paquete de actualizaciones a {% data variables.product.product_location_enterprise %} con `curl`: -```shell -admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL -``` diff --git a/translations/es-XL/data/reusables/enterprise_installation/enterprise-download-procedural.md b/translations/es-XL/data/reusables/enterprise_installation/enterprise-download-procedural.md deleted file mode 100644 index 3228e7c494..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/enterprise-download-procedural.md +++ /dev/null @@ -1 +0,0 @@ -1. Visita [la {% data variables.product.prodname_ghe_server %} página de descargas](https://enterprise.github.com/download). diff --git a/translations/es-XL/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md b/translations/es-XL/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md deleted file mode 100644 index 2a1353caa2..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md +++ /dev/null @@ -1 +0,0 @@ -Visita la [{% data variables.product.prodname_ghe_server %} Página de lanzamientos](https://enterprise.github.com/releases). Junto a la versión a la que vas a actualizar, haz clic en **Download** (Descargar), luego haz clic en la pestaña **Upgrading** (Actualización). diff --git a/translations/es-XL/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md b/translations/es-XL/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md deleted file mode 100644 index b4f159c7d7..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md +++ /dev/null @@ -1,4 +0,0 @@ -- **Fallo de software**, ya sea debido a una falla en el sistema operativo o a aplicaciones irrecuperables. -- **Fallas del hardware**, incluido el hardware de almacenamiento, la CPU, la RAM, las interfaces de red, etc. -- **Fallas del sistema host de virtualización**, incluidos los eventos no planeados y [de mantenimiento programado en AWS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html). -- **Red cortada lógica o físicamente**, si el error de las aplicación está en una red separada no se ve impactada por la falla. diff --git a/translations/es-XL/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/es-XL/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md deleted file mode 100644 index 7b601a70c1..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md +++ /dev/null @@ -1,55 +0,0 @@ -- [Minimum requirements](#minimum-requirements) -- [Almacenamiento](#storage) -- [CPU and memory](#cpu-and-memory) - -#### Minimum requirements - -We recommend different hardware configurations depending on the number of user licenses for {% data variables.product.product_location_enterprise %}. If you provision more resources than the minimum requirements, your instance will perform and scale better. - -{% data reusables.enterprise_installation.hardware-rec-table %} For more information about adjusting resources for an existing instance, see "[Increasing storage capacity](/enterprise/admin/installation/increasing-storage-capacity)" and "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)." - -{% if currentVersion == "enterprise-server@2.22" %} - -If you enable the beta for {% data variables.product.prodname_actions %} on your instance, we recommend planning for additional capacity. - -- You must configure at least one runner for {% data variables.product.prodname_actions %} workflows. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners)." -- You must configure external blob storage. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." - -The additional CPU and memory resources you need to provision for your instance depend on the number of workflows your users run concurrently, and the overall levels of activity for users, automations, and integrations. - -| Maximum jobs per minute | vCPU | Memoria | -|:----------------------- | ----:| -------:| -| Light testing | 4 | 30.5 GB | -| 25 | 8 | 61 GB | -| 35 | 16 | 122 GB | -| 100 | 32 | 244 GB | - -{% endif %} - -#### Almacenamiento - -We recommend a high-performance SSD with high input/output operations per second (IOPS) and low latency for {% data variables.product.prodname_ghe_server %}. Workloads are I/O intensive. If you use a bare metal hypervisor, we recommend directly attaching the disk or using a disk from a storage area network (SAN). - -Your instance requires a persistent data disk separate from the root disk. Para obtener más información, consulta "[Resumen del sistema](/enterprise/admin/guides/installation/system-overview)". - -{% if currentVersion ver_gt "enterprise-server@2.21" %} - -If you enable the beta of {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %} 2.22, you'll need to configure external blob storage. For more information, see "[Enabling {% data variables.product.prodname_actions %} and configuring storage](/enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage)." - -{% endif %} - -You can resize your instance's root disk by building a new instance or using an existing instance. Para obtener más información, consulta la sección [Incrementar la capacidad de almacenamiento](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity)" - -#### CPU and memory - -{% data variables.product.prodname_ghe_server %} requires more CPU and memory resources depending on levels of activity for users, automations, and integrations. - -{% data reusables.enterprise_installation.increasing-cpus-req %} - -{% warning %} - -**Warning:** We recommend that users configure webhook events to notify external systems of activity on {% data variables.product.prodname_ghe_server %}. Automated checks for changes, or _polling_, will negatively impact the performance and scalability of your instance. For more information, see "[About webhooks](/github/extending-github/about-webhooks)." - -{% endwarning %} - -You can increase your instance's CPU or memory resources. Para obtener más información, consulta "[Aumentar los recursos de memoria o la CPU](/enterprise/admin/installation/increasing-cpu-or-memory-resources). diff --git a/translations/es-XL/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/es-XL/data/reusables/enterprise_installation/hardware-rec-table.md deleted file mode 100644 index e3c92e2281..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/hardware-rec-table.md +++ /dev/null @@ -1,16 +0,0 @@ -{% if currentVersion == "enterprise-server@2.22" %} - -Minimum requirements for an instance with beta features enabled are **bold** in the following table. For more information, see "[Beta features in {% data variables.product.prodname_ghe_server %} 2.22](#beta-features-in-github-enterprise-server-222)." |{% endif %} -| Licencias de usuario | vCPU | Memoria | Almacenamiento conectado | Almacenamiento raíz | -|:---------------------------------------- | ------------------------------------------------------------------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------:| -------------------:| -| Prueba, Demo o 10 usuarios no frecuentes | 2{% if currentVersion == "enterprise-server@2.22" %}
    or [**4**](#beta-features-in-github-enterprise-server-222){% endif %} | 16 GB{% if currentVersion == "enterprise-server@2.22" %}
    or [**32 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 100 GB{% if currentVersion == "enterprise-server@2.22" %}
    or [**150 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | -| 10-3000 | 4{% if currentVersion == "enterprise-server@2.22" %}
    or [**8**](#beta-features-in-github-enterprise-server-222){% endif %} | 32 GB{% if currentVersion == "enterprise-server@2.22" %}
    or [**48 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 250 GB{% if currentVersion == "enterprise-server@2.22" %}
    or [**300 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 200 GB | -| 3000-5000 | 8{% if currentVersion == "enterprise-server@2.22" %}
    or [**12**](#beta-features-in-github-enterprise-server-222){% endif %} | 64 GB | 500 GB | 200 GB | -| 5000-8000 | 12{% if currentVersion == "enterprise-server@2.22" %}
    or [**16**](#beta-features-in-github-enterprise-server-222){% endif %} | 96 GB | 750 GB | 200 GB | -| 8000-10000+ | 16{% if currentVersion == "enterprise-server@2.22" %}
    or [**20**](#beta-features-in-github-enterprise-server-222){% endif %} | 128 GB{% if currentVersion == "enterprise-server@2.22" %}
    or [**160 GB**](#beta-features-in-github-enterprise-server-222){% endif %} | 1000 GB | 200 GB | - -{% if currentVersion == "enterprise-server@2.22" %} - -#### Beta features in {% data variables.product.prodname_ghe_server %} 2.22 - -If you enable beta features in {% data variables.product.prodname_ghe_server %} 2.22, your instance requires additional hardware resources. For more information about the beta features, see the [release notes for the 2.22 series](https://enterprise.github.com/releases/series/2.22) on the {% data variables.product.prodname_enterprise %} website.{% endif %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/hotpatching-explanation.md b/translations/es-XL/data/reusables/enterprise_installation/hotpatching-explanation.md deleted file mode 100644 index d08b46f274..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/hotpatching-explanation.md +++ /dev/null @@ -1 +0,0 @@ -Puedes mejorar {% data variables.product.prodname_ghe_server %} al último lanzamiento parchado utilizando un hotpatch, lo cual no requerirá una ventana de mantenimiento y, habitualmente, no requiere un reinicio. Puedes utilizar los hotpatches para subir de categoría a un nuevo lanzamiento parchado, pero no a un lanzamiento de características. Por ejemplo, puedes mejorar de `2.10.1` a `2.10.5` porque pertenecen a la misma serie de características, pero no de `2.10.9` a `2.11.0`, porque están en una serie de características diferente. diff --git a/translations/es-XL/data/reusables/enterprise_installation/image-urls-viewable-warning.md b/translations/es-XL/data/reusables/enterprise_installation/image-urls-viewable-warning.md deleted file mode 100644 index 6250141c45..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/image-urls-viewable-warning.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Advertencia:** si agregas un adjunto de imagen a una solicitud de extracción o comentario en un informe de problemas, cualquiera podrá ver la URL de la imagen anonimizada, aún si la solicitud de extracción se encuentra en un repositorio privado, o si se habilita el modo privado. Para mantener las imágenes confidenciales en privado, limítalas a una red privada o a un servidor que requiera de autenticación. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/increasing-cpus-req.md b/translations/es-XL/data/reusables/enterprise_installation/increasing-cpus-req.md deleted file mode 100644 index 92562eddd2..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/increasing-cpus-req.md +++ /dev/null @@ -1 +0,0 @@ -When you increase CPU resources, we recommend adding at least 6.5 GB of memory for each vCPU (up to 16 vCPUs) that you provision for the instance. When you use more than 16 vCPUs, you don't need to add 6.5 GB of memory for each vCPU, but you should monitor your instance to ensure it has enough memory. diff --git a/translations/es-XL/data/reusables/enterprise_installation/instance-will-restart-automatically.md b/translations/es-XL/data/reusables/enterprise_installation/instance-will-restart-automatically.md deleted file mode 100644 index eacd65c029..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/instance-will-restart-automatically.md +++ /dev/null @@ -1 +0,0 @@ -4. La instancia se reiniciará automáticamente. diff --git a/translations/es-XL/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md b/translations/es-XL/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md deleted file mode 100644 index 4de02dd0f8..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md +++ /dev/null @@ -1 +0,0 @@ -Para utilizar la automatización de Let's Encrypt, tu aplicativo debe configurarse con un nombre de host al que se pueda acceder públicamente mediante HTTP. También se le debe permitir al aplicativo realizar conexiones HTTPS salientes. diff --git a/translations/es-XL/data/reusables/enterprise_installation/monitoring-replicas.md b/translations/es-XL/data/reusables/enterprise_installation/monitoring-replicas.md deleted file mode 100644 index c49b48636a..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/monitoring-replicas.md +++ /dev/null @@ -1,8 +0,0 @@ -Puedes verificar la disponibilidad del {% data variables.product.prodname_ghe_server %} al controlar el código de estado que devuelve la URL `https://HOSTNAME/status`. Un aparato que puede servir el tráfico de usuario devolverá un código de estado de `200` (OK). Un aparato puede devolver un `503` (Servicio no disponible) por distintas razones: - - El aparato es una réplica pasiva, como la réplica en una configuración de disponibilidad alta de dos nodos. - - El aparato está en modo de mantenimiento. - - El aparato es parte de una configuración de replicación geográfica, pero es una réplica inactiva. - -También puedes utilizar el Tablero de resumen de replicación disponible en: - -`https://HOSTNAME/setup/replication` diff --git a/translations/es-XL/data/reusables/enterprise_installation/necessary_ports.md b/translations/es-XL/data/reusables/enterprise_installation/necessary_ports.md deleted file mode 100644 index b8cce678f2..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/necessary_ports.md +++ /dev/null @@ -1,12 +0,0 @@ -| Port (Puerto) | Servicio | Descripción | -| ------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 22 | SSH | Git a través de acceso SSH. Se admite clonar, extraer y subir operaciones a repositorios privados/públicos. | -| 25 | SMTP | SMTP con soporte de encriptación (STARTTLS). | -| 80 | HTTP | Acceso a aplicación web. *Todas las solicitudes se redireccionan al puerto HTTPS cuando se habilita SSL.* | -| 122 | SSH | Acceso a shell de instancia. *El puerto predeterminado (22) se dedica a la aplicación de git+el tráfico de red ssh.* | -| 161/UDP | SNMP | Se requiere para operar el protocolo de revisión de red. | -| 443 | HTTPS | Aplicación web y Git a través de acceso HTTPS. | -| 1194/UDP | VPN | Túnel de red de replicación segura en la configuración de alta disponibilidad. | -| 8080 | HTTP | {% data variables.enterprise.management_console %} basada en la web de texto simple. *No se requiere excepto que el SSL esté inhabilitado de forma manual.* | -| 8443 | HTTPS | {% data variables.enterprise.management_console %} seguro basada en la web. *Requerido para la instalación y la configuración básicas.* | -| 9418 | Git | Puerto simple de protocolo de Git. Únicamente clonar y extraer operaciones a repositorios públicos. *Comunicación de red no encriptada.* | diff --git a/translations/es-XL/data/reusables/enterprise_installation/open-vm-console-start.md b/translations/es-XL/data/reusables/enterprise_installation/open-vm-console-start.md deleted file mode 100644 index 2d0b8dfed8..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/open-vm-console-start.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Abre la consola de la máquina virtual utilizando tus herramientas de plataforma de virtualización. ![Consola de {% data variables.product.prodname_enterprise %}](/assets/images/enterprise/network-configuration/virtual-machine-console.png) -2. Para iniciar la configuración de red, presiona **S**. diff --git a/translations/es-XL/data/reusables/enterprise_installation/promoting-a-replica.md b/translations/es-XL/data/reusables/enterprise_installation/promoting-a-replica.md deleted file mode 100644 index df13349814..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/promoting-a-replica.md +++ /dev/null @@ -1 +0,0 @@ -Promover una réplica no configura la replicación para aplicativos existentes automáticamente. Despues de promoverla, si así lo quieres, puedes configurar la replicacion desde el nuevo aplicativo principal hacia uno existente y hacia el aplicativo primario previo. diff --git a/translations/es-XL/data/reusables/enterprise_installation/replica-ssh.md b/translations/es-XL/data/reusables/enterprise_installation/replica-ssh.md deleted file mode 100644 index a2206d46b0..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/replica-ssh.md +++ /dev/null @@ -1,4 +0,0 @@ -1. Conéctate a la instancia réplica a través de SSH como el usuario "admin" en el puerto 122: -```shell -$ ssh -p 122 admin@replica-host -``` diff --git a/translations/es-XL/data/reusables/enterprise_installation/replica-verify.md b/translations/es-XL/data/reusables/enterprise_installation/replica-verify.md deleted file mode 100644 index 3c937a2b37..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/replica-verify.md +++ /dev/null @@ -1,5 +0,0 @@ -1. Verifica la mejora ejecutando: - - ```shell - $ ghe-version - ``` diff --git a/translations/es-XL/data/reusables/enterprise_installation/replication-command.md b/translations/es-XL/data/reusables/enterprise_installation/replication-command.md deleted file mode 100644 index 22a2babcab..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/replication-command.md +++ /dev/null @@ -1,9 +0,0 @@ -1. Para comenzar la replicación de las bases de datos, utiliza el comando `ghe-repl-start`. - ```shell - $ ghe-repl-start - ``` - {% 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`. - - {% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/replication-status.md b/translations/es-XL/data/reusables/enterprise_installation/replication-status.md deleted file mode 100644 index a8928a2ed1..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/replication-status.md +++ /dev/null @@ -1 +0,0 @@ -1. En la instancia replicada, para garantizar que se estén ejecutando correctamente los servicios de replicación, ejecuta `ghe-repl-status`. Este comando devolverá un `OK` para todos los servicios cuando exista una replicación exitosa en progreso y la réplica se haya mejorado. diff --git a/translations/es-XL/data/reusables/enterprise_installation/request-a-trial.md b/translations/es-XL/data/reusables/enterprise_installation/request-a-trial.md deleted file mode 100644 index 5958ddb204..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/request-a-trial.md +++ /dev/null @@ -1 +0,0 @@ -Puedes solicitar una prueba para evaluar {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)". diff --git a/translations/es-XL/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md b/translations/es-XL/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md deleted file mode 100644 index b844e1ed54..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md +++ /dev/null @@ -1 +0,0 @@ -3. En la [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), configura y guarda a configuración que desees. diff --git a/translations/es-XL/data/reusables/enterprise_installation/software-license.md b/translations/es-XL/data/reusables/enterprise_installation/software-license.md deleted file mode 100644 index fb8cf81de8..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/software-license.md +++ /dev/null @@ -1 +0,0 @@ -Debes tener un archivo de licencia de {% data variables.product.prodname_enterprise %}. Para descargar un archivo de licencia existente o solicitar una licencia de prueba, visita [enterprise.github.com](https://enterprise.github.com/download). Para obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/installation/managing-your-github-enterprise-license/)". diff --git a/translations/es-XL/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/es-XL/data/reusables/enterprise_installation/ssh-into-instance.md deleted file mode 100644 index 3f6ba95cd9..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/ssh-into-instance.md +++ /dev/null @@ -1,4 +0,0 @@ -1. SSH en {% data variables.product.product_location_enterprise %}. -```shell -$ ssh -p 122 admin@HOSTNAME -``` diff --git a/translations/es-XL/data/reusables/enterprise_installation/ssh-into-target-instance.md b/translations/es-XL/data/reusables/enterprise_installation/ssh-into-target-instance.md deleted file mode 100644 index b8e68c3578..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/ssh-into-target-instance.md +++ /dev/null @@ -1,4 +0,0 @@ -1. Como administrador de sitio, [Entra por SSH en tu instancia destino de {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/). -```shell -$ ssh -p 122 admin@HOSTNAME -``` diff --git a/translations/es-XL/data/reusables/enterprise_installation/start-replication.md b/translations/es-XL/data/reusables/enterprise_installation/start-replication.md deleted file mode 100644 index 102b69218e..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/start-replication.md +++ /dev/null @@ -1 +0,0 @@ -1. En la instancia réplica, para comenzar la replicación, ejecuta `ghe-repl-start`. diff --git a/translations/es-XL/data/reusables/enterprise_installation/terminating-tls.md b/translations/es-XL/data/reusables/enterprise_installation/terminating-tls.md deleted file mode 100644 index 6873a1b51c..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/terminating-tls.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - - **Advertencia:** cuando se termina una conexión HTTPS en un balanceador de carga, las solicitudes de éste hacia {% data variables.product.prodname_ghe_server %} necesitarán utilizar HTTPS. Bajar la conexión de categoría a HTTP no es compatible. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/upload-a-license-file.md b/translations/es-XL/data/reusables/enterprise_installation/upload-a-license-file.md deleted file mode 100644 index 153a892f54..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/upload-a-license-file.md +++ /dev/null @@ -1 +0,0 @@ -2. En el prompt, carga tu archivo de licencia y configura una contraseña de consola de administración. Para obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion }}/admin/guides/installation/managing-your-github-enterprise-license/)". diff --git a/translations/es-XL/data/reusables/enterprise_installation/visit-your-instance.md b/translations/es-XL/data/reusables/enterprise_installation/visit-your-instance.md deleted file mode 100644 index 6b4488403c..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/visit-your-instance.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Visitar tu instancia**. diff --git a/translations/es-XL/data/reusables/enterprise_installation/vm-console-done.md b/translations/es-XL/data/reusables/enterprise_installation/vm-console-done.md deleted file mode 100644 index 2febe6dc27..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/vm-console-done.md +++ /dev/null @@ -1 +0,0 @@ -1. Para terminar tu configuración, presiona **D**. diff --git a/translations/es-XL/data/reusables/enterprise_installation/warning-on-scaling.md b/translations/es-XL/data/reusables/enterprise_installation/warning-on-scaling.md deleted file mode 100644 index c92642b612..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/warning-on-scaling.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Nota:** Siempre puedes mejorar tu CPU o memoria si cambias tu instancia de tamaño. Sin embargo, ya que cambiar de tamaño tu CPU o memoria requiere tiempo de inactividad para tus usuarios, recomendamos contar con recursos de sobra para compensar un escalamiento. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md b/translations/es-XL/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md deleted file mode 100644 index 84d1380fed..0000000000 --- a/translations/es-XL/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Advertencia:** El proceso para destinar nuevos recursos de sistema varía dependiendo de la plataforma de virtualización y tipo de recurso. Siempre deberás configurar el monitoreo y las alertas de los recursos clave del sistema. Para obtener más información, consulta la sección "[Monitorear tu aplicativo de {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/monitoring-your-github-enterprise-server-appliance/)". - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_management_console/access-monitoring.md b/translations/es-XL/data/reusables/enterprise_management_console/access-monitoring.md deleted file mode 100644 index a09820565c..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/access-monitoring.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Monitoreo**. ![Pestaña de monitoreo](/assets/images/enterprise/management-console/monitoring-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/advanced-security-tab.md b/translations/es-XL/data/reusables/enterprise_management_console/advanced-security-tab.md deleted file mode 100644 index bf61e1f47c..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/advanced-security-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_advanced_security %}**. ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/authentication-password.md b/translations/es-XL/data/reusables/enterprise_management_console/authentication-password.md deleted file mode 100644 index ae71195465..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/authentication-password.md +++ /dev/null @@ -1 +0,0 @@ -En "Contraseña de autenticación", escribe la contraseña de autenticación. diff --git a/translations/es-XL/data/reusables/enterprise_management_console/authentication-protocol.md b/translations/es-XL/data/reusables/enterprise_management_console/authentication-protocol.md deleted file mode 100644 index ca04ba0c58..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/authentication-protocol.md +++ /dev/null @@ -1 +0,0 @@ -En la parte derecha de "Contraseña de autenticación", en el menú desplegable de **Protocolo**, da clic en el protocolo de autenticación que quieras utilizar. diff --git a/translations/es-XL/data/reusables/enterprise_management_console/authentication.md b/translations/es-XL/data/reusables/enterprise_management_console/authentication.md deleted file mode 100644 index 853b5bf94e..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/authentication.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Autenticación**. ![Pestaña de autenticación en la barra lateral de configuración](/assets/images/enterprise/management-console/sidebar-authentication.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/badge_indicator.md b/translations/es-XL/data/reusables/enterprise_management_console/badge_indicator.md deleted file mode 100644 index 7b0c2a30f0..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/badge_indicator.md +++ /dev/null @@ -1 +0,0 @@ -Un equipo que se encuentra [sincronizado a un grupo LDAP](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap#enabling-ldap-sync) se indica con una insignia de LDAP especial. La lista de miembros para un equipo de LDAP sincronizado únicamente se puede administrar desde el grupo LDAP al que está mapeado. diff --git a/translations/es-XL/data/reusables/enterprise_management_console/enable-disable-code-scanning.md b/translations/es-XL/data/reusables/enterprise_management_console/enable-disable-code-scanning.md deleted file mode 100644 index a6adf2088e..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/enable-disable-code-scanning.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Warning**: Changing this setting will cause {% if currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_dotcom %}{% endif %} to restart. You should time this change carefully, to minimize downtime. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_management_console/enable-snmp.md b/translations/es-XL/data/reusables/enterprise_management_console/enable-snmp.md deleted file mode 100644 index 50a596de52..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/enable-snmp.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Monitoreando", selecciona **Habilitar SNMP**. ![Botón para habilitar SNMP](/assets/images/enterprise/management-console/enable-snmp.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/hostname-menu-item.md b/translations/es-XL/data/reusables/enterprise_management_console/hostname-menu-item.md deleted file mode 100644 index 2a77561048..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/hostname-menu-item.md +++ /dev/null @@ -1 +0,0 @@ -3. En la barra lateral izquierda, da clic en **Nombre de Host**. ![Pestaña de nombre de host en la barra lateral](/assets/images/enterprise/management-console/hostname-sidebar.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/pages-tab.md b/translations/es-XL/data/reusables/enterprise_management_console/pages-tab.md deleted file mode 100644 index a2700d139e..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/pages-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Páginas**. ![Barra lateral de páginas](/assets/images/enterprise/management-console/sidebar-pages.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/privacy.md b/translations/es-XL/data/reusables/enterprise_management_console/privacy.md deleted file mode 100644 index db9d6f7b35..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/privacy.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Privacidad**. ![Pestaña de privacidad en la barra lateral de configuración](/assets/images/enterprise/management-console/sidebar-privacy.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/save-settings.md b/translations/es-XL/data/reusables/enterprise_management_console/save-settings.md deleted file mode 100644 index 20de5c6bf9..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/save-settings.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de la barra lateral izquierda, da clic en **Guardar configuración**. ![El botón de guardar en la {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png) -1. Espera a que la configuración se ejecute por completo. diff --git a/translations/es-XL/data/reusables/enterprise_management_console/select-tls-only.md b/translations/es-XL/data/reusables/enterprise_management_console/select-tls-only.md deleted file mode 100644 index 39a7185d44..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/select-tls-only.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecciona **Únicamente TLS (recomendado)**. ![Casilla para escoger únicamente TLS](/assets/images/enterprise/management-console/tls-only.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/support-link.md b/translations/es-XL/data/reusables/enterprise_management_console/support-link.md deleted file mode 100644 index e6f57ebd39..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/support-link.md +++ /dev/null @@ -1 +0,0 @@ -4. En la parte superior derecha de {% data variables.enterprise.management_console %}, da clic en **Soporte**. ![Botón para acceder al área de soporte](/assets/images/enterprise/management-console/support-link.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/test-domain-settings-failure.md b/translations/es-XL/data/reusables/enterprise_management_console/test-domain-settings-failure.md deleted file mode 100644 index f439c93055..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/test-domain-settings-failure.md +++ /dev/null @@ -1 +0,0 @@ -1. Si no ves una tilde verde al costado de todas las entradas, revisa tu configuración para los elementos de configuración que hayan fallado. Para obtener más información, consulta la sección "[Configurar los servidores de nombre de DNS](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/)". ![Tabla mostrando el estado de las configuraciones de DNS y SSL](/assets/images/enterprise/management-console/domain-dns-ssl-settings-check.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/type-management-console-password.md b/translations/es-XL/data/reusables/enterprise_management_console/type-management-console-password.md deleted file mode 100644 index c00a2aa8ab..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/type-management-console-password.md +++ /dev/null @@ -1 +0,0 @@ -1. Si se te solicita, teclea tu contraseña de {% data variables.enterprise.management_console %}. ![Pantalla de desbloqueo de {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/unlock-password.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/updates-tab.md b/translations/es-XL/data/reusables/enterprise_management_console/updates-tab.md deleted file mode 100644 index da57a34276..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/updates-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de {% data variables.enterprise.management_console %}, da clic en **Actualizaciones**. ![Actualiza el elemento del menú](/assets/images/enterprise/management-console/updates_tab.png) diff --git a/translations/es-XL/data/reusables/enterprise_management_console/username_normalization.md b/translations/es-XL/data/reusables/enterprise_management_console/username_normalization.md deleted file mode 100644 index 18e29d7f39..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/username_normalization.md +++ /dev/null @@ -1,5 +0,0 @@ -Los nombres de usuario del {% data variables.product.prodname_ghe_server %} únicamente pueden contener caracteres alfanuméricos y rayas (`-`). El {% data variables.product.prodname_ghe_server %} convertirá en raya cualquier caracter no alfanumérico en el nombre de tu cuenta de usuario. Por ejemplo, un nombre de usuario `gregory.st.john` se convertirá en `gregory-st-john`. Nota que los nombres de usuarios normalizados tampoco pueden comenzar o terminar con una raya. Tampoco pueden contener dos rayas seguidas. - -Los nombres de usuarios creados a partir de direcciones de correo electrónico se crean con los caracteres normalizados que preceden al caracter `@`. - -Si múltiples cuentas se normalizan en el mismo nombre de usuario de {% data variables.product.prodname_ghe_server %}, solo se crea la primera cuenta de usuario. Los siguientes usuarios con el mismo nombre de usuario no podrán registrarse. diff --git a/translations/es-XL/data/reusables/enterprise_management_console/username_normalization_sample.md b/translations/es-XL/data/reusables/enterprise_management_console/username_normalization_sample.md deleted file mode 100644 index 0c7419d841..0000000000 --- a/translations/es-XL/data/reusables/enterprise_management_console/username_normalization_sample.md +++ /dev/null @@ -1,10 +0,0 @@ -Esta tabla brinda ejemplos de cómo se normalizan los nombres de usuarios en el {% data variables.product.prodname_ghe_server %}: - -| Nombre de usuario | Nombre de usuario normalizado | Resultado | -| ---------------------- | ----------------------------- | --------------------------------------------------------------------------------------------------------- | -| Ms.Bubbles | `ms-bubbles` | El nombre de usuario se crea correctamente. | -| !Ms.Bubbles | `-ms-bubbles` | No se crea este nombre de usuario debido a que comienza con una raya. | -| Ms.Bubbles! | `ms-bubbles-` | No se crea este nombre de usuario debido a que termina con una raya. | -| Ms!!Bubbles | `ms--bubbles` | No se crea este nombre de usuario debido a que contiene dos rayas seguidas. | -| Ms!Bubbles | `ms-bubbles` | No se crea este nombre de usuario. A pesar de que el nombre de usuario normalizado es válido, ya existía. | -| Ms.Bubbles@example.com | `ms-bubbles` | No se crea este nombre de usuario. A pesar de que el nombre de usuario normalizado es válido, ya existía. | diff --git a/translations/es-XL/data/reusables/enterprise_migrations/exclude-file-attachments.md b/translations/es-XL/data/reusables/enterprise_migrations/exclude-file-attachments.md deleted file mode 100644 index ff253121db..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/exclude-file-attachments.md +++ /dev/null @@ -1 +0,0 @@ -Los archivos adjuntos pueden resultar muy grandes y es posible que sobrecarguen tu archivo de migración final de manera innecesaria. diff --git a/translations/es-XL/data/reusables/enterprise_migrations/fork-persistence.md b/translations/es-XL/data/reusables/enterprise_migrations/fork-persistence.md deleted file mode 100644 index b48fdc0c18..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/fork-persistence.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Nota:** Las relaciones de las bifurcaciones no persisten después de una migración. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/enterprise_migrations/locking-repositories.md b/translations/es-XL/data/reusables/enterprise_migrations/locking-repositories.md deleted file mode 100644 index f543d86e1d..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/locking-repositories.md +++ /dev/null @@ -1,6 +0,0 @@ -{% tip %} - -**Nota:**Cerrar un repositorio previene que los usuarios suban información al mismo o que modifiquen sus recursos como informes de problemas, etiquetas, hitos, wikis, y comentarios. Los nuevos equipos y colaboradores no podrán asociarse con un repositorio cerrado. - -Si estás realizando una ejecución de prueba, no necesitas cerrar el repositorio. En el resto de los casos, se recomienda ampliamente. Para obtener más información, consulta "[Acerca de las migraciones](/enterprise/admin/migrations/about-migrations#types-of-migrations)". -{% endtip %} diff --git a/translations/es-XL/data/reusables/enterprise_migrations/make-a-list.md b/translations/es-XL/data/reusables/enterprise_migrations/make-a-list.md deleted file mode 100644 index eff3aa58c7..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/make-a-list.md +++ /dev/null @@ -1 +0,0 @@ -1. Para minimizar los tiempos de inactividad, haz una lista de repositorios que deseas exportar desde la instancia de origen. Puedes agregar múltiples repositorios a una exportación a la vez usando un archivo de texto que muestra la URL de cada repositorio en una línea separada. diff --git a/translations/es-XL/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/es-XL/data/reusables/enterprise_migrations/ready-to-import-migrations.md deleted file mode 100644 index 924da690a0..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/ready-to-import-migrations.md +++ /dev/null @@ -1 +0,0 @@ -1. Para importar los datos de migración archivados a una instancia de {% data variables.product.prodname_ghe_server %} , consulta "[Importando datos de migración a {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server/)". diff --git a/translations/es-XL/data/reusables/enterprise_migrations/review-the-import-csv.md b/translations/es-XL/data/reusables/enterprise_migrations/review-the-import-csv.md deleted file mode 100644 index 408f1efe18..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/review-the-import-csv.md +++ /dev/null @@ -1,16 +0,0 @@ -1. Revisa el archivo (CSV) separado por coma en `/PATH/REPO-NAME.git/git-import/raw-authors.csv`. Debería contener estas columnas: - - `ID`: el autor tal como se almacena en el repositorio original, seguido de un identificador único - - `NOMBRE`: el autor tal como se almacena en el repositorio original - - Para mapear autores desde el repositorio original a una dirección de correo electrónico y nombre, crea un nuevo archivo CSV con las columnas `ID,(ignorado),GIT_EMAIL,GIT_NAME`, que reemplace la información de autor por "ID" con "GIT_EMAIL" y "GIT_NAME". - - - #### Ejemplo: - - - ID del autor original: `octocat@111111-2222-3333-4444-55555555555` - - Nueva dirección de correo electrónico: `octocat@github.com` - - Nuevo nombre: `The Octocat` - - Para mapear el autor original a un nuevo usuario de Git, el archivo CSV debería incluir la línea: - - `octocat@111111-2222-3333-4444-55555555555, ,octocat@github.com,The Octocat` diff --git a/translations/es-XL/data/reusables/enterprise_migrations/specify-staging-path.md b/translations/es-XL/data/reusables/enterprise_migrations/specify-staging-path.md deleted file mode 100644 index a32966f9c2..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/specify-staging-path.md +++ /dev/null @@ -1 +0,0 @@ -Para especificar en donde se deben escalar los archivos de migración de acuerdo con la etapa, anexa el comando con `--staging-path=/full/staging/path`. La ruta predeterminada es `/data/user/tmp`. diff --git a/translations/es-XL/data/reusables/enterprise_migrations/token-generation.md b/translations/es-XL/data/reusables/enterprise_migrations/token-generation.md deleted file mode 100644 index 0729298906..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/token-generation.md +++ /dev/null @@ -1 +0,0 @@ -[Genera un acceso de token](/enterprise/user/articles/creating-an-access-token-for-command-line-use/) con los alcances `repo` y `admin:org` diff --git a/translations/es-XL/data/reusables/enterprise_migrations/unlocking-on-instances.md b/translations/es-XL/data/reusables/enterprise_migrations/unlocking-on-instances.md deleted file mode 100644 index 3e4f3c23cb..0000000000 --- a/translations/es-XL/data/reusables/enterprise_migrations/unlocking-on-instances.md +++ /dev/null @@ -1,5 +0,0 @@ -1. Libera todos los repositorios importados con el comando `ghe-migrator unlock`. Nececitarás tu GUID de Migración: -```shell -$ ghe-migrator unlock -g MIGRATION_GUID -> Unlocked octo-org/octo-project -``` diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/access-settings.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/access-settings.md deleted file mode 100644 index e0d9b8f423..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/access-settings.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}. ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/admin-tab.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/admin-tab.md deleted file mode 100644 index f4ab25ee82..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/admin-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Admin (Administrador)**. ![Herramientas de administrador](/assets/images/enterprise/site-admin-settings/user/user-admin-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/admin-top-tab.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/admin-top-tab.md deleted file mode 100644 index ede05a651f..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/admin-top-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In the upper-right corner of the page, click {% octicon "gear" %} **Admin**. ![Herramientas de administrador](/assets/images/enterprise/site-admin-settings/user/user-admin-tab-top.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/business.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/business.md deleted file mode 100644 index 53df7edc4a..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/business.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haga clic en **Enterprise**. ![Pestaña de Enterprise en la configuración Site Admin](/assets/images/enterprise/site-admin-settings/enterprise-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-preview.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-preview.md deleted file mode 100644 index faeb6063c9..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-preview.md +++ /dev/null @@ -1 +0,0 @@ -1. Para ver el mensaje, haga clic en **Preview (Vista previa)**. diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-repo.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-repo.md deleted file mode 100644 index b53dab7634..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-repo.md +++ /dev/null @@ -1 +0,0 @@ -1. En los resultados de búsqueda, da clic en el nombre del repositorio. ![Opciones de búsqueda de la configuración de administrador para el sitio](/assets/images/enterprise/site-admin-settings/click-repo.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-user-or-org.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-user-or-org.md deleted file mode 100644 index a31e8ca650..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-user-or-org.md +++ /dev/null @@ -1 +0,0 @@ -1. En los resultados de búsqueda, da clic en el nombre de usuario u organización. ![Opciones de búsqueda de la configuración de administrador para el sitio](/assets/images/enterprise/site-admin-settings/click-user.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-user.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-user.md deleted file mode 100644 index 9906e6913f..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/click-user.md +++ /dev/null @@ -1 +0,0 @@ -1. En los resultados de búsqueda, da clic en el nombre del usuario. ![Opciones de búsqueda de la configuración de administrador para el sitio](/assets/images/enterprise/site-admin-settings/click-user.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md deleted file mode 100644 index 5118fb574c..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) es una extensión de código abierto para Git que te permite trabajar con archivos grandes de la misma manera que con otros archivos de texto. diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md deleted file mode 100644 index cdc321cb6b..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md +++ /dev/null @@ -1 +0,0 @@ -El umbral de inactividad es cuánto tiempo debe estar inactivo un usuario para considerarse como inactivo. El umbral de inactividad predeterminado es de 90 días, sin embargo, puedes personalizar este umbral para {% data variables.product.product_location_enterprise %}. diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md deleted file mode 100644 index a7d1a0950a..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "{% data variables.large_files.product_name_short %}", da clic en **Habilitar** o **Inhabilitar**. ![Botón de inhabilitar](/assets/images/enterprise/management-console/git-lfs-toggle.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md deleted file mode 100644 index 6cc33bcb2e..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea el nombre de usuario y dirección de correo electrónico de cada cuenta de usuario que quieras crear, posteriormente, da clic en **Generar un enlace para restablecer la contraseña**. ![Botón de generar un enlace para restablecer la contraseña](/assets/images/enterprise/site-admin-settings/generate-password-reset-link-button.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md deleted file mode 100644 index 73540910b0..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Invitar usuario**. ![Pestaña de invitar usuario en la consola de administrador del sitio](/assets/images/enterprise/site-admin-settings/invite-user.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md deleted file mode 100644 index 7921b165d5..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md +++ /dev/null @@ -1 +0,0 @@ -Para ver los repositorios con acceso de lectura Git anónimo habilitado, filtra la lista de repositorios en el tablero de administración del sitio. diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md deleted file mode 100644 index 93cc041dc8..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** cuando el aplicativo se encuentre en modo de mantenimiento, la URL `https://HOSTNAME/status` devolverá un código de estado `503` (Servicio no disponible). Para obtener más información, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." - -{% endnote %} diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/management-console.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/management-console.md deleted file mode 100644 index af582499a0..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/management-console.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **{% data variables.enterprise.management_console %}**. ![pestaña {% data variables.enterprise.management_console %} en la barra lateral izquierda](/assets/images/enterprise/management-console/management-console-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/override-policy.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/override-policy.md deleted file mode 100644 index 34d0fe8b02..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/override-policy.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Nota:** Cada repositorio hereda automáticamente la configuración predeterminada de la organización o usuario al que pertenece. No puedes invalidar la configuración predeterminada si el dueño del repositorio ha requerido dicha configuración en todos sus repositorios. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/packages-tab.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/packages-tab.md deleted file mode 100644 index 7552439d3d..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/packages-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. In the left sidebar, click **Packages**. ![Packages tab in management console sidebar](/assets/images/enterprise/site-admin-settings/management-console-packages-tab.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/repository-search.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/repository-search.md deleted file mode 100644 index c4bac62704..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/repository-search.md +++ /dev/null @@ -1 +0,0 @@ -1. En el campo de búsqueda, teclea el nombre del repositorio y da clic en **Buscar**. ![Campo de búsqueda en la configuración de administrador de sitio](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/save-changes.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/save-changes.md deleted file mode 100644 index bf5b72a3d3..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/save-changes.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte inferior de la página, da clic en **Guardar cambios**. ![Guardar cambios](/assets/images/enterprise/site-admin-settings/save-changes-button.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/search-user-or-org.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/search-user-or-org.md deleted file mode 100644 index 37dcc4eda4..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/search-user-or-org.md +++ /dev/null @@ -1 +0,0 @@ -1. En el campo de búsqueda, teclea el nombre del usuario u organización y da clic en **Buscar**. ![Campo de búsqueda en la configuración de administrador de sitio](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/search-user.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/search-user.md deleted file mode 100644 index 97baa394b2..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/search-user.md +++ /dev/null @@ -1 +0,0 @@ -1. En el campo de búsqueda, teclea el nombre de usuario y da clic en **Buscar**. ![Campo de búsqueda en la configuración de administrador de sitio](/assets/images/enterprise/site-admin-settings/search-for-things.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/security-tab.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/security-tab.md deleted file mode 100644 index 5c26b1060f..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/security-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de la página, haz clic en {% octicon "shield" aria-label="The shield" %} **Security (Seguridad)**. ![Pestaña de seguridad](/assets/images/enterprise/site-admin-settings/repo/repo-security-top-tab.png) diff --git a/translations/es-XL/data/reusables/enterprise_site_admin_settings/sign-in.md b/translations/es-XL/data/reusables/enterprise_site_admin_settings/sign-in.md deleted file mode 100644 index feecf61f02..0000000000 --- a/translations/es-XL/data/reusables/enterprise_site_admin_settings/sign-in.md +++ /dev/null @@ -1 +0,0 @@ -1. Ingresa en {% data variables.product.product_location_enterprise %} a través de `http(s)://HOSTNAME/login`. diff --git a/translations/es-XL/data/reusables/enterprise_user_management/2fa_is_available.md b/translations/es-XL/data/reusables/enterprise_user_management/2fa_is_available.md deleted file mode 100644 index 77ebf6dca5..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/2fa_is_available.md +++ /dev/null @@ -1 +0,0 @@ -Cuando utilices LDAP o una autenticación integrada, la autenticación de dos factores será compatible. Los administradores de la organización le pueden solicitar a los miembros que tengan la autenticación de dos factores activada. diff --git a/translations/es-XL/data/reusables/enterprise_user_management/built-in-authentication-option.md b/translations/es-XL/data/reusables/enterprise_user_management/built-in-authentication-option.md deleted file mode 100644 index 76dcde13d9..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/built-in-authentication-option.md +++ /dev/null @@ -1 +0,0 @@ -Opcionalmente, selecciona **Permitir autenticación integrada** para invitar a los usuarios a utilizar la autenticación integrada si no pertenecen a el proveedor de identidad de {% data variables.product.product_location_enterprise %}. diff --git a/translations/es-XL/data/reusables/enterprise_user_management/built-in-authentication.md b/translations/es-XL/data/reusables/enterprise_user_management/built-in-authentication.md deleted file mode 100644 index 9eaef9dc01..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/built-in-authentication.md +++ /dev/null @@ -1 +0,0 @@ -Si quieres autenticar usuarios sin agregarlos a tu proveedor de identidad, puedes configurar la autenticación integrada. Para obtener más información, consulta "[Permitir autenticación integrada para usuarios fuera de tu proveedor de identidad](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider)". diff --git a/translations/es-XL/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/es-XL/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md deleted file mode 100644 index dc896f8db4..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Nota:** Si habilitas al acceso de lectura anónimo de Git, eres responsable de todos los accesos y usos de esta característica. {% data variables.product.company_short %} no será responsable de ningún acceso no deseado o uso indebido de la función. También puede que no utilices esta característica para violar tu licencia desde {% data variables.product.company_short %}, incluyendo el límite de la cantidad de licencias de usuario que has comprado con nosotros. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md b/translations/es-XL/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md deleted file mode 100644 index bc4124a742..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md +++ /dev/null @@ -1,8 +0,0 @@ -{% note %} - -**Notas:** -- No puedes cambiar las configuraciones de acceso de lectura de Git para los repositorios bifurcados ya que heredan sus configuraciones de acceso del repositorio raíz por defecto. -- Si un repositorio público se convierte en privado, entonces el acceso de lectura anónimo de Git se inhabilitará automáticamente para ese repositorio y sus bifurcaciones. -- Si un repositorio con autenticación anónima contiene activos de {% data variables.large_files.product_name_short %}, fallará al descargar los activos de {% data variables.large_files.product_name_short %} ya que aún requerirá autenticación. Recomendamos firmemente no habilitar el acceso de lectura anónimo de Git para un repositorio con activos de {% data variables.large_files.product_name_short %}. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/enterprise_user_management/external_auth_disables_2fa.md b/translations/es-XL/data/reusables/enterprise_user_management/external_auth_disables_2fa.md deleted file mode 100644 index 63c51b33e7..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/external_auth_disables_2fa.md +++ /dev/null @@ -1 +0,0 @@ -Cuando se utiliza SAML o CAS, la autenticación de dos factores no se admite o se administra en el aparato del {% data variables.product.prodname_ghe_server %}, pero es posible que lo admita un proveedor de autenticación externo. No está disponible la implementación de la autenticación de dos factores en organizaciones. Para obtener más información sobre cómo implementar la autenticación de dos factores, consulta "[Requerir autenticación de dos factores en tu organización](/enterprise/{{ currentVersion }}/user/articles/requiring-two-factor-authentication-in-your-organization/)." diff --git a/translations/es-XL/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md b/translations/es-XL/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md deleted file mode 100644 index 379cf01eff..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md +++ /dev/null @@ -1 +0,0 @@ -Como parte de su cofiguración de optimización, LDAP Sync no transferirá tu estructura de equipo anidada. Para crear relaciones entre equipos padre e hijo, deberás recrear manualmente la estructura de equipo anidada y sincronizarla con el grupo de LDAP correspondiente. Para obtener más información, consulta la sección "[Crear equipos](/enterprise/{{ currentVersion }}/admin/guides/user-management/creating-teams/#creating-teams-with-ldap-sync-enabled)" diff --git a/translations/es-XL/data/reusables/enterprise_user_management/manage-global-webhooks-api.md b/translations/es-XL/data/reusables/enterprise_user_management/manage-global-webhooks-api.md deleted file mode 100644 index e604de4fda..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/manage-global-webhooks-api.md +++ /dev/null @@ -1 +0,0 @@ -También puedes utilizar {% data variables.product.prodname_enterprise_api %} para administrar los webhooks globales. Para encontrar una lista de acciones completa, consulta la sección "[Webhooks globales](/v3/enterprise-admin/global_webhooks)". diff --git a/translations/es-XL/data/reusables/enterprise_user_management/two_factor_auth_header.md b/translations/es-XL/data/reusables/enterprise_user_management/two_factor_auth_header.md deleted file mode 100644 index 996425fdc1..0000000000 --- a/translations/es-XL/data/reusables/enterprise_user_management/two_factor_auth_header.md +++ /dev/null @@ -1 +0,0 @@ -### Autenticación de dos factores diff --git a/translations/es-XL/data/reusables/files/add-file.md b/translations/es-XL/data/reusables/files/add-file.md deleted file mode 100644 index de306026f6..0000000000 --- a/translations/es-XL/data/reusables/files/add-file.md +++ /dev/null @@ -1,5 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -1. Sobre la lista de archivos, da clic en **Crear archivo nuevo**. ![Botón de "Crear archivo nuevo"](/assets/images/help/repository/create_new_file.png) -{% else %} -1. En la parte superior de la lista de archivos, utilizando el menú desplegable de **Agregar archivo**, da clic en **Crear archivo nuevo**. !["Crear archivo nuevo" en el menú desplegable de "Agregar archivo"](/assets/images/help/repository/create_new_file.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/files/choose-commit-email.md b/translations/es-XL/data/reusables/files/choose-commit-email.md deleted file mode 100644 index 3f99d20dfa..0000000000 --- a/translations/es-XL/data/reusables/files/choose-commit-email.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -1. Debajo de los campos de mensaje de confirmación, haz clic en el menú desplegable de dirección de correo electrónico y elige una dirección de correo electrónico de autor de Git. Únicamente las direcciones de correo electrónico verificadas aparecen en el menú desplegable. Si habilitaste privacidad de la dirección de correo electrónico, entonces `@users.noreply.github.com` es la dirección de correo electrónico de autor de la confirmación por defecto. Para obtener más información, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)". ![Escoger direcciones de correo electrónico para confirmaciones](/assets/images/help/repository/choose-commit-email-address.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/files/choose_commit_branch.md b/translations/es-XL/data/reusables/files/choose_commit_branch.md deleted file mode 100644 index 352027c1c3..0000000000 --- a/translations/es-XL/data/reusables/files/choose_commit_branch.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de los campos del mensaje de confirmación, decide si deseas agregar tu confirmación a la rama actual o a una rama nueva. Si tu rama actual es la rama predeterminada, debes elegir crear una nueva rama para tu confirmación y después crear una solicitud de extracción. Para obtener más información, consulta "[Crear una solicitud de extracción nueva](/articles/creating-a-pull-request)". ![Confirmar opciones de rama](/assets/images/help/repository/choose-commit-branch.png) diff --git a/translations/es-XL/data/reusables/files/commit-author-email-options.md b/translations/es-XL/data/reusables/files/commit-author-email-options.md deleted file mode 100644 index 7090a05c3a..0000000000 --- a/translations/es-XL/data/reusables/files/commit-author-email-options.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Si no has habilitado la privacidad de direcciones de correo electrónico, puedes escoger la dirección verificada con la que serás autor de los cambios cuando edites, borres o crees archivos o fusiones una solicitud de extracción en {% data variables.product.product_name %}. Si habilitaste la privacidad de direcciones de correo electrónico, entonces la dirección del autor de los cambios no se podrá cambiar y será predeterminada a `@users.noreply.github.com`. -{% endif %} diff --git a/translations/es-XL/data/reusables/files/preview_change.md b/translations/es-XL/data/reusables/files/preview_change.md deleted file mode 100644 index a2f11b01e9..0000000000 --- a/translations/es-XL/data/reusables/files/preview_change.md +++ /dev/null @@ -1 +0,0 @@ -1. Arriba del contenido nuevo, da clic en **Previsualizar cambios**. ![Botón para previsualizar archivo](/assets/images/help/repository/edit-readme-preview-changes.png) diff --git a/translations/es-XL/data/reusables/files/propose_file_change.md b/translations/es-XL/data/reusables/files/propose_file_change.md deleted file mode 100644 index cc8c12b133..0000000000 --- a/translations/es-XL/data/reusables/files/propose_file_change.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Proponer cambio en el archivo**. ![Botón para proponer cambio de archivo](/assets/images/help/repository/propose-file-change-quick-pull.png) diff --git a/translations/es-XL/data/reusables/files/propose_new_file.md b/translations/es-XL/data/reusables/files/propose_new_file.md deleted file mode 100644 index 97d0f293ad..0000000000 --- a/translations/es-XL/data/reusables/files/propose_new_file.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Proponer nuevo archivo**. ![Botón para proponer nuevo archivo](/assets/images/help/repository/new-file-commit-button.png) diff --git a/translations/es-XL/data/reusables/files/write_commit_message.md b/translations/es-XL/data/reusables/files/write_commit_message.md deleted file mode 100644 index 726582b990..0000000000 --- a/translations/es-XL/data/reusables/files/write_commit_message.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte inferior de la página, teclea un mensaje de confirmación corto y significativo que describa el cambio que realizaste al archivo. Puedes atribuir el cambio a mas de un autor en el mensaje del mismo. Para obtener más información, consulta "[Crear una confirmación con co-autores múltiples](/articles/creating-a-commit-with-multiple-authors)". ![Mensaje de confirmación de tu cambio](/assets/images/help/repository/write-commit-message-quick-pull.png) diff --git a/translations/es-XL/data/reusables/gated-features/actions.md b/translations/es-XL/data/reusables/gated-features/actions.md deleted file mode 100644 index 30a9ce246b..0000000000 --- a/translations/es-XL/data/reusables/gated-features/actions.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_actions %} se encuentra disponible con {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_one %}. {% data variables.product.prodname_actions %} no se encuentra disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/allowed-ip-addresses.md b/translations/es-XL/data/reusables/gated-features/allowed-ip-addresses.md deleted file mode 100644 index 760ca3ba5e..0000000000 --- a/translations/es-XL/data/reusables/gated-features/allowed-ip-addresses.md +++ /dev/null @@ -1 +0,0 @@ -Las direcciones IP permitidas están disponibles con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)". diff --git a/translations/es-XL/data/reusables/gated-features/autolinks.md b/translations/es-XL/data/reusables/gated-features/autolinks.md deleted file mode 100644 index 92ed5a834f..0000000000 --- a/translations/es-XL/data/reusables/gated-features/autolinks.md +++ /dev/null @@ -1 +0,0 @@ -Los autoenlaces se encuentran disponibles en repositorios con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/branch-restrictions.md b/translations/es-XL/data/reusables/gated-features/branch-restrictions.md deleted file mode 100644 index 3114fe094a..0000000000 --- a/translations/es-XL/data/reusables/gated-features/branch-restrictions.md +++ /dev/null @@ -1 +0,0 @@ -Las ramas protegidas se encuentran disponibles en los repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en los repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}. La capacidad de restringir ramas es un tipo de protección de rama que está disponible para los repositorios públicos y privados propiedad de organizaciones en el {% data variables.product.prodname_team %}, la {% data variables.product.prodname_ghe_cloud %} y el {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/code-owners.md b/translations/es-XL/data/reusables/gated-features/code-owners.md deleted file mode 100644 index 5ea7086201..0000000000 --- a/translations/es-XL/data/reusables/gated-features/code-owners.md +++ /dev/null @@ -1 +0,0 @@ -Puedes definir a los propietarios del código en repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en repositorios privados y públicos con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/code-review-assignment.md b/translations/es-XL/data/reusables/gated-features/code-review-assignment.md deleted file mode 100644 index c60ebc77d2..0000000000 --- a/translations/es-XL/data/reusables/gated-features/code-review-assignment.md +++ /dev/null @@ -1 +0,0 @@ -La tarea de revisión de código se encuentra disponible con {% data variables.product.prodname_team %}{% if currentVersion ver_gt "enterprise-server@2.19" %}, {% data variables.product.prodname_ghe_server %} 2.20+, {% endif %} y{% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-XL/data/reusables/gated-features/display-names.md b/translations/es-XL/data/reusables/gated-features/display-names.md deleted file mode 100644 index 795924c123..0000000000 --- a/translations/es-XL/data/reusables/gated-features/display-names.md +++ /dev/null @@ -1 +0,0 @@ -Permitir que los miembros vean los nombres de perfil en los autores de comentarios se encuentra disponible con {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.18+, y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-XL/data/reusables/gated-features/draft-prs.md b/translations/es-XL/data/reusables/gated-features/draft-prs.md deleted file mode 100644 index 0379025602..0000000000 --- a/translations/es-XL/data/reusables/gated-features/draft-prs.md +++ /dev/null @@ -1 +0,0 @@ -Draft pull requests are available in public repositories with {% data variables.product.prodname_free_team %} for organizations and legacy per-repository billing plans, and in public and private repositories with {% data variables.product.prodname_team %}{% if currentVersion != "free-pro-team@latest" %}, {% data variables.product.prodname_ghe_server %} 2.17+,{% endif %} and {% data variables.product.prodname_ghe_cloud %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/enterprise-accounts.md b/translations/es-XL/data/reusables/gated-features/enterprise-accounts.md deleted file mode 100644 index 46b23ca02f..0000000000 --- a/translations/es-XL/data/reusables/gated-features/enterprise-accounts.md +++ /dev/null @@ -1 +0,0 @@ -Las cuentas empresariales se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Acerca de las cuentas empresariales](/articles/about-enterprise-accounts)".{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/enterprise_account_webhooks.md b/translations/es-XL/data/reusables/gated-features/enterprise_account_webhooks.md deleted file mode 100644 index 80fd10b342..0000000000 --- a/translations/es-XL/data/reusables/gated-features/enterprise_account_webhooks.md +++ /dev/null @@ -1,4 +0,0 @@ - -{% data reusables.gated-features.enterprise-accounts %} - -Los webhooks que se configuraron en cuentas u organizaciones empresariales y que son parte de una cuenta empresarial incluirán un objeto de cuenta de `enterprise`. diff --git a/translations/es-XL/data/reusables/gated-features/github-insights.md b/translations/es-XL/data/reusables/gated-features/github-insights.md deleted file mode 100644 index 5f07e45586..0000000000 --- a/translations/es-XL/data/reusables/gated-features/github-insights.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_insights %} se encuentra disponible con {% data variables.product.prodname_ghe_one %}. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/githubs-products)". diff --git a/translations/es-XL/data/reusables/gated-features/internal-repos.md b/translations/es-XL/data/reusables/gated-features/internal-repos.md deleted file mode 100644 index 5a367298ff..0000000000 --- a/translations/es-XL/data/reusables/gated-features/internal-repos.md +++ /dev/null @@ -1 +0,0 @@ -Los repositorios internos se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %} 2.20+. Para obtener más información, consulta la sección "Productos de GitHub". diff --git a/translations/es-XL/data/reusables/gated-features/more-info-org-products.md b/translations/es-XL/data/reusables/gated-features/more-info-org-products.md deleted file mode 100644 index 43430f219b..0000000000 --- a/translations/es-XL/data/reusables/gated-features/more-info-org-products.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta la sección "[Productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)".{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/more-info.md b/translations/es-XL/data/reusables/gated-features/more-info.md deleted file mode 100644 index 43430f219b..0000000000 --- a/translations/es-XL/data/reusables/gated-features/more-info.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}Para obtener más información, consulta la sección "[Productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)".{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/okta-team-sync.md b/translations/es-XL/data/reusables/gated-features/okta-team-sync.md deleted file mode 100644 index 66c6946bc3..0000000000 --- a/translations/es-XL/data/reusables/gated-features/okta-team-sync.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** La sincronización de equipos con Okta se encuentra actualmente en beta y está sujeta a cambios. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/gated-features/org-insights.md b/translations/es-XL/data/reusables/gated-features/org-insights.md deleted file mode 100644 index b1e47226f2..0000000000 --- a/translations/es-XL/data/reusables/gated-features/org-insights.md +++ /dev/null @@ -1 +0,0 @@ -Las perspectivas de organización se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "Productos de [{% data variables.product.prodname_dotcom %}](/articles/github-s-products)". diff --git a/translations/es-XL/data/reusables/gated-features/packages.md b/translations/es-XL/data/reusables/gated-features/packages.md deleted file mode 100644 index baa1748dfb..0000000000 --- a/translations/es-XL/data/reusables/gated-features/packages.md +++ /dev/null @@ -1,4 +0,0 @@ -{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 2.22, and {% data variables.product.prodname_ghe_one %}. -{% if currentVersion == "free-pro-team@latest" %} -
    {% data variables.product.prodname_registry %} no está disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. {% data variables.product.prodname_registry %} se encuentra disponible con {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} para organizaciones, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_one %}. {% data reusables.gated-features.more-info %} -{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/pages.md b/translations/es-XL/data/reusables/gated-features/pages.md deleted file mode 100644 index f98586530b..0000000000 --- a/translations/es-XL/data/reusables/gated-features/pages.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_pages %} se encuentra disponible en repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en repositorios privados y públicos con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/protected-branches.md b/translations/es-XL/data/reusables/gated-features/protected-branches.md deleted file mode 100644 index 79955d1cdb..0000000000 --- a/translations/es-XL/data/reusables/gated-features/protected-branches.md +++ /dev/null @@ -1 +0,0 @@ -Las ramas protegidas se encuentran disponibles en los repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en los repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/repository-insights.md b/translations/es-XL/data/reusables/gated-features/repository-insights.md deleted file mode 100644 index 96b3c3b1e0..0000000000 --- a/translations/es-XL/data/reusables/gated-features/repository-insights.md +++ /dev/null @@ -1 +0,0 @@ -La gráfica de perspectivas para este repositorio se encuentra disponible en repositorios públicos con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en repositorios públicos y privados con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}.{% if currentVersion == "free-pro-team@latest" %} Para obtener más información, consulta la sección "[Acerca de las gráficas de repositorio](/articles/about-repository-graphs)" y "[Productos de {% data variables.product.prodname_dotcom %}](/articles/github-s-products)".{% endif %} diff --git a/translations/es-XL/data/reusables/gated-features/restict-add-collaborator.md b/translations/es-XL/data/reusables/gated-features/restict-add-collaborator.md deleted file mode 100644 index 5d493a9bd7..0000000000 --- a/translations/es-XL/data/reusables/gated-features/restict-add-collaborator.md +++ /dev/null @@ -1 +0,0 @@ -La restricción de la capacidad para agregar colaboradores externos a los propietarios se encuentra disponible con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-XL/data/reusables/gated-features/restrict-email-domain.md b/translations/es-XL/data/reusables/gated-features/restrict-email-domain.md deleted file mode 100644 index 143ae6d021..0000000000 --- a/translations/es-XL/data/reusables/gated-features/restrict-email-domain.md +++ /dev/null @@ -1 +0,0 @@ -La restricción de notificaciones por correo electrónico para el correo del dominio se encuentra disponible con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-XL/data/reusables/gated-features/saml-sso.md b/translations/es-XL/data/reusables/gated-features/saml-sso.md deleted file mode 100644 index 51b1872fed..0000000000 --- a/translations/es-XL/data/reusables/gated-features/saml-sso.md +++ /dev/null @@ -1 +0,0 @@ -El inicio de sesión único de SAML se encuentra disponible con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-XL/data/reusables/gated-features/ssh-certificate-authorities.md b/translations/es-XL/data/reusables/gated-features/ssh-certificate-authorities.md deleted file mode 100644 index 780fba2e1c..0000000000 --- a/translations/es-XL/data/reusables/gated-features/ssh-certificate-authorities.md +++ /dev/null @@ -1 +0,0 @@ -El soporte para las autoridades con certificado SSH se encuentra disponible con {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %} 2.19+. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-XL/data/reusables/gated-features/team-synchronization.md b/translations/es-XL/data/reusables/gated-features/team-synchronization.md deleted file mode 100644 index 7f86941bf2..0000000000 --- a/translations/es-XL/data/reusables/gated-features/team-synchronization.md +++ /dev/null @@ -1 +0,0 @@ -La sincronización de equipos se encuentra disponible para cuentas organizacionales y empresariales que que utilicen {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/es-XL/data/reusables/gated-features/user-repo-collaborators.md b/translations/es-XL/data/reusables/gated-features/user-repo-collaborators.md deleted file mode 100644 index 0811bb65bf..0000000000 --- a/translations/es-XL/data/reusables/gated-features/user-repo-collaborators.md +++ /dev/null @@ -1 +0,0 @@ -Si estás utilizando {% data variables.product.prodname_free_user %}, puedes agregar colaboradores ilimitados en repositorios públicos y privados. diff --git a/translations/es-XL/data/reusables/gated-features/wikis.md b/translations/es-XL/data/reusables/gated-features/wikis.md deleted file mode 100644 index bf211c8701..0000000000 --- a/translations/es-XL/data/reusables/gated-features/wikis.md +++ /dev/null @@ -1 +0,0 @@ -Los Wikis se encuentran disponibles en repositorios públicos y privados con {% data variables.product.prodname_free_user %} y {% data variables.product.prodname_free_team %} para organizaciones, y en repositorios privados y públicos con {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, y {% data variables.product.prodname_ghe_server %}. {% if currentVersion == "free-pro-team@latest" %}{% data reusables.gated-features.more-info %}{% endif %} diff --git a/translations/es-XL/data/reusables/gist/anonymous-gists-cannot-be-deleted.md b/translations/es-XL/data/reusables/gist/anonymous-gists-cannot-be-deleted.md deleted file mode 100644 index 7885e269a6..0000000000 --- a/translations/es-XL/data/reusables/gist/anonymous-gists-cannot-be-deleted.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} -{% warning %} - -**Advertencia:** Los gists anónimos no pueden borrarse del buscador web. Para borrar un gist anónimo, contacta a {% data variables.contact.contact_support %}. Por favor proporciona la URL del gist que deseas borrar. - -{% endwarning %} -{% endif %} diff --git a/translations/es-XL/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/es-XL/data/reusables/gist/cannot-convert-public-gists-to-secret.md deleted file mode 100644 index 709decf653..0000000000 --- a/translations/es-XL/data/reusables/gist/cannot-convert-public-gists-to-secret.md +++ /dev/null @@ -1 +0,0 @@ -Luego de crear un gist, no puedes convertirlo para que deje de ser público y se vuelva secreto. diff --git a/translations/es-XL/data/reusables/git/commit-file.md b/translations/es-XL/data/reusables/git/commit-file.md deleted file mode 100644 index 3f12e264de..0000000000 --- a/translations/es-XL/data/reusables/git/commit-file.md +++ /dev/null @@ -1 +0,0 @@ -1. Confirma el archivo que has preparado en tu repositorio local. diff --git a/translations/es-XL/data/reusables/git/git-push.md b/translations/es-XL/data/reusables/git/git-push.md deleted file mode 100644 index 6ede19c30d..0000000000 --- a/translations/es-XL/data/reusables/git/git-push.md +++ /dev/null @@ -1,5 +0,0 @@ -1. [Sube los cambios](/articles/pushing-commits-to-a-remote-repository/) en tu repositorio local a {% data variables.product.product_location %}. - ```shell - $ git push origin your-branch - # Pushes the changes in your local repository up to the remote repository you specified as the origin - ``` diff --git a/translations/es-XL/data/reusables/git/remove-git-remote.md b/translations/es-XL/data/reusables/git/remove-git-remote.md deleted file mode 100644 index cf1a48f2a1..0000000000 --- a/translations/es-XL/data/reusables/git/remove-git-remote.md +++ /dev/null @@ -1,10 +0,0 @@ -1. Con la línea de comandos, elimina cualquier remoto de git que se encuentre actualmente configurado para el repositorio. - - ```shell - # Show existing remotes - $ git remote -v - > origin git@git-server/octocat/hello-world.git (fetch) - > origin git@git-server/octocat/hello-world.git (push) - # Remove existing remotes - $ git remote remove origin - ``` diff --git a/translations/es-XL/data/reusables/git/reset-head-to-previous-commit-codeblock.md b/translations/es-XL/data/reusables/git/reset-head-to-previous-commit-codeblock.md deleted file mode 100644 index 9b2be3228c..0000000000 --- a/translations/es-XL/data/reusables/git/reset-head-to-previous-commit-codeblock.md +++ /dev/null @@ -1 +0,0 @@ -Para eliminar esta confirmación y modificar el archivo, usa 'git reset --soft HEAD~1' y confirma y agrega nuevamente el archivo. diff --git a/translations/es-XL/data/reusables/git/stage_for_commit.md b/translations/es-XL/data/reusables/git/stage_for_commit.md deleted file mode 100644 index c0c6e98f70..0000000000 --- a/translations/es-XL/data/reusables/git/stage_for_commit.md +++ /dev/null @@ -1 +0,0 @@ -1. Prepara el archivo para confirmarlo para tu repositorio local. diff --git a/translations/es-XL/data/reusables/git/unstage-codeblock.md b/translations/es-XL/data/reusables/git/unstage-codeblock.md deleted file mode 100644 index 45204f439f..0000000000 --- a/translations/es-XL/data/reusables/git/unstage-codeblock.md +++ /dev/null @@ -1 +0,0 @@ -Para deshacer un archivo, usa 'git reset HEAD YOUR-FILE'. diff --git a/translations/es-XL/data/reusables/github-actions/actions-billing.md b/translations/es-XL/data/reusables/github-actions/actions-billing.md deleted file mode 100644 index 73fe10cf10..0000000000 --- a/translations/es-XL/data/reusables/github-actions/actions-billing.md +++ /dev/null @@ -1 +0,0 @@ -El uso de {% data variables.product.prodname_actions %} es gratuito para los repositorios públicos. Para los repositorios privados, cada cuenta de {% data variables.product.prodname_dotcom %} recibe una cantidad determinada de minutos y almacenamiento gratuitos dependiendo del producto que se utilice con la cuenta. diff --git a/translations/es-XL/data/reusables/github-actions/actions-do-not-trigger-workflows.md b/translations/es-XL/data/reusables/github-actions/actions-do-not-trigger-workflows.md deleted file mode 100644 index db22e0daad..0000000000 --- a/translations/es-XL/data/reusables/github-actions/actions-do-not-trigger-workflows.md +++ /dev/null @@ -1 +0,0 @@ -Cuando utilizas el `GITHUB_TOKEN` del repositorio para realizar tareas por parte de la app de {% data variables.product.prodname_actions %}, los eventos que `GITHUB_TOKEN` desencadena no crearán una ejecución de flujo de trabajo. Esto impide que crees ejecuciones de flujo de trabajo recursivas por accidente. Por ejemplo, si un flujo de trabajo sube código utilizando el `GITHUB_TOKEN` del repositorio, no se ejecutará un nuevo flujo de trabajo aún si el repositorio contiene alguno configurado para ejecutarse cuando ocurran eventos de `subida` de información. diff --git a/translations/es-XL/data/reusables/github-actions/actions-on-examples.md b/translations/es-XL/data/reusables/github-actions/actions-on-examples.md deleted file mode 100644 index bbd4bef292..0000000000 --- a/translations/es-XL/data/reusables/github-actions/actions-on-examples.md +++ /dev/null @@ -1,34 +0,0 @@ -##### **Ejemplo con un solo evento** - -```yaml -# Trigger on push -on: push -``` - -##### **Ejemplo con una lista de eventos** - -```yaml -# Trigger the workflow on push or pull request -on: [push, pull_request] -``` - -##### **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. - -```yaml -on: - # Trigger the workflow on push or pull request, - # but only for the master branch - push: - branches: - - master - pull_request: - branches: - - master - # Also trigger on page_build, as well as release created events - page_build: - release: - types: # This configuration does not affect the page_build event above - - created -``` diff --git a/translations/es-XL/data/reusables/github-actions/actions-spending-limit.md b/translations/es-XL/data/reusables/github-actions/actions-spending-limit.md deleted file mode 100644 index 11b904dde1..0000000000 --- a/translations/es-XL/data/reusables/github-actions/actions-spending-limit.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, tu cuenta tendrá un límite de gastos de $0, lo cual previene el uso adicional de minutos o almacenamiento después de que llegues a estos límites. Si incrementas tu límite de gastos por encima del predeterminado de $0, se te facturará por cualquier cantidad de minutos o almacenamiento que rebase los límites, también llamados excedentes. {% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenezca el repositorio en donde se ejecuta el 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-XL/data/reusables/github-actions/actions-unused-labels.md b/translations/es-XL/data/reusables/github-actions/actions-unused-labels.md deleted file mode 100644 index e83f8b8df5..0000000000 --- a/translations/es-XL/data/reusables/github-actions/actions-unused-labels.md +++ /dev/null @@ -1 +0,0 @@ - Cualquier etiqueta sin utilizar que no se asigne a un ejecutor se borrará automáticamente dentro de 24 horas. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/branch-requirement.md b/translations/es-XL/data/reusables/github-actions/branch-requirement.md deleted file mode 100644 index 88c3edc642..0000000000 --- a/translations/es-XL/data/reusables/github-actions/branch-requirement.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Este evento solo desencadenará una ejecución de flujo de trabajo si el archivo de dicho flujo se encuentra en la rama `master` o en la predeterminada. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/github-actions/contacting-support.md b/translations/es-XL/data/reusables/github-actions/contacting-support.md deleted file mode 100644 index af04edd36a..0000000000 --- a/translations/es-XL/data/reusables/github-actions/contacting-support.md +++ /dev/null @@ -1,9 +0,0 @@ -Si necesitas ayuda con cualquier asunto relacionado a la configuración de flujos de trabajo, tal como la sintaxis, ejecutores hospedados en {% data variables.product.prodname_dotcom %}, o acciones de construcción, busca un tema existente o inicia uno nuevo en el [tablero de {% data variables.product.prodname_actions %} de {% data variables.product.prodname_gcf %}](https://github.community/c/github-actions). - -Si tienes algún tipo de retroalimentación o solicitudes de características para {% data variables.product.prodname_actions %}, compártelas en el {% data variables.contact.contact_feedback_actions %}. - -Contacta a {% data variables.contact.contact_support %} para cualquiera de los siguientes, que tu tipo de uso o el tipo de uso que pretendes tener caiga en las siguientes categorías de limitación: - -* Si crees que tu cuenta se ha restringido de manera incorrecta -* Si llegas un error inesperado cuando ejecutas una de tus acciones, por ejemplo: una ID única -* Si llegas a una situación en donde el comportamiento existente contradice a aquél que se espera, pero no siempre se documenta diff --git a/translations/es-XL/data/reusables/github-actions/container-jobs-intro.md b/translations/es-XL/data/reusables/github-actions/container-jobs-intro.md deleted file mode 100644 index 2429ae39ff..0000000000 --- a/translations/es-XL/data/reusables/github-actions/container-jobs-intro.md +++ /dev/null @@ -1 +0,0 @@ -La configuración de jobs para su ejecución en un contenedor simplifica las configuraciones de red entre el job y los contenedores de servicio. Los contenedores de Docker en el mismo puente de red definido por el usuario exponen todos los puertos entre ellos, así que no necesitas mapear ninguno de los puertos para contenedores de servicio en el alojamiento de Docker. Puedes acceder al contenedor de servicio desde el contenedor del job utilizando la etiqueta que configuras en el flujo de trabajo. diff --git a/translations/es-XL/data/reusables/github-actions/copy-workflow-file.md b/translations/es-XL/data/reusables/github-actions/copy-workflow-file.md deleted file mode 100644 index 56754f5d09..0000000000 --- a/translations/es-XL/data/reusables/github-actions/copy-workflow-file.md +++ /dev/null @@ -1 +0,0 @@ -Puedes copiar este archivo de flujo de trabajo al directorio `.github/workflows` de tu repositorio y modificarlo como lo requieras. diff --git a/translations/es-XL/data/reusables/github-actions/defaults-override.md b/translations/es-XL/data/reusables/github-actions/defaults-override.md deleted file mode 100644 index bdb030a76a..0000000000 --- a/translations/es-XL/data/reusables/github-actions/defaults-override.md +++ /dev/null @@ -1 +0,0 @@ -Cuando se define más de una configuración predeterminada con el mismo nombre, {% data variables.product.prodname_dotcom %} utiliza la configuración predeterminada más específica. Por ejemplo, una configuración predeterminada definida en un job invalidará a aquella que tenga el mismo nombre definido en el flujo de trabajo. diff --git a/translations/es-XL/data/reusables/github-actions/disabled-actions-description.md b/translations/es-XL/data/reusables/github-actions/disabled-actions-description.md deleted file mode 100644 index 9a9ea1bc35..0000000000 --- a/translations/es-XL/data/reusables/github-actions/disabled-actions-description.md +++ /dev/null @@ -1 +0,0 @@ -Cuando inhabilitas a {% data variables.product.prodname_actions %}, no se ejecuta ningún flujo de trabajo en tu repositorio. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/disabling-github-actions.md b/translations/es-XL/data/reusables/github-actions/disabling-github-actions.md deleted file mode 100644 index e3dde15b13..0000000000 --- a/translations/es-XL/data/reusables/github-actions/disabling-github-actions.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, {% data variables.product.prodname_actions %} se encuentra habilitado 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. diff --git a/translations/es-XL/data/reusables/github-actions/docker-container-os-support.md b/translations/es-XL/data/reusables/github-actions/docker-container-os-support.md deleted file mode 100644 index 2a60ca6fac..0000000000 --- a/translations/es-XL/data/reusables/github-actions/docker-container-os-support.md +++ /dev/null @@ -1,8 +0,0 @@ -{% note %} - -**Nota:** Si tus flujos de trabajo utilizan acciones de contenedor de Docker o contenedores de servicio, entonces debes utilizar un ejecutor de Linux: - -* Si estás utilizando ejecutores hospedados en {% data variables.product.prodname_dotcom %}, debes utilizar el ejecutor `ubuntu-latest`. -* Si estás utilizando ejecutores auto-hospedados, debes utilizar una máquina Linux como tu ejecutor, y ésta debe tener Docker instalado. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/github-actions/docker-tag-with-ref.md b/translations/es-XL/data/reusables/github-actions/docker-tag-with-ref.md deleted file mode 100644 index 98f196a16b..0000000000 --- a/translations/es-XL/data/reusables/github-actions/docker-tag-with-ref.md +++ /dev/null @@ -1 +0,0 @@ -El flujo de trabajo anterior verifica el repositorio {% data variables.product.prodname_dotcom %} y utiliza la acción `build-push-action` para construir y subir la imagen de Docker. Éste configura la opción [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) de `build-push-action` para que etiquete automáticamente la imagen construida de Docker con la referencia de Git del evento del flujo de trabajo. Este flujo de trabajo se desencadena cuando se publica un lanzamiento de {% data variables.product.prodname_dotcom %}, para que la referencia sea la etiqueta de Git para el lanzamiento. diff --git a/translations/es-XL/data/reusables/github-actions/dockerfile-guidelines.md b/translations/es-XL/data/reusables/github-actions/dockerfile-guidelines.md deleted file mode 100644 index b59d70cc4a..0000000000 --- a/translations/es-XL/data/reusables/github-actions/dockerfile-guidelines.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Los documentos requerían argumentos en el README de las acciones y las omiten desde la instrucción `CMD`. -1. Usa los valores predeterminados que permiten usar la acción sin especificar ningún `args`. -1. Si la acción expone una marca de `--help`, o algo similar, utilízala para hacer tu propia documentación de la acción. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/enabled-actions-description.md b/translations/es-XL/data/reusables/github-actions/enabled-actions-description.md deleted file mode 100644 index 520ba655d2..0000000000 --- a/translations/es-XL/data/reusables/github-actions/enabled-actions-description.md +++ /dev/null @@ -1 +0,0 @@ -Cuando habilitas {% data variables.product.prodname_actions %}, los flujos de trabajo puede ejecutar acciones ubicadas dentro de tu repositorio y en cualquier otro repositorio público. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/enabled-local-github-actions.md b/translations/es-XL/data/reusables/github-actions/enabled-local-github-actions.md deleted file mode 100644 index 042f0aeea2..0000000000 --- a/translations/es-XL/data/reusables/github-actions/enabled-local-github-actions.md +++ /dev/null @@ -1 +0,0 @@ -Cuando habilitas únicamente las acciones locales, los flujos de trabajo solo pueden ejecutar acciones ubicadas en tu repositorio u organización. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/enterprise-billing-details.md b/translations/es-XL/data/reusables/github-actions/enterprise-billing-details.md deleted file mode 100644 index 1ae7ee4dfd..0000000000 --- a/translations/es-XL/data/reusables/github-actions/enterprise-billing-details.md +++ /dev/null @@ -1 +0,0 @@ -El uso incluye los minutos totales que utiliza cada organización. El resumen combinado de {% data variables.product.prodname_actions %} y {% data variables.product.prodname_registry %} no lista los minutos incluidos, minutos pagados, o un estimado de precio por GB de almacenamiento. diff --git a/translations/es-XL/data/reusables/github-actions/example-github-runner.md b/translations/es-XL/data/reusables/github-actions/example-github-runner.md deleted file mode 100644 index 84a1b53787..0000000000 --- a/translations/es-XL/data/reusables/github-actions/example-github-runner.md +++ /dev/null @@ -1,19 +0,0 @@ -### Ejecución en un sistema operativo diferente - -La plantilla inicial de flujo de trabajo configura los jobs para que se ejecuten en Linux, utilizando los ejecutores `ubuntu-latest` hospedados en {% data variables.product.prodname_dotcom %}. Puedes cambiar la clave `runs-on` para ejecutar tus jobs en un sistema operativo diferente. Por ejemplo, puedes utilizar los ejecutores de Windows hospedados en {% data variables.product.prodname_dotcom %}. - -{% raw %} -```yaml -runs-on: windows-latest -``` -{% endraw %} - -O puedes utilizar los ejecutores de macOS hospedados en {% data variables.product.prodname_dotcom %}. - -{% raw %} -```yaml -runs-on: macos-latest -``` -{% endraw %} - -También puedes ejecutar jobs en contenedores de Docker, o puedes proporcionar un ejecutor auto-hospedado que se ejecute en tu propia infraestructura. Para obtener más información, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)". diff --git a/translations/es-XL/data/reusables/github-actions/expression-syntax-if.md b/translations/es-XL/data/reusables/github-actions/expression-syntax-if.md deleted file mode 100644 index e0f6cf8414..0000000000 --- a/translations/es-XL/data/reusables/github-actions/expression-syntax-if.md +++ /dev/null @@ -1 +0,0 @@ -Podrías omitir la sintaxis de expresión cuando utilizas expresiones en un condicional `if` ({% raw %}`${{ }}`{% endraw %}) ya que {% data variables.product.prodname_dotcom %} evalúa automáticamente el condicional `if` como una expresión. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/github-context-warning.md b/translations/es-XL/data/reusables/github-actions/github-context-warning.md deleted file mode 100644 index 709fae57c8..0000000000 --- a/translations/es-XL/data/reusables/github-actions/github-context-warning.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Advertencia:** Cuando utilizas todo el contexto de `GitHub`, cuida que incluya la información sensible tal como un `github.token`. {% data variables.product.prodname_dotcom %} enmascara secretos cuando se imprimen en la consola, pero debes tener cuidado cuando exportes o imprimas el contexto. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/github-actions/gradle-workflow-steps.md b/translations/es-XL/data/reusables/github-actions/gradle-workflow-steps.md deleted file mode 100644 index 70ea3d62d6..0000000000 --- a/translations/es-XL/data/reusables/github-actions/gradle-workflow-steps.md +++ /dev/null @@ -1,4 +0,0 @@ -Este flujo de trabajo realiza los siguientes pasos: - -1. Revisa una copia del repositorio del proyecto. -1. Configura el JDK de Java. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/invalid-workflow-files.md b/translations/es-XL/data/reusables/github-actions/invalid-workflow-files.md deleted file mode 100644 index 942d9bf642..0000000000 --- a/translations/es-XL/data/reusables/github-actions/invalid-workflow-files.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Garantiza que solo confirmes los archivos de flujo de trabajo válidos en tu repositorio. Si `.github/workflows` contiene un archivo de flujo de trabajo inválido, {% data variables.product.prodname_actions %} generará una ejecución de flujo de trabajo fallida por cada confirmación nueva. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md b/translations/es-XL/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md deleted file mode 100644 index 48147e94cf..0000000000 --- a/translations/es-XL/data/reusables/github-actions/ip-allow-list-self-hosted-runners.md +++ /dev/null @@ -1,7 +0,0 @@ -{% warning %} - -**Advertencia**: Si utilzas una lista de IP permitidas y también quisieras utilizar {% data variables.product.prodname_actions %}, debes usar los ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Hospedar tus propios ejecutores](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)". - -{% endwarning %} - -Para permitir que los ejecutores auto-hospedados se comuniquen con {% data variables.product.prodname_dotcom %}, agrega la dirección o rango de direcciones IP de tus ejecutores auto-hospedados a la lista de IP permitidas. Para obtener más información, consulta "[Agregar una dirección IP permitida](#adding-an-allowed-ip-address)". diff --git a/translations/es-XL/data/reusables/github-actions/java-jvm-architecture.md b/translations/es-XL/data/reusables/github-actions/java-jvm-architecture.md deleted file mode 100644 index 86c5d9e0c0..0000000000 --- a/translations/es-XL/data/reusables/github-actions/java-jvm-architecture.md +++ /dev/null @@ -1,19 +0,0 @@ -### Especificar la versión y arquitectura de JVM - -La plantilla inicial de flujo de trabajo configura el `PATH` para que contenga OpenJDK 8 para las plataformas x64. Si quieres utilizar una versión diferente de Java, o enfocarte en una arquitectura diferente (`x64` o `x86`), puedes utilizar la acción `setup-java` para elegir un ambiente de ejecución de Java diferente. - -Por ejemplo, para utilizar la versión 9.0.4 del JDK para una plataforma x64, puedes utilizar la acción `setup-java` y configurar los parámetros `java-version` y `architecture` en `'9.0.4'` y `x64`. - -{% raw %} -```yaml -steps: - - uses: actions/checkout@v2 - - name: Set up JDK 9.0.4 for x64 - uses: actions/setup-java@v1 - with: - java-version: '9.0.4' - architecture: x64 -``` -{% endraw %} - -Para obtener más información, consulta la acción [`setup-java`](https://github.com/actions/setup-java). diff --git a/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-api.md b/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-api.md deleted file mode 100644 index e00d702fbe..0000000000 --- a/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-api.md +++ /dev/null @@ -1 +0,0 @@ -Para crear secretos utilizando la API de REST, deberás contar con acceso de escritura al repositorio. Para obtener más información, consulta la sección "[ API de secretos de {% data variables.product.prodname_actions %}](/v3/actions/secrets/)". diff --git a/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-organization.md b/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-organization.md deleted file mode 100644 index aab3a5ce5e..0000000000 --- a/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-organization.md +++ /dev/null @@ -1 +0,0 @@ -Para crear secretos a nivel organizacional, deberás tener acceso de `administrador`. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-repository.md b/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-repository.md deleted file mode 100644 index b791c730e3..0000000000 --- a/translations/es-XL/data/reusables/github-actions/permissions-statement-secrets-repository.md +++ /dev/null @@ -1 +0,0 @@ -Para crear secretos para un repositorio de una cuenta de usuario, deberás ser el propietario de éste. Para crear secretos para un repositorio de una organización, deberás tener acceso de `administrador`. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/postgres-environment-variables.md b/translations/es-XL/data/reusables/github-actions/postgres-environment-variables.md deleted file mode 100644 index 9d124b14a9..0000000000 --- a/translations/es-XL/data/reusables/github-actions/postgres-environment-variables.md +++ /dev/null @@ -1 +0,0 @@ -El script *client.js* busca las variables del ambiente de `POSTGRES_HOST` y `POSTGRES_PORT` para crear al cliente. El flujo de trabajo configura estas dos variables de ambiente como parte del paso "Conectar a PostgreSQL" para hacerlos disponibles para el script *client.js*. Para obtener más información acerca del script, consulta "[Probar el contenedor de servicio de PostgreSQL](#testing-the-postgresql-service-container)". diff --git a/translations/es-XL/data/reusables/github-actions/postgres-label-description.md b/translations/es-XL/data/reusables/github-actions/postgres-label-description.md deleted file mode 100644 index ee5193d9af..0000000000 --- a/translations/es-XL/data/reusables/github-actions/postgres-label-description.md +++ /dev/null @@ -1 +0,0 @@ -El flujo de trabajo configura un contenedor de servicio con la etiqueta `postgres`. Todos los servicios se deben ejecutar en un contenedor, entonces cada servicio requiere que especifiques la `image` del mismo. Este ejemplo utiliza la imagen del contenedor `postgres`, proporciona la cotraseña predeterminada de PostgreSQL, e incluye las opciones de revisión de estado para garantizar que el servicio se está ejecutando. Para obtener más información, consulta la [imagen de postgre](https://hub.docker.com/_/postgres) en Docker Hub. diff --git a/translations/es-XL/data/reusables/github-actions/private-repository-forks-configure.md b/translations/es-XL/data/reusables/github-actions/private-repository-forks-configure.md deleted file mode 100644 index f7eb90543f..0000000000 --- a/translations/es-XL/data/reusables/github-actions/private-repository-forks-configure.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de **Bifurcar los flujos de trabajo de la solicitud de extracción**, selecciona tus opciones. Por ejemplo: ![Habilita, inhabilita o limita las acciones para este repositorio](/assets/images/help/settings/actions-fork-pull-request-workflows.png) -1. Da clic en **Guardar** para aplicar la configuración. diff --git a/translations/es-XL/data/reusables/github-actions/private-repository-forks-overview.md b/translations/es-XL/data/reusables/github-actions/private-repository-forks-overview.md deleted file mode 100644 index 0812de3d4d..0000000000 --- a/translations/es-XL/data/reusables/github-actions/private-repository-forks-overview.md +++ /dev/null @@ -1,5 +0,0 @@ -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 repositories only, you can configure these policy settings for enterprise accounts, organizations, or repositories. 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. -- **Enviar secretos a los flujos de trabajo desde las solicitudes de extracción** - Pone disponibles todos los secretos de la solicitud de extracción. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/publish-to-maven-workflow-step.md b/translations/es-XL/data/reusables/github-actions/publish-to-maven-workflow-step.md deleted file mode 100644 index 49e92d34ed..0000000000 --- a/translations/es-XL/data/reusables/github-actions/publish-to-maven-workflow-step.md +++ /dev/null @@ -1 +0,0 @@ -Ejecuta el comando `mvn -B deploy` para publicar el repositorio `ossrh`. La variable de entorno `MAVEN_USERNAME` se establecerá con los contenidos de tu `OSSRH_USERNAME` secreto, y la variable de entorno `MAVEN_PASSWORD` se establecerá con los contenidos de tu `OSSRH_TOKEN` secreto. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/publish-to-packages-workflow-step.md b/translations/es-XL/data/reusables/github-actions/publish-to-packages-workflow-step.md deleted file mode 100644 index 6362c1a114..0000000000 --- a/translations/es-XL/data/reusables/github-actions/publish-to-packages-workflow-step.md +++ /dev/null @@ -1 +0,0 @@ -Ejecuta el comando `mvn -B deploy` para publicar en {% data variables.product.prodname_registry %}. La variable de ambiente `GITHUB_TOKEN` se configurará con el contenido del secreto `GITHUB_TOKEN`. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/publishing-java-packages-intro.md b/translations/es-XL/data/reusables/github-actions/publishing-java-packages-intro.md deleted file mode 100644 index ee09e51c12..0000000000 --- a/translations/es-XL/data/reusables/github-actions/publishing-java-packages-intro.md +++ /dev/null @@ -1 +0,0 @@ -Esta guía te muestra cómo crear un flujo de trabajo que publique paquetes de Java en {% data variables.product.prodname_registry %} y en el Repositorio Central de Maven. Con un solo flujo de trabajo, puedes publicar los paquetes en un solo repositorio o en varios repositorios. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/pure-javascript.md b/translations/es-XL/data/reusables/github-actions/pure-javascript.md deleted file mode 100644 index a69d63d0bd..0000000000 --- a/translations/es-XL/data/reusables/github-actions/pure-javascript.md +++ /dev/null @@ -1 +0,0 @@ -Para garantizar que tus acciones de JavaScript son compatibles con todos los ejecutores hospedados en GitHub (Ubuntu, Windows, y macOS), el código empaquetado de JavaScript que escribas debe ser puramente JavaScript y no depender de otros binarios. Las acciones de JavaScript se ejecutan directamente en el ejecutor y utiliza binarios que ya existen en el ambiente virtual. diff --git a/translations/es-XL/data/reusables/github-actions/redis-environment-variables.md b/translations/es-XL/data/reusables/github-actions/redis-environment-variables.md deleted file mode 100644 index 22bed48823..0000000000 --- a/translations/es-XL/data/reusables/github-actions/redis-environment-variables.md +++ /dev/null @@ -1 +0,0 @@ -El script *client.js* busca las variables de ambiente `REDIS_HOST` y `REDIS_PORT` para crear al cliente. El flujo de trabajo configura esas dos variables de ambiente como parte del paso "Connect to Redis" para hacerlas disponibles para el script *client.js*. Para obtener más información acerca del script, consulta la sección "[Probar el contenedor de servicio de Redis](#testing-the-redis-service-container)". diff --git a/translations/es-XL/data/reusables/github-actions/redis-label-description.md b/translations/es-XL/data/reusables/github-actions/redis-label-description.md deleted file mode 100644 index c13123527d..0000000000 --- a/translations/es-XL/data/reusables/github-actions/redis-label-description.md +++ /dev/null @@ -1 +0,0 @@ -El flujo de trabajo configura un contenedor de servicio con la etiqueta `reds`. Todos los servicios se deben ejecutar en un contenedor, entonces cada servicio requiere que especifiques la `image` del mismo. Este ejemplo utiliza la imagen del contenedor `redis`, e incluye opciones de verificación de estado para garantizar que el servicio se está ejecutando. Para obtener más información, consulta la [imagen de redis](https://hub.docker.com/_/redis) en Docker Hub. diff --git a/translations/es-XL/data/reusables/github-actions/release-trigger-workflow.md b/translations/es-XL/data/reusables/github-actions/release-trigger-workflow.md deleted file mode 100644 index 2e194c2adc..0000000000 --- a/translations/es-XL/data/reusables/github-actions/release-trigger-workflow.md +++ /dev/null @@ -1 +0,0 @@ -Cada vez que creas un nuevo lanzamiento en {% data variables.product.prodname_dotcom %}, puedes activar un flujo de trabajo para publicar tu imagen. El flujo de trabajo en el ejemplo siguiente se ejecuta cuando el se activa el evento `release` con el tipo de actividad `created`. Para obtener más información en el evento `release`, consulta la sección"[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#release). diff --git a/translations/es-XL/data/reusables/github-actions/run_id_description.md b/translations/es-XL/data/reusables/github-actions/run_id_description.md deleted file mode 100644 index 6e6f440116..0000000000 --- a/translations/es-XL/data/reusables/github-actions/run_id_description.md +++ /dev/null @@ -1 +0,0 @@ -Un número único para cada ejecución dentro de un repositorio. Este número no cambia si vuelves a ejecutar el flujo de trabajo. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/run_number_description.md b/translations/es-XL/data/reusables/github-actions/run_number_description.md deleted file mode 100644 index 73780cd878..0000000000 --- a/translations/es-XL/data/reusables/github-actions/run_number_description.md +++ /dev/null @@ -1 +0,0 @@ -Un número único para cada ejecución de un flujo de trabajo particular en un repositorio. Este número comienza en 1 para los flujos de trabajo que se ejecutan primero, e incrementa con cada ejecución nueva. Este número no cambia si vuelves a ejecutar el flujo de trabajo. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/runner-app-open-source.md b/translations/es-XL/data/reusables/github-actions/runner-app-open-source.md deleted file mode 100644 index 90e4ac2747..0000000000 --- a/translations/es-XL/data/reusables/github-actions/runner-app-open-source.md +++ /dev/null @@ -1 +0,0 @@ -La aplicación ejecutora de {% data variables.product.prodname_actions %} es de código abierto. Puedes contribuir y emitir informes de problemas en el repositorio [runner](https://github.com/actions/runner). diff --git a/translations/es-XL/data/reusables/github-actions/secrets-org-level-overview.md b/translations/es-XL/data/reusables/github-actions/secrets-org-level-overview.md deleted file mode 100644 index 931798da93..0000000000 --- a/translations/es-XL/data/reusables/github-actions/secrets-org-level-overview.md +++ /dev/null @@ -1 +0,0 @@ -Para los secretos almacenados a nivel organizacional, peudes utilizar las políticas de acceso para controlar qué repositorios pueden utilizar secretos organizacionales. Los secretos a nivel organizacional te permiten compartir secretos entre repositorios múltiples, lo cual reduce la necesidad de crear secretos duplicados. El actualizar un secreto de organización en una ubicación también garantiza que el cambio tome efecto en todos los flujos de trabajo del repositorio que lo utilicen. diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-auto-removal.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-auto-removal.md deleted file mode 100644 index d35854108b..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-auto-removal.md +++ /dev/null @@ -1 +0,0 @@ -Un ejecutor auto-hospedado se eliminará automáticamente de {% data variables.product.product_name %} si no se ha conectado a {% data variables.product.prodname_actions %} por más de 30 días. diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-check-installation-success.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-check-installation-success.md deleted file mode 100644 index 442edf5f31..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-check-installation-success.md +++ /dev/null @@ -1,10 +0,0 @@ - -#### Revisar que tu ejecutor auto-hospedado se haya agregado exitosamente - -Después de completar los pasos para agregar un ejecutor autoalojado, el ejecutor y su estado se enumeran ahora en "Self-hosted runners" (Ejecutores autoalojados). - -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. - -{% data reusables.github-actions.self-hosted-runner-connected-output %} - -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-XL/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md deleted file mode 100644 index c2c9b84e2a..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ /dev/null @@ -1,2 +0,0 @@ -1. En la sección de **Ejecutores auto-hospedados** de la página de configuración, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al grupo de ejecución que quieras configurar, luego da clic en **Editar nombre y acceso a la [organización|repositorio]**. ![Administrar permisos del repositorio](/assets/images/help/settings/actions-runner-manage-permissions.png) -1. Selecciona una política nueva de la lista desplegable o modifica el nombre del grupo ejecutor. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-configure.md deleted file mode 100644 index 02b7166c84..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-configure.md +++ /dev/null @@ -1,18 +0,0 @@ -1. Selecciona el sistema operativo y arquitectura de tu máquina de ejecutor auto-hospedado. ![Selecciona el sistema operativo del ejecutor autoalojado](/assets/images/help/settings/actions-runner-architecture-os.png) - - -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. - - {% note %} - - **Nota:** En Windows, si deseas instalar la aplicación del ejecutor autoalojado como un servicio, debes abrir un shell con privilegios de administrador. También recomendamos que uses `C:\actions-runner` como el directorio para la aplicación del ejecutor autoalojado de modo que las cuentas del sistema de Windows puedan acceder al directorio del ejecutor. - - {% endnote %} - - Las instrucciones te guían para completar estas tareas: - - Descargar y extraer la aplicación de ejecutor autoalojado. - - Ejecutar el script `config` para configurar la aplicación del ejecutor auto-hospedado y registrarlo con {% data variables.product.prodname_actions %}. El script `config` requiere la URL destino y un token de tiempo limitado generado automáticamente para autenticar la solicitud. - - En Windows, el script `config` también te pregunta si deseas instalar la aplicación del ejecutor autoalojado como un servicio. Para Linux y macOS, puedes instalar un servicio después de que termines de agregar el ejecutor. Para obtener más información, consulta "[Configurar la aplicación del ejecutor autoalojado como un servicio](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service)." - - Ejecutar la aplicación del ejecutor autoalojado para conectar la máquina a las {% data variables.product.prodname_actions %}. diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-connected-output.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-connected-output.md deleted file mode 100644 index 91b27bd97f..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-connected-output.md +++ /dev/null @@ -1,5 +0,0 @@ -```shell -√ Connected to GitHub - -2019-10-24 05:45:56Z: Listening for Jobs -``` diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-description.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-description.md deleted file mode 100644 index 8971b67554..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-description.md +++ /dev/null @@ -1 +0,0 @@ -Los ejecutores auto-hospedados ofrecen más control sobre las herramientas del hardware, sistema operativo y software que lo que ofrecen los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Con los ejecutores auto-hospedados, puedes elegir crear una configuración de hardware personalizada con más poder de procesamiento o más memoria para ejecutar jobs más grandes, instalar software disponible en tu red local, y escoger un sistema operativo que no se ofrezca en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md deleted file mode 100644 index 0b1919b9ba..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md +++ /dev/null @@ -1,3 +0,0 @@ -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. - -Todos los ejecutores auto-programados tienen la etiqueta `self-hosted` y puedes seleccionar cualquiera de ellos para proporcionar únicamente dicha etiqueta. Como alternativa, puedes utilizar `self-hosted` en un arreglo con etiquetas adicionales, tales como aquellas para un sistema operativo o arquitectura de sistema específicos, para seleccionar únicamente los tipos de ejecutor que especificas. diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md deleted file mode 100644 index a38f96f720..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-labels-view-assigned-labels.md +++ /dev/null @@ -1 +0,0 @@ -1. Ubica el ejecutor que quieres actualizar y da clic en {% octicon "triangle-down" aria-label="The downward triangle" %} para ver el menú de selección de etiquetas. Este menú muestra todas las etiquetas personalizadas disponibles para tu ejecutor auto-hospedado. Las etiquetas que ya hayas asignado a tu ejecutor auto-hospedado tienen un {% octicon "check" aria-label="Check mark" %} junto a ellas. ![Cambiar la etiqueta del ejecutor](/assets/images/help/settings/actions-runner-list-label.png) diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-list-group.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-list-group.md deleted file mode 100644 index 17332b0853..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-list-group.md +++ /dev/null @@ -1 +0,0 @@ -1. Si tu ejecutor está en un grupo, ubica el grupo ejecutor y da clic en {% octicon "chevron-down" aria-label="The downward chevron" %} para ver la lista de ejecutores. ![Listar el grupo ejecutor](/assets/images/help/settings/actions-org-enterprise-list-group-runners.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-list.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-list.md deleted file mode 100644 index e72a9060ea..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-list.md +++ /dev/null @@ -1 +0,0 @@ - 1. Ubica la lista de ejecutores bajo "Ejecutores auto-hospedados". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md deleted file mode 100644 index 0490bc1aa6..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md +++ /dev/null @@ -1,9 +0,0 @@ -Un ejecutor auto-hospedado puede ubicarse ya sea en tu organización o en tus ajustes de repositorio en {% data variables.product.prodname_dotcom %}. Para administrar un ejecutor auto-hospedado, debes tener los siguientes permisos, dependiendo de donde se agregó éste: -- **Repositorio de usuario**: debes ser el propietario del repositorio. -- **Organización**: Debes ser un propietario de la organización. -- **Repositorio de la organización**: Debes ser un propietario de la organización, o tener acceso administrativo al repositorio. -{% if currentVersion == "free-pro-team@latest" %} -- **Cuenta empresarial**: Debes ser un propietario de la empresa. -{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %} -- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator. -{% endif %} diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md deleted file mode 100644 index 87fbbd4f14..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-navigate-repo-and-org.md +++ /dev/null @@ -1 +0,0 @@ -1. En tu repositorio de organización, navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md deleted file mode 100644 index f2e993af27..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ /dev/null @@ -1,12 +0,0 @@ -1. Navega a donde está registrado tu ejecutor auto-hospedado: - * **En un repositorio organizacional**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. - * {% 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.{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**: - - 1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}. - 1. In the left sidebar, click **Enterprise overview**. - 1. {% endif %} In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**. -1. Navega a los ajustes de {% data variables.product.prodname_actions %}: - * **En un repositorio de organización**: da clic en **Acciones** en la barra lateral izquierda. - - ![Configuración de acciones](/assets/images/help/settings/settings-sidebar-actions.png) - * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %}**If using an enterprise-level runner**{% endif %}: click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies". diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-removal-impact.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-removal-impact.md deleted file mode 100644 index 09044c97a0..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-removal-impact.md +++ /dev/null @@ -1 +0,0 @@ -Este procedimiento eliminará el ejecutor auto-hospedado permanentemente. Si solo deseas detener de forma temporal un ejecutor de los trabajos asignados, puedes apagar la máquina o detener la aplicación `run`. El ejecutor permanecerá asignado en un estado "fuera de línea" y no ejecutará ningún job hasta que lo reinicies utilizando la aplicación `run`. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md deleted file mode 100644 index 5e1d8cf7cc..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ /dev/null @@ -1,15 +0,0 @@ -1. Debajo de **Ejecutores auto-hospedados**, 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) -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. - - El comando de eliminación realiza las siguientes tareas: - - * Elimina el ejecutor de {% data variables.product.product_name %}. - * 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. - - * **Si no tienes acceso a la máquina:** Da clic en **Sí, 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-XL/data/reusables/github-actions/self-hosted-runner-reqs-docker.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-reqs-docker.md deleted file mode 100644 index de3ca7dbdd..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-reqs-docker.md +++ /dev/null @@ -1 +0,0 @@ -Los ejecutores auto-hospedados deberán utilizar un sistema operativo Linux y tener Docker instalado para ejecutar las acciones de contenedores de Docker. Para obtener más información acerca de los requisitos de los ejecutores auto-hospedados, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#requirements-for-self-hosted-runner-machines)". diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-reusing.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-reusing.md deleted file mode 100644 index e16cb92082..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-reusing.md +++ /dev/null @@ -1 +0,0 @@ -Como alternativa, si no tienes acceso al repositorio, organización o empresa en {% data variables.product.product_name %} para eliminar un ejecutor, pero te gustaría reutilizar la máquina del ejecutor, entonces puedes borrar el archivo `.runner` dentro del directorio de la aplicación del ejecutor auto-hospedado. Esto permite que el ejecutor se registre sin tener que volver a descargar la aplicación del ejecutor auto-hospedado. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-security.md b/translations/es-XL/data/reusables/github-actions/self-hosted-runner-security.md deleted file mode 100644 index 052a683892..0000000000 --- a/translations/es-XL/data/reusables/github-actions/self-hosted-runner-security.md +++ /dev/null @@ -1,3 +0,0 @@ -Te recomendamos que no utilices ejecutores auto-hospedados con repositorios públicos. - -Las bifurcaciones de tu repositorio público pueden ejecutar código potencialmente peligroso en tu máquina de ejecutor auto-hospedado creando una solicitud de extracción que ejecute el código en un flujo de trabajo. diff --git a/translations/es-XL/data/reusables/github-actions/service-container-add-script.md b/translations/es-XL/data/reusables/github-actions/service-container-add-script.md deleted file mode 100644 index 399a3bd0ee..0000000000 --- a/translations/es-XL/data/reusables/github-actions/service-container-add-script.md +++ /dev/null @@ -1 +0,0 @@ -Agrega a tu repositorio un archivo nuevo llamado *client.js* con el siguiente código. diff --git a/translations/es-XL/data/reusables/github-actions/service-container-host-runner.md b/translations/es-XL/data/reusables/github-actions/service-container-host-runner.md deleted file mode 100644 index 0ef61112d6..0000000000 --- a/translations/es-XL/data/reusables/github-actions/service-container-host-runner.md +++ /dev/null @@ -1 +0,0 @@ -El ejemplo utiliza el ejecutor `ubuntu-latest` hospedado en {% data variables.product.prodname_dotcom %} como el hospedaje de Docker. diff --git a/translations/es-XL/data/reusables/github-actions/service-container-host.md b/translations/es-XL/data/reusables/github-actions/service-container-host.md deleted file mode 100644 index 57da27dae6..0000000000 --- a/translations/es-XL/data/reusables/github-actions/service-container-host.md +++ /dev/null @@ -1 +0,0 @@ -Este flujo de trabajo configura un job que se ejecuta en el contenedor `node:10.18-jessie` y utiiza el ejecutor `ubuntu-latest` hospedado en {% data variables.product.prodname_dotcom %} como el alojamiento de Docker para el contenedor. Para obtener más información acerca del contenedor `node:10.18-jessie`, consulta la [imagen del nodo](https://hub.docker.com/_/node) en Docker Hub. diff --git a/translations/es-XL/data/reusables/github-actions/service-container-localhost.md b/translations/es-XL/data/reusables/github-actions/service-container-localhost.md deleted file mode 100644 index ee26d0b158..0000000000 --- a/translations/es-XL/data/reusables/github-actions/service-container-localhost.md +++ /dev/null @@ -1 +0,0 @@ -El nombre del hospedaje es `localhost` o `127.0.0.1`. diff --git a/translations/es-XL/data/reusables/github-actions/service-container-prereqs.md b/translations/es-XL/data/reusables/github-actions/service-container-prereqs.md deleted file mode 100644 index 97d130245e..0000000000 --- a/translations/es-XL/data/reusables/github-actions/service-container-prereqs.md +++ /dev/null @@ -1 +0,0 @@ -Debes familiarizarte con la forma en la que trabajan los contenedores de servicio con {% data variables.product.prodname_actions %} y las diferencias de conexión de red entre los jobs que se están ejecutando directamente en el ejecutor y las que lo hacen en un contenedor. Para obtener más información, consulta la sección "[Acerca de los contenedores de servicios](/actions/automating-your-workflow-with-github-actions/about-service-containers)". diff --git a/translations/es-XL/data/reusables/github-actions/service-template-steps.md b/translations/es-XL/data/reusables/github-actions/service-template-steps.md deleted file mode 100644 index 01fd9eb069..0000000000 --- a/translations/es-XL/data/reusables/github-actions/service-template-steps.md +++ /dev/null @@ -1,5 +0,0 @@ -El flujo de trabajo realiza los siguientes pasos: - -1. Verifica el repositorio en el ejecutor -1. Instala las dependencias -1. Ejecuta un script para crear un cliente diff --git a/translations/es-XL/data/reusables/github-actions/setup-node-intro.md b/translations/es-XL/data/reusables/github-actions/setup-node-intro.md deleted file mode 100644 index 5b828b1ba5..0000000000 --- a/translations/es-XL/data/reusables/github-actions/setup-node-intro.md +++ /dev/null @@ -1 +0,0 @@ -Puedes utilizar la acción `setup-node` para crear un archivo local de tipo *.npmrc* en el ejecutor que configura el registro y alcance predeterminados. La acción `setup-node` también acepta un token de autenticación como entrada, el cual se utiliza para acceder a los registros privados o paquetes de nodo publicados. Para obtener más información, consulta la sección [`setup-node`](https://github.com/actions/setup-node/). diff --git a/translations/es-XL/data/reusables/github-actions/sidebar-secret.md b/translations/es-XL/data/reusables/github-actions/sidebar-secret.md deleted file mode 100644 index 1a695e7f67..0000000000 --- a/translations/es-XL/data/reusables/github-actions/sidebar-secret.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Secrets** (Secretos). \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-actions/spending-limit-enterprise-account.md b/translations/es-XL/data/reusables/github-actions/spending-limit-enterprise-account.md deleted file mode 100644 index a88241d3f8..0000000000 --- a/translations/es-XL/data/reusables/github-actions/spending-limit-enterprise-account.md +++ /dev/null @@ -1 +0,0 @@ -Si pagas por tu cuenta empresarial por factura, no puedes administrar el límite de gastos para la misma en {% data variables.product.product_name %}. Si quieres permitir que las organizaciones que pertenecen a tu cuenta empresarial utilicen {% data variables.product.prodname_actions %} con más almacenamiento o transferencia de datos de las que se incluye en sus cuentas, puedes prepagar los exceedntes. Ya que los excedentes deben prepagarse, no puedes habilitar los gastos ilimitados en cuentas que se paguen mediante factura. Tu límite de gastos será de 150% de la cantidad que hayas prepagado. Si tienes cualquier duda, [contacta a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact). diff --git a/translations/es-XL/data/reusables/github-actions/supported-github-runners.md b/translations/es-XL/data/reusables/github-actions/supported-github-runners.md deleted file mode 100644 index 1937ac1b93..0000000000 --- a/translations/es-XL/data/reusables/github-actions/supported-github-runners.md +++ /dev/null @@ -1,7 +0,0 @@ -| Entorno virtual | Etiqueta de flujo de trabajo YAML | -| -------------------- | --------------------------------- | -| Windows Server 2019 | `windows-latest` o `windows-2019` | -| Ubuntu 20.04 | `ubuntu-20.04` | -| Ubuntu 18.04 | `ubuntu-latest` o `ubuntu-18.04` | -| Ubuntu 16.04 | `ubuntu-16.04` | -| macOS Catalina 10.15 | `macos-latest` or `macos-10.15` | diff --git a/translations/es-XL/data/reusables/github-actions/ubuntu-runner-preview.md b/translations/es-XL/data/reusables/github-actions/ubuntu-runner-preview.md deleted file mode 100644 index 16447a14e6..0000000000 --- a/translations/es-XL/data/reusables/github-actions/ubuntu-runner-preview.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** El ambiente virtual de Ubuntu 20.04 se proporciona actualmente como una vista previa únicamente. La etiqueta de flujo de trabajo de YAML `ubuntu-latest` aún utiliza el ambiente virtual de Ubuntu 18.04. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/es-XL/data/reusables/github-connect/access-dotcom-and-enterprise.md deleted file mode 100644 index 75c6726d7c..0000000000 --- a/translations/es-XL/data/reusables/github-connect/access-dotcom-and-enterprise.md +++ /dev/null @@ -1 +0,0 @@ -1. Iniciar sesión en {% data variables.product.product_location_enterprise %} y {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/es-XL/data/reusables/github-connect/access-profile-settings.md b/translations/es-XL/data/reusables/github-connect/access-profile-settings.md deleted file mode 100644 index c601a6309d..0000000000 --- a/translations/es-XL/data/reusables/github-connect/access-profile-settings.md +++ /dev/null @@ -1 +0,0 @@ -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) diff --git a/translations/es-XL/data/reusables/github-connect/authorize-connection.md b/translations/es-XL/data/reusables/github-connect/authorize-connection.md deleted file mode 100644 index 220d5c6ec7..0000000000 --- a/translations/es-XL/data/reusables/github-connect/authorize-connection.md +++ /dev/null @@ -1 +0,0 @@ -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) diff --git a/translations/es-XL/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/es-XL/data/reusables/github-connect/connect-dotcom-and-enterprise.md deleted file mode 100644 index c375744a01..0000000000 --- a/translations/es-XL/data/reusables/github-connect/connect-dotcom-and-enterprise.md +++ /dev/null @@ -1 +0,0 @@ -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) diff --git a/translations/es-XL/data/reusables/github-connect/github-connect-tab-user-settings.md b/translations/es-XL/data/reusables/github-connect/github-connect-tab-user-settings.md deleted file mode 100644 index 1ba99c5619..0000000000 --- a/translations/es-XL/data/reusables/github-connect/github-connect-tab-user-settings.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_connect %}**. ![Pestaña de GitHub Connect en la barra lateral de la configuración de usuario](/assets/images/help/settings/github-connect-tab-user-settings.png) diff --git a/translations/es-XL/data/reusables/github-connect/sync-frequency.md b/translations/es-XL/data/reusables/github-connect/sync-frequency.md deleted file mode 100644 index 93299f0265..0000000000 --- a/translations/es-XL/data/reusables/github-connect/sync-frequency.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_ghe_server %} envía actualizaciones cada hora. diff --git a/translations/es-XL/data/reusables/github-insights/about-key-metrics.md b/translations/es-XL/data/reusables/github-insights/about-key-metrics.md deleted file mode 100644 index fad2d837fd..0000000000 --- a/translations/es-XL/data/reusables/github-insights/about-key-metrics.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_insights %} resalta las métricas clave ya que éstas se pueden accionar directamente para incrementar tanto velocidad como calidad. Las métricas clave son útiles para todos en la organización, desde colaboradores individuales y sus gerentes, hasta ejecutivos que buscan un panorama más amplio. diff --git a/translations/es-XL/data/reusables/github-insights/about-reports.md b/translations/es-XL/data/reusables/github-insights/about-reports.md deleted file mode 100644 index aa0ed75190..0000000000 --- a/translations/es-XL/data/reusables/github-insights/about-reports.md +++ /dev/null @@ -1 +0,0 @@ -Todas las otras métricas se incluyen en los reportes, los cuales contienen diversas métricas sobre el mismo tema, tal como las solicitudes de extracción o el código. diff --git a/translations/es-XL/data/reusables/github-insights/add-organizations.md b/translations/es-XL/data/reusables/github-insights/add-organizations.md deleted file mode 100644 index 38536525f5..0000000000 --- a/translations/es-XL/data/reusables/github-insights/add-organizations.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de la página, da clic en **Agregar Organización(es)**. Verás una lista de organizaciones asociadas con tu cuenta de {% data variables.product.prodname_enterprise %}. ![Botón de Agregar Organización(es)](/assets/images/help/insights/add-organizations.png) diff --git a/translations/es-XL/data/reusables/github-insights/app-id.md b/translations/es-XL/data/reusables/github-insights/app-id.md deleted file mode 100644 index 5a27c45ff8..0000000000 --- a/translations/es-XL/data/reusables/github-insights/app-id.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "App ID", teclea la ID de la App de tu {% data variables.product.prodname_github_app %}, la cual grabaste cuando creaste dicha app. ![Campo de App ID](/assets/images/help/insights/app-id.png) diff --git a/translations/es-XL/data/reusables/github-insights/choose-key-metric.md b/translations/es-XL/data/reusables/github-insights/choose-key-metric.md deleted file mode 100644 index 79dbbde28d..0000000000 --- a/translations/es-XL/data/reusables/github-insights/choose-key-metric.md +++ /dev/null @@ -1 +0,0 @@ -2. Debajo de **{% octicon "graph" aria-label="The graph icon" %} Métricas clave**, haz clic en el nombre de la métrica que deseas ver. ![Lista de métricas clave](/assets/images/help/insights/key-metrics-list.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-insights/client-id.md b/translations/es-XL/data/reusables/github-insights/client-id.md deleted file mode 100644 index 241bbd49c8..0000000000 --- a/translations/es-XL/data/reusables/github-insights/client-id.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "ID de Cliente", teclea la ID de cliente de tu {% data variables.product.prodname_github_app %}, la cual grabaste cuando creaste la app. ![Campo de ID de Cliente](/assets/images/help/insights/client-id.png) diff --git a/translations/es-XL/data/reusables/github-insights/client-secret.md b/translations/es-XL/data/reusables/github-insights/client-secret.md deleted file mode 100644 index a4112ec301..0000000000 --- a/translations/es-XL/data/reusables/github-insights/client-secret.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Secreto de Cliente", teclea el secreto del cliente de tu {% data variables.product.prodname_github_app %}, el cual grabaste cuando creaste la app. ![Campo de secreto de cliente](/assets/images/help/insights/client-secret.png) diff --git a/translations/es-XL/data/reusables/github-insights/contributors-tab.md b/translations/es-XL/data/reusables/github-insights/contributors-tab.md deleted file mode 100644 index 5d7e26c048..0000000000 --- a/translations/es-XL/data/reusables/github-insights/contributors-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Colaboradores**. ![Pestaña de colaboradores](/assets/images/help/insights/contributors-tab.png) diff --git a/translations/es-XL/data/reusables/github-insights/docker-requirements.md b/translations/es-XL/data/reusables/github-insights/docker-requirements.md deleted file mode 100644 index a2e194ab04..0000000000 --- a/translations/es-XL/data/reusables/github-insights/docker-requirements.md +++ /dev/null @@ -1 +0,0 @@ -El servidor de aplicaciones puede requerir que el demonio de Docker se ejecute como sudo. Kubernetes no es compatible. diff --git a/translations/es-XL/data/reusables/github-insights/download-latest-release.md b/translations/es-XL/data/reusables/github-insights/download-latest-release.md deleted file mode 100644 index 8c1caebddc..0000000000 --- a/translations/es-XL/data/reusables/github-insights/download-latest-release.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Desde el servidor de la aplicación, navega hasta el último lanzamiento de {% data variables.product.prodname_insights %} en la [Página de lanzamientos](https://github.com/github/insights-releases/releases/latest) para `github/insights-releases`. -2. Para descargar el último lanzamiento, debajo de "Activos", da clic en `insights-VERSION.tar.gz`. ![Activo de instalación](/assets/images/help/insights/installation-tgz.png) -3. Descomprime el directorio. diff --git a/translations/es-XL/data/reusables/github-insights/edit-contributor.md b/translations/es-XL/data/reusables/github-insights/edit-contributor.md deleted file mode 100644 index 4145300020..0000000000 --- a/translations/es-XL/data/reusables/github-insights/edit-contributor.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Editar** a la derecha del colaborador que quieras administrar. ![Botón editar](/assets/images/help/insights/edit-contributor.png) diff --git a/translations/es-XL/data/reusables/github-insights/edit-group.md b/translations/es-XL/data/reusables/github-insights/edit-group.md deleted file mode 100644 index c7f8f7c89d..0000000000 --- a/translations/es-XL/data/reusables/github-insights/edit-group.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Editar** a la derecha del nombre del grupo. ![Botón editar](/assets/images/help/insights/edit-group-button.png) diff --git a/translations/es-XL/data/reusables/github-insights/edit-team.md b/translations/es-XL/data/reusables/github-insights/edit-team.md deleted file mode 100644 index f03a3f2fcb..0000000000 --- a/translations/es-XL/data/reusables/github-insights/edit-team.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Editar Equipo** a un costado del equipo al que quieras agregar contribuyentes. ![Botón de editar equipo](/assets/images/help/insights/edit-team.png) diff --git a/translations/es-XL/data/reusables/github-insights/enterprise-api-url.md b/translations/es-XL/data/reusables/github-insights/enterprise-api-url.md deleted file mode 100644 index 953480375f..0000000000 --- a/translations/es-XL/data/reusables/github-insights/enterprise-api-url.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "URL de la API de {% data variables.product.prodname_dotcom %}", teclea {% if currentVersion == "free-pro-team@latest" %}https://api.github.com {% else %} la URL que utilizas para acceder a {% data variables.product.prodname_enterprise %}{% endif %}. ![Campo de URL de la API de {% data variables.product.prodname_enterprise %}](/assets/images/help/insights/enterprise-api-url.png) diff --git a/translations/es-XL/data/reusables/github-insights/events-tab.md b/translations/es-XL/data/reusables/github-insights/events-tab.md deleted file mode 100644 index 8d1576cfb4..0000000000 --- a/translations/es-XL/data/reusables/github-insights/events-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Eventos**. ![Pestaña de eventos](/assets/images/help/insights/events-tab.png) diff --git a/translations/es-XL/data/reusables/github-insights/events.md b/translations/es-XL/data/reusables/github-insights/events.md deleted file mode 100644 index adbb3ec604..0000000000 --- a/translations/es-XL/data/reusables/github-insights/events.md +++ /dev/null @@ -1 +0,0 @@ -Puedes utilizar los eventos para marcar días o periodos importantes en las métricas para agregar contexto para los espectadores. diff --git a/translations/es-XL/data/reusables/github-insights/exclude-files-tab.md b/translations/es-XL/data/reusables/github-insights/exclude-files-tab.md deleted file mode 100644 index aeefb67fe0..0000000000 --- a/translations/es-XL/data/reusables/github-insights/exclude-files-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Excluir archivos**. ![Pestaña de excluir eventos](/assets/images/help/insights/exclude-files-tab.png) diff --git a/translations/es-XL/data/reusables/github-insights/filter-reports.md b/translations/es-XL/data/reusables/github-insights/filter-reports.md deleted file mode 100644 index bb9e448478..0000000000 --- a/translations/es-XL/data/reusables/github-insights/filter-reports.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, para filtrar todas las métricas de la página, debajo de éstas, utiliza los menús desplegables "Equipos", "Repos" o de rango de fechas. ![Menús desplegables de los filtros](/assets/images/help/insights/filter-drop-downs.png) diff --git a/translations/es-XL/data/reusables/github-insights/insights-license.md b/translations/es-XL/data/reusables/github-insights/insights-license.md deleted file mode 100644 index 476846e6ea..0000000000 --- a/translations/es-XL/data/reusables/github-insights/insights-license.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Licencia de {% data variables.product.prodname_insights %}", da clic en "Escoger Archivos", y luego carga tu archivo de licencia de {% data variables.product.prodname_enterprise %}. ![Botón de escoger archivos](/assets/images/help/insights/choose-files.png) diff --git a/translations/es-XL/data/reusables/github-insights/install-script.md b/translations/es-XL/data/reusables/github-insights/install-script.md deleted file mode 100644 index 244f0742e4..0000000000 --- a/translations/es-XL/data/reusables/github-insights/install-script.md +++ /dev/null @@ -1,9 +0,0 @@ -4. Ejecuta el script del shell `Install.sh`. -5. Para habilitar SSL, ingresa el certificado SSL (`.crt/.cer/.pem`). Si no quieres habilitar SSL, déjalo en blanco. -6. Si eliges habilitar SSL, ingresa la llave SSL (`.key`). De lo contrario, déjalo en blanco. -5. Ingresa el nombre del host, el cual es la misma URL que utilizas para el servidor de la aplicación cuando creas la {% data variables.product.prodname_github_app %}. -6. La instalación tardará unos minutos en ejecutarse. Una vez que esté completo, verás un mensaje impreso en el terminal. - ``` - Installation complete - Run /opt/insights/scripts/start.sh to start GitHub Insights - ``` diff --git a/translations/es-XL/data/reusables/github-insights/key-metrics-and-reports.md b/translations/es-XL/data/reusables/github-insights/key-metrics-and-reports.md deleted file mode 100644 index 5aa1b6c7f8..0000000000 --- a/translations/es-XL/data/reusables/github-insights/key-metrics-and-reports.md +++ /dev/null @@ -1 +0,0 @@ -Los datos disponibles en {% data variables.product.prodname_insights %} se dividen en métricas clave y reportes. diff --git a/translations/es-XL/data/reusables/github-insights/manage-metrics.md b/translations/es-XL/data/reusables/github-insights/manage-metrics.md deleted file mode 100644 index d0509a768a..0000000000 --- a/translations/es-XL/data/reusables/github-insights/manage-metrics.md +++ /dev/null @@ -1 +0,0 @@ -Las personas con permisos de administrador en {% data variables.product.prodname_insights %} pueden administrar qué métricas se mostrarán. Para obtener más información, consulta "[Administrar métricas e informes disponibles](/insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports)". diff --git a/translations/es-XL/data/reusables/github-insights/navigate-to-key-metrics.md b/translations/es-XL/data/reusables/github-insights/navigate-to-key-metrics.md deleted file mode 100644 index dc890c7e62..0000000000 --- a/translations/es-XL/data/reusables/github-insights/navigate-to-key-metrics.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.prodname_insights %}, haz clic en **{% octicon "graph" aria-label="The graph icon" %} Métricas clave**. ![Pestaña Key Metrics (Métricas clave)](/assets/images/help/insights/key-metrics-tab.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/github-insights/permissions-levels.md b/translations/es-XL/data/reusables/github-insights/permissions-levels.md deleted file mode 100644 index 9e7c315fd7..0000000000 --- a/translations/es-XL/data/reusables/github-insights/permissions-levels.md +++ /dev/null @@ -1,5 +0,0 @@ -{% data variables.product.prodname_insights %} tiene dos niveles de permiso. - -- Los permisos administrativos corresponden al rol de administrador de sitio en {% data variables.product.prodname_enterprise %}. Las personas con permisos administrativos tiene acceso a todas las configuraciones de {% data variables.product.prodname_insights %}. - -- El resto de los usuarios en {% data variables.product.prodname_enterprise %} tienen cuentas de usuario en {% data variables.product.prodname_insights %}. Los usuarios pueden ver todas las métricas, pero tienen acceso limitado a las configuraciones. diff --git a/translations/es-XL/data/reusables/github-insights/private-key.md b/translations/es-XL/data/reusables/github-insights/private-key.md deleted file mode 100644 index 2176725ee4..0000000000 --- a/translations/es-XL/data/reusables/github-insights/private-key.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Llave Privada", teclea la llave privada de tu {% data variables.product.prodname_github_app %}, la cual se contiene en el archivo PEM que descargaste mientras creabas la app. ![Campo de llave privada](/assets/images/help/insights/private-key.png) diff --git a/translations/es-XL/data/reusables/github-insights/repo-groups-tab.md b/translations/es-XL/data/reusables/github-insights/repo-groups-tab.md deleted file mode 100644 index c64ec82d9f..0000000000 --- a/translations/es-XL/data/reusables/github-insights/repo-groups-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Grupos de Repo**. ![Pestaña de grupos de Repo](/assets/images/help/insights/repo-groups-tab.png) diff --git a/translations/es-XL/data/reusables/github-insights/repositories-tab.md b/translations/es-XL/data/reusables/github-insights/repositories-tab.md deleted file mode 100644 index 0b75836d25..0000000000 --- a/translations/es-XL/data/reusables/github-insights/repositories-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Repositorios**. ![Pestaña Repositories (Repositorios)](/assets/images/help/insights/repositories-tab.png) diff --git a/translations/es-XL/data/reusables/github-insights/repository-groups.md b/translations/es-XL/data/reusables/github-insights/repository-groups.md deleted file mode 100644 index 22c80f4b52..0000000000 --- a/translations/es-XL/data/reusables/github-insights/repository-groups.md +++ /dev/null @@ -1 +0,0 @@ -Puedes crear un grupo de repositorios para ver los datos combinados para los repositorios relacionados. Puedes filtrar por grupo de repositorio en cada métrica y reporte. diff --git a/translations/es-XL/data/reusables/github-insights/requires-machine.md b/translations/es-XL/data/reusables/github-insights/requires-machine.md deleted file mode 100644 index 1e3a979f4f..0000000000 --- a/translations/es-XL/data/reusables/github-insights/requires-machine.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_insights %} requiere una máquina, llamada servidor de la aplicación, hospedada ya sea en la nube o localmente. diff --git a/translations/es-XL/data/reusables/github-insights/run-script.md b/translations/es-XL/data/reusables/github-insights/run-script.md deleted file mode 100644 index 04a2265d09..0000000000 --- a/translations/es-XL/data/reusables/github-insights/run-script.md +++ /dev/null @@ -1,5 +0,0 @@ -4. Para iniciar con {% data variables.product.prodname_insights %}, ejecuta el script del shell `/opt/insights/scripts/start.sh`. -5. Si es la primera vez que inicias {% data variables.product.prodname_insights %}, el script tomará algunos minutos en ejecutarse. Una vez que esté completo, verás un mensaje impreso en el terminal. - ``` - GitHub Insights is running! - ``` diff --git a/translations/es-XL/data/reusables/github-insights/settings-tab.md b/translations/es-XL/data/reusables/github-insights/settings-tab.md deleted file mode 100644 index 069c991a2d..0000000000 --- a/translations/es-XL/data/reusables/github-insights/settings-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.prodname_insights %}, da clic en **{% octicon "gear" aria-label="The gear icon" %} Configuración**. ![Pestaña Parámetros](/assets/images/help/insights/settings-tab.png) diff --git a/translations/es-XL/data/reusables/github-insights/skip-ssl.md b/translations/es-XL/data/reusables/github-insights/skip-ssl.md deleted file mode 100644 index 2877bccb31..0000000000 --- a/translations/es-XL/data/reusables/github-insights/skip-ssl.md +++ /dev/null @@ -1 +0,0 @@ -1. Si no proporcionaste un certificado SSL durante la instalación, selecciona **Saltar Verificación de Certificado SSL**. ![Casilla de saltar verificación de certificado SSL](/assets/images/help/insights/skip-ssl.png) diff --git a/translations/es-XL/data/reusables/github-insights/teams-tab.md b/translations/es-XL/data/reusables/github-insights/teams-tab.md deleted file mode 100644 index b05be6ddd5..0000000000 --- a/translations/es-XL/data/reusables/github-insights/teams-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de **Configuración {% octicon "gear" aria-label="The gear icon" %}**, da clic en **Equipos**. ![Pestaña de equipos](/assets/images/help/insights/teams-tab.png) diff --git a/translations/es-XL/data/reusables/github-insights/view-events.md b/translations/es-XL/data/reusables/github-insights/view-events.md deleted file mode 100644 index e1c12015a7..0000000000 --- a/translations/es-XL/data/reusables/github-insights/view-events.md +++ /dev/null @@ -1 +0,0 @@ -2. Opcionalmente, para ver los eventos que ocurrieron durante cierto tiempo, da clic en el círculo enumerado sobre este lapso de tiempo. ![Círculos numerados para indicar eventos](/assets/images/help/insights/event-circles.png) diff --git a/translations/es-XL/data/reusables/github-insights/webhook-secret.md b/translations/es-XL/data/reusables/github-insights/webhook-secret.md deleted file mode 100644 index 58f2a01e14..0000000000 --- a/translations/es-XL/data/reusables/github-insights/webhook-secret.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Secretod e Webhook", teclea el secreto de webhook de tu {% data variables.product.prodname_github_app %}, el cual grabaste cuando la creaste. ![Campo secreto de webhook](/assets/images/help/insights/webhook-secret.png) diff --git a/translations/es-XL/data/reusables/gpg/copy-gpg-key-id.md b/translations/es-XL/data/reusables/gpg/copy-gpg-key-id.md deleted file mode 100644 index 772ad766b3..0000000000 --- a/translations/es-XL/data/reusables/gpg/copy-gpg-key-id.md +++ /dev/null @@ -1,9 +0,0 @@ -1. De la lista de llaves GPG, copia la ID de la llave GPG que quieres utilizar. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`: - ```shell - $ gpg --list-secret-keys --keyid-format LONG - /Users/hubot/.gnupg/secring.gpg - ------------------------------------ - sec 4096R/3AA5C34371567BD2 2016-03-10 [expires: 2017-03-10] - uid Hubot - ssb 4096R/42B317FD4BA89E7A 2016-03-10 - ``` diff --git a/translations/es-XL/data/reusables/gpg/desktop-support-for-commit-signing.md b/translations/es-XL/data/reusables/gpg/desktop-support-for-commit-signing.md deleted file mode 100644 index 6b66186106..0000000000 --- a/translations/es-XL/data/reusables/gpg/desktop-support-for-commit-signing.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:**[GitHub Desktop](https://desktop.github.com/) no es compatible con el firmado de confirmaciones. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/gpg/list-keys-with-note.md b/translations/es-XL/data/reusables/gpg/list-keys-with-note.md deleted file mode 100644 index c5344541e1..0000000000 --- a/translations/es-XL/data/reusables/gpg/list-keys-with-note.md +++ /dev/null @@ -1,10 +0,0 @@ - -1. Utiliza el comando `gpg --list-secret-keys --keyid-format LONG` para enumerar las llaves GPG para las cuales tienes tanto una llave pública como privada. Se requiere una llave privada para registrar confirmaciones o etiquetas. - ```shell - $ gpg --list-secret-keys --keyid-format LONG -``` - {% note %} - - **Nota:** Algunas instalaciones GPG en Linux pueden requerir que uses `gpg2 --list-keys --keyid-format LONG` para visualizar una lista de tus llaves existentes en su lugar. En este caso también deberás configurar Git para que use `gpg2` by running `git config --global gpg.program gpg2`. - - {% endnote %} diff --git a/translations/es-XL/data/reusables/gpg/paste-gpg-key-id.md b/translations/es-XL/data/reusables/gpg/paste-gpg-key-id.md deleted file mode 100644 index 1cb8593e93..0000000000 --- a/translations/es-XL/data/reusables/gpg/paste-gpg-key-id.md +++ /dev/null @@ -1,4 +0,0 @@ -1. Para configurar tu llave de firma GPG en Git, pega el siguiente texto en sustitución de la ID de la llave GPG que quieras utilizar. En este ejemplo, el ID de la llave GPG es `3AA5C34371567BD2`: - ```shell -$ git config --global user.signingkey 3AA5C34371567BD2 -``` diff --git a/translations/es-XL/data/reusables/gpg/private-email.md b/translations/es-XL/data/reusables/gpg/private-email.md deleted file mode 100644 index ae8911e5f8..0000000000 --- a/translations/es-XL/data/reusables/gpg/private-email.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Para mantener tu dirección de correo electrónico como privada, utiliza tus direcciones de tipo `no-reply` proporcionadas por {% data variables.product.product_name %}. -{% endif %} diff --git a/translations/es-XL/data/reusables/gpg/smime-git-version.md b/translations/es-XL/data/reusables/gpg/smime-git-version.md deleted file mode 100644 index 785a1da369..0000000000 --- a/translations/es-XL/data/reusables/gpg/smime-git-version.md +++ /dev/null @@ -1,6 +0,0 @@ - -{% note %} - -**Nota:** la verificación de firma S/MIME está disponible desde Git 2.19 o posterior. Para actualizar tu versiíon de Git, consulta el sitio web de [Git](https://git-scm.com/downloads). - -{% endnote %} diff --git a/translations/es-XL/data/reusables/gpg/supported-gpg-key-algorithms.md b/translations/es-XL/data/reusables/gpg/supported-gpg-key-algorithms.md deleted file mode 100644 index 5a91347f8e..0000000000 --- a/translations/es-XL/data/reusables/gpg/supported-gpg-key-algorithms.md +++ /dev/null @@ -1,11 +0,0 @@ - -### Algoritmos compatibles de llave GPG - -{% data variables.product.product_name %} es compatible con varios algoritmos GPG. Si tratas de agregar una llave generada con un algoritmo no compatible, puedes llegar a un error. - -- RSA -- ElGamal -- DSA -- ECDH -- ECDSA -- EdDSA diff --git a/translations/es-XL/data/reusables/gpg/x-509-key.md b/translations/es-XL/data/reusables/gpg/x-509-key.md deleted file mode 100644 index 49e22d5866..0000000000 --- a/translations/es-XL/data/reusables/gpg/x-509-key.md +++ /dev/null @@ -1,57 +0,0 @@ - -### Informarle a Git acerca de tu llave X.509 - -Puedes usar [smimesign](https://github.com/github/smimesign) para firmar confirmaciones y etiquetas utilizando S/MIME en lugar de GPG. - -{% data reusables.gpg.smime-git-version %} - -1. Instala [smimesign](https://github.com/github/smimesign#installation). -{% data reusables.command_line.open_the_multi_os_terminal %} -3. Configura Git para que use S/MIME para firmar confirmaciones y etiquetas. En Git 2.19 o posterior, utiliza los comandos `git config gpg.x509.program` y `git config gpg.format`: - - Para utilizar S/MIME para firmar todos los repositorios: - ```shell - $ git config --global gpg.x509.program smimesign - $ git config --global gpg.format x509 - ``` - - Para utilizar S/MIME para firmar un repositorio único: - ```shell - $ cd /path/to/my/repository - $ git config --local gpg.x509.program smimesign - $ git config --local gpg.format x509 - ``` - En Git 2.18 o inferior, utiliza el comando `git config gpg.program`: - - Para utilizar S/MIME para firmar todos los repositorios: - ```shell - $ git config --global gpg.program smimesign - ``` - - Para utilizar S/MIME para firmar un repositorio único: - ```shell - $ cd /path/to/my/repository - $ git config --local gpg.program smimesign - ``` - Si estás utilizando una llave X.509 que coincide con tu identidad de persona que confirma el cambio, puedes comenzar firmando confirmaciones y etiquetas. -4. Si no estás utilizando una llave X.509 que coincide con tu identidad de persona que confirmar el cambio, enumera las llaves X.509 para las cuales tienes tanto un certificado como una llave privada utilizando el comando `smimesign --list-keys`. - ```shell - $ smimesign --list-keys - ``` -5. De la lista de llaves X.509, copia el ID del certificado de la llave X.509 que desearías utilizar. En este ejemplo, el ID del certificado es `0ff455a2708394633e4bb2f88002e3cd80cbd76f`: - ```shell - $ smimesign --list-keys - ID: 0ff455a2708394633e4bb2f88002e3cd80cbd76f - S/N: a2dfa7e8c9c4d1616f1009c988bb70f - Algorithm: SHA256-RSA - Validity: 2017-11-22 00:00:00 +0000 UTC - 2020-11-22 12:00:00 +0000 UTC - Issuer: CN=DigiCert SHA2 Assured ID CA,OU=www.digicert.com,O=DigiCert Inc,C=US - Subject: CN=Octocat,O=GitHub\, Inc.,L=San Francisco,ST=California,C=US - Emails: octocat@github.com - ``` -6. Para configurar tu llave de firma X.509 en Git, pega el texto de abajo, sustituyendo el ID del certificado que copiaste anteriormente. - - Para utilizar tu llave X.509 para firmar todos los repositorios: - ```shell - $ git config --global user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f - ``` - - Para utilizar tu llave X.509 para firmar un repositorio único: - ```shell - $ cd /path/to/my/repository - $ git config --local user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f - ``` diff --git a/translations/es-XL/data/reusables/identity-and-permissions/about-team-sync.md b/translations/es-XL/data/reusables/identity-and-permissions/about-team-sync.md deleted file mode 100644 index dd3dc3b79e..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/about-team-sync.md +++ /dev/null @@ -1 +0,0 @@ -Cuando sincronizas un equipo de {% data variables.product.prodname_dotcom %} con un grupo de IdP, los cambios a este grupo se reflejan automáticamente en {% data variables.product.product_name %}, reduciendo la necesidad de hacer actualizaciones manuales y scripts personalizados. Puedes utilizar un IdP con la sincronización de equipos para gestionar las tareas administrativas tales como el incorporar miembros nuevos, otorgar permisos nuevos para hacer movimientos dentro de una organización, y eliminar el acceso de un miembro a la organización. diff --git a/translations/es-XL/data/reusables/identity-and-permissions/enable-team-sync-azure.md b/translations/es-XL/data/reusables/identity-and-permissions/enable-team-sync-azure.md deleted file mode 100644 index 2975c1b1cd..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/enable-team-sync-azure.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Sincronización de equipo", da clic en **Habilitar para Azure AD**. ![Botón para habilitar la sincronización de equipo en la página de configuraciones de seguridad](/assets/images/help/teams/enable-team-synchronization.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/identity-and-permissions/enable-team-sync-okta.md b/translations/es-XL/data/reusables/identity-and-permissions/enable-team-sync-okta.md deleted file mode 100644 index 88723bce43..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/enable-team-sync-okta.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Sincronización de equipo", da clic en **Habilitar para Okta**. ![Botón de habilitar sincronización de equipo para Okta en la página de configuraciones de seguridad](/assets/images/help/teams/enable-team-synchronization-okta.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md deleted file mode 100644 index e06397ae25..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Descripción", teclea la descripción de la dirección IP o el rango de ellas que se permitirá. ![Campo clave para agregar un nombre a la dirección IP](/assets/images/help/security/ip-address-name-field.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md deleted file mode 100644 index c5822b5f01..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en {% octicon "plus" aria-label="The plus icon" %} **Add** (Agregar). ![Botón Add allowed ip address (Agregar dirección ip permitida)](/assets/images/help/security/new-allowlist-entry-button.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md deleted file mode 100644 index 341761ada9..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Dirección IP", teclea una dirección o un rango de ellas, en notación CIDR. ![Campo clave para agregar una dirección IP](/assets/images/help/security/ip-address-field.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md deleted file mode 100644 index c5af4df841..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md +++ /dev/null @@ -1 +0,0 @@ -Puedes aprobar el acceso para una dirección IP única o para un rango de ellas utilizando notación CIDR. Para obtener más información, consulta "[Notación CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" en Wikipedia. diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md deleted file mode 100644 index cf93a9a028..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md +++ /dev/null @@ -1 +0,0 @@ -1. Para borrar permanentemente la entrada, da clic en **Sí, borrar esta lista de direcciones IP permitidas**. ![Botón Permanently delete IP allow list entry (Borrar permanentemente la entrada de la lista de IP permitida)](/assets/images/help/security/perm-delete-allowlist-entry-button.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md deleted file mode 100644 index 3337ce284d..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Lista de IP permitidas", a la derecha de la entrada que quieres borrar, da clic en **Borrar**. ![Botón Delete allowed IP address (Eliminar dirección IP permitida)](/assets/images/help/security/ip-address-delete-button.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md deleted file mode 100644 index 3eb92cb7de..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea una descripción del rango de direcciones IP permitidas. ![Campo clave para agregar un nombre a la dirección IP](/assets/images/help/security/ip-address-edit-name-field.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md deleted file mode 100644 index 4b1f4fe375..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Lista de IP permitidas", a la derecha de la entrada que quieres editar, da clic en **Editar**. ![Botón Edit allowed IP address (Editar dirección IP permitida)](/assets/images/help/security/ip-address-edit-button.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md deleted file mode 100644 index d8c518c615..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea una dirección IP, o rango de direcciones, en notación CIDR. ![Campo clave para agregar una dirección IP](/assets/images/help/security/ip-address-edit-field.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-enable.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-enable.md deleted file mode 100644 index e236790aec..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-enable.md +++ /dev/null @@ -1 +0,0 @@ -Para aplicar la lista de IP permitidas, primero debes agregar direcciones a la lista, y después habilitarla. Debes agregar tu dirección IP actual o un rango coincidente antes de habilitar la lista de permisos de IP. diff --git a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md b/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md deleted file mode 100644 index ad17976c02..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md +++ /dev/null @@ -1 +0,0 @@ -Por ejemplo, puedes permitir el acceso desde la única dirección IP de tu red de oficina. La lista de direcciones IP permitidas bloqueará el acceso mediante la web, las API y Git desde cualquier dirección IP que no se encuentre en ella. diff --git a/translations/es-XL/data/reusables/identity-and-permissions/supported-idps-team-sync.md b/translations/es-XL/data/reusables/identity-and-permissions/supported-idps-team-sync.md deleted file mode 100644 index 1d84b9f87c..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/supported-idps-team-sync.md +++ /dev/null @@ -1,3 +0,0 @@ -Puedes utilizar la sincronización de equipos con los IdP compatibles. - - Azure AD - - Okta \ No newline at end of file diff --git a/translations/es-XL/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/es-XL/data/reusables/identity-and-permissions/sync-team-with-idp-group.md deleted file mode 100644 index f344795070..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/sync-team-with-idp-group.md +++ /dev/null @@ -1 +0,0 @@ -Después de que habilites la sincronización de equipos, los mantenedores de equipo y propietarios de organización pueden conectar los equipos a un grupo de IdP en {% data variables.product.prodname_dotcom %} o a través de la API. Para obtener más información, consulta las secciones "[Sincronizar un equipo con un grupo de proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)" y "[Sincronización de equipo](/v3/teams/team_sync/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/es-XL/data/reusables/identity-and-permissions/team-sync-azure-permissions.md deleted file mode 100644 index c9ac053468..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-azure-permissions.md +++ /dev/null @@ -1,4 +0,0 @@ -Para habilitar la sincronización de equipo para Azure AD, tu instalación de Azure AD necesita los siguientes permisos: -- Lectura de todos los perfiles completos de usuarios -- Inicio de sesión y lectura del perfil de usuario -- Lectura de los datos del directorio diff --git a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/es-XL/data/reusables/identity-and-permissions/team-sync-confirm-saml.md deleted file mode 100644 index e25f3ba376..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-confirm-saml.md +++ /dev/null @@ -1 +0,0 @@ -3. Confirma que el SSO de SAML esté habilitado. Para obtener más información, consulta "[Administrar el inicio de sesión único de SAML para tu organización](/articles/managing-saml-single-sign-on-for-your-organization)". diff --git a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/es-XL/data/reusables/identity-and-permissions/team-sync-confirm.md deleted file mode 100644 index 85a182ab0f..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-confirm.md +++ /dev/null @@ -1,3 +0,0 @@ -5. Para confirmar la sincronización de equipo: - - Si tienes acceso IdP, haz clic en **Enable team synchronization (Habilitar sincronización de equipo)**. Serás redireccionado a la página de SSO de SAML de tu proveedor de identidad y se te solicitará que selecciones tu cuenta y revises los permisos requeridos. - - Si no tienes acceso de IdP, copia el vínculo de redirección de IdP y compártelo con tu administrador de IdP para continuar habilitando la sincronización de equipo. ![Botón para habilitar el redireccionamiento de la sincronización de equipo](/assets/images/help/teams/confirm-team-synchronization-redirect.png) diff --git a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-disable.md b/translations/es-XL/data/reusables/identity-and-permissions/team-sync-disable.md deleted file mode 100644 index a5bd837718..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-disable.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Advertencia:** Cuando inhabilitas la sincronización de equipos, cualquier miembro del equipo que se haya asignado al equipo de {% data variables.product.prodname_dotcom %} a través de un grupo de IdP se eliminará del mismo y podría perder acceso a los repositorios. - -{% endwarning %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/es-XL/data/reusables/identity-and-permissions/team-sync-okta-requirements.md deleted file mode 100644 index 713633752f..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-okta-requirements.md +++ /dev/null @@ -1,5 +0,0 @@ -Para habilitar la sincronización de equipos para Okta, en tu administrador de IdP deberás: - -- Habilitar el SSO de SAML y SCIM para tu organización utilizando Okta. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML y SCIM utilizando Okta](/github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta)". -- Proporcionar la URL del inquilino para tu instancia de Okta. -- Generar un token de SSWS válido con permisos administrativos de solo lectura para tu instalación de Okta como usuario de servicio. Para obtener más información, consulta la sección [Crear el token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) y [Usuarios de servicio](https://help.okta.com/en/prod/Content/Topics/Adv_Server_Access/docs/service-users.htm) en la documentación de Okta. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-required-permissions.md b/translations/es-XL/data/reusables/identity-and-permissions/team-sync-required-permissions.md deleted file mode 100644 index f05f83f14a..0000000000 --- a/translations/es-XL/data/reusables/identity-and-permissions/team-sync-required-permissions.md +++ /dev/null @@ -1,6 +0,0 @@ -Para habilitar la sincronización de equipos con cualquier IdP, debes obtener acceso administrativo con tu IdP o trabajar con tu administrador de IdP para configurar la integración y los grupos de IdP. La persona que configura tus grupos e integración de IdP debe tener alguno de los permisos requeridos. - - | IdP | Permisos requeridos | - | -------- | ------------------------- | - | Azure AD |
    • Administrador global
    • Administrador de Rol Privilegiado
    | - | Okta |
    • Usuario de servicio con permisos administrativos de solo lectura
    | diff --git a/translations/es-XL/data/reusables/interactions/collaborator-user-limit-definition.md b/translations/es-XL/data/reusables/interactions/collaborator-user-limit-definition.md deleted file mode 100644 index 30ae6cae5a..0000000000 --- a/translations/es-XL/data/reusables/interactions/collaborator-user-limit-definition.md +++ /dev/null @@ -1 +0,0 @@ -**Solo para colaboradores:** Cuando limitas las interacciones para `collaborators_only`, se restringirá temporalmente a los usuarios que no sean colaboradores \ No newline at end of file diff --git a/translations/es-XL/data/reusables/interactions/contributor-user-limit-definition.md b/translations/es-XL/data/reusables/interactions/contributor-user-limit-definition.md deleted file mode 100644 index c6a46d3188..0000000000 --- a/translations/es-XL/data/reusables/interactions/contributor-user-limit-definition.md +++ /dev/null @@ -1 +0,0 @@ -**Solo para contribuyentes:** Cuando limitas las interacciones para `contributors_only`, se restringirá temporalmente a los usuarios que no hayan hecho contribuciones anteriormente y que no sean colaboradores \ No newline at end of file diff --git a/translations/es-XL/data/reusables/interactions/existing-user-limit-definition.md b/translations/es-XL/data/reusables/interactions/existing-user-limit-definition.md deleted file mode 100644 index 946831df1e..0000000000 --- a/translations/es-XL/data/reusables/interactions/existing-user-limit-definition.md +++ /dev/null @@ -1 +0,0 @@ -**Usuarios existentes:** Cuando limitas las interacciones a `existing_users`, se restringirá temporalmente a los usuarios nuevos con cuentas de menos de 24 horas que no hayan hecho contribuciones anteriormente y que no sean colaboradores \ No newline at end of file diff --git a/translations/es-XL/data/reusables/interactions/interactions-detail.md b/translations/es-XL/data/reusables/interactions/interactions-detail.md deleted file mode 100644 index cd90f08c52..0000000000 --- a/translations/es-XL/data/reusables/interactions/interactions-detail.md +++ /dev/null @@ -1 +0,0 @@ -Cuando se habilitan las restricciones, solo el grupo de usuarios de {% data variables.product.product_name %} que hayas especificado podrá participar en las interacciones. Las restricciones caducan 24 horas después de la hora en la que se configuraron. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/issue-events/assignee-properties.md b/translations/es-XL/data/reusables/issue-events/assignee-properties.md deleted file mode 100644 index 2d4dc5badc..0000000000 --- a/translations/es-XL/data/reusables/issue-events/assignee-properties.md +++ /dev/null @@ -1 +0,0 @@ -`assignee` | `object` | La persona a la que se desasignó del informe de problemas. `assigner` | `object` | La persona que realizó la desasignación para este informe de problemas. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/issue-events/issue-event-common-properties.md b/translations/es-XL/data/reusables/issue-events/issue-event-common-properties.md deleted file mode 100644 index 420d46d294..0000000000 --- a/translations/es-XL/data/reusables/issue-events/issue-event-common-properties.md +++ /dev/null @@ -1,10 +0,0 @@ -| Nombre | Tipo | Descripción | -| ------------------------ | ----------- | ----------------------------------------------------------------------------------------------------- | -| `id` | `número` | El identificador único del evento. | -| `node_id` | `secuencia` | La [ID de Nodo Global](/v4/guides/using-global-node-ids) del evento. | -| `url` | `secuencia` | La URL de la API de REST para recuperar el evento. | -| `actor (actor)` | `objeto` | La persona que generó el evento. | -| `event` | `secuencia` | Identifica el tipo de evento real que ocurrió. | -| `commit_id` | `secuencia` | EL SHA de la confirmación que referenció este informe de problemas. | -| `commit_url` | `secuencia` | El enlace a la API de REST de GitHub para la confirmación que referenció a este informe de problemas. | -| `created_at (creado en)` | `secuencia` | La marca de tiempo que indica cuándo ocurrió el evento. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/issue-events/label-properties.md b/translations/es-XL/data/reusables/issue-events/label-properties.md deleted file mode 100644 index 11d26d653a..0000000000 --- a/translations/es-XL/data/reusables/issue-events/label-properties.md +++ /dev/null @@ -1 +0,0 @@ -`label` | `object` | La etiqueta que se eliminó del informe de problemas `label[name]` | `string` | El nombre de la etiqueta. `label[color]` | `string` | El código de color en hexadecimal. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/issue-events/project-card-properties.md b/translations/es-XL/data/reusables/issue-events/project-card-properties.md deleted file mode 100644 index f75188c90d..0000000000 --- a/translations/es-XL/data/reusables/issue-events/project-card-properties.md +++ /dev/null @@ -1 +0,0 @@ -`project_card` | `object` | El objeto de la tarjeta de proyecto. `project_id` | `integer` | El identificador único de la tarjeta de proyecto. `project_url` | `string` | La URL de la API de REST que recuperará la tarjeta de proyecto. `column_name` | `string` | El nombre de la columna en la cual está el informe de problemas. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/issue-events/review-dismissed-properties.md b/translations/es-XL/data/reusables/issue-events/review-dismissed-properties.md deleted file mode 100644 index e285192bea..0000000000 --- a/translations/es-XL/data/reusables/issue-events/review-dismissed-properties.md +++ /dev/null @@ -1 +0,0 @@ -`dismissed_review` | `object` | La información de la revisión que se descartó. `dismissed_review[state]` | `string` | El estado en el que se encontraba la solicitud de extracción cuando se descartó. Puede ser uno de entre: `commented`, `approved`, o `changes_requested`. `dismissed_review[review_id]` | `string` | El identificador único de la revisión de la solicitud de extracción. `dismissed_review[dismissal_message]` | `string` | El mensaje que incluyó el usuario cuando descartó la revisión. `dismissed_review[dismissal_commit_id]` | `string` | el Identificador único de la confirmación que descartó la revisión si es que existe. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/issue-events/review-request-properties.md b/translations/es-XL/data/reusables/issue-events/review-request-properties.md deleted file mode 100644 index ce213ffa6d..0000000000 --- a/translations/es-XL/data/reusables/issue-events/review-request-properties.md +++ /dev/null @@ -1 +0,0 @@ -`requested_reviewer` | `object` | La persona a la que se le solicitó revisar la solicitud de extracción. `review_requester` | `object` | La persona que solicitó una revisión. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/issue-events/timeline_events_object_properties.md b/translations/es-XL/data/reusables/issue-events/timeline_events_object_properties.md deleted file mode 100644 index 9743a09b2b..0000000000 --- a/translations/es-XL/data/reusables/issue-events/timeline_events_object_properties.md +++ /dev/null @@ -1 +0,0 @@ -Las propiedades de este evento no utilizan la misma estructura que las [propiedades comunes del objeto del evento para el informe de problemas](#issue-event-object-common-properties). Se devolverán las siguientes propiedades para este evento. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/es-XL/data/reusables/large_files/can-include-lfs-objects-archives.md deleted file mode 100644 index e2bb61154f..0000000000 --- a/translations/es-XL/data/reusables/large_files/can-include-lfs-objects-archives.md +++ /dev/null @@ -1,5 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} - -Puedes 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 de código fuente, tales como los archivos ZIP y .tar, que {% data variables.product.product_name %} crea para tu 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)". - -{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/large_files/does_not_carry.md b/translations/es-XL/data/reusables/large_files/does_not_carry.md deleted file mode 100644 index ff56a4b989..0000000000 --- a/translations/es-XL/data/reusables/large_files/does_not_carry.md +++ /dev/null @@ -1 +0,0 @@ -El ancho de banda no utilizado no se puede utilizar de un mes a otro. diff --git a/translations/es-XL/data/reusables/large_files/downgrade_data_packs.md b/translations/es-XL/data/reusables/large_files/downgrade_data_packs.md deleted file mode 100644 index 24574b76b0..0000000000 --- a/translations/es-XL/data/reusables/large_files/downgrade_data_packs.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de "Bajar de categoría el plan de datos", selecciona la cantidad de paquetes de datos a la que quieras bajar. ![Escoge la nueva cantidad de paquetes de datos que quieres](/assets/images/help/large_files/downgrade_number_of_data_packs.png) -2. Para terminar la operación, da clic en **Bajar de categoría el plan de datos**. ![Termina de bajar tu plan de categoría](/assets/images/help/large_files/downgrade_data_plan.png) diff --git a/translations/es-XL/data/reusables/large_files/free-storage-bandwidth-amount.md b/translations/es-XL/data/reusables/large_files/free-storage-bandwidth-amount.md deleted file mode 100644 index 968fc39ad9..0000000000 --- a/translations/es-XL/data/reusables/large_files/free-storage-bandwidth-amount.md +++ /dev/null @@ -1 +0,0 @@ -Cada cuenta que utilice {% data variables.large_files.product_name_long %} recibe {% data variables.large_files.initial_storage_quota %} de almacenamiento gratuito y {% data variables.large_files.initial_bandwidth_quota %} un mes de ancho de banda gratuito. Si las cuotas de ancho de banda y de almacenamiento no son suficientes, puedes decidir comprar una cuota adicional para {% data variables.large_files.product_name_short %}. diff --git a/translations/es-XL/data/reusables/large_files/owner_quota_only.md b/translations/es-XL/data/reusables/large_files/owner_quota_only.md deleted file mode 100644 index 4eaca49fa3..0000000000 --- a/translations/es-XL/data/reusables/large_files/owner_quota_only.md +++ /dev/null @@ -1 +0,0 @@ -El uso de almacenamiento y ancho de banda solo se descuenta de las cuotas de los repositorios de los propietarios. En las bifurcaciones, el uso de almacenamiento y ancho de banda se descuenta de la raíz de la red del repositorio. Cualquiera con acceso de escritura en un repositorio puede subir archivos a {% data variables.large_files.product_name_short %} sin afectar sus cuotas personales de almacenamiento y ancho de banda o sin comprar paquetes de datos. Bifurcar y extraer un repositorio se descuenta de el límite de ancho de banda del repositorio padre. diff --git a/translations/es-XL/data/reusables/large_files/pack_confirm.md b/translations/es-XL/data/reusables/large_files/pack_confirm.md deleted file mode 100644 index c14155a076..0000000000 --- a/translations/es-XL/data/reusables/large_files/pack_confirm.md +++ /dev/null @@ -1 +0,0 @@ -1. Para confirmar las cantidades en tu nuevo paquete de datos mensual, da clic en **Comprar**. ![Botón para comprar más maquetes de datos](/assets/images/help/billing/data-pack-purchase-button.png) diff --git a/translations/es-XL/data/reusables/large_files/pack_selection.md b/translations/es-XL/data/reusables/large_files/pack_selection.md deleted file mode 100644 index a5e2cdd6b8..0000000000 --- a/translations/es-XL/data/reusables/large_files/pack_selection.md +++ /dev/null @@ -1 +0,0 @@ -1. Ingresa la cantidad de paquetes de datos que quieres agregar a tu cuenta. Cada paquete cuesta {% data variables.large_files.pack_monthly_price %}, y proporciona {% data variables.large_files.pack_monthly_bandwidth %} de ancho de banda y {% data variables.large_files.pack_monthly_storage %} de almacenamiento. ![Botón para comprar más maquetes de datos](/assets/images/help/billing/data-pack-quantity-selector.png) diff --git a/translations/es-XL/data/reusables/large_files/rejected_pushes.md b/translations/es-XL/data/reusables/large_files/rejected_pushes.md deleted file mode 100644 index 551b3bee67..0000000000 --- a/translations/es-XL/data/reusables/large_files/rejected_pushes.md +++ /dev/null @@ -1 +0,0 @@ -Los usuarios no pueden subir activos {% data variables.large_files.product_name_short %} a {% data variables.product.prodname_ghe_server %} si {% data variables.large_files.product_name_short %} está inhabilitado en el aparato o en el repositorio. diff --git a/translations/es-XL/data/reusables/large_files/resolving-upload-failures.md b/translations/es-XL/data/reusables/large_files/resolving-upload-failures.md deleted file mode 100644 index f6194b7ee1..0000000000 --- a/translations/es-XL/data/reusables/large_files/resolving-upload-failures.md +++ /dev/null @@ -1 +0,0 @@ -Si existen archivos de {% data variables.large_files.product_name_short %} referenciados que no se cargaron con éxito, recibiras un mensaje de error. Para obtener más información, consulta la sección "[Resolver fallas de carga de {% data variables.large_files.product_name_long %}](/articles/resolving-git-large-file-storage-upload-failures)". diff --git a/translations/es-XL/data/reusables/large_files/storage_assets_location.md b/translations/es-XL/data/reusables/large_files/storage_assets_location.md deleted file mode 100644 index ecf863bf05..0000000000 --- a/translations/es-XL/data/reusables/large_files/storage_assets_location.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, el cliente de {% data variables.large_files.product_name_long %} almacena activos grandes en el mismo servidor que hospeda al repositorio de Git. Cuando se habilita {% data variables.large_files.product_name_short %} en el aplicativo de {% data variables.product.prodname_ghe_server %}, los activos grandes se guardan en la particion de datos de `/data/user/storage`. diff --git a/translations/es-XL/data/reusables/large_files/use_lfs_tip.md b/translations/es-XL/data/reusables/large_files/use_lfs_tip.md deleted file mode 100644 index 793474127b..0000000000 --- a/translations/es-XL/data/reusables/large_files/use_lfs_tip.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Tip:** Si subes archivos grandes a {% data variables.product.product_location %} frecuentemente, considera utilizar {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obtener más información, consulta "[Control de versiones de archivos grandes](/articles/versioning-large-files)." - -{% endtip %} diff --git a/translations/es-XL/data/reusables/linux/ensure-docker.md b/translations/es-XL/data/reusables/linux/ensure-docker.md deleted file mode 100644 index af323f3fe3..0000000000 --- a/translations/es-XL/data/reusables/linux/ensure-docker.md +++ /dev/null @@ -1 +0,0 @@ -1. [Asegúrate de que Docker se instaló](https://www.docker.com/) localmente. diff --git a/translations/es-XL/data/reusables/marketplace/add-payment-method-org.md b/translations/es-XL/data/reusables/marketplace/add-payment-method-org.md deleted file mode 100644 index 1dac024356..0000000000 --- a/translations/es-XL/data/reusables/marketplace/add-payment-method-org.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Si eliges un plan pago, revisa tu método de pago. - - Para cambiar el método de pago existente en el archivo para tu organización, haz clic en **Edit...(Editar...)**, a continuación completa el formulario para agregar un nuevo método de pago. Después de agregar con éxito un nuevo método de pago, regresarás automáticamente a la página de orden. ![Enlace para agregar un método de pago para tu organización](/assets/images/help/marketplace/marketplace-edit-payment-method-org.png) - - Si no hay un método de pago en el archivo para la organización, haz clic en **Add a Payment Method (Agregar método de pago)**, a continuación completa el formulario para agregar una tarjeta de crédito o una cuenta de PayPal. ![Enlace para agregar un método de pago para tu organización](/assets/images/help/marketplace/marketplace-add-payment-method-org.png) diff --git a/translations/es-XL/data/reusables/marketplace/add-payment-method-personal.md b/translations/es-XL/data/reusables/marketplace/add-payment-method-personal.md deleted file mode 100644 index 1c6b4a778e..0000000000 --- a/translations/es-XL/data/reusables/marketplace/add-payment-method-personal.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Si eliges un plan pago, revisa tu método de pago. - - Para cambiar el método de pago existente en el archivo para tu cuenta personal, haz clic en **Edit...(Editar...)**, a continuación completa el formulario para agregar un nuevo método de pago. Después de agregar con éxito un nuevo método de pago, regresarás automáticamente a la página de orden. ![Enlace para agregar un método de pago para tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-payment-method-personal.png) - - Si no hay un método de pago en el archivo para tu cuenta personal, haz clic en **Add a Payment Method (Agregar método de pago)**, a continuación completa el formulario para agregar una tarjeta de crédito o una cuenta de PayPal. ![Enlace para agregar un método de pago para tu cuenta personal](/assets/images/help/marketplace/marketplace-add-payment-method-personal.png) diff --git a/translations/es-XL/data/reusables/marketplace/browse-to-app.md b/translations/es-XL/data/reusables/marketplace/browse-to-app.md deleted file mode 100644 index ecf5ea3ed0..0000000000 --- a/translations/es-XL/data/reusables/marketplace/browse-to-app.md +++ /dev/null @@ -1 +0,0 @@ -1. Navega hasta la app que deseas instalar y luego haz clic en el nombre de la app. diff --git a/translations/es-XL/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/es-XL/data/reusables/marketplace/cancel-app-billing-settings.md deleted file mode 100644 index aad15ed791..0000000000 --- a/translations/es-XL/data/reusables/marketplace/cancel-app-billing-settings.md +++ /dev/null @@ -1 +0,0 @@ -1. Utiliza el menú desplegable de **Editar** y da clic en **Cancelar plan**. ![Enlace de cancelación en la sección de Compras de Marketplace de tu configuración de facturación para tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png) diff --git a/translations/es-XL/data/reusables/marketplace/cancel-app.md b/translations/es-XL/data/reusables/marketplace/cancel-app.md deleted file mode 100644 index 254a5132c7..0000000000 --- a/translations/es-XL/data/reusables/marketplace/cancel-app.md +++ /dev/null @@ -1 +0,0 @@ -1. En el cuadro de diálogo, da clic en **OK**. diff --git a/translations/es-XL/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/es-XL/data/reusables/marketplace/cancel-free-trial-billing-settings.md deleted file mode 100644 index 5ff8eeb3ff..0000000000 --- a/translations/es-XL/data/reusables/marketplace/cancel-free-trial-billing-settings.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Suscripciones", a un costado de la prueba gratuita que quieres cancelar, utiliza el menú desplegable de Editar y da clic en **Cancelar Plan**. diff --git a/translations/es-XL/data/reusables/marketplace/cancellation-clarification.md b/translations/es-XL/data/reusables/marketplace/cancellation-clarification.md deleted file mode 100644 index 9d0e73d752..0000000000 --- a/translations/es-XL/data/reusables/marketplace/cancellation-clarification.md +++ /dev/null @@ -1 +0,0 @@ -Cuando un cliente cancela una suscripción de {% data variables.product.prodname_marketplace %}, GitHub no desinstala la app automáticamente, así que el cliente puede esperar que las características gratuitas sigan funcionando. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/marketplace/choose-new-plan.md b/translations/es-XL/data/reusables/marketplace/choose-new-plan.md deleted file mode 100644 index 06d77434ca..0000000000 --- a/translations/es-XL/data/reusables/marketplace/choose-new-plan.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Editar tu plan", utiliza el menú desplegable y da clic en un nuevo plan. ![Menú desplegable listando todos los planes disponibles de la app](/assets/images/help/marketplace/marketplace-choose-new-plan.png) diff --git a/translations/es-XL/data/reusables/marketplace/choose-new-quantity.md b/translations/es-XL/data/reusables/marketplace/choose-new-quantity.md deleted file mode 100644 index f4bb23e509..0000000000 --- a/translations/es-XL/data/reusables/marketplace/choose-new-quantity.md +++ /dev/null @@ -1 +0,0 @@ -1. Si eliges un plan unitario, teclea una nueva cantidad. ![Campo para ingresar una nueva cantidad para un plan unitario](/assets/images/help/marketplace/marketplace-new-quantity.png) diff --git a/translations/es-XL/data/reusables/marketplace/choose-plan.md b/translations/es-XL/data/reusables/marketplace/choose-plan.md deleted file mode 100644 index feb401cec6..0000000000 --- a/translations/es-XL/data/reusables/marketplace/choose-plan.md +++ /dev/null @@ -1 +0,0 @@ -1. En la página de la aplicación, debajo de "Configuración y precios", da clic en el plan de precios que quieres utilizar. ![Lista de aplicaciones disponibles en los planes de precios](/assets/images/help/marketplace/marketplace-choose-plan.png) diff --git a/translations/es-XL/data/reusables/marketplace/complete-order-begin-installation.md b/translations/es-XL/data/reusables/marketplace/complete-order-begin-installation.md deleted file mode 100644 index b435e46e7f..0000000000 --- a/translations/es-XL/data/reusables/marketplace/complete-order-begin-installation.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en "**Completar orden y comenzar instalación**. ![Botón para completar orden y comenzar instalación](/assets/images/help/marketplace/marketplace-complete-order-begin-installation-button.png) diff --git a/translations/es-XL/data/reusables/marketplace/confirm-install-account-org.md b/translations/es-XL/data/reusables/marketplace/confirm-install-account-org.md deleted file mode 100644 index 06ee778967..0000000000 --- a/translations/es-XL/data/reusables/marketplace/confirm-install-account-org.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Información de Facturación", utiliza el menú desplegable de Cambiar de cuenta de facturación y escoge la organización en la cual quieres instalar la aplicación. ![Menú desplegable para cambiar de cuenta de facturación y el nombre y avatar que escogiste para la organización](/assets/images/help/marketplace/marketplace-confirm-org.png) diff --git a/translations/es-XL/data/reusables/marketplace/confirm-install-account-personal.md b/translations/es-XL/data/reusables/marketplace/confirm-install-account-personal.md deleted file mode 100644 index 376149eb4e..0000000000 --- a/translations/es-XL/data/reusables/marketplace/confirm-install-account-personal.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Información de Facturación", confirma que estás reinstalando la aplicación para tu cuenta personal. ![Tu nombre, tu avatar, el texto "Cuenta personal" y un menú desplegable para cambiar de cuenta de facturación](/assets/images/help/marketplace/marketplace-confirm-personal-account.png) diff --git a/translations/es-XL/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/es-XL/data/reusables/marketplace/downgrade-app-billing-settings.md deleted file mode 100644 index 597ce6e4b0..0000000000 --- a/translations/es-XL/data/reusables/marketplace/downgrade-app-billing-settings.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Tu suscripción", junto a la aplicación a la cual quieres bajar, utiliza el menú desplegable de Editar y da clic en **Cambiar plan** o **Cancelar plan**. ![Enlace de editar en la sección de Compras de Marketplace para la configuración de facturación en tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png) diff --git a/translations/es-XL/data/reusables/marketplace/downgrade-marketplace-only.md b/translations/es-XL/data/reusables/marketplace/downgrade-marketplace-only.md deleted file mode 100644 index 9288de4d96..0000000000 --- a/translations/es-XL/data/reusables/marketplace/downgrade-marketplace-only.md +++ /dev/null @@ -1 +0,0 @@ -El cancelar una app o bajarla de categoría a la versión gratuita no afecta tus [otras suscripciones pagadas](/articles/about-billing-on-github) en {% data variables.product.prodname_dotcom %}. Si deseas cancelar todas tus suscripciones pagas en {% data variables.product.prodname_dotcom %}, debes bajar de categoría cada suscripción paga por separado. diff --git a/translations/es-XL/data/reusables/marketplace/free-apps-encouraged.md b/translations/es-XL/data/reusables/marketplace/free-apps-encouraged.md deleted file mode 100644 index 47bb2bc12d..0000000000 --- a/translations/es-XL/data/reusables/marketplace/free-apps-encouraged.md +++ /dev/null @@ -1 +0,0 @@ -Se exhorta a que hayan aplicaciones gratuitas en {% data variables.product.prodname_marketplace %}, y también son una gran forma de ofrecer servicios de código abierto. Si listas una versión de paga de tu app fuera de {% data variables.product.prodname_marketplace %}, deberás ofrecer por lo menos un plan de pago cuando la lsitas en {% data variables.product.prodname_marketplace %}. diff --git a/translations/es-XL/data/reusables/marketplace/free-trials.md b/translations/es-XL/data/reusables/marketplace/free-trials.md deleted file mode 100644 index e4bfe03466..0000000000 --- a/translations/es-XL/data/reusables/marketplace/free-trials.md +++ /dev/null @@ -1 +0,0 @@ -Si eliges un plan pagado con prueba gratuita, puedes cancelarlo en cualquier momento durante tu periodo de prueba sin que se te cobre, pero perderás acceso a la app automáticamente. Tu suscripción paga comenzará al finalizar la prueba de 14 días. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". diff --git a/translations/es-XL/data/reusables/marketplace/github_apps_preferred.md b/translations/es-XL/data/reusables/marketplace/github_apps_preferred.md deleted file mode 100644 index d0dc86e09c..0000000000 --- a/translations/es-XL/data/reusables/marketplace/github_apps_preferred.md +++ /dev/null @@ -1 +0,0 @@ -Las GitHub Apps son la forma oficial y recomendada de integrarse con GitHub, ya que ofrecen permisos mucho más granulares para acceder a los datos \ No newline at end of file diff --git a/translations/es-XL/data/reusables/marketplace/install-buy.md b/translations/es-XL/data/reusables/marketplace/install-buy.md deleted file mode 100644 index 4b01765d4b..0000000000 --- a/translations/es-XL/data/reusables/marketplace/install-buy.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Instalar gratuitamente**, **Comprar con {% data variables.product.prodname_dotcom %}**, o **Evaluar gratuitamente por 14 días**. ![Botón de comprar con {% data variables.product.prodname_dotcom %}](/assets/images/help/marketplace/marketplace-buy-with-github-button.png) diff --git a/translations/es-XL/data/reusables/marketplace/issue-plan-changes.md b/translations/es-XL/data/reusables/marketplace/issue-plan-changes.md deleted file mode 100644 index 631433c517..0000000000 --- a/translations/es-XL/data/reusables/marketplace/issue-plan-changes.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa la información de tu nuevo plan e información de facturación, después, da clic en **Emitir cambios de plan**. ![Resumen de tu plan anterior, plan nuevo, e información de facturación, y botón de emitir cambios de plan](/assets/images/help/marketplace/marketplace-issue-plan-changes.png) diff --git a/translations/es-XL/data/reusables/marketplace/launch-with-free.md b/translations/es-XL/data/reusables/marketplace/launch-with-free.md deleted file mode 100644 index eb39ac397f..0000000000 --- a/translations/es-XL/data/reusables/marketplace/launch-with-free.md +++ /dev/null @@ -1 +0,0 @@ -Puedes emitir ambas, una app sin verificar y una verificada. Esto te permitirá hacer el lanzamiento con una versión gratuita de tu app. Una vez que GitHub verifique tu app, tu listado cambiará de sin verificar a verificado en {% data variables.product.prodname_marketplace %} y GitHub publicará tus planes de precios nuevos. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/marketplace/marketplace-apps-only.md b/translations/es-XL/data/reusables/marketplace/marketplace-apps-only.md deleted file mode 100644 index cc934e2a0f..0000000000 --- a/translations/es-XL/data/reusables/marketplace/marketplace-apps-only.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Este artículo aplica únicamente para las apps de instalación y compra de {% data variables.product.prodname_marketplace %}. Para obtener más información sobre las apps compradas a un integrador, consulta la sección "[Acerca de las integraciones](/articles/about-integrations)". - -{% endnote %} diff --git a/translations/es-XL/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/es-XL/data/reusables/marketplace/marketplace-billing-ui-requirements.md deleted file mode 100644 index a12daab943..0000000000 --- a/translations/es-XL/data/reusables/marketplace/marketplace-billing-ui-requirements.md +++ /dev/null @@ -1,9 +0,0 @@ -- Los clientes que cancelan un plan de pago que se haya comprado en {% data variables.product.prodname_marketplace %} deben degradar su versión automáticamente al plan gratuito de la app en caso de que éste exista. Se recomienda ampliamente la {% data reusables.marketplace.cancellation-clarification %} para permitir a los usuarios el rehabilitar su plan previo. -- Los clientes deben poder mejorar la versión de tu app desde la IU de la misma si proporcionas una [URL de mejora](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) en este formato: `https://www.github.com/marketplace//upgrade//` -- Los clientes deben poder modificar qué usuarios tienen acceso a tu app desde el sitio web de la misma si compraron plazas (plan de precios por unidad) o si el plan ofrece colaboradores ilimitados. -- Los clientes deben poder ver los siguientes cambios a su cuenta inmediatamente en la sección de facturación, perfil, o configuración de cuenta del sitio web de la app: - - Plan y precios actuales. - - Nuevos planes comprados. - - Mejoras, degradaciones, cancelaciones y la cantidad de días restantes del periodo de prueba gratuito. - - Cambios en los ciclos de facturación (mensual o anual). - - Uso y recursos restantes para los planes por unidad y de tasa fija. Por ejemplo, si el plan de precios es por unidad, el sitio de tu app debería mostrar las unidades que se utilizan y las que quedan disponibles. diff --git a/translations/es-XL/data/reusables/marketplace/marketplace-double-purchases.md b/translations/es-XL/data/reusables/marketplace/marketplace-double-purchases.md deleted file mode 100644 index 54100607a9..0000000000 --- a/translations/es-XL/data/reusables/marketplace/marketplace-double-purchases.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Nota:** En la versión actual de {% data variables.product.prodname_marketplace %}, es posible que un cliente compre tu app a través de {% data variables.product.prodname_marketplace %} cuando ya tienen una cuenta existente que se haya comprado desde el sitio web de tu app. Si te das cuenta de que ya tienes configurada una cuenta para el cliente que compró tu app, por favor reporta las compras "dobles" a [Soporte de GitHub](https://github.com/contact). - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/marketplace/marketplace-failed-purchase-event.md b/translations/es-XL/data/reusables/marketplace/marketplace-failed-purchase-event.md deleted file mode 100644 index a4387296c0..0000000000 --- a/translations/es-XL/data/reusables/marketplace/marketplace-failed-purchase-event.md +++ /dev/null @@ -1 +0,0 @@ -En caso de que un cliente mejore su plan y el pago falle, GitHub revertirá su suscripción de {% data variables.product.prodname_marketplace %} a su estado previo. GitHub también enviará un correo electrónico al cliente para informarle de dicho fallo y para permitirles volver a intentar la compra. Recibirás un webhook con la acción como `changed`, el cual te solicitará revertir el estado de la app al plan previo. diff --git a/translations/es-XL/data/reusables/marketplace/marketplace-malicious-behavior.md b/translations/es-XL/data/reusables/marketplace/marketplace-malicious-behavior.md deleted file mode 100644 index e56ebb9887..0000000000 --- a/translations/es-XL/data/reusables/marketplace/marketplace-malicious-behavior.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Si notas cualquier compra de {% data variables.product.prodname_marketplace %} que genera spam o que presenta cualquier otro comportamiento malicioso, por favor, completa el formato de [reportar abuso](https://github.com/contact/report-abuse) con más información sobre el usuario. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/marketplace/marketplace-org-perms.md b/translations/es-XL/data/reusables/marketplace/marketplace-org-perms.md deleted file mode 100644 index aec00d27c0..0000000000 --- a/translations/es-XL/data/reusables/marketplace/marketplace-org-perms.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - - **Tip**: Si una app requiere acceso a nivel organizacional, entonces sólo el propietario de la organización podrá comprarla, instalarla o cancelarla, así como administrar la facturación de la app para dicha organización. Si la app no requiere acceso a nivel organizacional, entonces cualquier administrador de repositorio podrá instalarla y desinstalarla. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/marketplace/marketplace-pricing-free-trials.md b/translations/es-XL/data/reusables/marketplace/marketplace-pricing-free-trials.md deleted file mode 100644 index 86f56d1553..0000000000 --- a/translations/es-XL/data/reusables/marketplace/marketplace-pricing-free-trials.md +++ /dev/null @@ -1 +0,0 @@ -Puedes ofrecer tu app gratuitamente por 14 días como un periodo de prueba gratuito. Los periodos de prueba gratuitos se convierten en suscripciones pagadas después de 14 días, a menos de que el cliente las cancele antes de que caduque dicho periodo de prueba gratuito. Selecciona "Habilitar el periodo de prueba gratuito de 14 días para este plan" para ofrecer un periodo de prueba gratuito. diff --git a/translations/es-XL/data/reusables/marketplace/review-app-perms-install.md b/translations/es-XL/data/reusables/marketplace/review-app-perms-install.md deleted file mode 100644 index 48bedff173..0000000000 --- a/translations/es-XL/data/reusables/marketplace/review-app-perms-install.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa los permisos de acceso a la app y después da clic en **Instalar**. diff --git a/translations/es-XL/data/reusables/marketplace/select-installation-repos.md b/translations/es-XL/data/reusables/marketplace/select-installation-repos.md deleted file mode 100644 index b774e51e6f..0000000000 --- a/translations/es-XL/data/reusables/marketplace/select-installation-repos.md +++ /dev/null @@ -1 +0,0 @@ -1. Si eliges otorgar acceso a la app para ingresar a repositorios limitados en vez de a todos tus repositorios, teclea el nombre de cada repositorio al cual quieras otorgarle acceso, y posteriormente da clic en el nombre de cada repositorio para seleccionarlo. ![Campo para seleccionar los repositorios a los cuales dejarás ingresar a la app](/assets/images/help/marketplace/marketplace-select-repo-field.png) diff --git a/translations/es-XL/data/reusables/marketplace/unverified-apps.md b/translations/es-XL/data/reusables/marketplace/unverified-apps.md deleted file mode 100644 index 5d9828e82c..0000000000 --- a/translations/es-XL/data/reusables/marketplace/unverified-apps.md +++ /dev/null @@ -1 +0,0 @@ -Las apps sin verificar solo se ofrecen con planes gratuitos. Para listar los planes de pago, debes emitir una app verificada. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/es-XL/data/reusables/marketplace/upgrade-app-billing-settings.md deleted file mode 100644 index fdda91148f..0000000000 --- a/translations/es-XL/data/reusables/marketplace/upgrade-app-billing-settings.md +++ /dev/null @@ -1 +0,0 @@ -1. Utiliza el menú desplegable de **Editar** y da clic en **Cambiar plan**. ![Menú desplegable de editar en la sección de compras de Marketplace para tu configuración de facturación en tu cuenta personal](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png) diff --git a/translations/es-XL/data/reusables/marketplace/visit-marketplace.md b/translations/es-XL/data/reusables/marketplace/visit-marketplace.md deleted file mode 100644 index 1a8b4ffaa6..0000000000 --- a/translations/es-XL/data/reusables/marketplace/visit-marketplace.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de cualquier página, da clic en **Mercado**. ![Enlace de Marketplace en el menú de navegación global en la parte superior de todas las páginas](/assets/images/help/marketplace/marketplace-link-global-navigation.png) diff --git a/translations/es-XL/data/reusables/notifications-v2/email-notification-caveats.md b/translations/es-XL/data/reusables/notifications-v2/email-notification-caveats.md deleted file mode 100644 index 7c06013543..0000000000 --- a/translations/es-XL/data/reusables/notifications-v2/email-notification-caveats.md +++ /dev/null @@ -1,5 +0,0 @@ -Solo recibirás correo electrónicos de notificación si optaste por recibir notificaciones por correo electrónico en los ajustes de las notificaciones. - -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.user_settings.verify-org-approved-email-domain %} -{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/notifications-v2/manage-notifications.md b/translations/es-XL/data/reusables/notifications-v2/manage-notifications.md deleted file mode 100644 index 4e84e36cd5..0000000000 --- a/translations/es-XL/data/reusables/notifications-v2/manage-notifications.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral, debajo de la lista de repositorios, utiliza el menú desplegable "Administrar notificaciones" para dar clic en **Configuración de notificaciones**. ![Opciones del menú desplegable "Administrar notificaciones"](/assets/images/help/notifications-v2/manage-notifications-options.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/notifications-v2/notifications-inbox-required-setting.md b/translations/es-XL/data/reusables/notifications-v2/notifications-inbox-required-setting.md deleted file mode 100644 index 0f4bae8763..0000000000 --- a/translations/es-XL/data/reusables/notifications-v2/notifications-inbox-required-setting.md +++ /dev/null @@ -1 +0,0 @@ -Para utilizar la bandeja de notificaciones en {% data variables.product.prodname_dotcom %} y {% data variables.product.prodname_mobile %}, debes habilitar las notificaciones web y móviles en tu configuración de notificaciones. diff --git a/translations/es-XL/data/reusables/notifications-v2/tip-for-syncing-email-and-your-inbox-on-github.md b/translations/es-XL/data/reusables/notifications-v2/tip-for-syncing-email-and-your-inbox-on-github.md deleted file mode 100644 index 415496cbdb..0000000000 --- a/translations/es-XL/data/reusables/notifications-v2/tip-for-syncing-email-and-your-inbox-on-github.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Tip:** Si recibes notificaciones tanto por web como por correo electrónico, puedes sincronizar automáticamente el estado de leído o no leído de las mismas para que las notificaciones web se marquen automaticamente como leídas una vez que las leas en tu correo electrónico correspondiente. Para habilitar esta sincronización, tu cliente de correo electrónico debe poder visualizar imágenes de 'notifications@github.com'. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/notifications/access_notifications.md b/translations/es-XL/data/reusables/notifications/access_notifications.md deleted file mode 100644 index a8d9e597cb..0000000000 --- a/translations/es-XL/data/reusables/notifications/access_notifications.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de cualquier página, da clic en {% octicon "bell" aria-label="The notifications bell" %}. ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) diff --git a/translations/es-XL/data/reusables/notifications/access_watching.md b/translations/es-XL/data/reusables/notifications/access_watching.md deleted file mode 100644 index 72e49c0f84..0000000000 --- a/translations/es-XL/data/reusables/notifications/access_watching.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de cualquier página, haz clic en {% octicon "bell" aria-label="The notifications bell" %}. Si [inhabilitaste las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications) y no ves el icono de campana, puedes navegar a . ![Notificación que indica cualquier mensaje no leído](/assets/images/help/notifications/notifications_general_existence_indicator.png) diff --git a/translations/es-XL/data/reusables/notifications/auto-watch.md b/translations/es-XL/data/reusables/notifications/auto-watch.md deleted file mode 100644 index c38428d3a1..0000000000 --- a/translations/es-XL/data/reusables/notifications/auto-watch.md +++ /dev/null @@ -1 +0,0 @@ -Observarás automáticamente a todos los repositorios que crees y que pertenezcan a tu cuenta de usuario. También puedes elegir seguir automáticamente todos los repositorios en los que tienes acceso de escritura, con excepción de sus bifurcaciones. Puedes observar cualquier otro repositorio manualmente. diff --git a/translations/es-XL/data/reusables/notifications/outbound_email_tip.md b/translations/es-XL/data/reusables/notifications/outbound_email_tip.md deleted file mode 100644 index 71ed4df747..0000000000 --- a/translations/es-XL/data/reusables/notifications/outbound_email_tip.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} - {% tip %} - - Únicamente recibirás notificaciones si habilitas el soporte para correo electrónico externo en {% data variables.product.product_location_enterprise %}. Para obtener más información, contacta a tu administrador de sitio. - - {% endtip %} -{% endif %} diff --git a/translations/es-XL/data/reusables/notifications/saved_for_late_sidebar.md b/translations/es-XL/data/reusables/notifications/saved_for_late_sidebar.md deleted file mode 100644 index 81155aeecf..0000000000 --- a/translations/es-XL/data/reusables/notifications/saved_for_late_sidebar.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, para ver tus notificaciones guardadas, da clic en **Guardado para después**. ![Botón de guardado para después](/assets/images/help/notifications/saved-for-later-tab.png) diff --git a/translations/es-XL/data/reusables/notifications/shared_state.md b/translations/es-XL/data/reusables/notifications/shared_state.md deleted file mode 100644 index 3bef620450..0000000000 --- a/translations/es-XL/data/reusables/notifications/shared_state.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Tip:** Si recibes notificaciones tanto por web como por correo electrónico, puedes sincronizar automáticamente el estado de leído o no leído de las mismas para que las notificaciones web se marquen automaticamente como leídas una vez que las leas en tu correo electrónico correspondiente. Para habililtar esta sincronización, tu cliente de correo electrónico debe poder visualizar imágenes de {% if currentVersion == "free-pro-team@latest" %}'`notifications@github.com`'{% else %} las direcciones de tipo no-reply que configuró tu administrador de sitio'{% endif %}. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/open-source/open-source-guide-general.md b/translations/es-XL/data/reusables/open-source/open-source-guide-general.md deleted file mode 100644 index 509030003d..0000000000 --- a/translations/es-XL/data/reusables/open-source/open-source-guide-general.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información sobre el código abierto, específicamente sobre como crear y hacer crecer un proyecto de código abierto, hemos creado unas [Guías de Código Abierto](https://opensource.guide/) que te ayudarán a fomentar una comunidad saludable. diff --git a/translations/es-XL/data/reusables/open-source/open-source-guide-repositories.md b/translations/es-XL/data/reusables/open-source/open-source-guide-repositories.md deleted file mode 100644 index b4e37a8ac1..0000000000 --- a/translations/es-XL/data/reusables/open-source/open-source-guide-repositories.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información acerca del código abierto, específicamente sobre cómo crear y hacer crecer un proyecto de código abierto, hemos creado las [Guías de Código Abierto](https://opensource.guide/) que te ayudarán fomentar una comunidad saludable mediante la recomendación de mejores prácticas para crear y mantener repositorios para tus proyectos de código abierto. diff --git a/translations/es-XL/data/reusables/open-source/open-source-learning-lab.md b/translations/es-XL/data/reusables/open-source/open-source-learning-lab.md deleted file mode 100644 index 25abe4991c..0000000000 --- a/translations/es-XL/data/reusables/open-source/open-source-learning-lab.md +++ /dev/null @@ -1 +0,0 @@ -También puedes tomar un curso gratuito de [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) sobre cómo mantener comunidades de código abierto. diff --git a/translations/es-XL/data/reusables/organizations/add-extension-to-cert.md b/translations/es-XL/data/reusables/organizations/add-extension-to-cert.md deleted file mode 100644 index 3902608f0f..0000000000 --- a/translations/es-XL/data/reusables/organizations/add-extension-to-cert.md +++ /dev/null @@ -1 +0,0 @@ -Cuando emites cada uno de los certificados de cliente, debes incluir una extensión que especifique para cuál usuario de {% data variables.product.product_name %} es cada uno de ellos. Para obtener más información, consulta [Acerca de las autoridades de certificación de SSH](/articles/about-ssh-certificate-authorities)". diff --git a/translations/es-XL/data/reusables/organizations/add-user-to-teams.md b/translations/es-XL/data/reusables/organizations/add-user-to-teams.md deleted file mode 100644 index 406d391932..0000000000 --- a/translations/es-XL/data/reusables/organizations/add-user-to-teams.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, agrega el usuario o equipos a la organización. ![Lista de los equipos de la organización](/assets/images/help/organizations/add-user-to-teams.png) diff --git a/translations/es-XL/data/reusables/organizations/app-managers-settings-sidebar.md b/translations/es-XL/data/reusables/organizations/app-managers-settings-sidebar.md deleted file mode 100644 index 3aa28b6399..0000000000 --- a/translations/es-XL/data/reusables/organizations/app-managers-settings-sidebar.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Administradores de la App**. ![Botón de administradores de la app en la barra lateral](/assets/images/help/organizations/app-managers-sidebar-button.png) diff --git a/translations/es-XL/data/reusables/organizations/billing.md b/translations/es-XL/data/reusables/organizations/billing.md deleted file mode 100644 index 38b46164e2..0000000000 --- a/translations/es-XL/data/reusables/organizations/billing.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de Configuración de tu organización, da clic en **Facturación**. ![Configuración de facturación](/assets/images/help/billing/settings_organization_billing_tab.png) diff --git a/translations/es-XL/data/reusables/organizations/block_users.md b/translations/es-XL/data/reusables/organizations/block_users.md deleted file mode 100644 index 94fa39e302..0000000000 --- a/translations/es-XL/data/reusables/organizations/block_users.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de Configuración de tu organización, da clic en **Usuarios bloqueados**. ![Usuarios bloqueados en la configuración de la organización](/assets/images/help/organizations/org-settings-block-users.png) diff --git a/translations/es-XL/data/reusables/organizations/can-require-ssh-cert.md b/translations/es-XL/data/reusables/organizations/can-require-ssh-cert.md deleted file mode 100644 index 5e09f73764..0000000000 --- a/translations/es-XL/data/reusables/organizations/can-require-ssh-cert.md +++ /dev/null @@ -1 +0,0 @@ -Puedes solicitar que los miembros usen certificados SSH para acceder a los recursos de la organización,{% if currentVersion ver_gt "enterprise-server@2.17" %}, a menos que SSH esté deshabilitado en tu repositorio {% endif %}. diff --git a/translations/es-XL/data/reusables/organizations/cancel_org_invite.md b/translations/es-XL/data/reusables/organizations/cancel_org_invite.md deleted file mode 100644 index fa0893709a..0000000000 --- a/translations/es-XL/data/reusables/organizations/cancel_org_invite.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Puedes [editar o cancelar una invitación](/articles/canceling-or-editing-an-invitation-to-join-your-organization) en cualquier momento después de que el usuario la acepte. -{% endif %} diff --git a/translations/es-XL/data/reusables/organizations/child-team-inherits-permissions.md b/translations/es-XL/data/reusables/organizations/child-team-inherits-permissions.md deleted file mode 100644 index e2fb2896f3..0000000000 --- a/translations/es-XL/data/reusables/organizations/child-team-inherits-permissions.md +++ /dev/null @@ -1 +0,0 @@ -Los equipos hijo heredan los permisos de acceso del equipo padre. Para obtener más información sobre las jerarquías de equipos, consulta la sección "[Acerca de los equipos](/articles/about-teams#nested-teams)". diff --git a/translations/es-XL/data/reusables/organizations/choose-to-restore-privileges.md b/translations/es-XL/data/reusables/organizations/choose-to-restore-privileges.md deleted file mode 100644 index db7d6fa123..0000000000 --- a/translations/es-XL/data/reusables/organizations/choose-to-restore-privileges.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}1. Si la persona que estás invitando era miembro de una organización en los tres meses pasados, escoge si quieres restaurar sus privilegios o comenzar desde cero, después, da clic en **Invitar y reinstaurar** o en **Invitar y comenzar desde cero**. - ![Decide si quieres restaurar los privilegios](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png){% else %} -1. Si la persona que estás agregando era miembro de una organización en los tres meses pasados, escoge si quieres restaurar sus privilegios o comenzar desde cero, después, da clic en **Agregar y reinstaurar** o en **Agregar y comenzar desde cero**. ![Choose whether to restore privileges](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png){% endif %} diff --git a/translations/es-XL/data/reusables/organizations/choose-user-license.md b/translations/es-XL/data/reusables/organizations/choose-user-license.md deleted file mode 100644 index 452ccd6044..0000000000 --- a/translations/es-XL/data/reusables/organizations/choose-user-license.md +++ /dev/null @@ -1 +0,0 @@ -1. Si tu organización pertenece a una cuenta empresarial con más de una licencia, escoge la licencia para el usuario. ![Opciones de licencia](/assets/images/help/organizations/choose-user-license.png) diff --git a/translations/es-XL/data/reusables/organizations/choose-user-role-send-invitation.md b/translations/es-XL/data/reusables/organizations/choose-user-role-send-invitation.md deleted file mode 100644 index e25c8b7b2f..0000000000 --- a/translations/es-XL/data/reusables/organizations/choose-user-role-send-invitation.md +++ /dev/null @@ -1,4 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}1. Si la persona que estás invitando nunca fue miembro de la organización o si eliminaste sus privilegios, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Send invitation** (Enviar invitación). - ![Opciones de rol y equipo y botón para enviar invitación](/assets/images/help/organizations/add-role-send-invitation.png){% else %} -1. Si la persona que estás invitando nunca fue miembro de la organización o si eliminaste sus privilegios, elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Add member** (Agregar miembro). ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png){% else %} -1. Elige un rol para el usuario y, de manera opcional, agrégalo a algunos equipos, luego haz clic en **Add member** (Agregar miembro). ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member-2.7-lower.png){% endif %} diff --git a/translations/es-XL/data/reusables/organizations/choose-user-role.md b/translations/es-XL/data/reusables/organizations/choose-user-role.md deleted file mode 100644 index 7027fd17bf..0000000000 --- a/translations/es-XL/data/reusables/organizations/choose-user-role.md +++ /dev/null @@ -1 +0,0 @@ -1. Si la persona que estás invitando jamás ha sido un miembro de alguna organización o si le quitaste sus privilegios, escoge un rol para el usuario. ![Opciones para convertir a un usuario en miembro o propietario](/assets/images/help/organizations/choose-new-member-role.png) diff --git a/translations/es-XL/data/reusables/organizations/convert-owners-team-confirm.md b/translations/es-XL/data/reusables/organizations/convert-owners-team-confirm.md deleted file mode 100644 index ad8afc2de3..0000000000 --- a/translations/es-XL/data/reusables/organizations/convert-owners-team-confirm.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de la descripción del nuevo rol de propietario, da clic en **Ok, entendido**. ![Descripción de los roles de los nuevos propietarios con botón resaltado de "Ok, entendido"](/assets/images/help/teams/okay-got-it.png) diff --git a/translations/es-XL/data/reusables/organizations/create-team-choose-parent.md b/translations/es-XL/data/reusables/organizations/create-team-choose-parent.md deleted file mode 100644 index ab8b84fae6..0000000000 --- a/translations/es-XL/data/reusables/organizations/create-team-choose-parent.md +++ /dev/null @@ -1 +0,0 @@ -6. Opcionalmente, Si estás creando un [equipo hijo](/articles/about-teams#nested-teams), utiliza el menú desplegable para escoger un equipo padre para tu nuevo equipo. ![Menú desplegable listando los equipos existentes de la organización](/assets/images/help/teams/choose-parent-team.png) diff --git a/translations/es-XL/data/reusables/organizations/create_team.md b/translations/es-XL/data/reusables/organizations/create_team.md deleted file mode 100644 index 6d23917e80..0000000000 --- a/translations/es-XL/data/reusables/organizations/create_team.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Crear equipo**. diff --git a/translations/es-XL/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md b/translations/es-XL/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md deleted file mode 100644 index 9e34e20bac..0000000000 --- a/translations/es-XL/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Cuando eliminas un usuario de la organización, sus datos de membresía se guardan durante tres meses. Si en el transcurso de ese tiempo invitas al usuario a que se vuelva a unir a la organización, puedes restaurar sus datos o cualquier bifurcación privada de tus repositorios de la organización que le haya pertenecido. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ currentVersion }}/user/articles/reinstating-a-former-member-of-your-organization)". - -{% endnote %} diff --git a/translations/es-XL/data/reusables/organizations/delete-ssh-ca.md b/translations/es-XL/data/reusables/organizations/delete-ssh-ca.md deleted file mode 100644 index de4d979dbc..0000000000 --- a/translations/es-XL/data/reusables/organizations/delete-ssh-ca.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de "Autoridades de Certificados SSH", a la derecha la autoridad que quieras borrar, da clic en **Borrar**. ![Botón de borrar](/assets/images/help/organizations/ca-delete-button.png) -2. Lee la advertencia y después da clic en **Entiendo, por favor borra esta Autoridad**. ![Botón de confirmación de borrado](/assets/images/help/organizations/ca-delete-confirmation.png) diff --git a/translations/es-XL/data/reusables/organizations/deleted-repos.md b/translations/es-XL/data/reusables/organizations/deleted-repos.md deleted file mode 100644 index cbf5855288..0000000000 --- a/translations/es-XL/data/reusables/organizations/deleted-repos.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Repositorios borrados**. ![Pestaña de repositorios borrados](/assets/images/help/organizations/deleted-repos.png) diff --git a/translations/es-XL/data/reusables/organizations/disable_project_board_results.md b/translations/es-XL/data/reusables/organizations/disable_project_board_results.md deleted file mode 100644 index 4948a92f59..0000000000 --- a/translations/es-XL/data/reusables/organizations/disable_project_board_results.md +++ /dev/null @@ -1 +0,0 @@ -Si decides habilitar nuevamente tableros de proyecto, todos los tableros de proyecto que se agregaron con anterioridad se encontrarán disponibles. diff --git a/translations/es-XL/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/es-XL/data/reusables/organizations/github-apps-settings-sidebar.md deleted file mode 100644 index 974ce5c5d7..0000000000 --- a/translations/es-XL/data/reusables/organizations/github-apps-settings-sidebar.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_app %}s**. ![Configuración de {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/github-apps-settings-sidebar.png) diff --git a/translations/es-XL/data/reusables/organizations/internal-repos-enterprise.md b/translations/es-XL/data/reusables/organizations/internal-repos-enterprise.md deleted file mode 100644 index 5edc88ab43..0000000000 --- a/translations/es-XL/data/reusables/organizations/internal-repos-enterprise.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -{% note %} - -**Nota:** Los repositorios internos se encuentran disponibles para las organizaciones que pertenecen a una cuenta empresarial. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". - -{% endnote %} -{% endif %} diff --git a/translations/es-XL/data/reusables/organizations/invite-teams-or-people.md b/translations/es-XL/data/reusables/organizations/invite-teams-or-people.md deleted file mode 100644 index d618fa6d16..0000000000 --- a/translations/es-XL/data/reusables/organizations/invite-teams-or-people.md +++ /dev/null @@ -1 +0,0 @@ -1. A la derecha de "Administrar acceso", da clic en **Invitar equipos o personas**. ![botón de "Invitar equipos o personas"](/assets/images/help/repository/manage-access-invite-button.png) diff --git a/translations/es-XL/data/reusables/organizations/invite_member_from_people_tab.md b/translations/es-XL/data/reusables/organizations/invite_member_from_people_tab.md deleted file mode 100644 index 7632d1b1ac..0000000000 --- a/translations/es-XL/data/reusables/organizations/invite_member_from_people_tab.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}1. En la pestaña de Personas, da clic en **Invitar miembro**. - ![Botón de invitar miembro](/assets/images/help/organizations/people-tab-invite-member.png){% else %} -1. En la pestaña de Personas, da clic en **Agregar miembro**. ![Add member button](/assets/images/help/organizations/people-tab-invite-member-ghe.png){% endif %} diff --git a/translations/es-XL/data/reusables/organizations/invite_to_org.md b/translations/es-XL/data/reusables/organizations/invite_to_org.md deleted file mode 100644 index 31590c86b1..0000000000 --- a/translations/es-XL/data/reusables/organizations/invite_to_org.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}1. Teclea el nombre de usuario, nombre completo, o dirección de correo electrónico de la persona que quieres invitar y da clic en **Invitar**. - ![Formato para invitar miembro](/assets/images/help/organizations/org-invite-modal.png){% else %} -1. Teclea el nombre de usuario, nombre completo, o dirección de correo electrónico de la persona que quieres agregar y da clic en **Invitar**. ![Invite member form](/assets/images/help/organizations/org-invite-modal-ghe.png){% endif %} diff --git a/translations/es-XL/data/reusables/organizations/invite_to_team.md b/translations/es-XL/data/reusables/organizations/invite_to_team.md deleted file mode 100644 index a994f1b321..0000000000 --- a/translations/es-XL/data/reusables/organizations/invite_to_team.md +++ /dev/null @@ -1,6 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -1. Agrega un miembro de la organización al equipo o invita a una persona que no sea miembro a unirse a un equipo: - - Si la persona que quieres agregar ya es miembro de la organización, escribe su nombre de usuario y haz clic en **Enter** (Intro). El usuario se agregará de inmediato al equipo. - - Si la persona que quieres agregar no es miembro de la organización, escribe su nombre de usuario o dirección de correo electrónico y haz clic en **Enter** (Intro). El usuario recibirá una invitación por correo electrónico para unirse a tu organización y se agregará al equipo una vez que la acepte.{% else %} -1. Escribe el nombre de usuario de la persona que quieres agregar y haz clic en **Enter** (Intro). El usuario se agregará de inmediato al equipo. ![Mensaje emergente de agregar miembro de equipo](/assets/images/help/organizations/Organization-add-team.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/organizations/member-privileges.md b/translations/es-XL/data/reusables/organizations/member-privileges.md deleted file mode 100644 index a3bf89423a..0000000000 --- a/translations/es-XL/data/reusables/organizations/member-privileges.md +++ /dev/null @@ -1 +0,0 @@ -4. En la barra lateral izquierda, da clic en **Privilegios de los miembros**. ![Opción de privilegios de los miembros en la configuración de la organización](/assets/images/help/organizations/org-settings-member-privileges.png) diff --git a/translations/es-XL/data/reusables/organizations/navigate-to-org.md b/translations/es-XL/data/reusables/organizations/navigate-to-org.md deleted file mode 100644 index 687b62102e..0000000000 --- a/translations/es-XL/data/reusables/organizations/navigate-to-org.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.product_name %}, navega hasta la página principal de la organización. diff --git a/translations/es-XL/data/reusables/organizations/new-org-permissions-more-info.md b/translations/es-XL/data/reusables/organizations/new-org-permissions-more-info.md deleted file mode 100644 index 0ab6723819..0000000000 --- a/translations/es-XL/data/reusables/organizations/new-org-permissions-more-info.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization)". diff --git a/translations/es-XL/data/reusables/organizations/new-organization.md b/translations/es-XL/data/reusables/organizations/new-organization.md deleted file mode 100644 index 15f8d14758..0000000000 --- a/translations/es-XL/data/reusables/organizations/new-organization.md +++ /dev/null @@ -1 +0,0 @@ -1. En la sección "Organizaciones", haz clic en **New organization** (Nueva organización). ![Botón para crear una organización nueva](/assets/images/help/settings/new-org-button.png) diff --git a/translations/es-XL/data/reusables/organizations/new-repo-permissions-more-info.md b/translations/es-XL/data/reusables/organizations/new-repo-permissions-more-info.md deleted file mode 100644 index dd351e85a7..0000000000 --- a/translations/es-XL/data/reusables/organizations/new-repo-permissions-more-info.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". diff --git a/translations/es-XL/data/reusables/organizations/new-ssh-ca.md b/translations/es-XL/data/reusables/organizations/new-ssh-ca.md deleted file mode 100644 index da74aca9dc..0000000000 --- a/translations/es-XL/data/reusables/organizations/new-ssh-ca.md +++ /dev/null @@ -1,3 +0,0 @@ -1. A la derecha de "Autoridades de Certificados SSH", da clic en **Nueva Autoridad**. ![Botón de nueva autoridad](/assets/images/help/organizations/new-ca-button.png) -2. Debajo de "Llave", pega tu llave SSH pública. ![Campo de llave para agregar autoridad](/assets/images/help/organizations/ca-key-field.png) -3. Da clic en **Agregar Autoridad**. diff --git a/translations/es-XL/data/reusables/organizations/new_team.md b/translations/es-XL/data/reusables/organizations/new_team.md deleted file mode 100644 index 16ddce1b4e..0000000000 --- a/translations/es-XL/data/reusables/organizations/new_team.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de tu nombre de organización, da clic en {% octicon "people" aria-label="The people icon" %}**Equipos**. ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab.png) -1. Al lado derecho de la pestaña de Equipos, da clic en **Equipo nuevo**. ![Botón de equipo nuevo](/assets/images/help/teams/new-team-button.png) diff --git a/translations/es-XL/data/reusables/organizations/oauth_app_access.md b/translations/es-XL/data/reusables/organizations/oauth_app_access.md deleted file mode 100644 index 64521be41f..0000000000 --- a/translations/es-XL/data/reusables/organizations/oauth_app_access.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} - 1. En la barra lateral de configuración, da clic en **Acceso de terceros**. ![pestaña de acceso de {% data variables.product.prodname_oauth_app %} en la barra lateral izquierda](/assets/images/help/settings/settings-sidebar-third-party-access.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/organizations/oauth_app_restrictions_default.md b/translations/es-XL/data/reusables/organizations/oauth_app_restrictions_default.md deleted file mode 100644 index fb24e84c2c..0000000000 --- a/translations/es-XL/data/reusables/organizations/oauth_app_restrictions_default.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}Cuando creas una organización nueva, las restricciones de acceso de {% data variables.product.prodname_oauth_app %} se habilitan predeterminadamente. Los propietarios de las organizaciones pueden [inhabilitar las restricciones de acceso de {% data variables.product.prodname_oauth_app %}](/articles/disabling-oauth-app-access-restrictions-for-your-organization) en cualquier momento.{% endif %} diff --git a/translations/es-XL/data/reusables/organizations/org-invite-expiration.md b/translations/es-XL/data/reusables/organizations/org-invite-expiration.md deleted file mode 100644 index 3dac78e542..0000000000 --- a/translations/es-XL/data/reusables/organizations/org-invite-expiration.md +++ /dev/null @@ -1 +0,0 @@ -Las invitaciones pendientes caducarán después de 7 días. Esto restablecerá cualquier licencia sin reclamar. diff --git a/translations/es-XL/data/reusables/organizations/org-ownership-recommendation.md b/translations/es-XL/data/reusables/organizations/org-ownership-recommendation.md deleted file mode 100644 index 98b0a8844c..0000000000 --- a/translations/es-XL/data/reusables/organizations/org-ownership-recommendation.md +++ /dev/null @@ -1 +0,0 @@ -Los proyectos mantenidos y admnistrados por un solo propietario de organización pueden llegar a ser inaccesibles con facilidad si no se puede contactar a dicho propietario. Te recomendamos que tu organización tenga por lo menos dos personas con permisos de *propietario* para garantizar que nadie tendrá acceso al proyecto. diff --git a/translations/es-XL/data/reusables/organizations/org_settings.md b/translations/es-XL/data/reusables/organizations/org_settings.md deleted file mode 100644 index ebbbd1cc29..0000000000 --- a/translations/es-XL/data/reusables/organizations/org_settings.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de tu nombre de organización, da clic en {% octicon "gear" aria-label="The Settings gear" %}**Configuración**. ![Botón de configuración de organización](/assets/images/help/organizations/organization-settings-tab.png) diff --git a/translations/es-XL/data/reusables/organizations/organization-name.md b/translations/es-XL/data/reusables/organizations/organization-name.md deleted file mode 100644 index 3f15c69ff8..0000000000 --- a/translations/es-XL/data/reusables/organizations/organization-name.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Nombre de cuenta{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %} de organización{% endif %}", teclea un nombre para tu cuenta de organización. ![Campo para teclear el nombre de organización](/assets/images/help/organizations/new-org-name.png) diff --git a/translations/es-XL/data/reusables/organizations/organization-wide-project.md b/translations/es-XL/data/reusables/organizations/organization-wide-project.md deleted file mode 100644 index c5c2097d33..0000000000 --- a/translations/es-XL/data/reusables/organizations/organization-wide-project.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de tu nombre de organización, da clic en {% octicon "project" aria-label="The Projects icon" %}**Proyectos**. ![Pestaña de proyectos para tu organización](/assets/images/help/organizations/organization-projects-tab.png) diff --git a/translations/es-XL/data/reusables/organizations/organizations_include.md b/translations/es-XL/data/reusables/organizations/organizations_include.md deleted file mode 100644 index 631b6619d0..0000000000 --- a/translations/es-XL/data/reusables/organizations/organizations_include.md +++ /dev/null @@ -1,8 +0,0 @@ -Las organizaciones incluyen: -{% if currentVersion == "free-pro-team@latest" %}- Una opción gratuita, {% data variables.product.prodname_free_team %}, con colaboradores ilimitados en repositorios públicos ilimitados con todas las características y en repositorios privados con características limitadas. -- La opción para mejorar a {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %} para obtener características adicionales, incluyendo administración y autenticación sofisticada para los usuarios, y opciones de soporte escaladas. {% data reusables.gated-features.more-info %}{% endif %} -- Membresía ilimitada con una variedad de roles que permiten [diferentes niveles de acceso a la organización y sus datos](/articles/permission-levels-for-an-organization) -- La capacidad de otorgarles a los miembros [un rango de permisos de acceso a los repositorios de la organización](/articles/repository-permission-levels-for-an-organization) -- [Equipos anidados que reflejan la estructura de tu empresa o grupo](/articles/about-teams) con permisos de acceso y menciones en cascada -- La posibilidad de que los propietarios de la organización vean el [estado de autenticación de dos factores(2FA)](/articles/about-two-factor-authentication) de los miembros -- La opción para [requerir que todos los miembros de la organización usen la autenticación de dos factores](/articles/requiring-two-factor-authentication-in-your-organization) diff --git a/translations/es-XL/data/reusables/organizations/outside-collaborators-use-seats.md b/translations/es-XL/data/reusables/organizations/outside-collaborators-use-seats.md deleted file mode 100644 index 96b676e886..0000000000 --- a/translations/es-XL/data/reusables/organizations/outside-collaborators-use-seats.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}Agregar a un colaborador externo a un repositorio privado utilizará una de tus licencias pagadas de la organización. Para obtener más información, consulta "[Acerca del precio por usuario](/articles/about-per-user-pricing/)."{% endif %} diff --git a/translations/es-XL/data/reusables/organizations/outside_collaborator_forks.md b/translations/es-XL/data/reusables/organizations/outside_collaborator_forks.md deleted file mode 100644 index 1065f0f5b3..0000000000 --- a/translations/es-XL/data/reusables/organizations/outside_collaborator_forks.md +++ /dev/null @@ -1 +0,0 @@ -Cuando agregas un colaborador externo a un repositorio, también es necesario que lo agregues en cualquier bifurcación del repositorio al que le quieras dar acceso. diff --git a/translations/es-XL/data/reusables/organizations/outside_collaborators_description.md b/translations/es-XL/data/reusables/organizations/outside_collaborators_description.md deleted file mode 100644 index 6aa199fca6..0000000000 --- a/translations/es-XL/data/reusables/organizations/outside_collaborators_description.md +++ /dev/null @@ -1,5 +0,0 @@ -Un colaborador externo es una persona que tiene acceso a uno o más repositorios de la organización, pero no es explícitamente miembro de la organización, como ser, un consultor o empleado transitorio. Para obtener más información, consulta: - -- "[Agregar colaboradores externos a repositorios de tu organización](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- "[Convertir a un miembro de la organización en colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" -- "[Eliminar a un colaborador externo de un repositorio de la organización](/articles/removing-an-outside-collaborator-from-an-organization-repository)" diff --git a/translations/es-XL/data/reusables/organizations/owners-and-admins-can.md b/translations/es-XL/data/reusables/organizations/owners-and-admins-can.md deleted file mode 100644 index 5f1b72ab38..0000000000 --- a/translations/es-XL/data/reusables/organizations/owners-and-admins-can.md +++ /dev/null @@ -1 +0,0 @@ -Solo los miembros con privilegios de propietario de una organización o privilegios de administrador de un repositorio pueden diff --git a/translations/es-XL/data/reusables/organizations/owners-team.md b/translations/es-XL/data/reusables/organizations/owners-team.md deleted file mode 100644 index 0fc0a2efb2..0000000000 --- a/translations/es-XL/data/reusables/organizations/owners-team.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de tu nombre de organización, da clic en {% octicon "people" aria-label="The people icon" %}**Equipos**. ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab.png) -1. En la pestaña de Equipos, da clic en **Propietarios**. ![Equipo del propietario seleccionado](/assets/images/help/teams/owners-team.png) diff --git a/translations/es-XL/data/reusables/organizations/people.md b/translations/es-XL/data/reusables/organizations/people.md deleted file mode 100644 index e8e2513452..0000000000 --- a/translations/es-XL/data/reusables/organizations/people.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de tu nombre de organización, da clic en {% octicon "organization" aria-label="The People icon" %}**Personas**. ![Pestaña de las Personas](/assets/images/help/organizations/organization-people-tab.png) diff --git a/translations/es-XL/data/reusables/organizations/people_tab_outside_collaborators.md b/translations/es-XL/data/reusables/organizations/people_tab_outside_collaborators.md deleted file mode 100644 index 36d51ab95b..0000000000 --- a/translations/es-XL/data/reusables/organizations/people_tab_outside_collaborators.md +++ /dev/null @@ -1 +0,0 @@ -4. Debajo de la pestaña "Personas", da clic en **Colaboradores externos**. ![Botón para seleccionar los colaboradores externos para una organización](/assets/images/help/organizations/select-outside-collaborators.png) diff --git a/translations/es-XL/data/reusables/organizations/reinstate-user-type-username.md b/translations/es-XL/data/reusables/organizations/reinstate-user-type-username.md deleted file mode 100644 index a6b7f6ce70..0000000000 --- a/translations/es-XL/data/reusables/organizations/reinstate-user-type-username.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea el nombre de usuario de la persona que quieres reinstaurar y da clic en **Invitar**. diff --git a/translations/es-XL/data/reusables/organizations/removed_outside_collaborators.md b/translations/es-XL/data/reusables/organizations/removed_outside_collaborators.md deleted file mode 100644 index 6a6d99c85c..0000000000 --- a/translations/es-XL/data/reusables/organizations/removed_outside_collaborators.md +++ /dev/null @@ -1 +0,0 @@ -1. Si se te solicita, lee la información acerca de los miembros y colaboradores externos que se eliminarán de la organización. Teclea el nombre de tu organización para confirmar el cambio y posteriormente da clic en **Eliminar miembros & requerir autenticación de dos factores**. ![Cuadro Confirmar aplicación obligatoria de dos factores](/assets/images/help/organizations/confirm-require-2fa.png) diff --git a/translations/es-XL/data/reusables/organizations/repo-creation-constants.md b/translations/es-XL/data/reusables/organizations/repo-creation-constants.md deleted file mode 100644 index 72dc1926cd..0000000000 --- a/translations/es-XL/data/reusables/organizations/repo-creation-constants.md +++ /dev/null @@ -1 +0,0 @@ -Los propietarios de las organizaciones siempre podrán crear cualquier tipo de repositorio, y los colaboradores externos jamás podrán crear algún tipo de repositorio. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". diff --git a/translations/es-XL/data/reusables/organizations/repository-defaults.md b/translations/es-XL/data/reusables/organizations/repository-defaults.md deleted file mode 100644 index c29be7f2c6..0000000000 --- a/translations/es-XL/data/reusables/organizations/repository-defaults.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda da clic en **Predeterminados del repositorio**. ![Pestaña de predeterminados del repositorio](/assets/images/help/organizations/repo-defaults-tab.png) diff --git a/translations/es-XL/data/reusables/organizations/repository-labels.md b/translations/es-XL/data/reusables/organizations/repository-labels.md deleted file mode 100644 index 5a0b17f592..0000000000 --- a/translations/es-XL/data/reusables/organizations/repository-labels.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Etiquetas de repositorio**. ![Pestaña de etiquetas de repositorio](/assets/images/help/organizations/repo-labels-tab.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/organizations/require-ssh-cert.md b/translations/es-XL/data/reusables/organizations/require-ssh-cert.md deleted file mode 100644 index 2fcf3beb6d..0000000000 --- a/translations/es-XL/data/reusables/organizations/require-ssh-cert.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, para requerir que los miembros utilicen certificados SSH, selecciona **Requerir Certificados SSH** y después da clic en **Guardar**. ![Casilla de Requerir Certificado SSH y botón de guardar](/assets/images/help/organizations/require-ssh-cert.png) diff --git a/translations/es-XL/data/reusables/organizations/require_two_factor_authentication.md b/translations/es-XL/data/reusables/organizations/require_two_factor_authentication.md deleted file mode 100644 index 19c5b74bc3..0000000000 --- a/translations/es-XL/data/reusables/organizations/require_two_factor_authentication.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Autenticación", selecciona **Requerir autenticación de dos factores para todos en tu organización**, y después da clic en **Guardar**. ![Casilla de Requerir autenticación bifactorial](/assets/images/help/organizations/require-2fa-checkbox.png) diff --git a/translations/es-XL/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/es-XL/data/reusables/organizations/reseller-ask-to-become-billing-manager.md deleted file mode 100644 index 70a6fe26d9..0000000000 --- a/translations/es-XL/data/reusables/organizations/reseller-ask-to-become-billing-manager.md +++ /dev/null @@ -1 +0,0 @@ -Si no eres un gerente de facturación para la organización, pide a tu cliente que solicite a un *propietario* de la misma[añadirte a la organización como gerente de facturación](/articles/adding-a-billing-manager-to-your-organization). diff --git a/translations/es-XL/data/reusables/organizations/review-team-repository-access.md b/translations/es-XL/data/reusables/organizations/review-team-repository-access.md deleted file mode 100644 index e714becaca..0000000000 --- a/translations/es-XL/data/reusables/organizations/review-team-repository-access.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa la lista de repositorios a la cual tendrá acceso el nuevo miembro del equipo, posteriormente, da clic en **Agregar _NOMBRE DE USUARIO_ a _NOMBRE DE EQUIPO_**. ![Cuadro modal con listado de repositorios a los que tendrá acceso el nuevo miembro del equipo y botón de confirmación](/assets/images/help/teams/add-team-member-repo-perms.png) diff --git a/translations/es-XL/data/reusables/organizations/security-and-analysis.md b/translations/es-XL/data/reusables/organizations/security-and-analysis.md deleted file mode 100644 index 5dbd561dc2..0000000000 --- a/translations/es-XL/data/reusables/organizations/security-and-analysis.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![Pestaña de "Seguridad & análisis"](/assets/images/help/organizations/org-settings-security-and-analysis.png) diff --git a/translations/es-XL/data/reusables/organizations/security.md b/translations/es-XL/data/reusables/organizations/security.md deleted file mode 100644 index 59283fd538..0000000000 --- a/translations/es-XL/data/reusables/organizations/security.md +++ /dev/null @@ -1,5 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -1. En la barra lateral izquierda, da clic en **Seguridad de la organización**. ![Configuración de seguridad de la organización](/assets/images/help/organizations/org-security-settings-tab.png) -{% else %} -1. En la barra lateral izquierda, haz clic en **Security** (Seguridad). ![Configuración de seguridad de la organización](/assets/images/help/organizations/org-settings-security-tab.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/organizations/send-invitation.md b/translations/es-XL/data/reusables/organizations/send-invitation.md deleted file mode 100644 index b5c51db484..0000000000 --- a/translations/es-XL/data/reusables/organizations/send-invitation.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en {% if currentVersion == "free-pro-team@latest" %}**Enviar invitación**{% else %}**Agregar miembro**{% endif %}. diff --git a/translations/es-XL/data/reusables/organizations/settings-sidebar-actions.md b/translations/es-XL/data/reusables/organizations/settings-sidebar-actions.md deleted file mode 100644 index 1a8897c829..0000000000 --- a/translations/es-XL/data/reusables/organizations/settings-sidebar-actions.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Acciones**. ![Configuración de acciones](/assets/images/help/settings/settings-sidebar-actions.png) diff --git a/translations/es-XL/data/reusables/organizations/specific_team.md b/translations/es-XL/data/reusables/organizations/specific_team.md deleted file mode 100644 index 967a05686f..0000000000 --- a/translations/es-XL/data/reusables/organizations/specific_team.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de tu nombre de organización, da clic en {% octicon "people" aria-label="The people icon" %}**Equipos**. ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab.png) -1. En la pestaña de Equipos, da clic en el nombre del equipo. ![Lista de los equipos de la organización](/assets/images/help/teams/click-team-name.png) diff --git a/translations/es-XL/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/es-XL/data/reusables/organizations/team-discussions-are-for-orgs.md deleted file mode 100644 index 98255c8e60..0000000000 --- a/translations/es-XL/data/reusables/organizations/team-discussions-are-for-orgs.md +++ /dev/null @@ -1 +0,0 @@ -Los debates de equipo solo se encuentran disponibles en las páginas de los equipos en las organizaciones. Para obtener más información, consulta [Acerca de los debates del equipo](/articles/about-team-discussions)". diff --git a/translations/es-XL/data/reusables/organizations/team-discussions-default.md b/translations/es-XL/data/reusables/organizations/team-discussions-default.md deleted file mode 100644 index ac9dab5426..0000000000 --- a/translations/es-XL/data/reusables/organizations/team-discussions-default.md +++ /dev/null @@ -1 +0,0 @@ -Los debates del equipo se encuentran disponibles en las organizaciones por defecto. diff --git a/translations/es-XL/data/reusables/organizations/team-discussions-permissions.md b/translations/es-XL/data/reusables/organizations/team-discussions-permissions.md deleted file mode 100644 index 2999e1f4f0..0000000000 --- a/translations/es-XL/data/reusables/organizations/team-discussions-permissions.md +++ /dev/null @@ -1 +0,0 @@ -Solo los miembros del equipo y propietarios de la organización pueden ver las publicaciones *Privadas*, y todos los miembros de la organización pueden ver las publicaciones *públicas*. diff --git a/translations/es-XL/data/reusables/organizations/team-discussions-purpose.md b/translations/es-XL/data/reusables/organizations/team-discussions-purpose.md deleted file mode 100644 index 52ea6dfeff..0000000000 --- a/translations/es-XL/data/reusables/organizations/team-discussions-purpose.md +++ /dev/null @@ -1 +0,0 @@ -En la página de tu equipo, puedes utilizar los debates de equipo para las conversaciones que se extienden en los proyectos o repositorios y no pertenecen a un informe de problemas o solicitud de extracción específicos. En vez de abrir un informe de problemas en un repositorio para debatir sobre una idea, puedes incluir a todo el equipo si tienes una conversación en un debate de equipo. diff --git a/translations/es-XL/data/reusables/organizations/team-discussions-tab.md b/translations/es-XL/data/reusables/organizations/team-discussions-tab.md deleted file mode 100644 index 814c4b4f76..0000000000 --- a/translations/es-XL/data/reusables/organizations/team-discussions-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de la página del equipo, da clic en {% octicon "comment-discussion" aria-label="The discussion icon" %}**Debates**. ![Pestaña de debates de equipo](/assets/images/help/teams/org-team-page-discussions-tab.png) diff --git a/translations/es-XL/data/reusables/organizations/team-repositories-tab.md b/translations/es-XL/data/reusables/organizations/team-repositories-tab.md deleted file mode 100644 index 531d881130..0000000000 --- a/translations/es-XL/data/reusables/organizations/team-repositories-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Arriba de la lista de miembros del equipo, da clic en {% octicon "repo" aria-label="The Repository icon" %}**Repositorios**. ![La pestaña de repositorios del equipo](/assets/images/help/organizations/team-repositories-button.png) diff --git a/translations/es-XL/data/reusables/organizations/team-synchronization.md b/translations/es-XL/data/reusables/organizations/team-synchronization.md deleted file mode 100644 index 5106e61f89..0000000000 --- a/translations/es-XL/data/reusables/organizations/team-synchronization.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Puedes utilizar la sincronización de equipos para agregar y eliminar automáticamente a los miembros del equipo en una organización a través de un proveedor de identidad. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)". -{% endif %} diff --git a/translations/es-XL/data/reusables/organizations/team_description.md b/translations/es-XL/data/reusables/organizations/team_description.md deleted file mode 100644 index 47f5808023..0000000000 --- a/translations/es-XL/data/reusables/organizations/team_description.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, en el campo de "Descripción", teclea una descripción del equipo. ![Campo de descripción del equipo](/assets/images/help/teams/org-team-description.png) diff --git a/translations/es-XL/data/reusables/organizations/team_maintainers_can.md b/translations/es-XL/data/reusables/organizations/team_maintainers_can.md deleted file mode 100644 index 87e0b70483..0000000000 --- a/translations/es-XL/data/reusables/organizations/team_maintainers_can.md +++ /dev/null @@ -1,15 +0,0 @@ -Los miembros con permisos de mantenedor del equipo pueden hacer lo siguiente: - -- [Cambiar el nombre y la descripción del equipo](/articles/renaming-a-team) -- [Cambiar la visibilidad del equipo](/articles/changing-team-visibility) -- [Solicitar agregar un equipo hijo](/articles/requesting-to-add-a-child-team) -- [Solicitar agregar o cambiar un equipo padre](/articles/requesting-to-add-or-change-a-parent-team) -- [Configurar la imagen de perfil del equipo](/articles/setting-your-team-s-profile-picture) -- [Editar debates de equipo](/articles/managing-disruptive-comments/#editing-a-comment) -- [Eliminar debates de equipo](/articles/managing-disruptive-comments/#deleting-a-comment) -- [Agregar a miembros de la organización al equipo](/articles/adding-organization-members-to-a-team) -- [Eliminar a miembros de la organización del equipo](/articles/removing-organization-members-from-a-team) -- [Promover un miembro del equipo existente a mantenedor del equipo](/articles/giving-team-maintainer-permissions-to-an-organization-member) -- Eliminar el acceso del equipo a los repositorios {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} -- [Administrar una tarea de revisión de código para el equipo](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team){% endif %}{% if currentVersion == "free-pro-team@latest" %} -- [Administrar los recordatorios programados para las solicitudes de extracción](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/es-XL/data/reusables/organizations/team_members_tab.md b/translations/es-XL/data/reusables/organizations/team_members_tab.md deleted file mode 100644 index 16225581a9..0000000000 --- a/translations/es-XL/data/reusables/organizations/team_members_tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de la página del equipo, da clic en {% octicon "organization" aria-label="The members symbol" %}**Miembros**. ![Pestaña de miembros](/assets/images/help/teams/members-tab.png) diff --git a/translations/es-XL/data/reusables/organizations/team_name.md b/translations/es-XL/data/reusables/organizations/team_name.md deleted file mode 100644 index df70ba69a0..0000000000 --- a/translations/es-XL/data/reusables/organizations/team_name.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Crear un equipo nuevo", teclea el nombre para tu equipo nuevo. ![Campo de nombre de equipo](/assets/images/help/teams/org-new-team-name.png) diff --git a/translations/es-XL/data/reusables/organizations/team_settings.md b/translations/es-XL/data/reusables/organizations/team_settings.md deleted file mode 100644 index 9db1abdbad..0000000000 --- a/translations/es-XL/data/reusables/organizations/team_settings.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior de la página del equipo, da clic en {% octicon "gear" aria-label="The Settings gear" %}**Configuración**. ![Pestaña de configuración de equipo](/assets/images/help/teams/team-settings-button.png) diff --git a/translations/es-XL/data/reusables/organizations/team_visibility.md b/translations/es-XL/data/reusables/organizations/team_visibility.md deleted file mode 100644 index c89f190a01..0000000000 --- a/translations/es-XL/data/reusables/organizations/team_visibility.md +++ /dev/null @@ -1 +0,0 @@ -1. Decide si el equipo será visible o secreto. ![Opciones de visibilidad que incluyen secreto y visible](/assets/images/help/teams/new-team-visibility.png) diff --git a/translations/es-XL/data/reusables/organizations/teams.md b/translations/es-XL/data/reusables/organizations/teams.md deleted file mode 100644 index 3d2237282f..0000000000 --- a/translations/es-XL/data/reusables/organizations/teams.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de tu nombre de organización, da clic en {% octicon "people" aria-label="The people icon" %}**Equipos**. ![Pestaña de equipos en la página de la organización](/assets/images/help/organizations/organization-teams-tab.png) diff --git a/translations/es-XL/data/reusables/organizations/teams_sidebar.md b/translations/es-XL/data/reusables/organizations/teams_sidebar.md deleted file mode 100644 index ff6322eefe..0000000000 --- a/translations/es-XL/data/reusables/organizations/teams_sidebar.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de Configuración, da clic en **Equipos**. ![Pestaña de equipos en la barra lateral de configuración de la organización](/assets/images/help/settings/settings-sidebar-team-settings.png) diff --git a/translations/es-XL/data/reusables/organizations/types-of-team-visibility.md b/translations/es-XL/data/reusables/organizations/types-of-team-visibility.md deleted file mode 100644 index 6295d27371..0000000000 --- a/translations/es-XL/data/reusables/organizations/types-of-team-visibility.md +++ /dev/null @@ -1,4 +0,0 @@ -Los equipos pueden ser visibles o secretos: - -- Todos los miembros en la organización pueden [ver y @mencionar](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) a los equipos visibles. -- Solo las personas en el equipo y aquellas con permisos de propietario pueden ver los equipos secretos. Son ideales para ocultar equipos con nombres o miembros sensibles, tales como aquellos que se utilizan para trabajar con socios o clientes externos. Los equipos secretos no pueden anidarse bajo equipos padre ni tener equipos hijo. diff --git a/translations/es-XL/data/reusables/organizations/user_must_accept_invite_email.md b/translations/es-XL/data/reusables/organizations/user_must_accept_invite_email.md deleted file mode 100644 index 2364cf8881..0000000000 --- a/translations/es-XL/data/reusables/organizations/user_must_accept_invite_email.md +++ /dev/null @@ -1 +0,0 @@ -1. La persona invitada recibirá un correo electrónico invitándola a la organización. Necesitarán aceptar la invitación antes de convertirse en miembros de la organización. diff --git a/translations/es-XL/data/reusables/organizations/verified-domains.md b/translations/es-XL/data/reusables/organizations/verified-domains.md deleted file mode 100644 index 50ecf2c709..0000000000 --- a/translations/es-XL/data/reusables/organizations/verified-domains.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Dominios verificados**. ![Botón de dominios verificados](/assets/images/help/organizations/verified-domains-button.png) diff --git a/translations/es-XL/data/reusables/organizations/watch-team-options.md b/translations/es-XL/data/reusables/organizations/watch-team-options.md deleted file mode 100644 index 8d3db29bd2..0000000000 --- a/translations/es-XL/data/reusables/organizations/watch-team-options.md +++ /dev/null @@ -1 +0,0 @@ -1. En el lado izquierdo de la página del equipo, debajo del nombre del equipo, diff --git a/translations/es-XL/data/reusables/package_registry/actions-configuration.md b/translations/es-XL/data/reusables/package_registry/actions-configuration.md deleted file mode 100644 index 5bceb5c877..0000000000 --- a/translations/es-XL/data/reusables/package_registry/actions-configuration.md +++ /dev/null @@ -1 +0,0 @@ -Los pasos de configuración varían de acuerdo con el cliente del paquete. Para obtener información general sobre como configurar un flujo de trabajo para {% data variables.product.prodname_actions %}, consulta la sección "[Configurar un flujo de trabajo](/github/automating-your-workflow-with-github-actions/configuring-a-workflow)". diff --git a/translations/es-XL/data/reusables/package_registry/add-npmrc-to-repo-step.md b/translations/es-XL/data/reusables/package_registry/add-npmrc-to-repo-step.md deleted file mode 100644 index 06c099773f..0000000000 --- a/translations/es-XL/data/reusables/package_registry/add-npmrc-to-repo-step.md +++ /dev/null @@ -1 +0,0 @@ -3. Agrega el archivo *.npmrc* al repositorio en donde {% data variables.product.prodname_registry %} pueda encontrar tu proyecto. Para obtener más información, consulta la sección "[Agregar un archivo a un repositorio utilizando la línea de comandos](/github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line)". diff --git a/translations/es-XL/data/reusables/package_registry/admins-can-configure-package-types.md b/translations/es-XL/data/reusables/package_registry/admins-can-configure-package-types.md deleted file mode 100644 index 82369c5e4a..0000000000 --- a/translations/es-XL/data/reusables/package_registry/admins-can-configure-package-types.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} -{% note %} - -**Note:** This package type may not be available for your instance, because site administrators can enable or disable each supported package type. For more information, see "[Configuring packages support for your enterprise](/enterprise/admin/packages/configuring-packages-support-for-your-enterprise)." - -{% endnote %} -{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md b/translations/es-XL/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md deleted file mode 100644 index 688d39e029..0000000000 --- a/translations/es-XL/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_registry %} es compatible con versiones `SNAPSHOT` de Apache Maven. Para utilizar un repositorio para descargar este tipo de artefacto, debes habilitar las CAPTURAS (SNAPSHOTS) en tu archivo*~/.m2/settings.xml* file. diff --git a/translations/es-XL/data/reusables/package_registry/authenticate-packages.md b/translations/es-XL/data/reusables/package_registry/authenticate-packages.md deleted file mode 100644 index 06d7047cf4..0000000000 --- a/translations/es-XL/data/reusables/package_registry/authenticate-packages.md +++ /dev/null @@ -1,9 +0,0 @@ -Necesitas de un token de acceso para publicar, instalar, y borrar paquetes en {% data variables.product.prodname_registry %}. Puedes utilizar un token de acceso personal para autenticarte con tu nombre de usuario directamente en {% 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. - -{% if currentVersion == "free-pro-team@latest" %} -To authenticate using a {% data variables.product.prodname_actions %} workflow: -- For package registries (`PACKAGE-REGISTRY.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`), 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 %} diff --git a/translations/es-XL/data/reusables/package_registry/authenticate-step.md b/translations/es-XL/data/reusables/package_registry/authenticate-step.md deleted file mode 100644 index 07bb226f02..0000000000 --- a/translations/es-XL/data/reusables/package_registry/authenticate-step.md +++ /dev/null @@ -1 +0,0 @@ -1. Autentícate en {% data variables.product.prodname_registry %}. Para obtener más información, consulta "[Autenticar a {% data variables.product.prodname_registry %}](#authenticating-to-github-packages)." diff --git a/translations/es-XL/data/reusables/package_registry/billing-for-container-registry.md b/translations/es-XL/data/reusables/package_registry/billing-for-container-registry.md deleted file mode 100644 index 7cf8e2459f..0000000000 --- a/translations/es-XL/data/reusables/package_registry/billing-for-container-registry.md +++ /dev/null @@ -1,3 +0,0 @@ -During the {% data variables.product.prodname_github_container_registry %} beta, both the new {% data variables.product.prodname_container_registry %} and existing {% data variables.product.prodname_registry %} Docker registry will be free. For more information about the {% data variables.product.prodname_registry %} Docker registry, see "[Configuring Docker for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages)." - -After the beta, the same billing and storage rates that other {% data variables.product.prodname_registry %} registries use will apply to the container registry. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages)." diff --git a/translations/es-XL/data/reusables/package_registry/container-registry-beta-billing-note.md b/translations/es-XL/data/reusables/package_registry/container-registry-beta-billing-note.md deleted file mode 100644 index 4cb919591c..0000000000 --- a/translations/es-XL/data/reusables/package_registry/container-registry-beta-billing-note.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Billing update for container image storage:** During the beta phase of {% data variables.product.prodname_github_container_registry %}, Docker image storage and bandwidth are free for the old `docker.pkg.github.com` and new `ghcr.io` hosting services. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)". - -{% endnote %} diff --git a/translations/es-XL/data/reusables/package_registry/container-registry-beta.md b/translations/es-XL/data/reusables/package_registry/container-registry-beta.md deleted file mode 100644 index 869fd9f4cd..0000000000 --- a/translations/es-XL/data/reusables/package_registry/container-registry-beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Note:** {% data variables.product.prodname_github_container_registry %} is currently in public beta and subject to change. Currently, {% data variables.product.prodname_github_container_registry %} only supports Docker image formats. During the beta, storage and bandwidth is free. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry/about-github-container-registry)". - -{% endnote %} diff --git a/translations/es-XL/data/reusables/package_registry/container-registry-feature-highlights.md b/translations/es-XL/data/reusables/package_registry/container-registry-feature-highlights.md deleted file mode 100644 index 935ba7b2bf..0000000000 --- a/translations/es-XL/data/reusables/package_registry/container-registry-feature-highlights.md +++ /dev/null @@ -1,4 +0,0 @@ -With the container registry you can: -- Store container images within your organization and user account, rather than a repository. -- Set fine-grained permissions and visibility independent of repository permissions and visibility. -- Access public container images anonymously. diff --git a/translations/es-XL/data/reusables/package_registry/create-npmrc-owner-step.md b/translations/es-XL/data/reusables/package_registry/create-npmrc-owner-step.md deleted file mode 100644 index 531955d282..0000000000 --- a/translations/es-XL/data/reusables/package_registry/create-npmrc-owner-step.md +++ /dev/null @@ -1,16 +0,0 @@ -2. En el mismo directorio que tu archivo `package.json`, crea o edita un archivo `.npmrc` para incluir una línea que especifique la URL de {% data variables.product.prodname_registry %} y el propietario de la cuenta. Reemplaza `OWNER` con el nombre de la cuenta de usuario u organización a la que pertenezca el repositorio que contiene tu proyecto. - -{% if currentVersion == "free-pro-team@latest" %} - ```shell -registry=https://npm.pkg.github.com/OWNER - ``` -{% else %} - If subdomain isolation is enabled: - ```shell - registry=https://npm.HOSTNAME/OWNER - ``` - If subdomain isolation is disabled: - ```shell - https://HOSTNAME/_registry/npm/OWNER - ``` -{% endif %} diff --git a/translations/es-XL/data/reusables/package_registry/default-name.md b/translations/es-XL/data/reusables/package_registry/default-name.md deleted file mode 100644 index f45ef82c00..0000000000 --- a/translations/es-XL/data/reusables/package_registry/default-name.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, {% data variables.product.prodname_dotcom %} publica el paquete en un repositorio existente con el mismo nombre que éste. diff --git a/translations/es-XL/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/es-XL/data/reusables/package_registry/docker_registry_deprecation_status.md deleted file mode 100644 index 79e9650f34..0000000000 --- a/translations/es-XL/data/reusables/package_registry/docker_registry_deprecation_status.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Note:** The {% data variables.product.prodname_registry %} Docker registry will be superseded by {% data variables.product.prodname_github_container_registry %}{% if currentVersion != "free-pro-team@latest" %} in a future {% data variables.product.product_name %} release{% endif %}.{% if currentVersion == "free-pro-team@latest" %} To learn how to migrate your existing Docker images and any workflows using them, see "[Migrating to {% data variables.product.prodname_github_container_registry %} for Docker images](/packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images)" and "[Getting started with {% data variables.product.prodname_github_container_registry %}](/packages/getting-started-with-github-container-registry)."{% endif %} - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/package_registry/lowercase-name-field.md b/translations/es-XL/data/reusables/package_registry/lowercase-name-field.md deleted file mode 100644 index 154f01e80b..0000000000 --- a/translations/es-XL/data/reusables/package_registry/lowercase-name-field.md +++ /dev/null @@ -1 +0,0 @@ -Dado que las letras mayúsculas no son compatibles, debes usar minúscula para el propietario del repositorio si el nombre de usuario o el nombre de la organización de {% data variables.product.prodname_dotcom %} contiene letras mayúsculas. diff --git a/translations/es-XL/data/reusables/package_registry/navigate-to-packages.md b/translations/es-XL/data/reusables/package_registry/navigate-to-packages.md deleted file mode 100644 index 2ae8790c43..0000000000 --- a/translations/es-XL/data/reusables/package_registry/navigate-to-packages.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en el nombre del paquete que quieres ver. ![Nombre del paquete](/assets/images/help/package-registry/package-name.png) diff --git a/translations/es-XL/data/reusables/package_registry/package-immutability.md b/translations/es-XL/data/reusables/package_registry/package-immutability.md deleted file mode 100644 index 639263f37e..0000000000 --- a/translations/es-XL/data/reusables/package_registry/package-immutability.md +++ /dev/null @@ -1,3 +0,0 @@ -Para evitar la confusión y la creación de problemas, {% data variables.product.prodname_dotcom %} reserva el nombre de un paquete y su número de versión de forma permanente. Aún si todo el paquete se borra, no puedes utilizar el nombre del paquete borrado en ningún repositorio que pertenezca a la misma cuenta. - -Para revisar o reemplazar una versión de paquete, te recomendamos publicar una nueva versión del mismo. diff --git a/translations/es-XL/data/reusables/package_registry/package-page-info.md b/translations/es-XL/data/reusables/package_registry/package-page-info.md deleted file mode 100644 index 4c6e5cedff..0000000000 --- a/translations/es-XL/data/reusables/package_registry/package-page-info.md +++ /dev/null @@ -1 +0,0 @@ -En la página del paquete, {% data variables.product.prodname_dotcom %} proporciona metadatos para cada versión, tal como la fecha de publicación. Puedes ver los detalles del paquete, incluyendo una descripción e instrucciones de uso y de instalación. Puedes descargar cualquier activo asociado con el paquete y ver la información de la actividad de descarga. Para obtener una página de paquete de ejemplo, consulta [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). diff --git a/translations/es-XL/data/reusables/package_registry/package-registry-with-github-tokens.md b/translations/es-XL/data/reusables/package_registry/package-registry-with-github-tokens.md deleted file mode 100644 index 06d58339f4..0000000000 --- a/translations/es-XL/data/reusables/package_registry/package-registry-with-github-tokens.md +++ /dev/null @@ -1 +0,0 @@ -Si estás utilizando un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes utilizar un `GITHUB_TOKEN` para publicar y consumir paquetes en {% data variables.product.prodname_registry %} sin que necesites almacenar y administrar un token de acceso personal. Para obtener más información, consulta la sección "[Autenticarse con el `GITHUB_TOKEN`](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". diff --git a/translations/es-XL/data/reusables/package_registry/package-settings-from-org-level.md b/translations/es-XL/data/reusables/package_registry/package-settings-from-org-level.md deleted file mode 100644 index 9507393f82..0000000000 --- a/translations/es-XL/data/reusables/package_registry/package-settings-from-org-level.md +++ /dev/null @@ -1,4 +0,0 @@ -1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization. -2. Under your organization name, click **Packages**. ![Container access invite button](/assets/images/help/package-registry/org-tab-for-packages.png) -3. Search for and select your package. -4. In the top right of your container image's landing page, click **Package settings**. ![Package settings button](/assets/images/help/package-registry/packages-settings-from-package-landing-page.png) diff --git a/translations/es-XL/data/reusables/package_registry/package-settings-from-user-level.md b/translations/es-XL/data/reusables/package_registry/package-settings-from-user-level.md deleted file mode 100644 index d766e264b3..0000000000 --- a/translations/es-XL/data/reusables/package_registry/package-settings-from-user-level.md +++ /dev/null @@ -1,5 +0,0 @@ -1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your user account. -2. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil, posteriormente, da clic en **Tu perfil**. ![Foto de perfil](/assets/images/help/profile/top_right_avatar.png) -3. On your profile page, in the top right, click **Packages**. ![Packages option on profile page](/assets/images/help/package-registry/packages-from-user-profile.png) -3. Search for and select your package. -4. In the top right of your container image's landing page, click **Package settings**. ![Package settings button](/assets/images/help/package-registry/packages-settings-from-package-landing-page.png) diff --git a/translations/es-XL/data/reusables/package_registry/packages-billing.md b/translations/es-XL/data/reusables/package_registry/packages-billing.md deleted file mode 100644 index 01d9a676db..0000000000 --- a/translations/es-XL/data/reusables/package_registry/packages-billing.md +++ /dev/null @@ -1 +0,0 @@ -El uso de {% data variables.product.prodname_registry %} es gratuito para los paquetes públicos. Para los paquetes privados, cada cuenta de {% data variables.product.product_name %} recibe una cantidad determinada de almacenamiento gratuito y de transferencia de datos, dependiendo del producto que se utilice en la cuenta. Predeterminadamente, tu cuenta tendrá un límite de gastos de $0, lo cual previene el uso adicional de almacenamiento o transferencia de datos después de que alcanzas el límite de las cantidades incluidas. Si incrementas tu límite de gastos por encima del $0 predeterminado, se te cobrará por cualquier almacenamiento o transferencia de datos extra, también llamados excedentes, hasta el tope del límite de gastos que hayas configurado. No podrán aplicarse los cupones que tenga tu cuenta para los excedentes de {% data variables.product.prodname_registry %}. diff --git a/translations/es-XL/data/reusables/package_registry/packages-from-code-tab.md b/translations/es-XL/data/reusables/package_registry/packages-from-code-tab.md deleted file mode 100644 index 505e716e44..0000000000 --- a/translations/es-XL/data/reusables/package_registry/packages-from-code-tab.md +++ /dev/null @@ -1,6 +0,0 @@ -1. A la derecha de la lista de archivos, da clic en **Paquetes**. - {% if currentVersion == "free-pro-team@latest" %} - ![Enlace de paquetes en la página de resumen](/assets/images/help/package-registry/packages-link.png) - {% else %} - ![Enlace de paquetes en la página de resumen](/assets/images/help/package-registry/packages-from-repo.png) - {% endif %} diff --git a/translations/es-XL/data/reusables/package_registry/packages-ghes-release-stage.md b/translations/es-XL/data/reusables/package_registry/packages-ghes-release-stage.md deleted file mode 100644 index 66d73926c6..0000000000 --- a/translations/es-XL/data/reusables/package_registry/packages-ghes-release-stage.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} -{% note %} - -**Note:** {% data variables.product.prodname_registry %} is currently in beta for {% data variables.product.prodname_ghe_server %} 2.22. To join the beta for your instance, use the [sign-up form](https://resources.github.com/beta-signup/). - -{% endnote %} -{% endif %} diff --git a/translations/es-XL/data/reusables/package_registry/public-or-private-packages.md b/translations/es-XL/data/reusables/package_registry/public-or-private-packages.md deleted file mode 100644 index 6e18d9cbf8..0000000000 --- a/translations/es-XL/data/reusables/package_registry/public-or-private-packages.md +++ /dev/null @@ -1 +0,0 @@ -Puedes publicar paquetes en un repositorio público (paquetes públicos) para compartir con todo {% data variables.product.prodname_dotcom %}, o en un repositorio privado (paquetes privados) para compartirlos con colaboradores o con una organización. diff --git a/translations/es-XL/data/reusables/package_registry/publish_package.md b/translations/es-XL/data/reusables/package_registry/publish_package.md deleted file mode 100644 index 8f978e4459..0000000000 --- a/translations/es-XL/data/reusables/package_registry/publish_package.md +++ /dev/null @@ -1,5 +0,0 @@ -1. Publicar el paquete: - - ```shell - $ npm publish - ``` diff --git a/translations/es-XL/data/reusables/package_registry/repository_connection_steps.md b/translations/es-XL/data/reusables/package_registry/repository_connection_steps.md deleted file mode 100644 index 222259c822..0000000000 --- a/translations/es-XL/data/reusables/package_registry/repository_connection_steps.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Under your package versions, click **Connect repository**. ![Connect a repository button on packages landing page](/assets/images/help/package-registry/connect-repository.png) - -1. Select a repository, then click **Connect repository**. ![Connect a repository button in repository selection pop-up window](/assets/images/help/package-registry/select_a_repo.png) diff --git a/translations/es-XL/data/reusables/package_registry/required-scopes.md b/translations/es-XL/data/reusables/package_registry/required-scopes.md deleted file mode 100644 index 5faf1e7e8b..0000000000 --- a/translations/es-XL/data/reusables/package_registry/required-scopes.md +++ /dev/null @@ -1 +0,0 @@ -Debes utilizar un token de acceso personal con los alcances adecuados para publicar e instalar paquetes en {% data variables.product.prodname_registry %}. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)". diff --git a/translations/es-XL/data/reusables/package_registry/spending-limit-enterprise-account.md b/translations/es-XL/data/reusables/package_registry/spending-limit-enterprise-account.md deleted file mode 100644 index 9da01e6ae3..0000000000 --- a/translations/es-XL/data/reusables/package_registry/spending-limit-enterprise-account.md +++ /dev/null @@ -1 +0,0 @@ -Si pagas por tu cuenta empresarial por factura, no puedes administrar el límite de gastos para la misma en {% data variables.product.product_name %}. Si quieres permitir que las organizaciones que pertenecen a tu cuenta empresarial utilicen {% data variables.product.prodname_registry %} con más almacenamiento o transferencia de datos de las que se incluye en sus cuentas, puedes prepagar los exceedntes. Ya que los excedentes deben prepagarse, no puedes habilitar los gastos ilimitados en cuentas que se paguen mediante factura. Tu límite de gastos será de 150% de la cantidad que hayas prepagado. Si tienes cualquier duda, [contacta a nuestro equipo de administración de cuentas](https://enterprise.github.com/contact). diff --git a/translations/es-XL/data/reusables/package_registry/verify_repository_field.md b/translations/es-XL/data/reusables/package_registry/verify_repository_field.md deleted file mode 100644 index c29ac87889..0000000000 --- a/translations/es-XL/data/reusables/package_registry/verify_repository_field.md +++ /dev/null @@ -1 +0,0 @@ -1. Verifica el campo `repository` en el *package.json*. de tu proyecto. El campo `repository` debe coincidir con la URL de tu repositorio de {% data variables.product.prodname_dotcom %}. Por ejemplo, si la URL de tu repositorio es `github.com/my-org/test`, entonces el campo de repositorio debe ser `git://github.com/my-org/test.git`. diff --git a/translations/es-XL/data/reusables/package_registry/viewing-packages.md b/translations/es-XL/data/reusables/package_registry/viewing-packages.md deleted file mode 100644 index 95c17700a7..0000000000 --- a/translations/es-XL/data/reusables/package_registry/viewing-packages.md +++ /dev/null @@ -1 +0,0 @@ -Después de que publiques un paquete, puedes verlo en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Visualizar paquetes](/packages/publishing-and-managing-packages/viewing-packages)". diff --git a/translations/es-XL/data/reusables/pages/about-front-matter.md b/translations/es-XL/data/reusables/pages/about-front-matter.md deleted file mode 100644 index 25ba903e24..0000000000 --- a/translations/es-XL/data/reusables/pages/about-front-matter.md +++ /dev/null @@ -1 +0,0 @@ -Para configurar variables y metadatos, tales como el título y diseño, de una página o publicación en tu sitio, puedes agregar YAML front matter a la parte superior de cualquier archivo Markdown o HTML. Para obtener más información, consulta la sección "[Front Matter](https://jekyllrb.com/docs/front-matter/)" en la documentación de Jekyll. diff --git a/translations/es-XL/data/reusables/pages/add-jekyll-theme.md b/translations/es-XL/data/reusables/pages/add-jekyll-theme.md deleted file mode 100644 index fa6c7c6fa7..0000000000 --- a/translations/es-XL/data/reusables/pages/add-jekyll-theme.md +++ /dev/null @@ -1 +0,0 @@ -Puedes agregar un tema de Jekyll a tu sitio de {% data variables.product.prodname_pages %} para personalizar la apariencia de tu sitio. diff --git a/translations/es-XL/data/reusables/pages/admin-must-push.md b/translations/es-XL/data/reusables/pages/admin-must-push.md deleted file mode 100644 index ecf165a64c..0000000000 --- a/translations/es-XL/data/reusables/pages/admin-must-push.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Nota**: Si los archivos fuente de tu sitio{% if currentVersion ver_lt "enterprise-server@2.23" %} se ubican en la fuente predeterminada de publicación—`master` para sitios de usuario y de organización o `gh-pages` para sitios de proyecto—pero tu sitio{% endif %} no se ha publicado automáticamente, asegúrate de que alguien con permisos administrativos y una dirección de correo electrónico verificada haya hecho publicaciones en la fuente de publicación. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/pages/best-with-supported-themes.md b/translations/es-XL/data/reusables/pages/best-with-supported-themes.md deleted file mode 100644 index 2953abaad5..0000000000 --- a/translations/es-XL/data/reusables/pages/best-with-supported-themes.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Estas instrucciones funcionan mejor con temas que {% data variables.product.prodname_pages %} determina como oficialmente compatibles. Para ver una lista completa de temas compatibles, consulta "[Temas compatibles](https://pages.github.com/themes/)" en el sitio de {% data variables.product.prodname_pages %}. -{% endif %} diff --git a/translations/es-XL/data/reusables/pages/build-failure-email-server.md b/translations/es-XL/data/reusables/pages/build-failure-email-server.md deleted file mode 100644 index a47aabb742..0000000000 --- a/translations/es-XL/data/reusables/pages/build-failure-email-server.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} - {% tip %} - - Solo recibiras un correo electrónico si habilitas la compatibilidad con correo externo en {% data variables.product.product_location_enterprise %}. Para obtener más información, contacta a tu administrador de sitio. - - {% endtip %} -{% endif %} diff --git a/translations/es-XL/data/reusables/pages/build-locally-download-cname.md b/translations/es-XL/data/reusables/pages/build-locally-download-cname.md deleted file mode 100644 index b6a36a45bc..0000000000 --- a/translations/es-XL/data/reusables/pages/build-locally-download-cname.md +++ /dev/null @@ -1 +0,0 @@ -1. Si utilizas un generador de sitio estático para construir tu sitio localmente y subes los archivos generados a {% data variables.product.product_name %}, extrae la confirmación que agregó el archivo _CNAME_ a tu repositorio local. Para obtener más información, consulta la sección "[Resolver problemas en dominios personalizados y en {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#cname-errors)". diff --git a/translations/es-XL/data/reusables/pages/configure-publishing-source.md b/translations/es-XL/data/reusables/pages/configure-publishing-source.md deleted file mode 100644 index 33256406b9..0000000000 --- a/translations/es-XL/data/reusables/pages/configure-publishing-source.md +++ /dev/null @@ -1 +0,0 @@ -1. Configura tu fuente de publicción. Para obtener más información, consulta "[Configurar una fuente de publicación para tu sitio {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)". diff --git a/translations/es-XL/data/reusables/pages/contact-dns-provider.md b/translations/es-XL/data/reusables/pages/contact-dns-provider.md deleted file mode 100644 index 2216af6827..0000000000 --- a/translations/es-XL/data/reusables/pages/contact-dns-provider.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información acerca de cómo crear el registro correcto, consulta la documentación de tu proveedor de DNS. diff --git a/translations/es-XL/data/reusables/pages/create-repo-name.md b/translations/es-XL/data/reusables/pages/create-repo-name.md deleted file mode 100644 index d5550d37e4..0000000000 --- a/translations/es-XL/data/reusables/pages/create-repo-name.md +++ /dev/null @@ -1 +0,0 @@ -1. Escribe un nombre para tu repositorio y una descripción opcional. Si estás creando un sitio de usuario u organización, tu repositorio se debe nombrar `.github.io` o `.github.io`. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/articles/about-github-pages#types-of-github-pages-sites)". ![Crear un campo de repositorio](/assets/images/help/pages/create-repository-name-pages.png) diff --git a/translations/es-XL/data/reusables/pages/decide-publishing-source.md b/translations/es-XL/data/reusables/pages/decide-publishing-source.md deleted file mode 100644 index cabe818a83..0000000000 --- a/translations/es-XL/data/reusables/pages/decide-publishing-source.md +++ /dev/null @@ -1 +0,0 @@ -1. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Decide{% else %}Si estás creando un sitio de proyecto, decide{% endif %} qué fuente de publicación quieres utilizar. {% if currentVersion ver_lt "enterprise-server@2.23" %}Si estás creando un sitio de usuario o de organización, debes almacenar el código fuente de tu sitio en la rama `master`.{% endif %} Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". diff --git a/translations/es-XL/data/reusables/pages/default-domain-information.md b/translations/es-XL/data/reusables/pages/default-domain-information.md deleted file mode 100644 index 9d94c5ca60..0000000000 --- a/translations/es-XL/data/reusables/pages/default-domain-information.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información acerca del dominio predeterminado para tu sitio, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/articles/about-github-pages#types-of-github-pages-sites)". diff --git a/translations/es-XL/data/reusables/pages/enforce-https-custom-domain.md b/translations/es-XL/data/reusables/pages/enforce-https-custom-domain.md deleted file mode 100644 index e127c49bd7..0000000000 --- a/translations/es-XL/data/reusables/pages/enforce-https-custom-domain.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, para requerir cifrado HTTPS para tu sitio, selecciona **Requerir HTTPS**. Puede tomar hasta 24 horas antes de que esta opción se encuentre disponible. Para obtener más información, consulta "[Asegurar tu sitio de {% data variables.product.prodname_pages %} con HTTPS](/articles/securing-your-github-pages-site-with-https)". ![Opción de Requerir HTTPS para dominios personalizados](/assets/images/help/pages/enforce-https-custom-domains.png) diff --git a/translations/es-XL/data/reusables/pages/jekyll-install-troubleshooting.md b/translations/es-XL/data/reusables/pages/jekyll-install-troubleshooting.md deleted file mode 100644 index 1be4622848..0000000000 --- a/translations/es-XL/data/reusables/pages/jekyll-install-troubleshooting.md +++ /dev/null @@ -1,9 +0,0 @@ -{% mac %} - -{% tip %} - -**Sugerencia:** si ves un error de Ruby cuando tratas de instalar Jekyll utilizando Bundler, es posible que necesites utilizar un administrador de paquete, como [RVM](https://rvm.io/) o [Homebrew](http://brew.sh/), para administrar tu instalación de Ruby. Para obtener más información, consulta la sección "[Solución de problemas](https://jekyllrb.com/docs/troubleshooting/#jekyll--macos)" en la documentación de Jekyll. - -{% endtip %} - -{% endmac %} diff --git a/translations/es-XL/data/reusables/pages/must-have-repo-first.md b/translations/es-XL/data/reusables/pages/must-have-repo-first.md deleted file mode 100644 index d11746390d..0000000000 --- a/translations/es-XL/data/reusables/pages/must-have-repo-first.md +++ /dev/null @@ -1 +0,0 @@ -Antes de que puedas crear tu sitio, debes tener un repositorio para el mismo en {% data variables.product.product_name %}. Si no estás creando tu sitio en un repositorio existente, consulta la sección "[Crear un repositorio para tu sitio](#creating-a-repository-for-your-site)". diff --git a/translations/es-XL/data/reusables/pages/navigate-publishing-source.md b/translations/es-XL/data/reusables/pages/navigate-publishing-source.md deleted file mode 100644 index 5bfdb6c007..0000000000 --- a/translations/es-XL/data/reusables/pages/navigate-publishing-source.md +++ /dev/null @@ -1 +0,0 @@ -1. Navega a la fuente de publicación para tu sitio. Para obtener más información acerca de las fuentes de publicación, consulta "[Acerca de las {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". diff --git a/translations/es-XL/data/reusables/pages/navigate-site-repo.md b/translations/es-XL/data/reusables/pages/navigate-site-repo.md deleted file mode 100644 index ff62cd8199..0000000000 --- a/translations/es-XL/data/reusables/pages/navigate-site-repo.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.product_name %}, navega al repositorio de tu sitio. diff --git a/translations/es-XL/data/reusables/pages/new-or-existing-repo.md b/translations/es-XL/data/reusables/pages/new-or-existing-repo.md deleted file mode 100644 index 694e53761d..0000000000 --- a/translations/es-XL/data/reusables/pages/new-or-existing-repo.md +++ /dev/null @@ -1,3 +0,0 @@ -Si tu sitio es un proyecto independiente, puedes crear un repositorio nuevo para almacenar el código fuente del mismo. Si tu sitio es un proyecto independiente, puedes crear un repositorio nuevo para almacenar el código fuente del mismo. - -Si quieres crear un sitio en un repositorio existente, salta hasta la sección "[Crear tu sitio](#creating-your-site)". diff --git a/translations/es-XL/data/reusables/pages/no_sensitive_data_pages.md b/translations/es-XL/data/reusables/pages/no_sensitive_data_pages.md deleted file mode 100644 index 0c36e74e9b..0000000000 --- a/translations/es-XL/data/reusables/pages/no_sensitive_data_pages.md +++ /dev/null @@ -1 +0,0 @@ -Los sitios {% data variables.product.prodname_pages %} no se deben usar para realizar transacciones que impliquen el envío de información confidencial como contraseñas o números de tarjeta de crédito. diff --git a/translations/es-XL/data/reusables/pages/private_pages_are_public_warning.md b/translations/es-XL/data/reusables/pages/private_pages_are_public_warning.md deleted file mode 100644 index 2579c5d10f..0000000000 --- a/translations/es-XL/data/reusables/pages/private_pages_are_public_warning.md +++ /dev/null @@ -1,5 +0,0 @@ - {% warning %} - - **Warning**: {% if currentVersion != "free-pro-team@latest" %}If your site administrator has enabled Public Pages, {% endif %}{% data variables.product.prodname_pages %} sites are publicly available on the internet, even if the repository for the site is private{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or internal{% endif %}. If you have sensitive data in your site's repository, you may want to remove it before publishing. For more information, see{% if currentVersion != "free-pro-team@latest" %} "[Configuring {% data variables.product.prodname_pages %} on your appliance](/enterprise/admin/installation/configuring-github-pages-on-your-appliance#making-github-pages-publicly-accessible)" and{% endif %} "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)." - - {% endwarning %} diff --git a/translations/es-XL/data/reusables/pages/recommend-bundler.md b/translations/es-XL/data/reusables/pages/recommend-bundler.md deleted file mode 100644 index 27e38cb734..0000000000 --- a/translations/es-XL/data/reusables/pages/recommend-bundler.md +++ /dev/null @@ -1,4 +0,0 @@ -Recomendamos utilizando [Bundler](http://bundler.io/) para instalar y ejecutar Jekyll. Bundler administra las dependencias de gema de Ruby, reduce los errores de construcción de Jekyll y evita los errores relacionados con el entorno. Para instalar Bundler: - - 1. Instala Ruby. Para obtener más información, consulta "[Instalar Ruby](https://www.ruby-lang.org/en/documentation/installation/)" en la documentación de Ruby. - 2. Instala Bundler. Para obtener más información, visita "[Bundler](https://bundler.io/)". diff --git a/translations/es-XL/data/reusables/pages/remove-submodule.md b/translations/es-XL/data/reusables/pages/remove-submodule.md deleted file mode 100644 index 65c0f17f10..0000000000 --- a/translations/es-XL/data/reusables/pages/remove-submodule.md +++ /dev/null @@ -1,9 +0,0 @@ -Para resolver problemas, primero decide si quieres utilizar un submódulo, lo cual es un proyecto de Git dentro de otro proyecto de Git; ya que estos a veces se crean por accidente. - -Si no quieres utilizar un submódilo, elimínalo reemplazando PATH-TO-SUBMODULE con la ruta del submódulo: -```shell -$ git submodule deinit PATH-TO-SUBMODULE -$ git rm PATH-TO-SUBMODULE -$ git commit -m "Remove submodule" -$ rm -rf .git/modules/PATH-TO-SUBMODULE -``` diff --git a/translations/es-XL/data/reusables/pages/save-custom-domain.md b/translations/es-XL/data/reusables/pages/save-custom-domain.md deleted file mode 100644 index 5873d54c62..0000000000 --- a/translations/es-XL/data/reusables/pages/save-custom-domain.md +++ /dev/null @@ -1 +0,0 @@ -1. 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-domain.png) diff --git a/translations/es-XL/data/reusables/pages/search-for-includes.md b/translations/es-XL/data/reusables/pages/search-for-includes.md deleted file mode 100644 index a4cd1d6d81..0000000000 --- a/translations/es-XL/data/reusables/pages/search-for-includes.md +++ /dev/null @@ -1 +0,0 @@ -Para solucionar problemas, busca el archivo `include` en el mensaje de error para ver dónde has referenciado otros archivos tales como {% raw %}`{% include example_header.html %}`{% endraw %}. diff --git a/translations/es-XL/data/reusables/pages/test-locally.md b/translations/es-XL/data/reusables/pages/test-locally.md deleted file mode 100644 index a86da44fc2..0000000000 --- a/translations/es-XL/data/reusables/pages/test-locally.md +++ /dev/null @@ -1 +0,0 @@ -Los cambios en tu sitio se publican automáticamente cuando se fusionan con la fuente de publicación de tu sitio. Si quieres pre-visualizar tus cambios primero, puedes hacer los cambios localmente en vez de en {% data variables.product.product_name %}. Después, prueba tu sitio localmente. Para obtener más información, consulta "[Verificar tu sitio de {% data variables.product.prodname_pages %} localmente con Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". diff --git a/translations/es-XL/data/reusables/pages/theme-customization-help.md b/translations/es-XL/data/reusables/pages/theme-customization-help.md deleted file mode 100644 index e57294b65e..0000000000 --- a/translations/es-XL/data/reusables/pages/theme-customization-help.md +++ /dev/null @@ -1 +0,0 @@ -El repositorio fuente de tu tema podría ofrecer algo de ayuda para personalizarlo. Por ejemplo, ve el "[_README_ de Minima](https://github.com/jekyll/minima#customizing-templates)." diff --git a/translations/es-XL/data/reusables/pages/update_your_dns_settings.md b/translations/es-XL/data/reusables/pages/update_your_dns_settings.md deleted file mode 100644 index 33f05b7544..0000000000 --- a/translations/es-XL/data/reusables/pages/update_your_dns_settings.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}1. Si hay un dominio personalizado para tu sitio, para evitar que alguien más lo tome, actualiza tu configuración de DNS. Para obtener más información, consulta la sección "[Configurar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/configuring-a-custom-domain-for-your-github-pages-site)".{% endif %} diff --git a/translations/es-XL/data/reusables/pages/visit-site.md b/translations/es-XL/data/reusables/pages/visit-site.md deleted file mode 100644 index 8333125c37..0000000000 --- a/translations/es-XL/data/reusables/pages/visit-site.md +++ /dev/null @@ -1,7 +0,0 @@ -1. Para ver tu sitio publicado, debajo de "{% data variables.product.prodname_pages %}", da clic en la URL del mismo. ![URL de tu sitio publicado](/assets/images/help/pages/click-pages-url-to-preview.png) - - {% note %} - - **Nota:** Es posible que tome hasta 20 minutos la publicación de los cambios en tu sitio luego de que subes los cambios a {% data variables.product.product_name %}. Si no ves los cambios reflejados en tu buscador después de una hora, consulta la sección "[Acerca de los errores de compilación de Jekyll para sitios de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". - - {% endnote %} diff --git a/translations/es-XL/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/es-XL/data/reusables/pages/www-and-apex-domain-recommendation.md deleted file mode 100644 index 23c373719c..0000000000 --- a/translations/es-XL/data/reusables/pages/www-and-apex-domain-recommendation.md +++ /dev/null @@ -1 +0,0 @@ -Si estás utilizando un dominio apex como tu dominio personalizado, te recomendamos configurar un subdominio `www`. Si configuras los registros correctos para cada dominio, teclea a tu proveedor de DNS, {% data variables.product.prodname_pages %} creará automáticamente redireccionamientos entre los dominios. Por ejemplo, si configuras `www.example.com` como el dominio personalizado para tu sitio, y tienes registros de `ALIAS` y `CNAME` configurados para los dominios de apex y de `www`, entonces `example.com` redireccionará a `www.example.com`. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)". diff --git a/translations/es-XL/data/reusables/pages/yaml-linter.md b/translations/es-XL/data/reusables/pages/yaml-linter.md deleted file mode 100644 index 6b661167bc..0000000000 --- a/translations/es-XL/data/reusables/pages/yaml-linter.md +++ /dev/null @@ -1 +0,0 @@ -Para identificar cualquier error, puedes copiar y pegar el contenido de tu archivo YAML en un filtro de YAML, tal como [YAML Validator](http://codebeautify.org/yaml-validator). diff --git a/translations/es-XL/data/reusables/pages/yaml-rules.md b/translations/es-XL/data/reusables/pages/yaml-rules.md deleted file mode 100644 index 523c3ec6a1..0000000000 --- a/translations/es-XL/data/reusables/pages/yaml-rules.md +++ /dev/null @@ -1,5 +0,0 @@ -- Utiliza espacios en vez de tabulaciones. -- Incluye un espacio después del `:` para cada valor de par de valor de claves, como `timezone: Africa/Nairobi`. -- Utiliza únicamente caracteres con codificación UTF-8. -- Cita cualquier caracter especial, tal como `:`, como en `title: "my awesome site: an adventure in parse errors"`. -- Para valores de líneas múltiples, utiliza `|` para crear líneas nuevas y `>` para ignorar líneas nuevas. diff --git a/translations/es-XL/data/reusables/policies/abuse.md b/translations/es-XL/data/reusables/policies/abuse.md deleted file mode 100644 index 3dc8d3fcfd..0000000000 --- a/translations/es-XL/data/reusables/policies/abuse.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_dotcom %} no tolera el abuso.{% if currentVersion == "free-pro-team@latest" %} Para más información sobre las políticas de {% data variables.product.prodname_dotcom %}consulta nuestros [Términos de Servicio](/articles/github-terms-of-service) y [Pautas de la Comunidad](/articles/github-community-guidelines).{% endif %} diff --git a/translations/es-XL/data/reusables/policies/github-community-guidelines-and-terms.md b/translations/es-XL/data/reusables/policies/github-community-guidelines-and-terms.md deleted file mode 100644 index d4a323671f..0000000000 --- a/translations/es-XL/data/reusables/policies/github-community-guidelines-and-terms.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.company_short %} proporciona un código de conducta básico para todos los que utilizan {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[{% data variables.product.company_short %} Términos de servicio](/github/site-policy/github-terms-of-service)y[{% data variables.product.company_short %} Pautas de la comunidad](/github/site-policy/github-community-guidelines)." diff --git a/translations/es-XL/data/reusables/policies/translation.md b/translations/es-XL/data/reusables/policies/translation.md deleted file mode 100644 index a45d7a38e4..0000000000 --- a/translations/es-XL/data/reusables/policies/translation.md +++ /dev/null @@ -1,3 +0,0 @@ -Este documento está traducido del inglés. En caso de conflicto, incertidumbre o aparente inconsistencia entre esta versión y la versión en inglés de este documento, la versión en inglés es la versión controladora. - -Si tienes sugerencias para mejorar nuestra traducción, por favor abre una propuesta en nuestro repositorio site-policy. diff --git a/translations/es-XL/data/reusables/pre-release-program/api-preview-warning.md b/translations/es-XL/data/reusables/pre-release-program/api-preview-warning.md deleted file mode 100644 index 73a6284c78..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/api-preview-warning.md +++ /dev/null @@ -1,5 +0,0 @@ -{% warning %} - -**Advertencia:** La API podría cambiar sin previo aviso durante el periodo de vista previa. Las características de la vista previa no son compatibles con un uso productivo. Si experimentas cualquier problema, contacta a {% data variables.contact.contact_support %}. - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/pre-release-program/content-attachments-public-beta.md b/translations/es-XL/data/reusables/pre-release-program/content-attachments-public-beta.md deleted file mode 100644 index 7ff031b1c3..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/content-attachments-public-beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** La API de {% data variables.product.prodname_unfurls %} se encuentra actualmente en beta y solo está disponible para su uso con GitHub Apps. Las características y los requisitos podrían cambiar en cualquier momento durante este periodo. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/pre-release-program/corsair-preview.md b/translations/es-XL/data/reusables/pre-release-program/corsair-preview.md deleted file mode 100644 index b9cdeaffaa..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/corsair-preview.md +++ /dev/null @@ -1,9 +0,0 @@ -{% note %} - -**Nota:** Para acceder a la API de {% data variables.product.prodname_unfurls %} durante el periodo de previsualización, debes proporcionar un [tipo de medios](/v3/media) en el encabezado `Accept`: - -``` -application/vnd.github.corsair-preview+json -``` - -{% endnote %} diff --git a/translations/es-XL/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md b/translations/es-XL/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md deleted file mode 100644 index 82dc2dc11c..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/expiring-user-access-tokens-beta.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -{% note %} - -**Nota:** Los tokens de usuario con caducidad son actualmente parte del beta de tokens de usuario a servidor y están sujetos a cambios. Para participar en la característica beta de tokens de usuario a servidor con caducidad, consulta la sección "[Activar las características beta para las aplicaciones](/developers/apps/activating-beta-features-for-apps)". Para obtener más información, consulta la sección "[Tokens de acceso con caducidad de usuario a servidor para las GitHub Apps](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps)". - -{% endnote %} -{% endif %} diff --git a/translations/es-XL/data/reusables/pre-release-program/fury-pre-release.md b/translations/es-XL/data/reusables/pre-release-program/fury-pre-release.md deleted file mode 100644 index 1df461cbaa..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/fury-pre-release.md +++ /dev/null @@ -1,11 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.21" %} -{% note %} - -**Nota:** Los Manifiestos de las {% data variables.product.prodname_github_app %}s se encuentran actualmente disponibles para que los desarrolladores los previsualicen. Para acceder a esta API durante el periodo de vista previa, debes proporcionar un [tipo de medios](/v3/media) personalizado en el encabezado de `Accept`: - -``` -application/vnd.github.fury-preview+json -``` - -{% endnote %} -{% endif %} diff --git a/translations/es-XL/data/reusables/pre-release-program/machine-man-preview.md b/translations/es-XL/data/reusables/pre-release-program/machine-man-preview.md deleted file mode 100644 index eaffcc0a7e..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/machine-man-preview.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -{% note %} - -**Nota:** Para acceder a la API con tu GitHub App, debes proporcionar un [tipo de medios personalizado](/v3/media) en el encabezado de `Accept` para tus solicitudes. - -`application/vnd.github.machine-man-preview+json` - -{% endnote %} -{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/pre-release-program/sailor-v-preview.md b/translations/es-XL/data/reusables/pre-release-program/sailor-v-preview.md deleted file mode 100644 index 5f78acf62a..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/sailor-v-preview.md +++ /dev/null @@ -1,11 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -{% note %} - -**Nota:** Ahora puedes utilizar la API de REST para agregar una razón cuando fijas un informe de problemas y verás las razones de haberlo fijado en las respuestas que incluyan informes de problemas o solicitudes de extracción. También verás las razones de haberlo fijado en los eventos que se muestren como `locked`. Esta característica se encuentra disponible actualmente para que los desarrolladores la previsualicen. Consulta la [publicación del blog](https://developer.github.com/changes/2018-01-10-lock-reason-api-preview) para encontrar todos los detalles. Para acceder a esta característica, debes proprocionar un [tipo de medios](/v3/media) personalizado en el encabezado de `Accept`: - -``` -application/vnd.github.sailor-v-preview+json -``` - -{% endnote %} -{% endif %} diff --git a/translations/es-XL/data/reusables/pre-release-program/starfox-preview.md b/translations/es-XL/data/reusables/pre-release-program/starfox-preview.md deleted file mode 100644 index 646b20ea48..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/starfox-preview.md +++ /dev/null @@ -1,11 +0,0 @@ -{% note %} - -**Nota:** Los detalles de la tarjeta de proyectos ahora se meustran en las respuestas de la API de REST para los eventos de informes de problemas y línea de tiempo relacionados con el proyecto. Esta característica está ahora disponible para que los desarrolladores la previsualicen. Para obtener más detalles, consulta la [publicación del blog](https://developer.github.com/changes/2018-09-05-project-card-events). - -Para recibir el atributo `project_card`, los tableros de proyecto deben [habilitarse](/articles/disabling-project-boards-in-a-repository) para un repositorio, y debes proprocionar un [tipo de medios](/v3/media) personalizado en el encabezado `Accept`: - -``` -application/vnd.github.starfox-preview+json -``` - -{% endnote %} diff --git a/translations/es-XL/data/reusables/pre-release-program/suspend-installation-beta.md b/translations/es-XL/data/reusables/pre-release-program/suspend-installation-beta.md deleted file mode 100644 index d7e78ccd7d..0000000000 --- a/translations/es-XL/data/reusables/pre-release-program/suspend-installation-beta.md +++ /dev/null @@ -1,4 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %} -El suspender una instalación de {% data variables.product.prodname_github_app %} se encuentra actualmente en beta y está sujeto a cambios. Antes de que puedas suspender una {% data variables.product.prodname_github_app %}, el propietario de ésta debe habilitar la suspeción de instalaciones al decidir integrarse en el beta. Para participar en la característica beta de suspención de instalaciones, consulta la sección "[Activar las características beta para las aplicaciones](/developers/apps/activating-beta-features-for-apps)". - -{% endif %} diff --git a/translations/es-XL/data/reusables/products/product-roadmap.md b/translations/es-XL/data/reusables/products/product-roadmap.md deleted file mode 100644 index c5dbc5773a..0000000000 --- a/translations/es-XL/data/reusables/products/product-roadmap.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información sobre los planes y las características planeados, consulta la sección [{% data variables.product.prodname_roadmap %}]({% data variables.product.prodname_roadmap_link %}). diff --git a/translations/es-XL/data/reusables/products/which-product-to-use.md b/translations/es-XL/data/reusables/products/which-product-to-use.md deleted file mode 100644 index 29a81813d9..0000000000 --- a/translations/es-XL/data/reusables/products/which-product-to-use.md +++ /dev/null @@ -1,3 +0,0 @@ -Si no estás seguro si {% data variables.product.prodname_ghe_server %}, {% data variables.product.prodname_ghe_cloud %}, o ambos son la mejor opción para tu organización, contacta a {% data variables.contact.contact_enterprise_sales %}. - -Las organizaciones con 12 o más programadores normalmente se benefician más con {% data variables.product.prodname_enterprise %}. Si tu organización tiene 11 o menos desarrolladores, considera {% data variables.product.prodname_team %}. Para obtener más información, consulta los productos de "{% data variables.product.prodname_dotcom %}" diff --git a/translations/es-XL/data/reusables/profile/access_org.md b/translations/es-XL/data/reusables/profile/access_org.md deleted file mode 100644 index 36f9fc193c..0000000000 --- a/translations/es-XL/data/reusables/profile/access_org.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte izquierda de tu página de perfil, debajo de "Organizaciones", da clic en el icono de tu organización. ![iconos de organización](/assets/images/help/profile/profile_orgs_box.png) diff --git a/translations/es-XL/data/reusables/profile/access_profile.md b/translations/es-XL/data/reusables/profile/access_profile.md deleted file mode 100644 index 89abd24e1c..0000000000 --- a/translations/es-XL/data/reusables/profile/access_profile.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}1. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil, posteriormente, da clic en **Tu perfil**. - ![Foto de perfil](/assets/images/help/profile/top_right_avatar.png){% else %} -1. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil, posteriormente, da clic en **Tu perfil**. ![Profile photo](/assets/images/enterprise/settings/top_right_avatar.png){% endif %} diff --git a/translations/es-XL/data/reusables/profile/activity-overview-summary.md b/translations/es-XL/data/reusables/profile/activity-overview-summary.md deleted file mode 100644 index b5edb397a4..0000000000 --- a/translations/es-XL/data/reusables/profile/activity-overview-summary.md +++ /dev/null @@ -1 +0,0 @@ -Cuando habilitas la sección de resumen de actividades en tu perfil, las personas podrán ver más información acerca de los tipos de contribuciones que haces y los repositorios en donde tienes más actividad. Quien esté viendo solo podrá encontrar información del resumen de actividad sobre los repositorios en los cuales tengan permisos de lectura. Una vez habilitadas, las personas pueden filtrar tu gráfica de contribuciones y línea de tiempo de actividad para una organización específica. diff --git a/translations/es-XL/data/reusables/profile/enterprise_access_profile.md b/translations/es-XL/data/reusables/profile/enterprise_access_profile.md deleted file mode 100644 index 197c5a4e75..0000000000 --- a/translations/es-XL/data/reusables/profile/enterprise_access_profile.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de {% data variables.product.prodname_ghe_server %}, da clic en tu foto de perfil, posteriormente, da clic en **Tu perfil**. ![Foto de perfil](/assets/images/enterprise/settings/top_right_avatar.png) diff --git a/translations/es-XL/data/reusables/profile/profile-readme.md b/translations/es-XL/data/reusables/profile/profile-readme.md deleted file mode 100644 index 1ad8938460..0000000000 --- a/translations/es-XL/data/reusables/profile/profile-readme.md +++ /dev/null @@ -1 +0,0 @@ -Si agregas un archivo de README a la raíz de un repositorio público con el mismo nombre que tu nombre de usuario, dicho README aparecerá automáticamente en tu página de perfil. Puedes editar el README de tu perfil con el Marcado Ampliado de GitHub para crear una sección personalizada en tu perfil. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/profile/user_profile_page_block_or_report.md b/translations/es-XL/data/reusables/profile/user_profile_page_block_or_report.md deleted file mode 100644 index 4a43c9d564..0000000000 --- a/translations/es-XL/data/reusables/profile/user_profile_page_block_or_report.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, debajo de la foto de perfil del usuario, da clic en **Bloquear o reportar usuario**. ![Enlace para reportar o bloquear usuario](/assets/images/help/profile/profile-block-or-report-button.png) diff --git a/translations/es-XL/data/reusables/profile/user_profile_page_navigation.md b/translations/es-XL/data/reusables/profile/user_profile_page_navigation.md deleted file mode 100644 index 2e3835f5c3..0000000000 --- a/translations/es-XL/data/reusables/profile/user_profile_page_navigation.md +++ /dev/null @@ -1 +0,0 @@ -1. Visita la página de perfil de usuario. diff --git a/translations/es-XL/data/reusables/project-management/access-collaboration-settings.md b/translations/es-XL/data/reusables/project-management/access-collaboration-settings.md deleted file mode 100644 index d0460c2736..0000000000 --- a/translations/es-XL/data/reusables/project-management/access-collaboration-settings.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, posteriormente, da clic en **Configuración**. ![Opción de configuración en menú desplegable desde la barra lateral del tablero de proyecto](/assets/images/help/projects/project-board-settings.png) diff --git a/translations/es-XL/data/reusables/project-management/add-collaborator.md b/translations/es-XL/data/reusables/project-management/add-collaborator.md deleted file mode 100644 index f5e8cd27c3..0000000000 --- a/translations/es-XL/data/reusables/project-management/add-collaborator.md +++ /dev/null @@ -1 +0,0 @@ -10. En los resultados de la búsqueda, da clic en el nombre de usuario correcto y luego da clic en **Agregar colaborador**. diff --git a/translations/es-XL/data/reusables/project-management/add-column-new-project.md b/translations/es-XL/data/reusables/project-management/add-column-new-project.md deleted file mode 100644 index d56d8abcfb..0000000000 --- a/translations/es-XL/data/reusables/project-management/add-column-new-project.md +++ /dev/null @@ -1 +0,0 @@ -1. En tu nuevo tablero de proyecto, para agregar tu primera columna, **Agrega una columna**. ![Botón para agregar columna en un tablero de proyecto vacío](/assets/images/help/projects/add-column.png) diff --git a/translations/es-XL/data/reusables/project-management/add-more-columns.md b/translations/es-XL/data/reusables/project-management/add-more-columns.md deleted file mode 100644 index dfc1b4f0bd..0000000000 --- a/translations/es-XL/data/reusables/project-management/add-more-columns.md +++ /dev/null @@ -1 +0,0 @@ -1. Agrega columnas para que se adapten a tu flujo de trabajo. diff --git a/translations/es-XL/data/reusables/project-management/automate-project-board-permissions.md b/translations/es-XL/data/reusables/project-management/automate-project-board-permissions.md deleted file mode 100644 index 67aeb85afd..0000000000 --- a/translations/es-XL/data/reusables/project-management/automate-project-board-permissions.md +++ /dev/null @@ -1 +0,0 @@ -Para configurar flujos de trabajo automáticos para un tablero de proyecto de un repositorio, debes tener acceso de escritura al mismo. Los miembros y propietarios de una organización pueden configurar flujos de trabajo automáticos en un tablero de proyecto que contemple a toda la organización. diff --git a/translations/es-XL/data/reusables/project-management/cascading-permissions.md b/translations/es-XL/data/reusables/project-management/cascading-permissions.md deleted file mode 100644 index 95f9c64fe6..0000000000 --- a/translations/es-XL/data/reusables/project-management/cascading-permissions.md +++ /dev/null @@ -1 +0,0 @@ -Si una persona cuenta con múltiples avenidas de acceso a un tablero de proyecto de una organización (individualmente, a través de un equipo o como miembro de una organización), el nivel de permiso más alto del tablero de proyecto invalida los niveles de permiso más bajos. diff --git a/translations/es-XL/data/reusables/project-management/choose-template.md b/translations/es-XL/data/reusables/project-management/choose-template.md deleted file mode 100644 index 94744bc70e..0000000000 --- a/translations/es-XL/data/reusables/project-management/choose-template.md +++ /dev/null @@ -1 +0,0 @@ -5. Opcionalmente, para agregar una plantilla a tu tablero de proyecto, utiliza el menú desplegable de **Plantilla:** y da clic en alguna de las opciones. ![Menú desplegable mostrando las opciones de plantilla para el tablero de proyecto](/assets/images/help/projects/project_board_template_drop_down_menu.png) diff --git a/translations/es-XL/data/reusables/project-management/click-create-column.md b/translations/es-XL/data/reusables/project-management/click-create-column.md deleted file mode 100644 index bb25125540..0000000000 --- a/translations/es-XL/data/reusables/project-management/click-create-column.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Crear columna**. diff --git a/translations/es-XL/data/reusables/project-management/click-edit-sidebar-menu-project-board.md b/translations/es-XL/data/reusables/project-management/click-edit-sidebar-menu-project-board.md deleted file mode 100644 index e28498488c..0000000000 --- a/translations/es-XL/data/reusables/project-management/click-edit-sidebar-menu-project-board.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, posteriormente, da clic en **Editar**. ![Opción de editar en el menú desplegable desde la barra lateral del tablero de proyecto](/assets/images/help/projects/project-board-edit-settings.png) diff --git a/translations/es-XL/data/reusables/project-management/click-menu.md b/translations/es-XL/data/reusables/project-management/click-menu.md deleted file mode 100644 index 03cc44dc05..0000000000 --- a/translations/es-XL/data/reusables/project-management/click-menu.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte superior derecha del tablero de proyecto, da clic en {% octicon "three-bars" aria-label="The three-bars octicon" %}**Menu**. diff --git a/translations/es-XL/data/reusables/project-management/click-new-project.md b/translations/es-XL/data/reusables/project-management/click-new-project.md deleted file mode 100644 index 2f7382451c..0000000000 --- a/translations/es-XL/data/reusables/project-management/click-new-project.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Proyecto Nuevo**. ![Botón de proyecto nuevo](/assets/images/help/projects/new-project-button.png) diff --git a/translations/es-XL/data/reusables/project-management/collaborator-option.md b/translations/es-XL/data/reusables/project-management/collaborator-option.md deleted file mode 100644 index 2588a939da..0000000000 --- a/translations/es-XL/data/reusables/project-management/collaborator-option.md +++ /dev/null @@ -1 +0,0 @@ -8. En la barra lateral izquierda, haz clic en **Collaborators** (Colaboradores). ![Opción de menú de colaboradores en la barra lateral izquierda](/assets/images/help/projects/project-board-collaborator-setting.png) diff --git a/translations/es-XL/data/reusables/project-management/collaborator-permissions.md b/translations/es-XL/data/reusables/project-management/collaborator-permissions.md deleted file mode 100644 index 15a7231e65..0000000000 --- a/translations/es-XL/data/reusables/project-management/collaborator-permissions.md +++ /dev/null @@ -1 +0,0 @@ -11. Opcionalmente, junto al nombre del colaborador nuevo, utiliza el menú desplegable y da clic en el nivel de permiso que le quieras otorgar: **Read**, **Write**, o **Admin**. ![Menú desplegable de permisos de colaborador con opciones read, write y admin](/assets/images/help/projects/org-project-collaborators-choose-permissions.png) diff --git a/translations/es-XL/data/reusables/project-management/confirm-label-deletion.md b/translations/es-XL/data/reusables/project-management/confirm-label-deletion.md deleted file mode 100644 index ab1018eb0f..0000000000 --- a/translations/es-XL/data/reusables/project-management/confirm-label-deletion.md +++ /dev/null @@ -1 +0,0 @@ - 1. Lee la advertencia y da clic en **OK**. diff --git a/translations/es-XL/data/reusables/project-management/copy-project-boards.md b/translations/es-XL/data/reusables/project-management/copy-project-boards.md deleted file mode 100644 index 6ab2e21a80..0000000000 --- a/translations/es-XL/data/reusables/project-management/copy-project-boards.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -También puedes copiar un tablero de proyecto para reutilizar sus configuraciones personalizadas en proyectos similares. Para obtener más información, consulta "[Copiar un tablero de proyecto](/articles/copying-a-project-board)". -{% endif %} diff --git a/translations/es-XL/data/reusables/project-management/create-label.md b/translations/es-XL/data/reusables/project-management/create-label.md deleted file mode 100644 index a14085126a..0000000000 --- a/translations/es-XL/data/reusables/project-management/create-label.md +++ /dev/null @@ -1 +0,0 @@ - 1. Para guardar la nueva etiqueta, haz clic en **Crear etiqueta**. diff --git a/translations/es-XL/data/reusables/project-management/create-project-button.md b/translations/es-XL/data/reusables/project-management/create-project-button.md deleted file mode 100644 index 051c367980..0000000000 --- a/translations/es-XL/data/reusables/project-management/create-project-button.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Crear proyecto**. diff --git a/translations/es-XL/data/reusables/project-management/create-project-name-description.md b/translations/es-XL/data/reusables/project-management/create-project-name-description.md deleted file mode 100644 index de2edcc0e3..0000000000 --- a/translations/es-XL/data/reusables/project-management/create-project-name-description.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea un nombre y descripción para tu tablero de proyecto. ![Campos para nombre y descripción de proyecto y botón de crear proyecto](/assets/images/help/projects/name-description-create-button.png) diff --git a/translations/es-XL/data/reusables/project-management/delete-label.md b/translations/es-XL/data/reusables/project-management/delete-label.md deleted file mode 100644 index a8e8b75108..0000000000 --- a/translations/es-XL/data/reusables/project-management/delete-label.md +++ /dev/null @@ -1 +0,0 @@ - 1. En la lista de etiquetas, a la derecha de la etiqueta que quieres borrar, da clic en **Borrar**. diff --git a/translations/es-XL/data/reusables/project-management/edit-in-project.md b/translations/es-XL/data/reusables/project-management/edit-in-project.md deleted file mode 100644 index a7379a106c..0000000000 --- a/translations/es-XL/data/reusables/project-management/edit-in-project.md +++ /dev/null @@ -1 +0,0 @@ -Puedes ver las propuestas y solicitudes de extracción en tu tablero de proyecto y hacerles ediciones leves haciendo clic en el título de la propuesta o solicitud de extracción. diff --git a/translations/es-XL/data/reusables/project-management/edit-label.md b/translations/es-XL/data/reusables/project-management/edit-label.md deleted file mode 100644 index 947c45c8ba..0000000000 --- a/translations/es-XL/data/reusables/project-management/edit-label.md +++ /dev/null @@ -1 +0,0 @@ - 1. En la lista de etiquetas, a la derecha de la etiqueta que quieres editar, da clic en **Editar**. diff --git a/translations/es-XL/data/reusables/project-management/edit-project-columns.md b/translations/es-XL/data/reusables/project-management/edit-project-columns.md deleted file mode 100644 index fef4685dda..0000000000 --- a/translations/es-XL/data/reusables/project-management/edit-project-columns.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Tip:** Para editar o eliminar una columna de tu tablero de proyecto, en la esquina superior derecha de la columna, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md b/translations/es-XL/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md deleted file mode 100644 index e2a658482f..0000000000 --- a/translations/es-XL/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información acerca de los atajos de teclado, consulta la sección "Tableros de Proyecto" en "[Atajos de teclado](/articles/keyboard-shortcuts/#project-boards)". diff --git a/translations/es-XL/data/reusables/project-management/label-color-randomizer.md b/translations/es-XL/data/reusables/project-management/label-color-randomizer.md deleted file mode 100644 index 0e17b2fabe..0000000000 --- a/translations/es-XL/data/reusables/project-management/label-color-randomizer.md +++ /dev/null @@ -1 +0,0 @@ -1. De manera opcional, para personalizar el color de tu etiqueta, edita el número hexadecimal, o da clic en el botón de actualización para obtener otra selección aleatoria. ![Emite un nuevo color de etiqueta cuando actualiza](/assets/images/help/issues/issues-color-refresh.png) diff --git a/translations/es-XL/data/reusables/project-management/label-description.md b/translations/es-XL/data/reusables/project-management/label-description.md deleted file mode 100644 index 4f582a8146..0000000000 --- a/translations/es-XL/data/reusables/project-management/label-description.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Descripción", teclea una descripción para ayudar a que los demás entiendan y utilicen tu etiqueta. ![Campo para teclear una descripción de etiqueta](/assets/images/help/issues/label-description-field.png) diff --git a/translations/es-XL/data/reusables/project-management/labels.md b/translations/es-XL/data/reusables/project-management/labels.md deleted file mode 100644 index 8240097a3c..0000000000 --- a/translations/es-XL/data/reusables/project-management/labels.md +++ /dev/null @@ -1 +0,0 @@ -1. Sobre la lista de informes de problemas o solicitudes de extracción, da clic en **Etiquetas**. ![Pestaña de etiquetas en la página de informes de problemas o solicitudes de extracción de un repositorio](/assets/images/help/issues/issues_labels_button.png) diff --git a/translations/es-XL/data/reusables/project-management/link-repos-to-project-board.md b/translations/es-XL/data/reusables/project-management/link-repos-to-project-board.md deleted file mode 100644 index c518396bd5..0000000000 --- a/translations/es-XL/data/reusables/project-management/link-repos-to-project-board.md +++ /dev/null @@ -1 +0,0 @@ -Puedes vincular hasta 25 repositorios a tu tablero de proyecto de organización o de usuario. Vincular repositorios facilita el agregar informes de problemas y solicitudes de extracción desde dichos repositorios a tu tablero de proyecto utilizando las **Tarjetas de adición de {% octicon "plus" aria-label="The Plus icon" %}**{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} o desde la barra lateral del informe de problemas o de la solicitud de extracción{% endif %}. diff --git a/translations/es-XL/data/reusables/project-management/linked-repositories.md b/translations/es-XL/data/reusables/project-management/linked-repositories.md deleted file mode 100644 index ed88bee9ce..0000000000 --- a/translations/es-XL/data/reusables/project-management/linked-repositories.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, debajo de **Repositorios vinculados**, busca un repositorio que te gustaría vincular a tu tablero de proyecto. ![Campo de búsqueda para vincular repositorios](/assets/images/help/projects/search-to-link-repository-on-create.png) diff --git a/translations/es-XL/data/reusables/project-management/milestones.md b/translations/es-XL/data/reusables/project-management/milestones.md deleted file mode 100644 index 2e8e655a89..0000000000 --- a/translations/es-XL/data/reusables/project-management/milestones.md +++ /dev/null @@ -1 +0,0 @@ -1. Junto al campo de búsqueda, da clic en **Hitos**. ![Botón de propuestas del hito](/assets/images/help/issues/issues_milestone_button.png) diff --git a/translations/es-XL/data/reusables/project-management/name-label.md b/translations/es-XL/data/reusables/project-management/name-label.md deleted file mode 100644 index 2935e37fc6..0000000000 --- a/translations/es-XL/data/reusables/project-management/name-label.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Nombre de etiqueta", teclea un nombre para tu etiqueta. ![Campo para teclear un nombre de etiqueta](/assets/images/help/issues/Issues-Label-Create.png) diff --git a/translations/es-XL/data/reusables/project-management/name-project-board-column.md b/translations/es-XL/data/reusables/project-management/name-project-board-column.md deleted file mode 100644 index 32f4c7f709..0000000000 --- a/translations/es-XL/data/reusables/project-management/name-project-board-column.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Nombre de columna", teclea el nombre de la columna que quieres crear. ![Teclea un nombre de columna](/assets/images/help/projects/type-column-name.png) diff --git a/translations/es-XL/data/reusables/project-management/project-board-import-with-api.md b/translations/es-XL/data/reusables/project-management/project-board-import-with-api.md deleted file mode 100644 index 2e5e93894c..0000000000 --- a/translations/es-XL/data/reusables/project-management/project-board-import-with-api.md +++ /dev/null @@ -1 +0,0 @@ -Puedes utilizar la API de {% data variables.product.prodname_dotcom %} para importar un tablero de proyecto. Para obtener más información, consulta la mutación "[importProject](/v4/mutation/importproject/)". diff --git a/translations/es-XL/data/reusables/project-management/project-board-permissions.md b/translations/es-XL/data/reusables/project-management/project-board-permissions.md deleted file mode 100644 index e6cf167a44..0000000000 --- a/translations/es-XL/data/reusables/project-management/project-board-permissions.md +++ /dev/null @@ -1,3 +0,0 @@ -- **Read** (Lectura), es el que otorga permiso a las personas para que vean un tablero de proyecto. -- **Write** (Escritura), es el que otorga permiso a las personas para que vean un tablero de proyecto, vinculen repositorios con un tablero de proyecto e interactúen con un tablero de proyecto. Para obtener más información, consulta "[Vincular un repositorio con un tablero de proyecto](/articles/linking-a-repository-to-a-project-board)". -- **Admin** (Administración), es el que otorga permiso a las personas para que vean un tablero de proyecto, interactúen con un tablero de proyecto, administren los parámetros de un tablero de proyecto y administren el acceso de otras personas al tablero de proyecto. diff --git a/translations/es-XL/data/reusables/project-management/project-board-visibility.md b/translations/es-XL/data/reusables/project-management/project-board-visibility.md deleted file mode 100644 index 53992bd638..0000000000 --- a/translations/es-XL/data/reusables/project-management/project-board-visibility.md +++ /dev/null @@ -1 +0,0 @@ -Por defecto, tu tablero de proyecto es privado y solo está visible para las personas con permisos de lectura, escritura o administración para el tablero de proyecto. Un tablero de proyecto está visible para todos los que dispongan de la URL del tablero de proyecto. diff --git a/translations/es-XL/data/reusables/project-management/project-note-more-options.md b/translations/es-XL/data/reusables/project-management/project-note-more-options.md deleted file mode 100644 index baf7065881..0000000000 --- a/translations/es-XL/data/reusables/project-management/project-note-more-options.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de las notas, da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.![Icono de kebab horizontal en la esquina superior derecha de la nota](/assets/images/help/projects/note-more-options.png) diff --git a/translations/es-XL/data/reusables/project-management/project-progress-locations.md b/translations/es-XL/data/reusables/project-management/project-progress-locations.md deleted file mode 100644 index 377e587007..0000000000 --- a/translations/es-XL/data/reusables/project-management/project-progress-locations.md +++ /dev/null @@ -1 +0,0 @@ -Cuando está habilitada la automatización de un tablero de proyecto, aparece una barra de progreso sobre el tablero de proyecto en la página con la lista de proyectos, en la barra lateral de propuestas y en las referencias al proyecto en otros tableros de proyecto. diff --git a/translations/es-XL/data/reusables/project-management/remove-collaborator.md b/translations/es-XL/data/reusables/project-management/remove-collaborator.md deleted file mode 100644 index 217a1fec5b..0000000000 --- a/translations/es-XL/data/reusables/project-management/remove-collaborator.md +++ /dev/null @@ -1 +0,0 @@ -4. Junto al colaborador que quieres eliminar, da clic en **X**. ![Icono de eliminación "X" junto al nombre de usuario del colaborador](/assets/images/help/projects/remove-project-board-collaborator.png) diff --git a/translations/es-XL/data/reusables/project-management/resync-automation.md b/translations/es-XL/data/reusables/project-management/resync-automation.md deleted file mode 100644 index 0ef46e7f66..0000000000 --- a/translations/es-XL/data/reusables/project-management/resync-automation.md +++ /dev/null @@ -1 +0,0 @@ -Cuando cierras un tablero de proyecto, se pausará cualquier automatización de flujo de trabajo configurada para el mismo. Si reabres un tablero de proyecto, tienes la opción de sincronizar la automatización, lo cual actualiza la posición de las tarjetas en el tablero de acuerdo con la configuración de automatización que se configuró para el mismo. Para obtener más información, consulta la sección "[Reabrir un tablero de proyecto cerrado](/articles/reopening-a-closed-project-board)" o "[Cerrar un tablero de proyecto](/articles/closing-a-project-board)". diff --git a/translations/es-XL/data/reusables/project-management/save-label.md b/translations/es-XL/data/reusables/project-management/save-label.md deleted file mode 100644 index e2d07f2ce4..0000000000 --- a/translations/es-XL/data/reusables/project-management/save-label.md +++ /dev/null @@ -1 +0,0 @@ - 1. Haz clic en **Guardar cambios**. diff --git a/translations/es-XL/data/reusables/project-management/select-automation-options-new-column.md b/translations/es-XL/data/reusables/project-management/select-automation-options-new-column.md deleted file mode 100644 index fd8568027c..0000000000 --- a/translations/es-XL/data/reusables/project-management/select-automation-options-new-column.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecciona las automatizaciones del flujo de trabajo que deseas configurar para la columna. ![Lista de opciones para automatizar la columna](/assets/images/help/projects/select-automation-options-new-column.png) diff --git a/translations/es-XL/data/reusables/project-management/select-column-preset.md b/translations/es-XL/data/reusables/project-management/select-column-preset.md deleted file mode 100644 index f77389cee7..0000000000 --- a/translations/es-XL/data/reusables/project-management/select-column-preset.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, debajo de "Automatización", selecciona una configuración predeterminada utilizando el menú desplegable. ![Selecciona preestablecer la automatización desde el menú](/assets/images/help/projects/select-automation.png) diff --git a/translations/es-XL/data/reusables/project-management/select-project.md b/translations/es-XL/data/reusables/project-management/select-project.md deleted file mode 100644 index 9bb5104d03..0000000000 --- a/translations/es-XL/data/reusables/project-management/select-project.md +++ /dev/null @@ -1 +0,0 @@ -1. En la lista de proyectos, da clic en el nombre del tablero de proyecto. ![Selecciona el proyecto](/assets/images/help/projects/select-project.png) diff --git a/translations/es-XL/data/reusables/project-management/use-automated-template.md b/translations/es-XL/data/reusables/project-management/use-automated-template.md deleted file mode 100644 index 84e39f88df..0000000000 --- a/translations/es-XL/data/reusables/project-management/use-automated-template.md +++ /dev/null @@ -1 +0,0 @@ -Puedes utilizar una plantilla de tablero de proyecto para crear un tablero de proyecto que ya tenga configurada la automatización. Para obtener más información, consulta "[Acerca de los tableros de proyectos](/articles/about-project-boards#templates-for-project-boards)." diff --git a/translations/es-XL/data/reusables/projects/disabled-projects.md b/translations/es-XL/data/reusables/projects/disabled-projects.md deleted file mode 100644 index ccd5bc09a1..0000000000 --- a/translations/es-XL/data/reusables/projects/disabled-projects.md +++ /dev/null @@ -1 +0,0 @@ -Únicamente verás este evento en las respuestas cuando se [habiliten](/articles/disabling-project-boards-in-a-repository) los tableros de proyecto en el repositorio. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/pull_requests/about-protected-branches.md b/translations/es-XL/data/reusables/pull_requests/about-protected-branches.md deleted file mode 100644 index 954c7903b4..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/about-protected-branches.md +++ /dev/null @@ -1 +0,0 @@ -Por defecto, cualquier solicitud de extracción se puede fusionar en cualquier momento, a menos que la rama de encabezado esté en conflicto con la rama base. diff --git a/translations/es-XL/data/reusables/pull_requests/automatically-delete-branches.md b/translations/es-XL/data/reusables/pull_requests/automatically-delete-branches.md deleted file mode 100644 index 13403e8cc2..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/automatically-delete-branches.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %} -Puedes hacer que se eliminen automáticamente ramas centrales después de que se fusionen solicitudes de extracción en tu repositorio. Para obtener más información, consulta la sección "[Administrar el borrado automático de ramas](/articles/managing-the-automatic-deletion-of-branches)". -{% endif %} diff --git a/translations/es-XL/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/es-XL/data/reusables/pull_requests/close-issues-using-keywords.md deleted file mode 100644 index ca62bcc47b..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/close-issues-using-keywords.md +++ /dev/null @@ -1 +0,0 @@ -Puedes vincular una solicitud de extracción a un informe de problemas para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} mostrar que se está trabajando en una solución y para cerrar {% endif %}automáticamente el informe de problemas cuando alguien fusione la solicitud de extracción. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". diff --git a/translations/es-XL/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md b/translations/es-XL/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md deleted file mode 100644 index 920bc5dfeb..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md +++ /dev/null @@ -1 +0,0 @@ -1. Recopila el nombre y dirección de correo electrónico de cada co-autor. {% if currentVersion == "free-pro-team@latest" %} Si alguien elige mantener su dirección de correo electrónico como privada, debes utilizar su correo de `no-reply` proporcionado por {% data variables.product.product_name %} para proteger su privacidad.{% endif %} diff --git a/translations/es-XL/data/reusables/pull_requests/commit-message-with-trailer-beginning.md b/translations/es-XL/data/reusables/pull_requests/commit-message-with-trailer-beginning.md deleted file mode 100644 index e8229e82ed..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/commit-message-with-trailer-beginning.md +++ /dev/null @@ -1,11 +0,0 @@ -1. Teclea tu mensaje de confirmación y una descripción corta y significativa sobre tus cambios. Después de tu descripción de la confirmación, en vez de cerrar las comillas, agrega dos líneas vacías. - ```shell - $ git commit -m "Refactor usability tests. - > - > - ``` - {% tip %} - - **Tip:** Si utilizas un editor de texto en la línea de comandos para teclear tu mensaje de confirmación, asegúrate de que existen dos líneas nuevas entre el final de la descripción y el indicador `Co-authored-by:`. - - {% endtip %} diff --git a/translations/es-XL/data/reusables/pull_requests/configure_pull_request_merges_intro.md b/translations/es-XL/data/reusables/pull_requests/configure_pull_request_merges_intro.md deleted file mode 100644 index 09fddb9c9f..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/configure_pull_request_merges_intro.md +++ /dev/null @@ -1 +0,0 @@ -Puedes configurar las opciones de fusión para una solicitud de extracción en {% data variables.product.product_location %} para que éstas satisfagan las necesidades de tu flujo de trabajo y tus preferencias para administrar el historial de Git. Para obtener más información, consulta la sección "[Configurar las fusiones de solicitudes de extracción](/articles/configuring-pull-request-merges)". diff --git a/translations/es-XL/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md b/translations/es-XL/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md deleted file mode 100644 index 1a25a1bdf1..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md +++ /dev/null @@ -1 +0,0 @@ -1. Decide si quieres mantener únicamente los cambios de tu rama, mantener únicamente los cambios de las demás ramas, o hacer un cambio nuevo, el cual puede incorporar cambios de ambas ramas. Borra los marcadores de conflicto `<<<<<<<`, `=======`, `>>>>>>>` y realiza los cambios que quieras en la fusión final. diff --git a/translations/es-XL/data/reusables/pull_requests/default-commit-message-squash-merge.md b/translations/es-XL/data/reusables/pull_requests/default-commit-message-squash-merge.md deleted file mode 100644 index 41c1333585..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/default-commit-message-squash-merge.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener información acerca de los mensajes de confirmación predeterminados para las fusiones de combinación, consulta "[Acerca de las fusiones de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#merge-message-for-a-squash-merge)." \ No newline at end of file diff --git a/translations/es-XL/data/reusables/pull_requests/default_merge_option.md b/translations/es-XL/data/reusables/pull_requests/default_merge_option.md deleted file mode 100644 index d504b9634f..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/default_merge_option.md +++ /dev/null @@ -1,5 +0,0 @@ -Cuando haces clic en la opción predeterminada **Merge pull request** (Fusionar solicitud de extracción) en una solicitud de extracción de {% data variables.product.product_location %}, todas las confirmaciones de la rama de característica se agregan a la rama de base en una confirmación de fusión. La solicitud de extracción se fusiona usando [la opción `--no-ff`](https://git-scm.com/docs/git-merge#_fast_forward_merge). - -Para fusionar solicitudes de extracción, debes tener [permisos de escritura](/articles/repository-permission-levels-for-an-organization/) sobre el repositorio. - -![standard-merge-commit-diagram](/assets/images/help/pull_requests/standard-merge-commit-diagram.png) diff --git a/translations/es-XL/data/reusables/pull_requests/dismiss_review.md b/translations/es-XL/data/reusables/pull_requests/dismiss_review.md deleted file mode 100644 index 119e0f10a0..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/dismiss_review.md +++ /dev/null @@ -1 +0,0 @@ -Si una solicitud de extracción ha cambiado desde que fue revisada y la persona que solicitó los cambios no se encuentra disponible para realizar una revisión en la que estos cambios se aprueben, los administradores del repositorio o las personas con acceso de escritura pueden descartar la revisión. diff --git a/translations/es-XL/data/reusables/pull_requests/mark-ready-review.md b/translations/es-XL/data/reusables/pull_requests/mark-ready-review.md deleted file mode 100644 index 923a377f7f..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/mark-ready-review.md +++ /dev/null @@ -1 +0,0 @@ -Cuando estés listo para obtener retroalimentación sobre tu solicitud de extracción, puedes marcar tu borrador de solicitud de extracción como listo para revisión. Con esto, solicitarás las revisiones de cualquier propietario de código en cuestión. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/pull_requests/perms-to-open-pull-request.md b/translations/es-XL/data/reusables/pull_requests/perms-to-open-pull-request.md deleted file mode 100644 index 65e3192495..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/perms-to-open-pull-request.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} - -{% note %} - -**Nota**: Para abrir una solicitud de extracción en un repositorio público, debes tener acceso de escritura en el encabezado de la rama origen o, para los repositorios que pertenecen a una organización, debes ser miembro de la organización propietaria del mismo para hacerlo. - -{% endnote %} - -{% endif %} diff --git a/translations/es-XL/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/es-XL/data/reusables/pull_requests/pull_request_merges_and_contributions.md deleted file mode 100644 index 9b045ef2ca..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/pull_request_merges_and_contributions.md +++ /dev/null @@ -1,7 +0,0 @@ -{% note %} - -**Notas:**{% if currentVersion != "free-pro-team@latest" %} -- Para que aparezcan en el gráfico de contribución de tu perfil, las confirmaciones de confirmación conjunta deben reunir los mismos criterios que las confirmaciones de un único autor.{% endif %} -- Cuando se cambian de base las confirmaciones, los autores originales de la confirmación y la persona que cambió de base las confirmaciones, ya sea en la línea de comando o en la {% data variables.product.product_location %}, recibe crédito de contribución. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/es-XL/data/reusables/pull_requests/rebase_and_merge_summary.md deleted file mode 100644 index 1c7d07ad87..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/rebase_and_merge_summary.md +++ /dev/null @@ -1,7 +0,0 @@ -Cuando seleccionas la opción **Rebase and merge** (Cambiar de base y fusionar) en la {% data variables.product.product_location %}, todas las confirmaciones de la rama de tema (o rama de encabezado) se agregan a la rama de base por separado sin una confirmación de fusión. Las solicitudes de extracción con confirmaciones con cambio de base se fusionan usando la [fast-forward option](https://git-scm.com/docs/git-merge#_fast_forward_merge) (opción de avance rápido). - -Para cambiar de base y fusionar solicitudes de extracción, debes tener [permisos de escritura](/articles/repository-permission-levels-for-an-organization/) en el repositorio, y el repositorio debe [permitir la fusión de cambio de base](/articles/configuring-commit-rebasing-for-pull-requests/). - -El comportamiento de cambio de base y de fusión en {% data variables.product.product_name %} varía levemente con respecto a `git rebase`. El cambio de base y la fusión en {% data variables.product.prodname_dotcom %} siempre actualizarán la información de la persona que confirma el cambio y crearán nuevas SHA de confirmación, mientras que el `git rebase` externo a {% data variables.product.prodname_dotcom %} no cambia la información de la persona que confirma el cambio cuando ocurre el cambio de base superponiendo un compromiso de antepasado. Para obtener más información sobre `git rebase`, consulta [el capítulo "Git rebase" del libro _Pro Git_](https://git-scm.com/docs/git-rebase). - -Para obtener una representación visual de `git rebase`, consulta [el capítulo "Ramas de Git - Cambio de base" del libro _Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/es-XL/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/es-XL/data/reusables/pull_requests/required-checks-must-pass-to-merge.md deleted file mode 100644 index c66dade3c4..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/required-checks-must-pass-to-merge.md +++ /dev/null @@ -1 +0,0 @@ -Si un repositorio requiere verificaciones de estado, éstas deben pasar antes de que fusiones tu rama con la rama protegida. Para obtener más información, consulta "[Acerca de las verificaciones de estado requeridas ](/articles/about-required-status-checks)". diff --git a/translations/es-XL/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/es-XL/data/reusables/pull_requests/required-reviews-for-prs-summary.md deleted file mode 100644 index 2373d9d9a8..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/required-reviews-for-prs-summary.md +++ /dev/null @@ -1,3 +0,0 @@ -Los administradores del repositorio pueden requerir que todas las solicitudes de extracción cuenten con una cantidad específica de revisiones de aprobación de las personas con permisos de *escritura* o *administrador* en el mismo o de un propietario del código designado antes de fusionarlas en una rama protegida. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". - -Cuando las revisiones requeridas están habilitadas, cualquier persona con acceso al repositorio puede aprobar cambios en una solicitud de extracción. Sin embargo, no podrás fusionar tu solicitud de extracción hasta que la cantidad requerida de revisores con permisos de *escritura* o *administrador* en el repositorio aprueben tus cambios sobre ésta en su revisión. Para obtener más información acerca de los niveles de permiso del repositorio, consulta "[Niveles de permiso del repositorio para una organización](/articles/repository-permission-levels-for-an-organization/)". Si se requiere la revisión de un propietario de código designado, y la solicitud de extracción afecta el código que tiene un propietario designado, se requiere la autorización de ese propietario. diff --git a/translations/es-XL/data/reusables/pull_requests/resolving-conversations.md b/translations/es-XL/data/reusables/pull_requests/resolving-conversations.md deleted file mode 100644 index 55f9e1b93b..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/resolving-conversations.md +++ /dev/null @@ -1,13 +0,0 @@ -### Resolver conversaciones - -Puedes resolver una conversación en una solicitud de extracción si abriste la solicitud de extracción o si tienes acceso de escritura al repositorio en el que se abrió la solicitud de extracción. - -Para indicar que se completó una conversación en la pestaña de **Archivos cambiados**, da clic en **Resolver conversación**. - -![Conversación de solicitud de extracción con botón Resolve conversation (Resolver conversación)](/assets/images/help/pull_requests/conversation-with-resolve-button.png) - -Toda la conversación se colapsará y se marcará como resuelta, y será más sencillo encontrar conversaciones que se deban seguir considerando. - -![Conversación resuelta](/assets/images/help/pull_requests/resolved-conversation.png) - -Si la sugerencia en un comentario está fuera del alcance de tu solicitud de extracción, puedes abrir un nuevo informe de problemas que rastree la retroalimientación y se vincule con el comentario original. Para obtener más información, consulte la sección "[Abrir un informe de problemas desde un comentario](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)". diff --git a/translations/es-XL/data/reusables/pull_requests/retargeted-on-branch-deletion.md b/translations/es-XL/data/reusables/pull_requests/retargeted-on-branch-deletion.md deleted file mode 100644 index 69fe3e0fd8..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/retargeted-on-branch-deletion.md +++ /dev/null @@ -1 +0,0 @@ -Si borras una rama de encabezado después de haber fusionado su solicitud de extracción, {% data variables.product.prodname_dotcom %} verificará cualquier solicitud de extracción abierta en el mismo repositorio que especifique la rama borrada como su rama base. {% data variables.product.prodname_dotcom %} actualiza automáticamente cualquier solicitud de extracción, cambiando su rama base a la rama base de la solicitud de extracción que se ha fusionado. diff --git a/translations/es-XL/data/reusables/pull_requests/squash_and_merge_summary.md b/translations/es-XL/data/reusables/pull_requests/squash_and_merge_summary.md deleted file mode 100644 index 302b1153e6..0000000000 --- a/translations/es-XL/data/reusables/pull_requests/squash_and_merge_summary.md +++ /dev/null @@ -1,7 +0,0 @@ -Cuando seleccionas la opción **Squash and merge** (Combinar y fusionar) en una solicitud de extracción en la {% data variables.product.product_location %}, las confirmaciones de la solicitud de extracción se combinan en una única confirmación. En lugar de ver todas las confirmaciones individuales de un contribuyente de una rama de tema, las confirmaciones se combinan en una confirmación y se fusionan en la rama predeterminada. Las solicitudes de extracción con confirmaciones combinadas se fusionan usando la [fast-forward option](https://git-scm.com/docs/git-merge#_fast_forward_merge) (opción de avance rápido). - -Para combinar y fusionar solicitudes de extracción, debes tener [permisos de escritura](/articles/repository-permission-levels-for-an-organization/) en el repositorio, y el repositorio debe [permitir la fusión de combinaciones](/articles/configuring-commit-squashing-for-pull-requests/). - -![commit-squashing-diagram](/assets/images/help/pull_requests/commit-squashing-diagram.png) - -Puedes combinar y fusionar para crear un historial Git más optimizado en tu repositorio. Los compromisos de trabajo en curso son útiles cuando se trabaja en una rama de característica, pero no son tan importantes para retenerlos en el historial Git. Si combinas estas confirmaciones en una única confirmación al fusionar con la rama predeterminada, puedes conservar los cambios originales usando un historial Git claro. diff --git a/translations/es-XL/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md b/translations/es-XL/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md deleted file mode 100644 index c412bd6107..0000000000 --- a/translations/es-XL/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md +++ /dev/null @@ -1 +0,0 @@ -Los recordatorios programados ayudan a los equipos en enfocarse en las solicitudes de revisión más importantes que requieren su atención. Los recordatorios programados para las solicitudes de extracción enviarán un mensaje a tu equipo en Slack en una hora específica, el cual incluirá todas las solicitudes de extracción que tú o tu equipo estén pendientes de revisar. Por ejemplo, puedes crear un recordatorio programado para mandar un mensaje al canal principal de comunicación en Slack, incluyendo todas las solicitudes de extracción abiertas en las cuales se necesite la revisión del equipo, cada miércoles a las 9:00 a.m. diff --git a/translations/es-XL/data/reusables/reminders/add-reminder.md b/translations/es-XL/data/reusables/reminders/add-reminder.md deleted file mode 100644 index ae3e5d2d36..0000000000 --- a/translations/es-XL/data/reusables/reminders/add-reminder.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Recordatorios programados", da clic en **Agregar tu primer recordatorio**. ![Botón de agregar recordatorio](/assets/images/help/settings/scheduled-reminders-add-button.png) diff --git a/translations/es-XL/data/reusables/reminders/approved-prs.md b/translations/es-XL/data/reusables/reminders/approved-prs.md deleted file mode 100644 index a54f1ad5e7..0000000000 --- a/translations/es-XL/data/reusables/reminders/approved-prs.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, para apagar los recordatorios programados para las solicitudes de extracción que ya se han revisado y aprobado, selecciona **Ignorar las solicitudes de extracción aprobadas**. Posteriormente, da clic en **Ignorar si tiene 1 o más aprobaciones** para escoger cuántas aprobaciones debe tener una solicitud de extracción para que se le ingnore. ![Casilla de ignorar solicitudes de extracción aprobadas](/assets/images/help/settings/scheduled-reminders-ignore-approved-prs.png) diff --git a/translations/es-XL/data/reusables/reminders/author-reviews.md b/translations/es-XL/data/reusables/reminders/author-reviews.md deleted file mode 100644 index 2b6c9e4548..0000000000 --- a/translations/es-XL/data/reusables/reminders/author-reviews.md +++ /dev/null @@ -1 +0,0 @@ -1. De forma opcional, para enviar recordatorios a los autores de la solicitud de extracción después de que se hayan completado las solicitudes de revisión, selecciona **Recordar a los autores después de las revisiones** y elige la cantidad de revisiones requeridas antes de que se envíe un recordatorio. ![Casilla de recordar a los autores después de la revisión](/assets/images/help/settings/scheduled-reminders-remind-authors.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/reminders/authorize-slack.md b/translations/es-XL/data/reusables/reminders/authorize-slack.md deleted file mode 100644 index 40416aa2f0..0000000000 --- a/translations/es-XL/data/reusables/reminders/authorize-slack.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Espacio de trabajo de Slack", da clic en **Autorizar espacio de trabajo de Slack** y sigue las instrucciones. ![Botón de Autorizar espacio de trabajo de Slack](/assets/images/help/settings/scheduled-reminders-authorize-slack.png) diff --git a/translations/es-XL/data/reusables/reminders/create-reminder.md b/translations/es-XL/data/reusables/reminders/create-reminder.md deleted file mode 100644 index 4ab80323d9..0000000000 --- a/translations/es-XL/data/reusables/reminders/create-reminder.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Crear recordatorio**. diff --git a/translations/es-XL/data/reusables/reminders/days-dropdown.md b/translations/es-XL/data/reusables/reminders/days-dropdown.md deleted file mode 100644 index 796c064a4b..0000000000 --- a/translations/es-XL/data/reusables/reminders/days-dropdown.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Días", da clic en **Días de la semana**{% octicon "triangle-down" aria-label="The down triangle icon" %} para seleccionar uno o más días en los que quieras recibir recordatorios programados. ![Menú desplegable de días](/assets/images/help/settings/scheduled-reminders-days.png) diff --git a/translations/es-XL/data/reusables/reminders/delete.md b/translations/es-XL/data/reusables/reminders/delete.md deleted file mode 100644 index e38f239283..0000000000 --- a/translations/es-XL/data/reusables/reminders/delete.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Al final del la página, da clic en **Borrar este recordatorio**. ![Boton de borrar un recordatorio programado](/assets/images/help/settings/scheduled-reminders-delete.png) -1. Para confirmar que quieres borrar el recordatorio programado, da clic en **OK**. diff --git a/translations/es-XL/data/reusables/reminders/edit-existing.md b/translations/es-XL/data/reusables/reminders/edit-existing.md deleted file mode 100644 index c1be9e16fb..0000000000 --- a/translations/es-XL/data/reusables/reminders/edit-existing.md +++ /dev/null @@ -1 +0,0 @@ -1. Junto al recordatorio programado que quieras actualizar, da clic en **Editar**. ![Editar el recordatorio programado existente](/assets/images/help/settings/scheduled-reminders-edit-existing.png) diff --git a/translations/es-XL/data/reusables/reminders/edit-page.md b/translations/es-XL/data/reusables/reminders/edit-page.md deleted file mode 100644 index 5be33e81c0..0000000000 --- a/translations/es-XL/data/reusables/reminders/edit-page.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz uno o más cambios a tu recordatorio programado. diff --git a/translations/es-XL/data/reusables/reminders/ignore-drafts.md b/translations/es-XL/data/reusables/reminders/ignore-drafts.md deleted file mode 100644 index c312dcae87..0000000000 --- a/translations/es-XL/data/reusables/reminders/ignore-drafts.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, para excluir las solicitudes de extracción de los recordatorios programados, selecciona **Ignorar borradores**. Para obtener más información, consulta la sección "[Borradores de solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests)". ![Casilla de ignorar borradores de solicitudes de extracción](/assets/images/help/settings/scheduled-reminders-ignore-drafts.png) diff --git a/translations/es-XL/data/reusables/reminders/ignored-labels.md b/translations/es-XL/data/reusables/reminders/ignored-labels.md deleted file mode 100644 index 51c448e099..0000000000 --- a/translations/es-XL/data/reusables/reminders/ignored-labels.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "etiquetas ignoradas", teclea una lista de etiquetas separadas por comas. Los recordatorios programados no incluirán ninguna solicitud de extracción que tenga una o más de estas etiquetas. ![Campo de etiquetas ignoradas](/assets/images/help/settings/scheduled-reminders-ignored-labels-field.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/reminders/ignored-terms.md b/translations/es-XL/data/reusables/reminders/ignored-terms.md deleted file mode 100644 index b738d4f371..0000000000 --- a/translations/es-XL/data/reusables/reminders/ignored-terms.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "condiciones ignoradas", teclea una lista separada por comas de los términos que podrían aparecer en los títulos de las solicitudes de extracción. Los recordatorios programados no incluirán ninguna solicitud de extracción que contenga uno o más de estos términos en sus títulos. ![Campo de términos ignorados](/assets/images/help/settings/scheduled-reminders-ignored-terms-field.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/reminders/min-age.md b/translations/es-XL/data/reusables/reminders/min-age.md deleted file mode 100644 index 0085472540..0000000000 --- a/translations/es-XL/data/reusables/reminders/min-age.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Edad mínima", teclea la edad de una solicitud de extracción en horas. Los recordatorios programados no incluirán solicitudes de extracción que sean más recientes que éste límite de edad. ![Campo de etiquetas ignoradas](/assets/images/help/settings/scheduled-reminders-min-age-field.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/reminders/min-staleness.md b/translations/es-XL/data/reusables/reminders/min-staleness.md deleted file mode 100644 index bfb59402dc..0000000000 --- a/translations/es-XL/data/reusables/reminders/min-staleness.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Tiempo mínimo transcurrido", teclea la hora de la última actividad en una solicitud de extracción, en horas. Los recordatorios programados no incluirán aquellas solicitudes de extracción cuya última actividad haya sido más reciente que el de esta hora. ![Campo de tiempo mínimo transcurrido](/assets/images/help/settings/scheduled-reminders-min-staleness-field.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/reminders/no-review-requests.md b/translations/es-XL/data/reusables/reminders/no-review-requests.md deleted file mode 100644 index 90a23c791d..0000000000 --- a/translations/es-XL/data/reusables/reminders/no-review-requests.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, para incluir únicamente las solicitudes de extracción en donde se solicita específicamente una revisión del equipo o de un miembro del equipo, selecciona **Requerir solicitudes de revisión**. Si no seleccionas esta opción, todas las solicitudes de extracción se incluirán en el recordatorio programado. ![Casilla de ignorar solicitudes de extracción sin solicitudes de revisión](/assets/images/help/settings/scheduled-reminders-prs-without-requests.png) diff --git a/translations/es-XL/data/reusables/reminders/real-time-alerts.md b/translations/es-XL/data/reusables/reminders/real-time-alerts.md deleted file mode 100644 index 0c5595a87f..0000000000 --- a/translations/es-XL/data/reusables/reminders/real-time-alerts.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, para recibir mensajes de Slack tan pronto sucedan ciertos eventos, selecciona **Habilitar alertas en tiempo real** y selecciona los eventos en los que éstas se recibirán. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/reminders/required-labels.md b/translations/es-XL/data/reusables/reminders/required-labels.md deleted file mode 100644 index f2b2098103..0000000000 --- a/translations/es-XL/data/reusables/reminders/required-labels.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Etiquetas requeridas", teclea una lista de etiquetas separadas por comas. Los recordatorios programados solo incluirán las solicitudes de extracción que no se hayan ignorado en caso de que tengan una o más de estas etiquetas. ![Campo de etiquetas requeridas](/assets/images/help/settings/scheduled-reminders-required-labels-field.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/reminders/scheduled-reminders.md b/translations/es-XL/data/reusables/reminders/scheduled-reminders.md deleted file mode 100644 index 36fd7c9f38..0000000000 --- a/translations/es-XL/data/reusables/reminders/scheduled-reminders.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Recordatorios programados**. diff --git a/translations/es-XL/data/reusables/reminders/slack-channel.md b/translations/es-XL/data/reusables/reminders/slack-channel.md deleted file mode 100644 index a9a40def0b..0000000000 --- a/translations/es-XL/data/reusables/reminders/slack-channel.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Canal de Slack", teclea el nombre del canal de Slack en donde quieres recibir notificaciones. ![Campo de canal de Slack](/assets/images/help/settings/scheduled-reminders-slack-channel.png) diff --git a/translations/es-XL/data/reusables/reminders/times-dropdowns.md b/translations/es-XL/data/reusables/reminders/times-dropdowns.md deleted file mode 100644 index b26d121a65..0000000000 --- a/translations/es-XL/data/reusables/reminders/times-dropdowns.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Seleccionar Horario(s)", da clic en **9:00 AM** {% octicon "triangle-down" aria-label="The down triangle icon" %} para seleccionar uno o más horarios en los cuales deseas recibir recordatorios programados. Opcionalmente, para cambiar tu huso horario, da clic en {% octicon "triangle-down" aria-label="The down triangle icon" %} junto a tu huso horario actual y selecciona un huso horario diferente. ![Menús desplegables de seleccionar horario(s)](/assets/images/help/settings/scheduled-reminders-times.png) diff --git a/translations/es-XL/data/reusables/reminders/tracked-repos.md b/translations/es-XL/data/reusables/reminders/tracked-repos.md deleted file mode 100644 index 30d62942ab..0000000000 --- a/translations/es-XL/data/reusables/reminders/tracked-repos.md +++ /dev/null @@ -1,5 +0,0 @@ -1. Debajo de "Repositorios rastreados", escoge sobre cuáles repositorios te gustaría que el equipo recibiera recordatorios de las revisiones de solicitudes de rastreo. - - Para recibir recordatorios de todos los repositorios a los cuales tiene acceso el equipo elegido, da clic en **Todos los repositorios**. - - Para recibir recordatorios de un subconjunto de repositorios, da clic en **Seleccionar únicamente repositorios**, y luego selecciona uno o más repositorios a los que tenga acceso el equipo elegido. - - ![Elige los repositorios rastreados](/assets/images/help/settings/scheduled-reminders-tracked-repos.png) diff --git a/translations/es-XL/data/reusables/reminders/update-buttons.md b/translations/es-XL/data/reusables/reminders/update-buttons.md deleted file mode 100644 index 9fc787133e..0000000000 --- a/translations/es-XL/data/reusables/reminders/update-buttons.md +++ /dev/null @@ -1 +0,0 @@ -1. Para guardar tus cambios, da clic en **Actualizar recordatorio**. Opcionalmente, para probar tus cambios mientras los actualizas, da clic en **Actualizar y probar recordatorio**. ![Botones de actualización](/assets/images/help/settings/scheduled-reminders-update-buttons.png) diff --git a/translations/es-XL/data/reusables/repositories/a-vulnerability-is.md b/translations/es-XL/data/reusables/repositories/a-vulnerability-is.md deleted file mode 100644 index 3c7913490f..0000000000 --- a/translations/es-XL/data/reusables/repositories/a-vulnerability-is.md +++ /dev/null @@ -1 +0,0 @@ -Una vulnerabilidad es un problema en el código de un proyecto que se puede aprovechar para dañar la confidencialidad, la integridad o la disponibilidad del proyecto o de otros proyectos que usan su código. Las vulnerabilidades varían en tipo, severidad y método de ataque. diff --git a/translations/es-XL/data/reusables/repositories/about-github-actions.md b/translations/es-XL/data/reusables/repositories/about-github-actions.md deleted file mode 100644 index e93b7ceb94..0000000000 --- a/translations/es-XL/data/reusables/repositories/about-github-actions.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_actions %} te ayuda a automatizar tus flujos de trabajo de desarrollo de software en el mismo lugar en el que almacenas código y colaboras con informes de problemas y solicitudes de extracción. Puedes escribir tareas individuales, llamadas acciones, y combinarlas para crear un flujo de trabajo personalizado. diff --git a/translations/es-XL/data/reusables/repositories/about-github-archive-program.md b/translations/es-XL/data/reusables/repositories/about-github-archive-program.md deleted file mode 100644 index 9e3cf851d7..0000000000 --- a/translations/es-XL/data/reusables/repositories/about-github-archive-program.md +++ /dev/null @@ -1 +0,0 @@ -Predeterminadamente, todos los repositorios públicos se incluyen en el {% data variables.product.prodname_archive %}, una sociedad entre {% data variables.product.prodname_dotcom %} y organizaciones tales como Software Heritage Foundation e Internet Archive para garantizar la preservación a largo plazo del software de código abierto en el mundo. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/repositories/about-internal-repos.md b/translations/es-XL/data/reusables/repositories/about-internal-repos.md deleted file mode 100644 index d921cfd133..0000000000 --- a/translations/es-XL/data/reusables/repositories/about-internal-repos.md +++ /dev/null @@ -1 +0,0 @@ -You can use internal repositories to practice "innersource" within your {% if currentVersion == "free-pro-team@latest" %}enterprise account{% else %}instance{% endif %}. Members of {% if currentVersion == "free-pro-team@latest" %}your enterprise account{% else %}any organization on your instance{% endif %} can collaborate using open source methodologies without sharing proprietary information publicly{% if currentVersion != "free-pro-team@latest" %}, even with private mode disabled{% endif %}. diff --git a/translations/es-XL/data/reusables/repositories/accessing-repository-graphs.md b/translations/es-XL/data/reusables/repositories/accessing-repository-graphs.md deleted file mode 100644 index 08f7bf2b8c..0000000000 --- a/translations/es-XL/data/reusables/repositories/accessing-repository-graphs.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de tu nombre de repositorio, da clic en {% octicon "graph" aria-label="The bar graph icon" %}**Perspectivas**. ![Pestaña de perspectivas en la barra de navegación del repositorio principal](/assets/images/help/repository/repo-nav-insights-tab.png) diff --git a/translations/es-XL/data/reusables/repositories/accessing-repository-people.md b/translations/es-XL/data/reusables/repositories/accessing-repository-people.md deleted file mode 100644 index 2877e8412b..0000000000 --- a/translations/es-XL/data/reusables/repositories/accessing-repository-people.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Personas**. ![Pestaña de personas en la barra lateral del repositorio](/assets/images/help/repository/accessing-repository-people.png) diff --git a/translations/es-XL/data/reusables/repositories/action-root-user-required.md b/translations/es-XL/data/reusables/repositories/action-root-user-required.md deleted file mode 100644 index db25da04f9..0000000000 --- a/translations/es-XL/data/reusables/repositories/action-root-user-required.md +++ /dev/null @@ -1 +0,0 @@ -**Nota:**{% data variables.product.prodname_actions %} debe ejecutarse por el usuario predeterminado (root) de Docker. Asegúrate de que tu Dockerfile no configure la instrucción de `USER`, de lo contrario, no podrás acceder a `GITHUB_WORKSPACE`. diff --git a/translations/es-XL/data/reusables/repositories/actions-ci-cd.md b/translations/es-XL/data/reusables/repositories/actions-ci-cd.md deleted file mode 100644 index f620d66af6..0000000000 --- a/translations/es-XL/data/reusables/repositories/actions-ci-cd.md +++ /dev/null @@ -1 +0,0 @@ -Con {% data variables.product.prodname_actions %} puedes crear capacidades de integración continua (CI, por sus siglas en inglés) de extremo a extremo y de funcionamiento continuo (CD, por sus siglas en inglés) directamente en tu repositorio. diff --git a/translations/es-XL/data/reusables/repositories/actions-env-var-note.md b/translations/es-XL/data/reusables/repositories/actions-env-var-note.md deleted file mode 100644 index 4362e3e21f..0000000000 --- a/translations/es-XL/data/reusables/repositories/actions-env-var-note.md +++ /dev/null @@ -1 +0,0 @@ -Cuando se define más de una variable de ambiente con el mismo nombre, {% data variables.product.prodname_dotcom %} utiliza la más específica. Por ejemplo, una variable de ambiente definida en un paso anulará aquellas de los jobs y flujos de trabajo con el mismo nombre, mientras ejecuta el paso. Una variable definida para un trabajo anulará aquella de un flujo de trabajo si tienen el mismo nombre, mientras ejecuta el job. diff --git a/translations/es-XL/data/reusables/repositories/actions-matrix-builds-os.md b/translations/es-XL/data/reusables/repositories/actions-matrix-builds-os.md deleted file mode 100644 index 0433de1e12..0000000000 --- a/translations/es-XL/data/reusables/repositories/actions-matrix-builds-os.md +++ /dev/null @@ -1 +0,0 @@ -Cuando defines una matriz de sistemas operativos, debes modificar el valor de `runs-on` a la propiedad de contexto de `matrix.os` que definiste. diff --git a/translations/es-XL/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/es-XL/data/reusables/repositories/actions-scheduled-workflow-example.md deleted file mode 100644 index 506768d0f0..0000000000 --- a/translations/es-XL/data/reusables/repositories/actions-scheduled-workflow-example.md +++ /dev/null @@ -1,11 +0,0 @@ -Puedes programar un flujo de trabajo para que se ejecute en horarios UTC específicos usando [sintaxis de cron POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Los flujos de trabajo programados se ejecutan en la confirmación más reciente en la rama base o en la rama por defecto. El intervalo más corto en el que puedes ejecutar flujos de trabajo programados es una vez cada 5 minutos. - -Este ejemplo activa el flujo de trabajo cada 15 minutos: - -```yaml -on: - schedule: - # * is a special character in YAML so you have to quote this string - - cron: '*/15 * * * *' - -``` diff --git a/translations/es-XL/data/reusables/repositories/actions-tab.md b/translations/es-XL/data/reusables/repositories/actions-tab.md deleted file mode 100644 index 6ad37f4246..0000000000 --- a/translations/es-XL/data/reusables/repositories/actions-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo del nombre de tu repositorio, da clic en **Acciones**. ![Pestaña de acciones en la navegación del repositorio principal](/assets/images/help/repository/actions-tab.png) diff --git a/translations/es-XL/data/reusables/repositories/actions-workflow-status-badge-into.md b/translations/es-XL/data/reusables/repositories/actions-workflow-status-badge-into.md deleted file mode 100644 index 74cdcea558..0000000000 --- a/translations/es-XL/data/reusables/repositories/actions-workflow-status-badge-into.md +++ /dev/null @@ -1,3 +0,0 @@ -Las insignias de estado muestran si un flujo de trabajo está fallando o pasando actualmente. Un lugar común para agregar una insignia de estado es el archivo README.md de tu repositorio, pero puedes agregarlo a cualquier página web que quieras. Predeterminadamente, las insignias muestran el estado de tu rama predeterminada. También puedes mostrar el estado de la ejecución de un flujo de trabajo para una rama o evento específicos utilizando los parámetros de query `branch` y `event` en la URL. - -![ejemplo de insignia de estado](/assets/images/help/repository/actions-workflow-status-badge.png) diff --git a/translations/es-XL/data/reusables/repositories/add-branch-protection-rules.md b/translations/es-XL/data/reusables/repositories/add-branch-protection-rules.md deleted file mode 100644 index f0d1f9909a..0000000000 --- a/translations/es-XL/data/reusables/repositories/add-branch-protection-rules.md +++ /dev/null @@ -1,2 +0,0 @@ -4. Junto a "Reglas de protección de rama", da clic en **Agregar regla**. ![Botón de agregar regla de protección de rama](/assets/images/help/branches/add-branch-protection-rule.png) -5. Debajo del "Patrón del nombre de la rama", teclea el nombre de la rama o el patrón que quieras proteger. ![Campo de regla de rama ](/assets/images/help/branches/specify-branch-protection-rule.png) diff --git a/translations/es-XL/data/reusables/repositories/allow-maintainers-user-forks.md b/translations/es-XL/data/reusables/repositories/allow-maintainers-user-forks.md deleted file mode 100644 index 21fe6f6b62..0000000000 --- a/translations/es-XL/data/reusables/repositories/allow-maintainers-user-forks.md +++ /dev/null @@ -1,7 +0,0 @@ -1. En las bifurcaciones que pertenecen a un usuario, si no quieres permitir que las personas con acceso de escritura en el repositorio ascendente realicen cambios en tu solicitud de extracción, deselecciona **Permitir ediciones de los mantenedores**. - - {% warning %} - - **Advertencia:** Si tu bifuración contiene flujos de trabajo de {% data variables.product.prodname_actions %}, la opción es **Permitir que los mantenedores hagan ediciones y tengan acceso a los secretos**. El permitir las ediciones en la rama de una bifurcación que contiene flujos de trabajo de {% data variables.product.prodname_actions %} también permite que un mantenedor edite los flujos de trabajo del repositorio, lo cual podría revelar los valores de los secretos y otorgar acceso a otras ramas potencialmente. - - {% endwarning %} diff --git a/translations/es-XL/data/reusables/repositories/archiving-repositories-recommendation.md b/translations/es-XL/data/reusables/repositories/archiving-repositories-recommendation.md deleted file mode 100644 index 6525dcb673..0000000000 --- a/translations/es-XL/data/reusables/repositories/archiving-repositories-recommendation.md +++ /dev/null @@ -1 +0,0 @@ -Recomendamos que cierres todas las propuestas y solicitudes de extracción, y que además actualices la descripción y el archivo README antes de que archives un repositorio. diff --git a/translations/es-XL/data/reusables/repositories/asking-for-review.md b/translations/es-XL/data/reusables/repositories/asking-for-review.md deleted file mode 100644 index f79f4ffb06..0000000000 --- a/translations/es-XL/data/reusables/repositories/asking-for-review.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Tip:** Después de que crees una solicitud de extracción, puedes pedir a alguien en específico que [revise tus cambios propuestos](/articles/reviewing-proposed-changes-in-a-pull-request). Para obtener más información, consulta "[Solicitar la revisión de una solicitud de extracción](/articles/requesting-a-pull-request-review/)". - -{% endtip %} diff --git a/translations/es-XL/data/reusables/repositories/assign-an-issue-as-project-maintainer.md b/translations/es-XL/data/reusables/repositories/assign-an-issue-as-project-maintainer.md deleted file mode 100644 index 21e754aeab..0000000000 --- a/translations/es-XL/data/reusables/repositories/assign-an-issue-as-project-maintainer.md +++ /dev/null @@ -1 +0,0 @@ -1. Si eres un mantenedor de proyecto, puedes [asignar el informe de problemas a alguien](/articles/assigning-issues-and-pull-requests-to-other-github-users), [agregarlo a un tablero de proyecto](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar), [asociarlo con un hito](/articles/associating-milestones-with-issues-and-pull-requests), o [aplicar una etiqueta](/articles/applying-labels-to-issues-and-pull-requests). diff --git a/translations/es-XL/data/reusables/repositories/autolink-references.md b/translations/es-XL/data/reusables/repositories/autolink-references.md deleted file mode 100644 index a7e2430c1f..0000000000 --- a/translations/es-XL/data/reusables/repositories/autolink-references.md +++ /dev/null @@ -1 +0,0 @@ -Si se configuran las referencias autovinculadas personalizadas para un repositorio, entonces las referencias a recursos externos, como un informe de problemas de JIRA o un ticket de Zendesk, se convertirán en vínculos acortados. Para saber qué autovínculos se encuentran disponibles en tu repositorio, contacta a alguien con permisos administrativos sobre el mismo. Para obtener más información, consulta la sección "[Configurar autovínculos para referenciar recursos externos](/articles/configuring-autolinks-to-reference-external-resources)". diff --git a/translations/es-XL/data/reusables/repositories/blocked-passwords.md b/translations/es-XL/data/reusables/repositories/blocked-passwords.md deleted file mode 100644 index dd9de7d23a..0000000000 --- a/translations/es-XL/data/reusables/repositories/blocked-passwords.md +++ /dev/null @@ -1,5 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Cuando tecleas una contraseña para ingresar, creas una cuenta, o cambias tu contraseña, {% data variables.product.product_name %} verificará si la contraseña que ingresaste se considera como débil de acuerdo con los sets de datos como HavelBeenPwned. La contraseña se puede considerar débil, incluso si no la usaste nunca antes. - -{% data variables.product.product_name %} solo inspecciona la contraseña cuando la escribes, pero nunca almacena la contraseña que ingresaste como texto simple. Para obtener más información, consulta [HaveIBeenPwned](https://haveibeenpwned.com/). -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/branch-rules-example.md b/translations/es-XL/data/reusables/repositories/branch-rules-example.md deleted file mode 100644 index fd61bf89e7..0000000000 --- a/translations/es-XL/data/reusables/repositories/branch-rules-example.md +++ /dev/null @@ -1 +0,0 @@ -Puedes crear una regla de rama en un repositorio para una rama específica, todas las ramas, o cualquier rama que coincida con un patrón de ponderación especificado con la sintaxis fnmatch. Por ejemplo, para requerir que cualquier rama que contenga la palabra `release` contenga por lo menos dos revisiones de solicitud de extracción antes de su fusión, puedes crear una regla de rama para `*release*`. diff --git a/translations/es-XL/data/reusables/repositories/changed-files.md b/translations/es-XL/data/reusables/repositories/changed-files.md deleted file mode 100644 index 733080c30b..0000000000 --- a/translations/es-XL/data/reusables/repositories/changed-files.md +++ /dev/null @@ -1 +0,0 @@ -1. En la solicitud de extracción, da clic en {% octicon "diff" aria-label="The file diff icon" %}**Archivos cambiados**. ![Pestaña de Archivos Cambiados](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png) diff --git a/translations/es-XL/data/reusables/repositories/changed-repository-access-permissions.md b/translations/es-XL/data/reusables/repositories/changed-repository-access-permissions.md deleted file mode 100644 index 6919fa6283..0000000000 --- a/translations/es-XL/data/reusables/repositories/changed-repository-access-permissions.md +++ /dev/null @@ -1 +0,0 @@ -8. Lee acerca de los permisos de acceso a repositorios que se han modificado. diff --git a/translations/es-XL/data/reusables/repositories/choose-line-or-range.md b/translations/es-XL/data/reusables/repositories/choose-line-or-range.md deleted file mode 100644 index 5696832849..0000000000 --- a/translations/es-XL/data/reusables/repositories/choose-line-or-range.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Decide si seleccionar una única línea o un rango: - - Para seleccionar una única línea del código, haz clic en el número de línea para resaltarla. ![Archivo con una única línea del código seleccionada](/assets/images/help/repository/highlight-line-of-code.png) - - Para seleccionar un rango de código, haz clic en el número de la primera línea del rango para resaltar la línea del código. Luego lleva el puntero hasta la última línea del rango del código, presiona Shift y haz clic en el número de línea para resaltar el rango. ![Archivo con un rango del código seleccionado](/assets/images/help/repository/highlight-range-of-code.png) diff --git a/translations/es-XL/data/reusables/repositories/choose-pr-review.md b/translations/es-XL/data/reusables/repositories/choose-pr-review.md deleted file mode 100644 index d91f18aebd..0000000000 --- a/translations/es-XL/data/reusables/repositories/choose-pr-review.md +++ /dev/null @@ -1 +0,0 @@ -1. En la lista de solicitudes de extracción, haz clic en la solicitud de extracción que deseas revisar. diff --git a/translations/es-XL/data/reusables/repositories/choose-repo-visibility.md b/translations/es-XL/data/reusables/repositories/choose-repo-visibility.md deleted file mode 100644 index 88101c9b4b..0000000000 --- a/translations/es-XL/data/reusables/repositories/choose-repo-visibility.md +++ /dev/null @@ -1 +0,0 @@ -1. Elige la visibilidad del repositorio. Para obtener más información, consulta la sección "[Acerca de la visibilidad de un repositorio](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)". ![Botones radiales para seleccionar la visibilidad del repositorio](/assets/images/help/repository/create-repository-public-private.png) diff --git a/translations/es-XL/data/reusables/repositories/click-dependency-graph.md b/translations/es-XL/data/reusables/repositories/click-dependency-graph.md deleted file mode 100644 index 94479c6214..0000000000 --- a/translations/es-XL/data/reusables/repositories/click-dependency-graph.md +++ /dev/null @@ -1 +0,0 @@ -3. En la barra lateral izquierda, da clic en **Gráfica de dependencias**. ![Pestaña de gráfica de dependencias en la barra lateral izquierda](/assets/images/help/graphs/graphs-sidebar-dependency-graph.png) diff --git a/translations/es-XL/data/reusables/repositories/copy-clone-url.md b/translations/es-XL/data/reusables/repositories/copy-clone-url.md deleted file mode 100644 index 0d8d2e865e..0000000000 --- a/translations/es-XL/data/reusables/repositories/copy-clone-url.md +++ /dev/null @@ -1,15 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -1. Debajo del nombre del repositorio, da clic en **Clonar o descargar**. ![Botón Clone or download (Clonar o descargar)](/assets/images/help/repository/clone-repo-clone-url-button.png) -2. To clone the repository using HTTPS, under "Clone with HTTPS", click -{% octicon "clippy" aria-label="The clipboard icon" %}. -Para clonar el repositorio utilizando una llave SSH -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, incluyendo un certificado que emita la autoridad de certificados SSH de tu organización, {% endif %} da clic en **Utilizar SSH** y luego en {% octicon "clippy" aria-label="The clipboard icon" %}. -![Botón Clone URL (Clonar URL)](/assets/images/help/repository/https-url-clone.png) -{% else %} -1. Sobre la lista de archivos, da clic en {% octicon "download" aria-label="The download icon" %} **Código**. ![Botón de "Código"](/assets/images/help/repository/code-button.png) -1. To clone the repository using HTTPS, under "Clone with HTTPS", click -{% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}, including a certificate issued by your organization's SSH certificate authority,{% endif %} click **Use SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %} To clone a repository using {% data variables.product.prodname_cli %}, click **Use {% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.{% endif %} - ![El icono de portapapeles para copiar la URL para clonar un repositorio](/assets/images/help/repository/https-url-clone.png) - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} - ![The clipboard icon for copying the URL to clone a repository with GitHub CLI](/assets/images/help/repository/https-url-clone-cli.png){% endif %} -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/create-issue-in-public-repository.md b/translations/es-XL/data/reusables/repositories/create-issue-in-public-repository.md deleted file mode 100644 index 32303d657f..0000000000 --- a/translations/es-XL/data/reusables/repositories/create-issue-in-public-repository.md +++ /dev/null @@ -1 +0,0 @@ -Cualquier usuario de {% data variables.product.product_name %} puede crear un informe de problemas en un repositorio público donde [no se hayan inhabilitado los informes de problemas](/articles/disabling-issues). diff --git a/translations/es-XL/data/reusables/repositories/create-pull-request.md b/translations/es-XL/data/reusables/repositories/create-pull-request.md deleted file mode 100644 index 0cd97fc67e..0000000000 --- a/translations/es-XL/data/reusables/repositories/create-pull-request.md +++ /dev/null @@ -1 +0,0 @@ -1. Para crear una solicitud de extracción que está lista para revisión, haz clic en **Create Pull Request** (Crear solicitud de extracción). Para crear un borrador de solicitud de extracción, utiliza el menú desplegable y selecciona **Crear Borrador de Solicitud de Extracción**, y posteriormente da clic en **Borrador de Solicitud de Extracción**. Para obtener más información acerca de las solicitudes de extracción en borrador "[Acerca de las solicitudes de extracción](/articles/about-pull-requests#draft-pull-requests)".![Botón Create pull request (Crear una solicitud de extracción)](/assets/images/help/pull_requests/pullrequest-send.png) diff --git a/translations/es-XL/data/reusables/repositories/create-repo.md b/translations/es-XL/data/reusables/repositories/create-repo.md deleted file mode 100644 index 5d318d0e76..0000000000 --- a/translations/es-XL/data/reusables/repositories/create-repo.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Crear repositorio**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}![Button to create repository](/assets/images/help/repository/create-repository-button.png){% endif %} diff --git a/translations/es-XL/data/reusables/repositories/create_new.md b/translations/es-XL/data/reusables/repositories/create_new.md deleted file mode 100644 index 92090980ee..0000000000 --- a/translations/es-XL/data/reusables/repositories/create_new.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de cualquier página, utiliza el menú desplegable {% octicon "plus" aria-label="Plus symbol" %} y selecciona **Repositorio Nuevo**. ![Menú desplegable con opción para crear un repositorio nuevo](/assets/images/help/repository/repo-create.png) diff --git a/translations/es-XL/data/reusables/repositories/default-issue-templates.md b/translations/es-XL/data/reusables/repositories/default-issue-templates.md deleted file mode 100644 index fe769bb1a1..0000000000 --- a/translations/es-XL/data/reusables/repositories/default-issue-templates.md +++ /dev/null @@ -1,2 +0,0 @@ -Puedes crear plantillas de informe de problemas predeterminadas{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} y un archivo de configuración predeterminado para éstas{% endif %} para tu cuenta de organización{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o de usuario{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/github/building-a-strong-community/creating-a-default-community-health-file)" - diff --git a/translations/es-XL/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/es-XL/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md deleted file mode 100644 index 0ad369bb46..0000000000 --- a/translations/es-XL/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md +++ /dev/null @@ -1,11 +0,0 @@ -{% warning %} - -**Advertencia:** - -- Si eliminas el acceso de una persona a un repositorio privado, todas sus bifurcaciones de ese repositorio privado se eliminarán. Los clones locales del repositorio privado se conservarán. Si se revoca el acceso de un equipo a un repositorio privado o se elimina un equipo con acceso a un repositorio privado, y los miembros del equipo no tienen acceso al repositorio a través de otro equipo, las bifurcaciones privadas del repositorio se eliminarán.{% if currentVersion != "free-pro-team@latest" %} -- Cuando [LDAP Sync esté habilitado](/enterprise/{{ currentVersion }}/admin/guides/user-management/using-ldap/#enabling-ldap-sync), si eliminas a una persona de un repositorio, perderá acceso, pero sus bifurcaciones no se eliminarán. Si la persona se agrega a un equipo con acceso al repositorio original de la organización dentro de los tres meses, su acceso a las bifurcaciones se restaurarán de manera automática la próxima vez que ocurra una sincronización.{% endif %} -- Eres responsable de asegurar que las personas que perdieron el acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. - -- Las personas con permisos administrativos en un repositorio privado{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o interno{% endif %} pueden dejar de permitir la bifurcación del mismo, y los propietarios de la organización pueden dejar de permitir la bifurcación de cualquier repositorio privado {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} o interno {% endif %} en una organización. Para obtener más información, consulta la sección "[Administrar la política de bifurcación para tu organización](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)" y "[Administrar la política de bifurcación para tu repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)". - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/repositories/deploy-keys-write-access.md b/translations/es-XL/data/reusables/repositories/deploy-keys-write-access.md deleted file mode 100644 index e32d6199c1..0000000000 --- a/translations/es-XL/data/reusables/repositories/deploy-keys-write-access.md +++ /dev/null @@ -1 +0,0 @@ -Las claves de despliegue con acceso de escritura pueden llevar a cabo las mismas acciones que un miembro de la organización con acceso administrativo o que un colaborador en un repositorio personal. Para obtener más información, consulta las secciones "[Niveles de permiso en los repositorios para una organización](/articles/repository-permission-levels-for-an-organization/)" y "[Niveles de permiso para un repositorio de una cuenta de usuario](/articles/permission-levels-for-a-user-account-repository/)". diff --git a/translations/es-XL/data/reusables/repositories/deploy-keys.md b/translations/es-XL/data/reusables/repositories/deploy-keys.md deleted file mode 100644 index 521b1e2a3b..0000000000 --- a/translations/es-XL/data/reusables/repositories/deploy-keys.md +++ /dev/null @@ -1 +0,0 @@ -Puedes lanzar proyectos desde un repositorio de {% data variables.product.product_name %} hacia tu servidor al utilizar una llave de despliegue, la cual es una llave SSH que otorga acceso a un repositorio específico. {% data variables.product.product_name %} adjunta la parte pública de la llave directamente en tu repositorio en vez de hacerlo a una cuenta de usuario, y la parte privada de ésta permanece en tu servidor. Para obtener más información, consulta la sección "[Entregar despliegues](/v3/guides/delivering-deployments/)". diff --git a/translations/es-XL/data/reusables/repositories/desktop-fork.md b/translations/es-XL/data/reusables/repositories/desktop-fork.md deleted file mode 100644 index cc9cd72cf3..0000000000 --- a/translations/es-XL/data/reusables/repositories/desktop-fork.md +++ /dev/null @@ -1 +0,0 @@ -Puedes utilizar {% data variables.product.prodname_desktop %} para bifurcar un repositorio. Para obtener más información, consulta la sección "[Clonar y bifurar repositorios de {% data variables.product.prodname_desktop %}](/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop)". diff --git a/translations/es-XL/data/reusables/repositories/edit-file.md b/translations/es-XL/data/reusables/repositories/edit-file.md deleted file mode 100644 index 01a0b1450a..0000000000 --- a/translations/es-XL/data/reusables/repositories/edit-file.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de la vista del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %} para abrir el editor de archivos. ![Botón Editar archivo](/assets/images/help/repository/edit-file-edit-button.png) diff --git a/translations/es-XL/data/reusables/repositories/edited-comment-list.md b/translations/es-XL/data/reusables/repositories/edited-comment-list.md deleted file mode 100644 index d92ee5268b..0000000000 --- a/translations/es-XL/data/reusables/repositories/edited-comment-list.md +++ /dev/null @@ -1,9 +0,0 @@ -2. En la parte superior del comentario, da clic en **editado** para abrir el historial de edición. - - {% note %} - - **Nota:** si no ves la opción de **editado**, entonces el comentario no tiene un historial de edición. - - {% endnote %} - -3. Para ver los detalles de un cambio específico, selecciónalo de la lista de ediciones. ![Ver los detalles de edición de un comentario](/assets/images/help/repository/choose-comment-edit-to-expand.png) diff --git a/translations/es-XL/data/reusables/repositories/enable-security-alerts.md b/translations/es-XL/data/reusables/repositories/enable-security-alerts.md deleted file mode 100644 index b4d2c23d70..0000000000 --- a/translations/es-XL/data/reusables/repositories/enable-security-alerts.md +++ /dev/null @@ -1,4 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} -Your site administrator must enable -Tu administrador de sitio debe habilitar las alertas de seguridad para las dependencias vulnerables de {% data variables.product.product_location_enterprise %} para que puedas utilizar esta característica. Para obtener más información, consulta "[Habilitar alertas de seguridad para dependencias vulnerables en el {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server)". -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/github-reviews-security-advisories.md b/translations/es-XL/data/reusables/repositories/github-reviews-security-advisories.md deleted file mode 100644 index a44a3be33c..0000000000 --- a/translations/es-XL/data/reusables/repositories/github-reviews-security-advisories.md +++ /dev/null @@ -1,3 +0,0 @@ -{% data variables.product.prodname_dotcom %} revisará cada asesoría de seguridad que se haya publicado, la agregará a la {% data variables.product.prodname_advisory_database %}, y podría utilzar esta asesoría de seguridad para enviar {% data variables.product.prodname_dependabot_alerts %} a los repositorios que se vean afectados. Si la asesoría de seguridad viene de una bifurcación, únicamente enviaremos una alerta si ésta tiene un paquete que se publique con un nombre único y esté en un registro de paquetes público. Este proceso puede tomar hasta 72 horas y {% data variables.product.prodname_dotcom %} podría contactarte para obtener más información. - -Para obtener más informació acera de las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". Para obtener más información acerca de la {% data variables.product.prodname_advisory_database %}, consulta la sección "[Buscar vulnerabilidades de seguridad en la {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)". diff --git a/translations/es-XL/data/reusables/repositories/github-security-lab.md b/translations/es-XL/data/reusables/repositories/github-security-lab.md deleted file mode 100644 index b4dac7c01f..0000000000 --- a/translations/es-XL/data/reusables/repositories/github-security-lab.md +++ /dev/null @@ -1 +0,0 @@ -También puedes unirte a [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}) para buscar temas relacionados con seguridad y contribuir con las herramientas y proyectos de seguridad. diff --git a/translations/es-XL/data/reusables/repositories/include-administrators.md b/translations/es-XL/data/reusables/repositories/include-administrators.md deleted file mode 100644 index a6a2dc595e..0000000000 --- a/translations/es-XL/data/reusables/repositories/include-administrators.md +++ /dev/null @@ -1 +0,0 @@ -1. También puedes seleccionar **Incluir administradores**. Esto requiere todas las restricciones de seguridad para los administradores de repositorio. ![Casilla de verificación Incluir administradores](/assets/images/help/repository/include-admins-protected-branches.png) diff --git a/translations/es-XL/data/reusables/repositories/initialize-with-readme.md b/translations/es-XL/data/reusables/repositories/initialize-with-readme.md deleted file mode 100644 index 14150f67e0..0000000000 --- a/translations/es-XL/data/reusables/repositories/initialize-with-readme.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecciona **Inicializar este repositiro con un README**. ![Inicializar este repositorio con una casilla de verificación README](/assets/images/help/repository/initialize-with-readme.png) diff --git a/translations/es-XL/data/reusables/repositories/internal-repo-default.md b/translations/es-XL/data/reusables/repositories/internal-repo-default.md deleted file mode 100644 index 91e0c929e5..0000000000 --- a/translations/es-XL/data/reusables/repositories/internal-repo-default.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Los repositorios internos son la configuración predeterminada de todo repositorio nuevo que se cree en una organización que pertenezca a una empresa empresarial. -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/issue-template-config.md b/translations/es-XL/data/reusables/repositories/issue-template-config.md deleted file mode 100644 index 5d4af5128f..0000000000 --- a/translations/es-XL/data/reusables/repositories/issue-template-config.md +++ /dev/null @@ -1 +0,0 @@ -Puedes personalizar el selector de plantilla de informe de problemas que ven las personas cuando crean un nuevo informe de problemas en tu repositorio si añades un archivo *config.yml* a la carpeta `.github/ISSUE_TEMPLATE`. diff --git a/translations/es-XL/data/reusables/repositories/legacy-issue-template-tip.md b/translations/es-XL/data/reusables/repositories/legacy-issue-template-tip.md deleted file mode 100644 index cc31378d2c..0000000000 --- a/translations/es-XL/data/reusables/repositories/legacy-issue-template-tip.md +++ /dev/null @@ -1,6 +0,0 @@ - -{% warning %} - -Este es el flujo de trabajo tradicional para crear una plantilla de informe de problemas. Te recomendamos utilizar el creador múltiple de plantillas de informe de problemas mejorado para crear varias plantillas. Para obtener más información, consulta "[Acerca de las plantillas de propuestas y solicitudes de extracción](/articles/about-issue-and-pull-request-templates)". - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/repositories/list-closed-pull-requests.md b/translations/es-XL/data/reusables/repositories/list-closed-pull-requests.md deleted file mode 100644 index 488f1155b3..0000000000 --- a/translations/es-XL/data/reusables/repositories/list-closed-pull-requests.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Cerrado** para ver una lista de solicitudes de extracción cerradas. ![Pestaña de cerrado](/assets/images/help/branches/branches-closed.png) diff --git a/translations/es-XL/data/reusables/repositories/merge-all-pulls-together.md b/translations/es-XL/data/reusables/repositories/merge-all-pulls-together.md deleted file mode 100644 index 7834ade19e..0000000000 --- a/translations/es-XL/data/reusables/repositories/merge-all-pulls-together.md +++ /dev/null @@ -1 +0,0 @@ -No puedes fusionar solicitudes de fusión individuales en una bifurcación privada temporal. En vez de esto, fusionas todas las solicitudes de extracción al mismo tiempo en la asesoría de seguridad correspondiente. diff --git a/translations/es-XL/data/reusables/repositories/migrating-from-codeplex.md b/translations/es-XL/data/reusables/repositories/migrating-from-codeplex.md deleted file mode 100644 index 27ba5cb637..0000000000 --- a/translations/es-XL/data/reusables/repositories/migrating-from-codeplex.md +++ /dev/null @@ -1 +0,0 @@ -Si estás migrándo tu proyecto desde CodePlex, lee la [guía de migración](https://aka.ms/codeplex-guide) para obtener más información. diff --git a/translations/es-XL/data/reusables/repositories/navigate-to-branches.md b/translations/es-XL/data/reusables/repositories/navigate-to-branches.md deleted file mode 100644 index 43150a9ad0..0000000000 --- a/translations/es-XL/data/reusables/repositories/navigate-to-branches.md +++ /dev/null @@ -1 +0,0 @@ -1. Sobre la lista de archivos, da clic en {% octicon "git-branch" aria-label="The branch icon" %}**NUMBER branches**. ![Vínculo de ramas en página de resumen](/assets/images/help/branches/branches-link.png) diff --git a/translations/es-XL/data/reusables/repositories/navigate-to-job.md b/translations/es-XL/data/reusables/repositories/navigate-to-job.md deleted file mode 100644 index 754ba8b32a..0000000000 --- a/translations/es-XL/data/reusables/repositories/navigate-to-job.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en el job que quieres ver. ![Listado de jobs en la barra lateral izqueirda](/assets/images/help/repository/check-suite-list.png) diff --git a/translations/es-XL/data/reusables/repositories/navigate-to-manage-access.md b/translations/es-XL/data/reusables/repositories/navigate-to-manage-access.md deleted file mode 100644 index 969bd44c02..0000000000 --- a/translations/es-XL/data/reusables/repositories/navigate-to-manage-access.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Administrar acceso**. ![pestaña de "Administrar acceso"](/assets/images/help/repository/manage-access-tab.png) diff --git a/translations/es-XL/data/reusables/repositories/navigate-to-repo.md b/translations/es-XL/data/reusables/repositories/navigate-to-repo.md deleted file mode 100644 index b65b86f93e..0000000000 --- a/translations/es-XL/data/reusables/repositories/navigate-to-repo.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.product_name %}, visita la página principal del repositorio. diff --git a/translations/es-XL/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/es-XL/data/reusables/repositories/navigate-to-security-and-analysis.md deleted file mode 100644 index 9bf9d43bf1..0000000000 --- a/translations/es-XL/data/reusables/repositories/navigate-to-security-and-analysis.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![pestaña de "Seguridad & análisis" en la configuración de repositorio](/assets/images/help/repository/security-and-analysis-tab.png) diff --git a/translations/es-XL/data/reusables/repositories/navigate-to-workflow.md b/translations/es-XL/data/reusables/repositories/navigate-to-workflow.md deleted file mode 100644 index 3ce7bea39c..0000000000 --- a/translations/es-XL/data/reusables/repositories/navigate-to-workflow.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en el flujo de trabajo que quieres ver. ![Lista de flujos de trabajo en la barra lateral izquierda](/assets/images/help/repository/workflow-sidebar.png) diff --git a/translations/es-XL/data/reusables/repositories/new-pull-request.md b/translations/es-XL/data/reusables/repositories/new-pull-request.md deleted file mode 100644 index bdae0d2bda..0000000000 --- a/translations/es-XL/data/reusables/repositories/new-pull-request.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -1. A la derecha del menú de rama, da clic en **Nueva solicitud de extracción**. ![Enlace de "Solicitud de extracción" sobre la lsita de archivos](/assets/images/help/pull_requests/pull-request-start-review-button.png) -{% else %} -1. Above the list of files, click -{% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull request**. - ![Enlace de "Solicitud de extracción" sobre la lsita de archivos](/assets/images/help/pull_requests/pull-request-start-review-button.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/open-with-github-desktop.md b/translations/es-XL/data/reusables/repositories/open-with-github-desktop.md deleted file mode 100644 index 3ea98c3ead..0000000000 --- a/translations/es-XL/data/reusables/repositories/open-with-github-desktop.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} -1. Debajo del nombre del repositorio, haz clic en **Clone or download** (Clonar o descargar). ![Botón Clone or download (Clonar o descargar)](/assets/images/help/repository/clone-repo-clone-url-button.png) -1. Haz clic en **Open in Desktop** (Abrir en escritorio) para clonar el repositorio y abrirlo en {% data variables.product.prodname_desktop %}. ![Botón Open in Desktop (Abrir en escritorio)](/assets/images/help/desktop/open-in-desktop-button.png) -{% else %} -1. Sobre la lista de archivos, da clic en {% octicon "download" aria-label="The download icon" %} **Código**. ![Botón de "Código"](/assets/images/help/repository/code-button.png) -1. Click -{% octicon "desktop-download" aria-label="The GitHub Desktop download icon" %} **Open with {% data variables.product.prodname_desktop %}** to clone and open the repository with {% data variables.product.prodname_desktop %}. - ![Botón de "Abrir con {% data variables.product.prodname_desktop %}"](/assets/images/help/repository/open-with-desktop.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/owner-drop-down.md b/translations/es-XL/data/reusables/repositories/owner-drop-down.md deleted file mode 100644 index d7d89499dd..0000000000 --- a/translations/es-XL/data/reusables/repositories/owner-drop-down.md +++ /dev/null @@ -1 +0,0 @@ -1. Utiliza el menú desplegable de **Propietario** y selecciona la cuenta que quieres sea propietaria del repositorio. ![Menú desplegable Propietario](/assets/images/help/repository/create-repository-owner.png) diff --git a/translations/es-XL/data/reusables/repositories/permissions-statement-read.md b/translations/es-XL/data/reusables/repositories/permissions-statement-read.md deleted file mode 100644 index cdb65a75f1..0000000000 --- a/translations/es-XL/data/reusables/repositories/permissions-statement-read.md +++ /dev/null @@ -1 +0,0 @@ -Las personas con acceso de lectura en el repositorio pueden llevar a cabo estos pasos. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/repositories/permissions-statement-write.md b/translations/es-XL/data/reusables/repositories/permissions-statement-write.md deleted file mode 100644 index 2d49f69e03..0000000000 --- a/translations/es-XL/data/reusables/repositories/permissions-statement-write.md +++ /dev/null @@ -1 +0,0 @@ -Las personas con acceso de escritura en el repositorio pueden llevar a cabo estos pasos. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/repositories/pr-title-description.md b/translations/es-XL/data/reusables/repositories/pr-title-description.md deleted file mode 100644 index 718347844a..0000000000 --- a/translations/es-XL/data/reusables/repositories/pr-title-description.md +++ /dev/null @@ -1 +0,0 @@ -1. Escribe un título y una descripción para tu solicitud de extracción. ![Título y campos de descripción de la solicitud de extracción](/assets/images/help/pull_requests/pullrequest-description.png) diff --git a/translations/es-XL/data/reusables/repositories/private_forks_inherit_permissions.md b/translations/es-XL/data/reusables/repositories/private_forks_inherit_permissions.md deleted file mode 100644 index e3fa887008..0000000000 --- a/translations/es-XL/data/reusables/repositories/private_forks_inherit_permissions.md +++ /dev/null @@ -1 +0,0 @@ -Las bifurcaciones privadas heredan la estructura de permisos del repositorio ascendente o padre. Por ejemplo, si el repositorio ascendente es privado y otorga acceso de lectura/escritura a un equipo, entonces el mismo equipo tendrá este tipo de acceso en cualquier bifurcación de dicho repositorio ascendente. Esto ayuda a que los propietarios de repositorios privados mantengan el control sobre su código. diff --git a/translations/es-XL/data/reusables/repositories/protected-branches-block-web-edits-uploads.md b/translations/es-XL/data/reusables/repositories/protected-branches-block-web-edits-uploads.md deleted file mode 100644 index da4c12713a..0000000000 --- a/translations/es-XL/data/reusables/repositories/protected-branches-block-web-edits-uploads.md +++ /dev/null @@ -1,3 +0,0 @@ -Si un repositorio cuenta con alguna rama protegida, no podrás editar o cargar archivos en ésta utilizando {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta"[Acerca de las ramas protegidas](/articles/about-protected-branches)". - -Puedes utilizar {% data variables.product.prodname_desktop %} para mover tus cambios a una rama nueva y confirmarlos. Para obtener más información, consulta la sección "[Confirmar y revisar cambios hechos a tu proyecto](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)". diff --git a/translations/es-XL/data/reusables/repositories/protected-branches-options.md b/translations/es-XL/data/reusables/repositories/protected-branches-options.md deleted file mode 100644 index 8a0907dceb..0000000000 --- a/translations/es-XL/data/reusables/repositories/protected-branches-options.md +++ /dev/null @@ -1 +0,0 @@ -Puedes requerir automáticamente la configuración de rama protegida para algunas o todas las ramas de tu repositorio. Para obtener más información, consulta "[Configurar ramas protegidas](/github/administering-a-repository/configuring-protected-branches)". diff --git a/translations/es-XL/data/reusables/repositories/reaction_list.md b/translations/es-XL/data/reusables/repositories/reaction_list.md deleted file mode 100644 index 7851fb8b55..0000000000 --- a/translations/es-XL/data/reusables/repositories/reaction_list.md +++ /dev/null @@ -1,10 +0,0 @@ -| contenido | emoji | -| ------------ | ---------- | -| `+1` | :+1: | -| `-1` | :-1: | -| `risa` | :smile: | -| `confundido` | :confused: | -| `corazón` | :heart: | -| `viva` | :tada: | -| `cohete` | :rocket: | -| `ojos` | :eyes: | diff --git a/translations/es-XL/data/reusables/repositories/relative-links.md b/translations/es-XL/data/reusables/repositories/relative-links.md deleted file mode 100644 index 3b5392ae06..0000000000 --- a/translations/es-XL/data/reusables/repositories/relative-links.md +++ /dev/null @@ -1,11 +0,0 @@ -Puedes definir enlaces relativos y rutas de imagen en los archivos representados para ayudar a que los lectores naveguen hasta otros archivos de tu repositorio. - -Un enlace relativo es un enlace que es relativo al archivo actual. Por ejemplo, si tienes un archivo README en la raíz de tu repositorio y tienes otro archivo en _docs/CONTRIBUTING.md_, el enlace relativo a _CONTRIBUTING.md_ en tu archivo README podría verse así: - -``` -[Contribution guidelines for this project](docs/CONTRIBUTING.md) -``` - -{% data variables.product.product_name %} transformará de manera automática el enlace relativo o la ruta de imagen en cualquier rama en la que te encuentres actualmente, de modo que el enlace o ruta siempre funcione. Puedes usar todos los operandos del enlace relativo, como `./` y `../`. - -Los enlaces relativos son más sencillos para los usuarios que clonan tu repositorio. Puede que los enlaces absolutos no funcionen en los clones de tu repositorio. Recomendamos usar enlaces relativos para consultar los archivos dentro de tu repositorio. diff --git a/translations/es-XL/data/reusables/repositories/releases.md b/translations/es-XL/data/reusables/repositories/releases.md deleted file mode 100644 index 3cf4870552..0000000000 --- a/translations/es-XL/data/reusables/repositories/releases.md +++ /dev/null @@ -1,9 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.22" %} - -1. Debajo del nombre de tu repositorio, da clic en **Lanzamientos**. ![Pestaña de lanzamientos](/assets/images/help/releases/release-link.png) - -{% else %} - -1. A la derecha de la lista de archivos, da clic en **Releases** o **Latest release**. ![Sección de lanzamientos en la barra lateral de lado derecho](/assets/images/help/releases/release-link.png) - -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/repo-name.md b/translations/es-XL/data/reusables/repositories/repo-name.md deleted file mode 100644 index d293eb0f1d..0000000000 --- a/translations/es-XL/data/reusables/repositories/repo-name.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea el nombre de tu repositorio, y una descripción opcional. ![Crear un campo de repositorio](/assets/images/help/repository/create-repository-name.png) diff --git a/translations/es-XL/data/reusables/repositories/repo-size-limit.md b/translations/es-XL/data/reusables/repositories/repo-size-limit.md deleted file mode 100644 index c990aecee5..0000000000 --- a/translations/es-XL/data/reusables/repositories/repo-size-limit.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Los repositorios y archivos individuales están sujetos a límites de tamaño. Para obtener más información, consulta "[¿Cuál es mi cuota de disco?](/articles/what-is-my-disk-quota)" -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/reported-content-resolved-tab.md b/translations/es-XL/data/reusables/repositories/reported-content-resolved-tab.md deleted file mode 100644 index 972bab252f..0000000000 --- a/translations/es-XL/data/reusables/repositories/reported-content-resolved-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Reportes de abuso", da clic en **Resueltos**. ![Pestaña de "Resueltos" debajo de "Reportes de abuso"](/assets/images/help/repository/reported-content-resolved-tab.png) diff --git a/translations/es-XL/data/reusables/repositories/repository-branches.md b/translations/es-XL/data/reusables/repositories/repository-branches.md deleted file mode 100644 index 59a1ebb75b..0000000000 --- a/translations/es-XL/data/reusables/repositories/repository-branches.md +++ /dev/null @@ -1 +0,0 @@ -1. En el menú izquierdo, da clic en **Ramas**. ![Sub-menú de opciones de repositorio](/assets/images/help/repository/repository-options-branch.png) diff --git a/translations/es-XL/data/reusables/repositories/request-changes-tips.md b/translations/es-XL/data/reusables/repositories/request-changes-tips.md deleted file mode 100644 index b68d3eba20..0000000000 --- a/translations/es-XL/data/reusables/repositories/request-changes-tips.md +++ /dev/null @@ -1,9 +0,0 @@ -{% tip %} - -**Tips**: -- Si se habilita las revisiones requeridas y un colaborador con acceso de _write_, _admin_, u _owner_ emite una revisión solicitando cambios, la solicitud de extracción no se podrá fusionar hasta queel mismo colaborador emita otra revisión aprobando los cambios en dicha solicitud de extracción. -- Los propietarios y administradores del repositorio pueden fusionar una solicitud de extracción, incluso si no recibió una revisión de aprobación o si un revisor que solicitó modificaciones abandonó la organización o no está disponible. -- Si están habilitadas las revisiones requeridas y el descarte de una revisión en espera, y se sube una confirmación de modificación de código a la rama de una solicitud de extracción aprobada, se descarta la aprobación. La solicitud de extracción se debe volver a revisar y aprobar antes de que se pueda fusionar. -- Cuando varias solicitudes de extracción abiertas tienen una rama de encabezado que apunta a la misma confirmación, no podrás fusionarlas si una o ambas tienen una revisión pendiente o rechazada. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/es-XL/data/reusables/repositories/request-security-advisory-cve-id.md deleted file mode 100644 index 74c0f82b9a..0000000000 --- a/translations/es-XL/data/reusables/repositories/request-security-advisory-cve-id.md +++ /dev/null @@ -1 +0,0 @@ -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. diff --git a/translations/es-XL/data/reusables/repositories/required-status-merge-tip.md b/translations/es-XL/data/reusables/repositories/required-status-merge-tip.md deleted file mode 100644 index 10cd6847eb..0000000000 --- a/translations/es-XL/data/reusables/repositories/required-status-merge-tip.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Tip:** Para fusionar exitosamente una solicitud de extracción en una rama base que tiene habilitada la verificación de estado requerida, la rama de encabezado de la solicitud debe estar actualizada con la rama base. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/repositories/review-changes.md b/translations/es-XL/data/reusables/repositories/review-changes.md deleted file mode 100644 index aeeb7df617..0000000000 --- a/translations/es-XL/data/reusables/repositories/review-changes.md +++ /dev/null @@ -1 +0,0 @@ -1. Sobre el código que ha cambiado, da clic en **Revisar cambios**. ![Botón para revisar cambios](/assets/images/help/pull_requests/review-changes-button.png) diff --git a/translations/es-XL/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/es-XL/data/reusables/repositories/review-policy-overlapping-commits.md deleted file mode 100644 index 007a89eb98..0000000000 --- a/translations/es-XL/data/reusables/repositories/review-policy-overlapping-commits.md +++ /dev/null @@ -1 +0,0 @@ -Después de que todos los revisores requeridos han aprobado una solicitud de extracción, no podrás fusionarla si existen otras solicitudes con revisiones pendientes o rechazadas y dichas solicitudes tienen una rama de encabezado que apunte a la misma confirmación. Alguien con permisos de *escritura* o *administrador* necesitará aprobar o descartar la revisión que está bloqueando esto en las demás solicitudes de extracción antes de que puedas fusionarlas. diff --git a/translations/es-XL/data/reusables/repositories/review-pr-commits.md b/translations/es-XL/data/reusables/repositories/review-pr-commits.md deleted file mode 100644 index 6607d8bb9b..0000000000 --- a/translations/es-XL/data/reusables/repositories/review-pr-commits.md +++ /dev/null @@ -1 +0,0 @@ -1. En la solicitud de extracción, da clic en {% octicon "git-commit" aria-label="The commit icon" %}**Confirmaciones**. ![Pestaña de confirmaciones en una solicitud de extracción](/assets/images/help/pull_requests/pull-request-tabs-commits.png) diff --git a/translations/es-XL/data/reusables/repositories/review-summary-comment.md b/translations/es-XL/data/reusables/repositories/review-summary-comment.md deleted file mode 100644 index c1451d0eb2..0000000000 --- a/translations/es-XL/data/reusables/repositories/review-summary-comment.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea un comentario que resuma tu retroalimentación sobre los cambios propuestos. ![Ventana de comentarios para el resumen de la revisión](/assets/images/help/pull_requests/review-summary-comment-window.png) diff --git a/translations/es-XL/data/reusables/repositories/section-links.md b/translations/es-XL/data/reusables/repositories/section-links.md deleted file mode 100644 index 864b211c59..0000000000 --- a/translations/es-XL/data/reusables/repositories/section-links.md +++ /dev/null @@ -1,3 +0,0 @@ -Puedes vincular directamente a una sección en un archivo expedido si deslizas el puntero sobre el encabezado de la sección para exponer el enlace: - -![Enlace de sección con el archivo README para el repositorio de github/scientist](/assets/images/help/repository/readme-links.png) diff --git a/translations/es-XL/data/reusables/repositories/security-advisories-republishing.md b/translations/es-XL/data/reusables/repositories/security-advisories-republishing.md deleted file mode 100644 index a481c37252..0000000000 --- a/translations/es-XL/data/reusables/repositories/security-advisories-republishing.md +++ /dev/null @@ -1 +0,0 @@ -También puedes utilizar {% data variables.product.prodname_security_advisories %} para volver a publicar los detalles de una vulnerabilidad de seguridad que ya has divulgado en otro lugar si copias y pegas los detalles de la vulnerabilidad en una asesoría de seguridad nueva. diff --git a/translations/es-XL/data/reusables/repositories/security-advisory-admin-permissions.md b/translations/es-XL/data/reusables/repositories/security-advisory-admin-permissions.md deleted file mode 100644 index 0fe5180481..0000000000 --- a/translations/es-XL/data/reusables/repositories/security-advisory-admin-permissions.md +++ /dev/null @@ -1,3 +0,0 @@ -Cualquier usuario con permisos de administrador puede crear un aviso de seguridad. - -Cualquiera con permisos de administrador en un repositorio tendrá también permisos de administrador en todas las asesorías de seguridad del mismo. Las personas con permisos de administrador en una asesoría de seguridad pueden agregar colaboradores, y estos tendrán permisos de escritura en dicha asesoría. diff --git a/translations/es-XL/data/reusables/repositories/security-advisory-collaborators-public-repositories.md b/translations/es-XL/data/reusables/repositories/security-advisory-collaborators-public-repositories.md deleted file mode 100644 index 7802889f79..0000000000 --- a/translations/es-XL/data/reusables/repositories/security-advisory-collaborators-public-repositories.md +++ /dev/null @@ -1 +0,0 @@ -Si eliminas a un usuario de un repositorio u organización, y éste también es un colaborador en una asesoría de seguridad, dicho usuario aún tendrá acceso a esta asesoría. diff --git a/translations/es-XL/data/reusables/repositories/security-advisory-edit-description.md b/translations/es-XL/data/reusables/repositories/security-advisory-edit-description.md deleted file mode 100644 index d52cf5c151..0000000000 --- a/translations/es-XL/data/reusables/repositories/security-advisory-edit-description.md +++ /dev/null @@ -1 +0,0 @@ -1. Escribe una descripción de la vulnerabilidad de seguridad. ![Descripción de vulnerabilidad en la asesoría de seguridad](/assets/images/help/security/security-advisory-description.png) diff --git a/translations/es-XL/data/reusables/repositories/security-advisory-edit-details.md b/translations/es-XL/data/reusables/repositories/security-advisory-edit-details.md deleted file mode 100644 index 883a034ccd..0000000000 --- a/translations/es-XL/data/reusables/repositories/security-advisory-edit-details.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea los detalles de la vulnerabilidad de seguridad que está tratando la asesoría de seguridad. ![Metadatos de asesoría de seguridad](/assets/images/help/security/security-advisory-metadata.png) diff --git a/translations/es-XL/data/reusables/repositories/security-alert-delivery-options.md b/translations/es-XL/data/reusables/repositories/security-alert-delivery-options.md deleted file mode 100644 index 3d8103cf7a..0000000000 --- a/translations/es-XL/data/reusables/repositories/security-alert-delivery-options.md +++ /dev/null @@ -1 +0,0 @@ -Si tu repositorio tiene un manifiesto de dependencias compatible {% if currentVersion == "free-pro-team@latest" %} (y configuraste la gráfica de dependencias en caso de tratarse de un repositorio privado){% endif %}, cada que {% data variables.product.product_name %} detecte una dependencia vulnerable en tu repositorio, recibirás un correo semanal de resúmen. También puedes configurar tus alertas de seguridad y notificaciones web, notificaciones individuales por correo electrónico, resúmenes diarios por correo electrónico o alertas en la interfaz de {% data variables.product.product_name %}. 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)". diff --git a/translations/es-XL/data/reusables/repositories/security-alerts-x-github-severity.md b/translations/es-XL/data/reusables/repositories/security-alerts-x-github-severity.md deleted file mode 100644 index e07cc19c88..0000000000 --- a/translations/es-XL/data/reusables/repositories/security-alerts-x-github-severity.md +++ /dev/null @@ -1 +0,0 @@ -Las notificaciones de correo electrónico para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de seguridad{% endif %} que afecten a uno o más repositorios incluyen el campo de encabezado `X-GitHub-Severity`. Puedes utilizar el valor del campo de encabezado `X-GitHub-Severity` para filtrar las notificaciones de correo electrónico para {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot_alerts %}{% else %}alertas de seguridad{% endif %}. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/repositories/security-guidelines.md b/translations/es-XL/data/reusables/repositories/security-guidelines.md deleted file mode 100644 index cb47dfe5d2..0000000000 --- a/translations/es-XL/data/reusables/repositories/security-guidelines.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Puedes crear una política de seguridad para dar instrucciones a las personas para reportar las vulnerabilidades de seguridad de manera responsable en tu proyecto. Para obtener más información, consulta "[Aumentar la seguridad para tu repositorio](/articles/adding-a-security-policy-to-your-repository)". -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/select-items-in-issue-or-pr-list.md b/translations/es-XL/data/reusables/repositories/select-items-in-issue-or-pr-list.md deleted file mode 100644 index e0ef9b0d01..0000000000 --- a/translations/es-XL/data/reusables/repositories/select-items-in-issue-or-pr-list.md +++ /dev/null @@ -1 +0,0 @@ -3. Selecciona la casilla junto a los elementos a los que quieras aplicar la etiqueta. ![Casilla de verificación de metadatos de propuestas](/assets/images/help/issues/issues_assign_checkbox.png) diff --git a/translations/es-XL/data/reusables/repositories/select-marketplace-apps.md b/translations/es-XL/data/reusables/repositories/select-marketplace-apps.md deleted file mode 100644 index 7b6ab9f584..0000000000 --- a/translations/es-XL/data/reusables/repositories/select-marketplace-apps.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -1. Opcionalmente, si la cuenta personal o de organización que estás creando utiliza cualquier {% data variables.product.prodname_github_app %} de {% data variables.product.prodname_marketplace %}, selecciona cualquier app que quieras utilizar en el repositorio. ![Lista de las {% data variables.product.prodname_github_app %} de tu cuenta de {% data variables.product.prodname_marketplace %} y opción para dar acceso](/assets/images/help/repository/create-repository-choose-marketplace-apps.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/sensitive-info-warning.md b/translations/es-XL/data/reusables/repositories/sensitive-info-warning.md deleted file mode 100644 index 8f11eb71bc..0000000000 --- a/translations/es-XL/data/reusables/repositories/sensitive-info-warning.md +++ /dev/null @@ -1,14 +0,0 @@ -{% warning %} - -**Advertencia:** Si tratas con información sensible, nunca realices `git add`, `commit`, o `push` en un repositorio. La información sensible puede incluir, pero no se limita a: - -- Contraseñas -- SSH keys (Claves SSH) -- [Llaves de acceso AWS](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSGettingStartedGuide/AWSCredentials.html) -- Llaves API -- Números de tarjetas de crédito -- Números de NIP - -Para obtener más información, consulta "[Eliminar datos confidenciales de un repositorio](/articles/removing-sensitive-data-from-a-repository)". - -{% endwarning %} diff --git a/translations/es-XL/data/reusables/repositories/settings-sidebar-actions.md b/translations/es-XL/data/reusables/repositories/settings-sidebar-actions.md deleted file mode 100644 index 1a8897c829..0000000000 --- a/translations/es-XL/data/reusables/repositories/settings-sidebar-actions.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Acciones**. ![Configuración de acciones](/assets/images/help/settings/settings-sidebar-actions.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-advisories.md b/translations/es-XL/data/reusables/repositories/sidebar-advisories.md deleted file mode 100644 index 43ade4f435..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-advisories.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haga clic en **Security advisories (Avisos de seguridad)**. ![Pestaña de avisos de seguridad](/assets/images/help/security/advisories-tab.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/es-XL/data/reusables/repositories/sidebar-code-scanning-alerts.md deleted file mode 100644 index 133c7dd251..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-code-scanning-alerts.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **alertas de escaneo de código**. Opcionalmente, selecciona la herramienta de escaneo de código que utilizaste. ![pestaña de "Alertas de escaneo de código"](/assets/images/help/repository/sidebar-code-scanning-alerts.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/es-XL/data/reusables/repositories/sidebar-dependabot-alerts.md deleted file mode 100644 index c48ea3e064..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-dependabot-alerts.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de seguridad, da clic en **alertas del {% data variables.product.prodname_dependabot_short %}**. ![Pestaña de alertas del {% data variables.product.prodname_dependabot_short %}](/assets/images/help/repository/dependabot-alerts-tab.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/repositories/sidebar-issue-pr.md b/translations/es-XL/data/reusables/repositories/sidebar-issue-pr.md deleted file mode 100644 index ac1e240ced..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-issue-pr.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo del nombre de tu repositorio, da clic en {% octicon "issue-opened" aria-label="The issues icon" %}**Informes de problemas** o en {% octicon "git-pull-request" aria-label="The pull request icon" %}**Solicitudes de extracción**. ![Selección de la pestaña de propuestas y solicitudes de extracción](/assets/images/help/repository/repo-settings-issues-pull-requests.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-issues.md b/translations/es-XL/data/reusables/repositories/sidebar-issues.md deleted file mode 100644 index 29c90c2269..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-issues.md +++ /dev/null @@ -1 +0,0 @@ -2. Debajo del nombre de tu repositorio, da clic en {% octicon "issue-opened" aria-label="The issues icon" %}**Informe de problemas**. ![Pestaña de informe de problemas](/assets/images/help/repository/repo-tabs-issues.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-moderation-reported-content.md b/translations/es-XL/data/reusables/repositories/sidebar-moderation-reported-content.md deleted file mode 100644 index 9220abe3a7..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-moderation-reported-content.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Contenido reportado**. !["Contenido reportado" en la barra lateral de configuración del repositorio](/assets/images/help/repository/repo-settings-reported-content.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-notifications.md b/translations/es-XL/data/reusables/repositories/sidebar-notifications.md deleted file mode 100644 index 8634453272..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-notifications.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Notificaciones**. ![Botón de notificaciones en la barra lateral](/assets/images/help/settings/notifications_menu.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-pr.md b/translations/es-XL/data/reusables/repositories/sidebar-pr.md deleted file mode 100644 index acf69601ea..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-pr.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo del nombre de tu repositorio, da clic en {% octicon "git-pull-request" aria-label="The pull request icon" %}**Solicitudes de extracción**. ![Selección de la pestaña de propuestas y solicitudes de extracción](/assets/images/help/repository/repo-tabs-pull-requests.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-security.md b/translations/es-XL/data/reusables/repositories/sidebar-security.md deleted file mode 100644 index 08919b826c..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-security.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de tu nombre de repositorio, da clic en **{% octicon "shield" aria-label="The shield symbol" %} Seguridad**. ![Pestaña de seguridad](/assets/images/help/repository/security-tab.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-settings.md b/translations/es-XL/data/reusables/repositories/sidebar-settings.md deleted file mode 100644 index b0e17a8591..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-settings.md +++ /dev/null @@ -1 +0,0 @@ -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/repository/repo-actions-settings.png) diff --git a/translations/es-XL/data/reusables/repositories/sidebar-wiki.md b/translations/es-XL/data/reusables/repositories/sidebar-wiki.md deleted file mode 100644 index 0e89e0e51c..0000000000 --- a/translations/es-XL/data/reusables/repositories/sidebar-wiki.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de tu nombre de repositorio, da clic en {% octicon "book" aria-label="Book symbol" %}**Wiki**. ![Enlace de menú del Wiki](/assets/images/help/wiki/wiki_menu_link.png) diff --git a/translations/es-XL/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/es-XL/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md deleted file mode 100644 index 0ef6d1e3d0..0000000000 --- a/translations/es-XL/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} Si existe una regla de rama protegida en tu repositorio que requiera un historial de confirmaciones linear, debes permitir la fusión por combinación, por rebase, o ambas. Para obtener más información, consulta "[Requerir un historial de confirmaciones linear](/github/administering-a-repository/requiring-a-linear-commit-history)."{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/start-line-comment.md b/translations/es-XL/data/reusables/repositories/start-line-comment.md deleted file mode 100644 index a21d885657..0000000000 --- a/translations/es-XL/data/reusables/repositories/start-line-comment.md +++ /dev/null @@ -1 +0,0 @@ -1. Pasa el puntero sobre la línea de código en la que deseas agregar un comentario y da clic en el icono de comentario azul. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} Para agregar un comentario en líneas múltiples, da clic y arrastra para seleccionar el rango de líneas, luego da clic en el icono de comentario azul.{% endif %} ![Icono de comentario azul](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/es-XL/data/reusables/repositories/submit-new-issue.md b/translations/es-XL/data/reusables/repositories/submit-new-issue.md deleted file mode 100644 index 99d68f14de..0000000000 --- a/translations/es-XL/data/reusables/repositories/submit-new-issue.md +++ /dev/null @@ -1 +0,0 @@ -1. Cuando termines, da clic en **Emitir nuevo informe de problemas**. diff --git a/translations/es-XL/data/reusables/repositories/submit-review.md b/translations/es-XL/data/reusables/repositories/submit-review.md deleted file mode 100644 index e079e1d77f..0000000000 --- a/translations/es-XL/data/reusables/repositories/submit-review.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Emitir revisión**. diff --git a/translations/es-XL/data/reusables/repositories/suggest-changes.md b/translations/es-XL/data/reusables/repositories/suggest-changes.md deleted file mode 100644 index 8407150b17..0000000000 --- a/translations/es-XL/data/reusables/repositories/suggest-changes.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, para sugerir un cambio específico a la línea {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} o líneas{% endif %},da clic en{% octicon "diff" aria-label="The diff symbol" %}, luego edita el texto dentro del bloque de sugerencia. ![Bloque de sugerencia](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/es-XL/data/reusables/repositories/task-list-markdown.md b/translations/es-XL/data/reusables/repositories/task-list-markdown.md deleted file mode 100644 index afb04a5bb2..0000000000 --- a/translations/es-XL/data/reusables/repositories/task-list-markdown.md +++ /dev/null @@ -1,9 +0,0 @@ -Para crear una lista de tareas, introduce los elementos de la lista con un caracter de espacio regular, seguido de `[ ]`. Para marcar una tarea como completada, utiliza `[x]`. - -``` -- [x] Finish my changes -- [ ] Push my commits to GitHub -- [ ] Open a pull request -``` - -![Lista de tareas generada](/assets/images/help/writing/task-list-rendered.png) diff --git a/translations/es-XL/data/reusables/repositories/tracks-vulnerabilities.md b/translations/es-XL/data/reusables/repositories/tracks-vulnerabilities.md deleted file mode 100644 index ec05e1f893..0000000000 --- a/translations/es-XL/data/reusables/repositories/tracks-vulnerabilities.md +++ /dev/null @@ -1,6 +0,0 @@ -Agregamos vulnerabilidades a la {% data variables.product.prodname_advisory_database %} desde las siguientes fuentes: -- La [National Vulnerability Database](https://nvd.nist.gov/) -- Una combinación de aprendizaje automático y revisión humana para detectar vulnerabilidades en confirmaciones públicas en {% data variables.product.prodname_dotcom %} -- Asesorías de seguridad que se reportan en {% data variables.product.prodname_dotcom %} -- The [npm Security advisories](https://www.npmjs.com/advisories) database -- [FriendsOfPHP](https://github.com/FriendsOfPHP/security-advisories) diff --git a/translations/es-XL/data/reusables/repositories/transfer-repository-steps.md b/translations/es-XL/data/reusables/repositories/transfer-repository-steps.md deleted file mode 100644 index 247f96eac1..0000000000 --- a/translations/es-XL/data/reusables/repositories/transfer-repository-steps.md +++ /dev/null @@ -1,10 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -1. En "Danger Zone" (Zona de peligro), haz clic en **Transfer** (Transferir). ![Botón Transfer (Transferir)](/assets/images/help/repository/repo-transfer.png) -1. Lee la información acerca de transferir un repositorio, luego escribe el nombre del usuario u organización al que le quieres transferir la titularidad del repositorio. ![Información acerca de la transferencia del repositorio y campo para escribir el nombre de usuario del propietario nuevo](/assets/images/help/repository/transfer-repo-new-owner-name.png) -1. Lee las advertencias acerca de la posible pérdida de características en función de la suscripción del propietario nuevo. ![Advertencias acerca de la transferencia de un repositorio a una persona que usa un producto gratuito](/assets/images/help/repository/repo-transfer-free-plan-warnings.png) -1. Escribe el nombre del repositorio que quieres transferir, luego haz clic en **I understand, transfer this repository** (Comprendo, transferir este repositorio). ![Botón Transfer (Transferir)](/assets/images/help/repository/repo-transfer-complete.png) -{% else %} -1. Click **Transfer**. ![Botón Transfer (Transferir)](/assets/images/help/repository/repo-transfer.png) -1. Lee las advertencias e ingresa el nombre del repositorio para confirmar que lo has hecho. -1. Escribe el nombre del propietario nuevo y haz clic en **I understand, transfer this repo** (Comprendo, trasferir este repositorio). ![Botón Transfer (Transferir)](/assets/images/help/repository/repo-transfer-complete.png) -{% endif %} diff --git a/translations/es-XL/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/es-XL/data/reusables/repositories/two-dot-diff-comparison-example-urls.md deleted file mode 100644 index 0394611c38..0000000000 --- a/translations/es-XL/data/reusables/repositories/two-dot-diff-comparison-example-urls.md +++ /dev/null @@ -1 +0,0 @@ -Por ejemplo, esta URL utiliza los códigos acortados de siete caracteres de SHA para comparar las confirmaciones `c3a414e` y `faf7c6f`: `https://github.com/github/linguist/compare/c3a414e..faf7c6f.` diff --git a/translations/es-XL/data/reusables/repositories/type-issue-title-and-description.md b/translations/es-XL/data/reusables/repositories/type-issue-title-and-description.md deleted file mode 100644 index 20ae5bf366..0000000000 --- a/translations/es-XL/data/reusables/repositories/type-issue-title-and-description.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea un título y descripción para tu informe de problemas. ![Un ejemplo de informe de problemas](/assets/images/help/issues/sample_issue.png) diff --git a/translations/es-XL/data/reusables/repositories/type-line-comment.md b/translations/es-XL/data/reusables/repositories/type-line-comment.md deleted file mode 100644 index 026672f6e5..0000000000 --- a/translations/es-XL/data/reusables/repositories/type-line-comment.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea tu comentario en el campo de comentario. ![Campo de comentario](/assets/images/help/pull_requests/comment-field.png) diff --git a/translations/es-XL/data/reusables/repositories/valid-community-issues.md b/translations/es-XL/data/reusables/repositories/valid-community-issues.md deleted file mode 100644 index 6363c3a421..0000000000 --- a/translations/es-XL/data/reusables/repositories/valid-community-issues.md +++ /dev/null @@ -1 +0,0 @@ -Para que se incluyan en el listado de perfiles de la comunidad, las plantillas de informe de problemas deben ubicarse en la carpeta `.github/ISSUE_TEMPLATE` y contener campos de `name:` y `about:` de YAML front matter válidos. diff --git a/translations/es-XL/data/reusables/repositories/view-run.md b/translations/es-XL/data/reusables/repositories/view-run.md deleted file mode 100644 index 1b3218434e..0000000000 --- a/translations/es-XL/data/reusables/repositories/view-run.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Ejecuciones de flujo de trabajo", da clic en el nombre de la ejecución que quieres ver. ![Nombre de la ejecución de flujo de trabajo](/assets/images/help/repository/run-name.png) diff --git a/translations/es-XL/data/reusables/repositories/workflow-notifications.md b/translations/es-XL/data/reusables/repositories/workflow-notifications.md deleted file mode 100644 index 223301c2fb..0000000000 --- a/translations/es-XL/data/reusables/repositories/workflow-notifications.md +++ /dev/null @@ -1,3 +0,0 @@ -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. - -También puedes ver el estado de las ejecuciones de flujo de trabajo en la pestaña Actions (Acciones) de un repositorio. 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)". diff --git a/translations/es-XL/data/reusables/repositories/you-can-fork.md b/translations/es-XL/data/reusables/repositories/you-can-fork.md deleted file mode 100644 index 2d290ce6cd..0000000000 --- a/translations/es-XL/data/reusables/repositories/you-can-fork.md +++ /dev/null @@ -1,3 +0,0 @@ -You can fork any public repository to your user account or any organization where you have repository creation permissions. For more information, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization)." - -You can fork any private repository you can access to your user account and any organization on {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} where you have repository creation permissions. You cannot fork a private repository to an organization using {% data variables.product.prodname_free_team %}.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[GitHub's products](/articles/githubs-products)."{% endif %} diff --git a/translations/es-XL/data/reusables/saml/about-authorized-credentials.md b/translations/es-XL/data/reusables/saml/about-authorized-credentials.md deleted file mode 100644 index a50d20815e..0000000000 --- a/translations/es-XL/data/reusables/saml/about-authorized-credentials.md +++ /dev/null @@ -1 +0,0 @@ -Puedes ver cada token de acceso personal y llave de SSH que se haya autorizado a un miembro para obtener acceso a la API y a Git. Sólo se pueden ver los últimos caracteres de cada token o llave. De ser necesario, trabaja en conjunto con el miembro para determinar qué credenciales deberías revocar. diff --git a/translations/es-XL/data/reusables/saml/about-linked-identities.md b/translations/es-XL/data/reusables/saml/about-linked-identities.md deleted file mode 100644 index af16354569..0000000000 --- a/translations/es-XL/data/reusables/saml/about-linked-identities.md +++ /dev/null @@ -1,3 +0,0 @@ -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](/github/setting-up-and-managing-organizations-and-teams/about-scim)". - -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-XL/data/reusables/saml/about-saml-access-enterprise-account.md b/translations/es-XL/data/reusables/saml/about-saml-access-enterprise-account.md deleted file mode 100644 index ebaf2e8eb6..0000000000 --- a/translations/es-XL/data/reusables/saml/about-saml-access-enterprise-account.md +++ /dev/null @@ -1 +0,0 @@ -Para acceder a los recursos de cada organización en {% data variables.product.product_name %}, el miembro debe tener una sesión activa de SAML en su buscador. Para acceder a los recursos protegidos de cada organización utilizando la API y Git, el miembro debe tener un token de acceso personal o llave de SSH que se le haya autorizado para su uso con la organización. Los propietarios de la empresa pueden ver y revocar la identidad vinculada de un miembro, las sesiones activas, o las credenciales autorizadas en cualquier momento. diff --git a/translations/es-XL/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/es-XL/data/reusables/saml/about-user-provisioning-enterprise-account.md deleted file mode 100644 index ba92edc2a7..0000000000 --- a/translations/es-XL/data/reusables/saml/about-user-provisioning-enterprise-account.md +++ /dev/null @@ -1 +0,0 @@ -Si utilizas a Okta como tu IdP, puedes utilizar SCIM para adminsitrar la membrecía de tu organización en tu cuenta empresarial. SCIM invita a las personas o las elimina de una organización en tu cuenta empresarial automáticamente con base en si son miembros del grupo que corresponde a cada organización en tu IdP o no. diff --git a/translations/es-XL/data/reusables/saml/add-okta-application.md b/translations/es-XL/data/reusables/saml/add-okta-application.md deleted file mode 100644 index a85908b4cb..0000000000 --- a/translations/es-XL/data/reusables/saml/add-okta-application.md +++ /dev/null @@ -1 +0,0 @@ -2. Da clic en **Agregar aplicación**. ![Botón de "Agregar aplicación" en la pestaña de Aplicaciones del tablero de Okta](/assets/images/help/saml/okta-add-application.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/assign-yourself-to-okta.md b/translations/es-XL/data/reusables/saml/assign-yourself-to-okta.md deleted file mode 100644 index b35823ca4e..0000000000 --- a/translations/es-XL/data/reusables/saml/assign-yourself-to-okta.md +++ /dev/null @@ -1 +0,0 @@ -1. Asigna la aplicación a tu usuario en Okta. Para obtener más información, consulta la sección [Asignar aplicaciones a los usuarios](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm) en la documentación de Okta. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/click-enterprise-account-application.md b/translations/es-XL/data/reusables/saml/click-enterprise-account-application.md deleted file mode 100644 index 7a5ffbfa99..0000000000 --- a/translations/es-XL/data/reusables/saml/click-enterprise-account-application.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en la etiqueta de la aplicación que creaste para tu cuenta empresarial. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/click-person-revoke-credentials.md b/translations/es-XL/data/reusables/saml/click-person-revoke-credentials.md deleted file mode 100644 index 2dc2102774..0000000000 --- a/translations/es-XL/data/reusables/saml/click-person-revoke-credentials.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en el nombre del miembro cuyas credenciales autorizadas quisieras ver o revocar. diff --git a/translations/es-XL/data/reusables/saml/click-person-revoke-identity.md b/translations/es-XL/data/reusables/saml/click-person-revoke-identity.md deleted file mode 100644 index 3ffa3edfa3..0000000000 --- a/translations/es-XL/data/reusables/saml/click-person-revoke-identity.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en el nombre del miembro cuya identidad vinculada quisieras ver o revocar. diff --git a/translations/es-XL/data/reusables/saml/click-person-revoke-session.md b/translations/es-XL/data/reusables/saml/click-person-revoke-session.md deleted file mode 100644 index 2e07596954..0000000000 --- a/translations/es-XL/data/reusables/saml/click-person-revoke-session.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en el nombre del miembro cuya sesión de SAML quisieras ver o revocar. diff --git a/translations/es-XL/data/reusables/saml/confirm-revoke-credentials.md b/translations/es-XL/data/reusables/saml/confirm-revoke-credentials.md deleted file mode 100644 index 4e3ee61f68..0000000000 --- a/translations/es-XL/data/reusables/saml/confirm-revoke-credentials.md +++ /dev/null @@ -1 +0,0 @@ -1. Lee la información, posteriormente, da clic en **Entiendo, revocar el acceso para este token**. diff --git a/translations/es-XL/data/reusables/saml/confirm-revoke-identity.md b/translations/es-XL/data/reusables/saml/confirm-revoke-identity.md deleted file mode 100644 index e5f8bb13d3..0000000000 --- a/translations/es-XL/data/reusables/saml/confirm-revoke-identity.md +++ /dev/null @@ -1 +0,0 @@ -1. Lee la información y da clic en **Revocar identidad externa**. diff --git a/translations/es-XL/data/reusables/saml/dotcom-saml-explanation.md b/translations/es-XL/data/reusables/saml/dotcom-saml-explanation.md deleted file mode 100644 index a187261d39..0000000000 --- a/translations/es-XL/data/reusables/saml/dotcom-saml-explanation.md +++ /dev/null @@ -1 +0,0 @@ -El SSO de SAML proporciona a los propietarios de organizaciones y empresas en {% data variables.product.prodname_dotcom %} una manera de controlar y asegurar el acceso a los recursos organizacionales como repositorios, informes de problemas y solicitudes de extracción. diff --git a/translations/es-XL/data/reusables/saml/okta-admin-button.md b/translations/es-XL/data/reusables/saml/okta-admin-button.md deleted file mode 100644 index 389d548a29..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-admin-button.md +++ /dev/null @@ -1 +0,0 @@ -1. En Okta, en la esquina superior derecha, da clic en **Admin**. ![Botón de Admin en Okta](/assets/images/help/saml/okta-admin-button.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/okta-applications-click-ghec-application-label.md b/translations/es-XL/data/reusables/saml/okta-applications-click-ghec-application-label.md deleted file mode 100644 index 6da8596cfa..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-applications-click-ghec-application-label.md +++ /dev/null @@ -1 +0,0 @@ -1. En la lista de aplicaciones, da clic en la etiqueta para la aplicación que creaste para la organización que utiliza {% data variables.product.prodname_ghe_cloud %}. ![Aplicación de {% data variables.product.prodname_ghe_cloud %} en Okta](/assets/images/help/saml/okta-ghec-application.png) diff --git a/translations/es-XL/data/reusables/saml/okta-configure-api-integration.md b/translations/es-XL/data/reusables/saml/okta-configure-api-integration.md deleted file mode 100644 index 529e9a78f7..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-configure-api-integration.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Configurar la integraciòn de la API**. ![Botón "Configurar Integración de API" para la aplicación de Okta](/assets/images/help/saml/okta-configure-api-integration.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/okta-dashboard-click-applications.md b/translations/es-XL/data/reusables/saml/okta-dashboard-click-applications.md deleted file mode 100644 index b5c901f3ce..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-dashboard-click-applications.md +++ /dev/null @@ -1 +0,0 @@ -1. En el tablero de Okta, da clic en **Aplicaciones**. ![Elemento "Aplicaciones" en la barra de navegación del tablero de Okta](/assets/images/help/saml/okta-applications.png) diff --git a/translations/es-XL/data/reusables/saml/okta-edit-provisioning.md b/translations/es-XL/data/reusables/saml/okta-edit-provisioning.md deleted file mode 100644 index 7ee0de69d7..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-edit-provisioning.md +++ /dev/null @@ -1,5 +0,0 @@ -10. A la derecha de "Aprovisionar a la App", da clic en **Editar**. ![Botón "Editar" para las opciones de aprovisionamiento de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-to-app-edit-button.png) -11. A la derecha de "Crear Usuarios", selecciona **Habilitar**. ![Casilla "Habilitar" para la opción de "Crear Usuarios" de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-enable-create-users.png) -12. A la derecha de "Actualizar Atributos de Usuario", selecciona **Habilitar**. ![Casilla "Habilitar" para la opción de "Actualizar Atributos de Usuario" de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-enable-update-user-attributes.png) -13. A la derecha de "Desactivar Usuarios", selecciona **Habilitar**. ![Casilla "Habilitar" para la opción de "Desactivar Usuarios" de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-enable-deactivate-users.png) -14. Haz clic en **Save (Guardar)**. ![Botón "Guardar" ára la configuración de aprovisionamiento de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-save.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/okta-enable-api-integration.md b/translations/es-XL/data/reusables/saml/okta-enable-api-integration.md deleted file mode 100644 index df060b1dce..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-enable-api-integration.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecciona **Habilitar la Integraciòn de la API**. ![Casilla "Habilitar la integración de la API" para la aplicación de Okta](/assets/images/help/saml/okta-enable-api-integration.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/okta-provisioning-tab.md b/translations/es-XL/data/reusables/saml/okta-provisioning-tab.md deleted file mode 100644 index 4dfddbd37a..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-provisioning-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo del nombre de la aplicación, da clic en **Aprovisionamiento**. ![Pestaña de "Aprovisionar" para la aplicación de Okta](/assets/images/help/saml/okta-provisioning-tab.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/okta-save-provisioning.md b/translations/es-XL/data/reusables/saml/okta-save-provisioning.md deleted file mode 100644 index a41287ac26..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-save-provisioning.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Save (Guardar)**. ![Botón "Guardar" ára la configuración de aprovisionamiento de la aplicación de Okta](/assets/images/help/saml/okta-provisioning-tab-save.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/okta-sign-on-tab.md b/translations/es-XL/data/reusables/saml/okta-sign-on-tab.md deleted file mode 100644 index 8d42ca1648..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-sign-on-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo del nombre de la aplicación, da clic en **Iniciar sesión**. ![Pestaña "Registrarse" para la aplicación de Okta](/assets/images/help/saml/okta-sign-on-tab.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/okta-view-setup-instructions.md b/translations/es-XL/data/reusables/saml/okta-view-setup-instructions.md deleted file mode 100644 index 2d44879c1c..0000000000 --- a/translations/es-XL/data/reusables/saml/okta-view-setup-instructions.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "MÉTODOS DE REGISTRO", da clic en **Ver las instrucciones de configuración". ![Botón de "Ver instrucciones de configuración" en la pestaña "Registrarse" de la aplicación de Okta](/assets/images/help/saml/okta-view-setup-instructions.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/outside-collaborators-exemption.md b/translations/es-XL/data/reusables/saml/outside-collaborators-exemption.md deleted file mode 100644 index a464f145b6..0000000000 --- a/translations/es-XL/data/reusables/saml/outside-collaborators-exemption.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** No se requiere que los colaboradores externos se autentiquen con un IdP para acceder a los recursos de una organización que cuente con el SSO de SAML. Para obtener más información sobre los colaboradores externos, consulta la sección "[Niveles de permiso para una organización](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#outside-collaborators)". - -{% endnote %} diff --git a/translations/es-XL/data/reusables/saml/revoke-authorized-credentials.md b/translations/es-XL/data/reusables/saml/revoke-authorized-credentials.md deleted file mode 100644 index e7a118ae40..0000000000 --- a/translations/es-XL/data/reusables/saml/revoke-authorized-credentials.md +++ /dev/null @@ -1 +0,0 @@ -1. Para revocar las credenciales, a la derecha de aquellas que quieras revocar, da clic en **Revocar**. ![Botón revocar](/assets/images/help/saml/revoke-credentials.png) diff --git a/translations/es-XL/data/reusables/saml/revoke-saml-session.md b/translations/es-XL/data/reusables/saml/revoke-saml-session.md deleted file mode 100644 index 3f755d3088..0000000000 --- a/translations/es-XL/data/reusables/saml/revoke-saml-session.md +++ /dev/null @@ -1 +0,0 @@ -1. Para revocar una sesión, a la derecha de aquella que quieras revocar, da clic en **Revocar**. ![Botón revocar](/assets/images/help/saml/revoke-session.png) diff --git a/translations/es-XL/data/reusables/saml/revoke-sso-identity.md b/translations/es-XL/data/reusables/saml/revoke-sso-identity.md deleted file mode 100644 index a4e367ac64..0000000000 --- a/translations/es-XL/data/reusables/saml/revoke-sso-identity.md +++ /dev/null @@ -1 +0,0 @@ -1. Para revocar la identidad vinculada, da clic en **Revocar** a la derecha de ésta. ![Botón revocar](/assets/images/help/saml/revoke-identity.png) diff --git a/translations/es-XL/data/reusables/saml/saml-identity-linked.md b/translations/es-XL/data/reusables/saml/saml-identity-linked.md deleted file mode 100644 index 0dab669030..0000000000 --- a/translations/es-XL/data/reusables/saml/saml-identity-linked.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Identidad de SAML vinculada**. ![Identidad vinculada de SAML](/assets/images/help/saml/saml-identity-linked.png) diff --git a/translations/es-XL/data/reusables/saml/saml-session-oauth.md b/translations/es-XL/data/reusables/saml/saml-session-oauth.md deleted file mode 100644 index edfd3436b4..0000000000 --- a/translations/es-XL/data/reusables/saml/saml-session-oauth.md +++ /dev/null @@ -1 +0,0 @@ -Si perteneces a cualquier organización que requiera el inicio de sesión único de SAML, puede que se te pida autenticarte a través de tu proveedor de identidad antes de que se te autorice un {% data variables.product.prodname_oauth_app %}. Para obtener más información acerca de SAML, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". diff --git a/translations/es-XL/data/reusables/saml/saml-single-logout-not-supported.md b/translations/es-XL/data/reusables/saml/saml-single-logout-not-supported.md deleted file mode 100644 index a54a71e0ce..0000000000 --- a/translations/es-XL/data/reusables/saml/saml-single-logout-not-supported.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.product_name %} no es compatible con el cierre de sesión único de SAML. Para terminar una sesión de SAML activa, los usuarios deben salir directamente en tu IdP de SAML. diff --git a/translations/es-XL/data/reusables/saml/saml-supported-idps.md b/translations/es-XL/data/reusables/saml/saml-supported-idps.md deleted file mode 100644 index c418507661..0000000000 --- a/translations/es-XL/data/reusables/saml/saml-supported-idps.md +++ /dev/null @@ -1,7 +0,0 @@ -Ofrecemos soporte limitado para todos los proveedores de identidad que implementan SAML 2.0 estándar. Ofrecemos soporte oficial de estos proveedores de identidad que se han probado internamente: -- Active Directory Federation Services (AD FS) -- Azure Active Directory (Azure AD) -- Okta -- OneLogin -- PingOne -- Shibboleth diff --git a/translations/es-XL/data/reusables/saml/search-ghec-okta.md b/translations/es-XL/data/reusables/saml/search-ghec-okta.md deleted file mode 100644 index df3227b020..0000000000 --- a/translations/es-XL/data/reusables/saml/search-ghec-okta.md +++ /dev/null @@ -1 +0,0 @@ -3. En el campo de búsqueda, teclea "GitHub Enterprise Cloud".![Campo "Buscar una aplicación" de Okta](/assets/images/help/saml/okta-search-for-an-application.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/testing-saml-sso.md b/translations/es-XL/data/reusables/saml/testing-saml-sso.md deleted file mode 100644 index cc17493314..0000000000 --- a/translations/es-XL/data/reusables/saml/testing-saml-sso.md +++ /dev/null @@ -1 +0,0 @@ -Cuando configuras el SSO de SAML en tu organización, puedes probar tu implementación sin que afecte a los miembros de tu organización cuando dejas sin marcar la opción **Requerir la autenticación con el SSO de SAML para todos los miembros de la organización _nombre de organización_**. diff --git a/translations/es-XL/data/reusables/saml/use-classic-ui.md b/translations/es-XL/data/reusables/saml/use-classic-ui.md deleted file mode 100644 index aa440f2101..0000000000 --- a/translations/es-XL/data/reusables/saml/use-classic-ui.md +++ /dev/null @@ -1,3 +0,0 @@ -Debes utilizar la "IU Clásica" en Okta. Para obtener más información, consulta la sección [Organized Navigation](https://developer.okta.com/blog/2017/09/25/all-new-developer-console#new-look--feel) en el blog de Okta. - -![Seleccionar "IU Clásica" en el selector de estilos de UI de Okta sobre el tablero](/assets/images/help/saml/okta-classic-ui.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/saml/view-authorized-credentials.md b/translations/es-XL/data/reusables/saml/view-authorized-credentials.md deleted file mode 100644 index ad4f78f8c0..0000000000 --- a/translations/es-XL/data/reusables/saml/view-authorized-credentials.md +++ /dev/null @@ -1 +0,0 @@ -1. Visualiza las credenciales autorizadas para el miembro debajo de "Credenciales autorizadas". diff --git a/translations/es-XL/data/reusables/saml/view-saml-sessions.md b/translations/es-XL/data/reusables/saml/view-saml-sessions.md deleted file mode 100644 index 97bca6424f..0000000000 --- a/translations/es-XL/data/reusables/saml/view-saml-sessions.md +++ /dev/null @@ -1 +0,0 @@ -1. Visualiza las sesiones activas de SAML para el miembro debajo de "Sesiones de SAML activas". diff --git a/translations/es-XL/data/reusables/saml/view-sso-identity.md b/translations/es-XL/data/reusables/saml/view-sso-identity.md deleted file mode 100644 index 7f79c9d0cb..0000000000 --- a/translations/es-XL/data/reusables/saml/view-sso-identity.md +++ /dev/null @@ -1 +0,0 @@ -1. Visualiza la identidad de SSO vinculada para el miembro debajo de "Identidad de SSO vinculada". diff --git a/translations/es-XL/data/reusables/scim/enterprise-account-scim.md b/translations/es-XL/data/reusables/scim/enterprise-account-scim.md deleted file mode 100644 index e71fd9587e..0000000000 --- a/translations/es-XL/data/reusables/scim/enterprise-account-scim.md +++ /dev/null @@ -1 +0,0 @@ -Si estás participando en el beta privado para el aprovisionamiento de usuario para cuentas empresariales, cuando habilites SAML para tu cuenta empresarial, se habilitará predeterminadamente el aprovisionamiento y desaprovisionamiento de SCIM en {% data variables.product.product_name %}. Puedes utilizar el aprovisionamiento para administrar la membrecía de la organización si configuras SCIM en tu IdP. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/search/date_gt_lt.md b/translations/es-XL/data/reusables/search/date_gt_lt.md deleted file mode 100644 index 948d4455e5..0000000000 --- a/translations/es-XL/data/reusables/search/date_gt_lt.md +++ /dev/null @@ -1 +0,0 @@ -Las fechas son compatibles con [calificadores de mayor qué, menor qué y rango](/articles/understanding-the-search-syntax). diff --git a/translations/es-XL/data/reusables/search/requested_reviews_search.md b/translations/es-XL/data/reusables/search/requested_reviews_search.md deleted file mode 100644 index e90c48dde3..0000000000 --- a/translations/es-XL/data/reusables/search/requested_reviews_search.md +++ /dev/null @@ -1 +0,0 @@ -Puedes encontrar una solicitud de extracción en donde se te haya solicitado una revisión, ya sea a ti o a algún equipo del que seas miembro, con el calificador de búsqueda `review-requested:[USERNAME]` o `team-review-requested:[TEAMNAME]`. Para obtener más información, consulta la sección "[Buscar informes de problemas y solicitudes de extracción](/articles/searching-issues-and-pull-requests)". diff --git a/translations/es-XL/data/reusables/search/requested_reviews_search_tip.md b/translations/es-XL/data/reusables/search/requested_reviews_search_tip.md deleted file mode 100644 index 4332eb09a3..0000000000 --- a/translations/es-XL/data/reusables/search/requested_reviews_search_tip.md +++ /dev/null @@ -1,5 +0,0 @@ -{% tip %} - -**Tip:** Puedes encontrar una solicitud de extracción en donde se te haya solicitado una revisión, ya sea a ti o a algún equipo del que seas miembro, con el calificador de búsqueda `review-requested:[USERNAME]` o `team-review-requested:[TEAMNAME]`. Para obtener más información, consulta la sección "[Buscar informes de problemas y solicitudes de extracción](/articles/searching-issues-and-pull-requests)". - -{% endtip %} diff --git a/translations/es-XL/data/reusables/search/required_login.md b/translations/es-XL/data/reusables/search/required_login.md deleted file mode 100644 index 8c973c3bb2..0000000000 --- a/translations/es-XL/data/reusables/search/required_login.md +++ /dev/null @@ -1 +0,0 @@ -Debes iniciar sesión para realizar búsquedas de código en todos los repositorios públicos. diff --git a/translations/es-XL/data/reusables/search/search_issues_and_pull_requests_shortcut.md b/translations/es-XL/data/reusables/search/search_issues_and_pull_requests_shortcut.md deleted file mode 100644 index 64fee4a7a0..0000000000 --- a/translations/es-XL/data/reusables/search/search_issues_and_pull_requests_shortcut.md +++ /dev/null @@ -1 +0,0 @@ -Puedes enfocar tu cursor en la barra de búsqueda que está sobre el listado de informe de problemas o solicitud de extracción con un atajo de teclado. Para obtener más información, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/#issue-and-pull-request-lists)". diff --git a/translations/es-XL/data/reusables/search/syntax_tips.md b/translations/es-XL/data/reusables/search/syntax_tips.md deleted file mode 100644 index f90619a584..0000000000 --- a/translations/es-XL/data/reusables/search/syntax_tips.md +++ /dev/null @@ -1,8 +0,0 @@ -{% tip %} - -**Sugerencia:**{% if currentVersion != "free-pro-team@latest" %} - - 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_enterprise %}.{% 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](/articles/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. - -{% endtip %} diff --git a/translations/es-XL/data/reusables/secret-scanning/beta.md b/translations/es-XL/data/reusables/secret-scanning/beta.md deleted file mode 100644 index 86eda34b55..0000000000 --- a/translations/es-XL/data/reusables/secret-scanning/beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Las {% data variables.product.prodname_secret_scanning_caps %} para los repositorios privados se encuentran actualmente en beta y están sujetas a cambios. Para solicitar acceso al beta,, [únete a la lista de espera](https://github.com/features/security/advanced-security/signup). - -{% endnote %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md b/translations/es-XL/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md deleted file mode 100644 index 4e4e6e8499..0000000000 --- a/translations/es-XL/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Si eres un investigador de seguridad, debes contactar directamente a los mantenedores para pedirles que creen asesorías de seguridad o que emitan CVEs en tu nombre en los repositorios que no administras. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/security/security-and-analysis-features-enable-read-only.md b/translations/es-XL/data/reusables/security/security-and-analysis-features-enable-read-only.md deleted file mode 100644 index 5d47d57541..0000000000 --- a/translations/es-XL/data/reusables/security/security-and-analysis-features-enable-read-only.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Si habilitas las características de seguridad y análisis, {% data variables.product.company_short %} realiza un análisis de solo lectura en tu repositorio. Para obtener más información, consulta la sección "[Acerca de cómo {% data variables.product.company_short %} utiliza tus datos](/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data)". -{% endif %} \ No newline at end of file diff --git a/translations/es-XL/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/es-XL/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md deleted file mode 100644 index 80125dc1cb..0000000000 --- a/translations/es-XL/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota**: No puedes inhabilitar algunas características de seguridad y análisis que están habilitadas predeterminadamente para los repositorios públicos. - -{% endnote %} diff --git a/translations/es-XL/data/reusables/shortdesc/authenticating_github_app.md b/translations/es-XL/data/reusables/shortdesc/authenticating_github_app.md deleted file mode 100644 index b3abd88d6f..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/authenticating_github_app.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener información sobre cómo autenticarte como una GitHub App, consulta la sección "[Opciones de Autenticación para GitHub Apps](/apps/building-github-apps/authentication-options-for-github-apps#authenticating-as-a-github-app)". diff --git a/translations/es-XL/data/reusables/shortdesc/authenticating_with_github_apps.md b/translations/es-XL/data/reusables/shortdesc/authenticating_with_github_apps.md deleted file mode 100644 index 17f72d31e8..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/authenticating_with_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes autenticarte como una {% data variables.product.prodname_github_app %} o como una instalación. diff --git a/translations/es-XL/data/reusables/shortdesc/authorizing_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/authorizing_oauth_apps.md deleted file mode 100644 index 4a33e5da5d..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/authorizing_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes habilitar a otros usuarios para que autoricen tu App de OAuth. diff --git a/translations/es-XL/data/reusables/shortdesc/creating_custom_badges_github_apps.md b/translations/es-XL/data/reusables/shortdesc/creating_custom_badges_github_apps.md deleted file mode 100644 index 967d4e1bf6..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/creating_custom_badges_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes reemplazar la insignia predeterminada en tu GitHub App si cargas tu propia imagen de logo y personalizas el fondo. diff --git a/translations/es-XL/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md deleted file mode 100644 index bb4d2e9483..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes reemplazar la insignia predeterminada en tu App de OAuth si cargas tu propia imagen de logo y personalizas el fondo. diff --git a/translations/es-XL/data/reusables/shortdesc/creating_github_apps.md b/translations/es-XL/data/reusables/shortdesc/creating_github_apps.md deleted file mode 100644 index a38af482fe..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/creating_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes crear y registrar una GitHub App bajo tu cuenta personal o bajo cualquier organización en la que tengas acceso administrativo. diff --git a/translations/es-XL/data/reusables/shortdesc/creating_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/creating_oauth_apps.md deleted file mode 100644 index 760c0f64fa..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/creating_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes crear y registrar una App de OAuth bajo tu cuenta personal o bajo cualquier organización en la que tengas acceso administrativo. Cuando ceras tu app de OAuth, recuerda proteger tu privacidad al utilizar únicamente la información que consideras pública. diff --git a/translations/es-XL/data/reusables/shortdesc/deleting_github_apps.md b/translations/es-XL/data/reusables/shortdesc/deleting_github_apps.md deleted file mode 100644 index 60cda19199..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/deleting_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes borrar las GitHub Apps cuando ya no las utilices. diff --git a/translations/es-XL/data/reusables/shortdesc/deleting_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/deleting_oauth_apps.md deleted file mode 100644 index f5731e4e80..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/deleting_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes borrar las Apps de OAuth cuando ya no las utilices. diff --git a/translations/es-XL/data/reusables/shortdesc/editing_permissions_for_github_apps.md b/translations/es-XL/data/reusables/shortdesc/editing_permissions_for_github_apps.md deleted file mode 100644 index 8ad4c69506..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/editing_permissions_for_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Después de registrar una GitHub App, puedes modificar sus permisos. diff --git a/translations/es-XL/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md b/translations/es-XL/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md deleted file mode 100644 index df319723ab..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Tu GitHub App puede realizar acciones en nombre de un usuario, como crear un informe de problemas, crear un despliegue, y utilizar otras terminales compatibles. diff --git a/translations/es-XL/data/reusables/shortdesc/iso_8601.md b/translations/es-XL/data/reusables/shortdesc/iso_8601.md deleted file mode 100644 index 94c647f9c9..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/iso_8601.md +++ /dev/null @@ -1 +0,0 @@ -Esta es una marca de tiempo en formato [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601): `AAAA-MM-DDTHH:MM:SSZ`. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/shortdesc/making-a-github-app-public-or-private.md b/translations/es-XL/data/reusables/shortdesc/making-a-github-app-public-or-private.md deleted file mode 100644 index 1aa24b6b7e..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/making-a-github-app-public-or-private.md +++ /dev/null @@ -1 +0,0 @@ -Cuando configuras una GitHub App, puedes hacer que su instalación sea pública para que cualquier usario u organización de GitHub pueda instalarla, o privada para que solo la puedas instalar en la cuenta que la creó. diff --git a/translations/es-XL/data/reusables/shortdesc/modifying_github_apps.md b/translations/es-XL/data/reusables/shortdesc/modifying_github_apps.md deleted file mode 100644 index 22d20675c1..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/modifying_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Después de crear una GitHub App, puedes hacerle cambios. diff --git a/translations/es-XL/data/reusables/shortdesc/modifying_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/modifying_oauth_apps.md deleted file mode 100644 index edf8f66672..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/modifying_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Despues de crear y registrar una App de OAuth, puedes hacerle cambios. diff --git a/translations/es-XL/data/reusables/shortdesc/permissions_github_apps.md b/translations/es-XL/data/reusables/shortdesc/permissions_github_apps.md deleted file mode 100644 index 7181e27759..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/permissions_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Cuando creas una GitHub App, configuras los permisos que definen los recursos a los cuales puede acceder a través de la API de REST. diff --git a/translations/es-XL/data/reusables/shortdesc/rate_limits_github_apps.md b/translations/es-XL/data/reusables/shortdesc/rate_limits_github_apps.md deleted file mode 100644 index a0de297409..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/rate_limits_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Los límites de tasa para las GitHub Apps ayudan a controlar la tasa de tráfico. diff --git a/translations/es-XL/data/reusables/shortdesc/suspending_a_github_app.md b/translations/es-XL/data/reusables/shortdesc/suspending_a_github_app.md deleted file mode 100644 index e11e92f619..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/suspending_a_github_app.md +++ /dev/null @@ -1 +0,0 @@ -Puedes bloquear temporalmente el acceso de una {% data variables.product.prodname_github_app %} a los recursos de tu cuenta si la suspendes. diff --git a/translations/es-XL/data/reusables/shortdesc/transferring_ownership_of_github_apps.md b/translations/es-XL/data/reusables/shortdesc/transferring_ownership_of_github_apps.md deleted file mode 100644 index 28b7aff5fd..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/transferring_ownership_of_github_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes transferir la propiedad de una GitHub App a otro usuario u organización. diff --git a/translations/es-XL/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md deleted file mode 100644 index de48d701ad..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Puedes transferir la propiedad de una App de OAuth a otro usuario u organización. diff --git a/translations/es-XL/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md deleted file mode 100644 index c3a2f108ac..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Cuando intercambias un código por un token de acceso, existe un conjunto de errores adicionales que pueden presentarse. El formato de estas respuestas se determina por el encabezado de aceptación que pases. diff --git a/translations/es-XL/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md deleted file mode 100644 index b802be22f5..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Cuando obtienes un token de OAuth para un usuario, pueden ocurrir algunos errores durante la fase inicial de solicitud de autorización. diff --git a/translations/es-XL/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md b/translations/es-XL/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md deleted file mode 100644 index 9c5d10b065..0000000000 --- a/translations/es-XL/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -Los alcances te permiten especificar exactamente el tipo de acceso que necesitas. Los alcances _limitan_ el acceso para los tokens de OAuth. No otorgan ningún permiso adicional más allá de aquél que el usuario ya tiene. diff --git a/translations/es-XL/data/reusables/sponsors/accept-legal-terms.md b/translations/es-XL/data/reusables/sponsors/accept-legal-terms.md deleted file mode 100644 index 8129f38507..0000000000 --- a/translations/es-XL/data/reusables/sponsors/accept-legal-terms.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa las [Condiciones Adicionales de {% data variables.product.prodname_sponsors %}](/github/site-policy/github-sponsors-additional-terms) y la [Declaración de Privacidad de {% data variables.product.prodname_dotcom %}](/articles/github-privacy-statement), posteriormente da clic en **Únete a la lista de espera**. diff --git a/translations/es-XL/data/reusables/sponsors/add-active-triggers.md b/translations/es-XL/data/reusables/sponsors/add-active-triggers.md deleted file mode 100644 index 583aa902ba..0000000000 --- a/translations/es-XL/data/reusables/sponsors/add-active-triggers.md +++ /dev/null @@ -1 +0,0 @@ -1. Para recibir actualizaciones del Evento de Patrocinio, selecciona **Activo**. ![Seleccionar eventos activos](/assets/images/help/sponsors/webhook-active.png) diff --git a/translations/es-XL/data/reusables/sponsors/add-introduction.md b/translations/es-XL/data/reusables/sponsors/add-introduction.md deleted file mode 100644 index 3be76170ed..0000000000 --- a/translations/es-XL/data/reusables/sponsors/add-introduction.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "introducción", teclea una descripción del trabajo que realizarás con tus patrocinios. ![Campo de texto para detalles de perfil](/assets/images/help/sponsors/introduction-box.png) diff --git a/translations/es-XL/data/reusables/sponsors/add-more-tiers.md b/translations/es-XL/data/reusables/sponsors/add-more-tiers.md deleted file mode 100644 index 41dc59e2da..0000000000 --- a/translations/es-XL/data/reusables/sponsors/add-more-tiers.md +++ /dev/null @@ -1 +0,0 @@ - 1. Repite los pasos anteriores hasta que hayas publicado todos los niveles que quieres ofrecer. diff --git a/translations/es-XL/data/reusables/sponsors/add-payload-url.md b/translations/es-XL/data/reusables/sponsors/add-payload-url.md deleted file mode 100644 index 6480484b6b..0000000000 --- a/translations/es-XL/data/reusables/sponsors/add-payload-url.md +++ /dev/null @@ -1 +0,0 @@ -1. Escribe una URL de carga, luego opcionalmente personaliza la configuración. Para obtener más información, consulta "[Crear webhooks](/webhooks/creating/#creating-webhooks)". ![Campos para la URL de carga y otras opciones de personalización](/assets/images/help/sponsors/webhook-payload-url.png) diff --git a/translations/es-XL/data/reusables/sponsors/add-webhook.md b/translations/es-XL/data/reusables/sponsors/add-webhook.md deleted file mode 100644 index 139d82c698..0000000000 --- a/translations/es-XL/data/reusables/sponsors/add-webhook.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Add webhook** (Agregar webhook). ![Botón para agregar webhook en la barra lateral Webhooks](/assets/images/help/sponsors/add-webhook-sponsors-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/change-tier.md b/translations/es-XL/data/reusables/sponsors/change-tier.md deleted file mode 100644 index c3a8a99efa..0000000000 --- a/translations/es-XL/data/reusables/sponsors/change-tier.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "{% data variables.product.prodname_sponsors %}", a la derecha de los colaboradores de código abierto, da clic en {% octicon "triangle-down" aria-label="The down triangle octicon" %} junto a tu cantidad patrocinada y luego da clic en **Cambiar nivel**. ![Botón de cambiar nivel](/assets/images/help/billing/edit-sponsor-billing.png) diff --git a/translations/es-XL/data/reusables/sponsors/click-add-tier.md b/translations/es-XL/data/reusables/sponsors/click-add-tier.md deleted file mode 100644 index a224aba3ac..0000000000 --- a/translations/es-XL/data/reusables/sponsors/click-add-tier.md +++ /dev/null @@ -1 +0,0 @@ -1. En la parte inferior de la página, da clic en **Agregar un nivel**. ![Botón de agregar nivel](/assets/images/help/sponsors/add-a-tier-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/confirm-add-webhook.md b/translations/es-XL/data/reusables/sponsors/confirm-add-webhook.md deleted file mode 100644 index c905947542..0000000000 --- a/translations/es-XL/data/reusables/sponsors/confirm-add-webhook.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Crear webhook**. ![Botón de crear webhook en la barra lateral de Webhooks](/assets/images/help/sponsors/create-webhook-sponsors-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/contact-info.md b/translations/es-XL/data/reusables/sponsors/contact-info.md deleted file mode 100644 index 21c9ed24f3..0000000000 --- a/translations/es-XL/data/reusables/sponsors/contact-info.md +++ /dev/null @@ -1 +0,0 @@ -1. Sigue las propuestas para completar tu información de contacto. diff --git a/translations/es-XL/data/reusables/sponsors/country-of-residence.md b/translations/es-XL/data/reusables/sponsors/country-of-residence.md deleted file mode 100644 index ad86229171..0000000000 --- a/translations/es-XL/data/reusables/sponsors/country-of-residence.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo de "País o región de residencia", utiliza el menú desplegable y selecciona tu ubicación de residencia. ![Menú desplegable de país o región de residencia](/assets/images/help/sponsors/country-of-residence-drop-down.png) -2. Haz clic en **Save (Guardar)**. diff --git a/translations/es-XL/data/reusables/sponsors/create-stripe-account.md b/translations/es-XL/data/reusables/sponsors/create-stripe-account.md deleted file mode 100644 index 39a619c541..0000000000 --- a/translations/es-XL/data/reusables/sponsors/create-stripe-account.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Da clic en **Cuenta de Stripe Connect**. ![Enlace para crear la cuenta de Stripe Connect](/assets/images/help/sponsors/create-stripe-connect-account.png) -2. Sigue las indicaciones para crear tu cuenta. diff --git a/translations/es-XL/data/reusables/sponsors/developer-sponsored-choose-updates.md b/translations/es-XL/data/reusables/sponsors/developer-sponsored-choose-updates.md deleted file mode 100644 index 67059c1759..0000000000 --- a/translations/es-XL/data/reusables/sponsors/developer-sponsored-choose-updates.md +++ /dev/null @@ -1 +0,0 @@ -4. Decide si quieres recibir actualizaciones por correo electrónico de el desarrollador patrocinado y después selecciona o deselecciona "Recibir actualizaciones de _DESARROLLADOR_." ![Casilla de verificación para recibir actualizaciones del programador patrocinado](/assets/images/help/sponsors/updates-checkbox-manage.png) diff --git a/translations/es-XL/data/reusables/sponsors/double-check-stripe-info.md b/translations/es-XL/data/reusables/sponsors/double-check-stripe-info.md deleted file mode 100644 index ed23abf61d..0000000000 --- a/translations/es-XL/data/reusables/sponsors/double-check-stripe-info.md +++ /dev/null @@ -1 +0,0 @@ -Al solicitar una cuenta Stripe Connect, asegúrate de que toda la información sea correcta antes de enviar tu solicitud. Una vez que enviaste tu solicitud, es difícil actualizar la información de identidad, como tu nombre y fecha de nacimiento. diff --git a/translations/es-XL/data/reusables/sponsors/draft-new-update.md b/translations/es-XL/data/reusables/sponsors/draft-new-update.md deleted file mode 100644 index 5d8b27e202..0000000000 --- a/translations/es-XL/data/reusables/sponsors/draft-new-update.md +++ /dev/null @@ -1 +0,0 @@ -4. A la derecha de "Email updates to your sponsorss" (Actualizaciones por correo electrónico para tus patrocinadores), haz clic en **New update** (Actualización nueva). ![Botón New update (Actualización nueva)](/assets/images/help/sponsors/new-update-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/edit-bank-information.md b/translations/es-XL/data/reusables/sponsors/edit-bank-information.md deleted file mode 100644 index 882bca0c04..0000000000 --- a/translations/es-XL/data/reusables/sponsors/edit-bank-information.md +++ /dev/null @@ -1 +0,0 @@ -4. En "Payouts information" (Información de pago), haz clic en **Edit your bank information** (Editar tu información bancaria). ![Editar tu enlace de información bancaria](/assets/images/help/sponsors/edit-bank-info.png) diff --git a/translations/es-XL/data/reusables/sponsors/edit-featured-work.md b/translations/es-XL/data/reusables/sponsors/edit-featured-work.md deleted file mode 100644 index d377218d1f..0000000000 --- a/translations/es-XL/data/reusables/sponsors/edit-featured-work.md +++ /dev/null @@ -1,3 +0,0 @@ -1. Opcionalmente, escoge los repositorios que se exhiben en tu perfil de {% data variables.product.prodname_sponsors %}. - - A la derecha de "Trabajo destacado", da clic en **Editar**. ![Botón de editar para trabajo destacado](/assets/images/help/sponsors/featured-work-edit-button.png) - - Selecciona hasta 6 repositorios y luego da clic en **Guardar**. ![Casillas para seleccionar los repositorios](/assets/images/help/sponsors/featured-work-select.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/edit-goal.md b/translations/es-XL/data/reusables/sponsors/edit-goal.md deleted file mode 100644 index e7e1c0756b..0000000000 --- a/translations/es-XL/data/reusables/sponsors/edit-goal.md +++ /dev/null @@ -1 +0,0 @@ -1. A la derecha de tu meta, da clic en **Editar**. ![Botón editar](/assets/images/help/sponsors/edit-goal-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/edit-tier.md b/translations/es-XL/data/reusables/sponsors/edit-tier.md deleted file mode 100644 index 57012f3cb1..0000000000 --- a/translations/es-XL/data/reusables/sponsors/edit-tier.md +++ /dev/null @@ -1 +0,0 @@ -1. A la derecha del nivel que quieras editar, da clic en **Editar**. ![Botón Edit tier (Editar nivel)](/assets/images/help/sponsors/edit-tier-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/github-contact-applicants.md b/translations/es-XL/data/reusables/sponsors/github-contact-applicants.md deleted file mode 100644 index 33aedc6add..0000000000 --- a/translations/es-XL/data/reusables/sponsors/github-contact-applicants.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_dotcom %} podría contactar a los solicitantes o participantes de {% data variables.product.prodname_sponsors %} pidiendo información adicional sobre su perfil o actividad de patrocinio para determinar la elegibilidad de dicho patrocinio o candidatura, o como parte de una investigación para la violación potencial de las condiciones. diff --git a/translations/es-XL/data/reusables/sponsors/github-review-app.md b/translations/es-XL/data/reusables/sponsors/github-review-app.md deleted file mode 100644 index eafd3d5e91..0000000000 --- a/translations/es-XL/data/reusables/sponsors/github-review-app.md +++ /dev/null @@ -1 +0,0 @@ -Es posible que {% data variables.product.prodname_dotcom %} tarde algunos días en revisar tu aplicación. Una vez que aprobemos tu aplicación, tu perfil automáticamente estará activo en [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors). diff --git a/translations/es-XL/data/reusables/sponsors/legal-additional-terms.md b/translations/es-XL/data/reusables/sponsors/legal-additional-terms.md deleted file mode 100644 index e4233f92f0..0000000000 --- a/translations/es-XL/data/reusables/sponsors/legal-additional-terms.md +++ /dev/null @@ -1 +0,0 @@ -El {% data variables.product.prodname_matching_fund %} es un regalo diseñado para motivar el financiamiento comunitario del trabajo realizado en código abierto y está sujeto a términos y condiciones adicionales. Para obtener información detallada sobre el {% data variables.product.prodname_matching_fund %}, consulta las "[Condiciones Adicionales de {% data variables.product.prodname_sponsors %}](/github/site-policy/github-sponsors-additional-terms)". diff --git a/translations/es-XL/data/reusables/sponsors/manage-developer-sponsorship.md b/translations/es-XL/data/reusables/sponsors/manage-developer-sponsorship.md deleted file mode 100644 index e789407cdb..0000000000 --- a/translations/es-XL/data/reusables/sponsors/manage-developer-sponsorship.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Debajo del nombre del desarrollador, da clic en **Patrocionio**. ![Botón de patrocinio](/assets/images/help/profile/sponsoring-button.png) -2. En la parte derecha de la página, da clic en **Administrar tu patrocinio**. ![Botón de administrar tu patrocinio](/assets/images/help/sponsors/manage-your-sponsorship-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/manage-existing-webhooks.md b/translations/es-XL/data/reusables/sponsors/manage-existing-webhooks.md deleted file mode 100644 index f5ee044875..0000000000 --- a/translations/es-XL/data/reusables/sponsors/manage-existing-webhooks.md +++ /dev/null @@ -1 +0,0 @@ -1. Para editar un webhook existente, da clic en **Editar**. Para eliminar un webhook existente, da clic en **Borrar**. ![Botones para administrar un webhook](/assets/images/help/sponsors/webhook-edit-delete-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/manage-org-sponsorship.md b/translations/es-XL/data/reusables/sponsors/manage-org-sponsorship.md deleted file mode 100644 index f324520697..0000000000 --- a/translations/es-XL/data/reusables/sponsors/manage-org-sponsorship.md +++ /dev/null @@ -1,2 +0,0 @@ -1. A un costado del nombre de la organización, da clic en **Patrocinio**. ![Botón de patrocinio](/assets/images/help/sponsors/org-sponsoring-button.png) -2. En la parte derecha de la página, da clic en **Administrar tu patrocinio**. ![Botón de administrar tu patrocinio](/assets/images/help/sponsors/manage-your-sponsorship-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/matching-fund-eligible.md b/translations/es-XL/data/reusables/sponsors/matching-fund-eligible.md deleted file mode 100644 index 0f4d492bcf..0000000000 --- a/translations/es-XL/data/reusables/sponsors/matching-fund-eligible.md +++ /dev/null @@ -1 +0,0 @@ -Eligibility for the {% data variables.product.prodname_matching_fund %} has passed. Applications received after the January 1, 2020 deadline are not eligible for {% data variables.product.prodname_matching_fund %}. diff --git a/translations/es-XL/data/reusables/sponsors/maximum-tier.md b/translations/es-XL/data/reusables/sponsors/maximum-tier.md deleted file mode 100644 index b41945e291..0000000000 --- a/translations/es-XL/data/reusables/sponsors/maximum-tier.md +++ /dev/null @@ -1 +0,0 @@ -El precio máximo es de $6000 dólares estadounidenses mensuales. diff --git a/translations/es-XL/data/reusables/sponsors/meet-the-team.md b/translations/es-XL/data/reusables/sponsors/meet-the-team.md deleted file mode 100644 index 9e7545d711..0000000000 --- a/translations/es-XL/data/reusables/sponsors/meet-the-team.md +++ /dev/null @@ -1,5 +0,0 @@ -1. Opcionalmente, elige a los miembros de la organización que están resaltados en tu perfil de {% data variables.product.prodname_sponsors %}. - - A la derecha de "Conoce al equipo", da clic en **Editar**. - ![Botón de editar miembros de organización en el perfil](/assets/images/help/sponsors/edit-org-members-profile-button.png) - - Selecciona hasta seis miembros de la organización y luego da clic en **Guardar**. ![Seleccionar miembros de la organización que se han resaltado](/assets/images/help/sponsors/select-highlighted-org-members.png) - - Opcionalmente, debajo de cada nombre de miembro resaltado, teclea una descripción del mismo. ![Descripción de los miembros de la roganización que se han resaltado](/assets/images/help/sponsors/description-highlighted-org-members.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-dev-sponsors-dashboard.md b/translations/es-XL/data/reusables/sponsors/navigate-to-dev-sponsors-dashboard.md deleted file mode 100644 index a047d8be56..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-dev-sponsors-dashboard.md +++ /dev/null @@ -1,2 +0,0 @@ -1. En la esquina superior derecha de cualquier página, da clic en tu foto de perfil, posteriormente, da clic en **{% data variables.product.prodname_sponsors %}**. ![Botón de {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. Si se muestra una lista de cuentas patrocinadas y elegibles, haz clic a la derecha de tu nombre en **Tablero**. ![Botón de tablero para patrocinadores del desarrollador](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-github-sponsors.md b/translations/es-XL/data/reusables/sponsors/navigate-to-github-sponsors.md deleted file mode 100644 index 9b012a163e..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-github-sponsors.md +++ /dev/null @@ -1 +0,0 @@ -1. Navega a [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors). diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-org-sponsors-dashboard.md b/translations/es-XL/data/reusables/sponsors/navigate-to-org-sponsors-dashboard.md deleted file mode 100644 index 410f47e530..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-org-sponsors-dashboard.md +++ /dev/null @@ -1,2 +0,0 @@ -1. En la esquina superior derecha de cualquier página, da clic en tu foto de perfil, posteriormente, da clic en **{% data variables.product.prodname_sponsors %}**. ![Botón de {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png) -2. En la lista de tus cuentas patrocinadas y elegibles, a la derecha de la organización, da clic en **Tablero**. ![Botón de tablero para patrocinadores de la organización](/assets/images/help/sponsors/org-sponsors-dashboard-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-payouts-tab.md b/translations/es-XL/data/reusables/sponsors/navigate-to-payouts-tab.md deleted file mode 100644 index b1fc1d59b4..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-payouts-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Pagos**. ![Pestaña de niveles de patrocinio](/assets/images/help/sponsors/payouts-tab.png) diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-profile-tab.md b/translations/es-XL/data/reusables/sponsors/navigate-to-profile-tab.md deleted file mode 100644 index c9a44cd179..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-profile-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Detalles de perfil**. ![Pestaña de detalles de perfil](/assets/images/help/sponsors/profile-tab.png) diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md b/translations/es-XL/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md deleted file mode 100644 index deb67e590b..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Niveles de patrocinio**. ![Pestaña de niveles de patrocinio](/assets/images/help/sponsors/sponsor-tiers-tab.png) diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-sponsored-developer.md b/translations/es-XL/data/reusables/sponsors/navigate-to-sponsored-developer.md deleted file mode 100644 index db56724ce1..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-sponsored-developer.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.product_name %}, visita el perfil del programador patrocinado. diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-sponsored-org.md b/translations/es-XL/data/reusables/sponsors/navigate-to-sponsored-org.md deleted file mode 100644 index beb63a9d81..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-sponsored-org.md +++ /dev/null @@ -1 +0,0 @@ -1. En {% data variables.product.product_name %}, navega al perfil de la organización patrocinada. diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-sponsors-tab.md b/translations/es-XL/data/reusables/sponsors/navigate-to-sponsors-tab.md deleted file mode 100644 index 1e3bf44b1e..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-sponsors-tab.md +++ /dev/null @@ -1 +0,0 @@ -3. En la barra lateral izquierda, da clic en **Tus patrocinadores**. ![Pestaña de patrocinadores](/assets/images/help/sponsors/sponsors-tab.png) diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-webhooks-tab.md b/translations/es-XL/data/reusables/sponsors/navigate-to-webhooks-tab.md deleted file mode 100644 index 78b8ed9faf..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-webhooks-tab.md +++ /dev/null @@ -1 +0,0 @@ -3. En la barra lateral izquierda, da clic en **Webhooks**. ![Pestaña de webhooks](/assets/images/help/sponsors/webhooks-tab.png) diff --git a/translations/es-XL/data/reusables/sponsors/navigate-to-your-goals-tab.md b/translations/es-XL/data/reusables/sponsors/navigate-to-your-goals-tab.md deleted file mode 100644 index 8a84aef458..0000000000 --- a/translations/es-XL/data/reusables/sponsors/navigate-to-your-goals-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Tus metas**. ![Pestaña de tus metas](/assets/images/help/sponsors/your-goals-tab.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/no-fees.md b/translations/es-XL/data/reusables/sponsors/no-fees.md deleted file mode 100644 index 4d19e32640..0000000000 --- a/translations/es-XL/data/reusables/sponsors/no-fees.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_sponsors %} no cobra ninguna cuota por patrocinio de las cuentas de usuario, así que el 100% de éstos van a la organización o al desarrollador patrocinado. diff --git a/translations/es-XL/data/reusables/sponsors/no-refunds.md b/translations/es-XL/data/reusables/sponsors/no-refunds.md deleted file mode 100644 index abd192f3a6..0000000000 --- a/translations/es-XL/data/reusables/sponsors/no-refunds.md +++ /dev/null @@ -1 +0,0 @@ -No se realizan reembolsos de pagos para {% data variables.product.prodname_sponsors %}. diff --git a/translations/es-XL/data/reusables/sponsors/opt-in-to-being-featured.md b/translations/es-XL/data/reusables/sponsors/opt-in-to-being-featured.md deleted file mode 100644 index 55c55fd832..0000000000 --- a/translations/es-XL/data/reusables/sponsors/opt-in-to-being-featured.md +++ /dev/null @@ -1 +0,0 @@ -1. Opcionalmente, selecciona **Ingresar para ser candidato potencial de github.com/sponsors**. ![Casilla para ingresar para ser considerado](/assets/images/help/sponsors/opt-in-to-being-featured.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/org-sponsored-choose-updates.md b/translations/es-XL/data/reusables/sponsors/org-sponsored-choose-updates.md deleted file mode 100644 index d2d41a3bcd..0000000000 --- a/translations/es-XL/data/reusables/sponsors/org-sponsored-choose-updates.md +++ /dev/null @@ -1 +0,0 @@ -4. Decide si quieres recibir actualizaciones por correo electrónico de la organización patrocinada y luego selecciona o deselecciona "Recibir actualizaciones de _ORGANIZACIÓN_." ![Casilla para recibir actualizaciones de la organización patrocinada](/assets/images/help/sponsors/org-updates-checkbox-manage.png) diff --git a/translations/es-XL/data/reusables/sponsors/overview-tab.md b/translations/es-XL/data/reusables/sponsors/overview-tab.md deleted file mode 100644 index 004a8bf7c6..0000000000 --- a/translations/es-XL/data/reusables/sponsors/overview-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Resumen**. ![Pestaña de resumen](/assets/images/help/sponsors/overview-tab.png) diff --git a/translations/es-XL/data/reusables/sponsors/payout-info.md b/translations/es-XL/data/reusables/sponsors/payout-info.md deleted file mode 100644 index 55f4306875..0000000000 --- a/translations/es-XL/data/reusables/sponsors/payout-info.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener información acerca de los tiempos de pago de {% data variables.product.prodname_sponsors %}, consulta la sección "[Condiciones Adicionales de GitHub Sponsors](/github/site-policy/github-sponsors-additional-terms#43-payment-timing)". diff --git a/translations/es-XL/data/reusables/sponsors/prorated-sponsorship.md b/translations/es-XL/data/reusables/sponsors/prorated-sponsorship.md deleted file mode 100644 index fdebd863f8..0000000000 --- a/translations/es-XL/data/reusables/sponsors/prorated-sponsorship.md +++ /dev/null @@ -1 +0,0 @@ -Se te cobrará inmediatamente un monto prorrateado por el tiempo transcurrido hasta tu próxima fecha de facturación regular. diff --git a/translations/es-XL/data/reusables/sponsors/publish-goal.md b/translations/es-XL/data/reusables/sponsors/publish-goal.md deleted file mode 100644 index e981da9bb1..0000000000 --- a/translations/es-XL/data/reusables/sponsors/publish-goal.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Publicar**. ![Botón Publicar](/assets/images/help/sponsors/publish-goal-button.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/publish-sponsor-update.md b/translations/es-XL/data/reusables/sponsors/publish-sponsor-update.md deleted file mode 100644 index 88fca3d181..0000000000 --- a/translations/es-XL/data/reusables/sponsors/publish-sponsor-update.md +++ /dev/null @@ -1 +0,0 @@ -7. Da clic en **Publicar**. diff --git a/translations/es-XL/data/reusables/sponsors/request-approval.md b/translations/es-XL/data/reusables/sponsors/request-approval.md deleted file mode 100644 index 8d67193141..0000000000 --- a/translations/es-XL/data/reusables/sponsors/request-approval.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Request approval** (Solicitar aprobación). ![Botón Request approval (Solicitar aprobación)](/assets/images/help/sponsors/request-approval-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/retire-goal.md b/translations/es-XL/data/reusables/sponsors/retire-goal.md deleted file mode 100644 index 3e858b0078..0000000000 --- a/translations/es-XL/data/reusables/sponsors/retire-goal.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Al final de la página, da clic en **Retrar**. ![El botón de retirar](/assets/images/help/sponsors/retire-goal-button.png) -2. Lee la advertencia y da clic en **OK**. ![Advertencia acerca de retirar una meta](/assets/images/help/sponsors/confirm-retire-goal.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/retire-tier.md b/translations/es-XL/data/reusables/sponsors/retire-tier.md deleted file mode 100644 index 48336675cf..0000000000 --- a/translations/es-XL/data/reusables/sponsors/retire-tier.md +++ /dev/null @@ -1 +0,0 @@ -7. Para retirar un nivel, da clic en **Retirar nivel** y luego da clic en **OK**. ![Botón Retire tier (Retirar nivel)](/assets/images/help/sponsors/retire-tier-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/review-and-publish-tier.md b/translations/es-XL/data/reusables/sponsors/review-and-publish-tier.md deleted file mode 100644 index 837f5bfa7f..0000000000 --- a/translations/es-XL/data/reusables/sponsors/review-and-publish-tier.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa tu nivel y da clic en **Publicar nivel**. ![Botón de publicar nivel](/assets/images/help/sponsors/publish-tier-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/save-profile.md b/translations/es-XL/data/reusables/sponsors/save-profile.md deleted file mode 100644 index c5f0c9ec37..0000000000 --- a/translations/es-XL/data/reusables/sponsors/save-profile.md +++ /dev/null @@ -1 +0,0 @@ -1. Haz clic en **Update profile (Actualizar perfil)**. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/save-tier-draft.md b/translations/es-XL/data/reusables/sponsors/save-tier-draft.md deleted file mode 100644 index c1899371f7..0000000000 --- a/translations/es-XL/data/reusables/sponsors/save-tier-draft.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Guardar borrador**. ![Botón de guardar borrador](/assets/images/help/sponsors/save-tier-draft.png) diff --git a/translations/es-XL/data/reusables/sponsors/select-a-tier.md b/translations/es-XL/data/reusables/sponsors/select-a-tier.md deleted file mode 100644 index 9e6cbb42ae..0000000000 --- a/translations/es-XL/data/reusables/sponsors/select-a-tier.md +++ /dev/null @@ -1 +0,0 @@ -1. En el lado derecho de la página, debajo de "Selecciona un nivel", revisa los niveles de patrocinio disponibles. Posteriormente, a la derecha del nivel que escojas, da clic en **Seleccionar**. ![Caja de selección de nivel](/assets/images/help/sponsors/select-a-tier-box.png) diff --git a/translations/es-XL/data/reusables/sponsors/select-goal-type.md b/translations/es-XL/data/reusables/sponsors/select-goal-type.md deleted file mode 100644 index 748959ba2f..0000000000 --- a/translations/es-XL/data/reusables/sponsors/select-goal-type.md +++ /dev/null @@ -1,4 +0,0 @@ -1. Debajo de "¿En qué se basa tu meta?", selecciona la **Cantidad de patrocinadores**" o **Patrocinios por mes**. ![Tipos de meta disponibles ](/assets/images/help/sponsors/select-goal-type.png) -2. Teclea la cantidad de patrocinadores que te gustaría tener, o la cantidad mensual a la que aspiras. -3. Debajo de "Describe tu meta", teclea una descripción de tu meta. ![Configuración de metas](/assets/images/help/sponsors/goal-settings.png) -5. Si eliges una meta basada en patrocinios por mes, selecciona "Entiendo que esto mostrará públicamente la cantidad de fondos de patrocinio que recibo mensualmente". ![Casilla en donde aceptas que entiendes que el fondo de tus patrocinios se publicará](/assets/images/help/sponsors/sponsorships-published-checkbox.png) diff --git a/translations/es-XL/data/reusables/sponsors/select-sponsorship-billing.md b/translations/es-XL/data/reusables/sponsors/select-sponsorship-billing.md deleted file mode 100644 index 65d1eb187e..0000000000 --- a/translations/es-XL/data/reusables/sponsors/select-sponsorship-billing.md +++ /dev/null @@ -1 +0,0 @@ -4. Dentro de "Billing information" (Información de facturación), revisa tus detalles de pago. Como alternativa, para cambiar los detalles de pago para toda tu cuenta {% data variables.product.product_name %}, haz clic en **Edit (Editar)**. Después, sigue las instrucciones para completar el formulario de pago. diff --git a/translations/es-XL/data/reusables/sponsors/send-update-to-sponsors.md b/translations/es-XL/data/reusables/sponsors/send-update-to-sponsors.md deleted file mode 100644 index bd5cd81ee4..0000000000 --- a/translations/es-XL/data/reusables/sponsors/send-update-to-sponsors.md +++ /dev/null @@ -1 +0,0 @@ -5. Opcionalmente, para enviar un correo electrónico a los patrocinadores en niveles específicos, usa el menú desplegable **All sponsors** (Todos los patrocinadores) y selecciona uno o más niveles. ![Selecciona el menú desplegable de los niveles de patrocinio](/assets/images/help/sponsors/select-tiers-email.png) diff --git a/translations/es-XL/data/reusables/sponsors/set-a-goal.md b/translations/es-XL/data/reusables/sponsors/set-a-goal.md deleted file mode 100644 index ded7911e20..0000000000 --- a/translations/es-XL/data/reusables/sponsors/set-a-goal.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Tus metas", da clic en **Configurar una meta**. ![Botón de configurar una meta ](/assets/images/help/sponsors/set-a-goal-button.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/settings-tab.md b/translations/es-XL/data/reusables/sponsors/settings-tab.md deleted file mode 100644 index c2aff80f73..0000000000 --- a/translations/es-XL/data/reusables/sponsors/settings-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Configuración**. ![Pestaña Parámetros](/assets/images/help/sponsors/settings-tab.png) diff --git a/translations/es-XL/data/reusables/sponsors/short-bio.md b/translations/es-XL/data/reusables/sponsors/short-bio.md deleted file mode 100644 index bc4baca57b..0000000000 --- a/translations/es-XL/data/reusables/sponsors/short-bio.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Biografía corta", teclea una descripción breve de ti y de tu trabajo. ![Campo de biografía corta](/assets/images/help/sponsors/short-bio.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/sponsors/sponsors-updates-tab.md b/translations/es-XL/data/reusables/sponsors/sponsors-updates-tab.md deleted file mode 100644 index 36dce476e7..0000000000 --- a/translations/es-XL/data/reusables/sponsors/sponsors-updates-tab.md +++ /dev/null @@ -1 +0,0 @@ -3. En la barra lateral izquierda, haz clic en **Updates** (Actualizaciones). ![Pestaña Updates (Actualizaciones)](/assets/images/help/sponsors/updates-tab.png) diff --git a/translations/es-XL/data/reusables/sponsors/sponsorship-details.md b/translations/es-XL/data/reusables/sponsors/sponsorship-details.md deleted file mode 100644 index 92e7f55087..0000000000 --- a/translations/es-XL/data/reusables/sponsors/sponsorship-details.md +++ /dev/null @@ -1 +0,0 @@ -Cualquiera con una cuenta de {% data variables.product.product_name %} puede patrocinar a alguien con un perfil de desarrollador u organización patrocinados mediante un pago mensual recurrente. Puedes escoger varios niveles de patrocinio, con cantidades de pago mensual y beneficios que configura la organización o el desarrollador patrocinado. Tu patrocinio compartirá la fecha de facturación de tu cuenta, así como el método de pago y recibos. diff --git a/translations/es-XL/data/reusables/sponsors/sponsorships-not-tax-deductible.md b/translations/es-XL/data/reusables/sponsors/sponsorships-not-tax-deductible.md deleted file mode 100644 index d1ce5fa2de..0000000000 --- a/translations/es-XL/data/reusables/sponsors/sponsorships-not-tax-deductible.md +++ /dev/null @@ -1 +0,0 @@ -Generalmente, los patrocionios no se deducen de impuestos, pero pueden hacerlo en ciertos casos. Es responsabilidad del colaborador de código abierto patrocinado—y no así de {% data variables.product.prodname_dotcom %}— informar a los patrocinadores si las contribuciones se están realizando a una entidad libre de impuestos como un 501(c)(3), y si los patrocinios pueden ser deducibles de impuestos. diff --git a/translations/es-XL/data/reusables/sponsors/stripe-supported-regions.md b/translations/es-XL/data/reusables/sponsors/stripe-supported-regions.md deleted file mode 100644 index 13a3744dfc..0000000000 --- a/translations/es-XL/data/reusables/sponsors/stripe-supported-regions.md +++ /dev/null @@ -1 +0,0 @@ -Para encontrar una lista de regiones compatibles, consulta [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors). diff --git a/translations/es-XL/data/reusables/sponsors/tax-form-information-dev.md b/translations/es-XL/data/reusables/sponsors/tax-form-information-dev.md deleted file mode 100644 index 77db328094..0000000000 --- a/translations/es-XL/data/reusables/sponsors/tax-form-information-dev.md +++ /dev/null @@ -1,4 +0,0 @@ -Para obtener más información acerca de los formatos de impuestos que necesitas llenar, consulta las siguientes instrucciones en el sitio web del Servicio de Impuestos Internos de los Estados Unidos. - -- [Instrucciones para el formulario W-9](https://www.irs.gov/pub/irs-pdf/iw9.pdf), para residentes de los EE.UU. -- [Instrucciones para el formulario W-8BEN](https://www.irs.gov/pub/irs-pdf/iw8ben.pdf), para residentes no estadounidenses diff --git a/translations/es-XL/data/reusables/sponsors/tax-form-information-org.md b/translations/es-XL/data/reusables/sponsors/tax-form-information-org.md deleted file mode 100644 index a867de8754..0000000000 --- a/translations/es-XL/data/reusables/sponsors/tax-form-information-org.md +++ /dev/null @@ -1 +0,0 @@ -Para obtener más información acerca de los formatos de impuestos que deben completar las organizaciones, consulta la sección [Instrucciones para el Formato W-8BEN-E](https://www.irs.gov/pub/irs-pdf/iw8bene.pdf) en el sitio web del Servicio de Impuestos Internos de los Estados Unidos. diff --git a/translations/es-XL/data/reusables/sponsors/tax-form-link.md b/translations/es-XL/data/reusables/sponsors/tax-form-link.md deleted file mode 100644 index a575b6cfed..0000000000 --- a/translations/es-XL/data/reusables/sponsors/tax-form-link.md +++ /dev/null @@ -1,2 +0,0 @@ -1. Da clic en **Formulario de impuestos**. ![Enlace para llenar el formato de impuestos](/assets/images/help/sponsors/tax-form-link.png) -2. Completa, firma y emite el formato de impuestos. diff --git a/translations/es-XL/data/reusables/sponsors/tier-details.md b/translations/es-XL/data/reusables/sponsors/tier-details.md deleted file mode 100644 index e77cfda36f..0000000000 --- a/translations/es-XL/data/reusables/sponsors/tier-details.md +++ /dev/null @@ -1,3 +0,0 @@ -Puedes crear hasta diez niveles de patrocinio que podrán escoger los patrocinadores. Cada nivel tiene sus propias cantidades de pago mensual en dólares estadounidenses y sus beneficios, tal como recibir acceso anticipado a las nuevas versiones o recibir menciones en el archivo README del proyecto. - -Una vez que tengas a un patrocinador en un nivel, no podrás editar el precio de éste. En vez de eso, deberás retirar el nivel y crear uno nuevo. Los patrocinadores existentes permanecerán en el nivel retirado hasta que cambien su nivel de patrocinio o cancelen su patrocinio. diff --git a/translations/es-XL/data/reusables/sponsors/tier-price-description.md b/translations/es-XL/data/reusables/sponsors/tier-price-description.md deleted file mode 100644 index d7dde173e5..0000000000 --- a/translations/es-XL/data/reusables/sponsors/tier-price-description.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea un precio mensual y descripción del nivel. ![Campos de texto para precio y descripción del nivel](/assets/images/help/sponsors/tier-price-description.png) diff --git a/translations/es-XL/data/reusables/sponsors/tier-update.md b/translations/es-XL/data/reusables/sponsors/tier-update.md deleted file mode 100644 index c2f4c896cc..0000000000 --- a/translations/es-XL/data/reusables/sponsors/tier-update.md +++ /dev/null @@ -1 +0,0 @@ -6. Revisa tu nivel y luego haz clic en **Update** (Actualizar). ![Botón Update tier (Actualizar nivel)](/assets/images/help/sponsors/update-tier-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/update-sponsorship.md b/translations/es-XL/data/reusables/sponsors/update-sponsorship.md deleted file mode 100644 index 15a7c1f53a..0000000000 --- a/translations/es-XL/data/reusables/sponsors/update-sponsorship.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Actualizar patrocinio**. ![Botón de actualizar patrocinio](/assets/images/help/sponsors/update-sponsorship-button.png) diff --git a/translations/es-XL/data/reusables/sponsors/view-eligible-accounts.md b/translations/es-XL/data/reusables/sponsors/view-eligible-accounts.md deleted file mode 100644 index f2282c169c..0000000000 --- a/translations/es-XL/data/reusables/sponsors/view-eligible-accounts.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Ver tus cuentas elegibles**. ![Botón para ver tus cuentas elegibles](/assets/images/help/sponsors/view-eligible-accounts.png) diff --git a/translations/es-XL/data/reusables/sponsors/webhook-content-formatting.md b/translations/es-XL/data/reusables/sponsors/webhook-content-formatting.md deleted file mode 100644 index d84dfcf656..0000000000 --- a/translations/es-XL/data/reusables/sponsors/webhook-content-formatting.md +++ /dev/null @@ -1 +0,0 @@ -4. Debajo de "Tipo de contenido", selecciona qué formato de datos quisieras recibir. Para obtener más información, consulta la sección "[Crear webhooks](/webhooks/creating/#content-type)" ![Menú para dar formato a los webhooks](/assets/images/help/sponsors/webhook-content-menu.png) diff --git a/translations/es-XL/data/reusables/sponsors/webhook-secret-token.md b/translations/es-XL/data/reusables/sponsors/webhook-secret-token.md deleted file mode 100644 index 8a20b41097..0000000000 --- a/translations/es-XL/data/reusables/sponsors/webhook-secret-token.md +++ /dev/null @@ -1 +0,0 @@ -5. Teclea un token secreto. Para obtener más información, consulta la sección "[Asegurar tus webhooks](/webhooks/securing/#securing-your-secret-token)". ![Campos para token secreto y otras opciones de personalización](/assets/images/help/sponsors/webhook-secret-token.png) diff --git a/translations/es-XL/data/reusables/sponsors/who-can-see-your-sponsorship.md b/translations/es-XL/data/reusables/sponsors/who-can-see-your-sponsorship.md deleted file mode 100644 index e9df98186e..0000000000 --- a/translations/es-XL/data/reusables/sponsors/who-can-see-your-sponsorship.md +++ /dev/null @@ -1 +0,0 @@ -1. Elegir quién puede ver tu patrocinio. diff --git a/translations/es-XL/data/reusables/sponsors/write-sponsor-update.md b/translations/es-XL/data/reusables/sponsors/write-sponsor-update.md deleted file mode 100644 index 88e704ebd4..0000000000 --- a/translations/es-XL/data/reusables/sponsors/write-sponsor-update.md +++ /dev/null @@ -1 +0,0 @@ -6. Escribe un asunto y un mensaje para tu actualización.![Campos de asunto y cuerpo](/assets/images/help/sponsors/subject-body-update.png) diff --git a/translations/es-XL/data/reusables/sponsors/you-can-be-a-sponsored-developer.md b/translations/es-XL/data/reusables/sponsors/you-can-be-a-sponsored-developer.md deleted file mode 100644 index 36da913554..0000000000 --- a/translations/es-XL/data/reusables/sponsors/you-can-be-a-sponsored-developer.md +++ /dev/null @@ -1 +0,0 @@ -Cualquiera que contribuya con un proyecto de código abierto y tenga una cuenta bancaria en una región compatible puede convertirse en un desarrollador patrocinado. Las contribuciones incluyen, entre otras, informes de errores, evaluación de propuestas, código, documentación, liderazgo, desarrollo comercial, gestión de proyectos, mentoría y diseño. Si vives en una región que aún no es compatible con {% data variables.product.prodname_sponsors %}, puedes inscribirte a la llista de espera para participar en el beta de {% data variables.product.prodname_sponsors %}. Para ver si {% data variables.product.prodname_sponsors %} está disponible en tu área, consulta la [lista de regiones compatibles](https://github.com/sponsors#regions). diff --git a/translations/es-XL/data/reusables/sponsors/you-can-be-a-sponsored-organization.md b/translations/es-XL/data/reusables/sponsors/you-can-be-a-sponsored-organization.md deleted file mode 100644 index a984205321..0000000000 --- a/translations/es-XL/data/reusables/sponsors/you-can-be-a-sponsored-organization.md +++ /dev/null @@ -1 +0,0 @@ -Cualquier organización que contribuya con un proyecto de código abierto y tenga una cuenta bancaria dedicada en una región compatible podrá convertirse en una organización patrocinada. Si vives en una región que aún no es compatible con {% data variables.product.prodname_sponsors %}, únete a la lista de espera en [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors). diff --git a/translations/es-XL/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/es-XL/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md deleted file mode 100644 index af4760bd17..0000000000 --- a/translations/es-XL/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ /dev/null @@ -1,3 +0,0 @@ -```shell -$ ssh-add ~/.ssh/id_rsa -``` diff --git a/translations/es-XL/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/es-XL/data/reusables/ssh/add-ssh-key-to-ssh-agent.md deleted file mode 100644 index 8b89cca426..0000000000 --- a/translations/es-XL/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ /dev/null @@ -1 +0,0 @@ -Si creaste tu llave con un nombre distinto, o si estás agregando una llave existente que tiene un nombre distinto, reemplaza *id_rsa* en el comando con el nombre de tu archivo de llave privada. diff --git a/translations/es-XL/data/reusables/ssh/dsa-support.md b/translations/es-XL/data/reusables/ssh/dsa-support.md deleted file mode 100644 index 4ecf3ca61b..0000000000 --- a/translations/es-XL/data/reusables/ssh/dsa-support.md +++ /dev/null @@ -1,5 +0,0 @@ -{% note %} - -**Nota:** Las llaves DSA de {% if currentVersion != "free-pro-team@latest" or currentVersion ver_lt "enterprise-server@2.19" %} se obsoletizaron en OpenSSH 7.0. Si tu sistema operativo utiliza OpenSSH, deberas utilizar una tipo de llave alterno cuando configures SSH, tal como una llave RSA. Por ejemplo, si tu sistema operativo es macOS Sierra, puedes configurar SSH utilizando una llave RSA.{% else %}Ya no hay compatibilidad con las llaves DSA (SSH-DSS). Las llaves existentes seguirán funcionando, pero no puedes agregar una llave DSA nueva a tu cuenta de {% data variables.product.product_name %}.{% endif %} - -{% endnote %} diff --git a/translations/es-XL/data/reusables/support/about-premium-plans.md b/translations/es-XL/data/reusables/support/about-premium-plans.md deleted file mode 100644 index e6b01bdb6b..0000000000 --- a/translations/es-XL/data/reusables/support/about-premium-plans.md +++ /dev/null @@ -1,23 +0,0 @@ - -### Planes {% data variables.contact.premium_support %} - -Existen dos planes de {% data variables.contact.premium_support %}: Premium y Premium Plus / {% data variables.product.microsoft_premium_plus_support_plan %}. - -| | {% data variables.product.premium_support_plan %} | {% data variables.product.premium_plus_support_plan %} | -| --------------------------- | -------------------------------------------------------- | ------------------------------------------------------------- | -| Horas de operación | 24 x 7 | 24 x 7 | -| Tiempo de respuesta inicial |
    • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
    • 4 horas para {% data variables.product.support_ticket_priority_high %}
    |
    • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
    • 4 horas para {% data variables.product.support_ticket_priority_high %}
    | -| Canales de soporte técnico |
    • Emisión de ticket en línea
    • Soporte vía telefónica
    |
    • Emisión de ticket en línea
    • Soporte vía telefónica
    • Compartir pantalla en problemas críticos
    | -| Capacitación | Acceso a contenido prémium |
    • Acceso a contenido prémium
    • 1 clase de capacitación virtual por año
    | -| Contactos autorizados | 10 | 25 | -| Recursos | Procesamiento de ticket con prioridad |
    • Procesamiento de ticket con prioridad
    • Gerente de Cuenta de Soporte Técnico Nombrado
    | -| Revisiones programadas | Revisión de estado y elaboración de informes bianual |
    • Reporte y verificación de salud trimestral
    • Revisiones de cuenta trimestrales
    | -| Administración | | 4 horas de Servicios administrados por mes | - - {% note %} - - **Notas:** - - Las revisiones programadas se limitan a una organización por trimestre. En cualquier momento puedes agregar revisiones programadas para más organizaciones por una tarifa adicional [contactándote con nuestro equipo de gestión de cuentas](https://enterprise.github.com/contact) o llamando al [+1 (877) 448-4820](tel:+1-877-448-4820). - - Para el {% data variables.product.premium_plus_support_plan %}, el 50 % de las horas de Servicios administrados no utilizadas se transfieren al siguiente mes y vencen al final del trimestre. - - {% endnote %} diff --git a/translations/es-XL/data/reusables/support/accessing-premium-content.md b/translations/es-XL/data/reusables/support/accessing-premium-content.md deleted file mode 100644 index dfb86f1060..0000000000 --- a/translations/es-XL/data/reusables/support/accessing-premium-content.md +++ /dev/null @@ -1,4 +0,0 @@ - -### Acceder a contenido prémium - -Puedes acceder al contenido premium iniciando sesión en el {% data variables.contact.contact_enterprise_portal %}. diff --git a/translations/es-XL/data/reusables/support/ask-and-answer-forum.md b/translations/es-XL/data/reusables/support/ask-and-answer-forum.md deleted file mode 100644 index 052dbc2d84..0000000000 --- a/translations/es-XL/data/reusables/support/ask-and-answer-forum.md +++ /dev/null @@ -1 +0,0 @@ -Puedes conectarte con desarrolladores de todo el mundo en el [{% data variables.product.prodname_gcf %}](https://github.community) para preguntar y responder preguntas, aprender e interactuar directamente con el personal de {% data variables.product.product_name %}. diff --git a/translations/es-XL/data/reusables/support/connect-in-the-forum-bootcamp.md b/translations/es-XL/data/reusables/support/connect-in-the-forum-bootcamp.md deleted file mode 100644 index e10ff24e88..0000000000 --- a/translations/es-XL/data/reusables/support/connect-in-the-forum-bootcamp.md +++ /dev/null @@ -1 +0,0 @@ -Conéctate con personas de todo el mundo en el [{% data variables.product.prodname_gcf %}](https://github.community) diff --git a/translations/es-XL/data/reusables/support/contacting-premium-support.md b/translations/es-XL/data/reusables/support/contacting-premium-support.md deleted file mode 100644 index df17b4d8de..0000000000 --- a/translations/es-XL/data/reusables/support/contacting-premium-support.md +++ /dev/null @@ -1,4 +0,0 @@ - -### Comunicarse con {% data variables.contact.premium_support %} - -Los clientes de {% data variables.contact.premium_support %} pueden utilizar el {% data variables.contact.contact_enterprise_portal %} para reportar problemas por escrito, en inglés. También puedes recibir soporte técnico en inglés por teléfono. Para obtener el número de teléfono de la {% data variables.contact.premium_support %}, consulta "[24x7 Phone Support](https://enterprise.githubsupport.com/hc/en-us/articles/360029707371-24x7-Phone-Support)" (Soporte técnico telefónico 24x7) en el {% data variables.contact.enterprise_portal %}. diff --git a/translations/es-XL/data/reusables/support/data-protection-and-privacy.md b/translations/es-XL/data/reusables/support/data-protection-and-privacy.md deleted file mode 100644 index 94fe6f433a..0000000000 --- a/translations/es-XL/data/reusables/support/data-protection-and-privacy.md +++ /dev/null @@ -1 +0,0 @@ -Cuando utilizas las ofertas de soporte de {% data variables.product.prodname_dotcom %}, se aplicará tanto la Declaración de Privacidad de {% data variables.product.prodname_dotcom %} como la Adenda de Protección de Datos de {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-XL/data/reusables/support/enterprise-resolving-and-closing-tickets.md b/translations/es-XL/data/reusables/support/enterprise-resolving-and-closing-tickets.md deleted file mode 100644 index 8003555496..0000000000 --- a/translations/es-XL/data/reusables/support/enterprise-resolving-and-closing-tickets.md +++ /dev/null @@ -1,5 +0,0 @@ -{% data variables.contact.enterprise_support %} podría considerar un ticket como resuelto después de proporcionar una explicación, recomendación, instrucciones de uso, instrucciones de solución alternativa, o recomendándote un lanzamiento disponible que trata el problema. - -Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.enterprise_support %} puede pedirte que elimines complementos, módulos o códigos no compatibles al intentar resolver el problema. Si el problema se arregla cuando el plug-in, módulo, o código personalizado no compatibles se eliminan, {% data variables.contact.enterprise_support %} podría considerar el ticket como resuelto. - -{% data variables.contact.enterprise_support %} podría cerrar tickets si están fuera del alcance de soporte, o si se han realizado diversos intentos para contactarte y no se han respondido. Si {% data variables.contact.enterprise_support %} cierra un ticket por falta de respuesta, puedes solicitar que lo vuelva a abrir. diff --git a/translations/es-XL/data/reusables/support/ghec-premium-priorities.md b/translations/es-XL/data/reusables/support/ghec-premium-priorities.md deleted file mode 100644 index eff65482a3..0000000000 --- a/translations/es-XL/data/reusables/support/ghec-premium-priorities.md +++ /dev/null @@ -1,6 +0,0 @@ -| Prioridad | Descripción | Ejemplos | -|:------------------------------------------------------------------:| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- | -| {% data variables.product.support_ticket_priority_urgent %} | Los flujos de trabajo de producción para tu organización o empresa en {% data variables.product.prodname_ghe_cloud %} fallan debido a los errores o suspensiones de servicios críticos, y las fallas impactan directamente a la operación de tu negocio. |
    • Los errores o suspenciones en {% data variables.product.prodname_dotcom_the_website %} afectan la funcionalidad principal de Git o de las aplicaciones web para todos los miembros de tu organización o empresa
    | -| {% data variables.product.support_ticket_priority_high %} | Los problemas de cuenta o de seguridad con tu organización o empresa en {% data variables.product.prodname_ghe_cloud %} están causando un impacto limitado en tu negocio. |
    • Un propietario de organización o empresa borró una organización sin querer
    • Un miembro de una organización o empresa subió datos sensibles en una confirmación, informe de problemas, solicitud de extracción o adjunto en el informe de problemas
    | -| {% data variables.product.support_ticket_priority_normal %} | Los miembros de tu organización o empresa en {% data variables.product.prodname_ghe_cloud %} están experimentando problemas moderados o limitados con {% data variables.product.prodname_dotcom_the_website %}, o tienes preocupaciones o dudas generales sobre tu organización o empresa. |
    • Preguntas sobre el uso de las API o de las características para tu organización o empresa
    • Problemas con herramientas para migración de datos de una organización que proporciona {% data variables.product.company_short %}
    • Características relacionadas con que tu organización o empresa no funcione como se espera
    • Preguntas generales de seguridad de tu organización o empresa
    | -| {% data variables.product.support_ticket_priority_low %} | Tienes una pregunta o sugerencia sobre tu organización o empresa en {% data variables.product.prodname_ghe_cloud %} que no es urgente, o no bloquea la productividad de tu equipo en alguna otra forma. |
    • Uso excesivo de recursos para tu organización o empresa
    • Solicitudes de verificaciones de estado
    • Ayuda con el uso de Gists, notificaciones, wikis, {% data variables.product.prodname_pages %}, {% data variables.product.prodname_desktop %}, Atom, u otros servicios periféricos o características en tu organización o empresa
    • Solicitudes de características
    • Retroalimentación de producto
    | diff --git a/translations/es-XL/data/reusables/support/ghes-priorities.md b/translations/es-XL/data/reusables/support/ghes-priorities.md deleted file mode 100644 index 406ae4daf0..0000000000 --- a/translations/es-XL/data/reusables/support/ghes-priorities.md +++ /dev/null @@ -1,6 +0,0 @@ -| Prioridad | Descripción | Ejemplos | -|:------------------------------------------------------------------:| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- | -| {% data variables.product.support_ticket_priority_urgent %} | {% data variables.product.prodname_ghe_server %} está fallando en un ambiente productivo, y dicha falla impacta en la operación de tu negocio.

    _{% data reusables.support.priority-urgent-english-only %}_ |
    • Errores o suspensiones que afectan la funcionalidad central de Git o de la aplicación web para todos los usuarios
    • Degradación grave de rendimiento para la mayoría de los usuarios
    • Almacenamiento agotado, o que se llena muy rápidamente
    • Incapacidad para instalar un archivo de licencia renovado
    • Incidente de seguridad
    • Pérdida de acceso administrativo para la instancia sin solución alternativa conocida
    • Falla para restaurar un respaldo en un ambiente productivo
    | -| {% data variables.product.support_ticket_priority_high %} | {% data variables.product.prodname_ghe_server %} está fallando en un ambiente productivo, pero el impacto a tu negocio es limitado. |
    • Degradación del rendimiento que reduce la productividad para muchos usuarios
    • Redundancia reducida por fallo en la Alta Disponibilidad (HA) o nodos de agrupación
    • Fallo en respaldar la instancia
    • Fallo para restaurar un respaldo en un ambiente de prueba o de montaje que podría poner en riesgo la restauración exitosa a un ambiente productivo
    | -| {% data variables.product.support_ticket_priority_normal %} | Estás experimentando problemas limitados o moderados con {% data variables.product.prodname_ghe_server %}, o tienes preocupaciones o dudas generales sobre la operación de tu instancia. |
    • Problemas en un ambiente de pruebas o de montaje
    • Consejo sobre utilizar las características y APIS de {% data variables.product.prodname_dotcom %}, o dudas sobre configurar las integraciones de terceros desde tu instancia
    • Problemas con las herramientas para la migración de datos de usuario que proporciona {% data variables.product.company_short %}
    • Mejoras
    • Reporte de errores
    • Características que no funcionan como se espera
    • Preguntas generales sobre seguridad
    | -| {% data variables.product.support_ticket_priority_low %} | Tienes una pregunta o sugerencia acerca de {% data variables.product.prodname_ghe_server %} que no es urgente o que no bloquea la productividad de tu equipo de otra forma. |
    • Solicitudes de características
    • Retroalimentación de producto
    • Solicitudes de verificación de estado (por el momento, únicamente disponible para clientes con un {% data variables.product.premium_support_plan %})
    • Notificar a {% data variables.product.company_short %} sobre mantenimiento planeado para tu instancia
    | diff --git a/translations/es-XL/data/reusables/support/github-can-modify-ticket-priority.md b/translations/es-XL/data/reusables/support/github-can-modify-ticket-priority.md deleted file mode 100644 index 68f0f1cd65..0000000000 --- a/translations/es-XL/data/reusables/support/github-can-modify-ticket-priority.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.company_short %} tiene la absoluta discreción para modificar la prioridad de un ticket en cualquier momento, y puede bajar la prioridad de un ticket después de determinar y mitigar la causa principal de un problema. diff --git a/translations/es-XL/data/reusables/support/help_resources.md b/translations/es-XL/data/reusables/support/help_resources.md deleted file mode 100644 index 58732b2932..0000000000 --- a/translations/es-XL/data/reusables/support/help_resources.md +++ /dev/null @@ -1,7 +0,0 @@ -Para preguntas, reportes de errores y debates sobre las {% data variables.product.prodname_github_app %}, {% data variables.product.prodname_oauth_app %}, y el desarrollo de API, explora el {% data variables.product.prodname_support_forum_with_url %}. El foro se modera y mantiene con el personal de {% data variables.product.product_name %}, pero no se garantiza que el personal de {% data variables.product.product_name %} responda las preguntas que se publiquen en el mismo. - -Considera contactar al [Soporte de GitHub](https://github.com/contact) directamente utilizando el formato de contacto para: - - respuestas garantizadas del personal de {% data variables.product.product_name %} - - solicitudes de soporte que involucren preocupaciones sobre datos sensibles o privados - - solicitudes de características - - retroalimentación sobre los productos de {% data variables.product.product_name %} diff --git a/translations/es-XL/data/reusables/support/premium-resolving-and-closing-tickets.md b/translations/es-XL/data/reusables/support/premium-resolving-and-closing-tickets.md deleted file mode 100644 index f90da555db..0000000000 --- a/translations/es-XL/data/reusables/support/premium-resolving-and-closing-tickets.md +++ /dev/null @@ -1,5 +0,0 @@ -{% data variables.contact.premium_support %} podría considerar un ticket como resuelto después de proporcionar una explicación, recomendación, instrucciones de uso, instrucciones de solución alternativa, o recomendándote un lanzamiento disponible que trata el problema. - -Si usas un complemento personalizado o no compatible, módulo o código personalizado, {% data variables.contact.premium_support %} puede pedirte que elimines el complemento, el módulo o el código no compatible mientras intentas resolver el problema. {% data variables.contact.premium_support %} puede considerar el ticket como resuelto si el problema se soluciona cuando se elimina el plug-in, módulo, o código personalizado no compatible. - -{% data variables.contact.premium_support %}Puede cerrar los tickets si están fuera del alcance de soporte o si se te ha intentado contactar varias veces sin recibir una respuesta. Si {% data variables.contact.premium_support %} cierra un ticket por no haber recibido respuesta, puedes solicitar que lo reabra. diff --git a/translations/es-XL/data/reusables/support/priority-urgent-english-only.md b/translations/es-XL/data/reusables/support/priority-urgent-english-only.md deleted file mode 100644 index dda9a125f2..0000000000 --- a/translations/es-XL/data/reusables/support/priority-urgent-english-only.md +++ /dev/null @@ -1 +0,0 @@ -El soporte para tickets con prioridad {% data variables.product.support_ticket_priority_urgent %} se encuentra disponible únicamente en inglés. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/support/receiving-credits.md b/translations/es-XL/data/reusables/support/receiving-credits.md deleted file mode 100644 index dda2e4a2ac..0000000000 --- a/translations/es-XL/data/reusables/support/receiving-credits.md +++ /dev/null @@ -1,19 +0,0 @@ - -### Recibir créditos por falta de respuesta a los tickets de soporte - -Si no recibes una respuesta inicial dentro del tiempo de respuesta garantizado en más de cuatro tickets en un trimestre basándote en el año fiscal de {% data variables.product.company_short %}, serás elegible para que se te dé crédito. En cumplimiento del Acuerdo de nivel de servicio, {% data variables.product.company_short %} te reembolsará el 20 % de la tarifa {% data variables.contact.premium_support %} trimestral en efectivo. Para recibir el reembolso, debes enviar una solicitud de crédito. - -La solicitud de crédito se debe hacer dentro de los 30 días del final del trimestre durante el cual {% data variables.contact.premium_support %} no respondió a tus tickets dentro del tiempo designado de respuesta. Las solicitudes de crédito no serán reconocidas luego del plazo establecido para su presentación. Una vez que este plazo se haya cumplido, habrás renunciado a la posibilidad de reclamar un reembolso por el crédito que te hubiera correspondido. - -Para recibir un reembolso, debes enviar una solicitud de crédito completa a . Para ser aceptada, la solicitud de crédito debe cumplir con las siguientes condiciones: -- Enviarse desde una dirección de correo electrónico que esté asociada a tu cuenta {% data variables.product.product_name %} -- Ser recibida por {% data variables.product.company_short %} en el plazo de 30 días a partir del cierre del trimestre en el que se produjeron los cuatro créditos calificados -- Pon "Credit Request" en la línea de asunto - -La siguiente información **se debe incluir** en tu solicitud de crédito: -- **Fecha** (la fecha debe estar comprendida en un plazo de 30 días a partir del cierre del trimestre de acuerdo con el cierre del año fiscal de {% data variables.product.company_short %} durante el que cual se produjeron los créditos que se reclaman [31 de enero, 30 de abril, 31 de julio o 31 de octubre]) -- **Contacto del cliente** (Debes especificar tanto el nombre como la dirección de correo electrónico) -- **Domicilio del cliente** -- **Créditos calificados**(Debes indicar la fecha de cada crédito calificado y el número de ticket asociado){% if currentVersion == "free-pro-team@latest" %} -- **Nombre de la organización {% data variables.product.prodname_ghe_cloud %}**{% endif %} -- **Número de ticket** diff --git a/translations/es-XL/data/reusables/support/scope-of-support.md b/translations/es-XL/data/reusables/support/scope-of-support.md deleted file mode 100644 index d0c2715abb..0000000000 --- a/translations/es-XL/data/reusables/support/scope-of-support.md +++ /dev/null @@ -1,12 +0,0 @@ - -### Alcance del soporte técnico - -Si tu solicitud de soporte técnico está fuera del alcance de lo que puede hacer nuestro equipo para ayudarte, podemos recomendarte los siguientes pasos para resolver el problema por fuera del {% data variables.contact.github_support %}. Es probable que tu solicitud de soporte técnico esté fuera del alcance del {% data variables.contact.github_support %} si se trata principalmente de lo siguiente: -- Integraciones de terceros -- Configuración del hardware -- CI/CD, como Jenkins -- Escribir scripts -- Configuración de sistemas de autenticación externos, como proveedores de identidad SAML -- Proyectos de código abierto - -Si no estás seguro de si el problema está fuera de nuestro alcance, abre un ticket y nos complacerá ayudarte a determinar la mejor manera de continuar. diff --git a/translations/es-XL/data/reusables/support/service-level-agreement-response-times.md b/translations/es-XL/data/reusables/support/service-level-agreement-response-times.md deleted file mode 100644 index 41074acba9..0000000000 --- a/translations/es-XL/data/reusables/support/service-level-agreement-response-times.md +++ /dev/null @@ -1,8 +0,0 @@ -### Tiempos de respuesta del Acuerdo de nivel de servicio - -Para los tickets que envías, el soporte técnico está disponible las 24 horas del día, los 7 días de la semana. El tiempo de respuesta inicial que garantiza el SLA depende del nivel de prioridad del ticket. El tiempo de respuesta comienza cuando {% data variables.contact.premium_support %} elige el nivel de prioridad del ticket. Una respuesta no implica que el problema se haya resuelto. - -| Nivel de prioridad del ticket | Tiempo de respuesta inicial | -| ------------------------------------------------------------------ | --------------------------- | -| {% data variables.product.support_ticket_priority_urgent %} | 30 minutos | -| {% data variables.product.support_ticket_priority_high %} | 4 horas | diff --git a/translations/es-XL/data/reusables/support/signing-up-for-premium-support.md b/translations/es-XL/data/reusables/support/signing-up-for-premium-support.md deleted file mode 100644 index ce37d5581c..0000000000 --- a/translations/es-XL/data/reusables/support/signing-up-for-premium-support.md +++ /dev/null @@ -1,4 +0,0 @@ - -### Registrarse en el {% data variables.contact.premium_support %} - -Para registrarte en {% data variables.contact.premium_support %} o actualizar tu plan, puedes [ponerte en contacto con nuestro equipo de administración de cuentas](https://enterprise.github.com/contact) o llamar a [+1 (877) 448-4820](tel:+1-877-448-4820). diff --git a/translations/es-XL/data/reusables/time_date/date_format.md b/translations/es-XL/data/reusables/time_date/date_format.md deleted file mode 100644 index 9644f0e2f9..0000000000 --- a/translations/es-XL/data/reusables/time_date/date_format.md +++ /dev/null @@ -1 +0,0 @@ -El formato de fecha debe seguir el estándar [ISO8601](http://en.wikipedia.org/wiki/ISO_8601), el cual es `YYYY-MM-DD` (año-mes-día). diff --git a/translations/es-XL/data/reusables/time_date/time_format.md b/translations/es-XL/data/reusables/time_date/time_format.md deleted file mode 100644 index 10c6a4fc54..0000000000 --- a/translations/es-XL/data/reusables/time_date/time_format.md +++ /dev/null @@ -1 +0,0 @@ -También puedes agregar información de tiempo ocpional `THH:MM:SS+00:00` después de la fecha, para buscar por hora, minuto y segundo. Se hace agregando `T`, seguido de `HH:MM:SS` (hora-minutos-segundos), y un intervalo de UTC (`+00:00`). diff --git a/translations/es-XL/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md b/translations/es-XL/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md deleted file mode 100644 index 5ee02e8903..0000000000 --- a/translations/es-XL/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md +++ /dev/null @@ -1 +0,0 @@ -No se soporta o administra en el aplicativo de {% data variables.product.prodname_ghe_server %}, pero puede que sí lo haga el proveedor de autenticación externo. No está disponible la implementación de la autenticación de dos factores en organizaciones. diff --git a/translations/es-XL/data/reusables/two_fa/about-recovery-codes.md b/translations/es-XL/data/reusables/two_fa/about-recovery-codes.md deleted file mode 100644 index 2022d3b128..0000000000 --- a/translations/es-XL/data/reusables/two_fa/about-recovery-codes.md +++ /dev/null @@ -1 +0,0 @@ -Cuando configuras la autenticación bifactorial, descargarás y guardarás los códigos de recuperación de dos factores. Si pierdes acceso a tu teléfono, puedes autenticarte en {% data variables.product.product_name %} utilizando tus códigos de recuperación. diff --git a/translations/es-XL/data/reusables/two_fa/after-2fa-add-security-key.md b/translations/es-XL/data/reusables/two_fa/after-2fa-add-security-key.md deleted file mode 100644 index 9c7e97b920..0000000000 --- a/translations/es-XL/data/reusables/two_fa/after-2fa-add-security-key.md +++ /dev/null @@ -1 +0,0 @@ -Después de que configuras la autenticación bifactorial utilizando una app móvil{% if currentVersion == "free-pro-team@latest" %} o a través de mensaje de texto{% endif %}, puedes agregar una llave de seguridad, como un lector de huella digital o Windows hello. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}La tecnología que habilita la autenticación con una llave de seguridad se llama WebAuthn. WebAuthn es el sucesor de la autenticación bifactorial y funciona en todos los buscadores modernos. Para obtener más información, consulta "[WebAuthn](https://webauthn.guide/)" y "[Can I Use](https://caniuse.com/#search=webauthn)."{% else %} la autenticación FIDO U2F solo se encuentra disponible actualmente para los buscadores Chrome, Firefox, y Opera.{% endif %} diff --git a/translations/es-XL/data/reusables/two_fa/auth_methods_2fa.md b/translations/es-XL/data/reusables/two_fa/auth_methods_2fa.md deleted file mode 100644 index 95203e259c..0000000000 --- a/translations/es-XL/data/reusables/two_fa/auth_methods_2fa.md +++ /dev/null @@ -1,10 +0,0 @@ -{% if currentVersion != "free-pro-team@latest" %} -### Métodos de autenticación que admiten la 2FA - -| Método de autenticación | Descripción | Soporte técnico de la autenticación de dos factores | -| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Incorporada | La autenticación se realiza para las cuentas de usuario que están almacenadas en el aparato del {% data variables.product.prodname_ghe_server %}. | Recibe soporte técnico y se administra en el aparato del {% data variables.product.prodname_ghe_server %}. Los administradores de la organización pueden solicitar que se habilite la 2FA para los miembros de la organización. |{% if currentVersion != "free-pro-team@latest" %} -| Autenticación incorporada con un proveedor de identidad | La autenticación se realiza para las cuentas de usuario que están almacenadas en el proveedor de identidad. | Depende del proveedor de identidad.{% endif %} -| LDAP | Permite la integración con el servicio de directorio de tu empresa para la autenticación. | Recibe soporte técnico y se administra en el aparato del {% data variables.product.prodname_ghe_server %}. Los administradores de la organización pueden solicitar que se habilite la 2FA para los miembros de la organización. | -| SAML | La autenticación se realiza en un proveedor de identidad externo. | {% data reusables.two_fa.2fa_not_supported_with_saml_and_cas %} | -| CAS | El servicio de inicio de sesión único lo proporciona un servidor externo. | {% data reusables.two_fa.2fa_not_supported_with_saml_and_cas %}{% endif %} diff --git a/translations/es-XL/data/reusables/two_fa/enable-two-factor-authentication.md b/translations/es-XL/data/reusables/two_fa/enable-two-factor-authentication.md deleted file mode 100644 index b2a1c4d7e3..0000000000 --- a/translations/es-XL/data/reusables/two_fa/enable-two-factor-authentication.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Autenticación bifactorial", da clic en **Habilitar la autenticación bifactorial**. ![Habilitar la opción de autenticación bifactorial](/assets/images/help/2fa/enable-two-factor-authentication-dialoge.png) diff --git a/translations/es-XL/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md b/translations/es-XL/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md deleted file mode 100644 index 7f1044ef03..0000000000 --- a/translations/es-XL/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md +++ /dev/null @@ -1,5 +0,0 @@ -6. Guarda tus códigos de recuperación en un lugar seguro. Tus códigos de recuperación te ayudarán a regresar a tu cuenta si pierdes acceso. - - Para guardar tus códigos de recuperación en tu dispositivo, haz clic en **Download** (Descargar). - - Para guardar una copia impresa de tus códigos de recuperación, haz clic en **Print** (Imprimir). - - Para copiar tus códigos de recuperación a fin de almacenarlo en un administrador de contraseñas, haz clic en **Copy** (Copiar). ![Lista de códigos de recuperación con opción para descargar, imprimir o copiar los códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) -7. Después de guardar tu código de recuperación de dos factores, haz clic en **Next** (Siguiente). diff --git a/translations/es-XL/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md b/translations/es-XL/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md deleted file mode 100644 index 64e9b815c0..0000000000 --- a/translations/es-XL/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Puedes enviar una invitación para reinstalar los privilegios del usuario y el acceso a la organización antes de que hayan habilitado la autenticación bifactorial. Los usuarios deben habilitar dicha autenticación antes de aceptar tu invitación de unirse nuevamente a la organización. -{% endif %} diff --git a/translations/es-XL/data/reusables/two_fa/show-recovery-codes.md b/translations/es-XL/data/reusables/two_fa/show-recovery-codes.md deleted file mode 100644 index 04e5957a89..0000000000 --- a/translations/es-XL/data/reusables/two_fa/show-recovery-codes.md +++ /dev/null @@ -1 +0,0 @@ -1. A un costado de "Códigos de recuperación", da clic en **Mostrar**. ![Botón para mostrar los códigos de recuperación](/assets/images/help/2fa/show-recovery-codes-button.png) diff --git a/translations/es-XL/data/reusables/two_fa/support-may-not-help.md b/translations/es-XL/data/reusables/two_fa/support-may-not-help.md deleted file mode 100644 index 122f6807aa..0000000000 --- a/translations/es-XL/data/reusables/two_fa/support-may-not-help.md +++ /dev/null @@ -1 +0,0 @@ -Por razones de seguridad, la Asistencia de {% data variables.product.product_name %} no puede restaurar el acceso a las cuentas con autenticación de dos factores habilitada si pierdes tus credenciales de autenticación de dos factores o si pierdes acceso a los métodos de recuperación de tu cuenta. diff --git a/translations/es-XL/data/reusables/two_fa/test_2fa_immediately.md b/translations/es-XL/data/reusables/two_fa/test_2fa_immediately.md deleted file mode 100644 index 60792f0f61..0000000000 --- a/translations/es-XL/data/reusables/two_fa/test_2fa_immediately.md +++ /dev/null @@ -1 +0,0 @@ -1. Después de que hayas guardado tus códigos de recuperación y hayas habilitado la autenticación bifactorial, te recomendamos salir y volver a entrar en tu cuenta. En caso de encontrar problemas tales como olvidar tu contraseña o un error de escritura en tu dirección de correo electrónico, puedes utilizar los códigos de recuperación para acceder a tu cuenta y corregir el problema. diff --git a/translations/es-XL/data/reusables/two_fa/username-password.md b/translations/es-XL/data/reusables/two_fa/username-password.md deleted file mode 100644 index b188dd4c97..0000000000 --- a/translations/es-XL/data/reusables/two_fa/username-password.md +++ /dev/null @@ -1 +0,0 @@ -1. Teclea tu nombre de usuario y contraseña en el prompt de autenticación. diff --git a/translations/es-XL/data/reusables/user-settings/access_settings.md b/translations/es-XL/data/reusables/user-settings/access_settings.md deleted file mode 100644 index f38634500b..0000000000 --- a/translations/es-XL/data/reusables/user-settings/access_settings.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en **Configuración**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/settings/userbar-account-settings_post2dot12.png) diff --git a/translations/es-XL/data/reusables/user-settings/developer_settings.md b/translations/es-XL/data/reusables/user-settings/developer_settings.md deleted file mode 100644 index d2c0a1b661..0000000000 --- a/translations/es-XL/data/reusables/user-settings/developer_settings.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Developer settings** (Parámetros del desarrollador). ![Sección Developer settings (Parámetros del programador)](/assets/images/settings/developer_settings.png) diff --git a/translations/es-XL/data/reusables/user-settings/edit_marketplace_listing.md b/translations/es-XL/data/reusables/user-settings/edit_marketplace_listing.md deleted file mode 100644 index 8fbdcdb4c6..0000000000 --- a/translations/es-XL/data/reusables/user-settings/edit_marketplace_listing.md +++ /dev/null @@ -1 +0,0 @@ -5. Desplázate hacia abajo a la sección de Marketplace y da clic en **Editar listado de Marketplace**. La sección de Marketplace solo se encuentra visible si permites que cualquier usuario u organización instale tu app cuando la registras. Para obtener más información, consulta la lista de [Requisitos de Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/). ![enlace para editar tu listado de GitHub Marketplace](/assets/images/marketplace/marketplace_edit_listing_text.png) diff --git a/translations/es-XL/data/reusables/user-settings/github_apps.md b/translations/es-XL/data/reusables/user-settings/github_apps.md deleted file mode 100644 index bab3732063..0000000000 --- a/translations/es-XL/data/reusables/user-settings/github_apps.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **GitHub Apps**. ![Sección GitHub Apps](/assets/images/settings/github_apps.png) diff --git a/translations/es-XL/data/reusables/user-settings/github_apps_advanced.md b/translations/es-XL/data/reusables/user-settings/github_apps_advanced.md deleted file mode 100644 index c7362fc03a..0000000000 --- a/translations/es-XL/data/reusables/user-settings/github_apps_advanced.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Avanzado**. ![pestaña de avanzado](/assets/images/github-apps/github_apps_advanced.png) diff --git a/translations/es-XL/data/reusables/user-settings/marketplace_apps.md b/translations/es-XL/data/reusables/user-settings/marketplace_apps.md deleted file mode 100644 index a8d57ea850..0000000000 --- a/translations/es-XL/data/reusables/user-settings/marketplace_apps.md +++ /dev/null @@ -1,4 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -1. En la barra lateral izquierda, da clic ya sea en **Apps de OAuth** o en **GitHub Apps** dependiendo del listado de {% data variables.product.prodname_marketplace %} que quieras administrar. **Nota:** También puedes administrar tu listado si navegas a https://github.com/marketplace/manage. ![Selección del tipo de app](/assets/images/settings/apps_choose_app.png) - -{% endif %} diff --git a/translations/es-XL/data/reusables/user-settings/modify_github_app.md b/translations/es-XL/data/reusables/user-settings/modify_github_app.md deleted file mode 100644 index a7a099365f..0000000000 --- a/translations/es-XL/data/reusables/user-settings/modify_github_app.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecciona la GitHub App que quieres modificar. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) diff --git a/translations/es-XL/data/reusables/user-settings/modify_oauth_app.md b/translations/es-XL/data/reusables/user-settings/modify_oauth_app.md deleted file mode 100644 index 53ce1f3abf..0000000000 --- a/translations/es-XL/data/reusables/user-settings/modify_oauth_app.md +++ /dev/null @@ -1 +0,0 @@ -1. Selecciona la {% data variables.product.prodname_oauth_app %} que quieres modificar. ![Seleccion de apps](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) diff --git a/translations/es-XL/data/reusables/user-settings/oauth_apps.md b/translations/es-XL/data/reusables/user-settings/oauth_apps.md deleted file mode 100644 index e902161c02..0000000000 --- a/translations/es-XL/data/reusables/user-settings/oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Apps de OAuth**. ![Sección de la App de OAuth](/assets/images/settings/oauth_apps_post2dot12.png) diff --git a/translations/es-XL/data/reusables/user-settings/update_oauth_app.md b/translations/es-XL/data/reusables/user-settings/update_oauth_app.md deleted file mode 100644 index 56d16c6109..0000000000 --- a/translations/es-XL/data/reusables/user-settings/update_oauth_app.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Actualizar aplicación**. ![Botón para actualizar la aplicación](/assets/images/oauth-apps/oauth_apps_update_application.png) diff --git a/translations/es-XL/data/reusables/user_settings/about-commit-email-addresses.md b/translations/es-XL/data/reusables/user_settings/about-commit-email-addresses.md deleted file mode 100644 index c1d07e7683..0000000000 --- a/translations/es-XL/data/reusables/user_settings/about-commit-email-addresses.md +++ /dev/null @@ -1 +0,0 @@ -For more information on commit email addresses,{% if currentVersion == "free-pro-team@latest" %} including your {% data variables.product.product_name %}-provided `noreply` email address,{% endif %} see "[Setting your commit email address](/articles/setting-your-commit-email-address)." diff --git a/translations/es-XL/data/reusables/user_settings/access_applications.md b/translations/es-XL/data/reusables/user_settings/access_applications.md deleted file mode 100644 index 090911a90e..0000000000 --- a/translations/es-XL/data/reusables/user_settings/access_applications.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Applications** (Aplicaciones). ![Pestaña de aplicaciones](/assets/images/help/settings/settings-applications.png) diff --git a/translations/es-XL/data/reusables/user_settings/access_authorized_oauth_apps.md b/translations/es-XL/data/reusables/user_settings/access_authorized_oauth_apps.md deleted file mode 100644 index dc25de86aa..0000000000 --- a/translations/es-XL/data/reusables/user_settings/access_authorized_oauth_apps.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en la pestaña **Aplicaciones OAuth Autorizadas**. ![Pestaña de Aplicaciones OAuth autorizadas](/assets/images/help/settings/settings-authorized-oauth-apps-tab.png) diff --git a/translations/es-XL/data/reusables/user_settings/access_settings.md b/translations/es-XL/data/reusables/user_settings/access_settings.md deleted file mode 100644 index d39891130f..0000000000 --- a/translations/es-XL/data/reusables/user_settings/access_settings.md +++ /dev/null @@ -1 +0,0 @@ -1. En la esquina superior derecha de cualquier página, da clic en tu foto de perfil y después da clic en **Configuración**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/es-XL/data/reusables/user_settings/account_settings.md b/translations/es-XL/data/reusables/user_settings/account_settings.md deleted file mode 100644 index c38c7bbe42..0000000000 --- a/translations/es-XL/data/reusables/user_settings/account_settings.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Cuenta**. ![Opción de menú de configuración de cuenta](/assets/images/help/settings/settings-sidebar-account-settings.png) diff --git a/translations/es-XL/data/reusables/user_settings/add_and_verify_email.md b/translations/es-XL/data/reusables/user_settings/add_and_verify_email.md deleted file mode 100644 index b447e92598..0000000000 --- a/translations/es-XL/data/reusables/user_settings/add_and_verify_email.md +++ /dev/null @@ -1,2 +0,0 @@ -1. En "Agregar dirección de correo electrónico", teclea tu dirección de correo electrónico y da clic en **Agregar**. ![Email addition button](/assets/images/help/settings/add-email-address.png){% if currentVersion == "free-pro-team@latest" %} -2. [Verifica tu dirección de correo electrónico](/articles/verifying-your-email-address).{% endif %} diff --git a/translations/es-XL/data/reusables/user_settings/automatic_watching_box.md b/translations/es-XL/data/reusables/user_settings/automatic_watching_box.md deleted file mode 100644 index a4c5ce0d12..0000000000 --- a/translations/es-XL/data/reusables/user_settings/automatic_watching_box.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Observar automáticamente", diff --git a/translations/es-XL/data/reusables/user_settings/billing.md b/translations/es-XL/data/reusables/user_settings/billing.md deleted file mode 100644 index fc5108d5f6..0000000000 --- a/translations/es-XL/data/reusables/user_settings/billing.md +++ /dev/null @@ -1 +0,0 @@ -1. En tu barra lateral de configuración de usuario, da clic en **Facturación**. ![Configuración de facturación](/assets/images/help/settings/settings-sidebar-billing.png) diff --git a/translations/es-XL/data/reusables/user_settings/blocked_users.md b/translations/es-XL/data/reusables/user_settings/blocked_users.md deleted file mode 100644 index 6ad845af3d..0000000000 --- a/translations/es-XL/data/reusables/user_settings/blocked_users.md +++ /dev/null @@ -1 +0,0 @@ -1. En tu barra lateral de configuración, da clic en **Usuarios bloqueados**. ![Pestaña de usuarios bloqueados](/assets/images/help/settings/settings-sidebar-blocked-users.png) diff --git a/translations/es-XL/data/reusables/user_settings/confirm_git_email_address_correct.md b/translations/es-XL/data/reusables/user_settings/confirm_git_email_address_correct.md deleted file mode 100644 index ec6e3181f3..0000000000 --- a/translations/es-XL/data/reusables/user_settings/confirm_git_email_address_correct.md +++ /dev/null @@ -1 +0,0 @@ -Confirma que has establecido correctamente la dirección de correo electrónico en Git: diff --git a/translations/es-XL/data/reusables/user_settings/confirm_git_username_correct.md b/translations/es-XL/data/reusables/user_settings/confirm_git_username_correct.md deleted file mode 100644 index 069f35f72c..0000000000 --- a/translations/es-XL/data/reusables/user_settings/confirm_git_username_correct.md +++ /dev/null @@ -1 +0,0 @@ -Confirma que has establecido correctamente el nombre de usuario en Git: diff --git a/translations/es-XL/data/reusables/user_settings/cost-management-tab.md b/translations/es-XL/data/reusables/user_settings/cost-management-tab.md deleted file mode 100644 index a1ab891af1..0000000000 --- a/translations/es-XL/data/reusables/user_settings/cost-management-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Facturación", da clic en **Administración de costos**. ![Pestaña de administración de costos](/assets/images/help/settings/cost-management-tab.png) diff --git a/translations/es-XL/data/reusables/user_settings/deleted-repos.md b/translations/es-XL/data/reusables/user_settings/deleted-repos.md deleted file mode 100644 index db48d0f662..0000000000 --- a/translations/es-XL/data/reusables/user_settings/deleted-repos.md +++ /dev/null @@ -1 +0,0 @@ -1. Debajo de "Repositorios", da clic en **Repositorios borrados**". ![Pestaña de repositorios borrados](/assets/images/help/settings/deleted-repos.png) diff --git a/translations/es-XL/data/reusables/user_settings/developer_settings.md b/translations/es-XL/data/reusables/user_settings/developer_settings.md deleted file mode 100644 index e1268dd5a0..0000000000 --- a/translations/es-XL/data/reusables/user_settings/developer_settings.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Developer settings** (Parámetros del desarrollador). ![Configuración de desarrollador](/assets/images/help/settings/developer-settings.png) diff --git a/translations/es-XL/data/reusables/user_settings/emails.md b/translations/es-XL/data/reusables/user_settings/emails.md deleted file mode 100644 index 793d3d5e6e..0000000000 --- a/translations/es-XL/data/reusables/user_settings/emails.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Correos Electrónicos**. ![Pestaña de correos electrónicos](/assets/images/help/settings/settings-sidebar-emails.png) diff --git a/translations/es-XL/data/reusables/user_settings/export-data.md b/translations/es-XL/data/reusables/user_settings/export-data.md deleted file mode 100644 index 8f76541546..0000000000 --- a/translations/es-XL/data/reusables/user_settings/export-data.md +++ /dev/null @@ -1,3 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %} -Puedes exportar y revisar los metadatos que almacena {% data variables.product.product_name %} sobre tu cuenta personal. -{% endif %} diff --git a/translations/es-XL/data/reusables/user_settings/jira_help_docs.md b/translations/es-XL/data/reusables/user_settings/jira_help_docs.md deleted file mode 100644 index 6de6f0f30d..0000000000 --- a/translations/es-XL/data/reusables/user_settings/jira_help_docs.md +++ /dev/null @@ -1 +0,0 @@ -1. Vincula tu cuenta de GitHub con Jira. Para obtener más información, consulta la [Documentación de ayuda de Atlassian](https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html). diff --git a/translations/es-XL/data/reusables/user_settings/keeping_your_email_address_private.md b/translations/es-XL/data/reusables/user_settings/keeping_your_email_address_private.md deleted file mode 100644 index 522e297d61..0000000000 --- a/translations/es-XL/data/reusables/user_settings/keeping_your_email_address_private.md +++ /dev/null @@ -1 +0,0 @@ -5. Para mantener tu dirección de correo electrónico como privada cuando realices operaciones de Git basadas en la web, da clic en **Mantener mi dirección de correo electrónico como privada**. ![Imagen de casilla para mantener tu dirección de correo electrónico como privada](/assets/images/help/settings/email_privacy.png) diff --git a/translations/es-XL/data/reusables/user_settings/link_email_with_your_account.md b/translations/es-XL/data/reusables/user_settings/link_email_with_your_account.md deleted file mode 100644 index 2dfca4929c..0000000000 --- a/translations/es-XL/data/reusables/user_settings/link_email_with_your_account.md +++ /dev/null @@ -1 +0,0 @@ -Agrega la dirección de correo electrónico a tu cuenta de {% data variables.product.product_name %} mediante la [configuración de tu dirección de correo electrónico para confirmaciones](/articles/setting-your-commit-email-address) para que dichas confirmaciones se te atribuyan y aparezcan en tu gráfica de contribuciones. diff --git a/translations/es-XL/data/reusables/user_settings/no-verification-disposable-emails.md b/translations/es-XL/data/reusables/user_settings/no-verification-disposable-emails.md deleted file mode 100644 index 715c021592..0000000000 --- a/translations/es-XL/data/reusables/user_settings/no-verification-disposable-emails.md +++ /dev/null @@ -1 +0,0 @@ -No puedes verificar una dirección de correo electrónico de dominios desechables. Si te gustaría mantener tu dirección de correo electrónico como privada, puedes utilizar la dirección de correo electrónico de `noreply` proporcionada por {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Configurar tu dirección de correo electrónico para confirmaciones en {% data variables.product.prodname_dotcom %}](/articles/setting-your-commit-email-address#setting-your-commit-email-address-on-github)". diff --git a/translations/es-XL/data/reusables/user_settings/notifications.md b/translations/es-XL/data/reusables/user_settings/notifications.md deleted file mode 100644 index e44f6f590b..0000000000 --- a/translations/es-XL/data/reusables/user_settings/notifications.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de la configuración de usuario, da clic en **Notificaciones**. ![Centro de notificaciones](/assets/images/help/settings/settings-sidebar-notifications.png) diff --git a/translations/es-XL/data/reusables/user_settings/organizations.md b/translations/es-XL/data/reusables/user_settings/organizations.md deleted file mode 100644 index 78aed7402b..0000000000 --- a/translations/es-XL/data/reusables/user_settings/organizations.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de configuración de usuario, da clic en **Organizaciones**. ![Configuración de usuario para organizaciones](/assets/images/help/settings/settings-user-orgs.png) diff --git a/translations/es-XL/data/reusables/user_settings/password-authentication-deprecation-desktop.md b/translations/es-XL/data/reusables/user_settings/password-authentication-deprecation-desktop.md deleted file mode 100644 index 9c46a6be7d..0000000000 --- a/translations/es-XL/data/reusables/user_settings/password-authentication-deprecation-desktop.md +++ /dev/null @@ -1,5 +0,0 @@ - {% warning %} - - **Advertencia**: Autenticarse en {% data variables.product.prodname_dotcom %} utilizand tu nombre de usuario y contraseña está en desuso. En vez de esto, te recomendamos autenticarte utilizando el buscador. - - {% endwarning %} diff --git a/translations/es-XL/data/reusables/user_settings/password-authentication-deprecation.md b/translations/es-XL/data/reusables/user_settings/password-authentication-deprecation.md deleted file mode 100644 index 58d028459a..0000000000 --- a/translations/es-XL/data/reusables/user_settings/password-authentication-deprecation.md +++ /dev/null @@ -1 +0,0 @@ -La autenticación basada en contraseña para Git es ahora obsoleta y te recomendamos utilizar un token de acceso personal (PAT) en sustitución cuando se te pida la contraseña, lo cual es más seguro. Trata a tu token tal como lo harías con una contraseña. 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)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/user_settings/payment-info-tab.md b/translations/es-XL/data/reusables/user_settings/payment-info-tab.md deleted file mode 100644 index 5bcf1150fc..0000000000 --- a/translations/es-XL/data/reusables/user_settings/payment-info-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Información de pago**. ![Pestaña de información de pago](/assets/images/help/settings/payment-info-tab.png) diff --git a/translations/es-XL/data/reusables/user_settings/personal_access_tokens.md b/translations/es-XL/data/reusables/user_settings/personal_access_tokens.md deleted file mode 100644 index e7421efd7a..0000000000 --- a/translations/es-XL/data/reusables/user_settings/personal_access_tokens.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Tokens de acceso personal**. ![Tokens de acceso personal](/assets/images/help/settings/personal_access_tokens_tab.png) diff --git a/translations/es-XL/data/reusables/user_settings/personal_dashboard.md b/translations/es-XL/data/reusables/user_settings/personal_dashboard.md deleted file mode 100644 index 2442ecd7f1..0000000000 --- a/translations/es-XL/data/reusables/user_settings/personal_dashboard.md +++ /dev/null @@ -1 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" %}[tablero personal](https://github.com/dashboard){% else %} tablero personal (`https://[hostname]/dashboard`){% endif %} diff --git a/translations/es-XL/data/reusables/user_settings/removes-personal-access-tokens.md b/translations/es-XL/data/reusables/user_settings/removes-personal-access-tokens.md deleted file mode 100644 index 307f8f807e..0000000000 --- a/translations/es-XL/data/reusables/user_settings/removes-personal-access-tokens.md +++ /dev/null @@ -1 +0,0 @@ -Como precaución de seguridad, {% data variables.product.prodname_dotcom %} elimina automáticamente los tokens de acceso personales que no se han usado durante un año. diff --git a/translations/es-XL/data/reusables/user_settings/repo-tab.md b/translations/es-XL/data/reusables/user_settings/repo-tab.md deleted file mode 100644 index bbf235fd23..0000000000 --- a/translations/es-XL/data/reusables/user_settings/repo-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, haz clic en **Repositories** (Repositorios). ![Pestaña Repositories (Repositorios)](/assets/images/help/settings/repos-tab.png) diff --git a/translations/es-XL/data/reusables/user_settings/restore-confirmation.md b/translations/es-XL/data/reusables/user_settings/restore-confirmation.md deleted file mode 100644 index feb88597f5..0000000000 --- a/translations/es-XL/data/reusables/user_settings/restore-confirmation.md +++ /dev/null @@ -1 +0,0 @@ -1. Lee la advertencia y da clic en **Entiendo, restaurar este repositorio**. ![Botón para confirmar restauración](/assets/images/help/settings/confirm-restoration-button.png) diff --git a/translations/es-XL/data/reusables/user_settings/restore-repo.md b/translations/es-XL/data/reusables/user_settings/restore-repo.md deleted file mode 100644 index 81ad52fe06..0000000000 --- a/translations/es-XL/data/reusables/user_settings/restore-repo.md +++ /dev/null @@ -1 +0,0 @@ -1. Junto al repositorio que quieres restaurar, da clic en **Restaurar**. ![Botón de restaurar](/assets/images/help/settings/restore-button.png) diff --git a/translations/es-XL/data/reusables/user_settings/review-oauth-apps.md b/translations/es-XL/data/reusables/user_settings/review-oauth-apps.md deleted file mode 100644 index b052fef60f..0000000000 --- a/translations/es-XL/data/reusables/user_settings/review-oauth-apps.md +++ /dev/null @@ -1 +0,0 @@ -1. Revisa los tokens que tienen acceso a tu cuenta. Para aquellos que no reconoces o que han caducado, da clic en **{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}**, y luego en **Revocar**. Para revocar todos los tokens, da clic en **Revocar todos**. ![Lista de {% data variables.product.prodname_oauth_app %} autorizadas](/assets/images/help/settings/revoke-oauth-app.png) diff --git a/translations/es-XL/data/reusables/user_settings/review_oauth_tokens_tip.md b/translations/es-XL/data/reusables/user_settings/review_oauth_tokens_tip.md deleted file mode 100644 index 9f2210b237..0000000000 --- a/translations/es-XL/data/reusables/user_settings/review_oauth_tokens_tip.md +++ /dev/null @@ -1 +0,0 @@ -Te recomendamos que revises frecuentemente tus integraciones autorizadas. Elimina cualquier aplicación y tokens que no se hayan utilizado en mucho tiempo. Para obtener más información, consulta la sección "[Revisar tus integraciones autorizadas](/articles/reviewing-your-authorized-integrations)". diff --git a/translations/es-XL/data/reusables/user_settings/saved_replies.md b/translations/es-XL/data/reusables/user_settings/saved_replies.md deleted file mode 100644 index e021c903da..0000000000 --- a/translations/es-XL/data/reusables/user_settings/saved_replies.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Respuestas guardadas**. ![Pestaña de respuestas guardadas](/assets/images/help/settings/saved-replies-tab.png) diff --git a/translations/es-XL/data/reusables/user_settings/security-analysis.md b/translations/es-XL/data/reusables/user_settings/security-analysis.md deleted file mode 100644 index 833c5cd4ed..0000000000 --- a/translations/es-XL/data/reusables/user_settings/security-analysis.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral izquierda, da clic en **Seguridad & análisis**. ![Configuración de análisis y seguridad](/assets/images/help/settings/settings-sidebar-security-analysis.png) diff --git a/translations/es-XL/data/reusables/user_settings/security.md b/translations/es-XL/data/reusables/user_settings/security.md deleted file mode 100644 index 7acbee4a79..0000000000 --- a/translations/es-XL/data/reusables/user_settings/security.md +++ /dev/null @@ -1,4 +0,0 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}1. En la barra lateral izquierda, da clic en **Seguridad de cuenta**. -![Configuración de seguridad para la cuenta del usuario](/assets/images/help/settings/settings-sidebar-account-security.png) -{% else %}1. En la barra lateral izquierda, haz clic en **Security** (Seguridad). -![Configuración de seguridad para la cuenta del usuario](/assets/images/help/settings/settings-sidebar-security.png){% endif %} diff --git a/translations/es-XL/data/reusables/user_settings/select_primary_email.md b/translations/es-XL/data/reusables/user_settings/select_primary_email.md deleted file mode 100644 index 4414ceb0a4..0000000000 --- a/translations/es-XL/data/reusables/user_settings/select_primary_email.md +++ /dev/null @@ -1 +0,0 @@ -1. En la lista de "Dirección de correo electrónico principal", selecciona la dirección que quieres asociar con tus operaciones de Git basadas en web. ![Selección de dirección de correo electrónico principal](/assets/images/help/settings/email_primary.png) diff --git a/translations/es-XL/data/reusables/user_settings/set_your_email_address_in_git.md b/translations/es-XL/data/reusables/user_settings/set_your_email_address_in_git.md deleted file mode 100644 index a49ac059e7..0000000000 --- a/translations/es-XL/data/reusables/user_settings/set_your_email_address_in_git.md +++ /dev/null @@ -1 +0,0 @@ -Configurar una dirección de correo electrónico en Git. Puedes utilizar {% if currentVersion == "free-pro-team@latest"%} tu [dirección de correo electrónico de `no-reply` proporcionada por {% data variables.product.product_name %}](/articles/setting-your-commit-email-address) o {% endif %} cualquier otra. diff --git a/translations/es-XL/data/reusables/user_settings/set_your_git_username.md b/translations/es-XL/data/reusables/user_settings/set_your_git_username.md deleted file mode 100644 index 5d4c47fcea..0000000000 --- a/translations/es-XL/data/reusables/user_settings/set_your_git_username.md +++ /dev/null @@ -1 +0,0 @@ -Establece un nombre de usuario en Git: diff --git a/translations/es-XL/data/reusables/user_settings/ssh.md b/translations/es-XL/data/reusables/user_settings/ssh.md deleted file mode 100644 index f646ee2d0d..0000000000 --- a/translations/es-XL/data/reusables/user_settings/ssh.md +++ /dev/null @@ -1 +0,0 @@ -1. En la barra lateral de configuración de usuario, da clic en **Llaves SSH y GPG**. ![Llaves de autenticación](/assets/images/help/settings/settings-sidebar-ssh-keys.png) diff --git a/translations/es-XL/data/reusables/user_settings/subscriptions-tab.md b/translations/es-XL/data/reusables/user_settings/subscriptions-tab.md deleted file mode 100644 index 1aeacc4ea2..0000000000 --- a/translations/es-XL/data/reusables/user_settings/subscriptions-tab.md +++ /dev/null @@ -1 +0,0 @@ -1. Da clic en **Suscripciones**. ![Pestaña Subscriptions (Suscripciones)](/assets/images/help/settings/subscriptions-tab.png) diff --git a/translations/es-XL/data/reusables/user_settings/sudo-mode-popup.md b/translations/es-XL/data/reusables/user_settings/sudo-mode-popup.md deleted file mode 100644 index 4c9b64d0fc..0000000000 --- a/translations/es-XL/data/reusables/user_settings/sudo-mode-popup.md +++ /dev/null @@ -1 +0,0 @@ -1. Si se te solicita, confirma tu contraseña {% data variables.product.product_name %}.![Diálogo Modo sudo](/assets/images/help/settings/sudo_mode_popup.png) \ No newline at end of file diff --git a/translations/es-XL/data/reusables/user_settings/verify-org-approved-email-domain.md b/translations/es-XL/data/reusables/user_settings/verify-org-approved-email-domain.md deleted file mode 100644 index d5e274fad2..0000000000 --- a/translations/es-XL/data/reusables/user_settings/verify-org-approved-email-domain.md +++ /dev/null @@ -1 +0,0 @@ -Si alguna organización de la cual eres miembro restringe las notificaciones por correo electrónico a un dominio de correo electrónico aprobado, deberás verificar la dirección en el dominio para recibir las notificaciones de actividad en la organización por este medio. Para obtener más información, consulta "[Restringir las notificaciones por correo electrónico a un dominio aprobado](/articles/restricting-email-notifications-to-an-approved-domain)". diff --git a/translations/es-XL/data/reusables/webhooks/action_type_desc.md b/translations/es-XL/data/reusables/webhooks/action_type_desc.md deleted file mode 100644 index 311ee7ae67..0000000000 --- a/translations/es-XL/data/reusables/webhooks/action_type_desc.md +++ /dev/null @@ -1 +0,0 @@ -El tipo de actividad se especifica en la propiedad `action` del objeto de la carga útil. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/app_desc.md b/translations/es-XL/data/reusables/webhooks/app_desc.md deleted file mode 100644 index 2d4a473fff..0000000000 --- a/translations/es-XL/data/reusables/webhooks/app_desc.md +++ /dev/null @@ -1 +0,0 @@ -`installation` | `object` | La instalación de {% data variables.product.prodname_github_app %}. Las cargas útiles de los webhooks contienen la propiedad `installation` cuando el evento se envía y se configura para una {% data variables.product.prodname_github_app %}. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/authorization_event.md b/translations/es-XL/data/reusables/webhooks/authorization_event.md deleted file mode 100644 index 89c9f52097..0000000000 --- a/translations/es-XL/data/reusables/webhooks/authorization_event.md +++ /dev/null @@ -1 +0,0 @@ -Cualquiera puede revocar su autorización a una GitHub App desde su [página de ajustes de cuenta de GitHub](https://github.com/settings/apps/authorizations). Revocar la autorización de una GitHub App no la desinstalará. Debes programar tu GitHub App para que cuando reciba su webhook deje de llamar a la API en nombre de la persona que revocó el token. Si tu GitHub App sigue utilizando un token de acceso revocado, esta recibirá el error `401 Bad Credentials`. diff --git a/translations/es-XL/data/reusables/webhooks/check_run_properties.md b/translations/es-XL/data/reusables/webhooks/check_run_properties.md deleted file mode 100644 index 5d5d485657..0000000000 --- a/translations/es-XL/data/reusables/webhooks/check_run_properties.md +++ /dev/null @@ -1,10 +0,0 @@ -| Clave | Tipo | Descripción | -| ------------------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes:
    • `created` - Se creó una ejecución de verificación.
    • `completed` - El `status` de la ejecución de verificación es `completed`.
    • `rerequested` - Alguien volvió a solicitar que se volviera a ejecutar tu ejecución de verificación desde la IU de la solicitud de extracción. Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub. Cuando recibes una acción como `rerequested`, necesitarás [crear una ejecución de verificación nueva](/v3/checks/runs/#create-a-check-run). Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó volver a ejecutar la verificación recibirá la carga útil de `rerequested`.
    • `requested_action` - Alguien volvió a solicitar que se tome una acción que proporciona tu app. Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó llevar a cabo una acción recibirá la carga útil de `requested_action`. Para aprender más sobre las ejecuciones de verificación y de las acciones solicitadas, consulta la sección "[Ejecuciones de verificación y acciones solicitadas](/v3/checks/runs/#check-runs-and-requested-actions)."
    | -| `check_run` | `objeto` | La [check_run](/v3/checks/runs/#get-a-check-run). | -| `check_run[status]` | `secuencia` | El estado actual de la ejecución de verificación. Puede ser `queued`, `in_progress`, o `completed`. | -| `check_run[conclusion]` | `secuencia` | El resultado de la ejecución de verificación que se completó. Puede ser una de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}`action_required` o `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | -| `check_run[name]` | `secuencia` | El nombre de la ejecución de verificación. | -| `check_run[check_suite][id]` | `número` | La id de la suite de verificaciones de la cual es parte esta ejecución de verificación. | -| `requested_action` | `objeto` | La acción que solicitó el usuario. | -| `requested_action[identifier]` | `secuencia` | La referencia del integrador de la acción que solicitó el usuario. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/check_run_short_desc.md b/translations/es-XL/data/reusables/webhooks/check_run_short_desc.md deleted file mode 100644 index 330f966929..0000000000 --- a/translations/es-XL/data/reusables/webhooks/check_run_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Ha ocurrido una actividad de ejecución de verificación. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[ejecuciones de verificación](/v3/checks/runs/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/check_suite_properties.md b/translations/es-XL/data/reusables/webhooks/check_suite_properties.md deleted file mode 100644 index 8d189a6002..0000000000 --- a/translations/es-XL/data/reusables/webhooks/check_suite_properties.md +++ /dev/null @@ -1,10 +0,0 @@ -| Clave | Tipo | Descripción | -| ---------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser:
    • `completed` - Todas las ejecuciones de verificación en una suite de verificación se completaron.
    • `requested` - Ocurre cuando se carga código nuevo al repositorio de la app. Cuadno recibas los eventos de la acción `requested`, necesitarás [crear una ejecución de verificación nueva](/v3/checks/runs/#create-a-check-run).
    • `rerequested` - Ocurre cuando alguien solicita volver a ejecutar toda la suite de verificaciones desde la IU de la solicitud de extracción. Cuando recibas los eventos de la acción `rerequested`, necesitarás [crear una ejecución de verificación nueva] (/v3/checks/runs/#create-a-check-run). Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub.
    | -| `check_suite` | `objeto` | La [check_suite](/v3/checks/suites/). | -| `check_suite[head_branch]` | `secuencia` | El nombre de la rama principal en la cual están los cambios. | -| `check_suite[head_sha]` | `secuencia` | El SHA de la confirmación más reciente para esta suite de verificaciones. | -| `check_suite[status]` | `secuencia` | El estado de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser `requested`, `in_progress`, o `completed`. | -| `check_suite[conclusion]` | `secuencia` | La conclusión de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser una de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %}`action_required` o `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | -| `check_suite[url]` | `secuencia` | La URL que apunta al recurso de la API de suite de verificación. | -| `check_suite[pull_requests]` | `array` | Una matriz de solicitudes de extracción que empatan con esta suite de verificaciones. Una solicitud de extracción que empata con una suite de verificaciones si tienen el mismo `head_sha` y `head_branch`. Cuando la `head_branch` de la suite de verificaciones está en un repositorio bifurcado, este será `null` y la matriz de `pull_requests` estará vacía. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/check_suite_short_desc.md b/translations/es-XL/data/reusables/webhooks/check_suite_short_desc.md deleted file mode 100644 index 6b16d8098a..0000000000 --- a/translations/es-XL/data/reusables/webhooks/check_suite_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Ha ocurrido una actividad de suite de verificaciones. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[suites de verificaciones](/v3/checks/suites/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/es-XL/data/reusables/webhooks/code_scanning_alert_event_properties.md deleted file mode 100644 index 61af71dbdc..0000000000 --- a/translations/es-XL/data/reusables/webhooks/code_scanning_alert_event_properties.md +++ /dev/null @@ -1,6 +0,0 @@ -| Clave | Tipo | Descripción | -| ------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. This can be one of `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch`, or `reopened`. | -| `alerta` | `objeto` | The code scanning alert involved in the event. | -| `ref` | `secuencia` | The Git reference of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty. | -| `commit_oid` | `secuencia` | The commit SHA of the code scanning alert. When the action is `reopened_by_user` or `closed_by_user`, the event was triggered by the `sender` and this value will be empty. | diff --git a/translations/es-XL/data/reusables/webhooks/code_scanning_alert_event_short_desc.md b/translations/es-XL/data/reusables/webhooks/code_scanning_alert_event_short_desc.md deleted file mode 100644 index e246022ed4..0000000000 --- a/translations/es-XL/data/reusables/webhooks/code_scanning_alert_event_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Activity related to code scanning alerts in a repository. The type of activity is specified in the action property of the payload object. For more information, see “[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning).” \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/commit_comment_properties.md b/translations/es-XL/data/reusables/webhooks/commit_comment_properties.md deleted file mode 100644 index 40e0b65076..0000000000 --- a/translations/es-XL/data/reusables/webhooks/commit_comment_properties.md +++ /dev/null @@ -1,4 +0,0 @@ -| Clave | Tipo | Descripción | -| ------------ | ----------- | ---------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser `created`. | -| `comentario` | `objeto` | El recurso de [comentario de la confirmación](/v3/repos/comments/#get-a-commit-comment). | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/commit_comment_short_desc.md b/translations/es-XL/data/reusables/webhooks/commit_comment_short_desc.md deleted file mode 100644 index 1970d7e84f..0000000000 --- a/translations/es-XL/data/reusables/webhooks/commit_comment_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Se creó un comentario de una confirmación. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[comentario de confirmación](/v3/repos/comments/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/content_reference_short_desc.md b/translations/es-XL/data/reusables/webhooks/content_reference_short_desc.md deleted file mode 100644 index 6e01a6af20..0000000000 --- a/translations/es-XL/data/reusables/webhooks/content_reference_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Una referencia de contenido nueva se muestra como `created`. Se crea una referenci de contenido nueva cuando el cuerpo o el comentario de un informe de problemas o solicitud de extracción incluye un URL que empte con un dominio de referencia de contenido configurado. Para obtener más información, consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments/)" para aprender más sobre las referencias de contenido y sus adjuntos. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/content_type.md b/translations/es-XL/data/reusables/webhooks/content_type.md deleted file mode 100644 index d26accf02a..0000000000 --- a/translations/es-XL/data/reusables/webhooks/content_type.md +++ /dev/null @@ -1,6 +0,0 @@ -Los webhooks pueden entregarse utilizando diferentes tipos de contenido: - -- El tipo de contenido `application/json` entregará la carga útil de JSON directametne como el cuerpo de la solicitud `POST`. -- El tipo de contenido `application/x-www-form-urlencoded` enviará la carga útil de JSON como un parámetro de forma llamado `payload`. - -Elige el que se adapte mejor a tus necesidades. diff --git a/translations/es-XL/data/reusables/webhooks/create_properties.md b/translations/es-XL/data/reusables/webhooks/create_properties.md deleted file mode 100644 index ff5dadf47f..0000000000 --- a/translations/es-XL/data/reusables/webhooks/create_properties.md +++ /dev/null @@ -1,6 +0,0 @@ -| Clave | Tipo | Descripción | -| --------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ref` | `secuencia` | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}El recurso [`git ref`](/v3/git/refs/#get-a-reference).{% else %}El recurso [`git ref`](/v3/git/refs/#get-a-reference).{% endif %} -| `ref_type` | `secuencia` | El tipo de objeto de Git ref que se creó en el repositorio. Puede ser `branch` o `tag`. | -| `master_branch` | `secuencia` | El nombre dela rama predeterminada del repositorio (a menudo `master`). | -| `descripción` | `secuencia` | La descripción actual del repositorio. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/create_short_desc.md b/translations/es-XL/data/reusables/webhooks/create_short_desc.md deleted file mode 100644 index 6b10732d78..0000000000 --- a/translations/es-XL/data/reusables/webhooks/create_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Se crea una rama o etiqueta de Git. Para obtener más información, consulta la API de REST de "[Datos de Git](/v3/git/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/delete_properties.md b/translations/es-XL/data/reusables/webhooks/delete_properties.md deleted file mode 100644 index 65a33de026..0000000000 --- a/translations/es-XL/data/reusables/webhooks/delete_properties.md +++ /dev/null @@ -1,4 +0,0 @@ -| Clave | Tipo | Descripción | -| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ref` | `secuencia` | {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}El recurso [`git ref`](/v3/git/refs/#get-a-reference).{% else %}El recurso [`git ref`](/v3/git/refs/#get-a-reference).{% endif %} -| `ref_type` | `secuencia` | El tipo de objeto de Git ref que se borró en el repositorio. Puede ser `branch` o `tag`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/delete_short_desc.md b/translations/es-XL/data/reusables/webhooks/delete_short_desc.md deleted file mode 100644 index b27b4c7ebd..0000000000 --- a/translations/es-XL/data/reusables/webhooks/delete_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Se borra una rama o etiqueta de Git. Para obtener más información, consulta la API de REST de "[Datos de Git](/v3/git/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/deploy_key_properties.md b/translations/es-XL/data/reusables/webhooks/deploy_key_properties.md deleted file mode 100644 index 48bd76e2d8..0000000000 --- a/translations/es-XL/data/reusables/webhooks/deploy_key_properties.md +++ /dev/null @@ -1,4 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | -------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser tanto `created` como `deleted`. | -| `clave` | `objeto` | El recurso [`deploy key`](/v3/repos/keys/#get-a-deploy-key). | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/deploy_key_short_desc.md b/translations/es-XL/data/reusables/webhooks/deploy_key_short_desc.md deleted file mode 100644 index 341444d304..0000000000 --- a/translations/es-XL/data/reusables/webhooks/deploy_key_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Una llave de despliegue se agrega o se elimina de un repositorio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[Llaves de despliegue](/v3/repos/keys/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/deployment_short_desc.md b/translations/es-XL/data/reusables/webhooks/deployment_short_desc.md deleted file mode 100644 index f92b214ae0..0000000000 --- a/translations/es-XL/data/reusables/webhooks/deployment_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Se crea un despliegue. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[despliegue](/v3/repos/deployments/#list-deployments)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/deployment_status_short_desc.md b/translations/es-XL/data/reusables/webhooks/deployment_status_short_desc.md deleted file mode 100644 index 63fcd491d1..0000000000 --- a/translations/es-XL/data/reusables/webhooks/deployment_status_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Se crea un despliegue. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[estados de despliegue](/v3/repos/deployments/#list-deployment-statuses)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/enterprise_short_desc.md b/translations/es-XL/data/reusables/webhooks/enterprise_short_desc.md deleted file mode 100644 index 484d0d79e7..0000000000 --- a/translations/es-XL/data/reusables/webhooks/enterprise_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Un administrador de repositorio o de sitio habilita o inhabilita el acceso de lectura anónimo de Git. Consulta "[Permitir que los administradores habiliten el acceso de lectura anónimo de Git en los repositorios públicos](/enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)" para obtener más detalles. Este evento no está disponible en la API de Eventos. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/events_api_payload.md b/translations/es-XL/data/reusables/webhooks/events_api_payload.md deleted file mode 100644 index 1cb35a3d84..0000000000 --- a/translations/es-XL/data/reusables/webhooks/events_api_payload.md +++ /dev/null @@ -1 +0,0 @@ -El [objeto del evento](#event-object-common-properties) incluye propiedades que son comunes para todos los eventos. Cada objeto de evento incluye una propiedad de `payload` y el valor es único para cada tipo de evento. El objeto de `payload` para este evento se describe a continuación. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/fork_properties.md b/translations/es-XL/data/reusables/webhooks/fork_properties.md deleted file mode 100644 index 0e440c0034..0000000000 --- a/translations/es-XL/data/reusables/webhooks/fork_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | -------- | ---------------------------------------------------------------------- | -| `forkee` | `objeto` | El recurso de [`repository`](/v3/repos/#get-a-repository) que se creó. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/fork_short_desc.md b/translations/es-XL/data/reusables/webhooks/fork_short_desc.md deleted file mode 100644 index ba9dda4009..0000000000 --- a/translations/es-XL/data/reusables/webhooks/fork_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Un usuario bifurca un repositorio. Para obtener más información, consulta la API de REST de "[bifurcaciones](/v3/repos/forks/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/gollum_properties.md b/translations/es-XL/data/reusables/webhooks/gollum_properties.md deleted file mode 100644 index b75fcc9a5e..0000000000 --- a/translations/es-XL/data/reusables/webhooks/gollum_properties.md +++ /dev/null @@ -1,8 +0,0 @@ -| Clave | Tipo | Descripción | -| -------------------- | ----------- | ---------------------------------------------------------------------- | -| `páginas` | `array` | Las páginas que se actualizaron. | -| `pages[][page_name]` | `secuencia` | El nombre de la página. | -| `pages[][title]` | `secuencia` | El título de la página actual. | -| `pages[][action]` | `secuencia` | La acción que se realizó en la página. Puede ser `created` o `edited`. | -| `pages[][sha]` | `secuencia` | El SHA de confirmación más reciente de la página. | -| `pages[][html_url]` | `secuencia` | Apunta a la página de wiki de HMTL. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/gollum_short_desc.md b/translations/es-XL/data/reusables/webhooks/gollum_short_desc.md deleted file mode 100644 index ced244e6d4..0000000000 --- a/translations/es-XL/data/reusables/webhooks/gollum_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Se crea o actualiza una página de wiki. Para obtener más información, consulta la sección "[Acerca de las wikis](/github/building-a-strong-community/about-wikis)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/installation_properties.md b/translations/es-XL/data/reusables/webhooks/installation_properties.md deleted file mode 100644 index c1d35216d4..0000000000 --- a/translations/es-XL/data/reusables/webhooks/installation_properties.md +++ /dev/null @@ -1,4 +0,0 @@ -| Clave | Tipo | Descripción | -| -------------- | ----------- | ----------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `created` - Alguien instala una {% data variables.product.prodname_github_app %}.
    • `deleted` - Alguien desinstala una {% data variables.product.prodname_github_app %}
      • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
    • `suspend` - alguien suspende la instalación de una {% data variables.product.prodname_github_app %}.
    • `unsuspend` - Alguien deja de suspender una instalación de {% data variables.product.prodname_github_app %}.
      • {% endif %}
    • `new_permissions_accepted` - Alguien acepta permisos nuevos para una instalación de {% data variables.product.prodname_github_app %}. Cuando un propietario de una {% data variables.product.prodname_github_app %} solcita permisos nuevos, la persona que instaló dicha {% data variables.product.prodname_github_app %} debe aceptar la solicitud de estos permisos nuevos.
    | -| `repositorios` | `array` | Una matriz de objetos del repositorio a los cuales puede acceder la instalación. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/installation_repositories_properties.md b/translations/es-XL/data/reusables/webhooks/installation_repositories_properties.md deleted file mode 100644 index 2912a8269d..0000000000 --- a/translations/es-XL/data/reusables/webhooks/installation_repositories_properties.md +++ /dev/null @@ -1,6 +0,0 @@ -| Clave | Tipo | Descripción | -| ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser tanto `added` como `removed`. | -| `repository_selection` | `secuencia` | La elección de repositorios en los cuales se encuentra la instalación. Puede ser tanto `selected` como `all`. | -| `repositories_added` | `array` | Una matriz de objetos del repositorio, los cuales se agregaron a la instalación. | -| `repositories_removed` | `array` | Una matriz de objetos del repositorio, los cuales se eliminaron de la instalación. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/es-XL/data/reusables/webhooks/installation_repositories_short_desc.md deleted file mode 100644 index 23ad2b3072..0000000000 --- a/translations/es-XL/data/reusables/webhooks/installation_repositories_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con los repositorios que se está agregando a la instalación de la GitHub App. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[Instalación de GitHub Apps](/v3/apps/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/installation_short_desc.md b/translations/es-XL/data/reusables/webhooks/installation_short_desc.md deleted file mode 100644 index 8111245f1e..0000000000 --- a/translations/es-XL/data/reusables/webhooks/installation_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con la instalación de una GitHub App. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[Instalación de GitHub Apps](/v3/apps/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/issue_comment_properties.md b/translations/es-XL/data/reusables/webhooks/issue_comment_properties.md deleted file mode 100644 index b4360f1f5c..0000000000 --- a/translations/es-XL/data/reusables/webhooks/issue_comment_properties.md +++ /dev/null @@ -1 +0,0 @@ -`changes`|`object` | Los cambios al comentario en caso de que la acción sea `edited`. `changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `issue`|`object` | El [issue](/v3/issues/) al cual pertenece el comentario. `comment`|`object` | El [comment](/v3/issues/comments/) mismo. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/issue_comment_short_desc.md b/translations/es-XL/data/reusables/webhooks/issue_comment_short_desc.md deleted file mode 100644 index ace7a566fa..0000000000 --- a/translations/es-XL/data/reusables/webhooks/issue_comment_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con el comentario de un informe de problemas. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[comentrios del informe de problemas](/v3/issues/comments/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/issue_comment_webhook_properties.md b/translations/es-XL/data/reusables/webhooks/issue_comment_webhook_properties.md deleted file mode 100644 index 4f99868512..0000000000 --- a/translations/es-XL/data/reusables/webhooks/issue_comment_webhook_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | -------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`, `edited`, o `deleted`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/issue_event_api_properties.md b/translations/es-XL/data/reusables/webhooks/issue_event_api_properties.md deleted file mode 100644 index fb04e14bbe..0000000000 --- a/translations/es-XL/data/reusables/webhooks/issue_event_api_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, o `unlabeled`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/issue_properties.md b/translations/es-XL/data/reusables/webhooks/issue_properties.md deleted file mode 100644 index 18b7bba8e5..0000000000 --- a/translations/es-XL/data/reusables/webhooks/issue_properties.md +++ /dev/null @@ -1 +0,0 @@ -`issue`|`object` | El [issue](/v3/issues) mismo. `changes`|`object`| Los cambios al informe de problemas si la acción está como `edited`. `changes[title][from]`|`string` | La versión previa del título si la acción fue `edited`. `changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `assignee`|`object` | El usuario opcional que se asignó o se desasignó del informe de problemas. `label`|`object` | La etiqueta opcional que se agregó o que se eliminó del informe de problemas. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/issue_webhook_properties.md b/translations/es-XL/data/reusables/webhooks/issue_webhook_properties.md deleted file mode 100644 index 8f64186801..0000000000 --- a/translations/es-XL/data/reusables/webhooks/issue_webhook_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre `opened`, `edited`, `deleted`, `pinned`, `unpinned`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, `unlabeled`, `locked`, `unlocked`, `transferred`, `milestoned`, o `demilestoned`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/issues_short_desc.md b/translations/es-XL/data/reusables/webhooks/issues_short_desc.md deleted file mode 100644 index e811ddbbcd..0000000000 --- a/translations/es-XL/data/reusables/webhooks/issues_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividar relacionada con un informe de problemas. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[informe de problemas](/v3/issues/comments/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/label_short_desc.md b/translations/es-XL/data/reusables/webhooks/label_short_desc.md deleted file mode 100644 index e1294c3e5d..0000000000 --- a/translations/es-XL/data/reusables/webhooks/label_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividar relacionada con un informe de problemas. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[etiquetas](/v3/issues/labels/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/member_event_api_properties.md b/translations/es-XL/data/reusables/webhooks/member_event_api_properties.md deleted file mode 100644 index e0a3a63a6a..0000000000 --- a/translations/es-XL/data/reusables/webhooks/member_event_api_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ---------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ponerse como `added` para indicar que un usuario aceptó una invitación al repositorio. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/member_properties.md b/translations/es-XL/data/reusables/webhooks/member_properties.md deleted file mode 100644 index 48050633c3..0000000000 --- a/translations/es-XL/data/reusables/webhooks/member_properties.md +++ /dev/null @@ -1 +0,0 @@ -`member`|`object` | El [user](/v3/users/) que se agregó. `changes`|`object`| Los cambios a los permisos del colaborador si la acción fue `edited`. `changes[old_permission][from]`|`string` | Los permisos previos del colaborador si la acción fue `edited`. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/member_short_desc.md b/translations/es-XL/data/reusables/webhooks/member_short_desc.md deleted file mode 100644 index 1469f1912f..0000000000 --- a/translations/es-XL/data/reusables/webhooks/member_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con los colaboradores del repositorio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[colaboradores](/v3/repos/collaborators/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/member_webhook_properties.md b/translations/es-XL/data/reusables/webhooks/member_webhook_properties.md deleted file mode 100644 index 5093d5d45f..0000000000 --- a/translations/es-XL/data/reusables/webhooks/member_webhook_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ----------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `added` - Un usuario acepta una invitación a un repositorio.
    • `removed` - Se elimina a un usuario como colaborador de un repositorio.
    • `edited` - Los permisos de colaborador de un usuario han cambiado.
    | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/membership_properties.md b/translations/es-XL/data/reusables/webhooks/membership_properties.md deleted file mode 100644 index c0dc6afc36..0000000000 --- a/translations/es-XL/data/reusables/webhooks/membership_properties.md +++ /dev/null @@ -1,6 +0,0 @@ -| Clave | Tipo | Descripción | -| --------- | ----------- | --------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser `added` o `removed`. | -| `alcance` | `secuencia` | El alcance de la membrecía. Acutalmente, solo puede ser `team`. | -| `member` | `objeto` | El [usuario](/v3/users/) que se agregó o se eliminó. | -| `equipo` | `objeto` | El [equipo](/v3/teams/) para la membrecía. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/membership_short_desc.md b/translations/es-XL/data/reusables/webhooks/membership_short_desc.md deleted file mode 100644 index 1c1bbad1a5..0000000000 --- a/translations/es-XL/data/reusables/webhooks/membership_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con la membrecía del equipo. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[miembros del equipo](/v3/teams/members/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/milestone_properties.md b/translations/es-XL/data/reusables/webhooks/milestone_properties.md deleted file mode 100644 index 962e4af8f9..0000000000 --- a/translations/es-XL/data/reusables/webhooks/milestone_properties.md +++ /dev/null @@ -1,8 +0,0 @@ -| Clave | Tipo | Descripción | -| ---------------------------- | ----------- | ------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser uno de entre: `created`, `closed`, `opened`, `edited`, o `deleted`. | -| `hito` | `objeto` | El hito mismo. | -| `changes` | `objeto` | Los cambios al hito si la acción se encuentra como `edited`. | -| `changes[description][from]` | `secuencia` | La versión previa de la descripción si la acción está como `edited`. | -| `changes[due_on][from]` | `secuencia` | La versión previa de la fecha límite si la acción se puso como `edited`. | -| `changes[title][from]` | `secuencia` | La versión previa del título si la acción se puso como `edited`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/milestone_short_desc.md b/translations/es-XL/data/reusables/webhooks/milestone_short_desc.md deleted file mode 100644 index dc0a80c9fe..0000000000 --- a/translations/es-XL/data/reusables/webhooks/milestone_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividar relacionada con los hitos. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[hitos](/v3/issues/milestones/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/org_block_short_desc.md b/translations/es-XL/data/reusables/webhooks/org_block_short_desc.md deleted file mode 100644 index 4044d08414..0000000000 --- a/translations/es-XL/data/reusables/webhooks/org_block_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con las personas que se bloquearon en una organización. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST "[bloquear a usuarios de una organización](/v3/orgs/blocking/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/org_desc.md b/translations/es-XL/data/reusables/webhooks/org_desc.md deleted file mode 100644 index 377361db00..0000000000 --- a/translations/es-XL/data/reusables/webhooks/org_desc.md +++ /dev/null @@ -1 +0,0 @@ -`organization` | `object` | Las cargas útiles de webhook contienen el objeto [`organization`](/v3/orgs/#get-an-organization) cuando el webhook se configura para para una organización o cuando el evento ocurre desde una actividad en un repositorio que pertenezca a la organización. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/organization_short_desc.md b/translations/es-XL/data/reusables/webhooks/organization_short_desc.md deleted file mode 100644 index e9c07e4350..0000000000 --- a/translations/es-XL/data/reusables/webhooks/organization_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con una organización y sus miembros. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[organizaciones](/v3/orgs/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/package_properties.md b/translations/es-XL/data/reusables/webhooks/package_properties.md deleted file mode 100644 index 3c0e0b78d1..0000000000 --- a/translations/es-XL/data/reusables/webhooks/package_properties.md +++ /dev/null @@ -1,4 +0,0 @@ -| Clave | Tipo | Descripción | -| --------- | ----------- | ------------------------------------------------------------ | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser `published` o `updated`. | -| `paquete` | `objeto` | La información sobre el paquete. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/page_build_short_desc.md b/translations/es-XL/data/reusables/webhooks/page_build_short_desc.md deleted file mode 100644 index 24f745aa0f..0000000000 --- a/translations/es-XL/data/reusables/webhooks/page_build_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Representa un intento de creación de un sitio de GitHub Pages, ya sea que fuese exitoso o no. Una carga a una rama habilitada de GitHub Pages (`gh-pages` para páginas de proyecto, `master` para páginas de organización y de usuario) activa este evento. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/payload_url.md b/translations/es-XL/data/reusables/webhooks/payload_url.md deleted file mode 100644 index b772022a24..0000000000 --- a/translations/es-XL/data/reusables/webhooks/payload_url.md +++ /dev/null @@ -1 +0,0 @@ -La URL de carga útil es la URL del servidor que recibirá las solicitudes de `POST` del webhook. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/ping_short_desc.md b/translations/es-XL/data/reusables/webhooks/ping_short_desc.md deleted file mode 100644 index 19b93ae7f6..0000000000 --- a/translations/es-XL/data/reusables/webhooks/ping_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Cuando creas un webhook nuevo, te enviaremos un evento de `ping` sencillo para informarte que configuraste el webhook correctamente. Este evento no se almacena, así que no se puede recuperar a través de la [API de Eventos](/v3/activity/events/). Puedes activar nuevamente un `ping` si llamas a la terminal [Hacer ping a un webhook del repositorio](/v3/repos/hooks/#ping-a-repository-webhook). diff --git a/translations/es-XL/data/reusables/webhooks/project_card_properties.md b/translations/es-XL/data/reusables/webhooks/project_card_properties.md deleted file mode 100644 index fe6afb0303..0000000000 --- a/translations/es-XL/data/reusables/webhooks/project_card_properties.md +++ /dev/null @@ -1,7 +0,0 @@ -| Clave | Tipo | Descripción | -| --------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| `Acción` | `secuencia` | La acción llevada a cabo en la tarjeta del proyecto. Puede ser `created`, `edited`, `moved`, `converted`, o `deleted`. | -| `changes` | `objeto` | Los cambios a la tarjeta del proyecto si la acción se puso como `edited` o `converted`. | -| `changes[note][from]` | `secuencia` | La versión previa de la nota si la acción se puso como `edited` o `converted`. | -| `after_id` | `número` | La id de la tarjeta a la cual sigue esta tarjeta ahora si la acción se "movió". Será `null` si es la primera tarjeta en una columna. | -| `project_card` | `objeto` | La [tarjeta de proyecto](/v3/projects/cards) misma. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/project_card_short_desc.md b/translations/es-XL/data/reusables/webhooks/project_card_short_desc.md deleted file mode 100644 index faf412ae71..0000000000 --- a/translations/es-XL/data/reusables/webhooks/project_card_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con las tarjetas de proyecto. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[tarjetas de proyecto](/v3/projects/cards)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/project_column_properties.md b/translations/es-XL/data/reusables/webhooks/project_column_properties.md deleted file mode 100644 index 6c00f64762..0000000000 --- a/translations/es-XL/data/reusables/webhooks/project_column_properties.md +++ /dev/null @@ -1,7 +0,0 @@ -| Clave | Tipo | Descripción | -| --------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó en la columna de proyecto. Puede ser una de entre `created`, `edited`, `moved` o `deleted`. | -| `changes` | `objeto` | Los cambios a la columna del proyecto si la acción se puso como `edited`. | -| `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | -| `after_id` | `número` | La id de la columna a la cual sigue ahora esta coumna si la acción se "movió". Será `null` si es la primera columna en un proyecto. | -| `project_column` | `objeto` | La [columna de proyecto](/v3/projects/columns) misma. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/project_column_short_desc.md b/translations/es-XL/data/reusables/webhooks/project_column_short_desc.md deleted file mode 100644 index 09252606b3..0000000000 --- a/translations/es-XL/data/reusables/webhooks/project_column_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con las columnas en un tablero de proyecto. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[columnas de proyecto](/v3/projects/columns)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/project_properties.md b/translations/es-XL/data/reusables/webhooks/project_properties.md deleted file mode 100644 index 482910c239..0000000000 --- a/translations/es-XL/data/reusables/webhooks/project_properties.md +++ /dev/null @@ -1,7 +0,0 @@ -| Clave | Tipo | Descripción | -| --------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------ | -| `Acción` | `secuencia` | La acción que se realizó en el proyecto. Puede ser uno de entre: `created`, `edited`, `closed`, `reopened`, o `deleted`. | -| `changes` | `objeto` | Los cambios al proyecto si la acción se puso como `edited`. | -| `changes[name][from]` | `secuencia` | La versión previa del nombre si la acción está como `edited`. | -| `changes[body][from]` | `secuencia` | La versión previa del cuerpo si la acción se puso como `edited`. | -| `project` | `objeto` | El [proyecto](/v3/projects/) mismo. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/project_short_desc.md b/translations/es-XL/data/reusables/webhooks/project_short_desc.md deleted file mode 100644 index b30f7ee1f9..0000000000 --- a/translations/es-XL/data/reusables/webhooks/project_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con los tableros de proyecto. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[proyectos](/v3/projects)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/public_short_desc.md b/translations/es-XL/data/reusables/webhooks/public_short_desc.md deleted file mode 100644 index 9763935f7f..0000000000 --- a/translations/es-XL/data/reusables/webhooks/public_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Cuando un repositorio privado se hace público. Sin duda alguna: el mejor evento de {% data variables.product.product_name %}. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/es-XL/data/reusables/webhooks/pull_request_event_api_properties.md deleted file mode 100644 index b5f3b809a1..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_event_api_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, y `synchronize`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_properties.md b/translations/es-XL/data/reusables/webhooks/pull_request_properties.md deleted file mode 100644 index 6417d9e8fd..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_properties.md +++ /dev/null @@ -1 +0,0 @@ -`number`|`integer` | El número de la solicitud de extracción. `changes`|`object` | Los cambios al comentario en caso de que la acción sea `edited`. `changes[title][from]`|`string` | La versión previa del título si la acción fue `edited`. `changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `pull_request`|`object` | La [solicitud de extracción](/v3/pulls) misma. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md b/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md deleted file mode 100644 index 3f5f46d78d..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | --------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_properties.md deleted file mode 100644 index 3900bdcfb8..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_properties.md +++ /dev/null @@ -1 +0,0 @@ -`changes`|`object` | Los cambios al comentario en caso de que la acción sea `edited`. `changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `pull_request`|`object` | La [solicitud de extracción](/v3/pulls/) a la cual pertenece el comentario. `comment`|`object` | El [comentario](/v3/pulls/comments) mismo. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_short_desc.md deleted file mode 100644 index 4c49a06ec7..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividar relacionada con los comentarios de revisión de la solicitud de extracción en el diff unificado de la misma. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[comentrios de revisión de la solicitud de extracción](/v3/pulls/comments/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md b/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md deleted file mode 100644 index 4f99868512..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | -------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó en el comentario. Puede ser `created`, `edited`, o `deleted`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_review_properties.md b/translations/es-XL/data/reusables/webhooks/pull_request_review_properties.md deleted file mode 100644 index 5b243e4d77..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_review_properties.md +++ /dev/null @@ -1,6 +0,0 @@ -| Clave | Tipo | Descripción | -| ---------------------- | ----------- | ----------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `submitted` - Se emitió una solicitud de extracción en un estado no pendiente.
    • `edited` - el cuerpo de una revisión se editó.
    • `dismissed` - Se descartó una revisión.
    | -| `solicitud_extracción` | `objeto` | La [solicitud de extracción](/v3/pulls/) a la cual pertenece la revisión. | -| `revisión` | `objeto` | La revisión que se afectó. | -| `changes[body][from]` | `secuencia` | La versión previa del cuerpo si la acción se puso como `edited`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/es-XL/data/reusables/webhooks/pull_request_review_short_desc.md deleted file mode 100644 index 3187b606c2..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_review_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con las revisiones de la solicitudes de extracción. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[revisiones de la solicitud de extracción](/v3/pulls/reviews/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_short_desc.md b/translations/es-XL/data/reusables/webhooks/pull_request_short_desc.md deleted file mode 100644 index 5eb1eb4efa..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con las solicitudes de extracción. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[solicitudes de extracción](/v3/pulls/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/es-XL/data/reusables/webhooks/pull_request_webhook_properties.md deleted file mode 100644 index b3918dbe88..0000000000 --- a/translations/es-XL/data/reusables/webhooks/pull_request_webhook_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de entre `opened`, `edited`, `closed`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `ready_for_review`, `labeled`, `unlabeled`, `synchronize`, `locked`, `unlocked`, o `reopened`. Si la acción se muestra como `closed` y la llave `merged` es `false`, esto significa que la solicitud de extracción se cerró con las confirmaciones sin fusionar. Si la acción se muestra como `closed` y la llave `merged` es `true`, la solicitud de extracción se fusionó. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/push_short_desc.md b/translations/es-XL/data/reusables/webhooks/push_short_desc.md deleted file mode 100644 index 2910251d00..0000000000 --- a/translations/es-XL/data/reusables/webhooks/push_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Se cargó una o más confirmaciones a la rama o etiqueta de un repositorio. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/release_event_api_properties.md b/translations/es-XL/data/reusables/webhooks/release_event_api_properties.md deleted file mode 100644 index 66573f5c90..0000000000 --- a/translations/es-XL/data/reusables/webhooks/release_event_api_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | --------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ponerse como `published`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/release_properties.md b/translations/es-XL/data/reusables/webhooks/release_properties.md deleted file mode 100644 index df4ac8edc4..0000000000 --- a/translations/es-XL/data/reusables/webhooks/release_properties.md +++ /dev/null @@ -1 +0,0 @@ -`changes[body][from]` |`string` | La versión previa del cuerpo si la acción aparece como `edited`. `changes[name][from]` |`string` | La versión previa del nombre si la acción aparece como `edited`. `release`|`object` | El objeto de [release](/v3/repos/releases/#get-a-release). \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/release_short_desc.md b/translations/es-XL/data/reusables/webhooks/release_short_desc.md deleted file mode 100644 index f470a14f0c..0000000000 --- a/translations/es-XL/data/reusables/webhooks/release_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con un lanzamiento. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[lanzamientos](/v3/repos/releases/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/release_webhook_properties.md b/translations/es-XL/data/reusables/webhooks/release_webhook_properties.md deleted file mode 100644 index 9f5366a41f..0000000000 --- a/translations/es-XL/data/reusables/webhooks/release_webhook_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
    • `published`: se publica un lanzamiento, pre-lanzamiento, o borrador de un lanzamiento
      • {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
    • `unpublished`: se borra un lanzamiento o pre-lanzamiento
    • `created`: se guarda un borrador, o se publica un lanzamiento o pre-lanzamiento sin que se haya guardado previamente como un borrador
    • `edited`: se edita un lanzamiento, pre-lanzamiento, o borrador de lanzamiento
    • `deleted`: se borra un lanzamiento, pre-lanzamiento, o borrador de lanzamiento
    • `prereleased`: se crea un pre-lanzamiento
    • `released`: se publica un lanzamiento o borrador de un lanzamiento, o se cambia un prelanzamiento a lanzamiento
      • {% endif %} | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/repo_desc.md b/translations/es-XL/data/reusables/webhooks/repo_desc.md deleted file mode 100644 index f266f32b59..0000000000 --- a/translations/es-XL/data/reusables/webhooks/repo_desc.md +++ /dev/null @@ -1 +0,0 @@ -`repository` | `object` | El [`repositorio`](/v3/repos/#get-a-repository) en donde ocurrió el evento. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/repository_import_properties.md b/translations/es-XL/data/reusables/webhooks/repository_import_properties.md deleted file mode 100644 index 86e022ed9b..0000000000 --- a/translations/es-XL/data/reusables/webhooks/repository_import_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ------------------------------------------------------------------------------------------------------- | -| `estado` | `secuencia` | El estado final de la importación. Este puede ser alguno de entre: `success`, `cancelled`, o `failure`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/repository_import_short_desc.md b/translations/es-XL/data/reusables/webhooks/repository_import_short_desc.md deleted file mode 100644 index fb5abbd6aa..0000000000 --- a/translations/es-XL/data/reusables/webhooks/repository_import_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionad con un repositorio que se está importando a GitHub. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[importaciones de código fuente](/v3/migrations/source_imports/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/repository_short_desc.md b/translations/es-XL/data/reusables/webhooks/repository_short_desc.md deleted file mode 100644 index 3fea0f91cf..0000000000 --- a/translations/es-XL/data/reusables/webhooks/repository_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con un repositorio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[repositorios](/v3/repos/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/repository_vulnerability_alert_properties.md b/translations/es-XL/data/reusables/webhooks/repository_vulnerability_alert_properties.md deleted file mode 100644 index 6c100121b1..0000000000 --- a/translations/es-XL/data/reusables/webhooks/repository_vulnerability_alert_properties.md +++ /dev/null @@ -1,4 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Este puede ser alguno de entre: `create`, `dismiss`, o `resolve`. | -| `alerta` | `objeto` | La alerta de seguridad de la dependencia vulnerable. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md b/translations/es-XL/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md deleted file mode 100644 index fac9eeeff2..0000000000 --- a/translations/es-XL/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Actividad relacionada con las alertas de vulnerabilidades de seguridad en un repositorio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la sección "[Acerca de las alertas de seguridad para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/secret.md b/translations/es-XL/data/reusables/webhooks/secret.md deleted file mode 100644 index 5e0669a771..0000000000 --- a/translations/es-XL/data/reusables/webhooks/secret.md +++ /dev/null @@ -1 +0,0 @@ -Configurar el secreto de un webhook te permite garantizar que las solicitudes de `POST` que se envían a la URL de la carga útil vienen de GitHub. Cuando configuras un secreto, recibirás el encabezado de `X-Hub-Signature` en el la solicitud de `POST` del webhook. Para obtener más detalles sobre cómo utilizar el secreto y el encabezado de `X-Hub-Signature` para asegurar las cargas útiles de tu webhook, consulta la sección "[Asegurar tus webhooks](/webhooks/securing/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/sender_desc.md b/translations/es-XL/data/reusables/webhooks/sender_desc.md deleted file mode 100644 index 4e8defa000..0000000000 --- a/translations/es-XL/data/reusables/webhooks/sender_desc.md +++ /dev/null @@ -1 +0,0 @@ -`sender` | `object` | El usuario que activó el evento. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/sponsorship_event_api_properties.md b/translations/es-XL/data/reusables/webhooks/sponsorship_event_api_properties.md deleted file mode 100644 index 1463278652..0000000000 --- a/translations/es-XL/data/reusables/webhooks/sponsorship_event_api_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ---------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser `created`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/sponsorship_properties.md b/translations/es-XL/data/reusables/webhooks/sponsorship_properties.md deleted file mode 100644 index ca9a773262..0000000000 --- a/translations/es-XL/data/reusables/webhooks/sponsorship_properties.md +++ /dev/null @@ -1 +0,0 @@ -`effective_date` | `string` | Los tipos de evento `pending_cancellation` y `pending_tier_change` incluirán la fecha en la que se hará válida la cancelación o el cambio de nivel. `changes[tier][from]` | `object` | El `tier_changed` o el `pending_tier_change` incluirán el nivel original antes del cambio o del cambio pendiente. Para obtener más información, consulta la sección "[carga útil de cambios para el nivel pendiente](/webhooks/event-payloads#webhook-payload-example-when-someone-downgrades-a-sponsorship)". `changes[privacy_level][from]` | `string` | Los tipos de evento `edited` incluyen los detalles sobre el cambio cuando alguien edita un patrocinio para cambiar su privacidad. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/sponsorship_short_desc.md b/translations/es-XL/data/reusables/webhooks/sponsorship_short_desc.md deleted file mode 100644 index 42a0ac4b88..0000000000 --- a/translations/es-XL/data/reusables/webhooks/sponsorship_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con un listado de patrocinio. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta "[Acerca de los Patrocinadores de GitHub](/github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/sponsorship_webhook_properties.md b/translations/es-XL/data/reusables/webhooks/sponsorship_webhook_properties.md deleted file mode 100644 index b6c5fd5404..0000000000 --- a/translations/es-XL/data/reusables/webhooks/sponsorship_webhook_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Esta puede ser una de entre: `created`, `cancelled`, `edited`, `tier_changed`, `pending_cancellation`, o `pending_tier_change`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/star_properties.md b/translations/es-XL/data/reusables/webhooks/star_properties.md deleted file mode 100644 index b3d3941c73..0000000000 --- a/translations/es-XL/data/reusables/webhooks/star_properties.md +++ /dev/null @@ -1,4 +0,0 @@ -| Clave | Tipo | Descripción | -| ------------ | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser `created` o `deleted`. | -| `starred_at` | `secuencia` | La hora en la cual se creó un marcado con estrella. {% data reusables.shortdesc.iso_8601 %} Será `null` para las acciones que estén como `deleted`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/star_short_desc.md b/translations/es-XL/data/reusables/webhooks/star_short_desc.md deleted file mode 100644 index 96b6d8380a..0000000000 --- a/translations/es-XL/data/reusables/webhooks/star_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionad con un repositorio que se está marcando con una estrella. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[marcar con una estrella](/v3/activity/starring/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/status_short_desc.md b/translations/es-XL/data/reusables/webhooks/status_short_desc.md deleted file mode 100644 index b867a240db..0000000000 --- a/translations/es-XL/data/reusables/webhooks/status_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Cuando el estado de una confirmación de Git cambia. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[estados](/v3/repos/statuses/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/team_add_short_desc.md b/translations/es-XL/data/reusables/webhooks/team_add_short_desc.md deleted file mode 100644 index 390ab9340b..0000000000 --- a/translations/es-XL/data/reusables/webhooks/team_add_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Cuando se [agrega un repositorio a un equipo](/v3/teams/#add-or-update-team-repository-permissions). \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/team_short_desc.md b/translations/es-XL/data/reusables/webhooks/team_short_desc.md deleted file mode 100644 index 298986c99c..0000000000 --- a/translations/es-XL/data/reusables/webhooks/team_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -La actividad relacionada con el equipo de una organización. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[equipos](/v3/teams/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/watch_properties.md b/translations/es-XL/data/reusables/webhooks/watch_properties.md deleted file mode 100644 index 763b1dbca3..0000000000 --- a/translations/es-XL/data/reusables/webhooks/watch_properties.md +++ /dev/null @@ -1,3 +0,0 @@ -| Clave | Tipo | Descripción | -| -------- | ----------- | ---------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Acutalmente, solo puede ser `started`. | \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/watch_short_desc.md b/translations/es-XL/data/reusables/webhooks/watch_short_desc.md deleted file mode 100644 index 84c0c31e72..0000000000 --- a/translations/es-XL/data/reusables/webhooks/watch_short_desc.md +++ /dev/null @@ -1 +0,0 @@ -Cuando alguien marca un repositorio con una estrella. {% data reusables.webhooks.action_type_desc %} Para obtener más información, consulta la API de REST de "[marcar con una estrella](/v3/activity/starring/)". \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/webhooks_intro.md b/translations/es-XL/data/reusables/webhooks/webhooks_intro.md deleted file mode 100644 index 7459e7faa4..0000000000 --- a/translations/es-XL/data/reusables/webhooks/webhooks_intro.md +++ /dev/null @@ -1 +0,0 @@ -Cuando configuras un webhook, puedes utilizar la IU o la API para elegir qué eventos te enviarán cargas útiles. El suscribirte únicamente a los eventos específicos que pretendes gestionar limita la cantidad de solicitudes HTTP a tu servidor. También puedes suscribirte a todos los eventos futuros y actuales. Predeterminadamente, los webhooks solo se suscriben al evento de carga. Puedes cambiar la lista de eventos a los que te suscribiste en cualquier momento. diff --git a/translations/es-XL/data/reusables/webhooks/webhooks_ssl.md b/translations/es-XL/data/reusables/webhooks/webhooks_ssl.md deleted file mode 100644 index cc8cc80bff..0000000000 --- a/translations/es-XL/data/reusables/webhooks/webhooks_ssl.md +++ /dev/null @@ -1 +0,0 @@ -Si tu "URL de carga útil" es un sitio seguro (HTTPS), tendrás la opción de configurar los ajustes de verificación de SSL. Si tu "URL de carga útil" no es segura (HTTP), GitHub no mostrará esta opción. Predeterminadamente, GitHub verifica el certificado SSL de tu sitio web cuando entrega cargas útiles de webhooks. La verificación de SSL ayuda a garantizar que las cargas útiles de los ganchos se entregan en tu terminal URL de forma segura. Tienes la opción de inhabilitar SSL, pero te recomendamos que mantengas seleccionado **Habilitar la verificación SSL**. \ No newline at end of file diff --git a/translations/es-XL/data/reusables/webhooks/workflow_run_desc.md b/translations/es-XL/data/reusables/webhooks/workflow_run_desc.md deleted file mode 100644 index c5d57f3d08..0000000000 --- a/translations/es-XL/data/reusables/webhooks/workflow_run_desc.md +++ /dev/null @@ -1,4 +0,0 @@ - -Este evento ocurre cuando una ejecución de flujo de trabajo se solicita o se completa, y te permite ejecutar un flujo de trabajo con base en el resultado terminado de otro flujo de trabajo. Por ejemplo, si tu flujo de trabajo de `pull_request` genera artefactos de compilación, puedes crear un nuevo flujo de trabajo que utilice a `workflow_run` para analizar los resultados y agregar un comentario la solicitud de extracción original. - -El flujo de trabajo que inició el evento `workflow_run` puede acceder a los secretos y tokens escritos que se utilizan en el flujo de trabajo original. \ No newline at end of file diff --git a/translations/es-XL/data/ui.yml b/translations/es-XL/data/ui.yml deleted file mode 100644 index 3e6d70b597..0000000000 --- a/translations/es-XL/data/ui.yml +++ /dev/null @@ -1,120 +0,0 @@ ---- -header: - github_docs: GitHub Docs - contact: Contacto - notices: - ghe_release_candidate: GitHub Enterprise Server 2.22 is currently under limited release as a release candidate. - localization_complete: Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos. - localization_in_progress: '¡Hola, explorador! Esta página está bajo desarrollo activo o todavía está en la etapa de traducción. Para obtener información más actualizada y precisa, visita nuestra documentación en inglés.' - product_in_progress: '👋 ¡Hola, explorador! Esta página está en desarrollo activo. Para la información más actualizada y precisa, por favor visita nuestra documentación del desarrollador.' -search: - need_help: '¿Necesitas ayuda?' - placeholder: Busca temas, productos... -homepage: - explore_by_product: Explorar por producto - version_picker: Versión -toc: - getting_started: Empezar - popular_articles: Artículos populares - guides: Guías -pages: - article_version: "Versión del artículo:" - miniToc: En este artículo -errors: - oops: '¡Ups!' - something_went_wrong: Parece que algo salió mal. - we_track_errors: Realizamos el seguimiento de estos errores automáticamente, pero si el problema continúa, no dudes en contactarnos. - page_doesnt_exist: Al parecer, esta página no existe. -support: - still_need_help: Still need help? - contact_support: Contactar con soporte técnico - ask_community: Ask the GitHub community -helpfulness: - able_to_find: '¿Te ayudó este documento?' - yes: true - no: false - yes_feedback: '¿Quieres saber sobre las características y actualizaciónes de los documentos nuevos? ¡Regístrate para recibir actualizaciones!' - email_placeholder: email@ejemplo.com - no_feedback: Estamos mejorando nuestros documentos constantemente. Nos encantaría saber cómo crees que podemos hacerlo aún mejor. - category_label: '¿Qué problema tuviste?' - category_default: Elige una opción - category_unclear: La información no estaba clara - category_confusing: El contenido era confuso - category_unhelpful: El artículo no respondió a mi pregunta - category_other: Otro - comment_label: Déjanos saber lo que podemos mejorar - optional: Opcional - required: Requerido - email_label: '¿Podemos contactarte si tenemos más preguntas?' - send: Enviar - feedback: '¡Gracias! Tu retroalimentación se ha emitido.' -contribution_cta: - title: Help us make these docs great! - body: All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request. - button: Make a contribution - or: O, - to_guidelines: learn how to contribute. -products: - graphql: - reference: - fields: Campos - arguments: Argumentos - name: Nombre - type: Tipo - description: Descripción - input_fields: Campos de entrada - return_fields: Campos de retorno - implemented_by: Implementado por - values: Valores - possible_types: Tipos posibles - preview_notice: Aviso de previsualización - deprecation_notice: Aviso de depreciación - rest: - reference: - parameters: Parámetros - response: Respuesta - code_sample: Ejemplo de código - code_samples: Ejemplos de código - preview_notice: Aviso de previsualización - preview_notices: Avisos de previsualización - see_preview_notice: Ver aviso de previsualización - see_preview_notices: Ver avisos de previsualización - preview_header_is_required: El encabezado es requerido -footer: - all_rights_reserved: Todos los derechos reservados - terms: Términos - privacy: Privacidad - security: Seguridad - product: - heading: Producto - links: - features: Características - security: Seguridad - enterprise: Empresa - case_studies: Estudios de caso - pricing: Precios - resources: Recursos - platform: - heading: Plataforma - links: - developer_api: API de desarrollo - partners: Socios - atom: Atom - electron: Electron - github_desktop: GitHub Desktop - support: - heading: Asistencia - links: - help: Ayuda - community_forum: Foro de la comunidad - training: Capacitación - status: Estado - contact_github: Ponte en contacto con GitHub - company: - heading: Empresa - links: - about: Acerca de - blog: Blog - careers: Carreras - press: Prensa - shop: Tienda diff --git a/translations/es-XL/data/variables/command_line.yml b/translations/es-XL/data/variables/command_line.yml deleted file mode 100644 index 3a9a90dfbe..0000000000 --- a/translations/es-XL/data/variables/command_line.yml +++ /dev/null @@ -1,10 +0,0 @@ ---- -#Use this variable wherever backticks are necessary: http://git.io/AArkqA -backticks: >- - {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} -#Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!) -codeblock: >- - {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}nombre de host{% endif %} -#GitHub URL example -git_url_example: >- - https://{% if currentVersion == "free-pro-team@latest" %}github.com{% else %}github.example.com{% endif %} diff --git a/translations/es-XL/data/variables/contact.yml b/translations/es-XL/data/variables/contact.yml deleted file mode 100644 index 2b764b9385..0000000000 --- a/translations/es-XL/data/variables/contact.yml +++ /dev/null @@ -1,31 +0,0 @@ ---- -contact_ent_support: 'GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) o [GitHub Premium Support](https://premium.githubsupport.com)' -contact_support: >- - {% if currentVersion == "free-pro-team@latest" %}[GitHub Support](https://support.github.com/contact) o [GitHub Premium Support](https://premium.githubsupport.com){% else %}tu administrador del sitio empresarial GitHub{% endif %} -report_abuse: >- - {% if currentVersion == "free-pro-team@latest" %}[Report abuse](https://github.com/contact/report-abuse){% endif %} -report_content: >- - {% if currentVersion == "free-pro-team@latest" %}[Report content](https://github.com/contact/report-content){% endif %} -contact_dmca: >- - {% if currentVersion == "free-pro-team@latest" %}[Copyright claims form](https://github.com/contact/dmca){% endif %} -contact_privacy: >- - {% if currentVersion == "free-pro-team@latest" %}[Privacy contact form](https://github.com/contact/privacy){% endif %} -contact_enterprise_sales: '[Equipo de ventas de GitHub](https://enterprise.github.com/contact)' -contact_feedback_actions: '[Formulario para retroalimentación de GitHub Actions](https://support.github.com/contact/feedback?contact[category]=actions)' -contact_partner_engineering: '[partnerengineering@github.com](mailto:partnerengineering@github.com)' -#The team that provides Standard Support -enterprise_support: 'Soporte para GitHub Enterprise' -#The larger team that includes Enterprise Support and Premium Support -github_support: 'Soporte de GitHub' -#The team that provides Premium Support -premium_support: 'Soporte prémium de GitHub' -#Enterprise Support portal -enterprise_portal: 'Portal de Soporte de GitHub Enterprise' -contact_enterprise_portal: '[Portal de Soporte de GitHub Enterprise](https://enterprise.githubsupport.com/hc/en-us)' -#GitHub Support portal (for dotcom) -support_portal: 'Portal de soporte de GitHub' -contact_support_portal: '[GitHub Support portal](https://support.github.com/contact)' -#The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free) -community_support: 'Soporte de la Comunidad de GitHub' -#The GitHub Community forum -community_support_forum: '[Foro de la comunidad de GitHub](https://github.community/)' diff --git a/translations/es-XL/data/variables/desktop.yml b/translations/es-XL/data/variables/desktop.yml deleted file mode 100644 index 2480a54e7d..0000000000 --- a/translations/es-XL/data/variables/desktop.yml +++ /dev/null @@ -1,4 +0,0 @@ ---- -#Supported platforms -mac-osx-versions: macOS 10.10 o posterior -windows-versions: Windows 7 64-bit o posterior diff --git a/translations/es-XL/data/variables/enterprise.yml b/translations/es-XL/data/variables/enterprise.yml deleted file mode 100644 index 1b338f51c1..0000000000 --- a/translations/es-XL/data/variables/enterprise.yml +++ /dev/null @@ -1,2 +0,0 @@ ---- -management_console: 'Consola de administración' diff --git a/translations/es-XL/data/variables/explore.yml b/translations/es-XL/data/variables/explore.yml deleted file mode 100644 index e9d8ccb885..0000000000 --- a/translations/es-XL/data/variables/explore.yml +++ /dev/null @@ -1,7 +0,0 @@ ---- -explore_github: >- - {% if currentVersion == "free-pro-team@latest" %}[Explore GitHub](https://github.com/explore){% else %}Explorar GitHub (`https://[hostname]/explore`){% endif %} -your_stars_page: >- - {% if currentVersion == "free-pro-team@latest" %}[stars page](https://github.com/stars){% else %}página de estrellas (`https://[hostname]/stars`){% endif %} -trending_page: >- - {% if currentVersion == "free-pro-team@latest" %}[Trending page](https://github.com/trending){% else %}Página de tendencias (`https://[hostname]/trending`){% endif %} diff --git a/translations/es-XL/data/variables/gists.yml b/translations/es-XL/data/variables/gists.yml deleted file mode 100644 index 8d92a5f066..0000000000 --- a/translations/es-XL/data/variables/gists.yml +++ /dev/null @@ -1,7 +0,0 @@ ---- -gist_homepage: >- - {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% else %}página de inicio de gist, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` si los subdominios están habilitados {% endif %} -gist_search_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` si los subdominios están habilitados{% endif %} -discover_url: >- - {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` si los subdominios están habilitados{% endif %} diff --git a/translations/es-XL/data/variables/large_files.yml b/translations/es-XL/data/variables/large_files.yml deleted file mode 100644 index b66af68568..0000000000 --- a/translations/es-XL/data/variables/large_files.yml +++ /dev/null @@ -1,15 +0,0 @@ ---- -product_name_long: 'Almacenamiento de archivos de gran tamaño Git' -product_name_short: 'Git LFS' -warning_size: '50 MB' -max_github_size: '100 MB' -max_github_browser_size: '25 MB' -initial_bandwidth_quota: '1 GB' -initial_storage_quota: '1 GB' -max_lfs_size: '2 GB' -max_file_size: '2 GB' -command_name: lfs -version_name: https://git-lfs.github.com/spec/v1 -pack_monthly_price: '$5 por mes' -pack_monthly_bandwidth: '50 GB' -pack_monthly_storage: '50 GB' diff --git a/translations/es-XL/data/variables/migrations.yml b/translations/es-XL/data/variables/migrations.yml deleted file mode 100644 index fd3edd8f1d..0000000000 --- a/translations/es-XL/data/variables/migrations.yml +++ /dev/null @@ -1,7 +0,0 @@ ---- -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: >- - La API de migraciones de organización te permite migrar un repositorio de GitHub a {% data variables.product.prodname_ghe_server %}. -source_imports_intro: >- - La API de Importaciones de Código Fuente te permite comenzar una importación desde un repositorio de origen en Git, Subversion, Mercurial o Team Foundation Server. 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-XL/data/variables/notifications.yml b/translations/es-XL/data/variables/notifications.yml deleted file mode 100644 index 46bbec17af..0000000000 --- a/translations/es-XL/data/variables/notifications.yml +++ /dev/null @@ -1,5 +0,0 @@ ---- -no_reply_address: >- - {% if currentVersion == "free-pro-team@latest" %}`noreply@github.com`{% else %}la dirección de correo electrónico sin respuesta configurada por el administrador del sitio{% endif %} -cc_address: >- - {% if currentVersion == "free-pro-team@latest" %}`@noreply.github.com`{% else %}en función de la dirección de correo electrónico sin respuesta configurada por el administrador del sitio{% endif %} diff --git a/translations/es-XL/data/variables/product.yml b/translations/es-XL/data/variables/product.yml deleted file mode 100644 index dbe04055b6..0000000000 --- a/translations/es-XL/data/variables/product.yml +++ /dev/null @@ -1,158 +0,0 @@ ---- -#Contains versioned and unversioned variables for all of our product names -## WARNING: Versioned variables don't work as expected in articles under "content/enterprise/admin/". Use unversioned variables instead. -#Company -company_short: 'GitHub' -#GitHub's flagship products -## Until we have versioning to support GitHub Enterprise Cloud content, avoid using this variable if the output should specifically be GitHub Enterprise Cloud or GitHub Enterprise Server -product_name: >- - {% if currentVersion == "free-pro-team@latest" %}GitHub{% else %}GitHub Enterprise{% endif %} -## Use this variable when the output should always be GitHub, regardless of the product the user is using -prodname_dotcom: 'GitHub' -## Use this variable when the output should always be GitHub Enterprise, regardless of the product the user is using -prodname_enterprise: 'GitHub Enterprise' -## Use this variable only when the output should specifically be GitHub.com, to distinguish from GitHub the company or other GitHub products (e.g. connecting GHE to GitHub.com) -prodname_dotcom_the_website: 'GitHub.com' -## Use these variables when the output should reflect one of our two specific GitHub Enterprise offerings -prodname_ghe_server: 'Servidor de GitHub Enterprise' -prodname_ghe_cloud: 'GitHub Enterprise Cloud' -prodname_ghe_one: 'GitHub One' -## Use these variables when referring specifically to a location within a product -product_location: >- - {% if currentVersion == "free-pro-team@latest" %}GitHub{% else %}tu instancia de servidor de GitHub Enterprise{% endif %} -product_location_enterprise: 'tu instancia de servidor de GitHub Enterprise' -prodname_free_user: 'GitHub Free' -prodname_pro: 'GitHub Pro' -prodname_team: 'GitHub Team' -prodname_free_team: 'GitHub Free' -prodname_enterprise_backup_utilities: 'Utilidades de respaldo del servidor de GitHub Enterprise' -#GitHub Connect (enterprise accounts, other unified features) -## Phrase content so that the uncapitalized unified contributions or unified search variables are not used at the start of a sentence. -prodname_github_connect: 'GitHub Connect' -prodname_unified_contributions: 'contribuciones unificadas' -prodname_unified_search: 'búsqueda unificada' -#GitHub Education -prodname_education: 'GitHub Education' -prodname_education_community: 'Education Community' -prodname_classroom: 'GitHub Classroom' -prodname_student_pack: 'GitHub Student Developer Pack' -#GitHub CLI -prodname_cli: 'CLI de GitHub' -#GitHub Desktop -prodname_desktop: 'GitHub Desktop' -desktop_link: 'https://desktop.github.com/' -#GitHub for Mobile -prodname_mobile: 'GitHub para móvil' -prodname_ios: 'GitHub para iOS' -prodname_android: 'GitHub para Android' -#GitHub Pages -prodname_pages: 'Páginas de GitHub' -#CodeQL -prodname_codeql: 'CodeQL' -prodname_ql: 'QL' -#Apps, GitHub Marketplace, and integrations -prodname_marketplace: 'Mercado GitHub' -prodname_github_app: 'App GitHub' -prodname_github_apps: 'GitHub Apps' -prodname_oauth_app: 'App OAuth' -#API and developer docs -prodname_dev_docs: 'la documentación del programador de GitHub' -prodname_enterprise_api: 'la API del servidor de GitHub Enterprise' -prodname_support_forum: 'Foro de Soporte y Desarrollo de la API de GitHub' -prodname_support_forum_with_url: '[Foro de desarrollo y soporte de la API de GitHub](https://github.community/c/github-api-development-and-support/37)' -prodname_unfurls: 'Adjuntos de Contenido' -prodname_component_kit: 'Kit de Componentes de GitHub' -#GitHub Actions -## Use this variable only when referring to GitHub Actions the product. When referring to the thing that someone creates using the product, call it an action (small a). See the terminology page of the Brand Guide for more. -prodname_actions: 'GitHub Actions' -#GitHub Debug -prodname_debug: 'Depuración de GitHub' -#GitHub Packages -prodname_registry: 'Paquetes de GitHub' -prodname_github_container_registry: 'GitHub Container Registry' -prodname_container_registry: 'container registry' -#GitHub Insights -prodname_insights: 'GitHub Insights' -#GitHub Sponsors -prodname_sponsors: 'Patrocinadores de GitHub' -prodname_matching_fund: 'Fondo Compensatorio para Patrocinios de GitHub' -#GitHub Advanced Security -prodname_advanced_security: 'Advanced Security' -#Codespaces -prodname_codespaces: 'Codespaces' -prodname_vscode: 'Visual Studio Code' -prodname_vs_codespaces: 'Codespaces de Visual Studio' -prodname_vs: 'Visual Studio' -#GitHub resources: blog, jobs, Learning Lab -prodname_gcf: 'Soporte de la Comunidad de GitHub' -prodname_blog: 'el blog de GitHub' -prodname_jobs: 'Empleos GitHub' -prodname_learning: 'Laboratorio de aprendizaje de GitHub' -prodname_learning_link: 'https://lab.github.com/' -prodname_roadmap: 'Itinerario público de GitHub' -prodname_roadmap_link: 'https://github.com/github/roadmap#github-public-roadmap' -#GitHub support -premium_support_plan: 'Plan prémium' -premium_plus_support_plan: 'Premium Plus Plan/GitHub Engineering Direct' -microsoft_premium_plus_support_plan: 'GitHub Engineering Direct' -support_ticket_priority_urgent: 'Urgente' -support_ticket_priority_high: 'Alto' -support_ticket_priority_normal: 'Normal' -support_ticket_priority_low: 'Bajo' -#Security features / code scanning platform / Security Lab -prodname_security: 'GitHub Security Lab' -prodname_security_link: 'https://securitylab.github.com/' -prodname_security_advisories: 'GitHub Security Advisories' -#Security features and code scanning platform -prodname_secret_scanning: 'escaneo de secretos' -prodname_secret_scanning_caps: 'Escaneo de secretos' -prodname_code_scanning: 'escaneo de código' -prodname_code_scanning_capc: 'Escaneo de código' -prodname_codeql_runner: 'CodeQL runner' -prodname_advisory_database: 'GitHub Advisory Database' -prodname_codeql_workflow: 'CodeQL Analysis workflow' -#GitHub Dependabot -prodname_dependabot: 'Dependabot de GitHub' -prodname_dependabot_short: 'Dependabot' -prodname_dependabot_alerts: 'Alertas del Dependabot de GitHub' -prodname_dependabot_security_updates: 'Actualizaciones de seguridad del Dependabot de GitHub' -prodname_dependabot_version_updates: 'Actualizaciones de versión para el Dependabot de GitHub' -#GitHub Policies -prodname_policies: 'Políticas de GitHub' -#GitHub Archive Program -prodname_archive: 'Programa de Archivo de GitHub' -prodname_arctic_vault: 'Bóveda de Código del Ártico' -#Links -product_url: >- - {% if currentVersion == "free-pro-team@latest" %}github.com{% else %}[hostname]{% endif %} -pricing_url: 'https://github.com/pricing' -signin_link: >- - {% if currentVersion == "free-pro-team@latest" %}[Sign in](https://github.com/login){% else %}Inicio de sesión (`https://[hostname]/login`){% endif %} -signout_link: >- - {% if currentVersion == "free-pro-team@latest" %}[Sign out](https://github.com/logout){% else %}Cierre de sesión(`https://[hostname]/logout`){% endif %} -raw_github_com: >- - {% if currentVersion == "free-pro-team@latest" %}raw.githubusercontent.com{% else %}[hostname]/user/repo/raw{% endif %} -#GitHub Enterprise Server past versions -current-340-version: '11.10.354' -#Developer site product variables -#Use this inside command-line and other code blocks -doc_url_pre: >- - {% if currentVersion == "free-pro-team@latest" %}https://developer.github.com{% else %}https://developer.github.com/enterprise/{{currentVersion}}{% endif %} -#Use this inside command-line code blocks -api_url_pre: >- - {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% else %}http(s)://[hostname]/api/v3{% endif %} -#Use this inside command-line code blocks -#Enterprise OAuth paths that don't include "/graphql" or "/api/v3" -oauth_host_code: >- - {% if currentVersion == "free-pro-team@latest" %}https://github.com{% else %}http(s)://[hostname]{% endif %} -device_authorization_url: >- - {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}[`https://github.com/login/device`](https://github.com/login/device){% else %}`http(s)://[hostname]/login/device`{% endif %} -#Use this all other code blocks -api_url_code: >- - {% if currentVersion == "free-pro-team@latest" %}https://api.github.com{% else %}http(s)://[hostname]/api/v3{% endif %} -#Use this inside command-line code blocks -graphql_url_pre: >- - {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% else %}http(s)://[hostname]/api/graphql{% endif %} -#Use this all other code blocks -graphql_url_code: >- - {% if currentVersion == "free-pro-team@latest" %}https://api.github.com/graphql{% else %}http(s)://[hostname]/api/graphql{% endif %} diff --git a/translations/es-XL/data/variables/search.yml b/translations/es-XL/data/variables/search.yml deleted file mode 100644 index f54721e5df..0000000000 --- a/translations/es-XL/data/variables/search.yml +++ /dev/null @@ -1,11 +0,0 @@ ---- -advanced_url: >- - {% if currentVersion == "free-pro-team@latest" %}[advanced search](https://github.com/search/advanced) página{% else %}página de búsqueda avanzada (`https://[hostname]/search/advanced`){% endif %} -search_page_url: >- - {% if currentVersion == "free-pro-team@latest" %}[search](https://github.com/search) page{% else %}buscar página (`https://[hostname]/search`){% endif %} -search_highlighting_link: >- - Para obtener más detalles sobre cómo recibir resultados de búsqueda resaltados, consulta [Encontrar metadatos con coincidencias de texto](#text-match-metadata). -search_query_description: >- - La consulta contiene una o más palabras clave y calificadores. Los calificadores te permiten limitar tu búsqueda en áreas específicas de GitHub. La API de REST es compatible con los mismos calificadores qeu GitHub.com. Para aprender más acerca del formato de la consulta, visita [Construir una consulta de búsqueda](#constructing-a-search-query). -order_description: >- - Determina si el primer resultado de búsqueda devolvió la mayor cantidad de coincidencias (`desc`) o la menor cantidad de coincidencias (`asc`). Este parámetro se ignora a menos de que proporciones `sort`. Predeterminado: `desc` 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: ''